U2000 Northbound CORBA Interface Alarm Filter Guide

U2000
V200R016C10
Northbound CORBA Interface Alarm

Filter Guide
Issue
02
Date
2016-03-20
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2016-03-20)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
U2000
Northbound CORBA Interface Alarm Filter Guide
About This Document
About This Document
Scope
This document describes operations related to the northbound CORBA interface alarm filter
function.
Product Versions
The following table lists the product version related to this document.
Product Name
Version
U2000
V200R016C10
Intended Audience
This document is intended for:
Network management engineers
Change History
02 (2016-03-20)
This is 02 version for V200R016C10. Compared with issue 01 (2016-02-25) of
V200R016C10, no change.
01 (2016-02-25)
This is 01 version for V200R016C10. Compared with issue Draft A (2015-12-30) of
V200R016C10, no change.
Issue 02 (2016-03-20)

ii
U2000
About This Document
Draft A (2015-12-30)
This is a draft for V200R016C10. Compared with issue 01 (2015-09-20) of V200R016C00,
no change is made.
Organization
1 Introduction to Northbound CORBA Interface
This introduction defines the Northbound CORBA interface provided by the U2000 and
describes the functions of the Northbound CORBA interface.
2 Configuring the Northbound CORBA Interface Alarm Filter
The U2000 northbound CORBA interface allows you to filter alarms reported in real time by
alarm RAT, NE type, and alarm ID.
3 Appendix
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
General Conventions
Issue 02 (2016-03-20)

iii
U2000
About This Document
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
Issue 02 (2016-03-20)

iv
U2000
About This Document
The keyboard operations that may be found in this document are defined as follows.
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl

+Alt+A means the three keys should be pressed
concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 02 (2016-03-20)
Action
Description
Click
Select and release the primary mouse button without

moving the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.

U2000
Contents
Contents
About This Document.....................................................................................................................ii
1 Introduction to Northbound CORBA Interface...................................................................... 1
1.1 Definition of Northbound Interface................................................................................................................................ 2
1.2 Definition of Northbound CORBA Interface................................................................................................................. 2
2 Configuring the Northbound CORBA Interface Alarm Filter............................................. 6

2.1 Introduction to the Filter Criteria Configuration File..................................................................................................... 7
2.2 Configuring the Event Alarm Forwarding or Filter........................................................................................................8
2.3 Configuring the Fault Alarm Forwarding or Filter.......................................................................................................10
3 Appendix....................................................................................................................................... 12
3.1 Filter Criteria Configuration Instances......................................................................................................................... 13
3.2 Mapping Between NE Type IDs and NE Type Names.................................................................................................14
3.3 Mapping Between Alarm RAT IDs and NE Type IDs................................................................................................. 24
Issue 02 (2016-03-20)

vi
U2000
Introduction to Northbound CORBA

Interface
About This Chapter

This introduction defines the Northbound CORBA interface provided by the U2000 and
describes the functions of the Northbound CORBA interface.
1.1 Definition of Northbound Interface
The northbound interface links the element management system (EMS) and the NMS.
1.2 Definition of Northbound CORBA Interface
The Northbound CORBA interface is one of the Northbound interfaces. The Northbound
CORBA interface conforms to the CORBA protocol, SFTP/FTP protocol, and 3GPP
specifications.
Issue 02 (2016-03-20)

U2000
1.1 Definition of Northbound Interface

The northbound interface links the element management system (EMS) and the NMS.
The NMS obtains information about the network elements (NEs) managed by the EMS and
delivers operation commands through the northbound interface. The NE information includes
the alarm, configuration, performance, and inventory data. Figure 1-1 shows the position of
the northbound interface in the network.
Figure 1-1 Position of the northbound interface
In the communication network, the U2000 provides the alarm, configuration, performance,
and inventory data of NEs to the NMS through the northbound interface.
1.2 Definition of Northbound CORBA Interface

The Northbound CORBA interface is one of the Northbound interfaces. The Northbound
CORBA interface conforms to the CORBA protocol, SFTP/FTP protocol, and 3GPP
specifications.
Interface Protocol
Table 1-1 describes the related information on interface protocol.
Issue 02 (2016-03-20)

U2000
Table 1-1 Interface protocol

Protocol
Details
CORBA
The design of network management interfaces adopts the CORBA

technology for interface definition. The CORBA technology uses
the IDL language to define the interface information model and
also uses the IIOP communication protocol stack.
The design of the network management interfaces complies with
the following CORBA standards:
l OMG ORB 2.3 standard
l OMG Notification Service 1.0 standard
l TAO 2.1.0 Version
NOTE
l OMG represents the Object Management Group.
l ORB represents the Object Request Broker.
SFTP/FTP
The file transfer mode in the management interface uses the

SFTP/FTP and the SSH and FTP protocol stack.
NOTICE
Using SFTP is recommended because of its higher security than FTP.
Issue 02 (2016-03-20)

U2000
Protocol
Details
3GPP
The CORBA interface complies with the following 3GPP

protocols:
l 3GPP TS 32.111-1 v6.0.0 Fault Management; Part 1: 3G fault
management requirements
l 3GPP TS 32.111-2 v6.0.0 Fault Management; Part 2: Alarm
Integration Reference Point (IRP): Information Service (IS)
l 3GPP TS 32.111-3 v6.0.0 Fault Management; Part 3: Alarm
Integration Reference Point (IRP): Common Object Request
Broker Architecture (CORBA) Solution Set (SS)
l 3GPP TS 32.352 v6.0.0 Telecommunication management;
Communication Surveillance (CS) Integration Reference Point
(IRP): Information Service (IS)
Performance Management (PM) Integration Reference Point
(IRP): Requirements
(IRP): Information Service (IS)
(IRP): Common Object Request Broker Architecture
(CORBA) Solution Set (SS)
Configuration Management (CM); Basic CM Integration
Reference Point (IRP): Requirements
Reference Point (IRP): Information Service (IS)
Reference Point (IRP): Common Object Request Broker
Architecture (CORBA) Solution Set (SS)
Configuration Management (CM); Bulk CM Integration
Reference Point (IRP): Requirements
Reference Point (IRP): Information Service (IS)
Reference Point (IRP): eXtensible Markup Language (XML)
file format definition
Issue 02 (2016-03-20)

U2000
Protocol
Details
Configuration Management (CM); Kernel CM: Requirements
Configuration Management (CM); Kernel CM Information
Service (IS)
Configuration Management (CM); Kernel CM Integration
Issue 02 (2016-03-20)

U2000
2 Configuring the Northbound CORBA Interface Alarm

Filter
Configuring the Northbound CORBA

Interface Alarm Filter
About This Chapter

The U2000 northbound CORBA interface allows you to filter alarms reported in real time by
alarm RAT, NE type, and alarm ID.
2.1 Introduction to the Filter Criteria Configuration File
The U2000 provides the CORBA filter criteria configuration file /opt/oss/server/etc/
IRPService/AlarmFilter.xml. Users can modify the configuration file to set filter criteria for
alarm forwarding.
2.2 Configuring the Event Alarm Forwarding or Filter
This section describes how to modify the AlarmFilter.xml configuration file to set filter
criteria for CORBA event alarms.
2.3 Configuring the Fault Alarm Forwarding or Filter
To modify filter criteria to filter CORBA fault alarms, you can modify the filter criteria
configuration file AlarmFilter.xml for CORBA alarms.
Issue 02 (2016-03-20)

U2000

Filter
2.1 Introduction to the Filter Criteria Configuration File

The U2000 provides the CORBA filter criteria configuration file /opt/oss/server/etc/
IRPService/AlarmFilter.xml. Users can modify the configuration file to set filter criteria for
alarm forwarding.
Scope
The CORBA filter criteria configuration file is divided into two parts:
l
Event alarm part.

Includes parameters in the <AlmCategory> node and restrictions of event alarms to be
forwarded.
Fault alarm part.

Includes contents in the <FaultCategory> node and restrictions of forwarded fault
alarms.
Filter Criteria Setting

l
In event alarm and fault alarm parts, you can configure multiple filter configuration
items <Netype name=""></Netype> or <Rattype name=""></Rattype>. In each <Netype
name=""></Netype> or <Rattype name=""></Rattype>, you can configure multiple
alarm IDs. For detailed operations, see 3.1 Filter Criteria Configuration Instances.
Event alarm and fault alarm parts contain a maximum of 10 <Netype name=""></
Netype> or <Rattype name=""></Rattype> (The sum of two configuration items is equal
to or less than 10.), including reference items with the same name, and a maximum of
100 AlmId. If you need to exceed the upper limit, contact OSS maintenance personnel.
By default, the AlmId has not been configured. If isSend is set to 1, all alarms of the NE
are forwarded. If isSend is set to 0, alarms are not forwarded.
If Netype name and Rattype name are configured, alarms meeting both requirements
are forwarded.
If the configuration file does not exist, all alarms are forwarded to the NMS.
Table 2-1 Configuration items in the CORBA filter criteria configuration file
Issue 02 (2016-03-20)
Parameter
Name
Descripti
on
Configuration References
Netype
name
NE type ID
Each Netype name uniquely identifies an NE type ID. For

details, see Table 3-1.
categoryId
Alarm type
ID
The parameter indicates the alarm type. By default, 1 indicates

a fault alarm and 3 indicates an event alarm.


Filter
U2000
Parameter
Name
Descripti
on
Configuration References
AlmId
Alarm ID
Each NE alarm has a fixed alarm ID, indicating its alarm type.
An alarm ID used within a product uniquely identifies a fault
or event. You can obtain information about a fault, including
the alarm name, clearance advice, cause, and related
parameters, based on the alarm ID.
For details about the mapping between alarm IDs and alarm
names, see U2000 Help.
NOTICE
AlmId of fault and event alarms for an NE type use unified numbers.
You must specify AlmId for events in the event alarm part and for
faults in the fault alarm part of the configuration file.
Rattype
name
Alarm RAT
ID
Indicates the RAT of an alarm.

l 0: common alarm
l 1: GSM alarm
l 2: UMTS alarm
l 3: LTE alarm
l 4: COMM alarm
2.2 Configuring the Event Alarm Forwarding or Filter

This section describes how to modify the AlarmFilter.xml configuration file to set filter
criteria for CORBA event alarms.
Prerequisites
Log in to the U2000 server as user ossuser.
Context
Before setting the alarm filter, ensure that the northbound CORBA interface has been properly
installed. If not, switch to the U2000 environment where the CORBA interface is installed.
l
In an SLS system, you need to perform the following steps only on the master server.
In an HA or remote HA system, you need to perform the following steps only on the
active server.
In an ATAE cluster online remote HA system, you need to perform the following steps
on the master server at both active site and standby sites. In a VM cluster system, you
need to perform the following steps on the master server at the active site.
You can modify the configuration file only by running commands.
Procedure
Step 1 Go to the U2000 installation directory.
The default installation directory is /opt/oss/server.
Issue 02 (2016-03-20)

U2000

Filter
By default, run the following command:

$ cd /opt/oss/server
Step 2 Run the environment variable script.
$ . /opt/oss/server/svc_profile.sh
Step 3 Check whether the CORBA interface is properly installed.
$ displayCorbaNBI
If the following information is displayed, the CORBA interface is properly installed.
-------Current Version-------CorbaNBI
NBIV..
Available CorbaNBI List:
Version
Specification
----------------------------NBIV1.2.0
International
NBIV1.5.0
TDSCDMA
NBIV1.6.0
TDSCDMA3.2.0
NBIV1.7.0
EPS1.1.0
NBIV2.0.0
CDMA
NBIV2.1.0
GSM/GPRS
NBIV2.2.0
WCDMA
NBIV2.3.0
LTE/EPC
NBIV3.0.0
CDMA2.1
NBIV3.1.0
CDMA3.0
NBIV3.3.1
CDMA3.1
The displayed information indicates the version of the northbound CORBA interface used in
the current system. If the interface is not installed, the preceding information is not displayed.
If the CORBA interface is improperly installed, you need to reinstall it. For detailed
operations, see U2000 Northbound CORBA Interface Installation and Maintenance Guide.
Step 4 Edit the configuration file.
Run the following command:
$ vi /opt/oss/server/etc/IRPService/AlarmFilter.xml
Edit the field <AlmCategory categoryId="3" isSend=="0"></AlarmCategory> in the event
alarm part of configuration file.
1.
Set the alarm forwarding parameter isSend: If isSend is set to 0, alarms are not
forwarded. If isSend is set to 1, alarms are forwarded. isSend is set to 0 by default.
NOTE
If isSend to set to 1 and NeType is not set, no alarm is forwarded.
2.
Netype name is used to set the NE type. For details about the mapping between NE type
names and NE type IDs, see Table 3-1.
AlmId indicates the ID of the event alarm to be forwarded. If it is not set, all event
alarms of the NE type are forwarded.
3.
Rattype name is used to set the alarm RAT. For details about the mapping between RAT
type names and NE type IDs, see Table 3-2.
4.
Save the modification and exit.
Issue 02 (2016-03-20)

U2000

Filter
Step 5 Run the $ nbi_adm -cmd restart CORBA command to restart the service so that the alarm
filter settings take effect.
----End
2.3 Configuring the Fault Alarm Forwarding or Filter

To modify filter criteria to filter CORBA fault alarms, you can modify the filter criteria
configuration file AlarmFilter.xml for CORBA alarms.
Prerequisites
Log in to the U2000 server as user ossuser.
Context
Before setting the alarm filter, ensure that the northbound CORBA interface has been properly
installed. If not, switch to the corresponding U2000 environment where the CORBA interface
is installed.
l
In an SLS system, you need to perform the following steps only on the master server.
In an HA or remote HA system, you need to perform the following steps only on the
active server.
In an ATAE cluster online remote HA system, you need to perform the following steps
on the master server at both active site and standby sites. In a VM cluster system, you
need to perform the following steps on the master server at the active site.
You can modify the configuration file only by running commands.
Procedure
Step 1 Go to the U2000 installation directory.
The default installation directory is /opt/oss/server.
By default, run the following command:
$ cd /opt/oss/server
Step 2 Run the environment variable script.
$ . /opt/oss/server/svc_profile.sh
Step 3 Check whether the CORBA interface is properly installed.
$ displayCorbaNBI
If the following information is displayed, the CORBA interface is properly installed.
-------Current Version-------CorbaNBI
NBIV..
Available CorbaNBI List:
Version
Specification
----------------------------NBIV1.2.0
International
NBIV1.5.0
TDSCDMA
NBIV1.6.0
TDSCDMA3.2.0
NBIV1.7.0
EPS1.1.0
Issue 02 (2016-03-20)

10
U2000
NBIV2.0.0
NBIV2.1.0
NBIV2.2.0
NBIV2.3.0
NBIV3.0.0
NBIV3.1.0
NBIV3.3.1

Filter
CDMA
GSM/GPRS
WCDMA
LTE/EPC
CDMA2.1
CDMA3.0
CDMA3.1
The displayed information indicates the version of the northbound CORBA interface used in
the current system. If the interface is not installed, the preceding information is not displayed.
If the CORBA interface is improperly installed, you need to reinstall it. For detailed
operations, see U2000 Northbound CORBA Interface Installation and Maintenance Guide.
Step 4 Edit the configuration file.
Run the following command:
$ vi /opt/oss/server/etc/IRPService/AlarmFilter.xml
Edit the field <FaultCategory categoryId="1" isSend="1"></FaultCategory> in the fault alarm
part of configuration file.
1.
Set the alarm forwarding parameter isSend: If isSend is set to 0, alarms are not
forwarded. If isSend is set to 1, alarms are forwarded. In the fault alarm part, isSend is
set to 1 by default.
NOTE
If isSend to set to 1 and NeType is not set, all alarms are forwarded by default.
2.
Netype name is used to set the NE type. For details about the mapping between NE type
names and NE type IDs, see Table 3-1.
AlmId indicates the ID of the fault alarm to be forwarded. If it is not set, all fault alarms
of the NE type are forwarded.
3.
Rattype name is used to set the alarm RAT. For details about the mapping between RAT
type names and NE type IDs, see Table 3-2.
4.
Save the modification and exit.
Step 5 Run the $ nbi_adm -cmd restart CORBA command to restart the service so that the alarm
filter settings takes effect.
----End
Issue 02 (2016-03-20)

11
U2000
3 Appendix
Appendix
About This Chapter

3.1 Filter Criteria Configuration Instances
3.2 Mapping Between NE Type IDs and NE Type Names
3.3 Mapping Between Alarm RAT IDs and NE Type IDs
Issue 02 (2016-03-20)

12
U2000
3 Appendix
3.1 Filter Criteria Configuration Instances

Configuring Multiple Alarms IDs for the Same NE Type
Filter criteria: Forward the ALM-25890 and ALM-26212 event alarms of the BTS3900 LTE.
The configuration instance is as follows:
<AlmCategory categoryId="3" isSend="1">
<!BTS3900 LTE-->
<Netype name="8200">
<AlmId name="25890"/>
</Netype>
</AlmCategory>
Configuring Different NE Types for the Same Alarm Type

Filter criteria: Forward the ALM-21814 event alarm of BSC6900 GU and the ALM-25890
event alarm of the BTS3900 LTE. The configuration instance is as follows:
<!BSC6900 GU -->
<Netype name="173">
</Netype>

</Netype>
</AlmCategory>
Configuring the Same NE Type for Different Alarm Types

Filter criteria: Forward the ALM-22863 event alarm and ALM-21814 fault alarm of BSC6900
GU. The configuration instance is as follows:

<Netype name="173">
</Netype>
</AlmCategory>
<FaultCategory categoryId="1" isSend="1">

<Netype name="173">
</Netype>
</FaultCategory>
Configuring Different NE Types for Different Alarm Types

Filter criteria: Forward the ALM-22863 event alarm of BSC6900 GU and the ALM-25600
fault alarm of the BTS3900 LTE. The configuration instance is as follows:

<Netype name="173">
Issue 02 (2016-03-20)

13
U2000
3 Appendix
</Netype>
</AlmCategory>

</Netype>
</FaultCategory>
Configuring Only the Alarm RAT

Filter criteria: Forward fault alarms whose RAT is GSM. The configuration instance is as
follows:

<Rattype name="1">
</Rattype>
</ FaultCategory>
Configuring the NE Type and Alarm RAT

Filter criteria: Forward fault alarms of the BSC6900 GU, whose RAT is GSM. The
configuration instance is as follows:

<Netype name="173">
</Netype>

<Rattype name="1">
</Rattype>
</ FaultCategory>
3.2 Mapping Between NE Type IDs and NE Type Names

Table 3-1 Mapping between NE type IDs and NE type names
Issue 02 (2016-03-20)
NE Type ID
NE Type Name
RNC
NodeB3812
SGSN
GGSN
CG
HLR
MSCServer
MGW
IWF
14
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
10
GGSN80
12
NodeB3806
13
NodeB3806A
14
NodeB3802C
15
unKnownNodeB
16
RouterNE
17
SwitchNE
18
BSC
20
PCU
21
MSC
22
HLR36
23
iMSC
24
rMSC
25
tMSC
26
GT800BSC
27
NodeB3812E
28
PCU33
29
MSCe
30
CMGW
31
CMSC
32
PDSN
34
RAC
35
GLMS
36
POC
37
CBSC
38
CT800GLMS
39
TSC
40
CBTS
41
RAU
42
PDSNR01

15
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
43
CHLR9820
44
SG7000
45
BSC6000
46
SPS
47
BSC6000BTS
49
MediaX3600
50
SNMP
52
AAA
53
HA
54
SGSN(UAG)
55
IMSOMU
56
CSCF
57
HSS
58
GTAS
59
RM
60
CCF
61
DOPRA
62
SBC
63
MRF
64
ATS
65
FIXMGW
66
FMCMGW
67
HLR-SC
68
HLR-DC
69
ASNGW
70
DBS3900 WiMAX
71
ICS
72
CSE
73
AIM
74
IPCTRX

16
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
75
MRFC
76
MRFP
77
MEDIAX
78
tMSCSvr
79
rMSCSvr
81
RRU
82
DBS3800
83
NodeB3812A
89
NodeB3812AE
90
DNSNE
91
DHCPNE
92
BTS3002C
93
BTS3012A
94
BTS3001C
95
BTS3012
96
BTS3012AE
97
BTS3006C
98
BTS3006A
99
BTS20
100
BTS22C
101
BTS3001CP
102
BTS30
103
BTS312
104
BTS3002E
105
BTS3012_II
106
AHR
107
IPSEC
108
ThirdPartyServer
109
TGW1000
110
DBS3836

17
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
111
NodeB3836
112
NodeB3836A
113
NodeB3836AE
114
DBS3900 GSM
115
M800MSC
116
RIM
117
CHLR-SC
118
CHLR-DC
119
GMS
120
SHLR
121
BTS3900 GSM
122
BTS3900A GSM
123
SOFTX3000
124
DBS3900 WCDMA
125
BTS3900 WCDMA
126
BTS3900A WCDMA
127
BTS3900AE WCDMA
128
HRC-BSC
133
CGPOMU
134
EIR
135
TD-RNC
136
TDNodeB
140
TDRRU
141
ETAS
142
BTS3036
143
BTS3036A
144
DBS3036
145
NodeB530
146
pBTS3701
149
OSN3500

18
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
150
Metro1000V3
151
UGC
152
ENUM
153
BITS
154
BOSS
155
Portal
159
DBS3900 LTE
160
BTS3900B GSM
161
BTS3900C GSM
162
BTS3900E GSM
163
MRMU
164
Mediation
167
SDC
168
MRS6100
169
USCDB
170
MiniMGW
171
BSC6900 GSM
172
BSC6900 UMTS
173
BSC6900 GU
174
USN
175
MME
176
SAEGW
177
UGW
180
SPG
181
UnknownTransmission
182
iGWB
184
RTN605
185
RTN610
186
RTN620
188
SAE-HSS

19
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
190
AP Manager
191
Eudemon
194
BTS3900
195
GbtsFunction
196
NodeBFunction
197
eNodeBFunction
198
CX600
199
BTS3900 eGSM
200
BTS3900 CL
201
ECO6910
202
UnknowneGBTS
203
CbtsFunction
204
RCS9880
205
DBS3900 IBS
206
BTS3803E WCDMA
208
BTS3203E LTE
301
VirtulNE
8193
GBTS
8194
BTS3900L WCDMA
8196
BTS3900L GSM
8199
BSC6810(R11+)
8200
BTS3900 LTE
8201
BTS3900A LTE
8202
BTS3702E
8203
BTS3702C
8206
BTS3701B
8207
DBS3900 FW
8212
UnknownWiMAXBTS
8213
BTS3900L LTE
8215
GBTS Group

20
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
8216
BSC6000(GSMR)
8217
BTS3901A LTE
8218
BTS3901E TDLTE
8219
BTS3202E
8222
SP_Node
8223
STP_Node
8225
3rdWiFi-5810
8226
BTS3902E WCDMA
8228
HPFCSwitch
8229
FWA3702C
8232
BTS3900AL WCDMA
8233
BTS3900AL LTE
8234
BTS3900AL GSM
8235
RCS
8236
TMS
8237
BTS3202B
8238
USU3900
8239
AAAOMD
8240
AAABMP
8241
ATAEHardware
8243
BTS3205E
8244
UIC
8245
SEQAnalyst
8246
NetProbe3010
8247
NetProbe9000
8248
NetProbe6200
8252
MAG9811
8301
MRP6600
8304
USU3910
8305
PICO BTS3900

21
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
8307
SVA-AC
8315
SVA3100
8316
SVA3200
8323
SVA-AG
9000
SE2600
9003
SIG
9004
OSG
9005
GUHLR
9006
CAS9910
9007
EER
9008
PGM
9013
GUEIR
9014
RCC
9015
ENS
9016
SIGServer
9017
RADIUSProxy
9018
GenexCNNastar
9019
ViewPoint
9020
LogicalHSS9860PoolNode
9034
UEIR
9035
UIM
9036
UNP
9037
UPCC
9038
DNS9816
9039
SANEX9510
9043
SigProbe
9044
SigProbeTDM
9046
VisualIP
9047
AGCF
9049
SVN

22
U2000
Issue 02 (2016-03-20)
3 Appendix
NE Type ID
NE Type Name
9050
AAU
9051
HSS9860
8320
MBTS
9057
BTS3512
9058
BTS3502C
9059
SPSV3
9061
MCE
9068
BSC6910 GU
9069
BSC6910 GSM
9070
BSC6910 UMTS
9171
NRS
9172
UGW9500
9173
eCNS600
9174
UPA
9175
DBS3900 eRelay
9176
RRN
9177
RCS9880BMP
9178
SE2900
9179
SeMG
9180
SANEX9510DSS
9188
GroundMonitor
9500
LogicalECNSPoolNode
9501
LogicalRNCInPoolNode
100000
OSS
100001
LogicalMSCPoolNode
100002
LogicalCDMAPoolNode
100003
LogicalSGSNPoolNode
100004
RNC Cluster
100005
BSC POOL
100006
SingleSDB POOL

23
U2000
3 Appendix
NE Type ID
NE Type Name
100007
GUHLR POOL
100008
IMSHSS POOL
100009
SAEHSS POOL
100010
USCDB POOL
100011
CSCF POOL
100012
MME POOL
3.3 Mapping Between Alarm RAT IDs and NE Type IDs

Table 3-2 Mapping between alarm RAT IDs and NE type IDs
Issue 02 (2016-03-20)
RatType
Supported NeType name
45,8216,194,173,9068,171,9069,8197,201
27,89,83,8226,206,2,12,13,14,82,110,111,112,113,124,1
25,126,127,8194,8232,109,145,194
8237,208,8219,8200,159,207,8201,8213,8217,8218,823
3,8243,194
205,27,89,83,8226,109,206,2,12,13,14,82,110,111,112,
113,124,125,126,127,194,8194,8232,145,8237,208,821
9,8200,159,207,8201,8213,8217,8218,8233,8243,8305

24

U2000 Northbound CORBA Interface Alarm Filter Guide

Uploaded by

Document Information

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

U2000 Northbound CORBA Interface Alarm Filter Guide

Uploaded by

Copyright:

Available Formats

U2000

Northbound CORBA Interface Alarm

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

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

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Huawei Proprietary and Confidential

About This Document

Press the keys concurrently. For example, pressing Ctrl

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

2 Configuring the Northbound CORBA Interface Alarm Filter............................................. 6

Huawei Proprietary and Confidential

1 Introduction to Northbound CORBA Interface

Introduction to Northbound CORBA

About This Chapter

Huawei Proprietary and Confidential

1 Introduction to Northbound CORBA Interface

1.1 Definition of Northbound Interface

1.2 Definition of Northbound CORBA Interface

Huawei Proprietary and Confidential

1 Introduction to Northbound CORBA Interface

Table 1-1 Interface protocol

The design of network management interfaces adopts the CORBA

The file transfer mode in the management interface uses the

Huawei Proprietary and Confidential

1 Introduction to Northbound CORBA Interface

The CORBA interface complies with the following 3GPP

Huawei Proprietary and Confidential

1 Introduction to Northbound CORBA Interface

Huawei Proprietary and Confidential

2 Configuring the Northbound CORBA Interface Alarm

Configuring the Northbound CORBA

About This Chapter

Huawei Proprietary and Confidential

2 Configuring the Northbound CORBA Interface Alarm

2.1 Introduction to the Filter Criteria Configuration File

Event alarm part.

Fault alarm part.

Filter Criteria Setting