replacing wdu
TRANSCRIPT
Changing of Mass Memory Units
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
1 (72)
MSCDOCM12NEDM12 Product Documentation
The information in this documentation is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia's customers only for the purposes of the agreement under which the documentationis submitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The documentation has been prepared to be used byprofessional and properly trained personnel, and the customer assumes full responsibility whenusing it. Nokia welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the documentation areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.
Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or theinformation in it.
This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.
Copyright © Nokia Corporation 2003. All rights reserved.
2 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
Contents
Contents 3
List of tables 4
List of figures 5
Summary of changes 7
1 Replacing the mass memory units 91.1 Replacing the mass memory units overview 91.2 Introduction to replacing WDUs 101.3 Introduction to replacing CTUs and FDUs 12
2 Preventing and resuming updates of disks and memory file diskcopies 15
2.1 Preventing updates of disks and memory file disk copies 162.2 Resuming updates of disks and memory file disk copies 17
3 Replacing the hard disk unit 193.1 General instructions for replacing the WDU 203.2 Replacing the WDU in STU and CHU 263.3 Formatting a WDU 34
4 Removing the hard disk unit 394.1 Removing a subrack WDU, disk units below 1 GB 394.2 Removing a subrack WDU, disk units of 1 GB and above 404.3 Removing a cartridge WDU 40
5 Installing the new hard disk unit 435.1 Installing a subrack WDU, disk units below 1 GB 435.2 Installing a subrack WDU, disk units of 1 GB and above 445.3 Installing a cartridge WDU 44
6 Replacing the FDU: floppy disk unit or magneto�optical disk drive 476.1 General instructions for replacing the FDU 476.2 Replacing the FDU in the STU and CHU 52
7 Replacing the cartridge tape unit 597.1 General instructions for replacing the CTU 597.2 Replacing the CTU in the STU and CHU 64
8 Replacing the adapters and cables 71
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
3 (72)
Contents
List of tables
Table 1. Changing of mass memory units overview 9
Table 2. Maximum amount of bad blocks 12
Table 3. HLR databases 15
4 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
List of figures
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
5 (72)
List of figures
6 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.
Changes made between issues 5�4 and 5�3
Structural changes, no effect on the contents of the document.
Changes made between issues 5�3 and 5�2
Chapter Replacing the hard disk unit , section General instructions for replacingthe WDU :
. A note about consulting instructions to restore software has been added.
. 'WO-BU' has been changed to 'WO-ID' in step Change the working state ofthe new WDU .
. A new step, Change the working state of the new WDU to WO-BU (ISC)has been added.
Changes between issues 5�2 and 5�1
Sections Replacing the hard disk unit , Removing the hard disk unit , Installingthe new hard disk unit , and Replacing the FDU: floppy disk unit or magneto-optical disk drive have been updated.
Changes between issues 5�1 and 5�0
All TOC attributes removed from the modules. Deleted links aspected to M5Sonly, pointing to Replacing the mass memory units. Instead, these links point toReplacing the mass memory units overview, which is no longer aspected to Monly. Online aspects deleted.
Changes between issues 5�0 and 4�1
Created new overview table, used aspects to make it visible only under M. Alsocreated new links pointing to this table and used aspects to make them visibleonly under M. Used aspects to hide old links under M. Used aspects to hide MTUin Concepts, as well. Section 'Replacing the FDU: floppy disk unit or magneto-optical disk drive' re-written entirely, based on section 'Replacing the cartridgetape unit'. General language checks.
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
7 (72)
Summary of changes
8 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
1 Replacing the mass memory units
1.1 Replacing the mass memory units overview
Table 1. Changing of mass memory units overview
Changing of mass memory unitsdescriptions Changing of mass memory units instructions
Replacing the mass memory units. Introduction to replacing WDUs. Introduction to replacing CTUs and FDUs. I/O devices
Preventing and resuming updates of disks andmemory file disk copies. Preventing updates of disks and memory file disk
copies. Resuming updates of disks and memory file disk
copies
Replacing the hard disk unit. General intructions for replacing the WDU. Replacing the WDU in STU and CHU. Formatting a WDU
Removing the hard disk unit. Removing a subrack WDU, disk units below 1 GB. Removing a subrack WDU, disk units of 1 GB and
above. Removing a cartridge WDU
Installing the new hard disk unit. Installing a subrack WDU, disk units below 1 GB. Installing a subrack WDU, disk units of 1 GB and
above. Installing a cartridge WDU
Replacing the FDU: floppy disk unit or magneto�optical disk drive. General instructions for replacing the FDU. Replacing the FDU in the STU and CHU
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
9 (72)
Replacing the mass memory units
Table 1. Changing of mass memory units overview (cont.)
Changing of mass memory unitsdescriptions Changing of mass memory units instructions
Replacing the cartridge tape unit. General instructions for replacing the CTU. Replacing the CTU in STU and CHU
Replacing the adapters and cables
1.2 Introduction to replacing WDUs
Hard disks function as the mass memory of the system. They restore theinformation of the system in case of a restart.
The operation and maintenance unit contains always two hard disks. The unitsthat produce large amount of data, like charging data, or that use large databases,may contain additional hard disks.
Hard disks do not need periodic maintenance. They need to be serviced in failuresituations only.
The hard disk unit is connected to an adapter which can be changed at the sametime with the unit. The adapter is used only in cartridge construction, not insubrack construction.
Before changing the WDU, you must stop all activity on the SCSI bus where youare making changes.
Hard disk units (WDUs) of the system are used to store, for instance, thefollowing 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.
10 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
For safety reasons the hard disk units are always backed up; one unit is called thesystem disk unit and the other the backup unit . In normal conditions the data inthe units is identical, and the system writes to both units. The system disk unit isread first, and the backup unit 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 unitfrom use. If the faulty unit is the system disk unit, the backup unit becomes thesystem disk unit.
Formatting and initialising a new hard disk unit is slow. Therefore you shouldalways have a new hard disk unit that is already formatted and initialised as aspare unit. If this is not the case, the disk unit should be changed, wheneverpossible, when it is not being used by the system (during night hours, forinstance). Even if the hard disk is already initialised, it is still recommended thatthe change is done during a low traffic period.
Note
Verify that an approximately 2 hour break in disk operations is possible. Durationof the break depends on the amount of data to be copied, the version of thesoftware build and the hardware. If the disk is not initialised the duration alsodepends on the capacity of the disk.
Terminal resistor
In the 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 spareunit can be initialised, for example, at the test laboratory before it is installed inthe actual unit.
The maximum amount of bad blocks of a WDU is shown in the following table.The P-list or Primary List shows the bad blocks detected already in the diskfactory. You can fetch the Primary List with, for example, the Service TerminalMAS-command BLP. The G-list or Grown List shows the bad blocks detected inuse. You can fetch the Grown List with, for example, the Service Terminal MAS-command BLG.
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
11 (72)
Replacing the mass memory units
Table 2. Maximum amount of bad blocks
Disk capacity P-list max. length G-list max. length G-list max. growth/month
100 MB 500 10 2
200 MB 500 10 2
500 MB 500 10 2
1 GB 1000 20 4
2 GB 1000 20 4
4 GB 1000 20 4
9 GB 1000 20 4
18 GB 1500 30 6
You can also use the MML command IWB to output the bad block lists.
Related topics
Replacing the hard disk unit
Replacing the mass memory units overview
1.3 Introduction to replacing CTUs and FDUs
The Cartridge tape unit (CTU) is used for backup copying of a network element(for example, software) and for storing network element data, for example,charging data. The CTU is a Digital Data Storage (DDS) recorder which hasbeen developed for computer-based binary data storage. The DDS recorder is anevolution of Digital Audio Tape (DAT) recorder.
The cartridge tape unit and the removable disk unit (FDU) are connected toadapters which can be changed at the same time with the unit. The adapter is usedonly in cartridge construction, not in subrack construction.
Before changing the disk unit, you must stop all activity on the SCSI bus whereyou are making changes.
12 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
Related topics
Replacing the cartridge tape unit
Replacing the FDU: floppy disk unit and magneto�optical disk drive
Replacing the mass memory units overview
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
13 (72)
Replacing the mass memory units
14 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
2 Preventing and resuming updates ofdisks and memory file disk copies
To make sure that no data is lost when changing disks, prevent first disk updatesand updates of memory file disk copies (command groups DB and DU). After thechange is completed, you can resume them.
For the whole topic summary, see Replacing mass memory units overview .
When changing a WDU, you need to:
. copy databases from memory to disk,
. prevent disk updates of databases,
. resume disk updates of databases.
What these databases are depends on the network element, the unit of the WDU,and the type of the network element (subrack or cartridge construction).
In the MSC, the databases are EQUIPM, OEDATA, and PEANUT; they are alllocated in the OMU.
The HLR databases are shown in the table below.
Table 3. HLR databases
HLR computer unit Databases in subrackconstruction
Databases in cartridgeconstruction
OMU EQUIPM EQUIPM
CM ENGINE, OEDATA, VIHDAT, andMYSTIC & all ACRAREs*
-
DBDU - VIHDAT and MYSTIC & allACRAREs*
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
15 (72)
Preventing and resuming updates of disks and memory file disk copies
Table 3. HLR databases (cont.)
HLR computer unit Databases in subrackconstruction
Databases in cartridgeconstruction
EMU - ENGINE
HLRU-x HOSTEL,x HOSTEL,x
ACU-x ACRARE,x or all ACRAREs &MYSTIC *
ACRARE,x or all ACRAREs &MYSTIC*
Note
The MYSTIC database is an exception as it shares certain functions with theACRARE databases. As a result, when you prevent or resume disk updates ofMYSTIC or ACRARE, you must prevent or resume disk updates of alloccurrences both databases.
Example 1. Changing CM's WDU in HLR
When you are changing CM's WDU in a subrack construction HLR, copy frommemory to disk, prevent disk updates, and at the end of the maintenance task,resume disk updates of ENGINE and VIHDAT. If MYSTIC is in use, do the sametasks also to MYSTIC and all ACRAREs.
Example 2. Changing HLRU-3's WDU in HLR
When you are changing HLRU-3's WDU in a subrack construction HLR, there isonly one database, HOSTEL 3, involved.
2.1 Preventing updates of disks and memory file diskcopies
To make sure that no data is lost when changing disks, before changing the diskprevent first disk updates and updates of memory file disk copies.
16 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
Note
If the other disk is broken, you cannot prevent the updates of memory file diskcopies giving the DUP command. Start from step 2.
Steps
1. Prevent the updates of memory file disk copies (DUP)
ZDUP:<unit>;
2. List the databases (DBL)
ZDBL;
3. Prevent disk updates of the databases (DBP)
ZDBP:<database name>,<occurrence>:DISK;
Related topics
Replacing the mass memory units overview
2.2 Resuming updates of disks and memory file diskcopies
Before you start
After you have changed the disks, you must remember to resume the disk updatesand the updates of memory file disk copies, if you have prevented them beforethe 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;
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
17 (72)
Preventing and resuming updates of disks and memory file disk copies
Related topics
Replacing the mass memory units overview
18 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
3 Replacing the hard disk unit
This section tells you how to change a hard disk unit (WDU).
There are two sets of instructions:
. general instructions for changing a WDU
. instructions for changing a WDU in the Statistical Unit (STU) or theCharging Unit (CHU).
In cartridge construction, the WDU is connected to an adapter. When you arechanging the WDU, you can change the adapter at the same time. See Replacingthe adapters and cables .
For the whole topic summary, see Replacing the mass memory units overview .
Before you start
Before changing the WDU, you must stop all activity on the SCSI bus where youare making changes.
Note
If both WDUs of the OMU, CM, HLRU, ACU, EMU, or DBDU are faulty, seeSafecopying overview .
Note
You should always have an initialised WDU at your disposal. This speeds up themaintenance task. See Formatting a WDU .
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
19 (72)
Replacing the hard disk unit
3.1 General instructions for replacing the WDU
This is how you change a WDU in other units than STU and CHU.
When you are changing the WDU, you can change the adapter at the same time.See Replacing the adapters and cables
Before you start
Before changing the WDU, you must stop all activity on the SCSI bus where youare making changes.
You should always have an initialised WDU at your disposal. See Formatting aWDU .
Note
Before starting the procedure, consult Restoring the software . For furtherinformation, see Instructions on Safecopying .
Steps
1. Check that you have a new formatted and initialised WDU
2. Find the working CM/ CMM (USI)
ZUSI:<unit type>;
where <unit type> is CM or CMM.
3. Copy the data from memory of the working CM/CMM to disk (DFC)
Copying the data to disk ensures that the latest data is safe on the disk evenin case of an accidental reset.
ZDFC:<unit type>,<unit index>;
4. Copy the data from database to disk (DBC)
ZDBC:<database name>,<occurrence>;
The databases you need to copy are those of the WDU's computer unit.You can list databases using the DBL command:
20 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
ZDBL:UNIT=<unit>;
5. Prevent file updates and disk updates of databases
See Preventing and resuming updates of disks and memory file disk copiesfor instructions.
However, note that if the other disk is broken, you cannot prevent updatesof memory file disk copies giving the DUP command.
6. Check that all databases have been unpacked from the disk log to thedisk database (DBX)
The command unpacks the disk logs if they are not empty.
ZDBX:<database name>,<occurrence>;
7. Block the WDU you are changing (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
8. Block other mass memory devices (FDU, CTU and WDU) on the sameunit pair's SCSI bus
9. Remove the WDU
See Removing the hard disk unit
10. Check the strappings of the new WDU
See the installation instructions.
11. Install the new WDU
See Installing the new hard disk unit
12. Change the state of the new WDU to WO-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
13. Change the states of other I/O devices on the same SCSI bus (ISC)
Change the states of:
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
21 (72)
Replacing the hard disk unit
. FDUs and WDUs to WO-BU,
. CTUs to WO-ID (if there is no tape in the unit, it remains in stateBL-SY).
To do this, use the ISC command as shown above.
14. Check that the new disk is the backup disk (WB) (IWQ)
Note that the command does not end in a semicolon.
ZIWQ:,<destination unit>,WS=
15. Check if the new WDU is formatted and initialised
If it is not, do it now.
ZIWI:,<destination unit>,<pair>:<drive>,<volumelabel>,<file count>,<version limit>,<initials>;
16. Change the working state of the new WDU from WO-ID to TE-ID(ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
17. Diagnose the WDU (UDD)
ZUDD:<main unit type>,<pair>,<main unit index>:<device type>,<device index>;
Expected outcome
If the diagnosis is successful, you will see diagnostic report 3999DIAGNOSIS EXECUTED - UNIT OK output to the alarm printer.
18. Change the working state of the new WDU to WO-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
19. Copy the system WDU to the new WDU (IPS)
ZIPS:�<source unit>�,<source I/O device>,<sourcepath>,,:,<destination I/O device>,<destinationpath>,,:<directory mode>,<copy task name>;
22 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
Note
If you want to copy also other than default versions, you should use parameter<source file version> and give it value FF:ZIPS:�<sourceunit>�,<source I/O device>,<source path>,,FF:,<destination I/O device>,<destination path>,,:<directorymode>,<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. Make sure thatthe 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 e.g.in the FAILED state, it is not possible to continue until the fault iscorrected.
20. 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>
21. Resume updates of disks and memory file disk copies of the databaseswhich you prevented before changing the WDU
See Resuming updates of disks and memory file disk copies for details.
22. Copy the data from database to disk
The databases you need to copy are those of the WDU's computer unit. SeePreventing and resuming updates of disks and memory file disk copies .
Copy the data from all the unit's databases in the same way.
ZDBC:<database name>,<occurrence>;
If copying does not succeed, check the state of the database as detailed inthe following step.
23. Check that the database states are restored to 'normal' or 'dumping'(DBS)
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
23 (72)
Replacing the hard disk unit
ZDBS:<database name>,<occurrence>;
The command displays the states of the databases.
24. Check that the states of the hard disks are corrected (WO-BU) (ISI)
ZISI:,<destination unit>,<pair>:<I/O device type>,<I/O device index>;
25. Check that the states of the units are correct (WO-EX, SP-EX) (USI)
ZUSI:<unit type>,<unit index>;
Further information:
Example 3. Changing OMU's WDU-0
1. Check the working CMM.
ZUSI:CMM;
The command prints out the working states of CMMs.
2. Copy the data from memory of the working (WO-EX) CMM to disk. Inthis example, CMM-1 is the working unit.
ZDFC:CMM,1;
3. Copy the data from all the unit's databases to disk, for example, OMU'sEQUIPM-0.
ZDBC:EQUIPM,0;
4. Prevent updates of memory file disk copies.
NOTE: if the other disk is broken, you cannot prevent updates of memoryfile disk copies giving the DUP command . Go to step 5.
ZDUP:<unit>;
5. Prevent disk updates of databases, for example, EQUIPM-0.
ZDBP:EQUIPM,0:DISK;
6. Check that all databases have been unpacked from the disk log to the diskdatabase.
ZDBX:EQUIPM,0;
7. Block OMU's WDU-0:
24 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
ZISC:,OMU:WDU,0:BL-US;
8. Block the other I/O devices on the same unit pair's SCSI bus.
9. Change the WDU.
10. Change the state of OMU's WDU-0 to WO-ID.
ZISC:,OMU:WDU,0:WO-ID;
11. Change the states of other I/O devices on the same SCSI bus in the sameway.
12. Check that the new disk is the backup disk (WB).
ZIWQ:,OMU
13. Format OMU's WDU-0.
ZIWI:,OMU:WB,,<volume label>,FFF,2,nn;
14. Change the working state of the new WDU from WO-ID to TE-ID.
ZISC:,OMU:WDU,0:TE-ID;
15. Diagnose OMU's WDU-0.
ZUDD:OMU,0:WDU,0;
16. Change the working state of WDU-0 to WO-BU.
ZISC:,OMU:WDU,0:WO-BU;
17. Copy the system disk (WDU-1) to backup disk (WDU-0), includingsubdirectories, using the default and active build directory name'MI_4_3_0'. Name the task as 'COPY'.
ZIPS:�OMU�,WDU-S,/MI_4_3_0,,:,WDU-B,/,:DIR=INC,NAME=COPY;
Check the progress of the copy task. Make sure that the copy task is in theSUCCESS state before continuing.
ZIPI:NAME=COPY;
18. Resume updates of memory file disk copies.
ZDUR:<unit>;
19. Resume disk updates of the databases, for example, EQUIPM-0.
ZDBR:EQUIPM,0:DISK;
20. Copy the data from all the unit's databases to disk, for example, OMU'sEQUIPM-0 .
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
25 (72)
Replacing the hard disk unit
ZDBC:EQUIPM,0;
21. Check that the database states are restored to 'normal' or 'dumping', forexample, EQUIPM-0.
ZDBS:EQUIPM,0;
22. Check the states of OMU's hard disks.
ZISI:,OMU:WDU;
23. Check the state of OMU.
ZUSI:OMU;
Related topics
Introduction to replacing WDUs
Replacing the mass memory units overview
3.2 Replacing the WDU in STU and CHU
This is how you change a WDU of the Statistical Unit (STU) or the ChargingUnit (CHU).
When you are changing the WDU, you can change the adapter at the same time.See Replacing the adapters and cables
Before you start
Because changing the WDU prevents file transfer to the Billing Centre, youshould complete the change during low traffic hours. This minimises the numberof charging files that remain untransferred because of the maintenance break.Before starting, ensure that the transfer to the Billing Centre has stopped. Take abackup if possible.
Before changing the WDU, you must stop all activity on the SCSI bus where youare making changes.
You should always have an initialised WDU at your disposal. See Formatting aWDU .
Steps
1. Check the AE-name of the Virtual File Store (VFS) application (QDI)
26 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
ZQDI;
2. Lock the VFS application (QDG)
This prevents the Billing Centre's access to the disks during themaintenance task.
ZQDG:<AE-name>,<state change>;
3. Change the network interface to the DOWN state
a. Check the units's network interface (EL0 or MB0)
ZQRI
b. Block the network interface
ZQRN:<unit>,<pair>:<interface name>:::DOWN;
c. Check that the network interface is in the DOWN state
ZQRI;
4. Find out which statistical/charging unit is in the SP-EX state (USI)
ZUSI:<unit type>,<unit index>;
If printout of the command shows that the computer unit of the faultyWDU is the active unit, you must change its state to SP-EX. In this wayyou can avoid accidental reset of the active unit during the maintenancetask.
ZUSC:<unit type>,<unit pair>,<unit index>:<workingstate>;
5. Check the file name (IMD)
ZIMD:,<destination unit>,<pair>:<tape unitidentifier>,<tape unit number>;
6. Close the tape of CTU and remove the tape (IMC)
ZIMC:,<destination unit>,<pair>:<tape unitidentifier>,<file name>:Y;
7. Block the WDU you are changing (ISC)
This causes a three-star alarm, 2650 STORING OF DATA FAILED ONONE DISK.
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
27 (72)
Replacing the hard disk unit
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
8. Block other I/O devices (CTU) on the same SCSI bus (ISC)
To do this, use the ISC command as instructed above.
9. Remove the WDU
See Removing the hard disk unit
10. Check the strappings of the new WDU
See the installation instructions.
11. Install the new WDU
See Installing the new hard disk unit
12. Change the state of the new WDU to WO-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
13. Change the states of other I/O devices on the same SCSI bus (ISC)
Change CTUs to WO-ID (if there is no tape in the unit, it remains in stateBL-SY).
To do this, use the ISC command as shown above.
14. Insert a new DAT/DDS tape into the CTU and open the tape file (IMP)
ZIMP:,<destination unit>,<pair>:<tape unitidentifier>,<tape unit>,,,<open file tape>;
15. Check that the disk works by reading the directory (DDE)
ZDDE:<unit type>,<unit pair>,<unit index>:�ZL:M�,�ZLP:M,MAS�,�ZMX:<W0/W1>-/DIRECTORY.DIR�;
16. If the disk is uninitialised, initialise it (IWI)
28 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
Note
The initialisation takes several hours.
You should always have a formatted disk at your disposal.
ZIWI:,<unit>,<unit pair>:WB,,<disk name>,7FFF,,<initials>;
17. If the diskname is incorrect or the size of the root directory is smallerthan 00000CCD blocks, initialise the root directory (IWK)
This will take a few seconds.
ZIWK:,<unit>,<unit pair>:WB,,<disk name>,7FFF,,<initials>;
18. Change the state of the WDU to TE-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
19. Diagnose the new WDU (UDD)
ZUDD:<main unit type>,<pair>,<main unit index>:<device type>,<device index>;
Expected outcome
If the diagnosis is successful, you will see diagnostic report 3999DIAGNOSIS EXECUTED - UNIT OK output to the alarm printer.
20. List the current tests (UDQ)
ZUDQ;
21. Display the diagnostic report history (UDH)
ZUDH:<unit type>,<unit pair>,<unit index>:<reportclass>:<date>,<time>;
22. Change the state of the WDU to WO-ID (ISC)
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
29 (72)
Replacing the hard disk unit
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
23. Find out the current disk file (IFI)
The line CURRENT DISK FILE NUMBER in the execution printoutshows the file the system will next write to. Write down the file number. Itwill be later referred to as FILE_1.
ZIFI:<unit>,<unit_pair_index>:<application>:<page>;
24. Copy the system WDU to the new WDU (IPS)
ZIPS:�<source unit>�,<source I/O device>,<sourcepath>,,,:,<destination I/O device>,<destinationpath>,:<directory mode>,<copy task name>;
Check the progress of the copy task to see when it is ready. Make sure thatthe 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 e.g.in the FAILED state, it is not possible to continue until the fault iscorrected.
25. Change the WDU's state to WO-BU (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
26. Find out which file is now the open charging file (IFO)
ZIFO:<unit>,<unit_pair_index>:<application>:,<status filter>;
Repeat the command until an open file is found. Then write down the filename. It will be later referred to as FILE_2.
27. Set the open file to the FULL status (IFS)
The system now locates the open file and closes it.
ZIFS:<unit>,<unit_pair_index>:<application>:,<status filter>:<task>;
30 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
28. Copy all files between FILE_1 and FILE_2 (including FILE_1 andFILE_2) (IPS)
ZIPS:<source unit>,<source I/O device>,<sourcepath>,<source file name>,:,<destination I/O device>,<destination path>,,;
29. Delete the old versions of the copied charging files from the backupWDU (IWD)
ZIWD:,<destination unit>,<pair>:<drive>::<filename>,<file name extension>,FF;
30. Unlock the Virtual File Store (VFS) application to restore the BillingCentre's access to the disks (QDG)
ZQDG:<AE-name>,UNL;
31. Change the network interface to the UP state
a. Check the unit's network interface (EL0 or MB0)
ZQRI
b. Change the network interface to the UP state
ZQRN:<unit>,<pair>:<interface name>:::UP;
c. Check that the network interface is in the UP state
ZQRI;
Further information:
Example 4. Changing WDU-0 in STU
1. Check the AE-name of the Virtual File Store (VFS) application.
ZQDI;
2. Lock the VFS application.
ZQDG:VFS,LOC;
3. Change the state of network interface EL0 to DOWN
a. Check the unit's network interface
ZQRI;
b. Block the network interface
ZQRN:<unit>,<pair>:EL0:::DOWN;
c. Check that the network interface is in the DOWN state
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
31 (72)
Replacing the hard disk unit
ZQRI;
4. Find out which STU is in the SP-EX state.
ZUSI:STU;
If the computer unit of the faulty WDU-0, STU-0, is the active unit, changeits state to SP-EX (STU-1 automatically becomes the active unit):
ZUSC:STU,0:SP;
5. Check the file name.
ZIMD:,STU,0:CTU,0;
6. Close the tape of the CTU. Then remove the tape.
ZIMC::CTU,<file name>:Y;
7. Block WDU-0 of the STU.
ZISC:,STU:WDU,0:BL-US;
8. Block other I/O devices (CTU) on the same SCSI bus.
9. Change the WDU.
10. Change the state of STU's WDU-0 to WO-ID.
ZISC:,STU:WDU,0:WO-ID;
11. Change the states of CTUs on the same SCSI bus to WO-ID using the ISCcommand. If there is no tape in the CTU, it remains in state BL-SY.
12. Insert a new DAT/DDS tape into the CTU. Preformat and open the tapefile.
ZIMP:,STU,0:CTU,0,,,Y;
13. Read the directory of WDU-0:
ZDDE:STU,0:�ZL:M�,�ZLP:M,MAS�,�ZMX:W0�/DIRECTORY.DIR�;
14. Initialise WDU-0, diskname STUWDU0:
ZIWI:,STU:WB,,STUWDU0,7FFF,,XX;
15. If the diskname is incorrect or the size of the root directory is smaller than00000CCD blocks, initialise the root directory of WDU-0 (disknameSTUWDU0).
ZIWK:,STU:WB,,STUWDU0,7FFF,,XX;
This will take a few seconds.
32 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
16. Change the state of the WDU to TE-ID.
ZISC:,STU:WDU,0:TE-ID;
17. Diagnose the new WDU (STU's WDU-0).
ZUDD:STU,0:WDU,0;
18. List the current tests.
ZUDQ;
19. Display the diagnostic report history.
ZUDH:STU,0;
20. Change the state of the WDU to WO-ID.
ZISC:,STU:WDU,0:WO-ID;
21. To find out the current disk file, output alarm limits and statistics inGSMCHA of the STU.
ZIFI:STU:GSMCHA:S;
The line CURRENT DISK FILE NUMBER in the execution printoutshows the file the system will next write to. Write down the file number. Itwill be later referred to as FILE_1.
22. Copy the system disk (WDU-1) to backup disk (WDU-0).
ZIPS:�STU�,WDU-S,/,:,WDU-B,/,:DIR=INC,NAME=<copytask name>;
Check the progress of the copy task. Make sure that the copy task is in theSUCCESS state before continuing.
ZIPI:NAME=<copy task name>;
23. Change the state of STU's WDU-0 to WO-BU:
ZISC:,STU:WDU,0:WO-BU;
24. Find out the currently open charging file of STU.
ZIFO:STU:GSMCHA:,OPEN;
Repeat the command until an open file is found. Then write down thefilename. It will be later referred to as FILE_2.
25. Set the status of the open charging file of STU to FULL:
ZIFS:STU:GSMCHA:,OPEN:F;
The system now locates the open file and closes it.
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
33 (72)
Replacing the hard disk unit
26. Copy all files between FILE_1 and FILE_2 (including FILE_1 andFILE_2), for example, copy file named CF0001 whose file name extensionis DAT.
ZIPS:�STU�,WDU-S,/,CF0001.DAT,:,WDU-B,/,,:NAME=FILE1;
Check the progress of the copy task (named FILE1). Make sure that thecopy task is in the SUCCESS state before continuing.
ZIPI:NAME=FILE1;
27. Delete old versions of all charging files CF%.DAT from the backup WDU.
ZIWD:,STU:WB::CF%,DAT,FF;
28. Unlock the Virtual File Store (VFS) application to restore the BillingCentre's access to the disks.
ZQDG:VFS,UNL;
29. Change state of network interface EL0 to UP
a. Check the unit's network interface
ZQRI;
b. Change the network interface to the UP state
ZQRN:<unit>,<pair>:<interface name>:::UP;
c. Check that the network interface is in the UP state
ZQRI;
Related topics
Introduction to replacing the WDUs
Replacing the mass memory units overview
3.3 Formatting a WDU
You should always have a formatted spare unit at your disposal so that it can bechanged if one of the WDU's becomes faulty.
In brief, formatting a spare WDU consists of
1. removing a WDU from the exchange,
2. replacing it with a spare WDU,
34 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
3. formatting the spare WDU,
4. removing the formatted WDU,
5. and putting back the original WDU.
Steps
1. Prevent disk updates and updates of memory file disk copies
See Preventing and resuming updates of disks and memory file disk copiesfor instructions.
2. Block the WDU to be removed (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
3. Block other I/O devices on the SCSI bus of the WDU (ISC)
To do this, use the ISC command as instructed above.
4. Remove the WDU
See Removing the hard disk unit
5. Check the strappings of the new (spare) WDU
See the installation instructions.
6. Install the new WDU
See Installing the new hard disk unit
7. Change the state of the WDU to WO-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device name>,<I/O device index>:<working state>
8. Initialise the WDU (IWI)
ZIWI:,<destination unit>,<pair>:<drive>,,<volumelabel>,<file count>,<version limit>,<initials>;
9. Block the initialised WDU (ISC)
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
35 (72)
Replacing the hard disk unit
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:BL-US;
10. Remove the initialised WDU
See Removing the hard disk unit
11. Put back the old WDU
See Installing the new hard disk unit
12. Change the state of the WDU first to WO-ID, then to WO-BU (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
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 to WO-ID (if there is no tape in the unit, it remains in stateBL-SY).
To do this, use the ISC command as shown above.
14. Resume database updating and file updating
See Resuming updates of disks and memory file disk copies forinstructions.
15. Output the active alarms (AHO)
ZAHO;
Further information:
Example 5. Formatting a WDU
In this example, OMU's WDU-0 is removed.
1. Prevent updates of memory file disk copies.
ZDUP:OMU;
2. Display the disk update state.
36 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
ZDUD:OMU;
3. Prevent disk updates of databases.
ZDBP:EQUIPM,0:DISK;
4. Block OMU's WDU-0.
ZISC:,OMU:WDU,0:BL-US;
5. Block other I/O devices on the SCSI bus of the WDU.
6. Remove the WDU.
7. Check the strappings of the new (spare) WDU.
8. Install the spare WDU.
9. Change the state of OMU's WDU-0 to WO-ID.
ZISC:,OMU:WDU,0:WO-ID;
10. Format and initialise the WDU.
ZIWI:,OMU:WB,,NAME,FFF,2,NN;
11. Block OMU's WDU-0:
ZISC:,OMU:WDU,0:BL-US;
12. Remove the initialised WDU.
13. Put back the old WDU.
14. Change the state of OMU's WDU-0 first to WO-ID and then to WO-BU.
ZISC:,OMU:WDU,0:WO-ID;
ZISC:,OMU:WDU,0:WO-BU;
15. Change back the states other I/O devices on the SCSI bus of the WDU.
16. Resume updates of memory file disk copies.
ZDUR:OMU;
17. Display the disk update state.
ZDUD:OMU;
18. Resume disk updates of databases.
ZDBR:EQUIPM,0:DISK;
19. Output the active alarms.
ZAHO;
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
37 (72)
Replacing the hard disk unit
Related topics
Introduction to replacing the WDUs
Replacing the mass memory units overview
38 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
4 Removing the hard disk unit
The correct way to do this depends on the type of the network element (subrackor cartridge construction) and the size of the hard disk unit (WDU).
For the whole topic summary, see Replacing the mass memory units overview .
4.1 Removing a subrack WDU, disk units below 1 GB
Steps
1. Detach the signal cable
2. Switch off power. Wait until disk rotation stops.
3. Detach the power cable
4. Remove the WDU
Related topics
Introduction to replacing WDUs
Replacing the hard disk unit
General instructions for replacing the WDU
Replacing the WDU in STU and CHU
Formatting a WDU
Replacing the mass memory units overview
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
39 (72)
Removing the hard disk unit
4.2 Removing a subrack WDU, disk units of 1 GB andabove
Steps
1. Switch off power. Wait until disk rotation stops.
2. Detach the power cable
3. Detach the signal cable
4. Remove the WDU
Related topics
Introduction to replacing WDUs
Replacing the hard disk unit
General instructions for replacing the WDU
Replacing the WDU in STU and CHU
Formatting a WDU
Replacing the mass memory units overview
4.3 Removing a cartridge WDU
Steps
1. Switch off power
Alarm 2809 MASS MEMORY POWER SUPPLY FAILURE may beprinted out. Wait until disk rotation stops.
2. Remove the WDU
Related topics
Introduction to replacing WDUs
Replacing the hard disk unit
40 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
General instructions for replacing the WDU
Replacing the WDU in STU and CHU
Formatting a WDU
Replacing the mass memory units overview
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
41 (72)
Removing the hard disk unit
42 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
5 Installing the new hard disk unit
The correct way to do this depends on the type of the network element (subrackor cartridge construction) and the size of the WDU.
For the whole topic summary, see Replacing the mass memory units overview .
5.1 Installing a subrack WDU, disk units below 1 GB
Steps
1. Install the new WDU
2. Connect the power cable
3. Switch on power
4. Connect the signal cable
Related topics
Introduction to replacing WDUs
Replacing the hard disk unit
General instructions for changing a WDU
Replacing the WDU in STU and CHU
Formatting a WDU
Replacing the mass memory units overview
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
43 (72)
Installing the new hard disk unit
5.2 Installing a subrack WDU, disk units of 1 GB andabove
Steps
1. Install the new WDU
2. Connect the power cable
3. Connect the signal cable
4. Switch on power
Related topics
Introduction to replacing WDUs
Replacing the hard disk unit
General instructions for changing a WDU
Replacing the WDU in STU and CHU
Formatting a WDU
Replacing the mass memory units overview
5.3 Installing a cartridge WDU
Steps
1. Install the new WDU
2. Switch on power
Related topics
Introduction to replacing WDUs
Replacing the hard disk unit
General instructions for changing a WDU
Replacing the WDU in STU and CHU
44 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
Formatting a WDU
Replacing the mass memory units overview
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
45 (72)
Installing the new hard disk unit
46 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
6 Replacing the FDU: floppy disk unit ormagneto�optical disk drive
Before you start
There are two sets of instructions:
. general instructions on changing a CTU,
. instructions on changing a CTU in the Charging Unit (CHU) or theStatistical Unit (STU).
Before changing the FDU, you must stop all activity on the SCSI bus where youare making changes.
The unit is connected to an adapter. When you are changing the unit, you canchange the adapter at the same time. See Replacing the adapters and cables . Formore information on FDUs, see Removable disk unit (FDU) .
For the whole topic summary, see Replacing the mass memory units overview .
6.1 General instructions for replacing the FDU
This is how you change an FDU in other units than the CHU or STU.
Steps
1. Copy the data from memory of CM/ CMM to disk (DFC)
This ensures that the latest data is safe on the disk even in case of anaccidental reset.
ZDFC:<unit type>,<unit index>;
2. If there is a floppy/MO disk in the drive, withdraw it using the ejectbutton on the front panel of the FDU
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
47 (72)
Replacing the FDU: floppy disk unit or magneto�optical disk drive
3. Block the FDU (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
4. Copy the data from database to disk (DBC)
The databases you need to copy are those of the WDU's computer unit.You can list the databases using the DBL command.
ZDBC:<database name>,<occurrence>;
5. Prevent disk updates and updates of memory file disk copies
See Preventing and resuming updates of disks and memory file disk copiesfor instructions.
6. Check that all databases have been unpacked from the disk log to thedisk database (DBX)
The command unpacks the disk logs if they are not empty.
ZDBX:<database name>,<occurrence>;
7. Block other I/O devices on the same SCSI bus (ISC)
Use the command ISC . It is particularly important to block the WDU.
8. Remove the FDU
The correct way to do this depends on the type of the network element(subrack or cartridge construction):
Subrack CTU
a. Switch off power.
b. Detach the power cable.
c. Detach the signal cable.
d. Remove the FDU.
Cartridge FDU
48 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
a. Switch off power.
a. Switch off the cartridge power supply. Alarm 2809 MASSMEMORY DEVICE POWER SUPPLY FAILURE may beprinted out.
b. Optional for ODPU: Press the button 'POWER OFF'. Waituntil the 'OFF' indicator turns on. No alarm is received.
b. Remove the FDU.
9. Check the strappings of the new FDU
10. Install the new FDU
The correct way to do this depends on the type of the network element(subrack or cartridge construction):
Subrack FDU
a. Install the new FDU.
b. Connect the power cable.
c. Connect the signal cable.
d. Switch on power.
Cartridge FDU
a. Install the new FDU.
b. Switch on power.
c. Check that Alarm 2870 is cancelled.
11. Insert a new floppy/MO disk into the FDU and wait for loading
12. Change the state of the FDU to TE-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
Note
You do not need to do this if Alarm 2870 has been generated. The alarmautomatically changes the state to TE-ID.
13. Diagnose the new FDU (UDD)
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
49 (72)
Replacing the FDU: floppy disk unit or magneto�optical disk drive
ZUDD:<main unit type>,<main unit index>:<devicetype>,<device index>;
The diagnosis will take about two minutes. If the result is successful, youwill see Diagnostic Report 3999 DIAGNOSIS EXECUTED - UNIT OKoutput to the alarm printer.
14. Change the state of the new FDU to WO-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
To check the working states of I/O devices, you can use the ISIcommand.
ZISI:,<destination unit>,<pair>:<I/O device type>,<I/O device index>;
Example 6.
Check the working states of all I/O devices of OMU:
ZISI:,OMU:;
15. 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 stateBL-SY).
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
16. Resume updates of disks and memory file disk copies of the databaseswhich you prevented
See Resuming updates of disks and memory file disk copies .
Further information:
Example 7. Changing FDU-0 in OMU
In this example, OMU's FDU-0 is changed.
50 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
1. Copy the data from memory of CMM-0 to disk.
ZDFC:CMM,0;
2. If there is a floppy/MO disk in the drive, withdraw it using the eject buttonon the front panel of the FDU.
3. Block FDU-0 in OMU.
ZISC:,OMU:FDU,0:BL-US;
4. Copy the data from database to disk.
ZDBC:EQUIPM,0;
5. Prevent updates of memory file disk copies and disk updates of databases
ZDUP:OMU;
ZDBP:EQUIPM,0:DISK;
6. Check that all databases have been unpacked from the disk log to thedatabase.
ZDBX:EQUIPM,0;
7. Block other I/O devices on the same SCSI bus using the ISC command. Itis particularly important to block the WDU.
8. Remove the FDU. See step 8 for more detailed instructions.
9. Check the strappings of the new FDU
10. Install the new FDU. See step 10 for more detailed instructions.
11. Insert a new floppy/MO disk into the FDU and wait for loading.
12. Change the state of FDU-0 to TE-ID.
ZISC::FDU,0:TE-ID;
13. Diagnose FDU-0 in OMU.
ZUDD:OMU,0:FDU,0;
14. 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;
15. Change the state of the OMU's WDU-0 first to WO-ID, then to WO-BU.
ZISC:,OMU:WDU,0:WO-ID;
ZISC:,OMU:WDU,0:WO-BU;
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
51 (72)
Replacing the FDU: floppy disk unit or magneto�optical disk drive
Change the state of CTU-0 to WO-ID
ZISC:,OMU:CTU,0:WO-ID;
16. Resume updates of memory file disk copies and disk updates of databases.
ZDUR:OMU;
ZDBR:EQUIPM,0:DISK;
For more information on FDUs, see Removable disk unit (FDU)
Related topics
Introduction to replacing the CTUs and FDUs
Replacing the mass memory units overview
6.2 Replacing the FDU in the STU and CHU
This is how you change a CTU in STU or CHU.
Steps
1. Check the AE-name of the Virtual File Store (VFS) application (QDI)
ZQDI;
2. Lock the VFS application (QDG)
This prevents the Billing Centre's access to the disks during themaintenance task.
ZQDG:<AE-name>,<state change>;
3. Find out the current disk file (IFI)
ZIFI:<unit>,<unit_pair_index>:GSMCHA:S;
The line CURRENT DISK FILE NUMBER in the execution printoutshows the file the system will write to. Write down the current disk filenumber. It will be later referred to as FILE_1.
4. Change the working state of the disk on the same SCSI bus to BL-US(ISC)
52 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
The system automatically ensures that the disk in the WO-BU state is thesystem disk.
ZISC:,<destination unit>,<pair>:WDU,<I/O deviceindex>:BL-US;
5. Change the state of FDU you are changing to BL-US (ISC)
ZISC:,<destination unit>,<pair>:FDU,<I/O deviceindex>:BL-US;
6. Remove the FDU
a. Switch off power.
a. Switch off the cartridge power supply.
b. Optional for ODPU: Press the button 'POWER OFF'. Waituntil the 'OFF' indicator turns on. No alarm is received.
b. Remove the FDU.
7. Install the new FDU
a. Install the new FDU.
b. Switch on power.
8. Change the working state of the backup WDU first to WO-ID andthen change the state to WO-BU (ISC)
ZISC:,<destination unit>,<pair>:WDU,<I/O deviceindex>:<working state>;
9. Check that the WDU operates correctly by reading the directorylisting (IWX)
ZIWX:,<destination unit>,<pair>:WB::<filename>,<extension>;
10. Find out which file is now the open charging file and write it down asFILE_2 (IFO)
Repeat the command until an open file is found.
ZIFO:<unit>,<unit_pair_index>:GSMCHA:,OPEN;
11. Set the open file to the FULL status (IFS)
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
53 (72)
Replacing the FDU: floppy disk unit or magneto�optical disk drive
The system now locates the open file and closes it.
ZIFS:<unit>,<unit_pair_index>:GSMCHA:,OPEN:F;
12. Copy all charging files between FILE_1 and FILE_2, (includingFILE_1 and FILE_2), from the system WDU to the backup WDU(IPS)
ZIPS:�<source unit>�,WDU-S,<source path>,<sourcefile name>,:,WDU-S,<destination path>,,;
13. Check that copying was successful.
ZIPI;
Make sure that the copy task is in the SUCCESS state before continuing.
If the copy task does not change into the SUCCESS state, but remains e.g.in the FAILED state, it is not possible to continue until the fault iscorrected.
14. Delete the old versions of all the copied charging files (from FILE_1 toFILE_2) from the backup WDU (IWD)
ZIWD:,<destination unit>,<pair>:WB::<file name>,<file name extension>,FF;
15. Change the working state of the FDU from WO-BU to TE-ID (ISC)
ZISC:,<destination unit>,<pair>:FDU,<I/O deviceindex>:TE-ID;
16. Insert the disk and diagnose the FDU (UDD)
ZUDD:<main unit type>,<main unit index>:FDU,<deviceindex>;
The diagnosis will take about two minutes. If the result is successful, youwill see Diagnostic Report 3999 DIAGNOSIS EXECUTED� UNIT OKoutput to the alarm printer.
17. List the current tests (UDQ)
ZUDQ;
18. Display the diagnostic history (UDH)
54 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
ZUDH:<unit type>,<unit pair>,<unit index>;
19. Change the state of the FDU to WO-ID (ISC)
ZISC:,<destination unit>,<pair>:FDU,<I/O deviceindex>:WO-ID;
20. Unlock the Virtual File Store (VFS) application to restore the BillingCentre's access to the disks (QDG)
ZQDG:<AE-name>,UNL;
21. Print out the active alarms (AHO)
ZAHO;
Analyse the alarms and find out what caused them
Further information:
Example 8. Changing FDU-0 in CHU
1. Check the AE-name of the Virtual File Store (VFS) application.
ZQDI;
2. Lock the VFS application. This prevents the Billing Centre's access to thedisks during the maintenance task.
ZQDG:VFS,LOC;
3. To find out the current disk file, output alarm limits and statistics in theGSMCHA application of the CHU.
ZIFI:CHU:GSMCHA:S;
The line CURRENT DISK FILE NUMBER in the execution printoutshows the file the system will write to. Write it down as FILE_1.
4. Change the state of WDU-0 to BL-US.
ZISC:,CHU:WDU,0:BL-US;
5. Change the state of FDU-0 to BL-US.:
ZISC:,CHU:FDU,0:BL-US;
6. Change the FDU.
7. Change the state of CHU's WDU-0 to WO-ID and then to WO-BU.
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
55 (72)
Replacing the FDU: floppy disk unit or magneto�optical disk drive
ZISC:,CHU:WDU,0:WO-ID;
ZISC:,CHU:WDU,0:WO-BU;
8. To check that the WDU operates correctly, output all file labels from thebackup WDU of the CHU.
ZIWX:,CHU:WB,::%,%;
9. Find out which file is now the open charging file and write it down asFILE_2.
ZIFO:CHU:GSMCHA:,OPEN;
Repeat the command until an open file is found.
10. Set the status of the open charging file in the CHU to FULL.
ZIFS:CHU:GSMCHA:,OPEN:F;
11. Copy file named CF0001 with the extension DAT from the system WDUto the backup WDU.
ZIPS:�CHU�,WDU-S,/,CF0001.DAT,:,WDU-B,/,,;
Copy all charging files from FILE_1 to FILE_2 in the same way.
12. Check that copying was successful. Make sure that the copy task is in theSUCCESS state before continuing.
ZIPI;
13. Delete old versions of all charging files CF%.DAT from the backup WDU.
ZIWD:,CHU:WB::CF%,DAT,FF;
Delete old versions of all the copied charging files (from FILE_1 toFILE_2).
14. Change the working state of the FDU from WO-BU to TE-ID.
ZISC:,CHU,0:FDU,0:TE-ID;
15. Insert the tape and diagnose FDU-0 in CHU-0.
ZUDD:CHU,0:FDU,0;
16. List the current tests.
ZUDQ;
17. Check the diagnostic history.
ZUDH:CHU,0;
18. Change the state of FDU-0 to WO-BU.
56 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
ZISC:,CHU:FDU,0:WO-ID;
ZISC:,CHU:FDU,0:WO-BU;
19. Unlock the Virtual File Store (VFS) application.
ZQDG:VFS,UNL;
20. Print out the active alarms.
ZAHO;
For more information on FDUs, see Removable disk unit (FDU)
Related topics
Introduction to replacing the CTUs and FDUs
Replacing mass memory units overview
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
57 (72)
Replacing the FDU: floppy disk unit or magneto�optical disk drive
58 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
7 Replacing the cartridge tape unit
There are two sets of instructions:
. general instructions on changing a CTU,
. instructions on changing a CTU in the Charging Unit (CHU) or theStatistical Unit (STU).
Before you start
In cartridge construction, the unit is connected to an adapter. When you arechanging the unit, you can change the adapter at the same time. See Replacing theadapters and cables .
For the whole topic summary, see Replacing the mass memory units overview .
7.1 General instructions for replacing the CTU
This is how you change a CTU in other units than the CHU or STU.
Steps
1. Copy the data from memory of CM/ CMM to disk (DFC)
This ensures that the latest data is safe on the disk even in case of anaccidental reset.
ZDFC:<unit type>,<unit index>;
2. If there is a DAT/DDS tape in the drive, withdraw it using the ejectbutton on the front panel of the CTU
3. Block the CTU (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
59 (72)
Replacing the cartridge tape unit
4. Copy the data from database to disk (DBC)
The databases you need to copy are those of the WDU's computer unit.You can list the databases using the DBL command.
ZDBC:<database name>,<occurrence>;
5. Prevent disk updates and updates of memory file disk copies
See Preventing and resuming updates of disks and memory file disk copiesfor instructions.
6. Check that all databases have been unpacked from the disk log to thedisk database (DBX)
The command unpacks the disk logs if they are not empty.
ZDBX:<database name>,<occurrence>;
7. Block other I/O devices on the same SCSI bus (ISC)
Use the command ISC . It is particularly important to block the WDU.
8. Remove the CTU
The correct way to do this depends on the type of the network element(subrack or cartridge construction):
Subrack CTU
a. Switch off power.
b. Detach the power cable.
c. Detach the signal cable.
d. Remove the CTU.
Cartridge CTU
a. Switch off power. Alarm 2870 MASS MEMORY POWERSUPPLY FAILURE may be printed out.
b. Remove the CTU.
9. Check the strappings of the new CTU
10. Install the new CTU
60 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
The correct way to do this depends on the type of the network element(subrack or cartridge construction):
Subrack CTU
a. Install the new CTU.
b. Connect the power cable.
c. Connect the signal cable.
d. Switch on power.
Cartridge CTU
a. Install the new CTU.
b. Switch on power.
c. Check that Alarm 2870 is cancelled.
11. Insert a new DAT/DDS tape into the CTU and wait for loading
12. Change the state of the CTU to TE-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type> ,<I/O device index>:<working state>;
Note
You do not need to do this if Alarm 2870 has been generated. The alarmautomatically changes the state to TE-ID.
13. Diagnose the new CTU (UDD)
ZUDD:<main unit type>,<main unit index>:<device type>,<device index>;
The diagnosis will take about two minutes. If the result is successful, youwill see Diagnostic Report 3999 DIAGNOSIS EXECUTED - UNIT OKoutput to the alarm printer.
14. Change the state of the new CTU to WO-ID (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type> ,<I/O device index>:<working state>;
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
61 (72)
Replacing the cartridge tape unit
To check the working states of I/O devices, you can use the ISIcommand.
ZISI:,<destination unit>,<pair>:<I/O device type> ,<I/O device index>;
Example 9.
Check the working states of all I/O devices of OMU:
ZISI:,OMU:;
15. 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 stateBL-SY).
ZISC:,<destination unit>,<pair>:<I/O device type> ,<I/O device index>:<working state>;
16. Resume updates of disks and memory file disk copies of the databaseswhich you prevented
See Resuming updates of disks and memory file disk copies .
17. If necessary, change the tape type
If, for instance, you are using the tape for backup copying, the tape typeshould be DAT/DDS (default type). This is how you change the tape type:
a. Check the tape type (IMD)
ZIMD;
b. Change the tape type (IMS)
ZIMS:,<destination unit>,<pair>:<tape unitidentifier>,<tape unit number>,<tape type>;
Further information:
Example 10. Changing CTU-0 in OMU
In this example, OMU's CTU-0 is changed.
62 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
1. Copy the data from memory of CMM-0 to disk.
ZDFC:CMM,0;
2. If there is a DAT/DDS tape in the drive, withdraw it using the eject buttonon the front panel of the CTU.
Close all event log streams on the tape drive.
ZDLC;
3. Block CTU-0 in OMU.
ZISC:,OMU:CTU,0:BL-US;
4. Copy the data from database to disk.
ZDBC:EQUIPM,0;
5. Prevent updates of memory file disk copies and disk updates if databases.
ZDUP:OMU;
ZDBP:EQUIPM,0:DISK;
6. Check that all databases have been unpacked from the disk log to thedatabase.
ZDBX:EQUIPM,0;
7. Block other I/O devices on the same SCSI bus using the ISC command. Itis particularly important to block the WDU.
8. Remove the CTU. See step 8 for more detailed instructions.
9. Check the strappings of the new CTU.
10. Install the new CTU. See step 10 for more detailed instructions.
11. Insert a new DAT/DDS tape into the CTU and wait for loading.
12. Change the state of CTU-0 to TE-ID.
ZISC::CTU,0:TE-ID;
13. Diagnose CTU-0 in OMU.
ZUDD:OMU,0:CTU,0;
14. Change the state of CTU-0 to WO-ID.
ZISC::CTU,0:WO-ID;
15. Change the state of the OMU's WDU-0 first to WO-ID, then to WO-BU.
ZISC:,OMU:WDU,0:WO-ID;
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
63 (72)
Replacing the cartridge tape unit
ZISC:,OMU:WDU,0:WO-BU;
16. Resume updates of memory file disk copies and disk updates of databases.
ZDUR:OMU;
ZDBR:EQUIPM,0:DISK;
Related topics
Introduction to replacing the CTUs and FDUs
Replacing the mass memory units overview
7.2 Replacing the CTU in the STU and CHU
This is how you change a CTU in STU or CHU.
Steps
1. Check the AE-name of the Virtual File Store (VFS) application (QDI)
ZQDI;
2. Lock the VFS application (QDG)
This prevents the Billing Centre's access to the disks during themaintenance task.
ZQDG:<AE-name>,<state change>;
3. Find out the current disk file (IFI)
ZIFI:<unit>,<unit_pair_index>:GSMCHA,S;
The line CURRENT DISK FILE NUMBER in the execution printoutshows the file the system will write to. Write down the current disk filenumber. It will be later referred to as FILE_1.
4. Change the working state of the disk on the same SCSI bus to BL-US(ISC)
The system automatically ensures that the disk in the WO-BU state is thesystem disk.
64 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
ZISC:,<destination unit>,<pair>:WDU,<I/O deviceindex>:<working state>;
5. Change the state of CTU you are changing to BL-US (ISC)
ZISC:,<destination unit>,<pair>:CTU,<I/O deviceindex>:BL-US;
6. Remove the CTU
The correct way to do this depends on the type of the network element(subrack or cartridge):
Subrack CTU, disk units below 1 GB
a. Detach the signal cable of the backup WDU.
b. Switch off power.
c. Detach the signal cable of the CTU.
d. Detach the power cable of the CTU.
e. Remove the CTU.
Subrack CTU, disk units of 1 GB and above
a. Switch off power.
b. Detach the power cable of the CTU.
c. Detach the signal cable of the CTU.
d. Remove the CTU.
Cartridge CTU
a. Switch off power.
b. Remove the CTU.
7. Install the new CTU
The correct way to do this depends on the type of the network element(subrack or cartridge):
Subrack CTU, disk units below 1 GB
a. Install the CTU.
b. Connect the power cable to the CTU.
c. Connect the signal cable to the CTU.
d. Switch on power.
e. Connect the signal cable to the backup WDU.
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
65 (72)
Replacing the cartridge tape unit
Subrack CTU, disk units of 1 GB and above
a. Install the CTU.
b. Connect the power cable to the CTU.
c. Connect the signal cable to the CTU.
d. Switch on power.
Cartridge CTU
a. Install the new CTU.
b. Switch on power.
8. Change the working state of the backup WDU first to WO-ID andthen change the state to WO-BU (ISC)
ZISC:,<destination unit>,<pair>:WDU,<I/O deviceindex>:<working state>;
9. Check that the WDU operates correctly by reading the directorylisting (IWX)
ZIWX:,<destination unit>,<pair>:WB::<filename>,<extension>;
10. Find out which file is now the open charging file and write it down asFILE_2 (IFO)
Repeat the command until an open file is found.
ZIFO:<unit>,<unit_pair_index>:GSMCHA:,OPEN;
11. Set the open file to the FULL status (IFS)
The system now locates the open file and closes it.
ZIFS:<unit>,<unit_pair_index>:GSMCHA:,OPEN:F;
12. Copy all charging files between FILE_1 and FILE_2, (includingFILE_1 and FILE_2), from the system WDU to the backup WDU(IPS)
ZIPS:�<source unit>�,WDU-S,<source path>,<sourcefile name>,:,WDU-B,<destination path>,,;
13. Check that copying was successful.
66 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
ZIPI;
Make sure that the copy task is in the SUCCESS state before continuing.
If the copy task does not change into the SUCCESS state, but remains e.g.in the FAILED state, it is not possible to continue until the fault iscorrected.
14. Delete the old versions of all the copied charging files (from FILE_1 toFILE_2) from the backup WDU (IWD)
ZIWD:,<destination unit>,<pair>:WB::<file name>,<file name extension>,FF;
15. Change the working state of the CTU from WO-BU to TE-ID (ISC)
ZISC:,<destination unit>,<pair>:CTU,<I/O deviceindex>:TE-ID;
16. Insert the tape and diagnose the CTU (UDD)
ZUDD:<main unit type>,<main unit index>:CTU,<deviceindex>;
The diagnosis will take about two minutes. If the result is successful, youwill see Diagnostic Report 3999 DIAGNOSIS EXECUTED� UNIT OKoutput to the alarm printer.
17. List the current tests (UDQ)
ZUDQ;
18. Display the diagnostic history (UDH)
ZUDH:<unit type>,<unit pair>,<unit index>;
19. Change the state of the CTU to WO-ID (ISC)
ZISC:,<destination unit>,<pair>:CTU,<I/O deviceindex>:WO-ID;
20. Unlock the Virtual File Store (VFS) application to restore the BillingCentre's access to the disks (QDG)
ZQDG:<AE-name>,UNL;
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
67 (72)
Replacing the cartridge tape unit
21. Print out the active alarms (AHO)
ZAHO;
Analyse the alarms and find out what caused them
Further information:
Example 11. Changing CTU-0 in CHU
1. Check the AE-name of the Virtual File Store (VFS) application.
ZQDI;
2. Lock the VFS application. This prevents the Billing Centre's access to thedisks during the maintenance task.
ZQDG:VFS,LOC;
3. To find out the current disk file, output alarm limits and statistics in theGSMCHA application of the CHU.
ZIFI:CHU,<chu pair>:GSMCHA:S;
The line CURRENT DISK FILE NUMBER in the execution printoutshows the file the system will write to. Write it down as FILE_1.
4. Change the state of WDU-0 to BL-US.
ZISC:,CHU:WDU,0:BL-US;
5. Change the state of CTU-0 to BL-US.:
ZISC:,CHU:CTU,0:BL-US;
6. Change the CTU.
7. Change the state of CHU's WDU-0 to WO-ID and then to WO-BU.
ZISC:,CHU:WDU,0:WO-ID;
ZISC:,CHU:WDU,0:WO-BU;
8. To check that the WDU operates correctly, output all file labels from thebackup WDU of the CHU.
ZIWX:,CHU:WB,::%,%;
9. Find out which file is now the open charging file and write it down asFILE_2.
ZIFO:CHU,<chu pair>:GSMCHA:,OPEN;
68 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
Repeat the command until an open file is found.
10. Set the status of the open charging file in the CHU to FULL.
ZIFS:CHU,<chu pair>:GSMCHA:,OPEN:F;
11. Copy file named CF0001 with the extension DAT from the system WDUto the backup WDU.
ZIPS:�CHU�,WDU-S,/,CF0001.DAT,:,WDU-B,/,,;
Copy all charging files from FILE_1 to FILE_2 in the same way.
12. Check that copying was successful. Make sure that the copy task is in theSUCCESS state before continuing.
ZIPI;
13. Delete old versions of all charging files CF%.DAT from the backup WDU.
ZIWD:,CHU:WB::CF%,DAT,FF;
Delete old versions of all the copied charging files (from FILE_1 toFILE_2).
14. Change the working state of the CTU from WO-BU to TE-ID.
ZISC:,CHU,0:CTU,0:TE-ID;
15. Insert the tape and diagnose CTU-0 in CHU-0.
ZUDD:CHU,0:CTU,0;
16. List the current tests.
ZUDQ;
17. Check the diagnostic history.
ZUDH:CHU,0;
18. Change the state of CTU-0 to WO-ID.
ZISC:,CHU:CTU,0:WO-ID;
19. Unlock the Virtual File Store (VFS) application.
ZQDG:VFS,UNL;
20. Print out the active alarms.
ZAHO;
Related topics
Introduction to replacing the CTUs and FDUs
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
69 (72)
Replacing the cartridge tape unit
Replacing the mass memory units overview
70 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units
8 Replacing the adapters and cables
These instructions are for changing of the SCSI-terminator, SCSI-adapters, andSCSI-cables.
For instructions on changing SCSIF plug-in units, see Replacing a SCSIF plug-inunit .
Before you start
Before changing adapters or cables, stop all activity on the SCSI bus where youare making changes.
Steps
1. Prevent database updating and file updating
See Preventing and resuming updates of disks and memory file disk copiesfor instructions.
2. Change the working state of all the SCSI devices of the bus you areworking on to the state BL-US (ISC)
ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:BL-US;
3. Change the terminator/adapter/cable
4. Change the working state of the mass memory unit to WO-BU (WDUand FDU) or WO-ID (CTU) (ISC)
Use the command ISC .
5. Resume file updating and database updating
See Preventing and resuming updates of disks and memory file disk copiesfor instructions.
Related topics
dn985329Issue 5-4 en
# Nokia CorporationNokia Proprietary and Confidential
71 (72)
Replacing the adapters and cables
Replacing the mass memory units overview
72 (72) # Nokia CorporationNokia Proprietary and Confidential
dn985329Issue 5-4 en
Changing of Mass Memory Units