Alarm: Abis Path overload Usage Count: 4 Alarm: Abis Path overload Usage Count: 4 90%
90%
Network: GSM Node: AXE BSC R06B Software: AXE BSC R06B
Network: GSM Node: AXE BSC R06B Software: AXE BSC R06B IP-A06 Node: AXE RBS 2409IP-A06 Node: AXE RBS 2409 Alarm: Abis Path overload Alarm is ceased after
Alarm: Abis Path overload Alarm is ceased after finishing Edge Call Alarm comesfinishing Edge Call Alarm comes up sporadically while PS Edge Calls SOLUTION: CONDITIONS: PROCEDURE: The perfor up sporadically while PS Edge Calls SOLUTION: CONDITIONS: PROCEDURE: The perfor mance of the DSL line is
mance of the DSL line is reflected in the following parameter settings in the BSreflected in the following parameter settings in the BS C. After aligning the parameter for maximum bandwidth in downlink and maximum ba C. After aligning the parameter for maximum bandwidth in downlink and maximum ba ndwidth in uplink the fault could not be
ndwidth in uplink the fault could not be reproduced any more. Parameters Settingreproduced any more. Parameters Setting : RRSGI:SCGR=scgr,MODE=IPM,PSTU=pstu,M
: RRSGI:SCGR=scgr,MODE=IPM,PSTU=pstu,MBWDL=16000,MBWUL=6000; The value of BWDL=16000,MBWUL=6000; The value of parameparame ter MBWUL could be increased if the alarm occurs, however too
ter MBWUL could be increased if the alarm occurs, however too high value may cauhigh value may cau se problems with the load regulation (increasing number of handovers, new calls se problems with the load regulation (increasing number of handovers, new calls rejecting). Parameter Explanation: MBWDL: (64-16384 kbps) This parameter
rejecting). Parameter Explanation: MBWDL: (64-16384 kbps) This parameter definesdefines the maximum bandwidth in downlink. The parameter defines the bandwidth in downl the maximum bandwidth in downlink. The parameter defines the bandwidth in downl ink that is considered 100% when calculating thresholds for triggering overload ink that is considered 100% when calculating thresholds for triggering overload prevention mechanisms. This value should be set as close to the
prevention mechanisms. This value should be set as close to the actual bandwidthactual bandwidth as possible.
as possible.
MBWUL: (64-16384 kbps) MBWUL: (64-16384 kbps)
This parameter defines the maximum bandwidth in uplink. The parameter defines th 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 e bandwidth in uplink that is considered 100% when calculating thresholds for tr iggering overload prevention mechanisms. This value should be set slightly less iggering overload prevention mechanisms. This value should be set slightly less than the actual bandwidth.
than the actual bandwidth.
TCH blocking with Abis Optimization sites Usage Count: 3 TCH blocking with Abis Optimization sites Usage Count: 3 90%
90%
Network: GSM Node: AXE BSC 09A APZ 212
Network: GSM Node: AXE BSC 09A APZ 212 55 Software: AXE BSC 09A-UM17 Site with A55 Software: AXE BSC 09A-UM17 Site with A bis Optimization does not work Printing of "RADIO TRANSMISSION SUPER CHANNEL DAT bis Optimization does not work Printing of "RADIO TRANSMISSION SUPER CHANNEL DAT A" shows state FLT Alarm :" ABIS
A" shows state FLT Alarm :" ABIS PATH OVERLOAD" Alarm: "ABIS PATH FAULT" on SupePATH OVERLOAD" Alarm: "ABIS PATH FAULT" on Supe r Channel High TCH drop in cells
r Channel High TCH drop in cells with Optimized ABIS Before this there was Groupwith Optimized ABIS Before this there was Group switch alarm with one XM( Plan-A) card
switch alarm with one XM( Plan-A) card fault.After group switch hardware unit rfault.After group switch hardware unit r estoration it is likely to be hangup situation prevailing between RTPGD (PGW) de 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 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 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 isconnect 2.Remove SC definition RRSCE:SCGR=y,SC=x,FORCE; 3.Re-initialize the SC RRSCI:SCGR=xx,SC=y,DEV1=RBLT2-xxx
RRSCI:SCGR=xx,SC=y,DEV1=RBLT2-xxxx,DCP=1,NUMDEV=nn; Forlopp release on TG , x,DCP=1,NUMDEV=nn; Forlopp release on TG , PGWPGW - RP restart could not worked ABIS PATH
- RP restart could not worked ABIS PATH OVERLOAD alarm on PICO cell Usage Count:OVERLOAD alarm on PICO cell Usage Count: 2 90%
2 90%
Network: GSM Node: AXE BSC 07B Feature: Abis over IP
Network: GSM Node: AXE BSC 07B Feature: Abis over IP ABIS PATH OVERLOAD alarm onABIS PATH OVERLOAD alarm on PICO cell Alarm :" ABIS
PICO cell Alarm :" ABIS PATH OVERLOAD" RTPGSR sends CPXTGLOADINF signal to RTPGPATH OVERLOAD" RTPGSR sends CPXTGLOADINF signal to RTPG SU, indicating IP overload, and this leads to "ABIs PATH
SU, indicating IP overload, and this leads to "ABIs PATH OVERLOAD " alarm for thOVERLOAD " alarm for th e relevant TG SOLUTION:
e relevant TG SOLUTION: CONDITIONS: "text" PROCEDURE: "text"CONDITIONS: "text" PROCEDURE: "text" Traffic reduced after abis optimization activated Usage Count: 2 Traffic reduced after abis optimization activated Usage Count: 2 90%
90%
GSM BSS 06A Traffic reduced after abis optimization activated Erlang Traffic is GSM BSS 06A Traffic reduced after abis optimization activated Erlang Traffic is reduced ALARM: ABIS PATH OVERLOAD Abis Optimization Feature implemented in one s reduced ALARM: ABIS PATH OVERLOAD Abis Optimization Feature implemented in one s ite The paramater PACKALG was set to 0
ite The paramater PACKALG was set to 0 in the TG ... so in the TG ... so the ABIS was not reallythe ABIS was not really being optimized SOLUTION: CONDITIONS: PROCEDURE: Set the PACKALG to 1
being optimized SOLUTION: CONDITIONS: PROCEDURE: Set the PACKALG to 1 How to avoid Abis-Interface over Satellite overload Usage Count: 1 How to avoid Abis-Interface over Satellite overload Usage Count: 1 90%
90%
How to avoid Abis-Interface over Satellite overload Network: GSM Node: AXE BSC 0 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
8B TCH congestion after ABIS/IP swap ALARM: ABIS PATH OVERLOAD Abis path overloaoverloa d alarm for the concerned TG Abis over
d alarm for the concerned TG Abis over satellite overload IPLOSTPACKUL shows higsatellite overload IPLOSTPACKUL shows hig h valies as compared to LOSTDLPACK Configuration change The problem is caused by h valies as compared to LOSTDLPACK Configuration change The problem is caused by bad transmission on Abis. If the IP
bad transmission on Abis. If the IP transmission is causing a lot of packet lostransmission is causing a lot of packet los ses, the overload mechanism will trigger which will cause TCH congestion during ses, the overload mechanism will trigger which will cause TCH congestion during the time the link is bad.
1.Remove the TG definition OPI. Radio X-ceiver Administration, Managed Object, D 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 isconnect 2.Remove SC definition RRSCE:SCGR=y,SC=x,FORCE; 3.Re-initialize the SC RRSCI:SCGR=xx,SC=y,DEV1=RBLT2-xxx
RRSCI:SCGR=xx,SC=y,DEV1=RBLT2-xxxx,DCP=1,NUMDEV=nn; Forlopp release on TG , x,DCP=1,NUMDEV=nn; Forlopp release on TG , PGWPGW - RP restart could not worked ABIS PATH
- RP restart could not worked ABIS PATH OVERLOAD alarm on PICO cell Usage Count:OVERLOAD alarm on PICO cell Usage Count: 2 90%
2 90%
Network: GSM Node: AXE BSC 07B Feature: Abis over IP
Network: GSM Node: AXE BSC 07B Feature: Abis over IP ABIS PATH OVERLOAD alarm onABIS PATH OVERLOAD alarm on PICO cell Alarm :" ABIS
PICO cell Alarm :" ABIS PATH OVERLOAD" RTPGSR sends CPXTGLOADINF signal to RTPGPATH OVERLOAD" RTPGSR sends CPXTGLOADINF signal to RTPG SU, indicating IP overload, and this leads to "ABIs PATH
SU, indicating IP overload, and this leads to "ABIs PATH OVERLOAD " alarm for thOVERLOAD " alarm for th e relevant TG SOLUTION:
e relevant TG SOLUTION: CONDITIONS: "text" PROCEDURE: "text"CONDITIONS: "text" PROCEDURE: "text" Traffic reduced after abis optimization activated Usage Count: 2 Traffic reduced after abis optimization activated Usage Count: 2 90%
90%
GSM BSS 06A Traffic reduced after abis optimization activated Erlang Traffic is GSM BSS 06A Traffic reduced after abis optimization activated Erlang Traffic is reduced ALARM: ABIS PATH OVERLOAD Abis Optimization Feature implemented in one s reduced ALARM: ABIS PATH OVERLOAD Abis Optimization Feature implemented in one s ite The paramater PACKALG was set to 0
ite The paramater PACKALG was set to 0 in the TG ... so in the TG ... so the ABIS was not reallythe ABIS was not really being optimized SOLUTION: CONDITIONS: PROCEDURE: Set the PACKALG to 1
being optimized SOLUTION: CONDITIONS: PROCEDURE: Set the PACKALG to 1 How to avoid Abis-Interface over Satellite overload Usage Count: 1 How to avoid Abis-Interface over Satellite overload Usage Count: 1 90%
90%
How to avoid Abis-Interface over Satellite overload Network: GSM Node: AXE BSC 0 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
8B TCH congestion after ABIS/IP swap ALARM: ABIS PATH OVERLOAD Abis path overloaoverloa d alarm for the concerned TG Abis over
d alarm for the concerned TG Abis over satellite overload IPLOSTPACKUL shows higsatellite overload IPLOSTPACKUL shows hig h valies as compared to LOSTDLPACK Configuration change The problem is caused by h valies as compared to LOSTDLPACK Configuration change The problem is caused by bad transmission on Abis. If the IP
bad transmission on Abis. If the IP transmission is causing a lot of packet lostransmission is causing a lot of packet los ses, the overload mechanism will trigger which will cause TCH congestion during 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 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
verload occur. PROCEDURE: 1. Make sure you have implemented all fixes in SCS9108SCS9108 63 . 2. Make sure you
63 . 2. Make sure you have the latest BTS software, which ncludes a fix have the latest BTS software, which ncludes a fix for Abisfor Abis over Satellite Check delivery note: 10945-LZY213440/8 3. Check the transmission over Satellite Check delivery note: 10945-LZY213440/8 3. Check the transmission for Abis.
for Abis.
Unable to make more than 26 calls in
Unable to make more than 26 calls in RBS Usage Count: 3RBS Usage Count: 3 88%
88%
Network: GSM Node: AXE BSC 07B RBS 2308
Network: GSM Node: AXE BSC 07B RBS 2308 Unable to make more than 26 calls Unable to make more than 26 calls in RBSin RBS Assignment command fails with No radio resource available No radio resource ava Assignment command fails with No radio resource available No radio resource ava ilable Pre-emption handling fails leading to assignment failure Abis path overlo ilable Pre-emption handling fails leading to assignment failure Abis path overlo ad alarm for the concerned TG SC
ad alarm for the concerned TG SC overload comes from PGW RP via signal CPXTGLOADoverload comes from PGW RP via signal CPXTGLOAD INF Parameters MBWUL MBWDL where set to a to
INF Parameters MBWUL MBWDL where set to a to low value MBWUL=400 and MBWDL=400 Slow value MBWUL=400 and MBWDL=400 S OLUTION: CONDITIONS: Alarm abis path
OLUTION: CONDITIONS: Alarm abis path overload received PROCEDURE: Check parameteoverload received PROCEDURE: Check paramete rs MBWUL and MBWDL with RRSGP:SCGR= ;
rs MBWUL and MBWDL with RRSGP:SCGR= ;
Set the parameters according to the guidelines by using The tool
Set the parameters according to the guidelines by using The tool for Abis over Ifor Abis over I P dimensioning 209/100 56-HSC 103 12/11 Uen B
P dimensioning 209/100 56-HSC 103 12/11 Uen B
High droprate for site connected over satellite Usage Count: 8 Network: GSM Feat 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
ure: Abis-Interface Over Satellite Node: AXE BSC 07B Node: AXE BSC 08A Node: AXENode: AXE BSC 08B Node: AXE BSC
BSC 08B Node: AXE BSC 09A Node: AXE BSC 09B Product Name: RHLAPD Product 09A Node: AXE BSC 09B Product Name: RHLAPD Product ID: CAID: CA AZ 107 7463 R6A05 Product ID: CAAZ 107
AZ 107 7463 R6A05 Product ID: CAAZ 107 7463 R7A01 Abis over satellite overload S7463 R7A01 Abis over satellite overload S DCCH setup successful rate low
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 0-3 0-4 0-5 0-6 0-7 0 1 2 3 4 5 RXOTS-67-1-6 RXOTS-RXOTS-67-1-67-1-7 RXOTS-RXOTS-67-1-67-4-0 RXOTS-RXOTS-67-1-67-4-1 RXOTS-RXOTS-67-1-67-4-2 RXOTS-RXOTS-67-1-67-4-3 RXOTS-RXOTS-67-1-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 67-8-2 67-8-3 67-8-4 67-8-5 67-8-6 RXOTS-67-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
END <rxapp:mo=rxotg-103; RADIO X-CEIVER ADMINISTRATION ABIS PATH STATUS MO RXOTGMO RXOTG -103 DEV RBLT2-1073 RBLT2-1074 RBLT2-1075 RBLT2-1076 RBLT2-1077 DCP 17 18 19 20 -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 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 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 M PLEX16 MPLEX16 MPLEX16 MPLEX32 UNDEF UNDEF UNDEF UNDEF 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 PLEX16 CONC CONC UNDEF UNDEF MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPL EX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UND EX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UND EF UNDEF UNDEF UNDEF MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 APSTATE SPEECH/DATA 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/ 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 DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPE ECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA
ECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATASPEECH/DATA SPEECH/DATA IDLE IDLE IDLE IDLE IDLE IDLE
IDLE IDLE IDLE IDLE IDLE IDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA CSPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA C F/TRXC SIGNAL TRXC SIGNAL IDLE
F/TRXC SIGNAL TRXC SIGNAL IDLE IDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DIDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEE 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 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
LE IDLE SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA 64K YES YESYES 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 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 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 NO NO NO NO NO TEI RBLT2-1078 RBLT2-1078 22 22 RBLT2-1079 RBLT2-1079 23 23 RBLT2-1080 RBLT2-1080 24 24 RBLT2-1081 RBLT2-1082 RBLT2-1083 RBLT2-1084 RBLT2-1085 RBLT2-1081 RBLT2-1082 RBLT2-1083 RBLT2-1084 RBLT2-1085 RBLT2-1086RBLT2-1086 25 26 27 28 29 30 25 26 27 28 29 30 RBLT2-1087 RBLT2-2544 RBLT2-2545 RBLT2-2546 RBLT2-2547 RBLT2-1087 RBLT2-2544 RBLT2-2545 RBLT2-2546 RBLT2-2547 31 302 303 304 305 31 302 303 304 305 61 0 61 0 8 1 8 1 9 2 9 2 10 3 10 3 11 11 RBLT2-2548 RBLT2-2548 306 306 RBLT2-2549 RBLT2-2549 307 307 RBLT2-2550 RBLT2-2550
308 308 RBLT2-2551 RBLT2-2552 RBLT2-2553 RBLT2-2554 RBLT2-2555 RBLT2-2551 RBLT2-2552 RBLT2-2553 RBLT2-2554 RBLT2-2555 309 310 311 312 313 309 310 311 312 313 RBLT2-2556 RBLT2-2556 314 314
RBLT2-2557 RBLT2-2557 315 315 RBLT2-2558 RBLT2-2558 316 316 RBLT2-2559 END RBLT2-2559 END 317 317
MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16
MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16MPLEX16 MPLEX16 MPLEX16 MPLEX16 MPLEX16 UNDEF
MPLEX16 UNDEF
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/DSPEECH/D ATA SPEECH/DATA SPEECH/DATA SPEECH/DATA SPEECH/DATA IDLE
ATA SPEECH/DATA SPEECH/DATA 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 The TF value must be like this:
The TF value must be like this: <rxmop:mo=rxotf-3; RADIO X-CEIVER ADMINISTRATIO<rxmop:mo=rxotf-3; RADIO X-CEIVER ADMINISTRATIONN MANAGED OBJECT DATA MO RXOTF-3 END <rxmop:mo=rxotf-103; RADIO X-CEIVER ADMINIST 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 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 578 TFCOMPPOS FSOFFSET NO TFAUTO TFMODE M SYNCSRC TFCOMPNEG DEFAULT TFCOMPPOS FS OFFSET TFAUTO NO
OFFSET TFAUTO NO
1. Check the following things : 1. Check
1. Check the following things : 1. Check routine E1 sync / check if OK routine E1 sync / check if OK with 1xE1with 1xE1 individually in a cabinet2. Block slave TG -
individually in a cabinet2. Block slave TG - put ESB A -> A put ESB A -> A port and then Debloport and then Deblo ck It.3. ESB cable in place :
ck It.3. ESB cable in place : Give proper TEI value for master and slave Give proper TEI value for master and slave TEI=62,TEI=62, 61 ; Check rxmop:mo=rxotf-xx; in both cabinets {master(M) in Master cabinet And 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
Slave(S) in slave cabinet}4 Ask for TFCOMP value from BTS team 5 PCM should beBTS team 5 PCM should be Cascaded in master cabinet and stand alone on slave cabinet in
Cascaded in master cabinet and stand alone on slave cabinet in IDB6 Check TG3 =IDB6 Check TG3 = 1..16 287..301 in order ; TG103 = 17..31
1..16 287..301 in order ; TG103 = 17..31 302..317 in order7. Then try No ESB cab302..317 in order7. Then try No ESB cab le and make both Cabinet as Stand Alone
le and make both Cabinet as Stand Alone ; 62, 62 [IDB manipulation required]8. R; 62, 62 [IDB manipulation required]8. R eload IDB in master Cabinet. Command RLCRP showing few FR &
eload IDB in master Cabinet. Command RLCRP showing few FR & its HR channels as Bits HR channels as B LOCK Usage Count: 5 60%
LOCK Usage Count: 5 60%
Network: GSM Node: AXE BSC R9.1 Node: AXE BSC
Network: GSM Node: AXE BSC R9.1 Node: AXE BSC R10 Node: AXE BSC R11 Software: AXR10 Node: AXE BSC R11 Software: AX E BSC R9.1 MD Software: AXE BSC
E BSC R9.1 MD Software: AXE BSC R10 MD Software: AXE BSC R11 MD R10 MD Software: AXE BSC R11 MD Command RLCRP shCommand RLCRP sh owing few FR & its HR
owing few FR & its HR channels as BLOCK Half Rate Channels not present in channels as BLOCK Half Rate Channels not present in CommanComman d RLCRP Alarm: ABIS PATH UNAVAILABLE HALF RATE leading to time
d RLCRP Alarm: ABIS PATH UNAVAILABLE HALF RATE leading to time slot going in unuslot going in unu sed condition Activation of new function or service-Half rate Implementation Eno sed condition Activation of new function or service-Half rate Implementation Eno ugh Time slots have not been reserved for EDGE
ugh Time slots have not been reserved for EDGE functionality SOLUTION: CONDITIONfunctionality SOLUTION: CONDITION S:The Following Conditions have been observed. 1) Command RLCRP shows as below 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
