Scribd
Upload
49 views2 pages

Testing Unit After Replacing A Plug-In Unit: Purpose

Uploaded by

myjunkaccounthotmail
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
49 views2 pages

Testing Unit After Replacing A Plug-In Unit: Purpose

Uploaded by

myjunkaccounthotmail
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Nokia WCDMA RAN, Rel.

RAS06,
Library:
System Library, v. 2

Identifier: dn0282569-3-en

Testing unit after replacing a plug-in unit


Purpose

If you have replaced the plug-in unit, you can test the unit with the following procedure. For more information on replacing plug-in units, see
Plug-in unit is faulty.

Steps

Expand/collapse all

1. Check unit state (USI)

ZUSI;

If the unit is in TE state, you can start the test. If it is not, bring the unit back into TE test state by using the USC command.

2. Start test of a unit (UDU)

To make sure that the repair operation was successful, test the unit.

ZUDU:<unit identification>:<partial test>:<priority>;

3. Monitor the test progress (UDQ)

You can monitor the progress of testing with occasional enquiries to the diagnostic system or via intermediate printouts that
are printed out on the alarm printer. The intermediate printouts give information about the partial diagnoses. The total test of a
unit may take from less than a second up to half an hour, depending on the hardware configuration of the unit (the duration
can be multiplied by increasing the number of test repetitions through file parameters).

ZUDQ;

If no faults are found in the total test, the following text is printed out on the printer: TOTAL DIAGNOSIS EXECUTED - UNIT
OK.

The message indicates that the system has registered the unit as operational.

4. Check the test result (UDH)

ZUDH:<unit identification>;

Example: Starting a total test

One of the features of the diagnostic system is that it diagnoses the faults in as many as 100 units at a time. The diagnostic system uses,
however, critical resources which force the diagnostic jobs in consecutive order. The system may respond that it is busy when given a
diagnosis activation command.

The UDQ command can be used to enquire about the reservation status of the diagnostic system, and about the currently active jobs, with an
accuracy down to the partial diagnosis and the unit.

The execution printout of the command shows which diagnostic jobs are queuing for execution.
1. Start the total test of OMU-0 (where 0 is the unit index).

ZUDU:OMU,0;

Example: Starting a partial test

You can interrupt a diagnostic job in progress with the UDS command. You may need to use this command if the system is occupied with a
diagnostic job whose results are not needed at the moment, or if the diagnostics system is not functioning properly.

1. Start the RAM partial test on OMU pair, unit index 1, as a priority job.

ZUDU:OMU,1:RAM:PRI:;

Example: Listing all broken units in the system

Use the command for listing broken units (UDL) to get a list of the functional units in the system that have been registered as broken (BRKN).

If there are broken units, they must be handled one at a time. For testing, transfer the unit to the TE state with the USC command. Then start
the diagnostics with the UDU command.

1. List broken units.

ZUDL;

As the default, the system lists all broken units. If you want a list of broken computer units only, use the COMP parameter value.

Related Topics

Descriptions

 Diagnostics and testing


 Diagnostics in failure situations

Printed from NED5

Copyright © Nokia Siemens Networks. All rights reserved.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy