Replacing Storage Devices: dn03430759 Issue 2-1 en # Nokia Corporation Nokia Proprietary and Confidential 1

Replacing Storage Devices
dn03430759 # Nokia Corporation 1 (44)

Issue 2-1 en Nokia Proprietary and Confidential
The product described in this document is still under development by Nokia Networks. However,
in the interest of offering early possibility to our customers to evaluate the documentation, this
documentation is provided in draft form. Therefore the customer understands that the
information in this document is subject to change without notice and describes only the prototype
product defined in the introduction of this documentation in its current state of development.
Nokia Networks welcomes customer comments as part of the process of continuous
development and improvement of its products and the documentation.
This document is not a final customer document and Nokia Networks does not take
responsibility for any errors or omissions in this document. No part of it may be reproduced or
transmitted in any form or means without the prior written permission of Nokia Networks. The
document has been prepared to be used by professional and properly trained personnel, and the
customer assumes full responsibility when using it.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding but
shall be defined in the agreement made between Nokia Networks and the customer.
Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING
MONETARY LOSSES), that might arise from the use of this document or the information in it.
UNDER NO CIRCUMSTANCES SHALL NOKIA BE RESPONSIBLE FOR ANY LOSS OF USE,
DATA, OR INCOME, COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES,
PROPERTY DAMAGE, PERSONAL INJURY OR ANY SPECIAL, INDIRECT, INCIDENTAL,
PUNITIVE OR CONSEQUENTIAL DAMAGES HOWSOEVER CAUSED.
THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED
BY APPLICABLE MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT,
ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THIS
DOCUMENT. NOKIA RESERVES THE RIGHT TO REVISE THIS DOCUMENT OR
WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE.
This document and the product it describes are protected by copyright according to the
applicable laws.
NOKIA and Nokia Connecting People are registered trademarks of Nokia Corporation. Other
product names mentioned in this document may be trademarks of their respective companies,
and they are mentioned for identification purposes only.
Copyright © Nokia Corporation 2006. All rights reserved. Reproduction, transfer, distribution or
storage of part or all of the contents in this document in any form without the prior written
permission of Nokia is prohibited.
2 (44) # Nokia Corporation dn03430759

Nokia Proprietary and Confidential Issue 2-1 en
Contents
Contents
Contents 3
List of tables 4
List of figures 5
Summary of changes 7
1 Overview of storage devices 9

1.1 Replacement of WDUs 9
1.2 Replacement of CTUs and FDUs 12
1.3 Replacement of MOs 12
1.4 I/O devices 13
2 Preventing and resuming updates of disks and memory file disk

copies 15
2.1 Preventing updates of disks and memory file disk copies 15
2.2 Resuming updates of disks and memory file disk copies 16
3 Formatting a hard disk unit (WDU) 17
4 Replacing a hard disk unit (WDU) 23
5 Replacing a removable disk unit (FDU) 33

5.1 Replacing an FDU in OMU, STU, and ACU 33
6 Replacing a cartridge tape unit (CTU) 37

6.1 Replacing a CTU in OMU, STU, and ACU 37
7 Replacing terminators and cables 43

List of tables
Table 1. Maximum amount of bad blocks 11

Table 2. I/O devices on SCSI-0 and SCSI-1 buses 13

List of figures
List of figures


Summary of changes
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes made between issues 21 and 20
In Chapter Replacing a hard disk unit (WDU) , a command has been corrected in
Step Copy the system disk (WDU-1) to backup disk (WDU-0), including
subdirectories, using the default and active build directory name AS9_9_18_0' .
Changes made between issues 20 and 11
The following changes have been made:
.
The title of the document has been changed from Replacing Mass Memory
Units to Replacing Storage Devices. It has been corrected throughout the
document.
. The disk capacity in Table Maximum amount of bad blocks has been
increased to 73 GB. A new hard disk unit is used, the WDW73.
. Replacement of MOs and I/O devices are introduced in Section Overview
of storage devices.
. How to replace a removable disk unit (FDU) has been introduced through
an example.
Changes made between issues 1-1 and 1-0
Minor editorial changes.


Overview of storage devices
1 Overview of storage devices

The change of storage devices is related to the following units:
WDU hard disk unit
FDU removable disk unit (floppy disk or magneto-optical disk)
CTU cartridge tape unit
The instructions given for replacing adapters and cables connected to the storage
devices are examples, and when performing these procedures, you have to
modify the examples to suit your situation, for example, by giving the correct
index number.
1.1 Replacement of WDUs

Hard disks and Magneto-Optical (MO) disks function as the storages of the
software (SW) system. They restore the information of the system in case of a
restart.
The Operation and Maintenance Unit (OMU) always contains two hard disks,
and there are hard disks in STU and ACU as well.
Hard disks do not need periodic maintenance, they need to be serviced only in
failure situations.
The hard disk unit is equipped to storage devices at cartridge (M92, DXT256), or
to computer cartridge (M98, DXTip) using an appropriate adapter which can be
changed with the unit at the same time. The adapter is used only in cartridge
construction, not in subrack construction.
Hard disk units (WDUs) of the system are used to store, for example, the
following data:

. program codes and loadable files of the computer units

. MML programs
. menus
.
statistics and charging data
. safecopies of software builds
.
databases
. alarm and recovery files
Before replacing the WDU, stop all activities on the Small Computer System
Interface (SCSI ) bus where you make the changes.
For safety reasons, the hard disk units are always backed up. They are called
system disk unit and backup unit. Normally, the data in the units is identical, and
the system writes to both units. The system disk unit is read first, while the
backup unit is read only if reading from the system disk unit fails.
When a failure occurs in a hard disk unit, the I/O system blocks the faulty unit
from use. If the faulty unit is active, the backup unit becomes the system disk
unit.
Formatting and initialising a new hard disk unit is slow. Therefore, keep a new
hard disk unit that is already formatted and initialised as a spare unit. If this is not
the case, the disk unit should be changed, whenever possible, when it is not being
used by the system (for example, during night hours). Even if the hard disk is
already initialised, it is still recommended that the change is done during a low
traffic period.
Note
Verify that an approximately two-hour break is possible in disk operations. The

duration of the break depends on the amount of data to be copied, the version of
the software build, and the hardware. If the disk is not initialised, the duration
also depends on the capacity of the disk.
Terminal resistor
In SCSIF environment, the terminal resistor is not allowed on the disk.

Bad blocks
You should always have an initialised spare WDU at your disposal. The spare
unit can be initialised, for example, in the test laboratory before it is installed in
the actual unit.
The maximum amount of bad blocks of a WDU is shown in Table Maximum

amount of bad blocks. The Primary list (P-list) shows the bad blocks detected
already in the disk factory. You can fetch the P-list with, for example, the Service
Terminal MAS-command BLP. The Grown list (G-list) shows the bad blocks
detected in use. You can fetch the G-list with, for example, the Service Terminal
MAS-command BLG.
Table 1. Maximum amount of bad blocks
Disk P-list max. G-list max. G-list max. Note

capacity length length growth/
month
4 GB 1000 20 4
9 GB 1000 20 4
18 GB 1500 30 6
36 GB 1500 30 6
73 GB 1500 30 6
You can also use the IWB MML command to output the bad block lists.
Hard disk (HDPU-A)
When you push the push button on the HDPU-A front panel for two seconds,
then the input supply voltage of the HDPU-A is cut off and the red LED lights up
(this button is only for cutting off input supply voltage; it does not switch power
on).
Power on: the input supply voltage connects to the HDPU-A, the cartridge's
power supply plug-in unit turns off and then turn on again.
If it is not possible to turn the power off (cartridge), then the HDPU-A is taken
out from the powered cartridge and then inserted again into it.
The red LED also lights on if the fuse of the input supply voltage (+5 V DC) is
blown or the supply voltage +12 V DC is missing.

1.2 Replacement of CTUs and FDUs

The Cartridge Tape Unit (CTU) is used for backup copying a network element
(for example, software) and for storing network element data (for example,
charging data). The CTU is a Digital Audio Tape (DAT) recorder.
The adapter is used only in cartridge construction, not in subrack construction.
The CTU and the removable disk unit (FDU) are equipped to storage devices at
cartridge (M92, DXT256) or to computer cartridge (M98, DXTip) using an
appropriate adapter which can be changed with the unit at the same time.
Note
The CTU is in use only in M92 and DXT256.
Before replacing the disk unit, stop all activities on the SCSI bus where you are
making changes.
1.3 Replacement of MOs
Note
In the instructions for Replacing Storage Devices, the MO unit is referred to as an

FDU.
The MOs are connected to adapters which can be changed with the unit at the
same time. The adapter is used only in cartridge construction, not in subrack
construction.
Before replacing the disk unit, stop all activities on the SCSI bus where you are
making changes.
For more information, see Replacing a removable disk unit (FDU).

1.4 I/O devices

The following I/O devices are connected to the SCSI-0 and SCSI-1 buses:
Table 2. I/O devices on SCSI-0 and SCSI-1 buses
SCSI-0 SCSI ID SCSI-1 SCSI ID
WDU-0 0 WDU-1 0
CTU-2 1 CTU-3 1
FDU-0 2 FDU-1 2
CTU-0 3 CTU-1 3


Preventing and resuming updates of disks and memory file disk copies
2 Preventing and resuming updates of

disks and memory file disk copies
To make sure that no data is lost when changing disks, first prevent disk updates,
and updates of memory file disk copies (Database Handling, DB Command
Group and Disk Update Handling, DU Command Group ). After the change is
completed, you can resume them.
For general information on storage devices, see Overview of storage devices.
2.1 Preventing updates of disks and memory file disk

copies
To make sure that no data is lost when changing disks, prevent disk updates and
the updates of memory file disk copies first before changing them.
Note
If the other disk is broken, you cannot prevent the updates of memory file disk
copies by giving the DUP command. Start from step List the databases (DBL).
Steps
1. Prevent the updates of memory file disk copies (DUP)
If you change the disk of ACU, you only need to prevent updates of the
unit in which the replaced disk exists. In case of an OMU disk change,
prevent all disk updates.
ZDUP:<unit>;
2. List the databases (DBL)

ZDBL;
3. Prevent disk updates of the databases (DBP)
If you change the disk of ACU, you only need to prevent updates of the
unit in which the replaced disk exists. In case of an OMU disk change,
prevent all disk updates.
ZDBP:<database name>,<occurrence>:DISK;
2.2 Resuming updates of disks and memory file disk

copies
Before you start
After you have changed the disks, remember to resume the disk updates and the
updates of memory file disk copies if you have prevented them before the change.
Steps
1. Resume updates of memory file disk copies (DUR)
ZDUR:<unit>;
2. Resume disk updates of databases (DBR)
ZDBR:<database name>,<occurrence number>:DISK;

Formatting a hard disk unit (WDU)
3 Formatting a hard disk unit (WDU)

The WDU is always equipped to cartridge by using an appropriate adapter. When
you change the WDU, you can change the adapter at the same time. For more
information on adapters, see Replacing terminators and cables.
This section shows how to format and initialise a WDU.
Keep a formatted spare unit at your disposal so that it can be changed if one of the
WDUs becomes faulty.
Formatting a spare WDU includes:
1. removing a WDU from the exchange

2. replacing it with a spare WDU
3. formatting the spare WDU
4. removing the formatted WDU
5. putting back the original WDU
Before you start
Before replacing the WDU, stop all activities on the SCSI bus where you are
making changes.
Note
Keep an initialised WDU at your disposal. This speeds up the maintenance task.
Steps
1. Prevent disk updates and updates of memory file disk copies

For more information, see Preventing and resuming updates of disks and
memory file disk copies.
2. Block the WDU to be removed (ISC)
ZISC:,<destination unit>:<I/O device type>,<I/O

device index>:<working state>;
3. Block other I/O devices on the SCSI bus of the WDU (ISC)

4. Remove the WDU

.
Remove the WDU from the storage devices at cartridge:
a. Switch off the power. Wait until disk rotation stops.
b. Remove the WDU.
. Remove the WDU from the computer cartridge:
a. Shut down the power with the button of the HDPU-A front
panel or the cartridge's power supply unit.
b. Remove the unit from the cartridge.
c. Check the interchangeability of the spare unit: the
interchangeability code of the new plug-in unit has to be the
same or newer. If it is newer, check the effects on
interchangeability of the units.
5. Check the strappings of the new (spare) WDU
6. Install the new WDU

. Install the WDU to the storage devices at cartridge:
a. Install the new WDU.
b. Switch on the power.
.
Install the WDU to the computer cartridge:
a. Insert the spare unit to the cartridge.
b. Switch on the cartridge power supply.
7. Change the state of the WDU to WO-ID (ISC)
ZISC:,<destination unit>:<I/O device name>,<I/O


8. Initialise the WDU (IWI)
ZIWI:,<destination unit>:<drive>,<system release

format>,<volume label>,<file count>,<version
limit>,<initials>;
9. Block the initialised WDU (ISC)

device index>:BL-US;
10. Remove the initialised WDU

. Remove the WDU from the storage devices at cartridge:
a. Switch off the power. Wait until disk rotation stops.
b. Remove the WDU.
a. Shut down the power with the button of the HDPU-A front
panel or the cartridge's power supply unit.
b. Remove the unit from the cartridge.
c. Check the interchangeability of the spare unit: the
interchangeability code of the new plug-in unit has to be the
same or newer. If it is newer, check the effects on
interchangeability of the units.
11. Put back the old WDU

. Install the WDU to the storage devices at cartridge:
.
Install the WDU to the computer cartridge:
a. Insert the spare unit to the cartridge.
b. Switch on the cartridge power supply.
12. Change the state of the WDU first to WO-ID, then to WO-BU (ISC)

13. Change the states of other I/O devices on the SCSI bus of the WDU
(ISC)
Change the states of:

. WDUs and FDUs to WO-BU

. CTUs and MTUs to WO-ID (if there is no tape in the unit, it remains
in BL-SY state).
Use the ISC command as shown above.
14. Resume database updating and file updating
For more information, see Resuming updates of disks and memory file disk
copies.
15. Output the active alarms (AHO)
ZAHO;
Further information:
Example 1. Formatting a WDU
In this example, OMU's WDU-0 is removed.
1. Prevent updates of memory file disk copies.
ZDUP:OMU;
2. Prevent disk updates of databases.
ZDBP:EQUIPM,0:DISK;
3. Block OMU's WDU-0.
ZISC:,OMU:WDU,0:BL-US;
4. Block other I/O devices on the SCSI bus of the WDU.
5. Remove the WDU.
6. Check the strappings of the new (spare) WDU.
7. Install the spare WDU.
8. Change the state of OMU's WDU-0 to WO-ID.
ZISC:,OMU:WDU,0:WO-ID;
9. Format and initialise the WDU.
ZIWI:,OMU:WB,F5,NAME,FFF,2,NN;

11. Remove the initialised WDU.
12. Put back the old WDU.
13. Change the state of the OMU's WDU-0 first to WO-ID and then to WO-
BU.
ZISC:,OMU:WDU,0:WO-BU;
14. Change back the states of other I/O devices on the SCSI bus of the WDU.
15. Resume updates of memory file disk copies.
ZDUR:OMU;
16. Resume disk updates of databases.
ZDBR:EQUIPM,0:DISK;
17. Output the active alarms.
ZAHO;


Replacing a hard disk unit (WDU)
4 Replacing a hard disk unit (WDU)

The process of changing a WDU in other units than STU and CHU is described
below:
When you replace the WDU, you can change the adapter at the same time. For
more information on adapters, see Replacing terminators and cables.
Before you start
Before replacing the WDU, stop all activities on the SCSI bus where you are
making changes.
Note
Always have an initialised WDU at your disposal.
Steps
1. Check if you have a new formatted and initialised WDU
2. Interrogate the states of the WDUs (USI)
ZISI:,OMU:WDU; , or ZISI:,ACU:WDU , or ZISI:,STU:WDU;
where the unit type is WDU. The right state of both WDUs is WO-BU.
Use the following command to see which one is active:
ZIWQ:,OMU:WB=0;
OLD CONFIGURATION OF DISKS IN DX220-LAB

OMU WS= 0, WB= 1

where WDU-0 is active and WDU-1 is backup.
3. Dump the data files from OMU, ACU, and STU to disks of OMU
. If you are replacing WDU of OMU, dump the data files of OMU,
CM, EDU, and CCC to disk of OMU
ZDFC:OMU;
ZDFC:CM,0;
ZDFC:EDU,0;
ZDFC:CCC,0;
Copy databases from memory to disk:
ZDBC:EQUIPM,0;
ZDBC:OEDATA,0;
ZDBC:TXDATA,0;
ZDBC:TNDATA,0;
ZDBC:RDDATA,0;
ZDBC:VUDATA,0;
. If you are replacing WDU of ACU, dump the data files of ACU to
disk of ACU
ZDFC:ACU,0;
Copy databases from memory to disk:
ZDBC:SXDATA,0;
ZDBC:ENGINE,0;
ZDBC:THSDAT,0;
. If you are replacing WDU of STU, dump the data files of STU to
disk of STU
ZDFC:STU,0;
There are no databases in STU.
4. Prevent file updates and disk updates of databases
For more information, see Preventing and resuming updates of disks and
memory file disk copies.
If the other disk is broken, you cannot prevent updates of memory file disk
copies by giving the DUP command.

5. Check if all databases have been unpacked from the disk log to the
disk database (DBX)
The command unpacks the disk logs if they are not empty.
ZDBX:<database name>,<occurrence>;
6. Block the WDU you are changing (ISC)

7. Block the other I/O devices on the same unit pair's SCSI bus (ISC)

8. Check if the state of the hard disk to be replaced is correct (BL-US)

(ISI)
ZISI:,<destination unit>:<I/O device type>,<I/O

device index>;
9. Remove the WDU

. Remove the WDU from the storage devices at cartridge:
a. Switch off the power. Alarm 2870 MASS MEMORY
POWER SUPPLY FAILURE can be printed out. Wait until
disk rotation stops.
b. Remove the WDU.
a. Switch off the power by pressing the 'POWER OFF' button
and wait for about seven seconds, until the 'OFF' led is on.
b. Remove the WDU unit from the cartridge.
Note
Power switching differs depending on which DXT model is in question.

. DXT256 uses WDDC-cartridge, disk/power card relations are
described below:
WDU 0 -> PSC4 0
WDU 1 -> PSC4 1

. DXTip uses computer cartridges, disk/power card relations are

described below:
WDU 0, WDU 1 (OMU's own power PSC6-A)
WDU 0 (ACU 0 and STU 0's own power unit PSC6-A)
WDU 1 (ACU 1 and STU 1's own power unit PSC6-A)
.
OMU and ACU are installed with cartridge (CM2C-A), and STU is
installed with CC3C-A in DXTip. The power switch is integered
directly to the front panel of the winchester adapter.
10. Fit the Storage Device plug-in units in computer cartridges
See the instructions on the Installation of DXT or DXTip .
11. Check the strappings of the new WDU, FDU of MO91
See the instructions on the Installation of DXT or DXTip .
12. Install the new WDU

. Install the new WDU to the storage devices at cartridge:
. Install the new WDU to the computer cartridge:
a. Install the WDU to the cartridge (the 'OFF' led is on
immediately) and wait for about three seconds until the 'OFF'
led is off.
13. Change the state of the new WDU to WO-ID (ISC)

For more information on formatting the disk, see Formatting a hard disk
unit (WDU).
14. Change the states of other I/O devices on the same SCSI bus (ISC)
Change the states of FDU and CTU:

. FDUs and WDUs to WO-BU
. CTUs to WO-ID

15. Check if the new disk is the backup disk (WB) (IWQ)
ZIWQ:,OMU:WB=0;
16. Diagnose the WDU (UDD)
In case of STU and ACU:
ZUDD:<main unit type>,<main unit index>:<device

type>,<device index>;
In case of OMU:
ZUDD:<main unit type>:<device type>,<device index>;
Expected outcome
If the diagnosis is successful, you can see the diagnostic report 3999
DIAGNOSIS EXECUTED - UNIT OK output to the alarm printer.
17. Change the working state of the new WDU to WO-BU (ISC)

18. Copy the system WDU to the new WDU (IPS)
ZIPS:<source unit>,<source I/O device>,<source

path>,,:,<destination I/O device>,<destination
path>,:<directory mode>,<copy task name>;
Note
If you also want to copy other than the default versions, use the <source file
version> parameter and give it the 'FF' value:
ZIPS:<source unit>,<source I/O device>,<source path>,,

FF:,<destination I/O device>,<destination path>,:
<directory mode>,<copy task name>;
The copying is now carried out in the background.

Check the progress of the copy task to see when it is ready. Ensure that the
copy task is in the SUCCESS state before continuing.
ZIPI:NAME=<copy task name>;
If the copy task does not change into the SUCCESS state, but remains for
example in the FAILED state, it is not possible to continue until the fault is
corrected.
19. Change the working state of the new WDU to WO-BU (ISC)
ZISC;,<destination unit>,<pair>:<I/O device type>,

<I/O device index>:<working state>
20. Destroy GEORGE
Use the OD service terminal command to prevent the log files of 'Q3
Disseminator' from getting corrupted.
ZOD:2B1
21. Remove LOGRECS* files from the disks LFILES on both OMU disks
Use the MD service terminal command in order to maintain the required

syncronisation status between DEEGUT and GEORGE during the hard
disk change.
ZMD:W0-/<used directory name>/LFILES/LOGR*.*
22. For copying empty DWOFILGX.IMG to LFILES, you have the

following alternatives:
. Copy empty DWOFILGX.IMG to LFILES from DAT tape.
ZMM:<DAT drive>-/<SW_release_package_directory_name>/
LFILES/DWOFILGX.IMG,DW0-/<used directory name>/LFILES/,
<SW_packet_file_set_name>
.
Copy empty DWOFILGX.IMG to LFILES directory from floppy
disk.
ZMM:F0-/DWOFILGX.IMG,DW0-/<used directory name>/
LFILES/

Note
Steps 1921 are true only when replacing the hard disk of the OMU.
23. Restart OMU (USU)
ZUSU:OMU,0:C=DSK;
24. Resume updates of disks and memory file disk copies of the databases
you prevented before changing the WDU
copies.
25. Copy the data from database to disk (DBC)
The databases you need to copy are those of the WDU's computer unit.
Copy the data from all the unit's databases in the same way.
ZDBC:<database name>,<occurrence>;
If copying is not successful, check the state of the database in the following
step.
26. Check if the database states are restored to 'normal' or 'dumping'

(DBS)
ZDBS:<database name>,<occurrence>;
The command displays the states of the databases.
27. Check if the states of the hard disks are corrected (WO-BU) (ISI)

device index>;
28. Check if the states of the units are correct (WO-EX, SP-EX) (USI)
ZUSI:<unit type>,<unit index>;
Example 2. Changing OMU's WDU-0

1. Check the state of OMU.
ZUSI:OMU;
The command prints out the working state of OMU.

2. Copy the data from memory to disk.
ZDFC:OMU;
3. Copy the data from all the unit's databases to disk, for example, OMU's
EQUIPM-0.
ZDBC:EQUIPM,0;
4. Prevent updates of memory file disk copies.
Note
If the other disk is broken, you cannot prevent updates of memory file disk copies
by giving the DUP command. Go to step Prevent disk updates of databases, for
example, EQUIPM-0.
ZDUP;
5. Prevent disk updates of databases, for example, EQUIPM-0.
ZDBP:EQUIPM,0:DISK;
6. Check if all databases have been unpacked from the disk log to the disk
database.
ZDBX:EQUIPM,0;
8. Block the other I/O devices on the same unit pair's SCSI bus.
9. Change the WDU.
10. Change the state of the OMU's WDU-0 to WO-ID.
11. Change the states of other I/O devices on the same SCSI bus in the same
way.
12. Check if the new disk is the backup disk (WB).

ZIWQ:,OMU:WB=0;
13. Format OMU's WDU-0.
ZIWI:,OMU:WB,F5,<volume label>,FFF,2,nn;
14. Change the working state of the new WDU from WOID to TE-ID.
ZISC:,OMU:WDU,0:TE-ID;
15. Diagnose OMU's WDU-0.
ZUDD:OMU:WDU,0;
16. Change the working state of WDU-0 to WO-BU.
17. Copy the system disk (WDU-1) to backup disk (WDU-0), including
subdirectories, using the default and active build directory name
'AS9_9_18_0'. Name the task as 'COPY'.
ZIPS:OMU,WDU-S,/AS9_-_18_0,:,WDU-B,/,:DIR=INC,
ISD=Y,NAME=COPY;
Check the progress of the copy task. Ensure that the copy task is in the
SUCCESS state before continuing.
ZIPI:NAME=COPY;
18. Destroy GEORGE.
Use the OD service terminal command to prevent the log files of 'Q3
Disseminator' from getting corrupted.
ZOD:2B1
19. Remove LOGRECS* files from the disks LFILES on both OMU disks.
Use the MD service terminal command in order to maintain the required
syncronisation status between DEEGUT and GEORGE during the hard
disk change.
20. For copying empty DWOFILGX.IMG to LFILES, you have two
alternatives:
.
Copy empty DWOFILGX.IMG to LFILES from DAT tape.
ZMM:<DAT drive>-/<SW_release_package_directory_name>/
LFILES/DWOFILGX.IMG,DW0-/<used directory name>/LFILES/,
<SW_packet_file_set_name>

. Copy empty DWOFILGX.IMG to LFILES directory from floppy

disk.
ZMM:F0-/DWOFILGX.IMG,DW0-/<used directory name>/
LFILES/
ZDUR;
22. Resume disk updates of the databases, for example, EQUIPM-0.
ZDBR:EQUIPM,0:DISK;
23. Copy the data from all the unit's databases to disk, for example, OMU's
EQUIPM-0.
ZDBC:EQUIPM,0;
24. Check if the database states are restored to 'normal' or 'dumping', for
example, EQUIPM-0.
ZDBS:EQUIPM,0;
25. Check the states of OMU's hard disks.
ZISI:,OMU:WDU;
26. Check the state of OMU.
ZUSI:OMU;

Replacing a removable disk unit (FDU)
5 Replacing a removable disk unit (FDU)

The FDU is connected to an adapter. When you change the unit, you can change
the adapter at the same time.
For more information on adapters, see Replacing terminators and cables.
Before you start
Before replacing the FDU, stop all activities on the SCSI bus where you are
making changes.
In DXTip the FDU is MO disk.
5.1 Replacing an FDU in OMU, STU, and ACU

Steps
1. Change the state of the FDU into Testing (ISC)

device index>:<working state>,FCD;
2. Block the I/O devices on the same SCSI bus

3. Change the states of the I/O devices on the SCSI bus into BL-US (ISC)
You have to change the states of all the possible devices (WDU, FDU,
CTU) separately.
ZISC:,<destination unit>,<pair>:<I/O device type>,

<I/O device index>:<working state>;

4. Remove the FDU

. Remove the FDU from the storage devices at cartridge:
a. Switch off the power.
b. Remove the FDU.
. Remove the FDU from the computer cartridge:
a. Switch off the power by pressing the 'POWER OFF' button
and wait for about seven seconds until the 'OFF' led is on.
b. Remove the FDU unit from the cartridge.
5. Check the strappings of the new FDU
6. Install the new FDU

. Install the FDU to the storage devices at cartridge:
a. Install the new FDU.
. Install the FDU to the computer cartridge:
a. Install the FDU to the cartridge ('OFF' led is on immediately)
and wait for about three seconds until the 'OFF' led is off.
7. Replace the FDU
8. Change the states of the I/O devices on the SCSI bus into Working
(ISC)
You have to change the states of all the possible devices (WDU, FDU,
CTU) separately.

9. Diagnose the FDU (UDD)
ZUDD:<main unit type>,<pair>,<main unit index>:

<device type>,<device index>;
10. Change the state of the FDU into Working (ISC)


Replacing a removable disk unit (FDU)
Example 3. Replacing FDU-0 in OMU
In this example, OMU's FDU-0 is changed.
1. Block FDU-0 in OMU.
ZISC:,OMU:FDU,0:BL-US;
2. Copy the data from database to disk.
ZDBC:EQUIPM,0;
3. Prevent updates of memory file disk copies and disk updates of databases.
ZDUP:OMU;
ZDBP:EQUIPM,0:DISK;
4. Check if all databases have been unpacked from the disk log to the
database.
ZDBX:EQUIPM,0;
5. Block other I/O devices on the same SCSI bus using the ISC command. It
is particularly important to block the WDU.
6. Remove the FDU.
7. Check the strappings of the new FDU.
8. Install the new FDU.
9. Insert a new floppy/MO disk into the FDU and wait for loading.
10. Change the state of FDU-0 to TE-ID.
ZISC::FDU,0:TE-ID;
11. Diagnose FDU-0 in OMU.
ZUDD:OMU,0:FDU,0;
12. Change the state of FDU-0 first to WO-ID and then to WO-BU.
ZISC::FDU,0:WO-ID;
ZISC::FDU,0:WO-BU;
13. Change the state of the OMU's WDU-0 first to WO-ID, then to WO-BU.

14. Resume updates of memory file disk copies and disk updates of databases.
ZDUR:OMU;
ZDBR:EQUIPM,0:DISK;

Replacing a cartridge tape unit (CTU)
6 Replacing a cartridge tape unit (CTU)

Note
This section is valid only in case of DXT256!
Instructions for replacing the Cartridge Tape Unit (CTU) are provided in this
section.
Before you start
The CTU is always equipped to cartridge using an appropriate adapter. When you
are changing the unit, you can change the adapter at the same time. For more
information on adapters, see Replacing terminators and cables.
6.1 Replacing a CTU in OMU, STU, and ACU

This section tells you how to change a CTU in OMU, STU, and ACU.
Steps
1. If there is a DAT/ tape in the drive, withdraw it by using the eject

button on the front panel of the CTU
2. Block the CTU (ISC)

3. Block other I/O devices on the same SCSI bus (ISC)


It is particularly important to block the WDU.
4. Remove the CTU
The correct way to do this depends on the type of the network element
(cartridge construction):
1. Switch off the power. Alarm 2870 MASS MEMORY POWER
SUPPLY FAILURE may be printed out.
2. Remove the CTU.
5. Check the strappings of the new CTU
6. Install the new CTU
The process depends on the type of the network element (cartridge

construction):
1. Install the new CTU.
2. Switch on the power.
3. Check if Alarm 2870 MASS MEMORY POWER SUPPLY
FAILURE is cancelled.
7. Insert a new DAT tape into the CTU and wait for loading
8. Change the state of the CTU to TE-ID (ISC)

Note
You do not need to do this if Alarm 2870 MASS MEMORY POWER SUPPLY
FAILURE was generated. The alarm automatically changes the state to TE-ID.
9. Diagnose the new CTU (UDD)
ZUDD:<main unit type>,<main unit index>:<device

type>,<device index>;

The diagnosis takes about two minutes. If the result is successful, you will
see the diagnostic report 3999 DIAGNOSIS EXECUTED - UNIT OK
output on the alarm printer.
10. Change the state of the new CTU to WO-ID (ISC)

To check the working states of I/O devices, you can use the ISI
command.

device index>;
For example, check the working states of all I/O devices of OMU:
ZISI:,OMU:;
11. Change the states of other I/O devices on the same SCSI-bus (ISC)
Change the states of:

.
FDUs and WDUs to WO-BU
. CTUs to WO-ID (if there is no tape in the unit, it remains in BL-SY
state)

12. Resume updates of disks and memory file disk copies of the databases
you prevented
copies.
13. Change the tape type, if necessary
If, for example, you are using the tape for backup copying, the tape type
should be DAT (default type). This is how you change the tape type.
Steps
a. Check the tape type (IMD)
ZIMD;

b. Change the tape type (IMS)
ZIMS:,<destination unit>:<tape unit

identifier>,<tape unit number>,<tape type>;
14. If you use the tape for storing SRL, mark the tape and open the tape
file (IMP)
This has to be done before you store data on the tape.
ZIMP:,<destination unit>,<pair>:<tape unit

identifier>,<tape unit>,,<check period of validity>,
<open tape file>;
Example 4. Changing CTU-0 in OMU
In this example, OMU's CTU-0 is changed.
1. If there is a DAT tape in the drive, withdraw it by using the eject button on
the front panel of the CTU.
2. Block CTU-0 in OMU.
ZISC:,OMU:CTU,0:BL-US;
3. Block other I/O devices on the same SCSI bus using the ISC command. It
is particularly important to block the WDU.
4. Change the CTU.
5. Check the strappings of the new CTU.
6. Insert a new DAT tape into the CTU and wait for loading.
7. Change the state of CTU-0 to TE-ID.
ZISC::CTU,0:TE-ID;
8. Diagnose CTU-0 in OMU.
ZUDD:OMU:CTU,0;
9. Change the state of CTU-0 to WO-ID.
ZISC::CTU,0:WO-ID;
10. Change the state of the OMU's WDU-0 first to WO-ID, then to WO-BU.

ZDUR;
12. Resume disk updates of databases.
ZDBR:EQUIPM,0:DISK;
13. Change the tape type of OMU's CTU-0 to DXDAT to store SRL.
ZIMS::CTU,0,DXDAT;
14. Mark the tape and open the tape file of CTU-0.
ZIMP::CTU,0,,Y,Y;


Replacing terminators and cables
7 Replacing terminators and cables

These instructions are for replacing the SCSI terminator, and the SCSI cables.
For instructions on changing the SCSIF plug-in unit, see Replacing a plug-in unit
in Replacing Plug-in Units.
Before you start
Before changing terminators or cables, stop all activities on the SCSI bus where
you are making changes.
Steps
1. Prevent database updating and file updating
ZDUP;
ZDBP:<database name>,<occurrence>:DISK;
2. Change the working state of all the SCSI devices of the bus you are
working on to the BL-US state (ISC)

device index>:BL-US;
3. Change the terminator/cable
4. Change the working state of the storage device to WO-BU (WDU and
FDU) or WO-ID (CTU )(ISC)


5. Resume file updating and database updating
ZDUR;
ZDBR:<database name>,<occurrence number>:DISK;


Replacing Storage Devices: dn03430759 Issue 2-1 en # Nokia Corporation Nokia Proprietary and Confidential 1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Replacing Storage Devices: dn03430759 Issue 2-1 en # Nokia Corporation Nokia Proprietary and Confidential 1

Uploaded by

Copyright:

Available Formats

Replacing Storage Devices

dn03430759 # Nokia Corporation 1 (44)

2 (44) # Nokia Corporation dn03430759

1 Overview of storage devices 9

2 Preventing and resuming updates of disks and memory file disk

3 Formatting a hard disk unit (WDU) 17

4 Replacing a hard disk unit (WDU) 23

5 Replacing a removable disk unit (FDU) 33

6 Replacing a cartridge tape unit (CTU) 37

7 Replacing terminators and cables 43

dn03430759 # Nokia Corporation 3 (44)

Table 1. Maximum amount of bad blocks 11

4 (44) # Nokia Corporation dn03430759

dn03430759 # Nokia Corporation 5 (44)

6 (44) # Nokia Corporation dn03430759

Changes made between issues 21 and 20

Changes made between issues 20 and 11

The following changes have been made:

Changes made between issues 1-1 and 1-0

Minor editorial changes.

dn03430759 # Nokia Corporation 7 (44)

8 (44) # Nokia Corporation dn03430759

1 Overview of storage devices

WDU hard disk unit

FDU removable disk unit (floppy disk or magneto-optical disk)

CTU cartridge tape unit

1.1 Replacement of WDUs

dn03430759 # Nokia Corporation 9 (44)

. program codes and loadable files of the computer units

Verify that an approximately two-hour break is possible in disk operations. The

In SCSIF environment, the terminal resistor is not allowed on the disk.

10 (44) # Nokia Corporation dn03430759

The maximum amount of bad blocks of a WDU is shown in Table Maximum

Table 1. Maximum amount of bad blocks

Disk P-list max. G-list max. G-list max. Note

Hard disk (HDPU-A)

dn03430759 # Nokia Corporation 11 (44)

1.2 Replacement of CTUs and FDUs

The adapter is used only in cartridge construction, not in subrack construction.

The CTU is in use only in M92 and DXT256.

1.3 Replacement of MOs

In the instructions for Replacing Storage Devices, the MO unit is referred to as an

For more information, see Replacing a removable disk unit (FDU).

12 (44) # Nokia Corporation dn03430759

1.4 I/O devices

Table 2. I/O devices on SCSI-0 and SCSI-1 buses

SCSI-0 SCSI ID SCSI-1 SCSI ID

dn03430759 # Nokia Corporation 13 (44)

14 (44) # Nokia Corporation dn03430759

2 Preventing and resuming updates of

For general information on storage devices, see Overview of storage devices.

2.1 Preventing updates of disks and memory file disk

1. Prevent the updates of memory file disk copies (DUP)

2. List the databases (DBL)

dn03430759 # Nokia Corporation 15 (44)

3. Prevent disk updates of the databases (DBP)

2.2 Resuming updates of disks and memory file disk

1. Resume updates of memory file disk copies (DUR)

2. Resume disk updates of databases (DBR)

ZDBR:<database name>,<occurrence number>:DISK;

16 (44) # Nokia Corporation dn03430759

3 Formatting a hard disk unit (WDU)

Changes made between issues 21 and 20

Changes made between issues 20 and 11