2653 FAILURE IN THE HANDLING OF CONTROL FILES

Meaning
The Virtual Data Storing Device (VDS device) is not able to handle its control files TTSCOF or TTTCOF, or its parameter file VIPARA.

1.INFORMACION GENERAL: 1.1 Tener en cuenta que actualmente se tiene la CHU-0 y la CHU-1 en servicio por cada MSS, su correspondencia para Mediacin es (NOKIA-X): MSS01TR MSS01TR MSS02TR MSS02TR MSS03TR MSS03TR CHU-0 CHU-1 CHU-0 CHU-1 CHU-0 CHU-1 NOK-GSM NOK-GSM NOK-GSM NOK-GSM NOK-GSM NOK-GSM TRUJILLO1 TRUJILLO 2 TRUJILLO 3 TRUJILLO 4 TRUJILLO 5 TRUJILLO 6

1.2 Identificar en las alarmas activas o en el histrico la alarma 2653 a que CHU (0 1), para que disco(s) WDU (S: System B: Backup) se ha reportado:
ZAHO; ZAHO::NR=2653; ZAHP::NR=2653:2011-06-13; => ver todas las alarmas actuales => Ver alarma actual nmero 2653 => histrico de alarmas crticas pasadas (YYYY-

MM-DD)

<HIST> MSS02TR CHU-1-1 SWITCH 2011-06-03 00:56:58.06 *** ALARM VDS-0 VIDAST (4518) 2653 FAILURE IN THE HANDLING OF CONTROL FILES WDU SB 05E50000 R 11472d <HIST> MSS02TR CHU-0-0 SWITCH 2011-06-03 01:43:09.61 *** ALARM VDS-0 VIDAST (4564) 2653 FAILURE IN THE HANDLING OF CONTROL FILES WDU SB 05E50000 R 61d

IDENTIFY UNIT TYPE: CHU ... CHARGING UNIT WDU ... WINCHESTER DISK UNIT WS .... SYSTEM DISK WB .... BACK UP DISK WSB.... SYSTEM AND BACK UP DISK

2. PROCEDIMIENTO: 2.1 Identificar si alguno de los files: TTTCOF00.IMG TTSCOF00 tiene campo ATTR (atributo) en estado LOCKED (L DL) segn la CHU (0 1) y DISCO WDU (WS WB) identificado en el paso anterior: ZIWX:,CHU,0:WS,::TT%,%; ZIWX:,CHU,0:WB,::TT%,%; ZIWX:,CHU,1:WS,::TT%,%; ZIWX:,CHU,1:WB,::TT%,%;
=> => => =>
verificar estado de files TT%,% en CHU-0, WDU-S (SYSTEM) verificar estado de files TT%,% en CHU-0, WDU-B (BACKUP) verificar estado de files TT%,% en CHU-1, WDU-S (SYSTEM) verificar estado de files TT%,% en CHU-1, WDU-B (BACKUP)

< ZIWX:,CHU,0:WS,::TT%,%;
MSCi MSS02TR 2011-06-03 10:25:08 VOLUME CHU_00.DIR: 0 INITIALIZED 07-02-25 REL 5 DIRECTORY OF LIMIT 2 =============================================================== FILE NAME FILE FILE FILE DATA PAGE 1 VERSION NO LENGTH LENGTH CREATOR ATTR (H) (H) (DEC) (DEC) TTSCOF00 TTSCOF00 TTTCOF00 TTTCOF00 TOTALS .VDS 1 A 90112 90000 VF D .IMG 1 B 90112 90000 VF D .IMG 19 24F2 70144 70000 ?? D .IMG 18 25E4 70144 70000 ?? L 322560 322048 ( INCLUDING FIDS )

FREE LABELS IN DIRECTORY 22761 FREE BLOCKS IN DISK 123047287 ( 85 %) 60081 MB DISK SIZE 143638992 BLOCKS 70136 MB COMMAND EXECUTED

< ZIWX:,CHU,0:WB,::TT%,%;
MSCi MSS02TR 2011-06-03 10:28:45 VOLUME CHU_01.DIR: 0 INITIALIZED 07-02-25 REL 5 DIRECTORY OF LIMIT 2 =============================================================== FILE NAME FILE FILE FILE DATA PAGE 1 VERSION NO LENGTH LENGTH CREATOR ATTR (H) (H) (DEC) (DEC) TTSCOF00 TTSCOF00 TTTCOF00 TTTCOF00 TOTALS .VDS 1 A 90112 90000 VF D .IMG 1 B 90112 90000 VF D .IMG 2D 24F2 70144 70000 ?? D .IMG 18 25E4 70144 70000 ?? DL 322560 322048 ( INCLUDING FIDS )

FREE LABELS IN DIRECTORY 22761 FREE BLOCKS IN DISK 123047287 ( 85 %) 60081 MB DISK SIZE 143638992 BLOCKS 70136 MB COMMAND EXECUTED

NOTA: En el ejemplo anterior se observa los files: TTTCOF00.IMG con FILE VERSION=18 para ambos disco (WS y WB) de la CHU-0.

2.2 Usar como referencia los siguientes comandos para resetear el file identificado en el paso anterior (TTTCOF00.IMG con FILE_VERSION=18):
CHU 0:

ZIWS:,CHU,0:WS,::TTTCOF00,IMG,18,R,L:; ZIWS:,CHU,0:WB,::TTTCOF00,IMG,9A,R,L:;
CHU 1:

ZIWS:,CHU,1:WS,::TTTCOF00,IMG,18,R,L:; ZIWS:,CHU,1:WB,::TTTCOF00,IMG,18,R,L:;

2.3 Verificar que la alarma 2653 ya no se reporta como alarma activa. Notificar a CGM que Mediacin de conformidad de la normalizacin de los procesos de transferencia de los archivos de las CHUs afectadas.
ZAHO::NR=2653; ZAHO;

3.INFORMACION COMPLEMENTARIA Ejemplos : ZIFO:CHU,0:GSMCHA::; ZIFO:CHU,1:GSMCHA::; ZIFO:CHU,0:GSMCHA:,FULL,; ZIFO:CHU,1:GSMCHA:,FULL,; ZIFI:CHU,0:GSMCHA:S:; ZIFI:CHU,1:GSMCHA:S:; ZIFO:CHU,0:GSMCHA:6738,; ZIFS:CHU,0:GSMCHA:6738,FULL:T:; ZIFS:CHU,0:GSMCHA:6738&&7053,FULL:T:; => => => => => => =>
verificar verificar estados de los charging files en CHU-0 verificar estados de los charging files en CHU-1 verificar Charging Files en FULL para CHU-0 verificar Charging Files en FULL para CHU-1 verificar current fill up ratio < 50% para CHU-0 verificar current fill up ratio < 50% para CHU-1

el estado del charging file 6738 en CHU-0

Cambiar el charging file 6738 de FULL a TRANSFERRED en CHU-0 => Cambiar los charging files 6738 al 7053 de FULL a TRANSFERRED en CHU-0

=>

2653 FAILURE IN THE HANDLING OF CONTROL FILES

Meaning
The Virtual Data Storing Device (VDS device) is not able to handle its control files TTSCOF or TTTCOF, or its parameter file VIPARA.

This may be caused by a fault in the hard disk or a break in the data storing chain. If the saving of TTSCOF (.IMG) fails, it means that the postprocessing system does not receive correct (up-to-date) information on the state of the data files in the VDS device. The postprocessing system receives the information that it requires for the transfer when the TTSCOF has been successfully saved on the disk again. However, if the fault is not corrected, the disk file group of the VDS device will start to fill up because the postprocessing system does not know which data files can be transferred. Because of this, data may be lost when the disk file group,which functions as a ring file buffer for the VDS device, fills up.
Supplementary information fields

application identifier for example: GENE00 (= GENERAL VDS DEVICE) OBSERV (= OBSERVATION REPORTS) MEASUR (= MEASUREMENT REPORTS)

number of the file in whose handling the error occurred for example: 05E30000 (= VIPARA) 05E40006 (= TTSCOF variant 6) 05E5000A (= TTTCOF variant 10)

failed file operation: R = an attempt was made to read from the file W = an attempt was made to write to the file T = an attempt was made to write the TTSCOF (.IMG) used for transmitting files this field has no meaning in IPA2800 network elements. FF = faulty device is not known (status is the general error code of the event)

5 general error message of the system. You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or in the document General Error Messages of System, Supplementary References. (Note: This field only indicates the situation when the fault first occurred. The cause for the fault may change during subsequent storing/reading without setting a separate alarm.)

Instructions
1. Check with the MML command AAP what other alarms associated with the disk system are active. They may be helpful in finding the fault. Also check the obtained logs with the service terminal command ZGD or ZGS. Note that when using service terminal commands, the session should be connected to the unit that is giving the alarm. 2. Avoid restarting the active unit or making a switchover until the fault has been corrected, because during those actions, the files in

question are read from the hard disks and the old data there may cause the data stored on the VDS device to be overwritten. 3. If the file in question is VIPARA, check if the REQMAN program block is operating with the service terminal commands ZOH and ZOHM. The process identifier of the REQMAN can be detected with the service terminal command ZSXP. For example ZSXP:REQ For example ZOH:95 For example ZOHM:95 Also check if the process has crashed with the service terminal command ZSLP. For example ZSLP:95 If the program blocks are not operating or if they have crashed, contact the local Nokia Customer Service Center. For more information see also the following alarm descriptions: - VDS device threshold alarms for charging applications: 2549 FIRST ALARM LIMIT FOR UNAVAILABLE VDS-DEVICE DATA FILES REACHED 2550 SECOND ALARM LIMIT FOR UNAVAILABLE VDS-DEVICE DATA FILES REACHED 2551 OUT OF AVAILABLE VDS-DEVICE DATA FILES - VDS device threshold alarms for other than charging applications: 2731 FIRST THRESHOLD VALUE FOR RING DISK FILE SYSTEM EXCEEDED 2732 SECOND THRESHOLD VALUE FOR RING DISK FILE SYSTEM EXCEEDED 2733 NO FREE RING DISK FILE - other alarms of the VDS device: 2386 OVERWRITING UNTRANSFERRED RING FILE 2651 STORING OF THE DATA FAILED ON BOTH DISKS 2652 PHYSICAL DISK IS FULL

Cancelling
Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected (when the operation in question (write/read) of the said file is successful again).