iManager U2000 Northbound SNMP Interface User Guide-(V100R002C01_01) (2)

iManager U2000 Unified Network Management SystemV100R002C01

Northbound SNMP Interface User Guide

Issue 01

Date 2010-05-18

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 01 (2010-05-18) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

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

Product Name Version

iManager U2000 V100R002C01

Intended AudienceThe iManager U2000 Northbound SNMP Interface User Guide describes the basic concept andprinciples of U2000 northbound SNMP interface. And it is also describes how to deploying andmaintaining the SNMP NBI. This document also provides the relationship between the SNMPNBI and license, description of alarms reported by the SNMP interface, the glossary, and theacronyms and abbreviations.

This document guides the user to understand basic operations of the U2000 SNMP NBI.

This document is intended for:

l Installation and Commissioning Engineer

l Data Configuration Engineer

l Application Developer

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

Symbol Description

DANGERIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

iManager U2000Northbound SNMP Interface User Guide About This Document


iii

Symbol Description

CAUTIONIndicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or savetime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

Command ConventionsThe 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 byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

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

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.

About This DocumentiManager U2000


iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-05-18)

Change HistoryUpdates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Changes in Issue 01 (2010-05-18) Based on Product Version V100R002C01Initial release.

iManager U2000Northbound SNMP Interface User Guide About This Document


v

Contents

About This Document...................................................................................................................iii

1 Overview......................................................................................................................................1-11.1 Network Position.............................................................................................................................................1-21.2 Introduction to SNMP.....................................................................................................................................1-2

1.2.1 Overview................................................................................................................................................1-31.2.2 Structure.................................................................................................................................................1-31.2.3 MIB Description.....................................................................................................................................1-61.2.4 Technical Features..................................................................................................................................1-7

1.3 Security Mechanism........................................................................................................................................1-81.3.1 Overview................................................................................................................................................1-91.3.2 Security Mechanism of SNMP v1 and v2c............................................................................................1-91.3.3 Security Mechanism of SNMP v3..........................................................................................................1-9

1.4 Performance Indexes.....................................................................................................................................1-10

2 Function Interfaces.....................................................................................................................2-12.1 Reporting Fault Alarms in Real-Time.............................................................................................................2-22.2 Querying Current Alarms................................................................................................................................2-3

2.2.1 Changing Filter Criteria.........................................................................................................................2-32.2.2 Synchronizing Alarms............................................................................................................................2-52.2.3 Acknowledging Alarms..........................................................................................................................2-62.2.4 Unacknowledging Alarms......................................................................................................................2-82.2.5 Clearing Alarms.....................................................................................................................................2-9

2.3 Alarm handshaking and Caching..................................................................................................................2-102.4 Traps..............................................................................................................................................................2-11

2.4.1 Overview..............................................................................................................................................2-112.4.2 Active Alarm Trap...............................................................................................................................2-122.4.3 Alarm Query Start Trap........................................................................................................................2-172.4.4 Alarm Query Stop Trap........................................................................................................................2-172.4.5 KeepAlive Info.....................................................................................................................................2-18

3 Deploying and Configuring SNMP.......................................................................................3-13.1 Overview.........................................................................................................................................................3-33.2 Configuration Requirements...........................................................................................................................3-43.3 Logging in to the Client of the NMS Maintenance Suite................................................................................3-4

iManager U2000Northbound SNMP Interface User Guide Contents


vii

3.4 Checking the SNMP NBI Status.....................................................................................................................3-63.5 Deploying the SNMP NBI for the First Time.................................................................................................3-7

3.5.1 Adding SNMP NBI Component............................................................................................................3-73.5.2 Adding the SNMP NBI Instance............................................................................................................3-8

3.6 Configuring the SNMP NBI..........................................................................................................................3-113.7 SNMP Configuration Parameters..................................................................................................................3-15

4 Deleting and Disabling an SNMP Interface.........................................................................4-14.1 Logging In to the System Monitor..................................................................................................................4-24.2 Stopping the SNMP NBI.................................................................................................................................4-24.3 Disabling the SNMP NBI................................................................................................................................4-44.4 Restarting the SNMP NBI...............................................................................................................................4-54.5 Deleting the SNMP NBI Instance...................................................................................................................4-74.6 Deleting the SNMP NBI Component..............................................................................................................4-8

5 Maintaining the SNMP NBI....................................................................................................5-15.1 Maintenance Description.................................................................................................................................5-25.2 Faults and Solutions........................................................................................................................................5-2

5.2.1 SNMP Agent Fails to Start.....................................................................................................................5-25.2.2 Fails to Receive Alarms.........................................................................................................................5-35.2.3 User Unable to Perform Certain Fault Operations.................................................................................5-35.2.4 NMS User Could not Connect to the SNMP Agent...............................................................................5-35.2.5 Real Time Alarms are Not Reported......................................................................................................5-45.2.6 Attempt to Acknowledge or Un-acknowledge or Clear Alarms Fails...................................................5-4

6 Accessing U2000 from NMS.....................................................................................................6-1

A Relations Between License and SNMP Interface..............................................................A-1

B Description of the Alarms Reported by the SNMP Interface..........................................B-1

C Sample........................................................................................................................................C-1

D Acronyms and Abbreviations...............................................................................................D-1

ContentsiManager U2000


viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-05-18)

Figures

Figure 1-1 Position of the SNMP alarm NBI in the network...............................................................................1-2Figure 1-2 SNMP structure.................................................................................................................................. 1-4Figure 1-3 SNMP protocol frame.........................................................................................................................1-5Figure 1-4 Security mechanism............................................................................................................................1-9Figure 2-1 Configuring alarm reporting procedure..............................................................................................2-2Figure 2-2 Caching Alarms................................................................................................................................2-11Figure A-1 Main dimensions...............................................................................................................................A-1

iManager U2000Northbound SNMP Interface User Guide Figures


ix

Tables

Table 1-1 SNMP Components..............................................................................................................................1-3Table 1-2 Component description........................................................................................................................ 1-4Table 1-3 PDU type..............................................................................................................................................1-6Table 1-4 SNMP Version and Details..................................................................................................................1-7Table 1-5 Performance indexes of the SNMP alarm NBI..................................................................................1-10Table 2-1 MIB Node Content...............................................................................................................................2-3Table 2-2 Alarm filter level..................................................................................................................................2-4Table 2-3 Alarm category filter Condition...........................................................................................................2-4Table 2-4 MIB Node Details - Acknowledging Alarms.......................................................................................2-7Table 2-5 Alarm states - Acknowledge Alarms................................................................................................... 2-7Table 2-6 MIB Node Details - Unacknowledging Alarms...................................................................................2-8Table 2-7 Alarm states - Unacknowledge Alarms................................................................................................2-8Table 2-8 MIB Node Details - Clearing Alarms.................................................................................................. 2-9Table 2-9 Alarm states - Clear Alarms...............................................................................................................2-10Table 2-10 Fields of hwNmNorthboundEventNotify TRAP-TYPE table.........................................................2-12Table 2-11 Trap Definition of Alarm Query Start Trap.....................................................................................2-17Table 2-12 3 Trap Definition of Alarm Query Stop Trap..................................................................................2-18Table 2-13 Trap Definition of KeepAlive Info..................................................................................................2-18Table 2-14 Filed List..........................................................................................................................................2-19Table 3-1 SNMP Agent parameters....................................................................................................................3-15Table 3-2 Third-party NMS parameters.............................................................................................................3-17Table 3-3 Heartbeat parameters..........................................................................................................................3-19Table 3-4 Fields of reported alarms....................................................................................................................3-19Table 3-5 Parameters of reported notification....................................................................................................3-22Table 3-6 Parameters of the format of reported time.........................................................................................3-23Table 3-7 Other Settings.....................................................................................................................................3-24Table 3-8 Parameters of the MIB frame.............................................................................................................3-24Table A-1 Description for Dimension.................................................................................................................A-2Table A-2 Description for License Item..............................................................................................................A-2Table B-1 The Alarms Reported for U2000 MIB................................................................................................B-1Table B-2 The Alarms Reported for T2000 old MIB..........................................................................................B-4

iManager U2000Northbound SNMP Interface User Guide Tables


xi

1 Overview

About This Chapter

This chapter introduces the Simple Network Management Protocol (SNMP) alarm NorthboundInterface (NBI) of the network management system.

1.1 Network PositionThis part describes the position of the SNMP NBI in a network.

1.2 Introduction to SNMPThis part introduces the SNMP protocol and structure.

1.3 Security MechanismThe security mechanism is provided by all the supported SNMP versions, SNMPv1, SNMPv2cand SNMPv3.

1.4 Performance IndexesThis part introduces the performance indexes of SNMP alarm NBI.

iManager U2000Northbound SNMP Interface User Guide 1 Overview


1-1

1.1 Network PositionThis part describes the position of the SNMP NBI in a network.

The SNMP alarm NBI is an agent module between the following entities:

l Element Management System (EMS)l Network Management System (NMS)

The SNMP alarm NBI provides the upper NMS with the following protocol versions:

l SNMP v1l SNMP v2cl SNMP v3

Figure 1-1 shows the position of the SNMP alarm NBI in the network.

Figure 1-1 Position of the SNMP alarm NBI in the network

NE1

NE2

NEn

Device Network

EMS

NMS

Get/Set SNMP Trap

SNMP alarmnorthbound interface

NE: Network Element NMS: Network Management System

EMS: Element Management System SNMP: Simple Network Management Protocol

1.2 Introduction to SNMPThis part introduces the SNMP protocol and structure.

1 OverviewiManager U2000


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-05-18)

1.2.1 OverviewThis part describes the function and structure of SNMP.

1.2.2 StructureSNMP involves of a series of protocols and specifications. It provides the method of collectingNMS information from NEs and reporting problems and errors to the NMS.

1.2.3 MIB DescriptionThis chapter provides the basic concepts of MIB.

1.2.4 Technical FeaturesThe U2000 supports SNMPv1, SNMPv2c, and SNMPv3.

1.2.1 OverviewThis part describes the function and structure of SNMP.

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

1.2.2 StructureSNMP involves of a series of protocols and specifications. It provides the method of collectingNMS information from NEs and reporting problems and errors to the NMS.

SNMP consists of the following three components:

Table 1-1 SNMP Components

Component Describes

Structure of Management Information (SMI) How to describe the managementinformation.

Management Information Base (MIB) How to store managed objects.

SNMP management protocol How to manage the objects and realize thenetwork management functions.

SNMP Structure

SNMP is a protocol used for communication between NMS processes and the SNMP agent. TheNMS adopting SNMP consists of the following components:



1-3

l Network management station. It is also called Explorer.

l SNMP agent.

Figure 1-2 SNMP structure

Agent

MIB

U2000

Notification

Operation

SNMP

1

1

1

2

2

1 2

5 6NMS

Managed System

NE database

Table 1-2 Component description

Component Description

NMS It indicates network management softwarerunning on a workstation. The administratorsends requests to managed NEs on the NMSfor monitoring and configuring NEs.

Agent It indicates an agent process running on amanaged NE. After the managed NE receivesa request sent by the NMS, the agent respondsto the request. An agent is mainly used forcollecting NE status information, performingoperations on NEs remotely on the NMS, andsending an alarm to the NMS.

MIB It indicates a virtual database considered asan NE status set maintained on NEs. Theagent collects NE status information bysearching MIB.




Issue 01 (2010-05-18)

Component Description

SNMP It indicates a protocol used forcommunication between NMS processes andthe SNMP agent. The NMS adopting SNMPconsists of the following components:l Explorer

– Sends query messages to managed NEsthrough SNMP.

– Receives responses and trap packetsfrom managed NEs.

l SNMP agent– Runs on NEs.

– Receives and handles query messagessent from agents.

– Obtains the values of managementvariables from other modules of NEsand generates response messages.

– Sends messages to the NMS.

– After an emergency occurs, the SNMPagent can actively send trap packets tothe NMS.

SNMP Protocol Frame

SNMP is a protocol used at the application layer and acts as a part of TCP/IP protocol family.It is carried on UDP.

Figure 1-3 SNMP protocol frame

SNMP Manager

SNMP application

GetN

extRequest

GetR

equest

SetR

equest

GetR

esponseTrap

UDP

IP

Physical Network

SNMP Manager

SNMP application

GetN

extRequest

GetR

equest

SetR

equest

GetR

esponseTrap

UDP

IP

Physical Network

MIBBase

Data Link Layer Data Link Layer



1-5

SNMP supports five types of protocol data units (PDUs), as follows:

Table 1-3 PDU type

PDU Function

GetRequest-PDU It is used for accessing an agent and obtaining variable valuesfrom the table.

GetNextRequest-PDU It can obtain the next logical ID descriptor from MIB. Itsfunctions are the same as those of GetRequest-PDU exceptthis function.

GetResponse-PDU It is used for responding to GetResponse, GetNextResponse,and SetRequest PDUs. It contains the ID descriptors relevantto the preceding PDUs and provides ID descriptors ofresponse status information, such as error codes, error status,and supplementary information list.

SetRequest-PDU It describes the action acting on an element. Typically, it isused for modifying the values in the variable list.

Trap-PDU It allows the network management module to report an eventoccurred on an NE or status change of an NE.

1.2.3 MIB DescriptionThis chapter provides the basic concepts of MIB.

The MIB is a key part of the SNMP network management framework. The MIB is the objectset managed by SNMP, including all the variables to be managed. All the SNMP operationssuch as Get and Set, aim at the managed objects in the MIB.

The MIB defines the managed objects that are used by the function interfaces of the SNMPNorthbound Interface. The definitions decide what operations the NMS can do and what networkmanagement information the NMS can obtain.

The international organization assigns MIB node 2011 to Huawei Technologies Co., Ltd(HUAWEI). HUAWEI assigns MIB node 2011.2.15 to the NMS. The NMS assigns MIB node1 as hwNmAgent. Therefore, the complete MIB node information is:

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

IHW-IMAPV1NORTHBOUND-TRAP-MIB defines the root node information of the SNMPNorthbound Interface.

The SNMP Northbound Interface further assigns the MIB node information based on the rootnode. See below:

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




Issue 01 (2010-05-18)

hwNmFault defines the alarm subinterface of the SNMP Northbound Interface.

NOTE

In later sections, the following acronyms are used to describe the MIB nodes:

l NA: Not Accessible

l RC: Read and Create

l RW: Read and Write

l RO: Read Only

1.2.4 Technical FeaturesThe U2000 supports SNMPv1, SNMPv2c, and SNMPv3.

Table 1-4 SNMP Version and Details

SNMP Version Supported Details

SNMPv1 l Mutual access to management information between theSNMP management system and SNMP Agent.

l Operations– Get

– Set

– Trap

l Protocol Data Unit (PDU)– GetRequest

– GetNextRequest

– GetResponse

– SetRequest

– Trap

l SNMPv1 community-based security modelNOTE

The NMS needs to get the community information from the U2000administrator.



1-7

SNMP Version Supported Details

SNMPv2c SNMPv2 supports all the SNMPv1 functions and the followingnew features:l Access to management information between SNMP

management systems.l Operations

– GetBulk

– Inform

– Report

l Updated format of the Trap PDU, which is the same as that ofthe Get/Set PDU.

l Fractionalized error codes.NOTE

The NMS needs to get the community information from the U2000administrator.

SNMPv3 SNMPv3 supports all SNMPv2 functions and the following newfeatures:l User-based security model

l The SNMPv3 supports all Security-Levels– No Authentication and No Privacy.

– Authentication and No Privacy.

– Authentication and Privacy.

In which, Auth-Protocol supports MD5 and SHA, Private-Protocol supports DES.NOTE

The NMS cannot access the NBI unless it gets the SNMP v3 informationfrom the U2000 administrator.

1.3 Security MechanismThe security mechanism is provided by all the supported SNMP versions, SNMPv1, SNMPv2cand SNMPv3.

1.3.1 OverviewThe security mechanism of the U2000 SNMP NBI is also the security mechanism of SNMP.Any access to the SNMP alarm NBI must be authenticated.

1.3.2 Security Mechanism of SNMP v1 and v2cThis section describes the security mechanism of SNMP versions v1 and v2c.

1.3.3 Security Mechanism of SNMP v3This section describes the security mechanism of SNMPv3 version.




Issue 01 (2010-05-18)

1.3.1 OverviewThe security mechanism of the U2000 SNMP NBI is also the security mechanism of SNMP.Any access to the SNMP alarm NBI must be authenticated.

Figure 1-4 shows that SNMP v1 and v2c use the community-based security mechanism, whileSNMP v3 uses the user-based security mechanism.

Figure 1-4 Security mechanism

NMS

SNMP alarm northbound interface

v3 uses userbased security

mechanism

v1/v2c usecommunity name

based securitymechanism

1.3.2 Security Mechanism of SNMP v1 and v2cThis section describes the security mechanism of SNMP versions v1 and v2c.

The security mechanism of SNMP v1 and v2c is community-based. The packet is sent in plaintext that is easy to be intercepted or modified. Compared with SNMP v3, the security is weaker.

Before the Get, Get Next or Set operation, NMS must know the community strings configuredin the agent.

For set operations, NMS must know the write community configured in the agent.

For get operations, NMS must know the read community configured in the agent.

In the Trap and Inform packets, the community name is the first read community configuredin the agent.

1.3.3 Security Mechanism of SNMP v3This section describes the security mechanism of SNMPv3 version.

SNMPv3 adopts the user-based security mechanism. The authentication and encryptionmechanisms are used during the interaction with SNMP. To do read and write operations toagent, user must know:l SNMP v3 user name in the Agent.

l Security level.

l The authentication and/or privacy passwords information.

The trap packets can be correctly resolved and handled only when the receiving end knowsauthentication parameters configured at agent correctly.



1-9

SNMP v3 uses the elements such as EngineID and EngineBoots to avoid delay, frame changeand other attacks. Therefore, the security is greatly optimized compared with SNMP v1 and v2c.

1.4 Performance IndexesThis part introduces the performance indexes of SNMP alarm NBI.

Table 1-5 lists the performance indexes of the SNMP alarm NBI.

Table 1-5 Performance indexes of the SNMP alarm NBI

Item Index

Maximum concurrent NMS connections 10

Alarm Forwarding capacity Not less than 60 alarms per second (threeNMSs connected)

Alarm forwarding delay Less than 10 seconds (three NMSsconnected)

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




Issue 01 (2010-05-18)

2 Function Interfaces

About This Chapter

The SNMP Northbound Interface provides different function interfaces to the different NMSs.

2.1 Reporting Fault Alarms in Real-TimeThe SNMP Northbound Interface reports the real-time fault alarms to the NMS, so that the NMScan get the exact information of NE real-time alarms.

2.2 Querying Current AlarmsThrough the SNMP NBI of the U2000, the upper layer NMS can query the current alarms(unterminated alarms) of the U2000.

2.3 Alarm handshaking and CachingReal time alarms are sent through Inform to the third party NMS. When the NMS is down dueto some failure at its side, real-time alarms are cached. When the failure is rectified, all the cachedalarms are sent to the NMS in the order in which they were received from the EMS.

2.4 TrapsThis chapter introduces the trap configuration information of the SNMP Northbound Interface.

iManager U2000Northbound SNMP Interface User Guide 2 Function Interfaces


2-1

2.1 Reporting Fault Alarms in Real-TimeThe SNMP Northbound Interface reports the real-time fault alarms to the NMS, so that the NMScan get the exact information of NE real-time alarms.

Context

This function adopts SNMP Trap or Inform mode as per the configuration.

Figure 2-1 shows the process of configuring the report of fault alarms in real-time.

Figure 2-1 Configuring alarm reporting procedure

Start

Register the IP addressand port of the NMS for

receiving alarms

Set the alarm contentsand sending options

Set the alarm filterconditions

Restart the SNMP Agent

End

Procedure

Step 1 Register the receiving IP address, port and the currently-used protocol version for receiving real-time alarms.

You can configure the NMS Receive Trap Address and NMS Receive Trap Port of the third-party NMS by using NMS Maintenance Suite, refer to 3.6 Configuring the SNMP NBI.

For details on NMS receive trap address and port, refer Third-Party NMS.

Step 2 Set the alarm contents and sending options

2 Function InterfacesiManager U2000



Issue 01 (2010-05-18)

You can configure the Alarm Field Settings of the SNMP by using NMS Maintenance Suite,so that you can set the variables that an alarm carries to change the alarm information. For details,see 3.6 Configuring the SNMP NBI.

For details on alarm field, refer Alarm Field Settings.

Step 3 Set the alarm filter conditions.

You can configure the third-party NMS items of the SNMP by using NMS Maintenance Suite,so that you can set the alarm filter criteria. For details, see 3.6 Configuring the SNMP NBI.

For details on alarm filter levels, refer Third-Party NMS.

Step 4 Restart SNMP Agent.

Restart the SNMP Agent for new settings to take effect.

The alarms are sent to the upper NMS by the SNMP Agent. The severity of the alarms is checkedagainst the specified filter conditions. Accordingly, the alarms are either reported or filtered out.

----End

2.2 Querying Current AlarmsThrough the SNMP NBI of the U2000, the upper layer NMS can query the current alarms(unterminated alarms) of the U2000.

2.2.1 Changing Filter CriteriaThe alarm filter criteria can be changed dynamically when the SNMP NBI is running.

2.2.2 Synchronizing AlarmsFault alarm synchronization is a process in which the alarms are queried by the third party NMSso that the alarms are consistent between upper NMS and EMS.

2.2.3 Acknowledging AlarmsNMS can acknowledge alarms based on the alarm serial numbers.

2.2.4 Unacknowledging AlarmsNMS can unacknowledge alarms based on the alarm serial numbers.

2.2.5 Clearing AlarmsNMS can clear alarms based on the alarm serial numbers.

2.2.1 Changing Filter CriteriaThe alarm filter criteria can be changed dynamically when the SNMP NBI is running.

ContextThe following MIB Node is exposed to the user.

Table 2-1 MIB Node Content

Node Name OID

thirdNMSFaultFilter 1.3.6.1.4.1.2011.2.15.1.3.5



2-3

Procedure

Step 1 Set the value of MIB node.

The format for setting the value of MIB node is as follows:

IP Address: Port: AlarmFilterLevel

The IP address and the port number are the same as specified in the snmp_agent_svc.xml fileand the alarm filter level is the condition for filtering the alarms.

CAUTIONEnter the IP address and port number of the upper-layer OSS.

NOTE

l On the Windows OS, the configuration file snmp_agent_svc.xml in the %IMAPROOT%\server\etc\conf.

l On the Solaris or SUSE Linux OS, the configuration file snmp_agent_svc.xml in the $IMAPROOT/server/etc/conf.

The alarm filter level is represented in four bits in binary notation. The alarm severity levels thatcan be filtered are critical, major, minor, and warning. Table 2-2 lists the meanings of each bitof the alarm filter level. If a bit is set to 0, it indicates that the alarms of the corresponding severitylevel are reported. If a bit is set to 1, it indicates that the alarms of the corresponding severitylevel are filtered out.

Table 2-2 Alarm filter level

Most SignificantBit (MSB)

Least SignificantBit (LSB)

Critical Alarm Major Alarm Minor Alarm Warning Alarm

The alarm category filter condition is represented in three bits in binary notation. The alarmseverity levels that can be filtered are event, fault, and recovery. Table 2-3 lists the meaningsof each bit of the alarm category filter condition. If a bit is set to 0, it indicates that the alarmsof the corresponding alarm category are reported. If a bit is set to 1, it indicates that the alarmsof the corresponding alarm category are filtered out.

Table 2-3 Alarm category filter Condition

Most Significant Bit (MSB) Least Significant Bit (LSB)

Event Fault Recovery

----End




Issue 01 (2010-05-18)

ExampleThe IP address of the upper-layer OSS is set to 10.70.73.159 and the serial number of the portfor receiving alarms is set to 161. To report only the critical and major alarms and filter out theminor and warning alarms, you need to set the MIB node to 10.70.73.159:161:0011.

2.2.2 Synchronizing AlarmsFault alarm synchronization is a process in which the alarms are queried by the third party NMSso that the alarms are consistent between upper NMS and EMS.

ContextNMS can specify the time interval for alarm synchronization.

This function adopts SNMP Trap or Inform mode depending upon the configuration done in thesnmp_agent_svc.xml file.

NOTE



The following MIB nodes are exposed.

Node Name OID

hwNmNorthboundEventSynchronization-CommandStart

1.3.6.1.4.1.2011.2.15.1.7.7.4

hwNmNorthboundEventSynchronization-CommandStop

1.3.6.1.4.1.2011.2.15.1.7.7.5

Procedure

Step 1 Set the MIB node exposed.

Set the hwNmNorthboundEventSynchronizationCommandStart node in the format as specified.

IP address of the NMS: Port number of the NMS: Start Time: End Time

The IP address and Port are same as configured in the snmp_agent_svc.xml file. Start Time andEnd Time parameters are in UTC time format and are optional.

The syntax for start time and end time is: YYYYMMDDhhmmss.

The variable description is as follows:

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.



2-5

l mm: Two digit minutes. The range of values is 00-59.

l ss: two digit seconds. The range of values is 00-59.

For Example,

Valid query conditions:

10.18.38.63:20061006090520:20061006090520 - Start time and end time are specified.

10.18.38.63:161:20061006090520 - No end time is specified.

The SNMP Northbound Interface sends a start synchronization notification to the NMS with thefollowing OID:

1.3.6.1.4.1.2011.2.15.1.7.7.4

Alarm synchronization starts.

Step 2 Receive active alarms present in the EMS Database.

The NMS receives the active alarms present in the EMS Database between time period specified(if any).

The OID of the synchronous data is:

1.3.6.1.4.1.2011.2.15

The OID carries the same VBs. The field formats are the same as those for a real-time alarm.

The alarms can be synchronized for the NMSs configured in the snmp_agent_svc.xml file.

Step 3 End alarm synchronization.

The alarm synchronization ends after all active alarms are sent to the NMS or the NMS usersends the stop alarm synchronization request to the SNMP Northbound Interface..

Set hwNmNorthboundEventSynchronizationCommandStop node in the format as specified:

IP Address: Port Number

The IP Address and the port number is the address of the NMS for which alarm synchronizationis to be stopped

The SNMP alarm Northbound Interface sends a notification to the NMS which contains theresult of synchronization.

1. Alarm synchronization has been successfully ended.2. Alarm synchronization is stopped by the NMS command.3. Error has occurred during the alarm synchronization.

NOTE

l If End Time is not present, the current system time of the EMS is treated as the End Time.

l If both are not present all the active alarms are queried.

l If End Time is present Start Time is mandatory.

----End

2.2.3 Acknowledging AlarmsNMS can acknowledge alarms based on the alarm serial numbers.




Issue 01 (2010-05-18)

Context

Table 2-4 shows the MIB node.

Table 2-4 MIB Node Details - Acknowledging Alarms

Node Name OID

hwNmAcknowledgeAlarms 1.3.6.1.4.1.2011.2.15.1.3.7

Procedurel Set the MIB node with alarm serial number

NMS sets the above mentioned node with the serial number of the alarm to beacknowledged.

To acknowledge multiple alarms, NMS sets the node with all the serial numbers, separatedby a comma.

Ack User field in U2000 client is set as SNMP Agent User when an alarm is acknowledgedby the SNMP Agent.

Invalid or non existent alarm serial numbers list is returned as failed to acknowledge.

For Example,

Consider the following string:

",1,,,2, 3 ,ab c,,4,3,d,4294967296 "

Valid Alarm Serial Number. = 1,2,4,3

Invalid Alarm Serial. Number. = ab c,d,4294967296

Table 2-5 shows the change in state when alarms are acknowledged.

Table 2-5 Alarm states - Acknowledge Alarms

Sl.No Alarm State State Change SETResponse

Failed List

1 Unacknowledge and Unclear

Acknowledgeand Unclear

Success Empty

2 Unacknowledge and Clear

Acknowledgeand Clear

Success Empty

3 Acknowledgeand Unclear

Acknowledgeand Unclear

Success Empty

4 Acknowledgeand Clear

NA Success Alarm SerialNumbers



2-7

NOTE

The GET operation is not supported on this MIB node.

----End

2.2.4 Unacknowledging AlarmsNMS can unacknowledge alarms based on the alarm serial numbers.

Context

Table 2-6 describes the MIB node.

Table 2-6 MIB Node Details - Unacknowledging Alarms

Node Name OID

hwNmUnAcknowledgeAlarms 1.3.6.1.4.1.2011.2.15.1.3.8

Procedure

Step 1 Set the MIB node with alarm serial number.

NMS sets the above mentioned node with the serial number of the alarm to be unacknowledged.

To unacknowledge multiple alarms, NMS sets the node with all the serial numbers, separatedby a comma.

Invalid or non-existent alarm serial numbers list is returned as failed to unacknowledge.

For Example,


",1,,,2, 3 ,ab c,,4,3,d,4294967296 "



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

Table 2-7 Alarm states - Unacknowledge Alarms

Sl.No Alarm State State Change SET Response Failed List

1 Unacknowledgeand Unclear

Unacknowledgeand Unclear

Success Empty

2 Unacknowledgeand Clear

Unacknowledgeand Clear

Success Empty


Unacknowledgeand Unclear

Success Empty




Issue 01 (2010-05-18)




NOTE

GET operation is not supported on this MIB node.

----End

2.2.5 Clearing AlarmsNMS can clear alarms based on the alarm serial numbers.

Context

Table 2-8 shows the MIB node.

Table 2-8 MIB Node Details - Clearing Alarms

Node Name OID

hwNmClearAlarms 1.3.6.1.4.1.2011.2.15.1.3.6

Procedure

Step 1 Set the MIB node with alarm serial number.

NMS sets the above mentioned node with the serial number of the alarm to be cleared.

To clear multiple alarms, NMS sets the node with all the serial numbers, separated by a comma.

Cleared User field in U2000 client is set as SNMP Agent User when an alarm is cleared bythe SNMP Agent.

Invalid or non-existent alarm serial numbers list is returned as failed to clear.

For Example,


",1,,,2, 3 ,ab c,,4,3,d,4294967296 "



Table 2-9 shows the change in state when alarms are cleared.



2-9

Table 2-9 Alarm states - Clear Alarms


1 Unacknowledgeand Unclear


Success Empty

2 Unacknowledgeand Clear


Success Empty


Acknowledgeand Clear

Success Empty



NOTE

GET operation is not supported on this MIB node.

----End

2.3 Alarm handshaking and CachingReal time alarms are sent through Inform to the third party NMS. When the NMS is down dueto some failure at its side, real-time alarms are cached. When the failure is rectified, all the cachedalarms are sent to the NMS in the order in which they were received from the EMS.

ContextFigure 2-2 shows the procedure of caching alarms.




Issue 01 (2010-05-18)

Figure 2-2 Caching Alarms

NMS Up

start

Set Cache Features,Timeout, Retries and Cache

Size

New Real Time Alarm

NMS Down Cache Alarms

End

Report Alarms

Yes

No

Yes

2.4 TrapsThis chapter introduces the trap configuration information of the SNMP Northbound Interface.

2.4.1 OverviewThis section describes the traps which the SNMP Northbound Interface provides for the NMS.

2.4.2 Active Alarm TrapThis section describes how the U2000 system sends real-time alarms to the NMS.

2.4.3 Alarm Query Start TrapThis section describes the alarm query start trap including the prerequisites and trap definition.

2.4.4 Alarm Query Stop TrapThis section describes about the alarm query stop trap including prerequisites and trap definition.

2.4.5 KeepAlive InfoThis section describes about the Keep Alive info, prerequisites, trap definition and field list.

2.4.1 OverviewThis section describes the traps which the SNMP Northbound Interface provides for the NMS.

The trap names are given below:



2-11

l Active alarm trap: hwNmNorthboundEventSynchronization

l Active alarm query start trap:hwNmNorthboundEventSynchronizationCommandStart

l Active alarm query stop trap: hwNmNorthboundEventSynchronizationCommandStop

l KeepAlive Info trap: hwNmNorthboundEventKeepAliveInfo

2.4.2 Active Alarm TrapThis section describes how the U2000 system sends real-time alarms to the NMS.

DescriptionThis section describes the purpose of the alarm trap.

PrerequisitesIf an alarm occurs to an NE or the U2000, U2000 sends the alarm trap to the NMS.

Field ListIn 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 datatypes are remarked in brackets.

Table 2-10 Fields of hwNmNorthboundEventNotify TRAP-TYPE table

Name OID Type Description Example

hwNmNorthboundNEName

1.3.6.1.4.1.2011.2.15.1.7.1.1

Octet string The name ofnetworkelement.

otm460

hwNmNorthboundNEType

1.3.6.1.4.1.2011.2.15.1.7.1.2

Octet string The device typeof element.

WDM_OTM

hwNmNorthboundObjectIn-stance

1.3.6.1.4.1.2011.2.15.1.7.1.3

Octet string The instance ofelement are asfollows numberofl Rack

l Frame

l Slot

l Subslot

l Port




Issue 01 (2010-05-18)


hwNmNorthboundEventType

1.3.6.1.4.1.2011.2.15.1.7.1.4

Octet string The type ofEvent.l Communicati

onl Environment

l Equipment

l Service

l Processerror

l Integrity

l Operational

l Physical

l SecurityServiceOrMechanism

l TimeDomain

Equipment

hwNmNorthboundEventTime

1.3.6.1.4.1.2011.2.15.1.7.1.5

Octet string Time at whichthe alarm wasgenerated. Theformat isl Local Time

(YYYY/MM/DD-hh:mm:ss)

l UTC Time(YYYY/MM/DD-hh:mm:ssZ)

l Local withTime Zone(YYYY/MM/DD:hh:mm:ss:hh:mm:TZ)

2009/09/05-03:44:20

hwNmNorthboundProbableCause

1.3.6.1.4.1.2011.2.15.1.7.1.6

Octet string The probablecause of thealarm.



2-13


hwNmNorthboundSeverity

1.3.6.1.4.1.2011.2.15.1.7.1.7

Octet string The level ofAlarm. Thelevels are asfollows:l Critical

l Major

l Minor

l Warning

l Indeterminate

Critical

hwNmNorthboundEventDetail

1.3.6.1.4.1.2011.2.15.1.7.1.8

Octet string The Alarm IDand detailinformation.

hwNmNorthboundAdditionalInfo

1.3.6.1.4.1.2011.2.15.1.7.1.9

Octet string The additionalinformation ofdevice, such asCountry, City.

(zero-length)

hwNmNorthboundFaultFlag

1.3.6.1.4.1.2011.2.15.1.7.1.10

Octet string The flag whichspecifieswhether thealarm is anevent, fault orrecovery.l Event

l Fault

l Recovery

Fault




Issue 01 (2010-05-18)


hwNmNorthboundFaultFunction

1.3.6.1.4.1.2011.2.15.1.7.1.11

Octet string The functiontype of thealarm. It can beany one of thefollowingvalues:l Power

l Environment

l Signal

l Relay

l Hardware

l Software

l Run

l Communication

l Service

l Processerror

l UNKNOWN_FUNC_TYPE

hwNmNorthboundDeviceIP

1.3.6.1.4.1.2011.2.15.1.7.1.12

IpAddress IP address of thedevice.

10.167.12.84

hwNmNorthboundSerialNo

1.3.6.1.4.1.2011.2.15.1.7.1.13

INTEGER The serialnumber ofalarm.

54

hwNmNorthboundProbableRe-pair

1.3.6.1.4.1.2011.2.15.1.7.1.14

Octet string Alarm repairrecommendations.

ID:187,DeviceType:1891

hwNmNorthboundResourceIDs

1.3.6.1.4.1.2011.2.15.1.7.1.15

Octet string The ID ofresource.

4063233.3145728.1.196609.61.1.1.-1

hwNmNorthboundsAdditionalVB1

1.3.6.1.4.1.2011.2.15.1.7.1.16

Octet string The additionalinformation ofthe alarm.


1.3.6.1.4.1.2011.2.15.1.7.1.17



1.3.6.1.4.1.2011.2.15.1.7.1.18




2-15



1.3.6.1.4.1.2011.2.15.1.7.1.19



1.3.6.1.4.1.2011.2.15.1.7.1.20



1.3.6.1.4.1.2011.2.15.1.7.1.21



1.3.6.1.4.1.2011.2.15.1.7.1.22



1.3.6.1.4.1.2011.2.15.1.7.1.23


hwNmNorthboundEventName

1.3.6.1.4.1.2011.2.15.1.7.1.24

Octet string The name ofevent.

ID:187,DeviceType:1891,CHAN_LOS

NOTEThe alarm trap notification is the same for real-time alarm reporting and as a response to querying active alarms.

How to configure AdditionalVB

Additional VBs are not defined in agent. New type of additional VB can be added withoutchanging the agent. Only snmp_agent_svc.xml needs to be changed. They do not have its ownOID and use fixed OID assigned to additional information. They will use OID according to theirorder in the additional vbs.

NOTE



For example, the first VB in the additional VBs will use HwNmNorthboundAdditionalVB1(1.3.6.1.4.1.2011.2.15.1.7.1.16.0)

The second VB in the additional VBs will use HwNmNorthboundAdditionalVB2(1.3.6.1.4.1.2011.2.15.1.7.1.17.0)

The eighth VB in the additional VBs will use HwNmNorthboundAdditionalVB8(1.3.6.1.4.1.2011.2.15.1.7.1.23.0).




Issue 01 (2010-05-18)

The maximum number of count of additional VBs is eight. Only the first 8 additional VBs willbe sent, and the other VBs are ignored.

The field for additional VBs can be configured by the user, the format is as follows:

AdditionalVBX=DEFINE_FIELD_NAME, Here X must begin from 1 and increase by 1 eachtime.

To configure the values for each additional VB which maps to the array index of the Parasparameter, is sent in FM alarm structure. The datatype of the additional VBs is Octect string. Ifthe value configured in the snmp_agent_svc.xml file does not match with the array index ofthe Paras parameter, null will be reported to the NMS.

2.4.3 Alarm Query Start TrapThis section describes the alarm query start trap including the prerequisites and trap definition.

DescriptionThe U2000 notifies the NMS of the start of the query. After the NMS receives the active alarmquery start trap, the query starts.

The hwNmNorthboundEventSynchronizationCommandStart node is to be set to start thealarm synchronization. This node is set as NMS IP: port: start time: end time. The syntax forStart and End time is YYYYMMDDhhmmss.

PrerequisitesThe NMS triggers the query.

Trap DefinitionThe following table describes the trap definition:

Table 2-11 Trap Definition of Alarm Query Start Trap

Name OID

hwNmNorthboundEventSynchronizationCom-mandStart

1.3.6.1.4.1.2011.2.15.1.7.7.4

Field ListNone

2.4.4 Alarm Query Stop TrapThis section describes about the alarm query stop trap including prerequisites and trap definition.

DescriptionThe U2000 notifies the NMS of the stop of the query. After the NMS receives the active alarmquery stop trap, it indicates that the query ends.



2-17

"hwNmNorthboundEventSynchronizationCommandStop" node sets to stop the alarmsynchronization. This node sets as NMS's IP: port and the agent stops alarm synchronization forthe specified IP and port.

Prerequisites

Query should be running.

Trap Definition

The following table describes the trap definition:

Table 2-12 3 Trap Definition of Alarm Query Stop Trap

Name OID

hwNmNorthboundEventSynchronizationCom-mandStop

1.3.6.1.4.1.2011.2.15.1.7.7.5

Field List

None

2.4.5 KeepAlive InfoThis section describes about the Keep Alive info, prerequisites, trap definition and field list.

Description

U2000 sends the Keep Alive info to the NMS regularly each period. If the NMS receives thetrap, the connection between the NMS and the U2000 works. If the NMS does not receive thetrap in this period and the heartbeat is enabled, it indicates that the NMS disconnects with theU2000.The range is from 3 to 300 seconds and the default value is 60.

Prerequisites

The U2000 sends the keepAlive info trap to the NMS regularly in the preset period.

Trap Definition

The following table describes the trap definition:

Table 2-13 Trap Definition of KeepAlive Info

Name OID

hwNmNorthboundEventKeepAliveInfo 1.3.6.1.4.1.2011.2.15.1.7.2




Issue 01 (2010-05-18)

Field ListIn 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 datatypes are remarked in brackets.

Table 2-14 Filed List

Name OID Type Description

hwNmNorthboundEvent-KeepAliveInfo

1.3.6.1.4.1.2011.2.15.1.7.2

Trap Notification for the KeepAlive traps.



2-19

3 Deploying and Configuring SNMP

About This Chapter

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

3.1 OverviewThis topic describes the background information and the terms involved in the process ofdeploying and configuring the northbound interface.

3.2 Configuration RequirementsU2000 SNMP NBI and the U2000 server run on the same PC or Sun workstation, any additionalconfiguration is not required. But to enable the SNMP NBI, you must purchase the license forthe corresponding functions.

3.3 Logging in to the Client of the NMS Maintenance SuiteAfter you log in to the client of the NMS Maintenance Suite, you can maintain the U2000 byusing the NMS Maintenance Suite, including deploying the U2000 and configuring the instanceof the northbound interface.

3.4 Checking the SNMP NBI StatusAfter check the license and ensure it is support SNMP functions, you need to check the currentstatus of SNMP NBI, and deploy the SNMP NBI according the status.

3.5 Deploying the SNMP NBI for the First TimeBy default, the SNMP NBI is not installed during the installation of U2000 server. To enablethe SNMP NBI, you need to add the SNMP NBI the SNMP NBI component first, then add theSNMP NBI instance.

3.6 Configuring the SNMP NBIIn order to enable the SNMP NBI, even though you have installed SNMP NBI component, youneed configure the SNMP parameters accord to NMS planning. Also, you can modify theparameters by configuring SNMP NBI again. As usual, the general parameters is mandatory.The advanced items is optional while the default value is recommended. Every advanced itemis independence and you need not set the parameters in sequence.

3.7 SNMP Configuration Parameters

iManager U2000Northbound SNMP Interface User Guide 3 Deploying and Configuring SNMP


3-1

You can ensure that the connection between the U2000 and the upper layer NMS is normal bycorrectly configuring basic parameters in the deployment tool. You can also configure advancedparameters for customizing the messages queried or reported through the SNMP interface.

3 Deploying and Configuring SNMPiManager U2000



Issue 01 (2010-05-18)

3.1 OverviewThis topic describes the background information and the terms involved in the process ofdeploying and configuring the northbound interface.

Attention Iteml 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.

CAUTIONl 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-relatedprocess.

l After initializing the database of the U2000, you need to configure the northbound interfaceinstance again.

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

TermsThe following explains certain confusable terms:

l Component: It is the software function unit that can be selected for installation. Acomponent can consist of multiple deployment packages.

l Deployment package: It is the software unit that is deployed on a PC. In a distributed system,the deployment packages of a component may be deployed on different PCs.Deployment packages are classified into the following types:– System single-instance: Such deployment packages can be installed on only one server

and the server can be deployed with only one instance.– Single-server single-instance: Such deployment packages can be installed on multiple

servers and each server can be deployed with only one instance.– Single-server multi-instance: Such deployment packages can be installed on multiple

servers and each server can be deployed with multiple instances.NOTE

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

NMS Maintenance SuiteThrough the GUI of the NMS maintenance tool, you can conveniently deploy the northboundinterface.



3-3

The NMS Maintenance Suite is a graphical system maintenance tool that is developed for theiManager U2000. The NMS Maintenance Suite is used to deploy the instances and distributedsystem of the U2000.

Refer to the NMS Maintenance Suite part of the iManager U2000 Administrator Guide for thedetails about the NMS Maintenance Suite.

3.2 Configuration RequirementsU2000 SNMP NBI and the U2000 server run on the same PC or Sun workstation, any additionalconfiguration is not required. But to enable the SNMP NBI, you must purchase the license forthe corresponding functions.

NOTE

For different operation system, the configuration requirements of U2000 is different, refer to thecorresponding Software Installation Guide for more information.

Hardware ConfigurationIn practice, the U2000 SNMP interface and the U2000 server run on the same PC or SUNworkstation. The hardware should be well configured enough to ensure the proper installationand 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 ConfigurationRequirements in the iManager U2000 Software Installation Guide.

Software ConfigurationThe function of U2000 SNMP interface is implemented based on the ORB technology of theSNMP. Since the the SNMP is integrated into the U2000 installation software, no additionalsoftware configuration is required for the installation of the U2000SNMP interface.

For details of software requirements U2000 Server, refer to section ConfigurationRequirements in the iManager U2000 Software Installation Guide.

LicenseThe U2000 controls the functions and available resources of the CORBA NBI through a license.If you want to enable the CORBA interface, you need to purchase the U2000 license. Ensurethe license support CORBA interface function before deploying the CORBA NBI.

For details, see A Relations Between License and SNMP Interface. If the license does notsupport 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 Applyingfor and Updating the License in the iManager U2000 Administrator Guide.

3.3 Logging in to the Client of the NMS Maintenance SuiteAfter you log in to the client of the NMS Maintenance Suite, you can maintain the U2000 byusing the NMS Maintenance Suite, including deploying the U2000 and configuring the instanceof the northbound interface.




Issue 01 (2010-05-18)

Prerequisitel The server of the NMS Maintenance Suite must be started.

l The client and the server of the NMS Maintenance Suite must communicate with each othernormally.

Context

In normal cases, the NMS Maintenance Suite server starts along with the OS. You can do asfollows to check whether the NMS Maintenance Suite server is started:

l In the Windows OS, check whether the msdaemon.exe and msserver.exe processes arestarted in the Task Manager window. If you can find the two processes in the process list,it indicates that the NMS Maintenance Suite server is started. Otherwise, open the DOSwindow and run the following command to start the NMS Maintenance Suite server:> net start nodemgr

l In the Solaris or SUSE Linux OS, run the following command as the root user to checkwhether the NMS Maintenance Suite server is started:# ps -ef | grep java

If ./engineering/jre/jre_unix/bin/java is displayed, it indicates that the NMS MaintenanceSuite server is started. Otherwise, run the following commands to start the NMSMaintenance Suite server:# cd /opt/HWENGR/engineering# ./startserver.sh

Procedure

Step 1 On a computer installed with the NMS Maintenance Suite client, double-click the U2000MSuite shortcut icon on the desktop and then wait about one minute. The Login dialog box isdisplayed.

NOTE

l In the Solaris OS, you must log in to the Java desktop system as the root user. Otherwise, the U2000MSuite shortcut icon is not displayed on the desktop.

l In the SUSE Linux OS, you cannot log in to the NMS Maintenance Suite client through the shortcuticon. You need to run the following commands as the root user to start the NMS Maintenance Suiteclient:# cd /opt/HWENGR/engineering# ./startclient.sh

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

l IP Address: It refers to the system IP address of the computer where the NMS MaintenanceSuite server resides. In a distributed system, you need to enter the system IP address of themaster server.

l Port No.: The default port number is 12212. You do not need to change the default valueduring login.

l User Name: The default user name is admin.

l Password: The initial password is admin.

Step 3 Click OK.



3-5

NOTE

l When you log in to the client of the NMS Maintenance Suite, a progress bar showing the progress of queryingcomponents and instances is displayed. In this case, wait until the operation is complete.

l The NMS Maintenance Suite works in single-user mode. That is, only one NMS Maintenance Suite clientcan log in to the NMS Maintenance Suite server at one time. In a high availability system, only one site canbe logged in at one time.

----End

ResultIf a dialog box is displayed during the login, indicating that network configuration informationis inconsistent and re-synchronization is required after login, read through the message to learnthe server that needs to be synchronized. Then, do as follows:

1. On the NMS Maintenance Suite client, click the Server tab.2. Right-click the server whose network configuration needs to be synchronized, and choose

Synchronize the network configuration from the shortcut menu. A dialog box isdisplayed for you to confirm the operation.

3. Click OK.

3.4 Checking the SNMP NBI StatusAfter check the license and ensure it is support SNMP functions, you need to check the currentstatus of SNMP NBI, and deploy the SNMP NBI according the status.

ContextThe 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 theinterface, you need to add the component first and then add the instance. For details, see3.5 Deploying the SNMP NBI for the First Time.

l If the SNMP NBI is installed during the installation of the U2000 server, to enable theinterface, you need to configure the instance. For details, see 3.6 Configuring the SNMPNBI.

The details for how to install the U2000 Server, refer to iManager U2000 Software InstallationGuide. If you want to install SNMP NBI, ensure you have select Northbound SNMP Interfacecomponent during the installation of the U2000 server.

Procedure

Step 1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Clientof the NMS Maintenance Suite.

Step 2 Click Instance tab, check whether the AgentSNMP exist in the instance list.l If the AgentSNMP instance exist, refer the steps in 3.6 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.




Issue 01 (2010-05-18)

Step 3 Click Deployment Package tabs, check whether the SNMP NBI exist in the deploymentpackage list.l If the SNMP NBI deployment package exist, refer the steps in 3.5.2 Adding the SNMP

NBI Instance to enable the SNMP NBI.l If the SNMP NBI deployment package not exist, refer the steps in 3.5 Deploying the SNMP

NBI for the First Time to enable the SNMP NBI.

----End

3.5 Deploying the SNMP NBI for the First TimeBy default, the SNMP NBI is not installed during the installation of U2000 server. To enablethe SNMP NBI, you need to add the SNMP NBI the SNMP NBI component first, then add theSNMP NBI instance.

3.5.1 Adding SNMP NBI ComponentThe SNMP NBI is one components of the U2000. If you have not installed the SNMP NBI bydefault, you need to add the SNMP NBI component.

3.5.2 Adding the SNMP NBI InstanceThe type of SNMP NBI deployment package is system single-instance, you can deploy oneinstance only. After adding the SNMP NBI component, you need to adding SNMP NBI instanceto enable the SNMP interface. You need set the general parameters, and it is recommended youset the advanced parameters to default value.

3.5.1 Adding SNMP NBI ComponentThe SNMP NBI is one components of the U2000. If you have not installed the SNMP NBI bydefault, you need to add the SNMP NBI component.

Prerequisitel The NMS Maintenance Suite server installed on the master and slave servers must be

started.l The System Monitor server of the U2000 must be started.

l The Database server process must be in the Running state.

l The NMS Maintenance Suite client communicates with the NMS Maintenance Suite serverin the normal state.

Contextl 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




3-7

Step 2 On the NMS Maintenance Suite client, choose Deploy > Add Component. The AddComponent dialog box is displayed.

CAUTIONl 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 Northbound SNMP Interface component and click OK, the progress bar isdisplayed.

Step 4 Wait until the dialog box is displayed to prompt the message The component is successfullyadded.

Step 5 Click OK, completed the operation.

----End

Postrequisite

After the component is added, you need to add the SNMP NBI instance, then you can enablethe SNMP interface.

3.5.2 Adding the SNMP NBI InstanceThe type of SNMP NBI deployment package is system single-instance, you can deploy oneinstance only. After adding the SNMP NBI component, you need to adding SNMP NBI instanceto enable the SNMP interface. You need set the general parameters, and it is recommended youset the advanced parameters to default value.

Prerequisitel The NMS Maintenance Suite server installed on the master and slave servers must be

started.

l The System Monitor server of the U2000 must be started.

l Database Server Process must be in the Enable state.

l The NMS Maintenance Suite client must communicate with the NMS Maintenance Suiteserver in the normal state.

l The component to which the instance is added must be installed. If the component is notinstalled, you must add SNMP NBI component first.


master server to perform this operation.

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




Issue 01 (2010-05-18)

Procedure


Step 2 On the NMS Maintenance Suite client, click the Deployment Package tab. Right-click thenorthbound SNMP interface deployment package and choose Add Instance. The dialog box isdisplayed.

Step 3 In the General tab, choose the items in the left object tree, configure the basic project parametersof the SNMP NBI, refer to SNMP Agent and Third-Party NMS for more information.

Step 4 Click the Advanced tab. Choose the required items in the left object tree, refer 3.7 SNMPConfiguration Parameters to set parameters.



3-9

l Heartbeat Settings

l Alarm Field Settings

l Set reporting notification

l Report Date Format Settings

l Other Settings

l MIB Frame Settings

Step 5 Click OK to complete the settings.

Step 6 Optional: In the case of a distribute HA system with multiple NICs, if you enter the IP addressof the master server to deploy SNMP NBI, and this IP address is not in the relevant address drop-list, the Address for Standby Server dialog box is displayed.1. Enter the IP address of the SNMP NBI on the standby server.

CAUTIONl The SNMP service can deploy in the primary server only.

l You can enter any IP address of the standby server (except 127.0.0.1). But you mustensure that the input IP address is correct. That is, the standby server should be able tocommunicate with the upper-layer NMS successfully with the input IP address.

l The CORBA NBI searches for the IP configuration list (hosts file) of the computerautomatically. Additionally, the first IP address in the configuration list is bound to theNaming service host address and Notify service host address. In the case of a single IPaddress, you need not set the Naming service host address and Notify service hostaddress. In the case of multiple IP addresses, you need to set these fields because thebound IP address is unknown. When setting theses fields, you need to set them to IPaddresses that the upper-layer NMS can have access to.

l Receive Request from NMS address is mandatory, Send Trap address is optional,the two parameters can be different.




Issue 01 (2010-05-18)

2. Click OK, complete the settings.

Step 7 Wait until the dialog box is displayed to prompt the success message.

Step 8 Click OK, complete add the CORBA instance.

Step 9 The dialog box is displayed, prompt that restart all of the NMS service.

Step 10 Click OK, close the dialog box.

Step 11 Log in to the System Monitor. Restart all services of the U2000.

Step 12 In the System Monitor client, check the Status of SNMP Service. If the process is running, theSNMP NBI is enabled successfully.

----End

3.6 Configuring the SNMP NBIIn order to enable the SNMP NBI, even though you have installed SNMP NBI component, youneed configure the SNMP parameters accord to NMS planning. Also, you can modify theparameters by configuring SNMP NBI again. As usual, the general parameters is mandatory.The advanced items is optional while the default value is recommended. Every advanced itemis independence and you need not set the parameters in sequence.

Prerequisitel Log in to the Solaris or SUSE Linux OS as the root user.

l Log in to the Windows OS as the Administrator user.

l In a HA system, configure the SNMP interface on the active server.

l The NMS Maintenance Suite server installed on the master and slave servers must bestarted.

l The System Monitor server of the U2000 must be started.



3-11

l The Database server process must be in the Enabled state.


l The SNMP NBI instance must be added. Otherwise, add the related SNMP NBIinstance first.




Procedure


Step 2 On the NMS Maintenance Suite client, choose NBI > Configure the SNMP interfaceinstance from the Main Menu. The dialog box is displayed.

Step 3 In the General tab, choose the items in the left object tree, configure the basic project parametersof the SNMP NBI, refer to SNMP Agent and Third-Party NMS for more information.

Step 4 Click the Advanced tab. Choose the required items in the left object tree, refer 3.7 SNMPConfiguration Parameters to set parameters.




Issue 01 (2010-05-18)

l Heartbeat Settings


l Set reporting notification


l Other Settings

l MIB Frame Settings

Step 5 Click OK to complete the settings.

Step 6 Optional: In the case of a distribute HA system with multiple NICs, if you enter the IP addressof the master server to deploy SNMP NBI, and this IP address is not in the relevant address drop-list, the Address for Standby Server dialog box is displayed.1. Enter the IP address of the SNMP NBI on the standby server.



3-13

CAUTIONl The SNMP service can deploy in the primary server only.

l You can enter any IP address of the standby server (except 127.0.0.1). But you mustensure that the input IP address is correct. That is, the standby server should be able tocommunicate with the upper-layer NMS successfully with the input IP address.

l The CORBA NBI searches for the IP configuration list (hosts file) of the computerautomatically. Additionally, the first IP address in the configuration list is bound to theNaming service host address and Notify service host address. In the case of a single IPaddress, you need not set the Naming service host address and Notify service hostaddress. In the case of multiple IP addresses, you need to set these fields because thebound IP address is unknown. When setting theses fields, you need to set them to IPaddresses that the upper-layer NMS can have access to.

l Receive Request from NMS address is mandatory, Send Trap address is optional,the two parameters can be different.

2. Click OK, complete the settings.

Step 7 The dialog box is displayed, prompt that restart all of the NMS service.

Step 8 Click OK, close the dialog box.

Step 9 Log in to the System Monitor. Restart all services of the U2000.

Step 10 In the System Monitor client, check the Status of SNMP Service. If the process is running, theSNMP NBI is enabled successfully.

----End




Issue 01 (2010-05-18)

3.7 SNMP Configuration ParametersYou can ensure that the connection between the U2000 and the upper layer NMS is normal bycorrectly configuring basic parameters in the deployment tool. You can also configure advancedparameters for customizing the messages queried or reported through the SNMP interface.

Tab Configuration Item

General l SNMP Agent

l Third-Party NMS

Advanced l Heartbeat Settings


l Set reporting notification Parameter


l Other Settings

l MIB Frame Setting

Basic Project

To use the SNMP NBI, you need to correctly configure the trap, community, and the IP addressand port of the upper layer NMS.

To use the SNMP V3 protocol for communication, you need to correctly configure theparameters of the SNMP V3 protocol.

WARNINGl If you have configured the parameters of the SNMP V3 protocol in the NMS Maintenance

Suite, the third-party NMS needs to use the configured parameters for connection.l If you do not configure the parameters, the third-party NMS uses the default parameters for

connection. By default, the user name is SNMPAgent, security model is USM, and securitylevel is no authentication and no encryption.

l The passwords of the authorization authentication protocol and the data encryption protocolare all null.

l When changing a password, you must enter the correct password set last time forconfirmation. In addition, you are not allowed to set a new password to null.

Table 3-1 SNMP Agent parameters

Parameter Description Value

Basic Project



3-15


Send Trap address Specifies the IP address onthe SNMP agent for sendingtraps to the upper layer NMS.

IP addresses except 127.0.0.1Default: IP address of theU2000 server.

Port Specifies the port for sendingtraps.

1-65535Default: null.Recommended value: greaterthan 1024.

Receive Request from NMSaddress

Specifies the IP address forreceiving requests from theupper layer NMS.

IP addresses except 127.0.0.1Default: IP address of theU2000 server.

Port Specifies the port forreceiving requests from theupper layer NMS.

1-65535Default: null.Recommended value: greaterthan 1024.

SNMP version The SNMP NBIU2000support three version ofprotocol: SNMP v1, v2c andv3.

l v1

l v2c

l v3

Default: v1.

SNMP v3 Para Settings

Security Model Specifies the security modelof the SNMP V3 protocol.

USM model

Security Level Specifies the security level ofthe SNMP V3 protocol.

l No Authentication and NoPrivacy

l Authentication and NoPrivacy

l Authentication andPrivacy

Authentication Specifies the authenticationprotocol used by the SNMPV3 protocol.

l NONE

l HMACMD5

l HMACSHA

Data Encryption Specifies the encryptionprotocol used by the SNMPV3 protocol.

l NONE

l DES

l AES




Issue 01 (2010-05-18)

Third-Party NMSTo send messages to the third-party NMS through the SNMP NBI, you need to correctlyconfigure the parameters of the third-party NMS, such as trap information and heartbeatinformation.

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

Table 3-2 Third-party NMS parameters


NMS Receive Trap Address Specifies the IP address ofthe third-party NMS.

IP address

Port Specifies the port of the third-party NMS for receivingtraps.

1~65535Default: 9831.

Read Community When the third-party NMSuses the SNMP V1 or V2cprotocol, the authenticationcontrol between the SNMPagent and the upper layerNMS is implementedthrough communityinformation. To be specific,only when the set communityis the same as that of theupper layer NMS, the third-party NMS can respond to thealarm query requestsreceived. Otherwise, thethird-party NMS ignores therequests.NOTE

The SNMP agent supports amaximum of 10 read/writecommunities.

The default read/writecommunity is public. Youcan also enter any characterstring consisting of 255characters at most.



3-17


Write Community When the third-party NMSuses the SNMP V1 or V2cprotocol, the authenticationcontrol between the SNMPagent and the upper layerNMS is implementedthrough communityinformation. To be specific,only when the set communityis the same as that of theupper layer NMS, the third-party NMS can respond to thealarm query requestsreceived. Otherwise, thethird-party NMS ignores therequests.NOTE

The SNMP agent supports amaximum of 10 read/writecommunities.

The default read/writecommunity is public. Youcan also enter any characterstring consisting of 255characters at most.

V3 User Name Specifies the user name usedby the third-party NMS tocommunicate witAgentSNMP through theSNMP V3 protocol.

l Character string (20)

l Default: SNMPAgent.

V3 Password Authentication Specifies the user passwordof the upper layer NMS forauthentication. Thispassword is used when theSNMP V3 authentication isenabled.

The default password is null.

V3 Password for Privacy If the security level is set toAuthentication andPrivacy, you must setencryption policy of thepassword.

The default password is null.

Alarm Level Specifies the alarm level. Thealarm level is classified intoCritical, Major, Minor, andWarning.

All the items are selected.

Alarm Category Specifies the category ofreported alarms. Thereported alarms are classifiedinto Event Alarm and FaultAlarm.

All the items are selected.




Issue 01 (2010-05-18)

Heartbeat SettingsTo receive heartbeat messages from the third-party NMS, you need to correctly configureheartbeat parameters.

Table 3-3 Heartbeat parameters


Heartbeat Period (not lessthan 15s)

Specifies the heartbeat periodof the third-party NMS. Thevalue of this parameter isgreater than or equal to amultiple of 15.

15-600 sDefault: 60 s.

Required Heartbeat Info There are multiple tabs, suchas NMS 1 and NMS 2, in thewindow. Only whenRequired Heartbeat Info isset to Yes at least on one tabpage, Heartbeat Period isvalid.

Yes, NoDefault: Yes.

Alarm Field SettingsYou can customize the information contained in reported alarms through the deployment tool.Table 3-4 shows the field information.

Table 3-4 Fields of reported alarms

Field Description Value

NE Name Indicates the NE name. Character string(255)

NE Type Indicates the NE type. Character string (64)

Object Instance Indicates the location information.For U2000, this parameter indicates the alarmsource and alarm location information.

Character string(255)



3-19


Event Type Indicates the NMS classification, including:l Communication

l Environment

l Equipment

l Service

l Processing error

l Unknown_EventType

When the configuration item of SupportX.733Alarm is set to 1, alarms are classifiedinto the following types:l communicationsAlarm

l environmentalAlarm

l equipmentAlarm

l qualityofServiceAlarm

l processingErrorAlarm

l Unknown_EventType

Character string (64)

Alarm Rising Time This parameter depends on theAlarmTimeFormat parameter.


Alarm Cause Indicates the cause of generating an alarm. Character string(255)

Alarm Severity Indicates the alarm level, including:l Critical

l Major

l Minor

l Warning

l Indefinite

l Unknown_Severity

When the configuration item of SupportX.733Alarm is set to 1, the alarm levelCleared is added.


Alarm Details Indicates the alarm details. Character string(255)

Alarm Location Indicates the location at which an alarm isgenerated.





Issue 01 (2010-05-18)


Type Flag Indicates the alarm classification, including:l Event

l Fault

l Recovery

l UNKNOWN_EVENT_TYPE


Alarm FunctionCategory

Indicates the function classification,including:


Power Indicates a poweralarm.

Environment Indicates anenvironment alarm.

Signal Indicates a signalingalarm.

Relay Indicates a trunkalarm.

Hardware Indicates a hardwarealarm.

Software Indicates a softwarealarm.

Run Indicates a runalarm.

Communication Indicatescommunicationfailure.

Service Indicates QoS.

Process error Indicates aprocessing error.

UNKNOWN_FUC_TYPE

Indicates theunknown alarm type.

Managed EquipmentAddress

Indicates the NE IP address. IP address

Alarm SerialNumber

Indicates the alarm serial number. Integer

Alarm RecoveryAdvice

Indicates the alarm recovery advice. Character string(255)

Resource ID Indicates the resource ID. Character string(255)



3-21


Event Name Indicates the alarm name. Character string(255)

Alarm Reason ID Indicates the alarm cause ID. Character string(255)

Alarm ID Indicates the alarm ID. Character string(255)

Managed EquipmentType

Indicates the managed equipment type. Character string(255)

Set reporting notificationThe upper layer NMS obtains alarm information through the SNMP agent in two ways: activereporting and active query. You can set the mode for sending alarms through the deploymenttool and set parameters for different alarm obtaining modes.

WARNINGl Trap (passive reporting) : The SNMP agent reports alarms only after receiving a request from

the upper layer NMS.l Inform (active reporting): The SNMP agent reports alarms once alarms are generated. In this

mode, if the parameters configured for the upper layer NMS are incorrect, the SNMP agenttries connecting to the upper layer NMS for many times. This will occupy a large number ofresources. As a result, the efficiency of the SNMP agent is reduced. Therefore, exercisecaution when you set this parameter to Inform.

Table 3-5 Parameters of reported notification


Reporting Mode Specifies the mode used bythe SNMP agent for sendingalarms to the upper layerNMS.

l Trap

l Inform

l Default Value: Trap




Issue 01 (2010-05-18)


Support X733 Alarm Specifies whether traps usethe event types and levelsdefined in X.733.l Yes indicates that the X.

733 format is used.l No indicates that the X.

733 format is not used.NOTE

X.733 is an alarm reportingfunction. This function helpsusers to send and clear alarms.

l Yes, No

l No

Trap Transmit Interval Specifies the time interval ofsending messages in Trapmode.

l 1 ms-1000 ms.

l Default: 40.

Inform Delay Specifies the delay ofsending messages in Informmode.

l 5s-120s.

l Default: 5.

Inform Failure Retry Specifies the retry times ofconnections in the case of afailure in Inform mode.

l 2 times-6 times.

l Default: 3.

Report Date Format SettingsThis parameter specifies the format of reported time of an alarm.

Table 3-6 Parameters of the format of reported time


Alarm Date Format Settings Alarm time can be recorded. l Local Time (without TimeZone)

l UTC Time

l Local Time (with TimeZone)

Default Value: UTC Time

Other SettingsThis parameter specifies whether alarms are recorded in logs. In addition, this parameterspecifies the alarm encoding format and the cache for real-time alarms.



3-23

Table 3-7 Other Settings


Record Log Specifies whether alarms arerecorded in logs.

No

Alarm Character Encode The alarm encoding format isas follows:

l GBK

l UTF-8

UTF-8

Real-time Alarm Cache Size Specifies the cache for real-time alarms. The maximumvalue is 50000 and theminimum value is 0. Eachupper layer NMS user isassigned with an independentcache.

l 0-50000

l Default Value: 10000

MIB Frame Setting

The U2000 provides two types of MIBs and three specifications. You can select the requiredtype to load.

NOTE

For the details of T2000 old MIB, U2000 MIB with old specification and new specification, see BDescription of the Alarms Reported by the SNMP Interface.

Table 3-8 Parameters of the MIB frame


MIB Set the MIB type to beloaded.Default: Use the U2000 MIBwith old specificationCustom-made: Use the MIBof the T2000 V200R006C03or prior versionYou can select the Newspec check box to enable thenew specification. Otherwiseuse the old one. You needchoose the MIB typeaccording the requirement.

l Default

l Custom-made

Resource information oforientation

Set the format of the alarmreporting of SNMP interface.

l Default, FDN

l Default Value: Default




Issue 01 (2010-05-18)

4 Deleting and Disabling an SNMP Interface

About This Chapter

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

4.1 Logging In to the System MonitorThis topic describes how to log in to the System Monitor of the U2000.

4.2 Stopping the SNMP NBIYou can use System Monitor to stopping the SNMP NBI.

4.3 Disabling the SNMP NBIBy disabling the SNMP NBI, you can disable the SNMP interface service without deleting theSNMP interface instance. In this way, the SNMP interface process will not start with theU2000 when you start the U2000 next time.

4.4 Restarting the SNMP NBIWhen the SNMP interface process is in the stopped state, you can restart the process in theSysmonitor client.

4.5 Deleting the SNMP NBI InstanceYou can delete an instance for the SNMP interface if it is not in use, which enhances the runningefficiency of the U2000.

4.6 Deleting the SNMP NBI ComponentYou can delete the component for the SNMP NBI if it is not in use, which enhances the runningefficiency of the U2000.

iManager U2000Northbound SNMP Interface User Guide 4 Deleting and Disabling an SNMP Interface


4-1

4.1 Logging In to the System MonitorThis topic describes how to log in to the System Monitor of the U2000.

PrerequisiteBefore logging in to the System Monitor of the U2000, make sure that:l The U2000 server runs in the normal state.

l The system monitoring process runs in the normal state.

l The System Monitor communicates well with the U2000 server.

l You have a valid user account and password of the U2000.

ContextYou can start the System Monitor, connect the System Monitor to the U2000 server, and monitorthe status of the U2000 server on the System Monitor.

For details about the system monitoring, see section Monitoring the U2000 Processes in theiManager U2000 Administrator Guide.

Procedure

Step 1 Choose Start > Programs > U2000 Network Management System > U2000 System

Monitor or double-click on the desktop to start the System Monitor.

NOTE

On the Solaris or SUSE Linux OS, double-click the U2000 System Monitor shortcut icon on the JavaDesktop System, Release 3 desktop.

Step 2 In the Login dialog box, enter the required user name and password to access the System Monitorwindow.

Step 3 Click Login to log in to the System Monitor of the U2000.

----End

4.2 Stopping the SNMP NBIYou can use System Monitor to stopping the SNMP NBI.

Prerequisitel Log in to the Solaris or SUSE 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.

4 Deleting and Disabling an SNMP InterfaceiManager U2000



Issue 01 (2010-05-18)

ContextNOTE

After the SNMP interface instance is added through the NMS Maintenance Suite, the default start mode isAutomatic. The SNMP interface process is started with the U2000.

Procedure

Step 1 Log in to the System Monitor.

Step 2 On the System Monitor, click 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 isStopped, it indicates that the operation is successful.



4-3

----End

4.3 Disabling the SNMP NBIBy disabling the SNMP NBI, you can disable the SNMP interface service without deleting theSNMP interface instance. In this way, the SNMP interface process will not start with theU2000 when you start the U2000 next time.





l The SNMP Service processes is in the Stopped state.

Procedure






Issue 01 (2010-05-18)

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 isDisabled, it indicates that the operation is successful.

----End

4.4 Restarting the SNMP NBIWhen the SNMP interface process is in the stopped state, you can restart the process in theSysmonitor client.



4-5





l The SNMP Service processes is in the Stopped state.

Procedure



Step 3 Select the SNMP Service process , right-click, and then choose Start the Process from theshortcut menu.

Step 4 In the System Monitor client, when Status of the relevant XML processes, namely SNMPService are Running, the operation is successful.




Issue 01 (2010-05-18)

----End

4.5 Deleting the SNMP NBI InstanceYou can delete an instance for the SNMP interface if it is not in use, which enhances the runningefficiency of the U2000.

Prerequisitel Log in to the Solaris or SUSE Linux OS as user root.






l It is recommended that you stop the SNMP NBI before delete the instance.






4-7

Procedure


Step 2 Click the Instance tab. Select the AgentSNMP instance from the instance list, right-click, andchoose Delete Instance

Step 3 Click OK. After the confirmation, the NMS Maintenance Suite begins deleting the AgentSNMPinstance.

Step 4 Click the Deployment Package tab, if the Instance Count of the SNMP NBI deploymentpackage is zero, that means the deletion success.

NOTE

After the AgentSNMP instance is deleted, the Sysmonitor does not display the information about theAgentSNMP process. If you need to re-enable the SNMP interface, refer to 3.5.2 Adding the SNMP NBIInstance.

----End

4.6 Deleting the SNMP NBI ComponentYou can delete the component for the SNMP NBI if it is not in use, which enhances the runningefficiency of the U2000.

Prerequisitel Log in to the Solaris or SUSE Linux OS as user root.








Issue 01 (2010-05-18)


l Ensure you have deleted the SNMP NBI instance.




Procedure


Step 2 On the NMS Maintenance Suite client, click Deployment Package tab, check whether theinstance 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. The deleting of the component isstarted.

NOTE

You can not delete the components which are basic or have not installed. You can not select them in theleft window.

Step 4 Wait until the message the component is successfully removed is displayed. Click OK.

Step 5 View the Deployment Package list, the Northbound SNMP Interface deployment packagenot exist indicate that the operation is successful.

----End



4-9

5 Maintaining the SNMP NBI

About This Chapter

This chapter introduces how to maintain the U2000 SNMP Northbound Interface.

5.1 Maintenance DescriptionThis section describes the basic requirement of maintenance SNMP NBI.

5.2 Faults and SolutionsThis section introduces the faults of the SNMP Northbound Interface and the related solutions.

iManager U2000Northbound SNMP Interface User Guide 5 Maintaining the SNMP NBI


5-1

5.1 Maintenance DescriptionThis section describes the basic requirement of maintenance SNMP NBI.

To ensure that the U2000 SNMP Northbound Interface works well, there are some requirementsas follows:

1. The maintenance personnel must be familiar with:

l Windows or the Sun workstation - Solaris 8 or Solaris 10, and SuSe Linux 10

l The SNMP protocol

l Basic concepts of the Telecommunication Management Network (TMN)

2. The PC or SUN workstation that is configured with the U2000 SNMP Northbound Interfaceruns normally.

3. The U2000 Server runs normally.

5.2 Faults and SolutionsThis section introduces the faults of the SNMP Northbound Interface and the related solutions.

5.2.1 SNMP Agent Fails to Start

5.2.2 Fails to Receive Alarms

5.2.3 User Unable to Perform Certain Fault Operations

5.2.4 NMS User Could not Connect to the SNMP Agent

5.2.5 Real Time Alarms are Not Reported

5.2.6 Attempt to Acknowledge or Un-acknowledge or Clear Alarms Fails

5.2.1 SNMP Agent Fails to Start

Symptom

After you start the U2000 system, the SNMP Agent does not work. The upper NMS fails toaccess the U2000 system.

Possible Causesl The listening port for the SNMP Agent is in use.

l SNMP service is dependent on log service and licence service.

Procedure

Step 1 Check if other process is using the port of the SNMP service. If there is, stop this process. Fordetails on port, refer to 3.7 SNMP Configuration Parameters.

5 Maintaining the SNMP NBIiManager U2000



Issue 01 (2010-05-18)

Step 2 Start the System Monitor. Check the dependent processes. If they are not started, you need tostart them. Then, start the SNMP Agent.

----End

5.2.2 Fails to Receive Alarms

SymptomYou have added the address of the third-party NMS to the configuration file. However, the NMSfails to receive the alarms.

Possible CausesAfter the configuration is changed, the AgentSNMP is not restarted.

Procedure

Step 1 Restart the AgentSNMP after you change its configuration. Therefore, after you set the IPaddress of the NMS, you need to restart the AgentSNMP.

----End

5.2.3 User Unable to Perform Certain Fault Operations

SymptomCertain Fault operations are not supported due to the license feature provided by the SNMPAgent.

Possible Causesl In Windows, License information file, %IMAPROOT%\server\etc\conf\license

\ONXXXXXXX.dat does not exist.l In Solaris or SUSE Linux, License information file, $IMAPROOT/server/etc/conf/

license/ONXXXXXXX.dat does not exist.l The license file is present but the user is unable to perform certain fault operations.

Procedure

Step 1 User needs to get valid license file.

Step 2 If the license file is valid and EMS SM is down, restart the EMS SM.

----End

5.2.4 NMS User Could not Connect to the SNMP Agent

DescriptionThe NMS user could not connect to the SNMP Agent.



5-3

Possible Causes

The following parameters do not match with the data present in the configuration file.

l Username

l Passwords for authentication and privacy

l SNMP version

l Security model (for SNMP V3)

l Encryption protocol (for SNMP V3) for Privacy (if enabled) and Authorization (ifenabled)

Solution

Ensure that the preceding parameters are correct.

5.2.5 Real Time Alarms are Not Reported

Description

The real-time alarms are not being reported.

Possible Causes

l The IP address and port in the configuration file for the corresponding user does not matchwith the client.

l The security parameters in the trap receiver application does not match with the parametersconfigured in the configuration file.

Solutions

1. Ensure that the configuration is correct.

2. After changing configuration, restart the SNMP agent.

5.2.6 Attempt to Acknowledge or Un-acknowledge or Clear AlarmsFails

Description

Active Alarms cannot be acknowledged or unacknowledged or cleared.

Possible Causes

l Invalid license.

l One or more dependent services are down.

l Version mismatch of the MIB file

5 Maintaining the SNMP NBIiManager U2000



Issue 01 (2010-05-18)

Solutions1. Ensure that the license is valid.2. Ensure that the dependent services are functioning.3. Ensure that there is no version mismatch of the MIB file.4. After changing configuration, restart the SNMP agent.



5-5

6 Accessing U2000 from NMS

This section describes about the various SNMP versions through which NMS can accessU2000.

U2000 supports the simultaneous access of four NMSs by SNMPv1, SNMPv2c or SNMPv3.SNMPv1 and SNMPv2c are based on the community mode, while SNMPv3 is based on the usermode.

Accessing U2000 by SNMPv1For NMS to access U2000, ensure that:

1. The U2000 administrator sets U2000 to support SNMPv1.2. The U2000 administrator configures community name, NMS IP address and port number,

filter alarm category and alarm level.3. The NMS obtains IP address and port number (4700 by default) of the SNMP Northbound

Interface from U2000 administrator.

Accessing U2000 by SNMPv2cFor NMS to access U2000, ensure that:

1. The U2000 administrator sets U2000 to support SNMPv2c.2. The U2000 administrator configures community name, NMS IP address and port number,

filter alarm category and alarm level.3. The NMS obtains the IP address and port number (4700 by default) of the SNMP

Northbound Interface from the U2000 administrator.

Accessing U2000 by SNMPv3To enable NMS for access U2000, ensure that:

1. The U2000 administrator sets U2000 to support SNMPv3 by modifying the SNMPNorthbound Interface configuration file.

2. The U2000 administrator configures SNMPv3 user name, security level, authenticationprotocol, authentication password, and privacy password

3. The U2000 administrator sets the SNMPv3 security levels. The U2000 administratorsupports 3 security levels which includes:

iManager U2000Northbound SNMP Interface User Guide 6 Accessing U2000 from NMS


6-1

l No Authentication and No Privacy

l Authentication and No Privacy

l Authentication and Privacy

In which, Auth-Protocol supports MD5 and SHA, Private-Protocol supports DES.4. The NMS obtains the IP address and port number (4700 by default) of the SNMP

Northbound Interface from the iMAP administrator.

6 Accessing U2000 from NMSiManager U2000



Issue 01 (2010-05-18)

A Relations Between License and SNMPInterface

This part introduces the relations between license and SNMP interface.

The U2000 license controls the software of SNMP interface in the following four dimensions:

l Interface function

l Technical domain

l Management capacity

l Number of OSS connections

l The first three dimensions depend on each other. The U2000 divides the license accordingto 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

technical domain

Management Capacity

Interface Function

iManager U2000Northbound SNMP Interface User Guide A Relations Between License and SNMP Interface


A-1

Table A-1 Description for Dimension

Dimension Meaning

Interface function l Alarm and inventory

l Service provisioning and test diagnosis

l Performance

l Common

l Notification reporting

Technical domain l Transport

l Router and Metro including security

l Access

Management capacity Physical inventory: Controls NEs. The unit isnumber of equivalent NEs.Service inventory: Controls E2E services.The unit is number of services.

Number of OSS connections Indicates the maximum number of OSS usersthat can be online concurrently.

On Solaris or SUSE Linux, view the license as user root. Use the text viewer to view the contentsof the $IMAPROOT/server/etc/conf/license/ONXXXXXXX.dat file.

On Windows, view the license as user administrator. Use the text viewer to view the contentsof the %IMAPROOT%\server\etc\conf\license\ONXXXXXXX.dat file.

Here each "X" represents an integer ranging from 0 to 9. Refer to Table A-2 for the details oflicense control items.

Table A-2 Description for License Item

License Control Item Abbreviation Value

License For NBI SNMPConnection

LNSDPENES07 0-20000

Per Equivalent NE Licensefor NBI-SNMP Alarm -Transmission Network

LNSDPENES01 0-300000

Per Equivalent NE Licensefor NBI-SNMP Alarm -IP

LNSDPENES02 0-300000

Per Narrowband ResourceLicense for NBI-SNMPAlarm--Access

LNSDPENEC21 0-300000

A Relations Between License and SNMP InterfaceiManager U2000


A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-05-18)

License Control Item Abbreviation Value

Per Broadband ResourceLicense for NBI-SNMPAlarm--Access

LNSDPENEC25 0-300000

iManager U2000Northbound SNMP Interface User Guide A Relations Between License and SNMP Interface


A-3

B Description of the Alarms Reported by theSNMP Interface

The Alarms Reported for U2000 MIBThe SNMP NBI support the U2000 MIB with two specifications. The new version have threemore alarm section than the old one: Alarm Reason ID, Alarm ID and Managed EquipmentType.

For more details to set this parameters, see MIB Frame Setting in 3.6 Configuring the SNMPNBI.

Table B-1 The Alarms Reported for U2000 MIB

Name Name in the MIB Description Value

NE Name hwNmNorthbound-NEName

NE name Characterstring (255)

NE Type hwNmNorthbound-NEType

NE equipment type Characterstring (64)

Objectinstance

hwNmNorthboun-dObjectInstance

Orientation informationThe format is as source=NEType/NEName location= Alarm LocationInformationFor example,source=EMS/Local NM location=Parti-tion=/ Server=LINUX-128

Characterstring (255)

iManager U2000Northbound SNMP Interface User Guide B Description of the Alarms Reported by the SNMP Interface


B-1


Event Type hwNmNorthboundEventType

On the network management system,event types are classified as follows:l Communication alarms

l Environment alarms

l Equipment alarms

l Service quality alarms

l Processing error alarms

l Unknown event type

When the SupportX.733Alarmconfiguration item is set to 1, event typesare classified as follows:l Communication alarms


l Equipment alarms





AlarmRisingTime

hwNmNorthboundEventTime

Alarm time.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 asYYYY/MM/DD - hh:mm:ssZ. Example:2009/12/23 - 11:30:30Z

l Local Time with timezoneinformation. The format is as YYYY/MM/DD - hh:mm:ss,hh:mmTZ[DST], where TZ stands for timezoneinformation. 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 1hr. The DST value is in seconds.)


AlarmCause

hwNmNorthbound-ProbableCause

Possible causes for an alarm Characterstring

B Description of the Alarms Reported by the SNMP InterfaceiManager U2000


B-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-05-18)


AlarmSeverity

hwNmNorthbound-Severity

Severity level of an alarm.The severity levels of the alarms are asfollows:l Critical

l Major

l Minor

l Warning

l Indefinite

l Unknown severity

When the SupportX.733Alarmconfiguration item is set to 1, theCleared severity level is added.


AlarmDetails

hwNmNorthboundEventDetail

ID, device type, and details of an alarm Characterstring (255)

AlarmLocation

hwNmNorthboun-dAdditionalInfo

Detailed location of the equipment Characterstring (255)

Type Flag hwNmNorthbound-FaultFlag

Alarm types are as follows:l Event

l Fault

l Recovery



AlarmFunctionCategory

hwNmNorthbound-FaultFunction

Function types are as follows:l Power alarms


l Signaling alarms

l Relay alarms

l Hardware alarms

l Software alarms

l Running alarms

l Communication faults



l Unknown type alarms


ManagedEquipmentAddress

hwNmNorthbound-DeviceIP

IP address of the equipment IP address



B-3


AlarmSerialNumber

hwNmNorthbound-SerialNo

Serial number of an alarm Integer

AlarmRecoveryAdvice

hwNmNorthbound-ProbableRepair

Advice for recovery Characterstring

ResourceID

hwNmNorthboun-dResourceIDs

Resource ID Characterstring (255)

EventName

hwNmNorthboundEventName

Event name of an alarm Characterstring (255)

AlarmReason ID

hwNmNorthboun-dReasonID

Indicates the alarm cause ID. Characterstring (255)

Alarm ID hwNmNorthbound-FaultID

Indicates the alarm ID. Characterstring (255)

ManagedEquipmentType

hwNmNorthbound-DeviceType

Indicates the managed equipment type. Characterstring (255)

The Alarms Reported for T2000 of the old architecture MIBIn U2000 V100R002C01, SNMP alarms in old MIB (that is, T2000 V200R006C03 and priorversions) can be adapted.

For more details to set this parameters, see MIB Frame Setting in 3.6 Configuring the SNMPNBI.

Table B-2 The Alarms Reported for T2000 old MIB


EMS Name northboundReportA-larmEmsName

NE name.The value is alwaysHuawei/T2000.


Equipment Type northboundReportA-larmManagedOb-jectClass

NE equipment type.For example, OptiX2500+.


Equipment Name northboundReportA-larmManagedObjec-tInstance

Equipment name.For example, NE350.





Issue 01 (2010-05-18)


NE Name northboundReportA-larmNEName

NE name, which isconsistent with theequipment name.For example, NE350.


Rack Name northboundReportA-larmRackName

Rack name.The value is always1.


Subrack Name northboundReportA-larmShelfName

Subrack name.1. In the WDM orOTN domain, an NEname is the name ofan optical NE and asubrack name is thename of the subrackthat is located in anoptical NE.2. In the SDH orother domain, an NEis a subrack. That is,an NE name and thesubrack name are thesame.For example, NE350.


Physical Location ofEquipment

northboundReportA-larmDevLocation

Physical location ofequipment.The value is alwaysnull.


Board Name northboundReportA-larmBoardName

Board name.For example, PQ1.


Port Type northboundReportA-larmPortType

Port type.For example,SDH_TU.


Port Number northboundReportA-larmPortNumber

Port number.For example, 1.

Integer (4)



B-5


Location of an AlarmObject

northboundReportA-larmLocation

Specific location ofan alarm.For example,ne=590174/rack=1/shelf=1/slot=5/domain=sdh/port=1/highPath=1/lowPath=0/layer=5The rules forassembling alarmlocation informationfor a PTN NE may beslightly different. Forexample,ne=3145796/rack=1/shelf=1/slot=4/domain=ptn/type=physical/port=1/location1=260/layer=15


Alarm Type northboundReportA-larmEventType

Alarm type.The value can be anyof the following:communicationsA-larm, qualityofServi-ceAlarm,equipmentAlarm,processingErrorA-larm, andenvironmentalA-larm.


Alarm Rising Time northboundReportA-larmEventTime

Alarm rising time.For example,2005-10-14,17:41:04.0.


Alarm Severity northboundReportA-larmPerceivedSever-ity

Alarm severity.The value can be anyof the following:Critical, Major,Minor, Warning,cleared, andindeterminate.


Possible AlarmCause

northboundReportA-larmProbableCause

Possible alarm cause.For example, RAI.





Issue 01 (2010-05-18)


Alarm Cause northboundReportA-larmSpecificPro-blems

Alarm cause.For example, NEcommunication waslost


Affect Service northboundReportA-larmOperationAf-fected

Whether an alarmaffects the service.The value can be 0 or1.0: The alarm does notaffect the service.1: The alarm affectsthe service.

Integer (4)

Alarm ID northboundReportA-larmID

Alarm ID.For example, 93.

Integer (4)

Alarm Name northboundReportA-larmName

Alarm name.For example,LP_RDI.


Advice on Fixing anAlarm

northboundReportA-larmProposedRe-pairActions

Advice on fixing analarm.The value is alwaysnull.


IP Address of theObject for AlarmRising

northboundReportA-larmIPAddress

IP address of theequipment where analarm is generated.The value is alwaysnull.


Serial Number of anAlarm

northboundReportA-larmNotificationI-dentifier

Serial number of analarm.For example, 109.

long(8)

ID of the Resourcefor Alarm Rising

northboundReportA-larmResourceID

ID of the resourcewhere an alarm isgenerated.The value is alwaysnull.

Integer (4)

AdditionalInformation

northboundReportA-larmAdditionalText

Additionalinformation.For example, AlarmParameter II(hex)0x02




B-7


Clear Alarm northboundReportA-larmCleared

Whether to clear analarm.The value can be 0 or1.0: Do not clear thealarm.1: Clear the alarm.

Integer (4)

Serial Number of theAlarm to Be Cleared

northboundReportA-larmCorrelatedNoti-fications

Serial number of thealarm to be cleared.The value is the sameas the value of thealarm serial numberfield.

Integer (4)

Additional AlarmInformation (10Fields)

northboundReportA-larmAdditionalVB

Additionalinformation of analarm.The value is the sameas the value of thealarm rising timefield.





Issue 01 (2010-05-18)

C Sample

Automatic Alarm Reporting5: hwNmNorthboundEventInfo.0.1 notification received from: 10.71.34.14 at 2010-1-26 15:19:27 Time stamp: 0 days 00h:19m:04s.98th Agent address: 10.71.34.14 Port: 6666 Transport: IP/UDP Protocol: SNMPv2c Notification Manager address: 10.70.71.174 Transport: IP/UDP Community: public Bindings (21) Binding #1: sysUpTime.0 *** (timeticks) 0 days 00h:19m:04s.98th Binding #2: internet.6.3.1.1.4.1.0 *** (oid) hwNmNorthboundEventInfo.0.1 Binding #3: hwNmNorthboundNEName.0 *** (octets) PTN910-2 Binding #4: hwNmNorthboundNEType.0 *** (octets) OptiX PTN 910 Binding #5: hwNmNorthboundObjectInstance.0 *** (octets) - Binding #6: hwNmNorthboundEventType.0 *** (octets) Equipment Binding #7: hwNmNorthboundEventTime.0 *** (octets) 2010/01/26 - 15:18:20 Binding #8: hwNmNorthboundProbableCause.0 *** (octets) ID:-76,DeviceType:129040384, Binding #9: hwNmNorthboundSeverity.0 *** (octets) Critical Binding #10: hwNmNorthboundEventDetail.0 *** (octets) ID:180,DeviceType:129040384, Binding #11: hwNmNorthboundAdditionalInfo.0 *** (octets) NE security log wrap Binding #12: hwNmNorthboundFaultFlag.0 *** (octets) Event Binding #13: hwNmNorthboundFaultFunction.0 *** (octets) Power Binding #14: hwNmNorthboundDeviceIP.0 *** (octets) 129.10.6.62 Binding #15: hwNmNorthboundSerialNo.0 *** (int32) 21529 Binding #16: hwNmNorthboundProbableRepair.0 *** (octets) ID:-76,DeviceType:129040384, Binding #17: hwNmNorthboundResourceIDs.0 *** (octets) 3145740.-1.-1.-1.-1.-1.-1.-1 Binding #18: hwNmNorthboundEventName.0 *** (octets) ID:180,DeviceType:129040384,Security log circle Binding #19: hwNmNorthboundReasonID.0 *** (octets) -76 Binding #20: hwNmNorthboundFaultID.0 *** (octets) 3 Binding #21: hwNmNorthboundDeviceType.0 *** (octets) 129040384

Start of Alarm Synchronization14: hwNmNorthboundEventSynchronizationStart.0.9 notification received from: 10.71.34.14 at 2010-1-26 15:13:30

iManager U2000Northbound SNMP Interface User Guide C Sample


C-1

Time stamp: 0 days 00h:13m:07s.88th Agent address: 10.71.34.14 Port: 6666 Transport: IP/UDP Protocol: SNMPv2c Notification Manager address: 10.70.71.174 Transport: IP/UDP Community: public Bindings (2) Binding #1: sysUpTime.0 *** (timeticks) 0 days 00h:13m:07s.88th Binding #2: internet.6.3.1.1.4.1.0 *** (oid) hwNmNorthboundEventSynchronizationStart.0.915: hwNmNorthboundEventSynchronizationQueryResult.0.10 notification received from: 10.71.34.14 at 2010-1-26 15:13:33 Time stamp: 0 days 00h:13m:10s.86th Agent address: 10.71.34.14 Port: 6666 Transport: IP/UDP Protocol: SNMPv2c Notification Manager address: 10.70.71.174 Transport: IP/UDP Community: public Bindings (21) Binding #1: sysUpTime.0 *** (timeticks) 0 days 00h:13m:10s.86th Binding #2: internet.6.3.1.1.4.1.0 *** (oid) hwNmNorthboundEventSynchronizationQueryResult.0.10 Binding #3: hwNmNorthboundNEName.0 *** (octets) TMO_PTN950-1 Binding #4: hwNmNorthboundNEType.0 *** (octets) OptiX PTN 950 Binding #5: hwNmNorthboundObjectInstance.0 *** (octets) SYSTEM CLOCK Binding #6: hwNmNorthboundEventType.0 *** (octets) Processerror Binding #7: hwNmNorthboundEventTime.0 *** (octets) 2010/01/25 - 22:16:27 Binding #8: hwNmNorthboundProbableCause.0 *** (octets) ID:77,DeviceType:129105920,\(1)A priority table is not manually set for the system, and NEs use their own default priority tables;\(2)A priority table is set, but only the internal clock source i ... Binding #9: hwNmNorthboundSeverity.0 *** (octets) Minor Binding #10: hwNmNorthboundEventDetail.0 *** (octets) ID:333,DeviceType:129105920,\(1)A priority table is not manually set for the system, and NEs use their own default priority tables;\(2)A priority table is set, but only the internal clock source i ... Binding #11: hwNmNorthboundAdditionalInfo.0 *** (octets) Alarm Parameter II(hex) 0x02 Binding #12: hwNmNorthboundFaultFlag.0 *** (octets) Fault Binding #13: hwNmNorthboundFaultFunction.0 *** (octets) Signal Binding #14: hwNmNorthboundDeviceIP.0 *** (octets) 129.10.6.64 Binding #15: hwNmNorthboundSerialNo.0 *** (int32) 10081 Binding #16: hwNmNorthboundProbableRepair.0 *** (octets) ID:77,DeviceType:129105920, Binding #17: hwNmNorthboundResourceIDs.0 *** (octets) 3145742.-1.-1.-1.-1.-1.-1.-1 Binding #18: hwNmNorthboundEventName.0 *** (octets) ID:333,DeviceType:129105920,CLK_NO_TRACE_MODE Binding #19: hwNmNorthboundReasonID.0 *** (octets) 77 Binding #20: hwNmNorthboundFaultID.0 *** (octets) 0 Binding #21: hwNmNorthboundDeviceType.0 *** (octets) 129105920

End of Alarm Synchronization105: hwNmNorthboundEventSynchronizationEnd.0.11 notification received from: 10.71.224.159 at 2010-1-5 14:23:20 Time stamp: 1 days 03h:39m:44s.42th Agent address: 10.71.224.159 Port: 32806 Transport: IP/UDP Protocol: SNMPv2c Notification Manager address: 10.71.36.89 Port: 162 Transport: IP/UDP Community: SNMPAgent Bindings (4) Binding #1: sysUpTime.0 *** (timeticks) 1 days 03h:39m:44s.42th

C SampleiManager U2000


C-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-05-18)

Binding #2: internet.6.3.1.1.4.1.0 *** (oid) hwNmNorthboundEventSynchronizationEnd.0.11 Binding #3: hwNmNorthboundEventSynchronizationEndStatus.0 *** (int32) stopped(2) Binding #4: hwNmNorthboundEventSynchronizationEndStatusDetail.0 *** (octets) Sync Stopped: The synchronization is stopped by the NMS's command!

Heartbeat3: hwNmNorthboundEventKeepAliveInfo.0.2 notification received from: 10.71.34.14 at 2010-1-26 15:19:23 Time stamp: 0 days 00h:19m:00s.97th Agent address: 10.71.34.14 Port: 6666 Transport: IP/UDP Protocol: SNMPv2c Notification Manager address: 10.70.71.174 Transport: IP/UDP Community: public Bindings (3) Binding #1: sysUpTime.0 *** (timeticks) 0 days 00h:19m:00s.97th Binding #2: internet.6.3.1.1.4.1.0 *** (oid) hwNmNorthboundEventKeepAliveInfo.0.2 Binding #3: hwNmAgent *** (octets) SNMP Agent

iManager U2000Northbound SNMP Interface User Guide C Sample


C-3

D 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 System

P

PDU Protocol Data Unit

S

SOAP Simple Object Access Protocol

iManager U2000Northbound SNMP Interface User Guide D Acronyms and Abbreviations


D-1

SMI Structure of Management Information

SNMP Simple Network Management Protocol

T

TCP Transmission Control Protocol

TMN Telecommunication Management Network

V

VB Variable Bindings

D Acronyms and AbbreviationsiManager U2000


D-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-05-18)

Documents

iManager U2000 Northbound SNMP Interface User Guide-(V100R002C01_01) (2)