Alarm: Abis Path overload Usage Count: 4 90% Network: GSM Node: AXE BSC R06B Software: AXE

BSC R06B IP-A06 Node: AXE RBS 2409 Alarm: Abis Path overload Alarm is ceased after finishing Edge Call Alarm comes up sporadically while PS Edge Calls SOLUTION: CONDITIONS: PROCEDURE: The perfor mance of the DSL line is reflected in the following parameter settings in the BS C. After aligning the parameter for maximum bandwidth in downlink and maximum ba ndwidth in uplink the fault could not be reproduced any more. Parameters Setting : RRSGI:SCGR=scgr,MODE=IPM,PSTU=pstu,MBWDL=16000,MBWUL=6000; The value of parame ter MBWUL could be increased if the alarm occurs, however too high value may cau se problems with the load regulation (increasing number of handovers, new calls rejecting). Parameter Explanation: MBWDL: (64-16384 kbps) This parameter defines the maximum bandwidth in downlink. The parameter defines the bandwidth in downl ink that is considered 100% when calculating thresholds for triggering overload prevention mechanisms. This value should be set as close to the actual bandwidth as possible. MBWUL: (64-16384 kbps) This parameter defines the maximum bandwidth in uplink. The parameter defines th e bandwidth in uplink that is considered 100% when calculating thresholds for tr iggering overload prevention mechanisms. This value should be set slightly less than the actual bandwidth. TCH blocking with Abis Optimization sites Usage Count: 3 90% Network: GSM Node: AXE BSC 09A APZ 212 55 Software: AXE BSC 09A-UM17 Site with A bis Optimization does not work Printing of "RADIO TRANSMISSION SUPER CHANNEL DAT A" shows state FLT Alarm :" ABIS PATH OVERLOAD" Alarm: "ABIS PATH FAULT" on Supe r Channel High TCH drop in cells with Optimized ABIS Before this there was Group switch alarm with one XM( Plan-A) card fault.After group switch hardware unit r estoration it is likely to be hangup situation prevailing between RTPGD (PGW) de vice & RBLT2 devices. REMEDY: CONDITIONS PROCEDURE: In order to release hangup s tate Super Channel re-initialization of SC is mendatory

1.Remove the TG definition OPI. Radio X-ceiver Administration, Managed Object, D isconnect 2.Remove SC definition RRSCE:SCGR=y,SC=x,FORCE; 3.Re-initialize the SC RRSCI:SCGR=xx,SC=y,DEV1=RBLT2-xxxx,DCP=1,NUMDEV=nn; Forlopp release on TG , PGW - RP restart could not worked ABIS PATH OVERLOAD alarm on PICO cell Usage Count: 2 90% Network: GSM Node: AXE BSC 07B Feature: Abis over IP ABIS PATH OVERLOAD alarm on PICO cell Alarm :" ABIS PATH OVERLOAD" RTPGSR sends CPXTGLOADINF signal to RTPG SU, indicating IP overload, and this leads to "ABIs PATH OVERLOAD " alarm for th e relevant TG SOLUTION: CONDITIONS: "text" PROCEDURE: "text" Traffic reduced after abis optimization activated Usage Count: 2 90% GSM BSS 06A Traffic reduced after abis optimization activated Erlang Traffic is reduced ALARM: ABIS PATH OVERLOAD Abis Optimization Feature implemented in one s ite The paramater PACKALG was set to 0 in the TG ... so the ABIS was not really being optimized SOLUTION: CONDITIONS: PROCEDURE: Set the PACKALG to 1 How to avoid Abis-Interface over Satellite overload Usage Count: 1 90% How to avoid Abis-Interface over Satellite overload Network: GSM Node: AXE BSC 0 8B TCH congestion after ABIS/IP swap ALARM: ABIS PATH OVERLOAD Abis path overloa d alarm for the concerned TG Abis over satellite overload IPLOSTPACKUL shows hig h valies as compared to LOSTDLPACK Configuration change The problem is caused by bad transmission on Abis. If the IP transmission is causing a lot of packet los ses, the overload mechanism will trigger which will cause TCH congestion during the time the link is bad.

More information can be found in SCS910863. SOLUTION: CONDITIONS: 1. Abis Path O verload occur. PROCEDURE: 1. Make sure you have implemented all fixes in SCS9108 63 . 2. Make sure you have the latest BTS software, which ncludes a fix for Abis over Satellite Check delivery note: 10945-LZY213440/8 3. Check the transmission for Abis. Unable to make more than 26 calls in RBS Usage Count: 3 88% Network: GSM Node: AXE BSC 07B RBS 2308 Unable to make more than 26 calls in RBS Assignment command fails with No radio resource available No radio resource ava ilable Pre-emption handling fails leading to assignment failure Abis path overlo ad alarm for the concerned TG SC overload comes from PGW RP via signal CPXTGLOAD INF Parameters MBWUL MBWDL where set to a to low value MBWUL=400 and MBWDL=400 S OLUTION: CONDITIONS: Alarm abis path overload received PROCEDURE: Check paramete rs MBWUL and MBWDL with RRSGP:SCGR= ; Set the parameters according to the guidelines by using The tool for Abis over I P dimensioning 209/100 56-HSC 103 12/11 Uen B High droprate for site connected over satellite Usage Count: 8 Network: GSM Feat ure: Abis-Interface Over Satellite Node: AXE BSC 07B Node: AXE BSC 08A Node: AXE BSC 08B Node: AXE BSC 09A Node: AXE BSC 09B Product Name: RHLAPD Product ID: CA AZ 107 7463 R6A05 Product ID: CAAZ 107 7463 R7A01 Abis over satellite overload S DCCH setup successful rate low 76%

High SDCCH access fails because of the greater values (than normal values) of th e CESTIMMASS counter High droprate observed in certain cells Unstable LAPD links on abis interface Cell resources repeatedly blocked and deblocked The problem i s caused by an underdimensioned LAPD window size. The default window size is 15 and this is not always sufficient for the long round-trip times of satellite lin ks. It means, allthough the bandwidth that is allocated for the LAPD links (16K, 32K, 64K, abis opt/IP) should be enough, there may still be overload. For norma l LAPD links (= no satellite) any overload problems are usually for uplink direc tion (BTS to BSC). That is because the measurement reporting for all ongoing cal ls cause a higher load on the uplink than on the downlink. However, as measureme nt reporting is sent as un-acknowledged data it does not fill up the output-wind ow buffer. For downlink direction (BSC to BTS), all messages are sent as acknowl edged data. So when window size is the bottleneck (as can be for abis over satel lite), the downlink direction may be overloaded while the uplink direction is no t. The solution is obviously to increase the window size to provide higher utili zation of the bandwidth despite of the long round-trip delay. However, it has to be investigated how to optimize the value. The EC (EC-HK68949) will double the window size as a temporarry solution. Please refer to TR HK68949, EC-HK68949, HK 84069 SOLUTION: CONDITIONS: 1) Enter print command to check if there are any sit es connected over satellite. <RXMOP:MOTY=RXOTG; 2) Search printout for parameter setting SIGDE=LONG. If none is found, this solution is not valid for You. 3) In itiate the following tracing to see if the problem is present. The tracing will generate a printout everytime a LAPD link is blocked due to overload. <TEST SYST EM; <ON IN RHLAPD CPLAUTOBLOCKDL; <ON IN DO:IF DR1=3,P MS,P SWD,; <INIT; 4) Wait and see if you receive any trace output. A 5-minute period without any trace ou tput should be sufficient to at least rule out any significant overload problem. That is, provided that trace is taken at peak traffic. 5) Terminate trace. <END TEST; 6) If there were some trace output the correction reffered to may solve t he problems. PROCEDURE: Note: Temporary solution is implemented in EC-HK68949. T his EC will increase the window size for LAPD-traffic links from 15 to 30. Final solution is required. 1) Load the following correcttion: EC-HK68949 applicable for 07B and 08A. For 08B, PLM will release a MCA to fix it (M-226, which is not releasd yet). How to avoid Abis-Interface over Satellite overload Usage Count: 8 How to avoid Abi s-Interface over Satellite overload Network: GSM Node: AXE BSC Hardware: RBS 200 0 Product name: RBS2000 TRS-2 76%

Product ID: HRB 105 01/4A R6 Problem area: Radio Base Station Feature: Abis-Inte rface Over Satellite Abis over satellite overload Link goes ABL Reset DXU to rec over site The User Description, Interfaces over Satellite. Provides information on the parameters and recommendations on the interfaces. In section 2.4.2, Limit ations, explains the limitations of the feature, Abis-Interface over Satellite. The Ericsson recommendation to minimize the risk of the Abis link or cell becomi ng non operational is to deploy the AbisInterface over Satellite feature in syst ems where the Abis link capacity does not exceed 25 I-frames/sec. The Document 5 1/1553-HSC 103 12/2, User Description, Interfaces over Satellite. Provides infor mation on the parameters and recommendations on the interfaces. In section 3.4.2 Limitations states to avoid the risk of the abis link or cell going down, it is not recommended to use Abis-Interface over Satellite in systems where the Abis link load can be very high (More than 25 I-frames/sec) . The LAPD statistics cou nter can be used to see the number of received and sent LAPD I frames. The chapt er, 2.33.1 Description of Measurements, LAPD Link Measurements per TRH device . The counters described in this chapter belong to the object type, LAPD. LAPD lin k measurements are done per TRH device. The behaviour of the logical LAPD links is measured continuously for each TRH device. A set of logical LAPD links associ ated to a TRH device has its own set of counters. Every five minutes the level c ounters associated with the TRH device are scanned and added to the accumulation s counters per TRH device. The following events are counted per TRH device: Tran smitted LAPD information frames (CTRIFRAME) Received LAPD information frames (CR ECIFRAME) Retransmissions (CRETRANSM) Received bad frames (CBADFRAME) are aborte d frames, frames with cyclic redundancy check (CRC) error and frames with wrong byte count. Protocol errors (CPROCOLERR) Link failures (CLINKFAIL) Link overload s (COVERLOAD) A configuration of 1x6,1x2,1x4 should give less LAPD load than 3x4 . The 1x6 would give the highest load on the TRX with BCCH and SDCCH. If a CF is not used for sharing this type of configuration will avoid the problem with DXU going down at temporarily LAPD overload. However this would require one more TS . The DXU should not go down due to LAPD overload. The information that this cou nter has to be multiplied by 10 is already exist in the ALEX library in the appl ication information for block RHLAPD. 2/155 18-CNT 242 1099 Uen C CTRIFRAME Numb er of transmitted LAPD I and UI frames. I and UI frames means information frames with acknowledged or unacknowledged frame transmission on level 2. The counter holds the number of frames transmitted on all links on the device divided by ten to prevent overflow. CRECIFRAME Number of received LAPD I and UI frames. The co unter holds the number of frames received on all links on the device, divided by ten to prevent overflow. However, this is not stated in document 3/198 17-apt 2 1009 rev E "BSC object types and counters. This document will be corrected for R 9.1 and R10. TR HE20330 was written to address the documentation issue. SOLUTION : CONDITION: 1. Hardware: RBS 2000. 2. Product name: RBS2000 TRS-2. 3. Product I D: HRB 105 01/4A R6. 4. Link goes ABL. 5. Reset DXU to recover site. 6. Feature, Abis-Interface Over Satellite enabled. PROCEDURE: Document 51/1553-HSC 103 12/2 , User Description, Interfaces over Satellite. Provides information on the param eters and recommendations on the interfaces. In section 2.4.2 Limitations states to avoid the risk of the abis link or cell going down, it is not recommended to use Abis-Interface over Satellite in systems where the Abis link load can be ve ry high. (More than 25 I-frames/sec).

The LAPD statistics counter can be used to see the number of received and sent L APD I frames. Please be aware that the values in counters, CRECFRAME and CTRIFRA ME in object type, LAPD have to be multiplied by ten. The information can be fou nd in the ALEX library, Application Information for block RHLAPD, 2/155 18-CNT 2 42 1099 Uen C. ABIS path is unavalaible Usage Count: 118 62% Network: GSM Node: AXE BSC R10 Node: AXE BSC R9.1 Software: AXE BSC R10 NAED Sof tware: AXE BSC R10 MD Product Name: RTODCON Product ID: CAAZ 107 6762 R3A01 Prod uct name: RGRLC Product ID: CAAZ 107 6908 R4A03 Product ID: CAAZ 107 6908 R3B04 Hanging RBLT device Alarm: TS SYNC FAULT Alarm: ABIS PATH UNAVAIL Event code: H' 4300 H'9303 H'0B48 Event code: H'4301 H'9303 H'0B49 Event Explanation: TIMEOUT A T FORLOPP AUDIT & FLERROR Event code: H'310D H'9303 H'0B49 Event Explanation: ER ROR REPORTED BY PROCEDURE FLERROR HIGH LEVEL DESCRIPTION: After release of GPRS call, some data are not cleared (OUTGOINGSUBMUP). During subsequent setup of hal f-rate call (on the same individual as previous GPRS call) if link break or link fault takes place some random action can be made by the system and finally half -rate call is not setup. DETAILED DESCRIPTION: When signal RTSZABISCON enters bl ock RTODCON (in state ACTIVELOOP H'3) to seizeEVEN half-rate (USER2) ODCI indivi dual, it marks USER2 as activeACTIVEUSERS(USER2) = ZINUSE). Next seizing of subr ate connection is made. Whenloop connection is 64K type signal BRELA is send to release existing 64K loopconnection and state is changed to RELLOOPSETUPTRAF (H' 4). As a confirmation ofrelease of 64k loop connection, GS is sending BRELAR sig nal to RTODCON. RTODCONchanges state to SETUPGSTRAF (H'6) and sends SRSELOPA to seize sub-rateconnection for USER2. RTTRINT informs RTODCON about loop release s endingRTRELABISLOOP and RTODCON is changing state to RELGSTRAFTOIDLE (H'A). OPED signalconfirm seizure of half-rate connection in the GS. After entrance of OPED ,RTODCON checks whether a 64K or sub-rate connection is to be released. But this is made only for USER1 even this user is not in use. THIS IS THE FAULT. The solu tion is to add additional check to find which user signal OPED refers to.For USE R1 existing functionality has to be preserved but for USER2 (EVEN HR)signal SRRE LA must be send. REMEDY: NOTE:This remedy is written for R10NAED. There are 2 di fferent release procedures below. REMEDY 1: CONDITIONS: ! RELEASE PROCEDURE TO R ELEASE THE HANGING RBLT24 device on the ABIS path ! ! Note that RBLT24 is used i n this procedure !! However, the procedure applies equally to RBLT3 ! !********* ************************************************!! CONDITIONS THAT MUST BE MET I N ORDER FOR THE RELEASE !! PROCEDURE TO BE APPLIED. !!************************** *******************************! ! 1. Print the ABIS path for the TG which has a n RXOTS with TS sync fault!RXAPP:MO=RXOTG-x; ! 2. Verify that there is a 64K (or 16K) RBLT24 device which is in APSTATE=IDLE ! RADIO X-CEIVER ADMINISTRATIONABIS PATH STATUSMORXOTG-155DEV DCP APUSAGE APSTATE 64K TEIRBLT24-3720 1 UNCONC SPEEC H/DATA YESRBLT24-3721 2 UNCONC SPEECH/DATA YESRBLT24-3722 3 UNCONC SPEECH/DATA Y ESRBLT24-3723 4 UNDEF IDLE YESRBLT243724 5 UNCONC SPEECH/DATA YESRBLT24-3725 6 U NCONC SPEECH/DATA YESRBLT24-3726 7 UNCONC SPEECH/DATA YESRBLT24-3727 8 UNCONC SP EECH/DATA YESRBLT24-3728 9 UNCONC SPEECH/DATA YESRBLT24-3729 10 UNCONC SPEECH/DA TA YESRBLT24-3730 11 UNCONC SPEECH/DATA YESRBLT24-3731 12 UNCONC SPEECH/DATA YES RBLT24-3732 13 CONC TRXC SIGNAL NO 0 9RBLT24-3733 14 UNDEF IDLE NORBLT24-3734 15 MPLEX32 IDLE NO MPLEX16 SPEECH/DATA NO MPLEX16 SPEECH/DATA NO::END ! 3. Print t he call path for the RBLT24 device which is not configured! RAPTI:DEV=RBLT24-x; ! ie. x=RBLT24-3723 ! ! For 16K, use RAPTI:DEV=RBLT24-x,SDEV=y; with y=0 to 7 ! ! 4. Verify from the result printout that the only indviduals seized !! are RBLT 24, RTTRINT, RXCDI, RTODCON, and RTVPH ! CALL PATH TRACING IN BSC/TRCLINK MUP SM UP MUP SMUP MISCBRANCH-

1RBLT24-3723 RTTRINT-6927RXCDI-8814BRANCH-2RTTRINT6927RTODCON-3090BRANCH-3RTTRIN T-6927RTVPH-14030END Take note of the pointer for block RTODCON, this will be re ferencedas ODCIPTR (ie. ODCIPTR=3090) ! 5. Print the following variables from th e block RTODCON ! PRINT VAR RTODCON ODCIPTR:3(0); ! ODCIPTR:ACTIVEUSERS(0)=0=ZNO TINUSE !PRINT VAR RTODCON ODCIPTR:3(1); ! ODCIPTR:ACTIVEUSERS(1)=1=ZINUSE ! VARI ABLE ACTIVEUSERS 253. ! THIS IS A 1-D, 2-ELEMENT ARRAY. THE FIRST ELEMENT, USER1 , CORRESPONDS TO ! 254. ! EITHER A FULL-RATE OR AN ODD HALF-RATE USER. THE SECON D ELEMENT, USER2, ! 255. ! CORRESPONDS TO AN EVEN HALF-RATE USER. THESE ELEMENTS CAN HOLD A VALUE OF ! 256. ! ZERO OR ONE. A ONE INDICATES THAT THE USER IS ACTI VE AND CANNOT BE ! 257. ! SEIZED AGAIN AND A ZERO INDICATES THAT THE USER IS AVA ILABLE AND CAN BE ! 258. ! SEIZED. NOTE THAT WHEN WORKING WITH USER1, A SEPARATE VARIABLE IS NEEDED ! 259. ! SO THAT IT IS POSSIBLE TO DISTINGUISH BETWEEN THE F ULL-RATE AND THE ! 260. ! ODD-HALF RATE CASE. THIS IS WHY THE VARIABLE 'CONNECTI ONTYPE' IS USED. ! ! In this case, USER1 (0) is not in-use and USER2 (1) is in-u se. !! However, it can be the other way around. ! PRINT VAR RTODCON ODCIPTR:25; ! ODCIPTR:FLCONNFIDUSER1=H'0000 H'0000!PRINT VAR RTODCON ODCIPTR:26; ! ODCIPTR:F LCONNFIDUSER2=FID_PTR ! ! In this case, variable 25 is 0, and variable 26 is a v alid FID. !! This is because USER2 is in-use !! If USER1 was in-use, variable 25 would be a valid FID, and variable 26 would be 0 ! ! 6. Print the forlopp indiv iduals connected to the FID ! SYFIP:FID=fid_ptr; ! 7. Verify that the following blocks are connected to the forlopp !! You will notice that the forlopp id is PA SSIVE and the status for !! the individuals are ACTIVE. ! INDIVIDUALS CONNECTED TO FORLOPPSEARCHYESFORLOPP-ID STATUS FLPROTYPE DATE TIMEH'0001 3F9C PASSIVE H'00 00 0008 040304 0015BLOCK FILENUMBER INDIVIDUAL STATUS FID-VARRTODCON H'0001 H'00 00 1378 ACTIVE2 H'0019RTODCON H'0001 H'0000 0C12 ACTIVE2 H'001ARMCHO H'0001 H'00 00 14D9 ACTIVE2 H'0024RMHTR H'0001 H'0000 14D9 ACTIVE2 H'0016SRSTRAF H'0002 H'00 00 1A34 ACTIVE2 H'001CRTTPR H'0001 H'0000 00FA ACTIVE2 H'001FRTTPH H'0003 H'0000 14D3 ACTIVE2 H'0001RTTPH H'0003 H'0000 0A95 ACTIVE2 H'0001RABDIAN H'0004 H'0000 0252 ACTIVE2 H'0037RMHAIDL H'0001 H'0000 14D9 ACTIVE2 H'0037RALT24 H'0001 H'000 0 0BE3 ACTIVE2 H'002FRMHAIUL H'0001 H'0000 14D9 ACTIVE2 H'0026RMHOAC H'0001 H'00 00 14D9 ACTIVE2 H'0029GS H'0003 H'0000 3B5D ACTIVE2 H'0087GS H'0003 H'0000 3ABD ACTIVE2 H'0087RMHBI H'0001 H'0000 3B10 ACTIVE2 H'002DRMHBI H'0001 H'0000 000A AC TIVE2 H'002DRMHBI H'0002 H'0000 14D9 ACTIVE2 H'002ERMCC H'0001 H'0000 14D9 ACTIV E2 H'001CEND! 8. Print the following variables in block RTODCON ! PRINT VAR RTOD CON ODCIPTR:40; ! ODCIPTR:CONNECTIONTYPE=1=ZHALFRATE !! This variable can also b e 0=ZFULLRATE ! PRINT VAR RTODCON ODCIPTR:39(1); ! ODCIPTR:SZUSERREF(1)=H'6A03=R MHTR !PRINT VAR RTODCON ODCIPTR:38(1); ! ODCIPTR:USERIND(1) = RMHTR_PTR ! ! MUST BE THE RMHTR INDIVIDUAL IN THE! ! PRINTOUT RECEIVED IN STEP 7. !! Variables 39 and 38 are printed for the active index which is 1 in this case !! However, it c ould be 0 depending on the result of step 5 ! PRINT VAR RTODCON ODCIPTR:36; ! OD CIPTR:STATE=H'C=TGFORLOPPREL ! NOTE: If the above conditions do not match then d o not proceed with therelease procedure. IF IN DOUBT, PLEASE CONSULT WITH SECOND -LINE BEFORE PERFORMING THE PROCEDURE. PROCEDURE: ! **************************** *****************************!! START OF RELEASE PROCEDURE !!******************* **************************************! ! 9. Print the variable SENDRTRELABISCON R in block RTODCON !! The value for indices 0 and 1 for this variable MUST be 0. ! PRINT VAR RTODCON ODCIPTR:43(0); ! ODCIPTR:SENDRTRELABISCONR=0=ZNO ! ! ODCIPT R:SENDRTRELABISCONR=1=ZYES ! PRINT VAR RTODCON ODCIPTR:43(1); ! ODCIPTR:SENDRTRE LABISCONR=0=ZNO ! ! ODCIPTR:SENDRTRELABISCONR=1=ZYES ! If the value received is 1 then this value needs to be set to 0. SET VAR RTODCON ODCIPTR:43(0)=0;PRINT VA R RTODCON ODCIPTR:43(0); ! ODCIPTR:SENDRTRELABISCONR=0=ZNO ! SET VAR RTODCON ODC IPTR:43(1)=0;PRINT VAR RTODCON ODCIPTR:43(1); ! ODCIPTR:SENDRTRELABISCONR=0=ZNO ! !10. Print the following variables in block RTODCON to determine the !! data t o be sent in the send signal SRRELA. ! PRINT VAR RTODCON ODCIPTR:1; ! ODCIPTR:AB ISMUP !PRINT VAR RBLT24 x:H'2A; ! GSINL !The above 2 printouts should produce th e same result. Do not continue if there is a mismatch.PRINT VAR RTODCON ODCIPTR: 2; ! ODCIPTR:ABISSUBMUP ! !11. Use the following data in the send signal SRRELA ! D1 = ODCIPTR:ABISMUPD2 = ODCIPTR:ABISSUBMUPD3 = H'C203 (RTODCON BLOCK REFERENC E = COWNREF = (BAN=5)D4 = ODCIPTR + 50000 (Add 50000 only in the case of an even half-rate user USER2) SEND SIG SRRELA REF COX VIA JBB WITH D1,D2,D3,D4; !12. Ve

rify that no events have been received. ! SYRIP:SURVEY; !13. Print the forlopp i ndividuals connected to the forlopp id as in !! step 6. ! SYFIP:FID=fid_ptr; !14 . Print the state for the RBLT24 device. ! STDEP:DEV=RBLT24-x;DEVICE STATE DETAI LSDEV SUBDEV STATE BLS ADM ABS CONFIGRBLT24-x IDLE H'00 PEND !15. Print the call path for the RBLT24 device using command RAPTI ! RAPTI:DEV=RBLT24-x; CALL PATH TRACING IN BSC/TRCLINK MUP SMUP MUP SMUP MISCBRANCH-1RBLT24-x IDLEEND !16. Print the configuration data for the TG. !

RXCDP:MO=RXOTG-y; !17. Manually block and deblock the time slots (RXOTS) where t he !! parameter RESULT=BLOCKED from the printout received in step 16. ! RXBLI:MO =RXOTS-y-zx;RXBLE:MO=RXOTS-y-z-x; !18. After about 5 minutes, the RXOTS should b e in service. Verify that!! all the time slots in the TG are configured. ! RXCDP :MO=RXOTG-y;!*********************************************************!! END OF RELEASE PROCEDURE 1 !! ********************************************************* ! REMEDY 2: CONDITIONS: ! RELEASE PROCEDURE TO REMOVE TS SYNC FAULTS ON TIME SLO TS ! ! APPLICABLE ONLY FOR AXE810 ! ! ****************************************** ***************!! CONDITIONS THAT MUST BE MET IN ORDER FOR THE RELEASE !! PROCED URE TO BE APPLIED. !! *********************************************************! ! 1. Initiate the following trace measure to verify if there are;! any hanging MUPs. The trace measure includes an instruction;! which is only valid if the enh anced test system feature is ;! loaded. TELMP;TELMI:LOAD=75,TI=50;TEST SYSTEM;ON IN DO:FOR 30 TIMES,P MS, P SWD, PRINT VAR RTODCON PR0:1,;ON IN RTODCON GSFAULT; INIT; ! 2. If no GSFAULT signals are received in block RTODCON then there are;! no hanging MUPS and the release procedure is not valid. If the ;! signal GSFAULT is received then continue with the release procedure; ie. ON INSIG3956303 RTODC ON BUFSIG LSN=H'005 GSFAULT ON THL FROM CH WITH H'00 19E9 H'0001 RTODCON VAR H'0 0 19E9:H'001=H'0000 H'6970 ! ABISMUP=H'6970 !PROCEDURE: !*********************** **********************************!! START OF RELEASE PROCEDURE !! ************* ********************************************! NOTE: The following release proced ure is to be applied for each different ABISMUP received in STEP 2. ! 3. Release the MUP in block CH. ; SEND SIG CMRELA REF CH VIA JBB WITH ABISMUP; ! 4. Verify no events have been received.; SYRIP:SURVEY;! ********************************* ************************!! END OF RELEASE PROCEDURE 2 !!************************ *********************************! SOLUTION: CONDITIONS: PROCEDURE:This problem is solved with the approved corrections MNAAH-3805 and MNAAH-3804 in block RTODC ON. These ACs are available in EC-A 38 and EC-40 for R10NAED. The latest solutio n to this problem is solved with the approved correction MNAAH-4026 in block RTO DCON. This AC is avaiable in R10MD AC-A 4 and R10MD CNA-1 AC-A 2. ABIS PATH UNAVAIL TS SYNC FAULT WITH LAPD MPLEX16 Usage Count: 5 62% Network: GSM Node: AXE BSC R8.1 Node: BTS LAPD Multiplexing 16 Alarm: ABIS PATH UNAVAIL The LAPD signaling channel on the ABIS is per TRU!! Hence the mismatch. SOLUTION: CONDITIONS:As per dimensioning guidelines we should not use cells havi ng more that 2 TRU's. Moreover when we have 4 PCM timeslots for 2 TRUs which see ms sufficient. However when we map these to PCM TS we need to acknowledge that e very TRU needs a 16 kbps TS for LAPD signaling(MPLEX16) so when there is mapping from air interface timeslots to abis interface timeslots we have the following. . 1. In this case we are considering a combined cell(i.e. BCCH+SDCCH/8) 2. We ha ve one 16Kbps TS for Lapd signaling for each TRU Mapping AIR INTERFACE TS0 TS7 T RU0 TCH TRU1 TCH BCCH +SDCCH TCH TS1 TCH TCH TS2 TCH TCH TS3 TCH TCH TS4 TCH TCH TS5 TCH TCH TS6 TCH TCH Total TCH=15 Mapping ABIS Interface 16K PCM TS n PCM TS n+1 LAPD TCH 16K 16K 16K TCH TCH TCH TCH TCH TCH

PCM TS n+2 PCM TS n+3 LAPD TCH TCH TCH TCH TCH TCH TCH Total TCH available=14!! You can see that for a COMB cell with 2 TRU we will nee d 2.125 PCM TS.. PROCEDURE:Dimension the PCM Timeslots considering that there wi ll be another PCM timeslot required. Alarm: ABIS PATH UNAVAILABLE Usage Count: 1 55 60% Network: GSM Node: AXE BSC Node: AXE BSC 06A Alarm: ABIS PATH UNAVAILABLE Comman d RXCDP returns RXOTS in SELECT Command RXLTI returns TEST SUCCESSFUL Configurat ion change EDGE was turned on This is not a software fault. In some circumstance s the fault has been investigated as a dimensioning of the ABIS path. Please see the suggested solution for relevant procedure. SOLUTION-1: Increase DT int he B SC for ABIS path. SOLUTION-2: Not enough resources to bring the TS's in service. SOLUTION-3: Increase number of NUMREQEGPRSBPC. SOLUTION-4: There is not enough ABIS devices (RBLT) to support after the Edge installation when site uses cascad ed T1. SOLUTION-5: There are defined 4 EGPRS channels in each cell for TG-x what means having 12 channels defined as 64k channels and customer has defined 13 ch annels. The first 12 channels are consecutive (DCP 1 to 12) but the 13TH channel is defined between 2 channels defined as MPLEX16 SPEECH/DATA and with DCP 15. T his is the cause. SOLUTION-1: CONDITIONS: 1. Alarm: ABIS PATH UNAVAILABLE. 2. RX CDP shows RXOTS in SELECT state. 3. Command RXLTI gives result TEST SUCCESSFUL. PROCEDURE: 1. Verify Abis size: RXAPP:MO=RXOTG-xx; eg: <rxapp:mo=rxotg-67; RADIO X-CEIVER ADMINISTRATION ABIS PATH STATUS MO RXOTG-67 DEV RBLT2-2145 DCP 1 APUSA GE UNCONC APSTATE CF/TRXC SIGNAL 64K NO TEI 62 11

RBLT2-2146 RBLT2-2147 2 3 RBLT2-2148 4 RBLT2-2149 RBLT2-2150 RBLT2-2151 RBLT2-2152 RBLT2-2153 RBLT2-2154 5 6 7 8 9 10 RBLT2-2155 11 RBLT2-2156 12 RBLT2-2157 13 RBLT2-2158 14 RBLT2-2159 15 RBLT2-2160 16 RBLT2-2161 17 RBLT2-2162 18 RBLT2-2163 RBLT2-2164 RBLT2-2165 RBLT2-2166 RBLT2-2167 RBLT2-2168 RBLT2-2169 RBL T2-2170 RBLT2-2171 RBLT2-2172 RBLT2-2173 RBLT2-2174 RBLT2-2175 END 19 20 21 22 23 24 25 26 27 28 29 30 31 UNCONC MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UNCONC UN CONC UNCONC CONC UNCONC MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UNDEF UN DEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNCONC UNCONC UNCONC UNDEF UNCONC TRXC SIGNAL SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D

ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEE CH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA IDLE TRXC SIGNAL NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO YES YES YE S YES YES YES YES YES YES YES YES YES NO 10 5 1 0 4 9 8 2. Calculate the number of resources in Abis to TS allocation, excluding signali ng and EDGE: Total number of RBLT2 - Number of RBLT2 used for signaling - Number of RBLT2 used for 64K eg:

31 RBLT2 - 8 RBLT2 (signaling for 8 TRX) - 12 RBLT2 (64K YES) = 11 3. Each RBLT2 left provides 4 TS: eg: 11 * 4 = 44 4. Calculate the number of RXOTS for SPEECH /DATA, excluding EDGE: (Number of TRX * 8) - Number of RXOTS used for signaling - Number of RXOTS reserved for EDGE eg: <rxcdp:mo=rxotg-67; RADIO X-CEIVER ADMIN ISTRATION MANAGED OBJECT CONFIGURATION DATA MO RXOTS-67-0-0 RXOTS-67-0-1 RXOTS-6 7-0-2 RXOTS-67-0-3 RXOTS-67-0-4 RXOTS-67-0-5 RXOTS-67-0-6 RXOTS-67-0-7 RXOTS-671-0 RXOTS-67-1-1 RXOTS-67-1-2 RXOTS-67-1-3 RXOTS-67-1-4 RXOTS-67-1-5 RXOTS-67-16 RXOTS-67-1-7 RXOTS-67-4-0 RXOTS-67-4-1 RXOTS-67-4-2 RXOTS-67-4-3 RXOTS-67-4-4 RXOTS-67-4-5 RXOTS-67-4-6 RXOTS-67-4-7 RXOTS-67-5-0 RXOTS-67-5-1 RXOTS-67-5-2 RX OTS-67-5-3 RXOTS-67-5-4 RXOTS-67-5-5 RXOTS-67-5-6 RXOTS-67-5-7 RXOTS-67-8-0 RXOT S-67-8-1 RXOTS-67-8-2 RXOTS-67-8-3 RXOTS-67-8-4 RXOTS-67-8-5 RXOTS-67-8-6 RXOTS67-8-7 RXOTS-67-9-0 RXOTS-67-9-1 RXOTS-67-9-2 RXOTS-67-9-3 RXOTS-67-9-4 RXOTS-67 -9-5 RXOTS-67-9-6 RXOTS-67-9-7 RXOTS-67-10-0 RXOTS-67-10-1 RXOTS-67-10-2 RXOTS-6 7-10-3 RXOTS-67-10-4 RXOTS-67-10-5 RXOTS-67-10-6 RXOTS-67-10-7 RESULT CONFIG CON FIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CO NFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFI G CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG S ELECT CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG ARFCN 149 149 149 149 HOP 149 149 HOP 149 149 HOP HOP HOP HOP HOP HOP 129 129 129 129 129 129 HOP HOP 129 129 HOP HOP HOP HOP HOP HOP 145 145 145 145 145 HOP 145 HOP HOP HOP HOP HOP HOP HOP HOP HOP HOP HOP HOP HOP HOP HOP HOP TXAD 0 0 0 0 7 0 0 7 0 0 7 7 7 7 7 7 1 1 1 1 1 1 6 6 1 1 6 6 6 6 6 6 2 2 2 2 2 5 2 5 4 4 4 4 4 4 4 3 3 3 3 3 3 3 3 TN 4 5 6 7 0 3 2 1 0 1 2 3 4 5 6 7 4 5 6 7 2 3 0 1 0 1 2 3 4 5 6 7 5 6 7 4 2 0 3 1 0 1 2 3 4 5 6 0 1 2 3 4 5 6 7 BPC 13313 13312 13311 13310 12463 13308 9310 13306 13315 13314 13305 13304 13303 13302 13301 13300 10516 10515 10514 10513 1 656 10505 10479 10478 10526 10523 10476 10475 10474 10473 10472 10471 1554 1553 1552 1527 1129 13995 2035 1508 11304 11302 11301 11300 11299 11298 11297 11986 1 1985 11984 11983 11982 11981 11980 11979 CHCOMB TCH TCH TCH TCH TCH TCH TCH TCH BCCH CBCH8 TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH BCCH CBCH8 TC H TCH TCH TCH TCH TCH TCH TCH TCH TCH SDCCH8 TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH OFFS 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 XRA NO N O NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO ICM ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON

RXOTS-67-11-0 RXOTS-67-11-1 RXOTS-67-11-2 RXOTS-67-11-3 RXOTS-67-11-4 RXOTS-67-1 1-5 RXOTS-67-11-6 RXOTS-67-11-7 CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG 145 145 HOP HOP HOP HOP HOP HOP 2 2 5 5 5 5 5 5 0 1 2 3 4 5 6 7 1568 1556 5454 5453 6833 5451 5450 5449 BCCH CBCH8 TCH TCH TCH TCH TCH TCH 0 0 0 0 0 0 0 0 NO NO NO NO NO NO NO NO ON ON ON ON ON ON ON ON Number of TRX => 8 Number of RXOTS for signaling => 7 <rlbdp:cell=GSMA1A; CELL C ONFIGURATION BPC DATA CELL GSMA1A CHGR 0 1 END NUMREQBPC SYSDEF 8 NUMREQEGPRSBPC 4 0 NUMREQCS3CS4BPC TN7BCCH EGPRS EACPREF <rlbdp:cell=GSMA1B; CELL CONFIGURATION BPC DATA CELL GSMA1B CHGR 0 1 END NUMREQB PC SYSDEF 8 NUMREQEGPRSBPC 4 0 NUMREQCS3CS4BPC TN7BCCH EGPRS EACPREF <rlbdp:cell=GSMA1C; CELL CONFIGURATION BPC DATA CELL GSMA1C CHGR 0 1 2 3 END NUM REQBPC SYSDEF 8 8 8 NUMREQEGPRSBPC 4 0 0 0 NUMREQCS3CS4BPC TN7BCCH EGPRS EACPREF Number of RXOTS reserved for EDGE => 12 (Number of TRX * 8) - Number of RXOTS us ed for signalling - Number of RXOTS reserved for EDGE (8 * 8) - 7 - 12 = 45 5. C omparing values from step 3 and step 4 lead to ABIS PATH UNAVAILABLE alarm. To c ease this alarm value from step 3 must be equal or greater then value from step 4. 6. Below are some alternatives concerning step 5: - Increase Abis path - Incr ease number of NUMREQEGPRSBPC - Decrease number of 64k resources in Abis - Incre ase number of RXOTS for signaling - Concentrate TRX signaling SOLUTION-2: CONDIT IONS: 1. Alarm: ABIS PATH UNAVAILABLE. PROCEDURE:

Not enough resources to bring the TS's in service. After using the LAPD concentr ation the problem has been fixed and the alarm has been ceased. SOLUTION-3: COND ITIONS: 1. EDGE Functionality activated. 2. Command RXAPP shows IDLE RBLT device with 64K=YES 3. RLBDP shows NUMREQEGPRSBPC = 0. 4. LMO 0840, Time Slots giving ABIS UNAVAILABLE. 5. Command RXCDP returns RXOTS in SELECT PROCEDURE: 1. End the GPRS service: RLGSE:CELL=; 2. Change the NUMREQEGPRSBPC from 0 to required numb er of TS for E-PBCH: RLBDC:CELL= ,NUMREQEGPRSBPC= ,CHGR= ; 3. Activate the GPRS service: RLGSI:CELL=; SOLUTION-4: CONDITIONS: 1. EDGE was turned on and the site went down with Alarm "ABIS PATH UNAVAILABLE". 2. Command RXAPP shows that only one RBLT24 is defined. 3. All Time slots out of service. 4. This site uses casca ded T1 means, using one T1, cascading the T1 from 1st Site to 2nd site via micro wave. PROCEDURE: Once removed the Edge configuration, the site recovered with th e RBLT24 resources. Edge takes up the resources. Add more RBLT device (ABIS devi ce ) towards the BTS. SOLUTION-5: CONDITIONS: 1. TS gets LMO 2800 with Paramente r NUMREQEGPRSBPC = 4 but it runs with NUMREQEGPRSBPC = 3 and in both cases there are more than enougth RBLT assigned to the TG. 2. Alarm: ABIS PATH UNAVAILABLE with NUMREQEGPRSBPC = 4. 3. Command RXMSP returns RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT STATUS, RXOTS LMO 2800. 4. Command RLBDP returns CELL CONFIGURATI ON BPC DATA, NUMREQEGPRSBPC 4. 5. Command RXAPP returns RADIO X-CEIVER ADMINISTR ATION ABIS PATH STATUS, shows more ABIS w/ 64K=YES than the necessary. 6. EGPRS is enable and there is one TS that goes ABIS PATH UNAVAILABLE but there are enou gh RBLT defined int he TG with 64k=YES. PROCEDURE: 1. Put the TG X out of servic e. RXBLI:MO=RXOTG-x,force,subord;

RXESE:MO=RXOTG-x,subord; 2. Undefine the RBLT defined with DCP 15 as a 64k chann el (or just try to block the corresponding device) RXAPE:MO=RXOTS-x-y-z,DCP=15; or BLODI:DEV=RBTLT-x; 3. Redefine parameter NUMREQEGPRSBPC to 4 tothe 3 cells re garding to TG-X. RLBDC:CELL=cell[,CHGR=chgr],NUMREQEGPRSBPC=4; 4. Try to put int o service the TG-X. Now the 3 cells should get 4 64k channels each one without a ny problem. RXESI:MO=RXOTG-x,subord; RXBLE:MO=RXOTG-x,subord; SOLUTION: CONDITIO NS: 1. Alarm: ABIS PATH UNAVAILABLE. 2. RXCDP shows RXOTS in SELECT state. 3. Co mmand RXLTI gives result TEST SUCCESSFUL. PROCEDURE: Please refer to OPI, BSC, C ell Configuration Data, Change. Link/ABIS path fail. Usage Count: 16 60% Network : GSM Node: AXE BSC R8.0 Node: RBS Model G12 (RBS2000 series) Link/ABIS path fail. Physical Loop Test on the transmission link at BTS show DIP is in wor king state (WO). DIP goes ABL when link is put into the DXU (command DTSTP). Com mand RXASP for MO RXOTG will show OML FAULT Radio X-Ceiver Administration Manage d Object Fault Information Radio X-Ceiver Administration Managed Object Fault Al arm Situations DXU (Distribution Switch Unit) faulty. SOLUTION: CONDITION: 1.Cur rent DXU is loaded with correct BTS Software. 2.Once the link is connected to th e DXU the DIP goes into state ABL 3.Loop the link just before connecting to the DXU, DIP is working. PROCEDURE: 1.Change the old DXU with another Unit DXU which is loaded with correct BTS Software version. 2.Install IDB for the replaced DXU 3.Load back the DXU and put RBS into operation Ensure that the replaced DXU is loaded with correct BTS Software version as the one defined in the BSC. ABIS PAT H FAULT Usage Count: 15 60% Network: GSM Node: AXE BSC ABIS PATH FAULT 1.CHECK THE NUMBER OF DEVICES ALLOCAT ED BY COMMAND-RXAPP:MO=RXOTG-XX; 2.ATTACH MORE DEVICES ACCORDING TO SIG(UNCON,CO N,MPLEX16) AND NUMBER OF TS UNCONFIGURED. RXAPI:MO=RXOTG-XX,DEV=RBLT-XX&&-XX,DCP =XX&&-XX;

EXDAI:DEV=RBLT-XX&&-XX; BLODE:DEV=RBLT-XX&&-XX; Site with Abis Optimization does not work Usage Count: 9 60% Network: GSM Node: AXE BSC 07B Software: AXE BSC 07B IP-A8 Site with Abis Optimi zation does not work Alarm: ABIS PATH FAULT "Network Busy" when initiating call Super Channel shows state WO The TG was working on other RBLT before with SCM Th e TG is working in TDM mode with the new RBLT RLCRP shows all cell resources ava ilable RBLT2 hanging Abis Optimization enabled Configuration change We have got a corruption for a specific super channel in the block RTPRH. The variable REQRB LTDEVFAULT is set to ZFAULT. When we configure the super channel the SCSTATE wil l be set to "2". CONFIGUREDFAULTY. Even though the prinout shows "WO" state. Thi s will cause the alarm ABIS PATH FAULT. If the variable REQRBLTDEVFAULT is set t o "0" for all devices everything works fine. The printout of the REQRBLTDEVFAULT when the TG had been changed back to TDM shows that the variable at the custome r exchange still had "ZFAULT". The problem can be broken down to these three 3 i ssues. 1. How did we got the corruption? 2. Why the corruption is not cleared in the Abis opt block. Even if we roll back to TDM. 3. Why the Super channel still reports WO state, even though it is not. Issue 1. This probably happened when t he customer changed the RBLT devices for this SC. They did some blocking that se t the old RBLT devices faulty in RTPRH. Then they change the SC configuration to have the new RBLT. But as this fault is not cleared correctly, the state of the OLD RBLT devices was still present for this SC. The variable REQRBLTDEVFAULT is set by the signal RTBLOCRESIND but then it never got cleared. Issue 2. This is a software fault. The REQRBLTDEVFAULT is not cleared at creation and change of t he super channel Issue 3. This is a software fault. When requesting the configur ation for the printout we send the signal RTREQSCDAT and then RTPRH does a check of the super channel fault. But there is not check of the variable SCSTATE. REM EDY: CONDITIONS: 1. Alarm: ABIS PATH FAULT 2. Printing SCSTATE variable in RTPRH shows "2". CONFIGUREDFAULTY. PRINT VAR RTPRH <SCIND>:H'FB; 3. The variable REQR BLTDEVFAULT is set to ZFAULT. PRINT VAR RTPRH <SCIND>:H'E0(0-); PROCEDURE: 1. Ad d the correction (shall be done before migration to SCM): pcorl:block=rtprh,ia=h '3abd,suid="6RAE/CAAZA 107 1417/NAS R4B01",ci=reqdevfault;

LCC AR0- 0; LHC IR/ W0- 32; FIRSI 224- AR1, AR0; end; pcori:block=rtprh,ia=h'3ab d; 2. Test to verify correct behaviour Test system; Telmi:load=80,ti=5; Get the pointer for the superchannel (x) Print var rtprh x:224(0-); ! REQRBLTDEVFAULT ! Print var rtprh x:226(0-); ! REQRBLTDEVSZ ! on var rtprh 251; ! SCSTATE ! on var rtprh 224; ! REQRBLTDEVFAULT ! on var do: p ia, p var,; init; Variable 224 shou ld be 0 -> NO FAULT Variable 226 should be 1 -> SEIZED Variable 251 should be 1 -> CONFIGURED 3. Create the Super Channel (RRSCI) 4. Initiate test calls 5. Remo ve the remedy correction pcore:block=rtprh,ia=h'3abd; pcorr:block=rtprh,ia=h'3ab d; End the teste system. End test; SOLUTION: CONDITIONS: 1. Alarm: ABIS PATH FAU LT 2. Printing SCSTATE variable in RTPRH shows "2". CONFIGUREDFAULTY. PRINT VAR RTPRH <SCIND>:H'FB; 3. The variable REQRBLTDEVFAULT is set to ZFAULT. PRINT VAR RTPRH <SCIND>:H'E0(0-); PROCEDURE: Load AC NWAER-0615. See TRs HJ88907 and HJ889 09. TS Sync Fault Usage Count: 7 60% Network: GSM Node: AXE BSC 07A Node: AXE RBS 2964 Hardware: AXE810 APZ 21233C So ftware Version:B4405R016H TS Sync Fault TS synchronization fault TS SYNCH FAULT alarms Intermittent TS SYNCH Fault BSC TS synchronization fault

TS SYNC faults are observed massive TS SYNC FAULT Reason for TS SYNC FAULT MANY TS SYNC FAULT ALARMS Command RXASP returns TS SYNCH FAULT on several RXOTSs High number of TS SYNC FAULTs TS take Sync Fault, LMO2000. BSC TS SYNCH FAULT ALARMS Alarm: TS SYNC FAULT BLO BLA LMO BTS CONF 0000 0000 2000 ENA ENA How to define DCP in RBS2964 cabinets for Two different E1's. Port defination In RXAPP using R XAPP command for 2 PCM's in Single Cabinet Cannot define E1's in subrack DCP mis match between command RABCI and command RXAPP RBLT2 device was missing in the ab is path device. Command RXAPP RXAPP command shows TRXs and CF signaling jumping from one DCP to another. E1 is distributed between two sites Master and Slave,E1 is coming to Master in A port and going out via B port.Another E1 is coming to master in C port and going via D port.Slave is taking E1 from Master at A port ( From Master's B) and C port(From Masters D). SOLUTION: CONDTIONS: 1. Master- sla ve cabinet configuration in RBS 2000.2. 2xE1's shared between 2 cabinets in casc aded mode. PROCEDURE: The correct mapping for DXU 31 Flemingo 2964 BTS (4 Ethern et Ports) is : ================================================================= === Port A C DCP values (range) 1 -31 -------Input Ports 287 - 317-----Input Por ts ==================================================================== The Distrib ution of DCP should be like this in Black and Blue: <rxapp:mo=rxotg-3; RADIO X-C EIVER ADMINISTRATION ABIS PATH STATUS MO RXOTG-3 DEV RBLT2-1057 RBLT2-1058 RBLT2 -1059 RBLT2-1060 RBLT2-1061 DCP 1 2 3 4 5 APUSAGE UNCONC UNCONC UNCONC UNCONC MP LEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 CONC CONC MPLEX16 MPLEX16 MPLEX32 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 APSTATE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA CF/TRXC SIGNAL TRXC SIGNAL SPEECH/DATA SPEECH/DATA IDLE SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA 64K YES YES YES YES NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO TEI RBLT2-1062 6 RBLT2-1063 RBLT2-1064 RBLT2-1065 RBLT2-1066 7 8 9 10 62 6 0 7 1 8 2 9 3 RBLT2-1067 11

RBLT2-1068 12 RBLT2-1069 13 RBLT2-1070 14 RBLT2-1071 15 RBLT2-1072 16 RBLT2-2529 287 RBLT2-2530 288 RBLT2-2531 RBLT2-2532 289 290 RBLT2-2533 291 RBLT2-2534 292 RBLT2-2535 293 RBLT2-2536 294 RBLT2-2537 295 RBLT2-2538 296 RBLT2-2539 RBLT2-2540 297 298

RBLT2-2541 299 RBLT2-2542 300 RBLT2-2543 301 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 CONC MPLEX16 MPL EX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPL EX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPL EX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UNDEF MPLEX16 MPLEX16 MPLEX 16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UNDEF SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEE CH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA TRXC SIGNAL SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEE CH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEE CH/DATA SPEECH/DATA SPEECH/DATA IDLE IDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA SP EECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DAT A SPEECH/DATA SPEECH/DATA IDLE NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO N O NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO 4 5 10 11

END <rxapp:mo=rxotg-103; RADIO X-CEIVER ADMINISTRATION ABIS PATH STATUS MO RXOTG -103 DEV RBLT2-1073 RBLT2-1074 RBLT2-1075 RBLT2-1076 RBLT2-1077 DCP 17 18 19 20 21 APUSAGE UNCONC UNCONC UNCONC UNCONC MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 M PLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 M PLEX16 MPLEX16 MPLEX16 MPLEX32 UNDEF UNDEF UNDEF UNDEF MPLEX16 MPLEX16 MPLEX16 M PLEX16 CONC CONC UNDEF UNDEF MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPL EX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UND EF UNDEF UNDEF UNDEF MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 APSTATE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/ DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPE ECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA IDLE IDLE IDLE IDLE IDLE IDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA C F/TRXC SIGNAL TRXC SIGNAL IDLE IDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEE CH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA IDLE IDLE ID LE IDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA 64K YES YES YES YES NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO TEI RBLT2-1078 22 RBLT2-1079 23 RBLT2-1080 24 RBLT2-1081 RBLT2-1082 RBLT2-1083 RBLT2-1084 RBLT2-1085 RBLT2-1086 25 26 27 28 29 30 RBLT2-1087 RBLT2-2544 RBLT2-2545 RBLT2-2546 RBLT2-2547 31 302 303 304 305 61 0 8 1 9 2 10 3 11 RBLT2-2548 306 RBLT2-2549 307 RBLT2-2550

308 RBLT2-2551 RBLT2-2552 RBLT2-2553 RBLT2-2554 RBLT2-2555 309 310 311 312 313 RBLT2-2556 314

RBLT2-2557 315 RBLT2-2558 316 RBLT2-2559 END 317 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UNDEF SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA IDLE NO NO NO NO NO NO NO NO NO NO NO NO The TF value must be like this: <rxmop:mo=rxotf-3; RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT DATA MO RXOTF-3 END <rxmop:mo=rxotf-103; RADIO X-CEIVER ADMINIST RATION MANAGED OBJECT DATA MO RXOTF-103 END TFMODE S SYNCSRC DEFAULT TFCOMPNEG 4 578 TFCOMPPOS FSOFFSET NO TFAUTO TFMODE M SYNCSRC TFCOMPNEG DEFAULT TFCOMPPOS FS OFFSET TFAUTO NO 1. Check the following things : 1. Check routine E1 sync / check if OK with 1xE1 individually in a cabinet2. Block slave TG - put ESB A -> A port and then Deblo ck It.3. ESB cable in place : Give proper TEI value for master and slave TEI=62, 61 ; Check rxmop:mo=rxotf-xx; in both cabinets {master(M) in Master cabinet And Slave(S) in slave cabinet}4 Ask for TFCOMP value from BTS team 5 PCM should be Cascaded in master cabinet and stand alone on slave cabinet in IDB6 Check TG3 = 1..16 287..301 in order ; TG103 = 17..31 302..317 in order7. Then try No ESB cab le and make both Cabinet as Stand Alone ; 62, 62 [IDB manipulation required]8. R eload IDB in master Cabinet. Command RLCRP showing few FR & its HR channels as B LOCK Usage Count: 5 60% Network: GSM Node: AXE BSC R9.1 Node: AXE BSC R10 Node: AXE BSC R11 Software: AX E BSC R9.1 MD Software: AXE BSC R10 MD Software: AXE BSC R11 MD Command RLCRP sh owing few FR & its HR channels as BLOCK Half Rate Channels not present in Comman d RLCRP Alarm: ABIS PATH UNAVAILABLE HALF RATE leading to time slot going in unu sed condition Activation of new function or service-Half rate Implementation Eno ugh Time slots have not been reserved for EDGE functionality SOLUTION: CONDITION S:The Following Conditions have been observed. 1) Command RLCRP shows as below

CELL N310173 CHGR 1 BCCH 1 BPC CBCH 1 SDCCH 7 NOOFTCH 14- 28 CHANNEL CHRATE SPV STATE ICMBAND CHBAND 64K 6095 TCH-5355 FR 1,2,3 IDLE 1 1800 N ONE TCH-18871 HR 1,3 IDLE 1 1800 TCH-18870 HR 1,3 IDLE 1 1800 6097 TCH-5357 FR 1 ,2,3 BLOCK 1 1800 NONE TCH-18875 HR 1,3 BLOCK 1 1800 TCH-18874 HR 1,3 BLOCK 1 18 00 6099 TCH-5359 FR 1,2,3 IDLE 1 1800 NONE TCH-18879 HR 1,3 IDLE 1 1800 TCH-1887 8 HR 1,3 IDLE 1 1800 6101 TCH-5361 FR 1,2,3 IDLE 2) Half rate support is active in BSC 3) Trapool for Half rate has been defined. 4) One 64k Time Slot has been reserved per cell for EDGE Functionality 5) Comma nd RLBDP shows NUMREQEGPRSBPC value equal to 2 in each cell PROCEDURE: 1) Dedica te one more 64k Time Slot for each cell RXAPI:MO=RXOTG-XX,DEV=RBLT-YY,DCP=ZZ,res 64k; OR 2) Decrease the value of parameter NUMREQEGPRSBPC by one RLBDC:CELL=CELL XXX,NUMREQEGPRSBPC=1; for all the three cells of the problematic site. by If the Half rate channels are not visible in Command RLCRP's printout even the H ALFRATESUPP parameter's value is ZERO then halt and reactive the cells once.Then check again,It should be visible by now. Hanging RBLT2 device Usage Count: 4 60 % Network: GSM Node: AXE BSC R11 Hanging RBLT2 device RBLT2 device was missing in the abis path device. Command RXAPP Solution: Procedure: 1. set the dip to ABL s tate (i.e pullou the U link from the DDF from the corresponding RBLT2 2.Blocked the DIP. Command DTBLI 3.Blocked the the RBLT2 device. Command BLODI 4.de-blocke d the DIP. Command DTBLE 5. define the abis path . Command RXAPI 6.de-Blocked th e the RBLT2 device. Command BLODE

Alarm when changing Abis Allocation Usage Count: 3 60% Network: GSM Node: AXE BSC 07B Command RXMOP returns Abis Path Allocation method is FIXED Alarm: ABIS PATH UNAVAILABLE Command RXCDP returns RXOTS in SELECT Ins ufficient TX equipment in command RXCDP EDGE Functionality is activated Configur ation change Abis Path Allocation method was changed from FLEXIBLE to FIXED SOLU TION: CONDITIONS: 1. RXMOP shows Abis Allocation method is FIXED. 2. Alarm: ABIS PATH UNAVAILABLE. 3. RXCDP shows RXOTS in SELECT state / Insufficient TX equipm ent. 4. RXTCP shows EDGE Functionality is activated. 5. The Number of RXOTS rese rved for EDGE in RLBDP is 8. 6. RXAPP shows 4 RBLT devices with 64K=YES. PROCEDU RE: 1. Verify EDGE Functionality: RXTCP:MO=RXOTG-xx; RLGSP:CELL=xx; 2. Verify the Number of RXOTS reserved for EDG E: RLBDP:CELL=xx; 3. Verify the RBLT devices with 64K=YES: RXAPP:MO=RXOTG-xx; 4. Th e difference between the values in step 2 and step 3 lead to ABIS PATH UNAVAILAB LE alarm. To cease this alarm value from step 3 must be equal or greater than th e value from step 2. 5. Increase the number of 64k resources in Abis Please, fol low OPI, Radio X-ceiver Administration, Abis Path Data, Change. Problem with feature Abis Optimization Usage Count: 3 60% Network: GSM Node: AXE BSC 07B Problem with feature Abis Optimization Alarm: Abi s Path Unavailable RXAPP shows not connected RTPGD devices Abis Optimization act ivation In the TDM mode the Abis Path will be connected to other physical E1s to the BTS. But in SCM mode the Abis path will only be an internal path for intern al communication between the TRH and the PGW. And the physical configured PCM li nks will be used as a broadband connection.

When adding the Abis path for SCM transmission you need to have one 64K device f or each GPRS channel that handles CS-3/CS-4 or EDGE. Then you need to have one d evice per 4 Speech channels that you want to use. Plus you need to add one devic e per TRX used by the BTS. In the TDM configuration the customer was using CONC and MPLEX, to allocate 4 TRXCs to one device. With SCM each TRXC need to have it s own device for signaling. There is no need to optimize the internal device usa ge in the BSC. The PGW has enough devices for this. Abis Path in TDM mode, if yo u use CONC and MPLEX, you will have 4 TRXC perdevice. RBLT-1058 RBLT-1059 RBLT-1 064 2 3 8 CONC CONC CONC TRXC SIGNAL CF/TRXC SIGNAL TRXC SIGNAL NO NO NO 0 62 1 6 2 8 4 9 5 10 But after migration to SCM, each TRXC shall have one device each. We do not have optimization of internal signaling. RTPGD-5335 RTPGD-5336 RTPGD-5337 RTPGD-5338 RTPGD-5339 RTPGD-5340 RTPGD-5341 RTPGD-5342 RTPGD-5343 0 0 0 0 0 0 0 0 0 SCCONC SCCONC SCCONC SCCONC SCCONC SCCONC SCCONC SCCONC SCCONC TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL CF/TRXC SIGNAL NO NO NO NO NO NO NO NO NO 0 1 2 4 5 6 8 9 62 10 So when migrating from CONC to SCCONC you need to add more devices so each TRXC can have its own device. SOLUTION: CONDITIONS: 1. Migration from TDM to SCM 2. T he alarm "ABIS PATH UNAVAIL" is raised. PROCEDURE: 1. Add more Abis Path devices with the RXAPI command If 12 TRXes are used, we need to add 9 more device to ge t the same Abis path as in TDM mode If 9 TRXes are used, we need to add 6 more d evices to get the same Abis path as in TDM mode. RXAPI:MO=RXOTG-XX,NUMDEV=old+9; RXAPI:MO=RXOTG-XX,NUMDEV=old+6; RXAPI:MO=RXOTG-XX,NUMDEV=old,RES64K; !12TRXes! !9TRXes! Two TRs has been written on the CPI HK83535 RXAPI format two for SCM mode does n ot contain option RES64K HK83539 There is no explanation on how to add Abis Path when migrating from TDM to SCM BTS Power Saving active Usage Count: 3 60% Network: GSM Node: AXE BSC 08A BTS Power Saving active The reactivated TRUs stay in Config for a short period Problem not occure if no traffic on cell

Alarm: ABIS PATH UNAVAILABLE RXOTS OPER w/ LMO 0840 UNCONF Command RXMSP on TS's shows STATE OPER, BLO 0000, BLA 0000, LMO 0840, BTS DIS, CONF UNCONF RXOTS OPER with BLO=0000 BLA=0000 LMO=0840 BTS=DIS CONF=UNCONF SOLUTION: CONDITIONS: - BTS power saving active - frequent ABIS PATH UNAVAILABLE alarm for a short period one or more RXOTS stay in config fter reactivation PROCEDURE: This behaviour ca n be considered as normal behaviour. When the TRX is woken up it reservs a 16k d evices from the ABIS pool for communication. In case there is no enough 16k devi ce available the RXOTX devices will stay in select and A-bis path unavailable al arm will raise until the devices is succesfuly ceased. During the STP tests we c ould not reproduce the fault because there was not traffic so enough 16k devs we re available. This behaviour can be avoided by adding new 16 devices to the ABIS pool. Normal behaviour RBS 2000 not operational, CF noop, TRX noop, Abis Path d own Usage Count: 2 Network: GSM Node: AXE BSC R07B RBS does not carry traffic RP fault alarm is present STDEP command shows STATE=BLOC Abis Path unavailable Rxm sp printout of Cf shows noop. RP Fault, HW Fault SOLUTION: CONDITIONS: PROCEDURE : Repair RP Fault 60% Problem in ABis path over Satellite Usage Count: 2 60% Network: GSM Node: AXE BSC Problem in ABis path over Satellite Not able to defin e Abis interface using satellite To start this functionality, the parameter SATE LLITSUPPORT must be allowed in the data base table. SOLUTION: Condition: - No sp ecific condition. Procedure: DBTRI; DBTSC:TAB=AXEPARS,NAME=SATELLITSUPPORT,VALUE =1; DBTRE:COM; the software loading will take about 2 to 3 hours Mismatch in Def ined and available NUMREQEGPRSBPC Usage Count: 1 60%

Network: GSM Node: AXE BSC/TRC 08A Node: AXE BSC 08A Software: AXE BSC 08A CP-A2 Not possible to reserve 56 64K EGPRS in Abis path 60 RBLT2 device. 04 RBLT2 for CF and TRX signaling in Abis path and rest 56 for 64K EGPRS. 8TRX=64 TS in Air interface 06 or more RBLT2 shows UNDEF IDLE Fixed Abis and baseband hopping is u sed RXASP returns Abis path unavailable Parameter TN7BCCH set to EDGE CSPSALLOC set to CSNOPRFPSLAST Configuration mismatch found between abis and air interface . SOLUTION: CONDITIONS: 1. 2. 3. 4. 8 E-TRX is used. 60 RBLT2 devices in Abis path baseband hopping is used 04 RBLT2 devices for CONC CF/TRX signaling 5. Problematic cell is khfbg2b and 2 channel group under that cell.TG-151 is use d for CHGR 0 GSM 900. TG-79 is for CHGR 1 GSM 1800. And we want to reserve 56 64 K under BAND 900 CHGR 0. 6. All other configuration is OK. PROCEDURE: Configure one non hopping CHGR 0 with 1 TRX and configure BCCH/SDCCH8 in that CH GR. And configure another Baseband hopping CHGR 1 with 7 TRX to make 56 64K for EDGE. Details procedure is below: Block the TG. RXBLI:MO=RXOTG-151,SUBORD,FORCE; Create another channel group unde r cell khfbg2b GSM 900. RLDGI:CELL=KHFBG2B,CHGR=1,SCTYPE=UL; RXTCI:MO=RXOTG-151, CELL=KHFBG2B,CHGR=1; 3. Assign frequency for CHGR 1 and Delete frequency from CH GR 0 without BCCH frequency.. RLCFI: CELL=KHFBG2B,DCHNO=102&106&110&115&117&119& 122,CHGR=1; RLCFE:CELL=KHFBG2B,DCHNO=102&106&110&115&117&119&122,CHGR=0; Reserve NUMREQEGPRSBPC =56 for cell khfbg2b in CHGR 1 and delete it from CHGR 0. RLBDC:CELL=KHFBG2B,CHGR=1,NUMREQEGPRSBPC=56; RLBDC:CELL=KHFBG2B,CHGR=0,NUMREQEG PRSBPC=0;

5. Push the SDCCH in CHGR 0 by RLCCC. 6. Hopping OFF in CHGR 0 and ON in CHGR 1. RLCHC:CELL=KHFBG2B,CHGR=0,HOP=OFF; RLCHC :CELL=KHFBG2B,CHGR=1,HOP=ON; 7. Activate the cell and deblock the TG. RLSTC:CELL=KHFBG2B,CHGR=1,STATE=ACTIVE; RX BLE:MO=RXOTRX-151-5,SUBORD; So, current configuration is 8TRX=64 TS in Air interface. 64-8=56 TS for EDGE. N o, TS in select mode and no alarm. In Abis path, 60 RBLT2 device. 04 RBLT2 for C F and TRX signaling. 56 for EDGE (DCP 287 to 315=29 and DCP 4 to 31 except 24=27 ). No RBLT2 is UNDEF IDLE. 1. Possible 2. Possible Total E-TRX But total 06 returns ABIS to configure for both Baseband and Synthesized hopping. to push SDCCH both in CH GR 0 and CHGR1. is 8.Defined NUMREQEGPRSBPC is 56. In Abis we define 56 64K for EDGE. RBLT2 shows UNDEF IDLE and also total 06 TS is in SELECT mode. RXASP also PATH UNAVAIL for that 06 TS. In Abis path out of 60 RBLT2 devices. 04 RBLT2 is used for CF/TRX signalling. So , for EDGE/Voice Traffic, 56 No. of 64 K in Abis. BTSPS causes high number of ABIS PATH UNAVAILABLE alarm Usage Count: 1 60% Network: GSM Node: AXE BSC 07B Node: AXE RBS 2000 Feature: BTS Power Saving Feat ure: Flexible Abis BTSPS causes high number of ABIS PATH UNAVAILABLE alarm Alarm : ABIS PATH UNAVAILABLE References: TR HK97785 and HL27866 The high occurrence o f alarm ABIS PATH UNAVAILABLE is caused by a side effect of using BTS Power Savi ng feature in Flexible TGs. If the TRX is switched off its Abis paths are releas ed. Hence few idle Abis resources (16K/64K - depends on configuration) apper in the TG. However if there are another TRXs in the TG serving EGPRS channels, and the TG is in Flexible Abis, these idle resources can be seized by flexible CS ca lls. Flexible calls (S/D with 16K prefered) can seize also non-64K Abis resource s. In fact FLAB feature is designed in that way that it preserves 64K pool - so it is preferred to seize 16K paths on non-64K pool first - this avoids splitting 64K resources. That using of 16K paths by flex can cause a lack of available Ab is 16K resources to configure fixed paths for TSs when the TRX is switching on. The TAS subsystem orders seizing Abis S/D fixed path in ordinary way (RTTRAFSEIZ E in RTTRINT) for each TS and when there are no idle resources (already seized b y flexible paths) it raises mentioned alarm. Such not configured TS remained in state SELECT up to next seizure attempt. TAS usually repeats seizure attempts wh en reconfiguring BPC after 3 min timer. Then that path seizing may result succes sful if some idle 16K resources apper in the TG in the meantime (it migh depend on flexible traffic intensity). Also in RTS there are two attempts of reseizing paths which follow RTACM task flow, so the TS can be recovered even earlier. The re is also some timer (around 3 min) in TAS for alarm

ceassing.Feature BTS Power Saving makes visible and multiplies effects of that F LAB disadvantage because it can switch particular TRXs off/on dynamically during traffic ongoing on another TRXs in the TG. That problem causes also the same sy mptoms when blocking/deblocking TRXs manually.It is not possible to fix this pro blem by corrections. Changes on feature/function level are needed to fix it in S W.Possible workarounds are:expand Abis interface resources by adding redundant p aths- do not use BTS power saving for flexible sides which are handling EDGE res ources. REMEDY: CONDITIONS: 1. BTSPS feature is active on the cells 2. Sites are configured with flexible Abis 3. The Abis resources are tightly allocated, all non-64K devices are used up by TRX/CF signalling and non-flexible timeslots 4. H igh frequency of "ABIS PATH UNAVAIL" alarms, ceasing without manual interaction after cca. 3 minutes PROCEDURE: 1. The behaviour is the consequence of the flexi ble Abis feature used together with BTS PS. 2. Increase the number of non-64K Ab is devices connected to the site, either adding more RBLT devices or decreasing the size of the 64K pool. 3. Turn off BTS PS for the concerned flexible Abis sit es. The problem connected with BTS Power Saving and extremely many alarms ABIS PATH UNAVAIL needs deeply investigation by BG-RESP and System responsible person. It lo oks like that there is dissimilarity between the BTS PS scanning and the alarm p eriod raising. Some kind of interaction between these processes should be provid ed on system level and it is hard to provide any correction to eliminate such si tuation. TS LOOPTEST FAILED after BTS rehomed Usage Count: 1 60% Network: GSM Node: AXE BSC 07B Sites rehomed failing TS LOOPTEST FAILED after ac tivating cells after being rehomed Alarm: ABIS PATH UNAVAILABLE Alarm: TS LOOPTE ST FAILED DT error in defining Abis path (DCP range, should be "x&&yy" ) RXAPI:M O=RXOTG-161, DEV=RBLT2-5157&&-5183,DCP=5&31; This error causes the following fau lt: MISMATCH BETWEEN NUMBER OF ARGUMENTS. So at the end, the site does not have enough Abis Path devices and when the TG is put into service then we get the ala rm: ABIS PATH UNAVAILABLE and after that the TS LOOP TEST FAIL, which is normal due to the missing abis path devices. REMEDY: CONDITIONS: - BTS sites rehomed fr om one BSC to another. - Error in DT for creating Abis Path PROCEDURE: Fix DT fo r Abis path definition. (DCP=5&&31) Pointer too large in RXCCD caused by corruption of HG idle list Usage Count: 46 Network: GSM Product name: RXCCD Product ID: CAAZ 107 7129 R2A03 Node: AXE BSC R 8 58%

Node: AXE BSC R9 Node: AXE BSC R9.1 Node: AXE BSC R10 NAED Product ID: CAAZ 107 7129 R3A02 Event explanation: Pointer too large Event code: H'0008 H'00FE H'0D35 Application error in block RXCCD at IA=H'0D35 Forlopp error in block RXCCD at I A=H'0C31 Forlopp error in block RXCCD at IA=H'0D1E Event explanation: Too long e xecution on C-level Event code: H'1106 H'00FE H'0C31 Event code: H'0008 H'00FE H '0D1E In some cases the TG are down, cannot handle calls. A-bis path disapears i n same cases for TG that are down, RXAPP. HIGH LEVEL DESCRIPTION: This problem h as been occurring in R8, R9 and now R9.1 also. The Hopping Group idle list is co rrupted and causes pointer too large events to occur repeatedly. DETAILED DESCRI PTION: The FC8 occur since variable CNEXTIDLEHGPTR is corrupted. The reason for the corruption is not know. This problem as been occurring since R8. TRs have be en opened for this issue in R8 and R9. Some of the TR in R9 mention corrections that could solve this problem. They appear to have been systemized in R9.1 but t he problem is evidently still occurring. Some TRs and primus solution mention th at a restart will clear the corruption. Although that is one possibility a relea se procedure was performed successfully to clear the corruption. The procedure c leared the corruption and allowed the TG that where down to be recovered success fully without having to perform a restart. The release procedure is obviously pr eferable to performing a restart. The procedure is described below but it is hig hly recommended to contact second line support to perform the procedure since ch anges may have to be done to the procedure depending of certain printouts gather ed. Note also that the FC8 will increase the intensity counter (SYELP;) so the B SC must be monitored. If the intensity counter limit is reached the BSC will res tart. The approved correction MNAAH-3563 in R9.1MD AC-A 4 is found to be suspect ed faulty and a new TR was issued HD84931 in block RXCCD. REMEDY: If the same pr oblem or a similar one occurs, please open a new CSR and include the information requested below. For R8: TEST SYSTEM; PRINT VAR RXCCD 14; !CNEXTIDLEHGPTR! PRIN T VAR RXCCD 0-:35; !NEXTHG! PRINT VAR RXCCD 0-:57; !TGREF! END TEST; For R9: TES T SYSTEM; PRINT VAR RXCCD 14; !CNEXTIDLEHGPTR! PRINT VAR RXCCD 0-:35; !NEXTHG! P RINT VAR RXCCD 0-:57; !TGREF! END TEST; For R9.1MD: TEST SYSTEM; PRINT VAR RXCCD 16; !CNEXTIDLEHGPTR! PRINT VAR RXCCD 0-:37; !NEXTHG! PRINT VAR RXCCD 0-:57; !TG REF! END TEST; From these print outs examine the idle list and see if corruption is present. REMEDY: CONDITIONS:

PROCEDURE: 1-Gather the FC8 events with command SYRIP:EVENT=X,FORME=LARGE;Using the event printout find from the CONNECTED INDIVIDUALS section the INDIVIDUAL fo r block RCCGD with FILENUMBER equal to 2. There could be more thanone individual but the one with the smallest INDIVIDUAL is in fact the cellpointer.Example: In the following example the cell pointer is H'176.CONNECTED INDIVIDUALSBLOCK FILE NUMBER INDIVIDUAL STATUS:RCCGD H'0002 H'0000 03FB ACTIVE2RCCGD H'0002 H'0000 017 6 ACTIVE2 <----Cell pointer :2-Now that the cell in which the problem is occurri ng is known print the cellname.PRINT SV ROTRAN cellpointer:44; ! ICELLNAME!3-Now the cell name is known so find the TG.rxtcp:cell=cellname,moty=rxotg;4-Print th e TG. There are good chances that the TG is hanging and in a strangestate and no t taking any calls. RXMSP:MO=RXOTG-X,SUBORD;Print also the Abis path to the TG. It is possible that no Abis path appear.This is also a consequence of the corrup tion. The Abis path will reappear oncethe procedure is performed.RXAPP:MO=RXOTGX; 5-Blocking the TG will reduce the number of FC8 occurring in the BSC.RXBLI:MO =RXOTG-X,SUBORD,FORCE;Note that if FC8 still occurs the above steps need to be r epeated since there are chances that more than one TG is affected by the corrupt ion and they must befound so that they can be blocked also.6-Print the following variables. The printouts will help us see the corruption.PRINT VAR RXCCD 0-:37; !NEXTHG!PRINT VAR RXCCD 0-:57; !TGREF!Confirm where the end of the idle list is located. The end of the list is thepointer where NEXTHG is H'FFFF and where TGR EF is H'FFFF also. This should bepointer H'0. From there follow the idle list un til you find the first busy individual. Once that pointer is found call it Y. A set var of CNEXTIDLEHGPTR needs to be done.SET VAR RXCCD 16 = Y-1; !CNEXTIDLEHGP TR-1, ie. link to start of good idle list! ===================================== ========================================The following steps are not always requi red. It will depend on the extend of the corruption. The above set var on CNEXTI DLEHGPTR is most of the time the onlyset var required.7-Once the above set var i s done we want to remove from RXCMOO the link betweenthe TG and the HG such that when the TG is put back into service it will thinkthat it has no HG connected t o it.This means that when the TG is brought back into service the HG must be red efinedby using the necessary O&M commands.PRINT VAR RXCMOO X:288; The X is the T G number(s) found previously. There can be more than one.The value printed is th e Logical MO for the TG. Call it Z. It will be used for the set var in RXCMOO.PR INT VAR RXCMOO Z:59(9); This is the reference to the HG individual which we will clear it should be different than H'FFFF.SET VAR RXCMOO Z:59(9)=H'FFFF;Clear th e reference to the HG individual.Note that step 7 needs to be repeated if more t han one TG is found to be affected by the corruption.8-Once all the set vars are done the TG can be brought back into service by de-blocking them. SOLUTION: CON DITIONS: PROCEDURE: The approved correction href="http://vm.ericsson.se:10081/we bshare/chwww.*cgi?typ=P&cdata=MWAAH-3577">MWAAH-3577 in block RXCCD will solve t his problem. The correction is available in R10 NAED AC-A 3.The approved correct ion href="http://vm.ericsson.se:10081/webshare/chwww.*cgi?typ=P&cdata=MWAAH3618" >MWAAH-3618 in block RXCCD will solve this problem. The correction is available in R9.1MD AC-A 4.The approved correction href="http://vm.ericsson.se:10081/websh are/chwww.*cgi? typ=P&cdata=MWAAH-3579">MWAAH-3579 in block RXCCD will solve thi s problem. The correction is available in R9 with ECA 45.TR HD76146 is in design for R8. The TR in R8 also includes the information collected by trap correction HD39065. RXAPE fails with ABIS PATH IN USE Usage Count: 31 Network: GSM Node: AXE BSC R10 Node: AXE BSC R11 Software: AXE BSC R10 MD Software: AXE BSC R11 MD Software: A XE BSC R6B RXAPE fails with ABIS PATH IN USE ALL MO's are undefined except TG RE MEDY: Forlopp Release the TG CONDITIONS: 58% 1.RXAPE fails with ABIS PATH in USE 2.RBLT24 devices are MBL and NC 3. RAPTI on the RBLT24 device shows no data

PROCEDURE: 1. Get TG FID RXMOP:MO=RXOTG-xxx; 2. Print all connected individulas to this forlopp SYFIP:FID=H'xxx-h'xxxx; 3. Release the first active indivual. Pr obably going to be RTVPH in this case SYFRI:FID=,FILENUM=,IND=,BLOCK=; 4. Confir m RXAPE works RXAPE:MO=RXOTG-xxx,DCP=x; MNALS-0354 and MNALS-0355 are already lo aded TGs cannot be recovered by O&M Usage Count: 29 58% Network: GSM Node: AXE BSC R12 Software: AXE BSC R12 MD Product Name: RTODCON Pr oduct ID: CAAZ 107 6762 R5A03 Product Name: RGSERV Product ID: CAAZ 107 7863 R6A 01 Product Name: RTAPH Product ID: CAAZ 107 7700 R3B01 Product Name: RNLCT Produ ct ID: CAAZ 107 6781 R9B02 Product Name: RXCCL Product ID: CAAZ 107 7128 R4A03 M ultiple sites down Cell sites can not be recovered via O&M No ABIS path seized w hen taking RXOCF into service using C'RXESI Not able to recover a TG after relea sing it with the command SYFRI ALARM: RADIO X-CEIVER ADMINISTRATION MANAGED OBJE CT FAULT Alarm: MANAGED OBJECT FAULT, Slogan: FORLOPP RELEASE Event Code: H'4301 H'C203 H'2B5A Event Code: H'4300 H'9503 H'4873 Event Code: H'4301 H'2A03 H'2C7E Event Code: H'4301 H'2A03 H'2D9F Event Code: H'4300 H'2A03 H'28C7 Event Code: H '4300 H'3103 H'0AFF Event Code: H'4301 H'C203 H'1B40 Event Code: H'4301 H'2A03 H '26E0 Event Explanation: ERROR REPORTED BY PROCEDURE FLERROR Event Code: H'320D H'00FF H'00FF Event Explanation: TIMEOUT AT FORLOPP AUDIT,NO FLERROR IP-A 20 was loaded HIGH LEVEL DESCRIPTION: When an automatic TG forlopp release occurs for a TG that is using FLEXIBLE ABIS , the TG couldn't be recovered by normal O&M and was followed by the application errors in block RTAPH, RGSERV, RTODCON, and RNLCT. Any site that went out of se rvice couldn't be recovered as well. REMEDY: CONDITIONS:

1.Bring MO=RXOCF into service using command RXESI. RXESI:MO=RXOCF-x; -Expect RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT IN SERVICE RESULT MO RXOCF-x END ST ATE COM RESULT EXECUTED LOADRESULT BLOCKED FROM OML BSSREL 120 2.Manually deblock the MO=RXOCF using command RXBLE. RXBLE:MO=RXOCF-x; RADIO X-CEIVER ADMINISTRATION MANUAL DEBLOCKING OF MANAGED OBJECT COMMAND RESULT MO RXOCF-x STATE NOOP RESULT EXECUTED 3.Print the ABIS path for the TG using the command RXAPP and you will see no ABI S individual is seized for CF signaling. RXAPP:MO=RXOTG-x; RADIO X-CEIVER ADMINISTRATION ABIS PATH STATUS MO RXOTG-83 DEV RBLT3-1992 RBLT31993 RBLT3-1994 RBLT3-1995 RBLT3-1996 RBLT3-1997 RBLT3-1998 RBLT3-1999 RBLT3-200 0 RBLT3-2001 RBLT3-2002 RBLT3-2003 RBLT3-2004 RBLT3-2005 RBLT3-2006 RBLT3-2007 D CP 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 APUSAGE UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF APSTATE IDLE I DLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE 64K NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO TEI

RBLT3-2008 RBLT3-2009 RBLT3-2010 RBLT3-2011 RBLT3-2012 RBLT3-2013 RBLT3-2014 RBL T3-2015 END 17 18 19 20 21 22 23 24 UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF UNDEF IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE NO NO NO NO NO NO NO NO PROCEDURE: 1.Print the fxed filesize in the block RTACM which is based on ACMINDIVIDUALS-1 and is stored in variables BAN=76(4),76(6), and 76(7). PRINT VAR RTACM 76(4); PRINT VAR RTACM 76(6); PRINT VAR RTACM 76(7); ! = ! = ! = H'1F ! H'1F ! H'1F ! 2.Print the variable TASKP:STATE (BAN=54) in the block RTACM and all individuals from 0 to H'1F will be in TASKP:STATE=2=SELECTING. PRINT VAR RTACM 0-:54; -EXPECT VARIABLE ARRAY RTACM VAR H'036 H'000000:......)H'0002:H'0002:H'0002:H'0002:H'000 2:H'0002:H'0002:H'0002: H'000008:......)H'0002:H'0002:H'0002:H'0002:H'0002:H'000 2:H'0002:H'0002: H'000010:......)H'0002:H'0002:H'0002:H'0002:H'0002:H'0002:H'000 2:H'0002: H'000018:......)H'0002:H'0002:H'0002:H'0002:H'0002:H'0002:H'0002:H'000 2: H'000020:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'00 0028:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'000030:.. ....)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'000038:......)H' 0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'000040:......)H'0000:H' 0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'000048:......)H'0000:H'0000:H' 0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'000050:......)H'0000:H'0000:H'0000:H' 0000:H'0000:H'0000:H'0000:H'0000: H'000058:......)H'0000:H'0000:H'0000:H'0000:H' 0000:H'0000:H'0000:H'0000: H'000060:......)H'0000:H'0000:H'0000:H'0000:H'0000:H' 0000:H'0000:H'0000: H'000068:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H' 0000:H'0000: H'000070:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H' 0000: H'000078:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H '000080:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'000088 :......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'000090:...... )H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'000098:......)H'0000 :H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'0000A0:......)H'0000:H'0000 :H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'0000A8:......)H'0000:H'0000:H'0000 :H'0000:H'0000:H'0000:H'0000:H'0000: H'0000B0:......)H'0000:H'0000:H'0000:H'0000 :H'0000:H'0000:H'0000:H'0000: H'0000B8:......)H'0000:H'0000:H'0000:H'0000:H'0000 :H'0000:H'0000:H'0000: H'0000C0:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000 :H'0000:H'0000: H'0000C8:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000 :H'0000:

H'0000D0:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'0000D 8:......)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'0000E0:..... .)H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'0000E8:......)H'000 0:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'0000F0:......)H'0000:H'000 0:H'0000:H'0000:H'0000:H'0000:H'0000:H'0000: H'0000F8:......)H'0000:H'0000:H'000 0:H'0000:H'0000:H'0000:H'0000 END 3.Increase the number of TASKP individuals to 64. SET VAR RTACM 76(4)=63; SET VAR RTACM 76(6)=63; SET VAR RTACM 76(7)=63; 4.Print the number of TASKp individuals. PRINT VAR RTACM 76(4); PRINT VAR RTACM 76(6); PRINT VAR RTACM 76(7); ! = ! = ! = H'3F ! H'3F ! H'3F ! 5.Bring MO=RXOCF into service using command RXESI. RXESI:MO=RXOCF-x; -Expect RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT IN SERVICE RESULT MO RXOCF-83 END S TATE COM RESULT EXECUTED LOADRESULT LOADED BSSREL 120 6.Now take into service all TGs which are out of service using command RXESI and RXBLE. SOLUTION: CONDITIONS: Some of the following application errors appear in the SYRIP:SURVEY printout.

H'4301 H'C203 H'2B5A H'4300 H'9503 H'4873 H'4301 H'2A03 H'2C7E H'4301 H'2A03 H'2 D9F H'4300 H'2A03 H'28C7 H'4300 H'3103 H'0AFF H'4301 H'C203 H'1B40 H'4301 H'2A03 H'26E0 PROCEDURE: This fault is fixed with the approved correction MWAER-0097 in the block RTAPH. The AC is planned to be included in IP-A 27 for R12MD. Please refer to TR HH75876. Command RXLTI returns FAULT IN SETUP OF RESOURCES Usage Count: 22 58% Network: GSM Node: AXE BSC RBS 2206 Command RXLTI returns FAULT IN SETUP OF RESO URCES RXOTS FAILS with LMO=0940 RXASP on TG returned Loop Test Failed RXLTI retu rns, Fault Interrupt, Fault Code 56, ABIS path in use RXAPP shows no idle RBLT d evice Need more RBLT devices towards the BTS. One TS was not allocated w/ ABIS p ath. Solution: Condition: Certain RXOTS remains Block even RXTEI passed. RXMSP s hows RXOTS in LMO 940 RXLTI fails w/ no resource available RXMDP shows no ABIS d evice connected in the RXOTS. Procedure: ADD more RBLT device (ABIS device ) tow ards the BTS. See explanation below The BTS was configured as 3sector x 2 TRU's i,e there are 6 TRU in this TG . There should be at least 6 DS0 for Control Func tion of the DXU & the TRU devices. Each TRX have 8 time slots (8 x 6) = 48 RXOTS avail for speech&data. In these 48 RXOTS, 3 will be used for Data or Broadcast channels (3 sector Sites) & 45 will be used for Speech. In this site, there are 17 DS0 (Timeslots/rblt devices), of which 6 are used for CF Control Function. 11 DSO's are allocated for Speech&Data. Each DS0 can handle 4 speech/data. With th is config, 44 RXOTS will be avaialble for speech. This means 1 RXOTS will not ha ve abis resources that is why blocked.

This RXOTS device will fail the RXLTI, but will pass the RXTEI . out of 48 RXOTS , 8 * 6 (TRU)=48 RXOTS of this 48 TRU, 3 are used as Data BCCH, available for Sp eech is 45 RXOTS Availalble TS for speech = 45 but avail DS0 for speech is only 44, thus 1 RXOTS for speech is LMO 940 no abis resource avail. This shows that t here is no enough ABIS devices (RBLT) to support the number of Timeslot availabl e in the BTS. Add additional RBLT 24 devices towards the site by RXAPI: Hanging RBLT in State Busy Usage Count: 21 58% Network: GSM Node: AXE RBS 2206 BTS SW: B4401R008F Product Name: RBLT Product ID : CAAZ 107 7702 R3A06 Hanging RBLT in State Busy Command BLODI returns "REJECTED DEVICE CONFIGURED FOR ABIS TRAFFIC" ABIS PATH IN USE is received by giving comm and RXAPE Hanging RBLT device in block RTTRINT The system problem cause is not f ound for this case. The hangong of the devices was produced during an a-bis path removal activity. REMEDY: CONDITIONS: PROCEDURE: 1. Print command STDEP. <stdep :dev=rblt-2431; DEVICE STATE DETAILS DEV RBLT-XXXX END SUBDEV STATE BUSY BLS ADM ABS H'00 CONFIG PC 2. Check that the device is connected and if it has forloop identity: RAPTI:DEV= rblt-; CALL PATH TRACING IN BSC/TRC LINK BRANCH-1 RBLT-XXXX END 3.- PRINT THE FO LLOWING VARIABLES: PRINT VAR RBLT XXXX:H'29; PRINT VAR RBLT XXXX:H'32; !GLSTATE= 6(BUSY)! !SEIZEDEV=0( NOTINPROGRESS)! !SUBFOUND SHOULD BE DIFFERENT TO ZERO! MUP SMUP MUP SMUP MISC PRINT VAR RBLT XXXX:H'33(0-); PRINT VAR RBLT XXXX:H'36(0-); !SUBSTATE=6(BUSY) PRINT VAR RBLT XXXX:H'37(0-); !S UBUSERIND! PRINT VAR RBLT XXXX:H'38(0-); !SUBUSERREF=H'2403(RTTRINT)!

4.- CHECK IF THE RTTRINT INDIVIDUALS (VAR H'37 SUBUSERIND) HAS FORLOPP PRINT VAR RTTRINT XX:H'1E; For this case: RTTRINT VAR H'00 10DB:H'01E=H'0000 H'001C -- FL CONNFIDRTI !FLCONNFIDRTI, where XX=SUBUSERIND var RBLT H'37; 5.- VERIFY THE FID IS THE SAME ASSIGNED TO THE TG <RXMOP:MO=RXOTG-275; RADIO X-C EIVER ADMINISTRATION MANAGED OBJECT DATA MO RXOTG-XXXX RSITE MX5006 SWVERREPL CO NFMD NODEL SWVERDLD B4401R008F TRACO POOL AHOP OFF COMB HYB FHOP SY MODEL G12 SWVERACT B4401R008F CONFACT 4 ABISALLOC BSSWANTED 110 TGFID H'0000-001C END 6.- PRINT THE FORLOPP <syfip:fid=h'0-h'1c; ORDERED < SIGDEL NORMAL WO TOLTR2_K000603Y52RA0010 INDIVIDUALS CONNECTED TO FORLOPP SEARCH NO FORLOPP-ID H'0000 001C BLOCK TRAN1 RXCCOR RXCBM : : RXCMSD RXCMSD RXCMSD RXODPI RCCGD RCC RCCGD RCC RNLC H'0001 H'0001 H'0001 H'0001 H'0002 H'0002 H'0002 H'0002 H'0002 H' 0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 H'0000 2DDD 2DDF 34A5 0226 02A2 02A2 0151 0151 7842 STATUS JOIN(MASTER) AD-191 TIME 071016 1317 PAGE 1 FLPROTYPE H'0000 0022 STATUS PASSIVE PASSIVE PASSIVE DATE 061221 FID-VAR H'0088 H'0034 H'0032 TIME 0318 FILENUMBER H'0006 H'0002 H'0001 INDIVIDUAL H'0000 007F H'0000 2DDF H'0000 0CA7 PASSIVE ACTIVE1 PASSIVE PASSIVE PASSIVE PASSIVE PASSIVE PASSIVE PASSIVE H'00FA H'00FA H'00FA H'0093 H'000E H'002F H'000E H'002F H'001C 7.- RELEASE THE FORLOPP SYFRI:FID=H'0-H'1C,BLOCK=RXCMSD,FILENUM=1,IND=H'2DDF;

SYFRI:FID=H'0-H'1C,BLOCK=RXCMSD,FILENUM=1,IND=H'2DDF; <; EXECUTED 8.- WAIT TWO M INUTES AND CHECK THE RBLT STATE, NOW IS IDLE <stdep:dev=rblt-2431; DEVICE STATE DETAILS DEV RBLT-2431 END SUBDEV STATE IDLE BLS ADM ABS H'00 CONFIG P 9.- NOW YOU CAN BLOCK AND REMOVE THE ABIS PATH USING COMMANDS BLODI/RXAPE H'3002 in block RTACM at IA H'0102 Usage Count: 14 58% Network: GSM Product Name: RTACM Product ID: CAAZ 107 7698 R1A03 Product ID: CAA Z 107 7698 R2A01 Product ID: CAAZ 107 7698 R5B01 Product Name: RXOARC Product ID : CAAZ 107 7105 R1A02 Product ID: CAAZ 107 7105 R2A02 Product ID: CAAZ 107 7105 R3A02 Node: AXE BSC R10 Node: AXE BSC R11 Node: AXE BSC 07B Event Code: H'3002 H '0329 H'0111 Event Code: H'3002 H'0329 H'0102 Event Code: H'3002 H'0329 H'0149 E vent Explanation: FORLOPP IDENTITY MISMATCH (TFID) Event Code: H'320D H'0329 H'0 28B Event Code: H'320D H'023C H'028B Event Explanation: TIMEOUT AT FORLOPP AUDIT ,NO FLERROR Command RXAPE returns ABIS PATH IN USE H'3002 in RTACM is printed ou t just after ordering RXESI command Manual FORLOPP with SYFRI does not clear thi s kind of corruption References: TR HF33838 DETAILED EXPLANATION: Turning the EC F (Exchange Control Function) on, caused additional check on FIR register at rec eption of signal RXICPCONNECTED in RTACM block. Unsuccessful compare of that sig nal's FID with FID stored in RTACM FLCONNFIDTASK (BAN 36) variable caused event FORLOPP IDENTITY MISMATCH. After a short discussion with BSC PLM regarding ECF r ecomendation, it was stated that Execution Control Function SHOULD NOT be turned on during normal operation due to fact that its functionality was never tested out in our application system (BSC APT). SOLUTION: CONDITIONS:

FORLOPP in RTACM block is received at IA H'0102. As a consequence of the first e rror (FORLOPP IDENTITY MISMATCH (TFID)) a second FORLOPP is received. The ECF (E xchange Control Function) is set to ON. PROCEDURE: Verify that the ECP is set to ON: SYFSP; Set the FORLOPP execution control function to OFF: SYFSC:FLECF=OFF; After turning off the ECF, taking the TG with subordinates into DEF state and th en back it into OPER state clears this type of corruption. Block all the MO inst ances subordinate to the specified MO. RXBLI:MO=<mo>,FORCE,SUBORD; Remove the MO from service into prepost service. RXESE:MO=<mo>,SUBORD; Back the MO into servi ce. RXESI:MO=<mo>,SUBORD; Unblock all of the MO instances subordinate to the spe cified MO. RXBLE:MO=<mo>,SUBORD; AC-A loading failed, cells are down after sideswitch Usage Count: 11 Network: GS M Node: AXE BSC AC-A loading failed No traffic after sideswitch Cell are down af ter sideswitch There is no BTS software loaded on APG RPs are working There is n o abnormal event in the SYRIP:SURVEY. BSC dip's are working, MO dips are in ABL state. The A-bis path devices are in IDLE state The signaling RBLT2 devices are in SEBU state. 58% The signaling towards the MO CF function is not established. RXESI gives DISKFIL E NOT FOUND , all MOs in BLOCKED state. BTS software is missing from BTSVOLUME S OLUTION: CONDITIONS: BTS software is missing from BTSVOLUME PROCEDURE: Load the necessary BTS software into APG RXOTS in status SELECT Usage Count: 11 Network: GSM Node: AXE BSC R9.1 Software: AXE BSC R9.1 MD 58%

RXOTS in status SELECT TS's did not carry traffic Alarm 'MANAGED OBJECT FAULT' w ith slogan 'ABIS PATH UNAVAIL' for the appropriate time slots After predefinitio n of TRX's and A-bis (parametar RES64K in command RXAPI) for support GPRS CS3 & CS4 feature,two 16k TS's(RXOTS) changed status from CONFIG into SELECT Wrong def inition SOLUTION: CONDITIONS: PROCEDURE: Define enough A-bis channel (notreserve d for 64k time slots) which will support configuration on base station. RXAPE to remove abis path between BTS and BSC, DCP hanging. Usage Count: 11 58% NETWORK: GSM Node: AXE BSC R8.0 Node: RBS 2000 Hanging DCP corrections MNALS-035 4 & MNALS-0355 in blocks RXOSCO & RXOCCO are loaded. RXAPE to remove abis path b etween BTS and BSC, DCP hanging. Hanging DCP (Digital Connection Point) because RXAPP shows Abis Path in use for TRXC Signalling when all MOs (excl TG) have bee n taken out of service. RXAPP shows "TRXC SIGNALLING" paths exist for all TRXs R XMSP:MO=RXOTG-55,SUBORD; shows all MOs out of service. RXAPE fails with ABIS PAT H IN USE Possible cause: A number of Forlopp Errors and Application Errors occur ed just prior to sending command RXAPE. SOFTWARE RECOVERY SURVEY EVENT TYPE EXPL ANATION EVENTCNT FRDEL 8 FORLOPP FORLOPP RELEASE REQUESTED FROM APPL 1 14 FORLOP P TIMEOUT AT FORLOPP AUDIT & FLERROR 2 2 APPLERR ERROR REPORTED BY PROCEDURE FLE RROR ... EVENT CODE INF1 INF2 INF3 INF4 SIDE STATE DATE TIME ACTIVE 8 H'3100 H'0 146 H'0001 H'0000 H'0000 A-EX PARAL 011002 1021 NO 14 H'310D H'EB00 H'1EFD H'00F F H'028B A-EX PARAL 011001 0939 NO 2 H'4301 H'EB00 H'1EFD H'0005 H'002C A-EX PAR AL 011001 0935 NO ... END SOLUTION: CONDITION: 1.RXMSP shows MO does not exist i n the TG (not accepted stating unreasonable value) . 2.RXAPP shows the MO is sti ll tied to the TG. 3.Indicates that the particular TG has hanging DCP in the sen se that all MOs have been taken out of service but printout from RXAPP still sho ws it being used in the ABIS path. PROCEDURE: 1.Trace initiated for the RBLT dev ices used in the ABIS path by the RAPTI command (ie. RAPTI:DEV=RBLT-3268). 2.RXA PP shows the devices involved wihtin the particular TG. 3.From the answer printo ut "call path tracing in bsc/trc" the FID (FOrlopp IDentity) for the respective devices is obtained. 4.SYFIP is then sent for more information about state/Forlo pp processes type and individuals connected to the specified forlopp. 5.The Bloc k, Filenumber and Individual (info from SYFIP) is then used in the command SYFRI to release the Forlopp/s. Correction for hanging DCPs have already been loaded into the BSC and thus situations such as this is usually isolated to only a few TGs and not affecting many TGs. This particular problem only involved 1 TG in th e whole BSC. PDCH hanging 58%

Usage Count: 9 Network: GSM Node: AXE BSC R9.1 Software: AXE BSC R9.1 MD PDCH ha nging No GPRS traffic possible in the affected cell Double seizure of ABIS path connection in the group switch H'4302 in block RTODCON at IA H'0D1E Event code: H'4302 H'C203 H'0D1E Event explanation: Hidden FLERROR STDEP shows RTGPHDV devic es in state BUSY RLCRP shows TCHs in state BUSY Loading corrections: BSC R9.1 AC -A5 and PLM EC-A23 with side switch restart CNI 109 22-APT 210 09-987 solves "Ha nging channels due to initial synchronization problems" See CNI description for more details Solution: Condition: Procedure: Load CNI 109 22-APT 210 09-987. REM EDY: CONDITIONS: 1. CN-I 109 22-APT 210 09-987 loaded 2. PDCH hanging occurs in the switch. PROCEDURE: Please collect the following information. 1. Follow the D CG appendix 18,section 5.3.2 to collect the GPRS related data. Collect the follo wing information from terdi trace. Commands to check the State of the RPP. CPULO AD; PROGRAM; SYSINFO; DUMP; APT ERRORLIST; Commands to APT GETSTAT APT GETSTAT A PT GETSTAT APT GETSTAT APT GETSTAT APT GETSTAT APT GETSTAT get general statistic s of some processes. RGCONR; RGRLCPR; RGRLCR; MP_MAC_xxx; !(xxx is the cell poin ter in hex, variable 44, block ROTRAN) RP_CHHCELL_xxx; RGSERVR; MP_DSPSUP; Additional commands to get data related to hanging TBFs. APT APT APT APT APT APT APT APT GETTBFLIST GETTBFINFO GETTBFLIST GETTBFINFO GETTBFLIST GETTBFINFO GETTB FLIST GETTBFINFO RGCONR; RGCONR 1; RGRLCPR; RGRLCPR 1; RP_CHHCELL_xxx; RP_CHHCEL L_xxx 1; MP_MAC_xxx; MP_MAC_xxx 1; Commands to get data related to hanging channels. APT GETLPDCHLIST RP_CHHCELL_xx x; APT GETLPDCHINFO RP_CHHCELL_xxx 5; APT GETLPDCHINFO RP_CHHCELL_xxx 4; APT GET LPDCHLIST MP_MAC_xxx; APT GETLPDCHINFO MP_MAC_xxx 4; APT GETLPDCHINFO MP_MAC_xxx 5; APT GETLPDCHLIST RGRLCR; APT GETLPDCHINFO RGRLCR 6;

2. Dump out the following blocks. LASUP:BLOCK=RGRLC&RTODCON&RXCDI&RNTCH&RNLCT&RM HBI&RTGPHDV, VCAT=ALL; RXAPI gives: MAX NO OF ABIS PATHS EXCEEDED IN BSC Usage Count: 8 58% Network: GSM Node: AXE BSC R11 Software: AXE BSC R11 MD Product Name: RTAPH Prod uct ID: CAAZ 107 7700 R2A05 Result printout after cmd RXAPI gives: MAX NO OF ABI S PATHS EXCEEDED IN BSC Alarm: MAX NO OF ABIS PATHS EXCEEDED PER TG After the Fu nction Change from R10 to R11, it is not possible to define further RBLT devices , even if enough SAE individuals are available. The reason is a pointer corrupti on in block RTAPH. REMEDY: CONDITIONS: PROCEDURE: Make a large restart. SYREI:RA NK=LARGE, EXPL=OTHER-xxxx; Until solution is provided updates can be read from T R HF336612 SOLUTION: CONDITIONS: PROCEDURE: Load correction MWAAH-4174. Correcti on is planned to be included in R11 AC-A1 This correction uses test system to se t variables. RXAPE fails with ABIS PATH IN USE. Usage Count: 6 58% Network: GSM Node: AXE BSC R11 Node: AXE BSC R12 Product Name: RTVPH Product ID: CAAZ 107 7700 R2A05 Product ID: CAAZ 107 7699 R3A03 RXAPE fails with ABIS PATH IN USE. Event Code: H'4301 H'2C03 H'01DD Event Code: H'4301 H'2C03 H'015C The Ab is paths hanging is caused by events H'1DD in RTVPH (release of already released VPI). It could be a consequence of previous corruption in linked lists in RTVPH . REMEDY: CONDITIONS: RXAPE fails with ABIS PATH in USE RBLT/RBLTXX devices are MBL and NC RAPTI on the RBLT/RBLTXX device shows no data PROCEDURE:

For R11: Follow SCS360665 to clear hanging. A TG forlopp release or a small syst em restart should clear the existing corruption. The fault was only reported for R11. However if the fault reoccurs in R12, do the followings: Load Trap-EC HG41 835. Load all released ACs in RTVPH, especially M01ER-0037 - to strongly decreas e probability of the fault occurrence. When the fault occurs (seen as either FLE RROR at H'2182 in RTVPH or H'1023 in RTTRINT or H'110E in RTAPH), please registe r new TR and include logs for each mentioned FLERROR events(command SYRIP:EVENT= <event>;). The following blocks should be dumped as soon as possible after the f ault occurs: RTODCON RTTRINT RTVPH RTAPH RTACM RBLTXX RXCDI RXCMOO Info from HH2 1215: The fault will be corrected in a later issue of the Source System, ie. R12 and R06. Design has reasonable suspicions, that the h'1DD events were caused by existing corruption in the linked lists in RTVPH. During last month the trap (E C-HH16976,EC-HH18887) dedicated for linked lists problem has delivered a solutio n (trap has triggered in HH37629) (we've prepared them for R12 - M01ER-0037 and now we are transfering it on higher releases omiting R11). Because the linked li st inconsistances are the most probably reason of our corruption (h'1DD), we may propose the solution included in M01ER-0037 - it is on R12 and we are not plann ing to transfer it down to R11. Command RXASP shows few Time Slots showing "ABIS PATH UNAVAILABLE" Usage Count: 5 58% Network: GSM Node: AXE BSC R8 Node: AXE BSC R9.1 Node: AXE BSC R10 Node: AXE BSC R11 Software: AXE BSC R10 MD Software: AXE BSC R9.1 MD Software: AXE BSC R8.0 M D Software: AXE BSC R11 MD Node: BTS Protocol: LAPD Command RXASP shows few Time Slots showing "ABIS PATH UNAVAILABLE" Few Time Slots not coming up at many site s few TS not coming even sufficient ABIS devices available The two 16kbps TS are not able to come up because in case of 16k LAPD multiplexing with CONFACT=4,one 16k TS/TRX(on average) is required to be reserved over abis interface for the s ignalling purpose between the BTS & BSC and it can not be used as a TCH. SOLUTIO N: CONDITIONS: The below conditions as an example should be there 1) we have 1ce ll/TG for a particular site which has 4 TRUs in that cell & we have exactly 8 Ti me slots of 64kbps each with us. we have defined the cell as CHGR=0 CHGR=1 (1 TR Us with one BCCH & 1 SDCCH/8 channel) (3 TRUs with no SDCCH/8 or SDCCH/4) 2) As per above definition two Time Slots are showing ABIS PATH UNAVAILABLE in C 'RXASP. 3) 16K bandwidth LAPD Multiplexing is used at the problematic site with CONFACT parameter's value eqal to 4.

PROCEDURE: Increase the number of SDCCH by 2 in Channel Group 1 of the cell. 1)H alt the channel group 1 of the cell. RLSTC:CELL=CELLXXA,state=HALTED,CHGR=1; 2)R LCCC:cell=CELLXXA,CHGR=1,SDCCH=2; 3)Make the channel group 1 active RLSTC:CELL=C ELLXXA,state=HALTED,CHGR=1; Following are the observations 1) RBS 2202 or 2206 h ave been used 2) LAPD Multiplexing is used at the problematic site This problem is not dependent on BSC's release level. NOTE: If there are 9 TS of 64 KBPS each then such problem wont come. Command RXAPI returns FAULT INTERRUPT, FAULT CODE 102, HARDWARE LIMIT FOR ABIS PATHS REACHED 58% Usage Count: 4 Network: GSM Node: AXE BSC R07B Product Name: RXCC Product ID: CAAZ 107 6693 R4A01 Command RXAPI r eturns FAULT INTERRUPT, FAULT CODE 102, HARDWARE LIMIT FOR ABIS PATHS REACHED Th e root cause of this problem has not been found. In case the problem occurs agai n a data collection procedure is provided to collect more information. Please se e remedy for relevant data collection procedure. REMEDY: CONDITIONS: AXE BSC R07 B Command RXAPI returns: FAULT INTERRUPT FAULT CODE 102 HARDWARE LIMIT FOR ABIS PATHS REACHED PROCEDURE: Open test system. TEST SYSTEM; Active TELMI command. TE LMI:LOAD=85,TI=50; Load the following trace. ON ON ON ON ON ON FLS RXCC RCVCMD1; FLS DO:IF DR5 = 25,P IA,P SWD,FOR 1 TIMES,ST,; FLIN; FLIN DO:P IA,P SWD,; FLOUT ; FLOUT DO:P IA,P SWD,; Start the trace.

INIT; Send command RXAPI. RXAPI:MO=RXOTG-X,NUMDEV=Y; Close the test system. END TEST; Log the information to a file and open a case in customer support to inves tigate the root cause of this problem. Check PGW RP state. EXRPP:RP=pgw rp; Bloc king RP. BLRPI:RP=pgw rp,FORCED; Deblocking RP. BLRPE:RP=pgw rp; Check PGW RP st ate. EXRPP:RP=pgw rp; Repeat step 8 to 11 for all PGW RPs. Send command RXAPI. R XAPI:MO=RXOTG-X,NUMDEV=Y; Abispath DCP 308 caused loop test failed Usage Count: 3 58% Network: GSM Node: AXE BSC 07B Hardware: RBS 2206 Software: BTS SW 08A Software: BTS BTS 08B Abis path defined with DCP number 308 caused TS loop test failed Ab is path defined with DCP number 22 and 308 cause TS synch fault and loop test fa ult RXLTI loop test failed always on the same RBLTx device on DCP 308 or DCP 22 The RBS SW fakes that it has found signaling on TS 22 during the SC scanning pro cess and it is not reconfigured properly. The scanning process will be used in T DM mode as well. SOLUTION: CONDITIONS: TS Synch fault on DCP number 22 or 308 PR OCEDURE: Load RBS SW 09A or newer. In case of RBS in cascade, load all RBSs in t he cascade chain. RXLTI loop test failed always on the same RBLTx device on DCP 308 or DCP 22 <rxlti:mo=rxots-107-8-4; RADIO X-CEIVER ADMINISTRATION TRC-BTS LOO P TEST RESULT MO RXOTS-107-8-4 RESULT TEST FAILED

TRADEV RTTGD-4398 END TRCATERDEV BSCATERDEV ABISDEV RBLT2-4182 <rxapp:mo=rxotg-107; RADIO X-CEIVER ADMINISTRATION ABIS PATH STATUS MO RXOTG-107 DEV RBLT2-4161 RBLT2-4162 RBLT2-4163 RBLT2-4164 RBLT2-4165 RBLT2-4166 RBLT2-416 7 RBLT2-4168 DCP 287 288 289 290 291 292 293 294 APUSAGE UNCONC UNCONC UNCONC UN CONC UNCONC UNCONC UNCONC MPLEX16 MPLEX16 MPLEX16 MPLEX16 RBLT2-4169 295 MPLEX16 MPLEX16 MPLEX16 MPLEX16 NO MPLEX16 MPLEX16 MPLEX16 RBLT2-4171 297 MPLEX16 MPLEX 16 MPLEX16 MPLEX16 RBLT2-4172 298 MPLEX16 MPLEX16 MPLEX16 SPEECH/DATA SPEECH/DAT A SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH /DATA SPEECH/DATA NO NO NO NO NO NO NO NO NO NO APSTATE TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL TRXC SIGNAL SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA 64K NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO RBLT2-4170 296 MPLEX16 SPEECH/DATA TEI 6 5 4 3 2 1 0

MPLEX16 RBLT2-4173 299 MPLEX16 MPLEX16 MPLEX16 MPLEX16 RBLT2-4174 300 MPLEX16 MP LEX16 MPLEX16 MPLEX16 RBLT2-4175 301 MPLEX16 MPLEX16 MPLEX16 MPLEX16 RBLT2-4176 302 MPLEX16 MPLEX16 MPLEX16 MPLEX16 RBLT2-4177 303 MPLEX16 MPLEX16 MPLEX16 MPLEX 16 RBLT2-4178 304 MPLEX16 MPLEX16 MPLEX16 MPLEX16 RBLT2-4179 305 MPLEX16 MPLEX16 MPLEX16 MPLEX16 NO MPLEX16 MPLEX16 MPLEX16 RBLT2-4181 307 MPLEX16 MPLEX16 MPLEX 16 SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEE CH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEE CH/DATA SPEECH/DATA NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO RBLT2-4180 NO NO NO NO NO NO 306 MPLEX16 SPEECH/DATA

MPLEX16 RBLT2-4182 RBLT2-4183 RBLT2-4184 RBLT2-4185 RBLT2-4186 RBLT2-4187 RBLT24188 RBLT2-4189 YES RBLT2-4191 308 309 310 311 312 313 314 315 317 UNDEF UNCONC UNCONC UNCONC UNCONC UNCONC UNCONC UNCONC MPLEX16 MPLEX16 MPLEX32 END BTS Loop T est: SPEECH/DATA IDLE TRXC SIGNAL CF/TRXC SIGNAL SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA IDLE IDLE NO NO NO NO YES YES YES YES YES RBLT2-4190 NO NO NO 316 UNCONC SPEECH/DATA 8 61 7 The BTS loop test is done in three phases. First, a transcoder resource is reque sted by RTTPR to the pool handler, as for a normal speech call. Then, if availab le, RTTPR orders the corresponding device owner (RTTGD in this case) to set up a GS loop connection. If successful, then RTTGSR orders the corresponding transco der channel to start the test. The actual test is done by the transcoder by send ing a pattern on the a-bis and checking it when it is received back. BTS Loop Te st failure: The test can fail for many reason: 1) GS doesn't perform the loop co nnection as expected and/or the connection to the RBLT on the MUX side of TRA; 2 ) TRA fails in the check of patterns; 3) A-bis path has problems; 4) BTS has pro blems. How to upgrade a 16K path to 64K when flexible Abis is used Usage Count: 3 How t o upgrade a 16K path to 64K when flexible Abis is used Network: GSM Node: AXE BS C R11 Software: AXE BSC R11 MD E-PDCH are not allocated ABISALLOC is changed to Flexible in the TG NUMREQEGPRSBPC parameter changed during a data connection SOL UTION: CONDITIONS: PROCEDURE: 58%

When using flexible abis and NUMREQEGPRSBPC > 0, PDCHs are configured with 16K/6 4K abis path. If the PDCH selected uses a 16k Abis path, in order to upgrade the path to 64K, and EDGE capable phone has to trigger the upgrade. If a non Edge c apable phone is used, the 16k path allocated (BPDCH) will not be upgraded to a 6 4K path (EPDCH). No traffic on abis path due to signaling taking all resources Usage Count: 3 58% Network: GSM Node: AXE BSC R8.0 Node: DXX Two paths used. DXX is setup to keep h alf of the devices of A-bis on each path No traffic on abis path due to signalin g taking all resources High Processor Load When one of the paths go down they ar e left with only three devices per cell. These devices will be configured for si gnaling only, leaving no devices for traffic. The priority of taking devices in a reconfiguration of A-bis interfaces is first CF, after TRXC signalling and at the end Speech/Data. If there is not enough available time slots, then no speech /data TS are going to be configured. High processor load is due to BTS reconfigu ration. SOLUTION: CONDITIONS: PROCEDURE: Use LAPD concetration or multiplexing. If that is used, then more time lots have to be configured for A-bis interface i n DXX. High Processor load in the BSC. Usage Count: 3 58% Network: GSM Node: AXE BSC R9.0 BSC Processor load 95-97% Abis DIP shows severel y errored seconds in alarm. Alarm DIGITAL PATH QUALITY SUPERVISION is outstandin g on an Abis DIP and shows severely errored seconds. One or more cells served by the errored DIP is continually re-configuring. SOLUTION: CONDITIONS: PROCEDURE: 1) Check the processor load: <plldp; PROCESSOR LOAD DATA INT PLOAD CALIM OFFDO OFFDI FTCHDO FTCHDI OFFMPH OFFMPL FTCHMPH FTCHMPL 1 94 445 2 1 2 1 1 442 1 442 2 97 460 3 0 3 0 1 457 1 457 3 89 420 6 1 6 1 2 407 2 407 4 95 444 4 0 4 0 1 440 1 440 5 96 450 1 0 1 0 2 449 2 449 6 95 450 3 0 3 0 1 447 1 447 7 95 450 4 0 4 0 0 446 0 446 8 96 455 1 0 1 0 1 454 1 454 9 96 455 2 0 2 0 0 453 0 453 10 94 456 7 0 7 0 1 449 1 449 11 96 474 3 1 3 1 2 468 2 468 12 96 450 3 1 3 1 2 442 2 442 END 2) Check the alarm list for the errored DIP: <ALLIP:PRCA=42;

O1/APT "DRNCB01_D000E00" 732 021028 DIGITAL PATH QUALITY SUPERVISION SES DIP 12R BLT DIPPART SESL2 1 QSV 3 0818 SECTION DATE 021028 TIME 081849 O1/APT "DRNCB01_D000E00" 735 021028 DIGITAL PATH QUALITY SUPERVISION ES DIP 12RB LT END DIPPART ESL2 26 QSV 28 0830 SECTION DATE 021028 TIME 083006 3) Print the digital path to get the SNT: <dtdip:dip=12rblt; DIGITAL PATH DIP 12 RBLT END SNT ETRBLT4-12 DEV DIPP CLREF DIPNUM DIPOWNER 12 DIPRBT4 4) Find the device range connected to the SNT: <ntcop:snt=etrblt4-12; SWITCHING NETWORK TERMINAL CONNECTION DATA SNT ETRBLT4-12 END SNTV SNTP 4 TSM-9-4 DIP 12RB LT DEV RBLT24-288&&-311 DEVP 5) Find the managed object: <rxmdp:moty=rxotrx,dev=rblt24-288; RADIO X-CEIVER AD MINISTRATION MANAGED OBJECT DEVICE INFORMATION MO RXOTRX-12-4 END 6) Block the C ontrol Function (CF): <RXBLI:MO=RXOCF-12,FORCE,SUBORD; RXBLI:MO=RXOCF-12,FORCE,S UBORD; <; RADIO X-CEIVER ADMINISTRATION MANUAL BLOCKING OF MANAGED OBJECT COMMAN D RESULT MO RXOTF-12 RXOTX-12-0 RXOTS-12-0-0 RXOTS-12-0-1 RXOTS-12-0-2 RXOTS-120-3 RXOTS-12-0-4 RXOTS-12-0-5 RXOTS-12-0-6 RXOTS-12-0-7 RXORX-12-0 RXOTRX-12-0 R XOIS-12 RXOCF-12 STATE COM COM COM COM COM COM COM COM COM COM COM COM COM COM R ESULT EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED EX ECUTED EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED DEVS RHDEV-332 DEVT RBLT24-2 88

END 7) Repair the DIP (not addressed here). 8) Deblock the Control Function (CF) : <rxble:mo=rxocf-1,subord; RXBLE:MO=RXOCF-1,SUBORD; <; RADIO X-CEIVER ADMINISTR ATION MANUAL DEBLOCKING OF MANAGED OBJECT COMMAND RESULT MO RXOCF-1 RXOIS-1 RXOT RX-1-0 RXORX-1-0 RXOTS-1-0-0 RXOTS-1-0-1 RXOTS-1-0-2 RXOTS-1-0-3 RXOTS-1-0-4 RXO TS-1-0-5 RXOTS-1-0-6 RXOTS-1-0-7 RXOTX-1-0 RXOTF-1 END < EX-A BSC4/R9/ECA1/SCA2 NVT-163 TIME 021028 1549 RADIO X-CEIVER ADMINISTRATION MANUAL DEBLOCKING OF MANA GED OBJECT RESULT MO RXOCF-1 RXOTF-1 END 9) Check the processor load again: <pll dp; PROCESSOR LOAD DATA INT PLOAD CALIM OFFDO OFFDI FTCHDO FTCHDI OFFMPH OFFMPL FTCHMPH FTCHMPL 1 12 6000 2 0 2 0 0 3 0 3 2 12 6000 5 0 5 0 1 1 1 1 3 13 6000 4 1 4 1 1 3 1 3 4 12 6000 5 0 5 0 1 0 1 0 5 13 6000 7 0 7 0 1 3 1 3 6 12 6000 5 0 5 0 1 0 1 0 7 11 6000 3 0 3 0 1 4 1 4 8 9 6000 6 0 6 0 2 1 2 1 9 12 6000 4 0 4 0 0 4 0 4 10 12 6000 2 0 2 0 2 1 2 1 11 13 6000 7 0 7 0 0 3 0 3 12 12 6000 4 0 4 0 1 0 1 0 END This solution addresses the high processor load symptom and does n ot attempt to address repairing the digital path problems. Deblocking the CF imm ediately after blocking (and before repairing the DIP) may relieve the processor load. RBLT erroneously linked to another TG Usage Count: 2 Network: GSM 58% STA TE OPER OPER RESULT EXECUTED EXECUTED PAGE 1 STATE PREOP NOOP NOOP NOOP NOOP NOO P NOOP NOOP NOOP NOOP NOOP NOOP NOOP PREOP RESULT ORDERED EXECUTED EXECUTED EXEC UTED EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED EXECUTED EXE CUTED ORDERED

Node: AXE BSC R12 Product Name: RBLTxx Product ID: CAAZ 107 7702 R4A01 Command R XCDP (Managed Object Configuration Data) shows RXOTS in RESULT SELECT Command RX LTI (Loop Test) on RXOTS/RBLT fails with FAULT IN SETUP OF RESOURCES Command RXA PP (ABIS path Status) shows RBLT APUSAGE UNDEF and APSTATE IDLE Command RAPTI (C all Path Trace) on RBLT shows that it is linked to another TG, but RAPTI on the other linked RBLT belonging to the erroneous RXOTS does not show the same call p ath Some timeslots (RXOTS) cannot be configured and remain in SELECT because the idle RBLTxx cannot be seized for traffic. A loop test on the RXOTS/RBLTxx fails with FAULT IN SETUP OF RESOURCES. The remedy is to disassociate the RBLTxx from the erroneous TG REMEDY: CONDITIONS: 1. AXE BSC R12 MD 2. Perform a loop test u sing the suspected RBLT and verify that it fails: RXLTI: MO=RXOTS-tg-trx-ts, DEV =RBLTxx-rblt; RESULT: example RADIO X-CEIVER ADMINISTRATION TRC-BTS LOOP TEST RE SULT MO RXOTS-tg-trx-ts TRADEV END R ESULT FAULT IN SETUP OF RESOURCES TRCATERDE V BSCATERDEV ABISDEV RBLTxx-rblt 3. Print the RBLT call path for all subdevices and verify that at least 1 subdev ice belongs to the wrong TG. Subdevices not belonging to a wrong TG should have no call path. No subdevice should be connected to the correct TG.: RAPTI: DEV=RB LTxx-rblt, SDEV=sdev; RESULT: example CALL PATH TRACING IN BSC/TRC LINK BRANCH-1 RBLTxx-rblt RTTRINT-rttrint RXOTS-wtg-wtrx-wts : RBLTxx-orblt : BUSY FID:fid FI D:fid ! wrong TG ! orbltsdev BUSY MUP SMUP MUP SMUP MISC 4. From the printout in step 2, obtain the other RBLTxx individual (orblt) and s dev (orbltsdev) . Print the RBLT callpath and verify that RBLTxx-rblt is not inc luded RAPTI: DEV=RBLTxx-orblt, SDEV=orbltsdev; 5. From the printout in step 2, obtain the RTTRINT individual (rttrint) verify t hat the suspect RBLT subdevice state is BUSY:

TEST SYSTEM; PRINT VAR RBLTxx rblt(subdev):54; ! subdev = sdev/2, state = BUSY ( 6)! RESULT: VARIABLE RBLTxx rblt:H'036(subdev)=H'0006 ! BUSY ! END END TEST; 6. From the printout in step 2, obtain the RTTRINT individual (rttrint) verify that the suspect RBLTxx points to it: - TEST SYSTEM; - PRINT VAR RBLTxx rblt(subdev) :56; ! subdev = sdev/2! RESULT: VARIABLE RBLTxx rblt:H'038(subdev)=H'2403 ! bloc k reference RTTRINT ! END - PRINT VAR RBLTxx rblt(subdev):55; ! subdev = sdev/2! RESULT: VARIABLE RBLTxx VAR rblt:H'037(subdev)=rttrint ! RTTRINT individual fro m step 2 ! END - END TEST: 7. From printout in step 2, obtain the RTTRINT indivi dual (rttrint) verify that it does not point to the suspect RBLT, but points to the other RBLT (yy). - TEST SYSTEM; - PRINT VAR RTTRINT rttrint:46; ! verify the block reference ! RESULT: VARIABLE RTTRINT VAR rttrint:H'02E=blkref ! block ref erence for RBLTxx ! END - PRINT VAR RTTRINT rttrint:45; ! verify the RBLTxx poin ter ! RESULT: VARIABLE RTTRINT VAR rttrint:H'02D=orblt ! matches the other RBLT and not the suspect RBLT ! END - END TEST; PROCEDURE: 1. STDEP:DEV=RBLT-rblt; ! Obtain the SUBDEV info (subdev) ! RESULT: e xample DEVICE STATE DETAILS DEV RBLTxx-rblt END SUBDEV subdev STATE BUSY BLS ADM ABS H'00 CONFIG PC

2. Activate Test System session. TEST SYSTEM; 3. Send signal RTRELEASEDEV. SEND RTRELEASEDEV TO RBLTxx VIA LNK WITH rblt, subdev, 1; 4. End test system session END TEST; How to upgrade a 16K path to 64K when flexible Abis is used Usage Count: 2 How t o upgrade a 16K path to 64K when flexible Abis is used Network: GSM Node: AXE BS C R11 Software: AXE BSC R11 MD E-PDCH are not allocated ABISALLOC is changed to Flexible in the TG NUMREQEGPRSBPC parameter changed during a data connection SOL UTION: CONDITIONS: PROCEDURE: 58% When using flexible abis and NUMREQEGPRSBPC > 0, PDCHs are configured with 16K/6 4K abis path. If the PDCH selected uses a 16k Abis path, in order to upgrade the path to 64K, and EDGE capable phone has to trigger the upgrade. If a non Edge c apable phone is used, the 16k path allocated (BPDCH) will not be upgraded to a 6 4K path (EPDCH). How can we get the idle devices on A-bis paths from bsm database periodically? U sage Count: 2 How can we get the idle devices on A-bis paths from bsm database p eriodically? Network: GSM Node: SUN OSS-RC 2.2 CP3 R1AB_1 Software: OSSRC_R2_shi pment_C11 AOM_901017_2_R1AB_1 Product Name: BSM Product ID: CXC 134 272/4 / r12k 02 bsm data export for abis path customer wants to see idle state abis paths SOL UTION: CONDITION: PROCEDURE: 58% The program bsm_export exports the MO data from the BSM database and prints them in a defined output format on the Standard Output (stdout) device. It is possib le to specify which attributes and properties of the MOs in the database that ar e to be exported by using a defined export specification file. The export specif ication file is used to generate the output-data file out of the database. Furth ermore, it is possible to define the export format as well as define from which configuration type the attributes and properties are to be exported by using dif ferent command line arguments.

For example; The format given below will export abis information for the given o ne BSC. For this example I do not suggest to run this query for whole network. I t will take a very long time and consume CPU and MEMORY. Instead use BSC by BSC like below.... root@ormas1o> more abis_export !TGs,Species,Path,Name,abiss.dev,a biss.dcp,abiss.abispath64k,abiss.apstate, \ abiss.apusage Species=TG12,Path=plmn =AXE,bsc=DBM06B1 root@ormas1o> /opt/ericsson/bin/bsm_export -p < --------------------------------------Configuration=VALID --------------------------------------!TGs|Species|Path |Name |abiss.dev |abiss.dcp| abiss.abispath64k|abiss.apstat e |abiss.apusage | 1 |"TG12" |"plmn=AXE,bsc=DBM06B1,site=BITKUCUKSU" |"RXOTG-128 "|"RBLT2-577" |1 | no |"speechdata&speechdata&speechdata&speechdata"|"mplex16&mp lex16&mplex16&mplex16"| 1 |"TG12" |"plmn=AXE,bsc=DBM06B1,site=BITKUCUKSU" |"RXOT G-128"|"RBLT2-578" |2 | no |"speechdata&speechdata&speechdata&speechdata"|"mplex 16&mplex16&mplex16&mplex16"| 1 |"TG12" |"plmn=AXE,bsc=DBM06B1,site=BITKUCUKSU" | "RXOTG-128"|"RBLT2-579" |3 | no |"speechdata&speechdata&speechdata&speechdata"|" mplex16&mplex16&mplex16&mplex16"| 1 |"TG12" |"plmn=AXE,bsc=DBM06B1,site=BITKUCUK SU" |"RXOTG-128"|"RBLT2-580" |4 | no |"trcxsignalling" |"conc" | : : : abis_expo rt Upgrade a 16K path to 64K when flexible Abis is used Usage Count: 2 58% Upgrade a 16K path to 64K when flexible Abis is used Network: GSM Service: EDGE Node: AXE BSC R11 Document Title: Feature Test Description BSS R11, Flexible Abi s Document ID: 320/152 91HSC 103 12 Uen A Feature: Flexible Abis Upgrade / downg rade of PDCH channels does not work as expected All used B-PDCH is upgraded to E -PDCH although MSs are not capable to use them (chapter 2.2.5 step 26) Not all o n-demand E-PDCH is downgraded when needed (chapter 2.2.5, step 27) Reference: Se e TR HH18320 SOLUTION: CONDITIONS: Upgrade / downgrade of PDCH channels does not work as expected PROCEDURE: By increasing the TBFULLIMIT and TBFDLLIMIT values the correct behaviour of the test case will be obtained. The description of the test case in the test description is insufficient and should have had increased values of TBFULLIMIT and TBFDLLIMIT as prerequisites. The author is requested to update the document. Please refer TR HH18320 for details.

NO alarm when Abis Path not available Usage Count: 2 Network: GSM Node: AXE BSC R10 MD Software: AXE BSC R10 MD AC-A 5 Service: EDGE NO alarm when Abis Path not available REMEDY: CONDITIONS: 58% If the fault still exists please collect following data: PROCCEDURE: 1. Define t races: ACTION: TEST SYSTEM; ON OU RXCDI RXDIIBLINFO; ON OU RXOLDF RXAUTOBBL; ON IN RXOAL RXKICKOFF, RXMOTIMEOUT; ON OU RXOAL RXSETMOTIM, RXWRTALSIT, FAULT; ON O U DO: P IA, P SWD,; ON IA RXOAL H'510, H'698; ON IA DO: P IA, P DR8,P DR11,; ON VAR RXOAL H'41; !CABISFAULT! ON VAR DO: P IA, P VAR,; TMSIZE 32000; INIT; 2. Cha nge number of the requested E-TCHs to reproduce the fault. ACTION: RLBDP:CELL=ce ll, RLBDC:CELL=cell,NUMREQEGPRSBPC=0,CHGR=0; NOTE: If any BPC is in BLOC state a nd LMO code 0800 means there is not enough abis paths. Use c'RXMSP:MO=mo,SUBORD, RLCRP:CELL=cell. Release terminal an collect traces. 3. Wait at least 2 minutes and check alarm list: ACTION: ALLIP; 4. If no alarm "abis path unavailable" is printed, collect following data: ACTION: LASUP:VCAT=ALL,BLOCK=RXCMOO;

5. Halt and activate the cell (c'RLSTC). 6. Wait at least 2 minutes and check al arm list: ACTION: ALLIP; 7. Terminate traces, restore initial configuration (use number of NUMREQEGPRSBPC from step 2). 8. Change value of NUMREQBPC in CHGR 1 t o 8 (as is described in the TR desc.). 9. Initiate traces and repeat steps 2 to 4. ACTION: INIT; 10. End Test System. 11. Attach transaction log and DCG ch. 4 d ata to the logs. The fault is reported in TR HF89956 below the configuration (RL BDP) : CELL CONFIGURATION BPC DATA CELL B13801 CHGR 0 1 CELL B13802 CHGR 0 1 CEL L B13803 CHGR 0 1 END; If change of NUMREQEGPRSBPC for CHGR 0 to 0 in this situa tion for all cells, then problems with 6 timeslots in the configuration. This is due to the fact that there are in normal configuration in our network 6 16k tim eslots idle on the A-bis path. These will be used for the first 6 BPC that are t ransferred from the EGPRS domain. However for the last 6 BPC's there are no idle 16 k timeslots left. These will end up in BLOC state. For these 6 expectation t o see an alarm in the allip printout: A2/APT "BDB1 746/1000 0" 726 050421 RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT FAULT MO RXOTS-60-2-1 1104 NUMREQBPC SYSD EF SYSDEF NUMREQEGPRSBPC 4 0 NUMREQCS3CS4BPC 0 0 TN7BCCH GPRS NUMREQBPC SYSDEF S YSDEF NUMREQEGPRSBPC 4 0 NUMREQCS3CS4BPC 0 0 TN7BCCH GPRS NUMREQBPC SYSDEF SYSDE F NUMREQEGPRSBPC 4 0 NUMREQCS3CS4BPC 0 0 TN7BCCH GPRS RSITE B1380_MC ALARM SLOGAN ABIS PATH UNAVAIL

However that alarm does not appear. The alarm does appear when change of NUMREQB PC value in CHGR 1 to in CHGR1 (so in this case to 8) In both cases the RLCRP pr intout shows the correct situation after NUMREQEGPRSBPC's namely BLOC for 6 of t he TimeSlots. Also the RXAPP printout shows that 6 idle 16k timeslots the 64K ti meslots are idle (correct), ,6 other 64K timeslots are in fault state (also corr ect). However parameter SYSDEF is used. the actual number of TS changing the hav e gone in use and 6 of no alarm is raised when GSM:RXODPI number is disabled in BSM_wizard Usage Count: 2 58% Network: GSM Node: SUN OSS Software: SUN Solaris 5.8 Software: Sybase 12.5 GSM:R XODPI number is disabled in BSM_wizard When trying to rehome one cell M46+ from one BSC to the other using BSM_wizard, the field for RXODPI number is disabled. And for other Cells, there is no problem. The DCP values in the ABIS path is out of range for a TG. When try to move this TG the BSM move RBS wizard core dummp, when move to the second step (window) in the wizard. BSM Coding fault SOLUTION: CONDITIONS: BSM_wizard crashed when trying to move RBS. PROCEDURE: This problem was addressed in TR HE31624 and is fixed in RC1.1 CP2 which was just released o n Mar 19th. defining abis path for a 3 cabinet site Usage Count: 2 defining abis path for a 3 cabinet site Network: GSM Node: AXE BSC R8.0 SOLUTION: --------PRO CEDURE: ---------for a three cabinet site if the TG for the three cabinets are 1 ,100,200 respectively, two pcm are required, now if the first two cabinets i.e m aster and slave are catered by the first pcm,then : for defining rblt devices to the first tg i.e tg-1: rxapi:mo=rxotg-1,dev=rblt-1&&-5,dcp=1&&5; for tg-100: rx api:mo=rxotg-100,dev=rblt-6&&10,dcp=6&&10; and now for a third tg i.e tg-200 dev ices are attached as: rxapi:mo=rxotg-200,dev=rblt-705&&-707,dcp=1&&3; 58%