0% found this document useful (0 votes)
217 views14 pages

SNMP Northbound Interface Variance (NetNumen U31 R07 V12.11.20-Netnumen U31 R07 V12.12.20.P02)

Uploaded by

Rodolfo Squique
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
217 views14 pages

SNMP Northbound Interface Variance (NetNumen U31 R07 V12.11.20-Netnumen U31 R07 V12.12.20.P02)

Uploaded by

Rodolfo Squique
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 14

SNMP Northbound Interface

Variance(NetNumen U31 R07


V12.11.20-Netnumen U31 R07
V12.12.20.P02)
SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

LEGAL INFORMATION

By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you
do not agree to the following terms, please notice that you are not allowed to use this document.

Copyright © 2022 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure 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.

and are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyone’s access to this document should not be construed as granting,
by implication, estopped or otherwise, any license or right to use any marks appearing in the
document.

The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual,
relevant contract or laws and regulations in relevant country (countries).

This document is provided “as is” and “as available”. Information contained in this document is
subject to continuous update without further notice due to improvement and update of ZTE
CORPORATION’s products and technologies.

ZTE CORPORATION

Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website
http://support.zte.com.cn
:
Email: [email protected]

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

Revision History

Product Version Document Version Serial Number Reason for Revision


NetNumen U31 R07
1.0
V12.12.20.P02

Author

Prepared
Date Document Version Reviewed by Approved by
by
2012-7-20 1.0 Bin Lu

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

Applicable to:

Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ Knowledge and skills Reference material
1
2
3

Follow-up document: After reading this document, you may need the following information
SEQ Reference material Information
1
2
3

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

TABLE OF CONTENTS

1 Version..............................................................................................................1
1.1 Functional Changes...........................................................................................1
1.2 Changes of the MIB File.....................................................................................2
1.3 Compatibility Problems......................................................................................5
1.3.1 Sequence Change of Fields in TRAP.................................................................5
1.3.2 Trap Content......................................................................................................5
1.4 Related Issues...................................................................................................7
1.5 MIB.................................................................................................................... 9

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

TABLES

Table 1-1 Functional Changes................................................................................................1


Table 1-2 Changes of the MIB File.........................................................................................2
Table 1-3 Trap Content........................................................................................................... 6
Table 1-4 Returned Values of the Set Operation....................................................................7
Table 1-5 Value Range of Table Filtering Parameters............................................................8
Table 1-6 Returned Values of the SET Operation...................................................................8
Table 1-7 Returned Values of the SET Operation...................................................................8

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

1 Version
NetNumen U31 R07 V12.11.20-Netnumen U31 R07 V12.12.20.P02

1.1 Functional Changes

Table 1-1 Functional Changes

Functio Descripti
Remarks
n on
SNMP
The TRAP version cannot be modified by modifying the ums-server\
TRAP
procs\ppus\uca.ppu\uca-fm-naf-snmp.pmu\uca-osf-fm-naf-snmp.par\
version Modified
conf\ uca-fm-naf-snmp-engines.xml file. The TRAP version can only
adjustme
be modified in the configuration center.
nt
Add the
following This function will add a new MIB node.
function: The system can perform a set operation on the clearAlarm node
Newly (.1.3.6.1.4.1.3902.4101.1.7.4.0) under the alarmOperation object
clearing
added
alarms by defined in the MIB file of the SNMP interface, to batch clear alarms
ID and according to the conditions.
severity
Add the This function will add a new MIB node.
following
The system can perform a set operation on the alarmTableFilter
function:
Newly node (.1.3.6.1.4.1.3902.4101.1.7.2.0) defined in the MIB file of the
setting
added SNMP interface to set the table filtering conditions,and the pre-
the table
defined conditions used to filter TRAP by MOC will take effect for the
filtering
conditions SNMP alarm table.

This function will add a new MIB node.


Add the
alarm Newly The system can perform a set operation on the alarmTrapEnable
TRAP added node ((.1.3.6.1.4.1.3902.4101.1.7.3.0)) under the alarmOperation
switch object defined in the MIB file of the SNMP interface, to start or stop
the reporting of alarm traps.
Central
northboun Central northbound configuration is added in the configuration
Newly
d center. All fm SNMP parameters are managed in the configuration
added
configurat center.
ion
The OMC ALARM alarm type is added. The EMS alarms’ event type
Alarm will be converted into this type.
Modified
Type Add Please refer to section 6.2.10 in <<NetNumen Northbound Alarm
SNMP Interface Interconnection Specifications>>
Alarm The alarm severity used in the reported Trap message is the same
Modified
severity as the alarm original severity

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

1.2 Changes of the MIB File

Table 1-2 Changes of the MIB File

Netnumen U31
NetNumen U31
Content R07 Description
R07 V12.11.20
V12.12.20.P02
Add the EMS system
TypeOfEvent omcAlarm(11)
type.
MAX-ACCESS MAX-ACCESS read- Modify the access
systemDN
accessible-for-notify only right of the node
Add the EMS system
TypeFilter omcAlarm(11)
type
SYNTAX SYNTAX
alarmNeIP DisplayString (SIZE DisplayString (SIZE Modify the length
(0..15)) (0..60))
Enable the alarm
TRAP function.
The system can
perform a set
operation on the
alarmTrapEnable
node
alarmTrapEnable None Newly added ((.1.3.6.1.4.1.3902.4
101.1.7.3.0)) under
the alarmOperation
object defined in the
MIB file of the SNMP
interface, to start or
stop the reporting of
alarm traps.
Add the following
function: setting table
filtering conditions.
The system can
perform a set
operation on the
alarmTableFilter None Newly added alarmTableFilter
node
(.1.3.6.1.4.1.3902.41
01.1.7.2.0) defined in
the MIB file of the
SNMP interface to
set the table filtering
conditions.
The function of alarm
clearance by ID and
severity.
The system can
perform a set
clearAlarm None Newly added operation on the
clearAlarm node
(.1.3.6.1.4.1.3902.41
01.1.7.4.0) under the
alarmOperation
object defined in the

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

MIB file of the SNMP


interface, to batch
clear alarms
according to the
conditions.
Add
sendNotificationId(Se
Add the following quence number of
attributes: the current trap
alarmNew
sendNotificationId, message),
alarmComment, alarmComment(Alar
m comment) in the
reported attributes.

Add the following Add


attributes: alarmComment(Alar
alarmCleared
m comment) in the
alarmComment, reported attributes.
Add
alarmComment(Alar
Add the following
m comment),
attributes:
alarmAckChange None alarmOtherInfo(Cust
alarmComment,
om alarm attributes
alarmOtherInfo
(custom1-10)) in the
reported attributes.
Add
Add the following alarmOtherInfo(Cust
alarmCommentChan
None attributes: om alarm attributes
ge
alarmOtherInfo (custom1-10)) in the
reported attributes.
Add
sendNotificationId(Se
quence number of
the current trap
message),
lastSendNotificationI
d(Sequence number
of the last trap
message),
Add the following
systemDN(System
attributes:
DN),
sendNotificationId,
timeZoneID(Time
lastSendNotificationId
zone ID of the
,
alarm’s occurrence
systemDN,
alarmSync None time),
timeZoneID,
timeZoneOffset(Time
timeZoneOffset,
zone offset of the
dSTSaving,
alarm’s occurrence
aid,
time),
alarmComment,
dSTSaving(DST
alarmOtherInfo
offset of the alarm’s
occurrence time),
aid(Alarm AID),
alarmComment(Alar
m comment),
alarmOtherInfo(Cust
om alarm attributes
(custom1-10)) in the
reported attributes.
alarmMeasure alarmMeasure alarmComment The variable name of
the alarm comment

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

is changed into
alarmComment.
messageInfo
NOTIFICATION-
TYPE
OBJECTS {
systemDN, It is a newly added
messageCode message body. If
} exceptions occur
STATUS current during the sending of
messageInfo None
DESCRIPTION synchronization
"This requests, this
notification is sent message will be
when ems on an sent.
abnormal situation."
::=
{ alarmNotificationPro
file 7 }
alarmNotificationMan
alarmNotificationMan datoryGroup
datoryGroup NOTIFICATION-
NOTIFICATION- GROUP
GROUP
NOTIFICATIONS {
NOTIFICATIONS alarmNew, Add types of
alarmNotificationMan
{ alarmNew, alarmCleared, messageInfo
datoryGroup
alarmCleared, alarmAckChange, messages.
alarmAckChange, alarmCommentChan
alarmCommentChan ge,
ge, alarmListRebuild,
alarmListRebuild, alarmSync,
alarmSync } messageInfo
}

1.3 Compatibility Problems

1.3.1 Sequence Change of Fields in TRAP

All the following changes are incompatible.

 The following fields are added in the alarm reporting traps:

sendNotificationId(Sequence number of the current trap message),alarmComment(Alarm


comment)

 The following fields are added in the alarm clearing traps:

alarmComment(Alarm comment)

 The following fields are added in the alarm acknowledging traps:

alarmComment(Alarm comment),alarmOtherInfo(Custom alarm attributes (custom1-10))

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

 The following fields are added in the alarm commenting traps:

alarmOtherInfo(Custom alarm attributes (custom1-10))

 The following fields are added in the alarm synchronizing traps:

sendNotificationId(Sequence number of the current trap


message),lastSendNotificationId(Sequence number of the last trap
message),systemDN(System DN),timeZoneID(Time zone ID of the alarm’s occurrence
time),timeZoneOffset(Time zone offset of the alarm’s occurrence time), dSTSaving(DST offset
of the alarm’s occurrence time), aid(Alarm AID),alarmComment(Alarm
comment),alarmOtherInfo(Custom alarm attributes (custom1-10))

1.3.2 Trap Content


In the new version, the actual sequence of fields in alarm reporting traps, alarm clearing
traps, acknowledgement status changing traps, comment changing traps, and
synchronization messages is as follows, Please parse the fields according to OID or the
sequence in the following table. Otherwise, incompatibility will occur. (Note: It is strongly
suggested that you use OID to parse the fields. In this way, when OIDs are added or
modified and consequently the sequence of MIB changes after the update of EMS, NMS
can still be compatible with the new OIDs. If you parse the fields according to the
sequence in the MIB file, when OIDs are added or modified and consequently the
sequence of MIB changes, NMS cannot be compatible with the changes, unless you
modify the NMS program.)

Table 1-3 Trap Content

No. Name OID


1 .1.3.6.1.2.1.1.3.0
2 .1.3.6.1.6.3.1.1.4.1.0
3 alarmEventTime .1.3.6.1.4.1.3902.4101.1.3.1.3
4 sendNotificationId .1.3.6.1.4.1.3902.4101.1.1.2
5 lastSendNotificationId .1.3.6.1.4.1.3902.4101.1.1.4
6 systemDN .1.3.6.1.4.1.3902.4101.1.1.3
7 alarmCode .1.3.6.1.4.1.3902.4101.1.3.1.11
8 alarmManagedObjectInstance .1.3.6.1.4.1.3902.4101.1.3.1.2
9 alarmEventType .1.3.6.1.4.1.3902.4101.1.3.1.4
10 alarmProbableCause .1.3.6.1.4.1.3902.4101.1.3.1.5
11 alarmPerceivedSeverity .1.3.6.1.4.1.3902.4101.1.3.1.6
12 alarmSpecificProblem .1.3.6.1.4.1.3902.4101.1.3.1.7
13 alarmAdditionalText .1.3.6.1.4.1.3902.4101.1.3.1.8
14 alarmNetype .1.3.6.1.4.1.3902.4101.1.3.1.12
15 alarmIndex .1.3.6.1.4.1.3902.4101.1.3.1.9
16 alarmId .1.3.6.1.4.1.3902.4101.1.3.1.1

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

17 alarmCodeName .1.3.6.1.4.1.3902.4101.1.3.1.14
alarmManagedObjectInstanceNam
18 .1.3.6.1.4.1.3902.4101.1.3.1.15
e
19 alarmSystemType .1.3.6.1.4.1.3902.4101.1.3.1.16
20 alarmNeIP .1.3.6.1.4.1.3902.4101.1.3.1.17
21 alarmAck .1.3.6.1.4.1.3902.4101.1.3.1.18
22 cleiCode .1.3.6.1.4.1.3902.4101.1.3.1.19
23 timeZoneID .1.3.6.1.4.1.3902.4101.1.3.1.20
24 timeZoneOffset .1.3.6.1.4.1.3902.4101.1.3.1.21
25 dSTSaving .1.3.6.1.4.1.3902.4101.1.3.1.22
26 aid .1.3.6.1.4.1.3902.4101.1.3.1.23
27 id .1.3.6.1.4.1.3902.4101.1.3.1.24
28 alarmMocObjectInstance .1.3.6.1.4.1.3902.4101.1.3.1.26
29 alarmComment .1.3.6.1.4.1.3902.4101.1.3.1.10
30 alarmOtherInfo .1.3.6.1.4.1.3902.4101.1.3.1.25

1.4 Related Issues


For the following three nodes (syncAlarm, alarmTableFilter, and clearAlarm), the returned
value and the configured value of the SET operation are different. This is different from the SNMP
specifications. In the SNMP specifications, it is required that the returned value and the configured
value of the SET operation should be the same.

i. syncAlarm

a) Synchronizing Alarms Based on the NE Position. The parameter format


of the SET operation is as follows: “position:pos1,pos2;”(pos1,pos2,…
posN in the parameter represent NE IDs defined on EMS.)

b) The returned values of the set operation are as follows:

Table 1-4 Returned Values of the Set Operation

Returned
Value Type Explanation
Value
0 INTEGER The setting is successful.
The server is busy. Please try
1 INTEGER
again later.
The server is processing the
2 INTEGER
previous request.
3 INTEGER Condition error
4 INTEGER Synchronization is allowed.
5 INTEGER TRAP reporting is disabled.

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

ii. alarmTableFilter

a) Setting Table Filtering Conditions.

The parameter format of the SET operation is as follows:

Example 1:

PerceivedSeverity:1,3; SystemType:6,11;TypeOfEvent:1,2;

ProbableCause:1001,1002;NEPosition: COMM:EMS=606531163267;

Example 2:

PerceivedSeverity:1,3; TypeOfEvent:1,2;

ProbableCause:1001,1002;NEPosition:COMM:EMS=0806164728805,Commo
nTopoObject=123

The parameter description and the value range are listed below:

Table 1-5 Value Range of Table Filtering Parameters

Condition Value Range


PerceivedSeverity [1,6]
TypeOfEvent [1,10]
SystemType System type
ProbableCause Northbound alarm code

b) Returned values of the SET operation and their descriptions are as


follows:

Table 1-6 Returned Values of the SET Operation

Returned Value Value Type Description


Current table filtering The operation is
STRING
conditions successful.
5, 6, 8, 9 INTEGER Condition error
7 INTEGER System error

iii. clearAlarm

a) Clearing Alarms by Alarm Severity and ID. The parameter format of the
SET operation, for example, “PerceivedSeverity:1,5; Id:156” means to
clear alarms whose alarm severity is 1 or 5 and whose alarm ID is 156.

b) The returned values of the SET operation:

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


SNMP Northbound Interface Variance(NetNumen U31 R07 V12.11.20-Netnumen U31 R07
V12.12.20.P02) Internal Use Only▲

Table 1-7 Returned Values of the SET Operation

Parameter Value Value Type Description


0 STRING The setting is successful.
1 INTEGER System error
2 INTEGER Condition error

1.5 MIB

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.

You might also like