M2000 V200R010

Northbound CORBA Interface Developer Guide
Issue Date 03 2010-12-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

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

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com

Website: Email:

Issue 03 (2010-12-31)

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

i

.

M2000 Northbound CORBA Interface Developer Guide About This Document About This Document Purpose This document provides information about the M2000 northbound CORBA interface. the changes in the third release are as follows: Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd. Compared with the second release. Related Versions The following table lists product versions related to this document. The document also provides operation guidelines for connecting the network management system (NMS). Product Name M2000 Version V200R010 Intended Audience This document is intended for: l Network administrator Update History 03 (2010-12-31) This is the third commercial release. iii ..

Ltd. Issue 03 (2010-12-31) . The alarm management has the following functions: querying alarms.4 Technical Specifications of Northbound CORBA Interface Modification Description The description of technical specifications is added. acknowledging alarms. and BulkCMIRP. clearing alarms. Organization 1 Introduction to Northbound CORBA Interface This introduction defines the Northbound CORBA interface provided by the M2000 and describes the functions of the Northbound CORBA interface. 01 (2010-07-31) Initial release. and reporting alarms in real time.. KernelCMIRP. Compared with the first release. NotificationIRP and CSIRP. 2 Common Management Function of the CORBA Interface The function of common management interface consists of a cluster of management functions. unacknowledging alarms. These functions are EPIRP. 02 (2010-10-30) This is the second commercial release.4 Technical Specifications of Northbound CORBA Interface Modification Description The content descriptions are changed. 5 Preparations for Interconnection Commissioning of the Northbound CORBA Interface iv Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 3 Configuration Management Function of the CORBA Interface The configuration management interface has the following three functions: BasicCMIRP. the changes in the second release are as follows: Content 1. 4 Alarm Management Function of the CORBA Interface The AlarmIRP interface is the only interface used in alarm management.About This Document M2000 Northbound CORBA Interface Developer Guide Content 1.

Indicates a hazard with a medium or low level of risk. Names of files. Indicates a potentially hazardous situation. For example. which if not avoided. which if not avoided. folders. data loss. you need to make certain preparations. Symbol Description Indicates a hazard with a high level of risk. v . performance degradation. Conventions Symbol Conventions The symbols that may be found in this document are defined as follows. Book titles are in italics. Ltd. directories. or unexpected results.M2000 Northbound CORBA Interface Developer Guide About This Document Before interconnecting the NMS to the M2000. Provides additional information to emphasize or supplement important points of the main text. 6 Troubleshooting the Northbound CORBA Interface The NMS interconnects with the M2000 through the northbound CORBA interface. General Conventions The general conventions that may be found in this document are defined as follows. Examples of information displayed on the screen are in Courier New. If you complete the preparations. refer to relevant troubleshooting methods in this chapter. could result in minor or moderate injury. could result in equipment damage. will result in death or serious injury. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. log in as user root. you can infer that the northbound CORBA interface meets the conditions for the interconnection.. Indicates a tip that may help you solve a problem or save time. and users are in boldface. If a fault occurs when the NMS is obtaining the data. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 7 Appendix A collection of supplementary material. which if not avoided.

For example. Format Key Key 1+Key 2 Key 1. Mouse Operations vi Huawei Proprietary and Confidential Copyright © Huawei Technologies Co... For example. tabs.. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Convention Boldface Italic [] { x | y | . and dialog titles are in boldface.. For example. } [ x | y | . Optional items are grouped in braces and separated by vertical bars. Convention Boldface > Description Buttons. Issue 03 (2010-12-31) . Multi-level menus are in boldface and separated by the ">" signs. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected. press Enter and press Tab. Keyboard Operations The keyboard operations that may be found in this document are defined as follows. One item is selected. Ltd.. A means the two keys should be pressed in turn. One item is selected or no item is selected. ] { x | y | . ]* GUI Conventions The GUI conventions that may be found in this document are defined as follows. }* Description The keywords of a command line are in boldface. Items (keywords or arguments) in brackets [ ] are optional.. Command arguments are in italics. Optional items are grouped in braces and separated by vertical bars. [ x | y | . parameters. Press the keys concurrently. Press the keys in turn. For example. choose File > Create > Folder. pressing Ctrl+Alt +A means the three keys should be pressed concurrently.About This Document M2000 Northbound CORBA Interface Developer Guide Command Conventions The command conventions that may be found in this document are defined as follows.. For example. pressing Alt.. menus. click OK. Key 2 Description Press the key. window..

Press the primary mouse button twice continuously and quickly without moving the pointer. Ltd. Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. vii .M2000 Northbound CORBA Interface Developer Guide About This Document The mouse operations that may be found in this document are defined as follows.

.

.......................2 Heartbeat Notification of the CORBA Communication Surveillance...........................3..........................iii 1 Introduction to Northbound CORBA Interface.2 Notification Description of the CORBA Alarm Management....1 Interface Description of the CORBA Alarm Management................3............................1-5 1............................................2 Definition of Northbound CORBA Interface.....2........................3-8 3...............4-1 4...................................................................................1-2 1........................................2 Common Configuration Management of the CORBA........................................3-4 3........1 Interface Description of the Entry Point of the CORBA Interface................................3 Function of Northbound CORBA Interface...........................................................3-2 3..................................................................................................................2-9 2....1.....................2 Interface Description of the CORBA Notification Management........ Ltd......................1 Entry Point of the CORBA Interface................................................1 Getting to Know Configuration Management of the CORBA Interface......2-11 2.........................................3.........................................2-29 3 Configuration Management Function of the CORBA Interface...........................1 Interface Management of the CORBA...........................................1 Definition of Northbound Interface...........................................................................1-1 1................................1.........2.....................1-6 1..............1 Interface Description of the CORBA Communication Surveillance.......................................................2.....................................4-29 4.............4-2 4........................................2 About IRP............................................2 Notification Description of the Entry Point of the CORBA Interface......................................................................................................... 2-2 2.........4-47 Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co..........................................4 Technical Specifications of Northbound CORBA Interface....2 Alarm Management of the CORBA............................................... 2-2 2......................................3 Communication Surveillance Function of the CORBA Interface..1-5 1....................1 Introduction to the CORBA Alarm Management...........................................................2-23 2....................3 Function and Interface of Basic Configuration Management of the CORBA.......................................................................2 Notification Description of the Common Configuration Management of the CORBA................................................................................................. ix .....3-3 3....................................................1 Introduction to Notification Management Function of the CORBA............................................2........................................................................................M2000 Northbound CORBA Interface Developer Guide Contents Contents About This Document.....................1 Interface Description of the Common Configuration Management of the CORBA...........................1-2 1..3-15 4 Alarm Management Function of the CORBA Interface.2-1 2...2 Notification Management Function of the CORBA Interface.....3 Mechanism for Forwarding Common Alarms........4-2 4.................2...................................................................2-11 2................2........2......3...........................1-7 2 Common Management Function of the CORBA Interface.......2-23 2.......3-1 3..........................2-12 2.....4-2 4..................................................................

.............................1 Common Troubleshooting and Information Collection (CORBA Interface)................5 Modifying the hosts File of the Server...................................7-5 7..........................1 Negotiating the Interconnection Parameters of the Northbound CORBA Interface...........................................5-5 6 Troubleshooting the Northbound CORBA Interface.....................................5-4 5...............................................................................................................................................................................6-2 6..............................................................................................................5-3 5............................................................4 Obtaining the Reference of the Entry Point Object............................................................2 Troubleshooting Failure to Obtain Data...............................5-2 5.......................................3 Description of Alarm Location Detailed Information...............5-5 5.......................................2 Description of filter in get_alarm_list..................................................................6 Using the CORBA Interface...........................................................1 Notification filter Description..................................7-1 7.........................................................................................3 Checking the CORBA Version......1...................................................2 Obtaining the IDL File......................................................2 Description of DN String..................................5-1 5................................................7-4 7..........................................................................7-2 7................................5-3 5......................................................................................................1........6-2 6.................3 Description of filter in get_alarm_count.............1..................................................................................................................................3 Operations Required When the IP Address or Hostname of the M2000 Server Changes.................................................................7-5 7...................1 Description of filter........ Ltd..............6-1 6..........................................Contents M2000 Northbound CORBA Interface Developer Guide 5 Preparations for Interconnection Commissioning of the Northbound CORBA Interface ................................................................6-5 7 Appendix................................. Issue 03 (2010-12-31) ....................................7-6 x Huawei Proprietary and Confidential Copyright © Huawei Technologies Co..7-2 7......

...................................................................................................................1-7 Figure 3-1 Querying the event flow of MOs............................. 7-6 Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.................................................................................... xi ..................................................................................................................1-6 Figure 1-4 Getting object reference of other IRPs by entry points............................................................................................. 1-2 Figure 1-2 Interface management functions...............................................................................................................................................................................................................................................1-5 Figure 1-3 Relation between managed object by the management domain......................................4-8 Figure 7-1 DN string.................................................... Ltd.............M2000 Northbound CORBA Interface Developer Guide Figures Figures Figure 1-1 Location of the northbound interface.3-22 Figure 4-1 Event flow of alarm information..... 1-7 Figure 1-5 Relations between IRPs..............

.

................................................................................................................................................................................................................................2-3 Table 2-5 Exceptions of getting EPIRP operation profile................................................................................................................................................................................................M2000 Northbound CORBA Interface Developer Guide Tables Tables Table 1-1 Interface protocol...........................................................................................................................................................................................................................................................2-7 Table 2-13 Values of getting IRP reference.......................................................................................................................2-13 Table 2-22 Parameters for getting notificationIRP operation profile...2-6 Table 2-11 Exceptions of getting IRP outline...................................... xiii .......2-6 Table 2-12 Parameters for getting IRP reference...............................2-4 Table 2-7 Values of getting EPIRP notification profile....................................................................................................................................................................................................2-8 Table 2-16 Values of releasing IRP reference..............................................................................2-8 Table 2-15 Parameters for releasing IRP reference.......................................................2-4 Table 2-8 Exceptions of getting EPIRP notification profile................2-8 Table 2-14 Exceptions of getting IRP reference.....................................1-3 Table 2-1 Values of getting EPIRP versions............. Ltd.......................2-12 Table 2-20 Values of getting notificationIRP versions................................................................................................................................................................................................................2-18 Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.............................................................2-4 Table 2-6 Parameters for getting EPIRP notification profile................................................................2-14 Table 2-26 Values of getting notificationIRP notification profile..........................................................2-15 Table 2-29 Values of getting notification categories..............................2-15 Table 2-27 Exceptions of getting notificationIRP notification profile..............................................................................2-9 Table 2-17 Exceptions of releasing IRP reference......................................2-16 Table 2-31 Parameters for subscribing specified notifications......................2-5 Table 2-9 Parameters for getting IRP outline.................................................................2-15 Table 2-28 Parameters for getting notification categories.......................................................................................................................................................................................................................................................................2-9 Table 2-18 Format of the notification of entry point register information change...............................................................................2-2 Table 2-2 Exceptions of getting EPIRP version......................................................................................................................2-10 Table 2-19 Notification management function of the CORBA interface..........................................2-5 Table 2-10 Values of getting IRP outline................2-13 Table 2-23 Values of getting notificationIRP operation profile..................................................................................2-3 Table 2-4 Values of getting EPIRP operation profile.....................................................................................................................2-16 Table 2-30 Exceptions of getting notification categories...............................................................2-14 Table 2-25 Parameters for getting notificationIRP notification profile.............2-17 Table 2-32 Values of subscribing specified notifications.2-13 Table 2-21 Exceptions of getting notificationIRP versions.............................2-3 Table 2-3 Parameters for getting EPIRP operation profile............................................................2-14 Table 2-24 Exceptions of getting notificationIRP operation profile.....................................

.....................2-27 Table 2-56 Parameters for setting heartbeat period.. 2-24 Table 2-48 Values of getting CSIRP operation profile.......................................3-5 Table 3-5 Exceptions of getting KernelCMIRP operation profile...................................................3-6 Table 3-8 Exceptions of getting KernelCMIRP notification profile.............................................................................................................................2-27 Table 2-57 Values of setting heartbeat period...................................................................................................................3-10 xiv Huawei Proprietary and Confidential Copyright © Huawei Technologies Co........................................................................................................................................ Issue 03 (2010-12-31) .........................................................................................................2-23 Table 2-44 Exceptions of querying specified subscription parameters.............................................................2-23 Table 2-45 Values of getting CSIRP versions............................................2-21 Table 2-41 Exceptions of querying subscription IDs..2-29 Table 2-61 Exceptions of triggering heartbeat notifications...................2-26 Table 2-52 Exceptions of getting CSIRP notification profile............................................................................... 2-26 Table 2-54 Values of getting heartbeat period......................................2-20 Table 2-38 Exceptions of changing subscription filter conditions.......................................................................................3-5 Table 3-6 Parameters for getting KernelCMIRP notification profile...3-6 Table 3-7 Values of getting KernelCMIRP notification profile........................2-28 Table 2-59 Parameters for triggering heartbeat notifications..................................2-22 Table 2-43 Values of querying specified subscription parameters.........................................3-7 Table 3-10 Exceptions of getting NRMIRP versions............................................................2-24 Table 2-46 Exceptions of getting CSIRP versions.............................................................2-19 Table 2-35 Exceptions of detaching notification subscription...2-25 Table 2-50 Parameters for getting CSIRP notification profile.................................2-19 Table 2-34 Parameters for detaching notification subscription...........................................................................................................................................................................................3-4 Table 3-2 Exceptions of getting KernelCMIRP versions...................................................2-25 Table 2-51 Values of getting CSIRP notification profile...................................................................................................................................2-22 Table 2-42 Parameters for querying specified subscription parameters.... 2-26 Table 2-53 Parameters for getting heartbeat period.............................................................................................................................................................. 2-29 Table 2-62 Format of the heartbeat notification...................................................2-20 Table 2-37 Values of changing subscription filter conditions.................................................................2-21 Table 2-39 Parameters for querying subscription IDs............................................................................................................................................................................... Ltd....................................................................................................................2-21 Table 2-40 Values of querying subscription IDs........................................3-8 Table 3-12 Notification of notifyObjectDeletion.......................................................................................................................................................................................................................................... 2-27 Table 2-55 Exceptions of getting heartbeat period...................................................................................................................................................................................................................................................................................................................................................................................... 2-25 Table 2-49 Exceptions of getting CSIRP operation profile..............2-30 Table 3-1 Values of getting KernelCMIRP versions........................................................................................................3-5 Table 3-4 Values of getting KernelCMIRP operation profile...........................Tables M2000 Northbound CORBA Interface Developer Guide Table 2-33 Exceptions of subscribing specified notifications...........2-29 Table 2-60 Values of triggering heartbeat notifications...............3-4 Table 3-3 Parameters for getting KernelCMIRP operation profile........................................................2-28 Table 2-58 Exceptions of setting heartbeat period...................................................................................................................................................................................................................................3-6 Table 3-9 Parameters for getting NRMIRP versions...........................................................................2-20 Table 2-36 Parameters for changing subscription filter conditions.....................................................................................2-24 Table 2-47 Parameters for getting CSIRP operation profile........................................3-7 Table 3-11 Notification of notifyObjectCreation.........................................

................................................................................................................................................................................................4-5 Table 4-9 Parameters for getting alarm list (I).........................................................................................................4-3 Table 4-3 Parameters for getting AlarmIRP operation profile...................................4-4 Table 4-7 Values of getting AlarmIRP notification profile....................................................................3-18 Table 3-24 Values of finding managed objects (I)...........4-20 Table 4-22 Parameters for acknowledging alarms.............................................................................................................................................................................................................................................................................................................................................................................................................................................................4-7 Table 4-14 Exceptions of getting alarm list (II).............................4-20 Table 4-21 Exceptions of getting alarm count.............................................................................................................4-9 Table 4-17 Acknowledged but uncleared alarms.................................................................................3-15 Table 3-17 Parameters for getting BasicCMIRP operation profile..............................................................................4-22 Table 4-24 Exceptions of acknowledging alarms..........................................................................3-22 Table 4-1 Values of getting AlarmIRP versions........................................................................................................................................4-6 Table 4-11 Exceptions of getting alarm list (I).............................................................................................................4-3 Table 4-4 Values of getting AlarmIRP operation profile...................................................................................................4-21 Table 4-23 Values of acknowledging alarms.................................................................3-16 Table 3-20 Parameters for getting BasicCMIRP notification profile.................................4-12 Table 4-18 Unacknowledged but cleared alarms...................................................3-17 Table 3-21 Values of getting BasicCMIRP notification profile...................................................................................................................................................................3-16 Table 3-18 Values of getting BasicCMIRP operation profile....................M2000 Northbound CORBA Interface Developer Guide Tables Table 3-13 Notification of notifyAttributeValueChange..............3-21 Table 3-29 Exceptions of finding managed objects (III)....................................................................................................................4-16 Table 4-19 Parameters for getting alarm count......4-2 Table 4-2 Exceptions of getting AlarmIRP versions..4-7 Table 4-15 Exceptions of getting alarm list (III)............................................................................4-7 Table 4-13 Values of getting alarm list (II).....................................................................4-8 Table 4-16 Unacknowledged and uncleared alarms............................................ Ltd.......................3-16 Table 3-19 Exceptions of getting BasicCMIRP operation profile..................3-17 Table 3-23 Parameters for finding managed objects (I)..............................................................................................4-4 Table 4-6 Parameters for getting AlarmIRP notification profile.. 3-12 Table 3-14 Notification of notifyCMSynchronizationRecommended................................................................................................................................................................................................................3-13 Table 3-15 Values of getting BasicCMIRP versions.......................................................3-21 Table 3-28 Exceptions of finding managed objects (II).....3-17 Table 3-22 Exceptions of getting BasicCMIRP notification profile.........3-19 Table 3-25 Exceptions of finding managed objects (I)............................................................................................................................................................................................. xv .................................................................................................................4-20 Table 4-20 Values of getting alarm count..................................3-15 Table 3-16 Exceptions of getting BasicCMIRP versions................................4-23 Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co..........4-3 Table 4-5 Exceptions of getting AlarmIRP operation profile.......................................................................................................................................................................................................................................................................................................4-6 Table 4-12 Parameters for getting alarm list (II)...3-20 Table 3-27 Values of finding managed objects (II)..........................................................3-22 Table 3-30 Steps used for the event flow of querying MOs.....................................................................................................................................................................4-4 Table 4-8 Exceptions of getting AlarmIRP notification profile..3-20 Table 3-26 Parameters for finding managed objects (II).......................................................................................................4-5 Table 4-10 Values of getting alarm list (I)............................

.......................6-2 Table 6-3 Possible Causes and Problem Localization ..........................................4-44 Table 4-40 Description of the configuration item....................................4-28 Table 4-33 Exceptions of adding comments to alarms...............................................Tables M2000 Northbound CORBA Interface Developer Guide Table 4-25 Parameters for unacknowledging alarms......................................................................................4-28 Table 4-34 notifyPotentialFaultyAlarmList..........................4-41 Table 4-39 Notification of alarm changes......................4-26 Table 4-31 Parameters for adding comments to alarms.............................................................................................................4-27 Table 4-32 Values of adding comments to alarms...................................................................................................................6-2 Table 6-2 Information to be collected..................4-26 Table 4-30 Exceptions of clearing alarms...................................... 4-34 Table 4-37 Notification of alarm clearance...................................5-6 Table 6-1 Troubleshooting.....................................................................................................................................................................................................................................................................................................................................................6-3 xvi Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.............................................. Issue 03 (2010-12-31) ....................................4-38 Table 4-38 Format of adding alarm comment..........................................................................4-30 Table 4-36 Notification of the change of the alarm acknowledgement status.....................................................................................................................................................................................................................................................................................................................................................................................................4-25 Table 4-28 Parameters for clearing alarms................................................................4-23 Table 4-26 Values of unacknowledging alarms...........4-24 Table 4-27 Exceptions of unacknowledging alarms........................................................................................................................ 4-29 Table 4-35 Notification of new alarms.................................................................................................................................................................................................................4-48 Table 5-1 Negotiated parameters...........................................................4-25 Table 4-29 Values of clearing alarms.............................. Ltd...........................................................................................................................5-2 Table 5-2 Usage of the CORBA interface....

2 Definition of Northbound CORBA Interface The Northbound interface is an interface between the Element Management System (EMS) and the Network Management System (NMS). 1.1 Definition of Northbound Interface The northbound interface links the element management system (EMS) and the NMS.. The Northbound CORBA interface is one of the Northbound interfaces. Ltd. 1. 1. 1-1 .4 Technical Specifications of Northbound CORBA Interface This section describes the technical specifications related to the northbound CORBA interface. 1. The Northbound CORBA interface conforms to the CORBA protocol.M2000 Northbound CORBA Interface Developer Guide 1 Introduction to Northbound CORBA Interface 1 Introduction to Northbound CORBA Interface About This Chapter This introduction defines the Northbound CORBA interface provided by the M2000 and describes the functions of the Northbound CORBA interface. FTP protocol. and 3GPP specifications. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.3 Function of Northbound CORBA Interface This section describes the concepts related to CORBA interface management and integrated reference point (IRP).

1 Definition of Northbound Interface The northbound interface links the element management system (EMS) and the NMS. The Northbound CORBA interface is one of the Northbound interfaces. FTP protocol. The Northbound CORBA interface conforms to the CORBA protocol. the M2000 is an EMS. The M2000 reports the alarm. performance and inventory data to the NMS through the northbound interface. The northbound interface is shown in Figure 1-1.2 Definition of Northbound CORBA Interface The Northbound interface is an interface between the Element Management System (EMS) and the Network Management System (NMS). Issue 03 (2010-12-31) . configuration. 1. The NE information includes the alarm.1 Introduction to Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide 1.. Figure 1-1 Location of the northbound interface In the communication network. configuration. 1-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd. performance and inventory data. the NMS obtains information about the network elements (NEs) managed by the EMS and delivers operation commands. On the northbound interface. Interface Protocol Table 1-1 describes the related information on interface protocol. and 3GPP specifications.

Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l ORB represents the Object Request Broker.. 1-3 .M2000 Northbound CORBA Interface Developer Guide 1 Introduction to Northbound CORBA Interface Table 1-1 Interface protocol Protocol CORBA Details The design of network management interfaces adopts the CORBA technology for interface definition. Ltd. FTP The file transfer mode in the management interface uses the File Transfer Protocol (FTP) and the FTP protocol stack.3 standard l OMG Notification Service 1.3 Version NOTE l OMG represents the Object Management Group.0 standard l TAO 1. The design of the network management interfaces complies with the following CORBA standards: l OMG ORB 2. The CORBA technology uses the IDL language to define the interface information model and also uses the IIOP communication protocol stack.

0. Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) l 3GPP TS 32.601 v6.413 v6.613 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.0.0 Telecommunication management.0 Telecommunication management. Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) 1-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.603 v6.0.602 v6.0 Telecommunication management. Part 1: 3G fault management requirements l 3GPP TS 32.0.0.0 Telecommunication management. Configuration Management (CM). Basic CM Integration Reference Point (IRP): Requirements l 3GPP TS 32.615 v6. Performance Management (PM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) l 3GPP TS 32.111-1 v6. Performance Management (PM) Integration Reference Point (IRP): Requirements l 3GPP TS 32. Configuration Management (CM).0 Fault Management. Communication Surveillance (CS) Integration Reference Point (IRP): Information Service (IS) l 3GPP TS 32.411 v6.0 Telecommunication management.1 Introduction to Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide Protocol 3GPP Details The CORBA interface complies with the following 3GPP protocols: l 3GPP TS 32.111-3 v6. Performance Management (PM) Integration Reference Point (IRP): Information Service (IS) l 3GPP TS 32. Configuration Management (CM). Ltd.0 Fault Management.412 v6.0.0.0 Telecommunication management.111-2 v6.0 Telecommunication management. Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition l 3GPP TS 32.611 v6.0. Configuration Management (CM).0. Configuration Management (CM).0 Telecommunication management.0 Telecommunication management. Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) l 3GPP TS 32.0 Telecommunication management. Issue 03 (2010-12-31) . Basic CM Integration Reference Point (IRP): Information Service (IS) l 3GPP TS 32.0.0. Configuration Management (CM).352 v6..0.612 v6. Configuration Management (CM).0. Bulk CM Integration Reference Point (IRP): Information Service (IS) l 3GPP TS 32. Bulk CM Integration Reference Point (IRP): Requirements l 3GPP TS 32.0 Telecommunication management.

0. and fault management.663 v6.0 Telecommunication management.3. 1. Kernel CM Information Service (IS) l 3GPP TS 32.0 Telecommunication management.0. Figure 1-2 Interface management functions Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Configuration Management (CM).662 v6. configuration management interface.1 Interface Management of the CORBA Based on the common management. Entry Point IRP (EPIRP) and NotificationIRP. The relatively independent interface function provided by the Itf-N interface can be considered as an IRP and then integrated in the network resource model as a managed object. Configuration Management (CM). such as common management interface. Figure 1-2 shows the interface management functions. the ItfN consists of a cluster of management interfaces. configuration management. and fault management interface.3. Configuration Management (CM).0 Telecommunication management.0. and fault management interface.3. configuration management. 1.1 Interface Management of the CORBA Based on the common management. 1.661 v6.2 About IRP The integrated reference point (IRP) is the abstract name of the interface function. such as common management interface. configuration management interface. Kernel CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) 1.3 Function of Northbound CORBA Interface This section describes the concepts related to CORBA interface management and integrated reference point (IRP). the ItfN consists of a cluster of management interfaces. 1-5 .M2000 Northbound CORBA Interface Developer Guide 1 Introduction to Northbound CORBA Interface Protocol Details l 3GPP TS 32. and fault management. Ltd. For example. Kernel CM: Requirements l 3GPP TS 32..

Figure 1-3 shows the relation between managed object by the management domain.2 About IRP The integrated reference point (IRP) is the abstract name of the interface function. Ltd. Entry Point IRP (EPIRP) and NotificationIRP. the Itf-N interface is considered as IRPAgent in the network resource model. IRPAgent is used as the subnode of ManagementNode.. Therefore. IRPAgent includes each object class of IRPs on the Itf-N interface. 1-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Figure 1-3 Relation between managed object by the management domain Relations Between IRPs Figure 1-4 shows the function of entry points that can get object reference of other IRPs. The relatively independent interface function provided by the Itf-N interface can be considered as an IRP and then integrated in the network resource model as a managed object. In the network resource model.3. For example. The managed object are called IRPs.1 Introduction to Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide 1. IRPAgent IRPAgent is the agent of IRP. Issue 03 (2010-12-31) . IRPAgent referred in the latter section is considered as the Itf-N interface system.

4 Technical Specifications of Northbound CORBA Interface This section describes the technical specifications related to the northbound CORBA interface. Value 5 8 15 1-7 ..M2000 Northbound CORBA Interface Developer Guide 1 Introduction to Northbound CORBA Interface Figure 1-4 Getting object reference of other IRPs by entry points Figure 1-5 shows relations between IRPs. Ltd. Specification Item Maximum number of NMS users on the CORBA interface Maximum number of notifications to be subscribed to on CORBA interfaces Maximum delay in reporting a northbound alarm (unit: second) Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Figure 1-5 Relations between IRPs 1.

Issue 03 (2010-12-31) ..1 Introduction to Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide 1-8 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd.

1 Entry Point of the CORBA Interface The entry point is the first object that IRPAgent accesses. 2. 2-1 . 2.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface 2 Common Management Function of the CORBA Interface About This Chapter The function of common management interface consists of a cluster of management functions. In this situation.2 Notification Management Function of the CORBA Interface The notification Management function of the CORBA interface is used for event reporting to the NMS and the management of order information. Function description and format are detailed in the introduction to the CORBA notification management function. These functions are EPIRP. NotificationIRP and CSIRP.3 Communication Surveillance Function of the CORBA Interface The communication surveillance interface function provides a mechanism to monitor the status of communication channels between the NMS and IRPAgent. exceptions can be detected as soon as possible. 2. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. AlarmIRP is one example of the managed object. Ltd. The NMS can access the point at any time according to your requirement and get CORBA reference of managed object in a managed system specified by IRPAgent..

getting IRP reference.1. that is. send a notification of entry point register information change to the NMS according to requirement.1 Entry Point of the CORBA Interface The entry point is the first object that IRPAgent accesses. The value of VersionNumberSet is a set of strings. Function format ManagedGenericIRPConstDefs::VersionNumberSet get_EP_IRP_versions () raises (GetEPIRPVersions). These functions consist of getting EPIRP versions. When IRPAgent is rebooted. the IP address of the server where IRPAgent is located is fixed and IOR is permanently effective. There is no parameter in getting EPIRP versions. these object references must be obtained again.1. Ltd. AlarmIRP is one example of the managed object. getting IRP outline. that is. getting EPIRP operation profile. Support (Y/N) Y 2-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Object references of other IRPs are variable. and releasing IRP reference. Getting EPIRP Versions l l Function description The NMS invokes get_EP_IRP_versions to get EPIRP versions. getting EPIRP notification profile. and releasing IRP reference. getting IRP outline. Huawei supports only one of the EPIRP versions. Table 2-1 Values of getting EPIRP versions Returned Value VersionNumberSet Description Indicates a set of versions that the EPIRP supports.1 Interface Description of the Entry Point of the CORBA Interface This describes the functions of CORBA entry point. getting EPIRP notification profile. In addition. Issue 03 (2010-12-31) .1 Interface Description of the Entry Point of the CORBA Interface This describes the functions of CORBA entry point.. These functions consist of getting EPIRP versions. 2. The NMS can access the point at any time according to your requirement and get CORBA reference of managed object in a managed system specified by IRPAgent. getting EPIRP operation profile. The interoperable object reference (IOR). 2.1. CORBA object reference of the entry point.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide 2. IOR is permanent. 2. getting IRP reference. is released as a file.2 Notification Description of the Entry Point of the CORBA Interface When changes happen to the IRP information (for the EPIRP instance itself or other EPIRP instances that the EPIRP instance knows) saved in the entry point.

Support (Y/N) Y Table 2-4 Values of getting EPIRP operation profile Returned Value MethodList Description Indicates the information list of operations the EPIRP supports. l Function format ManagedGenericIRPConstDefs::MethodList get_EP_IRP_operations_profile ( in ManagedGenericIRPConstDefs::VersionNumber iRPVersion ) raises ( GetEPIRPOperationsProfile. Ltd. The version ID should be consistent with the version ID returned by Getting EPIRP Versions. 2-3 .M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-2 Exceptions of getting EPIRP version Exception GetEPIRPVersions Description Indicates the exceptions caused by unknown reasons. ManagedGenericIRPSystem::InvalidParameter).. Support (Y/N) Y Getting EP IRP Operation Profile l Function description NMS invokes get_EP_IRP_operations_profile to get the profile of operations supported by EPIRP. Table 2-3 Parameters for getting EPIRP operation profile Parameter iRPVersion In/Out In Description Indicates the version ID of EPIRP in the EPIRP profile obtained by the NMS. The information list contains the following items: l Names of operations l Parameter lists Support (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. ManagedGenericIRPSystem::OperationNotSupported.

Support (Y/N) Y Table 2-7 Values of getting EPIRP notification profile Returned Value MethodList Description Indicates the profile list of notifications that an EPIRP supports. The profile list contains the following items: l Names of notifications supported by the EPIRP l Names of fields in the notification (including the names of filterable_data and remainder_of_body fields) 2-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The version ID should be consistent with the version ID returned by Getting EPIRP Versions. ManagedGenericIRPSystem::InvalidParameter). Ltd. Support (Y/N) Y N Y Getting EP IRP Notification Profile l Function description The NMS invokes get_EP_IRP_notification_profile to get the profile of the notification supported by EPIRP.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 2-5 Exceptions of getting EPIRP operation profile Exception InvalidParameter OperationNotSupported GetEPIRPOperationsProfile Description Indicates that the given iRPVersion is invalid or null. Table 2-6 Parameters for getting EPIRP notification profile Parameter iRPVersion In/Out In Description Indicates the version information about EPIRP in the EPIRP outline gotten by the NMS.. l Function format ManagedGenericIRPConstDefs::MethodList get_EP_IRP_notification_profile ( in ManagedGenericIRPConstDefs::VersionNumber iRPVersion ) raises ( GetEPIRPNotificationProfile. ManagedGenericIRPSystem::OperationNotSupported. Indicates that this operation is not supported. Indicates the exceptions caused by unknown reasons. Issue 03 (2010-12-31) Support (Y/N) Y .

0. Indicates the exceptions caused by unknown reasons. including this EPIRP instance itself.InvalidIRPVersion). Table 2-9 Parameters for getting IRP outline Parameter iRPVersion In/Out In Description Indicates the version information about EPIRP in the EPIRP outline gotten by the NMS. The parameter has the following two situations: l If this parameter is null.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-8 Exceptions of getting EPIRP notification profile Exception InvalidIRPVersion OperationNotSupported GetEPIRPNotificationProfile Description Indicates that the given iRPVersion is invalid or null. l If this parameter is not null. out EPIRPConstDefs::SupportedIRPListType supportedIRPList ) raises (GetIRPOutline. 2-5 .2. If you plan to query the general information about the CS IRP. Support (Y/N) Y N Y Getting IRP Outline l Function description The NMS invokes get_IRP_outline to get the outline of the management domain Managed Object. Support (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. Indicates that this operation is not supported. the Agent returns the outline of all EPIRPs. Ltd. the entered value is the complete IRP information. l Function format EPIRPConstDefs::ResultType get_IRP_outline ( in ManagedGenericIRPConstDefs::VersionNumber iRPVersion. the input parameter is CS IRP V1.

2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Parameter supportedIRPList In/Out Out Description Indicates the returned list of the IRP profile according to input parameter conditions. out string iRPReference 2-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Indicates that the operation fails. The list contains all IRP information in systemDn and IRPAgent. Indicates the exceptions caused by unknown reasons. Ltd.. in EPIRPConstDefs::IRPClassNameType irpClassName. Support (Y/N) Y Table 2-10 Values of getting IRP outline Returned Value OK FAILURE Description Indicates that the operation succeeds. Support (Y/N) Y Y Getting IRP Reference l Function description The NMS invokes get_IRP_reference to get the CORBA object reference specified in IRPAgent or the object reference of EPIRP. Issue 03 (2010-12-31) . in EPIRPConstDefs::DNType systemDn. Support (Y/N) Y Y Table 2-11 Exceptions of getting IRP outline Exception InvalidIRPVersion GetIRPOutline Description Indicates that the given IRPVersion is invalid. l Function format EPIRPConstDefs::ResultType get_IRP_reference ( in EPIRPConstDefs::ManagerIdentifierType managerIdentifier. The IRP information contains: l irpId l irpVersion l irpClassName l irpManagementScope The value of the parameter is of multinested structure. in EPIRPConstDefs::IRPIdType irpId.

Y Y Y Y Support (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd. iRPReference Out Indicates the CORBA object reference of IRP needed by the NMS. The value of this parameter should be consistent with the value of irpId returned by Getting IRP Outline. irpId In Indicates irpId of IRP obtained by the NMS. When you use a different managerIdentifier to get the same object of IRP. The value of this parameter should be consistent with the class name of IRP returned by Getting IRP Outline. an exception occurs. You can provide different values for managerIdentifier to invoke this operation. irpClassName In Indicates the class name of IRP obtained by the NMS. Table 2-12 Parameters for getting IRP reference Parameter managerIdentifier In/Out In Description Indicates a character string identifying Manager (NMS). 2-7 . The value of this parameter should be consistent with the value of systemDn returned by Getting IRP Outline. ManagedGenericIRPSystem::InvalidParameter). the reference is different.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface ) raises ( GetIRPReference. If the number of different values reaches five. systemDN In Indicates the DN value of IRPAgent obtained from the Agent system.. The character string is given by the NMS and is unique. Huawei recommends that you use a unique value for the parameter in an NMS.

l Function format EPIRPConstDefs::ResultType release_IRP_reference( in EPIRPConstDefs::ManagerIdentifierType managerIdentifier. in string iRPReference ) raises ( ReleaseIRPReference. Table 2-15 Parameters for releasing IRP reference Parameter managerIdentifier In/Out In Description Indicates a character string identifying the NMS. UnknownIRPReference).. Issue 03 (2010-12-31) . Support (Y/N) Y 2-8 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 2-13 Values of getting IRP reference Returned Value OK Failure Description Indicates that the operation succeeds. Support (Y/N) Y Y Table 2-14 Exceptions of getting IRP reference Exception InvalidParameter Description Indicates that the following parameters or their combination are invalid: l systemDN l irpId l irpClassName l managerIdentifier GetIRPReference Indicates the exceptions caused by unknown reasons. Y Support (Y/N) Y Releasing IRP Reference l Function description The NMS invokes release_IRP_reference to release the reference of a specified IRP that is not in use. The parameter should be consistent with managerIdentifier specified in Getting IRP Reference. Ltd. Indicates that the operation fails.

IOR of IRP to be released by the NMS.1. Triggering Conditions l l Issue 03 (2010-12-31) When the newly obtained object reference is successful through the Getting IRP Reference interface. Indicates that the operation fails.. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. that is. Y Support (Y/N) Y 2. The reason is that iRPReference is not obtained by managerIdentifier through the operation Getting IRP Reference. 2-9 . When the object is released successfully through the Releasing IRP Reference interface.2 Notification Description of the Entry Point of the CORBA Interface When changes happen to the IRP information (for the EPIRP instance itself or other EPIRP instances that the EPIRP instance knows) saved in the entry point. ReleaseIRPReference Indicates the exceptions caused by unknown reasons. send a notification of entry point register information change to the NMS according to requirement. Support (Y/N) Y Y Table 2-17 Exceptions of releasing IRP reference Exception UnknownIRPReference Description Indicates that the specified iRPReference is invalid or the specified managerIdentifier does not match iRPReference. Ltd.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Parameter iRPReference In/Out In Description Indicates the CORBA object reference. The parameter should be consistent with iRPReference returned by Getting IRP Reference through relevant managerIdentifier. Support (Y/N) Y Table 2-16 Values of releasing IRP reference Returned Value OK Failure Description Indicates that the operation succeeds.

Table 2-18 Format of the notification of entry point register information change Attribute Name domain_name Type string Domain header. Indicates the notification identifier and is used to exclusively identify a notification.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide l When the IRPAgent system starts or stops.fixed_h eader filterable_data a long remainder_of_ body filterable_data filterable_data b c TimeBase:: UtcT string IRP_DN string remainder_of_ body 2-10 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Issue 03 (2010-12-31) .fixed_h eader.) Indicates the instances of MO that sends the notification. Ltd. the IRP object instance. Notification Format Table 2-18 lists the format of the notification of entry point register information change.event_ty pe header. Indicates the name of an event. (This parameter is null. Indicates the type of the reported notification.. type_name string event_name e string string header. Indicates the time when an event occurs. Indicates the identifier of the IRPAgent that generates notifications.fixed_h eader. that is. The value of this parameter is defined by EPIRPNotifications::notifyIRPInfo Changes::ET_IRPINFO_CHANGE S. This parameter shows the version number of the associated IRP information model.event_ty pe Description Indicates the name of a managed domain. Indicates the DN value of the IRP when the information about the EP changes.

2. The change modes are as follows: l REGISTER A new object reference value is obtained.2. getting notificationIRP notification profile. MODIFY}.1 Introduction to Notification Management Function of the CORBA The notification management function of the CORBA interface is used for event reporting to the NMS. Table 2-19 describes the notification management function of the CORBA interface. detaching notification subscription.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Attribute Name CHANGE_MODE Type enum ChangeMod eType {REGISTE R.2 Interface Description of the CORBA Notification Management This describes the CORBA notification management function that involves getting notificationIRP versions. 2-11 . Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Function description and format are detailed in the introduction to the CORBA notification management function. order management. ADDITIONAL_T EXT string remainder_of_ body Indicates the additional description text added to the notification. l DEREGISTER The IRPAgent system stops or releases an object reference. getting notificationIRP operation profile.2 Notification Management Function of the CORBA Interface The notification Management function of the CORBA interface is used for event reporting to the NMS and the management of order information. subscribing specified notifications. 2. DEREGIST ER. 2. and order limitation. NOTE CosNotification::PropertySeq is the value type of remainder_of_body. changing subscription filter conditions.1 Introduction to Notification Management Function of the CORBA The notification management function of the CORBA interface is used for event reporting to the NMS. and querying parameters of specified subscription.. order management. 2. querying subscription IDs. getting notification categories. l MODIFY The IRPAgent system starts the object reference value.2. and order limitation. Domain remainder_of_ body Description Indicates that the change modes of the EPIRP information.2. Ltd.

The management includes the subscription period. IRPAgen can determine the validity by using the method of _non_existent provided by CORBA. notification class. IRPAgen check whether the currently subscribed CosNotifyComm::SequencePushConsumer object is valid. l Function format ManagedGenericIRPConstDefs::VersionNumberSet get_notification_IRP_versions () raises (GetNotificationIRPVersions).2 Interface Description of the CORBA Notification Management This describes the CORBA notification management function that involves getting notificationIRP versions. Issue 03 (2010-12-31) . querying subscription IDs. and querying parameters of specified subscription. getting notification categories.2. Getting Notification IRP Versions l Function description The NMS invokes get_notification_IRP_versions to get the NotificationIRP version information.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 2-19 Notification management function of the CORBA interface Scenario Enabling IRPAgent to report events to the NMS Description The NMS invokes the notification management interface to enable the NMS to receive the notification of CosNotifyComm::SequencePushConsumer that is defined by the CORBA specification IOR and the notification of integrating the CORBA specification. To ensure that all the subscribed notifications are valid. If an object is invalid. getting notificationIRP notification profile. The NMS is recommended to actively cancel unneeded subscription. and filter condition. the NMS is recommended to actively invoke an interface to cancel the subscription before the CosNotifyComm::SequencePushConsumer is invalid. subscribing specified notifications. Obtain the parameters irrelevant to the NotificationIRP version. The notification is sent to the NMS through the notification channel. 2-12 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Subscribing a maximum of eight notifications If the actual subscription number exceeds the maximum subscription number. getting notificationIRP operation profile.. changing subscription filter conditions. IRPAgent automatically cancels the subscription of the object. detaching notification subscription. If the CosNotifyComm::SequencePushConsumer object is invalid and need be subscribed again. Managing subscribed notifications 2. an exception occurs. Ltd.

ManagedGenericIRPSystem::InvalidParameter). Support (Y/N) Y Getting Notification IRP Operation Profile l Function description The NMS invokes get_notification_IRP_operations_profile to get the profile of operations supported by a specified version of NotificationIRP. l Function format ManagedGenericIRPConstDefs::MethodList get_notification_IRP_operations_profile ( in ManagedGenericIRPConstDefs::VersionNumber notification_irp_version ) raises ( GetNotificationIRPOperationsProfile.. Table 2-22 Parameters for getting notificationIRP operation profile Parameter notification_irp_version In/Out In Description Indicates the NotificationIRP version ID in the NotificationIRP profile obtained by the NMS. Ltd. Huawei supports only one of the NotificationIRP versions.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-20 Values of getting notificationIRP versions Returned Value VersionNumberSet Description Indicates a set of versions that the NotificationIRP supports. Support (Y/N) Y Table 2-21 Exceptions of getting notificationIRP versions Exception GetNotificationIRPVersions Description Indicates the exceptions caused by unknown reasons. Suppor t (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. ManagedGenericIRPSystem::OperationNotSupported. The version ID should be consistent with the version ID returned by Getting Notification IRP Versions. The value of VersionNumberSet is a set of strings. 2-13 .

Issue 03 (2010-12-31) Support (Y/N) Y .2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 2-23 Values of getting notificationIRP operation profile Returned Value MethodList Description Indicates the information list of operations the NotificationIRP supports. Support (Y/N) Y OperationNotSupported GetEPIRPOperationsProfile N Y Getting Notification IRP Notification Profile l Function description The NMS invokes get_notification_IRP_notification_profile to get the profile of the notification supported by NotificationIRP. Ltd. Indicates that this operation is not supported. The information list contains the following items: l Names of operations l Parameter lists Support (Y/N) Y Table 2-24 Exceptions of getting notificationIRP operation profile Exception InvalidParameter Description Indicates that the given notification_irp_version is invalid or null. The version ID should be consistent with the version ID returned by Getting Notification IRP Versions. l Function format ManagedGenericIRPConstDefs::MethodList get_notification_IRP_notification_profile ( in ManagedGenericIRPConstDefs::VersionNumber notification_irp_version ) raises ( GetNotificationIRPNotificationProfile. ManagedGenericIRPSystem::OperationNotSupported. ManagedGenericIRPSystem::InvalidParameter). 2-14 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Indicates the exceptions caused by unknown reasons. Table 2-25 Parameters for getting notificationIRP notification profile Parameter notification_irp_version In/Out In Description Indicates the NotificationIRP version ID in the NotificationIRP profile obtained by the NMS..

Indicates that this operation is not supported. Indicates the exceptions caused by unknown reasons. l Table 2-28 Parameters for getting notification categories Parameter notification_type_list In/Out Out Description Indicates the list of notification types that map to notification categories. ManagedGenericIRPSystem::OperationNotSupported). The profile list contains the following items: l Names of notifications supported by the NotificationIRP l Names of fields in the notification (including the names of filterable_data and remainder_of_body fields) NOTE Notifications are not defined in the NotificationIRP. Table 2-27 Exceptions of getting notificationIRP notification profile Exception InvalidIRPVersion OperationNotSupported GetNotificationIRPNotificationProfile Description Indicates that the given notification_irp_version is invalid or null. 2-15 . Support (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd.. Function format NotificationIRPConstDefs::NotificationCategorySet get_notification_categories ( out NotificationIRPConstDefs::NotificationTypesSet notification_type_list ) raises ( GetNotificationCategories. Support (Y/N) Y N Y Getting Notification Categories l Function description The NMS invokes get_notification_categories to query the notification categories supported by IRPAgent and the mapping notification types.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-26 Values of getting notificationIRP notification profile Returned Value Description Suppo rt (Y/ N) Y MethodList Indicates the profile list of notifications that an NotificationIRP supports.

Issue 03 (2010-12-31) . AlreadySubscribed. ManagedGenericIRPSystem::InvalidParameter.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 2-29 Values of getting notification categories Returned Value NotificationCategorySet Description Indicates the set of notification categories supported by IRPAgent. ManagedGenericIRPSystem::ParameterNotSupported. Subscribing Specified Notifications l l Function description The NMS invokes attach_push to subscribe notifications of specified categories. in NotificationIRPConstDefs::NotificationCategorySet notification_categories. in unsigned long time_tick. Indicates the exceptions caused by unknown reasons. in ManagedGenericIRPConstDefs::StringTypeOpt filter ) raises ( Attach.. Function format NotificationIRPConstDefs::SubscriptionId attach_push ( in string manager_reference. AtLeastOneNotificationCategoryNotSupported). Ltd. Suppor t (Y/N) Y Table 2-30 Exceptions of getting notification categories Exception Description Suppo rt (Y/ N) N Y OperationNotSupported GetNotificationCategories Indicates that this operation is not supported. 2-16 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Each element in this set specifies a notification category.

For IOR. l If you enter a value more than 15 (included). time_tick In Indicates a timer. The unit for this parameter is minute. the timer is set to the entered value. the parameter value should be CosNotifyComm::SequencePushConsumer. the timer never expires. the timer is set to 15.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-31 Parameters for subscribing specified notifications Parameter manager_reference In/Out In Description Identifies the event receiver at the NMS side. The IRPAgent uses the event channel to transfer the NMS an event information.. manager_reference invokes the push operation. Normally. Ltd. When the subscribed number exceeds eight. l If you enter null or 0. the NMS invokes Querying Parameters of Specified Subscription periodically to refresh the timer to ensure that the relevant channel is not released. 2-17 . Y Suppor t (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. After this timer expires. no new subscriptions are received. the subscribed notification is detached to release the notification channel resources. Set the value of the timer according to the following two situations: l If you enter a value between 1 and 15. that is.

Each element in the set should be an element of the notification category returned by Getting Notification Categories. Support (Y/ N) Y 2-18 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l If all the notification classes are subscribed. an AlreadySubscribed exception is displayed. refer to 7. The parameter is set based on all notification categories defined by notification_categories.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Parameter notification_categories In/Out In Description Defines the set of notifications to be filtered. l If notification_categories is null. Suppor t (Y/N) Y filter In Defines the filter condition for the notification subscription. If all the notification classes are subscribed in the set. there must be a notification class that is not subscribed in the parameter-defined set.. Ltd. If this parameter is valued null.1. infer that all the notification classes unsubscribed by manager_reference need be subscribed. For the repeated subscription of manager_reference. Issue 03 (2010-12-31) . If the set is null. an AlreadySubscribed exception is displayed. infer that conditions defined by notification_categories have no extra restrictions. The NMS can uniquely identify a subscription record by using this value. For details of the syntax. Y Table 2-32 Values of subscribing specified notifications Returned Value SubscriptionId Description Identifies the notification subscription. infer that all the notification categories supported by IRPAgent are subscribed.1 Notification filter Description.

Indicates the exceptions caused by unknown reasons. If this parameter is null. Support (Y/ N) Y ParameterNotSupported InvalidParameter AtLeastOneNotificationCategoryNotSupported Attach N Y Y Y Detaching Notification Subscription l l Function description The NMS invokes detach to detach the notification subscription. in NotificationIRPConstDefs::SubscriptionId subscription_id) raises ( DetachException. 2-19 Support (Y/N) Y subscription_id In Y . ManagedGenericIRPSystem::ParameterNotSupported. Table 2-34 Parameters for detaching notification subscription Parameter manager_reference In/Out In Description Indicates the identifier of the event receiver at the home NMS that is going to detach the notification subscription.. Indicates that this parameter is incorrect or that its format is incorrect. infer that all notifications earlier subscribed by manager_reference are detached. Indicates the unique identifier of the notification subscription. Function format void detach ( in string manager_reference. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-33 Exceptions of subscribing specified notifications Exception AlreadySubscribed Description Indicates that the notifications defined by notification_categories are already subscribed by the manager_reference receiver. Indicates that this parameter is incorrect or that the parameter notification_categories is invalid. Ltd. Indicates that this parameter is not supported. ManagedGenericIRPSystem::InvalidParameter). The parameter should be consistent with manager_reference specified in Subscribing Specified Notifications.

1. refer to 7. in string filter) raises ( ChangeSubscriptionFilter. ManagedGenericIRPSystem::InvalidParameter). Support (Y/N) Y ParameterNotSupported DetachException N Y Changing Subscription Filter Conditions l l Function description The NMS invokes change_subscription_filter to change the subscription filter conditions. subscription_id or their combination is invalid.. Indicates the subscription of filter conditions. Alternatively. Table 2-35 Exceptions of detaching notification subscription Exception InvalidParameter Description Indicates that the specified parameter manager_reference. Indicates the exceptions caused by unknown reasons. Suppor t (Y/N) Y Y NOTE For details of the syntax of filter.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Retract the subscription of the parameters having no values. Ltd. . Function format void change_subscription_filter ( in NotificationIRPConstDefs::SubscriptionId subscription_id.1 Notification filter Description. Indicates that this parameter is not supported. the notification subscription identified by subscription_id is not subscribed by manager_reference. Table 2-37 Values of changing subscription filter conditions Returned Value 2-20 Description - Suppor t (Y/N) Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. ManagedGenericIRPSystem::OperationNotSupported. Table 2-36 Parameters for changing subscription filter conditions Parameter subscription_id filter In/Out In In Description Indicates the unique identifier of the notification subscription.

Indicates the exceptions caused by unknown reasons. ManagedGenericIRPSystem::OperationNotSupported. The parameter should be consistent with the specified manager_reference given by Subscribing Specified Notifications. Indicates that this operation is not supported. Table 2-39 Parameters for querying subscription IDs Parameter manager_reference In/Out In Description Indicates the identifier of the event receiver to be queried at the NMS side. Ltd. 2-21 Support (Y/N) Y . the returned list is null. Support (Y/N) Y Table 2-40 Values of querying subscription IDs Returned Value SubscriptionIdSet Description Indicates the set of all subscription IDs related to manager_reference. l Function format NotificationIRPConstDefs::SubscriptionIdSet get_subscription_ids ( in string manager_reference ) raises ( GetSubscriptionIds. ManagedGenericIRPSystem::InvalidParameter).. If a specified manager_reference is valid but not subscribed. Querying Subscription IDs l Function description The NMS invokes get_subscription_ids to query all subscription IDs related to a specified manager_reference. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-38 Exceptions of changing subscription filter conditions Exception Description Suppo rt (Y/ N) Y N Y InvalidParameter OperationNotSupported ChangeSubscriptionFilter Indicates that the subscription_id or filter is invalid or null.

2 Common Management Function of the CORBA Interface

M2000 Northbound CORBA Interface Developer Guide

Table 2-41 Exceptions of querying subscription IDs Exception InvalidParameter OperationNotSupported GetSubscriptionIds Description Indicates that the manager_reference is invalid. Indicates that this operation is not supported. Indicates the exceptions caused by unknown reasons. Support (Y/N) Y N Y

Querying Parameters of Specified Subscription
l Function description The NMS invokes get_subscription_status to query parameters of a specified subscription, including subscription parameters and subscription statuses. l Function format
NotificationIRPConstDefs::NotificationCategorySet get_subscription_status ( in NotificationIRPConstDefs::SubscriptionId subscription_id, out ManagedGenericIRPConstDefs::StringTypeOpt filter_in_effect, out NotificationIRPConstDefs::SubscriptionState subscription_state, out unsigned long time_tick ) raises ( GetSubscriptionStatus, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter);

Table 2-42 Parameters for querying specified subscription parameters Parameter subscription_id time_tick filter_in_effect subscription_state In/Out In Out Out Out Description Indicates the unique identifier of the notification subscription. Indicates the value for invoking attach_push. Indicates the filter condition used by the current subscription. Indicates the status of the current subscription, including: l Active l Suspended Because the Suspended status is not supported, only the Active status exists. Support (Y/N) Y Y Y Y

2-22

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

Issue 03 (2010-12-31)

M2000 Northbound CORBA Interface Developer Guide

2 Common Management Function of the CORBA Interface

Table 2-43 Values of querying specified subscription parameters Returned Value NotificationCategorySet Description Indicates the set of notification categories supported by the current subscription. Support (Y/N) Y

Table 2-44 Exceptions of querying specified subscription parameters Exception InvalidParameter OperationNotSupported GetSubscriptionStatus Description Indicates that the subscription_id is invalid. Indicates that the operation is not supported. Indicates the exceptions caused by unknown reasons. Support (Y/N) Y N Y

2.3 Communication Surveillance Function of the CORBA Interface
The communication surveillance interface function provides a mechanism to monitor the status of communication channels between the NMS and IRPAgent. In this situation, exceptions can be detected as soon as possible. The NMS monitors communication channels using the following two ways: l l By setting a heartbeat interval, the NMS can receive heartbeat notifications to monitor the status of communication channels between the NMS and IRPAgent. The NMS actively invoke IRPAgent to trigger the heartbeat interface to query the status of communication channels.

2.3.1 Interface Description of the CORBA Communication Surveillance The CORBA communication surveillance involves getting CSIRP versions, getting CSIRP operation profile, getting CSIRP notification profile, getting heartbeat period, setting heartbeat period, and triggering heartbeat notifications. 2.3.2 Heartbeat Notification of the CORBA Communication Surveillance When the heartbeat period is up, IRPAgent sends a heartbeat notification accordingly to the NMS.

2.3.1 Interface Description of the CORBA Communication Surveillance
The CORBA communication surveillance involves getting CSIRP versions, getting CSIRP operation profile, getting CSIRP notification profile, getting heartbeat period, setting heartbeat period, and triggering heartbeat notifications.
Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 2-23

2 Common Management Function of the CORBA Interface

M2000 Northbound CORBA Interface Developer Guide

Getting CSIRP Versions
l l Function description The NMS invokes get_CS_IRP_versions to get the CSIRP version information. Function format
ManagedGenericIRPConstDefs::VersionNumberSet get_CS_IRP_versions () raises (GetCSIRPVersions);

There is no parameter in getting CSIRP versions. Table 2-45 Values of getting CSIRP versions Returned Value VersionNumberSet Description Support (Y/N)

Indicates a set of versions that the Y EPIRP supports. The value of VersionNumberSet is a set of strings. Huawei supports only one of the EPIRP versions.

Table 2-46 Exceptions of getting CSIRP versions Exception GetCSIRPVersions Description Indicates the exceptions caused by unknown reasons. Support (Y/N) Y

Getting CSIRP Operation Profile
l Function description The NMS invokes get_CS_IRP_operations_profile to get the profile of operations supported by a specified version of CSIRP. l Function format
ManagedGenericIRPConstDefs::MethodList get_CS_IRP_operations_profile ( in ManagedGenericIRPConstDefs::VersionNumber iRPVersion ) raises ( GetCSIRPOperationsProfile, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter);

Table 2-47 Parameters for getting CSIRP operation profile Parameter iRPVersion In/Out In Description Indicates the version ID of CSIRP in the profile obtained by the NMS. The version ID should be consistent with the version ID returned by Getting CSIRP Versions. Support (Y/N) Y

2-24

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

Issue 03 (2010-12-31)

ManagedGenericIRPSystem::InvalidParameter). Table 2-50 Parameters for getting CSIRP notification profile Parameter iRPVersion In/Out In Description Indicates the version ID of CSIRP in the profile obtained by the NMS. Ltd. Support (Y/N) Y N Y Getting CSIRP Notification Profile l Function description The NMS invokes get_CS_IRP_notification_profile to get the profile of notifications supported by a specified version of CSIRP. Indicates the exceptions caused by unknown reasons. l Function format ManagedGenericIRPConstDefs::MethodList get_CS_IRP_notification_profile ( in ManagedGenericIRPConstDefs::VersionNumber iRPVersion ) raises ( GetCSIRPNotificationProfile. ManagedGenericIRPSystem::OperationNotSupported. The version ID should be consistent with the version ID returned by Getting CSIRP Versions.. Support (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The information list contains the following items: l Names of operations l Parameter lists Support (Y/N) Y Table 2-49 Exceptions of getting CSIRP operation profile Exception InvalidParameter OperationNotSupported GetCSIRPOperationsProfile Description Indicates that iRPVersion is invalid or null. Indicates that this operation is not supported.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-48 Values of getting CSIRP operation profile Returned Value MethodList Description Indicates the information list of operations the CSIRP supports. 2-25 .

Indicates that this operation is not supported. Ltd. The profile list contains the following items: l Names of notifications supported by the CSIRP l Names of fields in the notification (including the names of filterable_data and remainder_of_body fields) Support (Y/N) Y Table 2-52 Exceptions of getting CSIRP notification profile Exception InvalidIRPVersion OperationNotSupported GetCSIRPNotificationProfile Description Indicates that the iRPVersion is invalid or null. l Function format CSIRPConstDefs::ResultType get_heartbeat_period( out CSIRPConstDefs::HeartbeatPeriodType heartbeatPeriod ) raises (GetHeartbeatPeriod). The value 0 is also valid and 0 means that the interval for sending heartbeat notifications is not set. the heartbeat period.. 2-26 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Table 2-53 Parameters for getting heartbeat period Parameter heartbeatPeriod In/Out Out Description Indicates the interval for which IRPAgent reports heartbeat notifications periodically to the NMS (unit: minute). Issue 03 (2010-12-31) Support (Y/N) Y . that is. Indicates the exceptions caused by unknown reasons. Value range: 5 to 60 The default value is 5.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 2-51 Values of getting CSIRP notification profile Returned Value MethodList Description Indicates the profile list of notifications that a CSIRP supports. Support (Y/N) Y N Y Getting Heartbeat Period l Function description The NMS invokes get_heartbeat_period to get the interval for sending heartbeat notifications.

The changed heartbeat period (unit: minute). l Function format CSIRPConstDefs::ResultType set_heartbeat_period( in CSIRPConstDefs::HeartbeatPeriodType heartbeatPeriod ) raises ( SetHeartbeatPeriod. Support (Y/N) Y Y Table 2-55 Exceptions of getting heartbeat period Exception GetHeartbeatPeriod Description Indicates the exceptions caused by unknown reasons. failure is returned for this operation. the Agent sends a heartbeat notification with the new heartbeat period immediately to all the NMS that have subscribed this notification. Ltd.. Table 2-56 Parameters for setting heartbeat period Parameter heartbeatPeriod In/Out In Description Indicates the heartbeat period. the Agent sends a notification informing about the change and sends no more heartbeat notifications later unless this value is changed to another different value. Whenever the heartbeatPeriod attribute changes.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-54 Values of getting heartbeat period Returned Value Success Failure Description Indicates that this operation succeeds. If the heartbeat period is changed to 0. ManagedGenericIRPSystem::OperationNotSupported). InvalidHeartbeatPeriod. Indicates that this operation fails. ManagedGenericIRPSystem::ValueNotSupported. Value range: 5 to 60 The value 0 is also valid. If the changed heartbeat period is the same in value as the old one. ConflictingHeartbeatPeriod. Support (Y/N) Y Setting Heartbeat Period l Function description The NMS invokes set_heartbeat_period to set the interval for Agent to send heartbeat notifications. 2-27 Support (Y/N) Y . Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

When receiving this operation. InvalidManagerIdentifier).. IRPAgent sends immediately a heartbeat notification and indicates in the notification that this notification is triggered by the NMS. Indicates that this operation is not supported. Support (Y/N) Y Y Table 2-58 Exceptions of setting heartbeat period Exception InvalidHeartbeatPeriod ConflictingHeartbeatPeriod ValueNotSupported OperationNotSupported SetHeartbeatPeriod Description Indicates that the specified heartbeat period is invalid.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 2-57 Values of setting heartbeat period Returned Value Success Failure Description Indicates that this operation succeeds. Indicates the exceptions caused by unknown reasons. This does not affect the normal heartbeat notifications sent periodically by IRPAgent. Ltd. Issue 03 (2010-12-31) . Indicates that this operation fails. Support (Y/N) Y Y N N Y Triggering Heartbeat Notifications l Function description The NMS invokes trigger_heartbeat to trigger a heartbeat notification. 2-28 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The NMS can perform this operation to actively query the communication state with IRPAgent. l Function format CSIRPConstDefs::ResultType trigger_heartbeat( in CSIRPConstDefs::ManagerIdentifierType managerIdentifier ) raises (TriggerHeartbeat. Indicates that the specified parameter is not supported. Indicates that the specified heartbeat period is the same as the current value.

Indicates that this operation fails.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Table 2-59 Parameters for triggering heartbeat notifications Parameter managerIdentifier In/Out In Description Indicates the identifier of the NMS triggering the heartbeat notification. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. In addition. Suppor t (Y/N) Y Table 2-60 Values of triggering heartbeat notifications Returned Value Success Failure Description Indicates that this operation succeeds. it does not affect the original heartbeat period.3. the NMS should be active to subscribe the heartbeat notification. When the sent heartbeat notification is triggered by the NMS.. The NMS successfully resets the heartbeat by performing the Setting Heartbeat Period operation.2 Heartbeat Notification of the CORBA Communication Surveillance When the heartbeat period is up. 2-29 Issue 03 (2010-12-31) . IRPAgent sends a heartbeat notification accordingly to the NMS. Triggering Conditions l l The heartbeat interval set by the NMS is not 0 and the interval time is up. Ltd. Suppor t (Y/N) Y Y 2. If the NMS expects a heartbeat notification. Indicates the exceptions caused by unknown reasons. the parameter must get the object reference of CSIRP through the Getting IRP Reference interface. Suppor t (Y/N) Y Y Table 2-61 Exceptions of triggering heartbeat notifications Exception InvalidManagerIdentifier TriggerHeartbeat Description Indicates that managerIdentifier is invalid. The parameter is a character string.

) Indicates the instances of MO that sends the notification. event_name e string string header. Indicates the time when the event occurs. (This parameter is null.fixed_he ader. Notification Format Table 2-62 lists the format of the heartbeat notification. Indicates the heartbeat interval. Ltd. that is.event_type Description Indicates the name of a managed domain. NOTE After sending a heartbeat notification.fixed_he ader. IRPAgent begins to count the heartbeat period again. a long remainder_of_b ody filterable_data filterable_data b c TimeBase:: UtcT string HEARTBEAT_P ERIOD unsigned short remainder_of_b ody 2-30 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.event_type Indicates the type of the reported heartbeat notification notifyHeartbeat.2 Common Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide l The NMS successfully passes the Triggering Heartbeat Notifications operation.fixed_he ader filterable_data Indicates the name of an event. Indicates the notification identifier and is used to exclusively identify a notification.. the attribute is used to indicate the currently defined interval. Because the NMS may modify the heartbeat interval. The value of this parameter is defined by CSIRPNotifications::notifyHeartbea t::EVENT_TYPE. type_name string header. Issue 03 (2010-12-31) . the CSIRP object instance. Table 2-62 Format of the heartbeat notification Attribute Name domain_name Type string Domain header. Indicates the identifier of the IRPAgent that generates notifications. This parameter shows the version number of the associated IRP information model.

Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. MANAGER_IDE NTIFIER remainder_of_b ody l If triggerFlag is IRPManager.M2000 Northbound CORBA Interface Developer Guide 2 Common Management Function of the CORBA Interface Attribute Name TRIGGER_FLA G Type ENUM {IRPMana ger.. the value of the parameter is the same as that for the triggerHeartbeat operation. the value of the parameter is null. Ltd. CHANNEL_ID string remainder_of_b ody The channel identifier of the OMG notification service. IRPAgent}. The attribute is valued as ENUM {IRPManager. IRPAgent } string Domain remainder_of_b ody Description Indicates whether the notification is normal or triggered by IRPManager. NOTE CosNotification::PropertySeq is the value type of remainder_of_body. 2-31 . l If triggerFlag is IRPAgent.

.

. The NMS can use the interfaces to manage configuration managed objects. When a configuration object needs to be created. and relative distinguished name (RDN). deleted.1 Getting to Know Configuration Management of the CORBA Interface This describes the concepts of the managed object (MO). and modify the interfaces of configuration managed objects.2 Common Configuration Management of the CORBA Common configuration has the function of actively reporting the change of a configuration object. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. You can query.M2000 Northbound CORBA Interface Developer Guide 3 Configuration Management Function of the CORBA Interface 3 Configuration Management Function of the CORBA Interface About This Chapter The configuration management interface has the following three functions: BasicCMIRP.3 Function and Interface of Basic Configuration Management of the CORBA BasicCMIRP provides interface operations for configuration managed objects. and BulkCMIRP. 3-1 . or modified. 3. 3. distinguished name (DN). Huawei only supports the interface of querying configuration managed objects. KernelCMIRP. or requests the NMS to synchronize the configuration. delete. Ltd. 3. create. network resource model (NRM). KernelCMIRP actively sends a notification to the NMS for managing configuration objects.

. Issue 03 (2010-12-31) . 3-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. DN and RDN A DN is the unique identification of an MO. which is provided by IRPAgent. It is an instance of a managed object class (MOC) that is defined in the network resource. which consists of a prefix and a set of RDNs. An MO is also a network resource that can be managed. It includes MOCs and their relevant attributes and operations.2 Description of DN String. Network Resource Model (NRM) An NRM. network resource model (NRM). see 7.1 Getting to Know Configuration Management of the CORBA Interface This describes the concepts of the managed object (MO). distinguished name (DN). Managed Object (MO) An MO is an abstract entity that can be accessed through an open interface in two or more systems. For details about the DN syntax. and relative distinguished name (RDN).3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide 3. is a model of the actual network resource that is managed. Ltd.

. deleted.sh 2 If the system displays the following information. getting KernelCMIRP operation profile.xsd" subNetworkId="2" dnPrefix="www. # modify_SubNetworkId.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Schema/ServiceConfig..xml . you can perform the following steps to modify SubNetworkId of a DN to identify the data reported by each M2000. notifyCMSynchronizationRecommended in the common configuration management of the CORBA interface.. 3-3 .2.. This part takes changing SubNetworkId to 2 for example. Run the following command to navigate to the installation directory of the M2000 server.2 Common Configuration Management of the CORBA Common configuration has the function of actively reporting the change of a configuration object. The default installation directory of the M2000 server is /opt/OMC. Current Corba Interface is CorbaNBI NBIV1. 3.huawei.sh 3. getting KernelCMIRP notification profile. or requests the NMS to synchronize the configuration. Modify success! Please Restart IRPService! 4.2. Run the following command to check the modification result: # cat /export/home/omc/var/etc/IRPService/itf_n_config.M2000 Northbound CORBA Interface Developer Guide NOTE 3 Configuration Management Function of the CORBA Interface When an NMS manages a network through multiple M2000s. you can infer that SubNetworkId is changed to 2 successfully. you can infer that SubNetworkId is already changed to 2. notifyObjectDeletion. Run the following command to restart IRPService: # svc_adm -cmd restartsvc IRPService After the service is restarted. Ltd. # . or modified. run the following command to view the running status of the service and ensure that it is running properly: # svc_adm -cmd status | grep IRPService If the system displays the following information. IRPService [running ] 5. run the following command: # cd /opt/OMC 2. and getting NRM versions.. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.xml If the following information is displayed in the beginning of the file.2 Notification Description of the Common Configuration Management of the CORBA The part describes the notifyObjectCreation.0 Begin to modify the value of subNetworkId in the CvtDef_Omc.2. you can infer that IRPService is running properly. The common configuration management involves getting KernelCMIRP versions.xml . 3. When a configuration object needs to be created. <SubNetwork xmlns:xsi="http://www.com"> 3. Begin to modify the value of subNetworkId in the itf_n_config./svc_profile. By default. Run the following command to modify SubNetworkId. KernelCMIRP actively sends a notification to the NMS for managing configuration objects. 1. notifyAttributeValueChange.1 Interface Description of the Common Configuration Management of the CORBA This describes the common configuration management of the CORBA interface.w3. Run the environment variable script. .

and getting NRM versions. ManagedGenericIRPSystem::InvalidParameter). Table 3-1 Values of getting KernelCMIRP versions Returned Value VersionNumberSet Description Indicates a set of versions that the KernelCMIRP supports. getting KernelCMIRP notification profile. Support (Y/N) Y Table 3-2 Exceptions of getting KernelCMIRP versions Exception GetKernelCMIRPVersionsException Description Indicates the exceptions caused by unknown reasons. l Function format ManagedGenericIRPConstDefs::VersionNumberSet get_kernel_CM_IRP_versions () raises (GetKernelCMIRPVersionsException).1 Interface Description of the Common Configuration Management of the CORBA This describes the common configuration management of the CORBA interface. Issue 03 (2010-12-31) . Ltd.. There is no parameter in getting KernelCMIRP versions. Huawei supports only one of the KernelCMIRP versions. ManagedGenericIRPSystem::OperationNotSupported. The value of VersionNumberSet is a set of strings.2. 3-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Function format ManagedGenericIRPConstDefs::MethodList get_kernel_CM_IRP_operation_profile( in ManagedGenericIRPConstDefs::VersionNumber kernel_CM_IRP_version ) raises ( GetKernelCMIRPOperationProfileException. getting KernelCMIRP operation profile.3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide 3. The common configuration management involves getting KernelCMIRP versions. Getting KernelCMIRP Versions l Function description The NMS invokes get_kernel_CM_IRP_versions to get the KernelCMIRP version information. Support (Y/N) Y Getting KernelCMIRP Operation Profile l Function description The NMS invokes get_kernel_CM_IRP_operation_profile to get the profile of operations supported by a specified version of KernelCMIRP.

. Indicates that the operation is not supported. Suppor t (Y/N) Y Table 3-4 Values of getting KernelCMIRP operation profile Returned Value MethodList Description Indicates the information list of operations that the FileTransferIRP supports.M2000 Northbound CORBA Interface Developer Guide 3 Configuration Management Function of the CORBA Interface Table 3-3 Parameters for getting KernelCMIRP operation profile Parameter kernel_CM_IRP_version In/Out In Description Indicates the KernelCMIRP version information in the IRP profile obtained by the NMS. l Function format ManagedGenericIRPConstDefs::MethodList get_kernel_CM_IRP_notification_profile ( in ManagedGenericIRPConstDefs::VersionNumber kernel_CM_IRP_version ) raises ( Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The information list contains the following items: l Names of operations l Parameter lists Support (Y/N) Y Table 3-5 Exceptions of getting KernelCMIRP operation profile Exception InvalidParameter Description Indicates that the kernel_CM_IRP_version is invalid or null. The version ID should be consistent with the version ID returned by Getting kernel CMIRP Versions. Indicates the exceptions caused by unknown reasons. Ltd. Support (Y/N) Y OperationNotSupported GetKernelCMIRPOperationProfileException N Y Getting KernelCMIRP Notification Profile l Function description The NMS invokes get_kernel_CM_IRP_notification_profile to get the profile of notifications supported by KernelCMIRP. 3-5 .

Ltd. ManagedGenericIRPSystem::OperationNotSupported. The version ID should be consistent with the version ID returned by Getting kernel CMIRP Versions. Issue 03 (2010-12-31) . Support (Y/N) Y Table 3-7 Values of getting KernelCMIRP notification profile Returned Value MethodList Description Indicates the profile list of notifications that an KernelCMIRP supports.3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide GetKernelCMIRPNotificationProfileException. Indicates that the operation is not supported. Support (Y/N) Y OperationNotSupported GetKernelCMIRPNotificationProfileException N Y Getting NRMIRP Versions l 3-6 Function description Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The profile list contains the following items: l Names of notifications supported by the KernelCMIRP l Names of fields in the notification (including the names of filterable_data and remainder_of_body fields) Suppor t (Y/N) Y Table 3-8 Exceptions of getting KernelCMIRP notification profile Exception InvalidIRPVersion Description Indicates that the given kernel_CM_IRP_version is invalid or null.. Table 3-6 Parameters for getting KernelCMIRP notification profile Parameter kernel_CM_IRP_version In/Out In Description Indicates the KernelCMIRP version information in the IRP profile obtained by the NMS. Indicates the exceptions caused by unknown reasons. ManagedGenericIRPSystem::InvalidParameter).

the parameter versionNumberList lists the version information about standard specifications that work as the extension basis. Ltd. Accordingly. Table 3-9 Parameters for getting NRMIRP versions Parameter versionNumberList In/Out Out Description Indicates the version of the NRMs supported by Agent. the parameter versionNumberList lists information about the extended version. Table 3-10 Exceptions of getting NRMIRP versions Exception GetNRMIRPVersion Description Indicates the exceptions caused by unknown reasons. out ManagedGenericIRPConstDefs::VersionNumberSet vSEVersionNumberList ) raises (GetNRMIRPVersion). l Function format void get_NRM_IRP_version ( out ManagedGenericIRPConstDefs::VersionNumberSet versionNumberList.. The version information has the following three parts: l Version information about standard specifications which work as the basis l Unique ID of the manufacturer l Version information about the extended NRM of this manufacturer Y Support (Y/N) Y There is no value in getting NRMIRP versions. This NRM is the extension on existing specifications.M2000 Northbound CORBA Interface Developer Guide 3 Configuration Management Function of the CORBA Interface The NMS invokes get_NRM_IRP_version to get the version of NRM supported by IRPAgent. Support (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. In this situation. 3-7 . The NRM has the following types: l Common NRM l Wireless access NRM l Core network NRM vSEVersionNumberList Out Indicates the unique version of the extended NRM supported by Agent.

This parameter shows the version number of the associated IRP information model. event_name e string string header.fixed_he ader filterable_data Indicates the name of an event. type_name string header.2. The value is defined by KernelCmNotifications::MO Creation::EVENT_TYPE. notifyObjectCreation When a configuration managed object is added. Ltd. l Notification format Table 3-11 lists the format of the notifyObjectCreation notification. the notifyObjectCreation notification.event_type Description Indicates the name of a managed domain. notifyCMSynchronizationRecommended in the common configuration management of the CORBA interface.fixed_he ader. notifyObjectDeletion.. send the notifyObjectCreation notification. Issue 03 (2010-12-31) . After the NMS receives the notification. (This parameter is null.fixed_he ader. the DN of the new MO instances. You need to not query configuration managed objects by querying an interface. Indicates the type of the reported notification. notifyAttributeValueChange. – The OMC adds a management NE. Indicates the notification identifier and is used to exclusively identify a notification.) Indicates the instances of MO that sends the notification.3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide 3.2 Notification Description of the Common Configuration Management of the CORBA The part describes the notifyObjectCreation. that is. add an MO at the NMS side according to e and ATTRIBUTE_LIST in the notification.event_type a long remainder_of_b ody 3-8 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Triggering conditions – An NE adds a configuration managed object. Table 3-11 Notification of notifyObjectCreation Attribute Name domain_name Type string Domain header. that is.

l Unknown The cause for triggering the notification is unknown. The list includes: l Attribute name l Value NOTE CosNotification::PropertySeq is the value type of remainder_of_body.. ADD_TEXT SOURCE string string remainder_of_b ody remainder_of_b ody ATTRIBUTE_LIST KernelCm Notificatio ns::MOCre ation::Initi alAttribute Values remainder_of_b ody Indicates the attribute list of a new object.M2000 Northbound CORBA Interface Developer Guide 3 Configuration Management Function of the CORBA Interface Attribute Name b c Type TimeBase: :UtcT string Domain filterable_data filterable_data Description Indicates the time when the event occurs. Ltd. Indicates the additional text related to the notification. Indicates the indicator of the source operation that triggers this notification. After the NMS receives the notification. The value of the attribute may be one of the following values: l Resource_operation This notification is triggered by an operation on the managed resources. 3-9 . notifyObjectDeletion The notifyObjectDeletion notification is sent when an MO is deleted. delete the corresponding object or its sub-object at the NMS side according to the e field in the notification. l Management_operation The notification is triggered by an NMS operation delivered from Manager. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Indicates the identifier of the IRPAgent that generates notifications.

event_ty pe header.3 Configuration Management Function of the CORBA Interface NOTE M2000 Northbound CORBA Interface Developer Guide The e field in the notification is the base object of the object to be deleted. This parameter shows the version number of the associated IRP information model. type_name string a long remainder_of_ body filterable_data filterable_data b c TimeBase:: UtcT string ADD_TEXT string remainder_of_ body 3-10 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.event_ty pe Description Indicates the name of a managed domain. (This parameter is null. Table 3-12 Notification of notifyObjectDeletion Attribute Name domain_name Type string Domain header. Indicates the additional text related to the notification. event_name e string string header. – The OMC deletes the configuration of an NE. l Notification format Table 3-12 lists the format of the notifyObjectDeletion notification. The value is defined by KernelCmNotifications::MODeleti on::EVENT_TYPE. the notifyObjectDeletion notification.) Indicates the instances of MO that sends the notification. the DN of the deleted MO instances.fixed_h eader filterable_data Indicates the name of an event. Indicates the notification identifier and is used to exclusively identify a notification. Indicates the time when the event occurs. Indicates the type of the reported notification. The sub-object does not send the notifyObjectDeletion notification. Issue 03 (2010-12-31) . Ltd. that is.fixed_h eader. Indicates the identifier of the IRPAgent that generates notifications. l Triggering condition – A configuration object of an NE is deleted. that is..fixed_h eader.

M2000 Northbound CORBA Interface Developer Guide 3 Configuration Management Function of the CORBA Interface Attribute Name SOURCE Type string Domain remainder_of_ body Description Indicates the indicator of the source operation that triggers this notification. – Attribute values of an NE managed by the OMC are changed. l Management_operation The notification is triggered by an NMS operation delivered from Manager. Ltd. l Triggering condition – Attributes of a configuration object at an NE side are modified. The list includes: l Attribute name l Value NOTE CosNotification::PropertySeq is the value type of remainder_of_body. After the NMS receives the notification. 3-11 . Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Notification format Table 3-13 lists the format of the notifyAttributeValueChange notification. notifyAttributeValueChange The notifyAttributeValueChange notification is sent when an MO is modified.. modify the MO in the NMS according to e and ATTRIBUTE_LIST in the notification. The value of the attribute may be one of the following values: l Resource_operation This notification is triggered by an operation on the managed resources. ATTRIBUTE_ LIST KernelCmN otifications:: MODeletion ::AttributeV alues remainder_of_ body Indicates the attribute list of an object to be deleted. l Unknown The cause for triggering the notification is unknown.

) Indicates the instances of MO that sends the notification. Indicates the additional text related to the notification. Indicates the identifier of the IRPAgent that generates notifications. Indicates the notification identifier and is used to exclusively identify a notification. that is. The value if defined by KernelCmNotifications::AttributeValu eChange::EVENT_TYPE. type_name string a long b c ADD_TEXT SOURCE TimeBase:: UtcT string string string 3-12 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Unknown The cause for triggering the notification is unknown. l Management_operation The notification is triggered by an NMS operation from Manager.fixe d_header filterable_d ata remainder_ of_body filterable_d ata filterable_d ata remainder_ of_body remainder_ of_body Indicates the name of an event. the notifyAttributeValueChange notification. This parameter shows the version number of the associated IRP information model. The value of the attribute may be one of the following values: l Resource_operation This notification is triggered by an operation on the managed resources.e vent_type header. the DN of the modified MO. that is.. Ltd.3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 3-13 Notification of notifyAttributeValueChange Attribute Name domain_name Type string Domain header.e vent_type Description Indicates the name of a managed domain. Indicates the type of the reported notification. event_name e string string header. (This parameter is null.fixe d_header. Indicates the time when the event occurs. Issue 03 (2010-12-31) .fixe d_header. Indicates the indicator of the source operation that triggers this notification.

Table 3-14 Notification of notifyCMSynchronizationRecommended Attribute Name domain_name Type string Domain header..M2000 Northbound CORBA Interface Developer Guide 3 Configuration Management Function of the CORBA Interface Attribute Name MODIFIED_A TTRIBUTE_S ET Type KernelCm Notificatio ns::Attribut eValueCha nge::Modif iedAttribut eSet Domain remainder_ of_body Description Indicates the list of the changed object attributes. the notification is sent. The list includes: l Attribute name.) 3-13 type_name string header.fixed_he ader. – The OMC timing mechanism sends synchronization information to an NE. l Attribute values after the change. NOTE Both the notification of creating the ManagedElement object and the notification of synchronizing configuration information are sent. event_name string header.fixed_he ader Indicates the name of an event. that is. Indicates the type of the reported notification. For example. l Attribute values before the change (optional). The value is defined by KernelCmNotifications::CMSynchr onizationRecommended::EVENT_ TYPE.fixed_he ader. the NMS can synchronize configuration data of IRPAgent according to the BASE_MOI field and the SCOPE field in the notification. l Triggering condition – The OMC adds a management NE. This parameter shows the version number of the associated IRP information model. (This parameter is null. Ltd. the notifyCMSynchronizationRecommended notification. After the NMS receives the notification.event_type Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. start a timing task to synchronize at 00:00 every day. .event_type Description Indicates the name of a managed domain. l Notification format Table 3-14 lists the format of the notifyCMSynchronizationRecommended notification. notifyCMSynchronizationRecommended When configuration information is modified greatly.

3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name e Type string Domain filterable_data Description Indicates the instances of MO that sends the notification. BASE_SUBTREE. }. Indicates the class of the base MO of a subtree specified to be synchronized. Indicates the time when the event occurs. Indicates the additional text related to the notification. BASE_NTH_LEVEL. Indicates the identifier of the IRPAgent that generates notifications. the configured MO instances. SCOPE KernelCm ConstDefs ::ScopePa ra 3-14 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Unsigned long level. that is. The attribute value may be: l Base MO l Whole subtree l From the base MO to the layer N subtree l Objects in layer N The default value is the whole subtree. struct ScopePara { ScopeType type. Indicates the scope specified for synchronization. This field is not supported. Issue 03 (2010-12-31) . Indicates the notification identifier and is used to exclusively identify a notification. a long remainder_of_b ody filterable_data filterable_data b c TimeBase ::UtcT string ADD_TEXT BASE_MOC string string remainder_of_b ody remainder_of_b ody BASE_MOI string remainder_of_b ody remainder_of_b ody Indicates the instance identifier of the base MO of a subtree specified to be synchronized. Ltd. The value is defined as follows: enum ScopeType { BASE_ONLY.. BASE_ALL }.

Ltd. Getting BasicCMIRP Versions l Function description The NMS invokes get_basicCm_IRP_version to get the BasicCMIRP version information. Support (Y/N) Y Getting BasicCMIRP Operation Profile l Function description The NMS invokes get_basicCm_IRP_operation_profile to get the profile of operations supported by a specified version of BasicCMIRP.. Huawei supports only one of the BasicCMIRP versions. The value of VersionNumberSet is a set of strings. There is no parameter in getting BasicCMIRP versions. delete. 3-15 . create. The NMS can use the interfaces to manage configuration managed objects.M2000 Northbound CORBA Interface Developer Guide NOTE 3 Configuration Management Function of the CORBA Interface CosNotification::PropertySeq is the value type of remainder_of_body. l Function format ManagedGenericIRPConstDefs::MethodList get_basicCm_IRP_operation_profile ( in ManagedGenericIRPConstDefs::VersionNumber basicCm_IRP_version ) raises ( Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Support (Y/N) Y Table 3-16 Exceptions of getting BasicCMIRP versions Exception GetBasicCmIRPVersion Description Indicates the exceptions caused by unknown reasons. Table 3-15 Values of getting BasicCMIRP versions Returned Value VersionNumberSet Description Indicates a set of versions that the BasicCMIRP supports. and modify the interfaces of configuration managed objects.3 Function and Interface of Basic Configuration Management of the CORBA BasicCMIRP provides interface operations for configuration managed objects. You can query. 3. l Function format ManagedGenericIRPConstDefs::VersionNumberSet get_basicCm_IRP_version() raises (GetBasicCmIRPVersion). Huawei only supports the interface of querying configuration managed objects.

Ltd. Issue 03 (2010-12-31) . The version ID should be consistent with the version ID returned by Getting BasicCMIRP Versions. The information list contains the following items: l Names of operations l Parameter lists Support (Y/N) Y Table 3-19 Exceptions of getting BasicCMIRP operation profile Exception InvalidParameter Description Indicates that the given basicCm_IRP_version is invalid or null. 3-16 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Support (Y/ N) Y OperationNotSupported GetBasicCmIRPOperationProfile N Y Getting BasicCMIRP Notification Profile l Function description The NMS invokes get_basicCm_IRP_notification_profile to get the profile of notifications supported by BasicCMIRP. Indicates the exceptions caused by unknown reasons. Support (Y/N) Y Table 3-18 Values of getting BasicCMIRP operation profile Returned Value MethodList Description Indicates the information list of operations that the BasicCMIRP supports. ManagedGenericIRPSystem::InvalidParameter). Indicates that the operation is not supported.. ManagedGenericIRPSystem::OperationNotSupported. Table 3-17 Parameters for getting BasicCMIRP operation profile Parameter basicCm_IRP_version In/Out In Description Indicates the BasicCMIRP version information in the IRP profile obtained by the NMS.3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide GetBasicCmIRPOperationProfile.

M2000 Northbound CORBA Interface Developer Guide

3 Configuration Management Function of the CORBA Interface

l

Function format
ManagedGenericIRPConstDefs::MethodList get_basicCm_IRP_notification_profile ( in ManagedGenericIRPConstDefs::VersionNumber basicCm_IRP_version ) raises ( GetBasicCmIRPNotificationProfile, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter);

Table 3-20 Parameters for getting BasicCMIRP notification profile Parameter basicCm_IRP_version In/Out In Description Indicates the BasicCMIRP version information in the BasicCMIRP profile obtained by the NMS. The version ID should be consistent with the version ID returned by Getting BasicCMIRP Versions. Support (Y/N) Y

Table 3-21 Values of getting BasicCMIRP notification profile Returned Value MethodList Description Indicates the profile list of notifications that an BasicCMIRP supports. The profile list contains the following items: l Names of notifications supported by the BasicCMIRP l Names of fields in the notification (including the names of filterable_data and remainder_of_body fields) Support (Y/N) Y

NOTE

Notifications are not defined in the BasicCMIRP.

Table 3-22 Exceptions of getting BasicCMIRP notification profile Exception InvalidParameter Description Indicates that the given basicCm_IRP_version is invalid or null. Indicates that the operation is not supported. Support (Y/ N) Y

OperationNotSupported

N

Issue 03 (2010-12-31)

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

3-17

3 Configuration Management Function of the CORBA Interface

M2000 Northbound CORBA Interface Developer Guide

Exception GetBasicCmIRPNotificationProfile

Description Indicates the exceptions caused by unknown reasons.

Support (Y/ N) Y

Finding Managed Objects
l Function description The NMS invokes find_managed_objects to query MOs in a specified condition and their attribute values. l Function format(1)
BasicCmInformationIterator find_managed_objects ( in BasicCMIRPConstDefs::DN baseObject, in BasicCMIRPConstDefs::SearchControl searchControl, in BasicCMIRPConstDefs::AttributeNameSet requestedAttributes ) raises ( FindManagedObjects, ManagedGenericIRPSystem::ParameterNotSupported, ManagedGenericIRPSystem::InvalidParameter, ManagedGenericIRPSystem::ValueNotSupported, ManagedGenericIRPSystem::OperationNotSupported, UndefinedMOException, IllegalDNFormatException, UndefinedScopeException, IllegalScopeTypeException, IllegalScopeLevelException, IllegalFilterFormatException, FilterComplexityLimit);

Table 3-23 Parameters for finding managed objects (I) Parameter baseObject In/Out In Description Indicates the ID of the base object instance. The parameter identifies exclusively the base object of an MO subtree. Support (Y/N) Y

3-18

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

Issue 03 (2010-12-31)

M2000 Northbound CORBA Interface Developer Guide

3 Configuration Management Function of the CORBA Interface

Parameter searchControl

In/Out In

Description Defines query conditions. The structure of the parameter is as follows:
struct SearchControl { ScopeType type; unsigned long level; FilterType filter; ResultContents contents; };

Support (Y/N) Y

The type field defines a query range and is used in combination with the level field. l If type is BASE_ONLY and level is null, a base object is returned. l If type is BASE_NTH_LEVEL, all the objects at the level layer are returned. If level is 0, the base object is returned. l If type is BASE_SUBTREE, all the objects between base objects and objects at the level layer are returned. l If type is BASE_ALL and level is null, base objects and all the objects under the base objects are returned. l The filter field is not supported. l If contents is NAMES, only the DNs of required MOs are returned and attributes of the MOs are not returned. l If contents is NAMES_AND_ATTRIBUTES, the DNs and attributes of required MOs are returned. requestedAttributes in Defines a name list of attributes to be queried. Y

Table 3-24 Values of finding managed objects (I) Returned Value BasicCmInformationIterator Description Indicates that the returned value is the CORBA object of BasicCmInformationIterator. Support (Y/N) Y

Issue 03 (2010-12-31)

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

3-19

Indicates an illegal filter condition. Ltd. Issue 03 (2010-12-31) . Indicates a complex filter condition that cannot be parsed. Indicates that the given parameters are not supported. Indicates the value is not supported. Table 3-26 Parameters for finding managed objects (II) Parameter how_many In/ Out In Description Indicates the number of objects that the NMS expects. Indicates the exceptions caused by unknown reasons. Indicates that the given parameter is invalid. Indicates an illegal filter scope type. Indicates that the filter scope is undefined.. Indicates that the operation is not supported. ManagedGenericIRPSystem::OperationNotSupported). Indicates an illegal filter scope level. The value of the parameter must be greater than 0. Indicates that baseObjectInstance is invalid.3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 3-25 Exceptions of finding managed objects (I) Exception Description Suppo rt (Y/ N) Y Y N Y N N Y Y N N N Y IllegalDNFormatException UndefinedScopeException IllegalScopeTypeException IllegalScopeLevelException IllegalFilterFormatException FilterComplexityLimit ParameterNotSupported InvalidParameter UndefinedMOException ValueNotSupported OperationNotSupported FindManagedObjects Indicates an illegal DN. Support (Y/N) Y 3-20 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. out BasicCMIRPConstDefs::ResultSet fetchedElements ) raises ( NextBasicCmInformations. l Function format(2) boolean next_basicCmInformations ( in unsigned short how_many. ManagedGenericIRPSystem::InvalidParameter.

Indicates that the operation is not supported. 3-21 . Support (Y/N) Y Table 3-27 Values of finding managed objects (II) Returned Value boolean Description Indicates that the returned value is of the Bool type. the length of the parameter is equal to how_many. l If the current configuration object number is less than or equal to the value of how_many. l TRUE indicates that some object information is not returned. The list includes the following subitems: l mo: the object class name of each returned attribute value l attributes: the list of queried attribute names and values NOTE l If the current configuration object number is more than the value of how_many. for example the value of InvalidParameter is 0. The list includes DNs and attribute lists.M2000 Northbound CORBA Interface Developer Guide 3 Configuration Management Function of the CORBA Interface Parameter fetchedElements In/ Out Out Description Returns an information list of configuration objects. Description Indicates operation failure caused by some unknown causes. Indicates an invalid parameter. Support (Y/N) Y Table 3-28 Exceptions of finding managed objects (II) Exception NextBasicCmInformations InvalidParameter OperationNotSupported l Function format(3) void destroy () raises ( DestroyException.. ManagedGenericIRPSystem::OperationNotSupported). l FALSE indicates that all object information is returned and iterator objects are released. Ltd. the parameter is the information about current configuration objects. Support (Y/N) Y Y N Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

1 2 Step The NMS uses the find_managed_objects interface to query MOs in a specified condition. Indicates that the operation is not supported.3 Configuration Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 3-29 Exceptions of finding managed objects (III) Exception DestroyException OperationNotSupported l Event flow The process of querying the event flow of MOs is shown in Figure 3-1.. Issue 03 (2010-12-31) 3-22 . Support (Y/N) Y N Table 3-30 lists the steps used for querying the event flow of MOs. IRPAgent queries MOs according to conditions provided by the NMS and creates the BasicCmInformationIterator object. Ltd. Table 3-30 Steps used for the event flow of querying MOs No. Figure 3-1 Querying the event flow of MOs Description Indicates the exceptions caused by unknown reasons. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

. 3 Step The NMS invokes the next_basicCmInformation interface of BasicCmInformationIterator to query qualified MOs. Ltd. 3-23 . 4 When the NMS does not select all the MO information. infer that the information list of MOs is not null. invoke destroy to release the BasicCmInformationIterator object. infer that the information list of MOs is null and IRPAgent automatically releases the BasicCmInformationIterator object. l If the returned value is true. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l If the returned value is false.M2000 Northbound CORBA Interface Developer Guide 3 Configuration Management Function of the CORBA Interface No.

.

and reporting alarms in real time. acknowledging alarms. alarms can be reported in real time. The alarm management has the following functions: querying alarms.2 Alarm Management of the CORBA The alarm management of the CORBA interface describes the CORBA alarm management and its functions. acknowledge. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.1 Introduction to the CORBA Alarm Management With alarm management function. you can query. clearing alarms. Ltd. counter-acknowledge alarms. In addition. 4. 4.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface 4 Alarm Management Function of the CORBA Interface About This Chapter The AlarmIRP interface is the only interface used in alarm management. clear.. and add comments to alarms. unacknowledging alarms. 4-1 .

Getting AlarmIRP Versions l l Function description The NMS invokes get_alarm_IRP_versions to get information about AlarmIRP versions. Table 4-1 Values of getting AlarmIRP versions Returned Value VersionNumberSet Description Indicates a set of versions that AlarmIRP supports. while the NMS manages alarms through the alarm operation interface. getting alarm list. unacknowledging alarms. and clearing alarms. alarm clearance notification.2. alarm acknowledgement status change notification.2 Alarm Management of the CORBA The alarm management of the CORBA interface describes the CORBA alarm management and its functions. Function format ManagedGenericIRPConstDefs::VersionNumberSet get_alarm_IRP_versions () raises (GetAlarmIRPVersions). and add comments to alarms. new alarm notification. the NMS collects alarm statistics and synchronizes alarms. getting alarm list.2.3 Mechanism for Forwarding Common Alarms In a multi-mode base station (MBTS). 4. clear. Through the alarm query interface. 4. counter-acknowledge alarms. Issue 03 (2010-12-31) Support (Y/N) Y . and clearing alarms.2 Notification Description of the CORBA Alarm Management The description of the CORBA alarm management notification contains the triggering conditions and formats of the potential faulty alarm list notification. getting AlarmIRP operation profile. 4.1 Introduction to the CORBA Alarm Management With alarm management function. getting AlarmIRP operation profile. 4. Huawei supports only one of the AlarmIRP versions. getting AlarmIRP notification profile.2.1 Interface Description of the CORBA Alarm Management The CORBA alarm management involves getting AlarmIRP versions. You can differentiate normal mode alarms from common alarms by viewing alarm information. alarm comment notification.2. getting alarm count. acknowledging alarms. common alarms can be generated on certain common devices. Ltd. getting alarm count.1 Interface Description of the CORBA Alarm Management The CORBA alarm management involves getting AlarmIRP versions. alarms can be reported in real time. There is no parameter in getting AlarmIRP versions. acknowledge. The value of VersionNumberSet is a set of strings. 4. alarm contents. unacknowledging alarms. and alarm change notification.. you can query. 4-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide 4. In addition. alarm contents. The real-time report of alarms enables the NMS to handle alarms in real time. acknowledging alarms. getting AlarmIRP notification profile.

The value of this parameter should be consistent with the version number displayed in Getting AlarmIRP Versions. ManagedGenericIRPSystem::OperationNotSupported.. Ltd. ManagedGenericIRPSystem::InvalidParameter). Support (Y/N) Y Getting AlarmIRP Operation Profile l Function description The NMS invokes get_alarm_IRP_operations_profile to get the profile of operations supported by AlarmIRP. The information list contains the following items: l Names of operations l Parameter lists Suppor t (Y/N) Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 4-3 . Suppor t (Y/N) Y Table 4-4 Values of getting AlarmIRP operation profile Returned Value MethodList Description Indicates the information list of operations that AlarmIRP supports. Table 4-3 Parameters for getting AlarmIRP operation profile Parameter alarm_irp_version In/Out in Description Indicates the version of managed objects in the AlarmIRP managed domain.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Table 4-2 Exceptions of getting AlarmIRP versions Exception GetAlarmIRPVersions Description Indicates the exceptions caused by unknown reasons. l Function format ManagedGenericIRPConstDefs::MethodList get_alarm_IRP_operations_profile ( in ManagedGenericIRPConstDefs::VersionNumber alarm_irp_version ) raises ( GetAlarmIRPOperationsProfile.

Indicates that this operation is not supported.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 4-5 Exceptions of getting AlarmIRP operation profile Exception InvalidParameter OperationNotSupported GetAlarmIRPOperationsProfile Description Indicates that the given alarm_irp_version is invalid or null. ManagedGenericIRPSystem::OperationNotSupported. Suppor t (Y/N) Y N Y Getting AlarmIRP Notification Profile l Function description The NMS invokes get_alarm_IRP_notification_profile to get the profile of notifications supported by AlarmIRP.. Indicates the exceptions caused by unknown reasons. The value of this parameter should be consistent with the version number displayed in Getting AlarmIRP Versions. l Function format ManagedGenericIRPConstDefs::MethodList get_alarm_IRP_notification_profile ( in ManagedGenericIRPConstDefs::VersionNumber alarm_irp_version ) raises ( GetAlarmIRPNotificationProfile. The profile list contains the following items: l Names of notifications supported by AlarmIRP l Names of fields in the notification (including the names of filterable_data and remainder_of_body fields) 4-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. ManagedGenericIRPSystem::InvalidParameter). Table 4-6 Parameters for getting AlarmIRP notification profile Parameter alarm_irp_version In/Out in Description Indicates the AlarmIRP version in the AlarmIRP profile obtained by the NMS. Ltd. Support (Y/N) Y Table 4-7 Values of getting AlarmIRP notification profile Returned Value MethodList Description Indicates the profile list of notifications that an AlarmIRP supports. Issue 03 (2010-12-31) Support (Y/N) Y .

refer to 7. NOTE For details about the filtering restrictions.1. no filtering conditions are set.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Table 4-8 Exceptions of getting AlarmIRP notification profile Exception InvalidParameter OperationNotSupported GetAlarmIRPNotificationProfile Description Indicates that the given alarm_irp_version is invalid or null. ManagedGenericIRPSystem::InvalidParameter).. if this parameter is null.2 Description of filter in get_alarm_list. only the alarm information related to the specified objects or the child objects in the current alarm list is displayed. Ltd. out AlarmInformationIterator iter ) raises ( GetAlarmList. Suppor t (Y/N) Y Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. ManagedGenericIRPSystem::ParameterNotSupported. If this parameter is a certain object. l Function format (1) AlarmIRPConstDefs::AlarmInformationSeq get_alarm_list ( in ManagedGenericIRPConstDefs::StringTypeOpt filter. 4-5 . in AlarmIRPConstDefs::DNTypeOpt base_object. Indicates that this operation is not supported. Indicates the exceptions caused by unknown reasons. filter in Defines the filtering conditions for the alarm information to be obtained by the NMS. Table 4-9 Parameters for getting alarm list (I) Parameter base_object In/Out in Description Either null or a certain object. all the alarm information in the current alarm list is displayed. Suppor t (Y/N) Y N Y Getting Alarm List l Function description The NMS invokes get_alarm_list to get an alarm list of the current operations that meet certain requirements. For the Union type. out boolean flag. If this parameter is null.

This parameter is the CORBA object of AlarmInformationIterator. the Returned Value shows the alarms that meet certain requirements. Issue 03 (2010-12-31) . Support (Y/N) Y Table 4-11 Exceptions of getting alarm list (I) Exception InvalidParameter ParameterNotSupported GetAlarmList Description Indicates that the parameter is invalid. Y Table 4-10 Values of getting alarm list (I) Returned Value AlarmInformationSeq Description l If flag is true. the iter shows the alarm information while the Returned Value list is null.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Parameter flag In/Out out Description l If flag is true. l If flag is false. the Returned Value shows alarm information. out AlarmIRPConstDefs::AlarmInformationSeq alarm_informations ) raises ( NextAlarmInformations. 4-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Suppor t (Y/N) Y iter out Indicates that the alarm information is obtained through iter when flag is false. Indicates that this operation is not supported. the Returned Value is null. Ltd. ManagedGenericIRPSystem::InvalidParameter). Indicates the exceptions caused by unknown reasons. l If flag is false. Support (Y/N) Y N Y l Function format (2) boolean next_alarmInformations ( in unsigned short how_many..

M2000 Northbound CORBA Interface Developer Guide

4 Alarm Management Function of the CORBA Interface

Table 4-12 Parameters for getting alarm list (II) Parameter how_many In/Out in Description Indicates the number of alarms that the NMS expects. The value of this parameter must be greater than 0 and less than or equal to 2000. alarm_informations out Indicates the displayed alarm information list. l If the number of current alarms exceeds the value of how_many, the sequence length of alarm_informations is equal to that of how_many. l If the number of current alarms is less than or equal to how_many, alarm_informations indicates the alarm information list. Y Suppo rt (Y/N) Y

Table 4-13 Values of getting alarm list (II) Returned Value boolean Description Indicates that the returned value is of boolean. l TRUE indicates that some alarm information is not returned. l FALSE indicates that all alarm information is returned and iterator objects are released. Support (Y/N) Y

Table 4-14 Exceptions of getting alarm list (II) Exception InvalidParameter Description Indicates that the parameter is invalid. For instance, if the value of how_many is 0, infer that this parameter is invalid. NextAlarmInformations l Function format (3)
void destroy () raises( CORBA::SystemException);

Support (Y/N) Y

Indicates that this operation is not supported.

Y

Issue 03 (2010-12-31)

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

4-7

4 Alarm Management Function of the CORBA Interface

M2000 Northbound CORBA Interface Developer Guide

Table 4-15 Exceptions of getting alarm list (III) Exception SystemException Description Indicates the exceptions caused by unknown reasons. Support (Y/N) Y

l

Event flow Figure 4-1 shows the event flow of alarm information. Figure 4-1 Event flow of alarm information

1. 2. 3. 4. 5. 6. 7.

Get alarm lists. Query alarms. The AlarmInformationIterator is displayed when the value of flag is false. All alarms are displayed when the value of flag is true. In case the value of flag is false, the next_alarmInformations is invoked. The system displays alarms. If the value false is displayed, objects are released. If the value true is displayed, the system continue to query alarms. Release objects directly.

Alarm Contents
l Unacknowledged and uncleared alarms Table 4-16 lists the format of the Unacknowledged and uncleared alarms.

4-8

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

Issue 03 (2010-12-31)

M2000 Northbound CORBA Interface Developer Guide

4 Alarm Management Function of the CORBA Interface

Table 4-16 Unacknowledged and uncleared alarms Attribute Name domain_name type_name Type string string Domain header.fixed_hea der.event_type header.fixed_hea der.event_type Description Indicates the version number of the associated IRP information model. Reports the name of a new alarm. The value of this parameter is as follows: AlarmIRPConstDefs::NotificationType :: NOTIFY_FM_NEW_ALARM. Indicates the name of an event and defines communication alarms, internal error-handling alarms, QoS alarms, and equipment alarms. The value of this parameter maps to AlarmIRPConstDefs::AlarmType. e b c g string TimeBase: :UtcT string short filterable_data filterable_data filterable_data filterable_data Indicates the object instances of an alarm. Indicates the time when an alarm occurs. Indicates the identifier of the IRPAgent. Indicates the possible reasons for an alarm and has more detailed categorizations compared with AlarmType. The value range and information about this parameter are defined in ProbableCause. h short filterable_data Indicates the severity of an alarm. The following lists severities of alarms: l INDETERMINATE l CRITICAL l MAJOR l MINOR l WARNING l CLEARED
NOTE Currently, INDETERMINATE is not supported.

event_name

string

header.fixed_hea der

Issue 03 (2010-12-31)

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

4-9

Issue 03 (2010-12-31) . the maintenance-mode alarm function is inactive. i string 4-10 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. see Reporting maintenance-mode alarms. The NMS receives maintenance-mode alarms only after this function is activated. f string remainder_of_b ody remainder_of_b ody Indicates the serial number of alarms and is used to be the only identifier for an alarm.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name jj Type long Domain filterable_data Description Vendor-customized alarm type 1: Fault alarm nn long filterable_data The maintenance-mode alarm statuses are as follows: l 0: Normal l 1: Creation l 2: Expansion l 3: Upgrade l 4: Commissioning No default value of this attribute is provided. This parameter records the Huawei alarm private information. For details about how to activate the maintenance-mode alarm function and the attribute. Indicates the detailed reasons for an alarm. The filterable_data area in alarm messages contains this attribute only after this attribute is activated. Ltd. By default..

Slot No.2. Open the /opt/OMC/etc/IRPService/itf_n_config. and then set enableSpecialAlarmStatusID to true.2. replace it with the CORBA V1. The information consists of the following items: l NE location l Vendor l NE name l Alarm name l Detailed alarm location information The format for location information is as follows: NeType: NodeB| NeLocation: ShangHai | vendor: Huawei | neName: N91003| alarmName: RF Unit Maintenance Link Failure| alarmLocation: Cabinet No.0 interface is installed by referring to the iManagerM2000V200R010C00 Guide to Query and Change Northbound CORBA Interface. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. To set the maintenance-mode alarm function.. If the installed interface is not the CORBA V1. Check whether the CORBA V1. 4. Board type=WRFU| appendInfo: NOTE AlarmIRPConstDefs::AttributeSetType is the value type of remainder_of_body. Subrack No.xml file.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name j Type string Domain remainder_of_b ody Description Indicates the detailed location information about an alarm. Run the following command to restart the IRPService service: svc_adm -cmd restartsvc IRPService l Alarms that are already acknowledged but not cleared Table 4-17 lists the format of the acknowledged but uncleared alarms. Ltd.0 interface. perform the following steps: 1. Run the following command to restart the FaultService service: svc_adm -cmd restartsvc FaultService 3.0 interface.=0.2.=1. Run the following command as user root or omcuser on the M2000 server to activate the maintenance-mode alarm function: SettingTool -cmd setparam -path "/imap/ifms/specialAlarmStatus/nbenable" -value "true" 2. 4-11 . <AlarmIRP irpId="4" Turner="synch" FileCategory="IM" ThreadNum="2" enableSpecialAlarmStatusID="false"> 5.=4.

this parameter shows the object instances of alarms occurred.fixed_header. type_name string b c g TimeBase: :UtcT string short filterable_data filterable_data filterable_data 4-12 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Indicates the identifier of the IRPAgent.fixed_header. The value of this parameter maps to AlarmIRPConstDefs::Alar mType. Indicates the time when an alarm occurs. The value range and information about this parameter are defined in ProbableCause. internal error-handling alarms. Indicates the state of an alarm.ev ent_type Description Indicates the version number of the associated IRP information model. Ltd.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 4-17 Acknowledged but uncleared alarms Attribute Name domain_name Type string Domain header. Indicates the possible reasons for an alarm and has more detailed categorizations compared with AlarmType. QoS alarms.fixed_header Indicates the name of an event and defines communication alarms. event_name string header. That is.ev ent_type header. e string filterable_data Indicates the MO instances in the alarm notification. The value of this parameter maps to AlarmIRPConstDefs::Notif icationType ::NOTIFY_FM _ACK_STATE_CHANGE D.. This parameter refers to the acknowledgement state of an alarm. Issue 03 (2010-12-31) . and equipment alarms.

M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name h Type short Domain filterable_data Description Indicates the severity of an alarm.. Ltd. The following lists the severities of alarms: l INDETERMINATE l CRITICAL l MAJOR l MINOR l WARNING l CLEARED NOTE Currently. INDETERMINATE is not supported. Vendor-customized alarm type 1: Fault alarm Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. k jj TimeBase: :UtcT long filterable_data filterable_data Indicates the time when an alarm is acknowledged. 4-13 .

The filterable_data area in alarm messages contains this attribute only after this attribute is activated. By default. Ltd. f string remainder_of_body Indicates the serial number of alarms and is used to be the only identifier for an alarm. Indicates an identifier for a user that acknowledges an alarm..4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name nn Type long Domain filterable_data Description The maintenance-mode alarm statuses are as follows: l 0: Normal l 1: Creation l 2: Expansion l 3: Upgrade l 4: Commissioning No default value of this attribute is provided. The OMC acknowledgement alarms should be performed only by OMC authorized users. the maintenance-mode alarm function is inactive. The NMS receives maintenancemode alarms only after this function is activated. For details about how to activate the maintenance-mode alarm function and the attribute. see Reporting maintenance-mode alarms. The NMS acknowledgement alarms should be acknowledged by users whose ids are in the range of ack_user_id. l string remainder_of_body 4-14 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Issue 03 (2010-12-31) .

Ltd. Slot No. Board type=WRFU| appendInfo: NOTE AlarmIRPConstDefs::AttributeSetType is the value type of remainder_of_body. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Unacknowledged but cleared alarms Table 4-18 lists the format of the unacknowledged but cleared alarms.=4. Subrack No. 4-15 ..=0. The information consists of the following items: l NE location l Vendor l NE name l Alarm name l Detailed alarm location information The format for location information is as follows: NeType: NodeB| NeLocation: ShangHai | vendor: Huawei | neName: N91003| alarmName: RF Unit Maintenance Link Failure| alarmLocation: Cabinet No. i string remainder_of_body Indicates the detailed reasons for an alarm. j string remainder_of_body Indicates the detailed location information about an alarm.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name n Type short Domain remainder_of_body Description Indicates the current state of alarm acknowledgement.=1. The value 1 indicates that the alarm in Acknowledge state. This parameter records the Huawei alarm private information.

fixed_header. Ltd.eve nt_type Description Indicates the version number of the associated IRP information model. internal error-handling alarms.fixed_header Indicates the name of an event and defines communication alarms.fixed_header.eve nt_type header. e string filterable_data Indicates the object instances in the alarm notification. event_name string header. and equipment alarms. type_name string b c g TimeBase ::UtcT string short filterable_data filterable_data filterable_data 4-16 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The value of this parameter maps to AlarmIRPConstDefs::Alar mType. Here this parameter refers to the alarms in Clear state.. Indicates the state of an alarm. The value range and information about this parameter are defined in ProbableCause. Issue 03 (2010-12-31) . Indicates the time when an alarm occurs. Indicates the identifier of the IRPAgent. The value of this parameter maps to AlarmIRPConstDefs::NotificationType : NOTIFY_FM_CLEARED_ ALARM. Indicates the possible reasons for an alarm and has more detailed categorizations compared with AlarmType. QoS alarms.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 4-18 Unacknowledged but cleared alarms Attribute Name domain_name Type string Domain header.

the maintenancemode alarm function is inactive. By default. INDETERMINATE is not supported. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. jj long filterable_data Vendor-customized alarm type 1: Fault alarm nn long filterable_data The maintenance-mode alarm statuses are as follows: l 0: Normal l 1: Creation l 2: Expansion l 3: Upgrade l 4: Commissioning No default value of this attribute is provided. 4-17 . For details about how to activate the maintenance-mode alarm function and the attribute. see Reporting maintenance-mode alarms. The following lists the severities of alarms: l INDETERMINATE l CRITICAL l MAJOR l MINOR l WARNING l CLEARED NOTE Currently. The NMS receives maintenance-mode alarms only after this function is activated. Ltd. The filterable_data area in alarm messages contains this attribute only after this attribute is activated.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name h Type short Domain filterable_data Description Indicates the severity of an alarm.

Issue 03 (2010-12-31) .4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name f Type string Domain remainder_of_body Description Indicates the serial number of alarms and is used to be the only identifier for an alarm. Ltd.. alarms can be cleared by users whose IDs are in the range of clear_user_id. 4-18 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. alarms can be cleared only by OMC authorized users. Indicates an identifier for a user that clears an alarm. the authorized user is NE. y string remainder_of_body ll i TimeBase ::UtcT string remainder_of_body remainder_of_body Indicates the time when an alarm is cleared. In case of automatic alarm clearance. For the NMS. This parameter records the Huawei alarm private information. Indicates the detailed reasons for an alarm. For the OMC.

The information consists of the following items: l NE location l Vendor l NE name l Alarm name l Detailed alarm location information The format for location information is as follows: NeType: NodeB| NeLocation: ShangHai | vendor: Huawei | neName: N91003| alarmName: RF Unit Maintenance Link Failure| alarmLocation: Cabinet No. ManagedGenericIRPSystem::ParameterNotSupported.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name j Type string Domain remainder_of_body Description Indicates the detailed location information about an alarm. ManagedGenericIRPSystem::OperationNotSupported. Board type=WRFU| appendInfo: NOTE AlarmIRPConstDefs::AttributeSetType is the value type of remainder_of_body. Ltd. Getting Alarm Count l Function description The NMS invokes get_alarm_count to get the count of all the current alarms different severities. You can query the count of alarms in different severities before Getting Alarm List.=4.=1. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. 4-19 . ManagedGenericIRPSystem::InvalidParameter).=0. Subrack No. Slot No. out unsigned long minor_count. out unsigned long cleared_count ) raises ( GetAlarmCount. out unsigned long warning_count. l Function format void get_alarm_count ( in ManagedGenericIRPConstDefs::StringTypeOpt filter. out unsigned long major_count. out unsigned long indeterminate_count. out unsigned long critical_count. The alarm count is consistent with the alarm information returned by Getting Alarm List.

3 Description of filter in get_alarm_count. Support (Y/N) Y N N Y Acknowledging Alarms l Function description The NMS invokes acknowledge_alarms to acknowledge one or more alarms. Y Y Y Y Y Y Table 4-20 Values of getting alarm count Returned Value Description Support (Y/N) - Table 4-21 Exceptions of getting alarm count Exception InvalidParameter ParameterNotSupported OperationNotSupported GetAlarmCount Description Indicates that the given parameters are invalid.1. Displays the count of alarms in minor. Indicates that the operation is not supported. Indicates that this parameter is not supported. Displays the count of alarms in cleared. 4-20 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Displays the count of alarms in indeterminate. Support (Y/N) Y critical_count major_count minor_count warning_count indeterminate_cou nt cleared_count out out out out out out Displays the count of alarms in critical.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 4-19 Parameters for getting alarm count Parameter filter In/ Out in Description Indicates the filtering conditions for the alarm count that the NMS wants to get. NOTE For details about the filtering format.. Issue 03 (2010-12-31) . Ltd. Displays the count of alarms in warning. Displays the count of alarms in major. refer to 7. Indicates the exceptions caused by unknown reasons.

NOTE Alarm severity is a parameter that must be entered. The ALARM_ID field in the alarm information indicates the alarm identifier. Table 4-22 Parameters for acknowledging alarms Parameter In/Out Description Supp ort (Y/ N) Y alarm_information_id_and_se v_list in Defines the identifier of alarms to be acknowledged and the set of alarm severities. The parameter is defined by the NMS. however. Ltd. out AlarmIRPConstDefs::BadAcknowledgeAlarmInfoSeq bad_ack_alarm_info_list ) raises ( AcknowledgeAlarms. the M2000 does not handle this parameter. ack_user_id in Defines the identifier of an NMS user who acknowledges alarms. ManagedGenericIRPSystem::ParameterNotSupported. in string ack_user_id. 4-21 . ManagedGenericIRPSystem::InvalidParameter).M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface l Function format ManagedGenericIRPConstDefs::Signal acknowledge_alarms ( in AlarmIRPConstDefs::AlarmInformationIdAndSevSeq alarm_information_id_and_sev_list. Defines the information about the system where the NMS is located.. Y ack_system_id in N Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Currently. in ManagedGenericIRPConstDefs::StringTypeOpt ack_system_id.

The following lists the reasons for errors: l If the alarm ID does not exist. Indicates that all the alarms that require acknowledgements fail in acknowledgement. Ltd. l If the acknowledge information does not display the wanted modification. the reason for the errors can be classified as UNKNOWNALARMID. If all the alarms are acknowledged correctly. although the alarm ID exists. the reason for the errors can be classified as ACKNOWLEDGMENTFAILED. the returned value is OK and this parameter is null. Support (Y/N) Y Y Y 4-22 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l If an alarm is already acknowledged. Issue 03 (2010-12-31) . the reason for the errors can be classified as ACKNOWLEDGMENTFAILED.. although the alarm ID exists.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Parameter In/Out Description Supp ort (Y/ N) Y bad_ack_alarm_info_list out Indicates errors in the alarm acknowledgement. The displayed information contains the alarm identifiers and the reasons for the errors. Table 4-23 Values of acknowledging alarms Returned Value OK PartialFailure Failure Description Indicates that all the alarms that require acknowledgements are acknowledged. Indicates that only some of the alarms that require acknowledgements are acknowledged.

. in ManagedGenericIRPConstDefs::StringTypeOpt ack_system_id. Indicates the exceptions caused by unknown reasons. Y Support (Y/N) Y ack_system_id in N Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Defines the information about the system where the NMS is located. Table 4-25 Parameters for unacknowledging alarms Parameter alarm_information_id_list In/Out in Description Defines the identifier of alarms to be unacknowledged. ManagedGenericIRPSystem::InvalidParameter). out AlarmIRPConstDefs::BadAlarmInformationIdSeq bad_alarm_information_id_list ) raises ( UnacknowledgeAlarms.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Table 4-24 Exceptions of acknowledging alarms Exception InvalidParameter AcknowledgeAlarms ParameterNotSupported Description Indicates that at least one group of parameters is invalid. Indicates the parameter is not supported. ack_user_id in Defines the identifier of an NMS user who unacknowledges alarms. 4-23 . The parameter is defined by the NMS and should be consistent with ack_user_id. Support (Y/N) Y Y Y Unacknowledging Alarms l l Function description The NMS invokes unacknowledge_alarms to unacknowledge one or more alarms. The ALARM_ID field in the alarm information indicates the alarm identifier. ManagedGenericIRPSystem::OperationNotSupported. Function format ManagedGenericIRPConstDefs::Signal unacknowledge_alarms ( in AlarmIRPConstDefs::AlarmInformationIdSeq alarm_information_id_list. in string ack_user_id. Ltd. ManagedGenericIRPSystem::ParameterNotSupported.

The displayed information contains the alarm identifiers and the reasons for the errors. Support (Y/N) Y Y Failure Y 4-24 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Indicates the cancel of the acknowledgements fails. the returned value is OK and this parameter is null. Support (Y/N) Y Table 4-26 Values of unacknowledging alarms Returned Value OK PartialFailure Description Indicates that all the alarms that require unacknowledgement are unacknowledged. The following lists the reasons for the errors: l If the alarm ID specified in the input parameter does not exist. If all the alarms to be unacknowledged are unacknowledged. Issue 03 (2010-12-31) .. Indicates that only some of that alarms that require unacknowledgements are unacknowledged. the error information is the alarm is unacknowledged state. the error information is could not find the alarm.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Parameter bad_alarm_information_id_li st In/Out out Description Indicates errors in the alarm unacknowledgement. Ltd. l If the alarm ID specified in the input parameter exists but the actual alarm status is "unacknowledged".

Defines the information about the system where the NMS is located. Indicates that the given parameters are not supported. ManagedGenericIRPSystem::ParameterNotSupported. Indicates the exceptions caused by unknown reasons. in ManagedGenericIRPConstDefs::StringTypeOpt clear_system_id. Support (Y/ N) Y ParameterNotSupported OperationNotSupported UnacknowledgeAlarms Y N Y Clearing Alarms l l Function description The NMS invokes clear_alarms to clear one or more alarms. ManagedGenericIRPSystem::InvalidParameter). Table 4-28 Parameters for clearing alarms Parameter alarm_information_id_list In/Out in Description Defines the identifier list of the alarms that the NMS would clear. Function format ManagedGenericIRPConstDefs::Signal clear_alarms ( in AlarmIRPConstDefs::AlarmInformationIdSeq alarm_information_id_list.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Table 4-27 Exceptions of unacknowledging alarms Exception InvalidParameter Description Indicates that all the groups of parameters or at least one group of parameters is invalid. in string clear_user_id. Suppor t (Y/N) Y clear_user_id in Y clear_system_id in N Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 4-25 . Ltd. out AlarmIRPConstDefs::BadAlarmInformationIdSeq bad_alarm_information_id_list ) raises ( ClearAlarms. Defines the identifier of an NMS user who clears alarms.. Indicates that the operation is not supported.

the returned value is OK and this parameter is null. The displayed information contains the alarm identifiers and reasons for the errors. Indicates the exceptions caused by unknown reasons. l The NE does not support manual alarm clearance. Support (Y/N) Y Y Y Table 4-30 Exceptions of clearing alarms Exception InvalidParameter ParameterNotSupported ClearAlarms Description Indicates that at least one group of parameters is invalid. Indicates that only some of the alarms that require clearance are cleared. Suppor t (Y/N) Y Table 4-29 Values of clearing alarms Returned Value OK PartialFailure Failure Description Indicates that all the alarms that require clearance are cleared.. Indicates that the given parameters are not supported. Indicates the clearance of alarms fails. If all the alarms to be cleared are cleared. Support (Y/N) Y Y Y 4-26 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Issue 03 (2010-12-31) . The following lists the reasons for the errors: l The alarm ID does not exist. Ltd.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Parameter bad_alarm_information_id _list In/Out out Description Indicates errors in the alarm clearance. l The OMC disconnects with the NE.

ManagedGenericIRPSystem::OperationNotSupported. Table 4-31 Parameters for adding comments to alarms Parameter alarm_information_id_list In/ Out in Description Refers to the list of the identifiers indicating the alarms to which the NMS will add comments. in string comment_text. Support ed (Y/N) Y comment_user_id in Y comment_system_id in N comment_text in Y Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. in ManagedGenericIRPConstDefs::StringTypeOpt comment_system_id. out AlarmIRPConstDefs::BadAlarmInformationIdSeq bad_alarm_information_id_list ) raises ( CommentAlarms. Function format ManagedGenericIRPConstDefs::Signal comment_alarms ( in AlarmIRPConstDefs::AlarmInformationIdSeq alarm_information_id_list.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Adding Comments to Alarms l l Function description The NMS invokes this function to add comments to one or more alarms. ManagedGenericIRPSystem::ParameterNotSupported. 4-27 . ManagedGenericIRPSystem::InvalidParameter). Refers to the identifier of the NMS user who will add comments to alarms. Refers to the information about the NMS system that will add comments to alarms. in string comment_user_id.. Ltd. Refers to the comments to be added to alarms.

. the returned value is OK and this parameter is empty. l If the alarm identifier specified in the typed parameter exists but adding comments to this alarm is not supported. the system displays commenting the alarm is not supported. The error information is as follows: l If the alarm identifier specified in the typed parameter does not exist.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Parameter bad_alarm_information_id_lis t In/ Out out Description Refers to the alarm information indicating the failure to add comments to alarms. Support ed (Y/N) N 4-28 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Issue 03 (2010-12-31) . Support ed (Y/N) Y Table 4-32 Values of adding comments to alarms Returned Value OK PartialFailure Failure Description Indicates that comments are successfully added to all the specified alarms. the system displays could not find the alarm. Indicates that comments are added to some of the specified alarms. Indicates that adding comments to the specified alarms fails. The system output contains alarm identifiers and error causes. Support ed (Y/N) Y Y Y Table 4-33 Exceptions of adding comments to alarms Exception OperationNotSupported Description Indicates that adding comments to a certain alarm is not supported. Ltd. If comments are successfully added to all the specified alarms.

fixed_hea der. Indicates the type of the reported notification. new alarm notification. The value of this parameter is defined by AlarmIRPConstDefs::Notifi cationType::NOTIFY_FM_ POTENTIAL_FAULTY_A LARM_LIST..event_type Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. that is. type_name string header. l l Triggering condition The connection between the NE and the OMC become disconnected. Indicates that at least one group of the typed parameters are invalid.fixed_hea der. This parameter shows the version number of the associated IRP information model.event_type Description Indicates the name of a managed domain.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Exception ParameterNotSupported InvalidParameter Description Indicates that one or more typed parameters are not supported. and alarm change notification. alarm acknowledgement status change notification. 4-29 . alarm comment notification.2 Notification Description of the CORBA Alarm Management The description of the CORBA alarm management notification contains the triggering conditions and formats of the potential faulty alarm list notification. alarm clearance notification.2. or is not sure about the current alarm list. Table 4-34 notifyPotentialFaultyAlarmList Attribute Name domain_name Type string Domain header. the IRPAgent sends the notifyPotentialFaultyAlarmList to inform the NMS that the current alarm list may be inaccurate. Support ed (Y/N) Y Y 4. In such a situation. Notification of Potential Faulty Alarm List The IRPAgent may find that the current alarm list is inconsistent with the actual network resources. notifyPotentialFaultyAlarmList. Notification format Table 4-34 lists the format of the notifyPotentialFaultyAlarmList notification. Ltd.

4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name event_name Type string Domain header.fixed_hea der filterable_data Description Indicates the name of an event. that is. Indicates the time when an event occurs. 4-30 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Notification format Table 4-35 lists the format of the new alarm notification. Indicates the reasons for reconstruction of alarm list. Indicates the notification identifier and is used to exclusively identify a notification. Table 4-35 Notification of new alarms Attribute Name domain_name Type string Domain header. e string a long remainder_of_bo dy b c TimeBase::Utc T string filterable_data filterable_data x string remainder_of_bo dy NOTE AlarmIRPConstDefs::AttributeSetType is the value type of the remainder_of_body. the object instance of AlarmIRP. Notification of New Alarms When new alarms occur on NEs or on the OMC. Ltd..) Indicates the instances of MO that sends the notification. Indicates the identifier of the IRPAgent that generates notifications.fixed_he ader. l l Triggering condition New alarms occur on NEs or on the OMC.event_type Description Indicates the version number of the associated IRP information model. (This parameter is null. Issue 03 (2010-12-31) . the NMS sends the new alarm notification.

The value range and information about this parameter are defined in ProbableCause of the IDL. The value of this parameter is as follows: AlarmIRPConstDefs::NotificationType :: NOTIFY_FM_NEW_ALAR M. internal error-handling alarms. the new alarm. a long remainder_of_b ody b c g TimeBase::Ut cT string short filterable_data filterable_data filterable_data Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The value of this parameter is that of AlarmIRPConstDefs::Alarm Type.fixed_he ader. event_name string header.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name type_name Type string Domain header.. and equipment alarms. the object instance of the alarm. Indicates the identifier of the IRPAgent. Indicates the time when an alarm occurs. Indicates the notification identifier and is used to exclusively identify a notification. 4-31 . e string filterable_data Indicates the instances of MO that sends the notification. Ltd.fixed_he ader Indicates the name of an event and defines communication alarms. that is. that is. Indicates the possible reasons for an alarm and has more detailed categorizations compared with AlarmType. QoS alarms.event_type Description Indicates the type of the reported alarm.

4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name h Type short Domain filterable_data Description Indicates the severity of an alarm. INDETERMINATE is not supported. The filterable_data area in alarm messages contains this attribute only after this attribute is activated. The NMS receives maintenance-mode alarms only after this function is activated. Issue 03 (2010-12-31) . f string remainder_of_b ody Indicates the serial number of alarms and is used to be the only identifier for an alarm.. For details about how to activate the maintenance-mode alarm function and the attribute. Ltd. 4-32 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. By default. see Reporting maintenancemode alarms. jj long filterable_data Vendor-customized alarm type 1: Fault alarm nn long filterable_data The maintenance-mode alarm statuses are as follows: l 0: Normal l 1: Creation l 2: Expansion l 3: Upgrade l 4: Commissioning No default value of this attribute is provided. The following lists severities of alarms: l INDETERMINATE l CRITICAL l MAJOR l MINOR l WARNING l CLEARED NOTE Currently. the maintenancemode alarm function is inactive.

. – The OMC successfully acknowledges or unacknowledges alarms.=1. 4-33 . Subrack No. l Triggering condition – The NMS successfully acknowledges or unacknowledges alarms through Acknowledging Alarms or Unacknowledging Alarms.=4. Board type=WRFU| appendInfo: NOTE AlarmIRPConstDefs::AttributeSetType is the value type of remainder_of_body. j string remainder_of_b ody Indicates the detailed location information about an alarm.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name i Type string Domain remainder_of_b ody Description Indicates the detailed reasons for an alarm. the NMS sends the alarm acknowledgement notification. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Slot No. The information consists of the following items: l NE location l Vendor l NE name l Alarm name l Detailed alarm location information The format of location information is as follows: NeType: NodeB| NeLocation: ShangHai | vendor: Huawei | neName: N91003| alarmName: RF Unit Maintenance Link Failure| alarmLocation: Cabinet No. Ltd. This parameter records the Huawei alarm private information. Notification of the Change of Alarm Acknowledgement Status If the acknowledgement status of an alarm is changed. l Notification format Table 4-36 lists the format of the alarm acknowledgement notification.=0.

.fixed_he ader. event_name string header. Indicates the identifier of the IRPAgent. This parameter shows the version number of the associated IRP information model. this parameter shows the object instances of alarms occurred.event_type a long remainder_of_b ody b c TimeBase: :UtcT string filterable_data filterable_data 4-34 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. internal error-handling alarms. That is.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 4-36 Notification of the change of the alarm acknowledgement status Attribute Name domain_name Type string Domain header.fixed_he ader. Indicates the type of the reported alarm. e string filterable_data Indicates the MO instances in the alarm notification. type_name string header. The value of this parameter is as follows: AlarmIRPConstDefs::NotificationType :: NOTIFY_FM_ACK_STATE _CHANGED. and equipment alarms. that is. Indicates the notification identifier and is used to exclusively identify a notification. Issue 03 (2010-12-31) .event_type Description Indicates the name of a managed domain.fixed_he ader Indicates the name of an event and defines communication alarms. Ltd. QoS alarms. the notification of the change of the alarm acknowledgement status. The value of this parameter is that of AlarmIRPConstDefs::AlarmType. Indicates the time when an alarm occurs.

The following lists the severities of alarms: l INDETERMINATE l CRITICAL l MAJOR l MINOR l WARNING l CLEARED NOTE Currently. k TimeBase: :UtcT long filterable_data Indicates the time when an alarm is acknowledged or unacknowledged.. Vendor-customized alarm type 1: Fault alarm jj filterable_data Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The value range and information about this parameter are defined in ProbableCause in the IDL. 4-35 . h short filterable_data Indicates the severity of an alarm. Ltd. INDETERMINATE is not supported.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name g Type short Domain filterable_data Description Indicates the possible reasons for an alarm and has more detailed categorizations compared with AlarmType.

The NMS receives maintenance-mode alarms only after this function is activated. l The OMC acknowledgement or unacknowledgement alarms should be performed only by OMC authorized users. The filterable_data area in alarm messages contains this attribute only after this attribute is activated.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name nn Type long Domain filterable_data Description The maintenance-mode alarm statuses are as follows: l 0: Normal l 1: Creation l 2: Expansion l 3: Upgrade l 4: Commissioning No default value of this attribute is provided. l In case of automatic acknowledgement. l string 4-36 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. l The NMS acknowledgement alarms should be acknowledged or unacknowledged by users whose ids are in the range of ack_user_id. the authorized user is system. f string remainder_of_b ody remainder_of_b ody Indicates the serial number of alarms and is used to be the only identifier for an alarm. Issue 03 (2010-12-31) . see Reporting maintenancemode alarms. By default. For details about how to activate the maintenance-mode alarm function and the attribute. Ltd. Indicates an identifier for a user that acknowledges or unacknowledges an alarm. the maintenancemode alarm function is inactive.

=1. i string remainder_of_b ody Indicates the detailed reasons for an alarm. Slot No. Board type=WRFU| appendInfo: NOTE AlarmIRPConstDefs::AttributeSetType is the value type of remainder_of_body.=4. For details. 4-37 . The information consists of the following items: l NE location l Vendor l NE name l Alarm name l Detailed alarm location information The format of location information is as follows: NeType: NodeB| NeLocation: ShangHai | vendor: Huawei | neName: N91003| alarmName: RF Unit Maintenance Link Failure| alarmLocation: Cabinet No. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name n Type short Domain remainder_of_b ody Description Indicates the current acknowledgement state of an alarm.. Ltd. This parameter records the private information of Huawei alarms. Subrack No.=0. l The value 1 indicates that the alarm in Acknowledge state. l The value 2 indicates that the alarm in Unacknowledge state. refer to the definition of AlarmIRPConstDefs::AckState. j string remainder_of_b ody Indicates the detailed location information about an alarm.

internal error-handling alarms. and equipment alarms. the NMS sends the alarm clearance notification. l Notification format Table 4-37 lists the format of the alarm clearance notification. event_name string header.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Notification of Alarm Clearance When an alarm is cleared.. Table 4-37 Notification of alarm clearance Attribute Name domain_name Type string Domain header.event_ type Description Indicates the name of a managed domain. l Triggering condition – The notification of alarm clearance shows that the NMS successfully clears alarms through Notification of Alarm Clearance. The value of this parameter is as follows: AlarmIRPConstDefs::NotificationType :: NOTIFY_FM_CLEARED_AL ARM.fixed_ header. The value of this parameter is that of AlarmIRPConstDefs::AlarmType. that is.fixed_ header Indicates the name of an event and defines communication alarms.fixed_ header. QoS alarms. This parameter shows the version number of the associated IRP information model. . Ltd.event_ type b TimeBase:: UtcT filterable_dat a 4-38 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Indicates the type of the reported notification. Issue 03 (2010-12-31) type_name string header. Indicates the time when an alarm is cleared. notification of alarm clearance. – The OMC successfully clears alarms. e a string long filterable_dat a remainder_of _body Indicates the object instances in the alarm notification. Indicates the notification identifier and is used to exclusively identify a notification. – The NEs automatically clear alarms.

M2000 Northbound CORBA Interface Developer Guide

4 Alarm Management Function of the CORBA Interface

Attribute Name c g

Type string short

Domain filterable_dat a filterable_dat a

Description Indicates the identifier of the IRPAgent. Indicates the possible reasons for an alarm and has more detailed categorizations compared with AlarmType. The value range and information about this parameter are defined in ProbableCause.

h

short

filterable_dat a

Indicates the severity of an alarm. The following lists the severities of alarms: l INDETERMINATE l CRITICAL l MAJOR l MINOR l WARNING l CLEARED
NOTE Currently, INDETERMINATE is not supported.

jj

long

filterable_dat a

Vendor-customized alarm type 1: Fault alarm

Issue 03 (2010-12-31)

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

4-39

4 Alarm Management Function of the CORBA Interface

M2000 Northbound CORBA Interface Developer Guide

Attribute Name nn

Type long

Domain filterable_dat a

Description The maintenance-mode alarm statuses are as follows: l 0: Normal l 1: Creation l 2: Expansion l 3: Upgrade l 4: Commissioning No default value of this attribute is provided. The filterable_data area in alarm messages contains this attribute only after this attribute is activated. By default, the maintenancemode alarm function is inactive. The NMS receives maintenancemode alarms only after this function is activated. For details about how to activate the maintenance-mode alarm function and the attribute, see Reporting maintenance-mode alarms.

f

string

remainder_of _body remainder_of _body

Indicates the serial number of alarms and is used to be the only identifier for an alarm. Indicates an identifier for a user that clears an alarm. l For the NMS, alarms can be cleared by users whose IDs are in the range of clear_user_id. l For the OMC, alarms can be cleared only by OMC authorized users. l In case of automatic alarm clearance, the authorized user is NE.

y

string

i

string

remainder_of _body

Indicates the detailed reasons for an alarm. This parameter records the Huawei alarm private information.

4-40

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

Issue 03 (2010-12-31)

M2000 Northbound CORBA Interface Developer Guide

4 Alarm Management Function of the CORBA Interface

Attribute Name j

Type string

Domain remainder_of _body

Description Indicates the detailed location information about an alarm. The information consists of the following items: l NE location l Vendor l NE name l Alarm name l Detailed alarm location information The format of location information is as follows: NeType: NodeB| NeLocation: ShangHai | vendor: Huawei | neName: N91003| alarmName: RF Unit Maintenance Link Failure| alarmLocation: Cabinet No.=1, Subrack No.=4, Slot No.=0, Board type=WRFU| appendInfo:

NOTE

AlarmIRPConstDefs::AttributeSetType is the value type of remainder_of_body.

Notification of Adding Alarm Comment
When the alarm comment is added through the Northbound interface, the notification is sent. l l Trigger condition The NMS successfully adds alarm comment. Notification format Table 4-38 the notification format of adding alarm comment. Table 4-38 Format of adding alarm comment Attribute Name domain_name Type string Domain header.fixed_header. event_type Description Indicates the management domain name. It is the version number of corresponding IRP information model.

Issue 03 (2010-12-31)

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

4-41

NOTIFY_FM_COMME NT_ADDED. that is. Indicates the identifier of the managed system (IRPAgent) that generates the notification. The value range and information about this parameter are defined in ProbableCause of IDL. event_name string header. The value is defined by AlarmIRPConstDefs::Al armType. Its value is alarm type. QoS alarm. Indicates the possible reasons for an alarm and has more detailed categorizations compared with alarmType. The value is AlarmIRPConstDefs::N otificationType ::. Issue 03 (2010-12-31) . notification of adding alarm comment.fixed_header. event_type Description Indicates the type of reported notification.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name type_name Type string Domain header. internal errorhandling alarm. Ltd. It defines notification alarm. Indicates the time when the notification of adding alarm comment occurs. the object instance of alarm. and equipment alarm.. Indicates the instances of MO that sends the notification. that is. Indicates the event name.fixed_header e string filterable_data b TimeBase:: UtcT string filterable_data c filterable_data g short filterable_data 4-42 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. see Reporting maintenance-mode alarms. Ltd. The NMS receives maintenancemode alarms only after this function is activated. By default. jj long filterable_data Vendor-customized alarm type 1: Fault alarm nn long filterable_data The maintenance-mode alarm statuses are as follows: l 0: Normal l 1: Creation l 2: Expansion l 3: Upgrade l 4: Commissioning No default value of this attribute is provided. For details about how to activate the maintenance-mode alarm function and the attribute.. the maintenance-mode alarm function is inactive.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name h Type short Domain filterable_data Description Indicates the following alarm severity: l INDETERMINATE l CRITICAL l MAJOR l MINOR l WARNING l CLEARED NOTE Currently. INDETERMINATE is not supported. The filterable_data area in alarm messages contains this attribute only after this attribute is activated. 4-43 .

The value is AlarmIRPConstDefs::N otificationType ::. Issue 03 (2010-12-31) . Indicates the serial number of alarms and is used to be the only identifier for an alarm. Ltd. NOTIFY_FM_CHANG ED_ALARM. that is. f string remainder_of_body o sequence remainder_of_body NOTE The value type of remainder_of_body domain is AlarmIRPConstDefs::AttributeSetType. It is the version number of corresponding IRP information model.fixed_header..4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name a Type long Domain remainder_of_body Description Indicates the notification identifier and is used to exclusively identify a notification. l l Trigger condition The NE alarm changes. Table 4-39 Notification of alarm changes Attribute Name domain_name Type string Domain header. event_type 4-44 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Indicates the added alarm comment information AlarmIRPConstDefs::C ommentSet. type_name string header. event_type Description Indicates the management domain name. Notification of Alarm Changes The alarm notification is delivered when the NE alarm changes. Indicates the type of the reported notification.fixed_header. the notification of new alarm. Notification format Table 4-39 describes the notification format of alarm changes.

Ltd. 4-45 . It defines notification alarm. e string filterable_data b c TimeBase:: UtcT string filterable_data filterable_data g short filterable_data h short filterable_data Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.fixed_header Description Indicates the event name. Indicates the instances of MO that sends the notification.. Its value is alarm type. The value range and information about this parameter are defined in ProbableCause of IDL. QoS alarm. Indicates the time when alarm changes. The value is defined by AlarmIRPConstDefs::Al armType. INDETERMINATE is not supported. internal errorhandling alarm. Indicates the possible reasons for an alarm and has more detailed categorizations compared with alarmType. that is. Indicates the identifier of the managed system (IRPAgent) that generates the notification.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name event_name Type string Domain header. the object instance of alarm. and equipment alarm. Indicates the following alarm severity: l INDETERMINATE l CRITICAL l MAJOR l MINOR l WARNING l CLEARED NOTE Currently.

the maintenance-mode alarm function is inactive. Indicates the serial number of alarms and is used to be the only identifier for an alarm. Ltd. This field records the Huawei alarm private information. f string remainder_of_body i string remainder_of_body 4-46 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. For details about how to activate the maintenance-mode alarm function and the attribute.4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide Attribute Name jj Type long Domain filterable_data Description Vendor-customized alarm type 1: Fault alarm nn long filterable_data The maintenance-mode alarm statuses are as follows: l 0: Normal l 1: Creation l 2: Expansion l 3: Upgrade l 4: Commissioning No default value of this attribute is provided. a long remainder_of_body Indicates the notification identifier and is used to exclusively identify a notification.. see Reporting maintenance-mode alarms. Indicates the detailed reasons for an alarm. The NMS receives maintenancemode alarms only after this function is activated. Issue 03 (2010-12-31) . By default. The filterable_data area in alarm messages contains this attribute only after this attribute is activated.

Common alarms are generated on some common devices in an MBTS. You can then determine whether the generated alarms are normal mode alarms or common alarms by viewing values in the Common Alarm Identifier column. On the M2000 client. Subrack No. The value of Common Alarm Identifier can be NA. Ltd. NE name. 4-47 . where NA indicates a normal mode alarm. and detailed alarm location information. alarm name. The directory for this configuration item is /imap/ifms/mbtsfilter.=1.=0. To avoid this problem. A common alarm can be reported repeatedly to the NMS through northbound interfaces.2. l Run the following commands to set the configuration item: # .M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Attribute Name j Type string Domain remainder_of_body Description Indicates the detailed location information about an alarm. Board type=WRFU| appendInfo: NOTE The value type of remainder_of_body domain is AlarmIRPConstDefs::AttributeSetType. /opt/OMC/svc_profile.The information consists of NE location. and the value range is 0-7. or LTE are to be reported. see Table 4-40. The default value is 0. GSM..sh Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. vendor. indicating that the common alarms whose Common Alarm Identifier values are GSM. The format is as follows: NeType: NodeB| NeLocation: ShangHai | vendor: Huawei | neName: N91003| alarmName: RF Unit Maintenance Link Failure| alarmLocation: Cabinet No. UMTS. common alarms can be generated on certain common devices. choose Monitor > Browse Alarm List and then choose Advanced > Properties > Common Alarm Indentifier. you can determine the method to be used for reporting common alarms through the northbound interfaces by setting a configuration item. or LTE.=4. UMTS. You can run the SettingTool command to set the configuration item. For details about this configuration item.3 Mechanism for Forwarding Common Alarms In a multi-mode base station (MBTS). Slot No. You can differentiate normal mode alarms from common alarms by viewing alarm information. 4.

only the common alarm whose Common Alarm Identifier value is GSM is to be reported. l In an MBTS UL. that is. l In an MBTS UL or GU. two alarms generated by the MBTS GSM and MBTS UMTS are to be reported. 1 Only the common alarm whose Common Alarm Identifier value is GSM is to be reported through the northbound interfaces. it indicates that FaultService is started: FaultService [running ] Run the SettingTool command to view the value of the configuration item: SettingTool -cmd getparam -path "/imap/ifms/mbtsfilter" Table 4-40 Description of the configuration item Value 0 Meaning The common alarms whose Common Alarm Identifier values are GSM. In an MBTS GU. Ltd. In an MBTS GU. One alarm is generated by the MBTS GSM and the other is generated by the MBTS UMTS. two common alarms with the same information are to be reported. only the common alarm whose Common Alarm Identifier value is GSM is to be reported. /imap/ifms/mbtsfilter. 2 Only the common alarm whose Common Alarm Identifier value is UMTS is to be reported through the northbound interfaces. UMTS. or LTE are to be reported through the northbound interfaces. no common alarm is to be reported. only the common alarm whose Common Alarm Identifier value is GSM is to be reported.. l In an MBTS GL. 3 Only the common alarms whose Common Alarm Identifier values are GSM or UMTS are to be reported through the northbound interfaces. Issue 03 (2010-12-31) .4 Alarm Management Function of the CORBA Interface M2000 Northbound CORBA Interface Developer Guide # SettingTool -cmd setparam -path "/imap/ifms/mbtsfilter" -value 1 If the directory of the configuration item. l l Run the following command to restart FaultService: # svc_adm -cmd restartsvc FaultService Run the following command to check whether FaultService is started: # svc_adm -cmd status | grep FaultService If the system displays the following information. only the common alarm whose Common Alarm Identifier value is UMTS is to be reported. is set to 1. 4-48 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. All the information contained in the alarms is the same except that they have different network serial numbers (SNs). only the common alarm whose Common Alarm Identifier value is UMTS is to be reported. l In an MBTS GU. l In an MBTS GL.

or LTE are not to be reported through the northbound interfaces. l In an MBTS GL.. only the common alarm generated by the MBTS LTE is to be reported. Ltd. l In an MBTS GU. only the common alarm whose Common Alarm Identifier value is GSM is to be reported. 6 Only the common alarms whose Common Alarm Identifier values are UMTS or LTE are to be reported through the northbound interfaces. No common alarm is to be reported. only the common alarm whose Common Alarm Identifier value is LTE is to be reported. UMTS. l In an MBTS GU. l In an MBTS GU. l In an MBTS UL.M2000 Northbound CORBA Interface Developer Guide 4 Alarm Management Function of the CORBA Interface Value 4 Meaning Only the common alarm whose Common Alarm Identifier value is LTE is to be reported through the northbound interfaces. 7 The common alarms whose Common Alarm Identifier values are GSM. two common alarms generated by the MBTS UMTS and MBTS LTE are to be reported. 5 Only the common alarms whose Common Alarm Identifier values are GSM or LTE are to be reported through the northbound interfaces. only the common alarm whose Common Alarm Identifier value is LTE is to be reported. regardless of the type of the MBTS. l In an MBTS UL. 4-49 . only the common alarm whose Common Alarm Identifier value is LTE is to be reported. no common alarm is to be reported. l In an MBTS UL. l In an MBTS GL. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. two common alarms generated by the MBTS GSM and MBTS LTE are to be reported. l In an MBTS GL. only the common alarm whose Common Alarm Identifier value is UMTS is to be reported.

.

The NMS interconnects to the M2000 by invoking the IDL file.M2000 Northbound CORBA Interface Developer Guide 5 Preparations for Interconnection Commissioning of the Northbound CORBA Interface Commissioning of the Northbound CORBA Interface About This Chapter Before interconnecting the NMS to the M2000. and receive notifications by using their host names. 5. subscribe to notifications.3 Checking the CORBA Version Before interconnecting the M2000 to the NMS.5 Modifying the hosts File of the Server This section describes how to enable the NMS host and the M2000 server to communicate with each other through their host names.2 Obtaining the IDL File This describes how to obtain the IDL file.6 Using the CORBA Interface This section describes how to use the northbound CORBA interface when the M2000 system adopts different networking modes. you need to make certain preparations.. 5. the1. 5. that is. 5. 5-1 5 Preparations for Interconnection . 5. 5. you can infer that the northbound CORBA interface meets the conditions for the interconnection. the IDL file of the M2000 needs to be provided to the NMS. make sure that the northbound CORBA version on the M2000 server is valid. Before the interconnection. After you modify the hosts files of the M2000 server and the NMS host. make sure that the NMS is licensed to use the northbound CORBA interface and has the negotiated interconnection parameters.ior file. If you complete the preparations.4 Obtaining the Reference of the Entry Point Object This describes how to obtain the reference of the entry point object. they communicate with each other.1 Negotiating the Interconnection Parameters of the Northbound CORBA Interface Before connecting the M2000 to the NMS. The reference of the entry point object is the prerequisite for the M2000 to invoke the northbound CORBA interface. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd.

ftpuser. If the RNC is used on site. Do as follows to check whether the NMS has the required license. make sure that the NMS has the required license. The M2000 provides the IP address and hostname of the server for the interconnection. The value of this parameter depends on the actual condition. Description For example. make sure that the NMS is licensed to use the northbound CORBA interface and has the negotiated interconnection parameters.. you can infer that the NMS is authorized to use the CORBA interface. ftpuser. Click the Resource Control Item tab. 5-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.1 Negotiating the Interconnection Parameters of the Northbound CORBA Interface Before connecting the M2000 to the NMS. see Table 5-1. Negotiating the Interconnection Parameters The negotiated parameters include the parameters that the M2000 should provide to the NMS and the parameters that the NMS should provide to the M2000. Ltd. Checking License Before the interconnection. 2. Log in to the M2000 client. IP address and hostname of the M2000 server The value of this parameter depends on the actual condition. The License Information window is displayed. the configuration model of this NE needs to be provided for the NMS. Choose License > OMC License Management > License Information. 1. The actual password of the FTP user. Issue 03 (2010-12-31) .ior file. FTP password Configuration model For example.5 Preparations for Interconnection Commissioning of the Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide 5. Table 5-1 Negotiated parameters Parameter Type Parameters provided to the NMS by the M2000 Parameter FTP user name Parameter Value The FTP user can be any user that has the permission to read the 1. 3. If Resource contains Alarm CORBA Interface or Basic Configuration CORBA Interface. For details.

. To use the other IDL files. Description The NMS provides its IP address and hostname for the interconnection. Ltd. change the version to V1. you can infer that this version is valid.2.M2000 Northbound CORBA Interface Developer Guide 5 Preparations for Interconnection Commissioning of the Northbound CORBA Interface Parameter Type Parameters provided to the M2000 by the NMS Parameter IP address and hostname of the NMS Parameter Value The value of this parameter depends on the actual condition.×. the IDL file of the M2000 needs to be provided to the NMS. # cd /opt/OMC # . Procedure Step 1 Run the following commands to check the CORBA version.0 according to the iManagerM2000V200R010C00 Guide to Query and Change Northbound CORBA Interface. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.0.0.sh # displayCorbaNBI The following message is displayed: -------Current Version-------CorbaNBI NBIV×.2.2 Obtaining the IDL File This describes how to obtain the IDL file.. 5./svc_profile.3 Checking the CORBA Version Before interconnecting the M2000 to the NMS. 5. Before the interconnection.Northbound File\Corba interface\<Installed Corba version>\IDL. The NMS interconnects to the M2000 by invoking the IDL file. After the package of release documents is decompressed. you need to consult Huawei R&D engineers. If the version is not V1. 5-3 . the path of the IDL file is as follows ENG\07. Prerequisite Log in to the M2000 server. make sure that the northbound CORBA version on the M2000 server is valid.× If the version is V1.2. CAUTION The northbound CORBA interface of the M2000 supports only the IDL file delivered with the version.

Prerequisite Log in to the M2000 server as user root or omcuser.ior file. you can download the document from the website:http://support. The reference of the entry point object is the prerequisite for the M2000 to invoke the northbound CORBA interface. see 2. If the file does not exist.com. see 6 Troubleshooting the Northbound CORBA Interface.ior file from the /opt/OMC/var/itf_n/EPIRP directory on the M2000 server to the specified local path through the FTP.Northbound File\Corba interface directory. # cd /opt/OMC # . Context For more information about the reference of the entry point object.4 Obtaining the Reference of the Entry Point Object This describes how to obtain the reference of the entry point object. and configuration functions by invoking the 1. In addition. Ltd.ior file exists.sh # cd var/itf_n/EPIRP # ls Check whether the 1. ----End 5-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Procedure Step 1 Run the following commands to view the reference of the entry point object. CAUTION When the FTP mode is used.5 Preparations for Interconnection Commissioning of the Northbound CORBA Interface NOTE M2000 Northbound CORBA Interface Developer Guide The iManagerM2000V200R010C00 Guide to Query and Change Northbound CORBA Interface document is decompressed to the doc\ENG\07. ./svc_profile. Step 2 The NMS obtains the 1. Issue 03 (2010-12-31) .huawei. NOTE The reference of the entry point object is dynamically generated by the northbound interface and is written to the /opt/OMC/var/itf_n/EPIRP/1. the1. The NMS obtains the common functions.ior file of the M2000.. alarm functions.ior file must be transferred in ASCII mode. that is.ior file. the 1. ----End 5.1 Entry Point of the CORBA Interface.

l If the NMS server uses the Microsoft Win32 operating system. Save the file and exit the vi editor. respectively.M2000 Northbound CORBA Interface Developer Guide 5 Preparations for Interconnection Commissioning of the Northbound CORBA Interface 5. Step 2 Run the following command to open the /etc/hosts file on the M2000 server. 10. they communicate with each other.103 and M2000_BAM03. and receive notifications by using their host names. 5-5 . Ltd. Procedure Step 1 Log in to the M2000 server as user root or omcuser. add the following information to the end of the /etc/hosts file. subscribe to notifications. see Table 5-2. add the IP address and hostname of the M2000 server to the hosts file saved in the system32\drivers\etc\hosts directory through the text editor. # vi /etc/hosts For example. Save the file and exit the vi editor. l If the NMS uses the UNIX operating system.. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.224. if the IP address and hostname of the NMS server are 10. add the IP address and hostname of the M2000 server to the /etc/hosts file through the vi editor.71.6 Using the CORBA Interface This section describes how to use the northbound CORBA interface when the M2000 system adopts different networking modes. HA system. For details about how to use the northbound CORBA interface in different networking modes.5 Modifying the hosts File of the Server This section describes how to enable the NMS host and the M2000 server to communicate with each other through their host names. remote HA system. For example.224.100 and nms_01. After you modify the hosts files of the M2000 server and the NMS host. SLS system. # vi /etc/hosts Step 3 Add the IP address and hostname of the interconnected NMS server at the end of the file.100 nms_01 Press Esc and run the :wq! command. and emergency system.71. log in to the system as user root.71.103 M2000_BAM03 Press Esc and run the :wq! command.71. if the IP address and hostname of the M2000 server are 10.224. The M2000 system can adopt the following networking modes: single-server system. respectively. Add the IP address and hostname of the M2000 server in the hosts file of the NMS. Then. ----End 5. the hosts file of the NMS server needs to be modified.224. Step 4 Optional: When the NMS accesses the M2000 through the hostname of the M2000. add the following information to the end of the /etc/hosts file: 10.

. See this document and M2000 Solution Description (Remote HA System) provided in the product documentation.5 Preparations for Interconnection Commissioning of the Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide Table 5-2 Usage of the CORBA interface M2000 System Type Single-server system HA system Remote HA system Usage Reference See this document. See this document. See this document and M2000 Semergency System User Guide provided in the product documentation. Ltd. See this document. SLS system Emergency system 5-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Issue 03 (2010-12-31) .

Free disk space is unavailable on the M2000 server.. 4. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.2 Troubleshooting Failure to Obtain Data This section describes how to troubleshoot the issue when data obtaining fails due to the following causes: 1. NEs are disconnected. 6-1 . 6. Certain key attribute of the MO is null. rectify the fault according to common troubleshooting methods. 2. The service is not started.1 Common Troubleshooting and Information Collection (CORBA Interface) If a fault occurs when the NMS attempts to obtain data through the northbound CORBA interface. The DN is repeated. If a fault occurs when the NMS is obtaining the data. 3. If it is not possible to rectify the fault by using common troubleshooting methods.M2000 Northbound CORBA Interface Developer Guide 6 Troubleshooting the Northbound CORBA Interface 6 Troubleshooting the Northbound CORBA Interface About This Chapter The NMS interconnects with the M2000 through the northbound CORBA interface. refer to relevant troubleshooting methods in this chapter. 6. Ltd. collect the fault information and contact Huawei engineers for assistance.3 Operations Required When the IP Address or Hostname of the M2000 Server Changes This describes the operations that should be performed for the M2000 and the NMS when the IP address or hostname of the M2000 server is changed. 6. 5. The MO data conversion fails. 6.

The MO 6-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Certain key attribute of the MO is null. If it is not possible to rectify the fault by using common troubleshooting methods. Table 6-2 Information to be collected Related Information Operation information Version information IP address information Log information Description Records the operations performed before a fault occurs and the troubleshooting measures taken later. see Table 6-1. Table 6-1 Troubleshooting Common Fault Obtaining data failed. Information Collection If a fault not included in Table 6-1 occurs when the NMS is obtaining the data. Troubleshooting Method See 6. The DN is repeated.2 Troubleshooting Failure to Obtain Data This section describes how to troubleshoot the issue when data obtaining fails due to the following causes: 1. Issue 03 (2010-12-31) . and NE version. You can obtain logs from the /opt/OMC/var/logs directory on the M2000 server. Table 6-2 lists the information that needs to be collected and the collection methods. 3. rectify the fault according to common troubleshooting methods.trace file for IRPService is iMAP..3 Operations Required When the IP Address or Hostname of the M2000 Server Changes. The .1 Common Troubleshooting and Information Collection (CORBA Interface) If a fault occurs when the NMS attempts to obtain data through the northbound CORBA interface. collect the fault information and contact Huawei engineers for assistance. See 6. NE mediation version. Indicates the IP address of the M2000 server.2 Troubleshooting Failure to Obtain Data.6 Troubleshooting the Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide 6. Ltd. 2. Indicates the information about the M2000 version.irp_agent. The IP address of the M2000 server is changed. Troubleshooting For the methods of handling common faults that may occur during the process for obtaining relevant data for the NMS.trace. you need to collect relevant information for fault localization. 6.

Table 6-3 lists the possible causes of the problem and methods for locating the problem. Handling the Fault of obtaining the configuration data failed The NMS invokes the northbound CORBA interface to obtain the configuration data. Table 6-3 Possible Causes and Problem Localization Cause Certain key attribute of the MO is null. Free disk space is unavailable on the M2000 server.. DC=www.M2000 Northbound CORBA Interface Developer Guide 6 Troubleshooting the Northbound CORBA Interface data conversion fails. Conversion of the MO data fails. Check the iMAP. The service is not started. If the value of SignallingPoint is NULL. ManagedElement=37. 5. The northbound CORBA interface fails to obtain the configuration data. Troubleshooting Obtaining data fails possibly due to the following causes: l l l l l l Certain key attribute of the MO is null. As a result. Description In the northbound CORBA interface. NEs are disconnected. Ltd. and SignallingPoint=0. This DN indicates the MO object of a signaling point. For example.irp_agent. 6-3 .com. NEs are disconnected.huawei. a DN is used to uniquely identify an MO. 6. NOTE This is a typical problem of the northbound CORBA interface. If the file includes the following information. IRPService is not started.118: (25382|59) Svr. you can infer that the key attribute signallingPointId is null. T-ER:TagID 0001:08-02 11:20:58. the NMS cannot obtain the required configuration data.GFace: attribute signallingPointId not exist! Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Localization Log in to the M2000 server.trace file under the /opt/OMC/var/ logs directory. SubNetwork=1. Problem Description The NMS cannot obtain relevant data of the NE. The DN is repeated. Free disk space is unavailable on the M2000 server. SignallingPoint is the key attribute of the MO. data of the MO cannot be obtained. 4.

. you can infer that The DN is repeated. you can infer that an exception related to NetIdListType occurs during the conversion of the data type. # cd /opt/OMC # . run the following command: # svc_adm -cmd startsvc IRPService Check whether the 1.irp_agent. If multiple MOs obtained share a DN.irp_agent. Check the status of IRPService. unsigned int. a DN is used to uniquely identify an MO. Conversion of the data type may fail. keyValue[220_0] Conversion of the MO data fails. the DN cannot uniquely identify an MO. run the relevant commands to start it. 1. Log in to the M2000 server. Issue 03 (2010-12-31) . IRPService [running ] 3. and their combinations). 2. while convertor to any where type is NetIdListType. .ior file exists after the service is started. sequence. Ltd. you can infer that the service is started. Description In the northbound CORBA interface.trace file under the /opt/OMC/var/ logs directory. the northbound CORBA interface indicates the exception. Check the iMAP. If the file includes the following information. If the file does not exist. struct. and unsigned long) obtained from the M2000 to the specified type of data (such as enum.trace file under the /opt/OMC/var/ logs directory. Log in to the M2000 server as user root or omcuser. string. If the file exists.gv moi number is more than the metaInfo length! Handling the Fault of Service Unactivation Check whether IRPService is started.sh # svc_adm -cmd status If the following message is displayed. If IRPService is not started. the interface indicates the exception. you can infer that the service process fails to be started. Check the iMAP. DuplicateRdnInfo . In this case. string./svc_profile. 6-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. long.6 Troubleshooting the Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide Cause The DN is repeated. In this case. If the file includes the following information. Localization Log in to the M2000 server. The northbound CORBA interface needs to convert the type of data (such as int. you can infer that the service process is successfully started. If the service is not started. long.

the northbound Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.M2000 Northbound CORBA Interface Developer Guide NOTE 6 Troubleshooting the Northbound CORBA Interface For details on how to check whether the 1. In this case.ior file. if the IP address or hostname of the M2000 server needs to be changed. right-click the disconnected NE and then choose Reconnect NE. On the M2000 client. 2. choose Topology > Main Topology. a new 1. the interface needs to instruct the NMS to obtain the new 1. Solution Contact Huawei technical support. To reinstall the NE mediation. Question The NMS obtains common data. Handling Insufficient Disk Space Faults on the M2000 Server Clear the disk space on the M2000 server. CAUTION Confirm the files can be deleted before clearing the disk space.ior file is generated. In the Main Topology window. Verify the network and rectify the network fault. Ltd. After the IP address of the M2000 server is changed. see the Commissioning Guide of the corresponding M2000 networking mode. 3.3 Operations Required When the IP Address or Hostname of the M2000 Server Changes This describes the operations that should be performed for the M2000 and the NMS when the IP address or hostname of the M2000 server is changed. You are advised to clear the disk space by referring to the Administrator Guide of the corresponding M2000 networking mode. and configuration data through obtaining the 1. settings of the northbound CORBA interface need not be changed.. Handling NE Disconnection Faults 1. The new 1. Rectify the fault on the NE mediation. In this case. see 5. alarm data.4 Obtaining the Reference of the Entry Point Object. what operations should be performed for the M2000 and the NMS? Answer If the IP address or hostname of the M2000 server needs to be changed. 6. Deleting a file by mistake can result in incorrect system operation.ior file and to modify the hosts file.ior file.ior file contains different information from the original 1. After the M2000 is interconnected to the NMS. 6-5 .ior file exists or not. you need to restart the northbound service process. After the northbound service process is restarted.

4 Obtaining the Reference of the Entry Point Object. For details on how to obtain the 1.6 Troubleshooting the Northbound CORBA Interface M2000 Northbound CORBA Interface Developer Guide interface needs to instruct the NMS to obtain the new 1.ior file.5 Modifying the hosts File of the Server. 6-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. see 5. see 5. the NMS cannot invoke the CORBA interface. For details on how to modify the hosts file of the NMS server.ior file. Otherwise. The 1.ior file is saved in the /opt/OMC/var/itf_n/EPIRP/ directory. Issue 03 (2010-12-31) .. Ltd.

syntax description. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. and conventions of the filter.3 Description of Alarm Location Detailed Information Analyze and locate alarms through Alarm Location Detailed Information.2 Description of DN String A DN string is used to represent each object.1 Description of filter This describes the supporting fields. The filters in the get_alarm_list and get_alarm_count are also described. 7.M2000 Northbound CORBA Interface Developer Guide 7 Appendix 7 About This Chapter A collection of supplementary material. 7. 7-1 . Appendix 7.. Ltd.

syntax description. syntax description. 7. 7.7 Appendix M2000 Northbound CORBA Interface Developer Guide 7.1. and conventions of the filter.1 Description of filter This describes the supporting fields. Ltd. 7. Issue 03 (2010-12-31) . Fields Supporting filter l l l type_name event_name e Description of Supported Syntax <ConstraintExpr>:= [ <Expr> ] <Expr> := <Expr> <ExprOp> <Expr> | "(" <Expr> ")" | "not" <Expr> | <SetExpr> <SetOp> <SetExpr> | <StrExpr> <StrOp> <StrExpr> | <NumExpr> <NumOp> <NumExpr> <NumOp> := "==" | "!=" | "<" | "<=" | ">" | ">=" <SetOp> := "==" | "!=" <StrOp> := "==" | "!=" <ExprOp>:="and"|"or" <NumExpr> := <NumTerm> | <NumExpr> "+" <NumTerm> | <NumExpr> "-" <NumTerm> <NumTerm> := <NumFactor> | <NumTerm> "*" <NumFactor> | <NumTerm> "/" <NumFactor> <NumFactor> := <Identifier> | <Number> | "(" <NumExpr> ")" | "-" <NumFactor> <StrExpr> := "$"<Identifier> | <String> | "(" <StrExpr> ")" <SetExpr> := "$"<Identifier> | <Set> 7-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. and conventions of the get_alarm_list. syntax description.2 Description of filter in get_alarm_list This describes the supporting fields..1. 7. and conventions of the filter.1.3 Description of filter in get_alarm_count This describes the supporting field of the get_alarm_count. syntax description. The filters in the get_alarm_list and get_alarm_count are also described.1 Notification filter Description This describes the supporting field.1. and conventions of the filter.1 Notification filter Description This describes the supporting field.

<Sp> := " " Convention l <Identifier> supports the following fields: – type_name – event_name –e NOTE These field names correspond to associated fields in the notification.. | : | " | \ | | | < | . filter can pass the syntax check. | > | / | ? | . 7-3 .| _ | = | + | [ | { | } | ] | . l The symbol $ must be added before <Identifier>." [ <Integer> ] ] <AlphaNum> := <Letter> | <Digit> | "_" <String> := "'" { <Char> }* "'" <Char> := <Letter> | <Digit> | <Other> <Set> := "{" <Elements> "}" <Elements> := [ <Element> { <Sp>+ <Element> }* ] <Element> := <Number> | "$"<Identifier> | <String> <Letter> := | l | m | n | w | x | y | H | I | J | S | T | U a | | | | | o z K V b | | | | | p A L W c | | | | | q B M X d | | | | | r C N Y e | | | | | s D O Z f | | | | t E P g | | | | u F Q h | | | | i | j | k v G R 7 Appendix <Digit> := 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 <Other> := <Sp> | ~ | ! | @ | # | $ | % | ^ | & | * | ( | ) | . If $ is not added. Instance $type_name == 'x1' Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.M2000 Northbound CORBA Interface Developer Guide <Identifier> := <Letter> { <AlphaNum> }* <Number> := <Integer> | <Float> | "-" <Number> <Integer> := { <Digit> }+ <Float> := <Integer> [ ". The notification. cannot be received. Ltd. however.

<Integer> is data of a decimal integer. The field name type_name supports the following values: – x1 – x3 – x5 l 7-4 The field name event_name supports the following values: Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. syntax description.7 Appendix M2000 Northbound CORBA Interface Developer Guide 7.1. Fields Supporting filter The following fields in get_alarm_list support filter: l l l l type_name event_name b h Syntax Description l l l l l l l l l <SingleExpr> := "$"<Identifier><separator><ExprOp> <separator><Expr> <OrExpr> ::= <SingleExpr><separator>"or"<separator><SingleExpr> <AndExpr> : "("<OrExpr>")"<separator>"and"<separator>"("<OrExpr>")" <separator>::= " " <ExprOp>::= "==" | "<=" | ">=" <Expr>:= <StrExpr> | <NumExpr> <StrExpr> := "'" { <Char> }* "'" <NumExpr>:= <Integer> <Identifier>::= "type_name" | "event_name" | "b" | "h" Convention The conventions are as follows: l <Identifier> supports the following fields: – type_name – event_name –b –h l l l l l l In <SingleExpr> preceding and following the keyword "or". Issue 03 (2010-12-31) . The operators that the field name b supports are only ">=" and "<=". In <SingleExpr> preceding and following the keyword "and".2 Description of filter in get_alarm_list This describes the supporting fields. <Identifier> must be the same. event_name. <Identifier> must be different except that for the field name b.. The field names type_name. and conventions of the get_alarm_list. Ltd. and h support only the operator "==".

Figure 7-1 shows the expression of a DN string.2 Description of DN String A DN string is used to represent each object. ManagementNode=1' 7.huawei. Supporting Field and Format l l The supporting field is e.1. SubNetwork=1 . Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. Instance l l l l $type_name == 'x1' $type_name == 'x1' or $type_name == 'x2' ($type_name == 'x1' or $type_name == 'x2') and ($event_name == 'x1') and ($b == 133459954540000000) ($b >= 133459954540000000) and ($b <= 133459955540000000) 7. 7-5 .com. Instance $e == 'DC=www. The supporting format is $e == 'DN'. The time format for alarms is the one defined in time of TimeBase::UtcT. Ltd. DN refers to the alarm to be filtered.M2000 Northbound CORBA Interface Developer Guide 7 Appendix – x1 – x2 – x3 – x4 – x5 l The field name h supports the following values: –2 –3 –4 –5 l The field name b is used to filter alarm time.3 Description of filter in get_alarm_count This describes the supporting field of the get_alarm_count.

managedElement=ME_1. The DN of a specific object is follows: l l l l DN for Object 5: subnetwork=subnetwork_A. Each object shown Figure 7-1 is numbered and the DN of each object can be obtained. signallingLinkSetTP=SLSTP_1. utranCell=UCL_1 DN for Object 11: subnetwork=subnetwork_A. managedElement=ME_2. managedElement= ME_1.. signallingPoint=SP_1. managedElement= ME_1. Issue 03 (2010-12-31) . Ltd.7 Appendix M2000 Northbound CORBA Interface Developer Guide Figure 7-1 DN string Figure 7-1 shows the RDN of each object. 7-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. mscFunction=MSCF_1. signallingLinkSetTP=SLSTP_2 DN for Object 12: subnetwork=subnetwork_A.3 Description of Alarm Location Detailed Information Analyze and locate alarms through Alarm Location Detailed Information. rncFunction=RNCF_1. signallingPoint=SP_1. mscFunction=MSCF_1 DN for Object 9: subnetwork= subnetwork_A. mscFunction=MSCF_1. signallingLinkTP=SLTP_1 7.

NeLocation: indicates the location of the NE in which the alarm occurs. Slot No. and neName give the information about the NE where the alarm occurs.=4. neName: indicates the name of the NE where the alarm occurs. alarmName: indicates the name of an alarm. the NMS can analyze and locate alarms through Alarm Location Detailed Information. Issue 03 (2010-12-31) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. Thus. vendor: indicates the manufacture of alarm devices.=0.M2000 Northbound CORBA Interface Developer Guide 7 Appendix The Alarm Location Detailed Information is shown in the field j in the notification. NOTE l l l The fields NeType give the information about the type of the NE that has alarms. The information can be also traced on the OMC. 7-7 . l l l l l l NeType: indicates the type of the NE that has alarms. Board type=WRFU| appendInfo: where. The Alarm Location Detailed Information contains the following items: l l l l l l NeType NeLocation Vendor neName Alarm name Alarm location The format for the Alarm Location Detailed Information is as follows: NeType: NodeB| NeLocation: ShangHai | vendor: Huawei | neName: N91003| alarmName: RF Unit Maintenance Link Failure| alarmLocation: Cabinet No. The fields NeLocation. Subrack No. alarmLocation: indicates the location information about an alarm. The fields alarmName and alarmLocation are used to locate alarms. Vendor. Ltd.=1.

Sign up to vote on this title
UsefulNot useful