1 RNC..............................................................................................21.1 Changing HW Unit in RNC..........................................................................21.2 Tips............................................................................................................4

1.2.1 Get HW Item code and HW version from RNC.....................................41.2.2 FB copy handling.................................................................................51.2.3 Check AAL2 Endpoint termination state..............................................51.2.4 Boot SW loading..................................................................................51.2.5 Check recovory debugger...................................................................5

2 Troubleshoot RNC..........................................................................62.1 Alarm “2518 No valid fallback copy”.........................................................62.2 Alarm “9047 Alarms not arriving from NE”................................................6

3 Troubleshoot Flexi hopper & Links..................................................63.1 Link down and far end cannot be seen in flexi hop. Mngr..........................63.2 Q1 settings and Error codes......................................................................7

4 Troubleshoot AXC / SAXC...............................................................74.1 Restart AXC from command window.........................................................7

5 Troubleshoot WBTS.......................................................................75.1 BTS ALARM Description BTS SW WN1.3-3..................................................75.2 BTS ALARM Description BTS SW WN2.0-1..................................................75.3 WBTS MANAGER BATCH FILE.....................................................................75.4 7750 FAILURE IN WCDMA BTS O&M CONNECTION.....................................75.5 BTS Mngr very slow / alarm “Telecom cell enabling or disabling” active...85.6 Traffic monitoring in WBTS........................................................................85.7 Check hanging resources in WBTS.............................................................85.8 Check file version of GAB and RRC file in RNC...........................................95.9 Cells in state BL(S) can sometimes be released by lock/unlock of VP........95.10 Not possible to Create COCO in RNW Object Browser............................95.11 Log concerning "sleeping cell"..............................................................105.12 RRC Failure issues and what to do........................................................10

5.12.1 RRC_CONN_STP_FAIL_AC (1)..........................................................105.12.2 RRC_CONN_STP_FAIL_BTS (1001C4 BTS).......................................105.12.3 RRC_CONN_STP_FAIL_TRANS (1001C5 Transmission Network).....11

6 IP................................................................................................126.1 Ping and trace..........................................................................................12

6.1.1 Ping WBTS from AXC remotely..........................................................126.1.2 Print AXC Routing table from command window...............................12

7 ATM............................................................................................147.1 DCN, Signalling & Traffic routing.............................................................14

1 RNC

1.1 Changing HW Unit in RNC

Back to index

Check status of unit:ZUSI:”unit type”,”unit number”;

Change unit state:Unit must be set in SE-NH before swap of HWZUSC

Note 1!If the PIU is a DMCU:Set the state to BL before you set it to SE-NH. Verify that there are no ongoing calls with commandZWPS:UNIT,DMCU,”unit number”:SIG;Check under column CURR. All figures shows 0 if there are no ongoing calls.

Note 2!If the PIU is a NIS1P:Check with ZYWI; if the traffic is running on the 4 SETs under the NIS1P card that will be replaced, i.e. check the MSP protection switch selector for all 4 SETs (protection group) under the NIS1P, an X in the printout shows which SET the traffic is running on and if it has a valid signal on both SETs. Use ZYWS:<prot group>:<WO or PR>; to switch MSP protestion if needed, repeat for the other SETs if needed. Do not switch if the other SET is not OK.

Swap HW unitIf applicable, e.g. on CCPC2-A cards. Check HMS jumper settings and RAM memory modules, e.g. compare settings with old card. Move RAM modules from old to new card.

HMS:

See also RNC HMS software update procedure_v1_16.pdf

Check HMS SW version:

Enter Service terminalZDDS? (Check that extension H…….HMS EXTENSION exists)If not:ZLP:H,HME;H (enter HME extension)?CO (Check syntax of command CO)Check HMS version and HMS type:CO:rack,subrack,ppa; (ppa is plug-in unit position in a hex format)

Note! HMS node exists in 2 variants, 1st release or A variant. If node is A variant the CO print out will tell that.

If the HMS is old load new version:

Example: Updating HMS slave SW in one plug-in unit in the subrack. Update of one plug-in unit. (See RNC HMS software update procedure_v1_16.pdf for instruction for all types of units)

The plug-in unit must be connected in the subrack and in SE-NH (SP-EX or WO-EX also possible, but not recommended):

-HME> FA:<rack>,<subrack>,<ppa>::< directory/file_name >,Dppa is plug-in unit position in a hex format

Example for RN2.2, HMS slave node 1st release variant:-HME> FA:1,3,9::W0-/Q2280400/LFILES/HMX1SNGX.IMG,D

Example for RN2.2, HMS slave node A release variant:-HME> FA:1,1,3::W0-/Q2280400/LFILES/HMXASNGX.IMG,D

The “SW package” directory can be left out in the command, using default package instead. Then command can be used on any RNC SW level.

Example for any RNC SW Release, HMS slave node 1st release variant (CO command show “slave node”):-HME> FA:1,4,9::W0-LFILES/HMX1SNGX.IMG,D

Example for any RNC SW release, HMS slave node A release variant (CO command show “A variant slave node”):-HME> FA:1,1,3::W0-LFILES/HMXASNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the commands /7/.2. Check that the plug-in units with type 1 st release HMS node are listed with “OK state”.

NOTE! If updating was not successful (for example write flash failed: ec = 0x00003D82),

See the Section 7.Troubleshooting.. Nokia Networks

For more details see full documentation by clicking the icon below

Back to index

/7/ Updating 1 st release HMS slave code in one plug-in unit in subrack:00:HME> FA:1,2,5::W0-/Q1023100/BLCODE/HMX1SNGX.BINcode type: normal codenode type: slave bin length: 00009BFE CRC: EF77C616

Reset HMS nodesInit HMS nodesSend data packets->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-Verify node CRC-Get nodes pgm versions- reset nodes- ask programmer version- ask code versionaddress CRC pacCnt codeVers pgmVers state-------- ----------- ------ -------- ------- ------0F 07 05 EF77C616-01 2700 02.01-12 01.01-03 OK

Check status of unit:ZUSI:”unit type”,”unit number”;

Change unit state:Set unit to TE-EXZUSC:

Check Boot SW vesions:ZWDI:UT=unit,UI=unit number;

Back to index

Make sure that the Flash Memory version is the same as the Disk File version.

Example:

FUNCTIONAL PLUG-IN BOOT PACKAGE: DISK FILEUNIT UNIT VER FLASH MEMORY----------- ------------- -----------------------------------DMPG-4 CDSP_B F2A PBOCDB02.PAC 1.5-1 03/12/23 E58A9BAC (Disk)

PBOCDB02.PAC 1.5-1 03/12/23 E58A9BAC (Flash)DMPG-5 CDSP_B F2A PBOCDB02.PAC 1.5-1 03/12/23 E58A9BAC PBOCDB02.PAC 1.5-1 03/12/23 E58A9BACDMPG-6 CDSP_B F2A PBOCDB02.PAC 1.5-1 03/12/23 E58A9BAC PBOCDB02.PAC 1.5-1 03/12/23 E58A9BACDMPG-7 CDSP_B F2A PBOCDB02.PAC 1.5-1 03/12/23 E58A9BAC PBOCDB02.PAC 1.5-1 03/12/23 E58A9BAC

If they are not the same load (replace) package:ZWDRWDR:UT=DMCU,UI=16,:::

Test the unit:ZUDU (run a full test)

To see the test executionZUSIZUDQ

To check the result:ZUDH

When the test has passed change the state of the unit: USC

END

Back to index

1.2 Tips

1.2.1 Get HW Item code and HW version from RNC

ZWFL:P:<cabinet HMS number>;

1.2.2 FB copy handling

Useful commands:

ZWQO:CR; To Interrogate active SW packagesZWQH List SW Package Change historyZWKS:MODE=DATA; Data copy to BU package.ZWKS:MODE=FULL,….. Full backup copy to disk.

Command calendar:

ZICL; Check command calendarZICL:CFILE=<file name>:COM; Check commands in task

In case of command calendar failure check MML command log. Sometimes the commands are not shown even though they have been executed:

ZIGO:,,,:USERID=ALL;

Sometimes the command WKS cannot be executed due to lack of resources.

ZWXI Interrogate resourcesZWXF Release resources

Back to index

1.2.3 Check AAL2 Endpoint termination state

ZRRI;ZLJI:ROU=<route found by ZRRI>;

1.2.4 Boot SW loading

WDI:(insert correct parameters) (Interrogate versions)WDR:(insert correct parameters) (load from disc to PROM)

Back to index

1.2.5 Check recovory debugger

ZDDS:<WO OMU>;?00-MAN>LP:1,RCB?100-RCB>IC:<unit,id>

Reset flag00-RCB>TP:<unit,id>,C,<flag> (flag: FLTY)Set flag00-RCB>TP:<unit,id>,S,<flag>

2 Troubleshoot RNC

2.1 Alarm “2518 No valid fallback copy”

Alarm often appears after SW upgrade of RNC, because packages named FBMON, FBWED and/or FBFRI have been deleted.

A complete backup is made on Mon, Wed and Fri and a data dump on Tue, Thu, Sat and Sun. This is scheduled in Command Calendar.

See FB copy handling

Back to index

2.2 Alarm “9047 Alarms not arriving from NE”

Try to restart OMU in SP-EX with code loading from disk, then switchover OMU. Try also NEMU reboot.

If still problems, try to restart ULAPRB process in active OMU.Use service terminal in active OMU, “Starter Extension (SQQ)”

ZLP:2,SQQ load extensionZ2RR:302 restart family 302

Back to index

3 Troubleshoot Flexi hopper & Links

3.1 Link down and far end cannot be seen in flexi hop. Mngr.

Suggestion to fix the problem:

1. In the flexi hopper Mngr. Right click on the IFUE-unit, a new view will appear (Indoor unit settings).

2. On the “Interfaces” tab, unmark the OU power supply box to shut down the power to the outdoor unit. ! MAKE SURE YOU CHOOSE THE CORRECT Flexibus !

3. Click OK

4. When the Outdoor unit power has shut down (the Outdoor unit Icon will “light down” when the power has shut down) right click on the IFUE-unit, a new view will appear (Indoor unit settings) mark the OU power supply box again and click OK.

5. The power will come back on and you should see the far end again. Everything should look normal if this fixed the problem.

3.2 Q1 settings and Error codes

See Document : Q1 Settings

Back to index

4 Troubleshoot AXC / SAXC

4.1 Restart AXC from command window

This could be handy if you cannot reach the AXC thruogh the AXC Mngr.

1. Start a command window (command prompt)2. rsh <ip> aps check running processes3. rsh <ip> akill 24 restart AXC, SW C2.0 and later (process name unit_driver)4. rsh <ip> akill 39 restart AXC, SW C1.7 (process name lcd_AXC.gz)

5 Troubleshoot WBTS

5.1 BTS ALARM Description BTS SW WN1.3-3

See file Bts alarm description

5.2 BTS ALARM Description BTS SW WN2.0-1

See file Bts alarm description

5.3 WBTS MANAGER BATCH FILE

Enable input window for WBTS IP address in Manager:

Replace existing text in batch file with this:

@Echo offset /p ip=Enter IP Address of WAM:java -classpath .\lib\servicesif.jar -Dplatypus.trampoline=false com.nokia.platypus.Start -servicebase .\lib\servicesimp.jar .\lib\applibs.jar -appbase .\lib\btsmanager.jar .\lib\jaxp.jar .\lib\parser.jar .\lib\applibs.jar .\lib\jh.jar -startapp com.nokia.em.bts.gui.application.BtsManagerApplication -ne %ip%

Back to index

5.4 7750 FAILURE IN WCDMA BTS O&M CONNECTION

Symptom: Alarm FAILURE IN WCDMA BTS O&M CONNECTION active, Site WO, DCN OK, ping OK, BTS Man can be connected but shows "OAM Iub disconnected" in lower right part.

Solution: Site reset

Back to index

5.5 BTS Mngr very slow / alarm “Telecom cell enabling or disabling” active

Sometimes date has changed to year 2072, which makes the BTSvery slow when using BTS Man. Also alarm "Telecom cell enablingor disabling" has been active in this situation.

To fix this try to set date and time in Node B:

1. Open a Telnet session in command window:Telnet <ip addr.>username: NokiaWCDMApassword: NETOulu$ date (check date)$ time (check time)$ date 2004-03-31 (set date)$ time 13:30:00 (set time)

Back to index

5.6 Traffic monitoring in WBTS

Traffic monitoring:

ZDDS:ICSU,0;? (Check if EXTENSION "BRM MONITORING" is listed)LP:1,E2K (only needed if EXTENSION "BRM MONITORING" is not listed)? (Check if EXTENSION "BRM MONITORING" is listed)1MCD:<wbts-no>;

Back to index

5.7 Check hanging resources in WBTS

Check hanging resources:

ZDDS:ICSU,0;? (Check if EXTENSION "BRM MONITORING" is listed)LP:1,E2K (only needed if EXTENSION "BRM MONITORING" is not listed)? (Check if EXTENSION "BRM MONITORING" is listed)1MCD:<wbts-no>,1,0;MCD:<wbts-no>,6,0;

Release hanging resources by recreate COCO (Is done in Application Launcher)

Back to index

5.8 Check file version of GAB and RRC file in RNC

Check file version in RNC:

ZWQV:ICSU,0:GAB%:;ZWQV:ICSU,0:RRC%:;

Back to index

5.9 Cells in state BL(S) can sometimes be released by lock/unlock of VP

CELLS IN BL(S) can sometimes be released by lock/unlock of VP

ZLCI:<if no>,VP:<VP no>; (check current state) Lock cells in RNW Object Browser. ZLCS:<if no>,<VP no>,:LOCKED; ZLCS:<if no>,<VP no>,:UNLOCKED; Unlock cells in RNW Object Browser.

Back to index

5.10 Not possible to Create COCO in RNW Object Browser

Sometimes COCO is “hanging” when it has been deleted and created again. This could be a solution:

!MAKE SURE YOU ARE DELETING THE CORRECT VPI!

1. ZLCI:<if id>,VC,<vpi>; Interrogate. If id = Interface ID e.g. Physical connection on NIS.

If the VCI is still defined you have to Lock and delete the VCI’s first:

1. ZLCI:<if id>,<vpi>,<vci>:LOCKED; To lock the VCI2. ZLCD:<if id>,<vpi>,<vci>;To delete VCI

Then:

3. ZLCS:<if id>,<vpi>,:LOCKED; To lock the VPI4. ZLCD:<if id>,<vpi>,; To delete VPI

Go back to the RNW Object Browser and create the COCO again.

Back to index

5.11 Log concerning "sleeping cell"

printout PC/AC/LC parameters from RNW Object Browser

ZDDS:ICSU,<any WO-EXE ICSU>;? (Check if EXTENSION "BRM MONITORING" is listed)LP:1,E2K (only needed if EXTENSION "BRM MONITORING" is not listed)? (Check if EXTENSION "BRM MONITORING" is listed)1CD:<wbts-id>,<cell-id>,0;

5.12 RRC Failure issues and what to do

Back to index

5.12.1 RRC_CONN_STP_FAIL_AC (1)(1001C3 Admission Control)

BRM module in RNC.Cause ‘Brm Memory Full’S/W fault in RNCCorrected in ECD04Site reset does not helpDisconnecting/reconnecting CoCo helps

Pre emption failureS/W fault in MSC Is corrected in MSC CD05Restart does not helpIt does appear randomly in all Node Bs

Back to index

5.12.2 RRC_CONN_STP_FAIL_BTS (1001C4 BTS)

Normally two reasons:

WSP fault or CE congestion.

WSP faultAlarms: Fault in O/M and DSP s/w interface, WSP capacity overloadRestart helps temporary but fault comes back.WSP card indicated in alarm needs to be changed.

CE congestionNo alarmsNumber of RAB’s is highFaults are coming only on busy hoursRestart does not helpAdding WSP card helps

Back to index

5.12.3 RRC_CONN_STP_FAIL_TRANS (1001C5 Transmission Network)

Normally two reasons: Iub/Iur/IuCS Congestion, ATM parameter failure

ATM parameter failureAlarms: Traffic to non existent ATM cell, ATM cell lost.Restart does not helpCorrection of parameters is needed

CongestionNo alarmsAll parameters correctNumber of RAB’s is highFaults are coming only on busy hoursRestart does not helpIncrease of PCR values helps

RRC connection failing due to Radio

Reasons: Bad coverage Rogue mobiles Cells reporting too low noise level (-112dBm) Sites using IMA group over SDH link DAC word approaching the 15% limit

Bad coverageNo alarmsFailures happen all timesRestart do not helpRollout and optimisation issue

Rogue mobilesNo alarmsFailures happens only certain times of the day and follow a certain pattern.Restart do not helpIdentifying the mobile and swap of UE is needed.

Cells reporting too low noise level (-112dBm)Can be detected with on-line monitoring. Restart do not helpWTR needs to be swapped.

Sites using IMA group over SDH linkAlarms: Traffic to non existent ATM cell, ATM cell lost.Also AC, BTS and Transmission counters have failuresSite is using leased lines with min 2xE1s connected to NIP card in RNCRestart does not helpReduce the site to use 1xE1Change the NIP interfaces (PET)

DAC word approaching the 15% limitNo alarms if the DAC word is still within the limitsIncoming frequency coming from synchronisation source is incorrect or transmission settings are wrongSetting the DAC word to nominal value (2000) helps temporary but the fault comes back when WSC card is synchronised to incoming signalRestart do not helpSynchronisation source and distribution needs to be audited.

Back to index

6 IP

6.1 Ping and trace

If you suspect that there can be some problems reaching the Network Element, try a ping with large packages:

Ping large packets:ping <ip-addr> -t -l 1024 -f

To trace the hops to the desired destination:

Trace hopstracert <ip-addr>

Back to index

6.1.1 Ping WBTS from AXC remotely

rsh <AXC IP> ping <WBTS IP>

6.1.2 Print AXC Routing table from command window

rsh <AXC IP> netstat -r

Back to index

7 ATM

7.1 DCN, Signalling & Traffic routing

See document ATM1

Back to index