Alcatel-Lucent GSM

Alarm Call Out User Guide

OMC Document User Guide Release B10

3BK 21217 AAAA PCZZA Ed.04

BLANK PAGE BREAK

Status Short title

RELEASED Alarm Call Out

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent.

2 / 28

3BK 21217 AAAA PCZZA Ed.04

Contents

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Filter Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Service Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.1 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 Configure the E-mail Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.3 E-mail Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.4 Printer Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACO Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 ACO Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1 Add an OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2 Remove an OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Filter and Service Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 Add a Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 Edit a Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3 Remove a Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4 Remove All Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.5 Add a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.6 Edit a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.7 Remove a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.8 Remove All Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Alarm Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Use Triggering Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Define an AS Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 Load Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 7 8 8 9 9 10 11 12 13 14 14 14 15 16 16 17 17 18 18 19 19 21 22 22 23 24 27

3BK 21217 AAAA PCZZA Ed.04

3 / 28

Tables

Tables
Table 1: Filter Parameter Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2: Service Description Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9

Table 3: Task Scenario Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Table 4: E-mail Message Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Table 5: Printer Message Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 / 28

3BK 21217 AAAA PCZZA Ed.04

Preface

Preface
Purpose
This user guide describes the Alarm Call Out feature present on the 9153 OMC-R iconbox. The guide explains the feature and provides procedures for its use and management.

Whats New

In Edition 04
New section Configure the E-mail Server (Section 1.3.2) was added.

In Edition 03
Update with the new equipment naming.

In Edition 02
Update of system title.

In Edition 01
Removed the tags in the sections. First oficial release of document for B10.

Audience Assumed Knowledge

This user guide is intended for operators of the OMC-R. You must have a basic understanding of the following: 9153 OMC-R operations and maintenance concepts Telecommunications engineering.

3BK 21217 AAAA PCZZA Ed.04

5 / 28

Preface

6 / 28

3BK 21217 AAAA PCZZA Ed.04

1 Introduction

1 Introduction
The Alarm Call Out Tool (ACO) allows the operator to manage alarms from designated OMC-Rs during nights, weekends and holidays, when not all OMC-Rs are supervised by an operator.

3BK 21217 AAAA PCZZA Ed.04

7 / 28

1 Introduction

1.1 Overview
The ACO system filters can supervize up to a maximum of five OMC-Rs. OMC-Rs can be added to or removed from the ACO system from the ACO Management window (refer to ACO Management (Section 2) ). It then sends the information to a printer and/or an operator via Short Message System (SMS)/e-mail. There is no hierarchical structure and no dedicated OMC-R that performs these services. ACO is a distributed system. This means that the ACO system can be configured in local or remote mode from any OMC-R. This is transparent to the operator. It is done via communication links based on the HTTP server on each OMC-R.

1.2 Filter Management

Creating filters is the first step in managing ACO. Filters are made out of: Filter Targets Event Type Probable Cause Severity. When creating a new filter, these four parameters must be specified. Filters Filter Targets Event Type Description Select the targets (BSS, MFS) on which the filter is applied. An event type is an occurrence in the running of the system which causes a problem, such as, an equipment shutdown. A probable cause is the cause of the problem, such as, a leak. Therefore, a probable cause is dependent on the event type selected. There are five different levels: Critical Major Minor Warning Indeterminate. Table 1: Filter Parameter Table

Probable Cause

Severity

8 / 28

3BK 21217 AAAA PCZZA Ed.04

1 Introduction

1.3 Service Management

An ACO service specifies the time of reporting and where the alarm results are sent. Each service has one filter associated with it. Service management is performed in the Service Management window. A service is made out of: Filter Timetable Alert destinations: E-mail Printing.

Services Filter Timetable Alert Destinations

Description Filters must be created before creating a service. Refer to Table 1 . Specifies day(s) and times when ACO is running. The alerts can be sent to a maximum of two e-mail addresses and/or a printer (SMS/e-mail service is for remote recipients only). Refer to E-mail Message Example (Section 1.3.3) and Printer Message Example (Section 1.3.4) to see examples of the reports that are sent.

Table 2: Service Description Table

1.3.1 Scenario
SMS/e-mail service is for remote recipients only. Certain operations require doing more than one task. The table below displays in what order certain tasks must be done. Task Create a New Alarm Filter. Task Order 1. Add a Filter (Section 2.2.1) . 2. Add a Service (Section 2.2.5) . Modify a filter name, event type, probable cause, and/or severity. Modify time, day, or alarm destination. Modify a service name. Edit a Filter (Section 2.2.2) Edit a Service (Section 2.2.6) 1. Remove a Service (Section 2.2.7) . 2. Add a Service (Section 2.2.5) .

3BK 21217 AAAA PCZZA Ed.04

9 / 28

1 Introduction

Task Enable or disable an alarm filter. Remove an alarm filter.

Task Order Edit a Service (Section 2.2.6) . 1. Remove a Service (Section 2.2.7) . 2. Remove a Filter (Section 2.2.3) .

Table 3: Task Scenario Table

1.3.2 Configure the E-mail Server

If the Email Server is not running on the same machine, perform the following steps in order to be able to send the email messages. 1. Update the /etc/hosts file, by adding the new line with the following information: < IP Address > < Email Server Name > Where: <IP Address> is the IP Address of the correspoding Email Server machine < Email Server Name > is the outgoing (SMTP) server name. For example: 10.11.12.13 smtp.alcatel-lucent.ro Save and close the hosts file. 2. Modify the /alcatel/omc3/as/tools/data/mailSms/mailSmsConfig.pf file: MAIL_SERVER_HOSTNAME=localhost MAIL_SERVER_PORT=25 EMAIL_USER_ADDR= AUTHENTICATION=NO USE_ENCRYPTION=NO LOGIN_MAIL_USER= PASSWORD_MAIL_USER= EMAIL_SMS_PROVIDER_ADDR= SMS_SUBJECT= SMS_PHONE_NUMBERS_SEPARATOR= ENCRYPTED_PASSWORD=YES (END) Replace the localhost with the <Email Server Name> For example: MAIL_SERVER_HOSTNAME=smtp.alcatel-lucent.ro Save and close the mailSmsConfig.pf file.

10 / 28

3BK 21217 AAAA PCZZA Ed.04

1 Introduction

1.3.3 E-mail Message Example

An e-mail message is limited to 160 characters; the length of an SMS message. An e-mail message contains the following information: Severity of the alarm The date and time The specific problem Equipment name. E-mail Message Example: major(2); 20021224133022.OZ; 102432,TSC-TRUNK[66]LOOP-TO-ITF[21]; BSS_101;cleared(1) Components Severity Description major (2) The number corresponds to the severity. Date and time: YYYYMMDDhhmmss.OZ or .OL Example: Year: 2002 Month: 12 Day: 24 Hour: 13 Minutes: 30 Seconds: 22 0Z: the date and time are presented in the Greenwich time zone OL: the date and time are presented in the local time zone. Specific problem Equipment name Table 4: E-mail Message Fields TSC-TRUNK, LOOP-TO-ITF BSS_101

3BK 21217 AAAA PCZZA Ed.04

11 / 28

1 Introduction

1.3.4 Printer Message Example

A printer message has a header and a body. Header: The header is the hostname of the OMC-R and the creation date and time. The fields are separated by semicolons. Body: The body contains the new alarms or the alarms whose status has just changed. The table below the example message explains the fields that appear. The fields are separated by colons. The body contains the alarms in ASCII format. Printer Message Example: host omcr15;2002/12/21 19:12; EVTTIME=20021215101822,OZ FRDNAME=BSS_101 SEV=major(2) EVTTYPE=equipmentAlarm PBCAUSE=ALC-equipmentUnderTest SPECPB=102432,TSC-TRUNK[66]LOOP-TO-ITF[21] CLRSTS=cleared(1) CLRTIME=20021215101825.OZ REPCOUNT=MONITOR=((AvailabilityStatus,), AdministrativeState,unlocked), (OperationalState,enabled), (AlarmStatus,activeReportable_Major), (UserLabel,BSS_101)); Field EVTTIME FRDNAME SEV EVTTYPE PBCAUSE SPECPB CLRSTS CLRTIME REPCOUNT MONITOR Description Event time Equipment name Severity Event type Probable cause Specific problem Whether the alarm is cleared or not. The time the alarm was cleared. The number of times the alarm has occurred. The equipment and the state of the equipment.

Table 5: Printer Message Fields Note: The date and time format for e-mail and printer messages is the same: YYYYMMDDhhmmss.0Z

12 / 28

3BK 21217 AAAA PCZZA Ed.04

2 ACO Management

2 ACO Management
This chapter explains how to create, modify and remove filters and services.

3BK 21217 AAAA PCZZA Ed.04

13 / 28

2 ACO Management

2.1 ACO Management Window

From the 9153 OMC-R Icon Box, click on the [ ACO Management ] icon (refer to 9153 OMC-R Getting Started ). The ACO Management window opens. This window lets you add and remove OMC-Rs from the list of configurable OMC-Rs.

2.1.1 Add an OMC-R

To add an OMC-R: 1. In the ACO Management window, click on [ Add OMC ] . The Add OMC window opens. 2. Enter the hostname or IP address of the OMC-R to be added. 3. Click on [ Add ] . A confirmation window opens, and the OMC-R is added to the list of configurable OMC-Rs.

2.1.2 Remove an OMC-R

To remove an OMC-R: 1. In the ACO Management window, click on [ Remove OMC ] . The Remove OMC window opens. 2. Select an OMC-R, and click on [ Remove ] . A confirmation window opens, and the OMC-R is removed from the list of configurable OMC-Rs.

14 / 28

3BK 21217 AAAA PCZZA Ed.04

2 ACO Management

2.2 Filter and Service Management Window

After you select an OMC-R to configure in the ACO Management window, the Filter and Service Management window opens. From this window you can access the: Filter Management Window Service Management Window. Managing alarm filters is done in the Filter Management window. In this window you can: View existing filters Add a filter Edit a filter Remove a filter Remove all filters. Managing services in done in the Service Management window. Each service is for a specific period each week. You can set up a service for immediate use or for future use. Use this window to: View existing services Add a service Edit a service Remove a service Remove all services.

3BK 21217 AAAA PCZZA Ed.04

15 / 28

2 ACO Management

2.2.1 Add a Filter

Naming Conventions: A filter name is made up of alphanumeric characters (a-z, 0 - 9) and the underscore symbol ( _ ). The filter name is case sensitive. The maximum number of characters is 30. Tip: Selecting the * , selects all values in a field. Procedure: To add a filter: 1. In the Filter Management window, click on [ Add ] . The Add a Filter window opens. 2. Enter the name of the new filter in the Filter Name box. 3. Select the Filter Targets 4. Select the Event Type The Probable Cause field reloads automatically based on the event type(s) selected. 5. Select the Probable Cause 6. Select the Severity . 7. Select Ignore the acknowledged alarms from the Options field, if required. 8. Click on [ Apply ] . A confirmation window opens, and the new filter is activated within 30 seconds. Next Step: Click on [ Back ] to return to the Filter Management window, or go to Add a Service (Section 2.2.5) to set the time, days, and destination of the filter.

2.2.2 Edit a Filter

To edit a filter: 1. In the Filter Management window, select a filter from the Filter drop-down menu. The name of the selected filter appears in the Filter field. 2. Click on [ Edit ] . The Edit a Filter window opens. 3. Modify the parameters as required. 4. Click on [ Update ] . A confirmation window opens and the filter parameters are updated. 5. Click on [ Back ] to return to the Filter Management window.

16 / 28

3BK 21217 AAAA PCZZA Ed.04

2 ACO Management

2.2.3 Remove a Filter

Prerequisite: Before removing a filter, you must remove the associated service. Complete the task Remove a Service (Section 2.2.7) first. Procedure: To remove a filter: 1. In the Filter Management window, select a filter from the Filter drop-down menu. The name of the selected filter appears in the Filter field. 2. Click on [ Remove ] . A confirmation window opens and the filter is removed. 3. Click on [ Back ] to return to the Filter Management window.

2.2.4 Remove All Filters

Prerequisite: Before removing all filters, you must remove the associated service. Complete the task Remove a Service (Section 2.2.7) first. Procedure : To remove all filters: 1. In the Filter Management window, click on [ Remove All ] . A confirmation window opens. 2. Click on [ Apply ] to remove all filters. 3. Click on [ Back ] to return to the Filter Management window.

3BK 21217 AAAA PCZZA Ed.04

17 / 28

2 ACO Management

2.2.5 Add a Service

Naming Conventions: A name can be made up of alphanumeric characters (a-z, 0-9) and the underscore symbol ( _ ). The service name is case sensitive. The maximum number of characters is 30. Prerequisite: Before adding a service, there must be existing filters in the Filter Management Filter List. Complete the task Add a Filter (Section 2.2.1) before adding a service. Procedure: To add a service: 1. In the Service Management window, click on [ Add ] . The Add a Service window opens. 2. Enter the name of the new service in the Service Name field. 3. Select enabled or disabled from the Application drop-down menu. 4. Select a filter from the Filter drop-down menu. 5. Give the maximum number of alarms that can be sent ("-1" means no limit). 6. Select a printer from the Printer drop-down menu, and/or enter an e-mail address in the first Email Address field. You can add a second e-mail address in the second Email Address field (optional). 7. Select the days the service is performed in the Time Table field. 8. Enter a period of time for each selected day. 9. Click on [ Apply ] . A confirmation window opens and the service is added. 10. Click on [ Back ] to return to the Service Management window.

2.2.6 Edit a Service

To edit a service: 1. In the Service Management window, select a service from the Service drop-down menu. The name of the selected service appears in the Service Name field. 2. Click on [ Edit ] . The Edit a Service window opens. 3. Modify the parameters as required. 4. Click on [ Update ] . A confirmation window opens and the service is updated. 5. Click on [ Back ] to return to the Service Management window.

18 / 28

3BK 21217 AAAA PCZZA Ed.04

2 ACO Management

2.2.7 Remove a Service

To remove a service: 1. In the Service Management window, select a service from the Service drop-down menu. The name of the selected service appears in the Service Name field. 2. Click on [ Remove ] . A confirmation window opens and the selected service is removed. 3. Click on [ Back ] to return to the Service Management window.

2.2.8 Remove All Services

To remove all services: 1. In the Service Management window, click on [ Remove All ] . A confirmation window opens. 2. Click on [ Apply ] to remove all services. 3. Click on [ Back ] to return to the Service Management window.

3BK 21217 AAAA PCZZA Ed.04

19 / 28

2 ACO Management

20 / 28

3BK 21217 AAAA PCZZA Ed.04

3 Alarm Management

3 Alarm Management
This chapter describes: The scripts triggering server How to filter the alarms that match a trigger condition How to register / unregister a service.

3BK 21217 AAAA PCZZA Ed.04

21 / 28

3 Alarm Management

3.1 Alarm Management Overview

The current service offers the possibility to launch a script when an alarm is raised and matches the specified conditions. The script receives the alarms with its attributes as argument. The service is based on the use of: the AS script triggering functionality, used in navigation mode, which is in charge of launching a navigation message with the alarm attributes an new OMC-R component called Script Triggering Server. The AS navigates to this server. The use of the service is composed of the following: a script, which receives an alarm as argument, defined and stored in a dedicated location a service (with a label), associated to the script. This is done with the registration service of the Script Triggering Server. an AS trigger configured to navigate to the service.

3.2 Scripts
The scripts must be located in /alcatel/var/share/sts/scripts_db. They have as argument the alarm with the attributes. The format of the argument is described in the document Format of the argument for the Current Alarm Script Triggering facility , which uses as a base the document: 9153 OMC-R Alarm and State Change Export Interface 3BK 09829 HAAA PBZZA . Three sample scripts are provided in /alcatel/omc3/sts/sample: stssmp_file.pl that store the alarms in a file, given as argument of the script stssmp_mail.pl that send a mail with the alarms that match a trigger condition stssmp_both.pl that perform both actions described above.

22 / 28

3BK 21217 AAAA PCZZA Ed.04

3 Alarm Management

3.3 Use Triggering Scripts

The Scripts Triggering Server is in charge of executing the scripts when an alarm matches the alarm filter in the trigger definition, and transmitting the alarms content to the scripts. The functions offered by the Scripts Triggering Server are the following: Register a service Display the existing service(s) Unregister a service. Register a Service:Enter the following commands to register a service: axadmin@host$ cd /alcatel/omc3/sts/script axadmin@host$ ./stssrv_reg.pl <service_name> <script_name> <navigation_label> where: <service_name> is the name of the service that will be registered <script_name> is the name of the trigger script located in the /alcatel/var/share/sts/scripts_db directory <navigation_label> is a unique label identified for this service used by AS to recognize the service during the definition of the AS trigger. Display the Service(s): Perform the following commands to display all services: axadmin@host$ cd /alcatel/omc3/sts/script axadmin@host$ ./stssrv_disp.pl When you register (unregister) a service, it is good to check with this script, if this service is added (removed) in (from) the current services list. Unregister a Service: Perform the following commands to unregister a service: axadmin@host$ cd /alcatel/omc3/sts/script axadmin@host$ ./stssrv_unreg.pl <service_name>

3BK 21217 AAAA PCZZA Ed.04

23 / 28

3 Alarm Management

3.4 Define an AS Trigger

1. From the 9153 OMC-R iconbox, click on [ AS:Current Alarms ] icon. The AS Current USM (0): Counter Summary window appears:

Figure 1: AS Summary 2. In the window above, follow the menu path: Option -> Trigger List -> <hostname>0 3. The AS Current USM (0): Trigger List <hostname>0 window appears:

Figure 2: AS Trigger List to create a new trigger definition, follow the menu path: Trigger -> New

24 / 28

3BK 21217 AAAA PCZZA Ed.04

3 Alarm Management

4. The Trigger Identification window appears:

Figure 3: Trigger Definition Select the Definition from the left window, then on the right window: type the Trigger Name click on the first [ Do ] button select Navigate To select the label previously defined at registering a service (e.g. trigger_fc ) select All Alarms Attributes select on incoming alarm(s) click on the second [ Do ] button select Navigate To

3BK 21217 AAAA PCZZA Ed.04

25 / 28

3 Alarm Management

select the label previously defined at registering a service (e.g. trigger_fc ) select All Alarms Attributes select on outgoing alarm(s) When finished with the Trigger definition, click on [ Save... ] button. To trigger the alarms, select Basic from the left window. An example is given below:

Figure 4: Trigger Basic

26 / 28

3BK 21217 AAAA PCZZA Ed.04

3 Alarm Management

Click on [ Apply ] button to activate the trigger script.

3.5 Load Limits

The script must not disturb the global performance of the OMC-R The following limitations must not be exceeded: CPU percentage used by the script, directly and indirectly, must be limited to 4% trigger alarms per hour: 50 script running duration: maximum 10 seconds numbers of triggers threshold crossing: 1.

3BK 21217 AAAA PCZZA Ed.04

27 / 28

3 Alarm Management

BLANK PAGE BREAK

28 / 28

3BK 21217 AAAA PCZZA Ed.04