Oss Commands Notes

Limited Internal
E 1 (95)
************************* BSC PRINTOUTS ********************************
e-remove
i-add
c-change
p-print
******************* BSC & CELL DATA PRINTOUTS **************************
CACLP; ! Time of the printouts!

RLTYP; ! Cell System Type!
RLLBP; ! Locating BSC Data! EVALTYPE: Ericsson 1 or 3, TINIT, TALLOC, TURGEN, TAAVELEN, THO, NHO, ASSOC, IBHO
RLDCP; ! Diff. Channel Allocation Data!
RLLSP; ! BSC Load Sharing Data! LSSTATE - must be ACTIVE for CLS to take effect in that BSC
RLOMP; ! Cell BSC Band Operating mode!
RLDEP:CELL=ALL; ! Definition of Cell! RLDEP:CELL=ALL,EXT; Description data for all external GSM cells defined in t
RLDEP:CELL=ALL,EX! -‘’-!
RLDEP:CELL=ALL,X ! -‘’-!
RLACP:CELL=ALL; ! Adaptive SDDCH Configuration!
RLCFP:CELL=ALL; ! Configurating Frequency Data! Check no of SDCCH, TN for SDCCH, CHGR hopping or not, HSN, SCTYPE - UL or OL, freque
RLCPP:CELL=ALL; ! Configurating Power Data! Max transmitted power: BSPWRB, BSPWRT for UL & OL
RLCPP:CELL=ALL,EX! -‘’-!
RLCHP:CELL=ALL; MAIO values
RLLHP:CELL=ALL; ! Locating Hierarchical Data! HCS
RLLHP:CELL=ALL,EXT
! -‘’-!
RLCXP:CELL=ALL; ! Configurating DTX DL!
RLCDP:CELL=ALL; ! Multiple Channel Allocation!
RLPCP:CELL=ALL; ! Dynamic MS PWR Cell Control!
RLBCP:CELL=ALL; ! Dynamic BTS PWR Cell Control!
RLIHP:CELL=ALL; ! Locating Intracell HO Data!
RLMFP:CELL=ALL; ! Measurement Frequencies! List all measurement frequencies in idle and active mode. Shows neighbours in BA and SA list
RLPBP:CELL=ALL; ! Handover Power Boost Data!
RLLOP:CELL=ALL; ! Cell Locating Data! BSPWR, BSTXPWR data
RLLUP:CELL=ALL; ! Locating Urgency Data!
RLLPP:CELL=ALL; ! Locating Penalty Data!
RLLFP:CELL=ALL; ! Locating Filter Data!
RLLDP:CELL=ALL; ! Cell Locating Disconnect Data!
RLSBP:CELL=ALL; ! System Info BCCH Data! Cell Bar CB, CBQ, CRO, TO, PT
RLSSP:CELL=ALL; ! System Info SACCH&BCCH Data!
RLOLP:CELL=ALL; ! Locating Overl. Subcell Data! LOL, LOLHYST, DTCB, TAOL - impowering for subcell change threshold when BSPW
RLLLP:CELL=ALL; ! Subcell Load Distr. Data!
RLDTP:CELL=ALL; ! Data Administration TSC!
RLSTP:CELL=ALL; ! Cell State! RLSTP:CELL=ALL,STATE=HALTED; To see HALTED cells
RLNRP:CELL=ALL; ! Neighbouring Relation!
RLSMP:CELL=ALL; ! System Info, BCCH Mess. Distr!
RLHPP:CELL=ALL; ! Cell Con. Of Cell to Ch. All.!
RLIMP:CELL=ALL; ! Cell Idle Channel Measurement!
RLLCP:CELL=ALL; ! Cell Load Sharing Data!
RLPRP:CELL=ALL; ! Diff. Chan. All. Prio. to RT!
RLPPP:PP=ALL; ! Diff. Chan. All. Pri. Profile!
RLDHP:CELL=ALL; ! Dynamic half rate info DHA
RLDMP:CELL=ALL; ! Dynamic HR/FR Mode Adaptation Data DMSUPP etc.
*************** ADDITIONAL RADIO RELATED PRINTOUTS ******************
CACLP;
RLVAP; ! Supervision of Alarm!
RLCAP; ! BSC Ciphering Algorithm!
RLVLP; ! Supervision of Logical Ch.!
RLSCP; ! Diff. Ch. Allocation Stat.!
RLBDP:CELL=ALL; ! Configuration BPC Data! Displays no of BPC, CS34 and EGPRS channels per CHGR in a cell
RLDGP:CELL=ALL; ! Definition of Channel Group!
RLCRP:CELL=ALL; ! Cell Resources! To check actual cell resources - no of BCCH, SDCCH, TCH; state:busy/idle;
RLSDP:CELL=ALL; ! Diff. Ch. All. Stat. Data! If all '0' - OML is down. Rlcrp:cell=all; will show resources for cells in the BSC in brief.
RLSLP:CELL=ALL; ! Superv. Of Log. Ch. Avail.!
RLLOP:CELL=ALL,EXT; ! Cell Locating data, external!
RLLAP:LAI=ALL; ! Cell Locating Area!
****************** X-CEIVER RELATED PRINTOUTS ***************************
RXTCP:MOTY=RXOTG; ! TG to Channel Group RBS 2000! (shows all the TG in a BSC, all the cell associated with each TG and the CHGR of th
RXTCP:MOTY=RXOTG,CELL=(xx); ! To check cell TG# (usually 1 TG represent 1 cabinet - hence can tell the cell is contained in which cabinet)
RXCDP:MO=RXOTG-(TG#); ! To check time slot functionality Displays RXOTX, RXORX and RXOTS data - ARFCN: HOP or Channel No.,
RXMOP:MOTY=RXOTG; ! Definition of MO, RBS 2000! RXMOP:MO=RXOTG-xx; To check parameter settings of cells/object (follow
RXMOP:MOTY=RXOTRX; ! -‘’- RBS 2000! RXMOP:MO=RXOTRX-xx-xx; To check parameter settings of cells/object (follow
RXMOP:MOTY=RXOTX; ! -‘’- RBS 2000! RXMOP:MO=RXOTX-xx-xx; To check parameter settings of cells/object (follow
RXMOP:MOTY=RXORX; ! -‘’- RBS 2000! RXMOP:MO=RXORX-xx-xx; To check parameter settings of cells/object (follow
RXMOP:MOTY=RXOTS; ! -‘’- RBS 2000! RXMOP:MO=RXOTS-xx-xx-xx; To check parameter settings of cells/object (follow
RXMDP:MOTY=RXOTRX; ! MO Device InformationRBS 2000RXMDP:MO=RXOTRX-xx; To check Device ID (RBLT-xxxx) for each TRX. E1
RXMSP:MOTY=RXOTRX; ! Status of MO RBS 2000! RXMSP:MO=RXOTRX-xx; To check status of device - TG, TRX etc - OPER o
Date: 6/1/2005
Rev: PA1
Sheet: OSS Commands
Limited Internal
E 2 (95)
RXASP:MOTY=RXOTG; ! Alarm Coordination D.RBS 2000! -0&&-7 0 to 7 selected

-0&-6 0 and 6 only selected
****************** TRANSCODER RELATED PRINTOUTS ***********************
CACLP;
RRLLP; ! Line Level Handling!
RRBSP; ! Radio Tr. Def. of BSCs in TRC!
RRTPP:TRAPOOL=AL! TRA Pool Handling!
RRMSP:TRAPOOL=AL! TRA Pool M. Hold Superv.!
RRMAP:TRAPOOL=AL! TRA Pool M. H. Superv. Alarm!
RRISP:TRAPOOL=ALL! TRA Pool Idle Supervision!
****************** BSC EXCHANGE DATA PRINTOUTS ***********************
CACLP;
RAEPP:ID=ALL; ! Radio Adm. Exch. Property! RAEPP:ID=CLSTIMEINTERVAL or GPRSPRIO or EBANDINCLUDED etc.
INMCT:SPG=0; ! IO Subs. Free File Management!
INMEP:NODE=A,IO=H! IO Subs. Medi Administration!
INMEP:NODE=B,IO=H! -‘’-!
INVOP; ! IO Subs. Vol. Administration!
INVOP:VOL=EXCHVO! -‘’-!
INVOP:VOL=OMFZLI ! -‘’-!
INVOP:VOL=RELVOL ! -‘’-!
INFIP; ! IO Subs. File Administration!
END;
IMMCT:SPG=0; ! IO Maint. Func. Ch. Transfer!
IMALP:NODE=A; ! IO Maint. Func. Node Alarm!
IMALP:NODE=B; ! -‘’-END!
-------------------------------------------------------------------------------------------
RXTCP:MO=RXOTG-(XX); To check site cell name

RXTCP:MOTY=RXOTG,CELL=(XX); To check site TG# (usually 1 TG represent 1 cabinet - hence can tell the cell is contained in which cabinet)
RXMFP:MO=RXOTG-(XX),FAULTY,SUBORD; 2 To check alarm type in specified RXOTG. RXOTG ID obtained from usage of earlier RXASP command. Re
RXELP:MO=RXOTG-(XX); Error lock/alarm (alarm history)
RLNRP:CELL=(XX),CELLR=(XX); Check all neighbours data OR specified neighbour only

RLMFC:CELL=(XX),MBCCHNO=(XX),LISTTYPE=(IDLE/ACTIVE),MRNIC; Both must do together in CHA !!!
RXASP:MOTY=RXOTG; To check site funtionali 1 Will display all RXOTG with alarm states in a BSC
RXCDP:MO=RXOTG-(XX); To check TG and cell status Displays RXOTX, RXORX and RXOTS data - ARFCN: HOP or Channel No., ICM
RXMOP:MO=RXOTX-(X)-(X); To check which cell is at fault To check data of objects
RXMSP:MO=RXOTG-(X); To check status of objects
RLCPC:CELL=(XX),SCTYPE=OL,BSPWRT=(X);
RLCPC:CELL=(XX),SCTYPE=UL,BSPWRT=(X);
RLCPC:CELL=(XX),BSPWRB=(X);
RLCHC:CELL=(XX),CHGR=(X),HOP=ON; To activate Hopping
RLLOC:CELL=(XX),FBUL and OL setting

RLOLC:CELL=(XX),LOUL and OL setting
RLCFP:CELL=(XX); To check cell frequency, no of SDCCH,

RLCRP:CELL=(XX); To check cell resources - no of BCCH, SDCCH, TCH; state:busy/idle; 64K channels; CHRATE:FR/HR; CHBAND:900,E900,1800;
If all '0' - OML is down. Rlcrp:cell=all; will show resources for cells in the BSC in brief.
RLBCP:CELL=(XX),DBPSTATE=ACTIVE/INACTIVE; To ON/OFF power control feature
RLBDP:CELL=(XX),CHGR=(X),NUMREQBPC=SYSDEF; To block chgr DCHNO ie. to test TRU by RLCFE
RLBCE/I:CELL=(XX); To active or inactive power control (DBPSTATE
--------------------------------------------------
Script to define ext cell in BSC level:
RLDEI:CELL=(XXXX),CSYSTYPE=GSM900/GSM1800,EXT;
RLDEC:CELL=(XXXX),CGI=(502-12-XXXX-XXXXX),BSIC=(XX),BCCHNO=(XX);
RLLOC:CELL=(XXXX),BSPWR=(XX),BSTXPWR=(XX),BSRXMIN=105,BSRXSUFF=150,MSRXMIN=105,MSRXSUFF=0,AW=ON,EXTPEN=ON;
RLLHC:CELL=(XXXX),LAYER=4,LAYERTHR=105;
RLCPC:CELL=(XXXX),MSTXPWR=33;
--------------------------------------------------
ALLIP:PRCA=43; Alarm printour categories. Refer to 'Alarm PRCA' category

ALLIP:ACL=a1; Followed by a2, a3 etc. - Used to check for such alarm conditions in BSC
a3 BER problem on E1 causing high SUDDEN drops can be due to this. But alarm can be intermittent, repeated checking required.
Using APG40 not APG30

alogfind -a 0800 -b 1300 -e 19970824 -g 19970825; Event Log History
alogfind -t mc -s ALLIP
Date: 6/1/2005
Rev: PA1
Sheet: OSS Commands
Limited Internal
E 3 (95)
alogfind -t alp
RLSTC:CELL=LIN1,STATE=ACTIVE; The command is used to change the state of a cell or channel group: ACTIVE or H
RLSTC:CELL=LIN2,CHGR=ALL,STATE=HALTED; No alarm triggered
RLSTC:CELL=LIN1,CHGR=0&1&3,STATE=ACTIVE;
RLSLE:CELL=XXXX; Disable alarm supervision

RXBLI:MO=RXOTRX-1-0,SUBORD,NOPRINT; orders the manual blocking of one or more Managed Object instances. Alarm trigerred
RXBLE:MO=RXOTS-27-5-0&&-7&RXOTS-27-6-0&&-7; This command orders the manual deblocking of one or more Managed Object instance
RLSLI:CELL=XXXX; Enable alarm supervision
Date: 6/1/2005
Rev: PA1
Sheet: OSS Commands
Limited Internal
E 4 (95)
GEN, TAAVELEN, THO, NHO, ASSOC, IBHOASS, IBHOSICH, IHOSICH for different bands
o take effect in that BSC
ata for all external GSM cells defined in the BSC is printed. CGI, Cell ID data, bsic
ping or not, HSN, SCTYPE - UL or OL, frequencies per CHGR
e mode. Shows neighbours in BA and SA list
ering for subcell change threshold when BSPWRB/T is changed
per CHGR in a cell
CH, TCH; state:busy/idle; 64K channels; CHRATE:FR/HR; CHBAND:900,E900,1800; ICMBAND:1-4.

ources for cells in the BSC in brief.
associated with each TG and the CHGR of the cells within the TG
cell is contained in which cabinet)
S data - ARFCN: HOP or Channel No., ICM - Yes or No, CHCOMB - BCCH, SDCCH8 or TCH, BSPWR
heck parameter settings of cells/object (following RXOTG value) in a BSC
heck parameter settings of cells/object (following RXOTG value) in a BSC. Will also show which CTU is assigned to which cell
heck parameter settings of cells/object (following RXOTG value) in a BSC. Will also show which CTU is assigned to which cell
heck Device ID (RBLT-xxxx) for each TRX. E1
heck status of device - TG, TRX etc - OPER or not
Date: 6/1/2005
Rev: PA1
Sheet: OSS Commands
Limited Internal
E 5 (95)
RSPRIO or EBANDINCLUDED etc. Shows data related to specified parameter
cell is contained in which cabinet)

d from usage of earlier RXASP command. Refer to GSM BTS Fault Codes for alarm explanation. Can also refer to CDD MO Dump.
or Channel No., ICM - Yes or No, CHCOMB - BCCH, SDCCH8 or TCH, BSPWR, SDCCH and TCH allocated to which frequency
FR/HR; CHBAND:900,E900,1800; ICMBAND:1-4.
ent, repeated checking required.
Date: 6/1/2005
Rev: PA1
Sheet: OSS Commands
Limited Internal
E 6 (95)
cell or channel group: ACTIVE or HALTED
Object instances. Alarm trigerred

r more Managed Object instance
Date: 6/1/2005
Rev: PA1
Sheet: OSS Commands
Limited Internal
E 7 (95)
TO DETERMINE WHETHER THERE IS SUFFICIENT E1 MAPPED TO A CELL FOR RADIO
Commands to be used highlighted in green
<RXTCP:MOTY=RXOTG,CELL=TSEEM11;
RADIO X-CEIVER ADMINISTRATION
TG TO CHANNEL GROUP CONNECTION DATA
MO CELL CHGR
RXOTG-110 TSEEM11 0
TSEEM11 1
TSEEM11 2
RXOTG-111 TSEEM11 3
END
MO CELL CHGR
RXOTG-110 TSEEM12 0
TSEEM12 1
TSEEM12 2
RXOTG-111 TSEEM12 3
END
MO CELL CHGR
RXOTG-110 TSEEM13 0
TSEEM13 1
TSEEM13 2
RXOTG-123 TSEEM13 3
END
<RXAPP:MO=RXOTG-110;
ABIS PATH STATUS
MO
RXOTG-110
DEV DCP APUSAGE APSTATE 64K

RBLT-3969 1 MPLEX16 SPEECH/DATA NO
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 8 (95)
MPLEX16 SPEECH/DATA NO
RBLT-3972 4 UNCONC TRXC SIGNAL NO
RBLT-3977 9 UNCONC CF/TRXC SIGNAL NO
MPLEX32 IDLE NO
RBLT-3991 23 UNDEF IDLE NO
Date: 6/1/2005
Rev: PA1
Limited Internal
E 9 (95)

RBLT-4003 289 UNCONC SPEECH/DATA YES
END
<RLBDP:CELL=TSEEM11;
CELL CONFIGURATION BPC DATA
CELL
TSEEM11
Date: 6/1/2005
Rev: PA1
Limited Internal
E 10 (95)
CHGR NUMREQBPC NUMREQEGPRSBPCNUMREQCS3CS4BPCTN7BCCH

0 8 4 2 EGPRS
1 16 0 0
2 8 0 0
3 32 0 0
END
<RADEP:DEV=RBLT-4022;
DEVICE DATA IN BSC
DEV SNT/DEVP
RBLT-4022 ETRBLT-125
DEV MISC1 MISC2 MISC3 MISC4
RBLT-4022 0
END
<NTCOP:SNT=ETRBLT-125;
SWITCHING NETWORK TERMINAL CONNECTION DATA
SNT SNTV SNTP DIP DEV

ETRBLT-125 1 MUX3-22-1 125RBLT RBLT-4000&&-4031
END
RXAPI:MO=RXOTG-123,DEV=RBLT-4022&&-4027,DCP=22&&27;
ABIS PATH RESULT
MO
RXOTG-123
DEV DCP RESULT

RBLT-4022 22 EXECUTED
END
Date: 6/1/2005
Rev: PA1
Limited Internal
E 11 (95)
RXAPE:MO=RXOTG-123,DCP=22&&27;
Date: 6/1/2005
Rev: PA1
Limited Internal
E 12 (95)
PPED TO A CELL FOR RADIO UPGRADES/ EDGE-GPRS CS3 4 EXPANSION
This would help determine the number of cabinets in use at a site. Usually 1 RXOTG would be assigned to 1 cabinet but o
certain occassions like a microcell with more than 1 RBS 2308, a single RXOTG assigned only is possible.
Notice that there are 3 cabinets in use for this site - RXOTG-110, 111 and 123
If we are to verify whether there is sufficient E1 timeslots for additional EDGE, GPRS CS34 timeslots we would only need t
look at the RXOTG ID in use for channel group 0 and 1. We would then have to verify whether there are any idle E1 timesl
available in this cabinets (Channel group 0 and 1 = using PGSM)
This will display all E1timeslots / ABIS paths assigned to the specified RXOTG
Each E1 timeslot has a device ID
TEI
Date: 6/1/2005
Rev: PA1
Limited Internal
E 13 (95)
In use for speech
10 Signalling channel for TRX. For UNCONCENTRATED method, 3 E1 timeslots are required for
each TRX to function. The TEI value of '10' represents the TRX number in the cabinet.
7
6
5
62 9
8
4
3
2
1
0
This IDLE timeslot can be used
Date: 6/1/2005
Rev: PA1
Limited Internal
E 14 (95)
11
This slots are in use for either GPRS CS3/4 or EDGE. 'YES' noted under 64K column to
indicate this. To determine how many CS3/4 or EDGE timeslots are in use per cell,
use the RLBDP command. Each EDGE or CS3/4 TRX timeslot takes up 1 E1 timeslot
Shows the number of EDGE and CS34 timeslots in a cell
Date: 6/1/2005
Rev: PA1
Limited Internal
E 15 (95)
TN7BCCH
This will display the E1 ID for the E1 timeslot labelled RBLT-4022
MUP
22054
ADMSTATE
EM SNT S
C C C
This will allow us to identify any E1 timeslots/ ABIS paths that have not been initiated. Without
initiation, the E1 slots cannot be seen after using the RXAPP command. These slots are actually
idle and available for use.
RBLT-4000&&-4031
If E1 timeslots with the following stated ID s are not shown using the RXAPP command
and are not found in the 2nd cabinet (RXOTG-111), they are most likely not intiated
To define one or more Abis paths between the Base Station Controller (BSC) and the Base Transceiver Station
A followup run of the RXAPP command will display the following E1 timeslots in the IDLE
state ready for use.
Date: 6/1/2005
Rev: PA1
Limited Internal
E 16 (95)
This will delete ABIS paths btw the BSC and BTS for a specified TG
Date: 6/1/2005
Rev: PA1
Limited Internal
E 17 (95)
ld be assigned to 1 cabinet but on

d only is possible.
34 timeslots we would only need to

ether there are any idle E1 timeslots
Date: 6/1/2005
Rev: PA1
Limited Internal
E 18 (95)
1 timeslots are required for

mber in the cabinet.
Date: 6/1/2005
Rev: PA1
Limited Internal
E 19 (95)
under 64K column to

e in use per cell,
es up 1 E1 timeslot
Date: 6/1/2005
Rev: PA1
Limited Internal
E 20 (95)
nitiated. Without
e slots are actually
and the Base Transceiver Station (BTS).
Date: 6/1/2005
Rev: PA1
Limited Internal
E 21 (95)
Frame Slip (E1) should be ideally 0. If higher, it may cause SUDDEN DROPS or OTHER DROPS to increase.
RXTCP:MOTY=RXOTG,CELL=PEMAM11;
RXAPP:MO=RXOTG-XX&-XX;
RADEP:DEV=RBLT2-XXX&-XXXX; --- Find ETM#
NTCOP:SNT=ETM2-4;
DTQUP:DIP=#RBL2&#RBL2;
Check under Frame slips, column SFV. If not equal to 0, then frame slips exist. ALEX has explanation for all abbv. - look under DTQUP command
*** Connected to NILA08 ***

<RXTCP:MOTY=RXOTG,CELL=HOREM11;
TG TO CHANNEL GROUP CONNECTDATA
MO CELL CHGR
RXOTG-10 HOREM11 0
HOREM11 1
RXOTG-11 HOREM11 3
END
<RXAPP:MO=RXOTG-10&-11;
ABIS PATH STATUS
MO
RXOTG-10
DEV DCP APUSAGE APSTATE 64K TEI

RBLT2-801 1 UNCONC TRXC SIGNAL NO 10
RBLT2-809 9 MPLEX16 SPEECH/DATA NO
MPLEX32 IDLE NO
RBLT2-814 14 UNDEF IDLE NO
RBLT2-820 20 UNCONC CF/TRXC SIGNAL NO 62 9
RBLT2-828 28 UNCONC SPEECH/DATA YES
MO
RXOTG-11
DEV DCP APUSAGE APSTATE 64K TEI

Date: 6/1/2005
Rev: PA1
Sheet: Frame Slip Verification
Limited Internal
E 22 (95)
RBLT2-885 21 UNCONC CF/TRXC SIGNAL NO 62 11
END
<RADEP:DEV=RBLT2-865&-885;
DEVICE DATA IN BSC
DEV SNT/DEVP MUP

RBLT2-865 ETM2-3 24832
RBLT2-885 ETM2-3 29952
DEV MISC1 MISC2 MISC3 MISC4 ADMSTATE

EM SNT S
RBLT2-865 5C C C
RBLT2-885 5C C C
DEV SNTINL
RBLT2-865 0
RBLT2-885 0
END
<NTCOP:SNT=ETM2-3;
SNT SNTV SNTP DIP DEV SNTINL

ETM2-3 1 XM-0-1-6 27RBL2 RBLT2-864 0
28RBL2 RBLT2-896&&-927 1
29RBL2 RBLT2-928&&-959 2
30RBL2 RBLT2-960&&-991 3
31RBL2 RBLT2-992&&-1023 4
32RBL2 RBLT2-1024&&-1055 5
33RBL2 RBLT2-1056&&-1087 6
34RBL2 RBLT2-1088&&-1119 7
35RBL2 RBLT2-1120&&-1151 8
36RBL2 RBLT2-1152&&-1183 9
37RBL2 RBLT2-1184&&-1215 10
38RBL2 RBLT2-1216&&-1247 11
39RBL2 RBLT2-1248&&-1279 12
40RBL2 RBLT2-1280&&-1311 13
41RBL2 RBLT2-1312&&-1343 14
42RBL2 RBLT2-1344&&-1375 15
43RBL2 RBLT2-1376&&-1407 16
44RBL2 RBLT2-1408&&-1439 17
45RBL2 RBLT2-1440&&-1471 18
46RBL2 RBLT2-1472&&-1503 19
47RBL2 RBLT2-1504&&-1535 20
48RBL2 RBLT2-1536&&-1567 21
49RBL2 RBLT2-1568&&-1599 22
50RBL2 RBLT2-1600&&-1631 23
51RBL2 RBLT2-1632&&-1663 24
52RBL2 RBLT2-1664&&-1695 25
53RBL2 RBLT2-1696&&-1727 26
54RBL2 RBLT2-1728&&-1759 27
55RBL2 RBLT2-1760&&-1791 28
56RBL2 RBLT2-1792&&-1823 29
57RBL2 RBLT2-1824&&-1855 30
58RBL2 RBLT2-1856&&-1887 31
59RBL2 RBLT2-1888&&-1919 32
60RBL2 RBLT2-1920&&-1951 33
61RBL2 RBLT2-1952&&-1983 34
62RBL2 RBLT2-1984&&-2015 35
63RBL2 RBLT2-2016&&-2047 36
64RBL2 RBLT2-2048&&-2079 37
65RBL2 RBLT2-2080&&-2111 38
66RBL2 RBLT2-2112&&-2143 39
67RBL2 RBLT2-2144&&-2175 40
68RBL2 RBLT2-2176&&-2207 41
69RBL2 RBLT2-2208&&-2239 42
70RBL2 RBLT2-2240&&-2271 43
71RBL2 RBLT2-2272&&-2303 44
72RBL2 RBLT2-2304&&-2335 45
73RBL2 RBLT2-2336&&-2367 46
74RBL2 RBLT2-2368&&-2399 47
75RBL2 RBLT2-2400&&-2431 48
76RBL2 RBLT2-2432&&-2463 49
77RBL2 RBLT2-2464&&-2495 50
78RBL2 RBLT2-2496&&-2527 51
79RBL2 RBLT2-2528&&-2559 52
80RBL2 RBLT2-2560&&-2591 53
81RBL2 RBLT2-2592&&-2623 54
82RBL2 RBLT2-2624&&-2655 55
83RBL2 RBLT2-2656&&-2687 56
84RBL2 RBLT2-2688&&-2719 57
85RBL2 RBLT2-2720&&-2751 58
86RBL2 RBLT2-2752&&-2783 59
87RBL2 RBLT2-2784&&-2815 60
88RBL2 RBLT2-2816&&-2847 61
89RBL2 RBLT2-2848&&-2879 62
XM-0-1-17
SNT EQLEV PROT SDIP SUBSNT DEFPST SNTP MODE

ETM2-3 1 3ETM2 0 XM-0-1-6 2048
1 XM-0-1-17 0
END
<DTQUP:DIP=27RBL2;
DIGITAL PATH QUALITY
UNACCEPTABLE PERFORMANCE LEVEL
INCOMING DIRECTION
DIP SECTION T1 N-ES N-SES N-UAS N-UAV SLIP SMI

27RBL2 10 0 0 0 0 0 0
Date: 6/1/2005
Rev: PA1
Limited Internal
E 23 (95)
OUTGOING DIRECTION
DIP SECTION T1 F-ES F-SES F-UAS F-UAV SMI

27RBL2 10 0 0 0 0 0
DEGRADED PERFORMANCE LEVEL
INCOMING DIRECTION

27RBL2 19 0 0 0 0 0 0
OUTGOING DIRECTION

27RBL2 19 0 0 0 0 0
FRAME SLIPS
DIP SECTION SFV SFTI

27RBL2 0 24
END
<RADEP:DEV=RBLT2-801&-846;
DEVICE DATA IN BSC
DEV SNT/DEVP MUP

RBLT2-801 ETM2-2 16767
RBLT2-846 ETM2-2 20159
DEV MISC1 MISC2 MISC3 MISC4 ADMSTATE

EM SNT S
RBLT2-801 5C C C
RBLT2-846 9C C C
DEV SNTINL
RBLT2-801 61
RBLT2-846 62
END
<NTCOP:SNT=ETM2-2;
SNT SNTV SNTP DIP DEV SNTINL

ETM2-2 1 XM-0-1-2 126RAL2 RALT2-403 0
127RAL2 RALT2-4064&&-4095 1
128RAL2 RALT2-4096&&-4127 2
129RAL2 RALT2-4128&&-4159 3
130RAL2 RALT2-4160&&-4191 4
131RAL2 RALT2-4192&&-4223 5
132RAL2 RALT2-4224&&-4255 6
133RAL2 RALT2-4256&&-4287 7
134RAL2 RALT2-4288&&-4319 8
135RAL2 RALT2-4320&&-4351 9
136RAL2 RALT2-4352&&-4383 10
137RAL2 RALT2-4384&&-4415 11
138RAL2 RALT2-4416&&-4447 12
139RAL2 RALT2-4448&&-4479 13
140RAL2 RALT2-4480&&-4511 14
141RAL2 RALT2-4512&&-4543 15
142RAL2 RALT2-4544&&-4575 16
143RAL2 RALT2-4576&&-4607 17
144RAL2 RALT2-4608&&-4639 18
145RAL2 RALT2-4640&&-4671 19
146RAL2 RALT2-4672&&-4703 20
147RAL2 RALT2-4704&&-4735 21
148RAL2 RALT2-4736&&-4767 22
149RAL2 RALT2-4768&&-4799 23
150RAL2 RALT2-4800&&-4831 24
151RAL2 RALT2-4832&&-4863 25
152RAL2 RALT2-4864&&-4895 26
153RAL2 RALT2-4896&&-4927 27
154RAL2 RALT2-4928&&-4959 28
155RAL2 RALT2-4960&&-4991 29
156RAL2 RALT2-4992&&-5023 30
157RAL2 RALT2-5024&&-5055 31
0RTG2 RTGLT2-0&&-31 32
1RTG2 RTGLT2-32&&-63 33
2RTG2 RTGLT2-64&&-95 34
3RTG2 RTGLT2-96&&-127 35
0RBL2 RBLT2-0&&-31 36
1RBL2 RBLT2-32&&-63 37
2RBL2 RBLT2-64&&-95 38
3RBL2 RBLT2-96&&-127 39
4RBL2 RBLT2-128&&-159 40
5RBL2 RBLT2-160&&-191 41
6RBL2 RBLT2-192&&-223 42
7RBL2 RBLT2-224&&-255 43
8RBL2 RBLT2-256&&-287 44
9RBL2 RBLT2-288&&-319 45
10RBL2 RBLT2-320&&-351 46
11RBL2 RBLT2-352&&-383 47
12RBL2 RBLT2-384&&-415 48
13RBL2 RBLT2-416&&-447 49
14RBL2 RBLT2-448&&-479 50
15RBL2 RBLT2-480&&-511 51
16RBL2 RBLT2-512&&-543 52
17RBL2 RBLT2-544&&-575 53
18RBL2 RBLT2-576&&-607 54
19RBL2 RBLT2-608&&-639 55
20RBL2 RBLT2-640&&-671 56
21RBL2 RBLT2-672&&-703 57
22RBL2 RBLT2-704&&-735 58
23RBL2 RBLT2-736&&-767 59
24RBL2 RBLT2-768&&-799 60
25RBL2 RBLT2-800&&-831 61
26RBL2 RBLT2-832&&-863 62
XM-0-1-13
SNT EQLEV PROT SDIP SUBSNT DEFPST SNTP MODE

ETM2-2 1 2ETM2 0 XM-0-1-2 2048
1 XM-0-1-13 0
END
<DTQUP:DIP=25RBL2&26RBL2;
DIGITAL PATH QUALITY
INCOMING DIRECTION

25RBL2 11 0 0 0 0 0 0
OUTGOING DIRECTION

25RBL2 11 0 0 0 0 0
INCOMING DIRECTION
Date: 6/1/2005
Rev: PA1
Limited Internal
E 24 (95)
25RBL2 19 0 0 0 0 0 0
OUTGOING DIRECTION

25RBL2 19 0 0 0 0 0
FRAME SLIPS

25RBL2 0 24
INCOMING DIRECTION

26RBL2 11 0 0 0 0 0 0
OUTGOING DIRECTION

26RBL2 11 0 0 0 0 0
INCOMING DIRECTION

26RBL2 19 0 0 0 0 0 0
OUTGOING DIRECTION

26RBL2 19 0 0 0 0 0
FRAME SLIPS

26RBL2 0 24
END
<
Date: 6/1/2005
Rev: PA1
Limited Internal
E 25 (95)
HOW TO SHOW WHICH AIR INTERFACE TIMESLOT IS ASSIGNED TO WHICH E1 TIMESLOT?
RXTCP:MOTY=RXOTG,CELL=(xx); To determine the cell is assigne

RXMOP:MOTY=RXOTRX-xx; OR RXMOP:MOTY=RXOTX-xx; After finding the RXOTG, find w
RXMDP:MOTY=RXOTS-Tg-Trx-0&&-7; To check object device informa
HOW TO INITIATE A CTR/CER/MTR AND EXTRACT THE DATA FOR POST PROCESSING
After login to OSSRC,

Right click, search for the 'Performance Management Recording' (PMR) tool and select it.
There are difficulties in using the PMR tool in Windows NT - Tab commands at the top are not selectable. Windows XP fun
CTR/ CER
Recording is initiated in the PMR tool. Alternatively, it can be initiated through CHT, using commands such as RATRI etc.
Once the status of the initiated CTR/ CER is completed, (status shown as 'Ready' or 'Warning'), the file needs to be import
The option 'imported' is available. Select the path where the file initiated is stored and select it. Sometimes recordings trigg
Click on completed recordings to view messages on it. Also, the recording may display 0 file size, events and recorded me
but if this happens as well after the import - recording errors exist. Once the import is successful, the raw file can be extrac
FTP to 10.200.61.104 - location of Ericsson OSSRC which contains the PMR tool and its stored data and search under thi
\ossrc\var\opt\ericsson\nms_rnr_pmr\data\userfiles Usually this path unless otherwise specified
Raw file can be opened using Excel.
MTR
To determine the IP address of the BSC where the recordings are stored, several commands need to be keyed in in the 'C
<space>cap_pdb_cat_map<space>eac_esi_map<space>|<space>grep<BSCName>
The above command will detail the IPs for the BSC specified. Use FTP and 'mget' command to extract the file from the sto
The files should be extracted to the OSSRC address, whether into your home folder or 'userfiles' folder for PMR recordings
In order to find out where the files are stored in the BSC, use the following commands at CHA:
aploc;
afpls -l <entry>; entry = MTRFIL00 etc This command tells u where the files are stored. In which ossdest in a particu
After that, at the 'Command Terminal' ftp to the ip address of the wanted BSC. User ID : ossuser Passwd : ossuser1
The MTR, CTR, CER files are usually stored under /CDH/ossdest00 - 05/Ready/
dir This shows the date the file was created as well as its size. Files with errors may have a size of '0'
Similar to CTR/CER, need to import the MTR in PMR to process the data. The data then needs to be exported into an 'Exc
Right click and choose 'Command Terminal' to open a window in the OSSRC. Use the following commands:
HIGH SUDDEN DROPS

Causes:
Frame slip
High BER on E1 Verified by checking for a3 alarms and looking at event log repeatedly. Highlight to Tech Ops to requ
High InterMSC Handover Congestion (TSTN diagram with TechOps, so RTO still has to contact Tech Op
Date: 6/1/2005
Rev: PA1
Sheet: Extra
Limited Internal
E 26 (95)
WHICH E1 TIMESLOT?
To determine the cell is assigned to which RXOTG/cabinet. More than 1 cell can share the same cabinet
After finding the RXOTG, find which TRX/TX in the cabinet is assigned to the cell u are looking at
To check object device information - E1 timeslot ID for each TCH timeslot. Each E1 timeslot can support up to 4 TCH timeslot.
OST PROCESSING
not selectable. Windows XP functions ok.
commands such as RATRI etc.

ning'), the file needs to be imported to 'process' the data and make it viewable.
ect it. Sometimes recordings triggerred will be in error.
ile size, events and recorded messages. This is such before the import is done
cessful, the raw file can be extracted and viewed using Excel.
stored data and search under this path:
ess otherwise specified
nds need to be keyed in in the 'Command Terminal' window.
and to extract the file from the stored location in the IP address
serfiles' folder for PMR recordings.
red. In which ossdest in a particular BSC where the MTRs are initiated.
ssuser Passwd : ossuser1
ay have a size of '0'
needs to be exported into an 'Excel' viewable format.
owing commands:
dly. Highlight to Tech Ops to request RTO assistance to do BER test

o RTO still has to contact Tech Ops for it.)
Date: 6/1/2005
Rev: PA1
Sheet: Extra
Limited Internal
E 27 (95)
port up to 4 TCH timeslot.
Date: 6/1/2005
Rev: PA1
Sheet: Extra
PRCA VALUES TO BE USED FOR COMMAND 'ALLIP:PRCA="XX";'
2 Printout Categories
2.1 PRCA Values for APZ (Numerical Order)
Table 1 PRCA Values for APZ (Numerical Order)

PRCA PRCA
Value Symbol
32 535
32 540
32 541
32 545
32 547
32 548
32 550
33 501
35 503
36 504
37 519
37 519
38 520
39 521
40 522
41 523
42 524
43 525
44 526
45 527
46 528
47 516
50 601
51 529
52 530
53 531
54 532
55 533
56 534
60 542
61 546
61 549
62 551
62 552
543
544
2.2 Description of PRCA for APZ (Alphabetical Order)

Table 2 PRCA Values for APZ (Alphabetical Order)
PRCA PRCA
Value Symbol
37 519
38 520
39 521
40 522
41 523
42 524
43 525
44 526
45 527
46 528
51 529
52 530
53 531
54 532
55 533
56 534
36 504
47 516
543
544
37 519
32 535
32 545
61 546
32 550
35 503
50 601
32 541
33 501
62 551
62 552
32 540
32 547
32 548
61 549
60 542
UES TO BE USED FOR COMMAND 'ALLIP:PRCA="XX";'
Values for APZ (Numerical Order)
RCA Values for APZ (Numerical Order)

Slogan/Description Block
EMG EMRP RESTART DATA EMGDU
RESTART DATA MISEDS
PREORDERED ADJUSTMENT OF SYSTEM CLOCK EXECUTED JOB
EMG EMRPD RESTART DATA EMGDU
RP RESTART DATA RPDU
RPD RESTART DATA RPDU
ERROR INTERRUPT DATA MISEDHD

APZ 212 20
PROCESSOR STATISTICS MEO
HB AL
Heartbeat to AOM
ALARM LIST ALA
CONGESTION IN ALARM SYSTEM ALA
ALARM ALA
Alarm category 0, Normally not used
ALARM ALA
Alarm category 1, Processors: CP, RP
ALARM ALA
Alarm category 2, IO device
ALARM ALA
Alarm category 3, Switching part
ALARM ALA
Alarm category 4, Switch
ALARM ALA
Alarm category 5, Switching devices
ALARM ALA
Alarm category 6, Subscriber lines
ALARM ALA
Alarm category 7, Load: processors, switching equipment
ALARM ALA
Alarm category 8, Power alarm
ALARM ALA
Alarm category 9, House alarm
ALARM STATUS AL
MCS AUTHORITY COMMAND INPUT RESTRICTED OIDC
ALARM ALA
Alarm category 10 (A) Alarm from subordinate exchange
ALARM ALA
Alarm category 11 (B) Cable alarm
ALARM ALA
Alarm category 12 (C) Spare
ALARM ALA
Alarm category 13 (D) Spare
ALARM ALA
Alarm category 14 (E) Spare
ALARM ALA
Alarm category 15 (F)
SCHEDULED ALARM STATUS REPORT ALA
EMG EMRPD RESTART INFO EMGDU
RPD RESTART INFO RPDU
PROGRAM STORE BUILD LEVEL DETAILS AFBLA
PROGRAM STORE BUILD LEVEL SURVEY AFBLA
Cancelled
Cancelled
ption of PRCA for APZ (Alphabetical Order)

RCA Values for APZ (Alphabetical Order)
Slogan/Description Block
ALARM ALA
Alarm category 0, Normally not used
ALARM ALA
Alarm category 1, Processors: CP, RP
ALARM ALA
Alarm category 2, IO device
ALARM ALA
Alarm category 3, Switching part
ALARM ALA
Alarm category 4, Switch
ALARM ALA
Alarm category 5, Switching devices
ALARM ALA
Alarm category 6, Subscriber lines
ALARM ALA
Alarm category 7, Load: processors, switching equipment
ALARM ALA
Alarm category 8, Power alarm
ALARM ALA
Alarm category 9, House alarm
ALARM ALA
Alarm category 10 (A) Alarm from subordinate exchange
ALARM ALA
Alarm category 11 (B) Cable alarm
ALARM ALA
Alarm category 12 (C) Spare
ALARM ALA
Alarm category 13 (D) Spare
ALARM ALA
Alarm category 14 (E) Spare
ALARM ALA
Alarm category 15 (F)
ALARM LIST ALA

ALARM STATUS AL
Cancelled
Cancelled
CONGESTION IN ALARM SYSTEM ALA
EMG EMRP RESTART DATA EMGDU
EMG EMRPD RESTART DATA EMGDU
EMG EMRPD RESTART INFO EMGDU
ERROR INTERRUPT DATA MISEDHD

APZ 212 20
HB AL
Heartbeat to AOM
MCS AUTHORITY COMMAND INPUT RESTRICTED OIDC
PREORDERED ADJUSTMENT OF SYSTEM CLOCK EXECUTED JOB
PROCESSOR STATISTICS MEO
PROGRAM STORE BUILD LEVEL DETAILS AFBLA
PROGRAM STORE BUILD LEVEL SURVEY AFBLA
RESTART DATA MISEDS
RP RESTART DATA RPDU
RPD RESTART DATA RPDU
RPD RESTART INFO RPDU
SCHEDULED ALARM STATUS REPORT ALA

ANSWER PRINTOUT TO COMMAND RXASP
RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT ALARM SITUATIONS
1 Format
1.1 Printout

MANAGED OBJECT ALARM SITUATIONS
/
|/
||MO EMG RSITE ALARM SITUAT
||mo-G01 [emg] rsite [alarm situat
|| .
|| .
|| .
||mo-G01 [emg] rsite [alarm situat
|\
+
|/
||MO RSITE ALARM SITUAT
||mo-G12 rsite [alarm situat
|| .
|| .
|| .
||mo-G12 rsite [alarm situat
|\
\
[NONE]
[NO ALARM SITUATIONS]
[EOT DURING PRINTOUT]
/ \
|FAULT INTERRUPT|
|fault type |
\ /
END
1.2 Parameters
alarm situation The alarm situation provides the type of fault in the ind
The following alarm situations are possible (listed in alp
ABIS PATH UNAVAIL

alarm situation
No transmission device exists between the BSC and th
BTS EXT AFFECTED

A fault exists in a piece of equipment external to the B
BTS EXT UNAFFECTED

A fault exists in a piece of equipment external to the B
BTS INT AFFECTED

A fault exists in a piece of equipment internal to the B
BTS INT UNAFFECTED

A fault exists in a piece of equipment internal to the B
CON QUEUE CONGESTION

At least one of the LAPD Concentrator concentration o
LMT INTERVENTION
Local maintenance activities being performed in the B
LOCAL MODE
The BTS equipment is in Local Mode or the BTS equip
LOOP TEST FAILED

Test of the traffic carrying capabilities of the TS has fa
MAINS FAILURE
An external power fault has been detected.
OML FAULT
A fault exists in the communications link between the
OPERATOR CONDITION
An abnormal condition has been detected in the BTS s
PERMANENT FAULT
A managed object is classified as being permanently f
TGC FAULT
No active TGC application exists in the transceiver gro
TS SYNC FAULT
Synchronization lost on uplink or downlink TRAU chan
emg Extension module group
Identifies the Transmission Remote Interface used for t

mo-G01 Managed object instance in BTS logical model G01.
mo-G12 Managed object instance in BTS logical model G12.
rsite Radio site identity
rsite
Identity of the radio site where the TG is located.
EOT DURING PRINTOUT

The operator has cancelled the printout
NO ALARM SITUATIONS
No alarm situations in the specified MOTY.
NONE
No data are to be printed
FAULT INTERRUPT
fault type
Fault interruption during printout
Fault type:
FORMAT ERROR
Format error
UNREASONABLE VALUE
details
Unreasonable value
FAULT CODE 2
CANNOT MIX DIFFERENT BTS LOGICAL MODELS
details
The MO parameter specified managed object instances from more than one
FAULT CODE 6
MO NOT IN VALID STATE
details
The managed object is not in an appropriate state. Command is not valid fo
2 Function
This printout is an answer printout to the command RXASP. All of the outstan
If particular managed object instances of a managed object type are requeste
If all managed object instances of a managed object type are requested, only
In either of the two cases, if the managed object instance TG is specified then
Managed object instances will be printed in order of the priority of the alarm s
Note: The printout will show faults which are superior object b
NONE is obtained if there is no defined managed object for the specified MOT
NO ALARM SITUATIONS is obtained if there are defined managed objects for
3 Action
This printout requires no action.
4 Printout Type
Answer printout
5 Printout Blocks
RXEALCRXOALC
6 Glossary
This document contains no glossary entries.
7 References
This document has no references.

ANSWER PRINTOUT TO COMMAND RXM
CT ALARM SITUATIONS RADIO X-CEIVER ADMINISTRATION MAN
1 Format
1.1 Printout
1.1.1 Format 1

\ MANAGED OBJECT FAULT INFORMATIO
\|
ALARM SITUATION || MO BTSSWVER
[alarm situation]|| mo-G01 [btsswver]
||
||
||
[alarm situation]||
/|
+ STATE BLSTATE INTERCNT CONCN
\| state [blstate][intercnt][concn
ALARM SITUATION || / \
[alarm situation]|| |FAULT CODES CLASS 1A|
|| |fcode1a ... fcode1a |
|| | . . |
|| | . . |
[alarm situation]|| | . . |
/| |fcode1a ... fcode1a |
/ \ /
/ \
|FAULT CODES CLASS 1B|
|fcode1b ... fcode1b |
| . . |
| . . |
| . . |
\ /
/ \
|FAULT CODES CLASS 2A|
|fcode2a ... fcode2a |
| . . |
| . . |
| . . |
\ /
the type of fault in the indicated managed object. / \
|EXTERNAL FAULT CODES CLASS 1B|
s are possible (listed in alphabetical order): |extfcode1b ... extfcode1b |
| . . |
| . . |
sts between the BSC and the BTS. | . . |
|extfcode1b ... extfcode1b |
\ /
equipment external to the BTS that leads to that equipment not being able to carr / \
equipment external to the BTS that does not directly interfere with its operational| . . |
| . . |
| . . |
equipment internal to the BTS that leads to that equipment not being able to carr|extfcode2b ... extfcode2b |
\ /
/ \
equipment internal to the BTS that does not directly interfere with its operational |REPLACEMENT UNITS|
|repl .... repl |
| . . |
oncentrator concentration outlet queues has reached an unacceptable filling level | . . |
| . . |
|repl .... repl |
es being performed in the BTS. \ /
.
.
ocal Mode or the BTS equipment has subsequently changed from Local to Remote .
MO BTSSWVER
mo-G01 [btsswver]
capabilities of the TS has failed.
s been detected.
STATE BLSTATE INTERCNT CONCN

unications link between the BSC and the BTS. state [blstate][intercnt][concn
/ \
been detected in the BTS site. |fcode1a ... fcode1a |
| . . |
| . . |
fied as being permanently faulty when fault situations have occurred, and have be| . . |
\ /
exists in the transceiver group. / \
link or downlink TRAU channels. | . . |
| . . |
| . . |
Remote Interface used for the Transceiver Group. \ /
BTS logical model G01. / \
BTS logical model G12. |FAULT CODES CLASS 2A|
| . . |
ere the TG is located. | . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
|REPLACEMENT UNITS|
|repl .... repl |
| . . |
| . . |
| . . |
|repl .... repl |
\ /
[NONE]
tances from more than one BTS logical model. [EOT DURING PRINTOUT]
/ \
|FAULT INTERRUPT|
|fault type |
\ /
te. Command is not valid for MO in state DEF.
END
1.1.2 Format 2
d RXASP. All of the outstanding alarm situations are printed for the specified managed object instances.
ed object type are requested, these will always be included in the printout if defi MANAGED OBJECT FAULT INFORMATIO
ct type are requested, only managed object instances with an alarm situation will MO BTSSWVER
mo-G12 [btsswver]
nstance TG is specified then subordinate managed object instances with an alarm situation will also be included in the p
RU RUREVISION
of the priority of the alarm situation. [ru][rurevision]
which are superior object blocked, if such faults exist that would normally not b RUPOSITION
bject for the specified MOTY. [ruposition]
.
fined managed objects for the specified MOTY but there are no alarms. .
.
RU RUREVISION
[ru][rurevision]
RUPOSITION
[ruposition]

state [blstate][intercnt][concn
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
|REPLACEMENT UNITS|
|repl .... repl |
| . . |
| . . |
| . . |
|repl .... repl |
\ /
.
.
.
MO BTSSWVER
mo-G12 [btsswver]
RU RUREVISION
[ru][rurevision]
RUPOSITION
[ruposition]
.
.
.
RU RUREVISION
[ru][rurevision]
RUPOSITION
[ruposition]

state [blstate][intercnt][concn
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
| . . |
| . . |
| . . |
\ /
/ \
|REPLACEMENT UNITS|
|repl .... repl |
| . . |
| . . |
| . . |
|repl .... repl |
\ /
[NONE]
/ \
|FAULT INTERRUPT|
|fault type |
\ /
END
1.2 Parameters
blstate Blocking state of a manage

The blocking state of a man
The priority is given by the
BLL
Blocked due to loading
BLT
Blocked due to testing
MBL
Manually blocked
BLO
Automatically blocked
BLA
Blocked due to activity ne
btshwrev Base Transceiver Station (B

The BTS hardware revision
There may be a number of

btsswver BTS software version
The BTS software version d
This is a string fifteen chara
type
BTS Manufacturer
Identifies the BTS manufact
gen
BTS Generation
A term to separate BTSs fro
rev
BTS Revision
A term used to separate BT
var
BTS Variant
A term used to separate dif

concnt Counter for the number of c
This parameter is only valid

conerrcn Counter for the number of a
This parameter is only valid

extfcode External Fault Code, Class 1
Faults external to a Transce
See Operational Instruction Ra

extfcode External Fault Code, class 2
Faults external to a Transce

fcode1a Internal Fault Code, class 1
Faults within a managed ob
fcode1a
The faults are 'A', meaning

fcode1b Internal Fault Code, Class 1
Faults within a managed ob
The faults are 'B' meaning t

fcode2a Internal Fault Code, Class 2
Faults in a managed object
The faults are 'A', meaning

intercnt Counter for the number of i
This counter measures the
lfreason Reason for last fault messa
AGBLK
Number of reserved acces
BTSREJ
BTS reject. The BTS rejec
BUFFCONG
Buffer Congestion. Allocat
CAS
Cascadability. The manag
CONONTRH
Two high concentration o
CRC
Cyclic redundancy check.
DCP
Digital Connection Point (
DCPABIS
Digital Connection Point u
DCP1
DCP2
DFAE
Disk File Access Error. Un
DFFE
Disk File Format Error. Un
DFNF
Disk file not found. Opera
FHOP
Frequency hopping type.
HFILEFE
Header File Format Error.
ICP
Interface switch Connecti
INSUFMEM
Insufficient Memory. Unab
INTERERR
Internal data error. An in
INVALMOD
Physically Loadable Unit (
LOADERR
Download Error. An error
NEGFAIL
There has been a failure t
NOTRH
No TRH available. Unable
NSIWDV
The operational software
OFFS
Frame number offset. The
PWR
Transmitter nominal powe
RETRYLIM
Download retry limit reac
RXARFCN
Receiver absolute radio fr
RXBAND
Receiver frequency band.
RXD
Receiver diversity. The m
STARTFL
The Managed Object faile
SWOMLF1
Software SW file optional
SWOMLF2
SW file mandatory OML fu
SWRSLF1
SW file optional Radio Sig
SWRSLF2
SW file mandatory RSL fu
SYNCSRC
Timing Function (TF) sync
TCHCAP
Traffic Channel (TCH) cap
TEI
Terminal Endpoint Identif
TFMODE
Timing function synchron
TGOMLF1
TG optional OML function
TGOMLF2
TG mandatory OML functi
TGRSLF1
TG optional RSL functions
TGRSLF2
TG mandatory RSL functio
TRXOMLF1
TRXC optional OML functi
TRXOMLF2
TRXC mandatory OML fun
TRXRSLF1
TRXC optional RSL functio
TRXRSLF2
TRXC mandatory RSL fun
TXARFCN
Transmitter absolute radi
TXBAND
Transmitter frequency ba
XRA
Extended Range. The ma
lastflt Last fault message resulting
DISFAIL
Failed to Disable, the man
ENAFAIL
Failed to Enable, the man
LOADFAIL
The Managed Object Faile
PARAM
Mismatched parameter.
STATE
The procedure cannot be
UNSUPP
Attempted to use an unsu
mo Managed Object Instance
mo-G01
Managed Object Instance
mo-G12
repl Replacement Unit

The identifier of a faulty ha

ru Replacement Unit Index
The replacement unit index
rulogica Replacement Unit Logical Id
The replacement unit logica
rupositi Replacement Unit Position
The replacement unit positi
rurevisi Replacement Unit Revision
The replacement unit revisi
ruserial Replacement Unit Serial Nu
The replacement unit serial
state Global state of a managed o
DEF
Managed object individua
COM
state
PREOP
OPER
NOOP
FAIL
EOT DURING PRINTOUT

The operator has cancelled the prin
NONE
No data are to be printed
FAULT INTERRUPT
fault type
Fault interruption during printout
Fault type:
UNREASONABLE VALUE
details
Unreasonable value
FAULT CODE 2
CANNOT MIX DIFFERENT BTS LOGICAL
details
The MO parameter specified manag
2 Function
This printout is received as an answer prin
The fault information is printed out fo
The operator may specify that the inf
The operator may specify that fault in
3 Action
4 Printout Type
Answer printout
5 Printout Block
RXEFICRXOFIC
6 Glossary
ABIS BSC to BTS Interface

APG Adjunct Processor Group
BSC Base Station Controller
BSS Base Station Subsystem
BTS Base Transceiver Station
DCP Digital Connection Point
HW Hardware
IOG Input/Output Group
IWD Interwork Description
LAPD Link Access Protocol on D C
MOI Managed Object Instance
O&M Operations and Maintenanc
OML Operations and Maintenanc
PLU Physically Loadable Unit
RSL Radio Signalling Link
SW Software
TCH Traffic Channel
TF Timing Function
TG Transceiver Group
TRH Transceiver Handler
TRXC Transceiver Controller
TS Time Slot
7 References
7.1 Operational Instructions
Radio X-ceiver Administration, BTS Fault, R

7.2 Command Descriptions
RXMFP Radio X-Ceiver Administrati

PRINTOUT TO COMMAND RXMFP
CEIVER ADMINISTRATION MANAGED OBJECT FAULT INFORMATION
X-CEIVER ADMINISTRATION
D OBJECT FAULT INFORMATION
BTSSWVER BTSHWREV
[btsswver] [btshwrev]
.
.
.
[btshwrev]
BLSTATE INTERCNT CONCNT CONERRCNT LASTFLT LFREASON

[blstate][intercnt][concnt][conerrcnt][lastflt] [lfreason]
\
CODES CLASS 1A|
a ... fcode1a |
. |
. |
. |
a ... fcode1a |
/
\
CODES CLASS 1B|
b ... fcode1b |
. |
. |
. |
b ... fcode1b |
/
\
CODES CLASS 2A|
a ... fcode2a |
. |
. |
. |
a ... fcode2a |
/
\
AL FAULT CODES CLASS 1B|
de1b ... extfcode1b |
. |
. |
. |
/
\
. |
. |
. |
/
\
EMENT UNITS|
... repl |
. |
. |
. |
... repl |
/
BTSSWVER BTSHWREV
[btsswver] [btshwrev]
.
.
.
[btshwrev]

\
CODES CLASS 1A|
a ... fcode1a |
. |
. |
. |
a ... fcode1a |
/
\
CODES CLASS 1B|
b ... fcode1b |
. |
. |
. |
b ... fcode1b |
/
\
CODES CLASS 2A|
a ... fcode2a |
. |
. |
. |
a ... fcode2a |
/
\
. |
. |
. |
/
\
. |
. |
. |
/
\
EMENT UNITS|
... repl |
. |
. |
. |
... repl |
/
RING PRINTOUT]
\
INTERRUPT|
type |
/
ect instances.
X-CEIVER ADMINISTRATION
D OBJECT FAULT INFORMATION
BTSSWVER
[btsswver]
n will also be included in the printout.
REVISION RUSERIALNO
revision] [ruserialno]
POSITION RULOGICALID
position] [rulogicalid]
REVISION RUSERIALNO

\
CODES CLASS 1A|
a ... fcode1a |
. |
. |
. |
a ... fcode1a |
/
\
CODES CLASS 1B|
b ... fcode1b |
. |
. |
. |
b ... fcode1b |
/
\
CODES CLASS 2A|
a ... fcode2a |
. |
. |
. |
a ... fcode2a |
/
\
. |
. |
. |
/
\
. |
. |
. |
/
\
EMENT UNITS|
... repl |
. |
. |
. |
... repl |
/
BTSSWVER
[btsswver]
REVISION RUSERIALNO
REVISION RUSERIALNO

\
CODES CLASS 1A|
a ... fcode1a |
. |
. |
. |
a ... fcode1a |
/
\
CODES CLASS 1B|
b ... fcode1b |
. |
. |
. |
b ... fcode1b |
/
\
CODES CLASS 2A|
a ... fcode2a |
. |
. |
. |
a ... fcode2a |
/
\
. |
. |
. |
/
\
. |
. |
. |
/
\
EMENT UNITS|
... repl |
. |
. |
. |
... repl |
/
RING PRINTOUT]
\
INTERRUPT|
type |
/
Blocking state of a managed object.

The blocking state of a managed object (MO) is printed as one of the values listed below.
The priority is given by the order of listing.
Blocked due to loading
Blocked due to testing

Manually blocked
Automatically blocked
Blocked due to activity needed
Base Transceiver Station (BTS) hardware revision

The BTS hardware revision gives the hardware revision of the managed object.
There may be a number of hardware revisions associated with each managed object. For managed object RXETS, the
BTS software version
The BTS software version describes the software packages in the BTS.
This is a string fifteen characters long of the form type-gen-rev-var.
BTS Manufacturer
Identifies the BTS manufacturer.
BTS Generation
A term to separate BTSs from the same manufacturer, which are conceptually different over the Abis interface.
BTS Revision
A term used to separate BTSs from the same manufacturer and within a generation which support different sets of fu
BTS Variant
A term used to separate different BTS software packages of the same manufacturer, generation and revision.
Counter for the number of connection setup attempts.
This parameter is only valid for managed object instances of type Time Slot (TS).
Counter for the number of abnormally terminated connections.
This parameter is only valid for managed object instances of type TS.
External Fault Code, Class 1B
Faults external to a Transceiver Group (TG) that affect managed object functionality.
See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for references to BTS Maintenance Manuals. These ma
External Fault Code, class 2B
Faults external to a Transceiver Group (TG) that do not affect managed object functionality.
Internal Fault Code, class 1A
Faults within a managed object instance environment that affect managed object functioinality.
The faults are 'A', meaning that faulty Hardware (HW) is part of the managed object.
Internal Fault Code, Class 1B
Faults within a managed object instance environment that affect managed object functionality.
The faults are 'B' meaning that the origin of the fault is external to the managed object.
Internal Fault Code, Class 2A
Faults in a managed object instance that do not affect managed object functionality.
The faults are 'A', meaning that faulty HW is part of the managed object.
Counter for the number of intermittent faults.
This counter measures the number of intermittent faults on a managed object instance, except in the case of a TG m
Reason for last fault message.
Number of reserved access grant blocks. The managed object is not capable of supporting the configured value.
BTS reject. The BTS rejected the software.
BUFFCONG
Buffer Congestion. Allocation of dynamic buffer failed.
Cascadability. The managed object is not capable of supporting the feature.
CONONTRH
Two high concentration on Transceiver Handler (TRH). Unable to load the operational software required for the Man
Cyclic redundancy check. The managed object is not capable of supporting the specified value.
Digital Connection Point (DCP) used for the connection to the Link Access Protocol on D Channel (LAPD) concentrato
Digital Connection Point used as the terminating point in the BTS for the Abis path. The DCP is not valid as a termin
Digital Connection Point used for the signalling path to the TRXC. The managed object is not connected to the speci
Digital Connection Point used for the specch and data connections to the TRXC. The managed object is not connecte
Disk File Access Error. Unable to access the file in Input/Output Group (IOG) or Adjunct Processor Group (APG).
Disk File Format Error. Unable to load the operational software for the MOI as file is incorrectly formatted.
Disk file not found. Operational Software required for the managed object is not found in the IOG/APG.
Frequency hopping type. The managed object is not capable of supporting the configured value.
Header File Format Error. Unable to load the operational software required for the MOI. The software version heade
Interface switch Connection Point. The mangaged object is not capable of supporting the configured value.
INSUFMEM
Insufficient Memory. Unable to load the operational software required for the MOI due to insufficient Base Station C
INTERERR
Internal data error. An internal error occurred during the load.
INVALMOD
Physically Loadable Unit (PLU) not in valid mode. The PLU is not in the correct mode for loading.
Download Error. An error occurred during the download.
There has been a failure to negotiate a Base Station Subsystem (BSS) release version between BSC and BTS.
No TRH available. Unable to load the operational software because there is no available transceiver handler.
The operational software header file does not contain an Interwork Description (IWD) version which is supported by
Frame number offset. The managed object is not capable of supporting the configured value.
Transmitter nominal power. The managed object is not capable of supporting the configured value.
RETRYLIM
Download retry limit reached.
Receiver absolute radio frequency channel number. The managed object is not capable of supporting the configured
Receiver frequency band. The managed object is not capable of supporting the configured value.
Receiver diversity. The managed object is not capable of supporting the configured value.
The Managed Object failed to start.
Software SW file optional Operations and Maintenance Link (OML) functions. The actual SW version loaded to the m
SW file mandatory OML functions. The actual SW version loaded to the managed object is not capable of supporting
SW file optional Radio Signalling Link (RSL) functions. The actual software (SW) version loaded to the managed obj
SW file mandatory RSL functions. The actual SW version loaded to the managed object is not capable of supporting
Timing Function (TF) synchronization source. The managed object is not capable of supporting the configured value
Traffic Channel (TCH) capabilities The managed object is not capable of supporting the wanted TCH speech version.
Terminal Endpoint Identifier The specified TEI is not correct for the managed object.
Timing function synchronization mode. The managed object is not capable of supporting the configured value.
TG optional OML functions. The managed object is not capable of supporting the wanted function.
TG mandatory OML functions. The managed object is not capable of supporting the wanted function.
TG optional RSL functions. The managed object is not capable of supporting the wanted function.
TG mandatory RSL functions. The managed object is not capable of supporting the wanted function.
TRXOMLF1
TRXC optional OML functions. The managed object is not capable of supporting the wanted function.
TRXOMLF2
TRXC mandatory OML functions. The managed object is not capable of supporting the wanted function. .
TRXRSLF1
TRXC optional RSL functions. The managed object is not capable of supporting the wanted function.
TRXRSLF2
TRXC mandatory RSL functions. The managed object is not capable of supporting the wanted function.
Transmitter absolute radio frequency channel number. The managed object is not capable of supporting the configu
Transmitter frequency band. The managed object is not capable of supporting the configured value.
Extended Range. The managed object is not capable of supporting the configured value.
Last fault message resulting from failure of the last attempted Operations and Maintenance (O&M) procedure between
Failed to Disable, the managed object remains Enabled.
Failed to Enable, the managed object remains Disabled.
LOADFAIL
The Managed Object Failed to Load Correctly.
Mismatched parameter.
The procedure cannot be accepted in current state.
Attempted to use an unsupported function.
Managed Object Instance in BTS logical model G01.
Managed Object Instance in BTS logical model G12.
Replacement Unit
The identifier of a faulty hardware unit.
Replacement Unit Index
The replacement unit index is used to show that the four strings belong to the same replacement unit.
Replacement Unit Logical Identity
The replacement unit logical identity gives the replacement unit logical identity of a managed object. There may be a
Replacement Unit Position
The replacement unit position gives the replacement unit position of the managed object. There may be a number of
Replacement Unit Revision
The replacement unit revision gives the replacement unit revision of the managed object. There may be a number of
Replacement Unit Serial Number
The replacement unit serial number gives the replacement unit serial number of the managed object. There may be a
Global state of a managed object instance
Managed object individual is defined.

Managed object individual in service but manually blocked.
Managed object individual which is being brought into operation.
Managed object individual which is operational.
Managed object individual which is temporarily not operational.
Managed object individual which is blocked permanently from own supervision.
ING PRINTOUT
erator has cancelled the printout
a are to be printed
nterruption during printout
NABLE VALUE
onable value
MIX DIFFERENT BTS LOGICAL MODELS
O parameter specified managed object instances from more than one BTS logical model.
out is received as an answer printout to command RXMFP.
information is printed out for one or more managed object instance, or for all defined managed objects of a managed
ator may specify that the information is printed only for managed object instances which are faulty.
ator may specify that fault information is also printed for managed objects which are subordinate to the specified mana
tout requires no action.

BSC to BTS Interface
Adjunct Processor Group
Base Station Controller
Base Station Subsystem
Base Transceiver Station
Digital Connection Point
Hardware
Input/Output Group
Interwork Description
Link Access Protocol on D Channel
Operations and Maintenance
Operations and Maintenance Link
Physically Loadable Unit
Radio Signalling Link
Traffic Channel
Timing Function
Transceiver Group
Transceiver Handler
Transceiver Controller
Time Slot
ational Instructions
eiver Administration, BTS Fault, Repair

mand Descriptions
Radio X-Ceiver Administration Managed Object Fault Information, Print

ANSWER PRINTOUT TO COMMAND RXELP
Radio X-ceiver Administration Error Log Data
1 Format
1.1 Printout

ERROR LOG DATA
FAULT INFORMATION LOG
MO BTSSWVER DATE TIME BTS

mo btsswver date time bts
REPLMAP 1AMAP
replmap 1amap
1BMAP 2AMAP
1bmap 2amap
EXT1BMAP EXT2BMAP
ext1bmap ext2bmap
.
.
.
MO BTSSWVER DATE TIME BTS

mo btsswver date time bts
REPLMAP 1AMAP
replmap 1amap
1BMAP 2AMAP
1bmap 2amap
EXT1BMAP EXT2BMAP
ext1bmap ext2bmap
[NONE]
/ \
|FAULT INTERRUPT|
|faulttype |
\ /
END
1.2 Parameters
bts The BTS state is the last known state of the managed object in the BTS
The possible BTS states are:
RES
The Managed object is in state RESET.
STA
The managed object is in state STARTED.
DIS
The managed object is in the state DISABLED.
ENA
The managed object is in the state ENABLED.
btsswver The BTS Software Version

The BTS software version describes the software packages in the BTS.
Represented by a string, fifteen characters long of the form type_gen_rev_va
type
BTS manufacturer.
Identifies the BTS manufacturer. This field is three characters long.
gen
BTS Generation.
A term to separate BTS from the same manufacturer, which are conceptually
rev
BTS Revision.
A term used to separate BTSs from the same manufacturer and within a gene
var
BTS Variant.
A term used to separate different BTS software packages of the same manufa
date Date
The date the error was received.
Represented by a string eight characters long in the format yy-mm-dd, where

ext1bmap External Fault Map Class 1B
A map which identifies faults external to the TG that do not affect Managed O
ext1bmap
The map is printed as a hexadecimal number four characters long where each digit of th
ext2bmap External Fault Map Class 2B
A map which identifies faults external to the TG that do not affect Managed O
The map is printed as a hexadecimal number four characters long where each digit of th
mo Managed Object Instance
replmap Replacement Units Map
The identifier of a number of possibly faulty hardware units.
The map is printed as a hexadecimal number twenty four characters long where each di
time Time
The time the error was received.
Represented by a string eight characters long in the format hh-mm-ss, where

1amap Internal Fault Map Class 1A
A map which identifies faults internal to the TG that affect Managed Object In
The map is printed as a hexadecimal number twenty four characters long, where each d
1bmap Internal Fault Map Class 1B
2amap Internal Fault Map Class 2A
NONE NONE is obtained if no defined managed object exists fulfilling the search crit
EOT DURING PRINTOUT

The operator has cancelled the printout.
FAULT INTERRUPT
fault type
A fault interruption occurred during printing.
Fault type:
FORMAT ERROR
Format error.
UNREASONABLE VALUE
details
Unreasonable value.
FAULT CODE 2
CANNOT MIX DIFFERENT BTS LOGICAL MODELS
details
The MO parameter specified managed object instances from more than one BTS logic
2 Function
This printout is received as an answer or result printout to the command RXELP.
The fault log is printed for one or more specified managed object instances or for all the
When the command RXELP is given the alphanumeric output device may be specified. I
Alternatively, an answer printout RADIO X-CEIVER ADMINISTRATION ERROR LOG DATA
3 Action
4 Printout Type
Answer printout
Result printout
5 Printout Block
RXEESCRXOESC
6 Glossary
This document contains no glossary entries.
7 References
7.1 Operational Instructions
Radio X-ceiver Administration, BTS Fault, Repair

7.2 Command Descriptions
RXELP RADIO CONTROL X-CEIVER ADMINISTRATION ERROR LOG, PRINT

7.3 Printout Descriptions
RADIO X-CEIVER ADMINISTRATION ERROR LOG DATA

r managed object RXETS, there may be two types of hardware in the BTS. If each TimeSlot (TS) is represented with a
over the Abis interface.
ch support different sets of functions and procedures over the Abis interface.
neration and revision.
Maintenance Manuals. These manuals contain information on how to decode the faults.
except in the case of a TG managed object instance where the counter measures the number of intermittent faults tha
ting the configured value.
software required for the Managed Object Instance (MOI) due to inability to set up a communication link because of pro
D Channel (LAPD) concentrator. The DCP is not valid as a terminating point in the LAPD concentrator.
e DCP is not valid as a terminating point for the Abis path.
is not connected to the specified DCP.
anaged object is not connected to the specified DCP.
ct Processor Group (APG).
correctly formatted.
in the IOG/APG.
. The software version header file format is not compatible with the BTS Logical Model.
he configured value.
to insufficient Base Station Controller (BSC) memory.
between BSC and BTS.
e transceiver handler.
version which is supported by the wanted BSS release.
gured value.
e of supporting the configured value.

al SW version loaded to the managed object is not capable of supporting the wanted function.
t is not capable of supporting the wanted function.
n loaded to the managed object is not capable of supporting the wanted function.
t is not capable of supporting the wanted function.
pporting the configured value.
wanted TCH speech version.
ng the configured value.
ed function.
nted function.
d function.
nted function.
nted function.
wanted function. .
nted function.
wanted function.
able of supporting the configured value.

igured value.
nce (O&M) procedure between BSC and BTS.
acement unit.
aged object. There may be a number of replacement unit logical identities associated with each managed object.
. There may be a number of replacement unit positions associated with each managed object.
. There may be a number of replacement unit revisions associated with each managed object.
naged object. There may be a number of replacement unit serial numbers associated with each managed object.
naged objects of a managed object type.
ordinate to the specified managed object instance.

BTS
bts
BTS
bts
aged object in the BTS
packages in the BTS.
of the form type_gen_rev_var.
ee characters long.
urer, which are conceptually different over the Abis interface. This field is three characters long.
anufacturer and within a generation which support different sets of functions and procedures over the Abis interface. Th
packages of the same manufacturer, generation and revision. This field is three characters long.
the format yy-mm-dd, where yy represents the year, mm the month and dd the day that the error was entered into th
that do not affect Managed Object functionality.

acters long where each digit of the number represents four bits of the binary fault map, for example, 0011 means bits 0 and 4 are set. Se
that do not affect Managed Object functionality.
acters long where each digit of the number represents four bits of the binary fault map, for example, 1000 means bit 15 is set. See Oper
ware units.
ur characters long where each digit of the number represents four bits of a binary fault map, for example, 000000000000 000000000400
the format hh-mm-ss, where hh represents the hour, mm the minute and ss the second that the error was entered int
hat affect Managed Object Instance functionality. The faults are 'A', meaning that faulty HW is part of the signalling ma
ur characters long, where each digit of the number represents four bits of the binary fault map, for example, 000000000000 0000000000
hat affect Managed Object Instance functionality. The faults are 'B', meaning that the origin of the fault is external to th
hat affect Managed Object Instance functionality. The faults are 'A', meaning that faulty HW is part of the signalling ma
exists fulfilling the search criteria.
om more than one BTS logical model.

mand RXELP.
object instances or for all the managed object instances of a specified managed object type.
ut device may be specified. In the case of the device being specified, a result printout, RADIO X-CEIVER ADMINISTRAT
STRATION ERROR LOG DATA is sent to the ordering IO device.
RROR LOG, PRINT

t (TS) is represented with a single board, BTSHWREV then shows the revision of each board. If 8 logical RXETS MO's a
ber of intermittent faults that occurred in the subordinate managed object instances.
munication link because of processor capacity limitations in the file handler. Too many Transceiver Controllers (TRXC) a
ncentrator.
each managed object.
each managed object.

es over the Abis interface. This field is three characters long.
the error was entered into the log.

11 means bits 0 and 4 are set. See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for references to BTS Main
00 means bit 15 is set. See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for references to BTS Maintenanc
e, 000000000000 000000000400 means bit 10 is set. See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for
hat the error was entered into the log.
W is part of the signalling managed object. This map is also used to represent internal fault class 1 for some BTS versio
mple, 000000000000 000000000011 means bits 4 and 0 are set. See Operational Instruction Radio X-ceiver Administration, BTS Fault,
in of the fault is external to the signalling managed object.
mple, 000000000000 000000000200 means bit 9 is set. See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair fo
W is part of the signalling managed object. This map is also used to represent internal fault class 2 for some BTS versio
mple, 000000000000 300000000000 means bits 44 and 45 are set. See Operational Instruction Radio X-ceiver Administration, BTS Fau
DIO X-CEIVER ADMINISTRATION ERROR LOG DATA is given on this device.
ard. If 8 logical RXETS MO's are represented with one board, BTSHWREV will be empty. In this case print BTSHWREV fo
nsceiver Controllers (TRXC) are specified on the same transmission device
Repair for references to BTS Maintenance Manuals. These manuals contain information on how to decode the fault map.
or references to BTS Maintenance Manuals. These manuals contain information on how to decode the fault map.
ministration, BTS Fault, Repair for reference to BTS Maintenance Manuals. These manuals contain information on how to find the replac
lt class 1 for some BTS versions.
ceiver Administration, BTS Fault, Repair for references to BTS Maintenance Manuals. These manuals contain information on how to dec
ministration, BTS Fault, Repair for references to BTS Maintenance Manuals. These manuals contain information on how to decode the
lt class 2 for some BTS versions.
X-ceiver Administration, BTS Fault, Repair for references to BTS Maintenance Manuals. These manuals contain information on how to d
this case print BTSHWREV for managed object RXETRX to see the hardware revision of the board.
ode the fault map.
rmation on how to find the replacement units.
contain information on how to decode the fault map.
formation on how to decode the fault map.
ls contain information on how to decode the fault map.

Limited Internal
E 95 (95)
INTERFERENCE REJECTION COMBINING
IRC ON/OFF
*** IRC for R10 onwards. Max ratio comb (MRC) for normal receiver diversity - it’s the algorithm used to maximise uplink signal
quality. MRC detects thermal noise, combines multiple received signals to produce a better C/N ratio
*IRC is most effective at detecting single cochannel interferers. Frame synch, type of ant diversity, adj interferers, type of
coding schemes, clutter area/propagation all have an effect on the final gain.
For single coch in urban, polarisation diversity with frame synch, gain is appx 5dB. Without synch its 2-3 dB
ANTENNA HOPPING
AHOP ON/OFF/ONXC0 - all except BCCH
FLEXIBLE POSITIONING SUPPORT for Location Based Services
Date: 6/1/2005
Rev: PA1
Sheet: Parameters

Oss Commands Notes

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Oss Commands Notes

Hochgeladen von

Copyright:

Verfügbare Formate

Limited Internal

************************* BSC PRINTOUTS ********************************

******************* BSC & CELL DATA PRINTOUTS **************************

CACLP; ! Time of the printouts!

*************** ADDITIONAL RADIO RELATED PRINTOUTS ******************

****************** X-CEIVER RELATED PRINTOUTS ***************************

RXASP:MOTY=RXOTG; ! Alarm Coordination D.RBS 2000! -0&&-7 0 to 7 selected

****************** BSC EXCHANGE DATA PRINTOUTS ***********************

RXTCP:MO=RXOTG-(XX); To check site cell name

RLNRP:CELL=(XX),CELLR=(XX); Check all neighbours data OR specified neighbour only

RLCHC:CELL=(XX),CHGR=(X),HOP=ON; To activate Hopping

RLLOC:CELL=(XX),FBUL and OL setting

RLCFP:CELL=(XX); To check cell frequency, no of SDCCH,

RLBCE/I:CELL=(XX); To active or inactive power control (DBPSTATE

Script to define ext cell in BSC level:

ALLIP:PRCA=43; Alarm printour categories. Refer to 'Alarm PRCA' category

Using APG40 not APG30

RLSLE:CELL=XXXX; Disable alarm supervision

o take effect in that BSC

ping or not, HSN, SCTYPE - UL or OL, frequencies per CHGR

e mode. Shows neighbours in BA and SA list

ering for subcell change threshold when BSPWRB/T is changed

per CHGR in a cell

CH, TCH; state:busy/idle; 64K channels; CHRATE:FR/HR; CHBAND:900,E900,1800; ICMBAND:1-4.

RSPRIO or EBANDINCLUDED etc. Shows data related to specified parameter

cell is contained in which cabinet)

FR/HR; CHBAND:900,E900,1800; ICMBAND:1-4.

ent, repeated checking required.

cell or channel group: ACTIVE or HALTED

Object instances. Alarm trigerred

TO DETERMINE WHETHER THERE IS SUFFICIENT E1 MAPPED TO A CELL FOR RADIO

Commands to be used highlighted in green

DEV DCP APUSAGE APSTATE 64K

RBLT-3992 24 MPLEX16 SPEECH/DATA NO

CHGR NUMREQBPC NUMREQEGPRSBPCNUMREQCS3CS4BPCTN7BCCH

DEV MISC1 MISC2 MISC3 MISC4

SNT SNTV SNTP DIP DEV

DEV DCP RESULT

PPED TO A CELL FOR RADIO UPGRADES/ EDGE-GPRS CS3 4 EXPANSION

Each E1 timeslot has a device ID

In use for speech

This IDLE timeslot can be used

Shows the number of EDGE and CS34 timeslots in a cell

This will display the E1 ID for the E1 timeslot labelled RBLT-4022

ld be assigned to 1 cabinet but on

34 timeslots we would only need to

1 timeslots are required for

under 64K column to

and the Base Transceiver Station (BTS).

*** Connected to NILA08 ***

DEV DCP APUSAGE APSTATE 64K TEI

DEV DCP APUSAGE APSTATE 64K TEI

DEV SNT/DEVP MUP

DEV MISC1 MISC2 MISC3 MISC4 ADMSTATE

SNT SNTV SNTP DIP DEV SNTINL

SNT EQLEV PROT SDIP SUBSNT DEFPST SNTP MODE

UNACCEPTABLE PERFORMANCE LEVEL

DIP SECTION T1 N-ES N-SES N-UAS N-UAV SLIP SMI

DIP SECTION T1 F-ES F-SES F-UAS F-UAV SMI

DEGRADED PERFORMANCE LEVEL

DIP SECTION T2 N-ES N-SES N-UAS N-UAV SLIP SMI

DIP SECTION T2 F-ES F-SES F-UAS F-UAV SMI

DIP SECTION SFV SFTI

* BSC PRINTOUTS ********

* BSC & CELL DATA PRINTOUTS ********

* ADDITIONAL RADIO RELATED PRINTOUTS ****

X-CEIVER RELATED PRINTOUTS *********

BSC EXCHANGE DATA PRINTOUTS *****

* Connected to NILA08 *