Internal Use Only▲

(GSM) Technical Requisition 20090306-010 Confidential Class: B

SN G20090306-010 (SN. 282) Requisition Type Notice

Subject Notice of iBSC & iTC Hardware Check

Issued by GSM Customer Service Dept. Urgent class Urgent

Marketing & Sales

No. 1, 3, 4, 5 Divisions Operator All
Division
All regional offices, GSM
Issued to Applicable Product ZXG10-iBSC iTC
Customer Service Dept.
Problem Description:

 NEC 0707 lot of granularity on GLI040201 board has problem, which results in media plane interruption
or one-way audio and noise.
 DSP fault of GUP/UPPB board makes DSP self-inspection failure during starting.
 OMP/CMP adopts ELPIDA granular memory board, which may be disabled in a hot environment.

Troubleshooting for NEC 0707 memory granularity problem of GLI040201 board

1. Check the history alarm of GLI board and make sure whether there is alarm code: 5396.
“Exceptional Internal Media Plane Communication”
2. The above alarm may be caused by PSN abnormity. So it is necessary to check whether there is
interruption alarm in PSN of the same time.
3. After eliminating the causes of PSN abnormity and personal error operation, if the above alarm appears
repeatedly, perform the check on GLI subcard bar code to make sure whether the board is of the fault
lot.
4. Pull out the fiber which is connecting with GLI board to make all of the ports automatically switch to
another board.
5. Pull out GLI board and record the bar code of subcard, as shown below.

Confidential and Proprietary Information of ZTE CORPORATION.

 　　　　　　　　　　　　　　 Internal Use Only▲

6. Check whether the bar code is listed in the following attachment. If yes, it is the subcard of fault lot.

GLI NEC 0707 Lot

of Memroy Granularity.xls

7. If any of two subcards is of the fault lot, replace GLI board.

8. Pay attention to the connection order of fiber GLI when plugging fiber.

Suggestions:

Situation 1: check alarm information. Immediately handle the alarm if there is any.

1) Check SPN unit to make sure whether the alarm is caused by PSN abnormal interruption.

2) Check bar code of board. Immediately replace the board if it is of fault lot.

Situation 2: if there is no alarm during running, it is recommended to check and record the bar code

during the major operation (like upgrade or inspection). If the code is in the list of fault lot, apply for

replacement ever if no alarm appears.

Troubleshooting for GUP/UPPB DSP fault

1. Telnet board, run SCSShowDSPStatus, check the running status of DSP chip. The print information is
as follows.
VTCD->SCSShowDSPStatus

Confidential and Proprietary Information of ZTE CORPORATION.

 　　　　　　　　　　　　　　 Internal Use Only▲

The CallbackFunction for DSP Reset is 0x31c51c .

The number of DSP is 14.

DSP0 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP1 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP2 Status is ERR_SELFCHECK. Updated 1 times. Succ Loaded 0 times. DB config is IBSC_AMREN.

DSP3 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP4 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP5 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP6 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP7 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP8 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP9 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP10 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP11 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP12 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is IBSC_AMREN.

DSP13 Status is RUNNING. Updated 1 times. Succ Loaded 1 times. DB config is

// The normal status shall be running as the above print in blue. Other status is abnormal, such as the

above print in red “ERR_SELFCHECK” which means DSP2 self-inspection failure.

2. If the self-inspection failure appears, type BSP_DbgBistShow to check the cause of self-inspection
failure.
For example:

VTCD->BSP_DbgBistShow

ERR DEVICE ID INDEX ERR CODE RESV

==========================================

0x1200 0x2 0x12001216 0x0

==========================================

value = 0 = 0x0

// If the query result displays the above part in red, ERR CODE is 0x12001216 which means abnormal

external SDRAM address pin dry joint.

Remark: if the following value corresponding to ERR CODE appears in the print information after typing

BSP_DbgBistShow, it indicates the fault is irrelated to hardware.

ERR CODE Cause

0x12001212 abnormal HPI data pin dry joint
0x12001213 abnormal HPI data pin interconnection

Confidential and Proprietary Information of ZTE CORPORATION.

 　　　　　　　　　　　　　　 Internal Use Only▲

0x12001214 abnormal external SDRAM data pin dry joint

0x12001215 abnormal external SDRAM data pin interconnection
0x12001216 abnormal external SDRAM address pin dry joint
0x12001217 abnormal external SDRAM address pin interconnection
3. If the following print appears after typing BSP_DbgBistShow, it indicates HW check is wrong.
VTCD->BSP_DbgBistShow

ERR DEVICE ID INDEX ERR CODE RESV

==========================================

0x1200 0x6 0x12140012 0x0

==========================================

value = 0 = 0x

// If the query result is 0x12140012, it means HW check error. But this may be caused by software error

check. The version before iBSCV6.10.200a has error check. It is necessary to reset the board and re-

check. If the above fault appear repeatedly after resetting and checking for three or four times, replace

the board.

4. If the above mentioned fault is found during check, it is necessary to repair board.
Suggestions:

If subscriber files a complaint that call cannot get through or call completion rate is low when iBSC is

running, perform check upon this notice.

If there is no complaint during the running, it is recommended to perform check during the equipment

inspection.

Troubleshooting for ELPIDA granular memory board of OMP/CMP

1. Pull out the standby CMP/OMP board, observe the model of memory board granularity, as shown below.

Confidential and Proprietary Information of ZTE CORPORATION.

 　　　　　　　　　　　　　　 Internal Use Only▲

2. Plug the standby CMP/OMP board. Originate the active/standby switchover of CPU1 and CPU2 on the
background five minutes after the board is running normally.
3. After the switchover is successful, pull out the current standby CMP/OMP board again and check the
model of memory board granularity.

Suggestions:

For the running iBSC, it is recommended to apply to the subscriber for check operation and then perform

the check on memory granularity.

If ELPIDA memory granularity is found, apply for board replacement.

Code of OMP memory board (512M): 053534000086

Code of CMP memory board (1G): 053500400002

This notice will take effect upon the date of issuing. All of the onsite maintenance engineers shall strictly

carry it out.

Prepared by Chen Qi Date March 5, 2009 Reviewed by Yang Yong Date March 6, 2009

Wei Fang
Approved by Date March 6, 2009 Issued by Date March 6, 2009
Guangtuan Guangzhi

Confidential and Proprietary Information of ZTE CORPORATION.