W-NMS Historical Fault Browser

411-5221-210

Wireless Service Provider Solutions

W-CDMAAlcatel-Lucent 9353 Management SystemHistorical Fault Browser411-5221-210 07.07/EN Preliminary September 2008

Wireless Service Provider Solutions

W-CDMAAlcatel-Lucent 9353 Management SystemHistorical Fault Browser

Document number: 411-5221-210Document issue: 07.07/ENDocument status: PreliminaryProduct release: OAM06.0Date: September 2008

Copyright © 2002-2008 Alcatel-Lucent, All Rights Reserved

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "writeprotected"; it may be altered only by authorized persons. While copies may be printed, it is notrecommended. Viewing of the master electronically ensures access to the current issue. Any hardcopiestaken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property ofAlcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep allinformation contained herein confidential, shall disclose the information only to its employees with a needto know, and shall protect the information from disclosure and dissemination to third parties. Except asexpressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the informationcontained herein. If you have received this document in error, please notify the sender and destroy itimmediately.

Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marksof Alcatel-Lucent, Alcatel and Lucent Technologies.

Windows is a registered trademark of Microsoft Corporation in the United States and other countries.Solaris™ and the JRE™ are trademarks of Sun Microsystems. Oracle is a trademark of OracleCorporation.

All other trademarks are the property of their owners.

PUBLICATION HISTORYSYSTEM RELEASE: OAM06.0

September 2008

Issue 07.07/EN Preliminary

Update after internal review

September 2008

Issue 07.06/EN Draft

Intermediate update

August 2008


Update for DR4

July 2008



April 2008


Update for Pre-DR4

April 2008



February 2008


Update for V6.0 April-08 portfolio content

SYSTEM RELEASE: OAM05.2

November 2007

Issue 06.03/EN Standard

Publication history i

Copyright © 2002-2008 Alcatel-Lucent Historical Fault Browser

Update for DR5

September 2007



August 2007


Update for OAM05.2

SYSTEM RELEASE: UMTS 5.1

June 2007

Issue 05.13/EN Standard

Update for UA 5.0 / OAM 5.1 Channel Readiness

May 2007


Document translated into Alcatel-Lucent template

February 2007


Update for UA 5.0 / OAM 5.1 Customer Readiness

The Publication History information for the outdated releaseshas been deleted.Document creation date: November 2002.

Publication history ii

411-5221-210 07.07/EN Preliminary September 2008 Copyright © 2002-2008 Alcatel-Lucent

1 About this publication................................................................................................................................................... 1

2 UMTS Access Network Collection Roadmap...............................................................................................................2

3 New in this release.........................................................................................................................................................3

4 Historical Fault Browser Operation..............................................................................................................................4

4.1 Overview.....................................................................................................................................................................5

4.1.1 Features............................................................................................................................................................... 6

4.1.2 Components......................................................................................................................................................... 7

4.1.3 System requirements........................................................................................................................................... 9

4.1.4 Supported Web browsers...................................................................................................................................10

4.1.5 HFB Agent..........................................................................................................................................................11

4.2 HFB user interface....................................................................................................................................................12

4.2.1 Select Retrieval Criteria page.............................................................................................................................13

4.2.2 View Records page............................................................................................................................................ 26

4.2.3 Alarm Record Details page................................................................................................................................ 38

4.2.4 Alarm report generation......................................................................................................................................39

4.2.5 Archiving and retrieving historical data...............................................................................................................43

4.3 Procedures............................................................................................................................................................... 44

4.3.1 Viewing historical alarms in HFB........................................................................................................................48

4.3.2 Generating alarm reports using the HFB WICL Editor....................................................................................... 49

4.3.3 Implementing the HFB input filtering feature...................................................................................................... 51

5 Historical Fault Browser Administration....................................................................................................................52

5.1 Overview...................................................................................................................................................................53

5.1.1 Administering HFB agent................................................................................................................................... 54

5.1.2 HFB Database Maintenance Program............................................................................................................... 55

5.1.3 Application log files.............................................................................................................................................56

5.1.4 HFB database schema.......................................................................................................................................58

5.1.5 Archiving and retrieval........................................................................................................................................82

5.1.6 Capacity planning...............................................................................................................................................83

5.2 Procedures............................................................................................................................................................... 85

5.2.1 Setting HFB database maintenance...................................................................................................................86

5.2.2 Clearing domains when HFB agent is removed................................................................................................. 87

6 Managing Oracle administrator user IDs................................................................................................................... 88

6.1 Overview...................................................................................................................................................................89

6.2 Procedures............................................................................................................................................................... 91

6.2.1 Changing passwords of HFB database users.................................................................................................... 92

Table of contents iii


6.2.2 Changing the Oracle tnslsnr port password....................................................................................................... 93

6.2.3 Changing HFB passwords..................................................................................................................................95

Table of contents iv


Figure 1 - HFB architecture................................................................................................................... ............. ........... 8

Figure 2 - Select Retrieval Criteria page............................................................................................... ............. ......... 13

Figure 3 - Network panel....................................................................................................................... ............. ......... 15

Figure 4 - Retrieval Criteria list.............................................................................................................. ............. ......... 18

Figure 5 - Network Domain Selection panel.......................................................................................... ............. ......... 18

Figure 6 - Search selected domains................................................................................................................... ......... 19

Figure 7 - Status panel.......................................................................................................................... ............. ......... 19

Figure 8 - Severity panel....................................................................................................................... ............. ......... 20

Figure 9 - Event Type panel.................................................................................................................. ............. ......... 21

Figure 10 - Probable Cause panel........................................................................................................ ............. ......... 22

Figure 11 - Date/Time panel............................................................................................................................... ......... 23

Figure 12 - Threshold panel.................................................................................................................. ............. ......... 24

Figure 13 - Criteria Sets panel.............................................................................................................. ............. ......... 25

Figure 14 - Example of View Records page (1/6)................................................................................. ............. ......... 27






Figure 20 - Alarm Record Details page................................................................................................. ............. ......... 38

Figure 21 - Alarm report generated via the HFB query interface.......................................................... ............. ......... 41

Figure 22 - Alarm report with filter information...................................................................................... ............. ......... 42

Figure 23 - Archived alarms on the View Records page....................................................................... ............. ......... 43

Figure 24 - WICL Script Editor window................................................................................................. ............. ......... 49

Figure 25 - Diagram of HFB alarm data tables................................................................................................... ......... 63

List of figures v


Table 1 - Search by values in the Network panel.................................................................................. ............. ......... 15

Table 2 - Operator Values in Network panel......................................................................................... ............. ......... 17

Table 3 - Status check boxes................................................................................................................ ............. ......... 19

Table 4 - Severity check boxes............................................................................................................. ............. ......... 20

Table 5 - Event type check boxes......................................................................................................... ............. ......... 21

Table 6 - Date/Time panel elements..................................................................................................... ............. ......... 23

Table 7 - Alarm List fields................................................................................................................................... ......... 32

Table 8 - Alarm Report fields.............................................................................................................................. ......... 39

Table 9 - FMBB or TUMSBB to HFB mapping...................................................................................... ............. ......... 58

Table 10 - Alarms table......................................................................................................................... ............. ......... 64

Table 11 - ThresholdInfo table.............................................................................................................. ............. ......... 70

Table 12 - nedata table......................................................................................................................... ............. ......... 71

Table 13 - severity table........................................................................................................................ ............. ......... 72

Table 14 - eventType table................................................................................................................................. ......... 72

Table 15 - Status table.......................................................................................................................... ............. ......... 73

Table 16 - trendindicationconst table.................................................................................................... ............. ......... 73

Table 17 - probablecauseconst table.................................................................................................... ............. ......... 73

Table 18 - Criteria set table................................................................................................................... ............. ......... 81

Table 19 - Default Oracle user IDs and password settings................................................................... ............. ......... 89

List of tables vi


1 About this publicationThis publication explains what is the Historical Fault Browser, how it works and how to administer itsrelated database.

Applicability

This publication applies to OAM06.0

Audience

This document is intended for UMTS WMS administrators.

Prerequisites

It is recommended that readers become familiar with document Alcatel-Lucent 9353 ManagementSystem: System Overview (NN-20500-031).

Related documents

The following publications are mentioned in this document:

• Alcatel-Lucent 9353 Management System - Security: User Configuration and Management(NN-10300-074)

• Alcatel-Lucent 9353 Management System – Security: Overview (NN-10300-031)

How this document is organized

This document consists of the following chapters:

• Historical Fault Browser Operation explains what is the Historical Fault Browser and describes itsgraphical user interface.

• Historical Fault Browser Administration explains how to administer the Historical Fault Browser.

• Managing Oracle administrator user IDs explains how to manage administrator user IDs on theOracle database.

Vocabulary conventions

For a definition of terms used in this document, see Alcatel-Lucent 9300 W-CDMA Product Family -Terminology (NN-20500-002).

1


2 UMTS Access Network Collection Roadmap

For collection roadmap, see Alcatel-Lucent 9300 W-CDMA Product Family - Document CollectionOverview and Update Summary (NN-20500-050).

2


3 New in this releaseThe following sections detail what is new in Alcatel-Lucent 9353 Management System - HistoricalFault Browser (411-5221-210) for OAM06.0.

Features

For more information, see the following sections:

• Alarm correlation (23571)

• HFB input filtering (24507)

• Alarm List fields (Alarm code display) (30639)

• HFB query interface (30641)

Other changes

See UMTS Access Network Collection Roadmap for the changes that are not related to features.

OneBTS added to the Alarm List fields.

Modified examples of View Records page. See View Records page.

New HFB database fields. See:

• Alarm Report fields

• FMBB or TUMSBB to HFB mapping

• Alarms table

3


4 Historical Fault Browser OperationThe Historical Fault Browser (HFB) is an optional software application that builds on the alarmmanagement functions of the Network Services Platform (NSP). The NSP alarm management toolsprovide real-time alarm information for the network elements they monitor. HFB provides a databaseof historical alarms for trend analysis.

There are instances when alarms are generated for NEs that are not fully enrolled by thesystem. In such cases, HFB captures the alarms but the corresponding NE information ismissing. HFB periodically updates these alarms with the missing NE information.

For an overview of the HFB application and its operation, see Overview.

For a procedure on retrieving alarms from the HFB database, see Viewing historical alarms in HFB.

4


4.1 OverviewThis section provides detailed information on the following topics:

• Features

• Components

• System requirements

• Supported Web browsers

• HFB Agent

• HFB user interface

5


4.1.1 FeaturesThe Historical Fault Browser (HFB) is a tool that supports stored alarm events for all managednetwork elements (NE). It provides a central storage and retrieval capability for network alarmevents, as well as alarm event filtering and report generation capabilities. The alarm eventssupported are raise alarm, clear alarm, acknowledge alarm, unacknowledge alarm, manual alarmclear, and notification ID change.

The HFB retrieves alarm events (raise and clear) from the network using the building blockarchitecture. The HFB stores the alarm events in an Oracle Relational Database ManagementSystem (RDBMS). The graphical user interface (GUI) for the HFB supports the search, display, andreport generation of the selected alarm event data from the database.

In summary, the HFB provides the following main features:

• generic alarm event history across network elements managed, which does not depend on thevendor or technology

• central storage of alarm event history in an Oracle RDBMS

• a web based Java application GUI for retrieving alarm event data that is easy to use and providesthe following features:

— sophisticated filtering support

— report generation capability for analysis and tracking purposes

6


4.1.2 ComponentsThe HFB consists of two separate component applications: the HFB Agent and the HFB GUI (seeHFB architecture). The HFB Agent retrieves alarm event information from the Fault ManagementBuilding Block (FMBB) and Topology Management Building Block (TUMSBB), and stores theinformation in the Oracle database. The HFB GUI supplies a flexible, graphical user interface (GUI)that is run in a supported web browser. The HFB GUI lets the user search for alarm events in thedatabase, and generate reports.

The HFB Agent takes advantage of the open architecture to retrieve information about alarm events.The HFB Agent is a client of the FMBB and TUMSBB. The HFB uses the open contract interfaceprovided by the FMBB and TUMSBB to retrieve information from the network. This interface is basedon the Common Object Request Broker Architecture (CORBA) Interface Definition Language (IDL).The HFB Agent begins to retrieve alarm event information immediately after the addition of a newnetwork element (NE) to the network.

The HFB is a client of the separate Oracle Relational Database Management System (RDBMS). Thealarm event information stored in the database maps to the information provided by the FMBB andTUMSBB CORBA IDL interfaces. The HFB communicates with the database through the databaseinterface.

7


Figure 1 HFB architecture

8


4.1.3 System requirementsHFB is a value added application that is deployed over the Network Services Platform (NSP). HFB iscompatible with NSP and you must install NSP before installing HFB. FMBB and TUMSBB must alsobe installed and running before HFB can be installed. For information on the hardware andoperatingfor HFB, see Alcatel-Lucent 9353 Management System - User Guide (NN-20500-032) .

HFB 2.4 requires that the Oracle 9.2.0.5 Relational Database Management System (RDBMS)software, Enterprise edition with the Partitioning Option be installed on the NSP server.Alcatel-Lucent has tested and approved HFB with Oracle RDBMS software. Applications developedusing Oracle database capabilities take advantage of the following features:

• large database capacity capable of storing 60,480,000 alarms

• fast retrieval of alarm history information

• stable and reliable database environment, accepted on a global basis.

9


4.1.4 Supported Web browsersThe HFB client workstation must have a supported Web browser installed. Examples are InternetExplorer 5.0 or later and Mozilla 1.4.

If using the Internet ExplorerWeb browser, ensure the following option is set:

• From the Internet Explorer Tools menu, select Internet Options.

• Select the General tab, and in the Temporary Internet files area, click Settings.

• In the list under Check for newer versions of stored pages, click the option Every visit to thepage.

• Click OK in the Settings window, and OK in the Internet Options window to close the window.

10


4.1.5 HFB AgentThe Historical Fault Browser (HFB) Agent retrieves alarm events from the managed network andstores them in a database. These alarm events include raise alarm, clear alarm, acknowledge alarm,unacknowledge alarm, manual alarm clear, and notification ID change. The HFB Agent uses keyattributes to connect the clear alarm events with original raise alarm events.

The HFB Agent is a client of the Fault Management Building Block (FMBB) and TopologyManagement Building Block (TUMSBB). The HFB Agent can operate only after FMBB and TUMSBBare installed and running in the network.

The HFB Agent connects to the FMBB to retrieve active and new alarms on a continuing basis. TheHFB Agent also connects to the Topology Management Building Block (TUMSBB) to retrieveinventory data on network elements needed for alarm events.

If either the HFB Agent or FMBB goes down, a data resynchronization takes place whencommunication is restored.

If FMBB goes down, it resynchronizes with its device adapters (DA) when it returns to service. Oncethis exercise is complete it sends a message to the HFB Agent announcing that the HFB Agent cannow update its data.

If the HFB Agent goes down, it contacts FMBB when it returns to service to obtain an up-do-date listof active alarms.

In either case, any alarms that were cleared during the loss of communication will cause adiscrepancy between the old list of active alarms stored by the HFB Agent and the new list of activealarms provided by FMBB. As a result, the HFB Agent will clear these alarms with the hfbmaster userID and will timestamp them with the server time where the HFB Agent is located.

If massive incoming alarm events exceed the HFB Agent capacity, the HFB Agent discards andlogs them. The HFB Agent can be customized.

11


4.2 HFB user interfaceHistorical Fault Browser (HFB) provides users with a flexible interface with which to search for alarmdata in the database. The HFB interface is a web based Java application. Users start the HFBinterface by entering the required universal resource locator (URL) in the address field of their webbrowser. The HFB client workstation supports various Web browsers (examples: Internet Explorer5.0 or later, Mozilla 1.4). The HFB user interface does not support the Web browser buttons fornavigation.

The HFB interface provides the tools for finding and viewing historical alarms. The HFB interfaceallows you to:

• build and save search criteria

• retrieve and view alarm records based on search criteria

• view details of alarms

• count the number of alarm records

• generate alarm reports

For detailed descriptions of HFB functions, see the following:

• Select Retrieval Criteria page

• View Records page

• Alarm Record Details page

• Alarm report generation

12


4.2.1 Select Retrieval Criteria pageUse the Select Retrieval Criteria page (see Select Retrieval Criteria page) to define which historicalalarms to retrieve. The Select Retrieval Criteria page allows you to build search criteria to retrieverequired alarm records from the HFB database. HFB displays the Select Retrieval Criteria pagewhen you open the application.

The Select Retrieval Criteria page contains two sections:

• criteria tabs

• Selected Retrieval Criteria List

Figure 2 Select Retrieval Criteria page

The top section of the Select Retrieval Criteria page contains eight tabs for setting querystatements. Each tab allows you to define a query statement using a specific attribute type. For adetailed description of the attributes in each criteria tab, see:

• Network panel

• Status panel

• Severity panel

• Event Type panel

• Probable Cause panel

13


• Date/Time panel

• Threshold panel

• Criteria Sets panel

When you open the Select Retrieval Criteria page, the Network panel is the default display.

The bottom section of the Select Retrieval Criteria page contains the Selected Retrieval CriteriaList. The criteria list is built from query statements created in the criteria tabs. The criteria areadditive. The query statements are concatenated to form the search criteria. The system uses thesearch criteria to filter data from the database and display alarm records that meet the criteria.

You can build a query statement using multiple values for the same attribute. The search criteria isformed using Boolean AND and OR logical operators. See the attribute descriptions for details onhow a query statement is constructed.

Manage the Selected Retrieval Criteria List using Delete Selected and Reset to Default. Todelete an individual query statement, select it and click Delete Selected. To clear all current querystatements, click Reset to Default. This resets all panels to default values and the Retrieval CriteriaList displays the default "Raised during the last two hours" query statement.

Click Count to determine how many records match your query. The number of matching records isdisplayed along with the timestamp. You can then choose to modify or cancel your query ifnecessary.

If the Selected Retrieval Criteria List is empty, the system will count all of the alarm records whichwere raised during the last two hours.

Use Save Criteria at any time to save a new set of retrieval criteria you have built, or to update anexisting criteria set. The Save Criteria Set page opens and you can specify a unique file name andsave your criteria set to the database. The file name must not exceed 40 characters.

Click View Records to search the database for alarms that meet the criteria you have specified. Ifthe Selected Retrieval Criteria List is empty, the system will retrieve the first 500 alarm records inthe database.

Some browsers generate a security warning message when you perform an action that requiresinteraction with the database server. You can eliminate these messages by selecting the appropriatebox in the message dialog before continuing.

Click Export Report to perform the same database search as the one requested using ViewRecords. However, the output is saved to a file and the record number is limited to 10,000. SeeAlarm report generation.

An In Progress dialog box appears as the system retrieves your query. The Historical Fault Browserwill time out after 30 minutes of either idle or query time. If your query is too time consuming, clickCancel to prevent the system from timing out, and then revise your query:

• Terminate and restart the HFB UI after a time out occurs. Although the session has been

14


terminated after 30 minutes of idle or query time, the HFB system remains responsive and amanual termination and restart is recommended.

• For information about the mapping of the HFB database fields to equivalent fields from the FaultManagement Building Block (FMBB) and Topology Management Building Block (TUMSBB), theCommon Object Request Broker Architecture (CORBA) Interface Definition Language (IDL) isprovided (see FMBB or TUMSBB to HFB mapping).

• Some fields may not apply to all domains. For more information, refer to the device adapterdocumentation for your domain.

Network panel

Use the Network panel (see Network panel) to add query statements to the Selected RetrievalCriteria List based on network attributes (see Search by values in the Network panel). The attributesare available from a pull down menu in the Search by field. A second pull down menu allows you todefine criteria based on partial values (see Operator Values in Network panel). Text entered in theValue field is case sensitive.

Figure 3 Network panel

If you choose to define retrieval criteria based on the NE ID attribute, you can specify the domains tosearch. See Multiple network domain search by NE ID.

Table 1 Search by values in the Network panel

15


Search by HFB database field Meaning Syntax (max sizes)

NE Name (see Note 1) NEUserLabel display informationconsisting of the nameof the network element

alphanumeric (80characters)

NE ID NENumber display informationconsisting of the net-work element identifier


CLFI CLFI Common LanguageFacility Identifier(CLFI) string receivedfrom the network ele-ment


Subcomponent ID subcomponentId additional detailsabout the network ele-ment that generatedthe alarm


Clear User ID MACUSERID user ID of the operatorwho manually clearedthe alarm user ID = hf-bmaster if the alarmwas cleared whileeither the HFB Agentor FMBB was down


Ack User ID AAUSERID user ID of the last userthat performed the lastacknowledgementevent.

Note: The current re-lease of HFB onlystores the last ac-knowledgement event


Additional Text additionalText description of thealarm condition


Full Component DN alarmedcomponent display information us-ing the distinguishedname (DN) to clearly


16


Search by HFB database field Meaning Syntax (max sizes)

identify the networkelement

Alarm Code faultcode Uniquely identifies thealarm type

Note 1: You cannot query the database using NE Name when the database contains morethan 14 million alarms.

Note 2: If you exceed the default sizes when you enter the values in the search panel, the HFBmay not properly execute a saved query.

Table 2 Operator Values in Network panel

Operator Meaning

Equals is equal to the entered value (see Note)

Does not equal the entered value will not appear (see Note)

Contains contains the entered value

Does not contain the entered value will not be part of the record

Starts with starts with the entered value

Ends with ends with the entered value

Note: This function may not be supported if the database structure of any of the fields inSearch by values in the Network panel has been changed.

You can build multiple query statements using the same alarm record field, but with differentoperators or values:

• If your query string only uses the positive operators, such as Contains or Equals, the system joinsthese multiple query statements with OR.

• If your query string uses only the negative operators, Does not contain or Does not equal, thequery string is joined by AND.

• If your query contains both positive and negative operators, the system will group the positivequeries with OR, group the negative queries with AND, then join the two groups using AND.

An alarm event must meet the criteria of at least one query statement for the system to select it fromthe database.

You can also build multiple query statements with different alarm record fields. The system joinsthese multiple query statements with a logical AND operator. An alarm event must meet all of thecriteria from each query statement for the system to select it from the database.

17


When you build query statements that include multiple statements with the same alarm record fieldand some with different fields, the system will group all criteria items for the same attribute so thatthey appear together. The criteria list is also sorted by positive criteria followed by negative criteria, toproduce the final alarm set. See Retrieval Criteria list for an example of a retrieval criteria list sortedin this way.

Figure 4 Retrieval Criteria list

Multiple network domain search by NE ID

When you specify a search by network element identifier (NE ID) with an operator value of Equals,you are given the option of searching all accessible network domains or limiting the search toselected domains. If you choose to restrict the search to selected domains (by selecting OK), theNetwork Domain Selection panel opens:

Figure 5 Network Domain Selection panel

Within this panel, you have two choices. You can choose that all of the domains listed be included inthe search, by clicking Add All Domains. Or you can select one or more of the domains listed and

18


click Add Selected Domains. In this case, query statements are created to specify the selecteddomains (see next figure).

Figure 6 Search selected domains

Status panel

Use the Status panel (see Status panel) to add query statements to the Selected Retrieval CriteriaList based on alarm and acknowledgement status. The system adds a separate statement for eachof the check box values (see Status check boxes). If an alarm status criteria and anacknowledgement status criteria are selected, the system queries the database for alarms with bothcriteria.

Figure 7 Status panel

A query statement is created for each check box selected. However, the system implements thesearch in the following order:

• performs a logical OR on selected alarm status levels

• performs a logical OR on selected acknowledgement status levels

• performs a logical AND on the resulting alarm and acknowledgement status levels

For example, selection of the Active, Cleared, and Acknowledged check boxes creates a searchcriteria that retrieves all active or (system) cleared alarms that have been acknowledged by anoperator.

The Status check boxes map to the activeStatus field and the Ack. Status check boxes map to theACKSTATUS field in the Historical Fault Browser (HFB) database.

Table 3 Status check boxes

Status type Check box Meaning

Alarm status Active selects alarms that have not

19


Status type Check box Meaning

been cleared

Cleared selects all cleared alarms(cleared by the system, an op-erator, or the hfbmaster userID)

Manually Cleared selects alarms cleared by anoperator and alarms clearedwith the hfbmaster user ID

Acknowledgement status Acknowledged selects alarms that have beenacknowledged by an operator

Unacknowledged selects alarms that have notbeen acknowledged by an op-erator

Severity panel

Use the Severity panel (see Severity panel) to add query statements to the Selected RetrievalCriteria List based on alarm severity. The system adds a separate statement for each of the checkbox values (see Severity check boxes).

Figure 8 Severity panel

You can select one or more of the alarm severity check boxes. A query statement is added for eachseverity selected. An alarm must have any one of the selected severity levels for the system to selectit from the database.

The Alarm Severity check boxes map to the perceivedSeverity field in the Historical Fault Browser(HFB) database.

Table 4 Severity check boxes

Check box Meaning

Critical selects critical alarms

20


Check box Meaning

Major selects major alarms

Minor selects minor alarms

Unknown selects alarms of unknown severity

Warning selects warning alarms

Event Type panel

Use the Event Type panel (see Event Type panel) to build a query statement based on event type.The system adds a separate statement for each of the check box values.

Figure 9 Event Type panel

A query statement is added for each event type selected. An alarm must be one of the selectedevent types (see Event type check boxes) for the system to select it from the database.

The Event Type check boxes map to the eventType field in the Historical Fault Browser (HFB)database.

The Event Type check boxes map to the eventType field in the Historical Fault Browser (HFB)database.

Table 5 Event type check boxes

Check box Meaning

Communications Communication alarms

Environment Environmental alarms

Equipment Equipment alarms

Processing Error Processing error alarms

Quality of Service Quality of Service alarms

Integrity Violation Indication that the information may have beenillegally modified, inserted or deleted

21


Check box Meaning

Operational Violation Indication that the requested service provision-ing was not possible due to service unavailab-ility, malfunction or incorrect invocation

Physical Violation Indication that a physical resource was viol-ated in such a way that a security attack mighthave occurred

Security Service Or Mechanism Violation Indication that a security attack was detectedby a security service or mechanism

Time Domain Violation Indication that an event occurred at an unex-pected or prohibited time

Probable Cause panel

Use the Probable Cause panel (see Probable Cause panel) to build a query statement based on theprobable cause of alarms. You can use only Global form text values from the M3100 standard or theCause Names from the X.721 standard. The results are also displayed as the text value only. Referto the Probable Cause field of the Alarm List for valid Probable Cause values. You can also enter anystring to search for an alarm with a configurable probable cause field.

Figure 10 Probable Cause panel

A query statement is added for each probable cause value you specify and you can build your criteriaspecifying either Contains or Does not contain. An alarm must have the probable cause matchingone of the values specified for the system to select it from the database. If you are using MicrosoftInternet Explorer on Windows 2000 or XP for the Historical Fault Browser, you must disable the scriptdebugging option to prevent Explorer from displaying invalid error messages. The Probable Causevalues map to the probableCause field in the Historical Fault Browser (HFB) database.

Date/Time panel

Use the Date/Time panel (see Date/Time panel) to build a query statement based on the date and

22


time that an alarm was raised or cleared.

Figure 11 Date/Time panel

The query statement is in the form event, date, time. You can create a query statement with a dateand time range, or just a start or an end date and time (see Date/Time panel elements). The systemgenerates a time range as a single query statement. The system joins multiple date and time querystatements with a logical OR operator. An alarm event must meet the criteria of at least one of thespecified query statements for the system to select it from the database.

The system provides an initial date and time query statement by default. The value of the defaultquery statement is the last two hours before the current time on the NSP server. You can delete thedefault Date and Time query statement.

ATTENTION

If you delete the default Date and Time query statement and do not replace it, HFB willsearch the alarms raised in the last two hours. Whenever possible, include a Date andTime query statement in the Retrieval Criteria List.

The Date and Time fields for a raised alarm map to the eventTime field in the Historical FaultBrowser (HFB) database. The Date and Time fields for a cleared alarm map to the clearTime field inthe HFB database. Alarm records in the database are stored in Coordinated Universal Time (UTC)and displayed in local time (local time of the operator).

Table 6 Date/Time panel elements

Element Function

Raised radio button selection of raised alarms

Cleared radio button selection of cleared alarms

From Date field entry of the start date in yyyy/mm/dd format

From Time field entry of the start time in hh:mm:ss format

23


Element Function

To Date field entry of the end date in yyyy/mm/dd format

To Time field entry of the end time in hh:mm:ss format

Threshold panel

Use the Threshold panel (see Threshold panel) to build a query statement based on the thresholdattributes of a Quality of Service alarm. The system adds a separate statement for each expressionselected for Triggered Threshold Parameter or Observed Threshold Value.

Figure 12 Threshold panel

Use the Threshold Parameter field to enter the name of the threshold attribute that triggered thealarm. This field maps to the triggered Threshold field in the Historical Fault Browser (HFB)database.

Use the Observed Threshold Value field to enter the actual value that triggered the alarm. This fieldmaps to the observedValue field in the HFB database. Use the pull-down menu to select an operatorin the Observed Threshold expression. Values include:

• = (equals the entered value)

• > (is greater than the entered value)

• < (is less than the entered value)

The query statement has the form parameter, operator, and value for both the Triggered ThresholdParameter and the Observed Threshold Value for that parameter. To build a query statement, youmay enter only the threshold parameter, or both the threshold parameter and an observed value.Multiple query statements are allowed.

HFB does not check that the observed value specified is valid for the specified parameter, sincethese vary with network element types. Once you have completed entering data, you should reviewthe query that the system has added to the Selected Retrieval Criteria List, to ensure the query isas you intended. This query statement applies only to network elements that can map a threshold

24


event to an alarm.

Criteria Sets panel

Use the Criteria Sets panel (see Criteria Sets panel) to select previously saved criteria sets to querythe HFB database. Only criteria sets that you have saved to the HFB database will appear in theCriteria Set list. This list displays the name of the criteria set, along with the number of alarm filtersin the set. Move your cursor over a criteria set in your list to display a tool tip that lists the alarm filterssaved in that set. The tool tip displays up to ten alarm filters.

Web browsers support tool tips differently. The Mozilla browser supports only one line for tool tips.The Netscape browser does not support tool tips. The Internet Explorer browser supports tool tips.

Figure 13 Criteria Sets panel

Use the checkboxes beside the list entries to either add the selected set to the Retrieval Criteria list,or to delete the selected set. Once you select a criteria set from your list and click Delete Selected,your criteria set will be removed from the HFB database without prompting you for confirmation.

Once you have added the criteria sets to your Retrieval Criteria List, you can modify the queries inthe list, retrieve alarms, generate reports, or save the modified queries under a new name.

At any time while you are logged on to the HFB application, you can save your set of retrieval criteriafor later use. For information on saving criteria sets, see Viewing historical alarms in HFB.

25


4.2.2 View Records pageThe system displays the retrieved alarm records when you click View Recordsin the SelectRetrieval Criteria page. The View Records page allows you to retrieve alarm records from theHistorical Fault Browser (HFB) database that meet the search criteria.

Each request to retrieve alarms from the database displaces the existing View Records page in themain window. The system does not open separate windows for each request.

The View Records page contains the Alarms List table that displays all of the alarm recordsretrieved from the database in groups of 25. The maximum number of alarm records retrieved fromthe database is 500. The Alarms List title bar indicates the group of alarms displayed, and the totalnumber of alarms retrieved. View other groups of alarms by selecting the corresponding page listedbelow the Alarms List. You can also scan through alarm records in consecutive groups using theNext page link.

The Alarms List displays several columns of information for each alarm (see Alarm List fields).Additional details can be viewed in the Record Details page by selecting an alarm. Refer to AlarmRecord Details page. Use of the fields varies across domains. For more information, refer to thedevice adapter documentation for your domain.

The following figures illustrate examples of View Records page generated from the HFB.

26


Figure 14 Example of View Records page (1/6)

27



28



29



30



31



Table 7 Alarm List fields

Field name Description

Alarm Code Identification number of the alarm Alarm Codeformat:

<Equip. Type> _<Alarm code on 4 digits(0#9)>_<MO Object Id on 5 digits (0#9)>where:

• Equip Type = OAM, BTS, MicroBTS, RNC,MSS, ESE, RSP , OneBTS

• Alarm code = Alarm code of the Equip.

32



Type

• MO Object Id = Object Id of the alarmedcomponent.

The Alarm Code is also named Fault Code.

For the possible alarm code values, see:

• Alcatel-Lucent 9300 W-CDMA ProductFamily - Node B Alarms Reference Guide(NN-20500–018)Alcatel-Lucent 9300 W-CDMA Product Family - RNC and MSSPOC Alarms Reference Guide(NN-20500-024).

NE ID This field displays the network element identifi-er.

NE Name This field displays the alphanumeric name ofthe network element.

Event Type This field contains the type of alarm recorded.The values are as follows:

• Communications

• Environment

• Equipment

• Processing Error

• Quality of Service

• Integrity Violation

• Operational Violation

• Physical Violation

• Security Service Or Mechanism Violation

• Time Domain Violation

Notification Id This field contains the original alarm identifiergenerated at the controller.

Full Component DN This field contains all of the details of the net-work element. See Note 2.

Subcomponent Id This field contains a subset of the informationabout the network element that generated thealarm. See Note 1.

33



Event Time This field indicates the local date and time thatan alarm was raised or cleared. Although thecursor does not change to a hand icon whenhovered above the Event time column, thiscolumn can be sorted in the same way as theother columns. A tool tip displays the UTC andtime difference when you pause your cursorover the field. See Note 3.

Details on raised and cleared times areprovided on the Alarm Record Details page.

Severity This field indicates the severity level of thealarm. The values are Critical, Major, Minor,Unknown and Warning.

Status This field indicates the status of the alarm. Thevalues are Active and Cleared.

Clear User Id This field specifies the user ID of the operatorwho cleared an alarm. The hfbmaster user IDindicates the alarm was cleared while eitherthe HFB Agent or FMBB was down. A nullentry indicates that the alarm was cleared bythe system.

Ack. Status This field indicates True or False values. ATrue value indicates that the alarm has beenacknowledged. A False value is the default foralarms that have never been acknowledged,or it indicates that the alarm has been unac-knowledged.

If the "Ack. User Id" field is not empty, and the"Ack. Status" field is False, this means that thealarm has been unacknowledged. If however,the "Ack. User Id" field is empty, and the "Ack.Status" field is False, this means that thealarm was never acknowledged.

Ack. User Id This field displays the user ID of the personthat last changed the acknowledgementstatus. Previous user IDs are overwritten when

34



this status is changed. A blank field indicatesthat the alarm was never acknowledged.

Ack Time This field displays the local time of the lastalarm acknowledgement or unacknowledge-ment event. Although the cursor does notchange to a hand icon when hovered abovethe Event time column, this column can besorted in the same way as the other columns.A tool tip displays the UTC and time differencewhen you pause your cursor over the field.

Alarm Duration The time difference between when the alarmwas raised and the corresponding clear.

Additional Text This field contains a description of the alarmcondition. See Note 1.

Probable Cause This field contains information that qualifiesthe cause of the alarm condition. Dependingon the device adaptor, the field will display analphanumeric or numeric string, a descriptionof the probable cause, or both. See Note 1.

CLFI This field contains the Common Language Fa-cility Identifier (CLFI) string received from thedevice adapter. See Note 1.

Filter Info This field contains the alarm stream manage-ment rule filter information.

For more information on the alarm streammanagement rules, see HFB input filtering.

Correlation Group Id This field identifies a group of alarms that arelinked to the same root cause.

Correlation Group Alarm Type Alarms are classified as:

• PrimaryMain, which designates the alarmroot cause of the correlation group.

• Main, which designates other alarm cause,than the primary one, of the correlationgroup.

• Symptom, which designates an alarm con-

35



sequence of a Primary or Main alarm.

Correlation Group Count Number of alarms correlated to the Primary-Main alarm.

The Correlation Group Count is displayed atthe PrimaryMain alarm row and includes:

• Main alarm count

• Symptom alarm count

Symptoms already correlated in other correla-tion groups and also correlated to this Primary-Main are included in the count.

The PrimaryMain alarm is not included in thecount (this value is only available on thePrimary Main alarm).

The CorrelationGroupCount enables to identifythe PrimaryMain alarm with the highest impacton the UTRAN system QoS.

Note 1: If the default size of this field has been increased to accommodate more than 1024characters, only the first 30 characters of the field will display in the Alarm List. To view thecomplete entry click the row number of the alarm to open the Alarm Record Details page.

Note 2: If the Distinguished Name (DN) is more than 30 characters, the Alarm List will displaythe last 30 characters, preceded by "...". Click the row number of that alarm to open the AlarmRecord Details page and view the complete entry.

Note 3: If the HFB GUI is open during a Daylight Savings Time change, you must restart yourHFB session to update the time display. When Daylight Savings Time is in effect, the timesshown on the HFB GUI and the NSP GUI may differ by one hour. HFB GUI times are Green-wich Mean Time (GMT) plus the standard time zone of the HFB GUI host.

Alarm correlation

Alarm correlation is an optional application that performs alarm grouping and findsdependencies between root causes and symptoms. The correlated alarm groups are reported tothe Alarm Manager and identified in the Correlation Alarm Type column.

• PrimaryMain, which designates the alarm root cause of the correlation group.

• Main, which designates other alarm causes, than the primary one, of the correlation root.

• Symptom, which designates an alarm consequence of a Primary or Main alarm.

36


For more information on alarm correlation, see Alcatel-Lucent 9353 Management System - UserGuide (NN-20500-032).

37


4.2.3 Alarm Record Details pageThe system displays the Record Details page (see Alarm Record Details page) in the main windowwhen you click on the row number of an alarm in the View Alarms page. The Record Details pageshows all attributes (listed in Alarm List fields) for the selected alarm.

Figure 20 Alarm Record Details page

38


4.2.4 Alarm report generationWhen you click Export Report, the system generates a report of the alarms that meet the currentlyspecified search criteria. Up to 10,000 retrieved alarms can be included in the report.

The report is produced as a text file in which the fields for each alarm are separated by tabs. All fieldsare provided for every alarm (see Alarm Report fields). If a field has no value, the two tabs thatdelimit that field are adjacent. If the last field has no value, the line will end with a tab. An end-of-linecharacter separates alarm records. All end-of-line characters and all tabs in an alarm field areconverted to spaces.

The text file can be imported into a spreadsheet application where the Alarm Report fields areconverted into column headings. Additional formatting may be necessary when viewing a report in aspreadsheet application. See Viewing historical alarms in HFB.

Table 8 Alarm Report fields

Database Column Alarm Report fields

faultcode Alarm Code

NENumber NE ID

NEUserLabel NE Name

eventType Alarm Type

notificationId Notification Id

alarmedcomponent Full Component DN

subcomponentId Subcomponent Id

eventTime Event Time

perceivedSeverity Severity

activeStatus Status

MACUserId Clear User Id

clearTime Clear Time

ackStatus Ack. Status

AAUserId Ack. User Id

ackTime Ack. Time

additionalText Additional Text

39


Database Column Alarm Report fields

probableCause Probable Cause

CLFI CLFI

filterinfo Filter Info

correlationGroupId Correlation Group ID

correlationAlarmType Correlation Alarm Type

correlationGroupCount Correlation Group Count

The following are examples of several alarms in the alarm report text file:

Ne 1561 NE1561 equipment 1 Ec:AutotestEC Ne:1561 Ec:AutotestEC:Ne:1561:2003-05-29T18:49:51 -0400 Critical Active False CCU Fail 66 - Timing Problem N1561

Ne 1562 NE1562 communications 1 Ec:AutotestEC Ne:1562 Ec:AutotestEC:Ne:1562:2003-05-29T18:49:51 -0400 Major Active False Tx AIS 1 - AIS N1562

Ne 1563 NE1563 quality of service 1 Ec:AutotestEC Ne:1563 Ec:AutotestEC:Ne:1563:2003-05-29T18:49:51 -0400 Minor Active False AU-4 Far-end background block errors thresholdcrossing 15-min 5019 N1563

The Alarm Report displays all event times in the UTC time format.

HFB query interface

The HFB query interface allows to generate alarm reports in CSV format, using theprepareReport command. The command syntax is:

prepareReport - sql <sql statement> -file <output file name> [-display <display number>][-cluster <cluster number>] [-verbose]

Note: The output file location is indicated in the command return message.

For more information, see Alcatel-Lucent 9353 Management System - WMS CommandsReference Guide (WICL) (NN-20500–030).

The following figure illustrates an example of XLS alarm report file generated usingprepareReport.

40


Figure 21 Alarm report generated via the HFB query interface

For the associated tasks, see Generating alarm reports using the HFB WICL Editor.

HFB input filtering

With the HFB input filtering feature alarms are not filtered in the HFB. The alarm stream rulemanagement filter information is added to the HFB. The filter information is included in a new"Filter info" alarm report column.

Examples of filter information values are listed below:

• Inhibit rule

• Modify to <new severity> rule

• Acknowledge rule

• Delay rule

• Threshold rule

• Toggling rule

• Application Launch rule ("Send an email rule"/"Send an SMS rule").

The following figure illustrates an example of alarm report that includes the "Filter info" reportcolumn .

41


Figure 22 Alarm report with filter information

For the associated tasks, see Implementing the HFB input filtering feature.

42


4.2.5 Archiving and retrieving historical dataYou can use the HFB database to archive and retrieve historical alarms. With the Archiving andRetrieval feature you can:

• perform archiving, retrieval and purging procedures while the HFB application is running

• archive up to the last 30 days of historical data

• retrieve up to seven days of archived historical data

• retrieve data from one day multiple times, overwriting the previous retrievals

• use the archiving and retrieval feature for disaster recovery.

When you are installing the HFB application, you have the option to configure the application to usethe archiving and retrieval feature instead of the backup and restore function in NSP for yourhistorical data.

When you query alarms from the HFB, the View Records page may display active data, as well asretrieved archived data. The archived alarm appears shaded in the View Records list, and theRecord Details page provides information on the archival of the selected record. The figure belowshows archived alarms in the alarms list.

Figure 23 Archived alarms on the View Records page

43


4.3 ProceduresThis section contains the following procedures:

• Viewing historical alarms in the HFB

• Generating alarm reports using the HFB WICL Editor

• Implementing the HFB input filtering feature

44


4.3.1 Viewing historical alarms in HFBUse this procedure to view alarms in the Historical Fault Browser. Before viewing alarms, youmust define search criteria to determine which alarms are retrieved from the alarms database.You can choose to display the results on screen or save them to a file.

Requirements

The HFB client workstation must have a supported Web browser (examples: Internet Explorer5.0 or later, Mozilla 1.4) installed.

The copying and pasting of URLs is not supported from one HFB client Web browser to another.Adding a Bookmark or Favorite for the URL of the HFB client is supported only for the main HFBpage, but not in the case of specific HFB pages. For example, a Favorite for http://<machinename>:8080/hfb is supported, but a Favorite for http://<machine name>:8080/hfb/alarmListis not supported.

Procedure

Step Action

1. From your Historical Fault Browser (HFB) graphical user interface (GUI) client workstation,enter the following web address: http://<machine name>:8080/hfb where <machinename> is the node name or IP address of the host machine on which the web server isinstalled.

2. In the security waning issued by your Web browser, click OK or Yes.This message is an SSL security warning. The message text varies depending on whichbrowser you are using; the format will be similar to one of the following:

• Security Alert: the security certificate was issued by

• Website certified by an unknown authority

• Warning - Security: do you want to accept the certificate

3. In the login window, enter your user name and password.

4. From the Select Retrieval Criteria page, click on one of the criteria tabs to start buildingyour query statement.

5. Use the window elements in the tab to define a query statement. For a detailed descriptionof the window elements and possible values, see Select Retrieval Criteria page.

You can also select from the criteria sets that you have previously saved. See Criteria Sets

45


panel.

6. Click Add to List to add the query statement to the Retrieval Criteria List.

7. You can create additional query statements in this criteria tab or select other tabs to createadditional query statements.

The system provides a default query of alarms records raised during the last two hours.

8.

If you want to Then

delete an existing query go to step 9

retrieve and display alarms based on the cur-rent query statement

go to step 12

save retrieved alarms to a file go to step 16

save the criteria set go to step 20

clear the current query statement and reset allcriteria tabs

go to step 24

9. In the Selected Retrieval Criteria area in the Main Window, click the square to the left ofthe query statement(s) in the Retrieval Criteria List that you want to delete.

10. Click either of the Delete Selected buttons to delete the query statement(s) from theRetrieval Criteria List.

11. Return to step 8.

12. (Optional) Click Count to determine how many records will match your query.

13. To retrieve alarms and display them in the View Records alarms list, click View Records.HFB will time out after 30 minutes of either idle or query time. After this time out, theHFB system remains responsive and it is recommended that you terminate and restartthe HFB UI.

14. To view the complete alarm (on the Alarm Record Details page) click the row number ofthe alarm at the far left of the View Records page.


16. Click Export Report.

46


You do not have to select View Records to generate a report.

17. Select the Save this file to disk option in the File Download window and click OK.

If, for any reason, you click Cancel to stop this operation, you must wait for a couple ofminutes before performing another action. This allows the server to process the cancelrequest and abort current processing.

18. Select the directory path and file name for the alarm report in the Save As window and clickSave. Open the file in a spreadsheet application.

Additional formatting may be necessary to view the file in a spreadsheet application. Forexample, to view a file in Microsoft Excel launch Excel and open the file using the Opencommand in the File menu. The Text Import Wizard opens. On the first screen, selectDelimited and click Next. On the second screen, select the Tab checkbox in the Delimitersarea and click Next. On the third screen, highlight the Additional Text column in the Datapreview area and then select Text in the Column data format area. Click Finish.


20. From the Selected Retrieval Criteria page in the main window, click Save Criteria to openthe Save Criteria Set page.

21. Enter a unique name in the Criteria Set Name field (maximum 40 characters).

The HFB will overwrite saved criteria sets if you do not use a unique file name for a newcriteria set. You cannot use spaces before or after an existing file name to rename a criteriaset. The HFB will not recognize spaces before or after a file name.

22. Click Save Criteria.

You can save a set of retrieval criteria at any time during your HFB session.


24. From the Selected Retrieval Criteria page in the main window, click either of the Reset toDefault buttons.

The Retrieval Criteria List displays the default Raised during the last two hours querystatement.

--End--

47


48


4.3.2 Generating alarm reports using the HFB WICL EditorTo view the alarm reports using the HFB WICL editor:

Procedure

Step Action

1. From the Network Services Platform (NSP) main window, select Configuration –> WICL ScriptEditor

The WICL Script Editor window opens.

Figure 24 WICL Script Editor window

2. Open the WISCI, then the prepareReport directories.

49


3. Select prepareReport.

For more information on prepareReport, see Alcatel-Lucent 9353 Management System - WMSCommands Reference Guide (WICL) (NN-20500-030)

4. To run prepareReport immediately, click Run now

5. To schedule the execution of prepareReport, click Schedule.

Note: The output file location is indicated in the command return message.

--End--

50


4.3.3 Implementing the HFB input filtering featureTo implement the input filtering feature:

Procedure

Step Action

1. From the Network Services Platform (NSP) main window, select Fault #> Alarm StreamRule Set.

2. To make a specific rule active, select it from the Inactive rules window and click Activate.The selected rule becomes active and appears in the Active rules window.

3. From the NSP, select Fault –> Launch Historical Fault Browser.The HFB window opens. In the HFB report window, the filter information appears for thealarms that match the criteria defined in the previously activated rule.

--End--

51


5 Historical Fault Browser AdministrationThis chapter provides information about the administration of the Historical Fault Browser (HFB)application.

For a description of how to administer the HFB, see Overview.

To set HFB database maintenance, see Procedures.

52


5.1 OverviewThis section contains the following topics:

• Administering HFB agent

• HFB Database Maintenance Program

• Application log files

• HFB database schema

• Archiving and retrieval

• Capacity planning

53


5.1.1 Administering HFB agentHFB agent administrative tasks are performed using Application Management (AM). AM is a set ofrelated software components used to manage Common Object Request Broker Architecture(CORBA) based applications. CORBA is a multi-vendor standard for object-oriented distributedcomputing.

After installation of the HFB agent, you must use AM to add and start the HFB agent instance, andconfigure its public attributes to begin the retrieval and storage of alarm events. See HFB agentattributes for a description of the attributes that must be configured.

You can also stop and remove the HFB agent using AM.

HFB agent attributes

You can view, and in many cases configure the following HFB agent attributes using the ApplicationManager:

• the FMBB subdomain of the HFB agent must match the domain name of the Fault ManagementBuilding Block (FMBB). The match is required in order for the HFB agent to connect to theCommon Object Request Broker Architecture (CORBA) server of the FMBB. (An HFB agentconnects to a single FMBB server.) The default value is Configuration Required.

• the TUMSBB subdomain of the HFB agent must match the domain name of the Topology UnifiedModelling Service Building Block (TUMSBB). The match is required in order for the HFB agent toconnect to the CORBA server of the TUMSBB. (An HFB agent connects to a single TUMSBBserver.) The default value is Configuration Required.

• the Release number, which is the release number of the HFB agent application. This attribute isread-only.

• the Logging level indicates the level of detail provided by logs for debugging purposes. The rangeof values is 1 through 5, with a default value of 3.

54


5.1.2 HFB Database Maintenance ProgramThe Historical Fault Browser (HFB) Database Maintenance Program is a required component of theHFB package. The HFB Database Maintenance Program is a set of stored procedures that allowsthe database administrator to manage the removal of old alarm event records from the database.Database maintenance parameters are configured during installation. They can be changed later,using Setting HFB database maintenance.

If alarm events occur during the hour gained or lost for Daylight Savings Time, these alarm eventrecords may not be removed from the database at the scheduled time. For example, alarm eventsthat occur during the hour lost will have a timestamp that will cause the records to be prematurelydeleted.

55


5.1.3 Application log filesThe log files for an application store the system messages for the application. System messages arerecords of application activity. You can refer to these messages when analyzing problems orexamining performance.

This section contains the following topics:

• Database log files

• HFB agent log file

• HFB GUI server log file

Database log files

General HFB log files reside in the following directory: /opt/nortel/logs/applications/hfb/db

With the exception of hfb_admin.log, the log files are created after the specific event occurs. Thedirectory contains the following files:

• hfb_admin.log contains system messages generated by the HFB Database MaintenanceProgram

• hfb_bulk_alarms.log contains system messages regarding bulk alarm inserts and updates

• hfb_bulk_nedata.log contains system messages regarding bulk network element (NE) insertsand NE updates

• hfb_purge_tables.log contains system messages regarding purging staging tables on start up

• hfb_bulk_delete.log contains system messages regarding bulk deletes

HFB agent log file

The following are typical types of system messages that go to the WMS log filealarmHistorynnnnn.log, where nnnnn is the process ID for the HFB agent instance:

• successful connection to FMBB or TUMSBB or the DB

• disconnection from FMBB or TUMSBB or the DB

• alarm insertions

• fault event updates

• network element events (updated on discovery)

• unsupported alarm records or unsupported attribute names in the alarm record

• failure to insert a record in the DB for any reason (For example, duplicates, wrong partition)

The alarmHistorynnnnn.log file resides in the following directory: /opt/nortel/logs/applications/hfb/

HFB GUI server log file

56


The HFB GUI uses the JBoss application server to maintain a client session and retrieve data fromthe database. The following two types of system messages go to the JBoss log file:

• system messages generated by the HFB GUI server (the JBoss application server)

• system messages generated by the Oracle database related to communication with the HFB GUIserver

View the log file generated by JBoss in the following directory:/opt/nortel/logs/3rd_party/java/jboss/server/default/log/hfb.log

57


5.1.4 HFB database schemaThis section contains information for database administrators about the organization of alarm datastored in the Historical Fault Browser (HFB) database. Database administrators are expected to usethe tables provided in this section for reference, and to use the HFB GUI to extract any requiredrecords from the database.

This section contains the following topics:

• Mapping to Building Block Interface Definition Language fields

• Supported database

• Supported standards

• HFB databases

• HFB database tables

Mapping to Building Block Interface Definition Language fields

The HFB database stores data provided at runtime by the Common Object Request BrokerArchitecture (CORBA) Interface Definition Language (IDL) interfaces of the following WMScomponents:

• Fault Management Building Block (FMBB)

• Topology Management Building Block (TUMSBB)

The fields in the HFB database tables have matching fields in the alarm event records delivered bythe FMBB or TUMSBB, with the following exception. The HFB database stores all integer valuesreceived from the FMBB as strings. The HFB database then uses a matching Type field created bythe HFB agent to maintain the FMBB contract definition. For an example, refer to the descriptions forthe following fields (see Alarms table):

• probableCause

• probableCauseType

The mapping of the FMBB or TUMSBB IDL attribute ID types to the equivalent fields in the HFBdatabase is shown (see FMBB or TUMSBB to HFB mapping). All attribute ID types apply to theFMBB IDL except for the neUserLabel attribute ID type which applies to the TUMSBB IDL. The X.721and X.733 standards are International Telecommunications Union (ITU) standards.

Table 9 FMBB or TUMSBB to HFB mapping

FMBB or TUMSBBattribute ID type

HFB database fieldname

HFB table name Standard

internal alarmId Alarms HFB

FMBB/TUMSBB do- domainName Alarms HFB

58





main name as enteredin AMC GUI

logrecordID logRecord Alarms X.721

managedObjectClass ClassId Alarms X.721

eventType eventType Alarms X.721

eventTime eventTime Alarms X.721

notificationIdentifier notificationId Alarms X.721

additionalText additionalText Alarms X.721

probableCause probableCause Alarms X.721

probableCauseType probableCauseType Alarms X.721

perceivedSeverity perceivedSeverity Alarms X.721

specificProblem specificProblem Alarms X.721

specificIdentifierType specProblemType Alarms X.721

trendIndication trendIndication Alarms X.721

activeStatus activeStatus Alarms X.721

unknownStatus unknownStatus Alarms X.721

alarmedcomponent alarmedcomponent Alarms X.721

equipmentType equipmentType Alarms Alcatel-Lucent internal

CLFI CLFI Alarms Alcatel-Lucent internal

alarmDisplayInfo.subcomponentId

subcomponentId Alarms Alcatel-Lucent internal

alarmDisplay-Info.neUserLabel

NEUserLabel Alarms Alcatel-Lucent internal

managedObjectIn-stance

NENumber Alarms Alcatel-Lucent internal

internal objectInstanceStrin g Alarms HFB

59





eventTime clearTime Alarms X.721

vendorSpecificMod-ule.ackTime

ackTime Alarms Alcatel-Lucent internal

internal alarmId ThresholdInfo HFB

threshold-Info.triggeredThreshold

triggeredThreshold ThresholdInfo X.721

threshold-Info.thresholdInfoType

thresholdType ThresholdInfo X.721

threshold-Info.observedValue

observedValue ThresholdInfo X.721

threshold-Info.observedValueType

observedValueType ThresholdInfo X.721

threshold-Info.indTypeChoice

indTypeChoice ThresholdInfo X.733

thresholdInfo.high high ThresholdInfo X.721

thresholdInfo.low low ThresholdInfo X.721

thresholdInfo.armTime armTime ThresholdInfo X.733

vendorSpecificMod-ule.actionRegUserName

AAUSERID Alarms Alcatel-Lucent internal

vendorSpecificMod-ule.ackStatus

ACKSTATUS Alarms Alcatel-Lucent internal

vendorSpecificMod-ule.actionRegUserName

MACUSERID Alarms Alcatel-Lucent internal

additionalKeyString alarmkeyvalue Alarms Alcatel-Lucent internal

vendorSpecificModule.FaultCodefaultcode Alarms Alcatel-Lucent internal

vendorSpecificModule.filterInfofilterinfo Alarms Alcatel-Lucent internal

60





vendorSpecificModule.CorrelationGroupIdcorrelationGroupId Alarms Alcatel-Lucent internal

vendorSpecificModule.CorrelationAlarmTypecorrelationAlarmType Alarms Alcatel-Lucent internal

vendorSpecificModule.CorrelationGroupCountcorrelationGroupCount Alarms Alcatel-Lucent internal

Supported database

Historical Fault Browser (HFB) supports Oracle Release 9.2.0.5 Relational Database ManagementSystem (RDBMS) software, Enterprise edition with the Partitioning option. The HFB applicationcommunicates with the database through the local database interface.

Supported standards

The Historical Fault Browser Relational Database Management System (RDBMS) maps to the FaultManagement Building Block (FMBB) and the Topology Unified Modelling Service Building Block(TUMSBB) contract definitions through the Common Object Request Broker Architecture (CORBA)Interface Definition Language (IDL). The CORBA IDL is based on Telecommunications ManagementNetwork (TMN) standards that support limited pseudo-Common Management Information ServiceElement (CMISE) operations.

HFB databases

The Historical Fault Browser (HFB) database defines the following data tables, which are created bythe HFB installer during installation of the HFB agent:

• two tables containing alarm event records (alarms and thresholdInfo)

• one table containing network element data (nedata)

• five tables containing information about the alarms table fields (severity, eventtype, status,trendindicationconst, probablecauseconst)

• one table to store criteria sets

The alarm_insert_staging table has the same field contents as the alarms table.

If the HFB Archiving and Retrieval feature is configured on your system, an additional user(hfbrestore) is created along with the following two tables:

• one table containing restored alarm event records (alarms)

• one table containing the partitioning information for the Retrieved Alarms table.

Additionally, the Oracle software creates by default the user_tab_partitions table which tracks thepartitions of all your tables. This table contains the required initial partition labelled ABC which shouldnot be removed. For more information on Archiving and Retrieval, see Archiving and retrieval.

61


The HFB GUI uses a database view called v_alarms which displays the contents of the currentalarms table. If the Archiving and Retrieval option is configured on your system, the view lists thecontents of the active alarms table along with the restored alarms table.

The HFB relationships among the data tables is shown (see Diagram of HFB alarm data tables).Each box in this diagram represents a data table. The items listed within each box represent thefields in each data table. The items "N,N" indicate the row mapping between the Alarms table and theother data tables, where "N" represents a numeric value. The first numeric value represents theminimum number of mapped rows. The second numeric value represents the maximum number ofmapped rows.

62


Figure 25 Diagram of HFB alarm data tables

The characteristics of the two alarm data tables represented in Diagram of HFB alarm data tables areas follows:

• Alarms table: The fields eventTime, specificProblem, probableCause, objectInstanceString,

63


classId, eventType, and alarmKeyValue together form the primary key of this table.

• ThresholdInfo table: For each row in the Alarms table, there can exist zero or one row of data inthe ThresholdInfo table. Each row of data in the ThresholdInfo table maps to an alarm event inthe Alarms table.

HFB database tables

This section provides the following information for each of the data tables in the Historical FaultBrowser (HFB) database:

• database columns (fields)

• field descriptions

• Oracle data types

Detailed information is provided for the alarm events stored in the Alarms table (see Alarms table).Threshold crossing information associated with a Quality of Service Alarm is also provided (seeThresholdInfo table).

Table 10 Alarms table

HFB database field Field description Oracle data type

futurekey used in combination with thedatasourceId field to uniquelyidentify alarms

VARCHAR2(400)

alarmId a distinct value for each alarmevent in the Alarms table

The other four data tableshave a matching field. Thefield contains a foreign key tolink data in the tables to thedistinct alarm event in theAlarms table.

VARCHAR2(40)

domainName the domain name of the HFBagent

This name must match the do-main name of the Fault Man-agement Building Block(FMBB) and Topology Man-agement (TUMSBB).

VARCHAR2(20)

logRecord contains the following informa-tion related to an alarm ac-

VARCHAR2(20)

64



knowledgment event:

• the user who acknow-ledged the alarm

• the IP address and nodename of the user's ma-chine

• the time at which user ac-knowledged the alarm

This field is empty for HFB Re-lease 2.3 because this releasedoes not support this field.

classId object class of the entity thatraised the alarm

NUMBER(9,0)

eventType type of alarm event recorded.Valid values are:

• 5002 (CommunicationAlarm)

• 5003 (EnvironmentalAlarm)

• 5004 (Equipment Alarm)

• 5010 (Processing ErrorAlarm)

• 5011 (Quality of ServiceAlarm)

NUMBER(9,0)

eventTime time that the alarm event wasrecorded in universal coordin-ated time (UTC) format

DATE

notificationId original alarm identifier gener-ated at the controller

NUMBER(10,0)

additionalText description of the alarm condi-tion

CLOB

probableCause cause of the alarm condition VARCHAR2(40

probableCause Type type of information receivedfrom the FMBB, and stored asa string in the probableCause

NUMBER(2,0)

65



field. Valid values are:

• 3 (object identifier string)

• 5 (integer)

perceivedSeverity severity level of the alarm. Val-id values are:

• 0 (Unknown. Also referredto as 'Indeterminate')

• 1 (Critical)

• 2 (Major)

• 3 (Minor)

• 4 (Warning)

• 5 (Cleared)

NUMBER(1,0)

specificProblem identifies the alarm point, andhelps connect raise alarmevents with clear alarm events

VARCHAR2(256)

specProblemType type of information receivedfrom the FMBB, and stored asa string in the specificProblemfield. Valid values are:

• 3 (global value string)

• 5 (local value integer)

NUMBER(2,0)

trendIndication severity trend of the alarm.Valid values are:

• 0 (Less Severe)

• 1 (No Change)

• 2 (More Severe)

CHAR(1)

activeStatus indicates if the alarm is nowactive or cleared. Valid valuesare:

• 0 (Cleared)

• 1 (Active)

CHAR(1)

unknownStatus indicates if there was a loss ofcommunication between the

CHAR(1)

66



FMBB and the network ele-ment. Valid values are:

• 0 (no loss of communica-tion)

• 1 (loss of communication)

equipmentType a string with information fordisplay purposes, for example,OC12, or PP160

VARCHAR2(30)

CLFI Common Language FacilityIdentifier (CLFI) string re-ceived from the Managed Ob-ject Agent (MOA)

VARCHAR2(40

subcomponentId contains display information.(For example, for SONET, thisfield can contain a string thatindicates the slot, subslot, orport type.)

VARCHAR2(256)

alarmedcomponent contains all the details thatidentify the network element

VARCHAR2(400)

NEUserLabel contains display informationconsisting of the alphanumericname of the network element.

VARCHAR2(80)

NENumber contains display informationconsisting of the network ele-ment identifier

VARCHAR2(80)

objectInstanceString formatted string for the ObjectInstance; indicates the distin-guished name of the objectthat raised the alarm. Thisformatted string begins withthe number of entries in theAttribute Value Assertion(AVA) list followed by a space.The formatted string continueswith the following data for

VARCHAR2(400)

67



each AVA entry in the AVAlist:

• unsigned long name con-verted to a string

• length of value string

• value string

• short valueType convertedto a string

A space separates each of thedata items

clearTime time of the clear event in UTCformat

resynchronization time is dis-played for alarms clearedwhile either the HFB Agent orFMBB was down

DATE

ackTime time of the alarm acknowledg-ment event

DATE

MACUSERID user ID of the operator whomanually cleared the alarm. Itis left empty if the alarm wasnot manually cleared.

user ID = hfbmaster if thealarm was cleared while eitherthe HFB Agent or FMBB wasdown

VARCHAR2(30)

AAUSERID user ID of the operator wholast acknowledged or unac-knowledged the alarm. It is leftblank if the alarm was neveracknowledged

VARCHAR2(30)

ACKSTATUS acknowledgement status ofthe alarm. The default value id0 if the alarm was never ac-knowledged

CHAR(1)

68



alarmKeyValue user definable string, if re-quired

VARCHAR2(40

NEfuturekey used in combination with thedatasourceId field to uniquelyidentify NEs

VARCHAR2(400)

datasourceId domain name of the ADKCORBA adapter

VARCHAR2(20)

faultcode identification number of thealarm Alarm Code format.

For more information, seeAlarm List fields

VARCHAR2(32)

filterinfo This field contains the alarmstream management rule filterinformation

For more information on thealarm stream managementrules, see HFB input filtering.

VARCHAR2(64)

correlationGroupId This field identifies a group ofalarms that are linked to thesame root cause.

VARCHAR2(80)

correlationAlarmType Alarms are classified as:

• PrimaryMain

• Main

• Symptom.


VARCHAR2(30)

correlationGroupCount Number of alarms correlatedto the PrimaryMain alarm.


NUMBER(5,0)

Note: The fields eventTime, specificProblem, probableCause, objectInstanceString, classId,eventType, and alarmKeyValue together form the primary key of this table.

69


Table 11 ThresholdInfo table

Field Field description Oracle data type

alarmId links data in this table to a dis-tinct alarm event in the Alarmstable

VARCHAR2(40)

triggeredThreshold name of the threshold attributethat triggered the alarm

VARCHAR2(40)

thresholdType indicates the type of informa-tion received from the FMBBand stored as a string in thetriggeredThreshold field. Validvalues are:

• null

• long integer (local form)

• string (global form)

NUMBER(2,0)

observedValue actual value that triggered thealarm

NUMBER

observedValue Type type of information receivedfrom the FMBB and stored asa string in the observedValuefield. Valid values are:

• null

• long integer (integer value)

• double (real value)

NUMBER(2,0)

indTypeChoice direction of change requiredfrom the threshold setting totrigger an alarm. Valid valuesare:

• 0 (upChoice)

• 1 (downChoice)

NUMBER(2,0)

hig maximum threshold setting forthe alarm

VARCHAR2(20)

low minimum threshold setting forthe alarm

VARCHAR2(20)

70



armTime For a counter threshold, thisfield indicates the later of thefollowing times:

• the time at which thethreshold offset was lastapplied

• the time at which thecounter was last initialized

For a gauge threshold, thisfield indicates the time atwhich the threshold was lastre-armed.

DATE

Table 12 nedata table


NEUserLabel display information consistingof the alphanumeric name ofthe network element

VARCHAR2(80)

NENumber display information consistingof the network element identifi-er

VARCHAR2(80)

objectInstanceString formatted string for the ObjectInstance; indicates the distin-guished name of the objectthat raised the alarm. Thisformatted string begins withthe number of entries in theAttribute Value Assertion(AVA) list followed by a space.The formatted string continueswith the following data foreach AVA entry in the AVAlist:

• unsigned long name con-verted to a string

• length of value string

• value string

VARCHAR2(400)

71



• short valueType convertedto a string

Note: A space separates eachof the data items.

domainName domain name of the HFBagent

VARCHAR2(20)

NEfuturekey used in combination with thedatasourceID field to uniquelyidentify NEs

VARCHAR2(400)

datasourceId domain name of the ADKCORBA adapter

VARCHAR2(20)

The five tables containing information about the alarms table fields are small (except for theprobablecauseconst table) and of fixed length. They are given next, in their entirety.

Table 13 severity table

perceivedSeverity NUM-BER(1)

perceivedSeverityNameVARCHAR2(20)

severityOrder NUMBER(1)

0 Unknown 4

1 Critical 1

2 Major 2

3 Minor 3

4 Warning 5

5 Cleared 6

Table 14 eventType table

eventType NUMBER(38) typeAcronymVARCHAR2(10)

typeName VARCHAR2(80)

5002 Comm Communication Alarm

5003 Envir Environmental Alarm

5004 Equip Equipment Alarm

5010 ProcErr Processing Error Alarm

72


eventType NUMBER(38) typeAcronymVARCHAR2(10)

typeName VARCHAR2(80)

5011 QOS Quality of Service Alarm

Table 15 Status table

activeStatus CHAR(1) statusName VARCHAR2(20)

0 Cleared

1 Active

Table 16 trendindicationconst table

trendIndication NUMBER(1) trendIndicationName VARCHAR2(20)

0 Less Severe

1 No Change

2 More Severe

Table 17 probablecauseconst table

probableCause NUMBER(5) probableCauseName VARCHAR2(80)

0 Indeterminate

1 AIS

2 Call Set Up Failure

3 Degraded Signal

4 Far End Receiver Failure

5 Framing Error

6 Loss Of Frame

7 Loss Of Pointer

8 Loss Of Signal

9 Payload Type Mismatch

10 Transmission Error

11 Remote Alarm Interface

73



12 Excessive BER

13 Path Trace Mismatch

14 Unavailable

15 Signal Label Mismatch

16 Loss Multi Frame

17 Receive Failure

18 Transmit Failure

19 Modulation Failure

20 Demodulation Failure

21 Broadcast Channel Failure

22 Connection Establishment Error

23 Invalid Message Received

24 Local Node Transmission Error

25 Remote Node Transmission Error

26 Routing Failure

51 Backplane Failure

52 Data Set Problem

53 Equipment Identifier Duplication

54 External IF DeviceProblem

55 Line Card Problem

56 Multiplexer Problem

57 NE Identifier Duplication

58 Power Problem

59 Processor Problem

60 Protection Path Failure

61 Receiver Failure

74



62 Replaceable Unit Missing

63 Replaceable Unit Type Mismatch

64 Synchronization Source Mismatch

65 Terminal Problem

66 Timing Problem

67 Transmitter Failure

68 Trunk Card Problem

69 Replaceable Unit Problem

70 Real Time Clock Failure

71 Antenna Failure

72 Battery Charging Failure

73 Disk Failure

74 Frequency Hopping Failure

75 IO Device Error

76 Loss Of Synchronization

77 Loss Of Redundancy

78 Power Supply Failure

79 Signal Quality Evaluation Failure

80 Transceiver Failure

81 protection Mechanism Failure

82 protection Resources Failure

101 Air Compressor Failure

102 Air Conditioning Failure

103 Air Dryer Failure

104 Battery Discharging

105 Battery Failure

75



106 Commercial Power Failure

107 Cooling Fan Failure

108 Engine Failure

109 Fire Detector Failure

110 Fuse Failure

111 Generator Failure

112 Low Battery Threshold

113 Pump Failure

114 Rectifier Failure

115 Rectifier High Voltage

116 Rectifier Low Voltage

117 Ventilations System Failure

118 Enclosure Door Open

119 Explosive Gas

120 Fire

121 Flood

122 High Humidity

123 High Temperature

124 High Wind

125 Ice Build Up

126 Intrusion Detection

127 Low Fuel

128 Low Humidity

129 Low Cable Pressure

130 Low Temperature

131 Low Water

76



132 Smoke

133 Toxic Gas

134 Cooling System Failure

135 External Equipment Failure

136 External Point Failure

151 Storage Capacity Problem

152 Memory Mismatch

153 Corrupt Data

154 Out Of CPU Cycles

155 SFWR Environment Problem

156 SFWR Download Failure

157 Loss Of Real Time

158 Reinitialized

159 Application Subsystem Failure

160 Configuration Or Customization Error

161 Database Inconsistency

162 File Error

163 Out Of Memory

164 Software Error

165 Time-out Expired

166 Underlaying Resource Unavailable

167 Version Mismatch

201 Bandwidth Reduced

202 Congestion

203 Excessive Error Rate

204 Excessive Response Time

77



205 Excessive Retransmission Rate

206 Reduced Logging Capability

207 System Resources Overload

5640 Enclosure Door Open

5641 Excessive Vibration

5642 Flood Detected

5643 Fire Detected

5644 Heating Or Ventilation Or Cooling System-Problem

5645 Humidity Unacceptable

5646 Leak Detected

5647 Material Supply Exhausted

5648 Pressure Unacceptable

5649 Pump Failure

5650 Receive Failure

5651 Temperature Unacceptable

5652 Loss Of Signal

5653 Loss Of Frame

5654 Framing Error

5655 Local Node Transmission Error

5656 Remote Node Transmission Error

5657 Call Establishment Error

5658 Degraded Signal

5659 Communications Subsystem Failure

5660 Communications Protocol Error

5661 lAN Error

78



5662 dTEDCE Interface Error

5663 Toxic Leak Detected

5664 Transmit Failure

5665 Unspecified Reason

5672 Response Time Excessive

5673 Queue Size Exceeded

5674 Bandwidth Reduced

5675 Retransmission Rate Excessive

5676 Threshold Crossed

5677 Performance Degraded

5678 Congestion

5679 Resource At Or Nearing Capacity

5692 Storage Capacity Problem

5693 Version Mismatch

5694 Corrupt Data

5695 CPU Cycles Limit Exceeded

5697 Software Error

5697 Software Program Error

5698 Software Program Abnormally Terminated

5699 File Error

5700 Out Of Memory

5701 Underlying Resource Unavailable

5702 Application Subsystem Failure

5703 Configuration Or Customization Error

5712 Power Problem

5713 Timing Problem

79



5714 Processor Problem

5715 Data Set Or Modem Error

5716 Multiplexer Problem

5717 Receiver Failure

5718 Transmitter Failure

5719 Output Device Error

5720 Input Device Error

5721 Input Output Device Error

5722 Equipment Malfunction

5723 Adapter Error

5732 Duplicate Information

5733 Information Missing

5734 Information Modification Detected

5735 Information Out Of Sequence

5736 Unexpected Information

5742 Denial Of Service

5743 Out Of Service

5744 Procedural Error

5752 Cable Tamper

5753 Intrusion Detection

5762 Authentication Failure

5763 Breach Of Confidentiality

5764 Non Repudiation Failure

5765 Unauthorized Access Attempt

5772 Delayed Information

5773 Key Expired

80



5774 Out Of Hours Activity

Table 18 Criteria set table


UserName The owner of the criteria set Varchar2(25)

Criteria_Name The name of the criteria set Varchar2(80)

Time The timestamp from when thecriteria set was saved to thedatabase

Date

Attribute The alarm attribute used as afilter in the query

Varchar2(30)

DisplayString The string representation ofthe query that is displayed onthe HFB GUI

Varchar(1024)

SQLString The string representation ofone query in the criteria set

Varchar(1024)

81


5.1.5 Archiving and retrievalThe active alarms table receives new alarms as they are generated from the network elements, andare stored according to the date they are generated. The alarm records are archived by date, and areexported to a file.

When you request a retrieval, the retrieved data will either be retrieved into the active alarms table orthe retrieved alarms table, depending on the date you are requesting. For example, if you request adate that falls within the range of dates stored in your active alarms table, the data is retrieved intothe active table. If you request a date that is outside the range of your active alarms table, the data isretrieved into the retrieved alarms table.

The Historical Fault Browser will also merge new information with the existing data in the database:

• If there are alarm records in the database that are not in the retrieved data, the unique records inthe database will be preserved.

• If there are alarm records in the retrieval that are not in the database, these unique records willbe added to the database.

• If there are alarm records in the database that match records in the retrieval, the retrieval recordswill overwrite the records in the database.

82


5.1.6 Capacity planningThis section contains the following topics:

• Database instance requirements

• Database capacity planning

Database instance requirements

For the Oracle database server to provide the best performance, the Historical Fault Browser (HFB)application requires a separate instance of the Oracle Relational Database Management System(RDBMS). If an existing instance supports other databases, you must create a new databaseinstance for the HFB application only.

Database capacity planning

You must make sure that enough disk space exists on the Oracle database to support the HistoricalFault Browser (HFB) configuration. HFB requires a special table space to contain the HFB databasetables.

For more information about the organization of alarm event data in the Oracle database, refer to HFBdatabase schema. Refer to the following example for support in calculating your disk spacerequirements.

1960 MB is pre-allocated at install time for the alarm records and 1280 MB is pre-allocated for alarmindexes. If the Archiving and Retrieval feature is installed on your system, and additional 440 MB ispre-allocated during installation for the restored alarm records and an additional 320 MB ispre-allocated for the restored alarm indexes.

Example

The following example shows how to derive the amount of disk space required to support an HFBdatabase.

Alarms table specifications

The alarms table has the following specifications (see Alarms table):

• The row size of the alarms table is 1Kb.

• The composite row size of the default indexes of the alarms table is 406 bytes.

In the Oracle RDBMS (Relational Database Management System), the index key of the default indexis the primary key of the table. The default index key of the alarms table is equal to the eventTime +specificProblem + probableCause + objectInstaceString + classId + eventType + alarmKeyValue.

Other specifications

83


For this example, the following additional specifications exist:

• the average entry size of one alarm is the row size of the alarms table + the row size of allindexes of the alarms table

• the average entry is approximately 1430 bytes for each alarm

Disk space calculations

The following results are calculated based on the above specifications:

• the formula to calculate the amount of disk space required for the alarms table is:

(average entry size) (number of alarm records per day) (number of days)

• in this example, the network generates 40 alarm events per second (20 raises + 20acknowledgements)

• the total amount of disk space required for the new HFB table space for a 30 day period isapproximately 71,000 MB

This is derived by multiplying 1430 bytes for an average entry by 1,728,000 for an averagenumber of alarms per day by 30 for the number of alarm days in the example, and rounding upthe resulting 70,700 MB.

• the amount of disk space required to support the other HFB tablespaces is approximately 10 GB,which includes the following table space requirements in addition to alarm record and indexspace:

— ROLLBACK (6000 MB)

— SYSTEM (250 MB)

— TEMP (4000 MB)

84


5.2 ProceduresThis section contains the following procedures:

• Setting HFB database maintenance

• Clearing domains when HFB agent is removed

85


5.2.1 Setting HFB database maintenanceUse this procedure to set new maintenance parameters for the HFB database. An initial set ofmaintenance parameters is normally set during installation.

Although you can use this procedure to inhibit maintenance activity on the database, this is notrecommended.

Procedure

Step Action

1. Log in to the WMS workstation as the root user and open a console window.

2. Configure the HFB database maintenance settings by entering:/opt/nortel/applications/hfb/current_hfb/swmgmt/bin/con figure_hfb.sh -subcomponentmaintenance

3. At the prompt, enter:set

4. Respond to the following prompt:Enter the number of days you want to keep (max 30 days):

--End--

86


5.2.2 Clearing domains when HFB agent is removedUse this procedure to clear all the alarms if an hfbagent is removed from the system for a specificdomain.

You must perform this procedure on the Sun machine on which the NSP server resides.

Procedure

Step Action

1. Connect as an Oracle user.

2. Source hfb.env by entering the following:$. /opt/nortel/config/applications/hfb/hfb.env

3. Connect to the database by entering the following:$ sqlplus hfbmaster/<password_of_hfbmaster>

4. Enter the following commands:SQL> exec hfb_clear_domain('<domainname>'); SQL> exit

--End--

87


6 Managing Oracle administrator user IDsThis section covers the management of administrator user IDs for the Oracle database. Refer toAlcatel-Lucent 9353 Management System - Security: User Configuration and Management(NN-10300-074) and Alcatel-Lucent 9353 Management System - Security: Overview (NN-10300-031)for information on managing all other users and roles.

For introductory information, see Overview.

For tasks, see Procedures.

88


6.1 OverviewIn general, all user and role mangement is performed using the Sun ONE Identity Server (IS)console.

This section covers the managment of administrator user IDs for the Oracle database. The Oracledatabase is used by the Historical Fault Browser (HFB) application.

Default Oracle user IDs and passwords are created at installation (see Default Oracle user IDs andpassword settings). It is recommended that you change the default passwords after installation. Seethe procedures:

• Changing passwords of HFB database users

• Changing the Oracle tnslsnr port password

• Changing HFB passwords

Table 19 Default Oracle user IDs and password settings

User type ID Password

HFB Oracle database sys change_on_install

system manager

dbsnmp dbsnmp

Account is locked on installa-tion of or upgrade to MIP 4.1.

outln outln

Account is locked on installa-tion of or upgrade to MIP 4.1.

hfbmaster ajdskcmogmst

hfbagent ljgamdlxgdrd

hfbgui sedaudsogkd

Listener on Oracle tnslsnr port Pqs42mK4hsr

Password rules for HFB

The following rules apply to creating passwords for hfbagent and hfbgui:

• must be from 1 to 30 characters long

• cannot contain quotation marks

89


• must be lowercase

• must begin with an alphabetic character from your database character set, and contain onlyalphanumeric characters. You are discouraged from using the following characters:

— underscore _

— dollar sign $

— pound sign #

— period .

— at symbol @

• cannot be an Oracle reserved word

See your Oracle documentation for further information.

90


6.2 ProceduresUse the following procedures for configuring and maintaining the Netscape Directory Server:

• Changing passwords of HFB database users

• Changing the Oracle tnslsnr port password

• Changing HFB passwords

91


6.2.1 Changing passwords of HFB database usersUse this procedure to change HFB database user passwords. Default passwords are created duringinstallation (see Default Oracle user IDs and password settings).

Procedure

Step Action

1. Log in to the WMS primary server as the root user ID and open a terminal window.

2. Change to the Oracle user ID by entering:su - oracle

3. Set the environment by entering:. /opt/nortel/config/applications/hfb/hfb.env

4. Log on to the database by entering the following command:sqlplus '/ as sysdba'

5. Change the oracle password by entering the following sequence of commands:alter user sys identified by <new_password>;alter user system identified by <new_password>;

6. Change the hfbmaster password by entering the following sequence of commands:alter user hfbmaster identified by <new_password>

7. Exit the database by entering:quit

--End--

92


6.2.2 Changing the Oracle tnslsnr port passwordUse this procedure to change the password for the listener on the Oracle tnslsnr port. The newpassword must conform to the restrictions and recommendations in Password rules for HFB.

You must have root user privileges to perform this procedure.

Procedure

Step Action

1. Log in to the primary server, open a terminal window and log in as the root user.

2. Enter the following:. /opt/nortel/config/applications/hfb/hfb.env

3. Enter the following:lsnrctl

The following prompt is displayed:

LSNRCTL>

4. Enter the following:change_password

The following prompt is displayed:

Old password:

5. Enter the <old password>.The following prompt is displayed:

New password:

6. Enter the <new password>.Reenter new password:

7. Enter the <new password> again.The prompt LSNRCTL> is displayed after the message indicating that the password hasbeen set successfully.

8. Enter the following:exit

You have completed the password change procedure.

93


--End--

94


6.2.3 Changing HFB passwordsUse this procedure to change the Historical Fault Browser (HFB) passwords hfbagent and hfbgui.

If you have installed the HFB agent on a secondary server, you must change the hfbagent passwordon the secondary server. Use the same password on the primary and secondary servers.

CAUTION

The password must follow certain rules; for example, it cannot startwith a number. See Password rules for HFB.

Requirements

Only the root user ID can perform this procedure.

This procedure depends on the installation package file NNhfb.pkg.

This procedure depends on the installation package file NNhfbgui.pkg.

Procedure

Step Action

1. Log in to the primary server and open a terminal window.Change the hfbagent password.

2. Change directories by entering:/opt/nortel/applications/hfb/current_hfb/swmgmt/bin/

3. Run the configuration command by entering:./configure_hfb.sh -subcomponent password

4. At the prompt, enter a new password for hfbagent.Change the hfbgui password.

5. Change directories by entering: /opt/nortel/applications/hfb/current_hfbgui/swmgmt/bin/

6. Run the configuration command by entering:./configure_hfbgui.sh -subcomponent password

95


7. At the prompt, enter a new password for hfbgui.

--End--

96


97


Wireless Service Provider SolutionsW-CDMAAlcatel-Lucent 9353 Management SystemHistorical Fault Browser

Copyright © 2002-2008 Alcatel-Lucent, All Rights Reserved

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be alteredonly by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures accessto the current issue. Any hardcopies taken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except asexpressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose theinformation only to its employees with a need to know, and shall protect the information from disclosure and dissemination to thirdparties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information containedherein. If you have received this document in error, please notify the sender and destroy it immediately.

Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks of Alcatel-Lucent, Alcateland Lucent Technologies.

Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Solaris™ and the JRE™ aretrademarks of Sun Microsystems. Oracle is a trademark of Oracle Corporation.

All other trademarks are the property of their owners.

Document number: 411-5221-210Document issue: 07.07/ENDocument status: PreliminaryProduct Release: OAM06.0Date: September 2008

Date post:	01-Dec-2015
Category:	Documents
Upload:	rookie2
View:	28 times
Download:	0 times

W-NMS Historical Fault Browser

Documents