NSN Administering Alarms in McRNC and Flexi Direct RNC

Multicontroller RNC, Rel. 3.0, Operating Documentation, Prerelease, Issue 01 Administering Alarms in mcRNC and Flexi Direct RNC DN09123463 Issue 02 DRAFT Approval Date 2013-05-14 Confidential Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information. Administering Alarms in mcRNC and Flexi Direct RNC The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Siemens Networks 2013. All rights reserved f Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set. The same text in German: f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes. 2 Id:0900d805809a71a5 Confidential DN09123463 Administering Alarms in mcRNC and Flexi Direct RNC Table of contents This document has 60 pages. Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 DN09123463 1 1.1 1.2 1.3 1.4 1.4.1 1.4.2 1.5 1.6 1.7 1.8 1.9 1.9.1 Overview of alarm administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Alarm system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Alarm repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Severity levels of the alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Alarm data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Type-specific alarm data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Instance-specific alarm data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Alarm flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Alarm blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Alarm filtering with identifying fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Radio network alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Alarm correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Alarm correlation for 70168 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 2 2.1 2.1.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 Alarm monitoring with SCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Permissions for SCLI commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledging and unacknowledging alarms . . . . . . . . . . . . . . . . . . . . Adding alarm types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the alarm type definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clearing automatic alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clearing manual alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring number of alarms processed per second . . . . . . . . . . . . . . Configuring the alarm blocking rules . . . . . . . . . . . . . . . . . . . . . . . . . . . Raising a test alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing active alarm data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarm history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarm manual and test instructions. . . . . . . . . . . . . . . . . . . . . . Viewing alarm recovery history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing notification ID of an alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing probable causes and specific problems . . . . . . . . . . . . . . . . . . Viewing the alarm type definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Alarm handling in OMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Id:0900d805809a71a5 Confidential 28 28 28 29 30 31 33 35 37 39 41 43 48 51 52 55 56 57 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Id:0900d805809a71a5 Confidential DN09123463 . . . . . . . . . . . . . . . . . . . . 20 User clears the alarm . . . . . .Administering Alarms in mcRNC and Flexi Direct RNC List of figures Figure 1 Figure 2 Figure 3 4 A fault is detected and an alarm raised. . . . . . 21 mcRNC fault management functional environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Optional parameters for raising a test alarm . . . . . . . 35 Parameters for configuring number of alarm events . . .Administering Alarms in mcRNC and Flexi Direct RNC List of tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 DN09123463 Type-specific alarm parameters . . . . . . . . . . . . . . . . . . . . . 56 Parameters for viewing all alarm type definitions used in the alarm system 57 Id:0900d805809a71a5 Confidential 5 . . . . . . . . 45 Numeric value for the Alarm severity . . . . . . . . . . . 45 Alarm parameters . . . . . . . 55 Parameters for viewing probable causes used in the alarm system . . . . . . . . . . . . . . . . 53 Parameters for viewing notification IDs of an alarm . . . . . . . . . . 48 Alarm filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Alarm type parameters . . . . . . . . . . . . . . . . . 45 Alarm filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Alarm filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Parameters for viewing active alarm data . . . . . 33 Alarm filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Alarm additional information for RNW alarms . . . . . . . . . . . . 46 Parameters for viewing alarm history . . . . . . . . . . . . . . . . . . . . . . . . 37 Mandatory parameters for raising test alarm . . . . . . . . . . . . . . . . . . . . . . . . 31 Forced values . . . . . . . . . . . . . . . . . . . . 56 Parameters for viewing specific problems used in the alarm system . . . . . . . . 13 Instance-specific alarm parameters . . . . . . . 34 Alarm filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Permissions to execute the SCLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering Alarms in mcRNC and Flexi Direct RNC 6 Id:0900d805809a71a5 Confidential DN09123463 . RU30) and 01 (2012-10-15. RU30) • • • DN09123463 Document title has been modified from Alarm Administration in mcRNC and I-HSPA Adapter to Administering Alarms in mcRNC and I-HSPA Adapter.Administering Alarms in mcRNC and Flexi Direct RNC Summary of changes Summary of changes Changes between document issues are cumulative. Therefore. Changes between issues 01 DRAFT (2012-07-03. Section Overview of alarm administration has been re-structured.10 Viewing active alarm data has been updated. Step 2 in section 2. Changes between issues 01 (2012-10-15. Term I-HSPA Adapter has been replaced with Flexi Direct RNC throughout the document. Id:0900d805809a70ec Confidential 7 . Parameters have been added to Table 13. the latest document issue contains all changes made to previous issues. RU30) and 02 DRAFT (2013-05-14. RU40) • • • • • • • Document title has been modified from Administering Alarms in mcRNC and I-HSPA Adapter to Administering Alarms in mcRNC and Flexi Direct RNC. The following sections have been modified: – Alarm system – Alarm blocking – Changing the alarm type definition – Viewing alarm history – Viewing the alarm type definition The following sections have been added: – Alarm correlation – Permissions for SCLI commands The following tables have been modified: – Alarm filters – Alarm parameters Section Adding alarm types has been removed. Table 15. and Table 20. The alarm system consists of an alarm processor. which is maintained by the alarm system. Alarm processor The alarm processor reads alarm notifications from syslog. Alarm management interfaces Alarm management interfaces provide access to the alarm data in the alarm system. the fault causing the alarm must be solved. The components share data with each other using the alarm repository. The processing of alarms is done according to various processing rules such as filtering rules. Each syslog record contains alarm notification information encoded in a predefined format. and an alarm repository. As a result. Convenience libraries perform initial validation for the syntax of the alarm records. alarm management interfaces. processes them and decides whether they will be turned into alarm events. After an alarm is raised. one should use the alarm system's management interface. convenience libraries. You cannot clear these alarms manually. The syslog parser validates and extracts this information and further processes it. correlation rules and suppression rules. Alarms are typically used in situations where it is possible to give instructions for corrective actions in the alarm description. 8 Id:0900d805809a717b Confidential DN09123463 . for example. Such alarms are cleared automatically when the system returns to its normal state. Syslog file The alarm processor reads log records from a dedicated syslog file and parses them. the alarm system can create new active alarms. Convenience libraries Convenience libraries provide an interface for applications to send requests for raising and clearing alarms. the libraries write the alarm records to the syslog file. Using the Alarmlightlib. when the hard disk is full and the system cannot write to it. The alarm applications write their alarm records to a syslog file through a convenience library. The alarms can also be raised through the alarm system to indicate that the system is not working normally. Alarm events are further processed by the alarm processor and are stored in alarm history. g Syslog is only used as an internal communication channel between the convenience library and alarm processor. such as replacing a hardware unit.1 Alarm system The alarm system indicates potential faults in the system as well as faults that require corrective actions. It must not be used for checking the state of alarms because it only contains incomplete information about the state of the alarms in the system. interested applications can poll the list of active alarms and the alarm history. To get full information. After successful validation. The solution can be an automatic recovery or a manual corrective action. modify the state or remove some of the existing active alarms.Overview of alarm administration Administering Alarms in mcRNC and Flexi Direct RNC 1 Overview of alarm administration 1. The following data is stored in the alarm repository: • • • Active alarms list Alarm history Alarm type parameters. After the alarm processor has read the alarm records from the syslog file. Maximum number of Alarm history events is 25000. This means that it will take around 10 seconds to process all notifications if the burst has suddenly generated 1000 notifications. Alarm system capacity or performance requirements The capacity or performance requirements of the alarm system are: • • • • g Maximum number of active alarms is configurable by NSN personel and is limited only by the size of internal memory.Administering Alarms in mcRNC and Flexi Direct RNC Overview of alarm administration Alarm repository The repository is the file-system based central storage for the alarm management system. 50 alarm notifications per second during alarm bursts (30 seconds burst once a day). the alarm repository is the only link between the alarm system components. One alarm event occupies around 2KB of disk space. Around 100 alarm notifications per second with low CPU utilization for the steady alarm flow. DN09123463 Id:0900d805809a717b Confidential 9 . Maximum number of Alarm history events is configurable by NSN personel and can be as big as the available disk space. depending on the capacity of syslog files used as communication channels. 8-10 alarm notifications per second for the steady alarm flow. Unlimited amount of alarm notifications per second during alarm bursts. All alarm data is stored in the alarm repository. Alarm system capacity or performance requirements The capacity or performance requirements of the alarm system are: • • • • Maximum number of active alarms is 10000. as every active alarm takes about 2KB. and the components use it to share data. Even with a huge number of notifications written to syslog. Managing alarms Alarms can be monitored and managed using SCLI and through some other management applications running on NetAct or OMS. the alarm system is processing them at a normal rate (around 100 per second). In addition to this.Administering Alarms in mcRNC and Flexi Direct RNC 1. a snapshot of Active Alarms is backed up in what are referred as snapshot files to aid recovery of active alarm list in case of Alarm System restart. All these files are stored in a dedicated partition and available across nodes. while the Alarm History is stored in binary files. The Active Alarms are stored in structured lists.2 Alarm repository The Alarm Repository is partly based on memory lists and partly based on binary files. 10 Id:0900d805809a70ee Confidential DN09123463 . Minor The Minor severity level indicates that there is a condition that does not affect services. a fault that affects a service. Major The Major severity level indicates that a service-affecting condition has developed and an urgent corrective action is required. that is. Cleared The Cleared severity level indicates that one or more previously reported alarms have been cleared. when the detected alarm condition is not currently degrading the capacity of the managed object. The following severity levels apply only to the perceived severity of the alarms: • • DN09123463 Indeterminate The Indeterminate severity level indicates that the severity level of the alarm cannot be determined.3 Severity levels of the alarms The severity levels of the alarms indicate the default and perceived severity of the alarms. It is not recommended to use this value. if necessary.Administering Alarms in mcRNC and Flexi Direct RNC 1. correct the problem to prevent it from becoming a more serious service affecting fault. for example. Such a severity can be reported. Action should be taken to further diagnose and. for example. This severity level can be reported. when a managed object becomes totally out of service and its capability must be restored. the application is not able to set the concrete level of severity for the detected fault. when there is a severe degradation in the capability of the managed object and its full capability must be restored. before any significant effects have been detected. for example. Corrective action should be taken to prevent a more serious fault. Warning The Warning severity level indicates the detection of a potential or impending service-affecting fault. for example. Id:0900d805809a70ef Confidential 11 . The following severity levels are used in the system: • • • • Critical The Critical severity level indicates that a service-affecting condition has occurred and an immediate corrective action is required. This severity level can be reported. Most of the 3GPP requirements are based on ITU-T recommendation X.4.NODE NOT RESPONDING 315 .SERVICE LEVEL DEGRADED BELOW THRESHOLD : 315 .Equipment malfunction : 4 (minor) : automatic : yes : no : x5 (equipment) : 0 : 30000 : 0 : Not defined Probable cause Default severity Clearing Auto acknowledged Switch over update Event type Clearing delay Informing delay Time to live Operation instructions 70011 . or attributes.4 1.111 series Release 4 specifications. You can only modify the dynamic parameters that are: • • • • • • Default severity Autoacknowledged Clearing delay Informing delay Time to live Switchover update.Administering Alarms in mcRNC and Flexi Direct RNC 1. specific to an alarm type. are defined in the following table.1 Alarm data Type-specific alarm data The alarms occurring in the system are based on 3GPP 32.Equipment malfunction 3 (major) automatic yes no x5 (equipment) 0 0 0 Not defined The type-specific parameters and their values are listed in Table 1 Type-specific alarm parameters. The parameters. The alarm type defines a class of alarms. 12 Id:0900d805809a70f0 Confidential DN09123463 .733. The following are examples of an alarm output including type-specific data: Specific problem Probable cause Default severity Clearing Auto acknowledged Switch over update Event type Clearing delay Informing delay Time to live Operation instructions : : : : : : : : : : : Specific problem : 70012 . Type-specific alarm parameters are either dynamic or static. Yes No Switchover update Defines whether the active alarm is to be updated into the new active unit by the alarm system. alarms with No as Switchover update value are cleared. Static field that cannot be modified. Integer If Clearing delay is not used. an alarm number.Administering Alarms in mcRNC and Flexi Direct RNC Alarm parameter Description Value range Specific problem Identifies the specific problem causing the alarm. For example. Critical Major Minor Warning Indicates whether the alarm is cleared automatically by the system or manually by the user. Each Default event type is mapped to a set of probable causes. Yes No Categorizes the alarm based on the nature of the failure. The specific problems selected in the Alarm Parameter List dialog. Integer Probable cause Categorizes the alarm into probable causes listed in 3GPP TS 32. For example. If a unit switchover takes place. Protection path failure.733. String Default severity Indicates the default severity of the alarm. X733. Type-specific alarm parameters Id:0900d805809a70f0 Confidential 13 . Manual Auto acknowledged Defines whether the alarm is acknowledged automatically when cleared. 70006. Each Probable cause is mapped to a Specific problem. Probable causes. X. Clearing delay is the period of time that the clearing of the alarm is delayed to filter the unnecessary cancellation if the alarm is raised again during the clearing delay. Static field that cannot be modified. based on ITU-T rec. in milliseconds. as listed in ITU-T rec. Communications Clearing (Changeover update) Event type Automatic Processing error Quality of Service Equipment Environmental Clearing delay Table 1 DN09123463 Defines the clearing delay period. the value is zero (0).111-2 annex B. String Operation instructions Table 1 1. both raising and clearing of the alarm is filtered as a false alarm.) Instance-specific alarm data Each alarm contains instance-specific data that is visible in the Alarm management application. Alarm ID Specific problem Managed object Severity Cleared Clearing Acknowledged Ack. Time to live Defines the live time. info Appl. time Alarm time Event type Application IAppl Addl.UNSAVED CONFIGURATION IN USE fsClusterId=ClusterRoot 5 (warning) yes automatic no N/A N/A 2011-08-10 18:00:02:143 EEST x2 (processing error) fsClusterId=ClusterRoot 362 x1 (raise) 7 (full visible) Id:0900d805809a70f0 Confidential DN09123463 . If the alarm is cleared during the informing delay. Type-specific alarm parameters (Cont.Integer seconds. Informing delay is the If Informing delay is not used. the waiting period before the informavalue is zero (0). then it must be greater than the Informing delay value. Integer Possible instructions for handling the alarm. the value is zero (0). in milliseconds. Addl. Maximum length is 254 characters.Administering Alarms in mcRNC and Flexi Direct RNC Alarm parameter Description Informing delay Defines the informing delay. tion concerning the raising of a new alarm in forwarded. If the value is positive. The following are examples of an alarm output including instance-specific data.4. Informing delay should be set to an alarm that has a tendency to be cleared almost immediately after it has been raised. The instance-specific alarm data refers to a specific alarm raised by an application.2 Value range If Time to live is not used.Time to live is defined only if the alarm is to be cleared by the alarm system after the given time has passed. in milli. user ID Ack. info Notification ID Extended event type Control indicator 14 : : : : : : : : : : : : : : : : : 114 70360 . fsLogicalNetworkElemId=NERNC89. Addl.fsLog icalNetworkElemId=NE-RNC156.fsFragmentId=external.fsClusterId=C lusterRoot : 6 (cleared) : yes : automatic : yes : Alarm Light : 2012-06-28 02:42:20:810 EEST : 2012-06-28 02:42:20:810 EEST : x2 (processing error) : appid=fshaProcessInstanceName$E$QNOBHER O$C$fshaRecoveryUnitName$E$QNOMUServer0$C$fsipHostName$E$CFPU0$C$fsFragmentId$E$Nodes$C$fsFragmentId $E$HA$C$fsClusterId$E$ClusterRoot.fsClusterId=Cl usterRoot : 4 (minor) : no : automatic : no : N/A : N/A : 2012-06-29 10:32:56:002 EEST : x5 (equipment) : appid=fshaProcessInstanceName$E$QNOBHER O$C$fshaRecoveryUnitName$E$QNOMUServer0$C$fsipHostName$E$CFPU- Id:0900d805809a70f0 Confidential 15 .BASE STATION LICENCE NOTIFICATION : moid=WBTS-19. time Alarm time Event type Application DN09123463 : 214452 : 7740 .fsFragmentId=external.Administering Alarms in mcRNC and Flexi Direct RNC Alarm ID Specific problem Managed object Severity Cleared Clearing Acknowledged Ack.BEATING WCDMA BTS ALARM : moid=WBTS325. info Appl.fsClusterId=C lusterRoot : si=7750 : afamily=rnw ai=1$S$0$S$0$S$0$S$0$S$0$S$0$S$0$S$0$S$ 0$S$0$S$0$S$0$S$0 atime=1340840538000 et=x2 modesc=WBTS-325 rawinfo=5077010000000000000000000000000 000000000000000000000000000000000 utc=180 : 693 : 7661 . info Alarm ID Specific problem Managed object Severity Cleared Clearing Acknowledged Ack. time Alarm time Event type Application IAppl Addl. user ID Ack.fsFragmentId=external. user ID Ack.fsLogicalNetworkElemId=NE-RNC156. based on ITU-T recommendation X733. info Appl.fsLog icalNetworkElemId=NE-RNC89. Static field that cannot be modified.Administering Alarms in mcRNC and Flexi Direct RNC IAppl Addl. Parameter Description Value range Alarm ID Unique alarm identifier. For example.fsFragmentId=external. Addl.fsClusterId=Cl usterRoot : si=64$S$1$S$64$S$4056FSMD$S$1$S$10 : afamily=rnw atime=1340955163960 et=x5 rawinfo=6401643430353646534D44202020011 000000000000000000000000000000000 st=Verification$S$of$S$target$S$ID$S$fa iled$S$3$S$times. Integer Managed object Identifier of the managed object that is the target of the alarm. user ID Table 2 16 Yes No Yes No ID of the user who has acknowl. Ack. Acknowledged The acknowledgement status of the alarm. 1007. utc=180 The instance-specific alarm parameters and their values are listed in Table 2 Instancespecific alarm parameters. Clearing Indicates whether the alarm is Manual cleared automatically by the Automatic system or manually by the user.String edged/unacknowledged the alarm. By default not applicable if the alarm has not been acknowledged/unacknowledged. String Severity Indicates the perceived severity of the alarm. Critical Major Minor Warning Indeterminate Cleared Cleared Shows whether the alarm has been cleared or not. Instance-specific alarm parameters Id:0900d805809a70f0 Confidential DN09123463 . info 0$C$fsFragmentId$E$Nodes$C$fsFragmentId $E$HA$C$fsClusterId$E$ClusterRoot. Administering Alarms in mcRNC and Flexi Direct RNC Parameter Description Value range Ack. time Date and time when the alarm was acknowledged/unacknowledged. The default value is null. Alarm time Date and time when the alarm was raised, cleared, or its severity was changed. For example, Fri Jan 09 18:47:34 EET 2005. Event type Categorizes the alarm based on the nature of the failure, as listed in ITU-T rec. X.733. Each Event type is mapped to a set of probable causes. Communications Processing error Quality of Service Equipment Environmental Application Identifier for the instance of the application that has raised the alarm. String IAppl Addl. info Identifying additional information on the alarm. String Appl. Addl Info Non-identifying additional information on the alarm. String Notification ID Unique identifier created to every alarm event (raise/cancel/change/acknowledgement) assigned by the alarm system. Alarm ID identifies every active alarm instance (set+cancel pairs), whereas Notification ID identifies every single alarm notification that the system can generate. Integer Extended event type Type of the alarm event itself. x1 = alarm raise x2 = alarm data change (for an active alarm) x3 = alarm acknowledgement x4 = alarm canceling Table 2 DN09123463 Instance-specific alarm parameters (Cont.) Id:0900d805809a70f0 Confidential 17 Administering Alarms in mcRNC and Flexi Direct RNC Parameter Description Value range Control indicator Bitmask value that indicates vis- 0 = full invisible ibility of the alarm. 1 = alarm is reported to NetAct 2 = alarm is visible in local UI (for example, OMS FM GUI) 4 = alarm is sent to OMS 7 = full visible Table 2 Instance-specific alarm parameters (Cont.) Details on additional information for RNW alarms are described in Table 3 Alarm additional information for RNW alarms Additional information parameter si Identifying supplementary information fields of the alarm. There can be more than one si fields, in which situation $S$ fillers are used to separate individual fields. Compare: alarms 7740 and 7661 in 1.4.2 Instance-specific alarm data. A missing si tag means that there are no identifying information fields for the given RNW alarm. afamily Internal value for the alarm system. It indicates that a given alarm is an RNW alarm. ai Rest of the supplementary information fields (non-identifying ones). atime Actual time of the alarm event. In case of BTS-originated alarm, it means the timestamp sent by the BTS in alarms. et Event type that originates from application SW or BTS. It might or might not be the same as Event type. modesc Managed object description. It is the name of the WBTS object that the user has defined in RNW DB. rawinfo Information specific to alarm system only. It contains the original supplementary byte buffer that the RNW alarm system needs if it has to read alarms from FlexiPlatform alarm system. Table 3 18 Description Alarm additional information for RNW alarms Id:0900d805809a70f0 Confidential DN09123463 Administering Alarms in mcRNC and Flexi Direct RNC Additional information parameter st Supplementary text for the alarm. A missing st tag means that the alarm does not have any supplementary text included. utc Alarm timestamp difference from the UTC time. Table 3 DN09123463 Description Alarm additional information for RNW alarms (Cont.) Id:0900d805809a70f0 Confidential 19 The alarm management application. Application SW is also involved. 1. The solution to a fault can be an automatic recovery administered by the system or a manual corrective action by the operator. the system can raise informative alarms about events that do not necessarily require any corrective actions. The system detects a fault. The alarm processor reads the request in the alarm repository. The information of an alarm event that requires corrective actions by the operator proceeds from the detection of a fault in a system to the clearing of the alarm as described below. Furthermore. 2. The Alarmlightlib reads the list of active alarms and sends it to the alarm management application for displaying it to the user. 3. If the alarm processor accepts the request. 9. The alarm processor reads the notification and processes it.Administering Alarms in mcRNC and Flexi Direct RNC 1. Once the problem is solved. Id:0900d805809a70f1 Confidential DN09123463 . 4. The Alarmlightlib writes the request to clear the alarm to the alarm system database. The alarm application sends an alarm notification to the alarm processor through the convenience libraries. 7. 5. 8. it sends the alarm cancel request to the RNW alarm system to check if it has to cancel the alarm. 6. Figure 1 g 20 A fault is detected and an alarm raised Step 7 is needed only if the alarm requires manual canceling. a request to clear the alarm comes from the OMS.5 Alarm flow Alarms inform users about the faults in the system. it removes the cleared alarm from the list of active alarms. polls the alarm system for the list of active alarms using the Alarmlightlib. The alarm processor updates the list of active alarms with the processed data. Administering Alarms in mcRNC and Flexi Direct RNC 8 7 9 Figure 2 DN09123463 User clears the alarm Id:0900d805809a70f1 Confidential 21 . The blocking rule can be applied for the internal alarms and does not work for the external alarms.6 Alarm blocking The alarm blocking filters incoming alarm notifications. The old record's status is changed to active. The activating. Blocking rule can be in the active (blocking is enabled) and non-active (blocking is disabled) state. deactivating. The alarm processor filters the corresponding alarm notifications based on the list of active blocking rules. The MOID provided must be a full managed object name or part of the managed object ID (MOID) flanked by the wildcard %--%MOID%. required for further operations like activating or deactivating the rules. The alarm processor logs the filtered alarm notifications into the syslog. The blocked alarms with auto acknowledgement are acknowledged by the alarm system.Administering Alarms in mcRNC and Flexi Direct RNC 1. the blocking rule gets a rule-id. Notification ID is used to differentiate between the alarms. the moment they are cleared. The blocked alarms without auto acknowledgement are manually acknowledged. If the blocking rule is activated. The API has a set of blocking rules defined and enables the following operations: • • • • • Adding the blocking rule to the list Removing the blocking rule from the list Activating or deactivating the blocking rule Searching for an available blocking rule in the list Providing a list of available blocking rules The blocking rule includes alarm number as a mandatory parameter and managed object as an optional one. The permissions applicable for the fsalarmagent must be provided to the users linked with the applications using the alarm agent library. If the added record is enabled. for which the blocking rule is applied. The alarm agent provides Java and the C++ application programming interface (API) to manage the alarm blocking. for example %NE3sAgent%. g 22 It is not necessary to restart the alarm processor to enable the existing active or nonactive blocking rules. deleting and querying operations can be performed to change the state of the blocking rule. Id:0900d805809a7179 Confidential DN09123463 . which is an unique-id. After adding into the system. A new record is added to the alarm system database that contains a list of blocking rules. The alarm blocking manages the alarm numbers and optionally. matching the blocking rule are automatically cleared by the alarm system. as it is always defined. then a new record is not added. the next raise / clear alarm notifications are blocked and the existing alarms in the list. and it does not allow incoming alarm notifications to be processed further. the managed objects linked with the alarm. The blocking rule can be added into the system either as active or non-active. The alarm system offers filtering properties to reduce the number of published alarm reports and to give the user only a useful amount of fault indication information. Repeated alarms that have the same information content are filtered out. if an alarm is repeated with the same identifying fields but with a different perceived severity. the alarm is considered changed and is updated in the alarm repository. the new alarm is filtered out. g DN09123463 If an alarm with non-zero Time to Live is repeated with the same identifying fields and same or different severity.7 Alarm filtering with identifying fields A single alarm can be identified by the identifying fields. the alarm instances are interpreted to be the same alarm. and a new alarm is raised only when the value in one or more of the identifying fields has changed in comparison to the currently active alarms. Id:0900d805809a717a Confidential 23 .Administering Alarms in mcRNC and Flexi Direct RNC 1. If the same alarm is raised when it is already active. its Time to Live is extended up to the expiration time defined for the last repetitive raise. However. The identifying fields are: • • • • Managed Object ID Specific Problem Identifying Additional Information Application ID The descriptions and possible values of these fields are listed in the alarm parameter tables. When two alarm instances have the same values for all the identifying fields. The alarm is cleared automatically after there are no more buffered alarms in the system for the given fault type. One such a reason can be. the buffered alarms can get activated. If there are multiple FTM alarms active for the same BTS site. The encapsulated FTM alarms are shown as 7665 BASE STATION TRANSMISSION ALARM alarm instances in RNC printouts. RNW Alarm System provides basic filtering tasks intended for application level alarm handlers. For more information. a failure in a common resource that is shared by all the faulty RNW objects. are indicated by the BTS-level alarms. which ensures that alarm situation is up-to-date in the RNC. The cell-level alarms are not reported separately. for example. then there are multiple instances of alarm number 7665 active for the same WBTS object. for example. RNW Alarm System is also responsible for keeping track of underlying Radio Network alarm situation.Administering Alarms in mcRNC and Flexi Direct RNC 1. RNW Alarm System limits the number of active alarms belonging to predefined fault categories to a defined level when it is apparent that there is a common reason for a large number of alarms. but FTM module alarms in the Flexi WCDMA BTS are handled in encapsulated format. it can be configured in the RNC. Special handling for FTM alarms in RNC The RNC implements some special handling for certain alarms from BTS sites. 7786 WCDMA BASE STATION OUT OF USE. In the Element Manager and NWI3 reporting interfaces the encapsulation is removed so that the original FTM alarm data is displayed to the user in EM and in NetAct. During suspend mode RNW Alarm System buffers internally all the alarms and when the number of active alarms belonging to a suspended fault category decreases. a large number of WCEL alarms at once. The RNW Alarm System collects alarms reported by BTSes over the BTS O&M interface. RNW ALARM SYSTEM SUSPEND MODE ACTIVATED) that contains information on the fault type that was observed in large quantities. The Radio Network objects appearing in RNW alarms are WBTS and WCEL.8 Radio network alarms Radio Network alarm handling is provided by a specific application alarm handler in the RNC. If the cell-level alarms are desired instead. is used when the whole BTS is affected because of the failure. The corresponding alarm manual page contains instructions on how to analyze the fault situation. This functionality prevents RNC alarm system and also alarm monitoring tools from exhaustion if a large scale RNW outage occurs that causes. This encapsulation is implemented because FTM alarm data content is not compatible with RNC alarm system as such. that is alarm from BTSs. This means that the data of each individual FTM alarm instance is encapsulated by BTS into a specific BTS alarm (targeted to a WBTS object) and it is stored in this format into the RNC alarm system. Basic BTS alarms targeted to WBTS and WCEL objects are handled in a straightforward fashion. the RNW Alarm System. detected in the RNC. A WBTS-object specific alarm. The RNC detects failures that affect all the working cells under the BTS. 24 Id:0900d805809a7178 Confidential DN09123463 . This reduces the alarms generated by the system and improves the reliability and performance of the system. The BTS-level failures. see General overview of RNC fault management. The suspend mode activation for a certain fault type is notified with a separate alarm (2881. The alarm situation between the RNC and individual base stations is synchronized automatically when needed. The RNW Alarm System provides a configurable suspend mode for the alarms that are set by RNC applications for RNW objects. RNW Alarm System handles all the alarms that are set by RNC application layer processes and are targeted to Radio Network objects (RNW alarms). The functional environment is similar to the one presented in Figure 3.Administering Alarms in mcRNC and Flexi Direct RNC See the alarm manual page for alarm 7665 BASE STATION TRANSMISSION ALARM in Multicontroller RNC and IPA-RNC Base Station Alarms (7000-7900) for details on how FTM alarm is encapsulated in this alarm. The Flexi Direct RNC alarm system is based on FlexiPlatform. Figure 3 DN09123463 mcRNC fault management functional environment Id:0900d805809a7178 Confidential 25 . To clear alarms on a cluster restart. If the alarms do not support switchover. It acts as a trigger to the Light Alarm System to clear alarms that were raised before the restart and have now become obsolete. Similar situations arise when a cluster is restarted. all active alarms are subjected to correlation. the alarm system automatically clears or updates obsolete alarms. However this behavior in Light Alarm System is configurable. the alarms raised against the MO becomes obsolete and needs to be cleared or updated. Light Alarm System has added two new attributes to the Configuration Directory.1 70159 MANAGED OBJECT FAILED 70166 MANAGED OBJECT LOCKED 70168 CLUSTER STARTED (RESTARTED) 70186 CLUSTER OPERATION INITIATED BY OPERATOR 70188 MANAGED OBJECT SHUTDOWN BY OPERATOR 70194 RECOVERY GROUP SWITCHOVER To reduce manual actions required for the user. The alarm system updates alarms that were raised by switched over application (HAS informs the alarm system about the switchover by sending the 70194 alarm) if the alarms supports switchover.9 Alarm correlation When a managed object (MO) is switched over. • automatic-only: This implies that only automatically cleared alarms in active alarm list are cleared on cluster restart. updates are not cleared and does not require manual clearing.Administering Alarms in mcRNC and Flexi Direct RNC 1. The following rules apply to alarm correlation: • • 1.9. • none: This value implies that none of the alarms raised before the cluster restart are cleared. updates (but the other mentioned conditions are valid) are cleared. The following alarms from HAS trigger the alarm correlation: • • • • • • g For alarm 70168. The alarm processor makes the alarm correlation by using the information provided by high availability services (HAS) in the form of alarms. • • 26 fsLightClearAlarmsOnNEReset This parameter implies what type of alarms (manual or automatic) need to be cleared. The permissible values for this parameter are as follows: • all: This value implies that all alarms (both manual and automatic) are cleared on a cluster restart. fsLightExcludeRangeFromNEResetRule This parameter implies that alarms within a range of specific problems (SP) should Id:0900d805809c23eb Confidential DN09123463 . Alarm correlation for 70168 Alarm 70168 is an informative alarm indicating that the whole cluster has been (re)started. This is the default value set in the Configuration Directory. All the alarms raised before the restart are obsolete and has to be cleared. The example above is in structured mode. The valid range is 0 < SPlow < SPhigh. This is the default value set in the Configuration Directory. The command show alarm active gives a different output in “structured mode” and “pretty mode”. g g DN09123463 The hyphen between the two values is mandatory. Id:0900d805809c23eb Confidential 27 . The possible values for this parameter are as follows: • SPlow-SPhigh: This implies that the alarms from SPlow through SPhigh should not be cleared. • none: This implies that no SPs need to be excluded during clearing of alarms.Administering Alarms in mcRNC and Flexi Direct RNC not be cleared on a cluster restart. This is a multivalued parameter and multiple ranges can be specified using this parameter. 1 2. see Administration Guide.1 Permissions Permissions for SCLI commands User must have correct permissions for executing SCLI commands. 28 Id:0900d805809a7199 Confidential DN09123463 . fsASManageAcknowledgement.1.Alarm monitoring with SCLI Administering Alarms in mcRNC and Flexi Direct RNC 2 Alarm monitoring with SCLI 2. fsASClearAlarm. see Security guide. To execute the following SCLI commands the corresponding permissions are required: Commands Permissions add or delete fsASManageConfig modify (set) fsASTest. and/or fsASManageConfig show fsASView Table 4 Permissions to execute the SCLI commands For more detailed description on the various permissions supported. For more information on managing user accounts. In the command line interface. 2 Acknowledge an alarm.Administering Alarms in mcRNC and Flexi Direct RNC 2.2 Acknowledging and unacknowledging alarms Purpose Acknowledge alarms to indicate to other users of alarm system that you are handling the alarms. enter: set alarm unacknowledge alarm-id <alarm-id> g DN09123463 The acknowledgment status is visible only in SCLI. Unacknowledge an alarm to release it for others to process. Id:0900d805809a717c Confidential 29 . In the command line interface. Steps 1 Log into the SCLI shell. enter: set alarm acknowledge alarm-id <alarm-id> 3 Unacknowledge an alarm. <file-path> is the argument specifying the absolute file path to the alarm type xml file under your home directory path. In the command line interface. place the file under /home (as the user root does not have a home directory) and provide the absolute path. enter: add alarm type from-directory dir-path /home/alarmxmls/ The following output is displayed: AlarmType Added successfully: /home/testalarmxml//test1.Administering Alarms in mcRNC and Flexi Direct RNC 2. <dir-path> is the argument specifying the absolute file path to the directory where the file is placed. enter: add alarm type from-file file-path /home/ \ alarmxmls/testspexists.xml The following output is displayed: AlarmType Added successfully 3 Add alarm type from directory. Example: To add an alarm type file located in the home directory. Steps 1 Log into the SCLI shell.3 Adding alarm types Purpose To add a new alarm type(s).xml 30 Id:0900d805809a717d Confidential DN09123463 . g If you are logged in as root. enter: add alarm type from-directory dir-path <dir-path> In the command. 2 Add alarm type from file. Example: To add an alarm type file located in the home directory. In the command line interface. g If you are logged in as root. enter: add alarm type from-file file-path <file-path> In the command. place the file under /home (as the user root does not have a home directory) and provide the absolute path. switchoverupdate Shows if the active alarm is to be updated into the new active unit by the alarm system when a unit switchover takes place. DN09123463 Id:0900d805809a717e Confidential 31 . The accepted value is a number. It is only the newly generated alarms that will show the modified alarm type parameters. it is acknowledged automatically. defines the severity level of the alarm. The accepted value is a number. informingdelay Shows the informing delay period of the alarms in milliseconds. Alarms with empty switchover update value are cleared then. The accepted value is a number. descriptions of the existing alarms will still show the original reference values. The original values are saved in the alarm system and can be restored using the alarm management application. the alarm stays active until it is explicitly cleared either by the application that raised it or by the user.Administering Alarms in mcRNC and Flexi Direct RNC 2. If the Time To Live value is not specified.4 Changing the alarm type definition Purpose To update the information of existing alarm type definition with values provided by the user. 2 Change the alarm type definition for specific problem. defaultseverity Alarm-type-specific parameter. The accepted values are on or off time-to-live Shows the lifetime of the alarms in milliseconds. In the command line interface. Table 5 Alarm type parameters Note that after you have modified any of the alarm type parameters. it means that when an alarm is cleared. The accepted values are on or off. When the parameter value for Autoacknowledged is On. Steps 1 Log into the SCLI shell. clearingdelay Shows the clearing delay period of the alarms in milliseconds. enter: set alarm type specific-problem <specific-problem> \ [autoacknowledged <auto-acknowledged-value>] \ [clearing-delay <clearing-delay-value>] \ [default-severity <default-severityvalue>] \ [informing-delay <informing-delay-value>] [switchoverupdate <switchover-update>] [time-to-live <time-to-live>] The parameters and their values are described in the following table: Alarm type parameter Description Value Range autoacknowledged Shows if the alarm is autoacknowledged or not. The accepted value is a number. The alarm type definition is updated for a given specific problem. Administering Alarms in mcRNC and Flexi Direct RNC 3 Restore the default alarm type definition for specific problem. In the command line interface. enter: set alarm type-restore-defaults specific-problem <specificproblem> 32 Id:0900d805809a717e Confidential DN09123463 . Summary The system automatically clears some alarms after the fault has been corrected. enter: set alarm clear forced yes alarm-id <alarm-id> This command clears one alarm with a specified alarm ID. The possible values for forced are as follows: Option Value Description forced yes Both manual and automatic alarms will be cleared. it allows clearing of automatically cleared alarms through the management interface using the set alarm clear command without the force keyword. In this case you cannot clear the alarm manually. To restart the alarm system.Administering Alarms in mcRNC and Flexi Direct RNC 2. In the command line interface.5 Clearing automatic alarms Purpose To manually clear automatic alarms. Restart the alarm system. 2 Clear specific alarm. To manually clear automatic alarms you must use forced option while clearing. no Only manual alarms will be cleared. enter the following command: set has restart managed-object /AlarmSystemLight 4 Clear specific alarm. fsLightManualAlarmClearingEnabled is set to false in LDAP. DN09123463 Id:0900d805809a717f Confidential 33 . This parameter does not affect manually cleared alarms set by alarm-type definition. In the command line interface. Table 6 g 3 Forced values By default. enter: set alarm clear alarm-id <alarm-id> This command clears one alarm with a specified alarm ID. If fsLightManualAlarmClearingEnabled is set to true. Steps 1 Log into the SCLI shell. If you press Enter without specifying any filter name after filter-by option in the command. The accepted value is a string of characters. The accepted value is number of severity. severity This option filters alarms with specified Severity. specific-problem This option filters alarms with specified Specific Problem. It is possible to clear more than one alarm at once by using the given criteria. The accepted value is a string of characters. enter: set alarm clear-matching-alarms forced yes filter-by [<filtername> <filtervalue> The option filter-by <filter-name> <filter-value> provides the possibility to clear the alarms by using the given criteria. The accepted value is a string of characters. managed-objectfull-name This option filters alarms with specified Managed Object pattern in DN format. The possible options for filter and their values are shown in the following table: Filter name Description Value Range application-id This option filters alarms with specified Application-ID. The accepted value is a number of the specific problem. managed-object This option filters alarms with specified Managed Object pattern. identifyingapplicationadditional-info This option filters alarms with specified Identifying Application Additional Info. The accepted value is a string of characters. then all alarms will be cleared by default.Administering Alarms in mcRNC and Flexi Direct RNC 5 g Clear alarms by the given criteria. Table 7 34 Alarm filters Id:0900d805809a717f Confidential DN09123463 . In the command line interface. 3 g Clear alarms by the given criteria. If you press Enter without specifying any filter name after filter-by option in the command. enter: set alarm clear alarm-id <alarm-id> This command clears one alarm with a specified alarm ID. The accepted value is a string of characters. Steps 1 Log into the SCLI shell. managed-objectfull-name This option filters alarms with specified Managed Object pattern in DN format. the alarm is cleared. The accepted value is a string of characters. so that the manual clearing of the alarm after it was cleared automatically is possible. The possible options for filter and their values are shown in the following table: Filter name Description Value Range application-id This option filters alarms with specified Application-ID. This is done either manually or automatically. However. managed-object This option filters alarms with specified Managed Object pattern.6 Clearing manual alarms Purpose When the fault that has caused the alarm has been corrected. Table 8 DN09123463 Alarm filters Id:0900d805809a7180 Confidential 35 . restrictions for manual clearing of the alarm can be removed. 2 Clear a specific alarm. In this case the user cannot clear the alarm manually. In the command line interface. then all alarms will be cleared by default. It is possible to clear more alarms at once by using the given criteria. This is indicated by the Clearing Info parameter value (Automatic/Manual). In the command line interface. enter: set alarm clear-matching-alarms filter-by [<filter-name> <filtervalue>] The option filter-by <filter-name> <filter-value> gives the possibility to clear the alarms by using the given criteria. Summary The system automatically clears some alarms after the fault has been corrected.Administering Alarms in mcRNC and Flexi Direct RNC 2. identifyingapplicationadditional-info This option filters alarms with specified Identifying Application Additional Info. The accepted value is a string of characters. The accepted value is a string of characters. Administering Alarms in mcRNC and Flexi Direct RNC Filter name Description Value Range severity This option filters alarms with specified Severity. This concerns alarms within the range of 7400-7799. The accepted value is number of severity. Table 8 g 36 Alarm filters (Cont.) Canceling RNW alarms with SCLI is not possible. An attempt to do so will result in the output as follows: Clear Operation failed: Alarm does not Exist or Alarm cannot be cleared manually. For canceling RNW alarms. Id:0900d805809a7180 Confidential DN09123463 . The accepted value is a number of the specific problem. OMS tools should be used instead. specific-problem This option filters alarms with specified Specific Problem. three attributes fsLightEventsProcessed. fsLightProcessingInterval. fsLightProcessorSl Sleeping time of the alarm processor. To configure the number of alarm events. and fsLightProcessorSleepInterval have been added to Configuration Directory. (1000-fsLightProcessingInterval) milliseconds Table 9 Parameters for configuring number of alarm events Example: To configure the number of alarm events. execute the following command: set config attribute fsClusterId=ClusterRoot fsFragmentId=AlarmMgmt fsFragmentId=AlarmProcessors fsAlarmProcessorId=AlarmProcessor1 DN09123463 Id:0900d805809a7181 Confidential 37 . fsLightProcessingI Time interval in milliseconds during which the nterval ALarm System processes alarm events. execute the following command: set config attribute fsClusterId=ClusterRoot fsFragmentId=AlarmMgmt fsFragmentId=AlarmProcessors fsAlarmProcessorId=AlarmProcessor1 fsAlarmProcessorConfigurationId=Default attribute-list fsLightEventsProcessed <value> Parameter Description fsLightEventsProce Number of events that the Alarm System is allowed ssed to process under normal conditions in fsLightProcessingInterval milliseconds. g Modifying of the parameters is not recommended without consulting a Nokia Siemens Networks representative.7 Configuring number of alarms processed per second Purpose To configure the number of alarms processed per second through SCLI commands. The number of alarms processed per second is dependant on the hardware used. 2 Configure the number of alarm events. Steps 1 Log into the SCLI shell by executing the fsclish command. Summary In order to restrict central processing unit (CPU) usage of Alarm System. Sleeping time eepInterval is the duration left in a second after processing the alarm events (fsLightProcessingInterval) in milliseconds. when it is bombarded with alarm events (150-200 events/seconds continuously for 10 seconds or more) while the system has other critical tasks to perform.Administering Alarms in mcRNC and Flexi Direct RNC 2. To verify if the values have taken effect. set any of the above three parameters to zero value. To restart the alarm system execute the following command: set has restart managed-object /AlarmSystemLight 4 Verifying the set configuration. 38 Id:0900d805809a7181 Confidential DN09123463 .Administering Alarms in mcRNC and Flexi Direct RNC fsAlarmProcessorConfigurationId=Default attribute-list fsLightEventsProcessed 20 g 3 To disable this feature. execute the following command: show config fsClusterId=ClusterRoot fsFragmentId=AlarmMgmt fsFragmentId=AlarmProcessors fsAlarmProcessorId=AlarmProcessor1 fsAlarmProcessorConfigurationId=Default The output displays the entire configuration of the Alarm System.You may verify the values of the set parameters. Restart the alarm system. g By default fsMultiSpBlockingRuleEnabled is set to false. by using the following command. for example 70001or 70002. to the Configuration Directory. activate. Summary Alarms can be blocked from being processed based on a specific problem (or a range of specific problems) and optionally a Managed Object Id. parameter fsMultiSpBlockingRuleEnabled is set to true. Add alarm blocking rule. Steps 1 Enable the Multi-sp Blocking Rules. retrieve and remove blocking rules. enter the following command: add alarm blocking-rule from-specific-problem <problem name> tospecific-problem < problem name> [managed-object-id <MO name> Where. This combination of a range of specific problems and a managed object id is termed as a blocking rule. Multi-sp Blocking Rules are rules based on a range of specific problems. i. To list the blocking rules in the alarm system. enter the following command: show alarm blocking-rules rule-id <rule-id> DN09123463 Id:0900d805809a7190 Confidential 39 . To add the alarm blocking rule. To set the parameter for fsMultiSpBlockingRuleEnabled to true. deactivate. based on a range of specific problems. 3 Show alarm blocking rule. you can add rules based on a single sp. To enable the Multi-sp Blocking Rules. enter the following command: set config timeout 10000 attribute fsClusterId=ClusterRoot fsFragmentId=AlarmMgmt fsFragmentId=AlarmProcessors fsAlarmProcessorId=AlarmProcessor1 fsAlarmProcessorConfigurationId=Default attribute-list fsMultiSpBlockingRuleEnabled true attribute-list fsMultiSpBlockingRuleEnabled true Restart the Alarm System for the configuration to be effective.Administering Alarms in mcRNC and Flexi Direct RNC 2. enter the following command: show alarm blocking-rules all To list the blocking rules specified by the unique rule id. set has restart managed-object /AlarmSystemLight g 2 If Multi-sp rules are disabled.8 Configuring the alarm blocking rules Purpose To configure the alarm blocking rules for the alarm system. You can add. from specific problem and to specific problem remain same. <problem name> is a number.e. 5 Deactivate the alarm blocking rule. only one can be activated. The rules can have overlapping range of specific problems incase their MOID filters are different and none of these rules have an empty MOID as a filter. Though both rules can exists at the same time. By default the rule is deactivated. To activate the rule for a specific rule-id. and the other doesn't specify a MOID (meaning all alarms within the specific problem range are blocked). by the alarm system. enter the following command: delete alarm blocking-rule rule-id <rule-id> Where. To deactivate the rule for a specific rule-id. all alarms in the active list matching to the given rule are cleared and removed from the active list. enter the following command: set alarm blocking-rule activate rule-id <rule-id> Where. To delete the alarm blocking rule for a specific rule-id.Administering Alarms in mcRNC and Flexi Direct RNC Where. rule-id is a unique-id assigned for each rule. by the alarm system. and any matching alarm raised from thereon will not be processed. rule-id is a unique-id assigned for each rule. 4 Activate the alarm blocking rule. by the alarm system. 40 Id:0900d805809a7190 Confidential DN09123463 . g Once a rule is activated. enter the following command: set alarm blocking-rule deactivate rule-id <rule-id> Where. g if there are two rules having the same range of Specific Problems and one has a MOID. 6 Delete alarm blocking rule. rule-id is a unique-id assigned for each rule. rule-id is a unique-id assigned for each rule. by the alarm system. application-id indicates the managed object ID of the application that raised or cleared the alarm.Administering Alarms in mcRNC and Flexi Direct RNC 2. enter: set alarm raise application-id <application-id-value> \ managedobject <managed-object-value> specific-problem <specificproblem-value> \ managed-object <managed-object-value> specificproblem <specific-problem-value> event time <event-time-value>] [identifying-application-additional-info \ <identifyingapplication-additional-info-value>] [severity <severity-value>] The mandatory parameters are in the following table: Parameter Description Value Range application-id The alarm will be created with this specific Application-ID. Steps 1 Log into the SCLI shell.9 Raising a test alarm Purpose To raise a test alarm. The accepted value is a number of the specific problem. In the command line interface. Table 11 DN09123463 Optional parameters for raising a test alarm Id:0900d805809a7191 Confidential 41 . managed-objectfull-name This is the name of the managed object in HAS format. 2 Raise a test alarm. The accepted value is a string of characters. managed-object indicates the ID of the faulty managed object. specific-problem The alarm will be created with this Specific Problem. The accepted value is a string of characters. The list of HAS names of RG and RU on the machine. Table 10 Mandatory parameters for raising test alarm The list of possible parameters and their values are shown in the following table: Parameter Parameter value applicationadditional-info The accepted value is a string of characters. managed-object The alarm will be created with this specific Managed Object pattern. The specific problem value must be known by the alarm system. \ fsipHostName=CLA-0.fsFragmentId=HA. If one character should not be specified. severity The accepted value is number of severity. identifyingapplicationadditional-info The accepted value is a string of characters.fshaRecoveryUnitName=Ap_Test.\ fsClusterId=ClusterRoot The sample output is: *** The ‘Alarm Notification’ to RAISE an Alarm was sent successfully.\ fsClusterId=ClusterRoot managed-object\ fshaProcessInstanceName=Mo_Test. Table 11 Optional parameters for raising a test alarm (Cont.Administering Alarms in mcRNC and Flexi Direct RNC Parameter Parameter value event-time The accepted value is date in format DDMMYYYYHHMMSSsss.fsFragmentId=Nodes. use _ which represents it.fsFragmentId=Nodes. enter the following command: set alarm raise specific-problem 70002 application-id\ fshaProcessInstanceName=Ap_Test. *** 42 Id:0900d805809a7191 Confidential DN09123463 .fsFragmentId=HA. use % which represents it.fshaRecoveryUnitName=Mo_Test.) Example: To raise a test alarm.\ fsipHostName=CLA-0. If one or more characters should not be specified. It is possible to select which alarm parameter will be shown and filter the output by giving the filtering criteria.fsLogicalNetworkElemId=NE-RNC425. Steps 1 Log into the SCLI shell.fsFragmentId=external. info : : : : : : : : : : : : : : Alarm ID Specific problem Managed object : 179554 : 7771 . 2 View active alarm data.fsClusterId =ClusterRoot : 3(major) : no : automatic : no : N/A : N/A : 2012-06-28 15:41:59:054 HKT : x4 (quality of service) : appid=fshaProcessInstanceName$E$QNOBH ERO$C$fshaRecoveryUnitName$E$QNOMUSer ver-0$C$fsipHostName$E$CFPU0$C$fsFragmentId$E$Nodes$C$fsFragment Severity Cleared Clearing Acknowledged Ack. time Alarm time Event type Application IAppl Addl.WCDMA CELL OUT OF USE : moid=WBTS-3/WCEL4.Administering Alarms in mcRNC and Flexi Direct RNC 2.10 Viewing active alarm data Summary Active alarm data can be displayed according to chosen options from the command show alarm active. enter: show alarm active The following are sample outputs: Alarm ID Specific problem Managed object Severity Cleared Clearing Acknowledged Ack. user ID Ack. Addl. time Alarm time Event type Application DN09123463 114 70360 . To view the active alarm data in the system. user ID Ack.UNSAVED CONFIGURATION IN USE fsClusterId=ClusterRoot 5 (warning) yes automatic no N/A N/A 2011-08-10 18:00:02:143 EEST x2 (processing error) fsClusterId=ClusterRoot Id:0900d805809a7192 Confidential 43 . info Appl. f sLogicalNetworkElemId=NE-RNC425. the parameters from-index and howmany can be used for specifying displayed output.fsFragmentId=external.fsClusterId =ClusterRoot : 3(minor) : no : automatic : no : N/A : N/A : 2012-06-28 15:08:52:477 HKT : x1 (communications) : appid=fshaProcessInstanceName$E$QNOBH ERO$C$fshaRecoveryUnitName$E$QNOMUSer ver-0$C$fsipHostName$E$CFPU0$C$fsFragmentId$E$Nodes$C$fsFragment Id$E$HA$C$fsClusterId$E$ClusterRoot.fsFragmentId=external.fsFragmentId=external.FAILURE IN WCDMA WBTS O&M CONNECTION : moid=WBTS2. info : : afamily=rnw ai=400$S$0d atime=1340869267000 et=x4 rawinfo=00040000000000000000000000000 00000000000000000000000000000000000 utc=480 Alarm ID Specific problem : 179462 : 7750 . Addl. time Alarm time Event type Application IAppl Addl.f sLogicalNetworkElemId=NE-RNC425.fsLogicalNetworkElemId=NE-RNC425. 44 Id:0900d805809a7192 Confidential DN09123463 .fsClusterId =ClusterRoot IAppl Addl. info Appl. Addl. info In case of many active alarm data records. info Appl.fsClusterId =ClusterRoot : si=1 : afamily=rnw ai=14608d atime=1340867320000 et=x1 rawinfo=01103900000000000000000000000 00000000000000000000000000000000000 utc=480 Managed object Severity Cleared Clearing Acknowledged Ack.Administering Alarms in mcRNC and Flexi Direct RNC Id$E$HA$C$fsClusterId$E$ClusterRoot. user ID Ack. More than one filter option can by applied at the same time. application-id This option filters alarms with specified Application-ID. cleared This option filters alarms that are in Cleared state. The from-index value of 1 specifies the latest alarm. The accepted value is a number of the specific problem. The accepted value is the numeric value of severity. specific-problem This option filters alarms with specified Specific Problem. which equals the number of records to be retrieved. managed-object This option filters alarms with specified Managed Object pattern. which means the parameter specifies the starting index for retrieving the records. The accepted values are true or false.Administering Alarms in mcRNC and Flexi Direct RNC Parameter Description from-index <number> This parameter will choose which row of alarm records the output starts from. how-many <number> This parameter will choose the number of rows of alarm records to be displayed. identifyingapplicationadditional-info This option filters alarms with specified Identifying Application Additional Info. The accepted values are true or false. g Information in the Additional infor- mation field is the correct one to be used if there is a discrepancy between content in MO field and Additional info field. The possible options for filters and their values are shown in the followingtable: Filter name Filter description and value Value Range acknowledged This option filters all alarms that are in Acknowledged state. severity This option filters alarms with specified Severity. The accepted value is a string of characters. The accepted value is a string of characters. The accepted value is a string of characters. Table 13 Alarm filters Numeric value 1 Indeterminate 2 Critical 3 Major Table 14 DN09123463 Alarm severity Numeric value for the Alarm severity Id:0900d805809a7192 Confidential 45 . Table 12 Parameters for viewing active alarm data The option filter-by <filter-name> <filter-value> gives the possibility to filter the output by the given criteria. The accepted value is a number of the specific problem.Administering Alarms in mcRNC and Flexi Direct RNC Numeric value Alarm severity 4 Minor 5 Warning 6 Cleared Table 14 Numeric value for the Alarm severity (Cont. enter: show alarm active severities 46 Id:0900d805809a7192 Confidential DN09123463 . The accepted value is the numeric value of the severity level specific-problem Shows all the Specific Problems of active alarms. starting from eight record in the alarm repository. The accepted value is a string of characters. enter: show alarm active [from-index < number>] [how-many < number>] \ [application-ids[from-index<number>][how-many<number>]][filterby<filter-by-value>] [managed-object-ids[fromindex<number>][how-many<number>]] \ [probable-cause [fromindex<number>][how-many<number>]][severities <severities value>]\ [specific-problem[from-index<number>][howmany<number>]] The option <parameter> <parameter-value> gives the possibility to choose which parameter of an active alarm will be displayed. Only one parameter can be viewed and specified in the command. managed-objectids Shows all the Managed Object IDs of active alarms.) Or When viewing active alarm data. The list of alarm parameters that can be specified for displayed output is shown in the following table: Parameter Parameter description and values Value Range application-ids Shows all the Application IDs of active alarms. enter: show alarm active from-index 8 how-many 5 filter-by acknowledged true severity 2 To view all severities of currently active alarms. The accepted value is a string of characters probable-causes Shows all the Probable Causes of active alarms. In the command line interface. you might be interested only in one parameter of active alarms. There are several parameters of active alarms that can be viewed by SCLI commands. The accepted value is a string of characters severities Shows all the Severities of active alarms. Table 15 Alarm parameters Example: To view five acknowledged alarms with severity two. Example: To view how many active alarms are in the system. In the SCLI. enter: show alarm alarm-count filter-by cleared false severity 1 acknowledged false The sample output is: Number of Alarms : 47 DN09123463 Id:0900d805809a7192 Confidential 47 .Administering Alarms in mcRNC and Flexi Direct RNC 3 View number of active alarms. enter: show alarm alarm-count The sample output is: Number of Alarms : 47 Example: To view the number of uncleared and unacknowleged alarms with severity one present in the system. enter: show alarm alarm-count [filter-by <filter-name> <filter-value>] The possible options for filter and its values are shown in the Alarm Filters table. which means the parameter specifies the starting index for retrieving the records. It is possible to select which alarm parameters will be shown and filter the output by the given filtering criteria.Administering Alarms in mcRNC and Flexi Direct RNC 2. Parameters for viewing alarm history Id:0900d805809a7193 Confidential DN09123463 . To view the alarm history. Addl.UNSAVED CONFIGURATION IN USE fsClusterId=ClusterRoot 5 (warning) yes automatic no N/A N/A 2011-08-10 18:00:02:143 EEST x2 (processing error) fsClusterId=ClusterRoot 362 x1 (raise) 7 (full visible) The following is the command with various parameters specified: show alarm history [from-index <number>] [how-many <number>] \ [filter-by <filter-name> <filter-value>] In case of many alarm history records. info Appl. how-many <number> Table 16 48 This parameter will choose the number of rows of alarm records to be displayed. which equals the number of records to be retrieved. enter the following command: show alarm history The sample output is: Alarm ID Specific problem Managed object Severity Cleared Clearing Acknowledged Ack. 2 View alarm history. user ID Ack. the parameters from-index and how-many can be used for specifying displayed output. Parameter Description from-index <number> This parameter will choose which row of alarm records the output starts from. Steps 1 Log into the SCLI shell. time Alarm time Event type Application IAppl Addl.11 Viewing alarm history Summary Alarm history data can be displayed according to chosen options from the command show alarm history. info Notification ID Extended event type Control indicator : : : : : : : : : : : : : : : : : 114 70360 . The accepted value is date in format DDMMYYYYHHMMSSSSS. managed-object This option filters all history records with specified Managed Object pattern. The accepted values are true or false.23:00:00 The output is: Alarm ID Specific problem OPERATOR DN09123463 : 621 : 70186 .01:00:00 to-event-time 29-112011. to-event-time This option filters all history records that contain this specified date and time. from-event-time This option filters all history records that contain this specified date and time. The possible options for filter and their values are shown in the following table: Filter name Filter description and value Value Range acknowledged This option filters all history records that are in Acknowledged state. cleared This option filters all history records that are in Cleared state. The accepted value is a string of characters. 29th Nov 2011. managed-object-fullname This option filters all history records with specified Managed Object pattern in DN format. The accepted value is a string of characters. Table 17 Alarm filters Example: To view first five records of cleared alarms that were cleared between 01:00.Administering Alarms in mcRNC and Flexi Direct RNC Parameter Description include-heartbeatalarms States if hearbeat alarms should be displayed in the list of events/alarms fetched. The accepted value is a string of characters. More than one filter option can by applied at the same time.) The option filter-by <filter-name> <filter-value> gives the possibility to filter the output by the given criteria. The accepted values are true or false. specific-problem This option filters all history records with specified Specific Problem. The accepted value is date in format DDMMYYYYHHMMSSSSS. Table 16 Parameters for viewing alarm history (Cont. enter: show alarm history from-index 0 how-many 4 filter-by cleared true from-event-time 20-11-2011. 20th Nov 2011 and 23:00.CLUSTER OPERATION INITIATED BY Id:0900d805809a7193 Confidential 49 . The accepted value is a number of the specific problem. application-id This option filters all history records with specified Application-ID. fsipHostName=CLA0.fsipHostN ame=CLA-0.fsFragmentId=Nodes. enter: show alarm history-count filter-by cleared false specificproblem 71096 The output is: Alarm Events count is: 82 50 Id:0900d805809a7193 Confidential DN09123463 . time : N/A Alarm time : 201 Event type : x4 (quality of service) Application : fshaProcessInstanceName=HASClusterManager. Info : Appl.fsFragmentId=H IAppl Addl.fsFragmentId=Nodes. Info : Recovery unit restarted by operator.Administering Alarms in mcRNC and Flexi Direct RNC Managed object : fshaRecoveryUnitName=FSFT_HAS_TEST_HIServer. enter: show alarm history-count [filter-by <filter-name> <filter-value>] The possible options for filter and its values are shown in the Alarm Filters table above. Example: To view how alarm events are in the history.fsClusterId=ClusterRoot Severity : 6 (cleared) Cleared : yes Clearing : automatic Acknowledged : no Ack. Notification ID : 2703 Extended event type : x4 (clear) Control indicator : 7 (full visible) 3 View number of alarm events. In the command line interface. user ID : N/A Ack.fshaRecover. Addl.fsFragmentId=HA. enter: show alarm history-count The output is: Alarm Events count is: 1822 Example: To view how many uncleared alarm events with specific problem 71096 are in history. The test instructions are the steps required to raise an alarm. g DN09123463 Test instructions should not be used in live NEs due to possible disturbances to the traffic. enter: show alarm test-instructions specific-problem <specific-problem> The parameter specific-problem <specific-problem> has a numeric value. It determines the specific problem for which the alarm test instructions information is retrieved. In the command line interface. Id:0900d805809a7194 Confidential 51 .12 Viewing alarm manual and test instructions Purpose To view the alarm manual and the test instructions for the alarm type identified by a specific problem. Steps 1 Log into the SCLI shell. Further information The parameter specific-problem <specific-problem> or more precisely all specific problems defined in the system. In the command line interface. It determines the specific problem for which the alarm manual is retrieved. can be checked by executing the command: show alarm specific-problems 3 View test instructions for an alarm.Administering Alarms in mcRNC and Flexi Direct RNC 2. 2 View the manual for an alarm. enter: show alarm manual specific-problem <specific-problem> The parameter specific-problem <specific-problem> has a numeric value. 666198 x3 0 107952 70159 MANAGED OBJECT FAILED 1 x2 2010-10-20 11:33:05:069 IST 6 0 0 1 fshaRecoveryGroupName=FTP.fsipHostName=CLA1.fsipHostName=CLA1.fshaRecoveryUnitName= FSClusterHAServer. based on the filtering criteria specified.fsClusterId=ClusterRoot fshaProcessInstanceName=HASClusterManager.fsFragmentId=Nodes.fsClusterId=Cl usterRoot Double failure: Both RU"s in cold active standby RG are faulty.fsFragmentId=HA. It is possible to filter the output displayed.fsipHostName= CLA1. enter the following command: show alarm recovery-history The sample output.Administering Alarms in mcRNC and Flexi Direct RNC 2. The same command can be executed as follows: 52 Id:0900d805809a7195 Confidential DN09123463 .fshaRecoveryUnitName=FSNod eHAServer.fsFragmen tId=HA.fsClusterId=ClusterRoot Cold active/standby RU failure: Important process FtpdIPv4Process has failed.fsFragmentId=HA.fsFragmentId=Nodes. Steps 1 Log into the SCLI shell. Summary Alarm recovery history data can be displayed according to the options chosen from the following command show alarm recovery-history. 2 View alarm history.fsFragmentId=HA. for example could be as follows: Alarm ID | Specific Problem | Alarm Text | Clearing Info | Event Type Name | Alarm Time | Perceived Severity | Acked | Ack Time | AckUser ID | Cleared | ManagedObject ID | Application ID | IAppl Additional Info | Appl Additional Info | Notification ID | Extended Event Type Name | Control Indicator 107948 70159 MANAGED OBJECT FAILED 1 x2 2010-10-20 11:33:04:992 IST 6 1 2010-1020 11:33:05:007 IST Alarm Light 1 fshaRecoveryUnitName=FSFTPServer.fsFragmentId=Nodes. To view the alarm recovery history.fsClusterId=ClusterRoot fshaProcessInstanceName=HASNodeAgent.fsFragmentId=RecoveryGroups. 66619 9 x4 0 You can choose to specify the filters based on the output desired.13 Viewing alarm recovery history Purpose To view the alarm recovery history. This option filters all history records that contain this specified date and time. More than one filter option can by applied at the same time.HH:MM:SS. Alarm filters Example: To view the recovery history for all nodes.HH:MM:SS. managed-object This option filters all history records with specified Managed Object pattern. The accepted value is a string of characters. to-event-time Table 18 The value-range is a date in format DD-MM-YYYY. mo-type This option filters all history records with specified Managed Object typepattern The value-range for motype is one of the following keywords: output can be filtered by HAS action type. specify the <filter name> as mo-type and <filter value> as node: show alarm recovery-history filter-by mo-type node The output is as follows: Alarm ID | Specific Problem | Alarm Text | Clearing Info | Event Type Name | Alarm Time | Perceived Severity | Acked | Ack Time | AckUser ID | Cleared | ManagedObject ID | Application ID | IAppl DN09123463 Id:0900d805809a7195 Confidential 53 .Administering Alarms in mcRNC and Flexi Direct RNC show alarm recovery-history [filter-by <filter-name> <filtervalue>] The option filter-by <filter-name> <filter-value> gives the possibility to filter the output by the given criteria. action-type g The action type set is cluster | node | rg | ru | process | other limited by the actions that can be extracted from HAS alarm messages. managed-objectfull-name This is the name of the managed object in HAS format. The value-range is a date in format DD-MM-YYYY. The list of HAS names of RG and RU on the machine. The value-range could be the following action types: lock | unlock | start | poweroff | shutdown | switchover. Multiple action types may be chosen. The possible options for filter and their values are shown in the following table: Filter name Filter description and value Value Range from-event-time This option filters all history records that contain this specified date and time. fsFragmentId=Nodes.fsFragmentId=Nodes. 42 x1 0 35 70189 MANAGED OBJECT UNLOCKED BY OPERATOR 1 x4 2010-09-15 19:22:56:989 EEST 6 0 0 1 fsipHostName=CLA0.fsClusterId=ClusterRoot Node unlocked by operator.Administering Alarms in mcRNC and Flexi Direct RNC Additional Info | Appl Additional Info | Notification ID | Extended Event Type Name | Control Indicator 35 70189 MANAGED OBJECT UNLOCKED BY OPERATOR 1 x4 2010-09-15 19:22:56:295 EEST 5 0 0 0 fsipHostName=CLA0.fsFragmentId=HA.fsClusterId=ClusterRoot fshaProcessInstanceName=HASClusterManager.fsFragmentId=HA.fsFragmentId=Nodes.fshaRecoveryUnitName= FSClusterHAServer.fsClusterId=ClusterRoot Node unlocked by operator.fsFragmentId=HA.fsClusterId=ClusterRoot fshaProcessInstanceName=HASClusterManager.fsipHostName=CLA0.fsFragmentId=Nodes.fsClusterId=ClusterRoot Node unlocked by operator.fshaRecoveryUnitName= FSClusterHAServer.fsFragmentId=HA.fsipHostName=CLA0. 41 x1 0 36 70189 MANAGED OBJECT UNLOCKED BY OPERATOR 1 x4 2010-09-15 19:22:56:300 EEST 5 0 0 0 fsipHostName=AS0.fsFragmentId=Nodes.fsipHostName=CLA0.fsFragmentId=Nodes. 45 x4 0 54 Id:0900d805809a7195 Confidential DN09123463 .fshaRecoveryUnitName= FSClusterHAServer.fsFragmentId=HA.fsClusterId=ClusterRoot fshaProcessInstanceName=HASClusterManager.fsFragmentId=HA. In the command line interface. The accepted value for parameter alarm-id is a number. Each alarm ID (the alarm unique identifier) can be associated with multiple notification IDs. Parameter Description from-index <number> This parameter specifies the starting index for retrieving the records.14 Viewing notification ID of an alarm Purpose To view all notification IDs of a specific alarm. enter: show alarm notification-id alarm-id <alarm-id-value> [from-index <number>] \ [how-many <number>] The parameter alarm-id <alarm-id-value> specifies the alarm for which the notification IDs must be displayed. how-many <number> Table 19 DN09123463 This parameter selects the number of rows of alarm records to be displayed. but each notification ID is only linked to one alarm ID. 2 View notification IDs of an alarm. Steps 1 Log into the SCLI shell. which is equal to the number of records to be retrieved. Summary The notification ID is a unique identifier (for the entire network element) assigned by the alarm system to every published alarm event (raise / clear / change / acknowledged /unacknowledged). Parameters for viewing notification IDs of an alarm Id:0900d805809a7196 Confidential 55 .Administering Alarms in mcRNC and Flexi Direct RNC 2. The total number of records displayed is equal to the number that you specify in the how-many <number> parameter. how-many <number> Table 20 3 This parameter allows you to choose the number of rows of alarm records to be displayed.Administering Alarms in mcRNC and Flexi Direct RNC 2. 2 View probable causes used in the alarm system. Alarm records are displayed from the particular row number which you specify in the from-index <number> parameter. Steps 1 Log into the SCLI shell. Parameters for viewing specific problems used in the alarm system Id:0900d805809a7197 Confidential DN09123463 .15 Viewing probable causes and specific problems Purpose To view all probable causes and specific problems used in the alarm system. how-many <number> Table 21 56 This parameter allows you to choose the number of rows of alarm records to be displayed. Parameters for viewing probable causes used in the alarm system View specific problems used in the alarm system. The total number of records displayed is equal to the number that you specify in how-many <number> parameter. Enter the following command: show alarm probable-causes [from-index <number>] [how-many <number>] Parameter Description from-index <number> This parameter allows you to specify the starting index number for retrieving the alarm records. Enter the following command: show alarm specific-problem [from-index <number>] [how-many <number>] Parameter Description from-index <number> This parameter allows you to specify the starting index number for retrieving the alarm records. Alarm records are displayed from the particular row number that you specify in the from-index <number> parameter. 2 View the alarm type definition for specific problem.INVALID SNMP TRAP COMMUNITY : : : : : : : 153 . 3 View all alarm type definitions used in the alarm system. This parameter allows the user to choose the number of rows of alarm records to be displayed. The total number of records displayed is equal to the number which is specified in the how-many <number> parameter. It determines the specific problem for which the alarm type definition is retrieved.16 Viewing the alarm type definition Purpose To view the alarm type definition for the given specific problem.Administering Alarms in mcRNC and Flexi Direct RNC 2. In the command line interface. enter: show alarm type specific-problem <specific-problem> The parameter specific-problem <specific-problem> has a numeric value. how-many <number> Table 22 Parameters for viewing all alarm type definitions used in the alarm system Example: To view the alarm type definition for a specific problem. In the command line interface. enter the following command: show alarm type specific-problem 70002 The output is: Specific problem STRING Probable cause Default severity Clearing Auto acknowledged Switch over update Event type Clearing delay DN09123463 : 70002 . Steps 1 Log into the SCLI shell. enter: show alarm type-all [from-index <number>] [how-many <number>] Parameter Description from-index <number> This parameter allows the user to specify the starting index number for retrieving the alarm records. Alarm records are displayed from the particular row number which is specified in the from-index <number> parameter.Corrupt data 4 (minor) manual yes yes x2 (processing error) 0 Id:0900d805809a7198 Confidential 57 . IN-MEMORY DATABASE PARTITION Specific problem NETWORK ELEMENT Probable cause : 70025 .SERVICE LEVEL DEGRADED BELOW Specific problem GETTING FULL Probable cause Default severity Clearing Auto acknowledged Switch over update Event type Clearing delay Informing delay Time to live Operation instructions : 70013 .Equipment malfunction 3 (major) automatic yes no x5 (equipment) 0 0 0 Not defined 315 .Equipment malfunction 4 (minor) automatic yes no x5 (equipment) 0 30000 0 Not defined 351 .Threshold crossed 3 (major) automatic yes no x4 (quality of service) 0 0 0 Not defined : 351 .POSSIBLE SECURITY THREAT IN : : : : : : : : : : : : : : : : : : : : 70011 .Threshold crossed Id:0900d805809a7198 Confidential DN09123463 .Administering Alarms in mcRNC and Flexi Direct RNC Informing delay : 0 Time to live : 0 Operation instructions : Not defined Example: To view all the alarm type definitions used in the alarm system. enter the following command: show alarm type-all from-index 10 how-many 5 The output is: 58 Specific problem Probable cause Default severity Clearing Auto acknowledged Switch over update Event type Clearing delay Informing delay Time to live Operation instructions : : : : : : : : : : : Specific problem THRESHOLD Probable cause Default severity Clearing Auto acknowledged Switch over update Event type Clearing delay Informing delay Time to live Operation instructions : 70012 .NODE NOT RESPONDING 315 . DISK DATABASE IS GETTING : : : : : : : : : : 4 (minor) manual yes yes x4 (quality of service) 0 0 0 Not defined 151 .Administering Alarms in mcRNC and Flexi Direct RNC DN09123463 Default severity Clearing Auto acknowledged Switch over update Event type Clearing delay Informing delay Time to live Operation instructions : : : : : : : : : Specific problem FULL Probable cause Default severity Clearing Auto acknowledged Switch over update Event type Clearing delay Informing delay Time to live Operation instructions : 70030 .Storage capacity problem 3 (major) automatic yes no x2 (processing error) 0 0 0 Not defined Id:0900d805809a7198 Confidential 59 . and also for controlling the RNC and OMS alarm system functionality. OMS element manager (EM) support OMS element manager provides Fault Management application for viewing and managing the alarm situation in the RNC. NWI3 interface support OMS works as a mediator between the RNC and NetAct and it provides NWI3 interface support for reporting and synchronizing alarms between these elements. OMS application layer functionality collects alarms from FP AS and stores the alarms to OMS alarm system. for example after connection break situations.Alarm handling in OMS Administering Alarms in mcRNC and Flexi Direct RNC 3 Alarm handling in OMS OMS functions Operation and Management Server (OMS) provides the NWI3 interface towards NetAct for alarm reporting and Element Management Interface (EMI) for RNC local management via OMS element manager. FlexiPlatform alarm database is used to store the RNC alarm situation in OMS and it also functions as alarm history storage for the whole network element. which means that RNC and BTS sites are not part of alarm synchronization scenario that is performed over NWI3. OMS applications can also set alarms that are handled by OMS alarm system. For more information on alarm system in OMS. The changes in alarm situation are reflected in real-time to NetAct and OMS element manager. see Managing Faults with OMS. OMS can also synchronize the alarm situation between itself and FP AS whenever needed. OMS own alarms are visible locally via the Fault Management application in the OMS element manager. OMS can also ask alarm cancellation from FP AS if the user has performed manual alarm cancelling task using the OMS EM. The counterpart for OMS alarm system in mcRNC/Flexi Direct RNC is the FP AS that sends the changes in alarm situation to OMS. FlexiPlatform alarm system provides also an interface for OMS applications to set and clear alarms. OMS interface to RNC OMS is connected to RNC with the BTS O&M interface which allows OMS to communicate using BTS O&M protocol messages. OMS alarm system OMS is implemented on top of FlexiPlatform that provides the alarm system functionality for OMS. 60 Id:0900d805809a71a4 Confidential DN09123463 . Alarm synchronization is done on the basis of alarm situation in OMS.