Imanager U2000 Northbound SNMP Interface User Guide

iManager U2000 Unified Network Management System V100R002C01
Northbound SNMP Interface User Guide

Issue Date 01 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 written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 01 (2010-05-18)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
iManager U2000 Northbound SNMP Interface User Guide
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document. Product Name iManager U2000 Version V100R002C01
Intended Audience
The iManager U2000 Northbound SNMP Interface User Guide describes the basic concept and principles of U2000 northbound SNMP interface. And it is also describes how to deploying and maintaining the SNMP NBI. This document also provides the relationship between the SNMP NBI and license, description of alarms reported by the SNMP interface, the glossary, and the acronyms and abbreviations. This document guides the user to understand basic operations of the U2000 SNMP NBI. This document is intended for:
l l l
Installation and Commissioning Engineer Data Configuration Engineer Application Developer
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description
DANGER
Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury.
WARNING
Issue 01 (2010-05-18)
iii
About This Document
Symbol
Description
CAUTION
TIP
Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
NOTE
Command Conventions
The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... }* Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
iv
Issue 01 (2010-05-18)
About This Document
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Changes in Issue 01 (2010-05-18) Based on Product Version V100R002C01

Initial release.
Issue 01 (2010-05-18)
Contents
Contents
About This Document...................................................................................................................iii 1 Overview......................................................................................................................................1-1
1.1 Network Position.............................................................................................................................................1-2 1.2 Introduction to SNMP.....................................................................................................................................1-2 1.2.1 Overview................................................................................................................................................1-3 1.2.2 Structure.................................................................................................................................................1-3 1.2.3 MIB Description.....................................................................................................................................1-6 1.2.4 Technical Features..................................................................................................................................1-7 1.3 Security Mechanism........................................................................................................................................1-8 1.3.1 Overview................................................................................................................................................1-9 1.3.2 Security Mechanism of SNMP v1 and v2c............................................................................................1-9 1.3.3 Security Mechanism of SNMP v3..........................................................................................................1-9 1.4 Performance Indexes.....................................................................................................................................1-10
2 Function Interfaces.....................................................................................................................2-1
2.1 Reporting Fault Alarms in Real-Time.............................................................................................................2-2 2.2 Querying Current Alarms................................................................................................................................2-3 2.2.1 Changing Filter Criteria.........................................................................................................................2-3 2.2.2 Synchronizing Alarms............................................................................................................................2-5 2.2.3 Acknowledging Alarms..........................................................................................................................2-6 2.2.4 Unacknowledging Alarms......................................................................................................................2-8 2.2.5 Clearing Alarms.....................................................................................................................................2-9 2.3 Alarm handshaking and Caching..................................................................................................................2-10 2.4 Traps..............................................................................................................................................................2-11 2.4.1 Overview..............................................................................................................................................2-11 2.4.2 Active Alarm Trap...............................................................................................................................2-12 2.4.3 Alarm Query Start Trap........................................................................................................................2-17 2.4.4 Alarm Query Stop Trap........................................................................................................................2-17 2.4.5 KeepAlive Info.....................................................................................................................................2-18
3 Deploying and Configuring SNMP.......................................................................................3-1

3.1 Overview.........................................................................................................................................................3-3 3.2 Configuration Requirements...........................................................................................................................3-4 3.3 Logging in to the Client of the NMS Maintenance Suite................................................................................3-4 Issue 01 (2010-05-18) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
3.4 Checking the SNMP NBI Status.....................................................................................................................3-6 3.5 Deploying the SNMP NBI for the First Time.................................................................................................3-7 3.5.1 Adding SNMP NBI Component............................................................................................................3-7 3.5.2 Adding the SNMP NBI Instance............................................................................................................3-8 3.6 Configuring the SNMP NBI..........................................................................................................................3-11 3.7 SNMP Configuration Parameters..................................................................................................................3-15
4 Deleting and Disabling an SNMP Interface.........................................................................4-1

4.1 Logging In to the System Monitor..................................................................................................................4-2 4.2 Stopping the SNMP NBI.................................................................................................................................4-2 4.3 Disabling the SNMP NBI................................................................................................................................4-4 4.4 Restarting the SNMP NBI...............................................................................................................................4-5 4.5 Deleting the SNMP NBI Instance...................................................................................................................4-7 4.6 Deleting the SNMP NBI Component..............................................................................................................4-8
5 Maintaining the SNMP NBI....................................................................................................5-1

5.1 Maintenance Description.................................................................................................................................5-2 5.2 Faults and Solutions........................................................................................................................................5-2 5.2.1 SNMP Agent Fails to Start.....................................................................................................................5-2 5.2.2 Fails to Receive Alarms.........................................................................................................................5-3 5.2.3 User Unable to Perform Certain Fault Operations.................................................................................5-3 5.2.4 NMS User Could not Connect to the SNMP Agent...............................................................................5-3 5.2.5 Real Time Alarms are Not Reported......................................................................................................5-4 5.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
viii
Issue 01 (2010-05-18)
Figures
Figures
Figure 1-1 Position of the SNMP alarm NBI in the network...............................................................................1-2 Figure 1-2 SNMP structure.................................................................................................................................. 1-4 Figure 1-3 SNMP protocol frame.........................................................................................................................1-5 Figure 1-4 Security mechanism............................................................................................................................1-9 Figure 2-1 Configuring alarm reporting procedure..............................................................................................2-2 Figure 2-2 Caching Alarms................................................................................................................................2-11 Figure A-1 Main dimensions...............................................................................................................................A-1
Issue 01 (2010-05-18)
ix
Tables
Tables
Table 1-1 SNMP Components..............................................................................................................................1-3 Table 1-2 Component description........................................................................................................................ 1-4 Table 1-3 PDU type..............................................................................................................................................1-6 Table 1-4 SNMP Version and Details..................................................................................................................1-7 Table 1-5 Performance indexes of the SNMP alarm NBI..................................................................................1-10 Table 2-1 MIB Node Content...............................................................................................................................2-3 Table 2-2 Alarm filter level..................................................................................................................................2-4 Table 2-3 Alarm category filter Condition...........................................................................................................2-4 Table 2-4 MIB Node Details - Acknowledging Alarms.......................................................................................2-7 Table 2-5 Alarm states - Acknowledge Alarms................................................................................................... 2-7 Table 2-6 MIB Node Details - Unacknowledging Alarms...................................................................................2-8 Table 2-7 Alarm states - Unacknowledge Alarms................................................................................................2-8 Table 2-8 MIB Node Details - Clearing Alarms.................................................................................................. 2-9 Table 2-9 Alarm states - Clear Alarms...............................................................................................................2-10 Table 2-10 Fields of hwNmNorthboundEventNotify TRAP-TYPE table.........................................................2-12 Table 2-11 Trap Definition of Alarm Query Start Trap.....................................................................................2-17 Table 2-12 3 Trap Definition of Alarm Query Stop Trap..................................................................................2-18 Table 2-13 Trap Definition of KeepAlive Info..................................................................................................2-18 Table 2-14 Filed List..........................................................................................................................................2-19 Table 3-1 SNMP Agent parameters....................................................................................................................3-15 Table 3-2 Third-party NMS parameters.............................................................................................................3-17 Table 3-3 Heartbeat parameters..........................................................................................................................3-19 Table 3-4 Fields of reported alarms....................................................................................................................3-19 Table 3-5 Parameters of reported notification....................................................................................................3-22 Table 3-6 Parameters of the format of reported time.........................................................................................3-23 Table 3-7 Other Settings.....................................................................................................................................3-24 Table 3-8 Parameters of the MIB frame.............................................................................................................3-24 Table A-1 Description for Dimension.................................................................................................................A-2 Table A-2 Description for License Item..............................................................................................................A-2 Table B-1 The Alarms Reported for U2000 MIB................................................................................................B-1 Table B-2 The Alarms Reported for T2000 old MIB..........................................................................................B-4
Issue 01 (2010-05-18)
xi
1 Overview
1
About This Chapter
1.1 Network Position This part describes the position of the SNMP NBI in a network. 1.2 Introduction to SNMP This part introduces the SNMP protocol and structure.
Overview
This chapter introduces the Simple Network Management Protocol (SNMP) alarm Northbound Interface (NBI) of the network management system.
1.3 Security Mechanism The security mechanism is provided by all the supported SNMP versions, SNMPv1, SNMPv2c and SNMPv3. 1.4 Performance Indexes This part introduces the performance indexes of SNMP alarm NBI.
Issue 01 (2010-05-18)
1-1
1 Overview
1.1 Network Position

This part describes the position of the SNMP NBI in a network. The SNMP alarm NBI is an agent module between the following entities:
l l
Element Management System (EMS) Network Management System (NMS)
The SNMP alarm NBI provides the upper NMS with the following protocol versions:
l l l
SNMP v1 SNMP v2c 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
NMS Get/Set SNMP Trap
SNMP alarm northbound interface
EMS
Device Network NEn NE1 NE2
NE: Network Element EMS: Element Management System
NMS: Network Management System SNMP: Simple Network Management Protocol
1.2 Introduction to SNMP

This part introduces the SNMP protocol and structure.
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-18)
1 Overview
1.2.1 Overview This part describes the function and structure of SNMP. 1.2.2 Structure SNMP involves of a series of protocols and specifications. It provides the method of collecting NMS information from NEs and reporting problems and errors to the NMS. 1.2.3 MIB Description This chapter provides the basic concepts of MIB. 1.2.4 Technical Features The U2000 supports SNMPv1, SNMPv2c, and SNMPv3.
1.2.1 Overview
This part describes the function and structure of SNMP. As a widely applied industry standard for the NMS protocols, the SNMP aims:
l l
To transmit the management information between two nodes. To help the manager to search and modify the information, and locate faults at any node in the network. To help the manager to diagnose the faults, configure the capacity, and generate reports.
The features of the SNMP are as follows:

l l
Uses the polling mechanism and provides a basic function set. Fits small, fast and cost effective network.
1.2.2 Structure
SNMP involves of a series of protocols and specifications. It provides the method of collecting NMS information from NEs and reporting problems and errors to the NMS. SNMP consists of the following three components: Table 1-1 SNMP Components Component Structure of Management Information (SMI) Management Information Base (MIB) SNMP management protocol Describes How to describe the management information. How to store managed objects. How to manage the objects and realize the network management functions.
SNMP Structure
SNMP is a protocol used for communication between NMS processes and the SNMP agent. The NMS adopting SNMP consists of the following components:
Issue 01 (2010-05-18) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3
1 Overview
l l
Network management station. It is also called Explorer. SNMP agent.
Figure 1-2 SNMP structure

Managed System
1
MIB
Operation SNMP
1 1 1
2 2 2 6
Agent
Notification 5
NMS
U2000
NE database
Table 1-2 Component description Component NMS Description It indicates network management software running on a workstation. The administrator sends requests to managed NEs on the NMS for monitoring and configuring NEs. It indicates an agent process running on a managed NE. After the managed NE receives a request sent by the NMS, the agent responds to the request. An agent is mainly used for collecting NE status information, performing operations on NEs remotely on the NMS, and sending an alarm to the NMS. It indicates a virtual database considered as an NE status set maintained on NEs. The agent collects NE status information by searching MIB.
Agent
MIB
1-4
Issue 01 (2010-05-18)
1 Overview
Component SNMP
Description It indicates a protocol used for communication between NMS processes and the SNMP agent. The NMS adopting SNMP consists of the following components:
l
Explorer
Sends query messages to managed NEs through SNMP. Receives responses and trap packets from managed NEs. Runs on NEs. Receives and handles query messages sent from agents. Obtains the values of management variables from other modules of NEs and generates response messages. Sends messages to the NMS. After an emergency occurs, the SNMP agent can actively send trap packets to the NMS.
SNMP agent

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 application
SNMP application
MIB Base
GetNextRequest
GetNextRequest
Trap GetResponse
Trap GetResponse
GetRequest
GetRequest
SNMP Manager UDP IP Data Link Layer Physical Network
SetRequest
SetRequest
SNMP Manager UDP IP Data Link Layer Physical Network
Issue 01 (2010-05-18)
1-5
1 Overview
SNMP supports five types of protocol data units (PDUs), as follows: Table 1-3 PDU type PDU GetRequest-PDU GetNextRequest-PDU Function It is used for accessing an agent and obtaining variable values from the table. It can obtain the next logical ID descriptor from MIB. Its functions are the same as those of GetRequest-PDU except this function. It is used for responding to GetResponse, GetNextResponse, and SetRequest PDUs. It contains the ID descriptors relevant to the preceding PDUs and provides ID descriptors of response status information, such as error codes, error status, and supplementary information list. It describes the action acting on an element. Typically, it is used for modifying the values in the variable list. It allows the network management module to report an event occurred on an NE or status change of an NE.
GetResponse-PDU
SetRequest-PDU Trap-PDU
1.2.3 MIB Description

This chapter provides the basic concepts of MIB. The MIB is a key part of the SNMP network management framework. The MIB is the object set managed by SNMP, including all the variables to be managed. All the SNMP operations such 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 SNMP Northbound Interface. The definitions decide what operations the NMS can do and what network management 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 node 1 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 SNMP Northbound Interface. The SNMP Northbound Interface further assigns the MIB node information based on the root node. See below:
--- huawei(2011) |--- products (2) |--- hwNetManagement(15) |--- hwNmAgent (1) |---- hwNmFault (5)
1-6
Issue 01 (2010-05-18)
1 Overview
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 l l l
NA: Not Accessible RC: Read and Create RW: Read and Write RO: Read Only
1.2.4 Technical Features

The U2000 supports SNMPv1, SNMPv2c, and SNMPv3. Table 1-4 SNMP Version and Details SNMP Version SNMPv1 Supported Details
l
Mutual access to management information between the SNMP management system and SNMP Agent. Operations

Get Set Trap GetRequest GetNextRequest GetResponse SetRequest Trap
Protocol Data Unit (PDU)

SNMPv1 community-based security model
NOTE The NMS needs to get the community information from the U2000 administrator.
Issue 01 (2010-05-18)
1-7
1 Overview
SNMP Version SNMPv2c
Supported Details SNMPv2 supports all the SNMPv1 functions and the following new features:
l
Access to management information between SNMP management systems. Operations

GetBulk Inform Report
Updated format of the Trap PDU, which is the same as that of the Get/Set PDU. Fractionalized error codes.
NOTE The NMS needs to get the community information from the U2000 administrator.
SNMPv3
SNMPv3 supports all SNMPv2 functions and the following new features:
l l
User-based security model 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, PrivateProtocol supports DES.

NOTE The NMS cannot access the NBI unless it gets the SNMP v3 information from the U2000 administrator.
1.3 Security Mechanism

The security mechanism is provided by all the supported SNMP versions, SNMPv1, SNMPv2c and SNMPv3. 1.3.1 Overview The 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 v2c This section describes the security mechanism of SNMP versions v1 and v2c. 1.3.3 Security Mechanism of SNMP v3 This section describes the security mechanism of SNMPv3 version.
1-8
Issue 01 (2010-05-18)
1 Overview
1.3.1 Overview
The 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, while SNMP v3 uses the user-based security mechanism. Figure 1-4 Security mechanism
NMS
v1/v2c use community name based security mechanism
v3 uses user based security mechanism
SNMP alarm northbound interface
1.3.2 Security Mechanism of SNMP v1 and v2c

This 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 plain text 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 configured in 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 configured in the agent.
1.3.3 Security Mechanism of SNMP v3

This section describes the security mechanism of SNMPv3 version. SNMPv3 adopts the user-based security mechanism. The authentication and encryption mechanisms are used during the interaction with SNMP. To do read and write operations to agent, user must know:
l l l
SNMP v3 user name in the Agent. Security level. The authentication and/or privacy passwords information.
The trap packets can be correctly resolved and handled only when the receiving end knows authentication parameters configured at agent correctly.
1 Overview
SNMP v3 uses the elements such as EngineID and EngineBoots to avoid delay, frame change and other attacks. Therefore, the security is greatly optimized compared with SNMP v1 and v2c.
1.4 Performance Indexes

This 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 Maximum concurrent NMS connections Alarm Forwarding capacity Alarm forwarding delay SNMP request response delay Index 10 Not less than 60 alarms per second (three NMSs connected) Less than 10 seconds (three NMSs connected) Less than 5 seconds (CPU usage is less than 50%)
1-10
Issue 01 (2010-05-18)
2 Function Interfaces
2
About This Chapter
Function Interfaces
The SNMP Northbound Interface provides different function interfaces to the different NMSs. 2.1 Reporting Fault Alarms in Real-Time The SNMP Northbound Interface reports the real-time fault alarms to the NMS, so that the NMS can get the exact information of NE real-time alarms. 2.2 Querying Current Alarms Through 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 Caching Real time alarms are sent through Inform to the third party NMS. When the NMS is down due to some failure at its side, real-time alarms are cached. When the failure is rectified, all the cached alarms are sent to the NMS in the order in which they were received from the EMS. 2.4 Traps This chapter introduces the trap configuration information of the SNMP Northbound Interface.
Issue 01 (2010-05-18)
2-1
2.1 Reporting Fault Alarms in Real-Time

The SNMP Northbound Interface reports the real-time fault alarms to the NMS, so that the NMS can 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 address and port of the NMS for receiving alarms
Set the alarm contents and sending options
Set the alarm filter conditions
Restart the SNMP Agent
End
Procedure
Step 1 Register the receiving IP address, port and the currently-used protocol version for receiving realtime alarms. You can configure the NMS Receive Trap Address and NMS Receive Trap Port of the thirdparty 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
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 checked against the specified filter conditions. Accordingly, the alarms are either reported or filtered out. ----End
2.2 Querying Current Alarms

Through 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 Criteria The alarm filter criteria can be changed dynamically when the SNMP NBI is running. 2.2.2 Synchronizing Alarms Fault alarm synchronization is a process in which the alarms are queried by the third party NMS so that the alarms are consistent between upper NMS and EMS. 2.2.3 Acknowledging Alarms NMS can acknowledge alarms based on the alarm serial numbers. 2.2.4 Unacknowledging Alarms NMS can unacknowledge alarms based on the alarm serial numbers. 2.2.5 Clearing Alarms NMS can clear alarms based on the alarm serial numbers.
2.2.1 Changing Filter Criteria

The alarm filter criteria can be changed dynamically when the SNMP NBI is running.
Context
The following MIB Node is exposed to the user. Table 2-1 MIB Node Content Node Name thirdNMSFaultFilter OID 1.3.6.1.4.1.2011.2.15.1.3.5
Issue 01 (2010-05-18)
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 file and the alarm filter level is the condition for filtering the alarms.
CAUTION
Enter the IP address and port number of the upper-layer OSS.
NOTE
l l
On the Windows OS, the configuration file snmp_agent_svc.xml in the %IMAPROOT%\server\etc \conf. 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 that can be filtered are critical, major, minor, and warning. Table 2-2 lists the meanings of each bit of the alarm filter level. If a bit is set to 0, it indicates that the alarms of the corresponding severity level are reported. If a bit is set to 1, it indicates that the alarms of the corresponding severity level are filtered out. Table 2-2 Alarm filter level Most Significant Bit (MSB) Critical Alarm Major Alarm Minor Alarm Least Significant Bit (LSB) Warning Alarm
The alarm category filter condition is represented in three bits in binary notation. The alarm severity levels that can be filtered are event, fault, and recovery. Table 2-3 lists the meanings of each bit of the alarm category filter condition. If a bit is set to 0, it indicates that the alarms of the corresponding alarm category are reported. If a bit is set to 1, it indicates that the alarms of the corresponding alarm category are filtered out. Table 2-3 Alarm category filter Condition Most Significant Bit (MSB) Event Fault Least Significant Bit (LSB) Recovery
----End
Example
The IP address of the upper-layer OSS is set to 10.70.73.159 and the serial number of the port for receiving alarms is set to 161. To report only the critical and major alarms and filter out the minor and warning alarms, you need to set the MIB node to 10.70.73.159:161:0011.
2.2.2 Synchronizing Alarms

Fault alarm synchronization is a process in which the alarms are queried by the third party NMS so that the alarms are consistent between upper NMS and EMS.
Context
NMS can specify the time interval for alarm synchronization. This function adopts SNMP Trap or Inform mode depending upon the configuration done in the snmp_agent_svc.xml file.
NOTE
l l
The following MIB nodes are exposed. Node Name hwNmNorthboundEventSynchronizationCommandStart hwNmNorthboundEventSynchronizationCommandStop OID 1.3.6.1.4.1.2011.2.15.1.7.7.4 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 and End 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 l l l
YYYY: Four digit year. The range of values is 1970 onwards. MM: Two digit month. The range of values is 01-12. DD: Two digit date. The range of values is 01-31. hh: Two digit hour. The range of value is 00-23.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-5
Issue 01 (2010-05-18)
l l
mm: Two digit minutes. The range of values is 00-59. 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 the following 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 user sends 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 synchronization is to be stopped The SNMP alarm Northbound Interface sends a notification to the NMS which contains the result of synchronization. 1. 2. 3. Alarm synchronization has been successfully ended. Alarm synchronization is stopped by the NMS command. Error has occurred during the alarm synchronization.
NOTE
l l l
If End Time is not present, the current system time of the EMS is treated as the End Time. If both are not present all the active alarms are queried. If End Time is present Start Time is mandatory.
----End
2.2.3 Acknowledging Alarms

NMS can acknowledge alarms based on the alarm serial numbers.
Context
Table 2-4 shows the MIB node. Table 2-4 MIB Node Details - Acknowledging Alarms Node Name hwNmAcknowledgeAlarms OID 1.3.6.1.4.1.2011.2.15.1.3.7
Procedure
l Set the MIB node with alarm serial number NMS sets the above mentioned node with the serial number of the alarm to be acknowledged. To acknowledge multiple alarms, NMS sets the node with all the serial numbers, separated by a comma. Ack User field in U2000 client is set as SNMP Agent User when an alarm is acknowledged by 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 1 2 3 4 Alarm State Unacknowledg e and Unclear Unacknowledg e and Clear Acknowledge and Unclear Acknowledge and Clear State Change Acknowledge and Unclear Acknowledge and Clear Acknowledge and Unclear NA SET Response Success Success Success Success Failed List Empty Empty Empty Alarm Serial Numbers
Issue 01 (2010-05-18)
2-7
NOTE
The GET operation is not supported on this MIB node.
----End
2.2.4 Unacknowledging Alarms

NMS 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 hwNmUnAcknowledgeAlarms OID 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, separated by a comma. Invalid or non-existent alarm serial numbers list is returned as failed to unacknowledge. 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-7 shows the change in state when alarms are unacknowledged. Table 2-7 Alarm states - Unacknowledge Alarms Sl.No 1 2 3 Alarm State Unacknowledge and Unclear Unacknowledge and Clear Acknowledge and Unclear State Change Unacknowledge and Unclear Unacknowledge and Clear Unacknowledge and Unclear SET Response Success Success Success Failed List Empty Empty Empty
2-8
Issue 01 (2010-05-18)
Sl.No 4
Alarm State Acknowledge and Clear
State Change NA
SET Response Success
Failed List Alarm Serial Numbers
NOTE
GET operation is not supported on this MIB node.
----End
2.2.5 Clearing Alarms

NMS 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 hwNmClearAlarms OID 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 by the SNMP Agent. Invalid or non-existent alarm serial numbers list is returned as failed to clear. 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-9 shows the change in state when alarms are cleared.
Issue 01 (2010-05-18)
2-9
Table 2-9 Alarm states - Clear Alarms Sl.No 1 2 3 4 Alarm State Unacknowledge and Unclear Unacknowledge and Clear Acknowledge and Unclear Acknowledge and Clear State Change Unacknowledge and Clear Unacknowledge and Clear Acknowledge and Clear NA SET Response Success Success Success Success Failed List Empty Empty Empty Alarm Serial Numbers
NOTE
GET operation is not supported on this MIB node.
----End
2.3 Alarm handshaking and Caching

Real time alarms are sent through Inform to the third party NMS. When the NMS is down due to some failure at its side, real-time alarms are cached. When the failure is rectified, all the cached alarms are sent to the NMS in the order in which they were received from the EMS.
Context
Figure 2-2 shows the procedure of caching alarms.
2-10
Issue 01 (2010-05-18)
Figure 2-2 Caching Alarms

start
Set Cache Features, Timeout, Retries and Cache Size
New Real Time Alarm
NMS Down
Yes
Cache Alarms
Report Alarms
Yes
NMS Up
No End
2.4 Traps
This chapter introduces the trap configuration information of the SNMP Northbound Interface. 2.4.1 Overview This section describes the traps which the SNMP Northbound Interface provides for the NMS. 2.4.2 Active Alarm Trap This section describes how the U2000 system sends real-time alarms to the NMS. 2.4.3 Alarm Query Start Trap This section describes the alarm query start trap including the prerequisites and trap definition. 2.4.4 Alarm Query Stop Trap This section describes about the alarm query stop trap including prerequisites and trap definition. 2.4.5 KeepAlive Info This section describes about the Keep Alive info, prerequisites, trap definition and field list.
2.4.1 Overview
This section describes the traps which the SNMP Northbound Interface provides for the NMS. The trap names are given below:
l l
Active alarm trap: hwNmNorthboundEventSynchronization Active alarm query start trap: hwNmNorthboundEventSynchronizationCommandStart Active alarm query stop trap: hwNmNorthboundEventSynchronizationCommandStop KeepAlive Info trap: hwNmNorthboundEventKeepAliveInfo
l l
2.4.2 Active Alarm Trap

This section describes how the U2000 system sends real-time alarms to the NMS.
Description
This section describes the purpose of the alarm trap.
Prerequisites
If an alarm occurs to an NE or the U2000, U2000 sends the alarm trap to the NMS.
Field List
In the following table , by default, the field types are those used for the connection with SNMPv1. For SNMPv2c or SNMPv3, the same data types will not be introduced again. Different data types are remarked in brackets. Table 2-10 Fields of hwNmNorthboundEventNotify TRAP-TYPE table Name hwNmNorthbo undNEName hwNmNorthbo undNEType hwNmNorthbo undObjectInstance OID 1.3.6.1.4.1.2011 .2.15.1.7.1.1 1.3.6.1.4.1.2011 .2.15.1.7.1.2 1.3.6.1.4.1.2011 .2.15.1.7.1.3 Type Octet string Description The name of network element. The device type of element. The instance of element are as follows number of
l l l l l
Example otm460
Octet string Octet string
WDM_OTM
Rack Frame Slot Subslot Port
2-12
Issue 01 (2010-05-18)
Name hwNmNorthbo undEventType
OID 1.3.6.1.4.1.2011 .2.15.1.7.1.4
Type Octet string
Description The type of Event.

l
Example Equipment
Communicati on Environment Equipment Service Processerror Integrity Operational Physical SecurityServi ceO rMechanism TimeDomain 2009/09/05-03: 44:20
l l l l l l l l
hwNmNorthbo undEventTime
1.3.6.1.4.1.2011 .2.15.1.7.1.5
Octet string
Time at which the alarm was generated. The format is

l
Local Time (YYYY/ MM/DDhh:mm:ss) UTC Time (YYYY/ MM/DDhh:mm:ssZ) Local with Time Zone (YYYY/ MM/ DD:hh:mm:s s:hh:mm:TZ)
hwNmNorthbo undProbableCa use
1.3.6.1.4.1.2011 .2.15.1.7.1.6
Octet string
The probable cause of the alarm.
Issue 01 (2010-05-18)
2-13
Name hwNmNorthbo undSeverity
OID 1.3.6.1.4.1.2011 .2.15.1.7.1.7
Type Octet string
Description The level of Alarm. The levels are as follows:

l l l l l
Example Critical
Critical Major Minor Warning Indeterminat e
hwNmNorthbo undEventDetail hwNmNorthbo undAdditionalI nfo hwNmNorthbo undFaultFlag
1.3.6.1.4.1.2011 .2.15.1.7.1.8 1.3.6.1.4.1.2011 .2.15.1.7.1.9
Octet string
The Alarm ID and detail information. The additional information of device, such as Country, City. The flag which specifies whether the alarm is an event, fault or recovery.
l l l
Octet string
(zero-length)
1.3.6.1.4.1.2011 .2.15.1.7.1.10
Octet string
Fault
Event Fault Recovery
2-14
Issue 01 (2010-05-18)
Name hwNmNorthbo undFaultFuncti on
OID 1.3.6.1.4.1.2011 .2.15.1.7.1.11
Type Octet string
Description The function type of the alarm. It can be any one of the following values:
l l l l l l l l
Example
Power Environment Signal Relay Hardware Software Run Communicati on Service Processerror UNKNOWN _FU NC_TYPE 10.167.12.84 54
l l l
hwNmNorthbo undDeviceIP hwNmNorthbo undSerialNo hwNmNorthbo undProbableRepair hwNmNorthbo undResourceID s hwNmNorthbo undsAdditional VB1 hwNmNorthbo undsAdditional VB2 hwNmNorthbo undsAdditional VB3
1.3.6.1.4.1.2011 .2.15.1.7.1.12 1.3.6.1.4.1.2011 .2.15.1.7.1.13 1.3.6.1.4.1.2011 .2.15.1.7.1.14 1.3.6.1.4.1.2011 .2.15.1.7.1.15 1.3.6.1.4.1.2011 .2.15.1.7.1.16 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
IpAddress INTEGER
IP address of the device. The serial number of alarm. Alarm repair recommendatio ns. The ID of resource. The additional information of the alarm. The additional information of the alarm. The additional information of the alarm.
Octet string
ID: 187,DeviceTyp e:1891 4063233.31457 28.1.196609.61. 1.1.-1
Octet string
Octet string
Octet string
Octet string
Issue 01 (2010-05-18)
2-15
Name hwNmNorthbo undsAdditional VB4 hwNmNorthbo undsAdditional VB5 hwNmNorthbo undsAdditional VB6 hwNmNorthbo undsAdditional VB7 hwNmNorthbo undsAdditional VB8 hwNmNorthbo undEventName
OID 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 1.3.6.1.4.1.2011 .2.15.1.7.1.24
Type Octet string
Description The additional information of the alarm. The additional information of the alarm. The additional information of the alarm. The additional information of the alarm. The additional information of the alarm. The name of event.
Example
Octet string
Octet string
Octet string
Octet string
Octet string
ID: 187,DeviceTyp e: 1891,CHAN_L OS
NOTE
The 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 without changing the agent. Only snmp_agent_svc.xml needs to be changed. They do not have its own OID and use fixed OID assigned to additional information. They will use OID according to their order in the additional vbs.
NOTE
l l
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).
The maximum number of count of additional VBs is eight. Only the first 8 additional VBs will be 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 each time. To configure the values for each additional VB which maps to the array index of the Paras parameter, is sent in FM alarm structure. The datatype of the additional VBs is Octect string. If the value configured in the snmp_agent_svc.xml file does not match with the array index of the Paras parameter, null will be reported to the NMS.
2.4.3 Alarm Query Start Trap

This section describes the alarm query start trap including the prerequisites and trap definition.
Description
The U2000 notifies the NMS of the start of the query. After the NMS receives the active alarm query start trap, the query starts. The hwNmNorthboundEventSynchronizationCommandStart node is to be set to start the alarm synchronization. This node is set as NMS IP: port: start time: end time. The syntax for Start and End time is YYYYMMDDhhmmss.
Prerequisites
The NMS triggers the query.
Trap Definition
The following table describes the trap definition: Table 2-11 Trap Definition of Alarm Query Start Trap Name hwNmNorthboundEventSynchronizationCommandStart OID 1.3.6.1.4.1.2011.2.15.1.7.7.4
Field List
None
2.4.4 Alarm Query Stop Trap

This section describes about the alarm query stop trap including prerequisites and trap definition.
Description
The U2000 notifies the NMS of the stop of the query. After the NMS receives the active alarm query stop trap, it indicates that the query ends.
"hwNmNorthboundEventSynchronizationCommandStop" node sets to stop the alarm synchronization. This node sets as NMS's IP: port and the agent stops alarm synchronization for the 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 hwNmNorthboundEventSynchronizationCommandStop OID 1.3.6.1.4.1.2011.2.15.1.7.7.5
Field List
None
2.4.5 KeepAlive Info

This 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 the trap, the connection between the NMS and the U2000 works. If the NMS does not receive the trap in this period and the heartbeat is enabled, it indicates that the NMS disconnects with the U2000.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 hwNmNorthboundEventKeepAliveInfo OID 1.3.6.1.4.1.2011.2.15.1.7.2
2-18
Issue 01 (2010-05-18)
Field List
In the following table, by default, the field types are those used for the connection with SNMPv1. For SNMPv2c or SNMPv3, the same data types will not be introduced again. Different data types are remarked in brackets. Table 2-14 Filed List Name hwNmNorthboundEventKeepAliveInfo OID 1.3.6.1.4.1.2011.2.1 5.1.7.2 Type Trap Description Notification for the Keep Alive traps.
Issue 01 (2010-05-18)
2-19
3 Deploying and Configuring SNMP
Deploying and Configuring SNMP
About This Chapter

This chapter describes how to deploy and configure the U2000 SNMP NBI. It includes the following information: 3.1 Overview This topic describes the background information and the terms involved in the process of deploying and configuring the northbound interface. 3.2 Configuration Requirements U2000 SNMP NBI and the U2000 server run on the same PC or Sun workstation, any additional configuration is not required. But to enable the SNMP NBI, you must purchase the license for the corresponding functions. 3.3 Logging in to the Client of the NMS Maintenance Suite After you log in to the client of the NMS Maintenance Suite, you can maintain the U2000 by using the NMS Maintenance Suite, including deploying the U2000 and configuring the instance of the northbound interface. 3.4 Checking the SNMP NBI Status After check the license and ensure it is support SNMP functions, you need to check the current status of SNMP NBI, and deploy the SNMP NBI according the status. 3.5 Deploying the SNMP NBI for the First Time By default, the SNMP NBI is not installed during the installation of U2000 server. To enable the SNMP NBI, you need to add the SNMP NBI the SNMP NBI component first, then add the SNMP NBI instance. 3.6 Configuring the SNMP NBI In order to enable the SNMP NBI, even though you have installed SNMP NBI component, you need configure the SNMP parameters accord to NMS planning. Also, you can modify the parameters 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 item is independence and you need not set the parameters in sequence. 3.7 SNMP Configuration Parameters
Issue 01 (2010-05-18)
3-1
You can ensure that the connection between the U2000 and the upper layer NMS is normal by correctly configuring basic parameters in the deployment tool. You can also configure advanced parameters for customizing the messages queried or reported through the SNMP interface.
3-2
Issue 01 (2010-05-18)
3.1 Overview
This topic describes the background information and the terms involved in the process of deploying and configuring the northbound interface.
Attention Item
l
Northbound interface is an optional component of the U2000. A license is required for using this function. If you do not install the northbound interface component during the installation of the U2000, you need to add it manually. The northbound interface is a System single-instance deployment package. Therefore, only one instance can be deployed.
CAUTION
l
After the northbound interface component is installed or added, you need to add a corresponding instance and configure parameters. Then, the U2000 can start the NBI-related process. After initializing the database of the U2000, you need to configure the northbound interface instance again. After the northbound interface instance is configured, you need to restart all the NMS services.
Terms
The following explains certain confusable terms:
l
Component: It is the software function unit that can be selected for installation. A component can consist of multiple deployment packages. 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 Suite

Through the GUI of the NMS maintenance tool, you can conveniently deploy the northbound interface.
The NMS Maintenance Suite is a graphical system maintenance tool that is developed for the iManager U2000. The NMS Maintenance Suite is used to deploy the instances and distributed system of the U2000. Refer to the NMS Maintenance Suite part of the iManager U2000 Administrator Guide for the details about the NMS Maintenance Suite.
3.2 Configuration Requirements

U2000 SNMP NBI and the U2000 server run on the same PC or Sun workstation, any additional configuration is not required. But to enable the SNMP NBI, you must purchase the license for the corresponding functions.
NOTE
For different operation system, the configuration requirements of U2000 is different, refer to the corresponding Software Installation Guide for more information.
Hardware Configuration
In practice, the U2000 SNMP interface and the U2000 server run on the same PC or SUN workstation. The hardware should be well configured enough to ensure the proper installation and running of the U2000 server. Any additional hardware configuration is not required the U2000 SNMP interface. For details of hardware requirements of U2000 Server, refer to section Configuration Requirements in the iManager U2000 Software Installation Guide.
Software Configuration
The function of U2000 SNMP interface is implemented based on the ORB technology of the SNMP. Since the the SNMP is integrated into the U2000 installation software, no additional software configuration is required for the installation of the U2000SNMP interface. For details of software requirements U2000 Server, refer to section Configuration Requirements in the iManager U2000 Software Installation Guide.
License
The U2000 controls the functions and available resources of the CORBA NBI through a license. If you want to enable the CORBA interface, you need to purchase the U2000 license. Ensure the license support CORBA interface function before deploying the CORBA NBI. For details, see A Relations Between License and SNMP Interface. If the license does not support the functions or resources needed, contact Huawei engineers to apply for the license. For the license introduction and information on how to apply for a license, see section Applying for and Updating the License in the iManager U2000 Administrator Guide.
3.3 Logging in to the Client of the NMS Maintenance Suite

After you log in to the client of the NMS Maintenance Suite, you can maintain the U2000 by using the NMS Maintenance Suite, including deploying the U2000 and configuring the instance of the northbound interface.
Prerequisite
l l
The server of the NMS Maintenance Suite must be started. The client and the server of the NMS Maintenance Suite must communicate with each other normally.
Context
In normal cases, the NMS Maintenance Suite server starts along with the OS. You can do as follows to check whether the NMS Maintenance Suite server is started:
l
In the Windows OS, check whether the msdaemon.exe and msserver.exe processes are started in the Task Manager window. If you can find the two processes in the process list, it indicates that the NMS Maintenance Suite server is started. Otherwise, open the DOS window and run the following command to start the NMS Maintenance Suite server:
> net start nodemgr
In the Solaris or SUSE Linux OS, run the following command as the root user to check whether 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 Maintenance Suite server is started. Otherwise, run the following commands to start the NMS Maintenance Suite server:
# cd /opt/HWENGR/engineering # ./startserver.sh
Procedure
Step 1 On a computer installed with the NMS Maintenance Suite client, double-click the U2000 MSuite shortcut icon on the desktop and then wait about one minute. The Login dialog box is displayed.
NOTE
l l
In the Solaris OS, you must log in to the Java desktop system as the root user. Otherwise, the U2000 MSuite shortcut icon is not displayed on the desktop. In the SUSE Linux OS, you cannot log in to the NMS Maintenance Suite client through the shortcut icon. You need to run the following commands as the root user to start the NMS Maintenance Suite client:
# 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 Maintenance Suite server resides. In a distributed system, you need to enter the system IP address of the master server. Port No.: The default port number is 12212. You do not need to change the default value during login. User Name: The default user name is admin. Password: The initial password is admin.
l l
Step 3 Click OK.
Issue 01 (2010-05-18)
3-5

NOTE
l l
When you log in to the client of the NMS Maintenance Suite, a progress bar showing the progress of querying components and instances is displayed. In this case, wait until the operation is complete. The NMS Maintenance Suite works in single-user mode. That is, only one NMS Maintenance Suite client can log in to the NMS Maintenance Suite server at one time. In a high availability system, only one site can be logged in at one time.
----End
Result
If a dialog box is displayed during the login, indicating that network configuration information is inconsistent and re-synchronization is required after login, read through the message to learn the server that needs to be synchronized. Then, do as follows: 1. 2. On the NMS Maintenance Suite client, click the Server tab. Right-click the server whose network configuration needs to be synchronized, and choose Synchronize the network configuration from the shortcut menu. A dialog box is displayed for you to confirm the operation. Click OK.
3.
3.4 Checking the SNMP NBI Status

After check the license and ensure it is support SNMP functions, you need to check the current status of SNMP NBI, and deploy the SNMP NBI according the status.
Context
The SNMP NBI is one of the components of U2000. The installation of the SNMP NBI is integrated in the process of installing the U2000 server. There are two cases of the installation.
l
If the SNMP NBI is not installed during the installation of the U2000 server, to enable the interface, you need to add the component first and then add the instance. For details, see 3.5 Deploying the SNMP NBI for the First Time. If the SNMP NBI is installed during the installation of the U2000 server, to enable the interface, you need to configure the instance. For details, see 3.6 Configuring the SNMP NBI.
The details for how to install the U2000 Server, refer to iManager U2000 Software Installation Guide. If you want to install SNMP NBI, ensure you have select Northbound SNMP Interface component during the installation of the U2000 server.
Procedure
Step 1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Client of the NMS Maintenance Suite. Step 2 Click Instance tab, check whether the AgentSNMP exist in the instance list. l l If the AgentSNMP instance exist, refer the steps in 3.6 Configuring the SNMP NBI to enable the SNMP NBI. If the AgentSNMP instance not exist, you need to check whether the SNMP NBI deployment package exist according to the Step 3.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-18)
3-6
Step 3 Click Deployment Package tabs, check whether the SNMP NBI exist in the deployment package list. l 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. 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 Time

By default, the SNMP NBI is not installed during the installation of U2000 server. To enable the SNMP NBI, you need to add the SNMP NBI the SNMP NBI component first, then add the SNMP NBI instance. 3.5.1 Adding SNMP NBI Component The SNMP NBI is one components of the U2000. If you have not installed the SNMP NBI by default, you need to add the SNMP NBI component. 3.5.2 Adding the SNMP NBI Instance The type of SNMP NBI deployment package is system single-instance, you can deploy one instance only. After adding the SNMP NBI component, you need to adding SNMP NBI instance to enable the SNMP interface. You need set the general parameters, and it is recommended you set the advanced parameters to default value.
3.5.1 Adding SNMP NBI Component

The SNMP NBI is one components of the U2000. If you have not installed the SNMP NBI by default, you need to add the SNMP NBI component.
Prerequisite
l
The NMS Maintenance Suite server installed on the master and slave servers must be started. The System Monitor server of the U2000 must be started. The Database server process must be in the Running state. The NMS Maintenance Suite client communicates with the NMS Maintenance Suite server in the normal state.
l l l
Context
l
In a distributed system, you only need to log in to the NMS maintenance tool server of the master server to perform this operation. In a high availability system, you only need to log in to the NMS maintenance tool server of the primary site to perform this operation.
Procedure
Step 1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Client of the NMS Maintenance Suite.
Step 2 On the NMS Maintenance Suite client, choose Deploy > Add Component. The Add Component dialog box is displayed.
CAUTION
l l
In the distributed system, the SNMP NBI could be deployed in master server only. You can add one SNMP NBI component only.
Step 3 Choose the Northbound SNMP Interface component and click OK, the progress bar is displayed. Step 4 Wait until the dialog box is displayed to prompt the message The component is successfully added. 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 enable the SNMP interface.
3.5.2 Adding the SNMP NBI Instance

The type of SNMP NBI deployment package is system single-instance, you can deploy one instance only. After adding the SNMP NBI component, you need to adding SNMP NBI instance to enable the SNMP interface. You need set the general parameters, and it is recommended you set the advanced parameters to default value.
Prerequisite
l
The NMS Maintenance Suite server installed on the master and slave servers must be started. The System Monitor server of the U2000 must be started. Database Server Process must be in the Enable state. The NMS Maintenance Suite client must communicate with the NMS Maintenance Suite server in the normal state. The component to which the instance is added must be installed. If the component is not installed, you must add SNMP NBI component first.
l l l
Context
l
3-8
Procedure
Step 1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Client of the NMS Maintenance Suite. Step 2 On the NMS Maintenance Suite client, click the Deployment Package tab. Right-click the northbound SNMP interface deployment package and choose Add Instance. The dialog box is displayed. Step 3 In the General tab, choose the items in the left object tree, configure the basic project parameters of 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 SNMP Configuration Parameters to set parameters.
Issue 01 (2010-05-18)
3-9

l l l l l l
Heartbeat Settings Alarm Field Settings Set reporting notification Report Date Format Settings Other Settings 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 address of the master server to deploy SNMP NBI, and this IP address is not in the relevant address droplist, the Address for Standby Server dialog box is displayed. 1. Enter the IP address of the SNMP NBI on the standby server.
CAUTION
l l
The SNMP service can deploy in the primary server only. You can enter any IP address of the standby server (except 127.0.0.1). But you must ensure that the input IP address is correct. That is, the standby server should be able to communicate with the upper-layer NMS successfully with the input IP address. The CORBA NBI searches for the IP configuration list (hosts file) of the computer automatically. Additionally, the first IP address in the configuration list is bound to the Naming service host address and Notify service host address. In the case of a single IP address, you need not set the Naming service host address and Notify service host address. In the case of multiple IP addresses, you need to set these fields because the bound IP address is unknown. When setting theses fields, you need to set them to IP addresses that the upper-layer NMS can have access to. Receive Request from NMS address is mandatory, Send Trap address is optional, the two parameters can be different.
3-10
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, the SNMP NBI is enabled successfully.
----End
3.6 Configuring the SNMP NBI

In order to enable the SNMP NBI, even though you have installed SNMP NBI component, you need configure the SNMP parameters accord to NMS planning. Also, you can modify the parameters 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 item is independence and you need not set the parameters in sequence.
Prerequisite
l l l l
Log in to the Solaris or SUSE Linux OS as the root user. Log in to the Windows OS as the Administrator user. In a HA system, configure the SNMP interface on the active server. The NMS Maintenance Suite server installed on the master and slave servers must be started. The System Monitor server of the U2000 must be started.
Issue 01 (2010-05-18)

l l
The Database server process must be in the Enabled state. The NMS Maintenance Suite client communicates with the NMS Maintenance Suite server in the normal state. The SNMP NBI instance must be added. Otherwise, add the related SNMP NBI instance first.
Context
l
Procedure
Step 1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Client of the NMS Maintenance Suite. Step 2 On the NMS Maintenance Suite client, choose NBI > Configure the SNMP interface instance 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 parameters of 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 SNMP Configuration Parameters to set parameters.
3-12
Issue 01 (2010-05-18)
l l l l l l
Heartbeat Settings Alarm Field Settings Set reporting notification Report Date Format Settings Other Settings 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 address of the master server to deploy SNMP NBI, and this IP address is not in the relevant address droplist, the Address for Standby Server dialog box is displayed. 1. Enter the IP address of the SNMP NBI on the standby server.
Issue 01 (2010-05-18)
3-13
CAUTION
l l
The SNMP service can deploy in the primary server only. You can enter any IP address of the standby server (except 127.0.0.1). But you must ensure that the input IP address is correct. That is, the standby server should be able to communicate with the upper-layer NMS successfully with the input IP address. The CORBA NBI searches for the IP configuration list (hosts file) of the computer automatically. Additionally, the first IP address in the configuration list is bound to the Naming service host address and Notify service host address. In the case of a single IP address, you need not set the Naming service host address and Notify service host address. In the case of multiple IP addresses, you need to set these fields because the bound IP address is unknown. When setting theses fields, you need to set them to IP addresses that the upper-layer NMS can have access to. 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, the SNMP NBI is enabled successfully.
----End
3-14
Issue 01 (2010-05-18)
3.7 SNMP Configuration Parameters

You can ensure that the connection between the U2000 and the upper layer NMS is normal by correctly configuring basic parameters in the deployment tool. You can also configure advanced parameters for customizing the messages queried or reported through the SNMP interface. Tab General Configuration Item
l l
SNMP Agent Third-Party NMS Heartbeat Settings Alarm Field Settings Set reporting notification Parameter Report Date Format Settings Other Settings MIB Frame Setting
Advanced
l l l l l l
Basic Project
To use the SNMP NBI, you need to correctly configure the trap, community, and the IP address and port of the upper layer NMS. To use the SNMP V3 protocol for communication, you need to correctly configure the parameters of the SNMP V3 protocol.
WARNING
l
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. 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 security level is no authentication and no encryption. The passwords of the authorization authentication protocol and the data encryption protocol are all null. When changing a password, you must enter the correct password set last time for confirmation. In addition, you are not allowed to set a new password to null.
Table 3-1 SNMP Agent parameters Parameter Basic Project

Description
Value
Parameter Send Trap address
Description Specifies the IP address on the SNMP agent for sending traps to the upper layer NMS. Specifies the port for sending traps.
Value IP addresses except 127.0.0.1 Default: IP address of the U2000 server. 1-65535 Default: null. Recommended value: greater than 1024.
Port
Receive Request from NMS address
Specifies the IP address for receiving requests from the upper layer NMS. Specifies the port for receiving requests from the upper layer NMS.
IP addresses except 127.0.0.1 Default: IP address of the U2000 server. 1-65535 Default: null. Recommended value: greater than 1024.
l l l
Port
SNMP version
The SNMP NBIU2000 support three version of protocol: SNMP v1, v2c and v3.
v1 v2c v3
Default: v1. SNMP v3 Para Settings Security Model Security Level Specifies the security model of the SNMP V3 protocol. Specifies the security level of the SNMP V3 protocol. USM model
l
No Authentication and No Privacy Authentication and No Privacy Authentication and Privacy NONE HMACMD5 HMACSHA NONE DES AES
Authentication
Specifies the authentication protocol used by the SNMP V3 protocol. Specifies the encryption protocol used by the SNMP V3 protocol.
l l l
Data Encryption
l l l
3-16
Issue 01 (2010-05-18)
Third-Party NMS
To send messages to the third-party NMS through the SNMP NBI, you need to correctly configure the parameters of the third-party NMS, such as trap information and heartbeat information.
WARNING
The NMS Receive Trap Address is not the IP address of the U2000 server.
Table 3-2 Third-party NMS parameters Parameter NMS Receive Trap Address Port Description Specifies the IP address of the third-party NMS. Specifies the port of the thirdparty NMS for receiving traps. When the third-party NMS uses the SNMP V1 or V2c protocol, the authentication control between the SNMP agent and the upper layer NMS is implemented through community information. To be specific, only when the set community is the same as that of the upper layer NMS, the thirdparty NMS can respond to the alarm query requests received. Otherwise, the third-party NMS ignores the requests.
NOTE The SNMP agent supports a maximum of 10 read/write communities.
Value IP address 1~65535 Default: 9831. The default read/write community is public. You can also enter any character string consisting of 255 characters at most.
Read Community
Issue 01 (2010-05-18)
3-17
Parameter Write Community
Description When the third-party NMS uses the SNMP V1 or V2c protocol, the authentication control between the SNMP agent and the upper layer NMS is implemented through community information. To be specific, only when the set community is the same as that of the upper layer NMS, the thirdparty NMS can respond to the alarm query requests received. Otherwise, the third-party NMS ignores the requests.
NOTE The SNMP agent supports a maximum of 10 read/write communities.
Value The default read/write community is public. You can also enter any character string consisting of 255 characters at most.
V3 User Name
Specifies the user name used by the third-party NMS to communicate wit AgentSNMP through the SNMP V3 protocol. Specifies the user password of the upper layer NMS for authentication. This password is used when the SNMP V3 authentication is enabled. If the security level is set to Authentication and Privacy, you must set encryption policy of the password.
l l
Character string (20) Default: SNMPAgent.
V3 Password Authentication
The default password is null.
V3 Password for Privacy
The default password is null.
Alarm Level
Specifies the alarm level. The All the items are selected. alarm level is classified into Critical, Major, Minor, and Warning. Specifies the category of reported alarms. The reported alarms are classified into Event Alarm and Fault Alarm. All the items are selected.
Alarm Category
3-18
Issue 01 (2010-05-18)
Heartbeat Settings
To receive heartbeat messages from the third-party NMS, you need to correctly configure heartbeat parameters. Table 3-3 Heartbeat parameters Parameter Heartbeat Period (not less than 15s) Description Specifies the heartbeat period of the third-party NMS. The value of this parameter is greater than or equal to a multiple of 15. There are multiple tabs, such as NMS 1 and NMS 2, in the window. Only when Required Heartbeat Info is set to Yes at least on one tab page, Heartbeat Period is valid. Value 15-600 s Default: 60 s.
Required Heartbeat Info
Yes, No Default: Yes.
Alarm Field Settings

You 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 NE Name NE Type Object Instance Description Indicates the NE name. Indicates the NE type. Indicates the location information. For U2000, this parameter indicates the alarm source and alarm location information. Value Character string (255) Character string (64) Character string (255)
Issue 01 (2010-05-18)
3-19
Field Event Type
Description Indicates the NMS classification, including:

l l l l l l
Value Character string (64)
Communication Environment Equipment Service Processing error Unknown_EventType
When the configuration item of SupportX. 733Alarm is set to 1, alarms are classified into the following types:
l l l l l l
communicationsAlarm environmentalAlarm equipmentAlarm qualityofServiceAlarm processingErrorAlarm Unknown_EventType Character string (64) Character string (255) Character string (64)
Alarm Rising Time Alarm Cause Alarm Severity
This parameter depends on the AlarmTimeFormat parameter. Indicates the cause of generating an alarm. Indicates the alarm level, including:
l l l l l l
Critical Major Minor Warning Indefinite Unknown_Severity
When the configuration item of SupportX. 733Alarm is set to 1, the alarm level Cleared is added. Alarm Details Alarm Location Indicates the alarm details. Indicates the location at which an alarm is generated. Character string (255) Character string (255)
3-20
Issue 01 (2010-05-18)
Field Type Flag
Description Indicates the alarm classification, including:

l l l l
Event Fault Recovery UNKNOWN_EVENT_TYPE Character string (64)
Alarm Function Category
Indicates the function classification, including: Power Environment Signal Relay Hardware Software Run Communication Indicates a power alarm. Indicates an environment alarm. Indicates a signaling alarm. Indicates a trunk alarm. Indicates a hardware alarm. Indicates a software alarm. Indicates a run alarm. Indicates communication failure. Indicates QoS. Indicates a processing error. Indicates the unknown alarm type.
Service Process error UNKNOWN_FUC_ TYPE Managed Equipment Address Alarm Serial Number Alarm Recovery Advice Resource ID
Indicates the NE IP address. Indicates the alarm serial number. Indicates the alarm recovery advice. Indicates the resource ID.
IP address Integer Character string (255) Character string (255)
Issue 01 (2010-05-18)
3-21
Field Event Name Alarm Reason ID Alarm ID Managed Equipment Type
Description Indicates the alarm name. Indicates the alarm cause ID. Indicates the alarm ID. Indicates the managed equipment type.
Value Character string (255) Character string (255) Character string (255) Character string (255)
Set reporting notification

The upper layer NMS obtains alarm information through the SNMP agent in two ways: active reporting and active query. You can set the mode for sending alarms through the deployment tool and set parameters for different alarm obtaining modes.
WARNING
l
Trap (passive reporting) : The SNMP agent reports alarms only after receiving a request from the upper layer NMS. 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 agent tries connecting to the upper layer NMS for many times. This will occupy a large number of resources. As a result, the efficiency of the SNMP agent is reduced. Therefore, exercise caution when you set this parameter to Inform.
Table 3-5 Parameters of reported notification Parameter Reporting Mode Description Specifies the mode used by the SNMP agent for sending alarms to the upper layer NMS. Value
l l l
Trap Inform Default Value: Trap
3-22
Issue 01 (2010-05-18)
Parameter Support X733 Alarm
Description Specifies whether traps use the event types and levels defined in X.733.
l
Value
l l
Yes, No No
Yes indicates that the X. 733 format is used. No indicates that the X. 733 format is not used.
NOTE X.733 is an alarm reporting function. This function helps users to send and clear alarms.
Trap Transmit Interval
Specifies the time interval of sending messages in Trap mode. Specifies the delay of sending messages in Inform mode. Specifies the retry times of connections in the case of a failure in Inform mode.
l l
1 ms-1000 ms. Default: 40. 5s-120s. Default: 5. 2 times-6 times. Default: 3.
Inform Delay
l l
Inform Failure Retry
l l
Report Date Format Settings

This parameter specifies the format of reported time of an alarm. Table 3-6 Parameters of the format of reported time Parameter Alarm Date Format Settings Description Alarm time can be recorded. Value
l
Local Time (without Time Zone) UTC Time Local Time (with Time Zone)
l l
Default Value: UTC Time
Other Settings
This parameter specifies whether alarms are recorded in logs. In addition, this parameter specifies the alarm encoding format and the cache for real-time alarms.
Issue 01 (2010-05-18)
3-23
Table 3-7 Other Settings Parameter Record Log Alarm Character Encode Description Specifies whether alarms are recorded in logs. The alarm encoding format is as follows: Value No
l l
GBK UTF-8
UTF-8 Real-time Alarm Cache Size Specifies the cache for realtime alarms. The maximum value is 50000 and the minimum value is 0. Each upper layer NMS user is assigned with an independent cache.
l l
0-50000 Default Value: 10000
MIB Frame Setting

The U2000 provides two types of MIBs and three specifications. You can select the required type to load.
NOTE
For the details of T2000 old MIB, U2000 MIB with old specification and new specification, see B Description of the Alarms Reported by the SNMP Interface.
Table 3-8 Parameters of the MIB frame Parameter MIB Description Set the MIB type to be loaded. Default: Use the U2000 MIB with old specification Custom-made: Use the MIB of the T2000 V200R006C03 or prior version You can select the New spec check box to enable the new specification. Otherwise use the old one. You need choose the MIB type according the requirement. Resource information of orientation Set the format of the alarm reporting of SNMP interface.
l l
Value
l l
Default Custom-made
Default, FDN Default Value: Default
3-24
Issue 01 (2010-05-18)
4 Deleting and Disabling an SNMP Interface
Deleting and Disabling an SNMP Interface
About This Chapter

This topic describes how to disable or delete an SNMP interface when the U2000 temporarily need not provide this interface to an external network. 4.1 Logging In to the System Monitor This topic describes how to log in to the System Monitor of the U2000. 4.2 Stopping the SNMP NBI You can use System Monitor to stopping the SNMP NBI. 4.3 Disabling the SNMP NBI By disabling the SNMP NBI, you can disable the SNMP interface service without deleting the SNMP interface instance. In this way, the SNMP interface process will not start with the U2000 when you start the U2000 next time. 4.4 Restarting the SNMP NBI When the SNMP interface process is in the stopped state, you can restart the process in the Sysmonitor client. 4.5 Deleting the SNMP NBI Instance You can delete an instance for the SNMP interface if it is not in use, which enhances the running efficiency of the U2000. 4.6 Deleting the SNMP NBI Component You can delete the component for the SNMP NBI if it is not in use, which enhances the running efficiency of the U2000.
Issue 01 (2010-05-18)
4-1
4.1 Logging In to the System Monitor

This topic describes how to log in to the System Monitor of the U2000.
Prerequisite
Before logging in to the System Monitor of the U2000, make sure that:
l l l l
The U2000 server runs in the normal state. The system monitoring process runs in the normal state. The System Monitor communicates well with the U2000 server. You have a valid user account and password of the U2000.
Context
You can start the System Monitor, connect the System Monitor to the U2000 server, and monitor the status of the U2000 server on the System Monitor. For details about the system monitoring, see section Monitoring the U2000 Processes in the iManager U2000 Administrator Guide.
Procedure
Step 1 Choose Start > Programs > U2000 Network Management System > U2000 System Monitor or double-click
NOTE
on the desktop to start the System Monitor.
On the Solaris or SUSE Linux OS, double-click the U2000 System Monitor shortcut icon on the Java Desktop System, Release 3 desktop.
Step 2 In the Login dialog box, enter the required user name and password to access the System Monitor window. Step 3 Click Login to log in to the System Monitor of the U2000. ----End
4.2 Stopping the SNMP NBI

You can use System Monitor to stopping the SNMP NBI.
Prerequisite
l l l l l
Log in to the Solaris or SUSE Linux OS as user nmsuser. Log in to the Windows OS as user Administrator. In a HA system, configure the SNMP interface on the active server. The U2000 must be operating. The SNMP Service processes are in the Running state.
4-2
Context
NOTE
After the SNMP interface instance is added through the NMS Maintenance Suite, the default start mode is Automatic. 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 is Stopped, it indicates that the operation is successful.
Issue 01 (2010-05-18)
4-3
----End
4.3 Disabling the SNMP NBI

By disabling the SNMP NBI, you can disable the SNMP interface service without deleting the SNMP interface instance. In this way, the SNMP interface process will not start with the U2000 when you start the U2000 next time.
Prerequisite
l l l l l
Log in to the Solaris or SUSE Linux OS as user nmsuser. Log in to the Windows OS as user Administrator. In a HA system, configure the SNMP interface on the active server. The U2000 must be operating. The SNMP Service processes is in the Stopped state.
Procedure
4-4
Issue 01 (2010-05-18)
Step 3 Select the SNMP Service process , right-click, and choose Startup Mode > Disable to disable the process. Step 4 On the System Monitor client, if Startup Mode of the related processes of the SNMP NBI is Disabled, it indicates that the operation is successful.
----End
4.4 Restarting the SNMP NBI

When the SNMP interface process is in the stopped state, you can restart the process in the Sysmonitor client.
Prerequisite
l l l l l
Log in to the Solaris or SUSE Linux OS as user nmsuser. Log in to the Windows OS as user Administrator. In a HA system, configure the SNMP interface on the active server. The U2000 must be operating. 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 the shortcut menu. Step 4 In the System Monitor client, when Status of the relevant XML processes, namely SNMP Service are Running, the operation is successful.
4-6
Issue 01 (2010-05-18)
----End
4.5 Deleting the SNMP NBI Instance

You can delete an instance for the SNMP interface if it is not in use, which enhances the running efficiency of the U2000.
Prerequisite
l l l l
Log in to the Solaris or SUSE Linux OS as user root. Log in to the Windows OS as user Administrator. In a HA system, configure the SNMP interface on the active server. The NMS Maintenance Suite server installed on the master and slave servers must be started. The U2000 must be operating. The NMS Maintenance Suite client communicates with the NMS Maintenance Suite server in the normal state. It is recommended that you stop the SNMP NBI before delete the instance.
l l
Context
l
Issue 01 (2010-05-18)
4-7
Procedure
Step 1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Client of the NMS Maintenance Suite. Step 2 Click the Instance tab. Select the AgentSNMP instance from the instance list, right-click, and choose Delete Instance
Step 3 Click OK. After the confirmation, the NMS Maintenance Suite begins deleting the AgentSNMP instance. Step 4 Click the Deployment Package tab, if the Instance Count of the SNMP NBI deployment package is zero, that means the deletion success.
NOTE
After the AgentSNMP instance is deleted, the Sysmonitor does not display the information about the AgentSNMP process. If you need to re-enable the SNMP interface, refer to 3.5.2 Adding the SNMP NBI Instance.
----End
4.6 Deleting the SNMP NBI Component

You can delete the component for the SNMP NBI if it is not in use, which enhances the running efficiency of the U2000.
Prerequisite
l l l l
Log in to the Solaris or SUSE Linux OS as user root. Log in to the Windows OS as user Administrator. In a HA system, configure the SNMP interface on the active server. The NMS Maintenance Suite server installed on the master and slave servers must be started. The U2000 must be operating.
4-8

l
The NMS Maintenance Suite client communicates with the NMS Maintenance Suite server in the normal state. Ensure you have deleted the SNMP NBI instance.
Context
l
Procedure
Step 1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Client of the NMS Maintenance Suite. Step 2 On the NMS Maintenance Suite client, click Deployment Package tab, check whether the instance count of SNMP NBI deployment package is zero. l l If Instance Count is not zero, you need to deleted the SNMP NBI instance first. 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 is started.
NOTE
You can not delete the components which are basic or have not installed. You can not select them in the left 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 package not exist indicate that the operation is successful. ----End
Issue 01 (2010-05-18)
4-9
5 Maintaining the SNMP NBI
5
About This Chapter
Maintaining the SNMP NBI
This chapter introduces how to maintain the U2000 SNMP Northbound Interface. 5.1 Maintenance Description This section describes the basic requirement of maintenance SNMP NBI. 5.2 Faults and Solutions This section introduces the faults of the SNMP Northbound Interface and the related solutions.
Issue 01 (2010-05-18)
5-1
5.1 Maintenance Description

This section describes the basic requirement of maintenance SNMP NBI. To ensure that the U2000 SNMP Northbound Interface works well, there are some requirements as follows: 1. The maintenance personnel must be familiar with:
l l l
Windows or the Sun workstation - Solaris 8 or Solaris 10, and SuSe Linux 10 The SNMP protocol Basic concepts of the Telecommunication Management Network (TMN)
2. 3.
The PC or SUN workstation that is configured with the U2000 SNMP Northbound Interface runs normally. The U2000 Server runs normally.
5.2 Faults and Solutions

This 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 to access the U2000 system.
Possible Causes
l l
The listening port for the SNMP Agent is in use. 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. For details on port, refer to 3.7 SNMP Configuration Parameters.
5-2
Issue 01 (2010-05-18)
Step 2 Start the System Monitor. Check the dependent processes. If they are not started, you need to start them. Then, start the SNMP Agent. ----End
5.2.2 Fails to Receive Alarms

Symptom
You have added the address of the third-party NMS to the configuration file. However, the NMS fails to receive the alarms.
Possible Causes
After 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 IP address of the NMS, you need to restart the AgentSNMP. ----End
5.2.3 User Unable to Perform Certain Fault Operations

Symptom
Certain Fault operations are not supported due to the license feature provided by the SNMP Agent.
Possible Causes
l
In Windows, License information file, %IMAPROOT%\server\etc\conf\license \ONXXXXXXX.dat does not exist. In Solaris or SUSE Linux, License information file, $IMAPROOT/server/etc/conf/ license/ONXXXXXXX.dat does not exist. 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

Description
The NMS user could not connect to the SNMP Agent.
Possible Causes
The following parameters do not match with the data present in the configuration file.
l l l l l
Username Passwords for authentication and privacy SNMP version Security model (for SNMP V3) Encryption protocol (for SNMP V3) for Privacy (if enabled) and Authorization (if enabled)
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 match with the client. The security parameters in the trap receiver application does not match with the parameters configured in the configuration file.
Solutions
1. 2. Ensure that the configuration is correct. After changing configuration, restart the SNMP agent.
5.2.6 Attempt to Acknowledge or Un-acknowledge or Clear Alarms Fails

Description
Active Alarms cannot be acknowledged or unacknowledged or cleared.
Possible Causes
l l l
Invalid license. One or more dependent services are down. Version mismatch of the MIB file
5-4
Solutions
1. 2. 3. 4. Ensure that the license is valid. Ensure that the dependent services are functioning. Ensure that there is no version mismatch of the MIB file. After changing configuration, restart the SNMP agent.
Issue 01 (2010-05-18)
5-5
6 Accessing U2000 from NMS
6
Accessing U2000 by SNMPv1
1. 2. 3.
Accessing U2000 from NMS
This section describes about the various SNMP versions through which NMS can access U2000. 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 user mode.
For NMS to access U2000, ensure that: The U2000 administrator sets U2000 to support SNMPv1. The U2000 administrator configures community name, NMS IP address and port number, filter alarm category and alarm level. The NMS obtains IP address and port number (4700 by default) of the SNMP Northbound Interface from U2000 administrator.
Accessing U2000 by SNMPv2c

For NMS to access U2000, ensure that: 1. 2. 3. The U2000 administrator sets U2000 to support SNMPv2c. The U2000 administrator configures community name, NMS IP address and port number, filter alarm category and alarm level. The NMS obtains the IP address and port number (4700 by default) of the SNMP Northbound Interface from the U2000 administrator.
Accessing U2000 by SNMPv3

To enable NMS for access U2000, ensure that: 1. 2. 3. The U2000 administrator sets U2000 to support SNMPv3 by modifying the SNMP Northbound Interface configuration file. The U2000 administrator configures SNMPv3 user name, security level, authentication protocol, authentication password, and privacy password The U2000 administrator sets the SNMPv3 security levels. The U2000 administrator supports 3 security levels which includes:
Issue 01 (2010-05-18)
6 Accessing U2000 from NMS

l l l
No Authentication and No Privacy Authentication and No Privacy 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-2
Issue 01 (2010-05-18)
A Relations Between License and SNMP Interface
A
l l l l l
Relations Between License and SNMP Interface
This part introduces the relations between license and SNMP interface. The U2000 license controls the software of SNMP interface in the following four dimensions: Interface function Technical domain Management capacity Number of OSS connections The first three dimensions depend on each other. The U2000 divides the license according to the dimensions to dynamically control the SNMP software.
For details of Dimension, refer to Figure A-1 and Table A-1. Figure A-1 Main dimensions
em ag an M
en
a tC
y cit pa
technical domain
Interface Function
Issue 01 (2010-05-18)
A-1
Table A-1 Description for Dimension Dimension Interface function Meaning

l l l l l
Alarm and inventory Service provisioning and test diagnosis Performance Common Notification reporting Transport Router and Metro including security Access
Technical domain
l l l
Management capacity
Physical inventory: Controls NEs. The unit is number of equivalent NEs. Service inventory: Controls E2E services. The unit is number of services.
Number of OSS connections
Indicates the maximum number of OSS users that can be online concurrently.
On Solaris or SUSE Linux, view the license as user root. Use the text viewer to view the contents of the $IMAPROOT/server/etc/conf/license/ONXXXXXXX.dat file. On Windows, view the license as user administrator. Use the text viewer to view the contents of 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 of license control items. Table A-2 Description for License Item License Control Item License For NBI SNMP Connection Per Equivalent NE License for NBI-SNMP Alarm Transmission Network Per Equivalent NE License for NBI-SNMP Alarm -IP Per Narrowband Resource License for NBI-SNMP Alarm--Access Abbreviation LNSDPENES07 LNSDPENES01 Value 0-20000 0-300000
LNSDPENES02 LNSDPENEC21
0-300000 0-300000
A-2
Issue 01 (2010-05-18)
License Control Item Per Broadband Resource License for NBI-SNMP Alarm--Access
Abbreviation LNSDPENEC25
Value 0-300000
Issue 01 (2010-05-18)
A-3
B Description of the Alarms Reported by the SNMP Interface
Description of the Alarms Reported by the SNMP Interface
The Alarms Reported for U2000 MIB

The SNMP NBI support the U2000 MIB with two specifications. The new version have three more alarm section than the old one: Alarm Reason ID, Alarm ID and Managed Equipment Type. For more details to set this parameters, see MIB Frame Setting in 3.6 Configuring the SNMP NBI. Table B-1 The Alarms Reported for U2000 MIB Name NE Name NE Type Object instance Name in the MIB hwNmNorthboundNEName hwNmNorthboundNEType hwNmNorthboundObjectInstance Description NE name NE equipment type Orientation information The format is as source=NEType/ NEName location= Alarm Location Information For example, source=EMS/Local NM location=Partition=/ Server=LINUX-128 Value Character string (255) Character string (64) Character string (255)
Issue 01 (2010-05-18)
B-1
Name Event Type
Name in the MIB hwNmNorthboundE ventType
Description On the network management system, event types are classified as follows:
l l l l l l
Communication alarms Environment alarms Equipment alarms Service quality alarms Processing error alarms Unknown event type
When the SupportX.733Alarm configuration item is set to 1, event types are classified as follows:
l l l l l l
Communication alarms Environment alarms Equipment alarms Service quality alarms Processing error alarms Unknown event type Character string (64)
Alarm Rising Time
hwNmNorthboundE ventTime
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 UTC Time. The format is asYYYY/ MM/DD - hh:mm:ssZ. Example: 2009/12/23 - 11:30:30Z Local Time with timezone information. The format is as YYYY/ MM/DD - hh:mm:ss,hh:mmTZ [DST], where TZ stands for timezone information. Example:
2009/12/23 - 19:30:30,+08:00[0]. ( if the date is not in DST ) 2009/12/23 - 19:30:30 +08:00 [3600] . (if the date is in DST of 1 hr. The DST value is in seconds.) Character string
Alarm Cause
hwNmNorthboundProbableCause
Possible causes for an alarm
B-2
Issue 01 (2010-05-18)
Name Alarm Severity
Name in the MIB hwNmNorthboundSeverity
Description Severity level of an alarm. The severity levels of the alarms are as follows:
l l l l l l
Critical Major Minor Warning Indefinite Unknown severity
When the SupportX.733Alarm configuration item is set to 1, the Cleared severity level is added. Alarm Details Alarm Location Type Flag hwNmNorthboundE ventDetail hwNmNorthboundAdditionalInfo hwNmNorthboundFaultFlag ID, device type, and details of an alarm Detailed location of the equipment Alarm types are as follows:
l l l l
Character string (255) Character string (255) Character string (64)
Event Fault Recovery Unknown event type
Alarm Function Category
hwNmNorthboundFaultFunction
Function types are as follows:

l l l l l l l l l l l
Power alarms Environment alarms Signaling alarms Relay alarms Hardware alarms Software alarms Running alarms Communication faults Service quality alarms Processing error alarms Unknown type alarms
Character string (64)
Managed Equipment Address
hwNmNorthboundDeviceIP
IP address of the equipment
IP address
Issue 01 (2010-05-18)
B-3
Name Alarm Serial Number Alarm Recovery Advice Resource ID Event Name Alarm Reason ID Alarm ID Managed Equipment Type
Name in the MIB hwNmNorthboundSerialNo hwNmNorthboundProbableRepair hwNmNorthboundResourceIDs hwNmNorthboundE ventName hwNmNorthboundReasonID hwNmNorthboundFaultID hwNmNorthboundDeviceType
Description Serial number of an alarm
Value Integer
Advice for recovery
Character string Character string (255) Character string (255) Character string (255) Character string (255) Character string (255)
Resource ID Event name of an alarm Indicates the alarm cause ID. Indicates the alarm ID. Indicates the managed equipment type.
The Alarms Reported for T2000 of the old architecture MIB

In U2000 V100R002C01, SNMP alarms in old MIB (that is, T2000 V200R006C03 and prior versions) can be adapted. For more details to set this parameters, see MIB Frame Setting in 3.6 Configuring the SNMP NBI. Table B-2 The Alarms Reported for T2000 old MIB Name EMS Name Name in the MIB northboundReportAlarmEmsName Description NE name. The value is always Huawei/T2000. NE equipment type. For example, OptiX 2500+. Equipment name. For example, NE350. Value Character string (255)
Equipment Type
northboundReportAlarmManagedObjectClass northboundReportAlarmManagedObjectInstance
Equipment Name
B-4
Issue 01 (2010-05-18)
Name NE Name
Name in the MIB northboundReportAlarmNEName
Description NE name, which is consistent with the equipment name. For example, NE350.
Rack Name
northboundReportAlarmRackName
Rack name. The value is always 1. Subrack name. 1. In the WDM or OTN domain, an NE name is the name of an optical NE and a subrack name is the name of the subrack that is located in an optical NE. 2. In the SDH or other domain, an NE is a subrack. That is, an NE name and the subrack name are the same. For example, NE350.
Subrack Name
northboundReportAlarmShelfName
Physical Location of Equipment
northboundReportAlarmDevLocation
Physical location of equipment. The value is always null.
Board Name
northboundReportAlarmBoardName northboundReportAlarmPortType
Board name. For example, PQ1. Port type. For example, SDH_TU. Port number. For example, 1.
Character string (255) Character string (64)
Port Type
Port Number
northboundReportAlarmPortNumber
Integer (4)
Issue 01 (2010-05-18)
B-5
Name Location of an Alarm Object
Name in the MIB northboundReportAlarmLocation
Description Specific location of an alarm. For example, ne=590174/rack=1/ shelf=1/slot=5/ domain=sdh/port=1/ highPath=1/ lowPath=0/layer=5 The rules for assembling alarm location information for a PTN NE may be slightly different. For example, ne=3145796/rack=1/ shelf=1/slot=4/ domain=ptn/ type=physical/ port=1/ location1=260/ layer=15
Alarm Type
northboundReportAlarmEventType
Alarm type. The value can be any of the following: communicationsAlarm, qualityofServiceAlarm, equipmentAlarm, processingErrorAlarm, and environmentalAlarm.
Alarm Rising Time
northboundReportAlarmEventTime
Alarm rising time. For example, 2005-10-14,17:41:0 4.0. Alarm severity. The value can be any of the following: Critical, Major, Minor, Warning, cleared, and indeterminate.
Alarm Severity
northboundReportAlarmPerceivedSeverity
Possible Alarm Cause
northboundReportAlarmProbableCause
Possible alarm cause. For example, RAI.
B-6
Issue 01 (2010-05-18)
Name Alarm Cause
Name in the MIB northboundReportAlarmSpecificProblems
Description Alarm cause. For example, NE communication was lost Whether an alarm affects the service. The value can be 0 or 1. 0: The alarm does not affect the service. 1: The alarm affects the service.
Affect Service
northboundReportAlarmOperationAffected
Integer (4)
Alarm ID
northboundReportAlarmID northboundReportAlarmName
Alarm ID. For example, 93. Alarm name. For example, LP_RDI. Advice on fixing an alarm. The value is always null. IP address of the equipment where an alarm is generated. The value is always null.
Integer (4)
Alarm Name
Advice on Fixing an Alarm
northboundReportAlarmProposedRepairActions
IP Address of the Object for Alarm Rising
northboundReportAlarmIPAddress
Serial Number of an Alarm
northboundReportAlarmNotificationIdentifier northboundReportAlarmResourceID
Serial number of an alarm. For example, 109. ID of the resource where an alarm is generated. The value is always null.
long(8)
ID of the Resource for Alarm Rising
Integer (4)
Additional Information
northboundReportAlarmAdditionalText
Additional information. For example, Alarm Parameter II(hex) 0x02
Issue 01 (2010-05-18)
B-7
Name Clear Alarm
Name in the MIB northboundReportAlarmCleared
Description Whether to clear an alarm. The value can be 0 or 1. 0: Do not clear the alarm. 1: Clear the alarm.
Value Integer (4)
Serial Number of the Alarm to Be Cleared
northboundReportAlarmCorrelatedNotifications
Serial number of the alarm to be cleared. The value is the same as the value of the alarm serial number field. Additional information of an alarm. The value is the same as the value of the alarm rising time field.
Integer (4)
Additional Alarm Information (10 Fields)
northboundReportAlarmAdditionalVB
B-8
Issue 01 (2010-05-18)
C Sample
C
Automatic Alarm Reporting
Sample
5: 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 Synchronization

14: hwNmNorthboundEventSynchronizationStart.0.9 notification received from: 10.71.34.14 at 2010-1-26 15:13:30
Issue 01 (2010-05-18)
C-1
C Sample

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.9 15: 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 Synchronization

105: 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-2
Issue 01 (2010-05-18)
C Sample
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!
Heartbeat
3: 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
Issue 01 (2010-05-18)
C-3
D Acronyms and Abbreviations
D
E EMS I IP
Acronyms and Abbreviations
This part list the acronyms and abbreviations in this document.
Element Management System
Internet Protocol
M MC MIB Monitor Center Management Information Base
N NBI NE NMC NMS Northbound Interface Network Element Network Management Center Network Management System
P PDU Protocol Data Unit
S SOAP Simple Object Access Protocol
Issue 01 (2010-05-18)
D-1
D Acronyms and Abbreviations
SMI SNMP T TCP TMN
Structure of Management Information Simple Network Management Protocol
Transmission Control Protocol Telecommunication Management Network
V VB Variable Bindings
D-2
Issue 01 (2010-05-18)

Imanager U2000 Northbound SNMP Interface User Guide - (V100R002C01 - 01)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Imanager U2000 Northbound SNMP Interface User Guide - (V100R002C01 - 01)

Uploaded by

Copyright:

Available Formats

iManager U2000 Unified Network Management System V100R002C01

Northbound SNMP Interface User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

About This Document

Installation and Commissioning Engineer Data Configuration Engineer Application Developer

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document