Documente Academic
Documente Profesional
Documente Cultură
1. DATA IDENTIFICATION
1.1 Definition
1.1.1 Type of data
All data stored in a system memory (ROM, RAM, DISK) is characterized as belonging to
one of the following three types:
Permanent :
Semi-permanent :
This is data that change during normal operations :-
- through man-machine interface (MMI).
- through subscriber action.
- spontaneously.
These data have to be stored on nonvolatile memory so that they can be retrieved when
the whole system is being rebooted or software have to be upgraded.
These data are the record of changes in a site’s environment. They are referred to as site
data.
Certain semi-permanent information is identical on every site in a given country (e.g. pre-
analysis data), and may only change in exceptional conditions through constructor MMI.
These are called country specification data.
Temporary :
These are data that are neither permanent nor semi-permanent. These types of data
receive a value when the system is initialized :
1.12 Files
-1-
Data is grouped in adjacent memory zones called files.
A file is characterized by its file type :
Permanent:
This type of the only contains permanent data.
Semi – permanent :
This type of file only contains semi-permanent data.
Temporary :
This type of file only contain temporary data.
In the rest of the chapter, the terms “data” and “files” refer both to programs (code and
data) obtained by compilation and files obtained by compilation and files obtained by
other production means.
1.1.3 Archive
- site archive:
* this type of archive contains a set of semi-permanent site data
- system archive :
* this type of archive contains permanent or temporary files.
Globally all these archives are grouped under the label ZOCB. The list of
archives together with their respective checksums are memorized in the XGID
file.
The archives are stored on logical drive 25 (DL 25) of the SMM disk. The file
which contains the OCB archives (ZOCB) is called SMMFIL.
• this type of support is used for initial loading of permanent and semi-permanent
data and as a protection against a simultaneous breakdown of the system and of
the nonvolatile media (OM disk).
- DM : Nonvolatile mass OM memory (disk) :
• this type of medium contains a copy of constantly updated permanent and semi-
permanent data. It is used for partial or total system restart.
• this type of medium is present in operational stations and contains files of all
types. The permanent and semi-permanent files are loaded from disk at
initialization.
The OM is a special case where certain programs are loaded when they are run.
-3-
(a) Permanent files :
Initial loading
MT or Disks
Station streamer
RAM Station RAM Station RAM
Backup on tape
after software
changes
MT or
streamer
Disks
Station
RAM Initial loading
memory
Loading of
RAM
RAM
-4-
(b) Semi – permanent files :
Initial loading
MT or
streamer Periodic storage of Disks
semi-permanent data
(Restart following
system breakdown and disks
or change of software level)
Disks
Initial loading
Station Disks
RAM
memory
Data backup
equivalent
Station Station
RAM RAM
-5-
(c) Temporary Files :
Loading from
RAM
RAM
Memory
Memory
-6-
1.4 Software Organization
1.4.1 Organization of software on disk
DISK
IDENTIFICATION
RTOS
SSOM
SMMLAS/
PRMSMM
ZOCB
SMMFIL
ZTO PGIL
ZLO
ZSM
Handled .
using . IDLIN
DMUTIL
.
ZMR
ZTR
XAFO LFNIL
XATR
XATX
. IDLIN
.
.
XASM
YFDT
YOFA
-7-
1.4.2 Software Identification
(a) RTOS :
Identification and management of these files with debugging utility.
-8-
Data identification can be done at the different editing levels (system, archive, file,
record).
ARC n
ARC m
IDLIN
⇒ ARCo
ARCHIVE Level
SYSTEM •
•
ARCt
FILE a
IDLIN FILE b
FILE z
REC 1
IDLIN REC 2
REC 3
FILE c RECORD Level
•
•
REC n
(d) CSN :
There is a command by which CSN software may be identified :
- IDLIN : Identification of connection unit software.
-9-
This command is used to check the program memory checksums sub-groups at the CSN
level. A sub-group is a place of software that corresponds:
- S-ENS = SOFTWARE 0 0 CSN code
- S-ENS = SOFTWARE X X Software (with PU type software)
VOL HDR
• Data blocks
• EOF •
•
•
File A File B
VOL HDR
• File A
• EOF • HDR • File B
• • EOF • •
data blocks data blocks
•
-11-
2.2 Basic magnetic tape operations
Blank tape
Sticker
BMPMQ :
No of magnetic
tape
Authorization
User’s name
If UVL = NO IATC User
need not be given Preventive check
on date of tape
• Blank tape
TOTO 93330 BRIVE
•
Sticker User
name
(UVL) (IATC)
Volume
name (VOL)
Date Double tape mark
(Annee (end of volume)
Jour) -12-
2.2.2. Setup
Once the tape is physically loaded on the drive, setup establishes the software link
between this drive and the installed volume.
MTO MTO
• •
Tape BMMNT
which is Volume TOTO
(setup)
Premarked
TOTO VOL = TOTO
• BM = O
•
CTRL = no.
MTO
SMM
•
Software
Transfer Volume TOTO
File IDFIC =
link “taxation”
•
BMASS
VOL = TOTO
LFN = transfer file name
IDFIC = “taxation”
file name to be
marked on taps
-13-
2.2.4 Downloading files to the tape
SMM MTO
•
Transfer
Volume TOTO
File
IDFIC = “ X X X X”
•
Activate transfer
command
TAXIL – FDTIL – OFAIL – ARCSV - DMSV
E H
Contents
TOTO 93330 BRIVE X X X X backup
of file • O • D ••
F R
User
name
-14-
2.2.5 De-assigning a volume and a transfer file
SMM MTO
Transfer
File VOL = TOTO
BMASS :
•
VOL = / TOTO, LFN = FILE NAME ;
De assigning symbol
Dismounting means releasing the drive from the volume linked with it.
- BMDMO :
- VOL = TOTO ;
-15-
3. APPLICTIONS
Record
XATX
FITAX
Print contents of :
- MLTX 1
in case of discrepancy
-16-
- MLTX 2
- Record
After the tape has been installed and assigned to the GTLC file which is the charge meter
transfer, use the command :
- TAXIL :
- OPTION = DIR;
MIS
SMC SMM
SMC
MIS
SMC SMM
SMC
MIS
SMC SMM
SMC
GTLC
MLTX 1 MLTX 2 TAXIL
Buffer
This phase can be repeated in order to make a second meter tape. Since the contents of
the buffer are unchanged, this tape will be exactly the same as the first.
-18-
3rd phase : deleting buffer contents
- TAXIL :
- OPT = EFF ;
Empties buffer contents and makes it ready for the next backup.
3.2 Backup and storage of itemized billing messages
3.2.1 Continuous transfer of FAC. DET (itemized bills) message to the YFDT area of the disk.
MIS
SMC SMM
SMC
-19-
-20-
3.2.2 Downloading of FAC. DET messages from the YFDT buffer to the tape
After installing and assigning the tape to the GTDT transfer file, use the command
- FDTIL :
- OPT = SC ;
SMM
GTDT
transfer
file
YFDI
The YFDT disk file is 100 Mb, made up of blocks of 2048 bytes.
When this file is 83% empty, the FAC. DET application sets off a non urgent alarm,
followed by an urgent alarm which it is 94% full.
The size of the disk’s YFDT buffer file gives it a capacity of 72 hours with 100%
FAC. DET subscribers and 800 000 TAHC (high speed subscriber terminals).
The fullness of the YFDT buffer file can be checked will the command
- FDTIL :
- OPT = STTUS;
If the SMM can not be accessed, the MLTX buffer can store 4 to 5 hours of itemized
billing depending on traffic.
-21-
3.3 Backup and storage of fault, alarm and observation messages
Overall the principle is the same as for FACDET.
alarm
MAL
Network
SMM
Alarm Task
YOFA
SSOM
MIS
SMA SMT SM
-22-
-Fault/alarm/obs message
3.3.2 Downloading fault/ALA/OBS messages them the YOFA buffer to the tape
After installing and assigning the tape to the OPFA transfer file, use the command.
- OFAIL :
- OPT = SC ;
SMM
•
OPFA
Transfer
YOFA
The YOFA file us 50 Mb, also with alarms when 83% and 94% full.
The file status of the YOFA buffer can be checked with the command OFAIL : OPT = STTUS.
-23-
3.4 Archive backup and restoration
After installing and assigning the tape to the transfer file XGAR, back up using the
command ARCSV with the name of the archive to be saved.
By specifying it in the command, one may, if one wishes, save only one or a few files in
this archive.
ARCSV :
ARCH = XATR;
SMM
XGID File
Archive addresses
ARCSV
XATE AD = xxx ARCH = XATR
-24-
The ARCRG command restores an archive or a group of archives or a file from an
archive by means of the same procedure.
First, the tape must be installed and assigned to the MVB 1 transfer file.
Next, the MVD 1 disk transfer file is assigned to the disk file to be backed up or restored
(FICDM).
DMSV BMASS
•
DMASS
MVD 1 MVB1
File ZZ disk Tape
VOL
(FICDM) Transfer Transfer
File File
•
DMRG
-25-
APPENDIX 1 : THE LECBAN COMMAND
1. ROLE :
The operator command LECBAN lists magnetic tapes concerning charge meters
(TAXIL), itemized billing (FDTIL) and observations, alarms and faults (OFAIL). This
listing decoded on a certain number of selected entries.
It is essential that magnetic tapes read with the LECBAN command should be used
without the write-permit ring. The volume for listing must be correctly set up and
assigned.
In the setup assignment command BMASS, the volume (VOL) and the file ID (IDFIC)
must be the same as those used when the tape was created.
These parameters are optional D1 H1 and D2H2 must both be either present or absent.
-26-
4. LIST TAPES OF OBSERVATIONS ALARMS AND FAULTS :
(a) General observations :
TYP = OBS : Request for readout of observation entries.
COD = - + - : Entry code number of observation items.
@ LECBAN, CEN = 0 :
CEN = 0 /92-03-06/12 h 55 MN 11/ANALYSIS OIF TAPE OPFA/GTDT/GTLC
@ TYP = OBS, N = 2,
PROCESS TLECBA ACC
DATE OF TAPE CREATION : 92-03-06
NCEN=NANTES/92-03-03/18 H 00 M 10 OBSERVATIONS OAT
INTERNAL TRAFFIC TAX=0000622730
ADDITIONAL SERVICES TAX= 0000000037
NCEN= NANTES/92-03-03/18 H 00 M 13 OBSERVATIONS OAT
NFSC = FD010 TAX = 0
NFSC = FD020 TAX = 0
NFSC = IFD01 TAX = 6
NFSC = IND01 TAX = 1
NFSC = PO02D TAX = 14
NFSC = PO04D TAX = 2
NFSC = FMN01 TAX = 0
NFSC = PO01D TAX = 22
NFSC = PO03D TAX = 1
NUMBER OF ITEMS OF TYPE : 30 1
NUMBER OF ITEMS OF TYPE : 31 1
NUMBER OF ITEMS OF TYPE : 32 6429
NUMBER OF ITEMS READ : 6431
NUMBER OF ITEMS MISTAKEN : 0
NUMBER OF ITEMS PRINTED : 2
PROCESS TLECBA EXC
Various meaning of COD
COD = 1 Output as when OCHLA has commenced
= 3/4/5/6/7/8/ Output of class Z/C/F/A/R/T respectively
= 9/10 Start & stop of subs sample observation
= 12 OABLA observation
= 26/28/29 For OMALA observation
-27-
(b) Observation regarding subscribers :
TYP = ABO : Request for readout of entries regarding subscriber
observation.
PREF = ---- + ---- : First figures of subscriber DN (9 maximum)
@ LECBAN, CEN = 0 :
CEN = 0/92-03-10/09 H 30 MN 35/ANALYSIS OF TAPE OPFA/GTDT/GTLC
@ TYP = ABO, N = 10;
PROCESS TLECBA ACC
DATE OF TAPE CREATION : 92-03-10
92-03-10/09 H 30 MN 53
DIRECTORY DAY HH MM SS FIGURES LENGTH LENGTH LENGTH INEF S INPUT
NUMBER SET CONNE- RINGING H S TAXES
DOWN CTION CONV.
040420140 70 9 5 13 40423174 8,3 6 5 0 0 1
040420142 70 9 5 33 0,0 6 6 0 0 0
040420136 70 9 5 33 0,0 7 6 0 0 0
040420136 70 9 5 53 40420094 8,0 6 5 0 0 1
040420142 70 9 5 53 40420074 8,0 6 5 0 0 1
040420140 70 9 5 33 0,0 6 6 0 0 0
040420138 70 9 5 33 0,0 8 6 0 0 0
040420138 70 9 5 52 40423174 8,0 6 5 0 0 1
040420140 70 9 5 52 40420088 7,7 6 5 0 0 1
040420138 70 9 5 13 0,0 6 6 0 0 0
NUMBER OF ITEM OF TYPE : 9 1
NUMBER OF ITEM OF TYPE : 11 5
NUMBER OF ITEM OF TYPE : 12 5
NUMBER OF ITEM OF TYPE : 32 43
NUMBER OF ITEM READ : 54
NUMBER OF ITEM MISTAKEN : 0
NUMBER OF ITEM PRINTED : 10
-28-
(c) Alarms :
@ LECBAN , CEN = 0 :
CEN = 0/92-03-06/12 H 58 MN 4G/ANALYSIS OF TAPE OPFA/GTDT/GTLC
@ TYP = ALA, N = 1;
PROCESS TLECBA ACC
DATE OF TAPE CREATION : 92-03-06
!!! * A0628/327/92-03-03/13 H 01/N =114 8/TYP=COM/CAT=IM/EVENT=DAL
/NCEN=NANTES/OBJECT=CDC/AGEO=CDC
/TEXAL = MODULATION SOURCE CHANNEL.
(d) Faults :
TYP = ANO : Request for readout of alarm messages
CLICH = : Profile code indicating seriousness of fault
TYPO = --- : Functional type of the output object or component
NORG = --- : Number of the component or object within the type
@ LECBAN, CEN = 0 :
CEN=0/92-03-06/13 H 00 MN 20/ANALYSIS OF TAPE OPFA/GTDT/GTLC
@ TYP = ANO, N = 1;
PROCESS TLECBA ACC
DATE OF TAPE CREATION : 92-03-06
• #F1387/T08F15/NCEN=NANTES/92-03-03/09 H 59/NOM=OFSTM
/N=0001/NIV=3/ENS=011/SEN=132-011-051/PS=00255/SERCOC=193
/EM: AF = PUPE2
/COD=020/LGU=025
-30-
(e) LOG :
TYP = JDB : List log
DV = ---- : Terminal name
CMD = ---- : Name of command to be listed
ACT=---- : Type of command activation
ACT=0 operator
ACT = 1 operator originated calendar
ACT = 2 other originated calendar
ACT = 3 periodical
ACT = 4 program
ACT = 5 permanent central
ACT = 6 temporary central
-31-
.. PROCESS TLECBA EXC
5. LISTING OF ITEMIZED BILLING TAPES :
3. FORMAT OF RECORD :
Tape addition Date : Date of addition of detailed billing tape
COD : XX – YY Length = 2 bytes (1-2)
XX : Function Type – DBCI (Detailed billing, with charge calculation, with
charge meter incrementation), value = h’01’
- DBC (Detailed billing, with charge calculation, without
charge meter incrementation) value = h’ 02’
-32-
- DBC (Detailed billing, with charge calculation, without
charge meter incrementation) value = h’ 02’
- DB (Detailed billing, without charge calculation, without
charge meter incrementation) value = h’ 03’
- DIN (outgoing accounting)m, value = h’20’
- DCA (Incoming accounting), value = h’10’
- IDT (Advice of duration and cost), value = h’08’
- DEA (Details of incoming calls), value =h ‘04’
- OPE (Operator ticket), value = h’40’
- DBCI + DIN, value = h’21’
- DBC + DIN, value = h’22’
- DB + DIN, value = h’23’
- DIN + DCA, value = h ‘30’
- DBCI + OPE, value = h’41’
- DBC + OPE, value = h ‘42’
- DB + OPE, value = h’43’
- DIN + OPE, value = h ‘60’
- DBCI + DIN + OPE, value = h ‘61’
- DBC + DIN + OPE , value = h ‘62’
- DB + DIN + OPE, value = h ‘63’
-33-
NDDR : I/C side identification (A – subscriber number)
Number in 10 digits maximum
Length = 5 bytes (9 – 13)
ICT : Number of charge units (0 to max. possible charge unit for a call)
Length = 3 bytes (33 – 35)
-34-
TA : Type of traffic (corresponds to the translator number used to handle the call)
- Local call
- National call
- Emergency, special call
- International Call
Length = 1 byte (28)
TC : Type of service
- Normal call (h ‘00’)
- Calling line identification restriction On call by call basis (h ‘ 01)
- Advice of charge call/call (h ‘02’)
- User to user signaling, applicable for chargeable access to access
information (h ‘ 04’)
- Closed user group (h ‘ 08)
- Three party service (h ‘20’)
- Unsuccessful call (h’40’)
- Call forwarding (h ‘ 80’)
Length = 1 byte (29)
When more than one type of service activated during a call, value for each of these is
added to give value of TC. For example.
Closed user group member invoking UUI, TC = h ‘08’ + h ‘04’ = h ‘OC’
-35-
These fields are :
- SADR (called party sub address)
- SADE (called party sub address)
- NDS (multiple subscriber number)
- UUI (user to user information)
- IPR (Progress indicator)
Length = 1 byte (38)
Depending on how many of these fields have been used during a call, h ‘01’ is
added for each of the used fields to give the value of XU. For example.
for a call with called party sub-address and calling party sub-address,
XU = h ‘01’ + h ‘01’ = h ‘02’
In order to charge, or not, the corresponding access-to-access field,
contents of data base may be modified through system command.
PO : : Operator identification
Number on 4 digits maximum
Length = 2 bytes ( 40 – 41)
-36-
This field is not shown in LECBAN format. By BMUTIL system command this
field can be seen. It is filled with h ‘FF’ for calls initiated system other than
Alcatel OPE 283.
Byte 39 : Reserved
1. ROLE :
This command is used to analyse, read, or retrieve on to a final tape the contents
of magnetic tapes.
2. CHIEF PRECAUTION :
Remove the ring from the original tape
3. PROCEDURE :
C = Command types by operator
R = Reply printed out on teleprinter
C CTRL – a
R @
C BMUTIL :
R @
C MT = BMEi + BMSj :
-37-
3.1 Positioning Functions :
(a) Rewind
R @
C RWD, MT - :
MT - = BME or BMS
R End of processing message
-38-
3.2 Analysis/readout of original tape contents
(a) Analysis :
R @
C ANA = OPT
OPT = BASE (basic analysis)
OPT = ERR (number of error blocks)
OPT = LGR (length)
R End of processing message
R @
C EDI = NBB – NBO
NBB = number of blocks for reading
NBB = 0 means “until end of readout signals are encountered”
(double TM end of tape sticker)
NBO = number of bytes per block for listing
NBO = 0 means “readout of whole block”
R End of processing message
-39-
3.3 Recovery of tapes
R @
C COP = -- :
COP = number of blocks from original tape to copy
COP = 0 means “until end of copy signals are encountered”
(double TRM end of tape sticker)
R End of processing message
R @
C WTM = 1
R End of processing message
R @
C WTM = 2
R End of processing message
R @
C WFD =-- TXT = ----
WFD = length of block in bytes
TXT = text (filled in with blanks)
R End of processing message
-40-
-41-
-42-
-43-
-44-
-45-
-46-
-47-
-48-
-49-
-50-
-51-
-52-
-53-
-54-
-55-
-56-
-57-
-58-
-59-
-60-
-61-
-62-
-63-
5. Saving of data in DGMA and then to streamer :
DGMA is an area within the hard disk for storage of data similar to a mag tape. Also
known as logical disk 27 of approx. H’20,000 sector storage capacity.
LSTSTR
STDEVGRP ; AK1
SRDEVPRT ; PSMR
STDEVNAM : SMR C∅ C∅
LIST TYPE : STRHDR
-64-
TERMINAL MANAGEMENT
Introduction
The fault messages are general in OCB-283 exchanges when an abnormal software or
hardware problem is detected in any of the exchange unit.
Handling OM faults is a centralized function which can be broken down into three main
activities:
Taken in isolation, a fault does not mean that the component is not functioning properly.
A fault is indicated by a spontaneous message emitted by a component on behalf of the OM.
It is a result of the detection of a fault by this component, either in its own operations
(equipment fault, detected by the equipment) or in the performance of a switching operation
(software fault, detected by the program).
In the latter case, responsibility for the fault may be shared, in proportions defined for
each fault, between the emitting component and the component or components with which pit
communicates.
Message
BM entry
FAULTS Memorization
PROCESSISSNG
MESSAG
Component diagnosis
OF
SUPERVISIO Listing
N
PERIOD 2 min. FAULTS
Filtering
Inhibition
FILTERS
BUFFER
- Handling filters :
This is an additional service to the statistical observation of faults which has to be selective in
order to work. An operator modified EDAV filter is used.
-67-
This provides the option of looking at faults on a deferred basis by recording them on a disk
buffer. The same filtering device is available through the ENBM filter.
Continues analysis beyond normal ongoing fault processing. Applies to certain faults involving
peripheral component equipment (memories, circuits, subscriber equipment).
Routine triggered by the ANOIL command which edits the last 15 faults filtered by the EDAR
filter.
Automatic reactions
-68-
N =6045 / NIV = 3/ ENS = 011 / SENS = 133 – 011 – 051 / PS = 0255 / SERCOC = 193
FAULT EMITTER
EM AF = PUPE3
OPERATOR INTERFACE
Commands which act on filters
There are three fault handling filters :
ENBM
TOFO YOFA
T15 F15
ENBM
TF
TOFO PFAU
T15 F15
ENBM
ANOIL
TOFO
T15 F15
-69-
15 RECORDS
The FILTERS
There are three operator commands which act directly on fault emission
FEMAR Stop of anomalies message transmission
-70-
FEMLA Actuate anomalies message transmission
This command has the effect of suppressing a component’s level 2
and 3 fault emission inhibition (i.e. reversing FEMAR command).
List command
There is an operator command for listing recorded faults.
ANOIL Print out of last anomalies
This command edits the last 15 faults recorded
In CSN whenever any of the PCB becomes faulty, locavar will be run by CSN
automatically. The results of locavar are written in EMSSO file of CSN. In addition the
details of diagnostic will be written LMIS file if OM and also the diagnostics are printed
on a TTY assigned with OPMN file. If any of the TABA module becomes faulty, it will
be printing ODCAB message on PFAC file in addition to the above.
UT NO + 1
-71-
EM = AFUR = URAD – 2 CN = 01, PAR = 04
R 1421 / 000 / CEN = 1 / 13 – 02 – 01 / 10 H 50 MN 52 / N = 003
DIAG = U 6 P 432. TYA = CSN, PAR, = ’04 ‘ H
CEN = 1, TABA 16, AFCN = CNLM 2 - 1
AGEO = SITE – 002 – B 0 1 – A 003 - R 090
We can find the same details by reading LMIS file using ARCIN commands
ARCIN :
FICH = LMIS, NOMS = FLMES 1, NUM = 1 < 63
-72-
ANALYSIS OF DIAGNOSTIC MESSAGES
C S N
DIAGNOSTIC
DIAG
DIAG
SYSTEM OPERATOR
SYSTEM
-73-
0 1 2 3 4 5 6 7
Front side
15 14 13 12 11 10 9
8
-74-
D I A G = U 6 P 43 2
U6 = E N S 6
INTERNAL SPPF = 2
CN LM
DIAG NO T A B AM
THLR/UT
1 TA BAD
SRPF 2 TABAM
3 TABAE
45 TABN4F
6 = TABNAL
7 TANAE
8 TAN4F
A TADP
9 TAN3G
-75-
NUME = 3
NORD = 3
TYPE = 24
NOCN = 1
PTRS = 2
PTRP = 1
N0 =2
INFO = 555
DIAG – U6P 432
SENS 1 = 10
ENS = 6
OM Dignostic files description
LIMS : Dignostics printed after automatic localization on UR
Organisation : DIR
NBE = 64
Edition structure : FLMES 1
Fields description :
NORD : Record number
TYPE : 24 ==> URA
NO : UR number
DIAG : Mnemonic of diagnostic
NOCN :CN number
PTRS : Next record
PTRP : Previous record
INFO : Supplementary information
NIV : Fault level
SENS 1 : UT no. +1
SENS 2 : Sub Assembly of Rank 2
SENS 3 : Sub Assembly of Rank 3
ENS : No of faulty module
if ENS = 1 UCX + timing signal distribution in the UCN
SENS 1 logic unit number
-76-
ENS = 2 TTRS (internal PCM side)
SENS 1 LR 1 number in the CN
SENS 2 ICNE TTRS number
NOCN CN number
if ENS = 8 GTA
SENS 1 TFILM or TRF8 number
SENS 2 ICNE TTRS number
NOCN CN number
PTRS = 2
PTRP = 1
INFO = 555
SENS 1 = 10
-77-
ENS = 6
SENS 1 = Sub Assembly (UT + 1)
SENS 2 = Sub Assembly of Rank 2
SENS 3 = Sub Assembly of Rank 3
ENS = No. of faulty Module
-78-
LOCAVAR & DEFENCE
1. Locavar is a software tool provided in the OCB-283 system for detecting hardware fault
in different units.
This simulation programme is normally resident on Disk of SMM and loaded in the units CMP
s
whenever required. However the locavar programme for CSN resides in CSN only.
Thus initial positioning to BLOM or BLOS status is essential for a locavar run. There are
various other defence reactions when a unit is attempted to be set to BLOM or BLOS
status. Before discussing the defence reactions while positioning it will be worth to
discuss the various status that can be assumed by various units of OCB-283 exchange.
These are also referred to as primary positioning of units (POSP) or stable state.
There are certain transient status or current status of functions within a unit, referred to as current
state (ETAC).
-79-
A list indicating POSP, ETAC and the edited status is given below. (Table-1)
TABLE – 2
-80-
INIT INIT
ENC INIT
INDO INDO
INDL INDL
NES NES
The central defence is located in (a) SMM (b) MLGX for switch (c) MLPC for CCS#7
links.
Any maloperation related to connection are detected by SAB, made over to MLGX via
MLCOM. MLGX carries out thorough test on the switch path and in case of problems
encountered give appropriate message to SMM for alarm message out put.
Similarly in case of any problem related to CCS#7 signalling link, the protocol handler
PU/PE gives message to central defence MLPC. MLPC takes care of reconfiguration of
signalling link. The respective PU/PE will give message to SMM for outputting fault
messages on appropriate terminal.
(i) If a SMC with one PC is already out of service the SMC with other PC will not be
set to INDL or BLOM i.e. manual request to do so shall be refused.
(ii) If number of units of same type are attempted to be set to BLOM then there will
be warning like “too many units are already out, this may cause switching
interruption and so confirm if the setting is still required. On confirming the
setting is effected. While effecting a setting the redundancies are also taken care
of, in order to ensure that the exchange does not remain in a degraded mode for
long.
eg.
(i) When a SMC is to be set to BLOM or BLOS the central defence first tries to
bring the standby SMC to ES by loading the functions of the SMC to be set to
BLOM so that the degradation period is minimum.
(ii) When a SMA with PU/PE is set to BLOM/BLOS then all the CCS#7 data links
are reconfigured to the reserve PU/PE by central defence i.e. MLPC.
-81-
(iii) When a SMT is to be set to BLOM or BLOS (due to fault) then first defence
reaction shall to be make the duplicate as PILOT.
The defence reactions are carried out by way of transaction of some defence messages between
units and SMM. These messages are stored in a file XDSF of OM on SMM disk. There
is a command “SRFIL” by which we can selectively retrieve the messages by using
appropriate parameters. Analysis of these messages may give some clue to the fault
responsible for these defence messages.
The general defence philosophy is that when a control station poses problem by requesting the
SMM to set it to BLOS the first reaction of SMM is to broadcast this situation to all other
stations and then bring up the standby station to inservice (ES) by loading all the MLS of
the faulty SMC. The change in the configuration of station is broadcast to all stations.
Then a locavar is run on the faulty station.
If there is a hardware fault then the station is permanently set to BLOS and this situation is
conveyed to all. In case there is no hardware fault detected thena the station is set to ES
but it will become standby only. If required the original standby which has now become
functional can be manually set to BLOM so that all the MLS again get loaded on to the
tested SMC. There can be two possibilities viz. either there may be a failure of
initialisation or iniotialisation may be successful. Even if the initialisation is successful,
after some time there may again be a request from this station for setting it to BLOS. In
either case there is a possbility of a fault in the station but perhaps not within the preview
of locavar program to detect. In such cases the defence message contents may give some
clue to find faulty PCB. (Retrievable by SRFIL)
The series of diagrams indicate the defence reactions in case of a station becoming faulty. The
name and purpose of messages are also given in the texts related to each elemental block
diagram.( Refer fig. 1 to 10).
-82-
Example of defence reactions
Example of reaction to a fault (SMC)
SMCY
CMS CMS PUS standby
SMC X fault
ICMAT ICMAT
ICMAT
ml
Boot MLSM
(Main)
(1) ORPOS
MIS
SMM
Central defence
Fig. 1
-83-
SMCY
PUS
standby
CMS PUP
(1)
fault
ICMAT ICMAT
SMC X
ICMAT
BSM
mt
MLSM
Boot (Main)
MIS
(2) ODIET
to all stations
(FTET)
Supervision
Init
Reconfiguration LOCAVAR SMM
Posting
Central defence
Fig. 2
-84-
SMCY
PUS
standby
CMS PUP
(1)
fault
ICMAT
S MC X ICMAT
ICMAT
mt
MLSM
Boot
(Main)
RPOS FPOS
MIS
(3) DPOS
Init SMM
Supervision
Posting LOCAVAR
Reconfiguration
Central defence
Fig. 3
-85-
SMCY
PUS
standby
CMS PUP
(1)
fault
S MC X ICMAT ICMAT
ICMAT
mt
MLSM
Boot
(Main)
MIS
MIS
(4) OMCOS
to all stations
SMM
Init
Supervision
Reconfiguration LOCAVAR
Posting
Central defence
Fig. 4
-86-
SMCY
PUS
standby
CMS PUP
(1)
fault
ICMAT ICMAT
ICMAT
mt
Local defence
CMP
start of
station
MLSM
Boot (Main)
(5) DPOS
(5) RPOS
test
MIS
MIS
SMM
Central defence
FIG. 5
-87-
SMCY
SMC X
PUS standby
CMS PUP
(1)
tes tes faul
tes
test
ICMAT ICMAT
ICMAT
BSM
mt
test
CMP
end of
station start of
LOCAVA station MLSM
Boot (Main)
Local defence
(6) FTEST
(diag)
MIS
MIS
Init
Supervision Reconfiguration LOCAVAR
Posting
Central defence
Fig. 6
-88-
Example of reaction on SMT 2 G
0 3 MIC 63 MIC 64 127
LA
0
S LA
A S 16
B A GLR
B
16
GLR
BETP 1 (A) BETP 2(A) BETP (8) BETP 2(B) 127
127
SMT A CLTH 2 SMT B
active CLTH 2 Standby
CLTH 1 LISM 1 CLTH 1
switchover
fault ESRE
21
ES
1 ICMAT LISM 2
BSM BSM
1 CMP
21
BOOT
CMP
MAS
S S
M MLMQ M MLMQ
C C
MAS
SMM
Central defence
FIG. 7
(1) Serious fault on CLTH 1 stored in ICMAT. Serious Fault Signal sent to CMP. Return of
CMP to boot which blocks operation of the BSM bus.
(2) The CLTH 1 receives from boot a BSM blockage RAZ and sends switchover order to the
CLTH 1 of the other logic unit. This unit switches from ESRE status to ES status and
hence takes over traffic flow.
-89-
0 3 MIC 63 MIC 64 127
LA
0
S LA
A S
A 16
B
B GLR
16
GLR
BETP (B)
127
SMTA SMT B
CLTH 2 active
CLTH LISM
CLTH CLTH 1
faul LISM 2
ICMAT
BSM BSM
CMP
CMP
BOOT
3 hard
MAS
ORPO
S S
MLMQ INTERFACE M MLMQ
M
C C
4 MIS
MAS ODIET
to all
SMM
Central defence
Fig. 8
(3) The CMP boot sends a hard ORPOS to central defence (SMM)
-90-
0 3 MIC 63 MIC 64 127
LA
0
S LA
A S
B A
B 16
16
GLR GLR
BETP (B)
127
SMTA SMT B
CLTH 2 active
CLTH LISM
CLTH CLTH
faul LISM
locavar
locava ICMAT
BSM
CMP
5 locava
locavar CMP
BOO
MAS
S
S MLMQ
MLMQ INTERFACE M
M
C
C
5 DPOS MIS
MIS
test
SMM
Central defence
Fig. 9
(5) LOCAVAR request sent to fault SMT. Yhis test only applies to boards
connected to the BSM and never to the ETUs and the SABs.
-91-
0 3 MIC 63 MIC 64 127
LA
0
S LA
S
A A
B B
16
GLR
BETP (B)
127
SMTA SMT B
CLTH 2 active
CLTH 2 LISM
CLTH CLTH
faul
LISM
end
locaof
var CMP
locavar CMP
BOO
S
S MLMQ
MLMQ INTERFACE M
M
C
C
MIS
MIS
FIG. 10
(6) The CMP receives end of test from the different agents of the logic unit being tested and
sends to the SMM either an FTEST if diagnosis or FPOS if no diagnosis. If diag, the logic
unit is BLOS at the end of the test, if no diag the unit is reintialized and put back into
operation at the end of the init.
-92-
4. LOCAVAR PROCEDURES :
As already mentioned earlier locavar can be initiated both manually and automatically by
SMM.
For manual locavar commands are given from terminal asking the SMM to carry out
locavar on a unit. SMM will run locavar only if the unit is found to be in manual
blocked (BLOM) condition. However this odes not apply to CSN which can not
be set to BLOM as total service to all subscribers will be interrupted. In CSN
locavar is run on different subassemblies as will be discussed later in the chapter.
For automatic locavar trigger comes from the station which encounters problem during
normal call processing, may be due to a hard or a soft fault. In case of a soft fault
the station is again set to ES by SMM after running locavar but the setting
request may be recurrent. If it is so then there can be two reasons viz. either the
software is faulty or software is getting corrupted due to hardware. The second
possibility calls for detecting the PCB responsible for such malfunction. This can
be detected by analysing the message coming from unit to SMM requesting
positioning to BLOS (ORPOS Message. (Message is retrievable by SRFIL).
For manual locavar the units in the OCB are divided in three categories and different
commands are there for these three categories:-
s
(3) ETU - Command is ETUTL
Locavar on SM stations :
Procedure : (i) Set the station to INDL then BLOM keeping in mind the
defence warning.
(ii) Give command & parameter as follows
@ SMTL :
@ AM = SMC2 (say)
-93-
s
Case of SMX : When running locavar in SMX all the PCB in the station are
tested but the RCMT cards corresponding to the inlets of this
s
SMX but having a multiple appearance in other SMX are not
covered. Some times following a switching problem of a inlet
LR belonging to one SMX to a outlet LR belonging to another
SMX, an alarm message comes refering to inlet LR (GLR) in
form of COM – GLR.
By seeing the alarm naturally a locavar is run on the COM (SMX) but there may not be any
diagnostic.
There is a different command to identify the COM where the said inlet could have
encountered error. Command LCXCT is used to locate the actual RCMT i.e. inlet card
which caused error while switching to a outlet LR. (The switching takes place in a SMX
where outlet error is available)
If there is any problem then the report would give & either the faulty RCMT no
along with the COM no or it will give the RCID number. Sometimes these cards
may not be faulty but the LCXE cable pertaining to the GLR may be faulty or
loosely connected. A physical check may help clearing the fault,. Sometimes the
fault could be on LA side and we may get alarms like SAB simple or double
s
fault. In such case the GLR may be interrogated. The status shown may be
FLA. In such case we may have to check the SAB card and other cards which
issue the LA link ICTSH or ACHIL board in SMA, ICTRQ card in SMT and or
TCILR or some logic card in CSNL.
The suspected card in CSN, SMT or SMA can be changed and following
command may be executed:-
@ GLRCT :
@ AFGRU = CSN NO - GLR NO or
AFGRT = SMT - GLR NO or
AFGRA = SMT - GLR NO or
-94-
AFGRX = SMT - GLR
As long as fault persists GLRCT will keep on accusing the GLR as FLA LX faults can be
cleared by systematically following the procedure iof changing related cards one by one.
Flow charts for GLR and SAB faults are given in fig. 11, 12, 13 & 14.
-95-
GLR – SIMPLE / GLR – DOUBLE FAULT
Y Alarm
ALAIL dictionary data
A1
sheet
List
A2
GLR
TELIN
Alarm
A3 dictionary data
sheet
Y
Diag ? Repair A5
N
A4
Alarm
dictionary data
sheet
Y Alarm ?
N
END
Fig. 11
-96-
Case of SAB Single or Double fault Alarms
START
GLR Alarm
A1 ETU dictionary data
alarms ?
Y sheet
A3 GLRC
N
STAT = FLA ?
A4 Note
address
Switch over
A5
CSNL
Switch over
SMT
GLRCT
N
STAT= LA
A6 LOCAVAR SMX
N 0
ENDDiag. ? FEX
Maintenance
of stations
E1 . figure
E1 . figure E1 . figure
Fig 12
-97-
E2
E3
LOCAVAR
A7 SMT-SMA-CSNL
Y FEX
Diag ? Maintenance
of stations
N
Change board
A81 ICID or
TCBTL
GLRCT
N
A4 STAT = FLA ?
Y
A82 Change board
SMA/SMT/CSNL
A9 GLRCT
N
STAT= FLA
A 10 0
Y
SAB alarm ? Repair ?
N
0 N
FIG. 13
-98-
E4
GLRLCT without
A111
SMTA
N
STAT=FLA ?
N
A1111 Change board
ICID
STAT=FLA ?
Isolate SMTB
END
GLRCT without
A112
SMTB
Y
STAT=FLA ?
N Change board
A1112 ICID
STAT=FLA ?
Isolate SMTA
E3, figure 2
START END
-99-
Fig. 14
s
NOTE: Routing locavar on SM are not suggested as central defence does this when
required Manual locavar therefore is run as a corrective measure. System has
provision for running locavar periodically (Once in 24 hrs.) on stand by station.
Locavar on ETU :
PCM related fault usually will point to fault in ICTRQ board. As a corrective measure
s
locavar may have to be run on ICTRQ boards i.,e. ETU .
@ ETUTL :
@ AM = SMT NO, ETU = ETU NO;
If diagnostic is there then change the ICTRQ board and again run locavar.
s
On getting no diagnostic restore the LR and circuits to normal.
Locavar on CSN :
Locavar on CSN manually is again required to be run as a corrective maintenance measure
usually central defence keeps on running locavar whenever some problem is encountered
and diagnostics are output on OPMN logical file
Manual locavar is not run on the CSN as a whole but on various sub assemblies as
discussed below:-
(b) CN
@ URTL:
@ AFCN = UR – CN, ENS = CN, TYM = CSN:
s
(c) UT
@ URTL:
@ AFCN = RU NO – CN NO, ENS = UTX, TYM = CSN:
s
(d) PCM of CSND
@ URTL :
@ AFUR = UR NO, ENS = MIC 0 to MIC 15,
TYM = CSN ;
(e) PCM of CNE
@ URTL:
@ AFCN = UR NO - CN NO, ENS = MIC0 to MIC 3,
TYM = CSN:
-101-
e.g. @ TELEMO ;
@ AFLR = 2 – 5, STTUS = INDL (UR – LR)
If the PCM happens to be 0 or 1 which carry COC channels then it should be ensured that at least
s
one the COC is active otherwise communication will not be possible.
Central defence being powerful locavar is automatically initiated by the defence whenever there
is some malfunction. The result of locavar is output or a terminal assigned to OPMN
logical file.
After changing the card accused by self locavar effectiveness of repair must be verified.
For control stations there is no separate repair command. The locavar command “SMTL”
can be used for checking the effectiveness of repair.
s
For CSN the diagnostic result gives one diagonostic number (N) and a diagnostic code
(DIAG) along with the name of the cards likely to be faulty in a decording order of
probability. After changing the card one by one in that order repair is initiated as
follows:
@ URTR :
@ AFUR = ......, TYM = CSN, DG = DIAG
N=.............;
-102-