W-NMS Historical Fault Browser

411-5221-210 Wireless Service Provider Solutions
W-CDMA
Alcatel-Lucent 9353 Management System
Historical Fault Browser

411-5221-210 07.07/EN Preliminary September 2008
Wireless Service Provider Solutions
W-CDMA
Alcatel-Lucent 9353 Management System

Document number: Document issue: Document status: Product release: Date: 411-5221-210 07.07/EN Preliminary OAM06.0 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 "write protected"; it may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to 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 as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. 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, 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 Oracle Corporation. All other trademarks are the property of their owners.
Publication history
PUBLICATION HISTORY
SYSTEM 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
Issue 07.05/EN Draft Update for DR4
July 2008
April 2008
Issue 07.03/EN Draft Update for Pre-DR4
April 2008
February 2008
Issue 07.01/EN Draft Update for V6.0 April-08 portfolio content
SYSTEM RELEASE: OAM05.2 November 2007

Issue 06.03/EN Standard
Copyright 2002-2008 Alcatel-Lucent
Publication history
ii
Update for DR5
September 2007
August 2007
Issue 06.01/EN Draft 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
Issue 05.12/EN Preliminary Document translated into Alcatel-Lucent template
February 2007
Issue 05.11/EN Preliminary Update for UA 5.0 / OAM 5.1 Customer Readiness
The Publication History information for the outdated releases has been deleted. Document creation date: November 2002.
Table of contents
iii
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
iv
6.2.2 Changing the Oracle tnslsnr port password....................................................................................................... 93 6.2.3 Changing HFB passwords..................................................................................................................................95
List of figures
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 15 - Example of View Records page (2/6)................................................................................. ............. ......... 28 Figure 16 - Example of View Records page (3/6)................................................................................. ............. ......... 29 Figure 17 - Example of View Records page (4/6)................................................................................. ............. ......... 30 Figure 18 - Example of View Records page (5/6)................................................................................. ............. ......... 31 Figure 19 - Example of View Records page (6/6)................................................................................. ............. ......... 32 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 tables
vi
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
About this publication

This publication explains what is the Historical Fault Browser, how it works and how to administer its related 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 Management System: 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 its graphical 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 the Oracle database.
Vocabulary conventions
For a definition of terms used in this document, see Alcatel-Lucent 9300 W-CDMA Product Family Terminology (NN-20500-002).
UMTS Access Network Collection Roadmap

For collection roadmap, see Alcatel-Lucent 9300 W-CDMA Product Family - Document Collection Overview and Update Summary (NN-20500-050).
New in this release

The following sections detail what is new in Alcatel-Lucent 9353 Management System - Historical Fault 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
Historical Fault Browser Operation

The Historical Fault Browser (HFB) is an optional software application that builds on the alarm management functions of the Network Services Platform (NSP). The NSP alarm management tools provide real-time alarm information for the network elements they monitor. HFB provides a database of historical alarms for trend analysis. There are instances when alarms are generated for NEs that are not fully enrolled by the system. In such cases, HFB captures the alarms but the corresponding NE information is missing. 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.1

Overview
This section provides detailed information on the following topics: Features Components System requirements Supported Web browsers HFB Agent HFB user interface
4.1.1
Features
The Historical Fault Browser (HFB) is a tool that supports stored alarm events for all managed network elements (NE). It provides a central storage and retrieval capability for network alarm events, as well as alarm event filtering and report generation capabilities. The alarm events supported are raise alarm, clear alarm, acknowledge alarm, unacknowledge alarm, manual alarm clear, and notification ID change. The HFB retrieves alarm events (raise and clear) from the network using the building block architecture. The HFB stores the alarm events in an Oracle Relational Database Management System (RDBMS). The graphical user interface (GUI) for the HFB supports the search, display, and report 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 the vendor 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 provides the following features: sophisticated filtering support report generation capability for analysis and tracking purposes
4.1.2
Components
The HFB consists of two separate component applications: the HFB Agent and the HFB GUI (see HFB architecture). The HFB Agent retrieves alarm event information from the Fault Management Building Block (FMBB) and Topology Management Building Block (TUMSBB), and stores the information 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 the database, 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 interface provided by the FMBB and TUMSBB to retrieve information from the network. This interface is based on 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 new network element (NE) to the network. The HFB is a client of the separate Oracle Relational Database Management System (RDBMS). The alarm event information stored in the database maps to the information provided by the FMBB and TUMSBB CORBA IDL interfaces. The HFB communicates with the database through the database interface.
Figure 1 HFB architecture
4.1.3
System requirements
HFB is a value added application that is deployed over the Network Services Platform (NSP). HFB is compatible with NSP and you must install NSP before installing HFB. FMBB and TUMSBB must also be installed and running before HFB can be installed. For information on the hardware and operatingfor 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 developed using 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.
10
4.1.4
Supported Web browsers
The HFB client workstation must have a supported Web browser installed. Examples are Internet Explorer 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 the page. Click OK in the Settings window, and OK in the Internet Options window to close the window.
11
4.1.5
HFB Agent
The Historical Fault Browser (HFB) Agent retrieves alarm events from the managed network and stores 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 key attributes 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 Topology Management Building Block (TUMSBB). The HFB Agent can operate only after FMBB and TUMSBB are installed and running in the network. The HFB Agent connects to the FMBB to retrieve active and new alarms on a continuing basis. The HFB Agent also connects to the Topology Management Building Block (TUMSBB) to retrieve inventory data on network elements needed for alarm events. If either the HFB Agent or FMBB goes down, a data resynchronization takes place when communication is restored. If FMBB goes down, it resynchronizes with its device adapters (DA) when it returns to service. Once this exercise is complete it sends a message to the HFB Agent announcing that the HFB Agent can now update its data. If the HFB Agent goes down, it contacts FMBB when it returns to service to obtain an up-do-date list of active alarms. In either case, any alarms that were cleared during the loss of communication will cause a discrepancy between the old list of active alarms stored by the HFB Agent and the new list of active alarms provided by FMBB. As a result, the HFB Agent will clear these alarms with the hfbmaster user ID 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 and logs them. The HFB Agent can be customized.
12
4.2
HFB user interface

Historical Fault Browser (HFB) provides users with a flexible interface with which to search for alarm data in the database. The HFB interface is a web based Java application. Users start the HFB interface by entering the required universal resource locator (URL) in the address field of their web browser. The HFB client workstation supports various Web browsers (examples: Internet Explorer 5.0 or later, Mozilla 1.4). The HFB user interface does not support the Web browser buttons for navigation. The HFB interface provides the tools for finding and viewing historical alarms. The HFB interface allows 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
13
4.2.1
Select Retrieval Criteria page
Use the Select Retrieval Criteria page (see Select Retrieval Criteria page) to define which historical alarms to retrieve. The Select Retrieval Criteria page allows you to build search criteria to retrieve required alarm records from the HFB database. HFB displays the Select Retrieval Criteria page when 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 query statements. Each tab allows you to define a query statement using a specific attribute type. For a detailed description of the attributes in each criteria tab, see: Network panel Status panel Severity panel Event Type panel Probable Cause panel
14
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 Criteria List. The criteria list is built from query statements created in the criteria tabs. The criteria are additive. The query statements are concatenated to form the search criteria. The system uses the search 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 is formed using Boolean AND and OR logical operators. See the attribute descriptions for details on how a query statement is constructed. Manage the Selected Retrieval Criteria List using Delete Selected and Reset to Default. To delete an individual query statement, select it and click Delete Selected. To clear all current query statements, click Reset to Default. This resets all panels to default values and the Retrieval Criteria List 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 is displayed along with the timestamp. You can then choose to modify or cancel your query if necessary. If the Selected Retrieval Criteria List is empty, the system will count all of the alarm records which were 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 an existing criteria set. The Save Criteria Set page opens and you can specify a unique file name and save 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. If the Selected Retrieval Criteria List is empty, the system will retrieve the first 500 alarm records in the database. Some browsers generate a security warning message when you perform an action that requires interaction with the database server. You can eliminate these messages by selecting the appropriate box in the message dialog before continuing. Click Export Report to perform the same database search as the one requested using View Records. However, the output is saved to a file and the record number is limited to 10,000. See Alarm report generation. An In Progress dialog box appears as the system retrieves your query. The Historical Fault Browser will time out after 30 minutes of either idle or query time. If your query is too time consuming, click Cancel 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
15
terminated after 30 minutes of idle or query time, the HFB system remains responsive and a manual termination and restart is recommended. For information about the mapping of the HFB database fields to equivalent fields from the Fault Management Building Block (FMBB) and Topology Management Building Block (TUMSBB), the Common Object Request Broker Architecture (CORBA) Interface Definition Language (IDL) is provided (see FMBB or TUMSBB to HFB mapping). Some fields may not apply to all domains. For more information, refer to the device adapter documentation for your domain.
Network panel
Use the Network panel (see Network panel) to add query statements to the Selected Retrieval Criteria List based on network attributes (see Search by values in the Network panel). The attributes are available from a pull down menu in the Search by field. A second pull down menu allows you to define criteria based on partial values (see Operator Values in Network panel). Text entered in the Value 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 to search. See Multiple network domain search by NE ID. Table 1 Search by values in the Network panel
16
Search by
HFB database field
Meaning
Syntax (max sizes)
NE Name (see Note 1) NEUserLabel
display information alphanumeric (80 consisting of the name characters) of the network element display information alphanumeric (80 consisting of the net- characters) work element identifier Common Language Facility Identifier (CLFI) string received from the network element alphanumeric (40 characters)
NE ID
NENumber
CLFI
CLFI
Subcomponent ID
subcomponentId
additional details alphanumeric (256 about the network ele- characters) ment that generated the alarm user ID of the operator alphanumeric (30 who manually cleared characters) the alarm user ID = hfbmaster if the alarm was cleared while either the HFB Agent or FMBB was down user ID of the last user alphanumeric (30 that performed the last characters) acknowledgement event. Note: The current release of HFB only stores the last acknowledgement event
Clear User ID
MACUSERID
Ack User ID
AAUSERID
Additional Text
additionalText
description of the alarm condition
alphanumeric (1024 characters)
Full Component DN
alarmedcomponent
display information us- alphanumeric (400 ing the distinguished characters) name (DN) to clearly
17
Search by
HFB database field
Meaning identify the network element
Syntax (max sizes)
Alarm Code
faultcode
Uniquely identifies the alarm type
Note 1: You cannot query the database using NE Name when the database contains more than 14 million alarms. Note 2: If you exceed the default sizes when you enter the values in the search panel, the HFB may not properly execute a saved query. Table 2 Operator Values in Network panel Operator Equals Does not equal Contains Does not contain Starts with Ends with Meaning is equal to the entered value (see Note) the entered value will not appear (see Note) contains the entered value the entered value will not be part of the record starts with the entered value ends with the entered value
Note: This function may not be supported if the database structure of any of the fields in Search by values in the Network panel has been changed. You can build multiple query statements using the same alarm record field, but with different operators or values: If your query string only uses the positive operators, such as Contains or Equals, the system joins these multiple query statements with OR. If your query string uses only the negative operators, Does not contain or Does not equal, the query string is joined by AND. If your query contains both positive and negative operators, the system will group the positive queries 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 from the database. You can also build multiple query statements with different alarm record fields. The system joins these multiple query statements with a logical AND operator. An alarm event must meet all of the criteria from each query statement for the system to select it from the database.
18
When you build query statements that include multiple statements with the same alarm record field and some with different fields, the system will group all criteria items for the same attribute so that they appear together. The criteria list is also sorted by positive criteria followed by negative criteria, to produce the final alarm set. See Retrieval Criteria list for an example of a retrieval criteria list sorted in 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 to selected domains. If you choose to restrict the search to selected domains (by selecting OK), the Network 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 in the search, by clicking Add All Domains. Or you can select one or more of the domains listed and
19
click Add Selected Domains. In this case, query statements are created to specify the selected domains (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 Criteria List based on alarm and acknowledgement status. The system adds a separate statement for each of the check box values (see Status check boxes). If an alarm status criteria and an acknowledgement status criteria are selected, the system queries the database for alarms with both criteria. Figure 7 Status panel
A query statement is created for each check box selected. However, the system implements the search 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 search criteria that retrieves all active or (system) cleared alarms that have been acknowledged by an operator. The Status check boxes map to the activeStatus field and the Ack. Status check boxes map to the ACKSTATUS field in the Historical Fault Browser (HFB) database. Table 3 Status check boxes Status type Alarm status Active Check box Meaning selects alarms that have not
20
Status type
Check box
Meaning been cleared
Cleared
selects all cleared alarms (cleared by the system, an operator, or the hfbmaster user ID) selects alarms cleared by an operator and alarms cleared with the hfbmaster user ID selects alarms that have been acknowledged by an operator selects alarms that have not been acknowledged by an operator
Manually Cleared
Acknowledgement status
Acknowledged
Unacknowledged
Severity panel
Use the Severity panel (see Severity panel) to add query statements to the Selected Retrieval Criteria List based on alarm severity. The system adds a separate statement for each of the check box 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 each severity selected. An alarm must have any one of the selected severity levels for the system to select it 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 Critical Meaning selects critical alarms
21
Check box Major Minor Unknown Warning
Meaning selects major alarms selects minor alarms selects alarms of unknown severity 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 selected event 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 Communications Environment Equipment Processing Error Quality of Service Integrity Violation Meaning Communication alarms Environmental alarms Equipment alarms Processing error alarms Quality of Service alarms Indication that the information may have been illegally modified, inserted or deleted
22
Check box Operational Violation
Meaning Indication that the requested service provisioning was not possible due to service unavailability, malfunction or incorrect invocation Indication that a physical resource was violated in such a way that a security attack might have occurred Indication that a security attack was detected by a security service or mechanism Indication that an event occurred at an unexpected or prohibited time
Physical Violation
Security Service Or Mechanism Violation
Time Domain Violation
Probable Cause panel

Use the Probable Cause panel (see Probable Cause panel) to build a query statement based on the probable cause of alarms. You can use only Global form text values from the M3100 standard or the Cause Names from the X.721 standard. The results are also displayed as the text value only. Refer to the Probable Cause field of the Alarm List for valid Probable Cause values. You can also enter any string 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 criteria specifying either Contains or Does not contain. An alarm must have the probable cause matching one of the values specified for the system to select it from the database. If you are using Microsoft Internet Explorer on Windows 2000 or XP for the Historical Fault Browser, you must disable the script debugging option to prevent Explorer from displaying invalid error messages. The Probable Cause values 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
23
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 date and time range, or just a start or an end date and time (see Date/Time panel elements). The system generates a time range as a single query statement. The system joins multiple date and time query statements with a logical OR operator. An alarm event must meet the criteria of at least one of the specified 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 default query statement is the last two hours before the current time on the NSP server. You can delete the default Date and Time query statement. ATTENTION If you delete the default Date and Time query statement and do not replace it, HFB will search the alarms raised in the last two hours. Whenever possible, include a Date and Time query statement in the Retrieval Criteria List.
The Date and Time fields for a raised alarm map to the eventTime field in the Historical Fault Browser (HFB) database. The Date and Time fields for a cleared alarm map to the clearTime field in the 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 Raised radio button Cleared radio button From Date field From Time field Function selection of raised alarms selection of cleared alarms entry of the start date in yyyy/mm/dd format entry of the start time in hh:mm:ss format
24
Element To Date field To Time field
Function entry of the end date in yyyy/mm/dd format 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 threshold attributes of a Quality of Service alarm. The system adds a separate statement for each expression selected 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 the alarm. 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 field maps to the observedValue field in the HFB database. Use the pull-down menu to select an operator in 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 Threshold Parameter and the Observed Threshold Value for that parameter. To build a query statement, you may 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, since these vary with network element types. Once you have completed entering data, you should review the query that the system has added to the Selected Retrieval Criteria List, to ensure the query is as you intended. This query statement applies only to network elements that can map a threshold
25
event to an alarm.
Criteria Sets panel

Use the Criteria Sets panel (see Criteria Sets panel) to select previously saved criteria sets to query the HFB database. Only criteria sets that you have saved to the HFB database will appear in the Criteria Set list. This list displays the name of the criteria set, along with the number of alarm filters in the set. Move your cursor over a criteria set in your list to display a tool tip that lists the alarm filters saved 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 in the 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 criteria for later use. For information on saving criteria sets, see Viewing historical alarms in HFB.
26
4.2.2
View Records page
The system displays the retrieved alarm records when you click View Recordsin the Select Retrieval Criteria page. The View Records page allows you to retrieve alarm records from the Historical Fault Browser (HFB) database that meet the search criteria. Each request to retrieve alarms from the database displaces the existing View Records page in the main 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 records retrieved from the database in groups of 25. The maximum number of alarm records retrieved from the database is 500. The Alarms List title bar indicates the group of alarms displayed, and the total number of alarms retrieved. View other groups of alarms by selecting the corresponding page listed below the Alarms List. You can also scan through alarm records in consecutive groups using the Next 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 Alarm Record Details page. Use of the fields varies across domains. For more information, refer to the device adapter documentation for your domain. The following figures illustrate examples of View Records page generated from the HFB.
27
Figure 14 Example of View Records page (1/6)
28
29
30
31
32
Table 7 Alarm List fields Field name Alarm Code Description Identification number of the alarm Alarm Code format: <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.
33
Field name Type
Description
MO Object Id = Object Id of the alarmed component.
The Alarm Code is also named Fault Code. For the possible alarm code values, see: Alcatel-Lucent 9300 W-CDMA Product Family - Node B Alarms Reference Guide (NN-20500018)Alcatel-Lucent 9300 WCDMA Product Family - RNC and MSS POC Alarms Reference Guide (NN-20500-024).
NE ID
This field displays the network element identifier. This field displays the alphanumeric name of the network element. 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
NE Name
Event Type
Notification Id
This field contains the original alarm identifier generated at the controller. This field contains all of the details of the network element. See Note 2. This field contains a subset of the information about the network element that generated the alarm. See Note 1.
Full Component DN
Subcomponent Id
34
Field name Event Time
Description This field indicates the local date and time that an alarm was raised or cleared. Although the cursor does not change to a hand icon when hovered above the Event time column, this column can be sorted in the same way as the other columns. A tool tip displays the UTC and time difference when you pause your cursor over the field. See Note 3. Details on raised and cleared times are provided on the Alarm Record Details page.
Severity
This field indicates the severity level of the alarm. The values are Critical, Major, Minor, Unknown and Warning. This field indicates the status of the alarm. The values are Active and Cleared. This field specifies the user ID of the operator who cleared an alarm. The hfbmaster user ID indicates the alarm was cleared while either the HFB Agent or FMBB was down. A null entry indicates that the alarm was cleared by the system. This field indicates True or False values. A True value indicates that the alarm has been acknowledged. A False value is the default for alarms that have never been acknowledged, or it indicates that the alarm has been unacknowledged. If the "Ack. User Id" field is not empty, and the "Ack. Status" field is False, this means that the alarm has been unacknowledged. If however, the "Ack. User Id" field is empty, and the "Ack. Status" field is False, this means that the alarm was never acknowledged.
Status
Clear User Id
Ack. Status
Ack. User Id
This field displays the user ID of the person that last changed the acknowledgement status. Previous user IDs are overwritten when
35
Field name
Description this status is changed. A blank field indicates that the alarm was never acknowledged.
Ack Time
This field displays the local time of the last alarm acknowledgement or unacknowledgement event. Although the cursor does not change to a hand icon when hovered above the Event time column, this column can be sorted in the same way as the other columns. A tool tip displays the UTC and time difference when you pause your cursor over the field. The time difference between when the alarm was raised and the corresponding clear. This field contains a description of the alarm condition. See Note 1. This field contains information that qualifies the cause of the alarm condition. Depending on the device adaptor, the field will display an alphanumeric or numeric string, a description of the probable cause, or both. See Note 1. This field contains the Common Language Facility Identifier (CLFI) string received from the device adapter. See Note 1. This field contains the alarm stream management rule filter information. For more information on the alarm stream management rules, see HFB input filtering.
Alarm Duration
Additional Text
Probable Cause
CLFI
Filter Info
Correlation Group Id
This field identifies a group of alarms that are linked to the same root cause. Alarms are classified as: PrimaryMain, which designates the alarm root cause of the correlation group. Main, which designates other alarm cause, than the primary one, of the correlation group. Symptom, which designates an alarm con-
Correlation Group Alarm Type
36
Field name
Description sequence of a Primary or Main alarm.
Correlation Group Count
Number of alarms correlated to the PrimaryMain alarm. The Correlation Group Count is displayed at the PrimaryMain alarm row and includes: Main alarm count Symptom alarm count
Symptoms already correlated in other correlation groups and also correlated to this PrimaryMain are included in the count. The PrimaryMain alarm is not included in the count (this value is only available on the Primary Main alarm). The CorrelationGroupCount enables to identify the PrimaryMain alarm with the highest impact on the UTRAN system QoS. Note 1: If the default size of this field has been increased to accommodate more than 1024 characters, only the first 30 characters of the field will display in the Alarm List. To view the complete 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 display the last 30 characters, preceded by "...". Click the row number of that alarm to open the Alarm Record Details page and view the complete entry. Note 3: If the HFB GUI is open during a Daylight Savings Time change, you must restart your HFB session to update the time display. When Daylight Savings Time is in effect, the times shown on the HFB GUI and the NSP GUI may differ by one hour. HFB GUI times are Greenwich 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 finds dependencies between root causes and symptoms. The correlated alarm groups are reported to the 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.
37
For more information on alarm correlation, see Alcatel-Lucent 9353 Management System - User Guide (NN-20500-032).
38
4.2.3
Alarm Record Details page
The system displays the Record Details page (see Alarm Record Details page) in the main window when you click on the row number of an alarm in the View Alarms page. The Record Details page shows all attributes (listed in Alarm List fields) for the selected alarm. Figure 20 Alarm Record Details page
39
4.2.4
Alarm report generation
When you click Export Report, the system generates a report of the alarms that meet the currently specified 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 fields are provided for every alarm (see Alarm Report fields). If a field has no value, the two tabs that delimit that field are adjacent. If the last field has no value, the line will end with a tab. An end-of-line character separates alarm records. All end-of-line characters and all tabs in an alarm field are converted to spaces. The text file can be imported into a spreadsheet application where the Alarm Report fields are converted into column headings. Additional formatting may be necessary when viewing a report in a spreadsheet application. See Viewing historical alarms in HFB. Table 8 Alarm Report fields Database Column faultcode NENumber NEUserLabel eventType notificationId alarmedcomponent subcomponentId eventTime perceivedSeverity activeStatus MACUserId clearTime ackStatus AAUserId ackTime additionalText Alarm Code NE ID NE Name Alarm Type Notification Id Full Component DN Subcomponent Id Event Time Severity Status Clear User Id Clear Time Ack. Status Ack. User Id Ack. Time Additional Text Alarm Report fields
40
Database Column probableCause CLFI filterinfo correlationGroupId correlationAlarmType correlationGroupCount
Alarm Report fields Probable Cause CLFI Filter Info Correlation Group ID Correlation Alarm Type 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 threshold crossing 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 the prepareReport 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 Commands Reference Guide (WICL) (NN-20500030). The following figure illustrates an example of XLS alarm report file generated using prepareReport.
41
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 rule management 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" report column .
42
Figure 22 Alarm report with filter information
For the associated tasks, see Implementing the HFB input filtering feature.
43
4.2.5
Archiving and retrieving historical data
You can use the HFB database to archive and retrieve historical alarms. With the Archiving and Retrieval 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 use the archiving and retrieval feature instead of the backup and restore function in NSP for your historical data. When you query alarms from the HFB, the View Records page may display active data, as well as retrieved archived data. The archived alarm appears shaded in the View Records list, and the Record Details page provides information on the archival of the selected record. The figure below shows archived alarms in the alarms list. Figure 23 Archived alarms on the View Records page
44
4.3

Procedures
This 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
45
4.3.1
Viewing historical alarms in HFB
Use this procedure to view alarms in the Historical Fault Browser. Before viewing alarms, you must 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 Explorer 5.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 HFB page, but not in the case of specific HFB pages. For example, a Favorite for http://<machine name>:8080/hfb is supported, but a Favorite for http://<machine name>:8080/hfb/alarmList is 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 <machine name> is the node name or IP address of the host machine on which the web server is installed. 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 which browser 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 building your query statement. 5. Use the window elements in the tab to define a query statement. For a detailed description of 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
46
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 create additional query statements. The system provides a default query of alarms records raised during the last two hours. 8. If you want to delete an existing query retrieve and display alarms based on the current query statement save retrieved alarms to a file save the criteria set go to step 9 go to step 12 Then
go to step 16 go to step 20
clear the current query statement and reset all go to step 24 criteria tabs
9. In the Selected Retrieval Criteria area in the Main Window, click the square to the left of the 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 the Retrieval 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, the HFB system remains responsive and it is recommended that you terminate and restart the HFB UI. 14. To view the complete alarm (on the Alarm Record Details page) click the row number of the alarm at the far left of the View Records page. 15. Return to step 8. 16. Click Export Report.
47
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 of minutes before performing another action. This allows the server to process the cancel request and abort current processing. 18. Select the directory path and file name for the alarm report in the Save As window and click Save. Open the file in a spreadsheet application. Additional formatting may be necessary to view the file in a spreadsheet application. For example, to view a file in Microsoft Excel launch Excel and open the file using the Open command in the File menu. The Text Import Wizard opens. On the first screen, select Delimited and click Next. On the second screen, select the Tab checkbox in the Delimiters area and click Next. On the third screen, highlight the Additional Text column in the Data preview area and then select Text in the Column data format area. Click Finish. 19. Return to step 8. 20. From the Selected Retrieval Criteria page in the main window, click Save Criteria to open the 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 new criteria set. You cannot use spaces before or after an existing file name to rename a criteria set. 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. 23. Return to step 8. 24. From the Selected Retrieval Criteria page in the main window, click either of the Reset to Default buttons. The Retrieval Criteria List displays the default Raised during the last two hours query statement. --End--
48
49
4.3.2
Generating alarm reports using the HFB WICL Editor
To view the alarm reports using the HFB WICL editor:
Procedure
Step Action
1. From the Network Services Platform (NSP) main window, select Configuration > WICL Script Editor The WICL Script Editor window opens. Figure 24 WICL Script Editor window
2. Open the WISCI, then the prepareReport directories.
50
3. Select prepareReport. For more information on prepareReport, see Alcatel-Lucent 9353 Management System - WMS Commands 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--
51
4.3.3
Implementing the HFB input filtering feature
To implement the input filtering feature:
Procedure
Step Action
1. From the Network Services Platform (NSP) main window, select Fault #> Alarm Stream Rule 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 the alarms that match the criteria defined in the previously activated rule. --End--
52
Historical Fault Browser Administration

This 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.
53
5.1

Overview
This section contains the following topics: Administering HFB agent HFB Database Maintenance Program Application log files HFB database schema Archiving and retrieval Capacity planning
54
5.1.1
Administering HFB agent
HFB agent administrative tasks are performed using Application Management (AM). AM is a set of related software components used to manage Common Object Request Broker Architecture (CORBA) based applications. CORBA is a multi-vendor standard for object-oriented distributed computing. After installation of the HFB agent, you must use AM to add and start the HFB agent instance, and configure its public attributes to begin the retrieval and storage of alarm events. See HFB agent attributes 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 Application Manager: the FMBB subdomain of the HFB agent must match the domain name of the Fault Management Building Block (FMBB). The match is required in order for the HFB agent to connect to the Common Object Request Broker Architecture (CORBA) server of the FMBB. (An HFB agent connects 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 Unified Modelling Service Building Block (TUMSBB). The match is required in order for the HFB agent to connect to the CORBA server of the TUMSBB. (An HFB agent connects to a single TUMSBB server.) The default value is Configuration Required. the Release number, which is the release number of the HFB agent application. This attribute is read-only. the Logging level indicates the level of detail provided by logs for debugging purposes. The range of values is 1 through 5, with a default value of 3.
55
5.1.2
HFB Database Maintenance Program
The Historical Fault Browser (HFB) Database Maintenance Program is a required component of the HFB package. The HFB Database Maintenance Program is a set of stored procedures that allows the 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 event records may not be removed from the database at the scheduled time. For example, alarm events that occur during the hour lost will have a timestamp that will cause the records to be prematurely deleted.
56
5.1.3
Application log files
The log files for an application store the system messages for the application. System messages are records of application activity. You can refer to these messages when analyzing problems or examining 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. The directory contains the following files: hfb_admin.log contains system messages generated by the HFB Database Maintenance Program 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) inserts and 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 file alarmHistorynnnnn.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
57
The HFB GUI uses the JBoss application server to maintain a client session and retrieve data from the 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 GUI server
View the log file generated by JBoss in the following directory: /opt/nortel/logs/3rd_party/java/jboss/server/default/log/hfb.log
58
5.1.4
HFB database schema
This section contains information for database administrators about the organization of alarm data stored in the Historical Fault Browser (HFB) database. Database administrators are expected to use the tables provided in this section for reference, and to use the HFB GUI to extract any required records 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 Broker Architecture (CORBA) Interface Definition Language (IDL) interfaces of the following WMS components: 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 by the FMBB or TUMSBB, with the following exception. The HFB database stores all integer values received from the FMBB as strings. The HFB database then uses a matching Type field created by the HFB agent to maintain the FMBB contract definition. For an example, refer to the descriptions for the following fields (see Alarms table): probableCause probableCauseType
The mapping of the FMBB or TUMSBB IDL attribute ID types to the equivalent fields in the HFB database is shown (see FMBB or TUMSBB to HFB mapping). All attribute ID types apply to the FMBB IDL except for the neUserLabel attribute ID type which applies to the TUMSBB IDL. The X.721 and X.733 standards are International Telecommunications Union (ITU) standards. Table 9 FMBB or TUMSBB to HFB mapping FMBB or TUMSBB attribute ID type internal FMBB/TUMSBB doHFB database field name alarmId domainName HFB table name Standard
Alarms Alarms
HFB HFB
59
FMBB or TUMSBB attribute ID type main name as entered in AMC GUI logrecordID managedObjectClass eventType eventTime notificationIdentifier additionalText probableCause probableCauseType perceivedSeverity specificProblem specificIdentifierType trendIndication activeStatus unknownStatus alarmedcomponent equipmentType CLFI alarmDisplay Info.subcomponentId alarmDisplayInfo.neUserLabel managedObjectInstance internal
HFB database field name
HFB table name
Standard
logRecord ClassId eventType eventTime notificationId additionalText probableCause probableCauseType perceivedSeverity specificProblem specProblemType trendIndication activeStatus unknownStatus alarmedcomponent equipmentType CLFI subcomponentId
Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms Alarms
X.721 X.721 X.721 X.721 X.721 X.721 X.721 X.721 X.721 X.721 X.721 X.721 X.721 X.721 X.721 Alcatel-Lucent internal Alcatel-Lucent internal Alcatel-Lucent internal
NEUserLabel
Alarms
Alcatel-Lucent internal
NENumber
Alarms
objectInstanceStrin g
Alarms
HFB
60
FMBB or TUMSBB attribute ID type eventTime vendorSpecificModule.ackTime internal
HFB database field name clearTime ackTime
HFB table name
Standard
Alarms Alarms
X.721 Alcatel-Lucent internal
alarmId
ThresholdInfo ThresholdInfo
HFB X.721
thresholdtriggeredThreshold Info.triggeredThreshol d thresholdthresholdType Info.thresholdInfoType thresholdInfo.observedValue observedValue
ThresholdInfo
X.721
ThresholdInfo
X.721
thresholdobservedValueType Info.observedValueTy pe thresholdInfo.indTypeChoice thresholdInfo.high thresholdInfo.low indTypeChoice
ThresholdInfo
X.721
ThresholdInfo
X.733
high low
ThresholdInfo ThresholdInfo ThresholdInfo Alarms
X.721 X.721 X.733 Alcatel-Lucent internal
thresholdInfo.armTime armTime vendorSpecificModule.actionRegUser Name vendorSpecificModule.ackStatus vendorSpecificModule.actionRegUser Name additionalKeyString AAUSERID
ACKSTATUS
Alarms
MACUSERID
Alarms
alarmkeyvalue
Alarms Alarms Alarms
Alcatel-Lucent internal Alcatel-Lucent internal Alcatel-Lucent internal
vendorSpecificModule.FaultCode faultcode vendorSpecificModule.filterInfo filterinfo
61
FMBB or TUMSBB attribute ID type
HFB database field name
HFB table name
Standard
vendorSpecificModule.CorrelationGroupId correlationGroupId vendorSpecificModule.CorrelationAlarmType correlationAlarmType
Alarms Alarms
Alcatel-Lucent internal Alcatel-Lucent internal Alcatel-Lucent internal
vendorSpecificModule.CorrelationGroupCount correlationGroupCount Alarms
Supported database
Historical Fault Browser (HFB) supports Oracle Release 9.2.0.5 Relational Database Management System (RDBMS) software, Enterprise edition with the Partitioning option. The HFB application communicates with the database through the local database interface.
Supported standards
The Historical Fault Browser Relational Database Management System (RDBMS) maps to the Fault Management 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 Management Network (TMN) standards that support limited pseudo-Common Management Information Service Element (CMISE) operations.
HFB databases
The Historical Fault Browser (HFB) database defines the following data tables, which are created by the 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 the partitions of all your tables. This table contains the required initial partition labelled ABC which should not be removed. For more information on Archiving and Retrieval, see Archiving and retrieval.
62
The HFB GUI uses a database view called v_alarms which displays the contents of the current alarms table. If the Archiving and Retrieval option is configured on your system, the view lists the contents 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 the fields in each data table. The items "N,N" indicate the row mapping between the Alarms table and the other data tables, where "N" represents a numeric value. The first numeric value represents the minimum number of mapped rows. The second numeric value represents the maximum number of mapped rows.
63
Figure 25 Diagram of HFB alarm data tables
The characteristics of the two alarm data tables represented in Diagram of HFB alarm data tables are as follows: Alarms table: The fields eventTime, specificProblem, probableCause, objectInstanceString,
64
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 in the ThresholdInfo table. Each row of data in the ThresholdInfo table maps to an alarm event in the Alarms table.
HFB database tables

This section provides the following information for each of the data tables in the Historical Fault Browser (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 (see ThresholdInfo table). Table 10 Alarms table HFB database field futurekey Field description used in combination with the datasourceId field to uniquely identify alarms Oracle data type VARCHAR2(400)
alarmId
a distinct value for each alarm VARCHAR2(40) event in the Alarms table The other four data tables have a matching field. The field contains a foreign key to link data in the tables to the distinct alarm event in the Alarms table.
domainName
the domain name of the HFB agent This name must match the domain name of the Fault Management Building Block (FMBB) and Topology Management (TUMSBB).
VARCHAR2(20)
logRecord
contains the following informa- VARCHAR2(20) tion related to an alarm ac-
65
HFB database field
Field description knowledgment event: the user who acknowledged the alarm the IP address and node name of the user's machine the time at which user acknowledged the alarm
Oracle data type
This field is empty for HFB Release 2.3 because this release does not support this field. classId object class of the entity that raised the alarm type of alarm event recorded. Valid values are: eventTime 5002 (Communication Alarm) 5003 (Environmental Alarm) 5004 (Equipment Alarm) 5010 (Processing Error Alarm) 5011 (Quality of Service Alarm) DATE NUMBER(9,0)
eventType
NUMBER(9,0)
time that the alarm event was recorded in universal coordinated time (UTC) format
notificationId
original alarm identifier gener- NUMBER(10,0) ated at the controller description of the alarm condi- CLOB tion cause of the alarm condition VARCHAR2(40
additionalText
probableCause probableCause Type
type of information received NUMBER(2,0) from the FMBB, and stored as a string in the probableCause
66
HFB database field
Field description field. Valid values are: 3 (object identifier string) 5 (integer)
Oracle data type
perceivedSeverity
severity level of the alarm. Val- NUMBER(1,0) id values are: 0 (Unknown. Also referred to as 'Indeterminate') 1 (Critical) 2 (Major) 3 (Minor) 4 (Warning) 5 (Cleared)
specificProblem
identifies the alarm point, and VARCHAR2(256) helps connect raise alarm events with clear alarm events type of information received NUMBER(2,0) from the FMBB, and stored as a string in the specificProblem field. Valid values are: 3 (global value string) 5 (local value integer) CHAR(1)
specProblemType
trendIndication
severity trend of the alarm. Valid values are: 0 (Less Severe) 1 (No Change) 2 (More Severe)
activeStatus
indicates if the alarm is now CHAR(1) active or cleared. Valid values are: 0 (Cleared) 1 (Active)
unknownStatus
indicates if there was a loss of CHAR(1) communication between the
67
HFB database field
Field description FMBB and the network element. Valid values are: 0 (no loss of communication) 1 (loss of communication)
Oracle data type
equipmentType
a string with information for VARCHAR2(30) display purposes, for example, OC12, or PP160 Common Language Facility VARCHAR2(40 Identifier (CLFI) string received from the Managed Object Agent (MOA) contains display information. VARCHAR2(256) (For example, for SONET, this field can contain a string that indicates the slot, subslot, or port type.) contains all the details that identify the network element VARCHAR2(400)
CLFI
subcomponentId
alarmedcomponent
NEUserLabel
contains display information VARCHAR2(80) consisting of the alphanumeric name of the network element. contains display information consisting of the network element identifier VARCHAR2(80)
NENumber
objectInstanceString
formatted string for the Object VARCHAR2(400) Instance; indicates the distinguished name of the object that raised the alarm. This formatted string begins with the number of entries in the Attribute Value Assertion (AVA) list followed by a space. The formatted string continues with the following data for
68
HFB database field
Field description each AVA entry in the AVA list: unsigned long name converted to a string length of value string value string short valueType converted to a string
Oracle data type
A space separates each of the data items clearTime time of the clear event in UTC DATE format resynchronization time is displayed for alarms cleared while either the HFB Agent or FMBB was down ackTime time of the alarm acknowledg- DATE ment event user ID of the operator who manually cleared the alarm. It is left empty if the alarm was not manually cleared. user ID = hfbmaster if the alarm was cleared while either the HFB Agent or FMBB was down AAUSERID user ID of the operator who VARCHAR2(30) last acknowledged or unacknowledged the alarm. It is left blank if the alarm was never acknowledged acknowledgement status of CHAR(1) the alarm. The default value id 0 if the alarm was never acknowledged VARCHAR2(30)
MACUSERID
ACKSTATUS
69
HFB database field alarmKeyValue
Field description user definable string, if required used in combination with the datasourceId field to uniquely identify NEs domain name of the ADK CORBA adapter identification number of the alarm Alarm Code format. For more information, see Alarm List fields
Oracle data type VARCHAR2(40
NEfuturekey
VARCHAR2(400)
datasourceId
VARCHAR2(20)
faultcode
VARCHAR2(32)
filterinfo
This field contains the alarm VARCHAR2(64) stream management rule filter information For more information on the alarm stream management rules, see HFB input filtering.
correlationGroupId
This field identifies a group of alarms that are linked to the same root cause. Alarms are classified as: PrimaryMain Main Symptom.
VARCHAR2(80)
correlationAlarmType
VARCHAR2(30)
For more information, see Alarm List fields correlationGroupCount Number of alarms correlated to the PrimaryMain alarm. For more information, see Alarm List fields Note: The fields eventTime, specificProblem, probableCause, objectInstanceString, classId, eventType, and alarmKeyValue together form the primary key of this table. NUMBER(5,0)
70
Table 11 ThresholdInfo table Field alarmId Field description Oracle data type
links data in this table to a dis- VARCHAR2(40) tinct alarm event in the Alarms table name of the threshold attribute VARCHAR2(40) that triggered the alarm indicates the type of informa- NUMBER(2,0) tion received from the FMBB and stored as a string in the triggeredThreshold field. Valid values are: null long integer (local form) string (global form)
triggeredThreshold
thresholdType
observedValue
actual value that triggered the NUMBER alarm type of information received from the FMBB and stored as a string in the observedValue field. Valid values are: null long integer (integer value) double (real value) NUMBER(2,0) NUMBER(2,0)
observedValue Type
indTypeChoice
direction of change required from the threshold setting to trigger an alarm. Valid values are: 0 (upChoice) 1 (downChoice)
hig
maximum threshold setting for VARCHAR2(20) the alarm minimum threshold setting for the alarm VARCHAR2(20)
low
71
Field armTime
Field description For a counter threshold, this field indicates the later of the following times: the time at which the threshold offset was last applied the time at which the counter was last initialized DATE
Oracle data type
For a gauge threshold, this field indicates the time at which the threshold was last re-armed. Table 12 nedata table Field NEUserLabel Field description display information consisting of the alphanumeric name of the network element Oracle data type VARCHAR2(80)
NENumber
display information consisting VARCHAR2(80) of the network element identifier formatted string for the Object VARCHAR2(400) Instance; indicates the distinguished name of the object that raised the alarm. This formatted string begins with the number of entries in the Attribute Value Assertion (AVA) list followed by a space. The formatted string continues with the following data for each AVA entry in the AVA list: unsigned long name converted to a string length of value string value string
objectInstanceString
72
Field
Field description short valueType converted to a string
Oracle data type
Note: A space separates each of the data items. domainName domain name of the HFB agent used in combination with the datasourceID field to uniquely identify NEs domain name of the ADK CORBA adapter VARCHAR2(20)
NEfuturekey
VARCHAR2(400)
datasourceId
VARCHAR2(20)
The five tables containing information about the alarms table fields are small (except for the probablecauseconst table) and of fixed length. They are given next, in their entirety. Table 13 severity table perceivedSeverity NUMBER(1) 0 1 2 3 4 5 Table 14 eventType table eventType NUMBER(38) typeAcronym VARCHAR2(10) Comm Envir Equip ProcErr typeName VARCHAR2(80) perceivedSeverityName VARCHAR2(20) Unknown Critical Major Minor Warning Cleared 4 1 2 3 5 6 severityOrder NUMBER(1)
5002 5003 5004 5010
Communication Alarm Environmental Alarm Equipment Alarm Processing Error Alarm
73
eventType NUMBER(38)
typeAcronym VARCHAR2(10) QOS
typeName VARCHAR2(80)
5011 Table 15 Status table
Quality of Service Alarm
activeStatus CHAR(1) 0 1 Table 16 trendindicationconst table trendIndication NUMBER(1) 0 1 2 Table 17 probablecauseconst table probableCause NUMBER(5) 0 1 2 3 4 5 6 7 8 9 10 11 Cleared Active
statusName VARCHAR2(20)
trendIndicationName VARCHAR2(20) Less Severe No Change More Severe
probableCauseName VARCHAR2(80) Indeterminate AIS Call Set Up Failure Degraded Signal Far End Receiver Failure Framing Error Loss Of Frame Loss Of Pointer Loss Of Signal Payload Type Mismatch Transmission Error Remote Alarm Interface
74
probableCause NUMBER(5) 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 51 52 53 54 55 56 57 58 59 60 61
probableCauseName VARCHAR2(80) Excessive BER Path Trace Mismatch Unavailable Signal Label Mismatch Loss Multi Frame Receive Failure Transmit Failure Modulation Failure Demodulation Failure Broadcast Channel Failure Connection Establishment Error Invalid Message Received Local Node Transmission Error Remote Node Transmission Error Routing Failure Backplane Failure Data Set Problem Equipment Identifier Duplication External IF DeviceProblem Line Card Problem Multiplexer Problem NE Identifier Duplication Power Problem Processor Problem Protection Path Failure Receiver Failure
75
probableCauseName VARCHAR2(80) Replaceable Unit Missing Replaceable Unit Type Mismatch Synchronization Source Mismatch Terminal Problem Timing Problem Transmitter Failure Trunk Card Problem Replaceable Unit Problem Real Time Clock Failure Antenna Failure Battery Charging Failure Disk Failure Frequency Hopping Failure IO Device Error Loss Of Synchronization Loss Of Redundancy Power Supply Failure Signal Quality Evaluation Failure Transceiver Failure protection Mechanism Failure protection Resources Failure Air Compressor Failure Air Conditioning Failure Air Dryer Failure Battery Discharging Battery Failure
76
probableCauseName VARCHAR2(80) Commercial Power Failure Cooling Fan Failure Engine Failure Fire Detector Failure Fuse Failure Generator Failure Low Battery Threshold Pump Failure Rectifier Failure Rectifier High Voltage Rectifier Low Voltage Ventilations System Failure Enclosure Door Open Explosive Gas Fire Flood High Humidity High Temperature High Wind Ice Build Up Intrusion Detection Low Fuel Low Humidity Low Cable Pressure Low Temperature Low Water
77
probableCauseName VARCHAR2(80) Smoke Toxic Gas Cooling System Failure External Equipment Failure External Point Failure Storage Capacity Problem Memory Mismatch Corrupt Data Out Of CPU Cycles SFWR Environment Problem SFWR Download Failure Loss Of Real Time Reinitialized Application Subsystem Failure Configuration Or Customization Error Database Inconsistency File Error Out Of Memory Software Error Time-out Expired Underlaying Resource Unavailable Version Mismatch Bandwidth Reduced Congestion Excessive Error Rate Excessive Response Time
78
probableCause NUMBER(5) 205 206 207 5640 5641 5642 5643 5644
probableCauseName VARCHAR2(80) Excessive Retransmission Rate Reduced Logging Capability System Resources Overload Enclosure Door Open Excessive Vibration Flood Detected Fire Detected Heating Or Ventilation Or Cooling SystemProblem Humidity Unacceptable Leak Detected Material Supply Exhausted Pressure Unacceptable Pump Failure Receive Failure Temperature Unacceptable Loss Of Signal Loss Of Frame Framing Error Local Node Transmission Error Remote Node Transmission Error Call Establishment Error Degraded Signal Communications Subsystem Failure Communications Protocol Error lAN Error
5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661
79
probableCauseName VARCHAR2(80) dTEDCE Interface Error Toxic Leak Detected Transmit Failure Unspecified Reason Response Time Excessive Queue Size Exceeded Bandwidth Reduced Retransmission Rate Excessive Threshold Crossed Performance Degraded Congestion Resource At Or Nearing Capacity Storage Capacity Problem Version Mismatch Corrupt Data CPU Cycles Limit Exceeded Software Error Software Program Error Software Program Abnormally Terminated File Error Out Of Memory Underlying Resource Unavailable Application Subsystem Failure Configuration Or Customization Error Power Problem Timing Problem
80
probableCauseName VARCHAR2(80) Processor Problem Data Set Or Modem Error Multiplexer Problem Receiver Failure Transmitter Failure Output Device Error Input Device Error Input Output Device Error Equipment Malfunction Adapter Error Duplicate Information Information Missing Information Modification Detected Information Out Of Sequence Unexpected Information Denial Of Service Out Of Service Procedural Error Cable Tamper Intrusion Detection Authentication Failure Breach Of Confidentiality Non Repudiation Failure Unauthorized Access Attempt Delayed Information Key Expired
81
probableCause NUMBER(5) 5774 Table 18 Criteria set table Field UserName Criteria_Name Time
probableCauseName VARCHAR2(80) Out Of Hours Activity
Field description The owner of the criteria set The name of the criteria set
Oracle data type Varchar2(25) Varchar2(80)
The timestamp from when the Date criteria set was saved to the database The alarm attribute used as a filter in the query The string representation of the query that is displayed on the HFB GUI The string representation of one query in the criteria set Varchar2(30)
Attribute
DisplayString
Varchar(1024)
SQLString
Varchar(1024)
82
5.1.5
Archiving and retrieval
The active alarms table receives new alarms as they are generated from the network elements, and are stored according to the date they are generated. The alarm records are archived by date, and are exported to a file. When you request a retrieval, the retrieved data will either be retrieved into the active alarms table or the retrieved alarms table, depending on the date you are requesting. For example, if you request a date that falls within the range of dates stored in your active alarms table, the data is retrieved into the active table. If you request a date that is outside the range of your active alarms table, the data is retrieved 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 in the database will be preserved. If there are alarm records in the retrieval that are not in the database, these unique records will be added to the database. If there are alarm records in the database that match records in the retrieval, the retrieval records will overwrite the records in the database.
83
5.1.6

Capacity planning
Database instance requirements Database capacity planning
This section contains the following topics:
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 database instance for the HFB application only.
Database capacity planning

You must make sure that enough disk space exists on the Oracle database to support the Historical Fault Browser (HFB) configuration. HFB requires a special table space to contain the HFB database tables. For more information about the organization of alarm event data in the Oracle database, refer to HFB database schema. Refer to the following example for support in calculating your disk space requirements. 1960 MB is pre-allocated at install time for the alarm records and 1280 MB is pre-allocated for alarm indexes. If the Archiving and Retrieval feature is installed on your system, and additional 440 MB is pre-allocated during installation for the restored alarm records and an additional 320 MB is pre-allocated for the restored alarm indexes.
Example
The following example shows how to derive the amount of disk space required to support an HFB database.
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 index is 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
84
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 all indexes 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 + 20 acknowledgements) the total amount of disk space required for the new HFB table space for a 30 day period is approximately 71,000 MB This is derived by multiplying 1430 bytes for an average entry by 1,728,000 for an average number of alarms per day by 30 for the number of alarm days in the example, and rounding up the 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 index space: ROLLBACK (6000 MB) SYSTEM (250 MB) TEMP (4000 MB)
85
5.2

Procedures
This section contains the following procedures: Setting HFB database maintenance Clearing domains when HFB agent is removed
86
5.2.1
Setting HFB database maintenance
Use this procedure to set new maintenance parameters for the HFB database. An initial set of maintenance parameters is normally set during installation. Although you can use this procedure to inhibit maintenance activity on the database, this is not recommended.
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 -subcomponent maintenance 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--
87
5.2.2
Clearing domains when HFB agent is removed
Use this procedure to clear all the alarms if an hfbagent is removed from the system for a specific domain. 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--
88
Managing Oracle administrator user IDs

This section covers the management of administrator user IDs for the Oracle database. Refer to Alcatel-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.
89
6.1
Overview
In 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 Oracle database is used by the Historical Fault Browser (HFB) application. Default Oracle user IDs and passwords are created at installation (see Default Oracle user IDs and password settings). It is recommended that you change the default passwords after installation. See the 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 HFB Oracle database sys system dbsnmp ID Password change_on_install manager dbsnmp Account is locked on installation of or upgrade to MIP 4.1. outln outln Account is locked on installation of or upgrade to MIP 4.1. hfbmaster hfbagent hfbgui Listener on Oracle tnslsnr port ajdskcmogmst ljgamdlxgdrd sedaudsogkd 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
90
must be lowercase must begin with an alphabetic character from your database character set, and contain only alphanumeric 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.
91
6.2

Procedures
Use 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
92
6.2.1
Changing passwords of HFB database users
Use this procedure to change HFB database user passwords. Default passwords are created during installation (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--
93
6.2.2
Changing the Oracle tnslsnr port password
Use this procedure to change the password for the listener on the Oracle tnslsnr port. The new password 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 has been set successfully. 8. Enter the following: exit You have completed the password change procedure.
94
--End--
95
6.2.3
Changing HFB passwords
Use 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 password on the secondary server. Use the same password on the primary and secondary servers.
CAUTION
The password must follow certain rules; for example, it cannot start with 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
96
7. At the prompt, enter a new password for hfbgui. --End--
97
Wireless Service Provider Solutions W-CDMA Alcatel-Lucent 9353 Management System Historical 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 altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to 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 as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. 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, 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 Oracle Corporation. All other trademarks are the property of their owners. Document number: Document issue: Document status: Product Release: Date: 411-5221-210 07.07/EN Preliminary OAM06.0 September 2008

W-NMS Historical Fault Browser

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

W-NMS Historical Fault Browser

Hochgeladen von

Copyright:

Verfügbare Formate

411-5221-210 Wireless Service Provider Solutions

Historical Fault Browser

Wireless Service Provider Solutions

Historical Fault Browser

SYSTEM RELEASE: OAM05.2 November 2007

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

Update for DR5

SYSTEM RELEASE: UMTS 5.1 June 2007

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

About this publication

How this document is organized

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

UMTS Access Network Collection Roadmap

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

New in this release

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

Historical Fault Browser Operation

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

Figure 1 HFB architecture

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

Supported Web browsers

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

HFB user interface

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

Select Retrieval Criteria page

Figure 2 Select Retrieval Criteria page

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

Date/Time panel Threshold panel Criteria Sets panel

411-5221-210 07.07/EN Preliminary September 2008

Copyright 2002-2008 Alcatel-Lucent

Copyright 2002-2008 Alcatel-Lucent

Historical Fault Browser

HFB database field

Syntax (max sizes)

NE Name (see Note 1) NEUserLabel

description of the alarm condition