175
 iManager U2000 Unified Network Management System V100R006C02 SNMP NBI User Guide Issue 05 Date 2013-05-17 HUAWEI TECHNOLOGIES CO., LTD.

u2000 Snmp Nbi User Guide-(v100r006c02_05)

Embed Size (px)

Citation preview

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 1/175

iManager U2000 Unified Network Management

System

V100R006C02

SNMP NBI User Guide

Issue 05

Date 2013-05-17

HUAWEI TECHNOLOGIES CO., LTD.

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 2/175

 

Copyright © Huawei Technologies Co., Ltd. 2013. 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: [email protected]

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 3/175

About This Document

Related Versions

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

Product Name Version

iManager U2000 V100R006C02

 

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

DANGER

Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.

iManager U2000 Unified Network Management System

SNMP NBI User Guide About This Document

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

ii

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 4/175

Symbol Description

WARNING

Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.

CAUTION

Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,

 performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save

time.

NOTE Provides additional information to emphasize or supplement

important points of the main text.

 

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.

 

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 .

iManager U2000 Unified Network Management System

SNMP NBI User Guide About This Document

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

iii

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 5/175

Convention Description

> 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 05 (2013-05-17) Based on Product Version V100R006C02

Errors are corrected.

Changes in Issue 04 (2013-01-26) Based on Product Version V100R006C02

Errors are corrected.

Changes in Issue 03 (2012-10-30) Based on Product Version V100R006C02

l Errors are corrected.

l Change the ID of the port for sending traps from the default value 982 to 6666.

l Change the read community from the default value public to Changeme_123.

l Change the write community from the default value private to Changeme_123.

l Change the description of the password complexity rule.

Changes in Issue 02 (2012-08-15) Based on Product Version V100R006C02

The following topics are added.

l How to configure the heartbeat notification trap to hwNmNorthboundKeepAlive

l How to report additional VBs alarm trap

l How to configure T2000Support item

Changes in Issue 01 (2012-06-30) Based on Product Version V100R006C02

Initial release.

iManager U2000 Unified Network Management System

SNMP NBI User Guide About This Document

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

iv

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 6/175

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 Deploying and Configuring SNMP.........................................................................................20

4.1 Overview......................................................................................................................................................................224.2 Configuration Requirements.........................................................................................................................................23

4.3 Flow of Deploying the SNMP NBI..............................................................................................................................24

4.4 Collecting Integration Parameters................................................................................................................................25

4.5 Checking the License....................................................................................................................................................27

4.6 Starting the Msuite........................................................................................................................................................29

4.6.1 Starting the Process of the MSuite Server.................................................................................................................29

4.6.2 Logging In to the MSuite Client................................................................................................................................29

4.6.3 Changing the Password of the MSuite......................................................................................................................31

4.7 Checking the SNMP NBI Status..................................................................................................................................32

4.8 Adding SNMP NBI Component...................................................................................................................................33

iManager U2000 Unified Network Management System

SNMP NBI User Guide Contents

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

v

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 7/175

4.9 Configuring the SNMP NBI.........................................................................................................................................34

4.10 Testing the SNMP NBI...............................................................................................................................................44

4.10.1 U2000 MIB..............................................................................................................................................................44

4.10.2 U2000-T MIB..........................................................................................................................................................44

4.11 Configuration Sample.................................................................................................................................................45

4.11.1 Deploying the SNMPv1 NBI...................................................................................................................................45

4.11.2 Deploying the SNMPv3 NBI...................................................................................................................................49

5 Configuring the SNMP NBI on the OSS................................................................................54

5.1 Configuring the SNMPv1 or SNMPv2c NBI...............................................................................................................55

5.2 Configuring the SNMPv3 NBI.....................................................................................................................................56

6 Calling the SNMP NBI...............................................................................................................59

6.1 U2000 MIB Subinterfaces............................................................................................................................................60

6.1.1 Reporting Real-Time Alarms....................................................................................................................................606.1.2 Changing Filter Criteria.............................................................................................................................................60

6.1.3 Synchronizing Alarms...............................................................................................................................................62

6.1.4 Acknowledging Alarms.............................................................................................................................................66

6.1.5 Unacknowledging Alarms.........................................................................................................................................68

6.1.6 Clearing Alarms.........................................................................................................................................................70

6.2 U2000-T MIB Subinterfaces........................................................................................................................................73

6.2.1 Reporting Real-Time Alarms....................................................................................................................................73

6.2.2 Synchronizing Alarms...............................................................................................................................................73

7 Maintaining the SNMP NBI......................................................................................................767.1 Maintenance Description..............................................................................................................................................77

7.2 Deleting and Disabling an SNMP Interface.................................................................................................................77

7.2.1 Logging In to the System Monitor Client..................................................................................................................77

7.2.2 Stopping the SNMP NBI...........................................................................................................................................78

7.2.3 Disabling the SNMP NBI..........................................................................................................................................80

7.2.4 Restarting the SNMP NBI.........................................................................................................................................81

7.2.5 Deleting the SNMP NBI Instance.............................................................................................................................82

7.2.6 Deleting the SNMP NBI Component........................................................................................................................83

7.3 Faults and Solutions......................................................................................................................................................847.3.1 SNMP Service Process Is Not Displayed..................................................................................................................84

7.3.2 SNMP Service Process Fails to Be Started...............................................................................................................85

7.3.3 NMS User Cannot Connect to the SNMP NBI.........................................................................................................86

7.3.4 The OSS Cannot Receive Heartbeat Information......................................................................................................87

7.3.5 OSS Cannot Receive Real-Time Alarms...................................................................................................................87

7.3.6 Acknowledge or Un-acknowledge or Clear Alarms Fails.........................................................................................88

7.3.7 How to configure the heartbeat notification trap to hwNmNorthboundKeepAlive................................................89

7.3.8 How to report additional VBs alarm trap..................................................................................................................90

7.3.9 How to configure T2000Support  item.....................................................................................................................92

7.3.10 How to report the event alarm.................................................................................................................................93

iManager U2000 Unified Network Management System

SNMP NBI User Guide Contents

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

vi

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 8/175

A Relations Between License and SNMP Interface.................................................................94

B Configuration Parameters.........................................................................................................96

B.1 General Configuration.................................................................................................................................................97

B.1.1 SNMP Agent.............................................................................................................................................................97B.1.2 Third-Party NMS......................................................................................................................................................99

B.2 Advanced Configuration............................................................................................................................................102

B.2.1 Heartbeat.................................................................................................................................................................103

B.2.2 Alarm Field.............................................................................................................................................................103

B.2.3 Notification.............................................................................................................................................................109

B.2.4 Time Format............................................................................................................................................................110

B.2.5 Encoding Format.....................................................................................................................................................111

B.2.6 Alarm Relativity Config.........................................................................................................................................112

B.2.7 Engineering Alarm..................................................................................................................................................113

B.2.8 Other Settings..........................................................................................................................................................114

B.2.9 MIB Frame..............................................................................................................................................................115

C U2000 MIB..................................................................................................................................118

C.1 MIB Description........................................................................................................................................................119

C.2 Reported Alarm Field by U2000 MIB.......................................................................................................................119

C.3 U2000 MIB Trap........................................................................................................................................................124

C.3.1 Active Alarm Notification Trap..............................................................................................................................124

C.3.2 Active Alarm Synchronization Start Trap..............................................................................................................128

C.3.3 Active Alarm Report Trap......................................................................................................................................129C.3.4 Active Alarm Synchronization End Trap...............................................................................................................133

C.3.5 KeepAlive Info (Heartbeat) Trap............................................................................................................................134

C.4 U2000 MIB Trap Sample...........................................................................................................................................136

C.4.1 Active Alarm Trap..................................................................................................................................................136

C.4.2 Active Alarm Synchronization Start Trap..............................................................................................................138

C.4.3 Active Alarm Synchronization Result Trap............................................................................................................139

C.4.4 Active Alarm Synchronization End Trap...............................................................................................................140

C.4.5 Heartbeat.................................................................................................................................................................141

D U2000-T MIB.............................................................................................................................143D.1 MIB Description........................................................................................................................................................144

D.2 Reported Alarm Field by U2000-T MIB...................................................................................................................144

D.3 U2000-T MIB Trap....................................................................................................................................................147

D.3.1 Active Alarm Notification Trap..............................................................................................................................148

D.3.2 Active Alarm Synchronization Start Trap..............................................................................................................151

D.3.3 Active Alarm Report Trap......................................................................................................................................152

D.3.4 Active Alarm Synchronization End Trap...............................................................................................................155

D.4 U2000-T MIB Trap Sample.......................................................................................................................................156

D.4.1 Active Alarm Trap..................................................................................................................................................156

D.4.2 Active Alarm Synchronization Start Trap..............................................................................................................158

iManager U2000 Unified Network Management System

SNMP NBI User Guide Contents

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

vii

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 9/175

D.4.3 Active Alarm Synchronization Result Trap...........................................................................................................158

D.4.4 Active Alarm Synchronization End Trap...............................................................................................................159

E Service Ports Description........................................................................................................161

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

F Equipment Supported..............................................................................................................163

G Acronyms and Abbreviations................................................................................................165

iManager U2000 Unified Network Management System

SNMP NBI User Guide Contents

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

viii

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 10/175

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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 1 Preview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

1

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 11/175

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

NBI

This chapter describes the basic principles of the SNMP

 protocol, including its system architectures, message types,

and protocol versions.

4 Deploying and Configuring

SNMP

This chapter describes the methods for deploying and

configuring the SNMP NBI.

5 Configuring the SNMP

NBI on the OSS

This chapter describes how the OSS connects to the

U2000 through the SNMP NBI when different protocol

versions are used.

6 Calling the SNMP NBI This chapter describes how the OSS manages alarms on the

U2000 through the SNMP NBI.

7 Maintaining the SNMP

NBI

This chapter describes the routine maintenance and FAQs

of the SNMP NBI.

A Relations Between License

and SNMP Interface

This appendix describes license control items of the SNMP

 NBI.

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 License

and SNMP Interface

This appendix describes U2000-T MIB details, including

U2000-T MIB node descriptions, alarm fields, traps, and

trap examples.

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

G Acronyms and

Abbreviations

This appendix describes terms, acronyms and abbreviations

used in the document.

 

1.2 Reading Guide

This reading guide provides recommended chapters for different readers.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 1 Preview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

2

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 12/175

NOTE

The SNMP NBI supports two formats of management information bases (MIBs): U2000 MIB and U2000-T

MIB.

l Both HW-IMAPV1NORTHBOUND-TRAP-MIB.mib  and HW-IMAPV2NORTHBOUND-TRAP-

MIB.mib refer to the U2000 MIB, which is used to manage transport, access, and datacom devices, or cross-domain devices. V1 and V2 indicate the SMI (Structure of Management Information) versions of the HW-

IMAPV1NORTHBOUND-TRAP-MIB.mib  and HW-IMAPV2NORTHBOUND-TRAP-MIB.mib

respectively. The OSS selects a version based on its supported SMI version. SMI versions differ in syntax.

For details, see RFC 1155 and RFC 1902.

l T2000-NETMANAGEMENT-MIB.mib refers to the U2000-T MIB, which supports upgrades of original

transport NMSs and can manage only transport devices.

IntendedAudience

Purpose Recommended Chapter

 Network 

Planning

Engineer 

Design, plan, and optimize networks.

They need to know working

 principles, network positions, andinterface parameters (such as IP

address and ports) of the SNMP NBI.

2 Overview, 3 Introduction to the

SNMP NBI, A Relations Between

License and SNMP Interface, BConfiguration Parameters, and E

Service Ports Description

Application

Developer 

Develop the OSS and programs for 

interconnecting with the SNMP NBI.

They need to know basic principles,

functions, MIB structures, and

 parameter definitions of the SNMP

 NBI.

2 Overview, 3 Introduction to the

SNMP NBI, 4 Deploying and

Configuring SNMP, 5 Configuring

the SNMP NBI on the OSS, 6

Calling the SNMP NBI, B

Configuration Parameters, C

U2000 MIB, andD U2000-T MIB

Focus on C U2000 MIB and D

U2000-T MIB.

Installation

and

Commissioni

ng Engineer 

Data

Configuratio

n Engineer 

Deploy the SNMP NBI and verify its

connection with the OSS. They do

not need to know basic concepts or 

 principles of the SNMP NBI.

Chapters 5, 6, and 7, and 6, and

appendixes B and D

Focus on 4 Deploying and

Configuring SNMP. Complete

SNMP NBI deployment and

configuration by referring to the

flowchart and procedures.

4 Deploying and Configuring

SNMP, 5 Configuring the SNMP

NBI on the OSS, 6 Calling the

SNMP NBI, B Configuration

Parameters, andE Service Ports

Description

System

Maintenance

Engineer 

Maintain the SNMP NBI and

diagnose SNMP NBI faults. They

need to know working principles and

 parameters of the SNMP NBI.

2 Overview, 3 Introduction to the

SNMP NBI, 7 Maintaining the

SNMP NBI, B Configuration

Parameters, B Configuration

Parameters, andE Service Ports

Description

iManager U2000 Unified Network Management System

SNMP NBI User Guide 1 Preview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

3

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 13/175

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

4

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 14/175

2.1 Introduction

The Simple Network Management Protocol (SNMP) northbound interface (NBI) is one of the

 NBIs provided by the U2000. The operational support systems (OSSs) can access U2000 by the

SNMP NBI to monitor and manage alarms in Huawei equipment networks.

The SNMP protocol consists of a set of standards for network management and is the most

widely used protocol in TCP/IP networks. TCP is short for Transmission Control Protocol and

IP is short for Internet Protocol.

Huawei developed the SNMP NBI for the U2000 in compliance with industry standards. With

this NBI, OSSs can interconnect with the U2000 quickly and manage alarms on the network.

NOTE

OSSs are computer systems used by telecommunications carriers to manage performance, inventories,

services, and faults of network equipment efficiently. By function, OSSs can be classified into the serviceassurance 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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

5

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 15/175

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

NE1

NE2

NEn

Device Network

U2000

OSS

Get/Set SNMP Trap

Northbound SNMP

Interface

 

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

6

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 16/175

synchronizing, clearing, acknowledging, and unacknowledging. Alarm synchronizing is to

query active alarms.

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

ng alarms

Subscribes alarms by alarm severity and alarm category. You can set the severity

and category when deploying the SNMP NBI.

Sets the alarm field or variable binding (VB).

Reporting

alarms

Reports alarms from NEs or the U2000.

Reporting

heartbeat

Reports heartbeat and sets the heartbeat period.

 

OSS

At the OSS side, the primary functions are:

l Synchronizing alarms (querying current alarms)

l

Changing filter criteria in real timel Acknowledging/Unacknowledging alarms

l Clearing alarms

NOTE

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

7

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 17/175

Function Description

Synchronizing

alarms (querying

current alarms)

Queries current alarms (uncleared alarms) on the U2000 in the Set

operation.

To query current alarms on the U2000, the OSS issues the query begincommand (value: 1) in the Set operation. After receiving the

command, the SNMP agent queries current alarms from the U2000

and reports the result to the OSS. If there are too many alarms and

the query needs to be stopped, the OSS issues the query end command

(value: 0) in the Set operation. After receiving the command, the

SNMP agent stops querying and does not report the result to the OSS.

For details on alarm synchronization, see 6.1.3 Synchronizing

Alarms.

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

Querying alarms by

criteria

Reports alarms by alarm severity and category. The filter criteria are

specified during alarm subscription.

You can change filter criteria in real time when loading the U2000

MIB.

Changing filter 

criteria in real time

Changes filter criteria using the Set operation when the SNMP NBI

is running.

The change will take effect without restarting the SNMP NBI.

Acknowledging/

Unacknowledging

alarms

Acknowledges or unacknowledges current alarms on the U2000

 based on alarm serial numbers (SNs).

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

To enable this function, set third-party NMS parameters only on the U2000 when deploying the SNMP

 NBI instead of configuring the OSS. Alarm information will be received at the preset port of the OSS

server.

After receiving alarms from the equipment or the U2000, the SNMP NBI reports these alarms

to the OSS using standard SNMP traps. For details, see D.3 U2000-T MIB Trap.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

8

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 18/175

Function Description

Subscribi

ng alarms

Subscribes alarms by alarm severity and alarm category. You can set the severity

and category when deploying the SNMP NBI.

Reportingalarms

Reports alarms from NEs or the U2000.

 

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 6.2.2 Synchronizing Alarms.

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

Function DescriptionQuerying

all current

alarms

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

operation.

Querying

alarms by

criteria

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

during alarm subscription.

 

2.4 Security MechanismThe 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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

9

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 19/175

Figure 2-2 Security mechanism

NMS

SNMP alarm northbound interface

v3 uses user 

based security

mechanism

v1/v2c use

community name

based security

mechanism

SNMPv1 and SNMPv2The 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 onSNMPv3.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

10

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 20/175

Security Level

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

Table 2-1 Security Level

Version Security Level Authentication

DataEncryption

Description

v1 Without

authentication

and encryption

Community None Uses only

community

names for 

access

authentication.

v2c Without

authentication

and encryption

Community None Uses only

community

names for access

authentication.

v3 Without

authentication

and encryption

User name None Uses only user  

names for 

access

authentication.

v3 With

authentication

and without

encryption

MD5 or SHA None Uses MD5 or  

SHA algorithms

for 

authentication.

v3 With

authentication

and encryption

MD5 or SHA AES or DES Uses MD5 or  

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

11

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 21/175

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

connections

10

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%)

iManager U2000 Unified Network Management System

SNMP NBI User Guide 2 Overview

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

12

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 22/175

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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 3 Introduction to the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

13

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 23/175

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 

NMS Agent

MIBSNMP

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 3 Introduction to the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

14

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 24/175

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 collection of equipment that the agent can query or set.

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

Link Layer 

IP

UDP

SNMP

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.

Figure 3-3 SNMP PDUs

GetRequest

GetNextRequest

SetRequest

GetResponse

Trap

NMS Agent

iManager U2000 Unified Network Management System

SNMP NBI User Guide 3 Introduction to the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

15

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 25/175

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 3 Introduction to the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

16

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 26/175

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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 3 Introduction to the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

17

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 27/175

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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 3 Introduction to the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

18

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 28/175

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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 3 Introduction to the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

19

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 29/175

4 Deploying and Configuring SNMP

About This Chapter

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

following inf ormation:

4.1 Overview

This topic describes the background information and the terms involved in the process of 

deploying and configuring the northbound interface.

4.2 Configur ation 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 corres ponding functions.

4.3 Flow of Deploying the SNMP NBI

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

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

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

4.6 Starting the Msuite

The Msuite is a graphical system maintenance tool that is developed for the U2000. The

Msuite is used to deploy the instances and distributed system of the U2000.

4.7 Checking the SNMP NBI Status

After check the license and ensure it is support SNMP functions, you need to check the current

status of SNMP NBI, and deploy the SNMP NBI according the status.

4.8 Adding SNMP NBI Component

The SNMP NBI is one of the components of the U2000. If you have not installed the SNMP NBI by default, you need to add the SNMP NBI component.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

20

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 30/175

4.9 Configuring the SNMP NBI

To enable the SNMP NBI, install the SNMP NBI component and set SNMP NBI parameters by

referring to the network management system (NMS) planning guide. Besides, you can modify

the parameters. Generally, general parameters are mandatory while advanced parameters are

optional (default values are recommended). Advanced parameters are independent of each other 

and no configuration order is required.

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

4.11 Configuration Sample

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

21

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 31/175

4.1 Overview

This topic describes the background information and the terms involved in the process of 

deploying and configuring the northbound interface.

Attention Item

l  Northbound interface is an optional component of the U2000. A license is required for 

using this function.

l If you do not install the northbound interface component during the installation of the

U2000, you need to add it manually.

l The northbound interface is a System single-instance deployment package. Therefore, only

one instance can be deployed.

CAUTION

l After the northbound interface component is installed or added, you need to add a

corresponding instance and configure parameters. Then, the U2000 can start the NBI-related

 process.

l After initializing the database of the U2000, you need to configure the northbound interface

instance again.

l After the northbound interface instance is configured, you need to restart all the NMS

services.

l You can configure only one IP address for one network interface. It is not allowed to set

multiple IP addresses for the same network interface. It is suggested that configure multiple

network interface for multiple IP address.

l If the NAT is used to transform addresses between the Msuite server and clients, deploy the

 NBI on the Msuite client that installed on the U2000 server. Otherwise, the NBI may be

failure to deploy.

l The U2000 server and the OSS must can communicate with each other. Otherwise, the OSS

cannot interconnect with the NBI of the U2000. Therefore, if the U2000 server is configured

with multiple network interface cards (NICs) and the NICs are in different network segments,

set the IP address for connecting to the OSS as the IP address of the U2000 server.

l You must configure the northbound interface again after the IP of NMS changed.

Terms

The following explains certain confusable terms:

l Component: It is the software functional unit that you can choose to install. Each component

can include multiple deployment packages.

l Deployment package: It is the software unit deployed on a computer. In distributed mode,

the deployment packages of one component may be deployed on different computers.

According to the quantity of the instances supported, you can classify the deployment packages into the following types:

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

22

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 32/175

– System single-instance: In a set of U2000, the deployment package can be installed on

only one of the servers and can be deployed with only one instance.

– Single-server single-instance: In a set of U2000, the deployment package can be

installed on multiple servers but can be deployed with only one instance on each server.

– Single-server multi-instance: In a set of U2000, the deployment package can be installedon multiple servers and can be deployed with multiple instances on each server.

l Instance: It is a physical process that appears after the deployment package is deployed.

You can add the instance during the installation of the U2000, or add the instance through

the Msuite after the U2000 is installed.

NOTE

l Instance names are irrelevant with process names queried on the System Monitor. You can change

instance names by using the Msuite.

l The type of northbound interface deployment package is System single-instance.

MsuiteThrough the GUI of the Msuite, you can conveniently deploy the northbound interface.

The Msuite is a graphical maintenance tool developed for the Huawei iManager U2000, a type

of Huawei network product. The Msuite is used to debug, maintain, and redeploy the U2000.

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

Msuite.

4.2 Configuration Requirements

U2000 SNMP NBI and the U2000 server run on the same PC or Sun workstation, any additionalconfiguration 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 theU2000 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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

23

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 33/175

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.

4.3 Flow of Deploying the SNMP NBI

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

Contextl Through the GUI of the Msuite, you can conveniently deploy SNMP NBIs.

l SNMP NBI is an optional component of the U2000. A license is required for using this

function.

l If you do not install the SNMP interface component during the installation of the U2000,

you need to manually add it.

l The SNMP interface component is a single-instance system. Therefore, only one instance

can be deployed.

l After the northbound interface (SNMP) server component is installed or added, you need

to add a corresponding instance and configure parameters. Then, the U2000 can start the

SNMP-related process.

l After initializing the database of the U2000, you need to configure the SNMP NBI instance

again.

Flowchart of Deploying the SNMP NBI

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

24

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 34/175

Figure 4-1 Flowchart of deploying the SNMP NBI

Check the License

Start

Deploy for 

the first time?

 Add the Northbound

Interface Component

Configure the Northbound

Interface

End

Yes

Yes

No

No

Collect ConnectionParameters

Test the

Norhtbound Interface

 

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

CAUTION

l Collect general parameters only and use default values for advanced parameters.

l For U2000 upgrades, select the MIB structure carefully by referring to B.2.9 MIB Frame.

l Using SNMPv3 is recommended because of its higher security than SNMPv1 and SNMPv2c.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

25

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 35/175

Table 4-1 General parameters

Item Sample Description

U2000 server IP address 10.71.227.2

03

Indicates the IP address of the U2000

server. Set this parameter whenconfiguring the SNMP agent.

Port to send trap 6666 Indicates the U2000 server port that sends

traps to the OSS.

The default port is 6666. You can not use

the port 161. For more details about port,

see the chapter "U2000 Port List" in

iManager U2000 Administrator Guide.

 port to receive

the request

9812 Indicates the U2000 server port that

receives request packets form the OSS.

Up-layer 

 NMS server 

IP address 10.70.71.97 Indicates the IP address of the OSS server.

Set this parameter when setting third-

 party NMS parameters.

Ensure the OSS can communicate with the

U2000 by this IP.

Port to receive

trap

6666 Indicates the OSS server port that receives

traps from the U2000.

SNMPv1/v2c Read

Community

Changeme_ 

123

Indicates the community-based security

mechanism.

WriteCommunity

Changeme_ 123

SNMPv3 user name admin Indicates the security mechanisms that use

the user name, authentication password,

and encryption password.

For details, see B.1.2 Third-Party NMS.

Password

Authentication

U2k_snmpv

3

Password for 

Privacy

u2000_SN

MP

Alarm Filter Alarm Level Critical

Major 

Indicates the level of alarms that are

reported to the OSS.

Alarm Category Fault Alarm Indicates the category of alarms that are

reported to the OSS.

 

Table 4-2 Advanced parameter 

Item Sample Description

Heartbeat Need heartbeat

Heartbeat Period:

60 s

Specifies whether to send the heartbeat

information to the OSS and the heartbeat

 period.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

26

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 36/175

Item Sample Description

Alarm field to report N/A Indicates the alarm information to be

reported to the OSS.

For details, see B.2.2 Alarm Field.

Reported

 Notificatio

n

Reporting

Mode

Trap Indicates the notification mode, such as

trap and inform. The trap and inform

mode are supported.

Do not use the inform mode unless it is

required.

Trap Transmit

Interval

40ms Indicates the interval for sending

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

Retry

3 Indicates attempts to retransmit

information when the OSS does not

respond in inform mode.

Alarm Date Format UTC Indicates the time format for reported

alarms. The UTC time, local time

(without time zone) and local time (with

time zone) are supported.

For details, see B.2.4 Time Format.

Encoding Format UTF-8 Indicates the code format for reported

alarms. The UTF-8 and GBK are

supported.

For details, see B.2.5 Encoding

Format.

Record Log No Specifies whether to log alarms.

Real-time Alarm Cache Size 10000 Indicates the cache size for reported

alarms. Each OSS user is assigned an

independent cache.

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

MIB or U2000 MIB.

For details, see B.2.9 MIB Frame.

 

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

27

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 37/175

Prerequisites

l The U2000 has been installed.

l The U2000 license has been loaded.

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

Step 2 Open the directory that contain License. Use the text viewer to view the contents of the License

file. For the relations between the control items in the U2000 license file and the SNMP NBI

functional items, see Table 4-3.

NOTE

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 4-3 Description for License Item

License Control Item Abbreviation Value

Per Equivalent NE License

for NBI-SNMP Alarm-

Transmission Network 

LNSDPENES01 0-100000

Per Equivalent NE License

for NBI-SNMP Alarm -IP

LNSDPENES02 0-100000

Per Narrowband Port License

for NBI-SNMP Alarm-

Access Network 

LNSDPENEC21 0~8000000

Per Broadband Port License

for NBI-SNMP Alarm-

Access Network 

LNSDPENEC25 0~8000000

Per PON Terminal Resource

License for NBI-SNMP

Alarm-Access Network 

LNSDNELCR84 0~8000000

Compatible License for 

SNMP Alarm NBI-Access

 Network 

LNSDNELCR75 0~8000000

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

28

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 38/175

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

4.6 Starting the Msuite

The Msuite is a graphical system maintenance tool that is developed for the U2000. The

Msuite is used to deploy the instances and distributed system of the U2000.

For details of Msuite, refer to appendix "Msuite" in the iManager U2000 Administrator 

Guide.

4.6.1 Starting the Process of the MSuite Server

This topic describes how to start the process of the MSuite server.

Context

Generally, the process of the MSuite server server is started with the OS startup. If the process

is not started, perform the following operations to start it.

NOTE

If the server is a Netra 240, V240, or V440 workstation, the process of the MSuite server is not started with

the OS startup.

Procedure

l In Windows OS, check whether the msdaemon.exe and msserver.exe processes are started

in the Task Manager window. If you can find the two processes in the process list, the

MSuite server is running. If the two processes do not exist in the process list, the MSuite

server is not running. In this case, perform the following operations to start the MSuite

server:

Go to the C:\HWENGR\engineering path, and double-click the startserver.bat file.

l In Solaris or SUSE Linux OS, run the following command as user root to verify that the

MSuite server is running:

# ps -ef | grep java

The MSuite server is running if /opt/HWNMSJRE/jre_sol/bin/java -server or /opt/

HWNMSJRE/jre_linux/bin/java -server is displayed. Run the following commands to

start the MSuite server if it is not running:# cd /opt/HWENGR/engineering # ./startserver.sh

----End

4.6.2 Logging In to the MSuite Client

This topic describes how to log in to the MSuite client.

Prerequisites

The MSuite server must be started.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

29

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 39/175

Context

If you consecutively enters incorrect passwords three times, the IP address of the PC on which

the MSuite client is installed will be locked by the U2000. The U2000 will unlock this IP address

5 minutes later.

Procedure

Step 1 On a computer where the MSuite client is installed, double-click the U2000 NMS Maintenance

Suite shortcut icon on the desktop and then wait about one minute. The Login dialog box is

displayed.

NOTE

l In Solaris/SUSE Linux OS, log in to the Java desktop system as user nmsuser. Otherwise, the U2000

NMS Maintenance Suite shortcut icon is not displayed on the desktop. To start the MSuite client by

running commands, run the following commands as user nmsuser. If you have logged in as the root

user, you cannot run the su - nmsuser command to switch to the nmsuser user to run the following

command:$ cd /opt/U2000/engineering $ ./startclient.sh

l If a dialog box showing The client and server versions are different. Upgrade the client using the

CAU. is displayed, the method of upgrading the U2000 client by using the CAU is as follow:

1. Install the U2000 client software in network mode: Enter https://server_IP_address:10443/cau

(more secure) or http://server_IP_address:8080/cau in the address box of the Internet Explorer,

and press Enter to access the Web installation page. For details, see Installing the U2000 Client

in Network Mode in the U2000 Client Software Installation Guide.

2. If you upgrade the U2000 client software using the CAU, the MSuite client is also upgraded. For 

details, see Upgrading a Standalone U2000 Client in In-Service CAU Mode in the U2000 Client 

Upgrade Guide.

Step 2 Set the login parameters.The login parameters are described as follows:

l IP Address:

– To log in to the local MSuite server, use the default IP address 127.0.0.1.

– To log in to the remote MSuite server, enter the IP address of the computer where the

MSuite server is installed. If multiple IP addresses are configured for the computer, use

the NMS application IP address.

TIP

The Login dialog box of the MSuite client has the function to keep the login list. Selecting an IP address

from the IP Address drop-down list is recommended. If the desired IP address is not displayed in the

drop-down list, enter an IP address.

l Port No.: The default port ID is 12212. There is no need to change the default value during

login but ensure that the port is not occupied.

l User Name: The default user name is admin.

l Password: The default password is Changeme_123. If the password has been changed, enter 

the new password.

Step 3 Click Login.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

30

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 40/175

NOTE

l When you log in to the MSuite client, a progress bar is displayed showing the progress of querying

components and instances. Wait until the operation is complete.

l The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the MSuite at one

time.

l Change the initial password upon your first login to ensure U2000 system security and remember the new

 password. For details, see 4.6.3 Changing the Password of the MSuite.

----End

Exception Handling 

If a dialog box is displayed during the login, indicating that network configuration information

is inconsistent and re-synchronization is required after login, read through the message to learn

the server that needs to be synchronized. Then, update the network configuration, for details,

see iManager U2000 Administrator Guide.

4.6.3 Changing the Password of the MSuite

This topic describes how to change the password of the MSuite. To ensure the security of the

U2000, change the password of the MSuite immediately and record the password after installing

the U2000 server.

Context

In the high availability system, you only need to log in to the MSuite server on the primary site

and change the password of the MSuite. The password of the MSuite on the secondary site is

then automatically changed.

Procedure

Step 1 Log in to the MSuite client. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 On the MSuite client, choose System > Change Password from the main menu. The Change

Password dialog box is displayed.

Step 3 Click OK . The Change Password dialog box is displayed.

Step 4 Enter the old password and new password.

NOTE

The initial password is Changeme_123.

The rules for modifying a password are as follows:

l The password contains a minimum of 8 characters and a maximum of 30 characters.

l The password must contain at least three of the following combinations:

l At least one lower-case letter 

l At least one upper-case letter 

l At least one digit

l At least one special character ~@#^*()-_+|[{}]:./?<>&!$\"%'=;,`space

l The password cannot contain the user name written in either the forward or backward format.

If the password does not meet requirements, an error message will be displayed.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

31

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 41/175

Step 5 Click OK . The password is changed.

----End

4.7 Checking the SNMP NBI StatusAfter check the license and ensure it is support SNMP functions, you need to check the current

status of SNMP NBI, and deploy the SNMP NBI according the status.

Prerequisites

l The Msuite client communicates with the Msuite server in the normal state.

l Ensure that all Msuite servers are started.

l Ensure that the database is running.

Deploy Environmentl Log in to the Solaris or Linux OS as user nmsuser.

l Log in to the Windows OS as user Administrator.

l In a distributed system, you only need to log in to the NMS maintenance tool server of the

master server to perform this operation.

l In a high availability system, you only need to log in to the NMS maintenance tool server 

of the primary site to perform this operation.

Context

The SNMP NBI is one of the components of U2000. The installation of the SNMP NBI isintegrated in the process of installing the U2000 server. There are two cases of the installation.

l If the SNMP NBI is not installed during the installation of the U2000 server, to enable the

interface, you need to add the component first and then add the instance. For details, see

4.8 Adding SNMP NBI Component.

l If the SNMP NBI is installed during the installation of the U2000 server, to enable the

interface, you need to configure the instance. For details, see 4.9 Configuring the SNMP

NBI.

The details for how to install the U2000 Server, refer to iManager U2000 Software Installation

Guide. If you want to install SNMP NBI, ensure you have select Northbound SNMP Interface

component during the installation of the U2000 server.

Procedure

Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 Click Instance tab, check whether the AgentSNMP exist in the instance list.

l If the AgentSNMP instance exist, refer the steps in 4.9 Configuring the SNMP NBI to

enable the SNMP NBI.

l If the AgentSNMP instance not exist, you need to check whether the SNMP NBI

deployment package exist according to the Step 3.

Step 3 Click Deployment Package tabs, check whether the SNMP NBI exist in the deployment package list.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

32

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 42/175

l If the SNMP NBI deployment package exist, refer the steps in 4.9 Configuring the SNMP

NBI to enable the SNMP NBI.

l If the SNMP NBI deployment package not exist, refer the steps in 4.8 Adding SNMP NBI

Component to enable the SNMP NBI.

----End

4.8 Adding SNMP NBI Component

The SNMP NBI is one of the components of the U2000. If you have not installed the SNMP

 NBI by default, you need to add the SNMP NBI component.

Prerequisites

l The Msuite client communicates with the Msuite server in the normal state.

l Ensure that all Msuite servers are started.

l Ensure that the database is running.

l Ensure the installation directory has enough available space. In the Solaris or Linux OS,

you can run the df -hk /opt command to view the remaining space of the /opt directory.

Deploy Environment

l Log in to the Solaris or Linux OS as user nmsuser.

l Log in to the Windows OS as user Administrator.

l In a distributed system, you only need to log in to the NMS maintenance tool server of the

master server to perform this operation.

l In a high availability system, you only need to log in to the NMS maintenance tool server 

of the primary site to perform this operation.

Procedure

Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 On the Msuite client, choose Deploy > Add Component. The Add Component dialog box is

displayed.

CAUTION

l In the distributed system, the SNMP NBI could be deployed in master server only.

l You can add one SNMP NBI component only.

Step 3 Choose the North-Bound SNMP Interface component and click OK , the progress bar is

displayed.

Step 4 Wait until the message the component is successfully added is displayed. Click OK , completedthe operation

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

33

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 43/175

Step 5 View the deployment package list in the Deployment Package tab, the North-Bound SNMP

Interface deployment package exist indicate that the operation is successful.

----End

Follow-up Procedure

After the component is added, you need to configure the SNMP NBI instance, then you can

enable the SNMP interface.

4.9 Configuring the SNMP NBI

To enable the SNMP NBI, install the SNMP NBI component and set SNMP NBI parameters by

referring to the network management system (NMS) planning guide. Besides, you can modify

the parameters. Generally, general parameters are mandatory while advanced parameters are

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

Prerequisites

l The Msuite client communicates with the Msuite server in the normal state.

l Ensure that all Msuite servers are started.

l Ensure that the database is running.

l Ensure the installation directory has enough available space. In the Solaris or Linux OS,

you can run the df -hk /opt command to view the remaining space of the /opt directory.

l Ensure that the component for the instance to be added is installed. If the component is not

installed, install it first. For details, see adding SNMP NBI component.

CAUTION

l Set the MIB to U2000 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

Deploy Environment

l Log in to the Solaris or Linux OS as user nmsuser.

l Log in to the Windows OS as user Administrator.

l In a distributed system, you only need to log in to the NMS maintenance tool server of the

master server to perform this operation.

l

In a high availability system, you only need to log in to the NMS maintenance tool server of the primary site to perform this operation.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

34

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 44/175

Process of Configuring the SNMP NBI

Figure 4-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.

Figure 4-2 Process of configuring the SNMP NBI

Optional Start

Set receive trap IP/port

of NMS/OSS

Set alarm filter criteria

Set Advanced

parameters

End

Set send trap and receive

request IP/port on U2000

Choose SNMP version

Whether 

SNMPv3 is used?

Set the v3 security level,

authentication and encrption

Set read/write

community

Set v3 user name,

password for authentication

and encryption

 Add NMS/OSS

No

Yes

Multiple NMS?

Yes

No

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

35

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 45/175

CAUTION

l After filter criteria for correlative alarms and engineering alarms are set, restart the U2000

for these settings to take effect.l Using SNMPv3 is recommended because of its higher security than SNMPv1 and SNMPv2c.

Procedure

Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu.

Step 3 Click SNMP Agent on the General tab.

For details on the SNMP agent, see B.1.1 SNMP Agent.

1. Set the trap transmit IP address/port and request receive IP address/port.

By default, the trap transmit port is 6666 and the request receive port is 9812.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

36

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 46/175

CAUTION

The trap-transmitting IP address and request-receiving IP address are both the U2000 server 

IP address. Ensure that this IP address can be used for successful communication betweenthe 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 v1.

Step 4 Click Third-Party NMS and set parameters for the OSS.

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

1. Set the trap receive IP address/port. The trap receive IP address is the IP address of the OSS

server. The port is 6666 by default.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

37

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 47/175

NOTE

The Receive Trap Address is not the IP address of the U2000 server.

Currently a maximum of 10 third-party NMSs are supported.

The same SNMPv3 user configured for different third-party NMSs, for example, NMS 1 and NMS

2, must use the same authentication and encryption passwords

When the U2000-T MIB is used, the SNMP NBI identifies OSSs by read or write community.

l If multiple OSSs use the same read or write community, only the first OSS gets the synchronized

results when any of the OSSs tries to synchronize data.

l It is recommended that each OSS uses a unique read or write community so that the OSS can get

correct synchronized results.

CAUTION

In a Linux-based HA system, if the floating IP address function is enabled during NMS

installation, set Send Trap address and Receive Request from NMS address to floatingIP addresses.

2. Set SNMP security parameters. For security concern, input parameters are encrypted. For 

example, to set Read Community, click next to Read Community and set parameters

in the Set Password dialog box.

The following are the default security parameters. Modifying these parameters is

recommended for security concern.

l If the SNMP version is set to v1 or v2c, configure the read and write communities. By

default, the read community is Changeme_123 and the write community is

Changeme_123.

l If the SNMP version is set to v3, configure the V3 User Name, V3 Authentication

Password, and V3 Privacy Password for SNMPv3 users.

l By default, the user name is admin and the two passwords are blank.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

38

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 48/175

CAUTION

In the case of SNMPv3, the V3 User Name is required. If no user name is entered, the

SNMP service process cannot start after deployment.To ensure the security of the U2000, passwords must be complex enough. For example, a

 password must contain eight or more characters of two types. The allowed characters are

digits, letters, and special characters. Remember to change passwords regularly.

The password must meet the following requirements to safeguard your user account.

l Consists more than 8 characters.

l The password cannot be the user name or its reverse spelling.

l The password must consist of three of the following types of characters at least:

l Lower-case letters

l Upper-case letters

l Digits

l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ?

and space

3. Set the alarm filter criteria, including Alarm Level and Alarm Category.

NOTE

Alarms are reported to the OSS based on the defined alarm severity and category.

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

Fault: Indicates that the SNMP NBI will report alarm generation and alarm clearance. That is, the second

and third places of the value of AlarmCategoryFilter in binary mode are set to 0 when the

thirdNMSFaultFilter subinterface is invoked.

Event alarm reporting is disabled by default and cannot be configured by using the Msuite. But you can

enable this function by following methods.

l You can enable event alarm function manually. For details, see 7.3.10 How to report the event

alarm.

l To configure event alarm reporting, you can invoke the thirdNMSFaultFilter subinterface and set

the first place of the value of AlarmCategoryFilter in binary mode to 0.

4. Optional: Click New Tab Item. To add more third-party NMSs, repeat the preceding

substeps.

Step 5 Optional: Click the Advanced tab.

1. Click Heartbeat, 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 Period Default: 60s

3s~300s

Specifies the heartbeat period of the third-

 party NMS.

Report Heartbeat

Info

Default: Yes

Yes, No

Specifies whether send the heartbeat

information to the third-party NMS.

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

39

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 49/175

2. Click Alarm Field and set the alarm information to be reported. For details, see B.2.2

Alarm Field.

3. Click notification and set the reporting mode and other relevant parameters.

Parameter Description Value

Reporting

Mode

Default: Trap Mode

Trap Mode, Inform

Mode

Specifies the mode used by the SNMP

agent for sending alarms to the OSS.

Support X733

Alarm

Default: No

Yes, No

Specifies whether traps use the event 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

Interval

Default: 0

0 ms-1000 ms

Specifies the time interval for sending

messages in Trap mode.

Inform Delay Default: 5

5 s - 120 s

Indicates the interval between two

attempts to send information in inform

mode. The second attempt is performed if 

the OSS does not respond.

Inform Failure

Retry

Default: 3

2 times-6 times

Indicates attempts to resend information

when the OSS does not respond in inform

mode.

 

4. Click Time Format and set the date format for reported alarms.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

40

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 50/175

Parameters

Value Description

Alarm

Time

Format

Default: UTC

Time

UTC Time,

Local Time

(without Time

Zone), Local

Time (with

Time Zone)

Indicates the format of the alarm time.

UTC TimeThe format is as YYYY/MM/DD - hh:mm:ssZ.

Example: 2009/12/23 - 11:30:30Z

Local Time (without Time Zone)

The format is as YYYY/MM/DD - hh:mm:ss.

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.

 

5. Click Encoding Format and set the code format for traps.

Parameters Value Description

AlarmCharacter 

Default: UTF-8UTF-8, GBK 

There are two types of alarmcoding as follows: UTF-8, GBK.

 

6. Click Alarm Relativity Config and specify whether to report the correlative alarms.

Parameters

Value Description

Alarm

Relativity

Config

Default: All

alarms

All alarms,

Root Alarm

All alarms: Queries and reports all alarms including the

root alarm and correlative alarms.

Root Alarm: Queries and reports only the root alarm and

common alarms.

 

7. Click Engineering Alarm and specify whether to report the engineering alarms.

Parameters Value Description

Engineering

Alarm

Default: All alarms

All alarms, Engineering Alarm

Specifies whether to report the

engineering alarms.

 

8. Click Other Settings, specify whether to log alarms, and set the cache size for alarms.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

41

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 51/175

Parameters Value Description

Record Log Default: No

Yes, No

Specifies whether alarms are recorded in logs.

Real-time Alarm

Cache Size

Default:

10000

0-50000

Specifies the cache for real-time alarms. Each

 NMS/OSS user is assigned with an independent

cache.

When the alarm generate rate is more than the

alarm reporting rate, the SNMP NBI will buffer the

alarm data in the cache.

 

9. Click MIB Frame and set the MIB structure and resource information for alarms.

CAUTION

Select an appropriate MIB structure based on integration scenarios. For details, see B.2.9

MIB Frame.

Step 6 Click OK  to complete the settings.

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.

Step 7 Optional: For an HA system with multiple network interface cards (NICs), if you use the IP

address of the primary site to deploy the SNMP NBI and this IP address is not displayed in the

required drop-down list, the Address for Standby Server dialog box will be displayed.

1. Set the IP address of the secondary site for the SNMP NBI.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

42

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 52/175

CAUTION

l The SNMP NBI can be deployed on the primary site only.

l You can set any of the IP addresses of the secondary site (except for 127.0.0.1). Ensurethat the secondary site can communicate with the OSS properly using this IP address.

l The SNMP NBI searches the IP configuration list (or host files) automatically and binds

the first IP address to the primary site. If necessary, manually bind an appropriate IP

address that can be used for communication.

l Receive Request from NMS address is mandatory, while Send Trap address is

optional. These two IP addresses can be different.

2. Click OK  to complete the settings.

Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.

WARNING

After the following operations, you must restart U2000.

l Deploy the SNMP NBI for the first time.

l Modify the Alarm Relativity Config or Engineering Alarm item.

Step 9 Optional: Click OK  to close the dialog box.

Step 10Optional: Log in to the System Monitor.

 Restart all processes of the U2000.Step 11 Check the status of the SNMP Service process. If the process is running, the SNMP NBI has

 been enabled successfully.

----End

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

43

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 53/175

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

4.10.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 The Heartbeat parameter on the Advanced tab is configured.

Heartbeat Period: 60s

Report Heartbeat Info: yes

Procedure

Step 1 On the System Monitor client, check the status of the SNMP service. If Status is Running, the

SNMP NBI is enabled.

l If no SNMP NBI process is f ound, see the 7.3.1 SNMP Service Process Is Not Displayed

for troubleshooting.

l If the SNMP NBI process fails to be started, see the 7.3.2 SNMP Service Process Fails to

Be Started for troubleshooting.

Step 2 Check whether heartbeat messages are received on the related OSS port. If no heartbeat message

is received, see the 7.3.4 The OSS Cannot Receive Heartbeat Information for 

troubleshooting.

----End

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

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 7.3.1 SNMP Service Process Is Not Displayedfor troubleshooting.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

44

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 54/175

l If the SNMP NBI process fails to be started, see the 7.3.2 SNMP Service Process Fails to

Be Started for troubleshooting.

----End

4.11 Configuration Sample

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

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

Prerequisitesl The Msuite has been started.

l The SNMP NBI component has been installed.

Network Planning 

The MIB file HW-IMAPV1NORTHBOUND-TRAP-MIB.mib is loaded to the OSS, as shown

in Figure 4-3. The OSS manages and monitors alarms from Huawei network equipment using

the SNMPv1 NBI. Table 4-4 and Table 4-5 list detailed parameters.

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

Configuration Parameters.

Table 4-4 Server parameters for the SNMPv1 NBI

Server Parameters Value

Upper-layer 

 NMS

IP address 10.70.71.97

 NMS Receive Trap Address 6666

MIB HW-IMAPV1NORTHBOUND-

TRAP-MIB.mib

U2000 IP address 10.71.226.158

Send Trap Port 6666

Receive Request from NMS address 9812

 

Table 4-5 Communication parameters for the SNMPv1 NBI

Parameters Value

SNMP Version SNMPv1

Read Community Changeme_123

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

45

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 55/175

Parameters Value

Write Community Changeme_123

 

Figure 4-3 Network planning parameters for the SNMPv1 NBI

Device Network

Informset/get

IP: 10.70.71.97

Received Port: 6666

MIB: HW-IMAPV1NORTHBOUND-TRAP-MIB.mib

IP: 10.71.226.158Received Port: 9812

Send Port: 9832

OSS

U2000

Read Community: Changeme_123

Wirte Community: Changeme_123

 

Procedure

Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu.

Step 3 Click the General tab and choose SNMP Agent from the navigation tree to set parameters for 

the SNMP agent.

SNMP agent parameters are U2000 server parameters.

l Send Trap address: 10.71.226.158 Port: 6666

l Receive Request from NMS address: 10.71.226.158 Port: 9812

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

46

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 56/175

Step 4 In the right pane, set the SNMP version (in this example, v1 is selected).

NOTE

Select v2c if SNMPv2c is used to deploy the SNMP NBI.

Step 5 Choose Third-Party NMS from the navigation tree to set parameters for third-party NMSs in

the right pane.

Third-party NMS parameters are OSS parameters. Set the parameters according to the data plan.

l  NMS Receive Trap Address: 10.70.70.97

l Port: 6666

l Read Community: Changeme_123

l Write Community: Changeme_123

NOTE

Parameter for SNMPv3 (such as user name/password, authentication password, and encryption password)

are invalid if v3 is not selected.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

47

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 57/175

Step 6 Click the Advanced tab and choose MIB Frame from the navigation tree. In the right pane,

select U2000 MIB from the MIB drop-down list.

Step 7 Click OK . The U2000 starts to redeploy the SNMP NBI.

Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

48

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 58/175

WARNING

After the following operations, you must restart U2000.

l Deploy the SNMP NBI for the first time.

l Modify the Alarm Relativity Config or Engineering Alarm item.

Step 9 Optional: Click OK  to close the dialog box.

----End

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

l The Msuite has been started.

l The SNMP NBI component has been installed.

Network Planning 

The MIB file T2000-NETMANAGEMENT-MIB.mib is loaded to the OSS, as shown in

Figure 4-4. The OSS manages and monitors alarms from Huawei network equipment using the

SNMPv1 NBI. Table 4-6 and Table 4-7 list detailed parameters.

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

Table 4-6 Server parameters for the SNMPv3 NBI

Server Parameters Value

Upper-layer 

 NMS

IP address 10.70.71.97

 NMS Receive Trap Address 9833

MIB T2000-NETMANAGEMENT-

MIB.mib

U2000 IP address 10.71.226.158

Send Trap Port 9831

Receive Request from NMS address 9832

 

Table 4-7 Communication Parameters for the SNMPv3 NBI

Parameters Value

SNMP Version SNMPv3

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

49

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 59/175

Parameters Value

Security Level With authentication and encryption

V3 User Name admin

V3 Password Authentication U2ksnmp_v3

V3 Password for Privacy u2000_SNMP

 

Figure 4-4 Network planning parameters for the SNMPv3 NBI

Device Network

SNMPv3Informset/get

IP: 10.70.71.97

Received Port: 9833

MIB: T2000-NETMANAGEMENT-MIB.mib

IP: 10.71.226.158

Received Port: 9832

Send Port: 9831

OSS

U2000

User: admin

 Authentication password: U2ksnmp_v3

Encryption password: u2000_SNMP

Procedure

Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu.

Step 3 Click the General tab and choose SNMP Agent from the navigation tree to set parameters for 

the SNMP agent.

SNMP agent parameters are U2000 server parameters.

l Send Trap address: 10.71.226.158 Port: 9831

l Receive Request from NMS address: 10.71.226.158 Port: 9832

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

50

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 60/175

Step 4 In the right pane, set the SNMP version (in this example, v3 is selected).

l Security Model: USM

l Security Level: With authentication and encryption

l Authentication: HMACMD5

l Data Encryption: DES

Step 5 Click the General tab and choose Third-Party NMS from the navigation tree to set parameters

for third-party NMSs.

Third-party NMS parameters are OSS parameters. Set the parameters according to the data plan.

l  NMS Receive Trap Address: 10.70.71.97

l Port: 9833

l V3 User Name: admin

l V3 Password Authentication: U2ksnmp_v3

l V3 Password for Privacy: u2000_SNMP

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

51

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 61/175

Step 6 Click the Advanced tab and choose MIB Frame Setting from the navigation tree. In the right

 pane, select T2000-MIB from the MIB drop-down list.

Step 7 Click OK . The U2000 starts to redeploy the SNMP NBI.

Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

52

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 62/175

WARNING

After the following operations, you must restart U2000.

l Deploy the SNMP NBI for the first time.

l Modify the Alarm Relativity Config or Engineering Alarm item.

Step 9 Optional: Click OK  to close the dialog box.

----End

iManager U2000 Unified Network Management System

SNMP NBI User Guide 4 Deploying and Configuring SNMP

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

53

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 63/175

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

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

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 5 Configuring the SNMP NBI on the OSS

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

54

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 64/175

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

Prerequisites

l For SNMP NBI deployment, the SNMP version has been set to SNMPv1 or SNMPv2c,

and write and read communities have been configured.

l For SNMP NBI deployment, third-party NMS parameters have been set properly and the

OSS can receive real-time alarms or heartbeat from the U2000.

Procedure

Step 1 Confirm SNMP NBI parameters with the U2000 administrator.

1. Log in to the Msuite client.

2. On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the

main menu. View parameters as follows.

Parameters

Description Default Value Navigation Path

IP

address and

 port of 

U2000

Indicates the

request receive IPaddress/port on the

U2000.

9812

This value can

 be modified

 based on system

conditions.

On the General tab, choose SNMP

Agent from the navigation and viewReceive Request from NMS address

and Port in the right pane.

SNMP

Versio

n

Indicates the SNMP

version for the

SNMP NBI.

v1 On the General tab, choose SNMP

Agent from the navigation tree and view

SNMP version in the right pane.

Read/

Write

Comm

unity

Indicates the access

authentication for 

the OSS to connect

to the U2000through the SNMP

 NBI.

Read

Community:

Changeme_123

WriteCommunity:

Changeme_123

On the General tab, choose Third-Party

NMS from the navigation tree and view

Read Community and Write

Community in the right pane.

 

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 5 Configuring the SNMP NBI on the OSS

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

55

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 65/175

CAUTION

Confirm with the U2000 administrator if you need to modify a parameter; otherwise, the

connection may fail.

----End

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

Procedure

Step 1 Confirm SNMP NBI parameters with the U2000 administrator.

1. Log in to the Msuite client.

2. On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the

main menu. View parameters as follows.

Parameters Description DefaultValue

Navigation Path

IP address

and port of 

U2000

Indicates the

request receive IP

address/port on

the U2000.

9812

This value can

 be modified

 based on

systemconditions.

On the General tab, choose SNMP

Agent from the navigation tree and

view Receive Request from NMS

address and Port in the right pane.

SNMP

Version

Indicates the

SNMP version for 

the SNMP NBI.

v1

Change the

value to v3 if 

SNMPv3 is

used.

On the General tab, choose SNMP

Agent from the navigation and view

SNMP version in the right pane.

Security

Model

USM model USM model   l Specifies the security model of the

SNMPv3 protocol.

l USM: User-based Security

Mechanism

iManager U2000 Unified Network Management System

SNMP NBI User Guide 5 Configuring the SNMP NBI on the OSS

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

56

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 66/175

Parameters Description DefaultValue

Navigation Path

Security

Level

Indicates the

security level,

including without

authentication

and encryption,

with

authentication

and without

encryption, and

with

authentication

and encryption.

Without

authentication

and encryption

On the General tab, choose SNMP

Agent from the navigation and view

Security Level in the right pane.

Authenticati

on Protocol

Indicates the

authentication

algorithm,

including NONE,

HMACMD5, and

HMACSHA.

 NONE On the General tab, choose SNMP

Agent from the navigation and view

Authentication in the right pane.

Data

Encryption

Protocol

Including the

encryption

algorithm,

including NONE,

DES, and AES.

 NONE On the General tab, choose SNMP

Agent from the navigation and view

Data Encryption.

User Name Indicates the user name for 

authentication.

admin On the General tab, choose Third-Party NMS from the navigation. In

the right pane, click the tab for 

configured OSSs and view V3 User

Name.

Authenticati

on Password

Indicates the

authentication

 password.

The default

value is left

 blank.

On the General tab, choose Third-

Party NMS from the navigation. In

the right pane, click the tab for 

configured OSSs and view V3

Authentication Password.

DataEncryption

Password

Indicates the dataencryption

 password.

The defaultvalue is left

 blank.

On the General tab, choose Third-Party NMS from the navigation. In

the right pane, click the tab for 

configured OSSs and view V3

Privacy Password.

 

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 5 Configuring the SNMP NBI on the OSS

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

57

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 67/175

CAUTION

Confirm with the U2000 administrator if you need to modify a parameter; otherwise, the

connection may fail.

----End

iManager U2000 Unified Network Management System

SNMP NBI User Guide 5 Configuring the SNMP NBI on the OSS

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

58

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 68/175

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

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

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

59

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 69/175

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

CAUTION

Ensure that the U2000 MIB has been loaded to the OSS. To load the U2000 MIB, set the MIB

type to U2000 MIB when deploying the SNMP NBI.

6.1.1 Reporting Real-Time AlarmsYou 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.

Context

The SNMP NBI component has been installed and the SNMP NBI instance has been configured

on the U2000.

After the trap-receiving IP address or port and SNMP version have been set for the OSS on the

U2000, the OSS can receive real-time alarms.

You do not need to set related parameters on the OSS. Ensure that the OSS is properly connected

to the U2000 and the related ports are permitted by the firewall.

For details on how to deploy and configure the SNMP NBI, see 4 Deploying and Configuring

SNMP.

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

iso(1).org(3).dod(6).internet(1).private(4).enterprises

(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent(1).hwNmFault(3).thirdNMSFaultFilter(5)

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

60

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 70/175

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

Table 6-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

vel

Indicates the severity of an alarm.

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.

AlarmCategor 

yFilter 

Indicates the category of an alarm.

Six binary digits are used to represent event, fault, clear, 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.

 

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

61

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 71/175

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

(fault or clear).

Table 6-2 shows the parameters of this sample.

Table 6-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

Reported

Critical, Major 0011

Alarm Category to be

Reported

Fault Alarm, Clear 100111

 

Procedure

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

The OSS receives responses from the U2000, indicating that the filter criteria are changed

successfully. The OSS will then receive the required alarms only.

6.1.3 Synchronizing Alarms

The SNMP NBI allows the OSS to initiate the synchronization operation to ensure that the alarminformation 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 6-1 shows the alarm synchronization process.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

62

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 72/175

Figure 6-1 Alarm synchronization process

SNMP NBINMS/OSS

Set alarmsynchronization start node

Report alarm

synchronization start trap

Report alarm

synchronization result trap  All

 Alarms

are

reported

Set alarm

synchronization start node

Report alarm

synchronization stop trap

Report the 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.

Stop the alarm

synchronization

1. The OSS stops the alarm 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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

63

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 73/175

iso(1).org(3).dod(6).internet(1).private(4).enterprises

(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent

(1).hwNmNorthboundEvent(7).hwNmNorthboundEventSynchronization

(7).hwNmNorthboundEventSynchronizationCommandStart(4)

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent

(1).hwNmNorthboundEvent(7).hwNmNorthboundEventSynchronization

(7).hwNmNorthboundEventSynchronizationCommandStop(5)

Object Syntax Max Access Description

hwNmNorthboundE

ventSynchroniza-

tionCommandStart

Octet string read-write Indicates that the

alarm

synchronization is

started.

hwNmNorthboundEventSynchroniza-

tionCommandStop

Octet string read-write Indicates that thealarm

synchronization is

stopped.

 

Setting Method

Start alarm synchronization.

The OSS can set the value of the MIB node to start alarm synchronization within a specified

time. The format is as follows:

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

You do not need to set the start and end time to stop the alarm synchronization.

Table 6-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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

64

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 74/175

Parameter Description

start

time:endtime

Indicates the start and end time for alarm synchronization.

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.

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 6-4 shows the parameters of this sample.

Table 6-4 Sample parameters - synchronizing alarms

Parameter Value MIB Object

The IP of the upper-layer 

 NMS

10.70.73.97 10.70.73.97

Receive Trap Port 6666 6666

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

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

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

65

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 75/175

Procedure

1. The OSS sets hwNmNorthboundEventSynchronizationCommandStart to:

10.70.73.97:6666:20110301000000:20110315000000

l The OSS receives traps from the U2000, indicating that the synchronization is started.

l The U2000 reports alarms saved in the database that are generated during the preset

time period.

2. Optional:

To stop the synchronization, the OSS sets

hwNmNorthboundEventSynchronizationCommandStop to 10.70.73.97:6666.

3. After the synchronization is completed or stopped, the U2000 sends traps through the

SNMP NBI to inform the OSS that the synchronization is ended.

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

CAUTION

The Acknowledgement User parameter is SNMP Agent User on the U2000 client after an

alarm is acknowledged by the OSS through the SNMP NBI.

Alarms with invalid or nonexistent serial numbers and historical alarm cannot be acknowledged

and the serial numbers will be returned to the OSS.

MIB Definition

The OID is 1.3.6.1.4.1.2011.2.15.1.3.7.

The full path is

iso(1).org(3).dod(6).internet(1).private(4).enterprises

(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent

(1).hwNmFault(3).hwNmAcknowledgeAlarms(7)

Object Type Max Access Description

hwNmAcknowledg-

eAlarms

Octet string read-write Indicates that alarms

are acknowledged

 based on serial

numbers.

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

66

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 76/175

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 6-5 Format description - acknowledging alarms

Parameter Description

Serial

Number,Se

rial

Number,...

alarm serial number 

Integer, separated by a comma.

 

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

Table 6-6 Alarm states - acknowledging alarms

Sl.No Alarm Status Status Change SET Response Failed List

1 Unacknowledge

and Unclear 

Acknowledge

and Unclear 

Success Empty

2 Unacknowledge

and Clear 

Acknowledge

and Clear 

Success Empty

3 Acknowledge

and Unclear 

Acknowledge

and Unclear 

Success Empty

4 Acknowledge

and Clear 

 NA Success serial number 

 

NOTE

If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical

alarms, no data will be returned after you acknowledge these alarms. The life cycle specifies the period in

which these alarms are saved in the current-alarm database.

Sample

Prerequisite

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

Purpose

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

67

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 77/175

Table 6-7 shows sample parameters.

Table 6-7 Sample parameters - acknowledging alarms

Parameter Value MIB ObjectAlarm serial number  20,30,10005,18000 20,30,10005,18000

 

Procedure

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.

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.

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

CAUTION

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).huawei(2011).products(2).hwNetManagement(15).hwNmAgent(1).hwNmFault(3).hwNmUnAcknowledgeAlarms(8)

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

68

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 78/175

Object Type Max Access Description

hwNmUnAcknowl-

edgeAlarms

Octet string read-write Indicates that alarms

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:

Serial Number,Serial Number,...

Table 6-8 Format description - unacknowledging alarms

Parameter Description

Serial

Number,Se

rial

Number,..

.

alarm serial number 

Integer, separated by a comma.

 

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

Table 6-9 Alarm states - unacknowledging alarms

Sl.No Alarm Status Status Change SET Response Failed List

1 Unacknowledge

and Unclear 

Unacknowledge

and Unclear 

Success Empty

2 Unacknowledgeand Clear  Unacknowledgeand Clear  Success Empty

3 Acknowledge

and Unclear 

Unacknowledge

and Unclear 

Success Empty

4 Acknowledge

and Clear 

 NA Success serial number 

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

69

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 79/175

NOTE

If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical

alarms, no data will be returned after you unacknowledge these alarms. The life cycle specifies the period

in which these alarms are saved in the current-alarm database.

Sample

Prerequisite

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

Purpose

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

Table 6-10 shows the parameters of this sample.

Table 6-10 Sample parameters - unacknowledging alarms

Parameter Value MIB Object

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

 

Step

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

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

70

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 80/175

CAUTION

The Clearance User parameter is SNMP Agent User on the U2000 client after an alarm is

cleared by the OSS through the SNMP NBI.Alarms with invalid or nonexistent serial numbers and historical alarm cannot be cleared and

the serial numbers will be returned to the OSS.

MIB Definition

The OID is 1.3.6.1.4.1.2011.2.15.1.3.6.

The full path is

iso(1).org(3).dod(6).internet(1).private(4).enterprises

(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent(1).hwNmFault(3).hwNmClearAlarms(6)

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 6-11 Format description - clearing alarms

Parameter Description

Serial

Number,Se

rial

Number,..

.

alarm serial number 

Integer, separated by a comma.

 

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

71

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 81/175

Table 6-12 Alarm status - clearing alarms

Sl.No Alarm Status Status Change SET Response Failed List

1 Unacknowledge

and Unclear 

Unacknowledge

and Clear 

Success Empty

2 Unacknowledge

and Clear 

Unacknowledge

and Clear 

Success Empty

3 Acknowledge

and Unclear 

Acknowledge

and Clear 

Success Empty

4 Acknowledge

and Clear 

 NA Success serial number 

 

NOTE

If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical

alarms, no data will be returned after you clear these alarms. The life cycle specifies the period in which

these alarms are saved in the current-alarm database.

Sample

Prerequisite

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

Purpose

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

Table 6-13 shows the parameters of this sample.

Table 6-13 Sample parameters - clearing alarms

Parameter Value MIB Object

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

 

Procedure

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 changesalong with the alarms. The alarm time is when the alarm is cleared.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

72

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 82/175

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

CAUTION

Ensure that the U2000-T MIB has been loaded to the OSS. To load the U2000-T MIB, set the

MIB type to U2000-T MIB when deploying the SNMP NBI.

6.2.1 Reporting Real-Time Alarms

You do not need to set any parameters for the OSS to receive alarm packets from the U2000through the SNMP NBI. After the SNMP NBI is properly deployed on the U2000, alarms will

 be reported to the OSS in real time.

Context

The SNMP NBI component has been installed and the SNMP NBI instance has been configured

on the U2000.

After the trap-receiving IP address or port and SNMP version have been set for the OSS on the

U2000, the OSS can receive alarms in real time.

You do not need to set related parameters on the OSS. Ensure that the OSS is properly connected

to the U2000 and the related ports are permitted by the firewall.

For details on how to deploy and configure the SNMP NBI, see 4 Deploying and Configuring

SNMP.

CAUTION

The reported alarm field for the U2000-T MIB consists of 36 bound variables (VBs). For details,

see D.2 Reported Alarm Field by U2000-T MIB.

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

Function

The UDP-based SNMP protocol cannot guarantee that all alarms are reported to the OSS and

some alarm packets may be lost. Therefore, the OSS synchronizes alarms to ensure alarm data

consistency and can also stop the synchronization.

After the synchronization starts, the U2000 sends traps through the SNMP NBI to inform theOSS that the alarm synchronization is started.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

73

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 83/175

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

Figure 6-2 Alarm synchronization process

SNMP NBINMS/OSS

Set alarm

synchronization start node

Report alarm

synchronization start trap

Report alarm

synchronization result trap  All

 Alarms

are

reported

Set alarm

synchronization start node

Report alarm

synchronization stop trap

Report the alarmsynchronization stop trap

.

.

.

.

.

.

.

.

Operation Description

Synchronize alarms 1. The OSS synchronizes alarms.

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

synchronization

1. The OSS stops the alarm 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.

MIB Definition

The OID is 1.3.6.1.4.1.2011.2.15.1.7.4.1.

The full path is

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

74

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 84/175

iso(1).org(3).dod(6).internet(1).private(4).enterprises

(1).huawei(2011).products(2).netManagement(15).nmAgent

(1).nmNorthboundEvent(7).northboundSynchAlarm

(4).northBoundSynchAlarmCommand(1)

Object Type Max Access Description

northBoundSynchA-

larmCommand

Integer read-write Indicates that the

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 isas follows:

number

Table 6-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 northBoundSynchAlarmCommand node to 1.

l The OSS receives traps from the U2000, indicating that the synchronization is started.

l The U2000 reports alarms saved in the database that are generated during the set time

 period.

2. Optional:

To stop the synchronization, set the northBoundSynchAlarmCommand node to 0.

3. After the synchronization is completed or stopped, the U2000 sends traps through the

SNMP NBI to inform the OSS that the synchronization is ended.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 6 Calling the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

75

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 85/175

7 Maintaining the SNMP NBI

About This Chapter

This chapter introduces how to maintain the SNMP NBI.

7.1 Maintenance Description

This section describes the basic requirement of maintenance SNMP NBI.

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

7.3 Faults and SolutionsThis section introduces the faults of the SNMP NBI and the related solutions.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

76

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 86/175

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

l Windows or the Sun workstation - Solaris 8 or Solaris 10, and Linux

l The SNMP protocol

l 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 Msuite.

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

7.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, youare recommended to use the Security (SSL) mode.

l The port used for login in common mode is different from that in SSL mode. The port

number is 31030 in common mode, and 31080 in security (SSL) mode.

l After last login, if you do not log in again during the preset period, your account hibernates

or the U2000 deletes the account.

l If you never use a new user account for login, the U2000 does not invalidate or delete the

account.

Procedure

Step 1 Double-click the shortcut icon on the desktop to start the system monitor client.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

77

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 87/175

NOTE

In the Solaris and Linux OS , login to the OS of the server as the nmsuser user. Run the following command

to start the system monitor client.

$ cd /opt/U2000/client

$ ./startup_sysmonitor_global.sh

/opt/U2000 is the default installation path for the U2000. You can change it as required.

Step 2 In the Login dialog box, select a server by selecting an IP address or host name from the

Server drop-down list.

NOTE

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), andthen 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 youcannot 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

7.2.2 Stopping the SNMP NBI

If you need not use the SNMP NBI, you can stop the process of the SNMP NBI by using the

System Monitor client.

Prerequisites

l Log in to the Solaris or Linux OS as user nmsuser.

l Log in to the Windows OS as user Administrator.

l The U2000 must be operating.

l The SNMP Service processes are in the Running state.

Context

NOTE

After the SNMP interface instance is added through the Msuite, the default start mode is Automatic. TheSNMP interface process is started with the U2000.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

78

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 88/175

Procedure

Step 1 Log in to the System Monitor.

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

Step 3 Select SNMP Service process, right-click and choose Stop the Process.

Step 4 The prompt dialog box displayed, click Yes.

Step 5 On the System Monitor client, if Status of the related processes of the SNMP NBI is

Stopped, it indicates that the operation is successful.

----End

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

79

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 89/175

7.2.3 Disabling the SNMP NBI

By disabling the SNMP NBI, you can disable the SNMP interface service without deleting the

SNMP interface instance. In this way, the SNMP interface process will not start with the

U2000 when you start the U2000 next time.

Prerequisites

l Log in to the Solaris or Linux OS as user nmsuser.

l Log in to the Windows OS as user Administrator.

l The U2000 must be operating.

l The SNMP Service processes is in the Stopped state.

Procedure

Step 1 Log in to the System Monitor.

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

Step 3 Select the SNMP Service process, right-click, and choose Startup Mode > Disable to disablethe process.

Step 4 On the System Monitor client, if Startup Mode of the related processes of the SNMP NBI is

Disabled, it indicates that the operation is successful.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

80

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 90/175

----End

7.2.4 Restarting the SNMP NBI

When the SNMP interface process is in the stopped state, you can restart the process in the

System monitor client.

Prerequisitesl Log in to the Solaris or Linux OS as user nmsuser.

l Log in to the Windows OS as user Administrator.

l The U2000 must be operating.

l The SNMP Service processes is in the Stopped state.

Procedure

Step 1 Log in to the System Monitor.

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

81

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 91/175

Step 3 Select the SNMP Service process, right-click, and then choose Start the Process from the

shortcut menu.

Step 4 In the System Monitor client, when Status of the relevant SNMP processes, namely SNMP

Service are Running, the operation is successful.

----End

7.2.5 Deleting the SNMP NBI Instance

You can delete an instance for the SNMP interface if it is not in use.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

82

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 92/175

Prerequisites

l The Msuite client communicates with the Msuite server in the normal state.

l Ensure that all Msuite servers are started.

lEnsure that the database is running.

l It is recommended that you stop the SNMP NBI before delete the instance.

Deploy Environment

l Log in to the Solaris or Linux OS as user nmsuser.

l Log in to the Windows OS as user Administrator.

l In a distributed system, you only need to log in to the NMS maintenance tool server of the

master server to perform this operation.

l In a high availability system, you only need to log in to the NMS maintenance tool server 

of the primary site to perform this operation.

Procedure

Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 Click the Instance tab. Select the AgentSNMP instance from the instance list, right-click, and

choose Delete Instance

Step 3 Click OK . After the confirmation, the Msuite begins deleting the AgentSNMP instance.

Step 4 Click the Deployment Package tab, if the Instance Count of the SNMP NBI deployment

 package is zero, that means the deletion success.

Step 5 Required: Log in to the System Monitor. Restart all processes of the U2000.

----End

Result

NOTE

After the AgentSNMP instance is deleted, the Sysmonitor does not display the information about the

AgentSNMP process. If you need to re-enable the SNMP interface, refer to 4.9 Configuring the SNMP

NBI.

7.2.6 Deleting the SNMP NBI Component

You can delete the component for the SNMP NBI if it is not in use.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

83

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 93/175

Prerequisites

l The Msuite client communicates with the Msuite server in the normal state.

l Ensure that all Msuite servers are started.

lEnsure the NMS processes are ended.

l Ensure you have deleted the SNMP NBI instance.

Deploy Environment

l Log in to the Solaris or Linux OS as user nmsuser.

l Log in to the Windows OS as user Administrator.

l In a distributed system, you only need to log in to the NMS maintenance tool server of the

master server to perform this operation.

l In a high availability system, you only need to log in to the NMS maintenance tool server 

of the primary site to perform this operation.

Procedure

Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 On the Msuite client, click Deployment Package tab, check whether the instance count of SNMP

 NBI deployment package is zero.

l If Instance Count is not zero, you need to deleted the SNMP NBI instance first.

l If Instance Count is zero, choose Deploy > Remove Component from the Main Menu.

The dialog box is displayed.

Step 3 Select Northbound SNMP Interface component, click OK .NOTE

You cannot delete the components which are basic or have not installed. You cannot select them in the left

window.

Step 4 Click OK  in the displayed dialog. The deleting of the component is started.

Step 5 Wait until the message the component is successfully removed is displayed. Click OK .

Step 6 View the deployment package list in the Deployment Package tab, the North-Bound SNMP

Interface deployment package not exist indicate that the operation is successful.

----End

7.3 Faults and Solutions

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

7.3.1 SNMP Service Process Is Not Displayed

Symptom

After the SNMP NBI is deployed, the SNMP Service process is not displayed on the SystemMonitor client.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

84

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 94/175

Possible Causes

The SNMP NBI is not licensed.

ProcedureStep 1 Check whether the license for the SNMP NBI has been obtained. If not, the SNMP service

 process is not displayed on the System Monitor client. For details, see 4.5 Checking the

License.

Step 2 If there is a license for the SNMP NBI, redeploy the NBI or restart the U2000. Then check for 

the SNMP Service process.

Step 3 If the SNMP Service process is not running, contact your Huawei engineers.

----End

7.3.2 SNMP Service Process Fails to Be StartedSymptom

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.

CAUTION

Do not use the default ports of the SNMP protocol (port 161 and port 162) to configure the

SNMP NBI, because these they are occupied by other processes.

Refer to chapter "U2000 Port List" in the iManager U2000 Administrator Guide and the

iManager U2000 Planning Guide before you configure ports for the SNMP NBI.

Procedure

Step 1 Check whether other processes are using the port of the SNMP service.

Run the netstat -an command to view the service ports opened by the system.

l On the Solaris or Linux OS, run the netstat -an | grep port_number command to view the

status of a specified port.

For example, run the netstat -an | grep 6666 command to view the status of port 6666.

l In the Windows OS, run the netstat -an | find "port_number" command to view the status

of a specified port.

For example, run the netstat -an | find "6666" command to view the status of port 6666.

NOTE

If any router or firewall is located on the network between the U2000 and the OSS, you must check the ports used by the U2000 and the OSS and ensure that these ports can be opened for normal communication.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

85

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 95/175

Table 7-1 Service ports of an SNMP NBI

Service Name Serving Port/  Protocol Type

Direction (withthe Server as theReference Object)

Description

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 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu.

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

----End

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

SNMPv2

l Receive Request from NMS address/port

l SNMP version

l Read community

l Write community

SNMPv3   l Receive Request from NMS address/port

l SNMP version

l User name

l Authentication password and encryption password

l Security model

l Authentication protocol and encryption protocol

 

l

The firewall blocks the communication between the request transmit port on the OSS andthe request receive port on the U2000.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

86

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 96/175

Procedure

Step 1 Log in the client of U2000 System Monitor and check whether the SNMP Service process is

started.

lIf there is no SNMP Service process, see7.3.1 SNMP Service Process Is NotDisplayed.

l If the SNMP Service process cannot be started, see 7.3.2 SNMP Service Process Fails to

Be Started.

Step 2 If the SNMP Service process has been started, determine the communication parameters with

OSS engineers and redeploy the SNMP NBI.

Step 3 Ensure the communication between the request transmit port on the OSS and the request receive

 port on the U2000 is not blocked by the firewall; otherwise they cannot communicate with each

other.

----End

7.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 the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client.

Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu.

Step 3 Check whether the loaded MIB meets the requirements:

Click the Advanced tab and choose MIB Frame from the navigation tree. In the right pane,

check whether MIB is set to U2000 MIB. If no, change it to U2000 MIB and then reconfigure

the SNMP NBI.

Step 4 Check whether the heartbeat function is disabled:

Click the Advanced tab and choose Heartbeat from the navigation tree. In the right pane, check 

whether Report Heartbeat Info is set to Yes. If no, change it to Yes and then reconfigure the

SNMP NBI.

----End

7.3.5 OSS Cannot Receive Real-Time Alarms

Symptom

The OSS cannot receive real-time alarms.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

87

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 97/175

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 Msuite MSuite client

and reconfigure the SNMP NBI based on the confirmation.

Step 2 Check whether the request transmit port on the OSS and the request receive port on the

U2000 are enabled on the firewall; otherwise they cannot communicate with each other.

----End

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

Procedure

Step 1 Log in the client of U2000, browse the history alarms. View the serial number is exist. If the

serial number is exist, the alarm is converted to history alarm, then you cannot acknowledge,

unacknowledge and clear history alarms.

Step 2 Log in the client of U2000 System Monitor, view whether the log service and fault service are

running normally. If not started, please restart the processes.

Step 3 View whether the MIB file the U2000 loaded is correct.

1. Log in the client of Msuite.

2. On the NMS MSuite client, choose NBI > Configure SNMP interface instance from themain menu.

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

88

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 98/175

3. Click Advanced, select MIB Frame. View whether the MIB is set to U2000 MIB. If the

MIB is set to U2000-T MIB, please modify to U2000 MIB. Then deploy the SNMP NBI

again.

Step 4 View whether the MIB file the NMS/OSS loaded is correct.

l If the MIB file is T2000-NETMANAGEMENT-MIB.mib, acknowledged or 

unacknowledged or cleared alarms is not supported.

l If the MIB file is HW-IMAPV1NORTHBOUND-TRAP-MIB.mib or HW-

IMAPV2NORTHBOUND-TRAP-MIB.mib, please get the U2000 version

documentation iManager U2000 Northbound SNMP Interface MIB file from Huawei

technology engineer. This documentation is published in Huawei support website.

----End

7.3.7 How to configure the heartbeat notification trap tohwNmNorthboundKeepAlive

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

The following operations are for Solaris. The operations in Linux or Windows are similar. The

environment variable for Windows is %IMAP_ROOT%.

CAUTION

l U2000 is running normally.

l The environment variables are correct. For details, refer to iManager U2000 Software

 Installation Guide.

l The SNMP NBI instance is deployed and configured.

l In a high availability system, you only need to log in to the primary site to perform this

operation. But you need to modify the configuration files in primary site and secondary site.

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

l For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.

l For windows, log in to the OS of the U2000 server as the Administrator user.

Step 2 Modify the configuration file $IMAP_ROOT/nbi/snmp/engineering/server/etc/conf/

snmp_agent_svc.xml.

Add the KeepAliveVBOID configuration item in the transfer label as the following shown.

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

  <param name="EmsName">Huawei/U2000</param>

  <param name="KeepAliveVBOID">1.3.6.1.4.1.2011.2.15.1.7.2.1.0</param></transfer>

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

89

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 99/175

NOTE

You can set the KeepAliveVBOID to 1.3.6.1.4.1.2011.2.15.1.7.2.1.0 or 1.3.6.1.4.1.2011.2.15.1.7.2.1.

Step 3 Check whether the $IMAP_ROOT/etc/conf/snmp_agent_svc.xml configuration file exists. If 

it exists, modify it by referring to the preceding step.

Step 4 Import the file to the database and reload it.

# SettingTool -cmd import -file $IMAP_ROOT/etc/conf/snmp_agent_svc.xml# svc_adm -cmd reload 

Step 5 Restart the SNMP NBI by system monitor client.

Step 6 Check the modification is correct. If not, repeat the operations.

# SettingTool -cmd getparam -path /imap/snmpagent/notify/transfer/KeepAliveVBOID

Step 7 Optional: Perform the following operations for the heartbeat notification trap to report

hwNmAgent instead of hwNmNorthboundKeepAlive:

1. Delete the KeepAliveVBOID configuration item from the $IMAP_ROOT/etc/conf/

snmp_agent_svc.xml and $IMAP_ROOT/nbi/snmp/engineering/server/etc/conf/

snmp_agent_svc.xml configuration files.

2. Delete the configuration item in the database and reload it.

# SettingTool -cmd delparam -path /imap/snmpagent/notify/transfer/KeepAliveVBOID# svc_adm -cmd reload 

3. Restart the SNMP NBI by system monitor client.

----End

7.3.8 How to report additional VBs alarm trap

Question

Additional VB are reserved and not reported by default. Additional VBs range from

hwNmNorthboundsAdditionalVB1 to hwNmNorthboundsAdditionalVB8. How to report

additional VBs alarm trap?

Answer

The following operations are for Solaris. The operations in Linux or Windows are similar. The

environment variable for Windows is %IMAP_ROOT%.

CAUTION

l U2000 is running normally.

l The environment variables are correct. For details, refer to iManager U2000 Software

 Installation Guide.

l The SNMP NBI instance is deployed and configured.

l In a high availability system, you only need to log in to the primary site to perform this

operation. But you need to modify the configuration files in primary site and secondary site.

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

90

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 100/175

l For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.

l For windows, log in to the OS of the U2000 server as the Administrator user.

Step 2 Modify the configuration file $IMAP_ROOT/nbi/snmp/engineering/server/etc/conf/

snmp_agent_svc.xml.

Add AdditionalVB1 to AdditionalVB8 configuration items in Mib1 label as the following

shown.

  <param name="VB22">GroupID</param>  <param name="VB23">MaintainAlmStatus</param>

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

  <param name="AdditionalVB2">1</param>

  <param name="AdditionalVB3">2</param>

  <param name="AdditionalVB4">3</param>

  <param name="AdditionalVB5">4</param>  <param name="AdditionalVB6">5</param>

  <param name="AdditionalVB7">6</param>

  <param name="AdditionalVB8">7</param></Mib1>

Step 3 Check whether the $IMAP_ROOT/etc/conf/snmp_agent_svc.xml configuration file exists. If 

it exists, modify it by referring to the preceding step.

Step 4 Import the file to the database and reload it.

# SettingTool -cmd import -file $IMAP_ROOT/etc/conf/snmp_agent_svc.xml# svc_adm -cmd reload 

Step 5 Restart the SNMP NBI by system monitor client.

Step 6 Check the modification is correct. If not, repeat the operations.

# SettingTool -cmd getparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB1

Step 7 Optional: Perform the following operations if the additional VBs are not needed.

1. Delete the AdditionalVB1 to AdditionalVB8 configuration item from the

$IMAP_ROOT/etc/conf/snmp_agent_svc.xml and $IMAP_ROOT/nbi/snmp/

engineering/server/etc/conf/snmp_agent_svc.xml configuration files.

2. Delete the configuration item in the database and reload it.

$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB1$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB2

$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB3$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB4$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB5$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB6$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB7$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/ AdditionalVB8$ svc_adm -cmd reload 

3. Restart the SNMP NBI by system monitor client.

----End

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

91

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 101/175

7.3.9 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

The following operations are for Solaris. The operations in Linux or Windows are similar. The

environment variable for Windows is %IMAP_ROOT%.

CAUTION

l U2000 is running normally.

l The environment variables are correct. For details, refer to iManager U2000 Software

 Installation Guide.

l The SNMP NBI instance is deployed and configured.

l In a high availability system, you only need to log in to the primary site to perform this

operation. But you need to modify the configuration files in primary site and secondary site.

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

l For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.

l For windows, log in to the OS of the U2000 server as the Administrator user.

Step 2 Modify the configuration file $IMAP_ROOT/nbi/snmp/engineering/server/etc/conf/

snmp_agent_svc.xml.

Modify the T2000Support configuration item as the following shown. 1 indicates enable, 0

indicates disable, the default value is 1.

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

Step 3Check whether the $IMAP_ROOT/etc/conf/snmp_agent_svc.xml configuration file exists. If 

it exists, modify it by referring to the preceding step.

Step 4 Import the file to the database and reload it.

# SettingTool -cmd import -file $IMAP_ROOT/etc/conf/snmp_agent_svc.xml# svc_adm -cmd reload 

Step 5 Restart the SNMP NBI by system monitor client.

Step 6 Check the modification is correct. If not, repeat the operations.

$ SettingTool -cmd getparam -path /imap/snmpagent/notify/transfer/T2000Support

----End

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

92

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 102/175

7.3.10 How to report the event alarm

Question

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

Answer

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

Criteria.

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

l For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.

l For windows, log in to the OS of the U2000 server as the Administrator user.

Step 2 Modify the configuration file $IMAP_ROOT/nbi/snmp/engineering/server/etc/conf/

snmp_agent_svc.xml.

Modify the first binary digital of filtercategory to 0. 0 indicates the SNMP NBI will report event

alarm, 1 indicates not. The default value is 1. For the following example, the SNMP NBI can

report event alarm, fault alarm and clear alarm, but cannot report acknowledge alarm,

unacknowledge alarm and change alarm.

<param name="filtercategory">000111</param>

Step 3 Check whether the $IMAP_ROOT/etc/conf/snmp_agent_svc.xml configuration file exists. If 

it exists, modify it by referring to the preceding step.

Step 4 Restart the SNMP NBI by system monitor client.

----End

iManager U2000 Unified Network Management System

SNMP NBI User Guide 7 Maintaining the SNMP NBI

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

93

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 103/175

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

technicaldomain

  M a n a

 g e m e n  t  C

 a p a c  i  t  y

Interface Function

iManager U2000 Unified Network Management System

SNMP NBI User Guide A Relations Between License and SNMP Interface

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

94

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 104/175

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

for NBI-SNMP Alarm-

Transmission Network 

LNSDPENES01 0-100000

Per Equivalent NE License

for NBI-SNMP Alarm -IP

LNSDPENES02 0-100000

Per Narrowband Port License

for NBI-SNMP Alarm-

Access Network 

LNSDPENEC21 0~8000000

Per Broadband Port License

for NBI-SNMP Alarm-

Access Network 

LNSDPENEC25 0~8000000

Per PON Terminal Resource

License for NBI-SNMP

Alarm-Access Network 

LNSDNELCR84 0~8000000

Compatible License for 

SNMP Alarm NBI-Access

 Network 

LNSDNELCR75 0~8000000

iManager U2000 Unified Network Management System

SNMP NBI User Guide A Relations Between License and SNMP Interface

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

95

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 105/175

B Configuration Parameters

The U2000 can connect to the NMS/OSS after you correctly set general parameters by using the

Msuite. You can also set advanced parameters to customize the messages queried or reported

through the SNMP NBI.

B.1 General Configuration

The SNMP NBI is used to exchange management information between the OSS and the

U2000. This NBI with the standard network management frame is provided by the U2000.

B.2 Advanced Configuration

You can set the advanced parameters for the SNMP NBI throughMsuite.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

96

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 106/175

B.1 General Configuration

The SNMP NBI is used to exchange management information between the OSS and the

U2000. This NBI with the standard network management frame is provided by the U2000.

B.1.1 SNMP Agent

The SNMP agent 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. Parameters for the SNMP

agent include the trap-transmitting IP address or port, request-receiving IP address or port, and

SNMP version.

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the mainmenu. In the dialog box that is displayed, click SNMP Agent on the General tab.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

97

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 107/175

Parameters

CAUTION

The trap-transmitting IP address and request-receiving IP address are both the U2000 server IP

address. Ensure that this IP address can be used for successful communication between the

U2000 and the OSS.

Refer to chapter "U2000 Port List" in the iManager U2000 Administrator Guide and the

iManager U2000 Planning Guide before you configure ports for the SNMP NBI. Before

configuring these ports, ensure that the specified ports are idle.

Do not use the default ports of the SNMP protocol (port 161 and port 162) to deploy the SNMP

 NBI, because they are occupied by other processes.

Parameter Value Description

Set SNMP Agent

Send Trap address IP addresses except 127.0.0.1

Default: IP address of the

U2000 server 

Specifies the IP address on the

SNMP agent for sending traps 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 1025~32767

Default: 6666

Recommended value: greater 

than 1024

Specifies the port for sending

traps.

Receive Request

from NMS address

IP addresses except 127.0.0.1

Default: IP address of the

U2000 server 

Specifies the IP address for 

receiving requests from the OSS.

On the U2000 with multiple

 NICs, set an IP address for 

successful communication

 between the U2000 and the OSS.

Port 1025~32767

Default: 9812

Recommended value:

1025~32767

Specifies the port for receiving

requests from the OSS.

SNMP version v1, v2c, v3

Default: v1

The SNMP NBIU2000 support

three SNMP protocol versions:

SNMPv1, SNMPv2c, and

SNMPv3.

SNMP v3 Parameter Settings

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

98

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 108/175

Parameter Value Description

Security Model USM model Specifies the security model of  

the SNMPv3 protocol.

USM: User-based SecurityMechanism

Security Level Without authentication and

encryption, With authentication,

Without encryption, With

authentication and encryption

Default: Without authentication

and encryption

Specifies the security level of the

SNMPv3 protocol.

Authentication NONE, HMACMD5,

HMACSHA

Default: NONE

Specifies the authentication

 protocol in SNMPv3. The value

of this parameter must beconsistent with that on the OSS.

The options are as follows:

l MD5: Message Digest

(Version 5)

l SHA: Secure Hash Algorithm

Data Encryption NONE, DES, AES

Default: NONE

Specifies the data encryption

 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

 

B.1.2 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 sendsrequests to the SNMP agent, receives responses or traps from the SNMP agent, parses these

 packets, and displays the result.

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu. Select Third-Party NMS in General tab.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

99

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 109/175

Parameters

NOTE

The Receive Trap Address is not the IP address of the U2000 server.

Currently a maximum of 10 third-party NMSs are supported.

The same SNMPv3 user configured for different third-party NMSs, for example, NMS 1 and NMS 2, mustuse the same authentication and encryption passwords

When the U2000-T MIB is used, the SNMP NBI identifies OSSs by read or write community.

l If multiple OSSs use the same read or write community, only the first OSS gets the synchronized

results when any of the OSSs tries to synchronize data.

l It is recommended that each OSS uses a unique read or write community so that the OSS can get

correct synchronized results.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

100

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 110/175

CAUTION

To ensure the security of the U2000, passwords must be complex enough. For example, a

 password must contain eight or more characters of two types. The allowed characters are digits,letters, and special characters. Remember to change passwords regularly.

The password must meet the following requirements to safeguard your user account.

l Consists more than 8 characters.

l The password cannot be the user name or its reverse spelling.

l The password must consist of three of the following types of characters at least:

l Lower-case letters

l Upper-case letters

l Digits

l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ? and

space

Parameters Value Description

Receive Trap

Address

IP address Indicates the IP address of the third-party NMS or  

the IP address for the OSS to communicate with

the U2000 server.

Port Default: 6666

1025~32767

Specifies the port of the third-party NMS for 

receiving traps.

NOTE

l When the U2000 is interconnected with the OSS,

enter the port ID that is provided by the OSS.

l When the U2000 is not interconnected with the

OSS, the port ID cannot be left blank. In this case,

use the default port ID 6666.

Read/Write

Community

Default

l Read Community:

Changeme_123

l Write Community:

Changeme_123

You can also enter anycharacter string

consisting of 255

characters at most.

When the third-party NMS uses the SNMPv1 or 

SNMPv2c protocol, the authentication control

 between the SNMP agent and the OSS is

implemented through community information.

The SNMP agent responds to operations

(including querying, acknowledging,

unacknowledging, and clearing alarms) onlywhen the read and write communities are the same

as those on the OSS; otherwise, operation

requests are ignored.

V3 User Name Default: admin

Character string (20)

Specifies the user name used by the OSS to

communicate with the SNMP agent through the

SNMPv3 protocol.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

101

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 111/175

Parameters Value Description

V3

Authentication

Password

The default password

is left blank.

Indicates the password for authenticating the OSS

when the OSS visits the SNMP agent.

If the security level is set to With authentication,Without encryption or Authentication and

Privacy, set encryption policy of the password.

V3 Privacy

Password

The default password

is left blank.

Indicates the password for encrypting data when

the OSS visits the SNMP agent.

If the security level is set to Authentication and

Privacy, set encryption policy of the password.

Alarm Level Default: All

Critical, Major, Minor,

Warning

Specifies the severity of reported alarms.

Alarm

Category

Default: Fault

Fault, Acknowledge,

Unacknowledged,

Changed

Specifies the category of reported alarms.

l Fault: Indicates that the SNMP NBI will report

alarm generation and alarm clearance. That is,

the second and third places of the value of 

AlarmCategoryFilter in binary mode are set

to 0 when the thirdNMSFaultFilter

subinterface is invoked.

l Acknowledge/Unacknowledged: Indicates

the SNMP NBI will report the alarm if its

acknowledge status is changed.

l Changed: Indicates the SNMP NBI will reportchanged information of the alarm, include

severity, affected trail and root alarm.

NOTEEvent alarm reporting is disabled by default and cannot

 be configured by using the Msuite. But you can enable

this function by following methods.

l You can enable event alarm function manually. For 

details, see 7.3.10 How to report the event

alarm.

l To configure event alarm reporting, you can invoke

the thirdNMSFaultFilter subinterface and set the

first place of the value of AlarmCategoryFilter in binary mode to 0.

For details about the thirdNMSFaultFilter

subinterface, see 6.1.2 Changing Filter

Criteria.

 

B.2 Advanced Configuration

You can set the advanced parameters for the SNMP NBI throughMsuite.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

102

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 112/175

B.2.1 Heartbeat

The U2000 can periodically send heartbeat information to the OSS through the SNMP NBI.

Based on the heartbeat information, the OSS determines whether the communication is

successful. The heartbeat settings are applicable to the U2000 MIB only.

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu. Choose Heartbeat on the Advanced tab.

Parameters

NOTE

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

Parameters Value Description

Heartbeat Period Default: 60s

3s~300s

Specifies the heartbeat period of the third-

 party NMS.

Report Heartbeat

Info

Default: Yes

Yes, No

Specifies whether send the heartbeat

information to the third-party NMS.

 

B.2.2 Alarm Field

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

103

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 113/175

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu. Choose Alarm Field on the Advanced tab.

Parameters

CAUTION

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.

Name Name in theMIB

Description Value

 NE Name hwNmNorthbou

ndNEName

Indicates the name of the NE where an

alarm is generated.

Octet string

 NE Type hwNmNorthbou

ndNEType

Indicates the type of the NE where an alarm

is generated.

Octet string

Object

instance

hwNmNorthbou

ndObjectInstanc

e

Indicates location information.

For example, Slot = 20. Port = 2 20-EFG2-2

(PORT2)-MAC:1

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

104

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 114/175

Name Name in theMIB

Description Value

Event Type hwNmNorthbou

ndEventType

Indicates alarm type. For non-X.733-

compliant alarms, options are as follows:

l Communication

l Environment

l Equipment

l Service

l Processing

l Unknown

For X.733-compliant alarms, options are as

follows:

l communicationsAlarm

l environmentalAlarm

l equipmentAlarm

l qualityofServiceAlarm

l  processingErrorAlarm

l Unknown_EventType

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

105

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 115/175

Name Name in theMIB

Description Value

Alarm time hwNmNorthbou

ndEventTime

Indicates the time at which an alarm is

generated, cleared, acknowledged,

unacknowledged, or changed.

l If an alarm is generated, this parameter 

indicates the time at which the alarm is

generated.

l If an alarm is cleared, this parameter 

indicates the time at which the alarm is

cleared.

l If an alarm is acknowledged, this

 parameter indicates the time at which

the alarm is acknowledged.

l If an alarm is unacknowledged, this parameter indicates the time at which

the alarm is generated.

l If an alarm is changed, this parameter 

indicates the time at which the alarm is

generated.

The options can be in either of the

following formats:

l Local Time without timezone

information. The format is as YYYY/

MM/DD - hh:mm:ss. Example:

2009/12/23 - 19:30:30

l UTC Time. The format is as YYYY/

MM/DD - hh:mm:ssZ. Example:

2009/12/23 - 11:30:30Z

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 DST value is represented

in seconds.)

Octet string

Alarm

Cause

hwNmNorthbou

ndProbableCaus

e

Indicates possible causes for an alarm. Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

106

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 116/175

Name Name in theMIB

Description Value

Alarm

Severity

hwNmNorthbou

ndSeverity

Indicates alarm severity.

For non-X.733-compliant alarms, optionsare as follows:

l Critical

l Major 

l Minor 

l Warning

l Indefinite

l Unknown severity

For X.733-compliant alarms, option

Cleared is included.

Octet string

Alarm

Details

hwNmNorthbou

ndEventDetail

Indicates ID, device type, and details of an

alarm.

Octet string

Alarm

Location

hwNmNorthbou

ndAdditionalInf 

o

Indicates the specific location of the

equipment where an alarm is generated.

Octet string

Type Flag hwNmNorthbou

ndFaultFlag

Indicates alarm type. Options are as

follows:

l Event: Indicates the event is generated.

l Fault: Indicates the alarm is generated.

l Recovery: Indicates the trap is alarm

recovery.

l Acknowledge: Indicates the alarm is

acknowledged.

l Unacknowledged: Indicates the alarm

is unacknowledged.

l Change: Indicates alarm is changed.

l UNKNOWN_EVENT_TYPE:

Unknown event type

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

107

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 117/175

Name Name in theMIB

Description Value

Alarm

Function

Category

hwNmNorthbou

ndFaultFunction

Indicates alarm type based on functions.

Options are as follows:

l Power alarms

l Environment alarms

l Signaling alarms

l Relay alarms

l Hardware alarms

l Software alarms

l Running alarms

l Communication faults

l

Service quality alarmsl Processing error alarms

l Unknown type alarms

Octet string

Managed

Equipment

Address

hwNmNorthbou

ndDeviceIP

Indicates IP address of the equipment. IP address

Alarm

Serial

 Number 

hwNmNorthbou

ndSerialNo

Indicates the serial number of an alarm. Integer 

Alarm

Recovery

Advice

hwNmNorthbou

ndProbableRepa

ir 

Indicates advice for alarm recovery. Octet string

Resource

ID

hwNmNorthbou

ndResourceIDs

Indicates ID of the resource where an alarm

is generated.

Octet string

Event

 Name

hwNmNorthbou

ndEventName

Indicates the event name of an alarm. Octet string

Alarm ID hwNmNorthbou

ndReasonID

Indicates the alarm ID. Integer  

Fault ID hwNmNorthbou

ndFaultID

Indicates the fault ID. Integer  

Managed

Equipment

Type

hwNmNorthbou

ndDeviceType

Indicates the managed equipment type. Octet string

Trail Name hwNmNorthbou

ndTrailName

Indicates the name of the trail affected by

an alarm.

Octet string

Root

Alarm

hwNmNorthbou

ndRootAlarm

Indicates the alarm is root alarm or not.

l 0: Non-root alarm

l 1: Root alarm

Integer 

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

108

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 118/175

Name Name in theMIB

Description Value

Group ID hwNmNorthbou

ndGroupID

Indicates the ID of alarm group. Integer  

Engineerin

g Alarm

Status

hwNmNorthbou

ndMaintainStatu

s

Specifies whether this alarm is generated

 by the NE in the engineer maintenance

state. Maintenance engineers can focus 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 engineer 

maintenance state, therefore, the alarmsgenerated by this kind of NEs are engineering

alarms.

Integer 

 

B.2.3 Notification

You can set the reported mode and the relevant parameters.

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the mainmenu. Select Notification in Advanced tab.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

109

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 119/175

Parameters

WARNING

l Trap mode: A received alarm is reported immediately regardless of whether the OSS returns

a response to the previous alarm reporting.

l Inform mode: A received alarm is reported immediately after the OSS returns a response to

the previous alarm reporting or the retried times is excessed. In this mode, if the parameters

configured for the OSS are incorrect, the SNMP agent tries connecting to the OSS for many

times. This will occupy a large number of resources. As a result, the efficiency of the SNMP

agent is reduced. Therefore, exercise caution when you set this parameter to Inform.

l The SNMPv1 supports the Trap mode only.

Parameter Description Value

Reporting Mode Default: Trap Mode

Trap Mode, Inform Mode

Specifies the mode used by the SNMP agent

for sending alarms to the OSS.

Support X733

Alarm

Default: No

Yes, No

Specifies whether traps use the event 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

Interval

Default: 0

0 ms-1000 ms

Specifies the time interval for sending

messages in Trap mode.

Inform Delay Default: 5

5 s - 120 s

Indicates the interval between two attempts

to send information in inform mode. The

second attempt is performed if the OSS does

not respond.

Inform Failure

Retry

Default: 3

2 times-6 times

Indicates attempts to resend information

when the OSS does not respond in inform

mode.

 

B.2.4 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.

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu. Choose Time Format on the Advanced tab.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

110

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 120/175

Parameters

Parameters

Value Description

Alarm

TimeFormat

Default: UTC

TimeUTC Time, Local

Time (without

Time Zone),

Local Time (with

Time Zone)

Indicates the format of the alarm time.

UTC Time

The format is as YYYY/MM/DD - hh:mm:ssZ.

Example: 2009/12/23 - 11:30:30Z

Local Time (without Time Zone)

The format is as YYYY/MM/DD - hh:mm:ss.

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.

 

B.2.5 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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

111

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 121/175

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu. Select Encoding Format in Advanced tab.

Parameters

Parameters Value Description

Alarm

Character 

Default: UTF-8

UTF-8, GBK 

There are two types of alarm coding

as follows: UTF-8, GBK.

 

B.2.6 Alarm Relativity Config 

Cause analysis indicates that some alarms are triggered by the root alarm. Report all alarms or 

only the root alarm as required.

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu.On the Advanced tab, click Alarm Relativity Config.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

112

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 122/175

Parameters

Parameters

Value Description

Alarm

RelativityConfig

Default: All

alarmsAll alarms,

Root Alarm

All alarms: Queries and reports all alarms including the root

alarm and correlative alarms.Root Alarm: Queries and reports only the root alarm and

common alarms.

 

NOTE

The following two correlative alarms are involved by the location relationships between correlative alarms

and root alarms:

l  NE-level correlative alarms: Correlative alarms and root alarms are generated on the same NE.

l Trail-based correlative alarms: Correlative alarms and root alarms are generated on different upstream

and downstream NEs connected by services.

After alarm correlation rules are enabled on the U2000, the NBIs report correlative alarms based on the

alarm correlation analysis results on the U2000 and different NBIs have different rules for reporting

correlative alarms. The SNMP NBI supports only trail-based correlative alarms.

B.2.7 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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

113

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 123/175

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu.On the Advanced tab, click Engineering Alarm.

Parameters

Parameters Value Description

Engineering

Alarm

Default: All alarms

All alarms, Engineering Alarm

Specifies whether to report the

engineering alarms.

 

B.2.8 Other Settings

Other settings includes whether record log and set the cache of the real-time alarms.

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu. Select Other Settings in Advanced tab.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

114

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 124/175

Parameters

Parameters Value Description

Record Log Default: No

Yes, No

Specifies whether alarms are recorded in logs.

Real-time Alarm

Cache Size

Default:

10000

0-50000

Specifies the cache for real-time alarms. Each NMS/

OSS user is assigned with an independent cache.

When the alarm generate rate is more than the alarm

reporting rate, the SNMP NBI will buffer the alarm

data in the cache.

 

B.2.9 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.

Navigation Path

On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main

menu. Choose MIB Frame on the Advanced tab.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

115

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 125/175

Parameters

CAUTION

This setting has a direct impact on the successful communication between the U2000 and theOSS 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)

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

116

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 126/175

Parameters

Value Description

MIB U2000 MIB,

U2000-T

MIB

U2000 MIB: If the MIB file HW-

IMAPV1NORTHBOUND-TRAP-MIB.mib or HW-

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 Reported Alarm Field by 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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide B Configuration Parameters

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

117

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 127/175

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.

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.

This document uses HW-IMAPV1NORTHBOUND-TRAP-MIB as an example.

MIB SMI Version

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

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

 

C.1 MIB Description

C.2 Reported Alarm Field by U2000 MIB

U2000 MIB support 19 alarm fields, you can customize the alarm fields.

C.3 U2000 MIB Trap

C.4 U2000 MIB Trap Sample

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

118

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 128/175

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).huawei(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 6.1 U2000 MIB Subinterfaces.

For the structure and details of U2000 MIB, see iManager U2000 SNMP NBI MIB File.

NOTE

The iManager U2000 SNMP NBI MIB File is available on the Huawei technical support website. To obtain

this document, contact the local technical support engineers.

C.2 Reported Alarm Field by U2000 MIB

U2000 MIB support 19 alarm fields, you can customize the alarm fields.

When the MIB frame set to U2000 MIB, the SNMP NBI will report the following alarm fields,

you can customize the alarm fields.

Name Name in theMIB

Description Value

 NE Name hwNmNorthbou

ndNEName

Indicates the name of the NE where an

alarm is generated.

Octet string

 NE Type hwNmNorthbou

ndNEType

Indicates the type of the NE where an alarm

is generated.

Octet string

Objectinstance hwNmNorthboundObjectInstanc

e

Indicates location information.For example, Slot = 20. Port = 2 20-EFG2-2

(PORT2)-MAC:1

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

119

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 129/175

Name Name in theMIB

Description Value

Event Type hwNmNorthbou

ndEventType

Indicates alarm type. For non-X.733-

compliant alarms, options are as follows:

l Communication

l Environment

l Equipment

l Service

l Processing

l Unknown

For X.733-compliant alarms, options are as

follows:

l communicationsAlarm

l environmentalAlarm

l equipmentAlarm

l qualityofServiceAlarm

l  processingErrorAlarm

l Unknown_EventType

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

120

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 130/175

Name Name in theMIB

Description Value

Alarm time hwNmNorthbou

ndEventTime

Indicates the time at which an alarm is

generated, cleared, acknowledged,

unacknowledged, or changed.

l If an alarm is generated, this parameter 

indicates the time at which the alarm is

generated.

l If an alarm is cleared, this parameter 

indicates the time at which the alarm is

cleared.

l If an alarm is acknowledged, this

 parameter indicates the time at which

the alarm is acknowledged.

l If an alarm is unacknowledged, this parameter indicates the time at which

the alarm is generated.

l If an alarm is changed, this parameter 

indicates the time at which the alarm is

generated.

The options can be in either of the

following formats:

l Local Time without timezone

information. The format is as YYYY/

MM/DD - hh:mm:ss. Example:

2009/12/23 - 19:30:30

l UTC Time. The format is as YYYY/

MM/DD - hh:mm:ssZ. Example:

2009/12/23 - 11:30:30Z

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 DST value is represented

in seconds.)

Octet string

Alarm

Cause

hwNmNorthbou

ndProbableCaus

e

Indicates possible causes for an alarm. Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

121

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 131/175

Name Name in theMIB

Description Value

Alarm

Severity

hwNmNorthbou

ndSeverity

Indicates alarm severity.

For non-X.733-compliant alarms, optionsare as follows:

l Critical

l Major 

l Minor 

l Warning

l Indefinite

l Unknown severity

For X.733-compliant alarms, option

Cleared is included.

Octet string

Alarm

Details

hwNmNorthbou

ndEventDetail

Indicates ID, device type, and details of an

alarm.

Octet string

Alarm

Location

hwNmNorthbou

ndAdditionalInf 

o

Indicates the specific location of the

equipment where an alarm is generated.

Octet string

Type Flag hwNmNorthbou

ndFaultFlag

Indicates alarm type. Options are as

follows:

l Event: Indicates the event is generated.

l Fault: Indicates the alarm is generated.

l Recovery: Indicates the trap is alarm

recovery.

l Acknowledge: Indicates the alarm is

acknowledged.

l Unacknowledged: Indicates the alarm

is unacknowledged.

l Change: Indicates alarm is changed.

l UNKNOWN_EVENT_TYPE:

Unknown event type

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

122

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 132/175

Name Name in theMIB

Description Value

Alarm

Function

Category

hwNmNorthbou

ndFaultFunction

Indicates alarm type based on functions.

Options are as follows:

l Power alarms

l Environment alarms

l Signaling alarms

l Relay alarms

l Hardware alarms

l Software alarms

l Running alarms

l Communication faults

l

Service quality alarmsl Processing error alarms

l Unknown type alarms

Octet string

Managed

Equipment

Address

hwNmNorthbou

ndDeviceIP

Indicates IP address of the equipment. IP address

Alarm

Serial

 Number 

hwNmNorthbou

ndSerialNo

Indicates the serial number of an alarm. Integer 

Alarm

Recovery

Advice

hwNmNorthbou

ndProbableRepa

ir 

Indicates advice for alarm recovery. Octet string

Resource

ID

hwNmNorthbou

ndResourceIDs

Indicates ID of the resource where an alarm

is generated.

Octet string

Event

 Name

hwNmNorthbou

ndEventName

Indicates the event name of an alarm. Octet string

Alarm ID hwNmNorthbou

ndReasonID

Indicates the alarm ID. Integer  

Fault ID hwNmNorthbou

ndFaultID

Indicates the fault ID. Integer  

Managed

Equipment

Type

hwNmNorthbou

ndDeviceType

Indicates the managed equipment type. Octet string

Trail Name hwNmNorthbou

ndTrailName

Indicates the name of the trail affected by

an alarm.

Octet string

Root

Alarm

hwNmNorthbou

ndRootAlarm

Indicates the alarm is root alarm or not.

l 0: Non-root alarm

l 1: Root alarm

Integer 

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

123

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 133/175

Name Name in theMIB

Description Value

Group ID hwNmNorthbou

ndGroupID

Indicates the ID of alarm group. Integer  

Engineerin

g Alarm

Status

hwNmNorthbou

ndMaintainStatu

s

Specifies whether this alarm is generated

 by the NE in the engineer maintenance

state. Maintenance engineers can focus 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 engineer 

maintenance state, therefore, the alarmsgenerated by this kind of NEs are engineering

alarms.

Integer 

 

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 trapsthrough the SNMP NBI.

Definition

Name Enterprise Type Description

hwNmNorthboundE

ventNotify

hwNmNorthboundE

ventInfo

Trap/Inform Indicates that real-

time alarms are

reported.

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

124

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 134/175

VB List

In the following table, listed data types are for SNMPv1. Most of these data types are applicable

to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.

NOTE

l Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm

notification traps are automatically sent by the U2000 while active alarm report traps are responses to

the query of active alarms from the OSS.

l Additional VBs range from hwNmNorthboundsAdditionalVB1 to

hwNmNorthboundsAdditionalVB8. By default, the Additional VBs are not reported and you can not

use them. But the SNMP can report the additional VBs also. For detail, see 7.3.8 How to report

additional VBs alarm trap.

VB OID DataType

Description

hwNmNorthbound-

 NEName

1.3.6.1.4.1.2011.2.

15.1.7.1.1

Octet

string

Indicates the name of a network 

element (NE).

hwNmNorthbound-

 NEType

1.3.6.1.4.1.2011.2.

15.1.7.1.2

Octet

string

Indicates the device type of a NE.

hwNmNorthboun-

dObjectInstance

1.3.6.1.4.1.2011.2.

15.1.7.1.3

Octet

string

Indicates the alarm location. The

options are as follows:

l Rack 

l Frame

l Slot

l Subslot

l Port

hwNmNorthbound

EventType

1.3.6.1.4.1.2011.2.

15.1.7.1.4

Octet

string

Indicates the type of events.

l Communication

l Environment

l Equipment

l Service

l Processerror 

l Integrity

lOperational

l Physical

l SecurityServiceOrMechanism

l TimeDomain

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

125

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 135/175

VB OID DataType

Description

hwNmNorthbound

EventTime

1.3.6.1.4.1.2011.2.

15.1.7.1.5

Octet

string

Indicates time when the alarm 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-

ProbableCause

1.3.6.1.4.1.2011.2.

15.1.7.1.6

Octet

string

Indicates the probable cause of the

alarm.

hwNmNorthbound-

Severity

1.3.6.1.4.1.2011.2.

15.1.7.1.7

Octet

string

Indicates the alarm severity. The

options are as follows:

l Critical

l Major 

l Minor 

l Warning

l Indefinite

l Unknown_Severity

hwNmNorthboundEventDetail

1.3.6.1.4.1.2011.2.15.1.7.1.8

Octetstring

Indicates the alarm ID anddetailed information.

hwNmNorthboun-

dAdditionalInfo

1.3.6.1.4.1.2011.2.

15.1.7.1.9

Octet

string

Indicates the additional

information of an NE.

hwNmNorthbound-

FaultFlag

1.3.6.1.4.1.2011.2.

15.1.7.1.10

Octet

string

Indicates alarm type. Options are

as follows:

l Event: Indicates the event is

generated.

l Fault: Indicates the alarm is

generated.

l Recovery: Indicates the trap is

alarm recovery.

l Acknowledge: Indicates the

alarm is acknowledged.

l Unacknowledged: Indicates

the alarm is unacknowledged.

l Change: Indicates alarm is

changed.

l UNKNOWN_EVENT_TYPE

: Unknown event type

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

126

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 136/175

VB OID DataType

Description

hwNmNorthbound-

FaultFunction

1.3.6.1.4.1.2011.2.

15.1.7.1.11

Octet

string

Indicates the function type of an

alarm. The options are as follows:

l Power 

l Environment

l Signal

l Relay

l Hardware

l Software

l Run

l Communication

l

Servicel Processerror 

l UNKNOWN_FU NC_TYPE

hwNmNorthbound-

DeviceIP

1.3.6.1.4.1.2011.2.

15.1.7.1.12

IP address Indicates the IP address of a

device.

hwNmNorthbound-

SerialNo

1.3.6.1.4.1.2011.2.

15.1.7.1.13

Integer Indicates the serial number of an

alarm.

hwNmNorthbound-

ProbableRepair 

1.3.6.1.4.1.2011.2.

15.1.7.1.14

Octet

string

Indicates the alarm

troubleshooting suggestions.

hwNmNorthboun-dResourceIDs

1.3.6.1.4.1.2011.2.15.1.7.1.15

Octetstring

Indicates the ID of a resource.

hwNmNorthbound-

sAdditionalVB1

1.3.6.1.4.1.2011.2.

15.1.7.1.16

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB2

1.3.6.1.4.1.2011.2.

15.1.7.1.17

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB3

1.3.6.1.4.1.2011.2.

15.1.7.1.18

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB4

1.3.6.1.4.1.2011.2.

15.1.7.1.19

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB5

1.3.6.1.4.1.2011.2.

15.1.7.1.20

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB6

1.3.6.1.4.1.2011.2.

15.1.7.1.21

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB7

1.3.6.1.4.1.2011.2.

15.1.7.1.22

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB8

1.3.6.1.4.1.2011.2.

15.1.7.1.23

Octet

string

Reserved field.

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

127

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 137/175

VB OID DataType

Description

hwNmNorthbound

EventName

1.3.6.1.4.1.2011.2.

15.1.7.1.24

Octet

string

Indicates the name of an event.

hwNmNorthboun-

dReasonID

1.3.6.1.4.1.2011.2.

15.1.7.1.25

Integer Indicates the ID of an alarm.

hwNmNorthbound-

FaultID

1.3.6.1.4.1.2011.2.

15.1.7.1.26

Integer Indicates the fault ID of an alarm.

hwNmNorthbound-

DeviceType

1.3.6.1.4.1.2011.2.

15.1.7.1.27

Octet

string

Indicates the device type ID of an

alarm.

hwNmNorthbound-

TrailName

1.3.6.1.4.1.2011.2.

15.1.7.1.28

Octet

string

Indicates the name of the trail

affected by an alarm.

hwNmNorthboun-dRootAlarm

1.3.6.1.4.1.2011.2.15.1.7.1.29

Integer Specifies whether the alarm is rootalarm or not.

l 0: Non-root alarm

l 1: Root alarm

hwNmNorthbound-

GroupID

1.3.6.1.4.1.2011.2.

15.1.7.1.30

Integer Indicates the group ID the alarm

 belongs to.

hwNmNorthbound-

MaintainStatus

1.3.6.1.4.1.2011.2.

15.1.7.1.31

Integer Indicates the engineering alarm

status.

l 0: Non-root engineering alarm

l 1: Engineering alarm

 

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.

FunctionAfter the OSS sends alarm query requests, the U2000 sends this type of traps to inform the OSS

that the synchronization starts.

Trigger Condition

The OSS triggers the alarm synchronization. For details, see 6.1.3 Synchronizing Alarms.

The OSS performs the operation hwNmNorthboundEventSynchronizationCommandStart

in the following format:

NMS IP:port:start time:end time

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

128

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 138/175

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

ventSynchroniza-

tionStartNotify

hwNmNorthboundE

ventSynchroniza-

tionStart

Trap/Inform Indicates that the

alarm

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

ventSynchroniza-

tionQueryResultNo-

tify

hwNmNorthboundE

ventSynchroniza-

tionQueryResult

Trap/Inform Indicates the

synchronization

result or required

alarms.

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

129

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 139/175

VB List

In the following table, listed data types are for SNMPv1. Most of these data types are applicable

to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.

NOTE

l Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm

notification traps are automatically sent by the U2000 while active alarm report traps are responses to

the query of active alarms from the OSS.

l Additional VBs range from hwNmNorthboundsAdditionalVB1 to

hwNmNorthboundsAdditionalVB8. By default, the Additional VBs are not reported and you can not

use them. But the SNMP can report the additional VBs also. For detail, see 7.3.8 How to report

additional VBs alarm trap.

VB OID DataType

Description

hwNmNorthbound-

 NEName

1.3.6.1.4.1.2011.2.

15.1.7.1.1

Octet

string

Indicates the name of a network 

element (NE).

hwNmNorthbound-

 NEType

1.3.6.1.4.1.2011.2.

15.1.7.1.2

Octet

string

Indicates the device type of a NE.

hwNmNorthboun-

dObjectInstance

1.3.6.1.4.1.2011.2.

15.1.7.1.3

Octet

string

Indicates the alarm location. The

options are as follows:

l Rack 

l Frame

l Slot

l Subslot

l Port

hwNmNorthbound

EventType

1.3.6.1.4.1.2011.2.

15.1.7.1.4

Octet

string

Indicates the type of events.

l Communication

l Environment

l Equipment

l Service

l Processerror 

l Integrity

lOperational

l Physical

l SecurityServiceOrMechanism

l TimeDomain

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

130

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 140/175

VB OID DataType

Description

hwNmNorthbound

EventTime

1.3.6.1.4.1.2011.2.

15.1.7.1.5

Octet

string

Indicates time when the alarm 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-

ProbableCause

1.3.6.1.4.1.2011.2.

15.1.7.1.6

Octet

string

Indicates the probable cause of the

alarm.

hwNmNorthbound-

Severity

1.3.6.1.4.1.2011.2.

15.1.7.1.7

Octet

string

Indicates the alarm severity. The

options are as follows:

l Critical

l Major 

l Minor 

l Warning

l Indefinite

l Unknown_Severity

hwNmNorthboundEventDetail

1.3.6.1.4.1.2011.2.15.1.7.1.8

Octetstring

Indicates the alarm ID anddetailed information.

hwNmNorthboun-

dAdditionalInfo

1.3.6.1.4.1.2011.2.

15.1.7.1.9

Octet

string

Indicates the additional

information of an NE.

hwNmNorthbound-

FaultFlag

1.3.6.1.4.1.2011.2.

15.1.7.1.10

Octet

string

Indicates alarm type. Options are

as follows:

l Event: Indicates the event is

generated.

l Fault: Indicates the alarm is

generated.

l Recovery: Indicates the trap is

alarm recovery.

l Acknowledge: Indicates the

alarm is acknowledged.

l Unacknowledged: Indicates

the alarm is unacknowledged.

l Change: Indicates alarm is

changed.

l UNKNOWN_EVENT_TYPE

: Unknown event type

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

131

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 141/175

VB OID DataType

Description

hwNmNorthbound-

FaultFunction

1.3.6.1.4.1.2011.2.

15.1.7.1.11

Octet

string

Indicates the function type of an

alarm. The options are as follows:

l Power 

l Environment

l Signal

l Relay

l Hardware

l Software

l Run

l Communication

l

Servicel Processerror 

l UNKNOWN_FU NC_TYPE

hwNmNorthbound-

DeviceIP

1.3.6.1.4.1.2011.2.

15.1.7.1.12

IP address Indicates the IP address of a

device.

hwNmNorthbound-

SerialNo

1.3.6.1.4.1.2011.2.

15.1.7.1.13

Integer Indicates the serial number of an

alarm.

hwNmNorthbound-

ProbableRepair 

1.3.6.1.4.1.2011.2.

15.1.7.1.14

Octet

string

Indicates the alarm

troubleshooting suggestions.

hwNmNorthboun-dResourceIDs

1.3.6.1.4.1.2011.2.15.1.7.1.15

Octetstring

Indicates the ID of a resource.

hwNmNorthbound-

sAdditionalVB1

1.3.6.1.4.1.2011.2.

15.1.7.1.16

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB2

1.3.6.1.4.1.2011.2.

15.1.7.1.17

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB3

1.3.6.1.4.1.2011.2.

15.1.7.1.18

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB4

1.3.6.1.4.1.2011.2.

15.1.7.1.19

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB5

1.3.6.1.4.1.2011.2.

15.1.7.1.20

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB6

1.3.6.1.4.1.2011.2.

15.1.7.1.21

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB7

1.3.6.1.4.1.2011.2.

15.1.7.1.22

Octet

string

Reserved field.

hwNmNorthbound-

sAdditionalVB8

1.3.6.1.4.1.2011.2.

15.1.7.1.23

Octet

string

Reserved field.

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

132

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 142/175

VB OID DataType

Description

hwNmNorthbound

EventName

1.3.6.1.4.1.2011.2.

15.1.7.1.24

Octet

string

Indicates the name of an event.

hwNmNorthboun-

dReasonID

1.3.6.1.4.1.2011.2.

15.1.7.1.25

Integer Indicates the ID of an alarm.

hwNmNorthbound-

FaultID

1.3.6.1.4.1.2011.2.

15.1.7.1.26

Integer Indicates the fault ID of an alarm.

hwNmNorthbound-

DeviceType

1.3.6.1.4.1.2011.2.

15.1.7.1.27

Octet

string

Indicates the device type ID of an

alarm.

hwNmNorthbound-

TrailName

1.3.6.1.4.1.2011.2.

15.1.7.1.28

Octet

string

Indicates the name of the trail

affected by an alarm.

hwNmNorthboun-dRootAlarm

1.3.6.1.4.1.2011.2.15.1.7.1.29

Integer Specifies whether the alarm is rootalarm or not.

l 0: Non-root alarm

l 1: Root alarm

hwNmNorthbound-

GroupID

1.3.6.1.4.1.2011.2.

15.1.7.1.30

Integer Indicates the group ID the alarm

 belongs to.

hwNmNorthbound-

MaintainStatus

1.3.6.1.4.1.2011.2.

15.1.7.1.31

Integer Indicates the engineering alarm

status.

l 0: Non-root engineering alarm

l 1: Engineering alarm

 

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.

Function

The U2000 sends this type of traps to inform the OSS that the alarm synchronization completes.

Trigger Condition

Active alarm synchronization end traps are triggered when:

l All required alarms have been reported to the OSS in trap packets.

l The OSS stops the synchronization.

The OSS triggers the termination of synchronization. For details, see 6.1.3 Synchronizing

Alarms.

The OSS performs the operation hwNmNorthboundEventSynchronizationCommandStopon the designated U2000 in the following format:

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

133

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 143/175

NMS IP:port

NOTE

NMS IP:port refers to the IP address and port of the OSS server.

Definition

Name Enterprise Type Description

hwNmNorthboundE

ventSynchronizatio-

nEndNotify

hwNmNorthboundE

ventSynchronizatio-

nEnd

Trap/Inform Indicates that the

alarm

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.

VB OID DataType

Description

hwNmNorthbound

EventSynchroniza-

tionEndStatus

1.3.6.1.4.1.2011.2.

15.1.7.7.3.1

Integer Indicates the synchronization

result. The options are as follows:

1: normalEnd(1): Indicates that

the synchronization wascomplete.

2: stopped(2): Indicates that the

OSS stopped the synchronization.

3: error(3): Indicates that

exceptions occurred during the

synchronization.

hwNmNorthbound

EventSynchroniza-

tionEndStatusDe-

tail

1.3.6.1.4.1.2011.2.

15.1.7.7.3.2

Octet

string

Indications the details about the

synchronization result.

 

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 NMSreceives the trap, the connection between the NMS/OSS and the U2000 works. If the NMS/OSS

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

134

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 144/175

does not receive the trap in this period and the heartbeat is enabled, it indicates that the NMS/

OSS disconnects with the U2000.

NOTE

You can configure the heartbeat, for details, see B.2.1 Heartbeat.

Condition

The U2000 sends the keepAlive info (heartbeat) trap to the NMS/OSS regularly in the preset

 period.

Trap Definition

Name ENTERPRISE Type Description

hwNmNorthboundE

ventKeepAlive

hwNmNorthboundE

ventKeepAliveInfo

Trap/Inform Notification for the

Keep Alive traps.

 

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

n

hwNmAgent 1.3.6.1.4.1.2011.2.15.1 OCTET STRING By default,

this field is

reported.

hwNmNorthbound-

KeepAlive

1.3.6.1.4.1.2011.2.15.1.7.2.1 OCTET STRING You can

make

configuratio

ns for the

heartbeat

notification

trap to reportthis field.

 

CAUTION

By default, the heartbeat notification trap reports the hwNMAgent field. You can make

modifications for the trap to report the hwNmNorthboundKeepAlive field. For details, see 7.3.7

How to configure the heartbeat notification trap to hwNmNorthboundKeepAlive.

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

135

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 145/175

C.4 U2000 MIB Trap Sample

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

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,see7.3.9 How to configure T2000Support item.

Table C-1 Configuration file path

Version File Path

Versions earlier than U2000 V100R002C00 server/conf/snmpagent.cfg

U2000 V100R002C00 and later versions server/etc/conf/snmp_agent_svc.xml

 

Table C-2 Description of the T2000support configuration item

Scenario T2000supportConfiguration Item

Example Value ofhwNmNorthboun-dObjectInstance

Description

Managing

multiple-

domain NEs

<param

name="T20

00Support"

>0</param>

hwNmNorthboundOb-

 jectInstance.0 ***

(octets) Slot=4 Port=1

TTP_TYPE=1 4-

 N1SL16-1(SDH-1)-SPI:1

l This mode is fit for the multi-

domain equipment scene.

l Alarm field: The reported

alarm identification

information contains only thealarm ID.

l When optical NEs exist in the

management domain, this

mode is not recommended.

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

136

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 146/175

Scenario T2000supportConfiguration Item

Example Value ofhwNmNorthboun-dObjectInstance

Description

Managing

optical NEs

of the

transport

domain

<param

name="T20

00Support"

>1</param>

hwNmNorthboundOb-

 jectInstance.0 ***

(octets) source=NE

(9-3500) location=4-

 N1SL16-1(SDH-1)-SPI:

1

l Alarm field: The redundancy

information, such as the alarm

ID and equipment type, is

deleted from the reported

alarm information.

l In this mode, the SNMP NBI

can report the information of 

optical NE.

 

<param name="T2000Support">0</param>13: Specific trap hwNmNorthboundEventInfo::hwNmNorthboundEventNotify #1trap(v1) received from: 10.71.224.13 at 2011-12-27 16:19:58

  Time stamp: 0 days 00h:05m:29s.09th

  Agent address: 10.71.224.13 Port: 6666 Transport: IP/UDP Protocol:

SNMPv1 Trap

  Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP

  Community: Changeme_123  SNMPv1 agent address: 10.71.224.13

  Enterprise: hwNmNorthboundEventInfo

  Specific Trap MIB Lookup Results

  Name: hwNmNorthboundEventNotify, Module: HW-IMAPV1NORTHBOUND-TRAP-

MIB, Enterprise: hwNmNorthboundEventInfo

  Bindings (19)  Binding #1: hwNmNorthboundNEName.0 *** (octets) NE(9-3500)

  Binding #2: hwNmNorthboundNEType.0 *** (octets) OptiX OSN 3500

  Binding #3: hwNmNorthboundObjectInstance.0 *** (octets) Slot=4 Port=1

TTP_TYPE=1 4-N1SL16-1(SDH-1)-SPI:1

  Binding #4: hwNmNorthboundEventType.0 *** (octets) Communication  Binding #5: hwNmNorthboundEventTime.0 *** (octets) 2011/04/27 -

16:11:30

  Binding #6: hwNmNorthboundProbableCause.0 *** (octets) ID:

1,DeviceType:0,\(1)The fiber jumper is not connected at the optical

interface of the board;\(2)The laser of the board on the opposite station

is shutdown;\(3)A fiber break occurs in the transm ...  Binding #7: hwNmNorthboundSeverity.0 *** (octets) Critical

  Binding #8: hwNmNorthboundEventDetail.0 *** (octets) ID:1,DeviceType:

0,Loss of signal

  Binding #9: hwNmNorthboundAdditionalInfo.0 *** (octets)

Alarm Parameter(hex) 0x01 0x00 0x01 0x01 0x01

  Binding #10: hwNmNorthboundFaultFlag.0 *** (octets) Fault  Binding #11: hwNmNorthboundFaultFunction.0 *** (octets) Communication

  Binding #12: hwNmNorthboundDeviceIP.0 *** (ipaddr) 10.70.71.97

  Binding #13: hwNmNorthboundSerialNo.0 *** (int32) 85415

  Binding #14: hwNmNorthboundProbableRepair.0 *** (octets) ID:

1,DeviceType:0,

  Binding #15: hwNmNorthboundResourceIDs.0 *** (octets)3145893.-1.4.1.1.1.-1.-1

  Binding #16: hwNmNorthboundEventName.0 *** (octets) ID:1,DeviceType:

0,R_LOS

  Binding #17: hwNmNorthboundReasonID.0 *** (int32) 1  Binding #18: hwNmNorthboundFaultID.0 *** (int32) 1

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

137

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 147/175

  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

<param name="T2000Support">1</param>21: Specific trap hwNmNorthboundEventInfo::hwNmNorthboundEventNotify #1trap(v1) received from: 10.71.224.13 at 2011-4-27 16:25:24

  Time stamp: 0 days 00h:02m:02s.27th

  Agent address: 10.71.224.13 Port: 6666 Transport: IP/UDP Protocol:

SNMPv1 Trap

  Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP

  Community: Changeme_123  SNMPv1 agent address: 10.71.224.13

  Enterprise: hwNmNorthboundEventInfo

  Specific Trap MIB Lookup Results

  Name: hwNmNorthboundEventNotify, Module: HW-IMAPV1NORTHBOUND-TRAP-

MIB, Enterprise: hwNmNorthboundEventInfo  Bindings (19)  Binding #1: hwNmNorthboundNEName.0 *** (octets) NE(9-3500)

  Binding #2: hwNmNorthboundNEType.0 *** (octets) OptiX OSN 3500

  Binding #3: hwNmNorthboundObjectInstance.0 *** (octets) source=NE

(9-3500) location=4-N1SL16-1(SDH-1)-SPI:1

  Binding #4: hwNmNorthboundEventType.0 *** (octets) Communication  Binding #5: hwNmNorthboundEventTime.0 *** (octets) 2011/04/27 -

16:11:30

  Binding #6: hwNmNorthboundProbableCause.0 *** (octets) \(1)The fiber

jumper is not connected at the optical interface of the board;\(2)The

laser of the board on the opposite station is shutdown;\(3)A fiber break

occurs in the transmission line;\(4) T ...  Binding #7: hwNmNorthboundSeverity.0 *** (octets) Critical

  Binding #8: hwNmNorthboundEventDetail.0 *** (octets) Loss of signal

  Binding #9: hwNmNorthboundAdditionalInfo.0 *** (octets)

Alarm Parameter(hex) 0x01 0x00 0x01 0x01 0x01

  Binding #10: hwNmNorthboundFaultFlag.0 *** (octets) Fault

  Binding #11: hwNmNorthboundFaultFunction.0 *** (octets) Communication  Binding #12: hwNmNorthboundDeviceIP.0 *** (ipaddr) 10.70.71.97

  Binding #13: hwNmNorthboundSerialNo.0 *** (int32) 85417

  Binding #14: hwNmNorthboundProbableRepair.0 *** (octets) (zero-

length)

  Binding #15: hwNmNorthboundResourceIDs.0 *** (octets)3145893.-1.4.1.1.1.-1.-1

  Binding #16: hwNmNorthboundEventName.0 *** (octets) R_LOS

  Binding #17: hwNmNorthboundReasonID.0 *** (int32) 1

  Binding #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

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::hwNmNorthboundEventSynchronizationStartNotify #9 trap(v1) received from: 10.71.88.151 at 2010-11-24

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

138

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 148/175

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::hwNmNorthboundEventSynchronizationQueryResultNotify #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:hwNmNorthboundEventSynchronizationQueryResult

  Bindings (19)

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

139

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 149/175

  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

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::hwNmNorthboundEventSynchronizationEndNotify #11 trap(v1) received from: 10.71.88.151 at 2010-11-24 15:57:45

  Time stamp: 0 days 00h:07m:25s.16th

  Agent address: 10.71.88.151 Port: 6666 Transport: IP/UDP Protocol:

SNMPv1 Trap

  Manager address: 10.70.73.96 Port: 8888 Transport: IP/UDP

  Community: Changeme_123  SNMPv1 agent address: 10.71.88.151

  Enterprise: hwNmNorthboundEventSynchronizationEnd

  Specific Trap MIB Lookup Results

  Name: hwNmNorthboundEventSynchronizationEndNotify, Module: HW-

IMAPV1NORTHBOUND-TRAP-MIB, Enterprise:

hwNmNorthboundEventSynchronizationEnd  Bindings (2)

  Binding #1: hwNmNorthboundEventSynchronizationEndStatus.0 *** (int32)normalEnd(1)

  Binding #2: hwNmNorthboundEventSynchronizationEndStatusDetail.0 ***

(octets) Sync End: Successfully queried all alarms!

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::hwNmNorthboundEventSynchronizationEndNotify #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!

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

140

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 150/175

Synchronization Was Stopped by Abnormal Event403: 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.

NOTE

Two OIDs are supported. For their configurations, see 7.3.7 How to configure the heartbeat notification trap

to hwNmNorthboundKeepAlive.

hwNmAgent (default)795: Specific trap

hwNmNorthboundEventKeepAliveInfo::hwNmNorthboundEventKeepAlive #2 trap

(v1) received from: 10.71.88.151 at 2010-11-24 15:57:20

  Time stamp: 0 days 00h:07m:00s.12th  Agent address: 10.71.88.151 Port: 6666 Transport: IP/UDP Protocol:

SNMPv1 Trap

  Manager address: 10.70.73.96 Port: 8888 Transport: IP/UDP

  Community: Changeme_123

  SNMPv1 agent address: 10.71.88.151

  Enterprise: hwNmNorthboundEventKeepAliveInfo  Specific Trap MIB Lookup Results

  Name: hwNmNorthboundEventKeepAlive, Module: HW-IMAPV1NORTHBOUND-TRAP-

MIB, Enterprise: hwNmNorthboundEventKeepAliveInfo

  Bindings (1)

  Binding #1: hwNmAgent *** (octets) SNMP Agent

hwNmNorthboundKeepAlive (configurable-1.3.6.1.4.1.2011.2.15.1.7.2.1)8: Specific trap

hwNmNorthboundEventKeepAliveInfo::hwNmNorthboundEventKeepAlive #2 trap

(v1) received from: 10.67.192.220 at 2012/6/26 11:19:13

  Time stamp: 0 days 00h:00m:15s.04th

  Agent address: 10.67.192.220 Port: 6666 Transport: IP/UDP Protocol:SNMPv1 Trap

  Manager address: 10.66.102.169 Port: 6666 Transport: IP/UDP

  Community: Changeme_123

  SNMPv1 agent address: 10.67.192.220  Enterprise: hwNmNorthboundEventKeepAliveInfo

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

141

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 151/175

  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

iManager U2000 Unified Network Management System

SNMP NBI User Guide C U2000 MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

142

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 152/175

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

143

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 153/175

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).huawei(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 6.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-

tAlarmEmsName

EMS name.

The value is always Huawei/

U2000.

Octet string

EquipmentType

northboundRepor-tAlarmManagedOb-

 jectClass

Type of the equipment where analarm is generated

For example, OptiX 2500+.

Octet string

Equipment

 Name

northboundRepor-

tAlarmManagedOb-

 jectInstance

 Name of the equipment where

an alarm is generated

For example, NE350.

Octet string

 NE Name northboundRepor-

tAlarmNEName

 Name of the NE where an alarm

is generated. The NE name is the

same as the equipment name.

For example, NE350.

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

144

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 154/175

Name Name in the MIB Description Value

Rack Name northboundRepor-

tAlarmRackName

 Name of the rack where an

alarm is generated

The value is always 1.

Octet string

Subrack 

 Name

northboundRepor-

tAlarmShelfName

 Name of the subrack where an

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.

Octet string

Physical

Location of 

Equipment

northboundRepor-

tAlarmDevLocation

Physical location of the

equipment where an alarm is

generated.

This parameter is always left

 blank.

Octet string

Board Name northboundRepor-

tAlarmBoardName

 Name of the board where an

alarm is generated.

For example, PQ1.

Octet string

Port Type northboundRepor-

tAlarmPortType

Port type.

For example, SDH_TU.

Octet string

Port Number northboundRepor-

tAlarmPortNumber 

Port number.

For example, 1.

Integer 

Location of 

an Alarm

Object

northboundRepor-

tAlarmLocation

Specific location of an alarm.

For example, ne=590174/

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

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

145

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 155/175

Name Name in the MIB Description Value

Alarm Type northboundRepor-

tAlarmEventType

Alarm type.

Options are as follows:

l communicationsAlarm

l qualityofServiceAlarm

l equipmentAlarm

l  processingErrorAlarm

l environmentalAlarm

Octet string

Alarm Rising

Time

northboundRepor-

tAlarmEventTime

Time at which an alarm is

generated. The option is always

the local time.

For example,

2005-10-14,17:41:04.0.

Octet string

Alarm

Severity

northboundRepor-

tAlarmPerceivedSe-

verity

Alarm severity.

Options are as follows:

l Critical

l Major 

l Minor 

l Warning

l Cleared

l Indeterminate

Octet string

Possible

Alarm Cause

northboundRepor-

tAlarmProbable-

Cause

Possible alarm cause.

For example, RAI.

Octet string

Alarm Cause northboundRepor-

tAlarmSpecificPro-

 blems

Alarm cause.

For example, NE

communication was lost

Octet string

Affect

Service

northboundRepor-

tAlarmOperatio-

nAffected

Whether an alarm affects

services or not.

Options are as follows:

l 0: The alarm does not affectservices.

l 1: The alarm affects services.

Integer 

Alarm ID northboundRepor-

tAlarmID

Alarm ID.

For example, 93.

Integer 

Alarm Name northboundRepor-

tAlarmName

Alarm name.

For example, LP_RDI.

Octet string

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

146

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 156/175

Name Name in the MIB Description Value

Advice on

Fixing an

Alarm

northboundRepor-

tAlarmProposedRe-

 pairActions

Alarm recovery suggestion.

This parameter is always left

 blank.

Octet string

IP Address of 

the Object for 

Alarm Rising

northboundRepor-

tAlarmIPAddress

IP address of the equipment

where an alarm is generated.

This parameter is always left

 blank.

IP address

Serial

 Number of an

Alarm

northboundRepor-

tAlarmNotificatio-

nIdentifier 

Serial number of an alarm.

For example, 109.

Integer 

ID of the

Resource for 

Alarm Rising

northboundRepor-

tAlarmResourceID

ID of the resource where an

alarm is generated.

This parameter is always left

 blank.

Integer 

Additional

Information

northboundRepor-

tAlarmAdditional-

Text

Additional information.

For example, Alarm Parameter 

II(hex) 0x02

Octet string

Clear Alarm northboundRepor-

tAlarmCleared

Whether to clear an alarm.

Options are as follows:

l 0: Do not clear the alarm.

l

1: Clear the alarm.

Integer 

Serial

 Number of 

the Alarm to

Be Cleared

northboundRepor-

tAlarmCorrelated-

 Notifications

Serial number of the alarm to be

cleared.

The value of this parameter is

the same as that of the Serial

Number of an Alarm

 parameter.

Integer 

Additional

Alarm

Information

(10 Fields)

northboundRepor-

tAlarmAdditio-

nalVB

Additional information of an

alarm.

The value of this parameter is

the same as that of the AlarmRising Time parameter.

Octet string

 

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

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

147

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 157/175

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-

tAlarm

northboundNotifica-

tionType

Trap Indicates that real-

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-

larmManagedOb-

 jectClass

1.3.6.1.4.1.

2011.2.15.

1.7.3.1

Octet string Indicates the type of the equipment

where an alarm is generated, for 

example, OptiX 2500+.

northboundReportA-larmManagedObjec-

tInstance

1.3.6.1.4.1.2011.2.15.

1.7.3.2

Octet string Indicates the name of the equipmentwhere an alarm is generated, for 

example, NE350.

northboundReportA-

larmEventType

1.3.6.1.4.1.

2011.2.15.

1.7.3.3

Octet string Indicates the alarm type.

The options are as follows:

l communicationsAlarm

l qualityofServiceAlarm

l equipmentAlarm

l  processingErrorAlarm

l environmentalAlarm

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

148

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 158/175

VB OID Type Description

northboundReportA-

larmEventTime

1.3.6.1.4.1.

2011.2.15.

1.7.3.4

Octet string Indicates the time when an alarm is

generated. The value is always set to the

local time, for example,

2005-10-14,17:41:04.0.

northboundReportA-

larmProbableCause

1.3.6.1.4.1.

2011.2.15.

1.7.3.5

Octet string Indicates the probable alarm cause, for 

example, RAI.

northboundReportA-

larmSpecificPro-

 blems

1.3.6.1.4.1.

2011.2.15.

1.7.3.6

Octet string Indicates the alarm cause, for example,

 NE communication was lost.

northboundReportA-

larmPerceivedSever-

ity

1.3.6.1.4.1.

2011.2.15.

1.7.3.7

Octet string Indicates the alarm severity.

Options are as follows:

l Critical

l Major 

l Minor 

l Warning

l Cleared

l Indeterminate

northboundReportA-

larmNotificationI-

dentifier 

1.3.6.1.4.1.

2011.2.15.

1.7.3.8

Integer Indicates the serial number of an alarm,

for example, 109.

northboundReportA-

larmCorrelatedNoti-

fications

1.3.6.1.4.1.

2011.2.15.

1.7.3.9

Integer Indicates the serial number of an alarm

to be cleared.

The value of this parameter is the same

as that of the serial number of an alarm.

northboundReportA-

larmProposedRe-

 pairActions

1.3.6.1.4.1.

2011.2.15.

1.7.3.10

Octet string Indicates the alarm troubleshooting

suggestions.

This parameter is always left blank.

northboundReportA-

larmAdditionalText

1.3.6.1.4.1.

2011.2.15.

1.7.3.11

Octet string Indicates the additional information, for 

example, Alarm Parameter II(hex) 0x02.

northboundReportA-

larmEmsName

1.3.6.1.4.1.

2011.2.15.

1.7.3.12

Octet string Indicates the EMS name.

The value is always Huawei/U2000.

northboundReportA-

larmNEName

1.3.6.1.4.1.

2011.2.15.

1.7.3.13

Octet string Indicates the name of the NE where an

alarm is generated. The NE name is the

same as the equipment name, for 

example, NE350.

For example, NE350.

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

149

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 159/175

VB OID Type Description

northboundReportA-

larmDevLocation

1.3.6.1.4.1.

2011.2.15.

1.7.3.14

Octet string Indicates the physical location of the

equipment where an alarm is generated.

This parameter is always left blank.

northboundReportA-

larmRackName

1.3.6.1.4.1.

2011.2.15.

1.7.3.15

Octet string Indicates the name of the rack where an

alarm is generated.

The value is always 1.

northboundReportA-

larmShelfName

1.3.6.1.4.1.

2011.2.15.

1.7.3.16

Octet string Indicates the name of the subrack where

an alarm is generated.

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

larmBoardName

1.3.6.1.4.1.

2011.2.15.

1.7.3.17

Octet string Indicates the name of the board where an

alarm is generated, for example, PQ1.

northboundReportA-

larmPortType

1.3.6.1.4.1.

2011.2.15.

1.7.3.18

Octet string Indicates the port type, for example,

SDH_TU.

northboundReportA-larmPortNumber  1.3.6.1.4.1.2011.2.15.

1.7.3.19

Integer Indicates the port number, for example,1.

northboundReportA-

larmLocation

1.3.6.1.4.1.

2011.2.15.

1.7.3.20

Octet string Indicates the specific location of an

alarm, for example, ne=590174/rack=1/

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-

larmOperationAf-

fected

1.3.6.1.4.1.

2011.2.15.

1.7.3.21

Octet string Specifies whether an alarm affects

services.

The options are as follows:

0: The alarm does not affect services.

1: The alarm affects services.

northboundReportA-

larmID

1.3.6.1.4.1.

2011.2.15.

1.7.3.22

Integer Indicates the alarm ID, for example, 93.

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

150

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 160/175

VB OID Type Description

northboundReportA-

larmName

1.3.6.1.4.1.

2011.2.15.

1.7.3.23

Octet string Indicates the alarm name, for example,

LP_RDI.

northboundReportA-

larmIPAddress

1.3.6.1.4.1.

2011.2.15.

1.7.3.24

IP address Indicates the IP address of the equipment

where an alarm is generated.

This parameter is always left blank.

northboundReportA-

larmResourceID

1.3.6.1.4.1.

2011.2.15.

1.7.3.25

Integer Indicates the ID of the resource where an

alarm is generated.

This parameter is always left blank.

northboundReportA-

larmCleared

1.3.6.1.4.1.

2011.2.15.

1.7.3.26

Integer Specifies whether to clear an alarm.

The options are as follows:

0: Do not clear the alarm.

1: Clear the alarm.

northboundReportA-

larmAdditionalVB1-

VB10

1.3.6.1.4.1.

2011.2.15.

1.7.3.27

Octet string Indicates the additional information

about an alarm.

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

larmStart

northboundNotifica-

tionType

Trap Indicates the alarm

synchronization is

started.

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

151

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 161/175

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

larm

northboundNotifica-

tionType

Trap/Inform Indicates the alarm

synchronization isstarted.

 

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-

larmManagedOb-

 jectClass

1.3.6.1.4.1.

2011.2.15.

1.7.3.1

Octet string Indicates the type of the equipment

where an alarm is generated, for 

example, OptiX 2500+.

northboundReportA-

larmManagedObjec-

tInstance

1.3.6.1.4.1.

2011.2.15.

1.7.3.2

Octet string Indicates the name of the equipment

where an alarm is generated, for 

example, NE350.

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

152

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 162/175

VB OID Type Description

northboundReportA-

larmEventType

1.3.6.1.4.1.

2011.2.15.

1.7.3.3

Octet string Indicates the alarm type.

The options are as follows:

l communicationsAlarm

l qualityofServiceAlarm

l equipmentAlarm

l  processingErrorAlarm

l environmentalAlarm

northboundReportA-

larmEventTime

1.3.6.1.4.1.

2011.2.15.

1.7.3.4

Octet string Indicates the time when an alarm is

generated. The value is always set to the

local time, for example,

2005-10-14,17:41:04.0.

northboundReportA-larmProbableCause

1.3.6.1.4.1.2011.2.15.

1.7.3.5

Octet string Indicates the probable alarm cause, for example, RAI.

northboundReportA-

larmSpecificPro-

 blems

1.3.6.1.4.1.

2011.2.15.

1.7.3.6

Octet string Indicates the alarm cause, for example,

 NE communication was lost.

northboundReportA-

larmPerceivedSever-

ity

1.3.6.1.4.1.

2011.2.15.

1.7.3.7

Octet string Indicates the alarm severity.

Options are as follows:

l Critical

l

Major l Minor 

l Warning

l Cleared

l Indeterminate

northboundReportA-

larmNotificationI-

dentifier 

1.3.6.1.4.1.

2011.2.15.

1.7.3.8

Integer Indicates the serial number of an alarm,

for example, 109.

northboundReportA-

larmCorrelatedNoti-

fications

1.3.6.1.4.1.

2011.2.15.

1.7.3.9

Integer Indicates the serial number of an alarm

to be cleared.

The value of this parameter is the same

as that of the serial number of an alarm.

northboundReportA-

larmProposedRe-

 pairActions

1.3.6.1.4.1.

2011.2.15.

1.7.3.10

Octet string Indicates the alarm troubleshooting

suggestions.

This parameter is always left blank.

northboundReportA-

larmAdditionalText

1.3.6.1.4.1.

2011.2.15.

1.7.3.11

Octet string Indicates the additional information, for 

example, Alarm Parameter II(hex) 0x02.

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

153

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 163/175

VB OID Type Description

northboundReportA-

larmEmsName

1.3.6.1.4.1.

2011.2.15.

1.7.3.12

Octet string Indicates the EMS name.

The value is always Huawei/U2000.

northboundReportA-

larmNEName

1.3.6.1.4.1.

2011.2.15.

1.7.3.13

Octet string Indicates the name of the NE where an

alarm is generated. The NE name is the

same as the equipment name, for 

example, NE350.

For example, NE350.

northboundReportA-

larmDevLocation

1.3.6.1.4.1.

2011.2.15.

1.7.3.14

Octet string Indicates the physical location of the

equipment where an alarm is generated.

This parameter is always left blank.

northboundReportA-

larmRackName

1.3.6.1.4.1.

2011.2.15.

1.7.3.15

Octet string Indicates the name of the rack where an

alarm is generated.

The value is always 1.

northboundReportA-

larmShelfName

1.3.6.1.4.1.

2011.2.15.

1.7.3.16

Octet string Indicates the name of the subrack where

an alarm is generated.

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

larmBoardName

1.3.6.1.4.1.

2011.2.15.

1.7.3.17

Octet string Indicates the name of the board where an

alarm is generated, for example, PQ1.

northboundReportA-

larmPortType

1.3.6.1.4.1.

2011.2.15.

1.7.3.18

Octet string Indicates the port type, for example,

SDH_TU.

northboundReportA-

larmPortNumber 

1.3.6.1.4.1.

2011.2.15.

1.7.3.19

Integer Indicates the port number, for example,

1.

northboundReportA-

larmLocation

1.3.6.1.4.1.

2011.2.15.

1.7.3.20

Octet string Indicates the specific location of an

alarm, for example, ne=590174/rack=1/

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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

154

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 164/175

VB OID Type Description

northboundReportA-

larmOperationAf-

fected

1.3.6.1.4.1.

2011.2.15.

1.7.3.21

Octet string Specifies whether an alarm affects

services.

The options are as follows:0: The alarm does not affect services.

1: The alarm affects services.

northboundReportA-

larmID

1.3.6.1.4.1.

2011.2.15.

1.7.3.22

Integer Indicates the alarm ID, for example, 93.

northboundReportA-

larmName

1.3.6.1.4.1.

2011.2.15.

1.7.3.23

Octet string Indicates the alarm name, for example,

LP_RDI.

northboundReportA-larmIPAddress

1.3.6.1.4.1.2011.2.15.

1.7.3.24

IP address Indicates the IP address of the equipmentwhere an alarm is generated.

This parameter is always left blank.

northboundReportA-

larmResourceID

1.3.6.1.4.1.

2011.2.15.

1.7.3.25

Integer Indicates the ID of the resource where an

alarm is generated.

This parameter is always left blank.

northboundReportA-

larmCleared

1.3.6.1.4.1.

2011.2.15.

1.7.3.26

Integer Specifies whether to clear an alarm.

The options are as follows:

0: Do not clear the alarm.

1: Clear the alarm.

northboundReportA-

larmAdditionalVB1-

VB10

1.3.6.1.4.1.

2011.2.15.

1.7.3.27

Octet string Indicates the additional information

about an alarm.

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 6.2.2 SynchronizingAlarms.

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

155

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 165/175

The OSS sets northBoundSynchAlarmCommand to 1.

NOTE

l 0: starts the alarm synchronization.

l1: ends the alarm synchronization.

Definition

Name Enterprise Type Description

northBoundSynchA-

larmEnd

northboundNotifica-

tionType

Trap/Inform Indicates that the

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 DataType

Description

northBoundSyn-

chAlarmEndStatus

1.3.6.1.4.1.2011.2.

15.1.7.4.3

Integer Indicates the alarm

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

NOTE

U2000-T MIB cannot support heartbeat trap.

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

  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

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

156

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 166/175

  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)

iManager U2000

  Binding #3: northboundReportAlarmEventType.0 *** (octets)

processingErrorAlarm  Binding #4: northboundReportAlarmEventTime.0 *** (octets)

2010-11-29,23:31:54.0

  Binding #5: northboundReportAlarmProbableCause.0 *** (octets) When the

database usage is larger than the threshold for the critical severity, the

NMS generates this alarm. When the database usage is smaller than the

threshold for the critical severit ...  Binding #6: northboundReportAlarmSpecificProblems.0 *** (octets)

(zero-length)  Binding #7: northboundReportAlarmPerceivedSeverity.0 *** (octets)

Critical

  Binding #8: northboundReportAlarmNotificationIdentifier.0 *** (int32)

20  Binding #9: northboundReportAlarmCorrelatedNotifications.0 ***

(int32) 20

  Binding #10: northboundReportAlarmProposedRepairActions.0 ***

(octets) (zero-length)

  Binding #11: northboundReportAlarmAdditionalText.0 *** (octets) (zero-

length)  Binding #12: northboundReportAlarmEmsName.0 *** (octets) iManager

U2000

  Binding #13: northboundReportAlarmNEName.0 *** (octets) iManager

U2000  Binding #14: northboundReportAlarmDevLocation.0 *** (octets) (zero-length)

  Binding #15: northboundReportAlarmRackName.0 *** (octets) 1

  Binding #16: northboundReportAlarmShelfName.0 *** (octets) (zero-

length)

  Binding #17: northboundReportAlarmBoardName.0 *** (octets) (zero-

length)  Binding #18: northboundReportAlarmPortType.0 *** (octets) (zero-

length)

  Binding #19: northboundReportAlarmPortNumber.0 *** (int32) 0

  Binding #20: northboundReportAlarmLocation.0 *** (octets) EMS System

  Binding #21: northboundReportAlarmOperationAffected.0 *** (int32) 0

  Binding #22: northboundReportAlarmID.0 *** (int32) 103

  Binding #23: northboundReportAlarmName.0 *** (octets) The DatabaseUsage 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

  Binding #30: northboundReportAlarmAdditionalVB4.0 *** (octets)2010-11-29,23:31:54.0

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

157

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 167/175

  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)

iManager U2000

  Binding #3: northboundReportAlarmEventType.0 *** (octets)processingErrorAlarm

  Binding #4: northboundReportAlarmEventTime.0 *** (octets)

2008-09-21,15:29:56.0

  Binding #5: northboundReportAlarmProbableCause.0 *** (octets) SFTPserver fault

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

158

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 168/175

  Binding #6: northboundReportAlarmSpecificProblems.0 *** (octets) SFTPserver 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) iManager

U2000

  Binding #13: northboundReportAlarmNEName.0 *** (octets) iManager

U2000

  Binding #14: northboundReportAlarmDevLocation.0 *** (octets) (zero-

length)  Binding #15: northboundReportAlarmRackName.0 *** (octets) 1

  Binding #16: northboundReportAlarmShelfName.0 *** (octets) (zero-length)

  Binding #17: northboundReportAlarmBoardName.0 *** (octets) (zero-

length)

  Binding #18: northboundReportAlarmPortType.0 *** (octets) (zero-length)

  Binding #19: northboundReportAlarmPortNumber.0 *** (int32) 0

  Binding #20: northboundReportAlarmLocation.0 *** (octets) EMS System

  Binding #21: northboundReportAlarmOperationAffected.0 *** (int32) 0

  Binding #22: northboundReportAlarmID.0 *** (int32) 60002

  Binding #23: northboundReportAlarmName.0 *** (octets) SFTP serverfault

  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 reportedto the OSS or the OSS automatically stops the synchronization.

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

159

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 169/175

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 #4trap(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: qq

  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: qq

  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 Event58: 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: SNMPv1Trap

  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

iManager U2000 Unified Network Management System

SNMP NBI User Guide D U2000-T MIB

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

160

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 170/175

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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide E Service Ports Description

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

161

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 171/175

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.

iManager U2000 Unified Network Management System

SNMP NBI User Guide E Service Ports Description

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

162

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 172/175

F Equipment Supported

Transport Equipment

Table F-1 Transport equipment supported by the SNMP NBI

Feature

MSTP

HybridMSTP

 WDM

OTN HybridRTN(TDMFeature)

TDMRTN

Packet RTN

PTN Marine

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 F-2 Router equipment supported by the SNMP NBI

Feature NE Series CX Series HuaweiSwitch

BRAS ATN Security

Alarm   √ √ √ √ √ √

 

iManager U2000 Unified Network Management System

SNMP NBI User Guide F Equipment Supported

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

163

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 173/175

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

Access Equipment

Table F-3 Access equipment supported by the SNMP NBI

Feature MSAN/DSLAM FTTx

Narrowband

Port

Broadband

Port

FTTH FTTB/FTTC

Alarm   √ √ √ √

iManager U2000 Unified Network Management System

SNMP NBI User Guide F Equipment Supported

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

164

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 174/175

G 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 

V

iManager U2000 Unified Network Management System

SNMP NBI User Guide G Acronyms and Abbreviations

Issue 05 (2013-05-17) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

165

7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)

http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 175/175

VB Variable Bindings, namely the alarm field to be reported.

iManager U2000 Unified Network Management System

SNMP NBI User Guide G Acronyms and Abbreviations