Oss Commands Notes
Oss Commands Notes
E 1 (95)
e-remove
i-add
c-change
p-print
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!
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)
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!
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!
-------------------------------------------------------------------------------------------
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);
--------------------------------------------------
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;
--------------------------------------------------
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;
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
ata for all external GSM cells defined in the BSC is printed. CGI, Cell ID data, bsic
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 parameter settings of cells/object (following RXOTG value) in a BSC
heck parameter settings of cells/object (following RXOTG value) in a BSC
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)
or Channel No., ICM - Yes or No, CHCOMB - BCCH, SDCCH8 or TCH, BSPWR, SDCCH and TCH allocated to which frequency
Date: 6/1/2005
Rev: PA1
Sheet: OSS Commands
Limited Internal
E 6 (95)
Date: 6/1/2005
Rev: PA1
Sheet: OSS Commands
Limited Internal
E 7 (95)
<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
<RXTCP:MOTY=RXOTG,CELL=TSEEM12;
RADIO X-CEIVER ADMINISTRATION
TG TO CHANNEL GROUP CONNECTION DATA
MO CELL CHGR
RXOTG-110 TSEEM12 0
TSEEM12 1
TSEEM12 2
RXOTG-111 TSEEM12 3
END
<RXTCP:MOTY=RXOTG,CELL=TSEEM13;
RADIO X-CEIVER ADMINISTRATION
TG TO CHANNEL GROUP CONNECTION DATA
MO CELL CHGR
RXOTG-110 TSEEM13 0
TSEEM13 1
TSEEM13 2
RXOTG-123 TSEEM13 3
END
<RXAPP:MO=RXOTG-110;
RADIO X-CEIVER ADMINISTRATION
ABIS PATH STATUS
MO
RXOTG-110
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 8 (95)
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3970 2 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3971 3 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3972 4 UNCONC TRXC SIGNAL NO
RBLT-3973 5 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3974 6 UNCONC TRXC SIGNAL NO
RBLT-3975 7 UNCONC TRXC SIGNAL NO
RBLT-3976 8 UNCONC TRXC SIGNAL NO
RBLT-3977 9 UNCONC CF/TRXC SIGNAL NO
RBLT-3978 10 UNCONC TRXC SIGNAL NO
RBLT-3979 11 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3980 12 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3981 13 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX32 IDLE NO
RBLT-3982 14 UNCONC TRXC SIGNAL NO
RBLT-3983 15 UNCONC TRXC SIGNAL NO
RBLT-3984 16 UNCONC TRXC SIGNAL NO
RBLT-3985 17 UNCONC TRXC SIGNAL NO
RBLT-3986 18 UNCONC TRXC SIGNAL NO
RBLT-3987 19 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3988 20 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3989 21 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3990 22 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT-3991 23 UNDEF IDLE NO
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 9 (95)
END
<RLBDP:CELL=TSEEM11;
CELL CONFIGURATION BPC DATA
CELL
TSEEM11
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 10 (95)
<RADEP:DEV=RBLT-4022;
DEVICE DATA IN BSC
DEV SNT/DEVP
RBLT-4022 ETRBLT-125
RBLT-4022 0
END
<NTCOP:SNT=ETRBLT-125;
SWITCHING NETWORK TERMINAL CONNECTION DATA
RXAPI:MO=RXOTG-123,DEV=RBLT-4022&&-4027,DCP=22&&27;
RADIO X-CEIVER ADMINISTRATION
ABIS PATH RESULT
MO
RXOTG-123
END
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 11 (95)
RXAPE:MO=RXOTG-123,DCP=22&&27;
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 12 (95)
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
TEI
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 13 (95)
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
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
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
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 15 (95)
TN7BCCH
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
Sheet: E1 Verification
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
Sheet: E1 Verification
Limited Internal
E 17 (95)
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 18 (95)
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 19 (95)
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
Limited Internal
E 20 (95)
nitiated. Without
e slots are actually
Date: 6/1/2005
Rev: PA1
Sheet: E1 Verification
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
MO CELL CHGR
RXOTG-10 HOREM11 0
HOREM11 1
RXOTG-11 HOREM11 3
END
<RXAPP:MO=RXOTG-10&-11;
RADIO X-CEIVER ADMINISTRATION
ABIS PATH STATUS
MO
RXOTG-10
MO
RXOTG-11
Date: 6/1/2005
Rev: PA1
Sheet: Frame Slip Verification
Limited Internal
E 22 (95)
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-877 13 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-878 14 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-879 15 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-880 16 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-881 17 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-882 18 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-883 19 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-884 20 MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
MPLEX16 SPEECH/DATA NO
RBLT2-885 21 UNCONC CF/TRXC SIGNAL NO 62 11
END
<RADEP:DEV=RBLT2-865&-885;
DEVICE DATA IN BSC
DEV SNTINL
RBLT2-865 0
RBLT2-885 0
END
<NTCOP:SNT=ETM2-3;
SWITCHING NETWORK TERMINAL CONNECTION DATA
<DTQUP:DIP=27RBL2;
DIGITAL PATH QUALITY
INCOMING DIRECTION
Date: 6/1/2005
Rev: PA1
Sheet: Frame Slip Verification
Limited Internal
E 23 (95)
OUTGOING DIRECTION
INCOMING DIRECTION
OUTGOING DIRECTION
FRAME SLIPS
<RADEP:DEV=RBLT2-801&-846;
DEVICE DATA IN BSC
DEV SNTINL
RBLT2-801 61
RBLT2-846 62
END
<NTCOP:SNT=ETM2-2;
SWITCHING NETWORK TERMINAL CONNECTION DATA
<DTQUP:DIP=25RBL2&26RBL2;
DIGITAL PATH QUALITY
INCOMING DIRECTION
OUTGOING DIRECTION
INCOMING DIRECTION
Date: 6/1/2005
Rev: PA1
Sheet: Frame Slip Verification
Limited Internal
E 24 (95)
25RBL2 19 0 0 0 0 0 0
OUTGOING DIRECTION
FRAME SLIPS
INCOMING DIRECTION
OUTGOING DIRECTION
INCOMING DIRECTION
OUTGOING DIRECTION
FRAME SLIPS
<
Date: 6/1/2005
Rev: PA1
Sheet: Frame Slip Verification
Limited Internal
E 25 (95)
HOW TO INITIATE A CTR/CER/MTR AND EXTRACT THE DATA FOR POST PROCESSING
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:
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
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.
owing commands:
Date: 6/1/2005
Rev: PA1
Sheet: Extra
Limited Internal
E 27 (95)
Date: 6/1/2005
Rev: PA1
Sheet: Extra
PRCA VALUES TO BE USED FOR COMMAND 'ALLIP:PRCA="XX";'
2 Printout Categories
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
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";'
HB AL
Heartbeat to AOM
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
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)
Cancelled
Cancelled
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)
Cancelled
Cancelled
HB AL
Heartbeat to AOM
1 Format
1.1 Printout
/
|/
||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]
/ \
|FAULT INTERRUPT|
|fault type |
\ /
END
1.2 Parameters
alarm situation The alarm situation provides the type of fault in the ind
LMT INTERVENTION
Local maintenance activities being performed in the B
LOCAL MODE
The BTS equipment is in Local Mode or the BTS equip
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
NO ALARM SITUATIONS
No alarm situations in the specified MOTY.
NONE
No data are to be printed
FAULT INTERRUPT
fault type
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
2 Function
This printout is an answer printout to the command RXASP. All of the outstan
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
3 Action
4 Printout Type
Answer printout
5 Printout Blocks
RXEALCRXOALC
6 Glossary
7 References
1 Format
1.1 Printout
1.1.1 Format 1
s been detected.
[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.
RADIO X-CEIVER ADMINISTRATION
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]
RU RUREVISION
[ru][rurevision]
RUPOSITION
[ruposition]
.
.
.
RU RUREVISION
[ru][rurevision]
RUPOSITION
[ruposition]
[NONE]
/ \
|FAULT INTERRUPT|
|fault type |
\ /
END
1.2 Parameters
BLL
Blocked due to loading
BLT
Blocked due to testing
MBL
Manually blocked
BLO
Automatically blocked
BLA
Blocked due to activity ne
type
BTS Manufacturer
gen
BTS Generation
rev
BTS Revision
var
BTS Variant
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
Digital Connection Point u
DCP2
Digital Connection Point u
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
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-G01
Managed Object Instance
mo-G12
Managed Object Instance
DEF
Managed object individua
COM
state
PREOP
Managed object individua
OPER
Managed object individua
NOOP
Managed object individua
FAIL
Managed object individua
NONE
No data are to be printed
FAULT INTERRUPT
fault type
Fault type:
UNREASONABLE VALUE
details
Unreasonable value
FAULT CODE 2
CANNOT MIX DIFFERENT BTS LOGICAL
details
2 Function
3 Action
4 Printout Type
Answer printout
5 Printout Block
RXEFICRXOFIC
6 Glossary
X-CEIVER ADMINISTRATION
D OBJECT FAULT INFORMATION
BTSSWVER BTSHWREV
[btsswver] [btshwrev]
.
.
.
[btshwrev]
BTSSWVER BTSHWREV
[btsswver] [btshwrev]
.
.
.
[btshwrev]
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
revision] [ruserialno]
POSITION RULOGICALID
position] [rulogicalid]
BTSSWVER
[btsswver]
REVISION RUSERIALNO
revision] [ruserialno]
POSITION RULOGICALID
position] [rulogicalid]
REVISION RUSERIALNO
revision] [ruserialno]
POSITION RULOGICALID
position] [rulogicalid]
RING PRINTOUT]
\
INTERRUPT|
type |
/
Automatically blocked
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.
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.
See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for references to BTS Maintenance Manuals. These ma
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.
See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for references to BTS Maintenance Manuals. These ma
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.
See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for references to BTS Maintenance Manuals. These ma
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.
See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for references to BTS Maintenance Manuals. These ma
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.
BUFFCONG
Buffer Congestion. Allocation of dynamic buffer failed.
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.
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
LOADFAIL
The Managed Object Failed to Load Correctly.
Mismatched parameter.
Replacement Unit
The identifier of a faulty hardware unit.
See Operational Instruction Radio X-ceiver Administration, BTS Fault, Repair for references to BTS Maintenance Manuals. These ma
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
ING PRINTOUT
erator has cancelled the printout
a are to be printed
NABLE VALUE
onable value
O parameter specified managed object instances from more than one BTS logical model.
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
Traffic Channel
Timing Function
Transceiver Group
Transceiver Handler
Transceiver Controller
Time Slot
ational Instructions
1 Format
1.1 Printout
REPLMAP 1AMAP
replmap 1amap
1BMAP 2AMAP
1bmap 2amap
EXT1BMAP EXT2BMAP
ext1bmap ext2bmap
.
.
.
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
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.
type
BTS manufacturer.
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.
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.
The map is printed as a hexadecimal number twenty four characters long, where each d
1bmap Internal Fault Map Class 1B
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
2amap Internal Fault Map Class 2A
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
NONE NONE is obtained if no defined managed object exists fulfilling the search crit
FAULT INTERRUPT
fault type
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
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
3 Action
4 Printout Type
Answer printout
Result printout
5 Printout Block
RXEESCRXOESC
6 Glossary
7 References
ch support different sets of functions and procedures over the Abis interface.
Maintenance Manuals. These manuals contain information on how to decode the faults.
Maintenance Manuals. These manuals contain information on how to decode the faults.
Maintenance Manuals. These manuals contain information on how to decode the faults.
Maintenance Manuals. These manuals contain information on how to decode the faults.
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
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.
correctly formatted.
in the IOG/APG.
. The software version header file format is not compatible with the BTS Logical Model.
he configured value.
e transceiver handler.
gured value.
n loaded to the managed object is not capable of supporting the wanted function.
ed function.
nted function.
d function.
nted function.
nted function.
wanted function. .
nted function.
wanted function.
Maintenance Manuals. These manuals contain information on how to decode the faults.
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.
BTS
bts
aged object in the BTS
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
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
ur characters long, where each digit of the number represents four bits of the binary fault map, for example, 000000000000 0000000002
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 3000000000
exists fulfilling the search criteria.
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
munication link because of processor capacity limitations in the file handler. Too many Transceiver Controllers (TRXC) a
ncentrator.
each managed object.
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
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,
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
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
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.
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
Date: 6/1/2005
Rev: PA1
Sheet: Parameters