format of current alarm script triggering ed01.pdf

Format of the argument for the Current Alarm Script Triggering facility - B8ED 01 RELEASED

Evolium 2379H1RE.WW625/02/2004 3BK 29379 HAAA PBZZA 1/1

All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

Format of the argumentfor the Current Alarm Script Triggering facility

- Release B8 onwards -



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

SYSTEM FUNCTIONAL BLOCKS

TABLE OF CONTENTS

1. INTRODUCTION.................................................................................................... 31.1 Scope of the document ................................................................................. 31.2 Convention and notations............................................................................. 3

2. DESCRIPTION OF THE FORMAT ........................................................................ 4

3. DESCRIPTION OF THE CONCERNED PARAMETERS....................................... 5

4. ACRONYMS .......................................................................................................... 6

5. APPENDIX A: OID VERSUS STRING VALUE FOR PBCAUSE........................... 7

6. APPENDIX B: SHORT DESCRIPTION OF EXCLUDED PARAMETERS........... 12

01 040225 First issue O&M System TD/O&M/OMC3 SpecED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

LIST OF FIGURES AND TABLES

Table 1: Differences between Argument and AASCE values for parameters ........................ 5Table 2: OID versus string value for PBCAUSE.................................................................. 11Table 3: Short description of excluded parameters (informal) ............................................. 12 HISTORY

Ed. 01 (25/02/2004): Creation

REFERENCED DOCUMENTS

Standards

[X.721] Information Technology - Open Systems Interconnection Structure ofManagement Information - Part 2: Definition of ManagementInformationCCITT Recommendation X.721 (ISO/IEC 10165-2); 1991 with thetechnical Corrigendum 1,1994

[X.733] Information Technology - Open Systems Interconnection - SystemsManagement:Alarm Reporting FunctionCCITT Rec. X.733 (ISO/IEC 10164-4), 1992

[M.3100] Maintenance: Telecommunications Management Network - GenericNetwork Information Model;CCITT Recommendation M.3100, July 1995

[GSM 12.11] Digital cellular telecommunications system (Phase 2+);Fault management of the Base Station System (BSS)GSM 12.11 version 6.1.0, TS 101 251, October 1998

Alcatel Document[AASCE] A1353-RA Alarm and State Change Export Interface

For Release B8: 3BK 09829 HAAA PBZZA



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

1. INTRODUCTION

1.1 Scope of the documentThis document specifies the format of the argument for the Current Alarm Script Triggeringfacility.It uses as a base the document that specifies the A1353-RA Alarm and State ChangeExport (AASCE) Interface, i.e. [AASCE].Some parts of the argument are recommended to be out of the scope ofthe Current Alarm Script Triggering facility and, therefore, are notdetailed in this document. These parts are highlighted hereafterusing courier font.

1.2 Convention and notationsThe following conventions are used:

Item MeaningCourier font Parts that are recommended to be

out of the scope of the CurrentAlarm Script Triggering facility(see above)

references a part (called a production)whose semantics and syntax are describedseparately.

| indicates that the form can be either the onereferenced by (exclusive) or theone referenced by where and denote either productionnames or particular constant parts.

[...]+ delimits a part that may be present once ormore times.



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

2. DESCRIPTION OF THE FORMATThe argument for the Current Alarm Script Triggering facility corresponds to one alarm.It is of the form:

,,;in which:- is equal to the following string:

where LNPS stands for List of Navigation Parameter Set.

- identifies the requested service.- denotes a list of parameters with their value.

It is of the form:[]+

in which: is of the following form:

=""This syntax allows to deal with a given parameter irrespective of the order in whichthe parameter appears in the list and irrespective of whether the parameter isactually present or not (it is absent when the corresponding parameter is notsignificant).N.B.: It is recommended not to rely upon the order in which

the parameter clauses are listed. is equal to the character :

N.B.: Actually, there could also be one or several non-printable characters following the : (like acarriage return or a Line Feed). The client scriptshall be robust enough so as to allow such extracharacters.



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

3. DESCRIPTION OF THE CONCERNED PARAMETERSThe parameters that can be managed through the Current Alarm Script Triggering facilityare the same as those that apply for Current Alarms at the AASCE interface (see section3.1.1 of [AASCE]).N.B.: Appendix B gives an informal description of the parameters

that can appear as argument but that are proposed to be outof the scope of the Current Alarm Script Triggering facility.

The values for a given parameter are the same as the values of that parameter at theAASCE interface, except for a number of peculiarities indicated in the following table:

Parameter Argument value AASCE valueADDINFO 1.3.12.2.1006.53.1.2.0.5.1000 alcatelAdditionalInformation

1.3.12.2.1006.53.1.2.0.5.1001 urlAddressOnAlarmDictionary1.3.12.2.1006.53.1.2.0.5.1002 reservedForTest1 significant

EVTTYPE 2.9.3.2.10.2 communicationAlarm2.9.3.2.10.3 environmentalAlarm2.9.3.2.10.4 equipmentAlarm2.9.3.2.10.10 processingErrorAlarm2.9.3.2.10.11 qualityofServiceAlarm

PBCAUSE The correspondance between the OID value (used in theargument) and the String value (used at the AASCE interface) isdefined in the following AS Configuration file defined by Alcatel:

/alcatel/omc3/as/conf/repository/locale/C.ISO-8859-1/probableCausesN.B.: Only the standard ProbableCause values are allowed.See Appendix A for more information.

SPECPB In the Argument value, for each Specific Problem, only thecorresponding integer value is indicated whereas, at the AASCEinterface, it is preceded with the name of the corresponding alarmin the associated alarm dictionary thanks to a dedicated ASConfiguration file, namely:

/alcatel/var/share/as/specificProblemsPlease note however that taking advantage of this file is highlydiscouraged, notably because it is a living file that might bechanged without noticing external clients since it is not part of anyexternal specification (on purpose). If a client decides to use it, anyproblem caused by this usage is placed under the responsability ofthe client.

Table 1: Differences between Argument and AASCE values for parameters



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

4. ACRONYMSAASCE A1353-RA Alarm and State Change ExportAS Alarm SurveillanceFDN Full Distinguished NameLNPS List of Navigation Parameter SetOID Object Identifier Description



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

5. APPENDIX A: OID VERSUS STRING VALUE FOR PBCAUSEThe following table indicates the correspondance between the OID value (used in theargument) and the String value (used at the AASCE interface) of the PBCAUSE parameter.

Argument value AASCE value[X.721] ProbableCause values

2.9.3.2.0.0.1 X721-adapterError2.9.3.2.0.0.2 X721-applicationSubsystemFailure2.9.3.2.0.0.3 X721-bandwidthReduced2.9.3.2.0.0.4 X721-callEstablishmentError2.9.3.2.0.0.5 X721-communicationsProtocolError2.9.3.2.0.0.6 X721-communicationsSubsystemFailure2.9.3.2.0.0.7 X721-configurationOrCustomizationError2.9.3.2.0.0.8 X721-congestion2.9.3.2.0.0.9 X721-corruptData2.9.3.2.0.0.10 X721-cpuCyclesLimitExceeded2.9.3.2.0.0.11 X721-dataSetOrModemError2.9.3.2.0.0.12 X721-degradedSignal2.9.3.2.0.0.13 X721-dTE-DCEInterfaceError2.9.3.2.0.0.14 X721-enclosureDoorOpen2.9.3.2.0.0.15 X721-equipmentMalfunction2.9.3.2.0.0.16 X721-excessiveVibration2.9.3.2.0.0.17 X721-fileError2.9.3.2.0.0.18 X721-fireDetected2.9.3.2.0.0.19 X721-floodDetected2.9.3.2.0.0.20 X721-framingError2.9.3.2.0.0.21 X721-heatingOrVentilationOrCoolingSystemProblem2.9.3.2.0.0.22 X721-humidityUnacceptable2.9.3.2.0.0.23 X721-inputOutputDeviceError2.9.3.2.0.0.24 X721-inputDeviceError2.9.3.2.0.0.25 X721-lANError2.9.3.2.0.0.26 X721-leakDetected2.9.3.2.0.0.27 X721-localNodeTransmissionError2.9.3.2.0.0.28 X721-lossOfFrame2.9.3.2.0.0.29 X721-lossOfSignal2.9.3.2.0.0.30 X721-materialSupplyExhausted2.9.3.2.0.0.31 X721-multiplexerProblem2.9.3.2.0.0.32 X721-outOfMemory2.9.3.2.0.0.33 X721-ouputDeviceError2.9.3.2.0.0.34 X721-performanceDegraded2.9.3.2.0.0.35 X721-powerProblem2.9.3.2.0.0.36 X721-pressureUnacceptable2.9.3.2.0.0.37 X721-processorProblem2.9.3.2.0.0.38 X721-pumpFailure2.9.3.2.0.0.39 X721-queueSizeExceeded2.9.3.2.0.0.40 X721-receiveFailure2.9.3.2.0.0.41 X721-receiverFailure2.9.3.2.0.0.42 X721-remoteNodeTransmissionError



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

Argument value AASCE value2.9.3.2.0.0.43 X721-resourceAtOrNearingCapacity2.9.3.2.0.0.44 X721-responseTimeExcessive2.9.3.2.0.0.45 X721-retransmissionRateExcessive2.9.3.2.0.0.46 X721-softwareError2.9.3.2.0.0.47 X721-softwareProgramAbnormallyTerminated2.9.3.2.0.0.48 X721-softwareProgramError2.9.3.2.0.0.49 X721-storageCapacityProblem2.9.3.2.0.0.50 X721-temperatureUnacceptable2.9.3.2.0.0.51 X721-thresholdCrossed2.9.3.2.0.0.52 X721-timingProblem2.9.3.2.0.0.53 X721-toxicLeakDetected2.9.3.2.0.0.54 X721-transmitFailure2.9.3.2.0.0.55 X721-transmitterFailure2.9.3.2.0.0.56 X721-underlyingResourceUnavailable2.9.3.2.0.0.57 X721-versionMismatch

[M.3100] ProbableCause values0 M3100-indeterminate1 M3100-aIS2 M3100-callSetUpFailure3 M3100-degradedSignal4 M3100-farEndReceiverFailure5 M3100-framingError6 M3100-lossOfFrame7 M3100-lossOfPointer8 M3100-lossOfSignal9 M3100-payloadTypeMismatch10 M3100-transmissionError11 M3100-remoteAlarmInterface12 M3100-excessiveBER13 M3100-pathTraceMismatch14 M3100-unavailable15 M3100-signalLabelMismatch16 M3100-lossOfMultiFrame51 M3100-backplaneFailure52 M3100-dataSetProblem53 M3100-equipmentIdentifierDuplication54 M3100-externalIFDeviceProblem55 M3100-lineCardProblem56 M3100-multiplexerProblem57 M3100-nEIdentifierDuplication58 M3100-powerProblem59 M3100-processorProblem60 M3100-protectionPathFailure61 M3100-receiverFailure62 M3100-replaceableUnitMissing63 M3100-replaceableUnitTypeMismatch64 M3100-synchronizationSourceMismatch65 M3100-terminalProblem66 M3100-timingProblem



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

Argument value AASCE value67 M3100-transmitterFailure68 M3100-trunkCardProblem69 M3100-replaceableUnitProblem101 M3100-airCompressorFailure102 M3100-airConditioningFailure103 M3100-airDryerFailure104 M3100-batteryDischarging105 M3100-batteryFailure106 M3100-commercialPowerFailure107 M3100-coolingFanFailure108 M3100-engineFailure109 M3100-fireDetectorFailure110 M3100-fuseFailure111 M3100-generatorFailure112 M3100-lowBatteryThreshold113 M3100-pumpFailure114 M3100-rectifierFailure115 M3100-rectifierHighVoltage116 M3100-rectifierLowFVoltage117 M3100-ventilationsSystemFailure118 M3100-enclosureDoorOpen119 M3100-explosiveGas120 M3100-fire121 M3100-flood122 M3100-highHumidity123 M3100-highTemperature124 M3100-highWind125 M3100-iceBuildUp126 M3100-intrusionDetection127 M3100-lowFuel128 M3100-lowHumidity129 M3100-lowCablePressure130 M3100-lowTemperatue131 M3100-lowWater132 M3100-smoke133 M3100-toxicGas151 M3100-storageCapacityProblem152 M3100-memoryMismatch153 M3100-corruptData154 M3100-outOfCPUCycles155 M3100-sfwrEnvironmentProblem156 M3100-sfwrDownloadFailure

[GSM 12.11] ProbableCause values0.4.0.0.3.11.0.0.0.1 GSM-gsmA-BisToBTSInterfaceFailure0.4.0.0.3.11.0.0.0.2 GSM-gsmA-BisToTRXInterfaceFailure0.4.0.0.3.11.0.0.0.3 GSM-gsmAntenna0.4.0.0.3.11.0.0.0.4 GSM-gsmBatteryBreakdown0.4.0.0.3.11.0.0.0.5 GSM-gsmBatteryChargingFault0.4.0.0.3.11.0.0.0.6 GSM-gsmClockSynchronisationProblem



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

Argument value AASCE value0.4.0.0.3.11.0.0.0.7 GSM-gsmCombiner0.4.0.0.3.11.0.0.0.8 GSM-gsmDisk0.4.0.0.3.11.0.0.0.9 GSM-gsmEquipmentFailure0.4.0.0.3.11.0.0.0.10 GSM-gsmExcessiveReceiverTemperature0.4.0.0.3.11.0.0.0.11 GSM-gsmExcessiveTransmitterOutputPower0.4.0.0.3.11.0.0.0.12 GSM-gsmExcessiveTransmitterTemperature0.4.0.0.3.11.0.0.0.13 GSM-gsmFrequencyHoppingDegraded0.4.0.0.3.11.0.0.0.14 GSM-gsmFrequencyHoppingFailure0.4.0.0.3.11.0.0.0.15 GSM-gsmFrequencyRedefinitionFailed0.4.0.0.3.11.0.0.0.16 GSM-gsmLineInterfaceFailure0.4.0.0.3.11.0.0.0.17 GSM-gsmLinkFailure0.4.0.0.3.11.0.0.0.18 GSM-gsmLossOfSynchronisation0.4.0.0.3.11.0.0.0.19 GSM-gsmLostRedundancy0.4.0.0.3.11.0.0.0.20 GSM-gsmMainsBreakdownWithBatteryBackUp0.4.0.0.3.11.0.0.0.21 GSM-gsmMainsBreakdownWithoutBatteryBackUp0.4.0.0.3.11.0.0.0.22 GSM-gsmPowerSupplyFailure0.4.0.0.3.11.0.0.0.23 GSM-gsmReceiverAntennaFault0.4.0.0.3.11.0.0.0.24 GSM-gsmReceiverFailure0.4.0.0.3.11.0.0.0.25 GSM-gsmReceiverMulticouplerFailure0.4.0.0.3.11.0.0.0.26 GSM-gsmReducedTransmitterOutputPower0.4.0.0.3.11.0.0.0.27 GSM-gsmSignalQualityEvaluationFault0.4.0.0.3.11.0.0.0.28 GSM-gsmTimeslotHardwareFailure0.4.0.0.3.11.0.0.0.29 GSM-gsmTransceiver0.4.0.0.3.11.0.0.0.30 GSM-gsmTranscoder0.4.0.0.3.11.0.0.0.31 GSM-gsmTranscoderOrRateAdapter0.4.0.0.3.11.0.0.0.32 GSM-gsmTransmitterAntennaFailure0.4.0.0.3.11.0.0.0.33 GSM-gsmTransmitterAntennaNotAdjusted0.4.0.0.3.11.0.0.0.34 GSM-gsmTransmitterFailure0.4.0.0.3.11.0.0.0.35 GSM-gsmTransmitterLowVoltageOrCurrent0.4.0.0.3.11.0.0.0.36 GSM-gsmTransmitterOffFrequency0.4.0.0.3.11.0.0.0.37 GSM-gsmDatabaseInconsistency0.4.0.0.3.11.0.0.0.38 GSM-gsmFileSystemcallUnsuccessful0.4.0.0.3.11.0.0.0.39 GSM-gsmInputParameterOutOfRange0.4.0.0.3.11.0.0.0.40 GSM-gsmInvalidParameter0.4.0.0.3.11.0.0.0.41 GSM-gsmInvalidPointer0.4.0.0.3.11.0.0.0.42 GSM-gsmMessageNotExpected0.4.0.0.3.11.0.0.0.43 GSM-gsmMessageNotinitialized0.4.0.0.3.11.0.0.0.44 GSM-gsmMessageOutOfSequence0.4.0.0.3.11.0.0.0.45 GSM-gsmSystemCallUnsuccessful0.4.0.0.3.11.0.0.0.46 GSM-gsmTimeoutExpired0.4.0.0.3.11.0.0.0.47 GSM-gsmVariableOutOfRange0.4.0.0.3.11.0.0.0.48 GSM-gsmWatchDogTimerExpired0.4.0.0.3.11.0.0.0.49 GSM-gsmCoolingSystemFailure0.4.0.0.3.11.0.0.0.50 GSM-gsmExternalEquipmentFailure0.4.0.0.3.11.0.0.0.51 GSM-gsmExternalPowerSupplyFailure0.4.0.0.3.11.0.0.0.52 GSM-gsmExternalTransmissionDeviceFailure0.4.0.0.3.11.0.0.0.53 GSM-gsmFanFailure0.4.0.0.3.11.0.0.0.54 GSM-gsmHighHumidity0.4.0.0.3.11.0.0.0.55 GSM-gsmHighTemperature



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

Argument value AASCE value0.4.0.0.3.11.0.0.0.56 GSM-gsmIntrusionDetected0.4.0.0.3.11.0.0.0.57 GSM-gsmLowHumidity0.4.0.0.3.11.0.0.0.58 GSM-gsmLowTemperature0.4.0.0.3.11.0.0.0.59 GSM-gsmSmokeDetected0.4.0.0.3.11.0.0.0.60 GSM-gsmExcessiveErrorRate0.4.0.0.3.11.0.0.0.61 GSM-gsmReducedAlarmReporting0.4.0.0.3.11.0.0.0.62 GSM-gsmReducedEventReporting0.4.0.0.3.11.0.0.0.63 GSM-gsmReducedLoggingCapability0.4.0.0.3.11.0.0.0.64 GSM-gsmSystemResourcesOverload0.4.0.0.3.11.0.0.0.65 GSM-gsmBroadcastChannelFailure0.4.0.0.3.11.0.0.0.66 GSM-gsmConnectionEstablishmentError0.4.0.0.3.11.0.0.0.67 GSM-gsmInvalidMessageReceived0.4.0.0.3.11.0.0.0.68 GSM-gsmInvalidMSUReceived0.4.0.0.3.11.0.0.0.69 GSM-gsmLAPDLink0.4.0.0.3.11.0.0.0.70 GSM-gsmLocalAlarmIndication0.4.0.0.3.11.0.0.0.71 GSM-gsmRemoteAlarmIndication0.4.0.0.3.11.0.0.0.72 GSM-gsmRoutingFailure0.4.0.0.3.11.0.0.0.73 GSM-gsmSS70.4.0.0.3.11.0.0.0.74 GSM-gsmTransmissionError

Table 2: OID versus string value for PBCAUSE



All r

ights

re

serv

ed. Pa

ssin

g on

an

d co

pyin

g of

th

is

docu

men

t, us

e an

d co

mm

unic

ation

of

its

co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izatio

n fro

m Al

cate

l.

6. APPENDIX B: SHORT DESCRIPTION OF EXCLUDEDPARAMETERSThe following table gives an informal description of the parametersthat can appear as argument but that are proposed to be out of thescope of the Current Alarm Script Triggering facility.

Parameter Short Description CommentsADDTEXT Additional Text (see

[X.733])This parameter containsa string in which anycharacter except " canpotentially appear

ALARMID AS Alarm IdentifierALSRCNAME Alarm Source NameBACKOBJ Back-up object (see

[X.733])Not significant FDN

BACKSTS Backed-up status 0 (meaning no) |1 (meaning yes)

CIMTIME Recording time in thecorresponding AS Manager

CLRABLSTS Clearable status notClearable (0) |clearable (1)

CORRFLAG Correlated Notificationflag

0 (meaning FALSE) |1 (meaning TRUE)

DOMAIN Access Control DomainEXPIRSTATUS Expiration StatusPBCAUSEID ID of the ProbableCause

valueNo added value comparedwith PBCAUSE

REPAIR Proposed Repair Actions(see [X.733])

Always equal to therepairActionRequiredOID value (from[X.721]), i.e.

2.9.3.2.0.2.2RSVSTS Reservation Status unreserved (0) |

reserved (1)TTFLAG Trouble-ticket creation

flagticketNotCreated (0) |ticketCreated (1)

Table 3: Short description of excluded parameters (informal)

END OF DOCUMENT

format of current alarm script triggering ed01.pdf

Documents