hw change

Replacing Plug-in Units and OtherHardware Units

DN70216177Issue 1-0 en

# Nokia Siemens Networks 1 (179)

3GNDOCU3CNEDAC.20Nokia Multimedia Gateway, Rel. U3C, ProductDocumentation

The information in this document 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 Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2007. All rights reserved.

2 (179) # Nokia Siemens Networks DN70216177Issue 1-0 en

Replacing Plug-in Units and Other Hardware Units

Contents

Contents 3

1 Plug-in unit is faulty 5

2 Taking unit out of use 9

3 Replacing plug-in unit with the same variant 15

4 Replacing plug-in unit with newer variant 23

5 Replacing CCPC2–A plug-in unit with CCP10 (OMU) 31

6 Replacing ESA12 plug-in unit with ESA24 41

7 Replacing MCPC2 plug-in unit with MCP18(-B) 49

8 Replacing MCPC2-A plug-in unit with MCP18(-B) 57

9 Replacing interface units 63

10 MCPC2(-A) plug-in unit is faulty 71

11 MCP18(-B) plug-in unit is faulty 75

12 PD20 plug-in unit is faulty 79

13 Fuse in PD20 plug-in unit is faulty 85

14 PD30 plug-in unit is faulty 87

15 Fuse in PD30 plug-in unit is faulty 93

16 ESA12 plug-in unit is faulty 95

17 ESA24 plug-in unit is faulty 103

18 BIE1C/T back interface unit is faulty 109

19 Fan tray is faulty 115

20 Fan tray (FTRA-B) is faulty 127

21 Hard disk is faulty 135

22 NEMU hard disk fails 141

23 MCPC2(-A), Primary operating system disk has failed, disk 0 143



Contents

24 MCPC2(-A), Secondary operating system disk has failed, disk 1 147

25 MCP18(-B), Primary operating system disk has failed, disk 0 151

26 MCP18(-B), Secondary operating system disk has failed, disk 1 155

27 Hard disk (HDS-B) is faulty 159

Related Topics 175



1 Plug-in unit is faultyDescription

When a plug-in unit is faulty, you must replace it with a plug-in unit of thesame or newer variant.

For more information on plug-in units, see either Nokia WCDMA RadioNetwork Controller Plug-in Unit Descriptions or Nokia Multimedia GatewayPlug-in Unit Descriptions in PDF format in NOLS.

Symptoms

A plug-in unit is faulty and needs to be replaced.

Recoveryprocedures

Replacing plug-in unit with the same variant

If you are replacing a plug-in unit with the same variant, follow theinstructions in Replacing plug-in unit with the same variant.

Some plug-in units cannot be replaced by using those instructions. TableInstructions for replacing plug-in units with the same variant gives a list ofthe plug-in units that must be replaced according to instructions specifiedin the latter column.

Table 1. Instructions for replacing plug-in units with the same variant

Plug-in unit See instructions in

MCP18 or MCP18-B (NEMU) MCP18(-B) plug-in unit is faulty

MCPC2 or MCPC2-A (NEMU) MCPC2(-A) plug-in unit is faulty

PD20 (subrack power supply) PD20 plug-in unit is faulty




Plug-in unit is faulty

Table 1. Instructions for replacing plug-in units with the same variant (cont.)

Plug-in unit See instructions in

ESA12 (Ethernet switch) ESA12 plug-in unit is faulty


Replacing plug-in unit with a newer variant

If you are replacing a plug-in unit with a newer variant, follow theinstructions in Replacing plug-in unit with newer variant.

Some plug-in units cannot be replaced by using those instructions. TableReplacing plug-in units with newer variants gives a list of the plug-in unitsthat must be replaced according to instructions specified in the lattercolumn.

Table 2. Replacing plug-in units with newer variants

Old plug-in unit New plug-in unit See instructions in

CCPC2-A (OMU) CCP10 (OMU) Replacing CCPC2–A plug-in unit withCCP10 (OMU)

ESA12 ESA24 Replacing ESA12 plug-in unit withESA24

MCPC2 (NEMU) MCP18 or MCP18-B (NEMU) Replacing MCPC2 plug-in unit withMCP18(-B) plug-in unit

MCPC2-A (NEMU) MCP18 or MCP18-B (NEMU) Replacing MCPC2-A plug-in unit withMCP18(-B)

Replacing other hardware equipment

If you are replacing other hardware equipment, see Table Instructions forreplacing other hardware equipment for which instructions to follow.

Table 3. Instructions for replacing other hardware equipment

Hardware equipment See instructions in

BIE1C or BIE1T back interface unit BIE1C/T back interface unit is faulty

Fan tray Fan tray is faulty

Fan tray (FTRA-B) Fan tray (FTRA-B) is faulty



Table 3. Instructions for replacing other hardware equipment (cont.)

Hardware equipment See instructions in

Fuse in PD20 plug-in unit Fuse in PD20 plug-in unit is faulty


OMU hard disk (HDS9/HDS-A) Hard disk is faulty

NEMU hard disk (HDS9/HDS-A) NEMU hard disk fails

HDS-B NEMU and OMU hard disks HDS-B is faulty

MCPC2 or MCPC2-A (NEMU) primary operatingsystem disk

MCPC2(-A), Primary operating system disk has failed,disk 0

MCPC2 or MCPC2-A (NEMU) secondaryoperating system disk

MCPC2(-A), Secondary operating system disk has failed,disk 1

MCP18 or MCP18-B (NEMU) primary operatingsystem disk

MCP18(-B), Primary operating system disk has failed,disk 0

MCP18 or MCP18-B (NEMU) secondaryoperating system disk

MCP18(-B), Secondary operating system disk has failed,disk 1






2 Taking unit out of usePurpose

Note

Note that the equipment database does not recognise MCPC2,MCPC2-A, MCP18 or MCP18-B plug-in units, and they do not haveworking states.

If you want to diagnose a unit, for example, first change the unit workingstate to TE-EX, then diagnose it and after the diagnosis take the unit backinto use.

If you need to take a unit out of use, the unit working state has to bechanged from WO to TE or SP and then to SE.

If the unit has ongoing tasks (for example, it is currently loading someinformation to disk) which cannot be interrupted in a controlled way, onlyuse the FCD parameter if you have to. It is recommended to wait a whileand try taking the unit out of use again later.

Table 4. The plug-in unit's LED display with different working states

Working state LED display

WO-EX Green

WO-RE Green blink

BL-EX Green

BL-ID Green

BL-RE Green blink

SP-EX Orange

SP-UP Green blink



Taking unit out of use

Table 4. The plug-in unit's LED display with different working states (cont.)

Working state LED display

SP-RE Green blink

TE-EX Red blink

TE-RE Red blink

SE-OU Red

SE-NH None

TR-OU Undefined

Before you start

If you want to remove a plug-in unit, change the state of the unit to SE-NHby following the procedure below.

The following figures describe working state transitions from normalworking state, WO-EX or SP-EX, to SE-NH.

If the unit whose working state you are changing is not redundant or isredundant by the load-sharing principle, change the state of the unitdirectly to TE, or first to BL state and then to TE state.

Figure 1. Taking an SN+ or non-redundant unit out of use using the BLworking state

WO-EX

SE-NH

BL-EX

SE-OU

BL-ID

TE-EX

(by user

(by user

(by system

(by user

(by user

) )

)

))



Figure 2. Taking an SN+ or non-redundant unit out of use, when the unit doesnot have a BL working state

If the unit whose working state you are changing is a 2N or N+1 replacableredundant unit, change the state of the unit first to SP and then to TE.

Figure 3. Taking an active 2N or N+1 redundant unit out of use

Steps

1. Check the unit working state (USI)

ZUSI:<unit type>;

When replacing a plug-in unit, the functional units of the plug-in unitmust be in SE-NH state.

Expected outcome

When the working state of a plug-in unit's functional unit is SE-NH,the LED display is off. In this working state you can continuereplacing the plug-in unit if needed.

Unexpected outcome

If the working state of a plug-in unit's functional unit is other than SE-NH, go to step 2 or 3.

WO-EX(by user

TE-EX(by user

SE-OU(by user

SE-NH) ) )

WO-EX SP-EX

SE-NH

TE-EX

SE-OU

(by user (by user

(by user

(by user

) )

)

)




2. If the working state of the unit you are taking out of use is WO-EX

Then

Change the state of the unit to SP or BL-EX (USC)

ZUSC:<unit type>,<unit index>:SP;

or

ZUSC:<unit type>,<unit index>:BL;

Note

Not all units have BL state.

If the unit has a long-running resource, it will stay in the BL-EX state.In that case, follow the instructions in Working state change fails.

Else

If the unit working state is other than WO-EX, go to the next step

3. Change the unit working state to TE (USC)

ZUSC:<unit type>,<unit index>:TE;

4. Change the unit working state to SE-OU (USC)

ZUSC:<unit type>,<unit index>:SE;

5. Change the unit working state to SE-NH (USC)

Note

A plug-in unit can only be removed when its functional units are in theSE-NH state. Also, a functional unit can only be removed from thesystem after it has been set to the SE-NH state (separated, nohardware) using the USC command.


Example Changing the state of the unit directly to TE



Change the state of A2SU directly from WO to TE, using the FCDparameter.

ZUSC:A2SU,0:TE::FCD;

When you change the state of the unit, the following prompt appearsasking you to confirm the command execution:

FORCED STATE TRANSITION REQUESTED

WO-EX -> TE

CONFIRM COMMAND EXECUTION: Y/N? Y

STATE OF SOME CHILD UNITS MAY ALSO BE CHANGED

CONFIRM COMMAND EXECUTION: Y/N? Y

Example Changing the state of the unit first to BL, then TE and SE

1. Change the working state of the DMCU unit from working state WOto BL-EX.

ZUSC:DMCU,<index>:BL;

When the unit is in working state BL-EX, the system changes it toBL-ID. When the working state is BL-ID, you can proceed andchange it to TE.

2. Change the working state from BL to TE.

ZUSC:DMCU,<index>:TE::;

3. Change the working state from TE to SE-OU.

ZUSC:DMCU,<index>:SE::;

4. Change the working state from SE-OU to SE-NH.

ZUSC:DMCU,<index>:SE::;

Example Changing the state of A2SU unit first to BL, then TE and SE

Change the state of A2SU fromWO to BL, then to TE and SE. Note that forA2SU units you always need to perform a forced state transition usingparameter state transition control.

1. Change the working state of the A2SU unit from WO-EX to BL-ID.

Use the value FCD for the state transition control parameter toset the A2SU from WO-EX to BL-ID.




Note

This command causes disturbances in network traffic.

ZUSC:A2SU,<index>:BL::FCD:;

2. Change the working state from BL-ID to TE-EX.

ZUSC:A2SU,<index>:TE::;

3. Change the working state from TE-EX to SE-OU.

ZUSC:A2SU,<index>:SE::;

4. Change the working state from SE-OU to SE-NH.

ZUSC:A2SU,<index>:SE::;

Example Changing the state of the unit first to SP and then to TE

Change the working state of OMU-1 from WO-EX to TE. Both OMUs are innormal working state

This command activates OMU's switchover. The working state of OMU-1changes to SP-EX and the working state of OMU-0 changes to WO-EX.

ZUSC:OMU,1:SP;

ZUSC:OMU,1:TE;

Example Changing the state of the unit from TE to SE-OU and then toSE-NH

Change the working state of OMU-1 from TE-EX to SE-NH

1. First, change the working state from TE-EX to SE-OU.

ZUSC:OMU,1:SE;

2. Then, change the working state from SE-OU to SE-NH.

ZUSC:OMU,1:SE;



3 Replacing plug-in unit with the samevariant

Purpose

This procedure describes how to replace a plug-in unit with the samevariant. A plug-in unit needs to be replaced if it is faulty or sometimes whenthe network element configuration is changed.

Some plug-in units or hardware equipment cannot be replaced by usingthese instructions. Table Instructions for replacing plug-in units andhardware equipment gives a list of the plug-in units and hardwareequipment that must be replaced according to instructions specified in thelatter column.

Note

When replacing the ESA12 and ESA24 plug-ins with the same variant,first take a backup of the configuration file of the old switch beforeinstalling the new switch.

Table 5. Instructions for replacing plug-in units and hardware equipment

Plug-in unit or hardware equipment See instructions in

MCP18 or MCP18-B (NEMU) MCP18(-B) plug-in unit is faulty

MCPC2 or MCPC2-A (NEMU) MCPC2(-A) plug-in unit is faulty




BIE1C or BIE1T back interface unit BIE1C/T back interface unit is faulty





Table 5. Instructions for replacing plug-in units and hardware equipment(cont.)

Plug-in unit or hardware equipment See instructions in

Fan tray Fan tray is faulty

OMU hard disk Hard disk is faulty

NEMU hard disk NEMU hard disk fails

MCPC2 or MCPC2-A (NEMU) primary operatingsystem disk

MCPC2(-A), Primary operating system disk has failed,disk 0

MCPC2 or MCPC2-A (NEMU) secondaryoperating system disk

MCPC2(-A), Secondary operating system disk has failed,disk 1

MCP18 or MCP18-B (NEMU) primary operatingsystem disk

MCP18(-B), Primary operating system disk has failed,disk 0

MCP18 or MCP18-B (NEMU) secondaryoperating system disk

MCP18(-B), Secondary operating system disk has failed,disk 1

Interface unit Replacing interface units

For more information on plug-in units, see Nokia Multimedia GatewayPlug-in Unit Descriptions or Nokia WCDMA Radio Network ControllerPlug-in Unit Descriptions in PDF format in NOLS. For general instructionson how to install plug-in units, see Installing plug-in units in Installing therMGW and RNC.

Caution

Electrostatic discharge and incorrect installation and uninstallation candamage circuits or shorten their lifetime. To ensure proper functioning ofthe plug-in units during their usual lifetime, take the followingprecautions before handling them:

. Before touching integrated circuits, ensure that you are working in anelectrostatic-free environment.

. Wear an ESD wrist strap or use another corresponding method todischarge static electricity in your body.

NI4S0, NI4S1-B, IPFGE and MDS-A plug-in units include CLASS 1LASER PRODUCT.

For more information on general environmental requirements, seeInstallation Site Requirements for MGW and RNC.



Insert the plug-in unit carefully. It is important to check that the lockingscrews are closed properly, and that the plug-in unit is well in its place.

Before you start

Always check the interchangeability of the spare plug-in unit beforechanging the unit. You can check the interchangeability against theRevision List. The interchangeability sticker is located in the front panel ofthe plug-in unit after the C number. The interchangeability code of the newplug-in unit must be the same as or newer than the old plug-in unit's code.If the interchangeability code of the new plug-in unit is newer than the oldunit's code, check the effects on the interchangeability of the subrack andthe other plug-in units.

It is recommended that you maintain a log of spares so that you can traceany plug-in unit at any time.

Before removing or inserting a plug-in unit, all the functional units of theplug-in unit must be in the SE-NH state. For instructions, see Taking unitout of use.

Steps

1. Remove the faulty plug-in unit from the subrack

Note

The functional units of the plug-in unit must be in SE-NH state before aplug-in unit can be removed.

a. Remove the cable(s) from the front panel of the plug-in unit ifthere are any.

Some plug-in units have LAN or STM-1 cable(s) in the frontpanel.

b. Unscrew locking screws on the front panel of the plug-in unit.

Locking screws keep the plug-in unit in its place. The numberof locking screws depends on the type of the plug-in unit.




Figure 4. Unscrewing locking screws

c. Open the two insertion/extraction levers on the front panel ofthe plug-in unit.

Insertion/extraction levers are locking clamps which securethe plug-in unit to the rack. Insertion/extraction levers arelocated on the upper and lower edge of the plug-in unit.

AllenkeyM2.5

DN02220548



Figure 5. Opening locking clamps and removing plug-in unit

d. Remove the plug-in unit from the subrack.

1

1

2




2. Install the new plug-in unit into the subrack

If you are replacing a CCPC2–A plug-in unit, check the HMSMjumper block. Only the OMU unit can act as an HMS master. Formore information, see Jumper settings of CCPC2-A C100575 inNokia Multimedia Gateway Plug-in Unit Descriptions and NokiaRadio Network Controller Plug-in Unit Descriptions in PDF format inNOLS.

a. Close the insertion/extraction levers on the front panel of theplug-in unit.


b. Close the locking screws carefully.


c. Insert cable(s) to the front panel of the plug-in unit if there areany.


3. Check the compatibility of the HMS node SW version of theplug-in unit

See instructions in Checking the software version of the HMS node.

4. Check the data on the installed plug-in unit (WFL)

ZWFL:P:<cabinet hms number>,<subrack hms number>,<ppa>;

Verify that plug-in unit data is correct.

5. Set the functional units into SE-OU working state (USC)


6. Set the functional units into TE working state (USC)


Wait until all functional units have restarted.

Expected outcome



All the units in the hierarchy should now be in TE-EX working state.

Unexpected outcome

If the unit restart fails, contact your local Nokia Customer ServiceCenter.

7. Check the version of the flash memory boot package of theplug-in unit against the SW package (WDI)

You can check the boot package versions of all functional units of acertain type by giving the name of the functional unit (for example,NIWU) as the value for the unit type parameter.

ZWDI:UT=<unit type>,UI=<unit index>;

For more information on the boot package compatibility andexamples, see Checking and updating the boot package of acomputer unit in Software Configuration Management.

Expected outcome

If the flash memory boot packages are compatible, you cancontinue.

Unexpected outcome

If the flash memory boot packages are not compatible, you mustupdate the boot package. Follow the instructions in Checking andupdating the boot package of a computer unit in SoftwareConfiguration Management.

8. Check that the repair operation was successful by starting totaldiagnosis of the unit (UDU)

ZUDU:<unit type>,<unit index>;

For more information, see Diagnostics and testing.

9. Set the unit to normal working state (USC)

Depending on the redundancy principle of the unit, the normalworking state of the unit is SP-EX or WO-EX.

ZUSC:<unit type>,<unit index>:WO|SP;




10. Check that there are no on-state alarms for the functional unit(AAP)

ZAAP;



4 Replacing plug-in unit with newer variantPurpose

This procedure provides instructions for replacing a plug-in unit with anewer variant of the same plug-in unit.

Some plug-in units cannot be replaced using these instructions. TableReplacing plug-in units with newer variants gives a list of the plug-in unitsthat must be replaced according to instructions specified in the lattercolumn.

Tip

This procedure includes instructions for replacing CCPC2-A plug-inunits with CCP10. There are separate instructions for replacing OMUCCPC2-A plug-in units with OMU CCP10. For more information, seetable Replacing plug-in units with newer variants.

Table 6. Replacing plug-in units with newer variants

Old plug-in unit New plug-in unit See instructions in

CCPC2-A (OMU) CCP10 (OMU) Replacing CCPC2–A plug-in unit withCCP10 (OMU)

ESA12 ESA24 Replacing ESA12 plug-in unit withESA24

MCPC2 (NEMU) MCP18 or MCP18-B (NEMU) Replacing MCPC2 plug-in unit withMCP18(-B)

MCPC2-A (NEMU) MCP18 or MCP18-B (NEMU) Replacing MCPC2-A plug-in unit withMCP18(-B)



Replacing plug-in unit with newer variant

For more information on plug-in units, see either Nokia MultimediaGateway Plug-in Unit Descriptions or Nokia WCDMA Radio NetworkController Plug-in Unit Descriptions in PDF format in NOLS. For generalinstructions on how to install plug-in units, see Installing plug-in units inInstalling the MGW and RNC.


Caution





When replacing a 2N redundant unit, you must replace both units. A mixed2N redundant unit configuration with an older and a newer variant of aplug-in unit is only allowed as a temporary solution during the replacementprocedure.

When replacing an N+1 redundant unit, you do not need to replace all theN+1 redundant units of the same plug-in unit variant. However, thecapacity of the more powerful plug-in unit variants in the unit group isalways limited to the level of the weakest plug-in unit variant.

Before you start

Check the interchangeability of the plug-in units from the Revision List. Ifyou are not sure about the interchangeability of the plug-in unit variants,please refer to the latest RNC or MGW HW Revision List available inNOLS.





Steps

1. Remove the plug-in unit from the subrack






AllenkeyM2.5

DN02220548










1

1

2




2. Delete the HW description data on the old plug-in unit

Follow the instructions in Deleting HW description data whenreplacing plug-in units.

3. Create the HW description data on the new plug-in unit

Follow the instructions in Creating HW description data whenreplacing plug-in units.

4. Install the plug-in unit into the subrack

a. If you are replacing a CCPC2-A plug-in unit with a CCP10 unit,remove the HMS jumpering if that is in place. HMS jumper isnot needed in CCP10.

b. Close the insertion/extraction levers on the front panel of theplug-in unit.


c. Close the locking screws carefully.


d. Insert cable(s) to the front panel of the plug-in unit if there areany.







Expected outcome


Unexpected outcome








Expected outcome


Unexpected outcome





9. Set the unit to WO or SP working state (USC)

Depending on the redundancy principle of the unit, set the unitworking state to WO-EX (SN+ units) or SP-EX (2N or N+1 units).



ZAAP;

11. If the unit you are replacing is 2N redundant, or if you want to changeall the N+1 units at the same time




Then

Make a unit switchover and replace the spare unit (USC)

Note

A mixed 2N pair with an older and newer variant does not maintain fullinput synchronism. For this reason new calls may fail but ongoing callsshould remain during the switchover.

. When replacing a 2N unit, change the working state of thespare unit to WO-EX.

ZUSC:<unit type>,<unit index>:WO;. When replacing an N+1 unit, change the working state of the

next unit in WO-EX state to SP. The N+1 unit in SP-EX statemust be a newer variant.

ZUSC:<unit type>,<unit index>:SP;

Replace the spare unit of the 2N redundant unit or, in case of an N+1redundant unit, the other N+1 units with newer variants.



5 Replacing CCPC2–A plug-in unit withCCP10 (OMU)

Purpose

This procedure provides instructions for replacing a CCPC2–A plug-in unitwith CCP10 when that unit is OMU. Because OMU is a 2N redundant unit,you must replace both the active and the spare unit. A mixed CCPC2–Aand CCP10 2N redundant unit configuration is only allowed as atemporary solution.

For replacing another CCPC2-A unit than OMU, see instructions inReplacing plug-in unit with newer variant.


Caution






Replacing CCPC2–A plug-in unit with CCP10 (OMU)



Before you start

Check the interchangeability of the plug-in units from the Revision List. Ifyou are not sure about the interchangeability of the plug-in unit variants,please refer to the latest RNC or MGW HW Revision List available inNOLS.

The upgrade set includes the hardware needed in the upgrade. Check thatyou have the following:

. one temporary cable for the upgrade (CJGA), needed because ofswitching between I/O devices

. one MDS-A plug-in unit and adapter

. two CCP10 plug-in units and 1-4 GB memory

Both units need 512 MB - 2 GB of memory. Both units must have thesame amount of memory.

. two HDS-A plug-in units and adapters

. two LAN cables for both OMU units (CA_130, CA_131, CA_138, andCA_139), type CHUS for ESA12 and CHES for ESA24

. 15 SCSI cables (CA_075 - CA_089), type CHS

Also create a fallback copy of the software build before starting theupgrade.

Note

Returning to the previously used HW/SW level is not possible after thesuccessful completion of the upgrade.



Note

Before removing or inserting a plug-in unit, both CCPC2-As and all theother units which are connected to the OMU must be in the SE-NHstate. For instructions, see Taking unit out of use.

Steps

1. Set SCSI bus 0 to SE-NH state (IHE)

a. Set SCSI bus 0 to TE-EX state.

ZIHE:OMU:SCSI,0:TE;

b. Set SCSI bus 0 to SE-OU state.

ZIHE:OMU:SCSI,0:SE;

c. Set SCSI bus 0 to SE-NH state.

ZIHE:OMU:SCSI,0:SE;

2. Remove the CCPC2-A plug-in unit (OMU-1) from the subrack

a. Remove the LAN cables from the front panel of the plug-inunit.


Locking screws keep the plug-in unit in its place. The numberof locking screws depends on the type of the plug-in unit. SeeFigure Unscrewing locking screws in Replacing plug-in unitwith newer variant.


Insertion/extraction levers are locking clamps which securethe plug-in unit to the rack. Insertion/extraction levers arelocated on the upper and lower edge of the plug-in unit. SeeFigure Opening locking clamps and removing plug-in unit inReplacing plug-in unit with newer variant.


3. Delete the HW description data on CCPC2-A (OMU-1)

Delete the functional unit description for OMU-1 and the portconnections and plug-in unit description of CCPC2-A. Follow theinstructions in Deleting HW description data when replacing plug-inunits.

4. Delete the HW description data on the old disk drives

Perform the following actions for both MDS-0 and WDU-0:




a. Delete and detach the functional unit description. Forinstructions, see Deleting and detaching functional unitdescription.

b. Delete the plug-in unit description. For instructions, seeDeleting plug-in unit description.

5. Remove the old SCSI components

Note

Remove the CCPC2-A plug-in unit (OMU-1) from the subrack beforeremoving the SCSI components.

Remove the following:. WDU-0. MDS-0. All SCSI cables of bus 0. The SCSI cable between OMU-1 and WDU-1

For detailed information, see Cable Lists in Site documents.

6. Install the temporary SCSI cable (CJGA) between OMU-1 andWDU-1

The following tables shows the cable locations:

Table 7. CJGA cable between OMU-1 and WDU-1

OMU-1 Connector WDU-1 Connector

1.0 2.0B 16.5H 3 1.0 2.0B 3W 1

1.0 2.0B 16.5O 4 1.0 2.0B 4C 2

1.0 2.0B 16.5U 5

7. Create the HW description data on the new disk drives

Perform the following actions for MDS-0:



a. Create plug in unit description for MDS-A. For instructions, seeCreating plug-in unit description.

b. Create and attach the functional unit description. Forinstructions, see Creating and attaching functional unitdescription.

Perform the following actions for WDU-0:

a. Create plug in unit description for HDS-A. For instructions, seeCreating plug-in unit description.

b. Create and attach the functional unit description. Forinstructions, see Creating and attaching Hard Disk Drive(WDU) description.

Perform the following actions for WDU-1:

a. Create plug in unit description for HDS-A. For instructions, seeCreating plug-in unit description.

b. Create and attach the functional unit description. Forinstructions, see Creating and attaching Hard Disk Drive(WDU) description.

8. Create the HW description data on CCP10

Create the plug-in unit description for CCP10, connect the ports forCCP10, and create and attach the OMU-1 functional unit. Note thatyou cannot check the software version of the HMS node before youhave installed the plug-in unit.

Note that the SCSI port locations are different in CCP10 and inCCPC2-A.


9. Install the CCP10 plug-in unit into the subrack

Note

Create the HW description data on CCP10 plug-in unit before installingit.

a. Before inserting CCP10 into to the subrack, install the HMSmaster net cables to the new position.

b. Remove the HMS jumpering if that is in place. HMS jumper isnot needed in CCP10.




c. Close the insertion/extraction levers on the front panel of theplug-in unit.


d. Close the locking screws carefully.


e. Insert LAN cables to the back panel of the plug-in unit.

10. Check the software version of the HMS node of CCP10

For instructions, see Checking the software version of the HMSnode.

11. Set OMU-1 into SE-OU working state (USC)

ZUSC:OMU,1:SE;

12. Set OMU-1 into TE working state (USC)

ZUSC:OMU,1:TE;

Wait until the unit has restarted. If the restart fails, contact your localNokia Customer Service Center.

13. Check the version of the CCP10 flash memory boot packageagainst the software package (WDI)

ZWDI:UT=OMU,UI=1;


Expected outcome


Unexpected outcome




14. Check that the repair operation was successful by starting totaldiagnosis of OMU-1 (UDU)

ZUDU:OMU,1;


15. Set OMU-1 to SP working state (USC)

ZUSC:OMU,1:SP;

16. Check that there are no on-state alarms for OMU-1 (AAP)

ZAAP;

17. Make the unit switchover (USC)

Only one switchover is allowed for OMU units.

Note

A mixed 2N pair with an older and newer variant does not maintain fullinput synchronism. For this reason new calls may fail but ongoing callsshould remain during the switchover.

ZUSC:OMU,1:WO;

18. Repeat steps 2-4 for OMU-0

Remove the OMU-0 CCPC2-A from the subrack. Delete the HWdescription data for the CCPC2-A and OMU-0.

19. Remove the SCSI cable between OMU-0 and WDU-1

20. Install the new SCSI cables for bus 0

Install the SCSI cables between OMU-0, WDU-0, MDS-0, and OMU-1.

21. Move the disk drive and the FDU drive into the new plug-in units

Move the disk drive of WDU-0 into the HDS-A plug-in unit and theMDS-0 into the MDS-A plug-in unit. Insert the new plug-in units intothe subrack.




22. Set SCSI bus 0 to WO-EX state (IHE)

a. Set SCSI bus 0 to SE-OU state.

ZIHE:OMU:SCSI,0:SE;

b. Set SCSI bus 0 to TE-EX state.

ZIHE:OMU:SCSI,0:TE;

c. Set SCSI bus 0 to WO-EX state.

ZIHE:OMU:SCSI,0:WO;

Wait until both WDU-0 and MDS-0 on SCSI bus 0 also change intoWO-EX and the mirroring completes. You can check the states withthe following command:

ZIHI:OMU:WDU;

If the mirroring is not complete, the states show the MIR and LCKflags.

If the states of WDU-0 and MDS-0 do not change to WO-EX, changethe states manually.

23. Set SCSI bus 1 to SE-NH state (IHE)

a. Set SCSI bus 0 to TE-EX state.

ZIHE:OMU:SCSI,1:TE;

b. Set SCSI bus 0 to SE-OU state.

ZIHE:OMU:SCSI,1:SE;

c. Set SCSI bus 0 to SE-NH state.

ZIHE:OMU:SCSI,1:SE;

24. Remove the temporary SCSI cable (CJGA) and the WDU-1 plug-in unit

25. Install the new SCSI cables for SCSI bus 1

Install the SCSI cables between OMU-0, WDU-1, and OMU-1.

26. Move the disk drive into the new plug-in unit

Move the disk drive of WDU-1 into the HDS-A plug-in unit. Insert thenew plug-in units into the subrack.

27. Set SCSI bus 1 to WO-EX state (IHE)

a. Set SCSI bus 1 to SE-OU state.

ZIHE:OMU:SCSI,1:SE;



b. Set SCSI bus 1 to TE-EX state.

ZIHE:OMU:SCSI,1:TE;

c. Set SCSI bus 1 to WO-EX state.

ZIHE:OMU:SCSI,1:WO;

Wait until WDU-1 on SCSI bus 1 also changes into WO-EX and themirroring completes. You can check the state with the followingcommand:

ZIHI:OMU:WDU;

If the mirroring is not complete, the state shows the MIR and LCKflags.

If the state of WDU-1 does not change to WO-EX, change the statemanually.

28. Repeat steps 8 - 15 for the other CCP10 plug-in unit (OMU-0)

29. Delete the old software packages

Delete the SW packages that are not needed anymore. Switchingover to the previously used HW/SW level is not possible after theupgrade.

30. Create a fallback copy of the new software package






6 Replacing ESA12 plug-in unit withESA24

Purpose

This procedure shows how to replace an ESA12 plug-in unit with ESA24.

For more information on plug-in units and cables and general instructionson how to install plug-in units, see Installing the MGW and RNC.

Note that the equipment database does not recognise ESA12 or ESA24,and it does not have working states.

Caution

Electrostatic discharge and incorrect installation and uninstallation candamage circuits or shorten their lifetime. To ensure proper functioning ofthe plug-in units during their usual lifetime, take the followingprecautions before handling them.






Replacing ESA12 plug-in unit with ESA24

Note


Before you start

If you are not sure about the interchangeability of the plug-in unit variants,please refer to the latest MGW HW Revision List available in NOLS.


You need to block the alarm 3053 (ETHERNET INTERFACE FAILURE)before replacing the unit and unblock it after you have replaced the unit.

1. Block the alarm 3053.

AFB:3053::RES::;

2. Change the plug-in unit as described in the steps 1-13.

3. After changing the plug-in unit, unblock the alarm 3053.

ZAFU:3053::;.

Steps

1. Remove the LAN cable(s) from the front panel of ESA12

Table 8. LAN cables to be removed from ESA12 when plug-in unit for OMU isCCP10 in MGW

Equip.

No

CABLE FROM CABLE TO Type Use

FU Position/Conn.

FU Position/Conn.

CA_130 ESA12 1.0F 12.ETH 3 OMU 0 1.0B 16.3B CHUS012 LAN 1)

CA_131 ESA12 1.0F 12.ETH 4 OMU 1 2.0B 16.3B CHUS012 LAN 1)

CA_132 ESA12 1.0F 12.ETH 5 NEMU/

MCP18(-B)

1.0B 13.3B CHUS048 LAN

NEMU/

MCPC2(-A)

1.0F 13.ETH 1 CNI006

1) Cabling from bottom



Table 9. LAN cables to be removed from ESA12 when plug-in unit for OMU isCCPC2–A in MGW

Equip.

No


FU Position/Conn.

FU Position/Conn.

CA_130 ESA12 1.0F 12.ETH3 OMU 0 1.0F 16.ETH CNI007 LAN

CA_131 ESA12 1.0F 12.ETH4 OMU 1 2.0F 16.ETH CNI012 LAN

CA_132 ESA12 1.0F 12.ETH5 NEMU/

MCP18(-B)

1.0B 13.3B CHUS048 LAN

NEMU/

MCPC2(-A)

1.0F 13.ETH1 CNI006

2. Unscrew the locking screws on the front panel of ESA12

Table 10. ESA12 to be removed

Position ID Name FU

Subrack 1

F12 C72490 ESA12 (NEMU)

Locking screws keep the plug-in unit in its place. Locking screws arelocated on top of the insertion/extraction levers. See FigureUnscrewing locking screws in Replacing plug-in unit with newervariant.

3. Open insertion/extraction levers on the front panel of ESA12

Insertion/extraction levers are locking clamps which secure the plug-in unit to the rack. Insertion/extraction levers are located on theupper and lower edge of the plug-in unit. See Figure Opening lockingclamps and removing plug-in unit in Replacing plug-in unit withnewer variant.

4. Double-click (within two seconds) the reset switch in the frontpanel of ESA12




The electricity switches off from the unit. There is no light in the LEDlight which is in the front panel of the ESA12 plug-in unit.

The electricity will be off for 20 seconds.

5. Remove ESA12 from the subrack within 20 seconds

If you do not remove the unit within 20 seconds, the unit willautomatically restart itself.

6. Install new cabling for ESA24

ESA24 has cables in the back side of the subrack.

Table 11. ESA24 LAN cables for ISU use (in MGW)

Equip.

No


FU Conn. FU Conn.

CA_135 ESA24 0 1.0B 12.4J ISU 0 2.0B 3.3B CHES015 LAN

CA_136 ESA24 0 1.0B 12.4P ISU 1 3.0B 16.3B CHES013 LAN

CA_137 ESA24 0 1.0B 12.4R ISU 2 4.0B 16.3B CHES023 LAN

CB0_135 ISU 3 1.0B 16.3 B ESA24 0 1.0B 12.4T CHES020 LAN

CB0_136 ISU 4 2.0B 16.3 B ESA24 0 1.0B 12.4V CHES022 LAN

CB0_137 ISU 5 3.0B 16.3 B ESA24 0 1.0B 12.4X CHES026 LAN

CB0_138 ISU 6 4.0B 16.3 B ESA24 0 1.0B 12.4Z CHES030 LAN

CC0_135 ISU 7 1.0B 16.3 B ESA24 0 1.0B 12.5B CHES032 LAN

CC0_136 ISU 8 2.0B 16.3 B ESA24 0 1.0B 12.5D CHES034 LAN

CC0_137 ISU 9 3.0B 16.3 B ESA24 0 1.0B 12.5F CHES038 LAN

CC0_138 ISU 10 4.0B 16.3 B ESA24 0 1.0B 12.5H CHES042 LAN

CA_140 ESA24 1 3.0B 13.4J ISU 0 2.0B 3.3D CHES006 LAN

CA_141 ESA24 1 3.0B 13.4P ISU 1 3.0B 16.3D CHES006 LAN

CA_142 ESA24 1 3.0B 13.4R ISU 2 4.0B 16.3D CHES013 LAN

CB0_139 ISU 3 1.0B 16.3D ESA24 1 3.0B 13.4T CHES026 LAN

CB0_140 ISU 4 2.0B 16.3D ESA24 1 3.0B 13.4V CHES022 LAN

CB0_141 ISU 5 3.0B 16.3D ESA24 1 3.0B 13.4X CHES018 LAN



Table 11. ESA24 LAN cables for ISU use (in MGW) (cont.)

Equip.

No


FU Conn. FU Conn.

CB0_142 ISU 6 4.0B 16.3D ESA24 1 3.0B 13.4Z CHES022 LAN

CC0_139 ISU 7 1.0B 16.3D ESA24 1 3.0B 13.5B CHES036 LAN

CC0_140 ISU 8 2.0B 16.3D ESA24 1 3.0B 13.5D CHES032 LAN

CC0_141 ISU 9 3.0B 16.3D ESA24 1 3.0B 13.5F CHES028 LAN

CC0_142 ISU 10 4.0B 16.3D ESA24 1 3.0B 13.5H CHES032 LAN

Table 12. ESA24 LAN cables to be installed when plug-in unit for OMU isCCP10 (in MGW)

Equip.

No


FU Conn. FU Conn.

CA_130 ESA24 0 1.0B 12.4C OMU 0 1.0B 16.3B CHES006 LAN

CA_131 ESA24 0 1.0B 12.4E OMU 1 2.0B 16.3B CHES012 LAN

CA_138 ESA24 1 3.0B 13.4C OMU 0 1.0B 16.3D CHES018 LAN

CA_139 ESA24 1 3.0B 13.4E OMU 1 2.0B 16.3D CHES012 LAN

CA_132 ESA24 0 1.0B 12.4G NEMU/

MCP18

1.0B 13.3B CHES006 LAN

NEMU 0/

MCP2(-A)

1.0F 13.ETH1 CHUS048

CA_133 ESA24 1 3.0B 13.4G NEMU/

MCP18

1.0B 13.3D CHES014 LAN

NEMU/

MCP2(-A)





Table 13. ESA24 LAN cables to be installed when plug-in unit for OMU isCCPC2–A (in MGW)

Equip.

No


FU Conn. FU Conn.

CA_130 ESA 24 0 1.0B 12.4C OMU 0 1.0F 16.ETH1 CHUS012 LAN

CA_131 ESA 24 0 1.0B 12.4E OMU 1 2.0F 16.ETH1 CHUS012 LAN

CA_132 ESA 24 0 1.0B 12.4G NEMU/

MCP18

1.0B 13.3B CHES006 LAN

NEMU/

MCP2(-A)


CA_133 ESA 24 1 3.0B 13.4G NEMU/

MCP18

1.0B 13.3D CHES014 LAN

NEMU/

MCP2(-A)


Note

Before cabling, remember to activate STP/RSTP/MSTP according tothe planned resiliency method. Alternatively, remove the factoryattached cable. See IP connection configuration documentation formore information.

Table 14. ESA24 LAN cable between Ethernet switches (in MGW)

Equip.

No


FU Conn. FU Conn.

CA_134 ESA 24 1 3.0B 13.5K ESA24 0 1.0B 12.5K CHES018 LAN (MGW)

7. Install terminators (ADMOD address modules) for ESA24



Table 15. Address setting modules to be installed for ESA24 (in MGW)

Position ID Name FU Use

1.0B 12.1S C108585 ADMOD01 ESA24 Cabinet address settingmodule

1.0B 12.1U C108585 ADMOD01 ESA24 Subrack address settingmodule

3.0B 13.1S C108585 ADMOD01 ESA24 Cabinet address settingmodule

3.0B 13.1U C108690 ADMOD03 ESA24 Subrack address settingmodule

8. Insert ESA24 in its location

Table 16. ESA24 to be installed

Position ID Name FU

Subrack 1

F12 C108427 ESA24 (NEMU)

9. Close the insertion/extraction levers on the front panel ofESA24

10. Close the locking screws carefully

11. Configure ESA24

You have to configure the ESA24 unit before taking it into use. Forinstructions, see Configuring ESA24 in IP Connection Configurationfor MGW.

12. Insert the LAN cable(s) to the front panel of ESA24

13. Configure or upgrade the ESA24 software

For more information, see section Upgrading ESA24 software inSoftware Configuration Management and the ESA24 User Guide.






7 Replacing MCPC2 plug-in unit withMCP18(-B)

Purpose

This procedure provides instructions for replacing an MCPC2 plug-in unit(NEMU) that is used with HDS/HDS9/HDS-A plug-in units with MCP18 orMCP18-B (NEMU) that is used with HDS-A plug-in units.

Note

NEMU software must be re-installed after replacing the MCPC2 plug-inunit with MCP18(-B), because of new hardware architecture in the newNEMU plug-in unit. Instructions are available from the SoftwareDelivery service in NOLS or from your local Nokia Customer ServiceCenter.

For more information on plug-in units and cables, see either NokiaMultimedia Gateway Plug-in Unit Descriptions and Cable Lists for MGW orNokia WCDMA Radio Network Controller Plug-in Unit Descriptions andCable Lists for RNC in PDF format in NOLS. For general instructions onhow to install plug-in units, see Installing plug-in units in Installing theMGW and RNC.



Replacing MCPC2 plug-in unit with MCP18(-B)

Caution





Note that the equipment database does not recognise MCPC2, MCP18 orMCP18-B, and they do not have working states.

Before you start

If you are not sure about the interchangeability of the plug-in unit variants,please refer to the latest RNC or MGW HW Revision List available inNOLS.


When replacing the MCPC2 (NEMU) plug-in unit with the MCP18 orMCP18-B plug-in unit, you must also replace the two HDS plug-in units(HDD 0 and HDD 1) with HDS-A plug-in units.

Steps

1. Shut down NEMU by selecting Shut down from the Start menu

When the Shut Down Windows message appears, select Shut downand confirm this by clicking OK in the dialog box.

2. Wait until the message appears that it is now safe to turn offyour computer



3. Remove the LAN cable(s) from the front panel of the MCPC2(NEMU) and the front panel of ESA12 or the back panel of theESA24 plug-in units and, if necessary, tie the cable(s) to thecable-shelf

Table 17. LAN cables to remove when MCPC2 is in use

Equip.No


FU Position/Conn. FU Position/Conn.

RNC:

CA_132 ESA 12 1.0F 12.ETH 5 NEMU/MCPC2

1.0F 13 ETH 1 CNI006 LAN(RNC)

ESA 24 1.0B 12.4G NEMU/MCPC2

1.0F 13 ETH 1 CHUX048 LAN 1)(RNC)

MGW:

CA_132 ESA 12 1.0F 12.ETH 5 NEMU/MCPC2

1.0F 13 ETH 1 CNI006 LAN(MGW)

ESA 24 0 1.0B 12.4G NEMU/MCPC2

1.0F 13 ETH 1 CHUS048 LAN 1)(MGW)

CA_133 ESA 24 1 3.0B 13.4G NEMU/MCPC2


1) Cabling from the bottom, tie the cable(s) to the cable shelf

4. Remove the MCPC2 (NEMU) plug-in unit

a. Unscrew locking screws on the front panel of the plug-in unit.


b. Open the two insertion/extraction levers on the front panel ofthe plug-in unit.


c. Double click (within two seconds) the reset switch in the frontpanel of MCPC2.

The electricity switches off. There is no light in the LED lightwhich is in the front panel of the plug-in unit.






The MCPC2 plug-in unit must be removed from the subrackwithin 20 seconds, or it will automatically restart itself.

5. Remove SCSI cabling between the MCPC2 (NEMU) and the HDS(HDD) plug-in units

The cables are located in the back panel of the subrack.

Table 18. SCSI cables to remove when MCPC2 (NEMU) and HDS are in use(RNC and MGW)

Equip.No.


FU Conn. FU Conn.

CA_030 NEMU 1.0B 13.4P HDD 0 (NEMU) 1.0B 14.3Q CJA002 SCSI bus

CA_031 NEMU 1.0B 13.4C HDD 0 (NEMU) 1.0B 14.3H CJB002 SCSI bus

CA_032 HDD 0 (NEMU) 1.0B 14.3W HDD 1 (NEMU) 2.0B 14.3H CJA005 SCSI bus

CA_033 HDD 0 (NEMU) 1.0B 14.4C HDD 1 (NEMU) 2.0B 14.3O CJB005 SCSI bus

6. Insert LAN cable(s) to the back panel of the MCP18(-B) (NEMU)and the front panel of ESA12 or the back panel of the ESA24plug-in units

For information on the routing of the cables, see Cable List for RNCand Cable Lists for MGW in site documents.

Table 19. LAN cables to install with MCP18(-B)

Equip.No


FU Position/Conn.

FU Position/Conn.

RNC:

CA_132 ESA 12 1.0F 12.ETH 5 NEMU/MCP18-B

1.0B 13.3B CHUS048 LAN(RNC)

ESA 24 1.0B 12.4G NEMU/MCP18-B

1.0B 13.3B CHES006 LAN(RNC)

MGW:



Table 19. LAN cables to install with MCP18(-B) (cont.)

Equip.No


FU Position/Conn.

FU Position/Conn.

CA_132 ESA 12 1.0F 12.ETH 5 NEMU/MCP18 1.0B 13.3B CHUS048 LAN(MGW)

ESA 24 0 1.0B 12.4G NEMU/MCP18 1.0B 13.3B CHES006 LAN(MGW)

CA_133 ESA 24 1 3.0B 13.4G NEMU/MCP18 1.0B 13.3D CHES018 LAN(MGW)

7. Install the new SCSI cabling between MCP18(-B) (NEMU) andthe HDS-A (HDD) plug-in units

Table 20. SCSI cables to install when MCP18(-B) (NEMU) and HDS-A are inuse (RNC and MGW)

Equip.No.


FU Conn. FU Conn.

RNC and MGW:

CA_090 NEMU 1.0B 13.4P HDD 0(NEMU)

1.0B 14.3F CHS004 SCSI bus 0

CA_091 NEMU 1.0B 13.4V HDD 0(NEMU)

1.0B 14.3M CHS004 SCSI bus 0

CA_092 NEMU 1.0B 13.5B HDD 0(NEMU)

1.0B 14.3S CHS004 SCSI bus 0

CA_093 NEMU 1.0B 13.5H HDD 1(NEMU)

2.0B 14.3F CHS010 SCSI bus 1

CA_094 NEMU 1.0B 13.5O HDD 1(NEMU)

2.0B 14.3M CHS010 SCSI bus 1

CA_095 NEMU 1.0B 13.5U HDD 1(NEMU)

2.0B 14.3S CHS010 SCSI bus 1

8. Remove the two HDS (HDD 0 and HDD 1) plug-in units from thesubrack




Note

Mark the plug-in units so that you know which is HDD 0 and which isHDD 1.

a. Unscrew locking screws on the front panel of the plug-in units.Locking screws keep the plug-in unit in its place. The numberof locking screws depends on the type of the plug-in unit. Formore information see figure Unscrewing locking screws inReplacing plug-in unit with newer variant.

b. Open the two insertion/extraction levers on the front panel ofthe plug-in units. Insertion/extraction levers are locking clampswhich secure the plug-in unit to the rack. Insertion/extractionlevers are located on the upper and lower edge of the plug-inunit. For more information see figure Opening locking clampsand removing plug-in unit in Replacing plug-in unit with newervariant.

c. Remove the plug-in units from the subrack.

9. Remove hard disks from the HDS plug-in units

a. Remove the power cables and SCSI cables from the HDSplug-in unit.

b. Open the cross-point screws. The hard disk is attached to theHDS with four recessed head screws.

10. Install hard disks to the HDS-A plug-in units

a. Attach the hard disks to the HDS-A plug-in units with cross-point screws.

b. Insert the power cables and SCSI cables to the HDS-A plug-inunit.

11. Install the MCP18 or MCP18-B (NEMU) plug-in unit and the twoHDS-A (HDD) plug-in units into the subrack

Note




Note

Do not reverse the position of the HDD 0 and HDD 1. Keep the disks inthe same order as they were when using the MCPC2 plug-in unit.

a. Close the insertion/extraction levers on the front panel of theplug-in units.

Insertion/extraction levers are locking clamps which securethe plug-in units to the rack. Insertion/extraction levers arelocated on the upper and lower edge of the plug-in unit.


Locking screws keep the plug-in units in its place. The numberof locking screws depends on the type of the plug-in unit.

12. Re-install NEMU software

For instructions on installing NEMU software, see the SoftwareDelivery service in NOLS or contact your local Nokia CustomerService Center.

13. Note down the change of the plug-in unit variant

Note down in Equipment Lists in Site Documentation when you havereplaced a plug-in unit with a newer variant.






8 Replacing MCPC2-A plug-in unit withMCP18(-B)

Purpose

This procedure provides instructions for replacing an MCPC2-A plug-inunit (NEMU) that is used with HDS/HDS9/HDS-A plug-in units with MCP18or MCP18-B (NEMU) that is used with HDS-A plug-in units.

Note

NEMU software must be re-installed after replacing the MCPC2-A plug-in unit with MCP18(-B), because of new hardware architecture in thenew NEMU plug-in unit. Instructions are available from the SoftwareDelivery service in NOLS or from your local Nokia Customer ServiceCenter.

For more information on plug-in units and cables, see either NokiaMultimedia Gateway Plug-in Unit Descriptions and Cable Lists for MGW orNokia WCDMA Radio Network Controller Plug-in Unit Descriptions andCable Lists for RNC in PDF format in NOLS. For general instructions onhow to install plug-in units, see Installing plug-in units in Installing theMGW and RNC.



Replacing MCPC2-A plug-in unit with MCP18(-B)

Caution





Note that the equipment database does not recognise MCPC2-A, MCP18or MCP18-B, and they do not have working states.

Before you start

If you are not sure about the interchangeability of the plug-in unit variants,please refer to the latest RNC or MGW HW Revision List available inNOLS.


Steps




3. Remove the LAN cable(s) from the front panel of the MCPC2-A(NEMU) and the front panel of ESA12 or the back panel ofESA24 plug-in units, and, if necessary, tie the cable(s) to thecable-shelf



Table 21. LAN cables to remove when MCPC2-A is in use

Equip.No



RNC:

CA_132 ESA 12 1.0F 12.ETH 5 NEMU/MCPC2-A

1.0F 13 ETH 1 CNI006 LAN(RNC)

ESA 24 1.0B 12.4G NEMU/MCPC2-A

1.0F 13 ETH 1 CHUX048 LAN 1)(RNC)

MGW:

CA_132 ESA 12 1.0F 12.ETH 5 NEMU/MCPC2-A

1.0F 13 ETH 1 CNI006 LAN(MGW)

ESA 24 0 1.0B 12.4G NEMU/MCPC2-A


CA_133 ESA 24 1 3.0B 13.4G NEMU/MCPC2-A


1) Cabling from the bottom, tie the cable(s) to the cable shelf

4. Remove serial interface cables CA_306 and CA_307 (MGW only)

Table 22. Serial interface cables to remove when MCPC2-A is in use (MGWonly)

Equip.No



CA_306 NEMU 1.0B 13U CM 0 1.0F 6.SER1 CHUR045 Serialinterface

CA_307 NEMU 1.0B 13.1Y OMU 0 1.0F 16.SER1 CHUR044 Serialinterface

5. Remove the MCPC2-A (NEMU) plug-in unit from the subrack

a. Unscrew locking screws on the front panel of the plug-in unit.





b. Open the two insertion/extraction levers on the front panel ofthe plug-in unit.


c. Double click (within two seconds) the reset switch in the frontpanel of MCPC2-A.




The MCPC2-A plug-in unit must be removed from the subrackwithin 20 seconds, or it will automatically restart itself.

6. Update the SCSI cabling from hard disk 0 - hard disk 1 to NEMU– hard disk 1

Remove the hard disk 0 ends of the cables CA_093, CA_094 andCA_095 between hard disk 0 and hard disk 1 and install them toNEMU.

Table 23. Removed WDU 0 ends of the CA_093, CA_094 and CA_095 cables

Equip.No

CABLE FROM

FU Position/Conn.

CA_093 hard disk 0(NEMU)

1.0B 14.3Y


1.0B 14.4E


1.0B 14.4P

Table 24. Updated SCSI cabling between NEMU and WDU 1 when MCP18(-B) is in use

Equip.No





Table 24. Updated SCSI cabling between NEMU and WDU 1 when MCP18(-B) is in use (cont.)

Equip.No



CA_093 NEMU 1.0B 13.5H hard disk 1(NEMU)

2.0B 14.3F CHS010 SCSI bus1

CA_094 NEMU 1.0B 13.5O hard disk 1(NEMU)

2.0B 14.3M CHS010 SCSI bus1

CA_095 NEMU 1.0B 13.5U hard disk 1(NEMU)

2.0B 14.3S CHS010 SCSI bus1

7. Install the MCP18 or MCP18-B plug-in unit into the subrack

Note


a. Close the insertion/extraction levers on the front panel of theplug-in units.

Insertion/extraction levers are locking clamps which securethe plug-in units to the rack. Insertion/extraction levers arelocated on the upper and lower edge of the plug-in unit.


Locking screws keep the plug-in units in its place. The numberof locking screws depends on the type of the plug-in unit.

8. Insert the LAN cable(s) to the back panel of the MCP18(-B)(NEMU) and the front panel of the ESA12 or the back panel ofthe ESA24 plug-in units

For information on the routing of the cables, see Cable List for RNCand Cable Lists for MGW in site documents.

Table 25. LAN cables to install with MCP18(-B)

Equip.No






Table 25. LAN cables to install with MCP18(-B) (cont.)

Equip.No



RNC:

CA_132 ESA 12 1.0F 12.ETH 5 NEMU/MCP18-B

1.0B 13.3B CHUS048 LAN (RNC)

ESA 24 1.0B 12.4G NEMU/MCP18-B

1.0B 13.3B CHES006 LAN (RNC)

MGW:

CA_132 ESA 12 1.0F 12.ETH 5 NEMU/MCP18

1.0B 13.3B CHUS048 LAN(MGW)

ESA 24 0 1.0B 12.4G NEMU/MCP18

1.0B 13.3B CHES006 LAN(MGW)

CA_133 ESA 24 1 3.0B 13.4G NEMU/MCP18

1.0B 13.3D CHES018 LAN(MGW)

9. Re-install NEMU software

For instructions on installing NEMU software, see the SoftwareDelivery service in NOLS or contact your local Nokia CustomerService Center.



9 Replacing interface unitsPurpose

This procedure provides instructions for replacing an interface unit with thesame or a newer variant.

This procedure can also be used for replacing the following interface unitswith a different type of an interface unit.

Table 26. Replacing interface units

Procedure Old unit New unit

Replacing NIWU with IWS1E/T(MGW)

IW16P1/A IW1S1

Replacing IWS1E/T with NIWU(MGW)

IW1S1 IW16P1/A

Replacing NIS1/NIS1P withNIP1 (RNC and MGW)

NI4S1-B NI16P1A

Replacing NIP1 with NIS1/NIS1P (RNC and MGW)

NI16P1A NI4S1-B

Note

When using these instructions for replacing an interface unit with thesame or a newer variant, it is not necessary to delete the interfaces,since the same interfaces will be applicable for the new unit.




Replacing interface units


Caution





When replacing a 2N redundant unit, you must replace both units. A mixed2N redundant unit configuration with an older and a newer variant of thesame plug-in unit is only allowed as a temporary solution.

Before you start



Caution

Traffic related to the interface unit cannot get through during thereplacement of the network element. You should first block the affectedresources before changing the interface unit.



Note

Before replacing an interface unit with a different type of an interfaceunit, all circuits related to the old unit must be deleted.

Steps

1. Change the old unit you want to replace into SE-NH state.

For instructions, see Taking unit out of use

2. If the interface unit is an ATM interface unit (i.e. NI4S1-B orNI16P1A)

Then

Proceed through the following the steps related to ATMinterface units

Note

Make a list of the interfaces of the old unit before deleting them.

a. Delete all ATM interfaces created for the old unit. Forinstructions, see Deleting ATM resources

i. Interrogate the exchange terminals belonging to the oldunit ZUSI:<unit type>,<unit index>::FULL;

ii. Interrogate the affected physical TTP by checking theexchange terminal configuration

ZYAI:PET;

ZYAI:SET;

iii. Interrogate the affected ATM interface by the physicalTTP

ZLAJ:<phyTTP number>;

iv. Delete the affected ATM interface and other resources.For instructions, see Deleting ATM resources.

v. Delete the physical TTP with the command ZYDD;

Else

Continue to step 3












AllenkeyM2.5

DN02220548





1

1

2




4. Delete the HW description data on the old plug-in unit

Note

When replacing a TDM interface unit (i.e. IW1S1 or IW16P1-A), youneed to keep the same functional unit index number for the ET whenequipping the new unit or, if that is not possible, check the ET used forsignalling by using ZNEL;

Check also the ET used for user plane by using ZRCI; (This commandis used only for MGW.)

Remove the SS7 configuration by following the instrustions inRemoving an MTP singnalling point.

Remove the circuit group, route and digit analysis related to thisinterface unit by following the instructions in Removing circuits fromgroups in MGW.

Follow the instructions in Deleting HW description data whenreplacing plug-in units.

5. Create the HW description data on the new plug-in unit


6. Install the plug-in unit into the subrack

a. Close the insertion/extraction levers on the front panel of theplug-in unit.




c. Insert cable(s) to the front panel of the plug-in unit if there areany.


7. Check the software version of the HMS node of the interfacecard



For instructions, see Checking the software version of the HMSnode.






Expected outcome


Unexpected outcome






Expected outcome


Unexpected outcome








12. Set the unit to WO or SP working state (USC)

Depending on the redundancy principle of the unit, set the unitworking state to WO-EX or SP-EX (2N units).


13. Create all the interfaces and links to the new unit

Note

If the interfaces of the old unit are applicable for the new unit, you canre-create the interfaces according to the list you made of the old unit'sinterfaces.

This step depends on the network planning. For instructions, seeIntergrate in RNC or MGW Product Documentation.


ZAAP;

15. Document update

Record unit type changes in corresponding site documents.



10 MCPC2(-A) plug-in unit is faultyDescription

When an MCPC2 or MCPC2-A (NEMU) plug-in unit is faulty, you mustreplace the faulty unit.

For more information on plug-in units, see either Nokia MultimediaGateway Plug-in Unit Descriptions or Nokia WCDMA Radio NetworkController Plug-in Unit Descriptions in PDF format in NOLS. For generalinstructions on how to install plug-in units, see Installing plug-in units in thesite document Installing the MGW and RNC.

Symptoms

If an MCPC2 or MCPC2-A plug-in unit is faulty, NEMU displays bluescreen during boot, or is in restart loop, or is otherwise non-functional.

Recoveryprocedures

Replacing MCPC2(-A) plug-in unit with the same variant

Purpose

Note that the equipment database does not recognise MCPC2 or MCPC2-A, and it does not have working states.

If you want to replace the plug-in unit with a newer variant, see ReplacingMCPC2 plug-in unit with MCP18(-B) or Replacing MCPC2-A plug-in unitwith MCP18(-B).



MCPC2(-A) plug-in unit is faulty

Caution




For more information on general environmental requirements, seeInstallation Site Requirements for Nokia IPA2800 Network Elements.

Note


When replacing an MCPC2 and MCPC2-A plug-in unit, it is recommendedto perform NEMU shutdown using the Platform Manager UI tool (steps 1–4), if it is possible. For more detailed instructions, see NEMU PlatformManager User Interface.

Before you start

Always check the interchangeability of the spare plug-in unit beforechanging the unit. The interchangeability sticker is located in the frontpanel of the plug-in unit after the C number. The interchangeability code ofthe new plug-in unit must be the same as or newer than the old plug-inunit's code. If the interchangeability code of the new plug-in unit is newerthan the old unit's code, check the effects on the interchangeability of thesubrack and the other plug-in units.


Steps

1. Log on to NEMU using Nemuadmin account (if possible)



If NEMU displays blue screen during boot, or is in restart loop, or isotherwise non-functional, please continue from step 5.

2. Start Platform Manager User Interface

Click Start > Programs > Nemu Platform Manager User Interface> PMUI.

3. Shut down the Platform Manager

Click the Stop PM button, or select Stop Platform Manager in thePlatform menu. The confirmation dialog opens. Click OK to confirmthis operation. Wait until the status is Platform Manager not running.





a. Remove the cables located on the front panel of the plug-inunit.

b. Unscrew the locking screws on the front panel of the plug-inunit.

Locking screws keep the plug-in unit in its place. Lockingscrews are located on top of the insertion/extraction levers.See Figure Unscrewing locking screws in Replacing plug-inunit with the same variant.

c. Open insertion/extraction levers on the front panel of the plug-in unit.

Insertion/extraction levers are locking clamps which securethe plug-in unit to the rack. Insertion/extraction levers arelocated on the upper and lower edge of the plug-in unit. SeeFigure Opening locking clamps and removing plug-in unit inReplacing plug-in unit with the same variant.

d. Double click (within two seconds) the reset switch in the frontpanel of MCPC2(-A).



e. Remove the plug-in unit from the subrack within 20 seconds.





7. Check that the marking strip is correct

Insert the correct marking strip if you have received a new markingstrip, or if there is no marking strip inside the subrack where the plug-in unit was located.

8. Install the new plug-in unit in the subrack

a. Insert the spare plug-in unit in its location.



d. Insert cables back to the front panel of the plug-in unit.

9. Log on to NEMU using Nemuadmin account


Click Start > Programs > Nemu Platform Manager User Interface> PMUI.

11. Check that the Platform Manager is running

If it is not on, click the Start PM button or select Start PlatformManager from the Platform menu. The Platform Manager starts.

If it is on, the Start PM button and Start Platform Manager in thePlatform menu are inactive and the Status field has the text Nemusoftware running.

12. Check Windows Event Log for any error messages

Select Start > Programs > Administrative Tools > Event Viewerand then select Start Event Viewer. Check that there are noabnormal events since the last restart.



11 MCP18(-B) plug-in unit is faultyDescription

When an MCP18 or MCP18-B plug-in unit is faulty, you must replace thefaulty unit.

For more information on plug-in units, see either Nokia MultimediaGateway Plug-in Unit Descriptions or Nokia WCDMA Radio NetworkController Plug-in Unit Descriptions in PDF format in NOLS. For generalinstructions on how to install plug-in units, see Installing plug-in units in thesite document Installing the MGW and RNC.

Symptoms

If an MCP18 or MCP18-B plug-in unit is faulty, NEMU displays a bluescreen during boot, or is in restart loop, or is otherwise non-functional.

Recoveryprocedures

Replacing MCP18(-B) plug-in unit with the same variant

Purpose

An MCP18 and MCP18-B plug-in unit uses the Windows 2000 operatingsystem. Note that the equipment database does not recognise MCP18 orMCP18-B, and it does not have working states.



MCP18(-B) plug-in unit is faulty

Caution





Note


When replacing an MCP18 and MCP18-B plug-in unit, it is recommendedto perform NEMU shutdown using the Platform Manager UI tool (steps 1–4), if this is possible. For more detailed instructions, see NEMU PlatformManager User Interface.

Before you start



Steps

1. Log on to NEMU using Nemuadmin account (if possible)



If NEMU displays a blue screen during boot, or is in restart loop, or isotherwise non-functional, please continue from step 5.


Click Start > Programs > Nemu Platform Manager User Interface> PMUI





a. Remove the cables located on the front panel of the plug-inunit.

b. Unscrew the locking screws on the front panel of the plug-inunit.


c. Open insertion/extraction levers on the front panel of the plug-in unit.







d. Insert cables back to the front panel of the plug-in unit.

7. Log on to NEMU using Nemuadmin account and start PlatformManager User Interface




Click Start > Programs > Nemu Platform Manager User Interface> PMUI

8. Check that the Platform Manager is running

If it is running, the Start PM button and Start Platform Manager inthe Platform menu are inactive and Status field has text Nemusoftware running....

9. If the Platform Manager is not running

Then

Click the Start PM button or select Start Platform Manager inPlatform menu

The Platform Manager starts.

10. Check Windows Event Log for any error messages

Start Event Viewer from Start > Programs > Administrative Tools> Event Viewer. Check that there are no abnormal events since thelast restart.



12 PD20 plug-in unit is faultyDescription

When a PD20 plug-in unit (subrack power supply) is faulty, you mustreplace the faulty unit.

For more information on plug-in units, see either Nokia WCDMA RadioNetwork Controller Plug-in Unit Descriptions or Nokia Multimedia GatewayPlug-in Unit Descriptions in PDF format in NOLS. For general instructionson how to install plug-in units, see Installing plug-in units in Installing theMGW and RNC.

For instructions on how to replace a faulty fuse in PD20 plug-in unit, seeFuse in PD20 plug-in unit is faulty.

Symptoms

One or several alarms number 3000 are set when a PD20 plug-in unit isfaulty.

Recoveryprocedures

Replacing PD20 plug-in unit with the same variant

Purpose

The PD20 plug-in unit is a subrack power supply. A PD20 plug-in unit doesnot have working states.

Note that changing a PD20 plug-in unit might affect the grade of service.



PD20 plug-in unit is faulty

Caution





Note


Before you start

Always check the interchangeability of the spare plug-in unit from theRevision List before changing the unit. If you are not sure about theinterchangeability of the plug-in unit variants, please refer to the latestRNC or MGW HW Revision List available in NOLS.

The interchangeability sticker is located in the front panel of the plug-in unitafter the C number. The interchangeability code of the new plug-in unitmust be the same as or newer than the old plug-in unit's code. If theinterchangeability code of the new plug-in unit is newer than the old unit'scode, check the effects on the interchangeability of the subrack and theother plug-in units.


Before removing or inserting the PD20 plug-in unit, all the functional unitsof the units in the subrack must be in the SE-NH state.



1. Check if any of the functional units is an N+1 redundant unit (ISU orICSU) and if its working state is other than WO-EX or WO-RE. WithN+1 redundant units, one unit is usually in SP-EX state.

2. If there is a functional unit of this kind, use the USI command todisplay its logical address.

ZUSI;

3. Write down the logical address.

4. Change the working state of all the functional units in the subrack toSE-NH. For instructions, see Taking unit out of use.

When changing the PD20 plug-in unit in the first subrack, whereTSS3 0 is located, TBU 0 must be in SE-NH state. When changingthe PD20 plug in unit in the second subrack, where TSS3 1 islocated, TBU 1 must be in SE-NH state.

When changing the PD20 plug-in unit, you must first block the alarm 3000(PLUG-IN UNIT POWER FAILURE). After changing the PD20 plug-in unit,you must unblock the alarm.


AFB:3000::RES::;

2. Change the PD20 plug-in unit as described in the steps 1-11.

3. After changing the PD20 plug-in unit, unblock the alarm 3000.

ZAFU:3000::;.

Before changing the PD20 plug-in unit, you must block the alarm 1291(SUBRACK CONNECTIVITY FAILURE). After changing the PD20 plug-inunit, you must unblock the alarm.


ZAFB:1291::TOT;

2. Change the PD20 plug-in unit as described in the steps 1-11.

3. After changing the PD20 plug-in unit, unblock the alarm 1291.

ZAFU:1291;

Switching the power off in the first subrack of the first cabinet may cause asevere corruption of the NEMU software, if the NEMU operating systemhas not been shut down in a controlled way before the power is switchedoff. To shut down NEMU:




1. Log on to NEMU using Nemuadmin account.

2. Shut down the NEMU by selecting Shut down from the Start menu.When the Shut Down Windows message appears, select Shut downand confirm this by clicking OK in the dialog box.

3. Wait until the message appears that it is now safe to turn off yourcomputer.

4. When the operating system is shut down, immediately disconnectthe MCPC2, MCPC2-A, MCP18 or MCP18-B plug-in unit from thesubrack.

Before you switch the power back on to the first subrack of the first cabinet,reconnect the MCPC2, MCPC2-A, MCP18 or MCP18-B plug-in unit to thesubrack.

Steps

1. Turn off the power from the subrack that belongs to the supplybranch with the faulty PD20

Turn off the subrack power only from the CPD80-B power unit(located in the upper part of the cabinet) that belongs to the supplybranch with the faulty PD20.

The units in the subrack must be in SE-NH state before you turn offthe switches.

When you turn the first switch off, there will be two alarms (3118 and3134). The alarms disappear when you turn the second switch off.


a. Unscrew the locking screws on the front panel of the plug-inunit.


b. Open insertion/extraction levers on the front panel of the plug-in unit.


c. Remove the plug-in unit from the subrack.







4. Turn on the power to one of the switches that you turned off

Either the alarm 3118 or 3134 is set.

5. Turn on the power to the other switch that you turned off


The HMS node SW version can only be checked with a serviceterminal command. The HMS node SW version information consistsof version, edition and repair number (X.Y-Z). HMS release level isdefined by X.Y. Nodes which have the same release level arecompatible. All HMS nodes within one network element must havethe same release level within the HMS hierarchy. For instance, allthe slave nodes must have the same release level which can,however, be different from the release level of the brigde nodes. Formore information on HMS node and HMS addressing, see Hardwareconfiguration data management in Hardware ConfigurationManagement for MGW or RNC.

a. Open a remote debugger session to the active OMU.

ZDDS:OMU,<index of the active unit>;

b. Load the HME service terminal extension.

0x-MAN>ZLP:1,HME

c. Display the HMS node SW version.

0x-MAN>Z1CO:<rack>,<subrack>,<ppa>

d. Check that the SW version is compatible.

e. Remove the HME service terminal extension.

0x-HME>ZL:1

f. Close the remote debugger session.

0x-MAN>ZE

If the HMS node SW version is incompatible, remove the plug-in unitand contact your local Nokia Customer Service Center.

7. Check data on the plug-in unit (WFL)






8. Change the units back to normal working state (USC)

Change all the functional units back to normal working state.Depending on the redundancy principle of the unit, the normalworking state is WO-EX or SP-EX.

Note

If there was a spare N+1 redundant unit in the subrack, change it backto SP-EX state. You should have the logical address of the unit writtendown.

ZUSC:<unit type>,<unit index>:SP|WO;

9. Check that all functional units in the subrack are in normalworking state (WO or SP) (USI)

ZUSI:<unit type>;

10. If there are still functional units that are not in WO or SP state

Then

Change the unit to the SP or WO working state (USC)




13 Fuse in PD20 plug-in unit is faultyDescription

When a fuse in a PD20 plug-in unit (subrack power supply) is faulty, youmust replace the faulty fuse.

For more information on the PD20 plug-in units and its fuses, see eitherNokia Multimedia Gateway Plug-in Unit Descriptions or Nokia WCDMARadio Network Controller Plug-in Unit Descriptions in PDF format inNOLS.

For instruction on how to replace a PD20 plug-in unit, see PD20 plug-inunit is faulty.

Symptoms

One or several alarms number 3000 are set when a fuse in PD20 plug-inunit is faulty.

Recoveryprocedures

Replacing a fuse in PD20 plug-in unit

Steps

1. Locate the faulty fuse

A red LED in the front panel of the PD20 indicates which fuse isfaulty.

2. Turn off the power from the subrack that belongs to the supplybranch with the faulty fuse



Fuse in PD20 plug-in unit is faulty

Turn off the subrack power only from the CPD80-B power unit(located in the upper part of the cabinet) that belongs to the supplybranch with the faulty fuse. From top to bottom, the first five fusesform one group for supplying the first branch (UB1) and the next fivefuses another group for supplying the second supply branch (UB2).

When you turn the switch off, the red LED indicating the fuse failuregoes out and the LED that indicates lack of supply voltage in thesupply branch in question is lit.

3. Remove the faulty fuse

a. Unscrew the cap of the fuse holder.

b. Remove the fuse.

4. Insert new fuse

a. Insert a new fuse.

b. Screw the cap back into the fuse holder.

5. Turn on the power switch



14 PD30 plug-in unit is faultyDescription

When a PD30 plug-in unit (subrack power supply) is faulty, you mustreplace the faulty unit.

For more information on plug-in units, see either Nokia WCDMA RadioNetwork Controller Plug-in Unit Descriptions or Nokia Multimedia GatewayPlug-in Unit Descriptions in PDF format in NOLS. For general instructionson how to install plug-in units, see Installing plug-in units in Installing theMGW and RNC.

For instructions on how to replace a faulty fuse in PD30 plug-in unit, seeFuse in PD30 plug-in unit is faulty.

Symptoms

One or several alarms number 3000 are set when a PD30 plug-in unit isfaulty.

Recoveryprocedures

Replacing PD30 plug-in unit with the same variant

Purpose

The PD30 plug-in unit is a subrack power supply. A PD30 plug-in unit doesnot have working states.

Note that changing a PD30 plug-in unit might affect the grade of service.




Caution





Note


Before you start

Always check the interchangeability of the spare plug-in unit from theRevision List before changing the unit. If you are not sure about theinterchangeability of the plug-in unit variants, please refer to the latestRNC or MGW HW Revision List available in NOLS.

The interchangeability sticker is located in the front panel of the plug-in unitafter the C number. The interchangeability code of the new plug-in unitmust be the same as or newer than the old plug-in unit's code. If theinterchangeability code of the new plug-in unit is newer than the old unit'scode, check the effects on the interchangeability of the subrack and theother plug-in units.


Before removing or inserting the PD30 plug-in unit, all the functional unitsof the units in the subrack must be in the SE-NH state.



1. Check if any of the functional units is an N+1 redundant unit (ISU orICSU) and if its working state is other than WO-EX or WO-RE. WithN+1 redundant units, one unit is usually in SP-EX state.

2. If there is a functional unit of this kind, use the USI command todisplay its logical address.

ZUSI;

3. Write down the logical address.

4. Change the working state of all the functional units in the subrack toSE-NH. For instructions, see Taking unit out of use.

When changing the PD30 plug in unit in the first subrack, whereTSS3 0 is located, TBU 0 must be in SE-NH state. When changingthe PD30 plug in unit in the second subrack, where TSS3 1 islocated, TBU 1 must be in SE-NH state.

Switching the power off in the first subrack of the first cabinet may cause asevere corruption of the NEMU software, if the NEMU operating systemhas not been shut down in a controlled way before the power is switchedoff. To shut down NEMU:

1. Log on to NEMU using Nemuadmin account.

2. Shut down the NEMU by selecting Shut down from the Start menu.When the Shut Down Windows message appears, select Shut downand confirm this by clicking OK in the dialog box.

3. Wait until the message appears that it is now safe to turn off yourcomputer.

4. When the operating system is shut down, immediately disconnectthe NEMU plug-in unit from the subrack.

Before you switch the power back on to the first subrack of the first cabinet,reconnect the NEMU plug-in unit to the subrack.

Steps

1. Block the alarm 1291 (SUBRACK CONNECTIVITY FAILURE)

ZAFB:1291::TOT;

2. Turn off the power from the subrack that belongs to the supplybranch with the faulty PD30




Turn off the subrack power only from the CPD80-B/CPD120/CPD120-A power unit (located in the upper part of the cabinet) thatbelongs to the supply branch with the faulty PD30.

The units in the subrack must be in SE-NH state before you turn offboth the switches.

When you turn the first switch off, there will be two alarms (3118 and3134). The alarms disappear when you turn the second switch off.


a. Unscrew the locking screws on the front panel of the plug-inunit.


b. Open insertion/extraction levers on the front panel of the plug-in unit.


c. Remove the plug-in unit from the subrack.





5. Turn on the power to one of the switches that you turned off

Either the alarm 3118 or 3134 is set.

6. Turn on the power to the other switch that you turned off


The HMS node SW version can only be checked with a serviceterminal command. The HMS node SW version information consistsof version, edition and repair number (X.Y-Z). HMS release level isdefined by X.Y. Nodes which have the same release level are



compatible. All HMS nodes within one network element must havethe same release level within the HMS hierarchy. For instance, allthe slave nodes must have the same release level which can,however, be different from the release level of the brigde nodes. Formore information on HMS node and HMS addressing, see Hardwareconfiguration data management in Hardware ConfigurationManagement for MGW or RNC.

a. Open a remote debugger session to the active OMU.

ZDDS:OMU,<index of the active unit>;

b. Load the HME service terminal extension.

0x-MAN>ZLP:1,HME

c. Display the HMS node SW version.

0x-MAN>Z1CO:<rack>,<subrack>,<ppa>

d. Check that the SW version is compatible.

e. Remove the HME service terminal extension.

0x-HME>ZL:1

f. Close the remote debugger session.

0x-MAN>ZE

If the HMS node SW version is incompatible, remove the plug-in unitand contact your local Nokia Customer Service Center.

8. Check data on the plug-in unit (WFL)



9. Change the units back to normal working state (USC)

Change all the functional units back to normal working state.Depending on the redundancy principle of the unit, the normalworking state is WO-EX or SP-EX.

Note

If there was a spare N+1 redundant unit in the subrack, change it backto SP-EX state. You should have the logical address of the unit writtendown.





10. Check that all functional units in the subrack are in normalworking state (WO or SP) (USI)

ZUSI:<unit type>;

11. If there are still functional units that are not in WO or SP state

Then

Change the unit to the SP or WO working state (USC)


12. Unblock the alarm 1291 (SUBRACK CONNECTIVITY FAILURE).

ZAFU:1291;



15 Fuse in PD30 plug-in unit is faultyDescription

When a fuse in a PD30 plug-in unit (subrack power supply) is faulty, youmust replace the faulty fuse. The fuses used with PD30 plug-in unit are10A 250V fast fuse (FA1...FA4, FB1...FB4) and 6.3A 250V slow fuse (FA5,FB5).

For more information on the PD30 plug-in unit and its fuses, see eitherNokia Multimedia Gateway Plug-in Unit Descriptions or Nokia WCDMARadio Network Controller Plug-in Unit Descriptions in PDF format inNOLS.

For instruction on how to replace a PD30 plug-in unit, see PD30 plug-inunit is faulty.

Symptoms

One or several alarms number 3000 are set when a fuse in PD30 plug-inunit is faulty.

Recoveryprocedures

Replacing a fuse in PD30 plug-in unit

Steps

1. Locate the faulty fuse

A red LED in the front panel of the PD30 indicates which fuse isfaulty.

2. Turn off the power from the subrack that belongs to the supplybranch with the faulty fuse



Fuse in PD30 plug-in unit is faulty

Turn off the subrack power only from the CPD80-B/CPD120/CPD120-A power unit (located in the upper part of the cabinet) thatbelongs to the supply branch with the faulty fuse. From top tobottom, the first five fuses form one group for supplying the firstbranch (UB1) and the next five fuses another group for supplying thesecond supply branch (UB2).

When you turn the switch off, the red LED indicating the fuse failuregoes out and the LED that indicates lack of supply voltage in thesupply branch in question is lit.

3. Remove the faulty fuse

a. Unscrew the cap of the fuse holder.

b. Remove the fuse.

4. Insert new fuse

a. Insert a new fuse.

b. Screw the cap back into the fuse holder.

5. Turn on the power switch



16 ESA12 plug-in unit is faultyDescription

When an ESA12 plug-in unit is faulty, you must replace the faulty unit.

Depending on the network element, see either Nokia WCDMA RadioNetwork Controller Plug-in Unit Descriptions or Nokia Multimedia GatewayPlug-in Unit Descriptions in PDF format in NOLS for more information onplug-in units. For general instructions on how to install plug-in units, seeInstalling plug-in units in Installing the MGW and RNC.

Symptoms

A red LED in the front panel of the ESA12 plug-in unit indicates that theplug-in unit has a fatal hardware failure.

Recoveryprocedures

Replacing ESA12 plug-in unit with the same variant

Purpose

Note that the equipment database does not recognise ESA12, and it doesnot have working states.



ESA12 plug-in unit is faulty

Caution




For more information on general environmental requirements, seeInstallation Site Requirements fo MGW and RNC.

Note


Before you start



The following is assumed in taking the backup of the configurationfile in this instruction:

. The IP address of the upgraded switch is 192.168.0.5.

. The IP address of the PC that is used as a TFTP client is in the samesubnetwork as the IP address of the ESA12.



If the IP address of the PC is not in the same subnetwork as the IPaddress of the ESA12, the TFTP transfer can only be done properlyif there is a router between the subnetworks directing the IP packetsto the correct subnetwork.

Check that you have the following:

. the ESA12 unit that needs to be upgraded

. a PC or a laptop with an Ethernet card installed in it

. TFTP client application installed on a PC or a laptop

The Windows 2000 and Linux operating systems include a TFTPclient application. If you have another operating system, you mustinstall the TFTP application separately on the PC or laptop. You canpurchase an commercial TFTP client application or download afreeware TFTP client application from the Internet.

. Telnet or service terminal program installed on a PC or a laptop

If you are updating the ESA12 software using only the Ethernetconnection, you need a Telnet program.

If you are updating ESA12 software using service terminal sessionand the Ethernet connection, you need a service terminal program.

. one straight-through Ethernet cable (RJ-45)

If the network element has only one ESA12 plug-in unit, you need to blockthe alarm 3053 (ETHERNET INTERFACE FAILURE) before replacing thenetwork element and unblock it after you have replaced the networkelement.


AFB:3053::RES::;

2. Change the plug-in unit as described in the steps 1-13.

3. After changing the plug-in unit, unblock the alarm 3053.

ZAFU:3053::;.

Steps

1. Take a backup of the configuration file of the ESA12 switch

a. Connect the PC or laptop to one of the Ethernet ports of theESA12 switch with an Ethernet cable

b. Check that the Ethernet switch is powered up.




When the ESA12 Ethernet switch is powered up, the LED onthe front panel of the switch is green.

c. If you are using service terminal session and Ethernetconnection

then

Connect the service terminal to ESA12 and start theterminal session:

i. Connect the service terminal to ESA12 with a serialcable.

ii. Start the service terminal session with the followingsettings:. Bitrate: 9600 bit/s. Parity: None. Data bits: 8. Stop bits: 1. Flow control: Xon/Xoff

d. If you are using only the Ethernet connection

then

Connect to the IP address of ESA12 via Telnet

i. Start a Telnet session by selecting Start -> Run on theWindows Taskbar.

ii. Connect to the IP address of ESA12:

telnet <IP address of ESA12>

For example: telnet 192.168.0.5

iii. Press Enter.

e. Log in to ESA12

Enter your login ID and password.

The default password is empty, that is, press Enter to continue.If the password has been changed, enter the new passwordand then press Enter.

NOKIA ESA-12.

Username:nokia

Password:********

The main menu of ESA12 opens:

ESA12 1.28 Aug 17 2000

Main Menu

1. General Configuration

2. SNMP Configuration

3. Ports Configuration

4. Ports Status



5. Load Factory Defaults

6. Software Upgrade

7. Reset

8. Logout

f. Enable the Upload/Download of the configuration file in theswitch:

i. Press 1 to enter the General Gonfiguration from the Mainmenu.

ii. Press 6 to enter the Advanced Features

iii. Press 7 for Enable Config Upload/Download

iv. Press Y in response to the prompt

g. Use the TFTP program to download and save the filenokia_cfg from the switch to your PC.

2. If the plug-in unit is completely faulty and you are unable to take abackup of the configuration file

Then

Configure ESA12 after you have followed the steps from 3 to 12

3. Remove the LAN cable(s) from the front panel

4. Unscrew the locking screws on the front panel of the plug-inunit

Locking screws keep the plug-in unit in its place. Locking screws arelocated on top of the insertion/extraction levers. See FigureUnscrewing locking screws in Replacing plug-in unit with the samevariant.

5. Open the insertion/extraction levers on the front panel of theplug-in unit

Insertion/extraction levers are locking clamps which secure the plug-in unit to the rack. Insertion/extraction levers are located on theupper and lower edge of the plug-in unit. See Figure Opening lockingclamps and removing plug-in unit in Replacing plug-in unit with thesame variant.

6. Double click (within two seconds) the reset switch in the frontpanel of ESA12

The electricity switches off from the unit. There is no light in the LEDlight which is in the front panel of the plug-in unit.





7. Remove the plug-in unit from the subrack within 20 seconds



Insert the correct marking strip if you have received a new markingstrip, or if there is no marking strip in the subrack where the plug-inunit was located.

9. Insert the spare plug-in unit in its location

10. Close the insertion/extraction levers on the front panel of theplug-in unit


12. Insert cable(s) back to the front panel of the plug-in unit

13. If you were unable to take a backup of the configuration file (forinstance, because the ESA12 plug-in unit was completely faulty)

Then

Configure ESA12

For instructions, see Configuring ESA12 in IP ConnectionConfiguration for MGW or IP Connection Configuration for RNC.

Else

Follow the instructions below

14. Upload the configuration file to the ESA12 switch

Start the TFTP client program on the PC or laptop and enter therequired settings. Set the following settings in the TFTP program:. Host IP address: IP address of ESA12 (for example,

192.168.0.5). Port: 69. Local file name: the name of the configuration file you copied

to your hard drive. If the TFTP program cannot find the file,change the path settings in the program.



. Remote file name: the name of the remote configuration filethat will be written to the ESA12 flash memory. The file namefor the configuration file to be loaded into ESA12 shouldalways be 'nokia_cfg'. Note that the file extension is separatedfrom the file name with an underscore (_), not a period.

. Transfer type: Binary

15. Upgrade the ESA12 software

For instructions, see Upgrading ESA12 software in SoftwareConfiguration Management.






17 ESA24 plug-in unit is faultyDescription

When an ESA24 plug-in unit is faulty, you must replace the faulty unit.


Symptoms

A red LED in the front panel of the ESA24 plug-in unit indicates that theplug-in unit has a fatal hardware failure.

Recoveryprocedures

Replacing ESA24 plug-in unit with the same variant

Purpose

Note that the equipment database does not recognise ESA24, and it doesnot have working states.




Caution





Note


Before you start

Note

This procedure will cause disturbances in the H.248 traffic.



The following is assumed in taking the backup of the configurationfile in this instruction:



. The IP address of the upgraded switch is 192.168.0.5.

. The IP address of the PC that is used as a TFTP server is192.168.0.128.

The IP address of the PC that is used as a TFTP server is selectedfrom the same subnetwork as the IP address of ESA24. If the IPaddress of the PC is not in the same subnetwork as the IP addressof ESA24, the TFTP transfer can only be done properly if there is arouter between the subnetworks directing the IP packets to thecorrect subnetwork.

. The ESA24 unit already has the BiNOS operating system installed.The current version needs to be upgraded to a newer one.

Check that you have the following:

. the ESA24 unit that needs to be upgraded

. PC or a laptop with an Ethernet card installed in it

. TFTP server application installed on a PC or a laptop

Note that the TFTP server application is different from the TFTPclient application.

The Windows 2000 and Linux operating systems include a TFTPserver application. If you have another operating system, you mustinstall the TFTP application separately on the PC or laptop. You canpurchase a commercial TFTP server application or download afreeware TFTP server application from the Internet.

. service terminal program installed on a PC or a laptop

. one straight-through Ethernet cable (RJ-45)

Steps

1. Take a backup of the configuration file of the ESA24 switch

a. Connect the PC or laptop to one of the Ethernet ports of theESA24 switch with an Ethernet cable

b. Check that the Ethernet switch is powered up.

When the ESA24 Ethernet switch is powered up, the LED onthe front panel of the switch is green.

c. Connect to the IP address of ESA24 via Telnet




i. Start a Telnet session by selecting Start -> Run on theWindows Taskbar.

ii. Connect to the IP address of ESA24:

telnet <IP address of ESA24>

For example: telnet 192.168.0.5

iii. Press Enter.

d. Log in to ESA24

Enter the default password 'nokia' and press Enter. If thepassword has been changed, enter the new password andthen press Enter.

User Access Verification

Password:

After successful log in, the ESA24 prompt is displayed:

ESA24>

e. Start the TFTP server on the PC or laptop and enter therequired settings.

Set up the TFTP server so that ESA24 is allowed to upload afile to this PC.

There are many different TFTP server applications available.The server management varies between different products, sosee the instructions supplied with the TFTP server application.

f. Enable the privileged mode in BiNOS

Enable the privileged mode in ESA24 operating system withthe command

enable

The privileged mode allows advanced viewing andconfiguration capabilities for the unit.

Note

The command prompt in privileged mode is the number sign, "#".

g. Upload the configuration file of the switch to the TFTP serverto take a backup of the configuration. The TFTP server issupposed to be running on the PC that has the IP address192.168.0.128. The configuration file is copied to TFTP-serverroot directory on PC.

ESB20-A#copy running-config upload-to 192.168.0.128 config.cfg.

Building the configuration ...

Upload complete



2. If the plug-in unit is completely faulty and you are unable to take abackup of the configuration file

Then

Reconfigure ESA24 manually

You need to reconfigure the ESA24 manually because it is notpossible to upload existing configuration file to TFTP server.Reconfigure ESA24 after you have followed the steps from 3 to 12.

3. Block Alarm 3053 ETHERNET INTERFACE FAILURE

Block the alarm by entering the following MML command:

ZAFB:3053:;

4. Remove the LAN cable(s) from the front panel

5. Unscrew the locking screws on the front panel of the plug-inunit

Locking screws keep the plug-in unit in its place. Locking screws arelocated on top of the insertion/extraction levers. See FigureUnscrewing locking screws in Replacing plug-in unit with the samevariant.

6. Open the insertion/extraction levers on the front panel of theplug-in unit

Insertion/extraction levers are locking clamps which secure the plug-in unit to the rack. Insertion/extraction levers are located on theupper and lower edge of the plug-in unit. See Figure Opening lockingclamps and removing plug-in unit in Replacing plug-in unit with thesame variant.

7. Double click (within two seconds) the reset switch in the frontpanel of ESA24

The electricity switches off from the unit. There is no light in the LEDlight which is in the front panel of the plug-in unit.


8. Remove the plug-in unit from the subrack within 20 seconds






Insert the correct marking strip if you have received a new markingstrip, or if there is no marking strip inside the subrack where the plug-in unit was located.

10. Insert the spare plug-in unit in its location

11. Close the insertion/extraction levers on the front panel of theplug-in unit


13. If you were unable to take a backup of the configuration file (forinstance, if the plug-in unit is completely faulty)

Then

Reconfigure ESA24

For instructions, see Configuring ESA24 in IP ConnectionConfiguration for MGW or IP Connection Configuration for RNC.

Else

Follow the instructions below

14. Download the configuration file to ESA24

Use the TFTP server to download the configuration file to ESA24.

15. Insert cable(s) back to the front panel of the plug-in unit

16. Remove the alarm blocking of Alarm 3053 ETHERNETINTERFACE FAILURE

Unblock the alarm by entering the following MML command:

ZAFU:3053:;

17. Upgrade the ESA24 software

For instructions, see Upgrading ESA24 software in SoftwareConfiguration Management.



18 BIE1C/T back interface unit is faultyDescription


Symptoms

BIE1C or BIE1T back interface unit is faulty.

Recoveryprocedures

Replacing a BIE1C or BIE1T back interface unit

Purpose

The following instructions explain how to replace BIE1C or BIE1T backinterface units.



BIE1C/T back interface unit is faulty

Figure 10. BIE1C back interface unit

Locking

AllenkeyM2.5

AllenkeyM2.5

NIWU / NIP1SRBI-B

BIE1C

Front side

Rear side

DN02220536



Figure 11. BIE1T back interface unit

Caution

Electrostatic discharge and incorrect installation and uninstallation candamage circuits or shorten their lifetime. To ensure proper functioning ofthe back interface units during their usual lifetime, take the followingprecautions before handling them.



NIWU / NIP1AllenkeyM2.5

Locking

AllenkeyM2.5

SRBI-B

BIE1T

Front side

Rear side

DN02220575





Note

Insert the back interface unit carefully. It is important to check that thelocking screws are closed properly, and that the back interface unit iswell in its place.

Before you start

Always check the interchangeability of the spare back interface unit beforechanging the unit. The interchangeability sticker is located in the frontpanel of the back interface unit after the C number. The interchangeabilitycode of the new back interface unit must be the same as or newer than theold back interface unit's code. If the interchangeability code of the newback interface unit is newer than the old unit's code, check the effects onthe interchangeability of the subrack and the other back interface units.

It is recommended that you maintain a log of spares so that you can traceany back interface unit at any time.

Note

Before removing or inserting a back interface unit, all the functionalunits in the plug-in unit (NI16P1) of the back interface unit must be inthe SE-NH state. For instructions, see Taking unit out of use.

Steps

1. Remove the cables from the front panel of the back interfaceunit

The functional units of the plug-in units must be in SE-NH statebefore removing the cables. The BIE1C unit has a coaxial cable andthe BIE1T a twisted pair cable on the front panel.

2. Unscrew locking screws on the front panel of the back interfaceunit



Locking screws keep the back interface unit in its place. The lockingscrews are located on the upper and lower edge of the backinterface unit. See Figures BIE1C back interface unit and BIE1Tback interface unit.

3. Open the insertion/extraction lever on the front panel of theback interface unit

Insertion/extraction levers are locking clamps which secure the plug-in unit to the rack. The insertion/extraction lever is located on thelower edge of the back interface unit.

4. Carefully remove the back interface unit from the subrack

5. Carefully insert the spare back interface unit in its location

6. Close the insertion/extraction lever on the front panel of theback interface unit


8. Insert cables back to the front panel of the back interface unit

The BIE1C unit has a coaxial cable and the BIE1T a twisted paircable on the front panel.

9. Set the functional units of the back interface unit to SE-OUworking state (USC)


10. Set the functional units of the back interface unit to TE workingstate (USC)


11. Check that the repair operation was successful by starting thetotal diagnosis of the unit (UDU)


To output the results of the diagnostics.

ZUDH:<unit type>,<unit index>;





12. Set the unit to SP or WO working state, depending on theredundancy principle (USC)


13. Check that the alarm disappears, if necessary (AAP)

ZAAP;



19 Fan tray is faultyDescription

An alarm is displayed if the fan tray (FTR) needs to be changed.

Depending on the network element, see either Nokia Multimedia GatewayPlug-in Unit Descriptions or Nokia WCDMA Radio Network ControllerPlug-in Unit Descriptions in PDF format in NOLS for information on fan tray(FTR/FTRA).

Symptoms

The alarm number 3013 is set when a fan tray is faulty.

Recoveryprocedures

Replacing fan tray

Purpose

Note that the equipment database does not recognise the fan tray, and itdoes not have working states.

The fan tray is located in a cabinet between subracks, see the figurebelow. See also Figure Co-ordinates of subracks and plug-in unit positionaddresses in Hardware Configuration Management.



Fan tray is faulty

Figure 12. Fan tray

DN042269

Power supply unit

Fan tray and cable trough



Caution

Electrostatic discharge and incorrect installation and uninstallation candamage circuits or shorten their lifetime. To ensure proper functioning ofthe fan trays during their usual lifetime, take the following precautionsbefore handling them.




Note

Insert the fan tray carefully. It is important to check that the lockingscrews are closed properly, and that the fan tray is well in its place.

Before you start

You must change the fan tray within four minutes. The control cableattached to the fan tray can be removed only for four minutes at amaximum.

Caution

Pay special attention to removing and inserting the control cable.

The control cable is attached both to the subrack and to the FTR. Whenremoving the control cable, always remove it first from the subrack, andthen from the FTR. When inserting the control cable, always insert itfirst to the FTR, and then to the subrack.



Fan tray is faulty

Always check the interchangeability of the spares before changing the fantray. The interchangeability sticker is located in the front panel of the fantray after the C number. The interchangeability code of the new fan traymust be the same as or newer than the old fan tray's code. If theinterchangeability code of the new fan tray is newer than the old unit'scode, check the effects on the interchangeability of the subrack and theplug-in units.

It is recommended that you maintain a log of spares so that you can traceany fan tray at any time.

Note

Replace the fan tray strictly in the order described in this procedure.Removing the control cable in the wrong order may cause a shortcircuit.

Steps

1. Remove the locking screws from the cable trough

2. Remove the locking screws from the fan tray

3. Remove the control cable from the subrack

The control cable is located behind the subrack, and it is attachedboth to the subrack and to the fan tray. Note that the control cablecan only be removed for four minutes at maximum.

After you have removed the cable from the subrack, the fan traystops. Note that the fan tray should not be stopped for more than fourminutes.

4. Remove the control cable from the fan tray

Note that the control cable can only be removed for four minutes atmaximum.

5. Pull the fan tray out of the subrack

For more information, see Figure Fan tray and Figure Co-ordinatesof subracks and plug-in unit position addresses in HardwareConfiguration Management.

6. Insert the new fan tray to the subrack



7. Connect the control cable behind the subrack to the fan tray

8. Connect the control cable behind the subrack to the subrack

9. Carefully close the locking screws in the front panel of the fantray

10. Carefully close the locking screws in the cable trough

11. Check that the alarm 3013 disappears and that there are no redLEDs on

Replacing fan tray during active traffic transfer

Purpose

Follow these instructions if you need to replace a fan tray while traffictransfer is active.



Fan tray is faulty

Figure 13. Identification of fuses

FB5

FA5

DN042303



Caution




For information on general environmental requirements, see InstallationSite Requirements for MGW and RNC.

Note


Before you start

You must change the fan tray within four minutes. The control cableattached to the fan tray or fuses FA5 and FB5 can be removed only for fourminutes at maximum.

Caution

Pay special attention to removing and inserting the control cable. Thecontrol cable is attached to both the subrack and the FTR.




Fan tray is faulty


Note

Replace the fan tray strictly in the order described in this procedure.Removing the control cable in the wrong order may cause a shortcircuit.

Steps

1. Remove fuse FB5 of the PD20

Figure 14. Detaching fuse FB5

After the fuse FB5 is removed, the warning LED is lit. After the fuseis detached, alarm 3015 is displayed.

2. Move the cable trough

Remember to handle the cables carefully.

FB5FB5

DN042284



Figure 15. Moving the cable trough

a. Remove the lower locking screws of the cable trough andloosen the upper ones. See insert 1 and 2 in Figure Moving thecable trough.

b. Loosen the locking screws of the subrack and move the cabletrough to the retaining screws of the subrack. See insert 3 inthe figure.

3. Remove the upper locking screws of the fan tray

4. Make sure that there is enough room to detach the control cableof the fan tray

5. Remove fuse FA5 of the PD20

DN042272

1

2

1

3

2



Fan tray is faulty

Figure 16. Detaching fuse FA5

Note

Detaching fuse FA5 shuts down the FTRA power supply. The newFTRA must be changed within four minutes at maximum (FTRA is shutdown during steps 5-10).

After removing the fuse, FTRA is shut down and the warning LED islit. Alarm 3013 is displayed.

6. Remove the control cable of the FTRA

The control cable is located behind the subrack and is attached toboth the subrack and the fan tray.

7. Pull the fan tray out of the subrack

Remove the rest of the bolts of the fan tray and pull the fan tray out.

8. Insert the new fan tray to the subrack

FA5

DN048669




10. Insert fuse FA5 back to its place

Figure 17. Inserting fuse FA5

After inserting fuse FA5, the warning LED is off and alarm 3015 isdisplayed.

After installing fuse FA5 back to its place, the FTRA is working again.

11. Carefully close the locking screws in the front panel of theFTRA

12. Move the cable trough back to its original place

13. Insert fuse FB5 back to its place

FA5FA5

DN048672



Fan tray is faulty

Figure 18. Inserting fuse FB5

After inserting fuse FB5, the warning LED is off and alarm 3013 isdisplayed.

14. Check that the alarm disappears and that there are no red LEDson

FB5

DN042296



20 Fan tray (FTRA-B) is faultyDescription

An alarm is displayed if the fan tray (FTRA-B) needs to be changed.

Depending on the network element, see either Nokia Multimedia GatewayPlug-in Unit Descriptions or Nokia WCDMA Radio Network ControllerPlug-in Unit Descriptions in PDF format in NOLS for information on fan tray(FTR/FTRA).

Symptoms

The alarm number 3013 is set when a fan tray is faulty.

Recoveryprocedures

Replacing fan tray

Purpose

Note that the equipment database does not recognise the fan tray, and itdoes not have working states.

The fan tray is located in a cabinet between subracks, see the figurebelow. See also Figure Co-ordinates of subracks and plug-in unit positionaddresses in Hardware Configuration Management.



Fan tray (FTRA-B) is faulty

Figure 19. Fan tray

DN0629958

Fan tray and cable trough



Caution





Note


Before you start

You must change the fan tray within one minute. The control cableattached to the fan tray can be removed only for one minute at amaximum.






Caution

Do not remove the locking screws of the internal fan tray beforeremoving the control cable from the fan tray. The fan tray will fall outwhen the locking screws are opened.

Note

Replace the fan tray strictly in the order described in this procedure.

Steps

1. Open the front panel finger screw, pull the locking latches upand remove the front panel

Figure 20. Removing front panel

DN0629961

2

3

1

Locking latches



2. Loosen, but do not open fully, the locking screws of the internalfan tray

Figure 21. Loosening locking screws

3. Remove the control cable from the fan tray

Figure 22. Removing control cable

The control cable is located behind the subrack, and it is attachedboth to the subrack and to the fan tray. Note that the control cablecan only be removed for one minute at maximum.

DN0629973

DN0629985




After you have removed the cable from the subrack, the fan traystops. Note that the fan tray should not be stopped for more than oneminute.

4. Open the locking screws of the internal fan tray

5. Pull the internal fan tray out of the subrack

For more information, see Figure Fan tray and Figure Co-ordinatesof subracks and plug-in unit position addresses in HardwareConfiguration Management.

6. Insert the new internal fan tray to the subrack

7. Tighten the locking screws


9. Insert the front panel, close the locking latches and tighten thefront panel finger screw

10. Check that the alarm 3013 disappears and that there are no redLEDs on

Replacing air filter

Purpose

Follow these instructions if you need to replace the air filter of the fan tray.

Caution






For information on general environmental requirements, see InstallationSite Requirements for Nokia IPA2800 Network Elements.

Before you start

Note

Replace the air filter of the fan tray strictly in the order described in thisprocedure.

Steps

1. Open the front panel finger screw, pull the locking latches upand remove the front panel

Figure 23. Removing front panel

2. Pull the air filter out of the internal fan tray

DN0629961

2

3

1

Locking latches




Figure 24. Pulling air filter out

3. Insert the new air filter

4. Insert the front panel, close the locking latches and tighten thefront panel finger screw

DN0629997



21 Hard disk is faultyDescription

The following instructions explain how to replace a faulty hard disk so thatno data is lost. It is recommended to perform this task during low traffic.

Note

If both hard disks of OMU become faulty at the same time, you need torestore the data from the FDU drive. For detailed instructions, seeRestoring software from FDU if both OMU hard disks are faulty.

Symptoms

One of the following alarms is set when a hard disk is faulty: 1803 (SCSIMALFUNCTION), 2819 (SCSI DEFECT), 2823 (HARD DISK VERIFICATION

FAILURE), 2860 (DISK FAILURE), or 2861 (NO ACCESS TO DISK).

Recoveryprocedures

Checking if hard disk is faulty

Identifying hard disk failure in the booting phase of OMU or not in bootingphase.

1. In the booting phase of OMU

ZLP:P,POM

ZPKL



Hard disk is faulty

. Log starts with 'ncr' means problems with the SCSI driver(check at least the SCSI cabling to rule out the HW errors)

. Log with 'sense' text means problems with the SCSI device(meaning either hard disk or FDU drive)

. Logs with'discarding' texts means Shadows file system hasrejected the corresponding device and the disk is not includedin the mount

. Error code 0x3685 ENXIO: device does not exist

. Error code 0x3684 EIO: device is in catatonic state

. Any other error: please contact the Nokia Help Desk

Note

If the log states: 'SHF: TWO DIFFERENT DATABASE FOUND,UNABLE TO CONTINUE', there are two valid disks with differentcontents and the system cannot interpret which one to use. The otherhard disk is to be removed. You should check both disk file contentsand make decision accordingly.

2. Not in booting phase:

There are alarms set on the hard disk device. Hard disk is diagnosedand put to the state according the diagnostics result of phase:

SE = broken,

WO = OK,

TE = under diagnosis

Changing a hard disk

Before you start

If you have formatted disks at your disposal, performing this task is faster.For instructions on formatting the hard disks, see Initialising hard disks.

Steps

1. Change the state of the WDU into TE (IHE)

ZIHE::WDU,<device index>:TE;



Note

When one of the hard disks is set to another state than WO-EX, thesystem locks the operating state of the remaining hard disk, thatmeans, additional working state flag LCK is displayed in the workingstate information of the other disk.

2. Change the state of the SCSI into SE (IHE)

The value for the SCSI bus index parameter is the same as theindex number of the faulty hard disk. If you changed WDU-0 to TEstate, then set SCSI-0 to SE state. If you changed WDU-1 to TEstate, then set SCSI-1 to SE state.

ZIHE::SCSI,<scsi bus index>:TE;

ZIHE::SCSI,<scsi bus index>:SE;


Note

If the disk is broken, the system has automatically separated the disk.

3. Remove the disk from its place

4. Check the strapping of the new disk

Make sure the strappings of the new disk correspond to those of thereplaced disk. For more information on strappings, see the SiteDocuments.

5. Put the new unit into its place and connect the power and signalcables

6. Change the state of SCSI into WO (IHE)



ZIHE::SCSI,<scsi bus index>:WO;



Hard disk is faulty

7. If the new disk is not formatted and initialised

Then

Format the disk (IWI)

Note

Formatting a disk is quite slow. It may take about 0.5 hours for a 9 GBWDU.

ZIWI::<disk device>;

Else

Initialise the WDU (IWK)

If you have a formatted disk at your disposal, initialise the disk.

ZIWK::<disk device>;

8. Diagnose the WDU in both OMU units (UDD)

Diagnosing the WDU in both OMUs

ZUDD:OMU,0:WDU,<device index>:<priority>;

ZUDD:OMU,1:WDU,:<device index>:<priority>;

ZUDD:<main unit identification>:<I/O device type>:<device index>:<priority>;

Expected outcome

Diagnosing takes maximum two minutes per unit.

Check the diagnostics result:

ZUDH:WDU,<device index>;

If the diagnosis result is OK, set the state of the WDU to WO-EX withthe following command:

ZIHE:OMU:WDU,<device index>:WO;



Unexpected outcome

If the diagnosis result is not OK, the state of the WDU isautomatically changed to SE-OU.

9. Check if the mirroring update is proceeding (IHI)

Wait while the system updates the data from the other disk. You cancheck that updating is proceeding. The mirror updating (MIR)additional state flag shows this.

ZIHI::WDU;

Expected outcome

Mirroring takes several minutes.

When mirroring has been successfully completed, both the MIR andLCK flags are reset.

Unexpected outcome

If both disks are in the WO-EX state and the MIR flag is no longerdisplayed, but the LCK flag is still set, the mirroring was notsuccessfully completed, and the hard disk duplication is notfunctional. See Mirroring fails for further instructions.



Hard disk is faulty



22 NEMU hard disk failsDescription

Because of the data duplication involved in mirror sets, the systemcontinues to function even when a member of the mirror set fails. If, for anyreason, either of hard disks fails or goes offline while in a raid level-1mirrored configuration, Windows 2000 continues to run from the mirroreddisk.

Recovering from hard disk failure when using software RAID1 is a verycomplicated process. Please follow the instructions carefully.

Note

Using OMU hard disks in NEMU is strictly forbidden, unless the disk iscompletely reformatted, including boot sector. OMU disk boot sector isincompatible with Windows 2000 file system and using OMU hard diskin NEMU will lead to failure in boot and loss of all data!

Symptoms

When either of the hard disks fail, a pop-up window with the text “Windows- FT Orphaning, a disk that is part of a fault-tolerant volume can no longerbe accessed” will appear to Windows desktop. Also, System Log will haveseveral events with event ID 15.

Recoveryprocedures

When you notice a disk failure, do the following:

1. Click OK in the pop-up window.

2. Log on to the system using an account with administrator privileges.



NEMU hard disk fails

3. Open the Disk Management by clicking Start, Programs,Administrative Tools and then click Computer Management.

4. In the console tree under Storage, click Disk Management.

5. Check which disk has status Missing.

6. If Disk 0 is missing, proceed to the instruction: MCPC2(-A), Primaryoperating system disk has failed, disk 0 or MCP18(-B), Primaryoperating system disk has failed, disk 0, depending on the NEMUplug-in unit used.

7. If Disk 1 is missing, proceed to the instruction: MCPC2(-A),Secondary operating system disk has failed, disk 1 or MCP18(-B),Secondary operating system disk has failed, disk 1, depending onthe NEMU plug-in unit used.



23 MCPC2(-A), Primary operating systemdisk has failed, disk 0

Description

Primary operating system disk (disk 0) has failed. See the recoveryprocedure for recovering from this failure.

Note

Read the section NEMU hard disk fails before you start the recoveryprocedure.

This procedure provides instructions for troubleshooting the primaryoperating system disk of NEMU on the HDS/HDS9/HDS-A plug-in unit.

Symptoms

A pop-up window with the text “Windows - FT Orphaning, a disk that is partof a fault-tolerant volume can no longer be accessed” appears to theWindows desktop. Also, the System Log has several events with event ID15. In this case, disk 0 is missing.

Recoveryprocedures

Recovering from hard disk failure (primary operating system, disk 0)

Steps

1. Break mirrors using Disk Management

a. Right-click partition C on the missing disk (Disk 0).

b. Select the Remove Mirror option. Select Missing and click theRemove Mirror button. Then click the Yes button.

c. Right-click the partition E on the missing disk (Disk 0).



MCPC2(-A), Primary operating system disk has failed, disk 0

d. Select the Remove Mirror option. Select Missing and click theRemove Mirror button. Then click the Yes button.

e. Shut down the MCPC2/MCPC2-A by clicking the Start buttonand selecting the Shutdown option. From the drop downmenu, select the Shutdown option and click the OK button.

2. When NEMU has shut down (the text 'It is now safe to turn offyour computer' is displayed), remove the HDS/HDS9/HDS-Aplug-in unit with the WDU-0 (broken disk).

3. Remove the HDS/HDS9/HDS-A plug-in unit with the WDU-1(good disk).

4. Set the SCSI ID of WDU-1 (good disk) to the same place as therewas in theWDU-0 (broken disk).

5. Insert the HDS/HDS9/HDS-A plug-in unit with the old WDU-1 asWDU-0, that is, replace the WDU-0 with the WDU-1.

6. Replace the broken hard disk with the new one. Set the SCSI IDof the new hard disk to the same place as there was in the oldWDU-1 (broken disk).

7. Insert the HDS/HDS9/HDS-A plug-in unit with the replaced harddisk as WDU-1.

8. Restart the MCPC2/MCPC2-A by pressing the RST button in theMCPC2-A front panel.

9. When NEMU has started, log on to NEMU using an account withadministrator privileges.

10. Re-mirror the disks using Disk Management

a. Start Computer Management from Start, Programs,Administrative Tools.

b. In the console tree under Storage, click Disk Management.

c. If the Write Signature and Upgrade Disk wizard opens:

i. Click the Next button.

ii. Check disk 1 and click the Next button.

iii. If displayed again, check disk 1 and click the Nextbutton.

iv. Click the Finish button.

v. Go to step e).



Note

Step e) is displayed online as step 5.

d. If the Write signature and Upgrade Disk wizard does not open:

i. Right-click Disk 1, and if Import Foreign Disks is visiblein the pop-up menu, select it. Click the OK button. Ifanother dialog opens, click the OK button.

ii. Right-click the Disk 1, and if Reactivate Disk is visible inthe pop-up menu, select it. Click the OK button. Wait forthe disk to go online.

iii. Delete all possible old partitions on Disk 1 by right-clicking the partition and selecting Delete Volume. Clickthe Yes button. Repeat this step as many times asneeded.

iv. Right-click Disk 1 and if Upgrade to Dynamic Disk optionis visible in the pop-up menu, select it. Click the OKbutton. Click Upgrade. Then click the Yes button twice.

e. Remove the missing hard disk by right-clicking Missing diskand selecting Remove Disk. In some cases, there can be twodisks identified as Disk 1. Ignore that, the extra Disk 1 willdisappear in the next reboot.

f. Right-click the C-partition on Disk 0, and then click Add Mirror.

g. In the Add Mirror window, select Disk 1 (if Disk 1 appearstwice, select the upper one) and click Add Mirror.

h. The Disk Management message box appears. Click the OKbutton. Regenerating of the C-drive begins.

i. Right-click the E-partition on Disk 0 and then click Add Mirror.

j. In the Add Mirror window, select Disk 1 and click Add Mirror.Regenerating of the E-drive begins.

k. Wait for the regenerating of both partitions to complete.



MCPC2(-A), Primary operating system disk has failed, disk 0



24 MCPC2(-A), Secondary operating systemdisk has failed, disk 1

Description

Secondary operating system disk (disk 1) has failed. See the recoveryprocedure for recovering from this failure.

Note


This procedure provides instructions for troubleshooting the secondaryoperating system disk of NEMU on the HDS/HDS9/HDS-A plug-in unit.

Symptoms


Recoveryprocedures

Recovering from hard disk failure (secondary operating system, disk 1)

Steps

1. Break mirrors using Disk Management:



c. Right-click partition E on the missing disk (Disk 1).



MCPC2(-A), Secondary operating system disk has failed, disk 1


e. Shut down the MCPC2/MCPC2-A by clicking the Start buttonand selecting the Shut Down option. From the drop-downmenu, select Shut Down and click the OK button.

2. When NEMU has shut down (the text 'It is now safe to turn offyour computer' is displayed), remove the HDS/HDS9/HDS-Aplug-in unit with the WDU-1 (broken disk).

3. Replace the broken hard disk with a new one. Set the SCSI ID ofa new hard disk to the same place as there was in the old WDU-1 (broken disk).

4. Insert the HDS/HDS9/HDS-A plug-in unit with a replaced harddisk as WDU-1.

5. Restart the MCPC2/MCPC2-A by pressing the RST button in theMCPC2/MCPC2-A front panel.







ii. Check disk 1 and click the Next button.

iii. If displayed again, check disk 1 and click the Nextbutton.


v. Go to step e).

Note

Step e) is displayed online as step 5.

d. If the Write Signature and Upgrade Disk wizard does not open:



i. Right-click Disk 1 and, if Import Foreign Disks is visiblein the pop-up menu, select it. Click the OK button. Ifanother dialog opens, click the OK button.

ii. Right-click Disk 1 and, if Reactivate Disk is visible in thepop-up menu, select it. Click the OK button. Wait for thedisk to go online.


iv. Right-click Disk 1 and, if Upgrade to Dynamic Disk isvisible in the pop-up menu, select it. Click the OK button.Click Upgrade. Then click the Yes button twice.

e. Remove the missing hard disk by right-clicking Missing diskand selecting Remove Disk. In some cases, there can appeartwo disks identified as Disk 1. Ignore that, the extra Disk 1 willdisappear in the next reboot.

f. Right-click C-partition on Disk 0 and then click Add Mirror.


h. The Disk Management message box appears. Click the OKbutton. Regenerating of C-drive begins.

i. Right-click E-partition on Disk 0 and then click Add Mirror.

j. In the Add Mirror window, select Disk 1 and click Add Mirror.Regenerating of E-drive begins.




MCPC2(-A), Secondary operating system disk has failed, disk 1



25 MCP18(-B), Primary operating systemdisk has failed, disk 0

Description

Primary operating system disk (disk 0) has failed. See the recoveryprocedure for recovering from this failure.

Note


This procedure provides instructions for troubleshooting the primaryoperating system disk of NEMU on the HDS-A plug-in unit.

Symptoms


Recoveryprocedures

Recovering from hard disk failure (primary operating system, disk 0)

Steps




c. Right-click the partition E on the missing disk (Disk 0).



MCP18(-B), Primary operating system disk has failed, disk 0


e. Shut down the MCP18/-B by clicking the Start button andselecting the Shutdown option. From the drop down menu,select the Shutdown option and click the OK button.

2. When NEMU has shut down (the text 'It is now safe to turn offyour computer' is displayed), remove the HDS-A plug-in unitwith the WDU-0 (broken disk).

3. Remove the HDS-A plug-in unit with the WDU-1 (good disk).

4. Set the SCSI ID of WDU-1 (good disk) to the same place as therewas in the WDU-0 (broken disk).

5. Insert the HDS-A plug-in unit with the old WDU-1 as WDU-0, thatis, replace the WDU-0 with the WDU-1.

6. Replace the broken hard disk with the new one. Set the SCSI IDof the new hard disk to the same place as there was in the oldWDU-1 (broken disk).

7. Insert the HDS-A plug-in unit with the replaced hard disk asWDU-1.

8. Restart the MCP18/-B by pressing the RST button in theMCP18/-B front panel.





c. Right-click disk 1 and if Write Signature is visible in the pop-upmenu, select it. Click the OK button.

d. Delete all possible old partitions on disk 1 by right-clickingpartition and selecting Delete Volume or Delete Partition. Clickthe Yes button. Repeat this step as many times as needed.

e. Right-click disk 1 and if Upgrade to Dynamic Disk is visible inthe pop-up menu, select it. Click the OK button.



f. Remove the missing hard disk by right-clicking Missing diskand selecting Remove Disk. In some cases, there can be twodisks identified as Disk 1. Ignore that, the extra Disk 1 willdisappear in the next reboot.

g. Right-click the C-partition on Disk 0, and then click Add Mirror.

h. In the Add Mirror window, select Disk 1 (if Disk 1 appearstwice, select the upper one) and click Add Mirror.

i. The Disk Management message box appears. Click the OKbutton. Regenerating of the C-drive begins.

j. Right-click the E-partition on Disk 0 and then click Add Mirror.

k. In the Add Mirror window, select Disk 1 and click Add Mirror.Regenerating of the E-drive begins.

l. Wait for the regenerating of both partitions to complete.



MCP18(-B), Primary operating system disk has failed, disk 0



26 MCP18(-B), Secondary operating systemdisk has failed, disk 1

Description

Secondary operating system disk (disk 1) has failed. See the recoveryprocedure for recovering from this failure.

Note


This procedure provides instructions for troubleshooting the secondaryoperating system disk of NEMU on the HDS-A plug-in unit.

Symptoms


Recoveryprocedures

Recovering from hard disk failure (secondary operating system, disk 1)

Steps

1. Break mirrors using Disk Management:



c. Right-click partition E on the missing disk (Disk 1).



MCP18(-B), Secondary operating system disk has failed, disk 1


e. Shut down the MCP18/-B by clicking the Start button andselecting the Shut Down option. From the drop-down menu,select Shut Down and click the OK button.

2. When NEMU has shut down (the text 'It is now safe to turn offyour computer' is displayed), remove the HDS-A plug-in unitwith the WDU-1 (broken disk).

3. Replace the broken hard disk with a new one. Set the SCSI ID ofa new hard disk to the same place as there was in the old WDU-1 (broken disk).

4. Insert the HDS-A plug-in unit with a replaced hard disk as WDU-1.

5. Restart the MCP18/-B by pressing the RST button in theMCP18/-B front panel.





c. Right-click Disk 1 and if Write Signature is visible in the pop-upmenu, select it. Click the OK button.

d. Delete all possible old partitions on Disk 1 by right-clickingpartition and selecting Delete Volume or Delete Partition. Clickthe Yes button. Repeat this step as many times as needed.

e. Right-click Disk 1 and if Upgrade to Dynamic Disk is visible inthe pop-up menu, select it. Click the OK button.

f. Remove the missing hard disk by right-clicking Missing diskand selecting Remove Disk. In some cases, there can appeartwo disks identified as Disk 1. Ignore that, the extra Disk 1 willdisappear in the next reboot.

g. Right-click C-partition on Disk 0 and then click Add Mirror.

h. In the Add Mirror window, select Disk 1 (if Disk 1 appearstwice, select the upper one) and click Add Mirror.

i. The Disk Management message box appears. Click the OKbutton. Regenerating of C-drive begins.

j. Right-click E-partition on Disk 0 and then click Add Mirror.



k. In the Add Mirror window, select Disk 1 and click Add Mirror.Regenerating of E-drive begins.

l. Wait for the regenerating of both partitions to complete.



MCP18(-B), Secondary operating system disk has failed, disk 1



27 Hard disk (HDS-B) is faultyDescription

The following instructions explain how to replace a faulty OMU or NEMUhard disk on the HDS-B plug-in unit so that no data is lost. It isrecommended to perform this task during low traffic.

In the case of the HDS-B plug-in unit, OMU and NEMU hard disks arelocated on the same hard disk adapter. The positions of OMU and NEMUhard disks on the HDS-B are shown in figure 1.



Hard disk (HDS-B) is faulty

Figure 25. HDS-B

When one of the hard disks on HDS-B is faulty, both NEMU and OMU unitsare affected. To be able to replace a faulty disk with a new one, the wholeHDS-B must be removed. Both OMU and NEMU disks on that plug-in-unitmust be tested when HDS-B is plugged in containing a replaced disk.

BACKPLANECONNECTORS

POWERCONNECTORS

SCSI BUSFLAT CABLES

SCSICONNECTORS

FRONT PANEL

HARD DISK

1

CN2

SCSIINTERFACE

1

CN2

SCSIINTERFACE

B

NEMU

A

OMU

1

2

3

4

5

HARD DISK

1 1

3 3

2 2

1

2

3

DN0639472



Note

In this release, NEMU's HDD (hard disk drive) and OMU's WDU areboth located in the HDS-B plug-in unit. As NEMU is not a functional unitof the network element, its components must not be created asfunctional units into the Equipment database. This means that NEMU(the MCP18 plug-in unit) and NEMU HDD (in the HDS-B plug-in unit)are created as plug-in units only.

However, OMU WDU, also located in the HDS-B plug-in unit, must becreated as a functional unit too.

For more information on plug-in units and functional units, seeHardware configuration data management in Hardware ConfigurationManagement for MGW or RNC.

Because of the data duplication involved in NEMU mirror sets, the systemcontinues to function even when a member of the mirror set fails. If, for anyreason, either one of the hard disks fails or goes offline while in a raidlevel-1 mirrored configuration, Windows 2000 continues to run from themirrored disk. Recovering from hard disk failure when using softwareRAID1 is a very complicated process. Please follow the instructions onreplacing a faulty NEMU hard disk carefully.

See the following procedures for each case:

. A. OMU hard disk is faulty (WDU 0 or WDU 1)

. B. NEMU hard disk (hard disk 0) is faulty

. C. NEMU hard disk (hard disk 1) is faulty

Symptoms

. An OMU hard disk is faulty: one of the following alarms is set: 1803(SCSI MALFUNCTION), 2819 (SCSI DEFECT), 2823 (HARD DISKVERIFICATION FAILURE), 2860 (DISK FAILURE), or 2861 (NOACCESS TO DISK).

. One of the NEMU hard disks is faulty: a pop-up window with the text“Windows - FT Orphaning, a disk that is part of a fault-tolerantvolume can no longer be accessed” will appear to Windows desktop,and System Log will have several events with event ID 15.




Recoveryprocedures

A. OMU hard disk is faulty

Before you start

Note

If both hard disks of OMU become faulty at the same time, you need torestore the data from the FDU drive. For detailed instructions, seeRestoring software from FDU if both OMU hard disks are faulty.

If you have formatted disks at your disposal, performing this task is faster.For instructions on formatting the hard disks, see Initialising hard disks.

Steps

1. Check if the OMU hard disk is faulty

a. In the booting phase of OMU

ZLP:P,POM

ZPKL

. Log starts with 'ncr' means problems with the SCSIdriver (check at least the SCSI cabling to rule out the HWerrors)

. Log with 'sense' text means problems with the SCSIdevice (meaning either hard disk or FDU drive)

. Logs with 'discarding' texts means Shadows file systemhas rejected the corresponding device and the disk isnot included in the mount

. Error code 0x3685 ENXIO: device does not exist

. Error code 0x3684 EIO: device is in catatonic state

. Any other error: please contact the Nokia Help Desk

Note

If the log states: 'SHF: TWO DIFFERENT DATABASE FOUND,UNABLE TO CONTINUE', there are two valid disks with differentcontents and the system cannot interpret which one to use. The otherhard disk is to be removed. You should check both disk file contentsand make decision accordingly.



b. Not in booting phase:

There are alarms set on the hard disk device. Hard disk isdiagnosed and put to the state according the diagnostics resultof phase. If the hard disk is broken, it is put to the state SE-OU:

SE = broken

Other possibilities are:

WO = OK,

TE = under diagnosis

2. Change the state of the faulty WDU into TE (IHE)

ZIHE::WDU,<deviceindex>:TE;

Note


3. Change the state of the SCSI into SE (IHE)

The value for the SCSI bus index parameter is the same as theindex number of the faulty hard disk. If you changed WDU-0 to TEstate, then set SCSI-0 to SE state. If you changed WDU-1 to TEstate, then set SCSI-1 to SE-NH state.




Note

If the disk is broken, the system has automatically separated the disk.

4. Remove the HDS-B plug-in unit from the subrack

5. Remove the broken OMU hard disk




6. Check the strappings of the new disk


7. Put the new hard disk into its place on the HDS-B and connectthe power and signal cables

8. Reinstall HDS-B plug-in unit

9. Re-mirror the NEMU hard disks

a. In the pop-up window Fault tolerant disk cannot be accessed,click OK.

b. If you have not logged in, log in using an account withadministrator privileges.

c. Sart Disk Management by selecting Computer Managementfrom Start, Settings, Control Panel, Administrative Tools.

d. Right-click the mouse on top of the disk with the status Missingand select Reactivate Disk.

e. Disk mirror regenerating will start.

10. Change the state of SCSI into WO (IHE)



ZIHE::SCSI,<scsi bus index>:WO;

11. If the new disk is not formatted and initialised

Then

Format the disk (IWI)

Note

Formatting a disk is quite slow. It may take about 0.5 hours for a 9 GBWDU.

ZIWI::<disk device>;

Else



Initialise the WDU (IWK)

If you have a formatted disk at your disposal, initialise the disk.

ZIWK::<disk device>;

12. Diagnose the WDU in both OMU units (UDD)

Diagnosing the WDU in both OMUs

ZUDD:OMU,0:WDU,<device index>:<priority>;

ZUDD:OMU,1:WDU,:<device index>:<priority>;

Expected outcome

Diagnosing takes a maximum of two minutes per unit.

Check the diagnostics result:

ZUDH:WDU,<device index>;

If the diagnosis result is OK, set the state of the WDU to WO-EX withthe following command:

ZIHE:OMU:WDU,<device index>:WO;

Unexpected outcome

If the diagnosis result is not OK, the state of the WDU isautomatically changed to SE-OU.


Wait while the system updates the data from the other disk. You cancheck that updating is proceeding. The mirror updating (MIR)additional state flag shows this.

ZIHI::WDU;

Expected outcome

Mirroring takes several minutes.

When mirroring has been successfully completed, both the MIR andLCK flags are reset.




Unexpected outcome

If both disks are in the WO-EX state and the MIR flag is no longerdisplayed, but the LCK flag is still set, the mirroring was notsuccessfully completed, and the hard disk duplication is notfunctional. See Mirroring fails for further instructions.

14. Check that NEMU disk mirroring is proceeding or has beencompleted

B. NEMU hard disk (hard disk 0) is faulty

Before you start

NEMU hard disk changing procedure differs depending on whether thefaulty disk is the primary operating disk (hard disk 0) or the secondaryoperating disk (hard disk 1). Follow these instructions if the broken disk isthe primary operating disk (hard disk 0).

Note


Steps

1. Click OK in the pop-up window

2. Log on to the system using an account with administratorprivileges

3. Open the Disk Management by clicking Start, Programs,Administrative Tools and then click Computer Management

4. In the console tree under Storage, click Disk Management




c. Right-click the partition E on the missing disk.




e. Shut down the MCP18(-B) by clicking the Start button andselecting the Shutdown option. From the drop down menu,select the Shutdown option and click the OK button.



7. Replace NEMU hard disk 1 (good disk) with a new disk

a. Change the state of the OMU WDU into TE (IHE).

Change the state of the WDU on the HDS-B with the brokenNEMU hard disk into TE.

ZIHE::WDU,1:TE;.

Note


b. Change the state of the OMU SCSI into SE-NH (IHE)

ZIHE::SCSI,1:TE;

ZIHE::SCSI,1:SE;

ZIHE::SCSI,1:SE;

c. When NEMU has shut down (the text 'It is now safe to turn offyour computer' is displayed), remove the HDS-B plug-in unitwith hard disk 1 (good disk).

d. Replace NEMU's hard disk with a new disk and set the SCSIID of the new hard disk 1 to be the same as that of the previoushard disk 1.

8. Install the HDS-B plug-in unit with the new hard disk 1 (newdisk)

a. Insert the HDS-B plug-in unit in hard disk 1 position.

b. Change the state of OMU SCSI in WO (IHE)

ZIHE::SCSI,1:SE;

ZIHE::SCSI,1:TE;

ZIHE::SCSI,1:WO;




c. Set the state of OMU WDU-1 to WO-EX

ZIHE:OMU:WDU,1:WO;


Wait while the system updates the other disk. OMU hard disks haveto mirrored before the other one of the HDS-B units can bedisconnected.

You can check that updating is proceeding, the mirror updating (MIR)flag shows this.

ZIHI::WDU;

Expected outcome

Diagnosing takes a maximum of two minutes. When mirroring hasbeen successfully completed, both the MIR an LCK flags are reset.

Unexpected outcome

If both disks are on the WO-EX state and the MIR flag is no longerdisplayed, but the LCK flag is still set, mirroring was not successfullycompleted, and the hard disk duplication is not functional. SeeMirroring fails for further instructions.

10. Replace NEMU hard disk 0 (broken disk) with the previous harddisk 1 (good disk)

a. Change the state of the OMU WDU-0 into TE (IHE)

ZIHE::WDU,0:TE;.

Note



ZIHE::SCSI,0:TE;

ZIHE::SCSI,0:SE;

ZIHE::SCSI,0:SE;



c. Remove the HDS-B plug-in unit with the hard disk 0 (brokendisk).

d. Replace the broken NEMU hard disk (hard disk 0) with theprevious hard disk 1 disk and set the SCSI ID of the hard diskto be the same as that of the old hard disk 0 (broken disk).

11. Install the HDS-B plug-in unit in hard disk 0 position (replacedwith the previous hard disk 1)

a. Insert the HDS-B plug-in unit in hard disk 0 position.

b. Change the state of OMU SCSI ID into WO (IHE)

ZIHE::SCSI,0:SE;

ZIHE::SCSI,0:TE;

ZIHE::SCSI,0:WO;


ZIHE:OMU:WDU,0:WO;


Wait while the system updates the other disk. You can check thatupdating is proceeding, the mirror updating (MIR) flag shows this.

ZIHI::WDU;

Expected outcome

Mirroring takes several minutes. When mirroring has beensuccessfully completed, both the MIR an LCK flags are reset.

Unexpected outcome


13. Restart the MCP18(-B) by pressing the RST button in the MCP18(-B) front panel

14. When NEMU has started, log on to NEMU using an account withadministrator privileges









ii. Check Disk 1 and click the Next button.

iii. If displayed again, check Disk 1 and click the Nextbutton.


v. Go to step e).













C. NEMU hard disk (hard disk1) is faulty

Before you start

NEMU hard disk changing procedure differs depending on whether thefaulty disk is the primary operating disk (hard disk 0) or the secondaryoperating disk (hard disk 1). Follow these instructions if the broken disk isthe secondary operating disk (hard disk 1).



Note


Steps

1. Click OK in the pop-up window

2. Log on to the system using an account with administratorprivileges

3. Open the Disk Management by clicking Start, Programs,Administrative Tools and then click Computer Management

4. In the console tree under Storage, click Disk Management




c. Right-click the partition E on the missing disk.


e. Shut down the MCP18(-B) by clicking the Start button andselecting the Shut Down option. From the drop down menu,select the Shut Down option and click the OK button.



7. Replace NEMU hard disk 1 (broken disk) with a new disk

a. Change the state of the OMU WDU into TE (IHE)

ZIHE::WDU,1:TE;.




Note



ZIHE::SCSI,1:TE;

ZIHE::SCSI,1:SE;

ZIHE::SCSI,1:SE;

c. When NEMU has shut down (the text 'It is now safe to turn offyour computer' is displayed), remove the HDS-B plug-in unitwith hard disk 1 (broken disk).

d. Replace the broken hard disk with a new disk and set the SCSIID of the new hard disk 1 to be the same as that of the previoushard disk 1.

8. Install HDS-B plug-in unit with hard disk 1

a. Insert the HDS-B plug-in unit in with the new disk in hard disk 1position.

b. Change the state of OMU SCSI-1 in WO (IHE)

ZIHE::SCSI,1:SE;

ZIHE::SCSI,1:TE;

ZIHE::SCSI,1:WO;


ZIHE:OMU:WDU,1:WO;


Wait while the system updates the other disk. You can check thatupdating is proceeding, the mirror updating (MIR) flag shows this.

ZIHI::WDU;

Expected outcome

Diagnosing takes a maximum of two minutes. When mirroring hasbeen successfully completed, both the MIR an LCK flags are reset.

Unexpected outcome




10. Restart the MCP18(-B) by pressing the RST button in the MCP18(-B) front panel

11. When NEMU has started, log on to NEMU using an account withadministrator privileges






ii. Check Disk 1 and click the Next button.

iii. If displayed again, check Disk 1 and click the Nextbutton.


v. Go to step e).


















Related Topics


Instructions

Taking unit back into use


Working state change fails

Descriptions

Possible working state transitions

Working state change


Instructions



Instructions




Related Topics


Instructions



Instructions



Instructions




Instructions






Instructions



Instructions



Instructions



Instructions



Instructions




Related Topics


Instructions




Instructions



Instructions


Fan tray is faulty

Instructions





Instructions


Hard disk is faulty

Instructions

Increasing capacity of hard disk

Descriptions

Hard disks

Operating states of I/O devices


Instructions

Increasing capacity of hard disk

Descriptions

Hard disks

Operating states of I/O devices



Related Topics

hw change

Documents

lockingallen key m2

esd wrist strap

allen key m2

general environmental requirements

remote debugger session

touching integrated circuits

cautionpay special attention

tftp application separately