Cell Site Structure and troubleshooting from OSS This procedure covers basic structure and troubleshooting of a site from an OSS perspective in situations where a site does not restore whether partially or completely, for example after a rehome or software upgrade. BTS Hierarchy: In order to troubleshoot a site from the BSC it is necessary to have a knowledge of the logical hierarchy of the BTS (In the BSC) as compared with its physical elements. Physically the BTS is made up of RUs (Replaceable Units) such as the DXU, TRU, etc. Logically these RUs are known as MOs (Managed Objects). The Main MO of any site, the TG (Transceiver Group) is not associated with any hardware at the BTS but resides in the BSC. It can be thought of as an “Address” of the site within the BSC. Connecting the TG to the Site in the Field is the DIP (Digital Path). It represents the T1 (Abis Interface) link to the BTS. In the BTS itself there are RUs, which are represented by MOs in the BSC. BTS Hierarchy Managed Objects Definition Physical representation RXOTG-XX Transceiver Group Entire RBS/DIP (usually) RXOCF-XX Control Function DXU RXOTF-XX Timing Function Oscillator within the DXU RXOIS-XX Interconnect Switch Switch in the DXU RXOTRX-XX-Y Transceiver Controller TRU RXOTX-XX-Y Transmitter Transmitter within the TRU RXORX-XX-Y Receiver Receiver within the TRU RXOTS-XX-Y-0&&-7 Time Slots Time Slots within the TRU Numbering convention: All MOs in a site share the number of the TG. For example, if a site has TG 46, all of the sub-MOs will have number 46. The MOs related to the TRUs will have additional numbers added to them which refer to the TRU’s assignment within the TG. For example, TRU #0 in RXOTG-46 will have RXOTRX-46-0, RXOTX-46-0, RXORX-46-0, and RXOTS-46-0-0&&-7. The BSC BTS TG DXU RXOCF RXOTF RXOIS TRU RXOTRX RXOTX RXORX RXOTS (-0&&- 7) TRU RXOTRX RXOTX RXORX RXOTS (-0&&- 7) TRU RXOTRX RXOTX RXORX RXOTS (-0&&- 7) DIP (RBLT)
Transcript
Cell Site Structure and troubleshooting from OSS
This procedure covers basic structure and troubleshooting of a site from an OSS perspective in situations where a site does not restore whether partially or completely, for example after a rehome or software upgrade.
BTS Hierarchy:
In order to troubleshoot a site from the BSC it is necessary to have a knowledge of the logical hierarchy of the BTS (In the BSC) as compared with its physical elements. Physically the BTS is made up of RUs (Replaceable Units) such as the DXU, TRU, etc.Logically these RUs are known as MOs (Managed Objects). The Main MO of any site, the TG (Transceiver Group) is not associated with any hardware at the BTS but resides in the BSC. It can be thought of as an “Address” of the site within the BSC. Connecting the TG to the Site in the Field is the DIP (Digital Path). It represents the T1 (Abis Interface) link to the BTS. In the BTS itself there are RUs, which are represented by MOs in the BSC.
RXOTG-XX Transceiver Group Entire RBS/DIP (usually)RXOCF-XX Control Function DXURXOTF-XX Timing Function Oscillator within the DXURXOIS-XX Interconnect Switch Switch in the DXU
RXOTRX-XX-Y Transceiver Controller TRURXOTX-XX-Y Transmitter Transmitter within the TRURXORX-XX-Y Receiver Receiver within the TRU
RXOTS-XX-Y-0&&-7 Time Slots Time Slots within the TRU
Numbering convention:All MOs in a site share the number of the TG. For example, if a site has TG 46, all of the sub-MOs will have number 46. The MOs related to the TRUs will have additional numbers added to them which refer to the TRU’s assignment within the TG. For example, TRU #0 in RXOTG-46 will have RXOTRX-46-0, RXOTX-46-0, RXORX-46-0, and RXOTS-46-0-0&&-7. The additional designations on the time slots refer to the time slot position within that TRU (i.e. TG 46, TRU 0, TS 0 thru 7).
Any object in this list has a superior and a subordinate MO. What this means is that in order to perform certain operations it is necessary to remember the status of subordinate and superior MOs. When loading and deblocking always follow the hierarchy from top to bottom, and when taking out of service always follow the hierarchy from bottom to top.
Troubleshooting example #1 – Sector down
When experiencing trouble at a site always get the “Big Picture” of how the site is behaving. Is the whole site down, or only certain sectors? Run the following commands to see at what level the site is experiencing problems:
ALLIPThis will give an overview of all the alarms that exist on the BSC at the time which may point you in the right direction for your specific site, then with the RLCRP command you will see which sectors have resources and which don’t. In our example, if sector B was down you would probably see alarms in the alarm list related to the TRUs at the site as well as the CF. You would see alarms for Logical Channels Availability, and probably alarms on the CF and the individual TRUs. They would look like this in the alarm printout:
What you’re looking atAlarm header: gives the alarm class (A1=critical, take immediate action, A2=less critical, take action during wkg hours, A3=take action within a week, O1 &O2=observation only), switch name (i.e. PLT12C0), alarm number, date and time the alarm occurred. The alarm information is printed underneath. When investigating an alarm look at the date and time stamp to see when it came in.
The alarm on the CF, “BTS Internal”, means a fault on the CF which is caused by an RU inside the BTS (TRU, PSU, ECU, etc.) The “OML FAULT” alarm on the TRX means that the TRU has lost communication with the BSC.
If the whole site were down due to a T1 failure, you would see the Cell Logical Channels Availability Supervision alarms for all 3 sectors, plus the following alarms on the CF, and the DIP:
In this case we have an OML Fault on the CF and the whole site has lost communication with the BSC. Also there are faults on the DIP which indicate the fault code (ALL1) and the state (Unavailable).
RLCRPThe RLCRP command gives the resources for a cell, i.e. number of BCCH, SDCCH, CBCH (always 0) and TCH. If the cell is up and carrying traffic the printout will look like this:<rlcrp:cell=pl223a;
Among other things, this command will indicate which TRUs are in the site by giving a list of the respective TX, RX, and TS objects. If any are blocked (whether they be manually blocked, out of service, or automatically blocked), they will show “BLOCKED” in the printout as well. For this example though, we are only interested in which TRUs are assigned to the site; in our case the printout shows TRU #0, 2 and 4 are assigned (3 sectors, 1 TRU per sector). Since B sector is down, look at TRU #2 by getting the status of the MOs, following the hierarchy top to bottom, TRX to TS:
This command will give the Status of the MOs. The Status can be any of the following:
OPER (Operational)COM MBL (Manually Blocked)DEF MBL (Manually Blocked and out of service (Unloaded))NOOP BLO (Not Operational, Automatically Blocked)
In our example, the resulting printout tells you that the TRX is in state NOOP BLO. In most cases you will need to block it down and re-load it. When blocking down a TRU, start at the bottom of the hierarchy and work your way up to the TRX:
RXBLI:MO=RXOTS-46-2-0&&-7; (Block the Time Slots)RXBLI:MO=RXORX-46-2&RXOTX-46-2; (Block the RX & TX)RXBLI:MO=RXOTRX-46-2; (Block the TRX)
Then unload the TRU in the same manner:
RXESE:MO=RXOTS-46-2-0&&-7; (Unload the Time Slots)RXESE:MO=RXORX-46-2&RXOTX-46-2; (Unload the RX & TX)RXESE:MO=RXOTRX-46-2; (Unload the TRX)
Then reload the TRX:
RXESI:MO=RXOTRX-46-2; (Load the TRX)
Just do the TRX at first to verify that you can communicate with it. If the response comes back “LOADING FAILED”, it will most likely have to be reset manually. If the response comes back “COM EXECUTED MO NOT LOADABLE FROM THE BSC” you can continue on.
Test the TRX:
RXTEI:MO=RXOTRX-46-2; (Run diagnostic test on TRX)
If there is a fault in the TRU you will get a fault code in the response to the command. At this point the TRU may need to be replaced, depending on the fault. If there is no fault, continue loading the TRU:
RXESI:MO=RXOTX-46-2&RXORX-46-2; (Load the TX & RX)RXESI:MO=RXOTS-46-20&&-7; (Load the Time Slots)RXBLE:MO=RXOTRX-46-2; (Deblock the TRX)RXBLE:MO=RXOTX-46-2&RXORX-46-2; (Deblock the TX & RX)RXBLE:MO=RXOTS-46-20&&-7; (Deblock the Time Slots)
Note the order of loading and deblocking is opposite that blocking and unloading. Always block and unload from the bottom up, load and deblock from the top down.At this point you should be operational. Verify by re-issuing the command:
When the entire site is down you will have to look at the MOs above the TRU level, and at the Dip (DIgital Path). Since the Dip is the connection to the BSC, get its status first of all. Usually the Dip has the same number as the TG, but sometimes if the site is microwaved or goes through Newbridge, it will be different. To verify use the RXAPP command on the TG:
RXAPP:MO=RXOTG-46; (Print device connection to the TG)
This will give a list of the RBLT24 devices connected to the TG. This is how the RBLT/TG connection is actually made; on a device level rather than a Dip level. There are 24 devices per Dip, numbered consecutively. Here you can see the device range of 1104-1121. To find the Dip, take the 1st device and divide by 24, the Dip number is 46, same as the TG. NOTE: The DIP and TG vaues are usually the same, but not always. If there are Microwave hops or Newbridge involved, they may not be the same. To get the status of the Dip, type the following command:
DTSTP:DIP=46RBLT; (Status the DIP)
The Status should be WO. If it is ABL, there is probably a problem with the T1 and a ticket would be issued with Pac Bell. (For a list of fault codes associated with the Dip, see the list at the end.) If the Dip is in state WO, check the devices:
STDEP:DEV=RBLT24-1104&&-1121; (Check devices)
All the devices should be either SEBU (Sealed Busy, used for LAPD connections to the BTS), BUSY (carrying traffic), or IDLE (Working, not carrying traffic). If they are in state MBL you will not be able to load the BTS even if the Dip is working. To deblock the devices type the following command:
BLODE:DEV=RBLT24-1104&&-1121; (Deblock devices)
Then type the STDEP command again, they should now be IDLE. If this didn’t bring the site back, start looking at MOs:
RXMSP:MO=RXOCF-46&RXOTF-46&RXOIS-46; (Check status of CF, TF & IS)
If all these show OPER then start looking at the TRUs as before. It may be that something got left blocked down, or is not operational.If any of the MOs show NOOP BLO then first try to restore them by a simple Block/Deblock RXBLI/RXESE sequence. If that fails you will have to unload the site up to the CF, but in order to unload the CF you will have to first block and unload all of its subordinate MOs. If not, when trying to unload the CF you will get a response “SUBORDINATE MO NOT IN VALID STATE”. After unloading the CF attempt to reload it. If it comes back “Loading Failed” it may need to be reset manually.
Troubleshooting example #3 – MOs Operational, Sector still down
In situations where all the MOs in a sector are operational and the sector is still down, there may be problems in the definition of the MOs. The TRX, TX and RX have to be defined correctly for the TRU to be operational. They have the following properties:
TRXTEI value, same as the TRX #DCP1 value, Digital Connection Point 1DCP2 value, Digital Connection Point 2CELL, sector designation
TXBAND, Operating band, must be GSM1900ANT, Antenna designationMPWR, Maximum PowerCELL, sector designation
RXBAND, Operating band, must be GSM1900RXD, Diversity. AB for normal diversity, A for Antenna A only, B for Antenna B onlyANTA, Antenna A ANTB, Antenna B
If all the MOs are operational and the TRU is not carrying traffic, there is probably a mismatch in the definitions. For example if a TRU is in B sector but the TX is connected to A sector, the TX will not enable. To print the MO definitions, use the following command:
RXMOP:MO=RXOTRX-46-2&RXOTX-46-2&RXORX-46-2;
This will print a list of definitions in the order of the command, TRX, TX and RX. Look for Cell or Antenna assignments that are out of place. For example, if the Cell designation wasn’t made on a TX, the printout would look like this:
RADIO X-CEIVER ADMINISTRATIONMANAGED OBJECT DATA
MO CELL CHGR TEI SIG DCP1RXOTRX-46-2 PL223B ALL 2 UNCONC 134
MO CELL CHGR BAND ANT MPWRRXOTX-46-2 ALL ALL GSM1900 ALPHAB 45
MO RXD BAND ANTA ANTB
RXORX-46-2 AB GSM1900 ALPHAB BETAB
END
You would need to correct this before the TRU will go operational. To change a parameter on a MO you must first block and unload the MO so that it is in state DEF. Then enter the following command:
RXMOC:MO=RXOTX-46-2,CELL=PL223B;
Then load and deblock the TX as usual and it should come up OPER and you will show resources after a few seconds.
COMMAND LIST
The following is a summary of commands used in these procedures:
ALLIP; -Print Alarm list-Print status of:
RXMSP:MO=RXOCF-XX; Control Function RXOTF-XX; Timing Function
RXMFP:MO=RXOXX; -Print faults on MORXELP:MO=RXOXX; -Print Error log of MORLCRP:CELL=PLXXXA; -Print Cell ResourcesRXTCP:MOTY=RXOTG,CELL=PLXXXA; -Print TG connected to CellRXTCP:MO=RXOTG-XX; -Print Cells connected to TGRXCDP:MO=RXOTG-XX; -Print MO configurationRXBLI:MO=RXOXX; -Block an MORXBLE:MO=RXOXX; -Deblock an MORXESI:MO=RXOXX; -Load an MORXESE:MO=RXOXX; -Unload an MORXTEI:MO=RXOXX; -Test an MORXAPP:MO=RXOTG-X; -Print RBLT24 devices conn. to TGDTSTP:DIP=XXRBLT; -Status DIPSTDEP:DEV=RBLT24-XX&&-YY; -Print status of device rangeBLODI:DEV=RBLT24-XX&&-YY; -Block devicesBLODE:DEV=RBLT24-XX&&-YY; -Deblock devicesRXMOP:MO=RXOXXX; -Print MO definitionRXMOC:MO=RXOXX,(parameter)=(x); -Change MO definition
The following commands are not covered here but may be useful:
DTQUP:DIP=XXRBLT; -Print DIP hitsRXMDP:MO=RXOCF-XX; -Print devices connected to CF RXOTRX-XX-Y; “ “ “ TRX RXOTS-XX-YY-Z; “ “ “ TSRLCFP:CELL=PLXXXA; -Print channel numbers for CellRLDEP:CELL=PLXXXA; -Print Cell definitionRLSTP:CELL=PLXXXA; -Print Cell statusRLSTC:CELL=PLXXXA,STATE=HALTED; -To halt a sectorRLSTC:CELL=PLXXXA,STATE=ACTIVE; -To activate a sectorRLNRP:CELL=PLXXXA,CELLR=ALL; -Print neighbors to the cell
FAULT CODE LIST
^^^^^^ SO CF INTERNAL FAULT MAP CLASS 1A ^^^^^^^^^^Fault No Fault TypeCF-1A 0CF-1A 1 Reset, Power onCF-1A 2 Reset, SwitchCF-1A 3 Reset, WatchdogCF-1A 4 Reset, SW faultCF-1A 5 Reset, RAM faultCF-1A 6 Reset, Internal function changeCF-1A 7 XBUS related faultCF-1A 8 Timing unit VCO (Oscillator) faultCF-1A 9 Timing bus related faultCF-1A 10 Indoor temp out of safe rangeCF-1A 11CF-1A 12 DC voltage out of rangeCF-1A 13CF-1A 14 Local bus related faultCF-1A 15 RBS database corruptedCF-1A 16 RU database corruptedCF-1A 17 HW and IDB inconsistentCF-1A 18 Internal configuration failedCF-1A 19 Indoor temperature above safe rangeCF-1A 20 Indorr temperature below safe range - - 47
^^^^^^ SO CF INTERNAL FAULT MAP CLASS 2A ^^^^^^^^^^^^^^^Fault No Fault TypeCF-2A 0CF-2A 1 Reset, Power onCF-2A 2 Reset, SwitchCF-2A 3 Reset, WatchdogCF-2A 4 Reset, SW FaultCF-2A 5 Reset, RAM FaultCF-2A 6 Reset, Internal function changeCF-2A 7 RXDA Amplifier Current FaultCF-2A 8 VSWR Limits ExceededCF-2A 9 Power Limits ExceededCF-2A 10 DXU-Opt EEPROM checksum faultCF-2A 11CF-2A 12 RX Maxgain/Mingain ViolatedCF-2A 13 Timing Unit VCO AgeingCF-2A 14 CDU Supervision/Communication LostCF-2A 15 VSWR/Output Power Supervision LostCF-2A 16 Indoor Temp Out Of Normal Conditional RangeCF-2A 17 Indoor HumidityCF-2A 18 DC Voltage Out Of RangeCF-2A 19 Power System in Standalone ModeCF-2A 20 CF-2A 21 Internal Power Capacity ReducedCF-2A 22 Battery Backup Capacity ReducedCF-2A 23 Climate Capacity ReducedCF-2A 24 HW FaultCF-2A 25 Loadfile Missing in DXU or ECUCF-2A 26 Climate Sensor FaultCF-2A 27 System Voltage Sensor FaultCF-2A 28 A/D Converter FaultCF-2A 29 Varistor FaultCF-2A 30 Bus Fault
CF-2A 31 High Frequency Software FaultCF-2A 32 Non-Volatile Memory CorruptedCF-2A 33 RX Diversity LostCF-2A 34 Output Voltage FaultCF-2A 35 Optional Synchronization SourceCF-2A 36 RU Data Base CorruptedCF-2A 37 Circuit Breaker TrippedCF-2A 38 Default Values UsedCF-2A 39 RX Cable DisconnectedCF-2A 40 Reset, DXU Link LostCF-2A 41 Lost communication to TRUCF-2A 42 Lost communication to ECUCF-2A 43 Internal Configuration FailedCF-2A 44 ESB Distribution FailureCF-2A 45 CF-2A 46 DB parameter faultCF-2A 47
^^^^^ SO CF EXTERNAL CONDITION MAP CLASS 1 ^^^^^^^^Fault No Fault TypeEXT CF-1B 4 L/R SWI (BTS in local mode)EXT CF-1B 5 L/R TI (Local to remote while link lost)EXT CF-1B 7 Synch Info Lost (Valid for IP transmission)
^^^^^ SO CF EXTERNAL CONDITION MAP CLASS 2 ^^^^^^^^Fault No Fault TypeEXT CF-2B 7 Synch Info Lost (Valid for IP transmission)EXT CF-2B 9 RBS DOOR (RBS cabinet door open)EXT CF-2B 10 MAINS FAIL (External power source fail)EXT CF-2B 11 ALNA/TMA FaultEXT CF-2B 12 ALNA/TMA DegradedEXT CF-2B 13 Auxiliary Equipment Fault
^^^^^^^^ SO CF, REPLACEMENT UNIT MAP ^^^^^^^^^^^^^^^No. Replacement UnitCF RU 0 DXUCF RU 1 ECUCF RU 2 MICRO RBS or SIR CABINETCF RU 3 Y LINKCF RU 4CF RU 5 CDUCF RU 6CF RU 7 PSUCF RU 8CF RU 9 BDM or BFUCF RU 10 ACCUCF RU 11 Active CoolerCF RU 12 ALNA/TMA ACF RU 13 ALNA/TMA BCF RU 14 BATTERYCF RU 15 FANCF RU 16 HEATERCF RU 17 HEATER EXCHANGER EXT FANCF RU 18 HEATER EXCHANGER INT FANCF RU 19 HUMIDITY SENSORCF RU 20 TMA CMCF RU 21 TEMPERATURE SENSORCF RU 22 CDU HLOUT HLIN CABLECF RU 23 CDU RX IN CABLECF RU 24 CU or TCUCF RU 25 DU or FDUCF RU 26 FUCF RU 27 FU CU PFWD CABLE or FDU TCU PFWD CABLE
CF RU 28 FU CU PREFL CABLE or FDU TCU PREFL CABLECF RU 29 CAB HLIN CABLECF RU 30 CDU BUSCF RU 31 ENVIRONMENTCF RU 32 LOCAL BUSCF RU 33 POWER COMMUNICATION LOOPCF RU 34 RBS DBCF RU 35 EOM BUSCF RU 36 TIMING BUSCF RU 37 FDU CXU RXA CABLECF RU 38 FDU CXU RXB CABLECF RU 39 XBUSCF RU 40 ANTENNACF RU 41 PSU DC CABLECF RU 42 CXU DC CABLECF RU 43 FLASH CARDCF RU 44 PTUCF RU 45 BATTERY TEMP SENSORCF RU 46 FCUCF RU 47 ^^^^^ SO TRXC INTERNAL FAULT MAP CLASS 1A ^^^^^^^^^^Fault No Fault TypeTRX-1A 0 TRX-1A 1 Reset, Power onTRX-1A 2 Reset, SwitchTRX-1A 3 Reset, WatchdogTRX-1A 4 Reset, SW faultTRX-1A 5 Reset, RAM faultTRX-1A 6 Reset, Internal function changeTRX-1A 7 Radio Baseband Loop Test FaultTRX-1A 8 Timing Reception FaultTRX-1A 9 Signal Processing FaultTRX-1A 10 Tora Dannie Communication FaultTRX-1A 11 DSP CPU Communication FaultTRX-1A 12 Terrestrial Traffic Channel FaultTRX-1A 13 RF Loop Test FaultTRX-1A 14 RU Data Base CorruptedTRX-1A 15 XBus Communication FaultTRX-1A 16 Initiation FaultTRX-1A 17 X-Interface FaultTRX-1A 18 DSP FaultTRX-1A 19 Reset, DXU Link LostTRX-1A 20 HW And IDB InconsistentTRX-1A 21 Internal Configuration FailedTRX-1A 22 Voltage Supply Fault - - -TRX-1A-47
^^^^^ SO TRXC INTERNAL FAULT MAP CLASS 1B ^^^^^^^^^^^Fault No Fault TypeTRX-1B 0 CDU Not UsableTRX-1B 1 Indoor Temp Out Of Safe RangeTRX-1B 2 TRX-1B 3 DC Voltage Out Of RangeTRX-1B 4 Indoor Temp Above Safe RangeTRX-1B 5 Indoor Temp Above Safe Range - - 47
^^^^^ SO TRXC INTERNAL FAULT MAP CLASS 2A ^^^^^Fault No Fault TypeTRX-2A 0 RX cable disconnectedTRX-2A 1 RX EEPROM checksum faultTRX-2A 2 RX Config table checksum faultTRX-2A 3 RX Synthesizer unlockedTRX-2A 4 RX Internal voltage faultTRX-2A 5 Astra Dixie communication faultTRX-2A 6 Astra Tracy communication faultTRX-2A 7 TX EEPROM checksum faultTRX-2A 8 TX Config table checksum faultTRX-2A 9 TX Synthesizer unlockedTRX-2A 10 TX Internal voltage faultTRX-2A 11 TX High temperatureTRX-2A 12 TX Output power limits exceededTRX-2A 13 TX SaturationTRX-2A 14 Voltage supply faultTRX-2A 15 VSWR/Output Power Supervision LostTRX-2A 16 Non volatile memory corruptedTRX-2A 17 Loadfile Missing in TRUTRX-2A 18 DSP FaultTRX-2A 19 High frequency software faultTRX-2A 20 RX initiation faultTRX-2A 21 TX initiation faultTRX-2A 22 CDU-bus communication faultTRX-2A 23 Default values usedTRX-2A 24TRX-2A 25 TX Max Power RestrictedTRX-2A 26 DB parameter faultTRX-2A 27 RX Path Fault
^^^^^^^ SO TRXC EXTERNAL CONDITION MAP CLASS 1 ^^^^^^^^^^^^^Fault No Fault TypeEXT TRX-1B 4 L/R SWI (TRU In Local Mode)EXT TRX-1B 5 L/R TI (Local to Remote while Link Lost)
^^^^^^ SO TRXC, REPLACEMENT UNIT MAP ^^^^^^^^^^^^^^^NO. RUTRX RU 0 TRU or dTRUTRX RU 1TRX RU 2 MICRO RBS or SIR CABINETTRX RU 3 CXU dTRU RXA CABLETRX RU 4 CXU dTRU RXB CABLETRX RU 5 CDU CXU RXA CABLETRX RU 6 CDU CXU RXB CABLETRX RU 7TRX RU 8TRX RU 9TRX RU 10 CDU TO TRU PFWD CABLETRX RU 11 CDU TO TRU PREFL CABLETRX RU 12 CDU TO TRU RXA CABLETRX RU 13 CDU TO TRU RXB CABLE - - 47
^^^^^^ AO TS EXTERNAL CONDITION MAP CLASS 1 ^^^^^^^^^^Fault No Fault TypeEXT TS-1B 3 TRA/PCU (Remote Transcoder/PCU Com. Lost)
^^^^^^ AO TF INTERNAL FAULT MAP CLASS 1B ^^^^^^^^^^^^^^^Fault No Fault TypeTF-1B 0 Optional synchronization source
TF-1B 1 DXU-opt. EEPROM checksum fault
^^^^^^ AO TF EXTERNAL CONDITION MAP CLASS 1 ^^^^^^^^^^^^^Fault No Fault TypeEXT TF-1B 0 EXT SYNCH (No Usable External Reference)EXT TF-1B 1 PCM SYNCH (No Usable PCM-Reference)
^^^^^ AO TF EXTERNAL CONDITION MAP CLASS 2 ^^^^^^^^^Fault No Fault TypeEXT TF-2B 0 EXT SYNCH (No Usable External Reference)EXT TF-2B 1 PCM sync (no usable PCM-reference)
^^^^^ AO TX INTERNAL FAULT MAP CLASS 1A ^^^^^^^^^^
Fault No Fault TypeTX-1A 0 TX offending
^^^^^ AO TX INTERNAL FAULT MAP CLASS 1B ^^^^^^^^^^^^^^Fault No Fault TypeTX-1B 0 Not UsableTX-1B 1 CDU VSWR Limits ExceededTX-1B 2 CDU Output Power Limits ExceededTX-1B 3 TX-1B 4 TX Antenna VSWR Limits ExceededTX-1B 5 TX-1B 6 TX EEPROM checksum faultTX-1B 7 TX Config table checksum faultTX-1B 8 TX Synthesizer A/B unlockedTX-1B 9 TX Synthesizer C unlockedTX-1B 10 Astra Tracy communication faultTX-1B 11 TX Internal voltage faultTX-1B 12 TX High temperatureTX-1B 13 TX Output power limits exceededTX-1B 14 TX SaturationTX-1B 15 TX-1B 16 TX-1B 17 TX Initiation faultTX-1B 18 HW FaultTX-1B 19 SW Load/Start FaultTX-1B 20 Input Power FaultTX-1B 21 Park FaultTX-1B 22 VSWR/Output Power Supervision LostTX-1B 23 Reset, Power OnTX-1B 24 Reset, Communication FaultTX-1B 25 CU reset, watchdogTX-1B 26 CU fine tuning faultTX-1B 27 TX Max Power RestrictedTX-1B 28 TCU High Temperature - -TX-1B 47 TX Auxiliary Equipment Fault
^^^^^ AO TX INTERNAL FAULT MAP CLASS 2A ^^^^^Fault No Fault TypeTX-2A 0 TX diversity fault
^^^^^ AO RX INTERNAL FAULT MAP CLASS 1B ^^^^^^^^^^^^^^^^^^Fault No Fault TypeRX-1B 0 RXDA Amplifier current faultRX-1B 1 ALNA/TMA faultRX-1B 2RX-1B 3 RX EEPROM checksum faultRX-1B 4 RX Config table checksum fault
RX-1B 5 RX Synthesizer A/B unlockedRX-1B 6 RX Synthesizer C unlockedRX-1B 7 Astra Dixie communication faultRX-1B 8 RX Internal voltage faultRX-1B 9 RX cable disconnectedRX-1B 10 RX Initiation faultRX-1B 11 CDU Output voltage faultRX-1B 12 TMA CM Output Voltage FaultRX-1B 13 RX Path Fault - -RX-1B 47 RX Auxiliary Equipment Fault
^^^^^^^^^^^^^^^ TERMINOLOGY ^^^^^^^^^^^^^^^^^^^^Fault No
The fault number is equal to the bit position in thefault map reported over the Abis interface.
INTERNAL FAULT MAP CLASS 1AAffect MO functionality. Faulty HW is part of the signaling MO.
INTERNAL FAULT MAP CLASS 1BAffect MO functionality. Origin of the fault is external to the signaling MO.
INTERNAL FAULT MAP CLASS 2ANot affect MO functionality. Faulty HW is part of the signaling MO.
EXTERNAL CONDITION MAP CLASS 1Affect MO functionality. The conditions are TG external.
EXTERNAL CONDITION MAP CLASS 2Not affect MO functionality. The conditions are TG external.
REPLACEMENT UNIT MAP (RU MAP)Suspected HW causing the faults in internal fault maps.
MOMangaged Object, the class of all object in the BTS O&Mmodel which BSC can communicate with.
SOService Object, an abstract subclass of MO which handlesHW. A SO manages one or more RUs.
AOApplication Object, an abstract subclass of MO which onlyhandles functionality.
RUReplaceable Unit, Smallest unit in a RBS2000 cabinetwhich can be replaced.
^^^^^ LOGICAL RU ^^^^^A unit which can be refered to but is not a singlepysical unit. There are tree different kinds of logical RUs:1. BUSSES -XBUS -LOCAL BUS -TIMING BUS
-CDU BUS -POWER COMMUNICATION LOOP2. ANTENNAS -RX A -RX B -TX A -TX B3. ENVIRONMENT -TEMPERATURE
^^^^^^^^^^^^^^^^ DIGITAL PATH FAULTS ^^^^^^^^^^^^^^^DIP fault 1 Alarm indication signal AISDIP fault 2 Loss of frame alignment
DIP fault 3 Excessive error rateDIP fault 4 Alarm indication from the remote endDIP fault 5 Alarm indication signal in time slot 16DIP fault 6 Loss of multiframe alignmentDIP fault 7 Alarm ind. from remote end signalling equipmentDIP fault 8 Alarm indication signal ALL1DIP fault 9 Loss of CRC multiframe alignmentDIP fault 10 Consectutive severely errrored seconds
^^^^^^^^^^^ RADIO X-CEIVER ADMINISTRATION ^^^^^^^^^^^^ MANAGED OBJECT STATUSBTS: Last known state of the MO in the BTSRES= MO is in state RESETSTA= STARTEDDIS= DISABLEDENA= ENABLED
BITMAP for BLO (Blocking origin of automatic blocking)HEX BITxxx1 0 AP object blocked from own superv. perm.xxx2 1 AT object blocked from own superv. temp.xxx4 2 AS object blocked due to fault suspectedxxx8 3 TG object blocked from TGxx10 4 TRXC object blocked from TRXCxx20 5 TGC object blocked from TGCxx40 6 OML object blocked from OMLxx80 7 X sparex100 8 LMT obj. blo. due to local maint. activitiesx200 9 CF object blocked from CFx400 10 LOM object blocked from due to local modex800 11 LOOP obj. blo. from due to loop test failure
BITMAP for BLA (Blocking origin of blocking due to action not completed)HEX BITxxx1 0 BNU obj. needs reset & uncond. load or reset & load. in progr.xxx2 1 BNR obj. needs reset & load check or reset & load. in progr.xxx4 2 BNL obj. needs reset and load check or loading in progressxxx8 3 BNP obj. needs polling or polling in progressxx10 4 BNT obj. needs testing or testing in progressxx20 5 BNI obj. needs intermittent test or interm. test in progr.xx40 6 BND obj. needs updating of MO dataxx80 7 BNS obj. needs to be startedx100 8 BNM obj. needs to be manually deblocked (BTS initiated)x200 9 BNO obj. needs loop test or loop loop test in progress
BITMAP for LMO (Blocking origin of logical managed object TS)HEX BITxx20 5 CRN LTS blocked due to creation in progressxx40 6 ENA LTS blocked due to not enabledxx80 7 Xx100 8 MO LTS blocked from TSx200 9 LTF LTS blocked from LTFx400 10 RSL RSL blocked from RSLx800 11 DEV LTS blocked from speech/data device1000 12 X2000 13 SYNCB LTS blo. due to sync. fault in BTS4000 14 X8000 15 CHG blocked due to change
BITMAP for LMO (Blocking origin of logical managed object TF)HEX BITxx20 5 CRN LTF blocked due to creation in progressxx40 6 ENA LTF blocked due to not enabled
xx80 7 Xx100 8 MO LTF blocked from TF
DIGITAL PATH (DIP) FAULT CODE LIST
~~~Numeric vaues~~~
1 Alarm indication signal, AIS2 Loss of frame alignment 3 Excessive error rate 4 Remote defect indication (Alarm indication from remote end in some AI2 documents) 5 Alarm indication signal in time slot 16 6 Loss of multiframe alignment 7 Alarm indication from the remote end signalling equipment 8 Alarm indication signal, ALL1 9 Loss of incoming signal 10 Consecutive severely errored seconds
~~~Abbreviations~~~
AIS Alarm indication signal LOF Loss of frame alignment ERATE Excessive error rate RDI Remote defect indication (REFF in some AI2 documents) AISM Alarm indication signal in time slot 16 LOMF Loss of multiframe alignment REFM Alarm indication from the remote end signalling equipment ALL1 Alarm indication signal LOS Loss of incoming signal CSES Consecutive severely errored seconds
Some common Dip faults you will see:
4, RDI Remote Defect Indicator (Yellow Alarm), problem at the remote end, either NIU or CSU2&8, LOF&ALL1, Loss of Framing, All 1’s alarm, the T1 is down due to a failure in the span2&9, LOF&LOS, Loss of Framing, Loss of Incoming signal, the circuit is either not patched in the BSC or there’s a T-Berd in the DSX
