012-NetNumen U31 R22 Northbound Interface User Guide (SNMP Interface)

NetNumen U31 R22
Unified Network Management System
Northbound Interface User

Guide (SNMP Interface)
Version: V12.11.40P01
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Document Version
Revision Date
Revision Reason
R1.1
2012-05-10
NetNumen U31 R22 (V12.11.40P01) Issued.

l
Added the "Manageable NEs" section.
Updated the "SNMP Management Frame", "Six Kinds of

Report Operations of SNMP", "Maintenance Operation
Description", "Checking the Communication Status Between
the Unified Northbound SNMP Interface and the Integrated
NMS", "Backing up System Logs", "Exceptional Running of
the Processes of the Unified Northbound SNMP Interface",
"Interconnection Failure Between Integrated NMS and
Northbound SNMP Interface" section.
Updated the "Configuring the Unified Northbound SNMP

Interface", "Interconnecting the Unified SNMP Interface With
the Integrated NMS", "OID List" chapter.
R1.0
2012-02-10
Serial Number: SJ-20120321105331-012

Publishing Date: 2012-05-10(R1.1)
NetNumen U31 R22 (V12.11.40) Issued.
About This Manual

Manual Description
This manual is applicable to NetNumen U31 R22 (V12.11.40P01) Unified Network
Management System (hereinafter referred to U31 R22).
U31 R22 is an network-level network management system based on the distributed,
multi-process and modular design. It can exercise unified management over the CTN,
SDH, WDM/OTN, Router, BAS and Switch series of optical transmission equipment from
ZTE.
Intended Readers
This manual applies to the following engineers:
l
l
l
Planning engineers
U31 R22 monitoring personnel
Maintenance engineers
What Is in This Manual

This manual contains the following chapters:
Chapter
Description
Chapter 1, System
Describes the concept, standards, position in the network, interface
Overview
functions, interface performance, and related concepts of the U31 R22

unified northbound SNMP interface.
Chapter 2, Configuring
Describes the methods and procedure of configuring the U31 R22 unified
the Unified Northbound
northbound SNMP interface.
SNMP Interface
Chapter 3,
Describes the interconnection procedure between the U31 R22 unified
Interconnecting the
northbound SNMP interface and the integrated NMS by examples, the
Unified SNMP Interface
usage guidelines about relevant documents.
With the Integrated NMS

Chapter 4, Maintaining
Describes the tasks and precautions of daily maintenance about the U31
the Unified Northbound
R22 unified northbound SNMP interface.
SNMP Interface
Chapter 5,
Describes the common troubleshooting methods of the U31 R22 unified
Troubleshootings
SNMP interface.
Chapter 6, OID List
Describes the OID values of the MIB nodes of the U31 R22 unified
northbound SNMP.
I
Conventions
1. Safety signs
The following safety signs may appear in this manual.
Safety Sign
Meaning
Equipment damage, data loss, degradation of equipment
Caution
performance, or other unpredictable result may occur if you

ignore this safety warning.
Provides additional information about a topic.
Note
Indicates a suggestion or hint to make things easier or more
Tip
productive.
2. Manual Usage Convention

This manual takes the U31 R22 client running on the Windows platform as an example
for illustration.
II
Contents
About This Manual ......................................................................................... I
Chapter 1 System Overview ...................................................................... 1-1
1.1 Interface Overview ............................................................................................. 1-1
1.2 Standards/Recommendations ............................................................................. 1-1
1.3 Position in the Network ....................................................................................... 1-2
1.4 Manageable NEs ............................................................................................... 1-2
1.5 Interface Functions............................................................................................. 1-4
1.6 Interface Performance ........................................................................................ 1-5
1.7 Related Concepts............................................................................................... 1-6
1.7.1 SNMP Management Frame....................................................................... 1-6
1.7.2 Six Kinds of Report Operations of SNMP ................................................... 1-7
1.7.3 Alarm Management Service Architecture of the Unified Northbound
SNMP Interface ..................................................................................... 1-8
1.7.4 SNMP Information Format ........................................................................ 1-9
Chapter 2 Configuring the Unified Northbound SNMP Interface ........... 2-1

2.1 Configuration Requirements................................................................................ 2-1
2.2 Configuration Flow ............................................................................................ 2-2
2.3 Starting Unified Northbound SNMP Alarm Services ............................................. 2-3
2.4 Setting Unified Northbound SNMP Agent Parameters .......................................... 2-3
2.5 Setting Unified Northbound SNMP Protocol Parameters (V2C Version).................. 2-5
2.6 Setting Unified Northbound SNMP Protocol Parameters (V3 Version) .................... 2-7
Chapter 3 Interconnecting the Unified SNMP Interface With the

Integrated NMS....................................................................................... 3-1
3.1 Application Scenario........................................................................................... 3-1
3.2 Prerequisites for Interconnection ......................................................................... 3-2
3.3 Interconncection Procedure ................................................................................ 3-3
3.3.1 Starting Unified Northbound SNMP Alarm Services ................................... 3-3
3.3.2 Setting Unified Northbound SNMP Agent Parameters ................................ 3-3
3.3.3 Setting Unified Northbound SNMP Protocol Parameters ............................. 3-4
3.3.4 Checking Interconnection Result .............................................................. 3-5
Chapter 4 Maintaining the Unified Northbound SNMP Interface ........... 4-1

4.1 Maintenance Operation Description .................................................................... 4-1
4.2 Checking Computer Security............................................................................... 4-2
4.3 Checking Password and Right Securities ............................................................ 4-2

4.4 Checking U31 R22 Console ............................................................................... 4-3
4.5 Checking the Communication Status Between the Unified Northbound SNMP
Interface and the Integrated NMS ..................................................................... 4-3
4.6 Backing up System Logs .................................................................................... 4-4
Chapter 5 Troubleshootings ..................................................................... 5-1

5.1 Exceptional Running of the Processes of the Unified Northbound SNMP
Interface .......................................................................................................... 5-1
5.2 Interconnection Failure Between Integrated NMS and Northbound SNMP
Interface .......................................................................................................... 5-3
Chapter 6 OID List ...................................................................................... 6-1

Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II
Chapter 1
System Overview
Table of Contents
Interface Overview .....................................................................................................1-1
Standards/Recommendations ....................................................................................1-1
Position in the Network...............................................................................................1-2
Manageable NEs .......................................................................................................1-2
Interface Functions.....................................................................................................1-4
Interface Performance ................................................................................................1-5
Related Concepts.......................................................................................................1-6
1.1 Interface Overview

NetNumen U31 R22 is an network-level network management system based on the
distributed, multi-process and modular design developed by ZTE Corporation. Hereafter
it is called U31 R22. It can exercise unified management over the CTN, SDH, WDM/OTN,
Router, BAS, and Switch series of transmission equipment.
U31 R22 northbound Simple Network Management Protocol (SNMP) interface is an
optional component of U31 R22. Operation Support System (OSS) can realize the unified
management of U31 R22 through the U31 R22 unified northbound SNMP interface.
1.2 Standards/Recommendations
U31 R22 unified northbound SNMP interface complies with the international standards.
Table 1-1 shows the TMF standards that the unified northbound SNMP interface complies
with.
Table 1-1 TMF Standards Followed by U31 R22 Unified Northbound SNMP Interface
Version
Description
SNMPv1
It is the first officially released protocol version.
SNMPv2
SNMPv2 expands some functions in protocol operations on the basis of SNMPv1.

SNMPv2 supports the mechanisms of mass data reading and more detailed error
information report to the management working station.
SNMPv2 supports distributed network management. Simultaneous transmission
of mass data reduces the ask/answer mode, and thus improves efficiency and
performance.
SNMPv2 has multiple subversions, among them, SNMPv2c is the most widely used.
1-1
SJ-20120321105331-012|2012-05-10(R1.1)
ZTE Proprietary and Confidential
NetNumen U31 R22 Northbound Interface User Guide (SNMP Interface)
Version
Description
SNMPv3
SNMPv3 focuses on enhancing the functions of protocol security

authentication/encryption, authorization/access control, and remote configuration
management. While in other areas, it follows some of the technical specifications of
SNMPv2.
Note:
U31 R22 unified northbound SNMP interface uses SNMPv2c and SNMPv3 protocols. It
supports the non-authentication and non-encryption, authentication and non-encryption,
and authentication and encryption of SNMPv3.
1.3 Position in the Network

U31 R22 unified northbound SNMP interface locates between U31 R22 and the integrated
NMS (OSS).
The integrated NMS manages U31 R22 through the unified northbound SNMP interface.
For the position of the U31 R22 unified northbound SNMP interface in the network
management system, see Figure 1-1.
Figure 1-1 Position in the Network Management System
OSS: Operation Support

System
EMS: Network Element

Management System
NMS: Network
Management System
1.4 Manageable NEs

l
SDH NEs
ZXMP S100, ZXMP S150, ZXMP S200, ZXMP S320, ZXMP S325, ZXMP S330,
ZXMP S360, ZXMP S380, ZXMP S385, ZXMP S390, ZXONE 5800, ZXMP S335.
WDM/OTN NEs
1-2
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 1 System Overview
ZXWM-32, ZXMP M600, ZXMP M720, ZXMP M721, ZXMP M800, ZXWM M900,
ZXMP M820, ZXMP M920, ZXONE 8000, ZXONE 8300, ZXONE 8500.
l
CTN NEs
ZXCTN 6100, ZXCTN 6110, ZXCTN 6120, ZXCTN 6200, ZXCTN 6220, ZXCTN 6300,
ZXCTN 9004, ZXCTN 9008.
USA Products
ZXUAS 10600, ZXE10 UAS2500S, ZXUAS 10800E, ZXUAS 10400, ZXUAS 10800.
Router
ZXR10 T8000-16, ZXR10 T8000-8, ZXR10 M6000-8, ZXR10 M6000-16, ZXR10
M6000-8s, ZXR10 M6000-5s, ZXR10 M6000-3s, ZXR10 T1200, ZXR10 T1200
BMSG, ZXR10 T600, ZXR10 T600 BMSG, ZXR10 T128, ZXR10 T64E, ZXR10
GER, ZXR10 GER04, ZXR10 GER02, ZXR10 ZSR 1822, ZXR10 ZSR 1842, ZXR10
ZSR 2842, ZXR10 ZSR 2882, ZXR10 ZSR 3842, ZXR10 ZSR 3884, ZXR10 ZSR
1809, ZXR10 ZSR 2822R, ZXR10 ZSR 1842R, ZXR10 ZSR 2842R, ZXR10 ZSR
2882R, ZXR10 ZSR 2822, ZXR10 ZSR 2884, ZXR10 ZSR 3822, ZXR10 ZSR 3844,
ZXR10 ZSR 3882, ZXR10 ZSR 1822E, ZXR10 GAR 2604, ZXR10 GAR2608, ZXR10
GAR3608, ZXR10 GAR7208, ZXR10 T16S, ZXR10 T16C, ZXR10 T32C, ZXR10
T64C, ZXR10 T160, ZXR10 T1216, ZXR10 T1212.
Switch
ZXR10 8902, ZXR10 8905, ZXR10 8908, ZXR10 8912, ZXR10 8902E, ZXR10
8905E, ZXR10 8908E, ZXR10 8912E, ZXR10 6902, ZXR10 6905, ZXR10 6908,
ZXR10 T40G, ZXR10 T64G, ZXR10 T160G, ZXR10 T240G, ZXR10 5224, ZXR10
5228, ZXR10 5228-FI, ZXR10 5252, ZXR10 5928, ZXR10 5928-FI, ZXR10 5928-PS,
ZXR10 5928E, ZXR10 5928E-FI, ZXR10 5952, ZXR10 5952E, ZXR10 5916E,
ZXR10 5128E, ZXR10 5116E, ZXR10 5128E-FI, ZXR10 5228A, ZXR10 5252A,
ZXR10 3928A, ZXR10 3928A-FI, ZXR10 3952A, ZXR10 3228A, ZXR10 3228A-EI,
ZXR10 3228A-FI, ZXR10 3252A, ZXR10 3206, ZXR10 3226, ZXR10 3228, ZXR10
3226-FI, ZXR10 3252, ZXR10 3906, ZXR10 3928, ZXR10 3928E, ZXR10 3928E-FI,
ZXR10 3952, ZXR10 3952E, ZXR10 59S STACK.
ZXR10 5109, ZXR10 5116, ZXR10 5116-FI, ZXR10 5116-SI, ZXR10 5124, ZXR10
5124-FI, ZXR10 5124-SI, ZXR10 2920-SI, ZXR10 2928-SI, ZXR10 2952-SI, ZXR10
2936-FI, ZXR10 2909-SI, ZXR10 2909-FU, ZXR10 2918-SI, ZXR10 2926-SI, ZXR10
2910E-PS, ZXR10 2918E, ZXR10 2918E-PS, ZXR10 2928E, ZXR10 2952E, ZXR10
2609-LE, ZXR10 2818S-LE, ZXR10 2826S-LE, ZXR10 2852S-LE, ZXR10 2609A,
ZXR10 2618A, ZXR10 2626A, ZXR10 2826A, ZXR10 2826A-PS, ZXR10 2609,
ZXR10 2609-FU, ZXR10 2809, ZXR10 2809-FU, ZXR10 2818S, ZXR10 2826S,
ZXR10 2852S, ZXR10 2826E, ZXR10 2618, ZXR10 2626, ZXR10 2609-EI, ZXR10
2818S-EI, ZXR10 2826S-EI, ZXR10 3904F, ZXR10 3904, ZXR10 3206S, ZXR10
2826, ZXR10 1816, ZXR10 29S STACK, ZXR10 5009.
Government and Enterprise Network Products
1-3
SJ-20120321105331-012|2012-05-10(R1.1)
ZXR10 5950-28TM, ZXR10 5950-28SM, ZXR10 5950-52TM, ZXR10 5950-28PM,

ZXR10 5950-24T, ZXR10 5950-48T, ZXR10 5250-24T, ZXR10 5250-52TM, ZXR10
3950-28TM, ZXR10 3950-28SM, ZXR10 3950-28PM, ZXR10 3950-52TS, ZXR10
2950-52TS, ZXR10 2950-28TC, ZXR10 2950-18TC, ZXR10 2950-18PC, ZXR10
2950-10PC, ZXR10 2850-18TM, ZXR10 2850-26TM, ZXR10 2850-52TC, ZXR10
2850-9TT, ZXR10 2850-9TS.
1.5 Interface Functions

Table 1-2 Function List of the Unified Northbound SNMP Interface
Function
Description
Reporting trap events
This function initially sends alarm events created on the Network

Element (NE) to the Operation Support System (OSS).
Querying the alarm IRP
This function enables users to perform the get operation upon alarm
version
Integration Reference Point (IRP) objects on the EMS from the OSS,
to get the version No. of the alarm IRP.
Querying the heartbeat IRP
This function enables users to perform the get operation upon
version
heartbeat IRP objects on the EMS from the OSS, to get the version
No. of the heartbeat IRP.
Querying and setting the
This function enables users to perform the get operation and set
heartbeat period
operation upon heartbeat objects on the EMS from the OSS, to

query and set the heartbeat period.
Querying current alarms
table objects on the EMS from the OSS, to query all current alarms.
Querying the number of

current alarms
number objects on the EMS from the OSS, to query the number of
critical, major, minor alarms, and notifications, and the number of
all current alarms.
Deleting current alarms
This function enables users to perform the operation upon alarm

table objects on the EMS from the OSS, to delete current alarms.
Filtering alarms
This function enables users to set and query the alarm filtering
conditions on the EMS from the OSS, to filter reported alarms.
While setting the filtering conditions, the user can configure whether
to enable the Object Identifier (OID) object for filtering control. If it is
enabled, other filtering conditions take effect only after this filtering
control is enabled.
Setting alarm processing
This function enables users to operate alarm table objects on the
measures
EMS from the OSS, to set alarm processing measures.
Acknowledging and
This function enables users to acknowledge and unacknowledge
Unacknowledging alarms
alarms in the current alarm table from the OSS.
1-4
SJ-20120321105331-012|2012-05-10(R1.1)
Function
Description
Reporting the alarm
This function enables the user to report the acknowledged and
acknowledged and
unacknowledged statuses of alarms on the EMS from the OSS. The
unacknowledged statuses
reporting format is alarm Trap format.
Customizing alarm contents
In alarms reported on the unified northbound interface, the user can

customize certain contents.
Manually synchronizing
After the unified northbound interface link is resumed, according to
alarms
the NMS requirements, the unified northbound interface can report

alarms generated during the link disconnection period to the NMS.
Modifying alarm attributes
The user can modify attributes of specified alarms through the

SNMP interface (such as the alarm severity) to comply with the NMS
requirements. At present, the U31 R22 northbound SNMP interface
only allows the user to modify the alarm acknowledgement status
AckStatus and the alarm remark field alarmMeasure.
Detecting whether the alarm

report trap is lost
The alarm trap on the unified northbound SNMP interface might

be lost due to OMM faults, link disconnection, or DCN congestion.
When the EMS finds that the alarm information is inconsistent with
the NMS alarms, it sends a list rebuild notification to notify the NMS
to reacquire the alarms. The notification is sent after the link between
the EMS and the NMS is recovered.
Adding an NE name
The user can add an NE name column, so that the carriers OSS
is easier to resolve and process the NE information during the
interconnection with the comprehensive EMS.
Synchronizing alarms by NE
This function enables the user to synchronize alarms by NE,

reducing system load and bearing capacity. The whole-network
alarm synchronization will cause great system consumption.
1.6 Interface Performance

For the specifications of the U31 R22 unified northbound SNMP interface, refer to Table
1-3.
Table 1-3 Specifications of U31 R22 Unified Northbound SNMP Interface
Performance Item
Performance Specification
Alarm processing
capability of the
interface
Capable of processing 300 alarms per second in the case of an alarm

volume of 100,000.
Capable of processing 400 alarms per second in light load conditions

(when the alarm volume is less than 2000).
1-5
SJ-20120321105331-012|2012-05-10(R1.1)
Performance Item
Performance Specification
Alarm processing
When the network devices are running properly (that is, the average interval of
response speed of
fault occurrence is more than one second), the average alarm response time
the interface
of the northbound interface (that is, the time from the occurrence of an alarm
on the NE to reporting the alarm to the integrated NMS by the northbound
interface) is no more than 10 seconds.
Supported number
The number of the current alarms that can be managed is no less than 100,000.
of current alarms
The supported number of the historical alarms depends on NMS. U31 R22
NMS can at least save history alarm data in the local file for six months.
The supported number of historical alarms depends on NMS. U31 R22 NMS
can at least save the performance history data of 15 minutes in the local file
for three months, and the performance history data of 24 minutes in the local
file for six months.
1.7 Related Concepts

1.7.1 SNMP Management Frame
SNMP management frame is composed of the following four components:
l
l
l
l
SNMP manager
SNMP agent
SNMP transmission management protocol
Management Information Base (MIB)
For the typical configuration structure of the northbound SNMP interface, see Figure 1-2.
For the descriptions of the components, refer to Table 1-4.
Figure 1-2 Structure of the Unified Northbound SNMP Interface
1-6
SJ-20120321105331-012|2012-05-10(R1.1)
Table 1-4 Component Description

Component
Description
OSS
It is the SNMP manager, meaning the integrated NMS that operates at the NMS end.
OSS uses the SNMP protocol to control and monitor the network nodes.
The whole network system must have one SNMP manager to work as the network
control center. The manager is the network control center. By operating the SNMP
manger, the network administrator sends requests to the managed system, and thus
monitors and installs the network devices.
SNMP manager can be a server used for network management, or an application
program that implements the management function in a network device.
Agent
SNMP agent, that is the proxy process that operates on the managed devices. It is a
software module in the managed system.
Agent maintains the information data managed by the managed system. After the
managed devices receive the requests from the SNMP manager, Agent makes
responses. The agent implements the following functions: gathering the managed
system status information, implementing the remote operations of the SNMP manger
to the managed system, and sending alarm information to the SNMP manger.
SNMP
SNMP manager and SNMP agent communicate with each other through SNMP
protocol
protocol, and use UDP to transmit SNMP packets.
MIB
MIB is a virtual data storage room that saves network management information which
is formed by multiple groups of managed objects. .
Note:
U31 R22 unified northbound SNMP interface works as the SNMP agent in the network
management system.
1.7.2 Six Kinds of Report Operations of SNMP

SNMP defines six report operations for the data exchange between management process
and the proxy.
l
l
l
l
l
Get-request operation: Extract one or multiple parameter values from the proxy
process.
Get-next-request operation: Extract the next parameter value following the current
parameter value from the proxy process.
Get-bulk operation: Extract one or multiple rows of data of one or multiple parameters
from the proxy process.
Set-request operation: Set one or multiple parameter values for the proxy process.
Get-response operation: Get response of one or multiple parameter values. This
operation is sent by the proxy process. It is also the responding operations of the
previous three operations.
1-7
SJ-20120321105331-012|2012-05-10(R1.1)
Trap operation: The proxy process actively sends packets and informs the
management process.
The management process send the four operations of get-request, get-next-request,

get-bulk, and get-request to the proxy process. For simplicity, these four operation are
called get, get-next, get-bult and set for short.
The proxy process sends operations of get-response and trap to the management process.
1.7.3 Alarm Management Service Architecture of the Unified

Northbound SNMP Interface
For the service architecture of alarm management of the unified northbound SNMP
interface, see Figure 1-3.
Figure 1-3 Alarm Management Service Architecture of the Unified Northbound SNMP
Interface
The unified northbound SNMP interface is a northbound adapter between the EMS and
the OSS, see Figure 1-3. This module responds to SNMP requests from the OSS and
returns responses. Meanwhile, it converts alarm messages from the EMS alarm standard
interface and reports them to the OSS in the SNMP trap mode.
1-8
SJ-20120321105331-012|2012-05-10(R1.1)
On the implementation layer, the EMS module provides an engine layer on the unified
SNMP interface to encapsulate the SNMP protocol stack, which converts the standard
SNMP protocol into a group of APIs. As the application layer for the unified SNMP
northbound engine, the alarm management of the unified northbound SNMP interface
provides the alarm service by directly using this group of APIs.
1.7.4 SNMP Information Format

Encapsulation Mode of SNMP Packets
For the format of SNMP packets encapsulated in IP data packets, see Figure 1-4.
Figure 1-4 Packet Format of IP Data
Frame Format of SNMP Packets

See Figure 1-5, the SNMP packet is composed of three units: SNMP header, PDU header,
and variable binding list.
1-9
SJ-20120321105331-012|2012-05-10(R1.1)
Figure 1-5 Frame Format of SNMP Packets
SNMP Header
There are two fields in the frame format of SNMP header. The definition of each field
is described as follows:
Version: SNMP version number. Manager and proxy must use the SNMP of the
same version.
Note:
The written version filed reduces one from the version number. For example,
SNMP (SNMPV1) should be written 0.
Community: A character string which works as the plain text password between
the management process and proxy process. The commonly used community is
"public".
PDU Header
SNMP defines five protocol data units (PDU) which correspond to the five kinds of
operation modes of SNMP packets.
Different PDU types correspond to the different frame formats of PDU header.
1-10
SJ-20120321105331-012|2012-05-10(R1.1)
PDU Type
For corresponding relationship of PDU type value and protocol operation, refer
to Table 1-5.
Table 1-5 PDU Type
Operation Name
PDU Type Value
get-request
get-next-request
get-response
set-request
trap
Request ID
It is an integer set by the management process. The proxy process has to return
this request ID when sending get-response packets.
Management process can send get packets to many agents simultaneously.
These packets all use UDP for transmission. The packets transmitted first may
arrive last. By the configuration of the request ID, management process can
identify that which request packet corresponds to the returned packet.
Error Status
It is a number ranging from 0 to 5, and entered by the proxy process during
responding. For the error status descriptions, refer to Table 1-6.
Table 1-6 Error Status Description
Error
Name
Description
noError
Everything is normal.
tooBig
The proxy cannot pack the answers in one SNMP packet.
noSuchName
An operation indicates a variable that does not exist.
badValue
A set operation indicates an invalid value or an invalid
Status
grammar.
readOnly
The management process tries to modify a read-only variable.
genErr
Other errors
Error Index
When an error of noSuchName, badValue, or readOnly appears, the proxy
process sets an error index during responding, which indicates the offset of the
variable with error in the variable list.
Enterprise
1-11
SJ-20120321105331-012|2012-05-10(R1.1)
It is the object ID of network devices of the trap packet.

This object ID is on a sub-tree under the Enterprise node {1.3.6.1.4.1} of the object
naming tree.
Trap Type (Generic-trap)

Trap type is classified in to seven kinds, refer to Table 1-7.
Table 1-7 Trap Type Description
Trap Type
Name
Description
coldStart
The agent performed the initialization.
warmStart
The agent performed re-initialization.
linkDown
An interface changes from working status to fault

status.
linkUp
An interface changes from fault status to working

status.
authenticationFail-
Receive a packet with invalid community from SNMP
ure
management process.
egpNeighborLoss
An EGP neighbor router changes into fault status.
enterpriseSpecific
Deputizing self-defined events requires a "specific

code".
When you use type 2, 3, and 5, the first variable will identify the corresponding
interface.
Agent IP
Enter the IP address of the agent.
Specific-code
If the trap type is 6, the specific-code points out the user-defined time of the agent,
otherwise it is 0.
Timestamp
Points out the time from agent process initialization to the occurrence of the event
that trap reported. The unit is 10 ms. For example, timestamp 1908 indicates that
the event happens 1908 ms after the agent initialization.
Variable-bindings
Points out the names and corresponding values for one or more variables.
Note:
In get packet or get-next packet, variable values should be ignored.
1-12
SJ-20120321105331-012|2012-05-10(R1.1)
Checking the Criteria of the U31 R22 Unified Northbound SNMP Interface
Criteria check of the U31 R22 unified northbound SNMP interface is a conventional query.
It is a particular case of get-bulk.
Criteria check conversions of the U31 R22 unified northbound SNMP interface: when you
perform get-bulk query, request that the values are as follow:
l
l
non_repeaters = 1
maxmum_repeatitions = 0
Note:
After U31 R22 unified northbound SNMP interface and integrated NMS are interconnected,
the integrated NMS must follow the steps below to acquire information:
l
l
Initiate get-bulk criteria query to acquire the needed information, and northbound
SNMP interface saves the acquired information to MIB.
Query the needed information from MIB by using the query of get, get-next, and
get-bulk.
1-13
SJ-20120321105331-012|2012-05-10(R1.1)
This page intentionally left blank.
1-14
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 2
Configuring the Unified

Table of Contents
Configuration Requirements .......................................................................................2-1
Configuration Flow ....................................................................................................2-2
Starting Unified Northbound SNMP Alarm Services ...................................................2-3
Setting Unified Northbound SNMP Agent Parameters ...............................................2-3
Setting Unified Northbound SNMP Protocol Parameters (V2C Version)......................2-5
Setting Unified Northbound SNMP Protocol Parameters (V3 Version) ........................2-7
2.1 Configuration Requirements

Hardware Configuration
The unified northbound SNMP interface runs in a same computer with the U31 R22
server. Therefore, the hardware configuration requirements of the unified northbound
SNMP interface and the U31 R22 server must be the same.
Note:
Refer to Section "Typical Hardware Configurations of the Server" in NetNumen U31
R22 Unified Network Management System Software Installation Guide for the hardware
configuration requirements of U31 R22 server.
Software Configuration
The unified northbound SNMP interface is integrated in the U31 R22 installation package.
The computer must be able to install and run the U31 R22 server. No other software
packages are needed during the installation of the northbound interface.
2-1
SJ-20120321105331-012|2012-05-10(R1.1)
Note:
Refer to Section "Software Configuration of the Server" in NetNumen U31 R22
Unified Network Management System Software Installation Guide for the configuration
requirements of the U31 R22 server software.
2.2 Configuration Flow

Before setting parameters, ensure that you have successfully installed the U31 R22 server.
The unified northbound SNMP interface is installed by default.
Note:
For details, refer to Section "Installing U31 R22 Server and Client" in NetNumen U31
R22 Unified Network Management System Software Installation Guide.
For the deployment and configuration flow of the SNMP interface, see Figure 2-1.
Figure 2-1 Configuration Flow of SNMP Interface
2-2
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 2 Configuring the Unified Northbound SNMP Interface
2.3 Starting Unified Northbound SNMP Alarm Services

Before setting parameters of the unified northbound SNMP agents and the protocol, you
need to start the unified northbound SNMP alarm services.
Steps
1. On the computer where the U31 R22 server is located, select the menu Start >
Programs > NetNumen Unified Management System > NetNumen Config Center.
The NetNumen(TM) Unified Management System window is displayed.
2. In the left navigation tree, select Configuration Center > Common Configuration >
Unified North Configuration.
3. Select Alarm SNMP below Unified North Configuration in the right pane.
4. Click Save All. The Message dialog box is displayed, indicating the parameters are
successfully saved.
5. Click OK.
Note:
When you exit the configuration center, the system automatically adds the unified
northbound SNMP alarm processes.
End of Steps
2.4 Setting Unified Northbound SNMP Agent

Parameters
The following parameters of the unified northbound SNMP agent include proxy host
address, proxy message code, Trap target address, alarm visibility rule, and alarm NE
filtering rule.
Prerequisite
You have started the unified northbound SNMP alarm services.
2-3
SJ-20120321105331-012|2012-05-10(R1.1)
Context
l
l
l
SNMP alarm supports default agent and common agent.

The default agent creates agents by using the system default parameters. U31 R22
supports one default agent.
The common agent creates agents in accordance with the parameters configured by
the user. U31 R22 supports five SNMP common agents. You can enable one or
multiple agents in accordance with the number of the interconnected integrated NMS.
The parameter interconnection process of each agent is the same.
If the SNMP alarm uses the default agent, select SNMP Default Agent below node
Steps
2. In the left navigation tree, select the node Configuration Center > Common
Configuration > Unified North Configuration.
3. Under the Unified North Configuration node in the right pane, expand the Alarm
SNMP node, and select SNMP Agent1.
SNMP alarm uses the configuration parameters of SNMP Agent1 to create the agent.
4. Expand node SNMP Agent1. Set the parameters by referring to Table 2-1.
Table 2-1 SNMP Agent Parameter Description
Parameter
Configuration Description
SNMP proxy host
IP address of the proxy host.
Agent Encoding
It is the coding mode of the integrated NMS operation system

that ensures the interconnection system can correctly analyze the
characters in the message. It supports GBK and UTF-8.
If you cannot acquire the coding mode of the integrated NMS
operation system, you can use the default setting. The system uses
the default coding mode of the unified NMS sever operation system.
2-4
SJ-20120321105331-012|2012-05-10(R1.1)
Parameter
Trap target address
SNMP manager address that receives the alarm SNMP northbound

Trap message. The format is: IP address reported by the Trap:
(IPV4 or IPV6) + port. You can set multiple IP addresses.
l
Format of IPV4: IP1;IP2:Port2;IP3:Port3...
Format of IPV6: [IP1];[IP2]:Port2;[IP3]:Port3...
When the port value is not entered, the default value is 162.
ALARM NAF Visible Filter
Select No.
ALARM MOC Filter
Set the NE Trap filtering condition. Only the alarms that meet the
filtering conditions will be reported. This filtering condition must be
set before the system starts. It cannot be modified after the system
starts. Restart the NMS server after the modification.
You can set the following parameters as needed:
l
default: uses ums-server\procs\ppus\uca.ppu\uca-fm

-naf-snmp.pmu\uca-osf-fm-naf-snmp.par\conf\uc
a-fm-naf-snmp-alarm-moc-filters.xml configuration
file.
all: sends all the NE alarm trap.
"": filters all the NE alarm Trap.
Note:
When you enable multiple unified northbound agents, the Trap target address must
are not repeated. Otherwise, the target device will receive the repeated Trap message.
5. Click Save All. The Message dialog box is displayed, indicating the operation is
successful.
6. Click OK.
End of Steps
2.5 Setting Unified Northbound SNMP Protocol

Parameters (V2C Version)
If the SNMP agent uses the protocol of V2C version. You need to set these parameters:
proxy host port, read, write, notify, and community values.
Prerequisite
You have set the parameters of the unified northbound SNMP agent.
2-5
SJ-20120321105331-012|2012-05-10(R1.1)
Context
This document describes how to set the protocol parameters by describing SNMP alarm
using SNMP Agent1. Configuration procedure of the other agents are similar.
Steps
2. In the left navigation tree, select Configuration Center > Common Configuration >
3. Under the Unified North Configuration node in the right pane, expand Alarm SNMP
> SNMP Agent1, and select V2C.
4. Expand the V2C node. Set the parameters by referring to Table 2-2.
Table 2-2 V2C Version Parameter Description
Parameter
SNMP proxy port
Set the host port that uses the V2C protocol from the port No. that
is not occupied. Value range: 0 to 65535.
V2C read community
Set the read operation community in the V2C version protocol.

It is the plain text of the management process and the proxy
process, such as public.
V2C write community
Set the write operation community in the V2C version protocol.

2-6
SJ-20120321105331-012|2012-05-10(R1.1)
Parameter
V2C notify community
Set the notify operation community in the V2C version protocol.

Note:
When you enable multiple unified northbound agents, the SNMP proxy port
cannot be repeated. Otherwise, you may fail to enable the unified SNMP alarm
services.
V2C version community of the SNMP common agent does not support multiple
parameters. If you set the community to public or private, they system will
authenticate this character string as a parameter.
successful.
6. Click OK to return to the NetNumen(TM) Unified Management System window.
7. Click Close.
8. Start NetNumen U31 Unified Management SystemConsole. The parameters are
successfully set.
Note:
The processes of the unified northbound SNMP alarm are not displayed in
NetNumen U31 Unified Management SystemConsole, you can check whether it
is successfully started through the MIBBrowser testing tool. For detailed operations,
see Section "Checking Interconnection Result".
End of Steps
2.6 Setting Unified Northbound SNMP Protocol

Parameters (V3 Version)
If the SNMP agent uses the protocol of V3 version, you need to set these parameters:
proxy host port, security name, authentication password, private password, authentication
encryption protocol, private password, encryption protocol, and security level.
Prerequisite
You have set the parameters of the unified SNMP agent.
2-7
SJ-20120321105331-012|2012-05-10(R1.1)
Context
This document describes how to set the protocol parameters by describing SNMP alarm
using SNMP Agent1. Configuration procedure of the other agents are similar.
Steps
SNMP > SNMP Agent1 node, and select the V3 node.
4. Expand the V3 node. Set the parameters by referring to Table 2-3.

Table 2-3 V3 Version Parameter Description
Parameter
SNMP proxy port
Set the host port that uses the V2C protocol from the port No.
that is not occupied. Value range: 0 to 65535.
2-8
SJ-20120321105331-012|2012-05-10(R1.1)
Parameter
V3 security Name
Set the user name, such as nbisnmp.
V3 authentication Password
Set the authentication password, at least eight bytes, such as
phrase, at least 8 byte
nbi888888.
V3 private Password phrase
Set the private password, such as nbi888888.
V3 authentication Password
Set the authentication protocol, such as MD5.
protocol
V3 private Password protocol
Set the private protocol, such as DES.
V3 security level
Set the security level. Select from the following three levels
as needed:
l
1: NOAUTH_NOPRIV
2: AUTH_NOPRIV
3: AUTH_PRIV
Note:
When the unified northbound SNMP agent with multiple V3 version protocols are
started, avoid repeated V3 security Name. Otherwise, the parameters of the V3
version authentication comply with the last effective conflagration.
successful.
7. Click Close.
successfully set.
Note:
The processes of the unified northbound SNMP alarm are not displayed in
NetNumen U31 Unified Management SystemConsole, you can check whether it
is successfully started through the MIBBrowser testing tool. For detailed operations,
see Section "Checking Interconnection Result".
End of Steps
2-9
SJ-20120321105331-012|2012-05-10(R1.1)
2-10
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 3
Interconnecting the Unified

SNMP Interface With the
Integrated NMS
Table of Contents
Application Scenario...................................................................................................3-1
Prerequisites for Interconnection ................................................................................3-2
Interconncection Procedure........................................................................................3-3
3.1 Application Scenario

This document describes the interconnection between the U31 R22 unified northbound
Simple Network Management Protocol (SNMP) and the integrated NMS of other
manufacturers through a typical application scenario.
Note:
l
l
This document simulates the integrated NMS to perform the interconnection by

describing MIBBrowser.
In this example, assume that Scale 1 is selected when installing the U31 R22, and the
SNMP agent uses the protocol of version V2C.
For the project application scenario, see Figure 3-1. U31 R22 and the unified northbound
SNMP interface are installed on a same computer, and the integrated NMS is installed on
another computer.
3-1
SJ-20120321105331-012|2012-05-10(R1.1)
Figure 3-1 Interconnection Scenario
For detailed information of MMS and the computers, refer to Table 3-1.
Table 3-1 Interconnection Information between SNMP and the Integrated NMS
EMS
Version
IP Address
Port ID
U31 R22
V12.11.40
10.10.10.9
Proxy host
port No:
21178
Integrated NMS (MIBBrowser)
Trap port No:

162
3.2 Prerequisites for Interconnection

1. U31 R22 and the integrated NMS are installed successfully. Service of U31 R22
console suspends.
2. The U31 R22 unified northbound SNMP interface is configured during the installation.
Note:
Refer to Chapter "Configuring Parameters for the Unified Northbound SNMP Interface"
for the configuration of the unified northbound SNMP interface.
3. The following documents have been obtained from ZTE:

l MIB Files
l Basic Data Table
l Unified SNMP Interface Standards
3-2
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 3 Interconnecting the Unified SNMP Interface With the Integrated NMS
3.3 Interconncection Procedure

3.3.1 Starting Unified Northbound SNMP Alarm Services
Before setting parameters of the unified northbound SNMP agents and the protocol, you
need to start the unified northbound SNMP alarm services.
Steps
3. Under the Unified North Configuration node in the right pane, select Alarm SNMP.
successful.
5. Click OK.
End of Steps
3.3.2 Setting Unified Northbound SNMP Agent Parameters

The following parameters of the unified northbound SNMP agent include proxy host
address, proxy message code, Trap target address, alarm visibility rule, and alarm NE
filtering rule.
Prerequisite
You have started the unified northbound SNMP alarm processes.
Steps
SNMP node, and select SNMP Agent1.
SNMP alarm uses the configuration parameters of SNMP Agent1 to create the agent.
4. Expand the SNMP Agent1 node. Set the parameters by referring to Table 3-2.
3-3
SJ-20120321105331-012|2012-05-10(R1.1)
Table 3-2 SNMP Agent Parameter Description

Parameter
Value
SNMP proxy host
10.10.10.9
Agent Encoding
Default setting
Trap target address
10.10.10.10:162
ALARM NAF Visible Filter
No.
ALARM MOC Filter
default
successful.
6. Click OK.
End of Steps
3.3.3 Setting Unified Northbound SNMP Protocol Parameters

If the SNMP agent uses the protocol of V2C version. You need to set these parameters:
proxy host port, read, write, notify, and community values.
Prerequisite
You have set the parameters of the unified northbound SNMP agent.
Steps
SNMP > SNMP Agent1 node, and select the V2C node.
4. Expand the V2C node. Set the parameters by referring to Table 3-3.
Table 3-3 V2C Version Parameter Description
Parameter
Value
SNMP proxy port
1610
V2C read community
public
V2C write community
public
V2C notify community
public
3-4
SJ-20120321105331-012|2012-05-10(R1.1)
successful.
7. Click Close.
successfully set.
End of Steps
3.3.4 Checking Interconnection Result

Preparations for checking the interconnection contain loading MIB files and setting SNMP
protocol version.
The interconnection content contains checking the Get operation and testing whether the
Trap operation receives alarms.
Prerequisite
l
l
l
l
You have started the unified northbound SNMP alarm services.

You have set the unified northbound SNMP agent parameters.
You have set the unified northbound SNMP protocol parameters.
NetNumen U31 Unified Network Management System Console starts normally.
Context
Note:
This document describes the interconnection by using the MIBBrowser tool to simulate
the integrated NMS. If you need the MIBBrowser tool, select BN-IP Management
during the installation.
If both the Get operation and the Trap operation receive normal responses, the unified
northbound SNMP alarm processes are successfully started.
Steps
1. Load MIB files.
a. In the installation path\tools\usf-mibbrowser folder, double-click the
mibBrowser.bat file to start the MIBBrowser tool, see Figure 3-2.
3-5
SJ-20120321105331-012|2012-05-10(R1.1)
Figure 3-2 MIB Browser Window
b. Select File > Load MIB from the main menu. The Load MIB Dialog box is
displayed.
c. Click Browse, and select the file directory: installation path\ums-serve
r\procs\ppus\uca.ppu\uca-fm-naf-snmp.pmu\uca-osf-fm-naf-snm
p.par\mib. Load all the files under the directory. For the navigation tree after
successful loading, see Figure 3-3.
3-6
SJ-20120321105331-012|2012-05-10(R1.1)
Figure 3-3 Navigation Tree After Loading MIB Files
Note:
The "MIB.exe" file provided by ZTE includes one MIB files and three *.txt files.
2. Set the SNMP protocol version.

a. Select Operations > Settings from the main menu. The MibBrowser Settings
window is displayed.
b. Click the General tab, and then set the parameter values for SNMP Version,
SNMP Port, and Trap Port.
In this example, set the parameters by referring to Table 3-4.
Table 3-4 Basic Parameters Configuration
Parameter
Description
Value
SNMP Version
The SNMP protocol version used by the system.
SNMPV2c
Graph Type
It is the graphic representation of the system alarm
Bar Chart
information.
SNMP Port
It is the SNMP port that the integrated NMS used to
1610
deliver commands.
3-7
SJ-20120321105331-012|2012-05-10(R1.1)
Parameter
Description
Value
Trap Port
It is the Trap port used by U31 R22 to report
162
messages to the integrated NMS.

Other
Use the default
parameters
settings.
Note:
If you select version SNMPV3, you need to switch to the V3 Settings tab, and
then set security parameters for Auth Protocol, Priv Protocol, Auth Password,
Priv Password, Target Host, Target Port, User Name, and Security Level.
c. Click OK to return to the ZTE MibBrowser window.

End of Steps
3.3.4.1 Testing Get Operations

After the integrated NMS is successfully interconnected with the unified northbound SNMP
interface, the integrated NMS can acquire the related information of the unified northbound
SNMP interface.
Prerequisite
The integrated NMS is successfully interconnected with the U31 R22 unified northbound
SNMP interface.
Steps
1. In the Loaded MibModules navigation tree of MIBBrowser,
select
ZTE-ALARM-IRP-MIB > enterprises > zteMIB > alarm > alarmIRP > alarmIRPInfo
> alarmirpVersion.
2. In the Host text box in the right pane, enter the IP address of U31 R22 Operation &
Maintenance Center (OMC): 10.10.10.9.
3. Select alarmirpVersion, right-click it, and select Get from the pop-up menu.
If the SNMP starts normally, you can know the output content in Figure 3-4.
3-8
SJ-20120321105331-012|2012-05-10(R1.1)
Figure 3-4 Get Operation Response
End of Steps
3.3.4.2 Receiving Trap Messages

After the integrated NMS has been successfully interconnected with the unified
northbound SNMP interface, the unified northbound SNMP interface actively reports the
Trap messages.
Prerequisite
The interconnection between U31 R22 unified northbound SNMP interface and the
integrated NMS is successful.
Steps
1. Select View > Trap Viewer from the MIBBrowser main menu. The Trap Viewer
window is displayed.
2. If SNMP runs normally, when there is a new alarm or alarm restoration information,
the alarm list in the Trap Viewer window displays the received alarms, see Figure 3-5.
3-9
SJ-20120321105331-012|2012-05-10(R1.1)
Figure 3-5 Received Alarm Information
End of Steps
3-10
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 4
Maintaining the Unified

Table of Contents
Maintenance Operation Description ...........................................................................4-1
Checking Computer Security ......................................................................................4-2
Checking Password and Right Securities ..................................................................4-2
Checking U31 R22 Console ......................................................................................4-3
Checking the Communication Status Between the Unified Northbound SNMP
Interface and the Integrated NMS ..............................................................................4-3
Backing up System Logs ............................................................................................4-4
4.1 Maintenance Operation Description

This section describes prerequisites, task, and precautions for maintaining the unified
northbound SNMP interface.
Prerequisites
To ensure the normal operation of the U31 R22 unified northbound SNMP interface,
maintenance personnel must be familiar with the following.
l
l
l
The Windows operating system and basic network operations

The SNMP interface technology
Telecom Management Network (TMN), and the basic networking structure and basic
operations of U31 R22
Precautions
Caution!
Always observe relevant precautions when working with U31 R22. Failure to do so can
result in improper operation.
Never modify the system time when the U31 R22 server is running.
If it is necessary to modify the system time during maintenance, follow the steps below:
1. Exit the U31 R22 server.
4-1
SJ-20120321105331-012|2012-05-10(R1.1)
2. Modify the system time.

3. Start the U31 R22 server.
Ensure U31 R22 has been successfully started before starting the U31 R22 unified
northbound SNMP interface. Ensure the U31 R22 client can log into the U31 R22
server normally.
Maintenance Tasks
l
l
Ensure that the server where U31 R22 is located works properly.
Ensure the U31 R22 unified northbound SNMP interface runs properly.
Note:
The following describes the routine maintenance operations of the northbound SNMP
interface on the Windows platform.
4.2 Checking Computer Security

This section describes how to check the computer security so as to ensure it can operate
U31 R22 properly.
Steps
1. Verify that the network management system regularly installs the patch program to
prevent Windows holes.
2. Check the firewall installation.
3. Verify that the antivirus library of the antivirus software is regularly updated, and the
antivirus library is the latest one.
End of Steps
4.3 Checking Password and Right Securities

This section describes how to regularly check the password and authority securities of the
operation system so as to ensure the security for U31 R22.
Steps
1. Check the password and right of the NMS Windows. Set a complex password.
2. Regularly change the password.
3. Do not use the GUEST account.
End of Steps
4-2
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 4 Maintaining the Unified Northbound SNMP Interface
4.4 Checking U31 R22 Console

This section describes how to check the U31 R22 console and the running status of the
U31 R22 processes on the U31 R22 server.
Prerequisite
You have successfully installed the U31 R22 server.
Steps
Programs > NetNumen Unified Management System > NetNumen Console.
The NetNumen U31 Network Unified Management System-Console dialog box
appears.
2. In the menu tree on the left, select CONSOLE > Console 1. The Detailed information
window appears.
3. Check the items of all the processes whose Operation type are Start process. Verify
that the Operation result is Successful.
l Start process of all the processes are Successful: indicates U31 R22 processes
run normally.
l
Start process of one or multiple processes are Failed., or they automatically
restart: indicates U31 R22 processes run improperly.
End of Steps
4.5 Checking the Communication Status Between

the Unified Northbound SNMP Interface and the
Integrated NMS
This section describes how to check the communication status between the unified
northbound SNMP interface and the integrated NMS.
Steps
1. On the server where the unified northbound SNMP interface is located, enter
the following command ping IP address of the computer where the
integrated NMS is located to check the network communication status.
If...
Then...
They can ping through
The communication is normal.
They cannot ping through
Problems occur to the network communication,

check the network connection.
4-3
SJ-20120321105331-012|2012-05-10(R1.1)
2. Check whether the processes if the unified northbound SNMP interface start
successfully. For the checking method, refer to Section Checking Interconnection
Result.
3. Start the client of the integrated NMS, and confirm that it can manage the U31 R22
connected by the unified northbound SNMP interface properly.
End of Steps
Result
The operation results are the same as what are described in the above steps, which
indicates that the communication status between the unified northbound SNMP interface
and the integrated NMS is normal.
4.6 Backing up System Logs

This section describes how to back up the logs of the U31 R22 unified northbound interface.
Context
U31 R22 log levels in descending order is: LM_ERROR > LM_INFO > LM_DEBUG.
l
l
LM_ERRO: It is used to record the wrong information of the function.

LM_INFO: It is used to record the necessary information for interface scheduling.
Such as interface and important function ingress, IDL packet data delivered by the
query and configuration interfaces.
LM_DEBUG: It is used to record the unnecessary information. Such as the F interface
packet returned from the server and some function implementation records.
Note:
The default log level is LM_INFO.
Steps
1. Back up the recent operating logs of the unified northbound interface.
a. On the computer where the U31 R22 server is located, enter the corresponding
directory in accordance with the selected scale during installation by referring to
Table 4-1.
Table 4-1 Log Directories of Different Installation Scales
Scale
Log Directory
Scale 1
\ums-server\works\uep\uep1\log
Scale 2 and Scale 3
\ums-server\works\uca\uca1\log
4-4
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 4 Maintaining the Unified Northbound SNMP Interface
Scale
Log Directory
Scale 4, Scale 5, and Scale 6
\ums-server\works\fmsnmp\fmsnmp1\log
Note:
This directory saves the recent operation logs of the U31 R22 unified northbound
interface. Each log file is 10 M by default.
b. Copy all the log files in this directory to another storage device for backup.
2. Back up the compressed log files.
a. On the computer where the U31 R22 server is located,
\ums-server\rundata\umd\output\timer directory.
enter the
Note:
In the centralized deployment mode, U31 R22 compresses the logs every day.
The compressed log files are saved in the \ums-server\rundata\umd\output\timer
directory.
b. Copy all the log files in this directory to another storage device for backup.
End of Steps
4-5
SJ-20120321105331-012|2012-05-10(R1.1)
4-6
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 5
Troubleshootings
Table of Contents
Exceptional Running of the Processes of the Unified Northbound SNMP Interface ....5-1
Interconnection Failure Between Integrated NMS and Northbound SNMP Interface ..5-3
5.1 Exceptional Running of the Processes of the

Unified Northbound SNMP Interface
Fault Symptoms
l
l
The U31 R22 console automatically logs out after it has been started.
The Get operation and (or) Trap operation fails during the interconnection between
the unified northbound SNMP interface and the integrated NMS.
Fault Causes
l
l
l
The processes of the U31 R22 unified northbound SNMP interface are not
successfully started.
Parameters of the U31 R22 unified northbound SNMP agent are wrongly set.
Parameters of the U31 R22 unified northbound SNMP protocol are wrongly set.
5-1
SJ-20120321105331-012|2012-05-10(R1.1)
Processing Flow
Figure 5-1 Processing Flow
Troubleshooting
l
Cause 1: The unified northbound SNMP alarm services are not started.
1. On the computer where the U31 R22 server is located, select the menu
Start > Programs > NetNumen Unified Management System > NetNumen
Config Center. The NetNumen (TM) Unified Management System window is
displayed.
SNMP node.
If the fault remains, go to Cause 2.
If the fault disappears, the handling is completed.
Cause 2: Parameters of the U31 R22 unified northbound SNMP agent are wrongly
set.
SNMP node, check and correct the agent parameters.

5-2
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 5 Troubleshootings
Cause 2: Parameters of the U31 R22 unified northbound SNMP protocol are wrongly
set.
SNMP node, check and correct the protocol parameters.
If the fault remains, keep the fault environment and seek technical support
from ZTE.
5.2 Interconnection Failure Between Integrated NMS

and Northbound SNMP Interface
Fault Symptoms
The integrated NMS cannot interconnect with the U31 R22 unified SNMP interface.
Fault Causes
l
l
l
l
The communication between U31 R22 and the integrated NMS is abnormal.
Operation failure of the U31 R22 integrated NMS.
Processes of the U31 R22 northbound interface are abnormal.
The U31 R22 unified northbound SNMP interface is operating exceptionally.
5-3
SJ-20120321105331-012|2012-05-10(R1.1)
Processing Flow
Figure 5-2 Processing Flow
Troubleshooting
l
Cause 1: The communication between the sever and the integrated NMS is abnormal.
1. Check whether the network connection of the U31 R22 server computer is normal.
If yes, go to Step 3.
If no, go to Step 2.
2. Check and handle the network adapter of U31 R22 server computer and the
communication protocol.
If the fault remains, go to Step 3.
3. Check whether the network connection of the integrated NMS server computer is
normal.
If yes, go to Step 5.
If no, go to Step 4.
4. Check and handle the network adapter of the integrated NMS server computer
and the communication protocol.
If the fault remains, go to Step 5.

5-4
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 5 Troubleshootings
5. On the computer where the U31 R22 server is located, ping integrated NMS
server computer IP.
If ping through, go to Cause 2.
If cannot through, go to Step 6.
6. Check and handle the communication line between the U31 R22 server NMS and
the integrated NMS server.
Cause 2: The integrated NMS is operating improperly.

Refer to the user manual of the integrated NMS.
Cause 3: The U31 R22 unified northbound SNMP interface is operating exceptionally.
Refer to Section Exceptional Running of the Processes of the Unified Northbound
SNMP Interface.
If the fault remains, keep the fault environment and seek technical support from
ZTE.
5-5
SJ-20120321105331-012|2012-05-10(R1.1)
5-6
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 6
OID List
MIB Node Name
MIB Leave Name
alarmIRPInfo
OID
.1.3.6.1.4.1.3902.4101.1.1
alarmIrpVersion
.1.3.6.1.4.1.39024101.1.1.1
sendNotificationId
.1.3.6.1.4.1.39024101.1.1.2
systemDN
.1.3.6.1.4.1.39024101.1.1.3
lastSendNotificationId
.1.3.6.1.4.1.39024101.1.1.4
alarmCount
.1.3.6.1.4.1.3902.4101.1.2
alarmIndeterminateNumber
.1.3.6.1.4.1.3902.4101.1.2.1
alarmCriticalNumber
.1.3.6.1.4.1.3902.4101.1.2.2
alarmMajorNumber
.1.3.6.1.4.1.3902.4101.1.2.3
alarmMinorNumber
.1.3.6.1.4.1.3902.4101.1.2.4
alarmWarningNumber
.1.3.6.1.4.1.3902.4101.1.2.5
alarmNumber
.1.3.6.1.4.1.3902.4101.1.2.6
currentAlarmEntry
.1.3.6.1.4.1.3902.4101.1.3.1
alarmId
.1.3.6.1.4.1.3902.4101.1.3.1.1
alarmManagedObjectInstance
.1.3.6.1.4.1.3902.4101.1.3.1.2
alarmEventTime
.1.3.6.1.4.1.3902.4101.1.3.1.3
alarmEventType
.1.3.6.1.4.1.3902.4101.1.3.1.4
alarmProbableCause
.1.3.6.1.4.1.3902.4101.1.3.1.5
alarmPerceivedSeverity
.1.3.6.1.4.1.3902.4101.1.3.1.6
alarmSpecificProblem
.1.3.6.1.4.1.3902.4101.1.3.1.7
alarmAdditionalText
.1.3.6.1.4.1.3902.4101.1.3.1.8
alarmIndex
.1.3.6.1.4.1.3902.4101.1.3.1.9
alarmComment
.1.3.6.1.4.1.3902.4101.1.3.1.10
alarmCode
.1.3.6.1.4.1.3902.4101.1.3.1.11
alarmNetype
.1.3.6.1.4.1.3902.4101.1.3.1.12
rowStatus
.1.3.6.1.4.1.3902.4101.1.3.1.13
alarmCodeName
.1.3.6.1.4.1.3902.4101.1.3.1.14
6-1
SJ-20120321105331-012|2012-05-10(R1.1)
MIB Node Name
MIB Leave Name
OID
alarmManagedObjectInstanceName
.1.3.6.1.4.1.3902.4101.1.3.1.15
alarmSystemType
.1.3.6.1.4.1.3902.4101.1.3.1.16
alarmNeIP
.1.3.6.1.4.1.3902.4101.1.3.1.17
alarmAck
.1.3.6.1.4.1.3902.4101.1.3.1.18
cleiCode
.1.3.6.1.4.1.3902.4101.1.3.1.19
timeZoneID
.1.3.6.1.4.1.3902.4101.1.3.1.20
timeZoneOffset
.1.3.6.1.4.1.3902.4101.1.3.1.21
dSTSaving
.1.3.6.1.4.1.3902.4101.1.3.1.22
aid
.1.3.6.1.4.1.3902.4101.1.3.1.23
id
.1.3.6.1.4.1.3902.4101.1.3.1.24
alarmOtherInfo
.1.3.6.1.4.1.3902.4101.1.3.1.25
alarmMocObjectInstance
.1.3.6.1.4.1.3902.4101.1.3.1.26
alarmNotificationProfile
.1.3.6.1.4.1.3902.4101.1.4.1
alarmNew
.1.3.6.1.4.1.3902.4101.1.4.1.1
alarmCleared
.1.3.6.1.4.1.3902.4101.1.4.1.2
alarmAckChange
.1.3.6.1.4.1.3902.4101.1.4.1.3
alarmCommentChange
.1.3.6.1.4.1.3902.4101.1.4.1.4
alarmListRebuild
.1.3.6.1.4.1.3902.4101.1.4.1.5
alarmSync
.1.3.6.1.4.1.3902.4101.1.4.1.6
messageInfo
.1.3.6.1.4.1.3902.4101.1.4.1.7
alarmFilterEnable
.1.3.6.1.4.1.3902.4101.1.6.1
alarmFilterCondition
.1.3.6.1.4.1.3902.4101.1.6.3
alarmTypeFilter
.1.3.6.1.4.1.3902.4101.1.6.3.4
alarmSeverityFilter
.1.3.6.1.4.1.3902.4101.1.6.3.5
alarmCodesExcludeFilter
.1.3.6.1.4.1.3902.4101.1.6.3.6
alarmTypeExcludeFilter
.1.3.6.1.4.1.3902.4101.1.6.3.7
alarmServerityExcludeFilter
.1.3.6.1.4.1.3902.4101.1.6.3.8
alarmOperation
.1.3.6.1.4.1.3902.4101.1.7
syncAlarm
.1.3.6.1.4.1.3902.4101.1.7.1
alarmTableFilter
.1.3.6.1.4.1.3902.4101.1.7.2
alarmTrapEnable
.1.3.6.1.4.1.3902.4101.1.7.3
clearAlarm
.1.3.6.1.4.1.3902.4101.1.7.4
csIRPInfo
1.3.6.1.4.1.3902.4101.4.1
6-2
SJ-20120321105331-012|2012-05-10(R1.1)
Chapter 6 OID List
MIB Node Name
MIB Leave Name
OID
csIRPVersion
1.3.6.1.4.1.3902.4101.4.1.1
csIRPHeartbeatPeriod
1.3.6.1.4.1.3902.4101.4.1.2
csNotificationProfile
1.3.6.1.4.1.3902.4101.4.2.1
heartbeatNotification
1.3.6.1.4.1.3902.4101.4.2.1.1
Note:
MIB file contains all the information of the U31 R22 northbound SNMP interface. Refer
to SNMP Interface Standards to acquire the released interface information of the current
U31 R22 unified northbound SNMP interface.
6-3
SJ-20120321105331-012|2012-05-10(R1.1)
6-4
SJ-20120321105331-012|2012-05-10(R1.1)
Figures
Figure 1-1 Position in the Network Management System .......................................... 1-2
Figure 1-2 Structure of the Unified Northbound SNMP Interface .............................. 1-6
Figure 1-3
Alarm Management Service Architecture of the Unified Northbound

SNMP Interface ..................................................................................... 1-8
Figure 1-4 Packet Format of IP Data......................................................................... 1-9

Figure 1-5 Frame Format of SNMP Packets ........................................................... 1-10
Figure 2-1
Configuration Flow of SNMP Interface ................................................... 2-2
Figure 3-1 Interconnection Scenario ......................................................................... 3-2

Figure 3-2 MIB Browser Window............................................................................... 3-6
Figure 3-3 Navigation Tree After Loading MIB Files ................................................. 3-7
Figure 3-4 Get Operation Response ........................................................................ 3-9
Figure 3-5
Received Alarm Information .................................................................. 3-10
Figure 5-1 Processing Flow ...................................................................................... 5-2

Figure 5-2 Processing Flow ...................................................................................... 5-4
Figures
Tables
Table 1-1 TMF Standards Followed by U31 R22 Unified Northbound SNMP
Interface................................................................................................... 1-1
Table 1-2 Function List of the Unified Northbound SNMP Interface ........................... 1-4
Table 1-3 Specifications of U31 R22 Unified Northbound SNMP Interface ................ 1-5
Table 1-4 Component Description ............................................................................. 1-7
Table 1-5 PDU Type................................................................................................ 1-11
Table 1-6 Error Status Description .......................................................................... 1-11
Table 1-7 Trap Type Description ............................................................................. 1-12
Table 2-1 SNMP Agent Parameter Description ......................................................... 2-4
Table 2-2
V2C Version Parameter Description ........................................................ 2-6
Table 2-3 V3 Version Parameter Description ............................................................ 2-8

Table 3-1 Interconnection Information between SNMP and the Integrated
NMS ........................................................................................................ 3-2
Table 3-2 SNMP Agent Parameter Description ......................................................... 3-4
Table 3-3
V2C Version Parameter Description ........................................................ 3-4
Table 3-4 Basic Parameters Configuration ............................................................... 3-7

Table 4-1 Log Directories of Different Installation Scales .......................................... 4-4
III
Tables
Glossary
DCN
- Data Communications Network
IP
- Internet Protocol
IRP
- Integration Reference Point
MIB
- Management Information Base
NE
- Network Element
OMC
- Operation & Maintenance Center
OSS
- Operation Support System
OSS
- Operation Support Subsystem
PDU
- Protocol Data Unit
SNMP
- Simple Network Management Protocol
UDP
- User Datagram Protocol

012-NetNumen U31 R22 Northbound Interface User Guide (SNMP Interface)

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

012-NetNumen U31 R22 Northbound Interface User Guide (SNMP Interface)

Diunggah oleh

Hak Cipta:

Format Tersedia

NetNumen U31 R22

Unified Network Management System

Northbound Interface User

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

NetNumen U31 R22 (V12.11.40P01) Issued.

Added the "Manageable NEs" section.

Updated the "SNMP Management Frame", "Six Kinds of

Updated the "Configuring the Unified Northbound SNMP

Serial Number: SJ-20120321105331-012

NetNumen U31 R22 (V12.11.40) Issued.

About This Manual

What Is in This Manual

Describes the concept, standards, position in the network, interface

functions, interface performance, and related concepts of the U31 R22

the Unified Northbound

northbound SNMP interface.

Describes the interconnection procedure between the U31 R22 unified

northbound SNMP interface and the integrated NMS by examples, the

Unified SNMP Interface

usage guidelines about relevant documents.

With the Integrated NMS

the Unified Northbound

R22 unified northbound SNMP interface.

Describes the common troubleshooting methods of the U31 R22 unified

Chapter 6, OID List

performance, or other unpredictable result may occur if you

2. Manual Usage Convention

Chapter 2 Configuring the Unified Northbound SNMP Interface ........... 2-1

Chapter 3 Interconnecting the Unified SNMP Interface With the

Chapter 4 Maintaining the Unified Northbound SNMP Interface ........... 4-1

4.3 Checking Password and Right Securities ............................................................ 4-2

Chapter 5 Troubleshootings ..................................................................... 5-1

Chapter 6 OID List ...................................................................................... 6-1

1.1 Interface Overview

It is the first officially released protocol version.

SNMPv2 expands some functions in protocol operations on the basis of SNMPv1.

ZTE Proprietary and Confidential

NetNumen U31 R22 Northbound Interface User Guide (SNMP Interface)

SNMPv3 focuses on enhancing the functions of protocol security

1.3 Position in the Network

OSS: Operation Support

EMS: Network Element

1.4 Manageable NEs

ZTE Proprietary and Confidential

Chapter 1 System Overview

Government and Enterprise Network Products

ZTE Proprietary and Confidential

NetNumen U31 R22 Northbound Interface User Guide (SNMP Interface)

ZXR10 5950-28TM, ZXR10 5950-28SM, ZXR10 5950-52TM, ZXR10 5950-28PM,

1.5 Interface Functions

Reporting trap events

This function initially sends alarm events created on the Network

Querying the alarm IRP

Querying the heartbeat IRP

This function enables users to perform the get operation upon

Querying and setting the

operation upon heartbeat objects on the EMS from the OSS, to

Querying current alarms

Querying the number of

Deleting current alarms

This function enables users to perform the operation upon alarm

Setting alarm processing