List of Change Notes

File Name: SRAN18A 1.3.2 Change Notes

Product Family: SRAN
Product: SBTS
System Release: SRAN18A

Creation date: 04-Sep--2019

Overview
This document contains list of all corrections delivered up to SRAN18A 1.3.2 SW.

Instruction
This document contains combined information from all of the regular Change Note Forms documents released for SRAN18
release for SBTS & BTS MEDproduct(s).
In order to check the exact list of of corrections provided in a maintenance SW deliveries filter the list of releases in column
Corrected in on the Change Notes sheet.
 Change Note ID Title Valid for Product
1808 [SBTS18A][Airscale][PET] flooding error Flexi Multiradio BTS
"PHY_PuschReceiveGroupedRespU was not received in SingleRAN
expected time for" for NB IoT traffic
1809 [BTSMED][18A][PET]BTSMED can't decode Trace Flexi Multiradio BTS
Message due to NBS send so fast SingleRAN

1874 Corrupted alarm fluctuating on AHCA during Flexi Multiradio BTS

commissioning of site SingleRAN

1869 [SBTS18A]Unexpected fault 4001 on WCDMA after Flexi Multiradio BTS

Upgrade SingleRAN

1875 [SRAN18A NPI] validation error when LTE3145 slim Flexi Multiradio BTS
carrier activated on FXDD radio SingleRAN

1870 [SRAN18A NPI] NBIOT has a lot of RRC reject Flexi Multiradio BTS
SingleRAN

1919 AMOB FAN Unit for cooling running on High speed and Flexi Multiradio BTS
generating lot of noise. SingleRAN

1924 SBTS in commissioned state after SW upgrade Flexi Multiradio BTS

SingleRAN

1925 FSP-13 crashes when fetching snapshot in a continuous Flexi Multiradio BTS
loop with HL 3RAT traffic SingleRAN

1922 RM's not detected in expected time Flexi Multiradio BTS

SingleRAN

1920 [NPI SRAN18SP] BCCH alarm is not visible in element Flexi Multiradio BTS
Manager even decline in KPI can notice . Block .- unblock SingleRAN
solve problem
1921 RANDOM 2G SECTOR GOING DOWN IN SRAN BTS Flexi Multiradio BTS
SingleRAN

1923 [SBTS18SP] Flexi Multiradio BTS

SingleRAN

2012 RF module failure and Transmission path failure in Flexi Multiradio BTS
stadium L26 SingleRAN

2013 2G KPI degraded after SRAN17A 1.1 implementation Flexi Multiradio BTS
SingleRAN

2014 [FL18 Drop6.0 _FFA]: UL noise (PUSCH and PUCCH), Flexi Multiradio BTS
RSSI and SINR degraded on 16 eNB and 77 eNB clusters SingleRAN
with Correction for LTE 3577 Predefined
1956 RTWP values shift seen on 3G cells after swapping to new Flexi Multiradio BTS
RM AHEGA SingleRAN

2015 2,5 times increase in TCH drop rate after SRAN 17A Flexi Multiradio BTS
upgrade SingleRAN

1955 SRAN18SP NPI: Propagation delay variation on AHEGB Flexi Multiradio BTS
hardware SingleRAN

2016 SRAN18SP NPI: Alarm 7745 CHANNEL FAILURE RATE Flexi Multiradio BTS
ABOVE DEFINED THRESHOLD raised for TRX3 (site SingleRAN
1035BB)
2018 FL18SP FSA (GA2) 84429 UHFA 14,24,34 cell down : Flexi Multiradio BTS
alarms 7653 and 6253 SingleRAN

2019 Dualband RRH (AHLBA and AHFIB) PIM Cancellation Flexi Multiradio BTS
introducing noise in FL18 GA3 SingleRAN

2020 [FL18A Drop2_FFA]: Flexi Multiradio BTS

VS_RRC_reconf_CA_deconfigure_fail_rate increase by SingleRAN
50+% with attempt increasing by ~30% on FL18A drop2
2021 Site AT0216BA sect 8 carriers 1&2 DRS success=0 Flexi Multiradio BTS
SingleRAN

1954 SBTS\RF Module gain adjusting failure\TT-000040144761 Flexi Multiradio BTS

SingleRAN

CNF000143 Incorrect alarm time Flexi Multiradio BTS

SingleRAN

1957 FL18A FOA: ASIA auto reset / 4383ASIA observed on Flexi Multiradio BTS
131005_MCKINNEY_NORTH_WT SingleRAN

1958 Not be able to open SRAN Element Manager from NetAct Flexi Multiradio BTS
Monitor for 3G WBTS part of SRAN SBTS17A. SingleRAN

1959 [FL18MP3.1][CRT][AirScale] AFHIB recovery fails during Flexi Multiradio BTS

CRT run FL18 3.1, cell disabled due AFHIB lost with alarm SingleRAN
0010 failure in optical interface
1960 FL18A (WDC 5G FOA): Counter M8006C332 is orders of Flexi Multiradio BTS
magnitude bigger than M8006C333 SingleRAN

1961 NPI SRAN18SP - Plan provisioning is failed due to PDL Flexi Multiradio BTS
validation failure SingleRAN

1963 S1-Connection Establishment Success Ratio for NB IoT Flexi Multiradio BTS
UEs problems after going to FL18 SingleRAN

1964 [TL18A pilot][PM Counter][M8001C5][FSIH+FZFF-e] UL Flexi Multiradio BTS

latency increased after upgrading, SingleRAN

1965 NPI SRAN18SP - Plan provisioning failed due to picPool Flexi Multiradio BTS
assignment SingleRAN

1966 Fault 10 reporting on AHPMDA after SC autonomous Flexi Multiradio BTS

reset SingleRAN

1974 WRN/LTE Flexi Multiradio BTS

L2/TeidManager/c3FCDrB197u1E35x4C5l1F/updateTeid SingleRAN
MapInternal: teid already in use
1967 2 LAA cells remained down after FL18A GPL application Flexi Multiradio BTS
on 084006 SingleRAN

1968 Alarm 1807 reported after SW upgrade Flexi Multiradio BTS

SingleRAN

1969 OAM stuck state after attempting to change cells 1/12/14 Flexi Multiradio BTS
from 2T4R to 2T2R SingleRAN

1970 Plan provisioning failed due to BTS didn't respond to Flexi Multiradio BTS
provision request within 270s SingleRAN

1971 Unable to perform parameter modification remotely from Flexi Multiradio BTS
NetAct using XML plan SingleRAN

1972 Cannot provision lower bandwidth e.g. 4.4Mhz in TX for Flexi Multiradio BTS
FXDA SingleRAN

1973 SBTS can not activate Lean GSM Solution feature. Flexi Multiradio BTS
SingleRAN

1975 NPI SRAN18SP - WebEm poor perfomance during Flexi Multiradio BTS
configuration validation SingleRAN

1976 All WCDMA cells stuck in "Commissioned" State after new Flexi Multiradio BTS
WCDMA cell addition SingleRAN

1977 eNB had Spurious reset during SU to PT4.4 Flexi Multiradio BTS
SingleRAN

1978 STBTS fault "topSlavePort value is out of range" : ref Flexi Multiradio BTS
Emergency S182 | CAS-191904-N6G6 SingleRAN
1979 [NPI SRAN18A] sIntrasearch wrong value after conversion Flexi Multiradio BTS
to SRAN18A SingleRAN

1980 [RP001614][SBTS18A] Object RSL in commissionning not Flexi Multiradio BTS

created after upgrade from WBTS18 to SBTS SingleRAN

1981 [SBTS18SPMP2][R4][LTE][RP000375] SyncE Flexi Multiradio BTS

Syncronization source is not taken in use after BTS reset SingleRAN
when 2 syncE sources are in priority list.
1982 [RP1780 DROP2] Transport layer connection failure in S1 Flexi Multiradio BTS
interface (6202) is raised when MRBTS-11231/LNBTS- SingleRAN,Flexi
11231 caClusterMemberId=4 Multiradio BTS
1983 [SBTS18A][FSMF+FSMF] All cells hosted by AHFIB SingleRAN
Flexi Multiradio BTS
disabled after primary link removal SingleRAN

1984 [SBTS18A][FSMF+FSMF][RGT] SRIO LED is gray (OFF) Flexi Multiradio BTS

on SC (ESM) module after domain collision is resolved SingleRAN

1985 [SBTS18A][ASIA]MO TOPF_R-1 diasppeared after reset Flexi Multiradio BTS

SingleRAN

2023 [SBTS18A] can't modify lcrid via ADMIN (greyed out) Flexi Multiradio BTS
SingleRAN

1986 [Airscale-FSMF][FL18A-GF18 2.0] EEPROM read error Flexi Multiradio BTS

(2078) alarm during '100 LTE Site reset' test SingleRAN

2011 [SBTS18SP_P7][CIT][FSMF+FSMF]BTS site autonomous Flexi Multiradio BTS

reset as recovery action after software update SingleRAN

1987 [SBTS18A] Unexpected radio module type can be added Flexi Multiradio BTS
from Wizard SingleRAN

1988 [SBTS18A][FSMF+FSMF][CR2] Wrong transmission Flexi Multiradio BTS

distance of RP3-01 connection between SMODs SingleRAN

1989 [CRT][Admin][SBTS][FDD][SBTS18A] Cannot log into Flexi Multiradio BTS

Admin using Google Chrome browser SingleRAN

1990 [OAM_SCT][SBTS][FDD][xL18A][R44][SMOKE] Flexi Multiradio BTS

Commissioning - LTE cells in Validated state - faultID: SingleRAN
4261 visible
1991 PortMode parameter value missing after upgrade 18SP to Flexi Multiradio BTS
18A SingleRAN

1992 [SBTS18A] [R3,R4] [RP000384]topFreqSyncSLS Flexi Multiradio BTS

(M51361C4) counter value is too low SingleRAN

1993 Confusing warning "Parameter relations not met" appears Flexi Multiradio BTS
after setting distRefPoint parameter in TIMINGGROUP SingleRAN
MO
1994 Inconsistency between reported alarm for fault 23 and Flexi Multiradio BTS
state of cells on BTS after use of RMOD (AHEH) with SingleRAN
FDSW.
1995 Unexpected fault 4341 after BBMOD hot removal Flexi Multiradio BTS
SingleRAN

1996 Fault 145 is not cleared in one of LCGs when resources Flexi Multiradio BTS
for PIC become available. SingleRAN

1997 Fault 6261 contains wrong description Flexi Multiradio BTS

SingleRAN

1998 [SBTS18A][RGT]FEG is not correctly calculated for Flexi Multiradio BTS

AHPMDA radio modules after PASSDEV removal SingleRAN

1999 [SBTS18A][FSMF] Crash during snapshot Flexi Multiradio BTS

SingleRAN

2000 [SRAN18A][FSMF]: 3/6 LTE cells remais down after Flexi Multiradio BTS
startup due the fault 4076 SingleRAN
2001 [SBTS 18A][CNI 32626] RF module failure is raised on Flexi Multiradio BTS
WCDMA cells when configuring cell set of the CNI SingleRAN

2002 [SBTS00][Legacy]BTS acted the RNW plan file too long Flexi Multiradio BTS
time SingleRAN

2003 [CNI-24657][SBTS18A] [Dualcore] Critical fault 4083 Flexi Multiradio BTS

visible in EM after successful fallback procedure. Cells SingleRAN
operational state: Disabled
2004 SRAN18A: IP connectivity test triggers TOP alarm and Flexi Multiradio BTS
sync is lost SingleRAN

2005 [SBTS18A][RP002128][FSMF+FSMF] WCDMA cell Flexi Multiradio BTS

addition causing extension reset fault 4114 SingleRAN

2006 [SBTS18A][Regression] Cablink between SMOD an Flexi Multiradio BTS

RMOD is not correctly detected on uncommissioned BTS SingleRAN
with long fiber in use.
2007 [LTE2745][LTE][FDD][Airscale][FL18A][ET][OAM_SCT] Flexi Multiradio BTS
Failure in replaceable baseband unit (2019) after hot swap SingleRAN
with signifficant difference of fiber lengths
2008 [OAM_SCT][LTE][TDD][trunk][R4][SMOKE] BTS startup Flexi Multiradio BTS
after Site reset delayed SingleRAN

2009 [SBTS18A][FSMr3][FRHB] Cell Power Failure (Fault Flexi Multiradio BTS

ID:4090, Alarm ID:7116) after configuring Supplemental SingleRAN
Downlink Carrier with 3CC DL Carrier Aggregation
2010 LTE2557, LTE1804
[SBTS18A][Admin]The snapshot exported from Site View Flexi Multiradio BTS
does not provide the full content of the existing SingleRAN
configuration
2073 On some SRAN WBTS we observed cases of HSPA Flexi Multiradio BTS
power loss. SingleRAN

2074 Iur drop call_SBTS Flexi Multiradio BTS

SingleRAN

2075 Failures on SBTS with 16 sectors Flexi Multiradio BTS

SingleRAN

2076 [FL18SP_ENB_0000_000732_000000] 2nd chain cell Flexi Multiradio BTS

became disabled after applying object locking parameter SingleRAN
when 1st chain cell (FHCA) faulty
2077 [FL18A Drop3.0 _FFA] Multiple sites reset with fault 4383 Flexi Multiradio BTS
SingleRAN

2078 SRAN : cannot collect snapshot with BTS busy Flexi Multiradio BTS
SingleRAN

2079 WRN/LTE Flexi Multiradio BTS

L2/TeidManager/c3FCDrB197u1E35x4C5l1F/updateTeid SingleRAN
MapInternal: teid already in use
2080 FL18A FOA - 131016/131048 DSP reset/Cells down after Flexi Multiradio BTS
Download of FL18A PT4.3 (site running PT4.2) SingleRAN

2081 [SRAN18A NPI] Sleeping Cell on SRAN18A NB-IOT site Flexi Multiradio BTS
SingleRAN

1975 NPI SRAN18SP - WebEm poor perfomance during Flexi Multiradio BTS
configuration validation SingleRAN

2082 Cell disabled due to unknown reason Flexi Multiradio BTS

SingleRAN

2083 SDU Data Volume counters for CAT-M Profile is showing Flexi Multiradio BTS
very large value after FL18A - gpl application SingleRAN

2084 [mMIMO] [FIT] TL18 NPI mMIMO: Special subframe 6 Flexi Multiradio BTS
feature can not be activated with AAHE MAA SingleRAN

2085 Unable to configure UL CA for LTE3864_UL Flexi Multiradio BTS

CA_5B_10Mhz+5MHz combination. SingleRAN
2086 208_2G sites and 218_3G sites in multiple BSC/RNC Flexi Multiradio BTS
were down SingleRAN

2087 NPI SRAN18SP - Diagnostic Files collected (6450) - FRI Flexi Multiradio BTS
crash SingleRAN

2088 [LTE4416][LAA][L18A] Cells are toggling between working Flexi Multiradio BTS
and faulty state SingleRAN

2089 [FL18A][SB][PET][3G-4G][FSME-FSMF] DSP group Flexi Multiradio BTS

autonomous reset (fault 6709) during stability testing SingleRAN

2090 Verizon FL18A FOA (GA1.1): 7652_6707 ABIA Flexi Multiradio BTS
Autonomous Reset on 084003_LEONARD_STREET SingleRAN

2091 [FL00][LTE2523][FRGY][Automated] Alarm "RF Module Flexi Multiradio BTS

Unauthorized" (4278) does not appear after removing SingleRAN
rfmplugin from ENB
2092 [SBTS18SP] DSP crash and WCDMA down in Stability Flexi Multiradio BTS
testing SingleRAN

2093 [SBTS18SP][R3][L] [SR000375] SYNCE missing- no Flexi Multiradio BTS

alarms SingleRAN

2095 eNodeB inter-site CA (LTE3022) is not enabled Flexi Multiradio BTS

automatically after recovery from X2 link failure SingleRAN

2117 Flapping alarm "No connection between primary and BTS Flexi Multiradio BTS
extension system module" on AisScale SBTS SingleRAN

2118 [SBTS19] fault 6282 is raised after the X2 link is setup Flexi Multiradio BTS
since the inconsistent LNADJ id is setup by RROM SingleRAN

2119 Multiple autonomous site resets with long fiber chaining Flexi Multiradio BTS
configuration, WCDMA not operational (fault 4001), RF SingleRAN
unit auto reset (fault 1900)
2120 [SBTS18SPmMP1.3][Regression]MCPA Power Pooling is Flexi Multiradio BTS
not supported with Dual band and triple band AS from SingleRAN
Rel5.1 radios
2097 Increase in Drop Rate along with RRE and CA Config Fail Flexi Multiradio BTS
with CRL23388 activation SingleRAN

2127 After SBTS restoration TRX goes to BL-RSL\\TT- Flexi Multiradio BTS
000036453775\\2G SingleRAN

2128 Reported number of eRAB with NBR remains zero after Flexi Multiradio BTS
LTE1042 activation SingleRAN

2130 SBTS 2G present non real alarms of VSWR Flexi Multiradio BTS
SingleRAN

2131 DSP application fatal error Flexi Multiradio BTS

SingleRAN

2132 Uplink degradation service after restart 2G BTS. Flexi Multiradio BTS
SingleRAN

2133 DSP platform fatal error Flexi Multiradio BTS

SingleRAN

2134 No alarms for BB sub unit HW fault in FSMF (In ref to Flexi Multiradio BTS
CAS-151966-S0L0 || Random Cells going faulty_ SingleRAN
Configuration error-BTS config error (Not enough HW for
2135 Increase
LCR) - NA)
in CAT-M RRE failures Flexi Multiradio BTS
SingleRAN

2136 Increased BER detected on the optical connection to Flexi Multiradio BTS
Radio Module SingleRAN

2137 Dummy SMOD after swapping two SMOD in the AirScale Flexi Multiradio BTS
rack SingleRAN
2138 Bharti_Orissa_7114-'CELL SERVICE PROBLEM:' Cell Flexi Multiradio BTS
configuration data distribution failed' SingleRAN

2139 Wrong BW showing on cell in MRBTS post upgrade from Flexi Multiradio BTS
SBTS SingleRAN

2140 Failure in optical interface for AZRB after SW upgrade Flexi Multiradio BTS
SingleRAN

2141 Site is unstable after that with cells crashing and also Flexi Multiradio BTS
seeing C-plane overload SingleRAN

2142 The validation from NetAct's CM Operation manager Flexi Multiradio BTS
always failed after activated the feature ' LTE486 PLMN ID SingleRAN
selected mobility profiles ' in the SRAN18A site.
2143 After MIMO/power changes two cells 7A& 7B of AZL06214 Flexi Multiradio BTS
stopped taking traffic/became sleepy SingleRAN

2144 [NPI LTE3071][FL18A Flexi Multiradio BTS

FL18A_ENB_0000_000689_000106] DSP crash(FID6707) SingleRAN
-UeStorage::add() is full at UeStorage.cpp, line: 0x28
2145 Problem with return from Test dedicated state Flexi Multiradio BTS
SingleRAN

2146 MacHS DSP crash during stability testing Flexi Multiradio BTS
SingleRAN

2147 SWDL error when activation tap is not placed Flexi Multiradio BTS
SingleRAN

2148 FATAL EXCEPTION Nid:0x2241 TYPE:EXTERNAL: Flexi Multiradio BTS

[0xEA07A]CpuL1DMemoryProtectionFault Violated SingleRAN
memory address(L1DMPFAR):0x00000010 Local access
2149 type:supervisor
Configuration error:
readInvalid
** frequency channel for the BTS Flexi Multiradio BTS
HW (1807) from URCC, URCB and URKA SingleRAN

2150 Cells remain down on 085800 and 085829 after upgrade Flexi Multiradio BTS
to FL18A 0.2 with 4256 fault (Fiber Delay and Antenna SingleRAN
Round Trip Delay exceeded)
2151 GSM UL measurement is not working on ANT2 / ANT4 Flexi Multiradio BTS
SingleRAN

2152 Inband IoT test model A14-1 24 (FRC:1240141050) not Flexi Multiradio BTS
working SingleRAN

2153 SRAN BTS Upgrade failed while upgrading from Flexi Multiradio BTS
SRAN16.10 to SRAN17A for Packet over TDM sites SingleRAN

2154 Failure in Optical (FauiltId 10) & BB bus Reception Error Flexi Multiradio BTS
MUKSU (FaultId 2016) Raised after Planned SingleRAN
Commissioning
2155 Cells disabled due to unknown problems (4261) Flexi Multiradio BTS
SingleRAN

2156 SW Upgrade from SRAN18 0.2 to SRAN18A 0.1 triggers Flexi Multiradio BTS
Relation Errors SingleRAN

2157 High HARQ failure rate in NB-IOT sites Flexi Multiradio BTS
SingleRAN

2129 Problem with LTE1130 "Dynamic PUCCH" for NB-IOT Flexi Multiradio BTS
SingleRAN

1950 TCH Assignment failure on 1800 after any Fluctuation on Flexi Multiradio BTS
site SingleRAN
2189 No update of ARP table in sites with HW AirScale SW Flexi Multiradio BTS
SRAN17A and SRAN18A 0.1 SingleRAN
2234 No update of ARP table in sites with HW AirScale SW Flexi Multiradio BTS
SRAN17A and SRAN18A 0.1 SingleRAN
2235 To understand the reason for CS code failures happening Flexi Multiradio BTS
after Load based AMR was activated SingleRAN

2236 [FL18] [AirScale] KPI VoLTE Packet Lost Ratio was Flexi Multiradio BTS
increased by 20-30% with FL18 feature LTE3225 FDD DL SingleRAN
CA 5CC enabled
2238 [FL18A Feature FNI]E-RAB ADR was degraded after Flexi Multiradio BTS
FL18A feature activation SingleRAN

2239 [SRAN18SP] RRH Energy Efficiency counters not Flexi Multiradio BTS
displayed in WebEM with SRAN configuration with only SingleRAN
2G and 3G RAT (no 4G Lte RAT)
2240 [SRAN18A][P8][2FSMF] [automatic retU calibration when Flexi Multiradio BTS
RETConfigfile is changed][MRBTS500] SingleRAN
[SBTS18A_ENB_0000_000422_000034]
2246 TX out of order Flexi Multiradio BTS
SingleRAN

2248 SRAN: BCF object in Monitor do not get proper agent Flexi Multiradio BTS
automatically SingleRAN

2247 (Single RAN 2G SRAN18)SBTS raised 1910 alarm while Flexi Multiradio BTS
only GSM was actived with AHDB configuration SingleRAN

2249 [FL18A][ 1.2PD] Alarm Inter eNB Communication Failure Flexi Multiradio BTS
(6284) is reported after SW upgrade SingleRAN

2250 SRAN17A - RAB DROP 3G - no HSUPA users Flexi Multiradio BTS

SingleRAN

2251 [SBTS18A][FSMF] fault 1905 raised on OBSAI RF on Flexi Multiradio BTS

mixed CPRI/OBSAI configuration, RF goes into SingleRAN
autonomous reset
2268 UHFB RRH signature 2 'FTP failure' signature 2 'FTP Flexi Multiradio BTS
failure', SingleRAN

2269 [NPI FL18A 0.1.1PD] Flexi Multiradio BTS

[FL18A_ENB_0000_000151_020085][LTE3819] DSP SingleRAN
crash at NbTransmissionParamsList.hpp, line: 0x43
2267 [FL18A 0.2.2] Tput Degradation After SW Upgrade Flexi Multiradio BTS
SingleRAN

2266 [SBTS18A] Unexpected fault 1850 affecting AHEGA unit Flexi Multiradio BTS
due to NAHKA crash SingleRAN

2265 [SBTS18A MP0.x][RP002074] Cells from secondary core Flexi Multiradio BTS
stays offline after hot remove/hot insert optical cable SingleRAN

2264 [NPI 18A] Missing table borders in Centralized RET Flexi Multiradio BTS
management SingleRAN

2263 [NPI 18A] Too narrow list of Served antenna lines in RET Flexi Multiradio BTS
commissioning SingleRAN

2262 [SRAN18A][I&V-Auto][CR2][T-KIE 7483] Flexi Multiradio BTS

[PATHMTUDISCOVERRES_R shows SingleRAN
pathMtuDiscoverResult OK even when TPL returns
2260 TplErrorCategory 1]
[SBST18A][FSMF][AREA]Cell addition results in periodic Flexi Multiradio BTS
drop of already active cell SingleRAN

2259 [SRAN18A] SBTS GSM remote PS Uplane IP not updated Flexi Multiradio BTS
correctly SingleRAN

2270 [SBTS18A][AHGB]][4+4][VR] WCDMA throughputs are Flexi Multiradio BTS

degraded after AHGB link break SingleRAN

2271 [SBTS18A][CR1][FSMr3] RF Module Configuring Failed Flexi Multiradio BTS

(1900) alarm raised after redfreqoffset set to 4.7 on FXJB SingleRAN

2272 [SBTS19]Wcell setup failure after cell lock/unlock from Flexi Multiradio BTS
GOMS SingleRAN
2273 [SRAN18SP][NPSCSV] Snapshot NOK Flexi Multiradio BTS
SingleRAN

2274 [SBTS18SP][FSMF+FSMF][PET] Calls are dropping or Flexi Multiradio BTS

rejected during stability testing SingleRAN

2257 GSM Calls are failing on Node-3 & Node-4 in 4+2 Flexi Multiradio BTS
configuration with AHDB SingleRAN

2258 Fault 125 on several WCDMA cells when DSS is activated Flexi Multiradio BTS
on both CPRI and OBSAI radio modules SingleRAN

2256 ProhibitTimer setting for VoLTE during reestablishment Flexi Multiradio BTS
SingleRAN

2255 RLF HO during SCell Swap Flexi Multiradio BTS

SingleRAN

2254 Decreased number of SUs allocated for WCDMA after Flexi Multiradio BTS
migration from SBTS16.10 SingleRAN

2275 [FL18A][Airscale][PET][1HFB] Flood of SRIO errors Flexi Multiradio BTS

causing bearer setup failures (UEC_DB_BEARER_INIT SingleRAN
failed)
2253 [FL18A 1.1][FiVe][FSMF] Diagnostic Files Collected after Flexi Multiradio BTS
SW upgrade SingleRAN

2252 [DualCore] Fault ID 103 Carrier Power Measurement Does Flexi Multiradio BTS
Not Work was Seen after Delta Commissioning SingleRAN

2261 AHDB DSS feature do not work. LTE is not using blanked Flexi Multiradio BTS
PRBs SingleRAN

2283 SRAN/ Fault 4261 raised 7115 Diagnostic files collected Flexi Multiradio BTS
alarms then not able to fetch snapshot observed in SingleRAN
SRAN18/TT-000040704779/4G-
2284 WCDMA18 Pilot: RNC_5434A RAB Success Ratio, Voice Flexi Multiradio BTS
(CSR) (re-estab incl) SingleRAN

2285 [NPI SRAN18A] LCELL allocation problem after sw Flexi Multiradio BTS
upgarade to SRAN18A SingleRAN

2288 After upgrade to SBTS18A, RRC and ERAB drop Flexi Multiradio BTS
increasing many sites SingleRAN

2294 [SBTS18A][Airscale][MIX OBSAI/CPRI][RP002128] After Flexi Multiradio BTS

RF hot remove/insert WCDMA cells not recovered SingleRAN
(disabled state) without any alarm
2295 TL18SP 3.0 not allowing more than 20Mhz difference on Flexi Multiradio BTS
UHFC RRH SingleRAN

2296 SRAN17A - SBTS Plan provisioning for auto VPN feature Flexi Multiradio BTS
failed with IPSec outage SingleRAN

2297 [NPI18A] FHEA problem - Antenna line switched off due to Flexi Multiradio BTS
high VSWR on PA with non-BCCH TRX SingleRAN

2298 Increase of the number of Radio Link Failures with cause Flexi Multiradio BTS
‘Radio Network Layer' after upgrade WCDMA18 to SingleRAN
SRAN18SP with radio unit swap to AHEGB
2324 [Trunk][BtsMed]scfmigrator.log has no update in BtsMed Flexi Multiradio BTS
and ENB updrade from SRAN18A to FL19 failed via SWM SingleRAN

2330 Bulk TRX are going in BL-RSL post NSA plan run Flexi Multiradio BTS
SingleRAN

CNF000150 remove unnecessary LTE L2 assert from Flexi Multiradio BTS

QueueCtx_L2RlcCoreUl::sendPowerHeadroomReport_All SingleRAN
Groups
2338 SINR_PUCCH_MAX (M8005C91) increase by ~15db with Flexi Multiradio BTS
FL18A drop3 SingleRAN
2339 Handover from PLMN 20801/20891 to PLMN20891 Flexi Multiradio BTS
(defined as equivalent) is not possible SingleRAN

2340 SRAN18A - gaps in measurements Flexi Multiradio BTS

SingleRAN

2341 NPI- SRAN18A 7114( supp info= Cell Configuration data Flexi Multiradio BTS
distribution fails) alarm on AHCA sites SingleRAN

2342 Increase in E-RAB DR OTH eNB after SW upgrade Flexi Multiradio BTS
SingleRAN

2343 Different Alarm BSC and SBTS Flexi Multiradio BTS

SingleRAN

2344 [NPI SRAN18A] Validation error - issues with assertion Flexi Multiradio BTS
7466 and 7467 after update to BTSMED 18A MP0.1 SingleRAN

2346 SRAN18SP/2.1 - Low CSSR 3G after SW upgrade Flexi Multiradio BTS

SingleRAN

2355 [NPI SRAN18A] Not enough HW for LCR wrong HW Flexi Multiradio BTS
allocation for connected FXEA 2xfiber SingleRAN

2347 FDD/FL18A/After enable super cell, uplink RTP packet Flexi Multiradio BTS
loss is high SingleRAN

2348 An alarm 7107 with fault ID '6297" raised at the sites Flexi Multiradio BTS
where were activated Inter eNB DL CA feature SingleRAN

2349 remove unnecessary LTE L2 assert from Flexi Multiradio BTS

QueueCtx_L2RlcCoreUl::sendPowerHeadroomReport_All SingleRAN
Groups
2350 HSUPA traffic not possible for LCG in ESM after ESM hot Flexi Multiradio BTS
remove - hot insert SingleRAN

2351 [SRAN18A CMCC NPI] Wrong Term MRBTS-1 was sent Flexi Multiradio BTS
to Netact in Alarm Text. SingleRAN

2352 [SBTSA18A][mMP][RP002014] Attach to WCDMA cell not Flexi Multiradio BTS

possible when DSS is enabled & RF is connected with SingleRAN
Long Fibers
2353 [SBTS 19][R4][G] CS call dropped during Beam switching Flexi Multiradio BTS
to BEAM-6 from beam hopping region occasionally SingleRAN

2354 [SBTS19]M5008C50 counter do not update correctly Flexi Multiradio BTS

according to configured HS-FACH baseband resources SingleRAN

2356 [SBTS19][R3][WG] Call drop is observed after deleting Flexi Multiradio BTS
and recreating RF Hop sector. SingleRAN

2357 [SRAN18A][Airscale][NPSCSV]RF module configuring Flexi Multiradio BTS

failed AHPMDA SingleRAN

2358 [SBTS18A][FSMF][LG] During LTE RAT reset parameter Flexi Multiradio BTS
change from ADMIN Fault 1910 'RF Module filter input SingleRAN
power missing'
2359 [SRAN18SP][Airscale]: BTS crashed during a stability Flexi Multiradio BTS
testing SingleRAN

2360 Loose phase and time synchronization, BSC time is used Flexi Multiradio BTS
instead of NTP time SingleRAN

2361 WA-[OAM_SCT][LTE][TDD][trunk][R4][SMOKE] Fault Flexi Multiradio BTS

1811 raised durring HW Reset SingleRAN

2362 [SRAN18A 1.0][COMPA][FSM3] Relation Errors are Flexi Multiradio BTS

displayed on Admin if inbandPRBIndexUL is set to 6 on SingleRAN
SBTS18A_ENB_1000_001141_000000 for IoT cells
2363 Some SRAN eNBs report wrong SW version in RTPM Flexi Multiradio BTS
Traffica reporting. SingleRAN
2364 PDL rule violation after RF diagnostic test deactivation Flexi Multiradio BTS
SingleRAN

2365 Two IPSEC tunnels established at the same time after Flexi Multiradio BTS
IPsec tunnel switchover SingleRAN

2366 [SBTS19][R3][WG] GTS crash is observed after TRX Flexi Multiradio BTS
deletion from RF Hop sector. SingleRAN

2438 SBTS18SP_ENB_2000_000865_000000 WCDMA cells Flexi Multiradio BTS

don´t startup in AHEGB due to "Invalid frequency channel SingleRAN
for the BTS HW" alarm
2376 GSM cell down after restarting with L900 inter-site Flexi Multiradio BTS
CA+actDlSlimcarrier config SingleRAN

CNF000152 CAS-226526-X8F: SRAN18A: AHEGA UARFCN change Flexi Multiradio BTS

after SRAN18A 1.0 and SRAN18A 1.1 SW upgraded it SingleRAN
cause to WCDMA F6 (10837) cell down

2449 SRAN17A Acceptance - Bad Speech Quality with GSM Flexi Multiradio BTS
NB-AMR SingleRAN

2450 Alarm 7116 WCEL OUT OF USE after alarm 7772, 7782 Flexi Multiradio BTS
HSDPA, HSDPA CONFIGURATION FAILED SingleRAN

2451 [SBTS18A][SR002074]Ghost fiber on RF Split Flexi Multiradio BTS

configuration SingleRAN

2452 [NPI SRAN18A] (6708) Flexi Multiradio BTS

EFaultId_ExternallyTriggeredDspFatalErrA SingleRAN

2453 WCDMA FSMF Limitation Flexi Multiradio BTS

SingleRAN

2454 FL18 2.1.2 mPD3 - Abnormal behavior of frequency layer Flexi Multiradio BTS
LTE1800 MHz after hw swap from FSMF+FXEB to SingleRAN
AirScale+AHEB
2455 SRAN BTS working on TDM (E1) through FTIF is not Flexi Multiradio BTS
restoring after transmission failure SingleRAN

2456 [P1/P2 features] LTE1891 Micro-DTX doesn't work for Flexi Multiradio BTS
SBTS in dual FSMF configuration SingleRAN

2457 Parameter change during recommissioning cause plan Flexi Multiradio BTS
activation fail SingleRAN

2458 AHHB can't be On Air, when AHHB (w/ D2+D4) is installed Flexi Multiradio BTS
on FSMF with RF Sharing. SingleRAN

2459 [SBTS17][FSMFr3] Technical report procedure stuck Flexi Multiradio BTS

forever when reload ADMIN page triggered SingleRAN

2460 [SRAN18A] PDL rule changed for minNumRrcCatM Flexi Multiradio BTS
SingleRAN

2461 BTS Reset rejected at KKN0156 and LEI0132 Flexi Multiradio BTS
SingleRAN

2462 Plan handling lead to "BTS did'nt respond in 270s" error Flexi Multiradio BTS
SingleRAN

2463 Random Sites coming in zero payload by checking on Flexi Multiradio BTS
sites, cells showing down without any alarm SingleRAN

2464 [SBTS18][CIT][FSMF]Cells mapped on one AHEGB Flexi Multiradio BTS

disabled after SBTS block unblock SingleRAN

2465 [SBTS19][2xFSMF][3RP-01]: Secondary core is not Flexi Multiradio BTS

resetting SingleRAN

2466 [SBTS18SP][FSMF+FSMF][FID:6709][STABI] DSP crash Flexi Multiradio BTS

occurred during stability test, WCDMA cell outage SingleRAN
2478 PM stats stopped at 12:15 am on May 9th Flexi Multiradio BTS
SingleRAN

2479 Spurious reset due to EAaErrorFatality_Supervision Flexi Multiradio BTS

toward SysAdapater (suspicious memory leak on SingleRAN
SysAdapater)
2480 RIM status mismatch between WebEM and NetAct Flexi Multiradio BTS
SingleRAN

2481 How to avoid the un-register BTS trace handling from Flexi Multiradio BTS
BTSMED : follow-up emergency RCA investigation SingleRAN

2482 [BTSMED] BTSMED_FAIL_CM_UL fails around 30%?. Flexi Multiradio BTS

SingleRAN

2474 BW parameters changes aren't possible through xml Flexi Multiradio BTS
(U900 3.8 activation) SingleRAN

2483 [LTE19][BTSMED19] HTTP ( 500 ) Server Error address Flexi Multiradio BTS
SingleRAN

2484 CAS-222711-J6Y4- BTSMEds of Netact NX from Flexi Multiradio BTS

SRAN18A MP0.3 to SRAN18A MP1.0 failed SingleRAN

2469 MHA : FLPMDK, FLEGHL RRH : AHHB, AHPMDA, Flexi Multiradio BTS
AHEGB Plan activation failed if DC power source for each SingleRAN
LNA is affected
2446 RSSI increased after FXED replacement by AREA Flexi Multiradio BTS
SingleRAN

2496 RIM alarm is not cleared even if RIM status is available for Flexi Multiradio BTS
all adjacencies defined in eNB SingleRAN

2477 [SBTS18A[QT][DUALCORE][FID=4076] Distributed site Flexi Multiradio BTS

support not enabled after planned commissioning SingleRAN

2526 SR000951: BTS Embedded Power Meter for Energy Flexi Multiradio BTS
Efficiency Monitoring showing wrong Real-time SingleRAN
Measurement for SMOD
2527 [SBTS18A MP1.0][MR][FSMF+FSMF] After radio changed Flexi Multiradio BTS
from OBSAI to CPRI, RM is does not detected SingleRAN

2528 [FSMr4][trunk]mpdcchNarBandNumCatM value is not right Flexi Multiradio BTS

in CELLC_RAC_RECONFIGURATION_RESP_MSG SingleRAN

2529 ABIA with Autonomous Restart Flexi Multiradio BTS

SingleRAN

2530 [SBTS18A][AHEGA][FDD][CNI-44004] Slim Carrier filter Flexi Multiradio BTS

doesn't work for AHEGA RF module SingleRAN

2531 [FDD][SRAN18A][FSMF][FID:1868]4th LTE cell went Flexi Multiradio BTS

down due to not enough HW for LCR SingleRAN

2532 No feedback signal /Tx out of order and RF module filter Flexi Multiradio BTS
power missing alarm appearing on AREA deployed sites SingleRAN

2533 [SRAN18A][Airscale][NPSCSV]the parameter Flexi Multiradio BTS

LNCEL.eutraCelId for INBAND NB-IoT cell value not SingleRAN
displayed
2534 [CNI34364]:Difference between RX main and RX AUX Flexi Multiradio BTS
RSSI DBM in IDD-2UD BB-hop sector is exceeding more SingleRAN
than 20 dbm during gsm cs call
2535 Relation error observed while validating DSS Feature on Flexi Multiradio BTS
SRAN18A SingleRAN

2571 Alarm 9047 and 8502 occurred on 10 SBTS sites Flexi Multiradio BTS
SingleRAN

2583 [TECH Cert SRAN]:WCELL in BL-NO-CELL state after Flexi Multiradio BTS
recomissioning nodeB to change antenna tranmission pipe SingleRAN
2345 [SRAN18A PP0.3.1][COMPA][FSM3] no connection to Flexi Multiradio BTS
MHA after rollback to SBTS18SP SingleRAN

2577 [SRAN18] SFPs deinstalled from modules still visible in Flexi Multiradio BTS
database. SingleRAN

2584 Alarm ‘7116 Base station service problem with fault- Flexi Multiradio BTS
6709 DSP concurrent crash error' SingleRAN

2566 LTE_5025I increase after SW upgrade from FL19 0.3PD Flexi Multiradio BTS
to FL19 2.1PD. SingleRAN

2568 FDD/SRAN18/ CM upload failed after register Flexi Multiradio BTS

SingleRAN

2522 [FDD][FSMF][FRGY][XL19]After SW upgrade, UI value of Flexi LTE Base

idleLBCellReSelPrio was changed because of migration Station
issue
2575 Does not work FXED due to the low temperature Flexi Multiradio BTS
SingleRAN

2569 SRAN\4G \ Issue 3: fault 6261 towards Megaplexer with Flexi Multiradio BTS
port 49151 under SRAN18SP 2.0.1 release SingleRAN

2585 BTS Reset rejected at KKN0156 and LEI0132 [BBC part Flexi Multiradio BTS
Murkku lost synchronization even when BTS in SingleRAN
synchronized issue]
2586 (Flexi Multiradio BTS TD-LTE 18A)Some band D FZHM Flexi Multiradio BTS
cells OOS after upgrade to TL18a, present 1868 faults SingleRAN

2574 FL19 FOA: Low DL throughput observed after upgrade to Flexi Multiradio BTS
1.2PD SingleRAN

2587 [SRAN19] || Automatic Software Fallback happneed for 4 Flexi Multiradio BTS
sites from S19 SDROP-5 to S19 DROP-3 SingleRAN

2570 Problem after execution the full-sync command on Flexi Multiradio BTS
BTSMED SingleRAN

2532 No feedback signal /Tx out of order and RF module filter Flexi Multiradio BTS
power missing alarm appearing on AREA deployed sites SingleRAN

2576 FDD without long_lat After SW Upgrade_18SP2 Flexi Multiradio BTS

SingleRAN

2579 [T&P STABI][FL19A][FSMF][EAR] GTS crash (6450) after Flexi Multiradio BTS
site block SingleRAN

2588 Backhaul port LED has no light after 18SP upgrade Flexi Multiradio BTS
SingleRAN

2589 We are experiencing reduction in the incoming Handover Flexi Multiradio BTS
causing traffic pattern changes leading for the call drop SingleRAN
degradation since upgrade. Case is solved after SBTS
2590 [CIT]
reset.Fault 1910 'RF Module filter input power missing' Flexi Multiradio BTS
after Power Reset SingleRAN

2591 SRAN18_SBTS - FRGY looks not supporting Flexi Multiradio BTS

LTE2100+3xWCDMA2100 together due to fault id 1807 SingleRAN
( Invalid frequency channel for the BTS HW)
2592 "RF Module filter input power missing" Alarm on FXJB Flexi Multiradio BTS
SingleRAN

2593 SW bug for Validation Error while activating LTE1530 Flexi Multiradio BTS
[Reduced LTE Guard Band] SingleRAN

2594 [SRAN18A Valid]: DB persistence for PM files is missing Flexi Multiradio BTS
with BTSMed18A connected to SBTS17A SingleRAN

2595 LTE cells down post SRAN18A 1.0.2 upgrade with alarm Flexi Multiradio BTS
1868 'Not Enough Hardware of LCR' SingleRAN
2631 [SRAN18A]: Plan Upload error : The operation was Flexi Multiradio BTS
unsuccessful because the actual configuration of the SingleRAN
SOAM BTS was not available
26080 Site stuck in "resetting site" status after SW Upgrade zu Flexi Multiradio BTS
SRAN18AMP1.2 SingleRAN
 References Reason for the Change Note
N/A Summary of the original problem:
flooding error "PHY_PuschReceiveGroupedRespU was not received in
expected time for" for NB IoT traffic
N/A Change 1: (CAS-185055-R8P9,PR385048)_x000D_
How end user/operator
Summary of the originalcould problem: detect _x000D_
the problem:
In syslog,
Trace Msgthere decode are failedflooding when error receiving
"PHY_PuschReceiveGroupedRespU
more than one message too was
N/A not received
frequently
Summary of
asthe in
sticking
expected
original TCP problem:_x000D_
timepackages._x000D_
for"
After
_x000D_ SW upgrade to SRAN18A P7 branch some newly installed AHCA units
Description
How
(A102) end faced user/operator
ofproblem
the fault:with could authonomous
detect the problem:_x000D_ resets that ends with 1850 alarm or
N/A ULPHY
Send
with
Summary constant
trace didn't
ofMessages
theresets
send originalPHY_PuschReceiveGroupedRespU
triggered
continously
problem:_x000D_
by NetAct
in same NSP sessionservice._x000D_
connection._x000D_
for a long time
because theofresources
_x000D_
Description the problem for ue_idFault is 4001burned-out,
on WCDMA newRAT receive afterrequest
SW upgrade may be
dropped.
Description
How
which end
cause user/operator
oftothe additional
fault:_x000D_couldSBTS detect reset._x000D_
the problem:_x000D_
N/A Summary
Decoding
AHCA
_x000D_ units of reports
more thethan original 1850
1 Trace problem:_x000D_
alarm messageor are ininconstant one received resetsbytebuffer(when
(alarm 0010 willTCP be
Misleading
sticking
visible
How
Dependency end too)packages /validation
user/operator
SW pushworks)
on configuration: feedback,
will
couldwill
be visible
cause
detecterrordecode
in
thewhen
NetAct
problem: LTE3145
exception._x000D_
NSPFault slim carrier
service._x000D_
4001 visible activated
after SW on
_x000D_
update._x000D_
FXDD
NB cellradio_x000D_ with many UEs.
N/A Summary
Dependency
Description
_x000D_ ofofthe on original
theconfiguration:_x000D_
fault:_x000D_ problem:_x000D_
In
Faulty
Not emil
Analysis
Description
How end
based log
component there
indicated
user/operator
on theare
of certain fault:
that
and lot of RRC
isolated
could
_x000D_ reject._x000D_
detect
configuration_x000D_
version: number the of problem:_x000D_
AHCA units that have embedded
_x000D_
slow
Baseband
Validation
FDD silicon ULPHY, errors
calculation
NAHKA SBTS18A in relation
chip
failed is facing
errors
due totab memory
missingin ADMIN._x000D_
data
cablnk_l_x000D_
corruption what caused SW
N/A Description
crash
_x000D_
How
Faultyend and how problem
user/operator
component trigger recovery
and version: can
could reset. be_x000D_
detect detected_x000D_
After the3 problem:_x000D_
recovery resets SW fallback to
In
backup
Faulty
BTSMEDcase
Dependency
Description
syslog, AMOB
image.
componentthere
trunk ofon thesubrack
Dueare
configuration:
fault:_x000D_
print
to fact iserror
used,
that"CRI its fans
n/a_x000D_
previous will
timerrelease,
nokia-imp-trunk.1.20180823105821.816d4e-1.noarch_x000D_
first delivered in(e.g. SW rotate
expired"._x000D_
installed
CD): withinmaximum
customer didn't
rpm._x000D_
support
Misleading
_x000D_
SBTS18A thisfeedback recovery error procedure for PDL there
rule._x000D_
is need to perform manual counter reset
N/A _x000D_
Summary
Faulty
Description
Impact
with component
command:_x000D_ ofofthe
to End-User: theoriginal fault:_x000D_
and problem:_x000D_
version:
first delivered n:a_x000D_
in(e.g. release, CD):_x000D_
Description
There
_x000D_
L2
Impact saidwere
Dependency that of
random theconfiguration:
-gfault:_x000D_
PhyPuschReceiveRespU
on
nokia-imp-trunk.1.20180823105821.816d4e-1.noarch_x000D_
i2c_access_new to Operator: DSP
-d 0x75 SW -ccrashes.
n/a_x000D_
0xDA_x000D_ Various
was not sent faults tolike
L2, 4131ULPHY were has sent it,
reported._x000D_
Faulty
_x000D_
but
While thecalculation
Workaround:
Impact
or_x000D_ component
parameter
to End-User:_x000D_ of"numOfRespUsInTti
first
fs_min,
delivered based in(e.g.
on rpm "release,
filled
of mate in PhyPuschReceiveRespU
CD): fan,n/a_x000D_
BM is unable to know of
N/A _x000D_
Summary
Faulty
NB-IoT
what
N/A iscomponent
Impacts
i2c_access of
possible
isofnot -gthe
the aligned
-d
fault original
maximum
0x75and
to with problem:
version:WBrpmLTE._x000D_
end-user_x000D_
-c 0xDA_x000D_ of _x000D_
PDL_x000D_
mate fan. It is taken from hwpf as lowest
How
Crash
_x000D_
In
rpm
Failed
Only
ImpactWB, end
from occurred
theninto user/operator
"numOfRespUsInTti
fans
it willavailable
Trace
End-User: during
ifbe Trace 3Gsnapshot
possible could
for
Message
temporaryto" detect
specified
is
againcollection
send the
calculated
loss HW
trigger
tooproblem:_x000D_
of _x000D_
release.
according
service_x000D_
frequently As ain
SW upgrade._x000D_ toresult
UE with
one we the
session maysameobtain
Fault
_x000D_
Faulty
"respu_queue",
overestimated
Description 4341
component
connection._x000D_ reported.
of the fs_min first Inand
in correction:
NB, theboth
the
delivered logs fans
"respu_queue"the
in(e.g.SPS1616
willrelease,
loop is not inswitch
CD):was
increasing
considered, PDLreporting
their
atjust
1311fs_min
sum a lot
_x000D_
the ofUE
and "not
will
N/A How
Summary
_x000D_
which
rotate
acknowledged
Dependency
Impact
Optimize end
with user/operator
of
istoreponsed the
max_rpm
Operator:_x000D_
Operator:
the strategy original
onreceived ofcould
totemporary problem:_x000D_
thedetect
forever._x000D_
L2 received
at
configuration:_x000D_
allocate same
WCDMA the
packets",
ue_id: problem:
tti._x000D_
celland the
outage_x000D__x000D_
K2 was reporting
1)
Long
ImpactStart
_x000D_
Impacts
Problem
allocatestartup
"ERR_DET:0x00000004to3RAT
of End-User:
visible
the
ue_id ofHL BTS
faultonly traffic
for during 2)(delineation
none_x000D_
toformat1 Start
onoperator_x000D_
REL5.1 commissioning
andunitsfetching
format2 thatcontinuous
error)"._x000D_
havedue slow
separately to FaultId:Snapshot
NAHKA
as much 4341;
SoCviaNumber:
as Flame
silicon.tool
possible No
3)
7101;
2) Wait
Dependency
_x000D_
LostTrace
specific
Workaround:
when Name:10.5h
configuration
the if Trace BTS
_x000D_
on
reset
resources secondary
configuration:
configuration:_x000D_
Message
SBTS_x000D_
dependency._x000D_
of ue_id core
send NB autonomous
cell
too
is burned-out, with many
frequently reset assession
inUEs._x000D_
forced one releaserecovery some ue whose
N/A _x000D_
action_x000D_
Summary
Two
Dependency ASIA
connection._x000D_
Impact
resumption of
modules
to Operator: the
schedule original
on configuration: inside
Misleading
requestproblem:_x000D_
AMOB may_x000D_
subrack._x000D_
feedback
not come error forfor a longvalidation_x000D_
time.
Description
_x000D_
BCCH
Faulty
Only alarmhow
happens
component
Workaround:_x000D_ ofisthe fornot problemvisible
FSMr4
and can
version:
on
correction:_x000D_ in theelement
version:_x000D_ beFDD detected:
SPS1616 Manager
ULPHY, -_x000D_ even
K2SBTS18A_x000D_
links when decline in KPI can notice
IDLE2_EN=0 is set .
How
Block
_x000D_
Faulty
in
Crash
Problem
Iignore
Workaround
Risk
-How end
.-will
ERR_STAT_CSR unblock
isuser/operator
component be
Cablink_r
analysis
problem caused :visible solve
Disable
ofcan the and
without
by
be problem_x000D_
_x000D_
on could
version:_x000D_
the
improper detect
switch
validation_x000D_
correction:
avoided Cablnk_l_x000D_
orapplying
effectsthe problem:_x000D_
port._x000D_ supply voltage
mitigated beforetocorrection
NAHKA SoC is in
N/A Perform
_x000D_
Summary
Faulty
BM,
Minorproblem
case
ready_x000D_ full
ofcomponent
slow ofcommissioning
the
existed
silicon original
first always,
with problem:_x000D_
delivered
NVID=7F using Admin._x000D_
but in(e.g.
got(850mVvisible
release, whenCD):
instead AMOBof SBTS18A_x000D_
was introduced,
920mV/950mV). In
_x000D_
Description
GSM
because
Faulty
addition
Risk
Correction DSPcomponent
analysis it has
DDR concurrent
ofof
effects: thehigher
parameters
the problem:_x000D_
fault:
and crash,
max_rpm
version:_x000D_
_x000D_
correction:_x000D_
correction:
correction:
N/A weren'tGSM DSPs
ofoptimized
fan
Low_x000D_
handle were
compared
every and
head crashing
to
need
decode toand
other fans
be
in GSMusedservice
modified
seperated with
bufferwas
Description
After
going
airscale
LFS
No
too._x000D_
Correction
PDL
Impact network
rule
memory_x000D_
-Interface down._x000D_
implementation
starting updated,ofwith
tomodules._x000D_
End-User: Plan
theFB_PS_LFS_OS_2018_09_0110
effects:_x000D_
effects: fault:
is activated
feedback
N/A _x000D_
ofaccessibility
protection from
(such
improved_x000D_ Netact as mutex
degradation_x000D_ to change channel
or semaphore)
(commit configuration,
"riod: foraddLRM's
support
N/A some
_x000D_
Summary
for
shared
FaultId:
IDLE2
-Interface
Description
-Customer ofdata the
4341;of
enable Trx
the
_x000D_
effects:
effects:
how Number:got
original
on stuck
lower
none_x000D_
problemN/A problem:
7101;inspeeds"
will BL_RST._x000D_
Name:
solved._x000D_- the
BTSfixsecondary for PR374747)._x000D_ core autonomous reset
_x000D_
Description
There
as
Risk
Impact recovery
-Customer
Faulty
-Test is toaOperator:
analysis crash
requirements:
component of
effects:the
action
of happened
the problem_x000D_
correction:_x000D_
caused
all
accessibility aat
correction:_x000D_
first cells
correction:
N/A delivered will binary
longer reach
no sysadapter
startup
KPI_x000D_
in(e.g. airtime for
onrelease,
risk_x000D_ when thedoing
CD):_x000D_ BTS. a BTSsnapshot
is not onAir
How
2G
This
Impact
No
_x000D_
Analysissector
Dependency
during end
correction
this
risk_x000D_
is toof
legacy user/operator
going
End-User:_x000D_
startup
the onissue, down
uses
configuration:
correctionphase. duecould
highest
however torpm
_x000D_
risk DSP
detect
it_x000D_
to has crash._x000D_
from
the the
been hwpf
customer problem:_x000D_
instead
revealed of lowest
/ end-user_x000D_
after rpm forimproved
introduction
N/A After
_x000D_
How
DSP
Rel3
Correction
Workaround:
calculation
SW crash end
network
crash
onwards user/operator
and
detection
effects: Plan
_x000D_
effects:_x000D_
of fault
N/A_x000D_
relative ismechanism
no activated
couldofdetect
4131_x000D_
speed
effects_x000D_ from
fan NetAct
the problem:_x000D_
controlled
beginning problem:
oftoby change channel
mate ASIA._x000D_
September 2018 configuration,
since builds
some
How
Circularly
False
_x000D_
Dependency
-Interface
FRM58.09.R09 end
alarm
of the user/operator
collect
effects:1907_x000D_
Trx got
on (trunk) snapshot
nostuck
configuration: couldinvia
effects_x000D_
and BL_RST
detect
ADMIN.
_x000D_
FRM58.08.R08H theandproblem:_x000D_
calls will notbranch
(stability be working H)._x000D_on the
Alarms
_x000D_
Impact
Description
None_x000D_
impacted
-Customer
Correction areTrxes._x000D_
to raised
Operator:_x000D_
ifofproblem
effects:_x000D_
effects: when
the correction:_x000D_ GSMvalidation_x000D_
based
corrected
no effects_x000D_ on DSP has crashed
certain configuration: , and TRX _x000D_ faulty alarms will
N/A Summary
be
Description
DSP
Rel3
_x000D_
Change
-Test
Modify
Fans
Impact raisedcrash
onwards
tothe
should ofcalculation
with
requirements:
the of
and
End-User: the the
GSM
channel
_x000D_
rotate original
fault fault:
fault:_x000D_
services
with
system
ofrpm
Cell
send problem:_x000D_
4131_x000D_
configuration down._x000D_
"numOfRespUsInTti
down.
Trace based Datavia network
ontransfer/calls
message temperature plan.
", consider
continuously ofAfter
BTS tonetwork
interrupted "respu_queue",
(notorwith
make plan
them max few
rpmof
receive
_x000D_
URI
Unit
Number
Faulty
Trxes
ifsum had
has
bytemperature
thewill
degraded._x000D_
server of
subscribe
too
component
UE get
in drops tight
with
samestuck
is low during
theMSE snapshot_collect_ind/ack
and
insame threshold._x000D_
outgoing
BL_RST
version:
enough).
stream. stateHOand
_x000D_
"respu_queue"._x000D_ increasedtheymo willafter
when
remain SRANadmin activation.
try to collect
in BL_RST 2G
Description
snapshot
_x000D_
DCR
Faulty
FB1809
state._x000D_increased every
component
Workaround:_x000D_ howfrom
b83dab1_x000D_ time.
problem
and 1% to
can
version: 4%._x000D_
be_x000D_
detected_x000D_
N/A Summary
It
Dependency
_x000D_
is not
Legacy
Alarms
Risk
None_x000D_
Impact analysisare ofraised
needed.
_x000D_
to Operator: the
on
of the original
when problem:
configuration:_x000D_
When snapshot
GSM
down.DSP
correction:
Cell _x000D_
collected
has
Minor_x000D_
Data crashed
transfer/calls triggered , and second
TRX faulty
interrupted time, it will call
or alarms willthe
Activation
first
FRHF_x000D_
Description
_x000D_
Impact
be one's
raised
Correction
degraded._x000D_ ofeffects:
to End-User:
with ofLTE3577
callback the
GSM results
problem:_x000D_
which
fault:_x000D_
services
_x000D_
N/A_x000D_ in L1 KPIThen
is destroyed.
down._x000D_ impact_x000D_crash happened.
TCH
_x000D_
Faulty
Temporary
Trx
Description
-Interfacedrop
stuck inand
component service
BL_RSL
effects:
of intercorrection:_x000D_
the HOSR
first
affected
after
delivered
N/A_x000D_ inon
plan first sector
disabled
activation
in: _x000D_ after
fromupgrade
cells._x000D_ Netact._x000D_ SW from SRAN16.10 to
N/A Problem
Dependency
Faulty
SRAN17A._x000D_
Description
_x000D_
Once
We
WBTS17,
-Customer Channel
changed
Workaround:_x000D_ description:_x000D_
component ofthe
WBTS18, on
effects:the configuration:
problem:
and
configuration version:_x000D_
fault:_x000D_
configN/A_x000D_
WBTS19,xml _x000D_
tois enable
changed
trunk_x000D_ idle2,BSC on sendsthe SPS1616-K2conf Data after ports, applying
RTWP
NA
DAPD
_x000D_
Artifact
Impact
the
Violated
although
-Test
Open values
configuration_x000D_
ofmemory
Configuration
to the
Operator:
requirements:
SSH in theory seen
RTPM
connection data to
address
that shift
framework
_x000D_
N/A BTS
should
to lower
access
sends
affected not after
causing SW execute
activation_x000D_
BTS_CONF_COMPLETE
be
RF update
DSP
needed._x000D_
and +commands
AHEGA/AHEGB
crash._x000D_ (one ofHW
message to BSC
them
swap._x000D_
How
_x000D_
KPI
And
Impact
will be end
drop
BSC to dueuser/operator
sends
End-User:
successful):_x000D_ to unavailable
BTS_RESET_REQ
_x000D_couldresources_x000D_
detect the to Trx problem:_x000D_
but BTS doesn't handle this
N/A _x000D_
Summary
Faulty
SW
Description
RESET_REQ
Dependency
Testing
Call update
drop/no
i2c_access_new component
has offromof the
on
shown original
theconfiguration:_x000D_
SBTS16.10
correctly
service -gfault:
first
and
that
-d problem:
delivered
_x000D_
version:
due
_x000D_with
0x75 to toTrx
IDLE2_EN
-c _x000D_
newer
in(e.g.
getsSBTS
0xDA_x000D_ release,
= 0, inreleases
stuck CD):_x000D_
insome_x000D_
BL_RSL._x000D_ SRAN17A
2.5
Legacy
_x000D_
Enahnced
NA
cases times
onwards._x000D_
Not
Correctiona fault
Workaround:
i2c_access the RFSW increase
-description:_x000D_
impact
Measurement
link -g _x000D_
between
-d 0x75 in
onTCH
issue._x000D_ KPIs
-c drop
Report(EMR)
K20xDA_x000D_
and rate
is aSPS1616 after
consequence has SRAN to be of 17A
doesn't_x000D_ feature
enabled upgrade_x000D_
activation._x000D_
in BSC and
_x000D_
LNA
Dependency
Averaging
train
Impact
Wait
Afterwards Temperature
correctly
fortostartup Period(BMA)
Operator:
reset onorto itRF compensation
configuration:
finish._x000D_
causes
_x000D_
module. setsome toThisbe improvements
_x000D_
more
problems
will triggerthan forwere
in 1the_x000D_
again the SW implemented
upgrade, butinto
sectors._x000D_ problem
N/A How
Summary
Faulty
Dependency
SRAN18A
No
_x000D_
Impact
TI end
Dependency_x000D_
Stability
canimplementation,
reoccur user/operator
componentof
to_x000D_0.1 the
on load.
End-User:_x000D_
as original
configuration:
long and Average
first could
problem:
version:
as delivered
such newthatSW detect
RTWP
we _x000D_
_x000D_
_x000D_
in(e.g.
end
with the
for
up problem:
the
fix release,
with
won't Zvolen
beCD):
the_x000D_ _x000D_
cluster since this upgrade
installed._x000D_
Upgrade
Antenna
GTS
LTE3577
show
_x000D_
Description
NA
No calls
K2 reporting
Risk and
analysis timing
onsite
-105.31dBm, to
ofmisalignment._x000D_
affected
ifdelineation
problemSBST17A
SBTS18_ENB_0000_000739_000000_x000D_
activation thewhich needed_x000D_
cells_x000D_
based
correction: isbuild
error very
onand from
similar
certain
_x000D_
sendingSBST16 to before where
configuration_x000D_
back_x000D_ theFHEL cutover radio
from is
_x000D_
SRAN16.10
installed_x000D_
Faulty
Enahnced
packet
Workaround:
None_x000D_
Description component
not Measurement (-105.50dBm).
accepted
of Notheworkaroundand version:
control Report(EMR)
correction:_x000D_ _x000D_
symbols._x000D_
_x000D_ has to be enabled in BSC and
N/A How
Summary
Description
Impacts
_x000D_
Averaging
Impact
GTS_x000D_
In stability end toofuser/operator
of theofthe
Operator the
fault
Operator:_x000D_
Period(BMA)
branch original
correction:
I from could
to operator:problem:_x000D_
set
build detect
to_x000D_
be
R02I _x000D_
more thethan
there problem:
is new 1 forDDR _x000D_
the sectors._x000D_
initialization procedure
t-put
Alarm
M_TRX
L1
Description
withKPI
_x000D_
Operation
Cell
With
Correctionis drop
higher7745
not
IDLE2_EN -active_x000D_
less
CHANNEL
impacted._x000D_
lapdmT200tfof
&effects: the
Maintenance
voltages than
= fault: expected_x000D_
correction:
1None_x000D_
(the FAILURE
Parameter
_x000D_
applying default _x000D_ RATE
filled
forvalue),
slow as ABOVE
thisperproblem_x000D_
NAHKAs. DEFINED
specification
This and
is mandatory THRESHOLD
ABISrequired
_x000D_
raised
2
Faulty
configuration.
Mutex
-Interface
doesn't
improvement. for
faultscomponent
is were TRX3
implemented
show effects: (site
identified
up._x000D_
Since and 1035BB)_x000D_
None_x000D_: common/shared
version:_x000D_
for
build R07I there is AHCA datafixofwith LRM to avoidDDR
modified race
N/A _x000D_
Description
a)
GSM FHEL
Workaround:
conditions
-Customer
Impact
_x000D_
parameters DSP, toradio of the
types fault:_x000D_
problem_x000D_
correction:
were
SBTS18SP_ENB_0000_000377_000082_x000D_
End-User:
when
effects:
that it's
is correction:_x000D_
None
accessed
_x000D_
additional considered
_x000D_
by other
change as non to
threads.
needed GAIA _x000D_
address and thus a wrong
the problem._x000D_
Description
RMOD_L-2/RU_L-1
CRL-25063
correction
Radio
Collect
Increased
Calls
_x000D_
Risk analysis latency
will snapshots
notMSE of
factor the
implemented.
misalignment
was
alarm
work._x000D_
of the problem_x000D_
with can't
used
threshold
a gap
correction: be
BSTAT enabled
between
time. average
_x000D_
Don't
None_x000D_ after
antennas BB
Rouding
trigger reset._x000D_
connected
collectingsolution to master / slave
circularly.
Due
_x000D_
Risk
Faulty
Analysis to
implemented_x000D_
nahka.
(causing incorrect
Problem
analysis ofwrong
component theofcorrectionRSSI
is
DSP
the related
first Correction
base
correction:
deliveredtoband
risk
correction:_x000D_ lack
toLow Configuration,
of
behavior
timing
in:_x000D_
the risk
customer in case
measurements/verification
_x000D_ and/ end-user_x000D_
there was of ~4db
CPRI difference
Radios forthere
in
N/A was
Description
Summary
gain)
WCDMA
Risk
_x000D_
Impact
All
Low. aanalysis
SRAN17 difference
Change ofof
to carrier
Operator: the the
of original
offault:_x000D_
before
the
releases_x000D_
proved 30dBmin SW
correction: problem:_x000D_
in
correction:_x000D_
_x000D_other the
is REL5.1 Uplink
delivered resulting
to
families, customer._x000D_ in failure
verified by HW of Incoming
measurements
Handovers.
RMOD_L-2/RU_L-1
The
b)
_x000D_
If
Risk
in theLapD
Analysis
Capacity
Correction
RF root
analysis
tech
Oulu cause
timer
of file
will theBTS/DSP
be was
of
have has
correction
effects:_x000D_
effects:
team the
reduced
and been
alsocan't
been detected
correction:
_x000D_
proven linked
wrongbe
riskenabled
subscribed,
,since to
fromasthe
to
_x000D_
the
few the
UL
compared because
impact
Level
customer
of
memory then
the neglect
Trx'es as
of
with /OpenCpriAgent
stability noise
an unnecessary
end-user_x000D_
are levelinandand
specification
subscribe
bystuck
field isignored
writes
stucked
ABISin the
the
when
PIMC
configuration
Faulty
HO
_x000D_ Detect
SAFE_x000D_
BL_RST_x000D_
Impact
-Interface UnRegister
algorithm.
component messages._x000D_
to End-User:_x000D_
verification._x000D_ effects: These
SnapshotFile._x000D_
unnecessary writes were impacting bits within an
and version:_x000D_
None_x000D_
None _x000D_
N/A _x000D_
important
Summary
RFSW/REL5.1/Draco
Correction
GSM
Risk
-Customer analysis
Correction Services register
ofeffects:
theofwill
effects:_x000D_original
the which
_x000D_
be problem:
controls
(currently
correction:
down._x000D_
None_x000D_
Improved the
not
stability _x000D_ PIMC
of BTSengine,
version isduring
used)_x000D_resulting
snapshotincollection a momentary
Description
malfunction
Different
_x000D_
Problem
Workaround:_x000D_
-Interface
Analysis
Workaround:
Safe
-Test
-Interface range
exist
of of
effects:
requirements: theof_x000D_
effects: the
PIM
fromin 256QAM
correction:_x000D_
correction cancellation
begin
no_x000D_
no None -riskUEbranches
all
change_x000D_ toCQIcausing
the value
customer a was
are degradation/not
affected._x000D_ takenininthe
end-user:_x000D_ to Uplink
account noise
during
Do
floor._x000D_
implementation
notrequirements:
Dependency
_x000D_
None_x000D_
-Customer
SAFE_x000D_
Lock/unlock
Impact
-Test
-Customer reset openCpriLogManager_
effects:on of
to Operator:_x000D_
from
effects: CRL18781_x000D_
configuration:
BSCreduced
no risk
or Block/unblock
Snapshot
cells down _x000D_
of /false
collection
RFs when agent
alarms_x000D_
from
is simulated
with restart
Admin_x000D_
1850 while there are ongoing rl
active_x000D_
_x000D_
FHEL
Impact
-Test
GSM
Correction Radio
-TestServices
procedures to End-User:_x000D_
requirements:
requirements: inshould
effects: MTwill beno be installed_x000D_
down_x000D_
stability test require memtest tool that will make memory
SW
How
_x000D_
RTT wrote
Description
Correction
na
stress end
difference
testing user/operator
2effects:
ofFPGA the between registers could
correction:_x000D_
_x000D_ antennas which
detect caused
& the
t-putproblem: the issues,
drop._x000D_ _x000D_ but these 2 registers
are
256QAM
BTSdescribed
Faulty
_x000D_
There
Difference was
Workaround:_x000D_
will UE
component
handle a slight
between required
in the FPGA and
delay
KPIsbetter
specification
version:
in
BTS_RESET_REQ channel
different
before _x000D_
andRFM document
quality
after from than
detection
activation
BSC asexpected
they
in(CPRI
of are
theinvalid
allLTE3577 before
thisso.._x000D_
cases SCell was
case)
irrespective
in
added_x000D_
of fact,
Workaround:_x000D_
resulting
minimized._x000D_
GTS_x000D_
Complete it'sinSBTS
Trx state._x000D_ FPGAwrongreset. issue,
RSSIPeer but writing
Correction rats will these
was 2 registers
used
be impacted._x000D_ at GSM-DSP. is not needed To overcome currently,this,
so
_x000D_these 2effects:NA_x000D_
N/A_x000D_
whenever
-Interface awrite TRXoperations comes to Supervisory have been removed now GTSfrom will thesend code_x000D_
Description
M_TRX__RSSI_CORRECTION_CFG
_x000D_
-Customer
Faulty component of theproblem
effects:NA_x000D_
how fault: _x000D_
first delivered
correction:_x000D_ in(e.g.message
will solved._x000D_ release, CD): to ALL the TRXs in the BCF
_x000D_
Different
so
Description
-Test that
NA_x000D_
Based
BTS range
allhandle
the
requirements:NA
will on TP ofprovided
TRXs
the inthe 256QAM
correction:
correction:_x000D_
willwith
Trx have
reset UE CQI
_x000D_
the
correction,
and same
send value data
adding
state was to anot
maintain
change NULL taken in to account
consistency.
check
again tobefore
BSC._x000D_ during
accessing
N/A Summary of the original problem:_x000D_
FORK FPGA reports "DRS NotAllowed"._x000D_
_x000D_
N/A How end user/operator
Summary of the originalcould problem: detect _x000D_
the problem:_x000D_
Transmission
Incorrect correlator is impossible handlingand procedure
t-put is 0._x000D_
during delay search with training
_x000D_ active has lead to situation when delay has been incorrectly for
sequence
N/A Description
GSM
How end
signal user/operator
of
withthePaBiasSwitching
fault:_x000D_ could detect active.
the problem:_x000D_
This was leading to alarm
FORK time
reporting._x000D_
Alarm N1 counter reported is inmore NetAct advanced is different thanwith NAHKA the time N1, reported
it causes in allBTS, even
measurements
_x000D_
later than current requests
time._x000D_ to arrive 10 ms too late._x000D_
N/A How end user/operator
_x000D_
Summary of the originalcould problem:_x000D_
detect the problem:_x000D_
Critical
Description
BTS
Dependency Autonomous
alarm how being
on problem
Reset
reported
configuration:_x000D_ iscan performed
on
beaffected
detected_x000D_
dueantenna
to RROM line.crash_x000D_
Alarm was vanishing
after
Alarm
_x000D_ restart
LAA units_x000D_time reported and reappearing in NetActafter is different
severalwith hours. the Alarmtime reported
was onlyinoccurringBTS, in on
N/A non
RawAlarmHistory.txt
How
Summary
_x000D_ BCCH
end user/operator
ofantenna._x000D_
the original is UTC could
problem:_x000D_
time_x000D_
detect the problem:_x000D_
_x000D_
Sigsev
Diagram
Faulty component inforRROM_x000D_
fault 4424 and was updated. FRI had to implement new changes and
version:_x000D_
Faulty
_x000D_
where
The issue
Description component
waswas missing
of thethere first
implementation
in delivered
fault:_x000D_
all released in: sw _x000D_
from FRI part._x000D_
versions. It's very occasional, so easy
N/A FRI
Description
_x000D_
Summary
to beSBTS18SP_x000D_
When ofofthe
omitted._x000D_
PaBiasSwitching theoriginal
fault:_x000D_ problem:_x000D_
has been active during coarse delay search then
_x000D_
Due
Description
Since
incorrect tointroduction
hybrid of cell
correlator the interactions
correction:_x000D_
ofprocedure
improvedwith SWbeen
has lnRels
crashleading detection
some pointers for REL5.1
to situation could when RFs
be captures
end of in
Description
invalidated._x000D_
FRI
August implemented
Workaround:_x000D_
correlator 2018 were ofR&Dthe diagram
correction:_x000D_
receivedfor
containing setfault
"chopped" of occasional
4424._x000D_
data. Such reports caseindicating
has beenthat SW
correctly
N/A Sumary
_x000D_
crashes
The issue
identified
Change of
happen
toand the
occurs
getdelay original
localwhat
from time
search problem:_x000D_
finally
theinstead endsofwith
startup
algorithm andUTChasRFSW
onlybefore
beenradio rollback
executed to passive/backup
RAWAlarmHistory.txt
HW reset once
maymore, help._x000D_
but
is
The
Dependency
Risk
version
_x000D_
correlatorcounter
analysis
generated._x000D_ and has counting
reporting
on
of
not the attempts
configuration:_x000D_
beencorrection:
alarmtriggered calculation
1850._x000D_ again andforalgorithm
_x000D_ EN-DC bearers has be executedcounts tooonmuch
ANR
N/A
_x000D_
potential
Description
incorrect + HybridEN-DC
data._x000D_ Cell_x000D_
of the establishment
correction:_x000D_ attempts. Not possible to use it for meaningful
N/A Summary
_x000D_
How
success
Whenend
Description RFSW ofhow
rate the
user/operator original
calculation._x000D_
detectsproblem faulty problem:_x000D_
could detect the
willsituation
solved._x000D_ (FORK problem:_x000D_
N1 NAHKA N1), it adds -10 ms
Plan
offsetprovisioning
Alarm
_x000D_
Dependency
Correction 1850
into
timeFORK happen is failed
description:_x000D_
reported on
on configuration:_x000D_
BCN REL5.1 in BTSMED_x000D_
in counter._x000D_
NetAct RFs
will be(Galaxy
the same family)
time as andreported
in postmortem in BTS.logs
_x000D_
we
Description
Problem can see
Nullified LnRel
is only of
"recovery
the
pointersproblem:_x000D_
affecting reset"._x000D_
are units properly
with GSM handled PaBiasSwitching
now. active or LTE uDTX
N/A Summary
_x000D_
Less
Description attempts
active._x000D_
Risk analysis ofofthe the
ofneedoriginal
the to beproblem:
problem_x000D_ calculated._x000D_
correction:_x000D_ _x000D_
S1-Connection
Description
_x000D_
1)
SWBTSMED workaround of Establishment
consider
the fault:_x000D_
would PDL Success
validation
be executed failed
only Ratio
when isthe
in case downgrade
the validation
faulty after activation
condition process
is detected. of
feature
After
How
exceed
Faulty
The only end
weeks LTE4475
theuser/operator
component 30S
of diagnosis
possibility NB-IoT
timeout._x000D_
and
is that itMultiple
could hasdetect
version:_x000D_
the been Coverage
correction the
determined
problem:
doesn't Levels that _x000D_
_x000D_
work due
andtowe'd HWget components
the same
N/A _x000D_
Description
tolerances
Attempts
2) Validation
Problem
issue._x000D_ and
is inoftook
and the
success
allnot problem:
around
legacy optimal related
FRM3x 46S _x000D_
configuration
counters
toSW._x000D_
finish the have
parameters
whole values validation
different
we might process._x000D_
byoccasionaly
magnitude
Description
M8001C5
experience
order._x000D_
3) Time consumed
_x000D_ showsof thecorruption
data higher
problem: values
on complicated _x000D_
in the after RAM.
andSWbig upgrade._x000D_
This configuration
is causing SW which
service contains
crash what
_x000D_
finally
hundreds
When
Correction
Faulty trigger
UE even
trigger
component RFthousands
effects:_x000D_recovery
the firstre-RACH
delivered reset.
of objects procedure
In
in(e.g.addition
of MO forDDR
release, LNADJW,
a UL initialization
dataLNHOW
CD):_x000D_ transmissionprocedure
and LNRELW,
in new has
N/A Description
Summary
been
which
coverage
-Interface
N/A modified
cause ofofthe
level,
(legacy)_x000D_
effects:thethe original
tothe correction:
validation
apply
fault:
NPDCCH
None_x000D_ problem:_x000D_
higher
_x000D_ took _x000D_
grant
voltage
25S+ fortoafter
contention
validate
DDR the initialization._x000D_
resolution
configuration shall be of these
send in 3
Disabling
wrong
Too
MOs._x000D_
new
_x000D_
-Customer broad
CSS. validation
LBT1944
but
definition
effects: error
in LTE4475, ofvisible
the attempt
None_x000D_ in ADMIN
it was send
counter. _x000D_
to NB-IoT
_x000D_ UE in USS._x000D_
_x000D_
_x000D_
Dependency
-Test
Impact requirements: on configuration:_x000D_
to Operator:_x000D_ None
N/A How
Summary
It hasend
Dependency
Performance been user/operator
ofconfirmed
the
on original could
configuration:_x000D_
degradation._x000D_ that problem:_x000D_
often detect RF resetsthe problem:_x000D_
problem:
increase _x000D_
probability of problem
configure
PORT-x
NA_x000D_
Perform
S1-connection
_x000D_plan
apperance. never
more became
than
validation
Also Establishement
it has 32been active
RX CHANNELs
from because
NetAct/BTSMED
Successthat
confirmed itperwas
ratio AirScale
only not
is with acquired._x000D_
downgrade
above
selected half.units
If due
kindmore oftothan
(HW no 12
CHANNELs
_x000D_
configuration._x000D_
EMM:AUTHENTICATION
tolerances)
Workaround:_x000D_ are related the
experience to RESPONSE
WNCELs
issue. Problem withinsame was value
uplink_x000D_ mainlyofvisible picPool, on wrong
Galaxy family
N/A relation
How
Summary
_x000D_
(AHxxx)
Faulty end error
user/operator
of the
component
RF restart._x000D_ and willoriginal
parametersbeand visible._x000D_
could
problem:_x000D_
version:_x000D_ detect the
optimization was problem:_x000D_
done for those units. In pararell HW
SW
It _x000D_
is legacy
upgrade_x000D_
Description
measurements
NA_x000D_
_x000D_ bug,
of the
how which
forproblem came
fault:_x000D_
other canout
REL5.1 be afterdetected:
platform refactor. _x000D_
units Implementation
are performed toofmake manage sure
_x000D_
remote
itproblem
EMM:AUTHENTICATION
Description
took more teid
won't was
of
thenthe based
appear 30S
fault:_x000D_
to on
there key:
complete
correction:_x000D_ or ifremote_teid
RESPONSE the validation,
needed isoptimizeand remoteSicad.
missing_x000D_ which will timeout
configuration Which for for
filesinalso Gcad
N/A Description
depoloyment
Summary
BTSMED,
_x000D_
Wrong
them._x000D_
Impact
Correlator of
validation
thenofthe
like
the
to Operator:_x000D_
handling original
the airscale
fault:_x000D_
rule plan problem:_x000D_
remoteSicad
in admin_x000D_
procedure will failed._x000D_
during delay was search equal 0.algorithm _x000D_has been
Failure
Which
RUMAG
Description
_x000D_
Impossible
_x000D_
modified cause
indoes
tooptical
toofcollisons
notinterface_x000D_
the
calculate
enforce create
fault:
new betweenRESULT
_x000D_
success
data same
ratio
capturing forKPI_x000D_
CONFIGURE_CAC_TASK._x000D_
remote_teid
when previous but fromalgorithmdifferent remote
execution
trsw
_x000D_
When
Dependency
Faulty
has not adress._x000D_
UE trigger
component
been on configuration:_x000D_
the firstre-RACH
successful._x000D_ delivered procedure
in(e.g. release, for a UL CD): data transmission in new
_x000D_
N/A _x000D_
Description
Summary
coverage
AirScale
Dependency
Faults
Workaround:
Big amount of ofthe
areplatform_x000D_
level,
visibleonthe
_x000D_original
the
instances correction:_x000D_
configuration:_x000D_
sinceNPDCCH problem:_x000D_
introduction
of MOs grant LNADJW, for contention
of improved LNHOW SW resolution
and
detection shall
LNRELW_x000D_ be send in
mechanism
Description
Separated
During
new
None_x000D_
_x000D_
NIDD/SW
_x000D_
Risk CSS.
FRM58.08.R08H theupdate
analysis implementation
handling
but ofof the
in correction:_x000D_
LTE4475,
theand ofFRM58.09.R09._x000D_
needed. CONFIGURE_CAC_TASK
correction:_x000D_of
it was
NIDD maxTotalBandwidth
cansend betoupdates
NB-IoT in UEvalidation
object
FL19 fetch rule,
in USS._x000D_ failed
only._x000D_ it was
and
For
CONFIGURE_CAC_TASK::dataRootDN
believed
Faulty
_x000D_ Gcad
Negligible/no that
Deployment
component only one
risk._x000D_and band introduced is possible
version:_x000D_
version: _x000D_usageper of
empty,
ccid
RX/TX_PU_L.instead
added logs of In
trswSicad.
for
case clarity,
of multiband
N/A reordered
RX/TXes
Summary
PDL_x000D_
Faulty
List
Description
_x000D_ multiple
of
calling
component
scfValidator_x000D_
Dependency
Releases ofthe
on original
and/or of
bands
andcallback problem:_x000D_
wereand
version:_x000D_
theconfiguration:_x000D_
correction:
Change-Delivery thus
_x000D_ Failed
validated RESULT
where as
Faultyone, creation.
SWwhich led to falsewas
components
negatives_x000D_
BTS
MOAM
_x000D_ Reset
delivered._x000D_
NIDD
_x000D_
LTE4475
Correction update after
133778_x000D_ andrecommissioning
iseffects:_x000D_
enabled_x000D_counter SW update is stuck - all cells are down, no faults are
necessary._x000D_
_x000D_
reported,
Faulty
All LTEcomponent
-Interface andmanual SBTSFCT
effects: first
releases
none_x000D_ reset
delivered has to
(including in(e.g.be maintenance
forced
release, to recover
CD):_x000D_ BTS._x000D_
packages) that use
N/A Summary
How
_x000D_ end
SBTS18SP_x000D_
Faulty
Description ofeffects:
component thethen
H user/operator
SBTS18SP_ENB_0000_000377_000121_x000D_
branch
-Customer (later how original
first
problem
and R08H)
reduced problem:_x000D_
could
delivered
version:willor detect in(e.g.
solved:_x000D_
_x000D_
RFSW
maintenance thetrunkproblem:_x000D_
release,(09.R09
effort CD):_x000D_
due or elimination
to later). In particular:
of faulty
If
How
1) multiple
_x000D_ Due
end user/operator
to
cells PDL
FL18A_ENB_0000_000151_020085_x000D_
As
SFS
alarms above_x000D_
SBTS18SP, and MAC usingperformance
PS_x000D_
SBTS18A,
reporting_x000D_ thecould samedetect
L18SP, issue,
band the
fail
L18A._x000D_plan problem:_x000D_
validation
validationwith is timeout from BTSMED
"CarrierBandwidthNotSupportedByRadio",
OAM
side_x000D_
-Test stuck
Impact
_x000D_
Workaround: state
to End-User:_x000D_
requirements: _x000D_ after n/aattempting to changeit's cells_x000D_
probably that problem._x000D_
N/A Summary
_x000D_
2)
no
Impact Due
Releases
Workaround:_x000D_
Risk to to
impact_x000D_
Performance
List analysis of timeout,
the
End-User:_x000D_
knife original
and/or
of the BTSMED
provided, problem:_x000D_
Change-Delivery
correction: remove
implement
_x000D_ indication
where
the validation
Faulty SW logical
components
of these was 3
some
Description
mentioned
delivered:
Downgrade
SAFE_x000D_ BTSes tounsync
directly(PLAN_VALIDATE_IND)_x000D_
_x000D_
Service of
degradation
FL17SP1，
MOs the
SW C++
that states
infault:_x000D_
on affected
code
FL18,
doesn't ininstead
BTSMED,
cells._x000D_
FL18SP,
support some
of improved
PDL
FL18A_x000D_
rule. BTSesSW crash handler thread is
detection
All
OpenCpriAgent
3)
blocked_x000D_
Impact
_x000D_carriers
mechanism Because on RX/TX
noisresult
to Operator:_x000D_
(hiding message/event/timer
theare under treated
issue)._x000D_ PLAN_VALIDATE_IND
as if they based,werewithout singleisband.message/event/timer,
created, They BTSaredoesn't
all
N/A Summary
itvalidated
think
_x000D_
does
Impact
wrong
Analysis the toof ofthe
nothing.
plan
together the
Operator:_x000D_
validation
End-User:_x000D_ original
validation
The
errorwhen
correction northbound problem:_x000D_
procedure
checking
visible layer
riskintoADMIN_x000D_
the max
iscustomer
finished_x000D_
(MCTRL/REM/LIM)
total bandwidth, / end-user: as_x000D_
let
opposed
OpenCpriAgent
to
Cannot
checking
to
4)
How
KPI
Call
_x000D_ endprovision
start/configure/software
So when
user/operator
once
degradation._x000D_
may
Description
SAFE_x000D_ fail._x000D_
of the perlowernext
band._x000D_bandwidth
plan
could
correction:_x000D_ operation/reset/xx,
validation
detect e.g.
the 4.4Mhz
comeproblem:_x000D_ in TX find
in,OpenCpriAgent
BTS for FXDA_x000D_
the previous
responds plan these
_x000D_
message/event
validation
Optimize
Workaround:_x000D_
HW control hLayer
isparameters
ongoing(actually
toperformance_x000D_
send has ARD0546 beenit has message
been removed
optimized radio
to assure because
and alsoofprocess
support timeout).
for widerradio's
BTS
HW
N/A How
Summary
response.
will
_x000D_ put end
Workaround:_x000D_
Dependency
Impact
Disable
tolerances.
Correction this
to user/operator
of the
OpenCpriAgent
new on plan
validation_x000D_
Operator:_x000D_ original could
configuration:_x000D_
effects:_x000D_
DDR Initialization problem:_x000D_
validation also detect
in
creates
procedure thesome
queue problem:_x000D_
to wait timers
update._x000D_ for the to previous
trigger some one actions
is in
BCCH
a
done._x000D_
Description
Cannot
Only repeatable
S1-connection
_x000D_
Site
Correctly transmission
provision
affects
reset._x000D_
working of manner,
the
multiband lower not
fault:_x000D_
Establishment
success happening
sending
bandwidth_x000D_
RX/TXes._x000D_
rateSuccessheartbeat
KPI_x000D_afterRatio Lean
message, GSM
may beorand CMSTsomeenabling
downgrade due toon
other RRC
site._x000D_
messages
5)
hconverter
_x000D_
connection
Description
Risk analysis
-Interface Then…. for
thread
setup
ofof
effects: radio
the the is
second
status
blocked
failed_x000D_
correction:_x000D_
NA_x000D_ plan
correction:_x000D_monitor
byvalidation
error to radio.
log print_x000D_
is These
timeouttimers again._x000D_
are stored in a
N/A _x000D_
Summary
Basically,
Description
Faulty
centralized
PDL
New rule
-Customer ifofeffects:
component ofthe
the
timer the
updated_x000D_
parameters original
plan fault:_x000D_
service.
and validation problem:_x000D_
version:_x000D_
correction:_x000D_
have NA_x000D_been When is(MCTRL/REM/LIM)
confirmed interrupted without let
with electrical finishing it normally(no
OpenCpriAgent
signal measurements. to
How
WebEm
result),
Dependency
The end
customerBTS
MCtrl@68050._x000D_
reset
_x000D_
BBC
Impact
-Test or
will
Workaround:_x000D_ poor
user/operator
thewill
when
Acquire
requirements:
of perfomance
onis think
OpenCpriAgent
change Ownership
NA is could
configuration:_x000D_
unable the toplan
high, during detect
setofbut e.g.
resetsitconfiguration
validation
transparent the
4.4Mhz
has itselfproblem:_x000D_
is bandwidth
been ongoing
because
CONNECTORvalidation_x000D_
mitigated forever._x000D_
ofinand
noTXconnection
forseen
when
is FXDA_x000D_
CCU as with
is
_x000D_
None_x000D_
No
radio/no
Risk
Enabled GSM
save._x000D_
Disabled analysis services
heartbeat
during
LTE4475 of Host
the possible
message
or avoidafter
correction:_x000D_
Module UEs enabling
response,
Detection_x000D_
re-RACH this
OpenCpriAgent
in new feature. coverageUE willwill not all
clear beits
level._x000D_ able to
timers
N/A Description
Summary
How
_x000D_
Dependency
attach
Faulty
in
Nothe end with
timer ofGSM
component
risk_x000D_ ofthe
user/operator
ontheconfiguration:_x000D_
service. original
correction:_x000D_
BTS_x000D_
first
The problem:_x000D_
could
issuedetect
delivered herein(e.g. theafter
is, problem:
release, PR391866, _x000D_
CD):_x000D_ one OpenCpriAgent
Refactory
SrioFlushGarbagePingPongList()
Perform
Faulty
N/A_x000D_
_x000D_ the
allcomponent
plan code
ofvalidation
SBTS18A_ENB_1000_000549_000000_x000D_
clear
Risk
Description
Correction analysisOpenCpriAgents'
of
effects:the the logic
and totimers
version:
from
correction:
correction:_x000D_
_x000D_ perform
NetAct_x000D_is the
_x000D_
during
_x000D_ called validation.
by ErrorDriver
reset, it leads other to OpenCpriAgents
empty garbage
collection
Correction
Safe_x000D_
The
No alarms sendaccumulator
CONVENG_x000D_
_x000D_
Description
don't NPDCCH anyof the
effects:_x000D_
1850 grant forping-pong
onfault:_x000D_
heartbeat Galaxy contentionfamily list
message orandradio
resolution
units_x000D_ prevent shallPlatformCE
status monitor
be sendmessage in newdescriptors
to radios. leak.
N/A After
Summary
_x000D_
Faulty
Due correction
to
Workaround:_x000D_
When
Description
-Interface
CSS_x000D_ ofof
acomponent
CPU
radio
effects:the
loading,for
original
doesn't
the PR382993
and data
fault:_x000D_
no receiveproblem:
version:_x000D_
effects_x000D_
none_x000D_ submission this_x000D_
heartbeat function
getting is accidently
messages, earlieritor called
delay
will reset. by
fromPLH every
DSPlayer CPU
BB. can
and
The
Faulty
-Customer
Correctionitcells
MOAM_x000D_
_x000D_
Other
still
Plan detect
Description should did
component
validation
than this
usingnot
be iscalled
radio,
effects:_x000D_
effects:
how comefirst
older
forced
nobut
corrected
problem only
up
delivered
SW, to after
because
sleeping once.
stop
will only Software
due Due
in(e.g.
artificially to
OpenCpriAgent
validation_x000D_
solved:
cells to
The
and Activation,
race
release,
timeout,increasing
NPDCCH
need condition
that
for hence
CD):_x000D_
ismake
SW infor
inlimits
grant an
upgrade ErrorDriver
manual
plan
abnormal
oncontention eNB
validation it'sreset
state,
of affected isit
possible
was
-Test needed
-Interface
resolution
units_x000D_ that
requirements: to
two
anything bring
SBTS18SP_ENB_0000_000377_000146_x000D_
_x000D_ normally
effects:
shall beorNone_x000D_
RX/TX_PU_BP_L-multibandMaxTotalBandwidth
doesn't
not finished do more
upandthe
against
system
send CPUs
inblocknewcells._x000D_
radio. call
the Why
CSS_x000D_ thisthis
next function
plan OpenCpriAgent in at
validation
(if theallsame
operation
possible)time_x000D_
doesn't and
would
work return
N/A the
_x000D_
Summary
Faulty same
Dependency
help._x000D_
either?
-Customer
-Test descriptor
ofeffects:
component
(MTRL/REM/LIM)
requirements: the original twice.
on configuration:_x000D_
first problem:_x000D_
delivered
None_x000D_
oscilloscope Because
let in(e.g.
OpenCpriAgents of that,
to measure release, later on LFS
to CD):_x000D_
quality reset of one kernel
by one
electrical issignals
freeing
duringinsidethe
re-
same
Description
topSlavePort
_x000D_
commission,
Dependency
Impact buffer
-Testanalysis
Risk
RF to End-User:
requirements: of
two
value
the
SBTS18A_ENB_0000_000422_000034_x000D_
Issue coming only
other
on
of times
correction:
is
with out
inLean
configuration:_x000D_
the OpenCpriAgents
_x000D_
None
correction: aofrow range_x000D_
_x000D_
GSM what
_x000D_ causes
orwill
CMST also enablekernel
clear all oops
side and including
._x000D_
timers, kernel other
Do
_x000D_
Msg4 notretransmission
panic._x000D_
Description
OpenCpriAgents',
No_x000D_
None_x000D_ cancel all timer
of the _x000D_
correction:_x000D_
which may will beimpact
an issue. thisIfOpenCpriAgent.
eNB detected a So DTX forforCAS-191826-
UL data
_x000D_
How
Update
over NPUSCH end
Workaround:_x000D_
Faulty
T2D1, user/operator
component
inthe
this re-commission
validation
(message andrule could
version:_x000D_ detect
6toinscenario,
check
the figure), the problem:_x000D_
finally
carriers theper all
msg4 OpenCpriAgents
band._x000D_
re-transmission don't
shall be
Risk
topSlavePort
Additional
BB_x000D_
How analysis
end
response._x000D_
Faulty
Impact
Carriers
scheduled component
towill value
ofgrouped
user/operator
information
Operator:_x000D_
withbe theand
new is
correction:_x000D_
CSS,out
for could
version:
by of range_x000D_
setting
if band
NACKdetect awhen
_x000D_ fixed
isthe power
problem:_x000D_
checking
detected, value
thenthe the have
rule, USS been
so added
multiband
shall be used.in the
cases
NA
_x000D_
Problem
SYSADAPT
Loss
respective
will
But reflect
the of DTX with
synchro page
reality DSP
rev.0_x000D_
with
of
detection now reset,
BTS BTS
and
for kernel
Site theoops
MED_x000D_
- ifManager
NPUSCH and
Online
configuration
format kernel is panic._x000D_
Help._x000D_
1 hasn't otherwise
been supportedcorrect - by pass.FL18A
Description
Faulty
_x000D_
Dependency
(only CRC component ofon theconfiguration:_x000D_
OK/failure fault:_x000D_
firstfeedback
deliveredare in(e.g. release,
supported forCD):_x000D_
NPUSCH format 1).The DCI
HWAPI
Faulty
N0 for component
NA_x000D_ deliver
SBTS18A_ENB_0000_000422_000034_x000D_
Description msg4 slave
ofretransmission
the firstport
fault:_x000D_
correction
correction:_x000D_
deliverednumber :_x000D_
may asmissed
in(e.g.
be 0 which
release, by meansUE issue
CD):_x000D_
due to thiswithlimitation.
port and
should
_x000D_
Double provide
memory typevalue
SBTS18SP_ENB_0000_000377_000121_x000D_
Use
Updated async properties freeinon
instead 1,472083A,
NIDD
PlatformCE
of sync dofor not accept such
buffers/descriptors
472083A.101,
hconverter error value,
472083A.102, butDSP
by
log print_x000D_it should
472083A.203 because
N/A Summary of the original problem:_x000D_
"sIntrasearch " parameter value changed after sw update to SBTS18A
software._x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
How powered
RET end user/operator off after sw couldupdate_x000D_
detect the problem:_x000D_
When performing software update from pervious release to
_x000D_
N/A SBTS18A_x000D_
How
Summary end user/operator
of the originalcould problem:_x000D_
detect the problem:_x000D_
_x000D_
Perform
SyncE Syncronization
SW update from source WBTS is not to SBTS_x000D_
taken in use after BTS reset when 2
Description
_x000D_
syncE sources of the arefault:_x000D_
in priority list._x000D_
N/A _x000D_
Description
Migration error of the fault:_x000D_
problem_x000D_
of sIntrasearch parameter occur. _x000D_
RET
How
Wrong
_x000D_ configured_x000D_
end IP user/operator
address configuration could detect for 7th theand problem:_x000D_
8th set of IP address for FBBC1
_x000D_
SyncE
and
Faulty FBBC2_x000D_
Syncronization
component first source
delivered is not taken
in(e.g. in useCD):_x000D_
release, after BTS reset when 2
N/A Faulty
syncE
_x000D_
Summary component
sources
of theare original
SBTS18A_ENB_0000_000422_000034_x000D_ first
in priority
delivered
problem: list._x000D_
in(e.g.
_x000D_ release, CD):_x000D_
_x000D_
How
Not throughput
end user/operator validation_x000D_
SBTS18A_ENB_0000_000422_000015_x000D_ could detect the problem:_x000D_
Description
Transport
_x000D_
Workaround:_x000D_ layer
of the connection
fault:_x000D_ failure_x000D_
N/A SyncE
_x000D_
How
Summary
Change
Impact end Syncronization
user/operator
totheof parameter
the original
Operator:_x000D_ source
could
problem:_x000D_
value detect
is notafter
back taken
the sw problem:
inupdate_x000D_
use after
_x000D_ BTS reset when 2
syncE
Description
No
SRIO allsw
_x000D_
After LED
cells
sources is
updatewill
howgraybe
are problem
(OFF)
Onin priority
operator Air_x000D_
on
canSC
need list._x000D_
be (ESM)
detected_x000D_
change module
loglink and aftercreate
domain RSL collision is
Transport
_x000D_
resolved_x000D_
Descriptionlayer
mannually_x000D_ of the connection
correction:_x000D_ failure_x000D_
N/A Summary
Description
_x000D_
fix migration
Dependency ofhowthe original
problemproblem:_x000D_
rules_x000D_
on configuration:_x000D_ can be detected: _x000D_
The problem
Description
Alarm_x000D_
How
_x000D_ ofisthe
end user/operator
Workaround:_x000D_
SYNCE_x000D_ thatfault:_x000D_
DEM try todetect
could createthe TOPF_CONF_M
problem:_x000D_ before TOP_CONF_M
Wrong
_x000D_
Trigger
was
Risk created_x000D_
After swIP domainID
analysis address
update collision
of operator
the configuration between
correction:_x000D_
need for 7th
change 2 FSMF and 8th
loglink system
setcreate
and ofmodules.
IP address
RSL _x000D_ for FBBC1
N/A Summary
and
Description
_x000D_FBBC2_x000D_
safe_x000D_
mannually_x000D_
Workaround:_x000D_ ofofthe theoriginal
fault:_x000D_problem:_x000D_
Input
DCS fieldset
Description
not
Unknown_x000D_
_x000D_ related the to
ofreasonig lcrId
fault:_x000D_ is not available (cell for
NotEnoughThroughput and nb iot cell also)_x000D_
_x000D_
BASEBAND_ROUTING_TASK_x000D_
SRIO
The problem
Correction
Description
Dependency LED effects:_x000D_
isofis
set
on that
the as DEM
disabled try to
configuration:_x000D_
correction:_x000D_ (gray,
create OFF) TOPF_CONF_M
after successfuly before
domain TOP_CONF_M
id collision
N/A Summary
_x000D_
resolving._x000D_
was
Description
create
Carrier
-Interface RSL ofand
created_x000D_ ofthe
aggregation
effects: the original
fault:_x000D_
update problem:_x000D_
correction:_x000D_
no containing
loglink
change during
7th andmigration_x000D_
8th system modules_x000D_
EEPROM
Faulty
_x000D_
Specification
DEM will read
component
correctly error
wasn't and
set (2078)
include
version:
REFs alarm
lcrId
under during
_x000D_
parameters
SYNCE_R. '100_x000D_
LTE
ADMIN Sitewillreset' test _x000D_
choose correct
_x000D_
DCS_x000D_
Dependency
Risk analysis
sources to displayon
of theconfiguration:_x000D_
SYNCE
correction:_x000D_
statuses_x000D_
N/A How
FSMF end
N/A_x000D_
Dependency
minor_x000D_
Faulty
_x000D_ user/operator
+ FSMF
component on dualcore could
configuration:_x000D_ detect theinproblem:_x000D_
configuration
and version:_x000D_ use.
Performing
Software
_x000D_
N/A_x000D_
Correction
IPSVC
Workaround: update
any scenario
SBTS18A_MP0.X_x000D_ to SBTS18A
effects:_x000D_
_x000D_ that causes
SW._x000D_ reset and startup with HWF_x000D_
_x000D_
Faulty
-Interface
None_x000D_
Correction component
effects:
effects:_x000D_ and version:_x000D_
No_x000D_
N/A Description
Problem
N/A_x000D_
Faulty
-Customer
_x000D_
-Interface Description:_x000D_
component of the no
effects:
effects: fault:_x000D_
and
first version:_x000D_
Unknown_x000D_
delivered
change in:_x000D_
There
Unexpected
_x000D_
N/A_x000D_
CABINET_L's isSBTS18A_MP0.X_x000D_
no judging
-Test requirements:
IPSVC
Description ofradio
reasoning
the module
the
No parameter
correction: type
status can
was
_x000D_ whether
be
notadded is null
cleared from before
whenWizard_x000D_
using it._x000D_
CABINET_L was
_x000D_
Faulty
loaded
DCS will component
from HWF_x000D_
validate first delivered
throughput in(e.g. release, CD):_x000D_
for cells._x000D_
N/A Correction
Summary
N/A_x000D_
Faulty
_x000D_
Impact
List Releases ofdescription:_x000D_
component the
to End-User:_x000D_original
and/or problem:_x000D_
firstChange-Delivery
delivered in(e.g.where release, CD):_x000D_
Faulty SW components was
ARGA
SFP_R
_x000D_
N/A_x000D_
Dependency
SBTS (474800A)
transmissionDistance
will
delivered._x000D_
Risk analysis doesn'ton
of the should be removed
configuration:_x000D_
work_x000D_
correction:_x000D_ wasn't filled fromproperly
BPF2 for SMOD-SMOD
SFP_Rs._x000D_
Workaround:_x000D_
N/A_x000D_
_x000D_
SBTS18A_MP0.X_x000D_
None_x000D_
N/A _x000D_
Summary
Workaround:_x000D_
Impact
Analysis
Added ofthethecorrection
original
toofOperator:_x000D_
subscribe for TOP_CONF_Mproblem:_x000D_
risk to the customer when its created / end-user_x000D_
we execute that
How
Cannot
Use
Faulty
SBTS end log
Parameter
will user/operator
component
Workaround:_x000D_
None_x000D_
code_x000D_ into editor,
doesn't Admin using
work_x000D_
and and could Google
detect
version:_x000D_
edit the
Chrome problem:_x000D_
lcrId parameters_x000D_ browser older than version 68,
SFP_R
Firefox
MOAM
_x000D_
Correction older
transmissionDistance
0_x000D_
No workaround_x000D_ than 60_x000D_ wasn't filled properly for SMOD-SMOD
effects:_x000D_
N/A SFP_Rs._x000D_
Summary
_x000D_ effects:
_x000D_
Description
-Interface ofofthe theoriginal problem:_x000D_
correction:_x000D_
None_x000D_
_x000D_
How
Commissioning
Faulty
Add
-Customer
Added end
protection
new
Description user/operator
component
subscribe
parameters
effects:
of the - LTE
for first
for cells
parameter could
lcrIdinwizard_x000D_
delivered
None_x000D_
TOP_CONF_M
to
correction:_x000D_ detect
Validated
type is the
in(e.g. state
problem:_x000D_
its -created
faultID:
boost::optional_x000D_
when release, 4261
CD):_x000D_
we visible_x000D_
execute that
Description
The
_x000D_
MOAM
-Test end
code_x000D_
Corrected user
IPofaddress
0_x000D_
requirements: could
the fault:_x000D_
not
None log into Admin
allocation for 7th on andChrome
8th system browsermodulesolder in than version
carrier
N/A 68
How
Problem
oranalysis
_x000D_
Risk
SFP_R end
Firefoxdescription:_x000D_
user/operator
older
of thethan
transmissionDistance
aggregation._x000D_ could
60_x000D_
correction:_x000D_ detect
wasn't the filled problem:_x000D_
properly for SMOD-SMOD
SCT
Wrong
_x000D_/ System
SCFeffects:_x000D_
Workaround:_x000D_
no
SFP_Rs._x000D_
Risk risk
Correction
_x000D_ analysis fileofComponent
used whichTesting_x000D_
the correction:_x000D_ resulted this error._x000D_
Description
_x000D_
Not performing
N/A_x000D_
-Interface of
effects:
how the fault:_x000D_
reset_x000D_
N/A_x000D_
problem will solved._x000D_
N/A Cannot
Description
Problem
Dependency
-Customer
_x000D_
Corrected log
description:_x000D_
IPinto
ofaddress
on
effects:theAdminfault:_x000D_
correction:_x000D_
using Google
configuration:_x000D_
N/A_x000D_
allocation for 7th Chromeand 8th browser_x000D_
system modules in carrier
Fault
Corrected
TopFreqSyncSLS
_x000D_ 4261
FSMF+FSMF_x000D_
Correction
-Test
Description product
Cell
requirements:
aggregation._x000D_ effects:
of the Disable_x000D_
counter
codeN/A of should
correction:_x000D_
N/A_x000D_ FSMF in not
BPF2_x000D_
be resetted but after reconfiguration of
_x000D_
If
TOP PC master
Dependency
-Interfaceis unknow,
CABINET_L's the
on
effects: counting
migration shall
configuration:_x000D_
reasonigStatus
N/A_x000D_ ruleiscontinue
will not remvoe
cleared from
before last
portmode
value._x000D_
loading from HWF_x000D_
N/A Summary
Dependency
_x000D_
Faulty
No_x000D_
-Customer
Risk analysis ofeffects:
component the
on
of theoriginal
and problem:_x000D_
configuration:_x000D_
version:_x000D_
N/A_x000D_
correction:_x000D_
2xASIA+3xABIA+AMIA+FRGT+2xFXEB_x000D_
Impact
When
DEM_x000D_
_x000D_
-Test
Risk
No configure
to Operator:_x000D_
analysis
requirements:
risk_x000D_ of theparameter in Parameter Editor, PDL will do validation and
correction:_x000D_
N/A
_x000D_
Value
report
Faulty
Correction for
error,the
component butcounter
effects: thereand topFreqSyncSLS
should beisnoloaded
version:_x000D_
CABINET_L validation
(M51361C4)
fromerrors.
HWF with is
PDLnow logic
too is
cleared low incorrect
in 15min
N/A Summary
counter
when
About
Faulty change ofeffects:_x000D_
period.
page_x000D_
component
reasoningStatus_x000D_
Correction the Itoriginal
parameter
isandcurrently
first problem:_x000D_
in PE
delivered 465
version:_x000D_ has and
been
in(e.g. itrelease,
should
fixed._x000D_
have been around 666 since
CD):_x000D_
A
the
DEM minor
_x000D_
switching alarm is reported
time
SBTS18A_ENB_0000_000292_000000
_x000D_
-Interface
No 0_x000D_
risk_x000D_ effects: lasts around
N/a_x000D_ instead 234s. of critical_x000D_
In the
patchedNIDDwith there is described
topFreqSyncSLS
How
_x000D_
Faulty end user/operator
effects:counter
FL18A_OM_0000_COMMON_976543_000000.FSM4_x000D_
-Customer component first
Fault could: 'The
delivered
2078 detect
number
will notthe
in(e.g. problem:_x000D_
of seconds
release,
appear_x000D_ during this interval while
CD):_x000D_
N/A Summary
the
When
How
Impact
About Timing
_x000D_
-Test end
-Interface ofover
configuring
page_x000D_ the Packet
to user/operator original
End-User:_x000D_
requirements:
effects:_x000D_ the SCT problem:_x000D_
parameter
could
frequency detect insynchronization
PE,thechange
problem:_x000D_
some service
parameters
was in lockedwhich has
After
state.'
related
The several
None_x000D_
_x000D_
Faulty BP_Rhot
operator
_x000D_
component
No risk_x000D_ will remove
parameters,
seefirstan / insert
inconsistency
then do
delivered of the BBMOD,
PDL
in(e.g. between
validation,
release, fault
the4341
reported error
CD):_x000D_ was
alarm
keep and consistent
state of
reported._x000D_
_x000D_
with
cells.
Impact PE._x000D_
Antoalarm
SBTS18A_ENB_0000_000292_000000 that doesn't show its impact._x000D_
End-User:_x000D_ patched with
N/A _x000D_
Summary
Correction
Impact
The ofdescription:_x000D_
the original
FL18A_OM_0000_COMMON_976543_000000.FSM4_x000D_
endtouser
-Customer Operator:_x000D_
could
effects:_x000D_ not log problem:_x000D_
into Admin on Chrome browser older than version
Alarm
Don't
Description
How
68
_x000D_
No or
SFP_R endfor
reset
Firefox fault 145fault:_x000D_
user/operator
counter
ofolder
the
transmissionDistance
risk_x000D_ not
after
than cleared_x000D_
could
reconfiguration
60_x000D_ detect
wasn't the filled problem:_x000D_
properly for SMOD-SMOD
_x000D_
When
DCS
Fault doesn't
4341
we do
Workaround:_x000D_
SFP_Rs._x000D_ reported_x000D_
PDL
create validation
PATH object for the under
changed channels,
parameters
because in PE,
of thatthereFRIhas cannot
no
N/A How
Summary
-Testend
BP_R
calculate
_x000D_
Impact
N/A_x000D_ to user/operator
MOC of in
impactthe original
plan,
for the
Operator:_x000D_
requirements:_x000D_ could
so thereproblem:_x000D_
fault_x000D_detect
will the problem:_x000D_
be report some error incorrectly. we need
Unexpected
Fault
add
_x000D_
The 6261
Description
the
operatorBP_R
Workaround:_x000D_
No risk contains
ofalarm_x000D_
the
MOC
could wrong
fault:_x000D_
intolog
not plan, description_x000D_
into toAdmin
unsure onthe correctbrowser
Chrome error reported
older than in version
_x000D_
PE._x000D_
Dependency
After
68 or the
Description
SMOD-SMOD Firefoxsecond on
ofolder
the configuration:_x000D_
hot insert,
correction:_x000D_
CABLINK_Rthan we
60_x000D_
shows detectedfiberLength LINK UP in 3125
equal to MBaud/s correctly,
N/A How
_x000D_
Temporaryendwe
None_x000D_
but
Description
after user/operator
of
switched
taking the fault:_x000D_
SFP_R::transmissionDistance._x000D_ the
ownership couldspeed ofdetect
to 6250 the problem:_x000D_
PATH_DELAY MBaud/s, we didthe
to update notmo correctly
if detect
Raise
After new
Dependency
_x000D_
the
Checking
LINK fault
needed._x000D_
Workaround: antenna
DOWN6261
for picPool
on and line check
amplifier
configuration:_x000D_
_x000D_ event. in WTS
Because the alarm
isofhot
is done intext
this, plugged,
for the
Airscale
some unexpected
fault._x000D_
riod
when internal issues
it shouldn't
flags appears
which
have shouldin
_x000D_
case
Faulty
have of
been_x000D_
been
None_x000D_
Description
N/A_x000D_ gaincleared
component ofupdate_x000D_and
on LINKversion:_x000D_
the correction:_x000D_ DOWN, remained set._x000D_
N/A Description
_x000D_
Summary
FRI@25806_x000D_
Risk
Added
_x000D_analysis ofofthe
implementationofthe original
the fault:_x000D_
toproblem:_x000D_
correction:_x000D_
copy CABLINK_R::fiberLength to
Description
there
_x000D_
Then
Dependency
Fault
Faulty iscomponent
6261
on athecrash
of on thehappened
description
third fault:_x000D_
configuration:_x000D_
SFP_R::transmissionDistance._x000D_
Cells will on Air_x000D_ hot
andremoval,
should at binary
be
version:_x000D_
correction:_x000D_ we"Failuresysadapter
detected whenthe
in correctly
connection doing
between
LINK a DOWN BTS and event,
Gain
snapshot_x000D_
Faulty
but Application
Airscale_x000D_
BTSMEDdid
ADMIN_x000D_
Updated
_x000D_ component
not orsend
browser3rd party has
the first been
'disconnect'
tool"
validation triggered
deliveredinstead
to chrome oftoo
in(e.g.
event many
"Failure
to
release,
[68 MCU times.
- 70]in HWAPI, Fixbecause
&CD):_x000D_
connection
firefox by skipping
[60 between
- 62] of those
BTS and
;_x000D_
N/A passdev_r
_x000D_
Summary
flags
iOMS
Added which
Correction orcase ofeffects:_x000D_
3rd creation._x000D_
the
were
party
for original
of edge not
SBTS18A_ENB_0000_000306_000000_x000D_
Risk analysis the tool"_x000D_problem:_x000D_
cleared._x000D_
correction:_x000D_
browser as it was treated like chrome ;_x000D_
_x000D_
How
*It was
Faulty end
None._x000D_
If
Temporary
browser expected
user/operator
component
istaking toownership
not supported,andhave
first could
Alarm detect
version:_x000D_
delivered aof for fault
in(e.g.
message therelease,
PATH_DELAY_x000D_4076_x000D_
problem:_x000D_
is displayed CD):_x000D_
under the login form and
circularly
_x000D_
The
WTS_x000D_
Dependency collect
roottocause onwas snapshot
configuration:_x000D_
SBTS18A_ENB_0000_000404_000000_x000D_
Impact
the modal
-Customer End-User:_x000D_
appears
effects:_x000D_ that logging
after the viaLINKADMIN._x000D_
inDOWN
a warning afteris the speed change
displayed in case of 3125
newer- 6250
_x000D_
How
was endcorrectly
None_x000D_
Any
Correction
browser,
N/A user/operator
configuration
not error
effects:_x000D_
in casedetected
with of could by detect
passdev._x000D_
older riod.
thanAfter the problem:_x000D_
supported more in detail analysis on the code,
range.
Description
*Configure
we
Faulty
_x000D_
Impactdetected
-Interface componentusing
ofthatthethe
to End-User:_x000D_
effects:_x000D_ Long
fault:_x000D_
first Fiber cable_x000D_
PORT_LOCKOUT
delivered in(e.g. release,
bit was set CD):_x000D_
on the port when we
URI
_x000D_ had
None_x000D_
Impact
received
None._x000D_ tosubscribe
SBTS18A_ENB_0000_000344_000000_x000D_
Faulty component
the
Operator:_x000D_
LINK DOWN snapshot_collect_ind/ack
and
first delivered
version:_x000D_
port write. in(e.g. The portmo
release, when
CD):_x000D_
event adminjudges
handler try to collect
if we have
snapshot
Description
_x000D_
FRI_x000D_
Legacy
Customer
LINK
-Customer DOWN every
hasoforthe
issue_x000D_ nottime._x000D_
fault:_x000D_
"empty
effects:_x000D_ operational
event" cells by the without
value activeof this alarm
bit. If PORT_LOCKOUT=0
on each of -
*BBC
Impact
it_x000D_
is not implementation
them._x000D_
LINK
SFP_R to
DOWN,needed.
End-User:_x000D_
when
Operator:_x000D_
should ifbe filledwas
PORT_LOCKOUT=1 snapshotnot updated
properly._x000D_ collected when
- empty specs
triggered for
WeFiberLengthTooLong
event.second have time,foundit will
outcall the
that in
specifications
None_x000D_
Faulty
Impact
first
-Testone's
Warning
_x000D_
case we component
tochange
may were
End-User:_x000D_
callbackbe
requirements:_x000D_ the updated_x000D_
first
which
confusing delivered
speed is for
destroyed.
while the in(e.g.
the then
release,
operator._x000D_
port crash
is up, CD):_x000D_
thehappened.
speed set function_x000D_
N/A Summary of the original problem:_x000D_
RF module failure is raised on WCDMA cells when configuring LTE and
WCDMA cells. _x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
Description
FHSU and RU of the shouldn't
problem:_x000D_ be released in ADET/MOAM_x000D_
The max carrier spacing between LTE cell and WCDMA cell exceeds the total
_x000D_
N/A bandwidthof
Dependency
Summary ofthe on
theconfiguration:_x000D_
original
RF unit.problem: So the configuration
_x000D_ of WCDMA cell is rejected with
failure._x000D_
no
Critical
dependency_x000D_
fault 4083 visible in EM after successful fallback procedure. Cells
_x000D_ state: Disabled_x000D_
operational
N/A Faulty
_x000D_
Summary
How end component
of the original
user/operator and version:_x000D_
problem:_x000D_
could detect the problem:_x000D_
MOAM_x000D_
How
IP
From connectivity
end
WebEM, user/operatortest triggers
some WCDMA could TOP detect
cells alarm theand
can't problem:
besync on air is_x000D_
lost_x000D_
with fault 1900._x000D_
Upgrade from SBTS18A_build1 to SBTS18A_bulid2 (IM sync successful - the
_x000D_
N/A Description
same
How
Summary endmeta_xxx.zip)_x000D_
user/operator
ofofthe theoriginal
correction:_x000D_
fault:_x000D_could
problem:_x000D_
detect the problem:_x000D_
corrupted
By
CONNECTOR_L::SetAsSyncSource
There
ADET recommissioning
is nocm_data.ims2
doesn't releaseany
validation detected
checking
FHSU parameter
and forRU after
maxnotexecution
activation
related spacing
ownerships..._x000D_
carrier to
was reset_x000D_
TOP_x000D_
sentbetween
second time_x000D_
fallback
_x000D_
LTE/WCDMA/GSM to SBTS18A_build1 on MSM_x000D_
cells on SBTS._x000D_
N/A after
Description
How
Summary
_x000D_
Risk fallback
end user/operator
analysis ofofthe done
the
of original
the fault:_x000D_
consistencycould
problem:_x000D_
correction:_x000D_ detect
checkthe is problem:_x000D_
done, fallback marked as
inconsistent_x000D_
OAM
Alarm
*It was
Faulty
No riskwasvisible:
expected
componentreconfiguring
4114_x000D_
toand have TOP,
Alarm which
version:_x000D_ for fault causes 4076_x000D_TOP tuning restart, even though it
Critical
should
_x000D_
SBTS16not 4083 befault reconfigured.
towards_x000D_ reported_x000D_ The reason for that is the problem with reporting
N/A How
_x000D_
recovery end action
localPriority
Description user/operator
of
onthe TOP by could
fault:_x000D_
performed: detecttriggered
BM/HWAPI._x000D_
update the problem:_x000D_ via ADMIN to align SW on
By replacing
_x000D_
Wrong
*Configure
Impact
ESM_x000D_ check Radio._x000D_
using of clock
to End-User:_x000D_ LongsyncHubRole
Fiber cable_x000D_ for 3+3_x000D_
Dependency
_x000D_
Calls are impossible_x000D_ on configuration:_x000D_
N/A Summary
Should
Dependency
Description
_x000D_ exist ofoftheon
onthe original
every problem:_x000D_
configuration:_x000D_
fault:_x000D_
fault:platform
_x000D_ with TOP enabled_x000D_
BTS
Channels
Impact
NOK:
_x000D_ startup
N/A_x000D_
*BBC implementation
not were
to OnAir after not
Operator:_x000D_
on Site resetnot
deleted
was
SBTS18A_build1, delayed_x000D_
after updated
recommissioning
4083when specscaused
critical for FiberLengthTooLong
fault stillby radio cells are
visible,
_x000D_
specifications
removal._x000D_
Some WCDMA
Faulty component were
cells updated_x000D_
and can't version:_x000D_
on air._x000D_
N/A Summary
Faulty
_x000D_
MCtrl
Description
Disabled
OAM_x000D_ didnt ofsend
component
_x000D_ofthetheoriginal
ClearDeviceReq
problem_x000D_ problem:_x000D_
and version:_x000D_ during recommissioning caused by radio
Cell
DEM
_x000D_ Power
Dependency
replacement.
In some 0_x000D_
Workaround:_x000D_cases Failure
on
MCtrl
during fault (4090)
configuration:_x000D_
couldn't
boot orsend visible,
when cell not
clearDeviceReq
system is on operational._x000D_
high
to REM,
load, because
i2c read transfers
there was
_x000D_
*Long
no
may radio
Faulty
NA_x000D_filefiber_x000D_
with
to clear,
component ETIMEOUT consequently
first delivered value.MCtrl There
in(e.g. didn't
are
release,system
sendCD):_x000D_
clearDeviceReq
components which to does not
N/A How
Summary
_x000D_
properly
SBTS18A end
DEM._x000D_
DEM_x000D_
Faulty user/operator
of
handle
component the this
_x000D_ original error
first could
problem:
and detect
delivered cause _x000D_
in(e.g. the problem:_x000D_
all release,
sorts of problems._x000D_
CD):_x000D_
See
Export
Faulty
_x000D_
DEM prontoas image
component
0_x000D_
Description description._x000D_
of thenot and work appropriately on site view_x000D_
version:_x000D_
correction:_x000D_
_x000D_
*moam
Description @ xL18A@130047_x000D_
Workaround:_x000D_
New validation of the correction:_x000D_
fault:_x000D_
correction:
checking _x000D_ so that the configuration of cells
is implemented
N/A How
Summary
_x000D_
Fix
The
changed end
Description
removed
driver
None_x000D_
Workaround:_x000D_
whose max user/operator
of
swm forofthe
check
i2c
the original
code
carrier master
fault:_x000D_
for
spacing could
problem:
andexistance
added detect
controller
exceeds sct ofChanging
was the
ru_ls
casetotal problem:
recently
towhen HSDPA
cover
bandwidth _x000D_
sending
changed
it.whenpower
of RF didn't
clearDeviceReq.
tounit
one correctly
core apply
would hasdetect
be during
With
status
execute
runtime
this
timeout
Timing
FallbackDetected
_x000D_
Unknown_x000D_
Faulty
rejected._x000D_ via
Export
fix component
MCtrl automatic
calculations
situation willas send
whenon
and done
first site
script_x000D_
active view_x000D_
clearDeviceReq
thefor
delivered system
wrong
result isstatus
in(e.g. channels._x000D_
onto highREM(and
rele_x000D_ load. Unfortunately
is NothingToDo, consequentlyone core not
to DEM)
all
activate
_x000D_
even
componentsifisthere
resultCD):_x000D_
Description
ase, Successedofexpect
istheno correction:_x000D_
radio
this anymore.
and error
need to to happen REM partition.
switch can
andhandle theyActivate
doclearDeviceReq
not handle
both ofit properlyfor non-
N/A Description
Summary
existent
causing
Dependency
DEM ofsorts
of
willRadio._x000D_
all the
howonthe original
*SBTS18A_ENB_0000_000422_000015_x000D_
Risk analysis
them._x000D_ provide of theaproblem:
problems problem:_x000D_
configuration:_x000D_
problem
of correction:_x000D_
WA for can TCOM
not
correction:_x000D_ in
be differentsent an
detected
reconfiguring places,outdated
_x000D_
TOPespecially HSDPA
if configured power
during to
boot
localPriority is
MacHs_x000D_
Calls
_x000D_
up._x000D_areExport
None_x000D_
execute
boost::none
Improve
No risk. dropped
checking andas on competition
on 3+3_x000D_
reported
for view andand
site localPriority check Nokia
is area. Problem seen is Nokia
image_x000D_
0._x000D_
_x000D_
reporting
Risk analysis null measurements
of the correction:_x000D_
correction: over No IuR for rlId = 0._x000D_
risk_x000D_
N/A How
_x000D_
Summary
The
Faulty
Risk
Max end
Description
i2c-axxia.c
Safe_x000D_
Analysis Allowable
analysis user/operator
ofofthe
component ofthethe
of original
will
Fiber
the fault:
and
correctionfail could
problem:
is detect
version:_x000D_
with
_x000D_
correction:_x000D_
length -ETIMEOUT
risk distance
to the_x000D_thefrom
customer problem:
for transactions
last Execution
RMOD
/ end-user: Noofimpact
consisting
towards anSM automatic
more
unit. than
script
How
The
1 site
end
DCS_x000D_
Export
message which
Unknown_x000D_
_x000D_ ashas user/operator
image sends
16 cells
when not
the HSPA and
work
delay couldis
parameter
blocking
detect the
appropriately
between change
randomly
those problem:
on tocells
messages
site SBTS KPI with
view_x000D_ (increasing
degradation_x000D_
is fault id
more than124or25ms.
(not This
_x000D_
enough
is
decreasing).
required
*There
Correction DSP
are by capacity
no_x000D_
SMBus
effects:_x000D_
specifications to set up
specification. a cell)._x000D_
whether Higher
link between layer components
FHS & SMOD do not properly
is also
N/A Description
_x000D_
Summary
handle
Faulty
Dependency
HPSA
Correction power ofeffects:_x000D_
component
this
considered_x000D_
Mctrl will send ofthethe original
error._x000D_
on
loss fault: logic
problem:
configuration:_x000D_
is
first
seen_x000D_
clearDeviceReq delivered rejected 2ndwhen
in(e.g.
even some
chain
release, IE
cell
radio inCD):_x000D_
became
UIR messging_x000D_
couldn't disabled
be found without any
_x000D_
How
alarm._x000D_
no_x000D_end user/operator
N/A_x000D_
CONNECTOR_L::SetAsSyncSource
anymore._x000D_
-Interface effects: None_x000D_ could detect the problem:
execution _x000D_
wasn't sent second time
Dependency
Allocate
_x000D_
Description
Analysis
REM
-Customershould cell
of the resources
of onthe
handle
effects: configuration:
fault:
correction while
TCOM
configuration:_x000D_
clear
Should risk there
device toIuR
was
work_x000D_ the
req are
between
not or
customer
even able were
if competitor
HSUPA
to/update
radio and
cant Cellusers._x000D_
end-user_x000D_
be Nokia
Maximum
detected._x000D_ Power in
N/A _x000D_
How
Summary
Impact
Faulty
its end to user/operator
equipment_x000D_
database._x000D_
N/A_x000D_
-Test of the would
component
*Configurations original
End-User:_x000D_
requirements: and None could
problem:_x000D_
detect
version:_x000D_
be limited by fiber the problem:_x000D_
length, might affect chaining
Description
_x000D_
Multiple
Cannot
n/a
TCOM/HSCH
-Customer sites
make ofreset
the not fault:
calls._x000D_
did
effects:_x000D_ with save _x000D_
fault the4383._x000D_
Cell Maximum Power during Cell unlock
TCOM
Description
_x000D_
Replacement
Faulty is unable
procedure._x000D_
component of theradio
if problem
of tofault:_x000D_
allocate
and based
is new MCD+DCD
on certain
version:_x000D_
possible again. configuration even if there are still DCD+DCDs
IuR_x000D_
N/A available_x000D_
No
_x000D_
ummary
anystatus
Impact ASIA toofOperator:_x000D_
implemented
or the original problem:
ASIB_x000D_ in order to Cannot
checkcollect the cellsnapshotin second with
radioBTS in
LRM
chain_x000D_
Risk
busy_x000D_
assessment
Dependency
Faulty
_x000D_
Cell only
not checks
component (is
for itempty
on configuration:
operational._x000D_ and easy/safe
version: DCD+DCDs
Rel2, to port
SBTS17A_R4 Rel3, toormaintenance
Kepler
Rakewhere
Rel4_x000D_ andbranches
last HSUPA
Codec_x000D_ or risky
CF isto
deliver
_x000D_
allocated, to running
leading live to anetworks?):
bug if the last safe/unsafe_x000D_
allocation happens on an
N/A Summary
Dependency
_x000D_
How
Faulty
Fault end
MCD+DCD._x000D_
first of the
user/operator
component
Workaround:_x000D_ introduced original
on configuration:
and problem:_x000D_
could
: Legacy_x000D_
version: detect
chained
SBTS17A thecells_x000D_
problem:
1.3_x000D_ When customer tries to
_x000D_
collect
It is legacy
N/A_x000D_
None_x000D_ the snapshot
bug, which viacame WebEM, out after it is rejected
refactor.by Implementation
SBTS with error of manage
"Request
Faulty
Description
rejected
remote
Impact
Dependency
_x000D_ component
teid
to as BTS
was
ofon
End-User: theconfiguration:
based
isfault:_x000D_
and
busy"_x000D_
first
call version:
on
deliveredkey:_x000D_
drop_x000D_ remote_teid
MOAM,
in(e.g. release, FRI_x000D_and CD):remoteSicad.
Legacy_x000D_ Which for Gcad
N/A Summary
During
_x000D_
depoloyment
List
REL4_x000D_ theofsecond
Releases
Description ofthetheoriginal
like
and/or airscale
SIB problem:_x000D_
update,remoteSicad
Change-Delivery
correction:_x000D_ before MAC_BcchModIndReq
was equal
where Faulty 0. SW
Which cause
components is sent
collisons
to MAC,
was
BTS
the
Impact
_x000D_
Faulty
In order
Fixed reset
Description
between
timer
delivered:_x000D_
component
list due
totosame
above of
Operator:
of comply to
the
channels DSP
remote_teid
shows first
CDR
with forcrash._x000D_
fault:_x000D_
timeout,
delivered
SMBus but specification,
from
when
degradation_x000D_
which thein(e.g. different
timings Paging
release, remote
Activation
Axxiatrsw
CD):
calculations
the Timeout
adress._x000D_
n/a_x000D_
I²C
are , the
allowed._x000D_
module willreset
abort
will
URI
_x000D_
the happen._x000D_
Faulty has
multi no
component
messagemechanism and
transfer to process
version: if the_x000D_
delay snapshot between pending.
finishing _x000D_
sending one
N/A Summary
_x000D_
How
Description
message
Risk end
Workaround:
analysis ofofthe
to user/operator
and the
of original
SBTS17A_ENB_1000_000652_000132_x000D_
Impact End-User:none_x000D_
starting
the fault:_x000D_
cell problem:_x000D_
could
disabled
correction:_x000D_
HSPA
another detect
power causes
is longer losstheleads problem:
than less25ms. n/a_x000D_
servcice
to less to end user_x000D_
Unfortunately
throughput _x000D_
it isn't that
MAC
hard risk.
Low PS
Description
Dependency
_x000D_
There to aresources
istriggerbottleneck
ofon the are
configuration:
this runABIA
correction:_x000D_
with
situation out. Itbusy
wasprocessing
on none_x000D_
aCPU caused by
system. wrongto
In speed
order allocation
when for specific
its problem,
fix this DSPs arewe
UE
busy
Faulty
Impact
Add
shouldcaused
_x000D_
Description
with
defensive cell
component by
ofsure
to Operator:
make wrong
data
the fault:
operation message
operations._x000D_
n/a_x000D_
correction:_x000D_
first
cell
HSPA
hardware delivered
iswhen order
down_x000D_
power
does callin(e.g. received
function
loss_x000D_
whole release, byCD):_x000D_
MAC
getNewConfig.
transaction PS._x000D_
without waiting for
N/A _x000D_
Summary
Faulty
Accepted
Legacy_x000D_
software offillthe
component
torlId 0original
=some on and some
data. problem:_x000D_
version: URI_x000D_
checkings.
Fortunately, Fixed
in addition null measurements
to Manual mode when thatallis radio
WebEm
_x000D_
Dependency
Faulty
How end
Workaround:
links
currentlyare poor
component
used perfomance
user/operator
on byconfiguration:
anddriver
Block/Unblock
deleted._x000D_
Site reset
the version:
could during
to apply detect
RMOD_x000D_
to new
perform configuration
n/a_x000D_
FL18A the 1.0,
problem:
PtxMaxHSDPA
I²C SBTS18A,validation_x000D_
transfers, n/a_x000D_
andTL18A,
the FL18A_x000D_
PtxCellMax
module supports
_x000D_
Faulty socomponent
Workaround:
values._x000D_
No
alsomore called _x000D_ first delivered
null measurements_x000D_
Sequence mode. In in(e.g.
this mode, release, theCD):module SRAN18 SP_x000D_
automatically
N/A Description
Summary
Faulty
Impact
Setup
_x000D_
performs R99 ofcells
component ofthe
to predefined
End-User: the original
correction:_x000D_
fault:
beforeand No
correction:
sequence problem:_x000D_
version:
n/a_x000D_
coverage._x000D_
HSUPA n/a_x000D_
Implement
user
of setup,
operations newLow -reasoningStatus
cell configuration_x000D_
it sends a slave in order to raise
address,
Refactory
On daily
_x000D_
fault
Impact to
Description
Risk
transmits tobasis
the
analysis the
End-User:
cell
ofof
specified code
65
inthe
the to logic
second 70 cells
none_x000D_to
correction:_x000D_
correction:
number perform
ofreport
radio in cell
the
Nochain._x000D_
bytes risks
from disabled
validation. duechanges
identified_x000D_
the FIFO, to unknown transfer direction,
problem._x000D_
Impact
Dependency
resendstothe
Description
_x000D_
TCOM/HSCH
Correction End-User:
Operator:
of ontheconfiguration:
effects:_x000D_
should
slave BTS
n/a_x000D_
correction:
address save is the
down._x000D_
and n:a_x000D_
_x000D_
Cell
thenMaximum reads specified Power number during Cell unlock.
of bytes This
to FIFO.
N/A Attach
Summary
_x000D_
Risk
Impact
Whileanalysis
would
-Interface
LRM willcell
tonow
prevent
very ofoperation
the
Operator: of original
the
effects:_x000D_
check
incorrect
inflexible, nofailed
correction:
all
this logproblem:_x000D_
because
can
DCD+DCDs_x000D_
HSDPA
does be
n/a_x000D_
fit cellsent
acollected_x000D_
power most was
common toundergoingcase ofshutdown._x000D_
MacHs._x000D_ multi message
_x000D_
PDCP
Impact
Correction
-Customer SDU
Workaround:_x000D_
Faulty
transfercomponent
to- the Data
Operator:one Volume
effects:_x000D_ and
wheren/a_x000D_ counters
version:
you firstn/a_x000D_
writefor CAT-M
a register - PMQAPID:
number you 7 want
counters - and
to read
How
M8047C4
If
_x000D_
the end
-Interfacesite
Workaround:
No
Risk
then null
analysis
read user/operator
isand ofM8047C5
ASIA+ABIA,
effects:_x000D_
it. Tonone_x000D_
measurements_x000D_ the this
use could
correction: itare
mode showing
detect
is already_x000D_
Low_x000D_
effectively, the very
OnAir, problem:_x000D_
alarge
and radio
number value for CAT-M_x000D_
of SW download
conditions must is be met
N/A Alarm
_x000D_
Summary
triggered,
Faulty
-Customer
Workaround:
Correction
-Test
Low_x000D_
to ensure #4261 ofeffects:
component
then
requirements:
the the
(Cell original
RUMAG
effects:_x000D_
n/a_x000D_
transactiondisabled
Update problem:
first delivered
will due
usefitto
HSDPA
does Nounknown
Profile
in(e.g.
the powersupport willproblem)
Arelease,
predefinedfor of
all SSP6
betypes
CD):
usedof
sequence. visible
in BPF2Inincase
n/a_x000D_
byradios nor this
(since
BTS_x000D_ theis not
How
specification_x000D_
issue
_x000D_ end
netact._x000D_
Description
-Interface
Analysis
-Test
the case, is with user/operator
requirements:
of ofABIA,
aeffects:
the the
fallback not
correction:
correction
none_x000D_
to manualcould
radio detect
risktype).
_x000D_
tomode theProfilethe
customer problem:
A rate
is used._x000D_ isn/a_x000D_
7.68Gbps which is higher
/ end-user_x000D_
_x000D_
When
than
Impact
URI
Description
add
-Customer
Correction TDD
6Gbps, special
tomechanism
End-User:
ofProfile
effects: subframe
Bn/a_x000D_
ofrate
the correction:_x000D_
Low_x000D_
No HSPA 6 feature
is lower
processing power (5.12
snapshot was
loss_x000D_ enabled
Gbps)._x000D_
pending. by_x000D_
setting
N/A Description
"tddSpecSubfConf"
Summary
_x000D_
For
RiskGcad
-Interface
-Test analysis ofofthe
Deployment
effects:
requirements: the
of original
the fault:_x000D_
to
None_x000D_6introduced
for
problem:_x000D_
correction:_x000D_
Cell lock allandcells,_x000D_
usage of
unlock (withccidnew insteadCell Maxof trswSicad._x000D_
Power and
During
cells
Unable
Impact
Attach
Risk
_x000D_ arein
Description
-Customer
N/A_x000D_
HSDPA cell
to
cell
to
analysis configure
disabled
reconfiguration
Operator:
Power)operation
how of replicated
effects: the
problem state
UL CA
n/a_x000D_
should after
procedure
for
correction:NA_x000D_
Low will
in not feature
LTE3864_UL
be executed
solved._x000D_
MT. profile
activation counters
CA_5B_10Mhz+5MHz_x000D_
when with no
cellwere
isalarms_x000D_
not updated
undergoing
_x000D_
shutdown
correctly
Correction
Risk
RUMAG analysis asor
will different
teardown
effects:NA_x000D_
use
of the Profile profiles
operation._x000D_
A on could
correction: FTP be wrongly
n/a_x000D_
account when updated
radio iseven though to
connected there
ABIA. was
How endbearers
Workaround:
_x000D_
no radio
-Interface
Correction
Correction user/operator fulfillingcould
n/a_x000D_
effects:NA_x000D_
effects:_x000D_
effects:_x000D_ detect the to
the conditions problem:
problem:Config
update By trying
those CAtowith
_x000D_ activate
current SSP6
on
combination_x000D_
configurations
Dependency
_x000D_
-Customer
-Interface
-Interface with
on configuration:
effects:_x000D_
effects:NA_x000D_
effects: None_x000D_RMODs:Cell AAHB, attach AANB, AAHE, AAHC,
functionality must beAAHD, AANA,
used._x000D_
AEQD_x000D_
Configure
_x000D_
Dependency
-Test
Description
-Customer UL ofon
requirements:retest CA_5B_10Mhz+5MHz_x000D_
configuration:
effects:_x000D_
the
effects: correction:_x000D_
None_x000D_ snapshot CAT-M is used_x000D_
_x000D_
Faulty
MAC
-TestPS component
requirements:
does not allocate and None version: UE beforeMCtrl_x000D_ CCCH related message is received as
Description
_x000D_
Faulty
confirmation component offorthe fault:_x000D_
fault:
attachand procedure._x000D_
version:
SSP6 was n/a_x000D_
not implemented _x000D_
Cannot
Faulty
_x000D_ configure UL
component firstCA_5B_10Mhz+5MHz_x000D_
delivered in(e.g. release, CD): SBTS_x000D_
N/A Summary of the original problem:_x000D_
BTS spontaneous reset_x000D_
_x000D_
N/A How end user/operator
Summary of the originalcould problem:_x000D_
detect the problem:_x000D_
Faultrestart._x000D_
Site regarding BTS reset appeared in WebEM_x000D_
_x000D_
FRI crash due to check parameters of a inexisting object. FRI tried to use
N/A Descriptionof
LNREL_A
Summary objects
ofthetheoriginal
fault:_x000D_
which problem:_x000D_
were deleted._x000D_
BM crashed
_x000D_
Baseband unit due resets
to TOP in loop frequencyDeviation
due to radio time valueparameters
exceeding chainging
accepted every
range._x000D_
How
time aend TX-only
user/operatorcell is being could setdetect up._x000D_ the problem: instability_x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
Description
How
eNB crashed
end user/operator
Dependency ofondue
theconfiguration:
to
fault: incorectcould
_x000D_ NB
detect
TOP UEsynchronization
the
state problem:_x000D_
caused bysource Skipped TTI _x000D_
used_x000D_
FRI
_x000D_
Cells crash
reach is onAir
happening but quickly due todrop, FRI trying then keep to use coming
a deleted backobject._x000D_
and dropping in
N/A _x000D_
loop._x000D_
How
Summary
Faultyend user/operator
of the original
component and version: could
problem:_x000D_
detect
BM, the SBTS17Aproblem:_x000D_ 1.0_x000D_
_x000D_
Unexpected
eNB crash when
Dependency alarm flexiComp
- Fault IDenabled_x000D_
on configuration: 6709._x000D_
N/A_x000D_
Description
_x000D_
Faulty component of the fault:_x000D_
first delivered in(e.g. release, CD):
N/A Description
How
Summary
When end TX-only
user/operator
ofofthe thecell
original
SBTS17A_ENB_1000_000652_000094_x000D_
Faulty component fault:_x000D_
andhasversion:could
its
problem:_x000D_
timing detect
N/A parameters
the problem:dsp
_x000D_ calculated, crash_x000D_
it also alters the RX
parameters
DSP
_x000D_
Alarm concurrent
"RF Module for DSP, crash Unauthorized"
which
error._x000D_
are shared (4278) with does regular not appear
cells and after
must removing
be aligned
between
_x000D_
Description
rfmplugin toboth
Impactcomponent
Faulty from of types
End-User: the
ENB_x000D_
fault:_x000D_
firstof cells.
service
delivered It was
temporary cause
in(e.g. by scope
loss_x000D_
release, CD): of N/A_x000D_
calculation reduced to
N/A Summary
Faulty
Unexpected
_x000D_
single direction, of problem
component the rather
original
andwhere problem:_x000D_
version:_x000D_
than there is mismatch
considering both, even between for singledsp_contextdirectionaland
DSP
MACPS:
Impact crash
antSelection._x000D_
How end
cells._x000D_ and 3G cells
toFL18A1.0
user/operator
Operator:
End-User: -stability down_x000D_
FL18A_ENB_0000_010015_000000;
could
n/a_x000D_ KPI detect the problem:_x000D_ FL18A -
is bad_x000D_
FL18A_ENB_0000_000802_000000;
Remove
_x000D_ Rfmpluging from ENB (more FL18A details 1.1PD in test steps - in Problem
N/A Summary
Description)_x000D_
How end
Workaround:
Impact of the
to user/operator
Operator:on
Only original
FL18A_ENB_0000_000003_000027_x000D_
Dependency configuration:
configuration:_x000D_
if sites
other problem:_x000D_
could
are
source detect
FlexiComp_x000D_
instable_x000D_
could the be problem:_x000D_
used as synchronization source
Operator
_x000D_
BTS
than TOP.does
autonomous
Configurations By not notusing
which have
reset, contain
TOPany issue
WCDMA information
TX-only service
won't cells ifisSYNCE
down_x000D_
appear._x000D_
for example synchronization
when LAA feature sourceisisin
missing._x000D_
Faulty
Description
_x000D_
Workaround:
use
Impact and component
tosuch ofn/a_x000D_
End-User: the fault:_x000D_
cells andbelong
Callversion: Fl18A_x000D_
istodropped._x000D_
same cell set and regular cells._x000D_
N/A Summary
_x000D_
Alarm
Description
No alarms, ofofNo
for Fault thethe original
4278
61631fault:_x000D_
is ornotproblem
correction:_x000D_ anyappearing
other : _x000D_
alarms
because indicating
runtimethat object SYNCE RMOD_R is missing
is notif
eNodeB
Faulty
created
During
one source
Description
Impact
BM corrected inter-site
component
ack/nack
tobecause is
Operator:
of totheavoid CA
missing_x000D_
processing,
RMOD_L
first iscrashing
not
delivered
correction:_x000D_
and KPI enabled
ready
a HARQ
version:_x000D_
impact._x000D_ upon for automatically
in(e.g. mapping
list
release,
exceedingfor one is CD):
not after
subframe
set recovery
FL18A_x000D_
whenever
frequencyDeviation from
erroneously RMOD X2 link
ppb is
failure_x000D_
not
contains
_x000D_
Addingseenan more
inextra
BPF._x000D_
SBTS18A_ENB_1000_000623_000036
measurements thancheck
but theto
clamp max see number
if the object
to nearest of items.
extreme Only up to theobjects
exists.(LNREL_A
value_x000D_ max amount which was
N/A _x000D_
Summary
processed,
How
were end ofleading
the
to user/operator
SBTS18A_ENB_1000_000671_000000
Workaround:
Impact deleted)_x000D_
End-User:eNB original tostability
list
reset._x000D_ problem:_x000D_
could
mismanagement
detect the
impacts theproblem:_x000D_
_x000D_
4G and null pointer access._x000D_
service_x000D_
How
RiskASIA-ASIA
_x000D_
SYNCE endfunctionality
Dependency
analysis user/operator
of SRIO
on linkcould
configuration:_x000D_
the would
correction: goes
have detect
nodown_x000D_thebroken.
torisk_x000D_
be problem Lack:_x000D_
of any alarms related to
_x000D_
None.
Dependency
SYNCE._x000D_
After
Faulty removing
Description
Impact
Correction
Risk Simple
component ofon
to Operator:
analysis configuration
and
the configuration:_x000D_
effects:_x000D_
of the adding
correction:_x000D_
firststability
delivered
correction: X2with
KPI link RMOD._x000D_
Inter-site
down_x000D_
in(e.g.
N/A_x000D_ release, CA stop CD):working,DCS@77582_x000D_Reset eNB and
N/A How
Summary
NB end user/operator
None_x000D_
_x000D_
all ok_x000D_
Scheduler
-Interface
Correction of the
effects: original
makes
effects: no up could
problem:_x000D_
detect
forcrash_x000D_
Noeffects_x000D_
FRI lost TTI so theNB problem:_x000D_
UE states are kept._x000D_
WhenRight
Description
_x000D_
Impact
Workaround:
Faulty
-Customer
-Interface acomponent
toside
site distName
howASIA
End-User:
effects:
effects: problem
none_x000D_ connection
and changes,
service
N/A_x000D_
TOP loss X2
canunavailable_x000D_
version:_x000D_
can be
be when
CAused will
detected:_x000D_
safely fullrack
not
as work_x000D_
configuration
reference and as in use _x000D_
_x000D_
Faulty
Trigger
Description
Correction
OAM BBC
backup_x000D_
-Customer component
faulty inofFL00_FSM3_9999_180930_042927_x000D_
impactsituation
the fault
effects: :andn/a related
version:_x000D_
:_x000D_
N/A_x000D_ to SYNCE functionality._x000D_
N/A Description
Summary
MAC-hs,
_x000D_
LNADJ_A
Description
Impact
-Test requirements:of ofthe
of
Operator: the
to legacy_x000D_
created theoriginal
problem_x000D_
fault:_x000D_
without problem:_x000D_
correction:_x000D_
stability
no special IPKPI address
requirements
down_x000D_ by ANR(CPlane feature), long time later,
CA
Multiple
Added
Faultyover
_x000D_
Description
LNADJ_A
Non-optimal resets
X2updated
component
protection will
of when
serdes
the not in be
fault:
with
first chained
chip
case possible
code
IPv6
settings
delivered radios
and
did
of mismatch toin(e.g.
notestablish._x000D_
are fiber
available
implement
used
between length
release, on
by ASIA-ASIAis changed
ANR._x000D_
correct
antSelection
CD): fault
Trunk SRIOduring run
state_x000D_
andports_x000D_
and
_x000D_
time._x000D_
Faulty
And there component
dsp_context_x000D_
xL18A_x000D_
Workaround: is not try additional
tofirst have delivered
actionin(e.g.
configuration to trigger release,
reduced CA when CD):_x000D_
to avoid LNADJ_Amixing updatedcell typeswith as
N/A How
_x000D_
Summary
Risk end
IP._x000D_
Dependency
Legacy_x000D_
described analysisuser/operator
of the
on original
of configuration:_x000D_
configuration:
the correction:
previously_x000D_ could
problem:_x000D_
detect
SYNCE theisproblem:reset
Safe_x000D_ used , 2 sources_x000D_ eNB_x000D_
_x000D_
How
MCPA
Problem
Impact
Analysisend feature
user/operator
toseen
of wasn't
theonly
End-User: if No
correction fully
full could
racksupported
detect
to the the
riskconfiguration
direct impact on problem:_x000D_
multi-band
customer in use
in End-User_x000D_ radios._x000D_
_x000D_
/ end-user_x000D_
Multiple
_x000D_
Faulty
Description
Impact
Correction toreset
component of and
End-User: the fault:
effects:_x000D_4001
:andDEM_x000D_
Call isdrop_x000D_
version:
wrong
correction:_x000D_ visible._x000D_
task
OAM stop
, FRI_x000D_
and start sequence when
N/A _x000D_
Summary
How
Faulty
Impact end
distinguished
-Interface
Now user/operator
of
component thename
to Operator:_x000D_
effects:
single-direction original
and iscells could
problem:_x000D_
changed_x000D_
N/A_x000D_ version: detect
will correctlyLFS _x000D_ the problem:_x000D_
calculate UL and DL radio time so it
Description
Enabling
End
Faulty
_x000D_user
Operator
Impact
-Customer
will match to MCPA
could
component
is of expected
Operator:
the the
effects:
not notice
feature
fault:_x000D_
properlyfirst different
N/A_x000D_
Site on
introduced
delivered multi-band
informed
autonomous
values KPI degradation.
radios
: n/a_x000D_
in(e.g.
about
regardless reset_x000D_
release,
anof likeCD):
unauthorized
cell From
AHPMDA._x000D_
lowRadio_x000D_
n/a_x000D_
calculation level perspective
order._x000D_
Problem
_x000D_
we
Faultycould
Dependency
-Test with
noticed
component
requirements: retrieving/updating
on that for some UEs
configuration:None_x000D_
first N/A delivered values
in(e.g. PUCCH on HWF_x000D_
release, requesting was stopped._x000D_
CD): legacy_x000D_
N/A Description
_x000D_
Summary
Impact
Correction ofimpact
ofthetheoriginal
to End-User:_x000D_
Workaround:_x000D_
Workaround: End-User: fault:_x000D_
None_x000D_
: n/a problem:_x000D_
eventually , loss of synchro can lead to KPI
GSM
How
Some
Makeend
Resources
Impact
Faulty
Dependency
_x000D_ DSP
of
issues_x000D_ tothe
user/operator
component
sure willsites
End-User:
from
RMOD onNACK reported M_TRX_CONSTANT_CFG
could
configuration:_x000D_
other and 4G
inserted node
version: with
service
isare detect1reduced
or 2the
DEM_x000D_ TRXes
affected_x000D_
available inproblem:
due to
BPF._x000D_stuck
C/A_x000D_
due in
not BL-RSL
toestablish
wrongstate_x000D_
Power
after Budget
link
value
Reestablishments_x000D_
_x000D_ sentconfiguration_x000D_
break._x000D_
Chaining
Description byof GTS._x000D_
the correction:_x000D_
N/A GTS
_x000D_
How
ummary
Impact
Faulty end
was
Description
Corrected toofuser/operator
sending
component the
Operator:
the original
of handling
the wrong
first
4G problem:_x000D_
could
isPower
no delivered
correction:_x000D_
way
of todetect
down_x000D_
HARQ detectBudget
list the
in(e.g. during value
problem:_x000D_
release,
if one source to CD):
ack/nack DSP in
n/a_x000D_
fails_x000D_
processing which will
M_TRX_CONSTANT_CFG._x000D_
Description
D-Channel
During
_x000D_
Faulty
Set ready
avoid
Impact activation
component
theto crash.Failure
ofmapping
theNull
Operator:_x000D_
for offault:_x000D_
alarms
and the LTE1042
seen
version:_x000D_
guards
when were
RADIO infeature(SRAN17A
BSC_x000D_
also reached
placedethernet in the release),
crash
enabled none
point._x000D_ of the that,
to ensure KPI
Increase
_x000D_
related
Workaround:
Impact
HAS_x000D_
After
even X2 though in
the
tolink RRC
End-User:LTE1042
break Drops
changing
none_x000D_
RMOD CAnot
scenario
is are
due
HW pegged
to
impacted_x000D_
may
eNB
available counter as shown
help._x000D_
is not peg
automatically
in BPF, in LTE1042-RSLTE-LNCEL-2-
runtime recovered._x000D_
object RMOD_R is
N/A Summary
_x000D_
Dependency
Risk
created to of
analysis ofthe
(DETECTED_RLF_MAX_DL_RETR),
Description ensure the
on
of original
hour-PM_19636-2018_07_20-09_27_34__837.xls
configuration:
the FRI willproblem:_x000D_
fault:_x000D_
correction: be able power
None_x000D_ increase
pooling_x000D_
to raise fault on in RRC file._x000D_
that Reestablishment
specific RMOD
attempts
After
_x000D_
FHDB
Impact
Faulty some
Correction Ant
toand 2effects:
component
Workaround:_x000D_
Description
object._x000D_ disturbance
with
Operator:
of increase
thefake CAVSWR
first
correction: inKPI_x000D_
inERABAbis
delivered
correction:_x000D_
Internal R&D alarm.
link,
Updated Drops._x000D_
in(e.g.
fault 1All
or
willTRX2be
release,
the TRXes
code allocated
raised in ifsome
CD):_x000D_
to match in this
suspicious sites
the pipe are
diagram are
unable
scenario to
for fault
_x000D_
re-establish
How
down._x000D_
occurs
61623,
Site
HW end
team user/operator
component
Reset._x000D_
related
61624 theand
provided toIUA
SBTS18A_ENB_0000_000386_000000_x000D_
Faulty HARQand SCTP could
version:
4299._x000D_
better linkdetect
list._x000D_
serdes with
GTS_x000D_BSC._x000D_
settingsthe problem:to be used Do on delta recommissioning
ASIA-ASIA SRIO to
N/A Summary
activate
_x000D_
Workaround:
Dependency
_x000D_
interfaces._x000D_
Risk
-Interface
analysis of
LTE1042 the
on original
feature.
none_x000D_
effects:
of theconfiguration:_x000D_
None_x000D_
correction:problem:_x000D_
Both Low LNBTS_A risk._x000D_ and LNCEL_A will change, and
GSM
Dependency
they
How
_x000D_
Impact
Faulty DSP
are
end
None_x000D_
Risk
Description
Correction
-Customer tounder
component
analysis Crash,
user/operator
ofon same
End-User:_x000D_
of
the
effects: the GSM
configuration:
first services
CHANGE_CONTEXT.
could
delivered
correction:_x000D_
correction:
RMOD_R
None_x000D_ detect
DFCA
No
will are
in(e.g.
be down._x000D_
the
and problem:
Antenna
release,
risk._x000D_
created For
even exmaple,
CD):the
Hopping
though SBTS
GTS enabled._x000D_
2G present
legacy_x000D_
RMOD is not
/CHANGE_CONTEXT-1/LNBTS_A-43920,
alarms
_x000D_
Description
Temporary
Check
Risk
Analysis
-Testanalysis
available of inVSWR
whether
of service
of
requirements:the the
of ip and
correction
the
BPF._x000D_ is TRX risk
correction:DEM
affected
correction:
existed
None BL-RST.
on disabled
in LNADJ_R,
to
Nothe will _x000D_
handle
risk._x000D_cells._x000D_
customer if not, LNADJ_R's
end-user: dist
/ subscribe No name change, it
LNADJ_R_x000D_
impact._x000D_
N/A Summary
Faulty
Impact
Correction
will
Correction
stop
-Interface toold of
component theagent,
user/operator
End-User: original
/CHANGE_CONTEXT-1/LNBTS_A-43920/LNCEL_A-21
_x000D_
How end effects:_x000D_
effects:
X2
effects: and
No Carriers
N/A_x000D_ problem:_x000D_
version:
could
version:_x000D_
then
impact._x000D_
start detect
willIUAnewnotSCTP_x000D_
the
be problem:_x000D_
on-air_x000D_ ._x000D_
one_x000D_
Uplink
_x000D_
Description
GSM
Impact
MAC
Risk
-Interface
-Customer degradation
services
PS_x000D_
-Interface ofof the
are
to Operator:_x000D_
analysis effects:_x000D_
effects:_x000D_
effects: the service
fault:_x000D_
down.Major
correction:
N/A_x000D_ afteralarmsno fluctuation raisedaton
risk_x000D_ siteBSC._x000D_
and voice is also distorted.
_x000D_
Description
The
There
Impact
Faulty VSWR
-Customer
Interface
Risk
-Test
-Customer would
component
analysis value
ofbe
to Operator:
effects the :is
effects:_x000D_
requirements: of thefault:_x000D_
multiple
effects:_x000D_n/a high
first No at this
delivered
service_x000D_
autonomous
correction:None_x000D_
RMOD which scenario
in(e.g.
is notsite and
release,
resets
available should CD):
whenin not be
legacy_x000D_
BPFlong reported._x000D_
fibre info
(more cablesin are
N/A _x000D_
Summary
In
Description
usedthisin
Faulty
-Test
Analysis
Problem
-Test case, ofof
component
chaining
requirements:
of
requirements: the
the
Description) original problem:_x000D_
LNCEL_A.actNbrForNonGbrBearers
the fault:_x000D_
configurations._x000D_
first delivered
correction risk to in(e.g. the customer release,/ end-user_x000D_modification
CD):_x000D_
DSP Platform
type="objectLocking".
Dependency
DSPHWApi
How end
Workaround: fatal
to user/operator
ison crashing
FL18A_ENB_0000_000151_010055_x000D_
Impact
_x000D_
Correction End-User:none_x000D_ error,
configuration:
effects:None_x000D_ If could
Networkdue GSM DSPs
actNbrForNonGbrBearers
toAvailability
detect
NULL
FHDBthe were
pointer
Ant is2crashing
problem:_x000D_
with
access fake
impacted._x000D_ and
changes,
, because
VSWR GSM URIservice
alarm._x000D_
DSP should wasadd
going
the
_x000D_
Application
After down._x000D_
LNCEL_A
link
Workaround:_x000D_
-Interface fluctuation
hastorequested
DELTA
effects:None_x000D_ ,Uplink cellLockingNeeded
toquality
allocate to behuge monitored
memory._x000D_
list. _x000D_ for BB Hopping enable
N/A _x000D_
Summary
Faulty
sector.
Description
Impact
However,
No
-Customer uplink
to ofeffects:None_x000D_
component ofthe original
quality
End-User:_x000D_
Operator:
URI
Workaround_x000D_ the
didn't and gets itproblem:_x000D_
version:
correction:_x000D_
accessibility
do degraded
because RF KPIsitSW_x000D_
and areVoice
didn't down_x000D_
consider is distorted._x000D_
the situation that there
How
No alarms
Problem
exists
-Test end
Dependency
_x000D_
MCPA multi user/operator
feature
with for
level
requirements:X2 BB
on subconstruction
configuration:
connection.
support
MO unitcould
isCA HWdetect
provided
Lack fault
N/A_x000D_
of intheFSMF.problem:_x000D_
service._x000D_
under
with the fix Some
CHANGE_CONTEXTand correct cells become powerduring faulty
budget with
DELTA
value
fault
Faulty
_x000D_
is sent 1868
Description
Alarms
Workaround: BTS
component
areGTS
recommissioning._x000D_
by raised
ofTRXtheconfiguration
to fault:_x000D_
when
DSPfirst
lock/unlockdelivered
inGSM
correction:_x000D_ error
DSP
M_TRX_CONSTANT_CFG
solves (not
in(e.g.has enough
thisrelease,
crashed HW
problem._x000D_ CD):
, and forSRAN17A
LCR)._x000D_
TRX faulty2.0_x000D_
message._x000D_ alarms will
N/A _x000D_
Summary
Faulty
uplink
be raised
Impact
In current
Update quality
to
HWF of the
component
with gets
GSM original
Operator:_x000D_
URI and
degraded
implementation,
every services
time problem:_x000D_
version:
newand down._x000D_
itBB_x000D_
tTotal Voice
just is distorted
simply
values areadd after fluctuation at
(*changeContext)-
calculated_x000D_
How
Increase
Impact
_x000D_
KPI and end
site._x000D_
Description
referenceDN in
user/operator
toservice CAT-M
End-User:
ofandthe RRE could
failures._x000D_
none_x000D_
degradation._x000D_ detect the problem:_x000D_ that's
moUnderChangeContextDn.getName(),
correction:_x000D_
No
_x000D_
Riskalarms
Faulty
After
Description
SWCR2856 linkcomponent
incorrect._x000D_
analysis for BB
fluctuation,
of the
isof sub
implemented
the unit
fault:_x000D_
first BCCH HW
delivered
correction:_x000D_
correction: to fault
Reconfiguration
in(e.g.
provide
n/a_x000D_ in FSMF release,
an _x000D_
triggered
automatic CD):recovery
legacy_x000D_
and during andBCCHcollect the
N/A _x000D_
How
Summary end to user/operator
Reconfiguration
Signal pool
Workaround:_x000D_
additional
Impact
safe_x000D_
Correction of the wrong
memory
Operator:
history original
of fake
effects:_x000D_ is full
IUA could
problem:_x000D_
hopping
SCTPanddetect
alarm_x000D_ there
events the
configuration noproblem:_x000D_
is to more
find was
the memory
RC sent of to left
this DSP to allocate
causing for
issue._x000D_
In
Increased
NetAct._x000D_
Impact
degradation
new
Description
signals
Transient
Dependency
_x000D_
None_x000D_
-Interface BER
to End-User:
alarmofwhich
inon
the detected
uplink._x000D_
7608 willon
fault:_x000D_
is GSM leading
configuration:
effects:_x000D_ be the
Services optical
tonone_x000D_
raised DSP will connection
crash._x000D_
when besoftware
down._x000D_ to Radioautomatic
triggers Module_x000D_ recovery
_x000D_
No
of specification
Workaround:
TRX._x000D_
Correction
-Customer was made for such usa cease , so no implementation was
none._x000D_
effects:_x000D_
effects:_x000D_
N/A Description
How
Summary
Faulty
_x000D_
Impact end
Dependency
done for
-Interface
-Test user/operator
tosuchof
component ofthe
Operator:
requirements:
effects:theconfiguration:
on original
fault:_x000D_
case._x000D_
and GSM could
problem:_x000D_
version:
correction:_x000D_
NA_x000D_ Services detect
yes_x000D_
Dual
URIwill thebe
core
(version:problem:
configuration(2
down._x000D_
unknown) Fault from : ASIA, 1900 series.
4 ABIA)
SYSADAPT_x000D_ and
M8061C142
_x000D_
After
This
GSM
Risk comissioning
issue
TRXs
Description
In analysis
-Customer
case of UE of and
iseffects:
around
specific
of
the theC143
deletion to single
need
16._x000D_
to core,
BB Hopping.
correction:_x000D_
correction:_x000D_
NA_x000D_
(that an update
happens other At
just ASIA
in
least NIDD
after present
one and
Scellsector SW.
in subrack_x000D_
should
Activation) is presented
be configured
internal scell
_x000D_
as
with
fast SMOD_EXT_R
Dependency
Low
Faulty
Only
-Test BB Hopping._x000D_
Workaround:_x000D_
impact.
report
component
scheduling VSWR
requirements: onlist
The sites in
first
alarm ADMIN._x000D_
configuration: will
delivered
(introduced
NA after REL3_x000D_
automatically
100
within(e.g.
consecutive
release,
CRL23388) recover,alarms CD):
isinreduced
case unknown_x000D_
fromof byany
filterTRX
this toparticular
create
stuck a
Description
_x000D_
Faulty
Dependency
hysteresis
Reset component
of the
UE if needed._x000D_
without ofsite
theconfiguration:
on
effect._x000D_
establishing fault:_x000D_
will and version:
recover
IUA SCTP the n/a_x000D_
GSMissue.
link._x000D_ DSP_x000D_
No workaround to avoid the
GSM
How
Faulty
_x000D_
Impact end
and
issue._x000D_
Correction to user/operator
LTE
component
End-User:
effects:are :and using
No could
MOAM_x000D_ the same
version:
none_x000D_
impact detect scheduling
GTS_x000D_the problem:_x000D_ slot on link from system module
to
SMOD_EXT_R
Riskradio
_x000D_
Faulty module._x000D_
component
analysis of isthe visible
first
and in ADMIN
delivered
version:
correction:_x000D_ UEC_x000D_
in(e.g.althoughrelease, ASIA CD):is comissioned
SBTS18SP 1.3_x000D_ as single
_x000D_
core,
Faulty
Impact
No without
Description component
observed
Safe_x000D_ ofRFS
to Operator: risk
thedue or
first UlComp._x000D_
todelivered
correction:_x000D_
parameter this WA_x000D_ in(e.g. is
change release,
not taken CD): into n/a_x000D_
N/A_x000D_
account until next
_x000D_
Impact
Faulty
Dependency
Correction
GSM
enodeb DSPcomponent
toreset_x000D_
End-User:
will ondropconfiguration:_x000D_
effects:won't first loss
packetsdelivered
of 2G
detect without service
many in(e.g. L3VSWRfor
release,
payload a while_x000D_CD):
alarm_x000D_
or withFL18A_x000D_
wrong/Corrupted L3
Description
Impact
_x000D_
LTE + 2G
-Interface
length._x000D_
Analysis of the
toofEnd-User:
sharing
effects:
the fault:_x000D_
with none_x000D_
None_x000D_
correction GSMconfiguration
riskservice
to thequality using specified
customer is impacted(voice indexes._x000D_
/ end-user_x000D_ is distorted once
N/A Summary of the original problem:_x000D_
Cells got disabled due to Fault 7114 'CELL SERVICE PROBLEM:' fault 6253
'Cell configuration data distribution failed'_x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
How customer
Wrong BW showing can detect on cellthe in problem
MRBTS after : faultupgrade7114_x000D_ from SBTS_x000D_
_x000D_
N/A Description
There
Summary wasofinofthe WebUI
theoriginal
fault:_x000D_
possibleproblem:_x000D_
to display:_x000D_
No celland
channel
AHFB lock
downlink
AHIB
after RRHs the
bandwidthcreation
fail during with
of APUCCH_FDD_A_x000D_
reduced
reset request._x000D_
offset (if actRedFreqOffset is set to
true) _x000D_
_x000D_
N/A while
How
Summary
Dependency end
_x000D_ user/operator
of the originalcould
on configuration:_x000D_ problem:_x000D_
detect the problem:_x000D_
in
Reset
In WebEM
specific
N/A_x000D_ of AHFB case
it is not and
forcedDRX
displayed
AHIB._x000D_ procedure
but possible fallstointo receive
infinite by loop_x000D_
the operator from
WebEM._x000D_
_x000D_
_x000D_
N/A _x000D_
Description
How
Summary
Faultyend user/operator
componentofofthe theoriginal
fault:_x000D_ could
problem:_x000D_
and version:_x000D_ detect the problem:_x000D_
Primary
a)
Plan btsprovisioning
crash_x000D_
SYSADAPT_x000D_
Description portofselection
the from faultwas NetAct's
:_x000D_ applied CMincorrectly._x000D_
Operation Manager fails during
_x000D_
b)
validation._x000D_
hundreds not
Parameters occurrences
taken intoofaccount._x000D_ log: INF/UEC/UecForcedDrxProcessing.cpp#157
N/A Dependency
[ueContextId:1571
_x000D_
Summary
Faulty
All needed componentofparameters
the
on configuration:_x000D_
original
cellId:3686658]_x000D_
first toproblem:_x000D_
delivered
displayin(e.g. valuesrelease, in WebEM:_x000D_
CD): SBTS18SP _x000D_
Primary
_x000D_
How
Sleeping
- endport
channel CELL
user/operator
selected
detected
downlink withcould
after
bandwidthno detect
ethernet
U-plane theenabled._x000D_
reset
problem:_x000D_
(dlChBw)_x000D_ executed on K2 where ULPHY is
_x000D_
Description
Plan
deployed._x000D_
-Impact provisioning
channel
to End-User:ofdownlink
the from fault:_x000D_
NetAct's
Service
bandwidth CM Operation
interruption_x000D_
with reducedManager._x000D_
offset (if actRedFreqOffset is
N/A Summary
Activation
_x000D_
set to true)
Faulty componentof
Forced the original
_x000D_ Drx
andrejected problem:_x000D_
version:_x000D_ because Forced Drx Profile was not
6706
set_x000D_
-Impact
RFSW, DSP
Description
How end
channel
to crash
connectivity
Operator: theoccurred
user/operator
ofuplink fault:_x000D_
Cells
bandwidthcould during
component._x000D_
are detect normal
disabled_x000D_ operation after SW upgrade_x000D_
the problem:_x000D_
(ulChBw)_x000D_
sm
CELL
_x000D_
are paramter
is not taking
prepared LNCEL.moPrMappingList
traffic correctly._x000D_
and available in NIDD _x000D_ caused error while it (parameter) was
N/A Summary
Dependency
needless_x000D_
_x000D_
How end
Workaround:
(dlChBw,
Impact of the
to user/operator
ulChBw on original
Siteconfiguration:_x000D_
End-User:_x000D_ reset_x000D_ problem:_x000D_
could
and actRedFreqOffset detect the problem:_x000D_ are available in NIDD in
Site
_x000D_was
Description
Alarm working
report._x000D_
LTE3745 ofbehaviour
themust
MRBTS/LNBTS/LNCEL/LNCEL_FDD)_x000D_
Unexpected
feature infault:_x000D_
testbe dedicated
during activated_x000D_
reset, state.
service There was problem with return back
loss._x000D_
to normal
Dependency
During
_x000D_
Description Uplane state.ofon When
reset,
the siteallreset
configuration:_x000D_
not
correction:_x000D_ performed were
HW resources from correctly
main WEBGUI disabled "no (AT
N/A Summary
Activate
External
Description
response"
Impact
Faulty
Add LNCEL tothe
componentof
event),
isof the
feature
End-User:
Operator:_x000D_
to celloriginal
seen._x000D_
the which
fault:_x000D_
and 'LTE486
lock problem:_x000D_
caused
None_x000D_
version:
list atPLMNthe AT event
ID selected
UEC_x000D_
creation was received
mobility
of APUCCH_FDD_A_x000D_ byprofiles'_x000D_
CPU while the
MAC-hs
interrupt
During
_x000D_
AHFB and NbIOTcrash_x000D_
routine
AHIB UEs, was
RRHs attach
notfailure
properly
eNBduring crashed
configured due yet._x000D_
reset._x000D_ to wrong storage check
_x000D_
Faulty
code._x000D_
How
Impact endcomponent
Risk analysis to user/operator
Operator: of theand first
Wrong version:_x000D_
could
delivered
correction: detect
display in(e.g. therelease,
_x000D_
Safe_x000D_ problem:_x000D_ CD):_x000D_
N/A How
Summary end
Dependency
_x000D_
Change user/operator
site
Workaround:_x000D_ of to the originalstate
onnormal
FL18A_ENB_0000_000151_020133_x000D_
PDL, WebEM_x000D_ could
problem:_x000D_
configuration:_x000D_ fromdetect testthe problem:_x000D_
dedicated state. Perform site reset in
BTS
During
Uplane autonomous
Dependency SW
WEBGUI._x000D_
Workaround:
None
_x000D_
Correction reset
, except upgrade
on
executed reset,,older
download
toWCDMA
configuration:_x000D_
None_x000D_
using
effects:_x000D_ RFSWfails,
recover serviceall cells
previous
version._x000D_ isissue
down_x000D_
under on FSMFK2 where (WCDMA) ULPHYgoes is
down_x000D_
deployed._x000D_
None_x000D_
_x000D_
Impact
Faulty
-Interface component
to End-User:_x000D_
effects: None_x000D_first delivered in(e.g. release, CD):_x000D_
N/A Summary
_x000D_
No serviceofeffects:
_x000D_
Description ofthethe original
SBTS18A_ENB_1000_000623_000071_x000D_
-Customer for affected fault:_x000D_ problem:_x000D_
correction:_x000D_
Service cells_x000D_
restoration._x000D_
Description
Fatal
Faulty
In
Corrupted
Changed
_x000D_
-Test
ADMIN error
certain component orofsleeping
scenarios
harq
logic
requirements:
added the
during
new fault:_x000D_
pointer
and cell
(intelligent appears
version:_x000D_
causes
PPS._x000D_
parameters
None shutdown,
Machs
on RV after to
view cell deletion
crash_x000D_
forbase
example)
on EFS in MCtrl
ULPHY wouldwhen
update_x000D_ double
trigger
For
use same
of same
MACPS_x000D_
carrier
_x000D_
Impact setup
PSFEATURE_x000D_
Added source descriptor
twicefile
to End-User:_x000D_
new Operator:
SFS's from name
Cells isthe happening.
in
same targetBD
crashing_x000D_
requirement:_x000D_ cause It but
is(once
possible
withdirectly
different
onlyand inpath,
case
once espically
ofbycell delete
the in
N/A 0
Summary
symbol._x000D_
_x000D_ is "" inoftargetBD.
subscription
Dependency
path
None_x000D_
SBTS18A_PHY_RX_x000D_
OM_GEN_SFS_EM.1738
Risk analysis the
of theoriginal
callback).
on configuration: If problem:_x000D_
swm one
correction:_x000D_will
Cell setup
None_x000D_
search
bandwidthwasthe already
file removed
information ongoing, to"/ram/"
second
display and
insetup
do
WebEM all
_x000D_
Alarm
values1807
Faulty
operation
distribution
Workaround:
Safe_x000D_ component
for would appears
whenever
following befirst
Disable after
queuedone
deliveredSW
oftothem
LTE3745_x000D_
parameters:_x000D_ upgrade._x000D_
trigger
in(e.g.
downloaded
immediately
release,successfully.
CD):_x000D_
after the first that will cause
Description
_x000D_
finished._x000D_
Faulty
distribution
Impact
- component ofdownlink
failedthedue
FL18A_ENB_0000_000689_000000_x000D_
to Operator:_x000D_
channel fault:_x000D_
and
firsttodelivered
version:
the file MAC-hs,_x000D_
bandwidth not found._x000D_
in(e.g. release, CD):_x000D_
(dlChBw)_x000D_
N/A It
How
Summary
- is caused
_x000D_ end
Description
Plan user/operator
ofeffects:_x000D_
bythe lack
FL18A_ENB_0000_000802_000205_x000D_
provisioning
Correction
channel of the original
downlink of clearing
fails_x000D_ could
problem:_x000D_
correction:_x000D_
bandwidth detect
andwith freeing
thereduced
problem:_x000D_
descriptors
offset (iffrom one table in NBIoT
actRedFreqOffset is
PRACH._x000D_
Upgrade
Fault
set to 4256
Faulty
Dependency
Break
_x000D_
Impact
-Interface toto
component
infinite
true) is
SBTS18A
End-User:
effects: present
on after
configuration:
first
loop._x000D_
_x000D_ 0.2,
delivered
Service
None_x000D_ alarm
upgrading appears_x000D_
None_x000D_
in(e.g.
impact_x000D_ SW to SBTS18A
release, 0.2_x000D_
CD): Legacy_x000D_
_x000D_
-_x000D_
Workaround:_x000D_
Impact
-Customer to End-User:_x000D_
channel effects:
uplinkNone_x000D_
bandwidth (ulChBw)_x000D_
N/A Description
How
Summary
Impact
Faulty end
Dependency
None_x000D_
Service
_x000D_
-Test
Risk analysis user/operator
componentofofthe
todegradation
End-User:
Operator:
requirements: onthe
of original
the fault:_x000D_
configuration:
and Call could
problem:_x000D_
onversion: drop_x000D_
stability_x000D_
affected
correction:_x000D_
None detect
NBIOT the
MCtrl_x000D_
SWM_x000D_
cells._x000D_ problem:
inband _x000D_
enabled_x000D_
Incorrect
Upgrading
GSM
_x000D_
_x000D_
Risk
Safe_x000D_ ULvalue
analysis measurement
theofsoftware
ofthe Max.Total.Bandwidths
toisSBTS18A
correction: not workingSafe_x000D_ 0.2_x000D_
onand ANT2 Max.Total.Bandwidth
/ ANT4_x000D_ in FJ-CPRI
rmods._x000D_
_x000D_
Impact
Faulty
Description
Workaround:
Correction component
to Operator:
Operator:_x000D_
ofNone_x000D_ first
and Sitedelivered
version:
the correction:_x000D_
effects:_x000D_ autonomous SBTS18A_PHY_RX_x000D_
in(e.g. reset_x000D_
release, CD): main SBTS18A stream_x000D_
0.1 _x000D_
N/A Description
How
Summary
_x000D_
KPI
sm end user/operator
ofeffects:_x000D_
degradation._x000D_
-Interface
Correction
parameter ofthe
effects: the original
fault:_x000D_
LNCEL.moPrMappingList
None_x000D_ could
problem:_x000D_
detect the problem:_x000D_
has been removed_x000D_
t2a
Starting
Duringandcomponent
Workaround:
Impact
Faulty
Dependency
_x000D_
Description
-Customer
-Interface test
tota3
test dedicated
values
(T-CTRL
End-User:
of
effects:on
None_x000D_
effects: are state
L3still+ zero
theconfiguration:_x000D_
first Service
delivered
correction:_x000D_
None_x000D_
None_x000D_ SRT
ofdown SBTSbecause
in use),
in(e.g. , NBIOT
after
interruption_x000D_ int14override
release,thisICS
upgrade_x000D_ example
startis uplink
CD): not
"Static
yettestmodel
sent._x000D_
reference
_x000D_
sensitivity
fails._x000D_
Fixed UE storage
-Testanalysis
-Customer
Risk level"
FL18A_ENB_0000_000487_020055_x000D_
None_x000D_
Workaround:_x000D_
requirements: effects:
of theassize acorrection:_x000D_
test
Services
None from
check._x000D_ T-gate_x000D_
restored_x000D_
N/A Dependency
_x000D_
Summary
Impact
Problem
Description
-Test requirements:
Safe_x000D_ ofnotofthe
toisOperator: on
Operator:_x000D_
the
met configuration:_x000D_
original
ifSW problem:_x000D_
Upgrade
correction:_x000D_
U-plane
None reset failure_x000D_
is not performed for K2's where ULPHY is
None_x000D_
Description
_x000D_
SRAN
Impact
Faulty BTS
component
to
deployed._x000D_
Risk
Site
Includereset
analysis
harq usingUpgrade
oflist
End-User: the
of fault:_x000D_
and
WEBGUI
the
checking failed
Sporadic towhile
version:_x000D_
correction:_x000D_
does lack
preventnot upgrading
of
work service._x000D_
list toafterbefrom SRAN16.10
corrupted.
changing from to SRAN17A
Null test
guards also for
dedicated
T-gate
How
Packet
Mctrl,
_x000D_ end
Workaround: can't
GTS,
Safe_x000D_
state
placed to
Correction over
in user/operator
normal
the measure
TDM
MOAM_x000D_ sites._x000D_
None_x000D_
crash
state._x000D_
effects:_x000D_ signal
couldcorrectly.
point._x000D_ detect the Thatproblem:_x000D_
may be caused because some
N/A Summary
routing
Introduction
_x000D_
Impact
Faulty
_x000D_
Description
-Interface component
to of the
or Operator:_x000D_
mapping
of
effects:
of new
the original
is
and problem:_x000D_
ECarrierBandwith
not correct for div
version:_x000D_
correction:_x000D_
None_x000D_ forantennas
NbIoT cell (ANT2(0.2Mhz) & ANT4 in where is
only
MAC_CellSetupReq
How
FaultId
Longer
Faulty RX).
end
HAS_x000D_
Correction
Disable
-Customer 10 user/operator
ANT1
component
startup
Workaround:_x000D_
Risk
Description
analysisAT is ofraised
dueand
effects:_x000D_
of
the
external
effects: the after
first
to ANT3
causes could
planned
additional
delivered
correction:_x000D_
correction:
None_x000D_
events (TX/RX)
infailed
detect commissioning.
validation
GSM
the
autonomous
in(e.g.
None_x000D_
case of problem:_x000D_
UL on
release,
U-plane measurement
L2 Allside
reset._x000D_cells
CD):_x000D_
reset. Clear forwere
test
is working
the model
down, All
interrupt withRFs
flag the
same
functionality
After
not
when
-Testdetected
upgrade
configuration._x000D_
the sourcefor
(Fault
effects:
requirements:
interrupt of NbIoT._x000D_
FL18A_ENB_0000_000689_000000_x000D_
_x000D_
-Interface
SSH
For same
site reset was Sw,
file 10) remote
None_x000D_
used
routinename
None BB bus
tohasin connectivity
reset reception
targetBD and change
properly but error
failure
configuredwith (MUKSU)
sitecan
different
to
not be toseen._x000D_
normal raised
path,
miss (fault
mode._x000D_
especially
"first" the
N/A Summary
_x000D_
2016)_x000D_
Correction
path "" inofeffects:
Workaround:_x000D_
Faulty is component
interrupt._x000D_
-Customer the original
targetBD. first
None_x000D_
Servicesswm problem:_x000D_
delivered will in(e.g.the
search
restored._x000D_ release,
removed CD):_x000D_
file "/ram/" and do
Cell
-Testappear
Description
_x000D_
None_x000D_
Impact
-Interface
distribution to End-User:disabled
of
effects:
requirements: ontheconfiguration:
FL18A_ENB_0000_000802_000000_x000D_
Dependency whenever after
one upgrade._x000D_
fault:_x000D_
Service
None_x000D_
correction:_x000D_
None of degradation._x000D_
them None_x000D_
downloaded successfully. that will cause
During
After
How
_x000D_
If
-Customerend
upgrade
distribution
carrier
Risk test
analysis user/operator
setup model
effects:to
failure
ofistheSRAN
L2
triggered
due
No checks
tocould
17A
call the software,
ifdetect
drops_x000D_
while
correction:_x000D_ file not the there
problem:_x000D_
it is found._x000D_
already were
ongoing,packet drops
it will not in beQos
called
N/A Summary
module
BTS
How
Impact
Faulty
again.
-Test is
end
Description
_x000D_ not
component
to of
, which ofthe
user/operator
onAir_x000D_
Operator:
End-User:
requirements:
Safe_x000D_ Instead, the original
MAC_StartUlTestModelReq.resourceBlockOffset
ifresulted
and Disabled
Calls problem:_x000D_
could
in remote
version:_x000D_
itcorrection:_x000D_
provides
None may any detect
cellsbe connectivity
the problem:_x000D_
dropped._x000D_
appearance._x000D_
onFinish callback, failure
isonly
within
viait backhaul_x000D_
thebe
will range
called of after
given
Validation
Cell.
_x000D_
Start-up
BSTAT, NbIot
first setup
Risk
ULPHY analysis error
scenario
MANO,
is Cell
clearing ofhasafter
but only
MOAM_x000D_
completes._x000D_
the table sw
issue update_x000D_
oneisdescriptors
correction:_x000D_
with PRB,
intermittent_x000D_
so thisinvalue NBIoT should
after usingbe always elements= 0, but of this
_x000D_
Dependency
Description
Workaround:
Impact
RROM
Safe_x000D_
table._x000D_
Correction to
sends ofon theconfiguration:
Operator:_x000D_ fault:_x000D_Issue
None_x000D_
resourceBlockOffset
effects:_x000D_ from seen only on(=24)._x000D_
hostCell TDM sites_x000D_
N/A How
Summary
_x000D_
BTSOMexe end
Description
KPI
Faulty
Previously
ULPHY isuser/operator
of
degradation._x000D_
-Interface
Risk component
analysis of
error
freeingthe
crashed
effects: the
of original
was
the fault:_x000D_
first
unused not
None_x000D_ could
resultingproblem:_x000D_
delivered
visible, detect
to because
descriptors
correction:_x000D_ fault
in(e.g. the problem:_x000D_
10's_x000D_
in release,
in MAC_CellSetupReq
NBIoT CD):_x000D_ RROM sends
PRACH._x000D_
NB-IoT
Faulty
_x000D_
Rejected
Do
SBTS18A
ulChBw
Correction
Description
-Customer
Safe_x000D_ UL
sw component
update HARQ
ofchannels from
0.0.1_x000D_
host
effects:
of the failure
and
are
SRAN18
cell._x000D_ notisincluded
version:
correction:_x000D_
None_x000D_
Service high, even
to SRAN18A_x000D_
without _x000D_ adding more repetitions doesn't
in BASEBAND_CALCULATION_RESULT
degradation._x000D_
help._x000D_
TRSW,
Dependency
in
_x000D_
case
Workaround:
-Interface
Risk
Aligned
-Test when
FTM_SRAN17A_CBTS18_2018.08.28_0289_x000D_
analysisvalueeffects:
requirements: on
FailureRecalculationNeeded_x000D_
site
of configuration:
of the reset recovers
Max.Total.Bandwidths
None_x000D_
correction:Safe_x000D_
None None_x000D_
the cells._x000D_
and Max.Total.Bandwidth in FJ-CPRI
N/A _x000D_
Summary
Description
Impact
Dependency
-Customer
rmods
Correction to ofeffects:_x000D_
ofthe
to bpf-tool._x000D_
End-User:on
effects: original
theconfiguration:
fault:_x000D_ problem:_x000D_
None_x000D_
Services NB IOT_x000D_
restored_x000D_
How
Inefficient
Faulty end
Dependency
Missing
Description
_x000D_
-Test
Correction user/operator
componentresource
parameter
requirements:
-Interface ofon
effects:_x000D_
effects: andallocation
theconfiguration:
after
None
None_x000D_ could
version: detect
for
SW update._x000D_
correction:_x000D_
first delivered LTE2664
None_x000D_
MOAM
in(e.g. the_x000D_
problem:_x000D_
release,whenCD): NB-IoT planed in PUCCH
SRAN17A_x000D_
blanking
_x000D_
Check
_x000D_
PLH
Impact
Faulty
Risk will
-Interface the
analysis
-Customer area._x000D_
component
tonot syslog
Operator:_x000D_
proceed
effects:of the
effects: toand find
with
None_x000D_ many
version:
correction:
None_x000D_ UL/DL
the calculation
RROM_x000D_
Safe_x000D_ transmission
if t2a and ta3 failure_x000D_
values are still
N/A _x000D_
Summary
Faulty
Dependency
GSM
Impact UL componentofeffects:
tomeasurement
invalid._x000D_
-Customer
-Test the
End-User:
requirements: original
on configuration:_x000D_
first
and isproblem:_x000D_
delivered
version:
none_x000D_
Service
None not DCS_x000D_
workingin(e.g.on
restoration_x000D_ release,
ANT2 /CD): SBTS18 2.1_x000D_
ANT4_x000D_
How
On
with sites
_x000D_ end
Description
_x000D_
Faulty iot-fdd
Correction
-Test which
user/operator
component
requirements:cells
of the has 900
defined_x000D_
effects:_x000D_ fault:_x000D_
first None could
and 1800
delivered detect in master
in(e.g. therelease,
problem:_x000D_
slaveCD): configuration and also on
Two
SBCF
Faulty
_x000D_
The extra
Workaround:sites,
failure
componentPRBs after
mainly
FL18A_ENB_0000_010069_000000_x000D_
Impact
-Interface
Risk to End-User:
analysis Operator:
effects: are
any
happens
None_x000D_
of the first inpower
fragment
delivered
upgrade
Service
None_x000D_ onor transmission
Msg3whenDTX
in(e.g.
interruption_x000D_
correction:Safe_x000D_ fails_x000D_ LTE2664
release,
due fluctuation
and NB-IoT
toCD):_x000D_
Msg2 onnot
is siteenabled
, 1800 in
received TCH
by UE.
N/A Description
PUCCH
assignment
Faulty
Msg1
_x000D_
-Customer with blanking
component veryof
effects:the
failure
FL18A_ENB_0000_000802_000000_x000D_
large problem:
area._x000D_
occur
and
StableTA on _x000D_
site._x000D_
version:_x000D_
should
service_x000D_ be filtered out depends on field
No update
Sometime
PARAM,
deployment._x000D_
_x000D_
Workaround:
Impact
-Test
Correction
Description ofofarp
after
toADMIN_x000D_
End-User:
Operator:
requirements: table
reset
none_x000D_
effects:_x000D_
the All in
manually
None_x000D_
cells
correction:_x000D_
None theare sites after
itonair,
get nochanging
restored alarms the
its mac
. butraised_x000D_ address for the
not permanent
same
WA._x000D_
Impact
_x000D_
Create ip._x000D_
Description
-Interface to
pmuri End-User:
offor
effects: theSFP fault:_x000D_
Service
None_x000D_
related degradation_x000D_
caouters with default mcc, mnc, mncLength in
N/A Summary
_x000D_ of the original problem:_x000D_
_x000D_
Faulty
Dependency
The
Impact
case maximum
Description
Workaround:
-Customer component
to
LNBTS_A Operator:
of on PUCCH
configuration:
None_x000D_
the
effects: is first delivered
region
correction:_x000D_
not Test
Stable presentmodels is
None_x000D_
service_x000D_
in in(e.g.
reserved
for NbIot
SCF._x000D_ release,
unexpectedly._x000D_
not CD): SBTS18A 0.1_x000D_
working._x000D_
No update
How of arp table in the detect
sites after changing the mac address for the
-Testend
How
_x000D_
Corrected
Impact
BPF2:
same
end to user/operator
user/operator
Operator:
the sir
requirements:
merged
ip._x000D_
andKPI
4 RFChips spcould
None could detect
degradation_x000D_
shaper
to one related
RFChipthe problem:
the configuration
problem:_x000D_
in AHDA_x000D_ _x000D_ after upgrade _x000D_
After
Impact
Faulty upgrading
Dependency
Time tocomponent
Workaround:
Description
_x000D_ totime,
End-User:
ofonTCH enb from
theconfiguration:_x000D_
None_x000D_and
assignment
None_x000D_ SRAN17A
version:_x000D_
correction:_x000D_ to SRAN18A,
failure 100% in 1800 enb layer,is up is and
seenrunning.
in the KPIs.then
_x000D_
GW were swapped with samewhen ip_x000D_
address and
SBTS18A_PHY_RX,
LTE2664
_x000D_
Risk
Add
Workaround:_x000D_
condition
analysis and NB-IoT
of
to the
handle LTE_UP_x000D_
enabled,
correction:
MRI
correction:_x000D_ NB_IoT RU_L PRB is indifferent
PUCCHmac
down_x000D_ address. and then
blanking
How
ping end user/operator
stopped working._x000D_ could detect the problem: _x000D_
Impact
_x000D_
area_x000D_
This is
Safe_x000D_
Since impacting
this
Description to Operator:
isof racethe also Relations
condition the end
correction:_x000D_ with errors
user.
veryIn seen._x000D_
low order to recover,BTS
repeatability, customer
restartismight resetting
fix
After
_x000D_ upgrading enb from SRAN17A to SRAN18A, enb is up and running. then
Faulty
_x000D_
the
Risk site,
this._x000D_
For component
analysis
all NbIotwhich ofalso
Cell the first
impact delivered the cell
correction:_x000D_ in(e.g.
availability._x000D_
MAC_StartUlTestModelReq.resourceBlockOffset release, CD): SBTS18A 0.1_x000D_ = and then
GW were
Description swapped
how problem with same ip
can beRROM_x000D_ address
detected: _x000D_ and different mac address.
Faulty
_x000D_
Correction
Safe_x000D_ component
Workaround:_x000D_
0_x000D_ effects:NA_x000D_
effects:_x000D_ and version:
ping
After stopped
swapping working._x000D_
GW with same ip andupdate_x000D_
different MAC address, linux is getting
Impact
_x000D_
Description
Add the
-Interface tomissing
End-User:
of the
effects: fault:
parameter
effects:NA_x000D_ UEspecification
attach
correction:_x000D_
None_x000D_ after procedure
sw did not maybetake into
impactedaccount , accessibility
fluctuating
_x000D_
updated with new mac address but in FP arp table update is not seen for new
possible
Faulty
conditions
Correction
Add
_x000D_
Risk component
rejected
-Customer
analysis issues_x000D_
and code
effects:_x000D_
channels
effects:
effects:NA_x000D_ first doesdelivered
to the notlist handlein(e.g. it properly._x000D_
release, CD):From FL17A
of channels-to-be-recalculated in
Description
the MAC address._x000D_ ofof the the None_x000D_
correction:_x000D_
fault:_x000D_
N/A Summary of the original problem:_x000D_
Failures for CS RAB M1001C836 even in low loaded cells_x000D_
_x000D_
N/A How end user/operator
Summary of the originalcould problem: detect VoLte the problem:_x000D_
packet loss_x000D_
KPI counter increased seen_x000D_
_x000D_
_x000D_
How end user/operator could detect the problem: Bad speech quality. MOS
N/A Descriptionofofthe
measurements
Summary themay
original
fault:_x000D_
be bad_x000D_
problem:_x000D_
There
_x000D_
KPI degradation
exist failureseen for NBAP due toPSCR the DRX for profile
the concerned configuration cell before applied each in TTIBof the
"no_free_codes"
Description
mode. _x000D_ of theNACK fault:_x000D_ for HD AMR. As seen in BRM monitoring._x000D_
N/A UCI-only grants
_x000D_
Summary of the were original being problem: unsuccessfully RRH Energy requested Efficiency for TTI-bundling
counters notUEs.
This
How
displayed
The legacylead
end user/operator
toinfunctionality
problems
WebEM with withcould SRAN
after thethese detect
bundling
configuration
the UEs
NACK's problem:_x000D_
isnormal
with RNC
that only
PUSCH-grants,
2G
will and 3G RAT
put further which (no
caused
UEs
4G
PSCR's Lte
failRAT)_x000D_
the
to acceptpacketRRCConnectionReconfiguration
"freeze" loss._x000D_
for 60 seconds so that whatevermessage the situation that causing
providesthis
N/A Fake
_x000D_
Summary
(in BTS?) DRXcould ofseetings
the be original and problem:_x000D_
resolved. that is sent to UEs during
Unfortunately with TTIB thison, whenperiod
"freeze" UE has BRMa
QCI5
How
Remote
will not
Dependency end
bearer
Electrical
startuser/operator
active
new Tilt
on configuration: but(RET)
HS-PDSCH no
could QCI1 isdetect
displaying
code
Onlybearer._x000D_
the problem:
downgrade
occurs unusual
when check
behavior
(oractUciOnlyGrants
any other counters
after
PSCR performing
in procedure)
= true and
_x000D_
webem_x000D_
Send
and this
TTI-bundling Configuration
can cause is used._x000D_ DLFilecode Download congestion task._x000D_ since HS-PDSCH codes cannot be
N/A Description
_x000D_
Summary
downgraded. ofofthe theoriginal
And fault:_x000D_
in these problem:_x000D_
situations major part of DL spreading code
The
Description
How
False
resources
Faulty exact
end
positiveuser/operator
component root
wereof alarm
thecause fault:_x000D_
reserved
and 1907._x000D_
isversion:
could
not
for identified
detect
HS-PDSCH
MACPS_x000D_ the : whyproblem:
(10UE or dideven device
not 14like outwould
the
of 15send SF16GetTilt
RRCConnectionReconfiguration
Wrong
task
_x000D_ as counter
codes)_x000D_ FAIL._x000D_ computation was message done._x000D_ for TTIB activation, which includes
N/A Summary
_x000D_
HowIn
Faulty
Fake NetAct,
_x000D_ end
DRX
componentof the original
user/operator
Fault
settings 1844 first
?_x000D_ problem:_x000D_
occurs
could
delivered detect
then Alarm
in(e.g. therelease,
problem:_x000D_
1773 isCD): raised._x000D_
n/a_x000D_
When
Dependency
_x000D_
Occasional
Bothproblem
The ofreconfiguring
the failedalarm
on configuration:
was 1907
PSCR's 2G-SRAN
observed reported
seemed
under or 2G+LTE-SRAN,
N/A_x000D_
on toRF
the be module
following to the
that
related conditions:_x000D_ BCF active
vanishes
releasing ofafterSW ID is not
_x000D_
Description
reset._x000D_
updated
ERGCH/EHIHC
-Impact UEtoon has of
the
End-User:QCI5theNetactfault:
codes and Bad side._x000D_
Fault
(used
QCI9 speech 1844
bearers_x000D_
for HSUPA indicates
quality_x000D_ calls). that_x000D_
the RET is
N/A Summary
Faulty
NotCalibrated._x000D_
_x000D_
o component
QCI5 ofhas theTTI original
and
bundling problem:
version: enabled URI SBTS _x000D_ raises 1910 alarm while only GSM
(enforceTtiBundling=true)_x000D_
was
RNCactived
_x000D_
Description
How
Impact
o end
QCI5
raised with
to user/operator
of
Operator:
usesan the
old AHDB
DRX fault:_x000D_
issue
MOS configuration_x000D_
could
Profile that
can3_x000D_detect
be badthe
should address problem:
, customer wrong IDinseen_x000D_
the complains_x000D_
difficulty releasing
_x000D_
Impact
Incorrect
-ERGCH/EHICH
Faulty to DPD
Incomponent
this End-User:
case PAREST
codes
UE firstNone_x000D_
rejected HWinforming
delivered
and state
thein(e.g. machine interruption._x000D_
RRCConnectionReconfiguration_x000D_
delay release, of used CD): codes/signatures
n/a_x000D_ between
N/A Summary
_x000D_
Description
Howmayend
Workaround:
It
RNC and aofUE
BTS. ofthe
be user/operator the
Disableoriginal
issue
Upon faultunder problem:_x000D_
:could
_x000D_
uci-only
checking some detect
grants the
conditions_x000D_problem: 1910 alarm in customer
or TTI-bundling._x000D_
Cells
Impact
Dependency
Diagram
_x000D_
_x000D_ are
piloting_x000D_
tofordown
Operator:
End-User:ondue
fault to
configuration:
4424 When Configuration
wasupdating
none_x000D_
"CR_2277_RAN826_PSCR_Ack_during_failed_code_release" updated. GSMaerror: FRI
non
retconfighad
BCCHBTS configuration
tofileimplement
antennavia NetAct, error
line._x000D_
new the (not and
changes
operation
enough
appear
_x000D_
where
Description
Impact was
implementationto
toHW be for
missing
of
End-User:failed
the LCR)
in fault:on (1868)_x000D_
implementation
the
correction:_x000D_
BTS call SW, input
set customer
itupwaspower
success from
point
found is too FRI
oflow
rate
out view,
part._x000D_
and itbecause
decrease_x000D_
that this not
was causes the
fullycalibration
loopback
implemented is
N/A _x000D_
Summary
Faulty
power
Don't
Impact
not
in BTS component
triggered
request
SW. of NACK
issues._x000D_
to Operator: the original
automatically
UCI-only and RRH
status problem:_x000D_
version:
grants Energy
after
raised forFRM3_x000D_
retconfig
inTTI-bundling
Efficiency
L2 is Undefined update_x000D_
counters
UEs._x000D_Errornot wherein
displayed in WebEM
it should be
How
On several
end
Dependency
_x000D_
Impact
with
Invalid SRAN to user/operator
sites,
Operator:
Parameter itbased
on configuration:
configuration was
ERAB could
observed
with
onsetup detect that
N/A_x000D_
only 2Gthe
failure
CR_2277_x000D_ there
and problem:
related 3G is RATanKPI increase
cells
(no are
4G in
degradation down_x000D_
Ltecall dropsbe
RAT)_x000D_
might due to
several
Faulty
_x000D_
Dependency
_x000D_
seen_x000D_
Workaround:
Risk radio on
component
analysis link failures
configuration:
None_x000D_
of the first
correction: due toAHDB
delivered no sync
in(e.g. lost._x000D_
with
risk_x000D_ release,
GSM only_x000D_
CD): n/a_x000D_
N/A _x000D_
Summary
Faulty
Description
Workaround:
Dependency
Analysis component
ofofof the
theon the
add original
fault:_x000D_
correction
configuration: problem:_x000D_
and version:_x000D_
LNBTS_A risk MO to into
None_x000D_ the SCF even
the customer if only WNBTS and
/ end-user_x000D_
How
Cells end
are
Workaround:
GNBTS
Description
Impact
_x000D_
Correction down
user/operator
End-User:
used._x000D_ after
SBTS17A_ENB_1000_000652_000132_x000D_
Faulty
Problem component
toiswith IDLE2
ofswitch-off
the
effects:_x000D_ and upgrade_x000D_
correction: could
(especially
version:
none_x000D_
CRL19754;_x000D_ detect
Bug FRM
in was case the
(radion problem:_x000D_
of
detected SRIO SW)_x000D_
switch
in ALMAG typecode.B) Reason to
Decreased
_x000D_
implementation.
OR
why
Faulty make
earlier
-Interface TTI-B
component RRCpossible
mentioned
effects:_x000D_ connections
_x000D_
and fault only
version: in
occurredfor Cell-level
DRXwas
WBTS18 profile RRC
because report the and
2 (enforceTtiBundling=true
0.1mPD2_x000D_ increase
publishing of counter
resultonly
N/A How
Summary
Faulty
_x000D_
M1006C311end
Description
code
Impact
for
-Customerfor
QciTab user/operator
component
tosend ofwith
ofthe
Operator: original
configuration
the
effects:_x000D_ correction
wrong
QCI1);_x000D_ could
problem:_x000D_
CS_CALL_RADIO_CONN_LOST._x000D_
first delivered detect
alarming_x000D_
file
:_x000D_ in(e.g.
task therelease,
was problem:
done even cells
CD):_x000D_
CD): downthe
n/a_x000D_
before , rool
taskback was clears
the
SW
Faulty
OR
-Testissue_x000D_
upgrade
SBTS17A_x000D_
Dependency
_x000D_
In
completed.
caseswitch LNBTS_A
requirements:
component OF fails. Alarm:
onTTI-B._x000D_
configuration:
is
first notdelivered(0030)
present EFaultId_SwUpdateAl
None_x000D_
in
in(e.g.SCF,release, pm_uri CD): will be is seen._x000D_
computed
WBTS18 in this case
_x000D_
_x000D_
Impact
Description
using
Workaround: to End-User:
some
0.1mPD2_x000D_ of
bogusRFthereset_x000D_
fault:_x000D_
GSMfor
value calls impact_x000D_
plmnId._x000D_
N/A Description
How
Summary
_x000D_
Faulty
Major
Impact end to user/operator
scenario
componentofofthe
End-User: the original
shows fault:_x000D_
and could
that problem:_x000D_
version:
none_x000D_
correction: detect
thecircumventing
radio
n/a_x000D_ the problem:
link wasthe abnormally _x000D_
problem deleted
with withchecks
stricter cause5
Fault
SW
eNB
Impact upgrade
(Operation
_x000D_
Correctioncrashes
1905
Description
for fake toDRX because
isofwill
Operator:
impacts due
thefail
requested
End-User:_x000D_ to:KPI
and
of
paging
correction:
application._x000D_n/a null thevalues
due
degrades occurance
Alarm
toadd in
unexpected
onisregisters.
reset seen._x000D_
when
GSM_x000D_
DPD Cell transmission
Switch
PAREST Update router
HW from parameter
isUE machine
state not RLC list is
on
_x000D_
full_x000D_
Workaround:
Faulty
problem).
disabled._x000D_
coarse
Impact
increase
Fix component
to
delay
is limiting The
inOperator:
CS none_x000D_
thecause
search
failures
DRX first
BCFofactivation
delivered
the unexpected
interruption_x000D_
mightactive cause SWin(e.g.
during ID
limited isrelease,
cell
TTIB update
notusers correct
only CD):could
forison Legacy_x000D_
radio
QCI1 link failure.
theconnected
be Netact
bearer _x000D_
in toThis
bearerthe
N/A Description
_x000D_
Summary
indicates
_x000D_
cell_x000D_
list and only ofof
that the
in the
UEcaseoriginal
fault:_x000D_
has DRX problem:_x000D_
detected profilea2radio selected. link failure _x000D_ in downlink._x000D_
The
How
DLadvance
Impact
_x000D_KPIs
reason
end
Dependency
Risk
Description
In to degradation
analysis user/operator
ison
End-User:
of
for ofthat
the the
configuration:
the
FakeDrx lossobserved:
RAMcould
correction:_x000D_
correction:
correction: disk detect
of service_x000D_
profile CQIs
should
None_x000D_
Update
theSmall_x000D_
rangetheDPD/ SNIR
be
problem:created
oradded
algorithm
check evenDSP successfully
inDL crashes
lowthroughput_x000D_
for inputat
conversion at
powerRRH's
restart
NbTransmissionParamsList.hpp
_x000D_
Dependency
_x000D_
Correction
FRI
scenario (usl
implemented
drxLongCycle
Impact initialize
to(Operator: on
CNI-40317
effects:_x000D_ usrReboot-
to configuration:
properly
drxOnDuratT:
wrongimplemented)the
KPI_x000D_ rfhInit2-ramDisk),
at line:
None._x000D_
diagram
_x000D_ _x000D_ 0x43
for fault which butenables
4424._x000D_ the ramCat-M deviceand on inband
the
N/A NB-IoT._x000D_
How
Summary
Impact
_x000D_
Faulty
site end
-Interface to user/operator
WA73XC356
component
drxLongCycle(10)-- of the original
Operator:
effects: creation
and could
problem:_x000D_
accessibility
None_x000D_ version:
drxOnDuratT(10),failed detect
n/a_x000D_
in
, cells
the the LTE problem:_x000D_
are
_x000D_ down_x000D_
board before the upgrade and
_x000D_
Since
Observe
Faulty
there
_x000D_
-Customer
Risk introduction
was
analysis
drxLongCycle(20)--
Workaround: 4G
componentno DL
effects:any
of the hourly
of
error
none_x000D_ and improved
Increased KPIsrecorded
version:
info
correction:_x000D_
correction:
drxOnDuratT(20), afterSW SW
CP_LRM, crash
performance._x000D_
no into
risk_x000D_ upgrade_x000D_
_x000D_ detection
trace.
SBTS17A _x000D_ for2.0_x000D_
REL5.1 RFs, a set of
Description
_x000D_
occasional
Workaround:
Faulty
-Test
Safe
Analysis of reports
component
requirements:
drxLongCycle(32)-- ofnone_x000D_
the the fault:_x000D_
correctionwas
first
None received
delivered
risk to the
drxOnDuratT(30), indicating
in(e.g. customer release,
_x000D_ that/ SW CD): crashes
end-user_x000D_n/a_x000D_ happen which
N/A Description
finally
Summary
Incorrect
Faulty
Dependency
_x000D_
Correction
_x000D_ ends
component
drxLongCycle(64)-- of
sizeofthe
up on the
with
effects:1910ofconfiguration:
original
NbTransmissionParamsList
fault:_x000D_
RFSW
first problem:
delivered
alarm
drxOnDuratT(60),
correction:_x000D_ rollback n/a_x000D_ _x000D_
in(e.g.
removed_x000D_to passive/backup
release,
_x000D_ is CD):
used SBTS17A_x000D_
,version
causingand thereporting
DSP
crash._x000D_
alarm
RRC
Modification
_x000D_
Impact
_x000D_
-Interfaceblocking
Description1850._x000D_
to End-User:
drxLongCycle(80)--
Implement ofofthe
effects: due x-shift todrxOnDuratT(80),
Uplane
Loss
no_x000D_ timing
correction:_x000D_ calculations
overload,_x000D_
of service_x000D_
CR_2277_RAN826_PSCR_Ack_during_failed_code_release counter
i connectivityM8013C66 component
increasewas on some in
introduced,
_x000D_
sites.
Impact
Faulty
_x000D_
-Customer
Use _x000D_
component
scrambler
drxLongCycle(128)--
BTS side. however
to End-User:
effects:
_x000D_ and
for FCT/FSP radio
3G
no_x000D_ version: component
service
drxOnDuratT(100), link.n/a_x000D_
impact_x000D_
Requires of _x000D_
RFSW RapidIO was't IDLE2readysequence._x000D_
for that change
N/A Summary
yet._x000D_
How
_x000D_
Impact
-Test end
Dependency
_x000D_ to of the
user/operator
Operator:
requirements:
drxLongCycle(160)--
Return PSCR on Nack original
configuration:
Cells
no problem:_x000D_
could
1910 down_x000D_
drxOnDuratT(100),
status Invalid detect
Cat-M
alarm the
parameter andproblem:_x000D_
inband
_x000D_ whenNB-IoT ERGCH/EHICH are used_x000D_ code is still
_x000D_
Alarm
How
The
beingWEBEM
Faulty
Risk
Impact end1850
to user/operator
component
analysis
drxLongCycle(=256)--
used happens
Operator:
by table
ofuser thefirstshownon could
REL5.1
delivered
Increased in Centralized
correction:N/A_x000D_
while detect
call
drxOnDuratT(200)._x000D_
RNC RFs
in(e.g.
tries the (mainly
drops._x000D_
to problem:_x000D_
RET Galaxy
release,
remove management
theCD): family)
n/a_x000D_
codes._x000D_ has
andmissing
in
Dependency
postmortem
FSP
borders, reset,
Workaround:
Faulty
_x000D_
Correction
_x000D_ ineffects:
component Unit
SRAN17A
logs
on reset,
_x000D_configuration:_x000D_
"recovery
and
_x000D_ synchronisation
the
version: borders
reset" MAC can
were be
failure,
PS_x000D_clearly
seen._x000D_1868,
visible. disabled The borderscells and increase
alarm
N/A Summary
_x000D_
0016
the
Not
Impactlegibility
All Galaxy
mixing
-Interface
Workaround:
Risk
Now analysis
Fake of
(synchronisation
to End-User:
CPRI
effects:
DRX the
of
family ofthe
Remove original
with
logic
the data
(FDD)
_x000D_ inproblem:_x000D_
alarm)
None_x000D_
OBSAI
correction:
going the
multi-NAHKA
commissioned toon appear_x000D_
table_x000D_
be alimited
single
None_x000D_ / multi-band
configuration._x000D_
PICs_x000D_
only to theproducts case TTIB-ON are affected, + QCI1
Served
Description
_x000D_
Faulty
however
_x000D_
-Customer
bearer
Correction inantenna
component
severity
the oflist
effects: theand
effects:_x000D_lines_x000D_
DRX in
fault:_x000D_
will
first varry dropdown
delivered per frequency
Profile in(e.g. list are
selection release,too
variant,
chosen narrow_x000D_
CD):cell2nd n/a_x000D_
powerDRX and carriers
Profile. _x000D_
Due
Description
How
_x000D_
Impact
-Test
For to
end
congiuartion.SoC
to user/operator
requirements:
-Interface
all other of
silicon
Operator:
effects: We
case thehave fault:_x000D_
tolerances
correction:
legacySWknown
None_x000D_ could
upgrade
behavior detect
and
_x000D_ not
CQIfailure_x000D_
DCD+PICs the
degradation
going optimal
problem:_x000D_
are
to beset configuration
on toAHEGBhave theuntis
placed._x000D_ parameters,
leastand severe
priority data
N/A Summary
corruption
Driver
Operator
How
_x000D_
Impact
DL
when
Code endresponses
to in
throughput
-Customer selecting
was of the
user/operator
ineffects:
RET
End-User:the
disabling original
RAM
management
to Improve
degradation
keplers clientmight
temporary
switch problem:_x000D_
could
for was be
inuser
resource
router detect
incorrect
page
AHLOAoccasionally
loss by of the
will and
4G
allocation
sending
connection problem:_x000D_
detect
(MCU experienced.
this
and
service_x000D_
AHFIB to
within inproblem_x000D_
decreaseUP HWAPI,
LTE._x000D_
the This causes
CC&S).SW
the chances
cell_x000D_ Inthe
of
Path
services
some
_x000D_
By MTU
opening
cases crash
Workaround:_x000D_
problem Discovery
API_SUM_SET_TYPE_FWD_REQ
-Test
Risk Served
, itof
occuring_x000D_
analysis
requirements: which
wastheantenna is completed
recovering
finally
correction:
None triggers
lines and
,n/a_x000D_
indropdownRFsuccessful
some
message recovery
other intoRETcases only
reset.
HWAPI detailsfirst
, never
Inwith time
addition, when
view._x000D_
msgTypes=0.RAM/DDR It
operator
recovered._x000D_
Description
_x000D_
Manfully
Impact
Faulty
initialization
When
was changed
Correction trigger
component
tomake
allocating of
Operator: the
procedure
to this
diravoid
resources
effects:_x000D_ action
fault:_x000D_
'/ram'
and has
this from
instability_x000D_
version:
onrouter
been
RRH,
for Admin.
Issue
users, modified._x000D_
then
switch Starting
injected
upgrade
DCD+PICs
off._x000D_ inwith 2nd
isFRM58.11.R18I_x000D_
are successfully,
avoided trying, the
asafter
much following
theas
N/A message
Summary
_x000D_
Missing
Description
inactive
possible
-Interface tois
tableof
reset, shown:"Cannot
oftheborders
decrease the original
'/ram'
effects:_x000D_ in problem:_x000D_
fault:_x000D_
disk
the triggerofPMTU
Centralized
is recovered._x000D_
chances RET
the problem discovery"_x000D_
management_x000D_ occurring_x000D_
After
Dependency
_x000D_
Table
Workaround:
Faulty
Risk adding
design
component
analysis
-Customer anone_x000D_
onofisnew cell
configuration:
not allowing
configuration:_x000D_
the
effects:_x000D_ first to configuration,
delivered
correction:n/a_x000D_ enough
Rel4 in(e.g. onwards cell (including
space_x000D_
release, from CD): another radio goes
5g)_x000D_
SRAN18SP 1.3.4,
offline
Dependency
_x000D_
How
SRAN18SP
It
Risk end
Correction
Description
-Test ._x000D_
hasanalysis
been user/operator
on
confirmed
2.1_x000D_
effects:
requirements: of ofthe configuration:
the thatcould
correction:_x000D_
n/a_x000D_
correction: often detect
RET
Theoptical isthe
problemused_x000D_
problem:_x000D_
breaks can onstill connection
occur at very between high BBU
N/A _x000D_
Summary
Dependency
Configure
Description
and
Faulty RF
loads_x000D_
-Interface
The component
enhancement of
aseffects: ofthe
well theasoriginal
PATHMTUDISCOVERREQ
on configuration: problem:_x000D_
correction:_x000D_
unconnected
and
n/a_x000D_ version:
on checking n/a_x000D_
n/a_x000D_
SFPes
the return andplugged checkof
value for
into the increase
RF
'ramDisk' probability of
and 'ftpFileGet' is
How
SBTS
Faultyfixend
_x000D_
Analysis
-Customer
the GSM
of user/operator
PATHMTUDISCOVERRES_R
correct
Impact
problem component
to
sizeof
this remote
appearance.
End-User:
of
effects:
the FTP and
correction PS
issue. InOnly
n/a_x000D_ Uplane
could
version:
NbTransmissionParamsList
worst
Ifriskselected
the detect
IP
scenario
to
errorthe not
values._x000D_
webem_x000D_ the updated
units
info DL
customer problem:
(NAHKA
'/ram is/correctly
throughput
in order By
end-user:
missing' tochecking
SoC bewhen
degraded
silicon
adjusted
is changed
status
Low_x000D_
reportednature)
upwith totoofBBU,
cell in
through
Faulty
_x000D_
admin._x000D_
Correction
-Test
then the GENA
component
NbUeStorage_x000D_
40%_x000D_
experiencerequirements:
user thecan
effects: command
issue. and
first
decide
Low_x000D_
n/a version:
Problem from
what BSC._x000D_
delivered ADMIN_x000D_
was
to in(e.g.
domainly next release,visibleCD):
(inactive on resetGalaxy
legacy_x000D_
or mkdirfamilyram (AHxxx)
N/A _x000D_
Summary
Faulty
Description
and component
parameters
Interface
manually)._x000D_ ofofthe
effects: original
theoptimization
fault:_x000D_
first delivered
None_x000D_ problem:_x000D_
wasin(e.g. done for release,thoseCD): units.n/a_x000D_In parallel, HW
How
WCDMA
_x000D_
Faulty end
measurements
Impact
Customer
Risk to user/operator
analysis throughputs
PathMtuDiscoverResult
Description component ofof
Operator:
End-User:
effects: thefor
the other
Low. DL are
fault:_x000D_
first could
delivered
temporary field
KPIs
correction: degraded
REL5.1
Decreased ofdetect
degraded_x000D_
loffplatform
n/a_x000D_ os the
after
PATHMTUDISCOVERRES_R
in(e.g. chances problem:_x000D_
AHGB
release,
service_x000D_
units of the are link
CD): break_x000D_
n/a_x000D_
performed
problem wrongly
to make sure
occurring_x000D_ set.
7725
_x000D_
Different
problem
Impact
Risk Alarm
Correction
Test Cell
toimpedance
analysis raised
End-User:
requirements: than
of thethe
effects:_x000D_ atcorrection:
BSC
will one beand
none_x000D_ added
optimized GPRS (from
n/a_x000D_ will
there not
another aswork._x000D_
Rmod) is marked as
well._x000D_
N/A Configure
How
Summary
Impact end
Information
redeployment
Workaround:
_x000D_
Correction
-Interface to user/operator
of
BTS the
End-User:
about
Operator: with
original
needed._x000D_
SW
effects:_x000D_
effects: error differentcould
problem:_x000D_
none_x000D_
was
downgrade_x000D_
disabled
n/a_x000D_ notUplane
detect
propagated
cells_x000D_ the
remote problem: CS/PS
to DEM. Hot Ipaddress
remove
DEM did not anddelete execute
cablink._x000D_
1900
conf_m
_x000D_
the
Faulty
ImpactGENA
-Interface
-Customer alarm
objects
component
to command
Operator:
effects: raised
effects:_x000D_ and after
correctly._x000D_
from
visibility
n/a_x000D_ redfreqoffset
version: BSC. & clarity Afteron
Faults this
aresetRET IPto address
visible4.7 instead
sinceisintroduction
tables_x000D_ of(4393:
not correctlyofupdated
_x000D_
EFaultId_ReducedLteGuardBandConfNotMatchingFrHwAl_x000D_
Impact
Dependency
at BTS/Web
improved
Workaround:
-Customer
Description
-Test to Operator:
SW
requirements: ofAdmin._x000D_
on
effects: theconfiguration:
detection
automated useability reset,of
mechanism
correction:_x000D_
n/a_x000D_ FSMF
soWEBEM_x000D_
no inconfiguration
need
FRM58.08.R08H_x000D_ with passthrough
and bbmod.
N/A Description
_x000D_
Summary
Dependency
FRM58.09.R09._x000D_
Workaround:
-Test
Fallback ofof
requirements:
to the
oldon the original
n/a_x000D_
way fault:_x000D_
configuration:
n/a
of x-shiftproblem:_x000D_ noe_x000D_
timings calculation_x000D_
How
PLH end
WCELs
_x000D_ wasisuser/operator
Description
Workaround: not
notof able onair
the
User to and
handle
fault:_x000D_ could
correction:_x000D_
can alarm
hold todetect
mouse 7771
handle the
raised
cursor failed
problem: after
response
above unlock
set
antennaredfreqoffset
from
operation_x000D_
HWAPI
line to see todue 4.7 to
whole
_x000D_
Faulty
different
DISABLE_ROUTING_TASK.
HW
Description
name
RiskBCN component
in
analysisIpcomes
address
tooltop_x000D_
ofof the every
the andReceived
correction:
first version:
delivered
frame add
correction: The
from
OAM_x000D_
DCS@74442_x000D_
(10ms), failed
in(e.g.
Safe, BSC
borders the
we task
without
for should
release,
comparison
just the reset
CD):
fallback be
table_x000D_[isusing
cleared
_x000D_
to doneGENA
previous by BCN is
when
_x000D_
How
command] endand
requested,
solution._x000D_
All LTE user/operator
CLEAR_STREAM_CONF_TASK._x000D_
was
notSBTS notreleases
particularly properly could each detect
communicated
(including 10ms, the problem:_x000D_
since
maintenance toit Transport._x000D_
will bepackages) extra unneeded that useload if
Description
Cellanalysis
Faulty
_x000D_
nobody
Risk
branch iscomponent
Correction Hdown
needs(laterofof after
the
that.
the
effects:_x000D_
then fault:_x000D_
cell
first unlock.
delivered
correction:_x000D_
MCU
correction:
R08H) HWAPIor RFSW And in(e.g.
safe_x000D_
asks can't be(09.R09
release,
around
trunk setup CD):
each again._x000D_
DEM,
n/a_x000D_
later).TAS_x000D_
second.
or We also have
In particular:
_x000D_
FXJB
Dependency
calibration
CSS
Correction
SBTS18SP,
-Interface doeseffects:
styling for not
on
effects
is BCN support
changed
SBTS18A, :each
_x000D_
N/A_x000D_ tothe
configuration:_x000D_ LTE9.4._x000D_
second_x000D_
L18SP,show entire _x000D_
L18A. antenna line value._x000D_
_x000D_
Description
Impact
Air
No Scale
particular
-Interface
-Customer to BSC of configuration
End-User: the
to be
effects:_x000D_
effects: fault:_x000D_
in
Cell use
none_x000D_
N/A_x000D_ is andnot
but onAir issue
Ipaddress -should
Unable forbe Uplane
topresent
call_x000D_PS/CS on config remote with ipaddress
TCOM-TOAM
_x000D_
should
WCDMA
Dependency
Risk
-Customer be
-Testanalysis
Impact to cells._x000D_
requirements: onofisthe
configured notcorrection:
sending
configuration:
effects:_x000D_
End-User:_x000D_ differently._x000D_
correction:_x000D_
performance resource tests,release
FXJB._x000D_
none_x000D_ KPIs observation in TCOM-LRM when TCOM is
located
Impact
_x000D_
-Test
Correction
No
Safe service
as in
tothe FSP
Operator:
requirements:in board
effects:_x000D_
fixaffected
is only cellother
diagnostic
triggered
sector than
down_x000D_ (RF 0x10
fails_x000D_
upon is not and
that 0x20.
transmitting)._x000D_
rare Cell Setup fail after cell
circumstance_x000D_
N/A Summary of the original problem:_x000D_
Remote Snapshot collecting never ends with long link break in 3s after
collection starts_x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
How end user/operator
Frequency signal is decreased could detect for severalthe problem:_x000D_
seconds every five
start remote snapshot collecting ,and disconntct the connection with BTSMED
minutes._x000D_
N/A in 3s._x000D_
_x000D_
Summary of the original problem:_x000D_
_x000D_
How
GSM end
Calls user/operator
are failing oncould Node-3 detect & Node-4the problem:_x000D_
in 4+2 configuration with
Description
AHDB_x000D_
Frequency signal of the fault:_x000D_
is decreased for several seconds every five
N/A minutes._x000D_
_x000D_
Summary
SNAPSHOT_COLLECT_IND of the original problem:_x000D_ is still not received from BTSMED within 60
_x000D_
How
Fault
seconds, end
125 user/operator
on several
but don't deal WCDMA
could
with the detect
cells when
the problem:_x000D_
problem._x000D_ DSS is activated on both CPRI and
Description
Calls
OBSAI
_x000D_ not radioworkingofmodules_x000D_
the on fault:_x000D_
the Node-3 & Node-4_x000D_
N/A RF
_x000D_
Summary SW justofmask
Dependency the original
blinkedproblem:_x000D_
on configuration: bits with NA_x000D_WCDMA carriers. . It will make LTE carriers
Description
How
wrong
_x000D_
be end
blinked value user/operator
ofofthe
every srProhibitTimerCatM
fault:_x000D_
firve could detect the
minutes_x000D_ in problem:_x000D_
Connection
Prepare
RRCConnectionReestablishment_x000D_
Faulty component
_x000D_ configuration
failure and is observedwith
version:many on (9)switching
URI_x000D_ WCDMAofcells nodes and to let
Node-3.
at least_x000D_ 3 have DSS
N/A RF
enabled.
_x000D_
Summary Channel
Dependency Connect
of is the
onreleased
original
them through
configuration: stating
problem:_x000D_'Conn
radiosfail
WCDMA inand threes.
for LTEChannel'._x000D_
_x000D_
TX carriers are setup on the
New
_x000D_
How
RLF
Faulty
same Hand
calls
end user/operator
pipe_x000D_
component are
Over notwon't triggered start
could
first delivered on
whendetect
Node-3 RLF
in(e.g. the& indicator
problem:_x000D_
Node-4CD):
release, came
with n/a_x000D_
allduring
other nodes blocked
from
Description
Problem
SCellSwap._x000D_
_x000D_ ADMIN._x000D_
canofbe thedetected
fault:_x000D_ by checking content of
N/A Summary
Path
_x000D_
Impact
Faulty for toWCDMA
component of the original
RRCConnectionReestablishment,
End-User: control
and problem:_x000D_
channel
none_x000D_
version: RFwas inSW RRC chosed re-establishment
Vega_x000D_ through DSS procedure link. DSS has
Uplane
downlink
performed
How
_x000D_
Dependency end was bywrongly
timing.
user/operator
cat-m
on ThatUE
configuration:calculated
desynchronized
could
with VoLTE and cells
detect
None_x000D_ are
bearer._x000D_
the the linkdown
problem: andLogs afteranalyzing._x000D_
upgrade._x000D_
cells._x000D_
_x000D_
Impactcomponent
Faulty to Operator:first cannot
deliveredcollect in(e.g.
snasphoot release, , troubleshooting
CD): n/a_x000D_
N/A Summary
Dependency
Description
How end
impact_x000D_
_x000D_
Faulty component ofofthe
user/operator
on original
theconfiguration:_x000D_
fault:_x000D_
and version: problem:_x000D_
could detect
HAS_x000D_ the problem: _x000D_
ABIA
Impact
_x000D_
many all,(9)DSP
sr-ProhibitTimer-r9
SCellSwap
Not cells
to WCDMA crash
cannot
will
End-User: be,cells cells
onAir_x000D_
bein call down
and
drops or
,atUEin
RRCConnectionReestablishment
aborted letby wrong
RlfInd
least
attach 3if havestate
the _x000D_
procedure
possible DSS set
was
issues_x000D_
enabled. totriggered
fixed value
Connect by 0A6
them for
_x000D_
cat-m
measReport._x000D_
Workaround:
Faulty
through UE
component withnone_x000D_
radios VoLTE firstbearer
in threes. delivered
_x000D_ insteadin(e.g. of release,
O&M parameter. CD): SBTS18A IE macMainConfig
0.2_x000D_in
N/A Summary
Impact ofofthe
RRCConnectionReestablishment
_x000D_
Description
How end to user/operator theoriginal
Operator:_x000D_ fault: could problem:_x000D_
_x000D_ detect was thebuild problem: according SBTS tostartup_x000D_
requirements for
After
Dependency
Transparent
_x000D_
Frequency
Impact
Faulty
Description LTEcomponent Legacy
RRCConnectionReconfiguration_x000D_
to End-User:ofmode
on
signal SOAM
theconfiguration:_x000D_
isandfor port3
decreased
No SWwas
version:
calls
correction:_x000D_ Upgrade,
or forset
RP002014.
drop for
several Diagnostic
FBBC
calls_x000D_ seconds instead
DCS_x000D_ files ofcollected
every local (6450)CDR
mode._x000D_
five minutes. Alarm
is
UE
KPI present
_x000D_
Description
greater
increase_x000D_
SNAPSHOT_COLLECT_IND on than
howLTE, 8, and
problemLTE3105 blackbox
canand be information
detected_x000D_
is stillLTE1617
not received shows
should be
from anON_x000D_
unexpected
BTSMED within spurious
60
N/A reset
Summary
_x000D_
Dependency
WCDMA
Impact
Faulty
seconds, during
to cell
component of LTE the
Operator:
sOAM on original
SW
willconfiguration:
notfirst
cancels activation._x000D_
reach
Calls problem:_x000D_
delivered
not
the onsnapshot
Air
_x000D_
working state._x000D_
None_x000D_
in(e.g. on release,
the Node-3
collection._x000D_ CD):&SBTS18A Node-4_x000D_ 0.2_x000D_
_x000D_
Alarm
Faulty
In some
Workaround: 7116
component
configurationBASE
don't andsetup STATION
with
version:FSMF
WCDMA SERVICE
Cplane
+and revPROBLEM
2FBBC/FBBA_x000D_
LTE .TX
697491_x000D_
carriers with
onfault ID 134 'Rx
the same
signal
_x000D_
Description
How
Workaround:
Impact
Faulty end
Risk analysis
pipe._x000D_ level
component failure'
to user/operator
ofNone_x000D_
the
End-User:_x000D_
of the andraised
fault:_x000D_ couldin network_x000D_
version:
correction: detect
UEC_x000D_
NA_x000D_ the problem:_x000D_
N/A _x000D_
Summary
Faulty
SBTS
Alarm
Service
Correction may
6450
component ofeffects:_x000D_
isthe
raise
interruption original
visible._x000D_
a and
first
faultsuch problem:_x000D_
on delivered
version:
affected like:cells._x000D_
DCS_x000D_
in(e.g.
6253 -release, Cell configuration CD): data distribution
_x000D_
DSS
Description
Faulty iscomponent
failed_x000D_ noteffects:_x000D_
working
FL00_FSM4_9999_190115_024406_x000D_
-Interface , only
of the correction:_x000D_
first slim carrier
delivered in(e.g. feature
release, is working_x000D_
CD):
_x000D_
How
makeend
Workaround:
Flood
Description
Accumulate
Impact of toSRIO user/operator
of
allN/A_x000D_
FL00_FSM3_9999_000000_000000_x000D_
-Customer blinked the
errors
Operator:_x000D_ fault:_x000D_
preceding
effects:_x000D_
bits arecausing could
masked detect
bearer
t14 values with all the
setup
to problem:
compute failures
carriers._x000D_ for_x000D_
(UEC_DB_BEARER_INIT
total t14 needed in the
N/A _x000D_
Summary
failed)_x000D_
Create
Thererequirements:
Unable
Impact
-Test was
calculation_x000D_to of
atoseveral athe
End-User:
use change
DSS original
TxMeasurements
on problem:_x000D_
inCPRI/OBSAI
FSMr3
Possible U-Boot
call MOs
drops_x000D_(introduced
and UdpReport
configuration_x000D_ in MO with parameter
How
Failed
Description
_x000D_ endCell
to user/operator
PS_LFS_BT_2019_01_0002)
"identifier"
Impact
Risk analysis blocking
equal
ofof
End-User: the 1_x000D_
the operation
correction: could _x000D_
None_x000D_
correction: detect
blocked
where the
the
no risk_x000D_ cell
problem:_x000D_
size teardown
of the U-Boot during log sitebuffer
reset_x000D_
was
AHDB
_x000D_
Local
Dependency
increased.
Enable DSS
mode
Workaround:_x000D_
Impact
Risk
Correction to
analysis Thefeature
TxMeasurements
will
Operator:on
ofside
be
effects:_x000D_
the does
configuration:
set effect
KPI for not
and
port3
was work_x000D_
UdpReports;
n/a_x000D_
that
on FBBC
degradation_x000D_
correction:Safe_x000D_ the start if two
fault
addressor103 more raised._x000D_
of theRmods nvrd are wasconnected
moved to
N/A _x000D_
How
Summary
a lower
Disable
Impact
and
Correction end
port
-Interface to 3user/operator
DSS. of
address the
Operator:
will beoriginal
Split than
used._x000D_
effects:No._x000D_
effects:_x000D_ WCDMA could
problem:
it used todetect
srProhibitTimerCatM
cells beto _x000D_
theleast
(nvrd
at problem:_x000D_
address
value was
twoisgroups calculated
wrong_x000D_- DSS and based non on U-
Description
The
Counter
Faulty
Boot
DSS._x000D_steps
log impact
component
Workaround:n/a_x000D_
_x000D_
-Customer
-Interface and of theobservations
observed
address/size)._x000D_
effects: fault:_x000D_
and
effects:No._x000D_
None_x000D_ after
version: aren/a_x000D_
WBTSs
as below:_x000D_ upgraded to WBTS18 _x000D_
1.
There
_x000D_
In
UdpReport
LTS a SW
Workaround:
Risk
-Test The
wasis upgrade
analysis
-Customer increase
site
not
requirements:The is
of in
functionallity
finding
None_x000D_
effects: the in
commissioned
scenario,
NoM1006C186
GNCEL doesn't
correction:
drop
same the cause
old state
workafter
release
N/A_x000D_
calls_x000D_
test ofdue
case and
WBTS
expanding
asto working
has upgrade,_x000D_
incorrect
this the
PR. on state
nvrdBCF with
handling
initialized
which LWG
ofhad at profile
subsription
address and
different
N/A configuration
_x000D_
Summary
Faulty
A.
IDs
ID When
than
from
Description
Correction
-Test component ofeffects:_x000D_
GTS_x000D_
the
requirements: ofthe
different mentioned
newtheoriginal
software
clients_x000D_
first problem:_x000D_
above._x000D_
delivered
correction:_x000D_
None release in(e.g.
is started,release, theCD):newer n/a_x000D_
U-Boot is started from
2.
How
One
uImage
_x000D_
_x000D_
Description
Handling
-Interface
Separated UlComp
BCF
endand user/operator
ofBlock
effects:
of cell
this
RlfInd
the
constraint is cannot
one initiated
N/A_x000D_ could
tells
correction:_x000D_
during be from
Linuxallocated._x000D_
SCellSwap
description detectADMIN._x000D_
that
andthe the problem:
nvrd
triggered
now DSS is byat
linkKPI
address
A6will degradation_x000D_
measReport
preventB (lower control than A).
was
3.
_x000D_
When
Dependency It Linux
istoobserved
sr-ProhibitTimer-r9
added._x000D_
-Customer
Impact
channels starts,
onchoosing
End-User:_x000D_
effects:
from that
configuration:
itincannot
All the BCCH
find TRX
DSS_x000D_
beany
RRCConnectionReestablishment
cells will
it._x000D_ valid
onAir_x000D_ in eachnvrd at sector
that remains
address.
will be set inTherefore,
working
with O&M it
N/A Description
How
Summary
_x000D_
-Test
WCDMA end
re-initializes
Dependency
state
_x000D_ and user/operator
ofof
BCF
requirements:
parameter_x000D_ the
the
resources onthe original
fault:_x000D_
isramdisk.
configuration:
stuck N/Ain
are could
problem:_x000D_
notThere
Blockingdetect
None._x000D_
willstate
available._x000D_ theno
be problem:_x000D_
on/var/log/last.0
ADMIN. Unexpected_x000D_ (so the logs from the
It
Set
Afteris up
previous
Faulty
_x000D_
Risk observed
upgrade
following
component
analysis startup that
to the
of SBTS18A,
configuration:_x000D_
are though
and lost). we
version:
correction: RRC
Also
correction:_x000D_havethe and forced
n/a_x000D_
RPRAM
Safe_x000D_ ERAB the drop
speed
files, increasing
where to 100mbps many
applications andstoredisabled
Auto-negotiation
FBBA1
sites._x000D_
some
Faulty
Description
_x000D_
Correction
Impact
safe_x000D_
Risk - LTE
information,
component
to
analysis ofof
Operator: 6DSP
the
effects:_x000D_atfault:_x000D_
the are
and both
forlost.
WCDMA LTE
theTherefore
version: ends
3x2600
RAT
correction:Safe_x000D_ when
is (3x20M)_x000D_
Draco_x000D_ the
applications
not workingcontrol registeron
wrongly
properly ofSBTS._x000D_
EIF1 PHY
assume that this
N/A transceiver
FBBA2
_x000D_
Summary
Faulty
MCtrl
was -not
reserved
a isspurious
-Interface
Correction component of is the
able
effects:checked,
original
tofor
reset,
effects:_x000D_ firstcreateLTE
None_x000D_ Auto-negotiation
problem:_x000D_
but
delivered
when in not used
CARRIERS_BLOCK_TASK
factin(e.g. (should
it wasrelease, bit
justinathis beCD):
normal register
used forforoverbooked
n/a_x000D_
reboot isLTE
enabled
that3xis1800 and
TRX
needed so in
we
(3x20M))_x000D_
How
After
Faulty
because end
_x000D_
Workaround:
case
-Customer
Correction end
hot up remove/insert
ofcomponent
-Interface user/operator
with 100mbps
CARRIERS_READY_FOR_SETUP_TASK
software effects:
Site
effects:
effects:_x000D_ first
upgrade. FRGT
could
No delivered
reset_x000D_
None_x000D_ call half detect
duplex
WCDMA
Nevertheless
drops in(e.g.
relatedthe
onrelease,
some
problem:_x000D_
the
this
to thisBTS cells which
CD):
"spurious arefor not
is leading
N/A._x000D_
issue._x000D_ this
reset" operational
TRX
alarm istonot
KPI-
FSMF
Collecting
disabled
_x000D_
Impact
handled
degradation
information
-Interface
-Customer
-Test -to 2DSP
state_x000D_
by KPI
End-User:
requirements: reserved
for
theHO,
GTS._x000D_
istovisible
effects:
effects: RLF
for 125._x000D_
customer_x000D_
No none_x000D_
tofault
the
None_x000D_
None GSM,
HO, ERABs 4DSP and
customer/operator._x000D_ reserved comparisonfor LTEw/ 2x1800
the same _x000D_
N/A Summary
collected
_x000D_
Impact
_x000D_
Description
-Customer
-Test ofeffects:
to before ofthe
End-User:
requirements: theoriginal
upgrade_x000D_
temp problem:_x000D_
correction:_x000D_
Site
None on loss of service on affected RFs_x000D_
air_x000D_
Description
_x000D_
SW
Impact
Dependency
CNI-35232
-Test is requirements:
not allowing
to Operator:ofon
was the fault:_x000D_
more
configuration:
reverted DSS
many than
is(9)not20Mhz
N/A_x000D_
None_x000D_ difference
working_x000D_
FSMR3
WCDMA boards
cells and onletUHFC
only_x000D_ at least RRH_x000D_
3 have DSS
Wrong
Description
How
_x000D_
_x000D_
Impact
enabled. end order user/operator
toConnect ofofthe
Operator: allocating
fault:_x000D_
them AlarmscouldUlComp
through 7116detect cells._x000D_
with
radios the inproblem:_x000D_
fault 'Rx signal level failure' raised on
threes
N/A Summary
LTE3105
After
How
Workaround:
Faulty
_x000D_ end
RF
RF AHEGA_x000D_ hot
component of remove/insert
the
user/operator
works original
improperly,
None_x000D_ and version: problem:_x000D_
could WCDMA
whatdetect leads the
operation
Mctrl_x000D_
WCDMA
FSMr3 to
problem:_x000D_
DSP
U-Boot failure cells
R2 ofCodec/Decoder
versions RLF-triggered
not recovered
starting with HO.
(disabled
_x000D_ RLF-
SBTS
HO
state)
Try
_x000D_ to
Dependency
_x000D_ Plandue
failure
without
perform
PS_LFS_BT_2019_01_0002 provisioning
any
on such
toconfiguration:
RRC
alarm_x000D_ for auto
commissioning
Connection VPN
None_x000D_
until onfeature
Reconfiguration
SBTS._x000D_ failed with
PS_LFS_BT_2019_02_0002._x000D_ IPSec
w/ fullConfig
usage._x000D_
_x000D_
outage_x000D_
Description
Faulty
Workaround:
_x000D_ component ofNone
the correction:_x000D_
first delivered in(e.g. release, CD):
available._x000D_ CD):_x000D_
Legacy_x000D_
N/A Summary
Description
_x000D_
Faulty
Sync GTS component of
&oftheBCFtheoriginal
SBTS18SP_ENB_0000_000377_000042_x000D_ fault:_x000D_
and
information problem:_x000D_
version:
first delivered DCS_x000D_
properly._x000D_
in(e.g. release, CD): see above_x000D_
Invalid
Dependency
Description
BTSSM
How
Impact
_x000D_
_x000D_ end antenna
todoes
user/operator
ofon
End-User: not
the pipe index
configuration:_x000D_
allow
fault:_x000D_
Call
correction: to
could mapping
continue
service detect
_x000D_ causing
with
the the problem:
degradation_x000D_ invalid
configuration
Plan dapd power
failure_x000D_
due to thereading which
in
No
Impact
Faulty
In effect
Max.Total.Bandwidth
_x000D_ fault
general
Corrected
Risk analysis _x000D_
tois
component raised.
End-User:
theof problem
Operator:_x000D_
handling the LTE
first of limitation_x000D_
cell
calls could
delivered
happens
not beId_x000D_
possible
correction:n/a_x000D_
subscription marked
independently
in(e.g. onrelease,
failedas routable
on
cells_x000D_
CD): when a channel
configuration
N/A_x000D_ if at least
N/A leads
Summary
marked
_x000D_
Description
Impact
LTE1617
Unexpected
Correction totoas incorrect
ofeffects:
the
criticaltheoriginal
ofAlarm
enabled.
Operator: VSWR problem:_x000D_
reading
(CHANNEL_M::preventingCellSetup)
fault:_x000D_
But beand
KPIit Degradation_x000D_
n/a_x000D_
seen._x000D_ would observedantennaLineSwitchedOff
"better" if lte3105 alarm._x000D_
is not enabled and/or
UdpReport
routable._x000D_
Dependency
TRSW
_x000D_
ifImpact
Risk the analysis
-Interface build isfunctionality
configuration
to End-User:
Operator:
effects:on
used
of the on
n/a_x000D_noeNB
Cell doesn't
configuration:_x000D_
for both
call
correction:
down.w/onadded work
several
cell
Problems anddue
down_x000D_
Low_x000D_ cells toconfigured._x000D_
modified
with incorrect ipsec
fetching handling
objectsof
snapshot._x000D_ is subscription
not properly
IDs
_x000D_
UHFC
How from
handled._x000D_
Workaround:
Description
-Customer
Analysis end RRH different
user/operator
ofeffects:
of
the clients_x000D_
connected._x000D_
None_x000D_
the correction
fault:_x000D_
n/a_x000D_ could riskdetect
to the the customerproblem:_x000D_ / end-user_x000D_
N/A _x000D_
Summary
The
Impact
Faulty
-Test lotproblem
Dependency
Workaround:
ACorrection component
to ofeffects:_x000D_
requirements:
of BTS the
Operator:
SWcan
on original
be
configuration:_x000D_
N/A_x000D_
WD and cell
n/a problem:_x000D_
detected
version:
is
failure with
down_x000D_
can befake
CPLANE seenVSRW - UEC,
in syslog alarm being
FL18A_x000D_
before raised even
spurious BTS
How
The
_x000D_
Dependency
though
Description
SBTS scf
end
-Interface
reset._x000D_ with update
thereuser/operator
ofis
mixed on
effects: therule
no syntax
configuration:
power
Obsai
correction:
None_x000D_ could
/ on parser
CPRI detect
second RFdon't
none_x000D_
_x000D_ the support
problem:_x000D_
antenna._x000D_
module float number._x000D_
configuration._x000D_
_x000D_
Enable
In Faulty
Workaround:
Faulty
Description
-Customer component
TxMeasurements
DSP,componentDecoder ofnone_x000D_
thewill
effects: and
first version:
clear and
the UdpReports;
delivered
correction:_x000D_
None_x000D_ n/a_x000D_
memory
in(e.g. section release, faults 103 n/a_x000D_
allocated
CD): or 7116
for a new can be codevisible
block
N/A How
Summary
_x000D_
Faulty
Impact
Added
before Rxend
Description
or -Test toisuser/operator
signal
component of
end
requirements:
itcondition of
sent the
power
the
user original
for fault:_x000D_
thatand no
processing,
N/A. could
3Gproblem:
:alarms._x000D_
version:
premits
correction:_x000D_ detectTAS
calls_x000D_
creation
This _x000D_
the
is problem:_x000D_
SBTS17A_x000D_
ofdoneCARRIERS_BLOCK_TASK
to ensure that the allocated even if
Upgrade
TRX
Invalid
_x000D_
Faulty
Description
Impact
The are
start going
antennaBTS
component
tosection of to
End-User:
CARRIERS_READY_FOR_SETUP_TASK
memory address inpipe
the some
BL-RSL.after
offirst version
indexdelivered
correction:_x000D_
does Call
thenot mapping
Drop
contain
nvrd was will
&plan fail._x000D_
in(e.g.activation.
causing
accessibility
data
moved release,
from back So
invalid
toCD):itTRX's
issues_x000D_
iswhen dapd
ongoing_x000D_
the wasold are
n/a_x000D_
power notreading
previously
location in working
starting which
with
_x000D_
state
Faulty
in
Description
effect
allocate
Impact
Risk
used._x000D_ and
componentcalls
_x000D_
tocells
analysis ofof
operator
PS_LFS_BT_2019_02_0003._x000D_ ofare
the the
the :not 3Gpossible._x000D_
fault:_x000D_
first same delivered
KPIs
correction:ulcomp are in(e.g.
grouprelease,
down_x000D_
safe_x000D_ one afterCD): the legacy_x000D_
other, not mixing
N/A Description
_x000D_
Summary
leads
Wrong
them_x000D_
Impact
Correction ofeffects:_x000D_
tosubscription
toincorrect ofthe
Operator:
End-User: theoriginal
fault:_x000D_
VSWR ID
KPI problem:_x000D_
mecanism
reading and
none_x000D_
decrease_x000D_ created antennaLineSwitchedOff
several TxMeasurements alarm._x000D_
MOs and
Description
Remove
Impact
_x000D_
UdpReport
User
Workaround:
-Interface
Risk can't tounnecessary
analysis ofSite
End-User:
activate
MO
effects: the
of with
the fault:
the
Reset
N/A_x000D_ LTE
_x000D_
parameter
none_x000D_
BTS/ RF
correction: L2 Asserts_x000D_
SW_x000D_
correction:n/a_x000D_ "identifier"
module
No risks._x000D_ equal 1_x000D_
reset_x000D_
TRX
_x000D_
Dependency
Workaround
Impact
-Customer
Correction
Risk Reset
analysis request
to Operator: :on
effects:_x000D_
effects: the from
configuration:_x000D_
ofdisable SW
_x000D_ BSC not
LTE1617_x000D_
does
correction:
n/a_x000D_ was not handled
allow
n:a_x000D_ up to 55Mhz completelydifference by GTS._x000D_
between the 2
N/A BTS_RESET_REQ
How
Summary
The
Dependency
_x000D_
Description
carriers
Impact
-Test
There end
problem
Correction
-Interface toon user/operator
ofaeffects:_x000D_
ofthe
Operator:
requirements:_x000D_
should effects:occured
on
UHFC
be original
theconfiguration:
no for TRX
could
configuration:_x000D_
on problem:_x000D_
correction:_x000D_
plan
1900
duplicate
n/a_x000D_ FHEA from
detect
fails_x000D_
RRH_x000D_ BSC
NO_x000D_
variant
packets the areproblem:_x000D_
due
sent notto the
since handledfact ofinbeing
memory TRXSC
is clean a MEDUSAbefore
states._x000D_
LTE
SINR_PUCCH_MAX
RRH._x000D_
Description
Improved
FT L2 Assert
None._x000D_
_x000D_
using._x000D_
-Interface
-Customer routing
of the
effects:
effects: canmanagement
be(M8005C91)
correction:
none_x000D_triggered
n/a_x000D_ upon
n/a_x000D_
logic increase
toinvalid
take by ueIndex
~15db_x000D_ _x000D_
"preventingCellSetup" into
_x000D_
Faulty
-Interface
-Customer
-Test component
consideration_x000D_
Workaround: effects:
requirements: none_x000D_
effects: and n/aversion: BTSMED
None._x000D_
configuraiton working_x000D_ SWM_x000D_
Description
How
Faulty
_x000D_
Dependency
-Customer
Risk end
-Testanalysis user/operator
component
requirements: howon
effects:
of the problem
configuration:
and could
can
PRversion:
None._x000D_
correction: detect
be
configuration detected:_x000D_
_x000D_ theofproblem:_x000D_
MED28.02.R18A_x000D_
Draco_x000D_
will solved._x000D_
No risk correction_x000D_
Fault
SINR_PUCCH_MAX
_x000D_
Faulty
NA_x000D_
Risk
Description
-Test
Correction6150
component
analysis
requirements: isofseen
of
the the
effects:_x000D_ and
first counter
payload
delivered
correction:_x000D_
correction:_x000D_
None._x000D_ increase
reduces
in(e.g._x000D_ to zero.CD):
release, Connectivity
FL00_x000D_ ping test
passed.
_x000D_
Faulty
Analysis
Align
Correction
Impact
-Interfacewith to_x000D_
component
ofEnd-User:_x000D_
BPF1
is
the done first
correction delivered
Multiband.Max.Total.Bandwidth=
effects:_x000D_ in order risk
to send in(e.g.
to the tocustomer
TRSWrelease, CD):
configuration N/A._x000D_
/ end-user_x000D_
60,2;65,25 for both added and
_x000D_
Description
Impact
Faulty
Correction component
toipsec of the
End-User:
Multiband.Max.Rx.Total.Bandwidth=
modified
MED27.08.R09E_x000D_
KPI Degradation_x000D_
no_x000D_ effects:_x000D_
objects fault:_x000D_
and none_x000D_
version:
in _x000D_
one step/call. 60,2;65,25
Currently_x000D_ it is done in 2 steps._x000D_
SINR
Impact
_x000D_
GTS_x000D_
Dependency
-Interface
-Customer istowronglyEnd-User: calculated
on configuration_x000D_
Operator:_x000D_
effects:_x000D_
effects:_x000D_ Poor signal in case on of cell fully allocated PRB for F1
edges_x000D_
users_x000D_
Impact
_x000D_
N/A_x000D_
Risk to Operator:
analysis
KPI Degradation_x000D_
no_x000D_
-Customer End-User: of the BTSMED
effects:_x000D_ correction:
call drop_x000D_ upgrade
n/a_x000D_
risky_x000D_ fails_x000D_
N/A Summary of the original problem:_x000D_
Handovers to equivalent PLMNs are not working as specified and HO is
blocked for _x000D_
N/A _x000D_ of the original problem: pm files are partly loaded in webem if they
Summary
Howpresent
are end user/operatorin multiple zip could filesdetect in thethe snapshot_x000D_
problem: some handovers are
blocked because of the fault._x000D_
_x000D_
N/A _x000D_
How
Summary end user/operator
of the originalcould problem:_x000D_
detect the problem: load snapshot and look at
Description
counters_x000D_
LTE cells are ofdown.
the fault: 7114 check alarm against
with Fault equivalent
ID :- 6253 PLMNs 'Celland configuration
forbidden TAs data
was implemented
_x000D_
distribution failed'_x000D_ with an error._x000D_
N/A Descriptionofofthe
_x000D_
Summary theoriginal
fault: recursive
problem:_x000D_ zip reader not concatenating result_x000D_
_x000D_
How
Counter
Dependencyend M8006C264
user/operator
on configuration: wascould notdetectincremented
Operator the problem:
must if RLF
be usingalarming
triggered appears_x000D_
X2 handover
equivalent PLMN and
Dependency
_x000D_
failed
forbidden withTA tx2overall-expiry._x000D_
on configuration: snapshot that contains multiple zips containing
lists._x000D_
N/A pm files_x000D_
Description
_x000D_
Summary ofofthe theoriginal
fault:_x000D_ problem:_x000D_
Releasing
How
Many
Faultyend
_x000D_ SBTS user/operator
componentpshavingnodeand during
TRX could
degradation
version:celldetectdelete
UEC_x000D_ the
isalarm,
not
problem:_x000D_
atomic
whichin is L2considering
code. Issue caused
occurs by
when
the
Higher
internal
_x000D_
Faulty cell LTE_5092g
setup
component faultycomes 1836;
and KPI._x000D_
after
afterfirst
version: isPM_x000D_
alarm
phasecancelled and before wesecond
still seephase 1836 of in Active
ps node
N/A releasing._x000D_
_x000D_
status
Summary
Faulty from ofsnapshot._x000D_
component the original problem:in(e.g.
first delivered BTS MD upgrade
release, CD):causes_x000D_
n/a_x000D_
Description
_x000D_
validation
Faulty component errorof the occursfault:_x000D_
for MRBTS
first delivered with version
in(e.g. release,SBTS18A CD): ADMIN mMP0.1 123 (during
Dependency
How
loading
In case
Impact end
SBTS18SP_x000D_to of
ofuser/operator
the
tx2overall
on
End-User: Plan configuration:
from timercould
Handover NetAct)
expirydetect
n/a_x000D_
isLocalduring
not the validation
problem:_x000D_
RLF triggered
triggered to works
particular handover,
properly.
cells with During
counters
2 PLMNs for
N/A Summary
abnormal
Unexpected
validation
from whicherab
_x000D_ ofone
the the
fault isoriginal
MRBTS
release
1836
forbidden problem:_x000D_
israised_x000D_
werenot in treated
not HRR incremented._x000D_
as AirScale
a result call butdrops._x000D_
is treated as
Low
_x000D_
Impact
Faulty CSSR
FSMF_x000D_ component on 3G after
to End-User: and upgraden/a_x000D_
none_x000D_
version: to SRAN18 2.1_x000D_
Dependency
Description
_x000D_
Impact to Operator: ofon theconfiguration:
fault:_x000D_
HO failure rate No._x000D_increase & CDR increase. Further PLMN
N/A Summary
_x000D_
Fault
How
versus
Impact
Faulty end
raising of the
to user/operator
component
primaryOperator: original
unexpectedly
PLMN first
PMis problem:_x000D_
could
notdue
delivered
file detect
download
working toin(e.g.
code the
asisnotproblem:
problem:_x000D_
aligned
release,
expected._x000D_
not Perform
working_x000D_
CD): with thethe
n/a_x000D_ new validation
fault with
BTS scfconfiguration
diagram._x000D_
the
BBMODs
_x000D_
Faulty file._x000D_
connected
component error
and appearssides
toversion:
random UEC(not FL16_x000D_
enough
in rack. Lack HW for LCR alarmtoondeploy
of resources some
sites)
_x000D_
cells_x000D_
Workaround:
Impact just afternone_x000D_
to End-User: upgrade
There call
is no from SBTS 18A
isworkaround
failed_x000D_ forMP0.1 to MP0.2 . Problem
the issue._x000D_
N/A Summary
Dependency
Description
_x000D_
disappeared
Faulty component ofofthe after
on original
theconfiguration:
fault:
site problem:_x000D_
first reset._x000D_
Validation
delivered n/a_x000D_
logic issues
in(e.g. release,when CD):engine parses the rule
FL16/SRAN16_x000D_
High ULtopacket
"SMOD((every
Description
_x000D_
Impact of the
Operator: loss in case
SMOD_R(configDN
fault:_x000D_
correction:
kpi
correction bad, of lte SuperCell
the=logic
:concatenate
fix cells external
are with
down_x000D_
results
between HighSpeed
SMOD.distname
inPLMN
recursive & TAs zip andreader
to allow
configuration_x000D_
Faulty
SMOD_R/SMOD_BP_R.unitType
Incorrectly
How end
service_x000D_
_x000D_
Impact
proper component
to user/operator
HO created
End-User:
_x000D_ and
cablnks
none version:
could , between
detect
counter n/a_x000D_
inisthe
range
modules
notproblem:
'FSM'|'FSI')
and No
incremented cabinetall exist))
cells
duehavewill
properly_x000D_ to use
beportMode
of
N/A _x000D_
Summary
defined"_x000D_
nodeId
OnAir_x000D_
Workaround: of the
instead oforiginal
slot forproblem:
none_x000D_ mapping.An alarm behavior
Legacy 7107 withbecame fault ID unsuitable
'6297" raised withat
How
the
Impact
Risk sites
Faulty
Risk end
introduction
_x000D_ towhere
analysis user/operator
component
analysis ofof
Operator: of were
manual
thefirst
the activated
ERAB could
domain
correction:
delivereddrop
correction:_x000D_ detect
Inter
id setting
n/a_x000D_
KPI in(e.g.eNB
the release,
does problem:_x000D_
DL
notCA
possibility feature_x000D_
properlyCD):on n/a_x000D_
REL4._x000D_
register all
_x000D_
Dependency
Description
High UL packet
drops_x000D_
Correction
Correction ofon theloss
configuration:
effects:_x000D_
effects: fault:_x000D_
visibleare
correction:_x000D_
results in KPIs_x000D_
n/a_x000D_
concatenated_x000D_
N/A How
Summary
Dependency
_x000D_
During
Execute
Impact
In some end
-Interface to user/operator
of
releasingthe
UPlaneDeployment
ontarget
End-User:
cases
effects: original
configuration:
of could
allnone_x000D_
PS
pmcell problem:_x000D_
node
timestampsdetect
forcalculation
in
handoveronethe
REL4_x000D_ time
are problem:
wrong
will be mode
during
present_x000D_ Anwas
cell
selected alarm set7107
delete._x000D_ for FBBC
faster,_x000D_ with faultport3ID
'6297"
SRAN
_x000D_
because
Description
Workaround:
Faulty
there could
-Customer raised
site iseffects:
CABLNK_L
component of
begetting
atthethefault:_x000D_
none_x000D_
more andsites
hanged.
was where
version:
customer
handovers Fault were
missing._x000D_
can 6150
PDL_x000D_
tosee LTE activated
is seenInter
allcells,_x000D_
counters andand eNB
payload DL CA
timestamps reduces to in
present
feature_x000D_
zero_x000D_
Faulty
_x000D_
MAC
Impact
Risk PS component
toissue:_x000D_
analysis
snapshot_x000D_
handovers Operator:
canoflead theand noto version:
correction:
proper
different MOAM_x000D_
alarming
safe_x000D_
cells._x000D_ and clearance_x000D_
N/A _x000D_
Summary
Dependency
candidateSubcellId
Description
Faulty
If there
-Test
Correction willofeffects:_x000D_
component
requirements: of
bethe
on the
anyoriginal
configuration:
was problem:
not
correction:_x000D_
first
impact delivered
snapshot onset All HSUPA
toin(e.g.
invalid
network/KPIs
with configurations
multiple set
but
release,zips upCD):
it still
will failure_x000D_
in
with
berange
containing rel3 so
n/a_x000D_
positive. when
pm it was FBBC
files used is by
Description
_x000D_
Faulty
used._x000D_
UL PHY
Workaround:
Added
-Interface component how
incrementation theproblem
aseffects:_x000D_
valid
ofn/a_x000D_parameter._x000D_
fault:
first delivered
Wrong
of can
counters be GB detected:_x000D_
in(e.g.
configuration
release, CD):
for abnormal shows
erab n/a_x000D_
issue in
release due reporting
to overall error
Fault
_x000D_
in
timer
Impact
-Customer 6150
PBCR_x000D_
expiry is
to End-User: seen and
during
effects:_x000D_ RLF payload
triggeredreduces
none_x000D_ to zero. Connectivity ping test
handovers._x000D_
N/A passed.
How
Summary
-Testend
Faulty
ULPHY
_x000D_
Description
Impact _x000D_
user/operator
ofofthe
component
to issue:_x000D_
End-User:
requirements: theoriginal
and could
problem:_x000D_
3Gversion:
correction:_x000D_
call detect
success the
DCS_x000D_rateproblem:_x000D_
impact_x000D_
_x000D_
Alarm
Sudden
Dependency
Risk- not
Impact
Code from
analysis
vsto loss
sending
fault different
on
Operator: of
of HSUPA MRBTS in LCG_x000D_
PhyPuschReceiveGroupedRespU
configuration:
diagram
the vaidation
correction:_x000D_ shows
corrected_x000D_ ToP inunder
fails_x000D_ use_x000D_ MRBTS-1 to MACin NetAct. PS when _x000D_
_x000D_
Faulty
servingCell
Description
Impact
Correction component was
to Operator:of safe_x000D_
is thenot fault
first
0 and
KPI delivered
: degradation_x000D_
LTE there L2 Assert
were
in(e.g.delayed can
release,
be UEs triggered
CD): reported
n/a_x000D_
uponbyinvalid MAC ueIndex
PS.
N/A Description
How
Summary
Delayed
Faulty
_x000D_
Risk end
Workaround: user/operator
ofeffects:_x000D_
component
analysis
Correction UEs ofthe the
were original
n/a_x000D_
of the fault:
and
wrongly could
_x000D_
problem:_x000D_
version:
correction: detect
calculated n/a_x000D_
Safe_x000D_ theinproblem:_x000D_
internal processing when waiting for
restart
Wrong
GRM
all
_x000D_ BTSMED
doesn't
information
Workaround:_x000D_
Impact
Correction
-Interface to timing
End-User: calculation
inform
and orN/A_x000D_
effects:_x000D_
effects: switchover_x000D_
new
triggering
no for
serviceHSUPA DIO offset
resource
stepinofcase
of available_x000D_
next status of DSS
processing to LRM configuration_x000D_
after ESM
(decoder) was done
reset_x000D_
_x000D_
too
Faulty
Dependency
fast.
Description
Set
-Interface
domain
-Customer component
In effects:_x000D_
theidon
of 1end
the
effects: configuration
on first
the
correction:
left
better delivered
results
core and
LTE5092g N/A_x000D_
were
PDL in(e.g.
domain incomplete
rule release,
id 2 on and
updated_x000D_
values_x000D_ CD):whole
right core_x000D_ processing was
N/A Description
How
Summary
Afterend
dropped
_x000D_
Impact
-Test
-Customer ESM user/operator
ofeffects:_x000D_
towithout ofthe
reset,
Operator:
requirements: theoriginal
SBTS18A_ENB_1000_000623_000071_x000D_ fault:_x000D_
response
GRM N/Acould
Cell problem:
only
is to detect
informs
MAC
down_x000D_ _x000D_
the
PS._x000D_
LRM problem:_x000D_
of new HSUPA resource status if
Call
MO
Attach
_x000D_
Faulty
HsRach
Risk dropped
of
Description
-Test CONF_REF
toservice
WCDMA
component
analysis
requirements: ofobserved
of
the cell
decode with
not possible
is correction:_x000D_
the and
degraded_x000D_
version:
correction: bad
failed call
LTE during
n/a_x000D_ when
quality
L2_x000D_ BTSMED
DSS
during is enabled
beam
start, switching_x000D_
it &causes
RF is distname
connectedof
runtime
with
_x000D_
When Long
Dependency
Impact
Workaround:
Analysis toMO
creating Fibers_x000D_
of cannot
End-User:
theon
sitecablnks be
correction CAconverted._x000D_
configuration:
reset_x000D_ does
search risknot SuperCell_x000D_
to
forthe work
matching , lower
customer throughput_x000D_
concentrators
/ end-user_x000D_ on cabinet and
N/A _x000D_
How
Summary
Faulty
Dependency
smod/bbmodend
Correction user/operator
ofeffects:_x000D_
component the
on original
willconfiguration:
nofirst
longer could
problem:
delivered rely detectOnly
on M5008C50
in(e.g. the
seen
nodeId problem:_x000D_
release, counter
in Rel3
but anddoes
onCD):_x000D_ not update
Rel4_x000D_
slotNr_x000D_
Dependency
Description
correctly
Call dropped
Impact
18A_x000D_
_x000D_
Faulty
-Interface toaccording ofon
Operator:
component the
observed
configuration:
effects:_x000D_ fault:_x000D_
toToP configured
correction:
and with
unusable,
version:_x000D_bad NA_x000D_
_x000D_ HS-FACH
callCAquality_x000D_
inter baseband
site does not resources_x000D_
work_x000D_
[DCS]
_x000D_
Faulty
Risk
ULPHY
deduction Wrong
component
analysis
-Customer - FL18SP,
FBBC timing
of the and
port3
effects:_x000D_ equation
FL18A, version:
correction:
mode FL19, was
basedsmall. in onuse.
CP_GRM_x000D_
trunk_x000D_ [WTS]issue
potential
cablink_r_x000D_ Constant
with existingapplied hwf for RTT
as new
N/A Summary
calculation
Description
How
-Testend
Workaround:
Impact
_x000D_
Faulty
changes ofwas
component
toalso ofthe
user/operator
the
End-User:_x000D_
requirements: original
aligned
fault:
none_x000D_
include andbpf problem:_x000D_
could
_x000D_
to
version:wrongly detect
changes_x000D_ calculated
the problem:
BTSMED_x000D_ value Unexpected
by DCS, sovalue restoring
for
correct
notification
M5008C50
Call
LTE
Faulty
_x000D_ drop
resources
Correction
Risk value
iseffects:._x000D_
component
analysis about
counter
observed
required
ofnotthechanges
after
first after
revert changing
available._x000D_
delivered
correction: in
deleting
of
CpriForwardingOffsets
this the
in(e.g.constant._x000D_
andcommissioned
N/A_x000D_ recreating
release, CD):RF MO minHsRachResSteps
Hop was
Legacy
ULPHY sector_x000D_
not sent to
_x000D_
Fl18SP_x000D_ to
subscriber_x000D_
1_x000D_
_x000D_
Fault
-Interface
Description
Correctionfirst introduced
effects:._x000D_
effects:
of the correction: : SRAN18SP_x000D_
N/A_x000D_ PBCR error will be reported properly and ToP
N/A Summary
_x000D_
How
Impact
will beend
Dependency
-Interface
-Customer reportedof the
to user/operator
Operator:_x000D_
End-User:
on as
effects: original
effects:._x000D_ Nocould
configuration:
N/A_x000D_
unusable.
high problem:_x000D_
HSUPA
packet detect
DSS
_x000D_ calls
loss the
enabled problem:
_x000D_
rate, + long
VOLTE Delete
fibers
call and Recreate a
quality
RF
Fault module
Dependency
Description
Sector
_x000D_
Impact with
(Obsai/CPRI)_x000D_
6150
impacted_x000D_
-Customer
-Test configuring
Rf
to End-User:
requirements:.isofon the
Hopping
configuration:
visible.
effects: fault: failed
none_x000D_
LTE
N/A_x000D_ RATwith
TCOM/LRM
Enabled._x000D_ is not AHPMDA.
n/a_x000D_ does
working. notAfter
include
Traffic adding notthe
isclusters 2G-900
that are (3TRX
available._x000D_ full of
HS-RACH
_x000D_
per
Impact
Risk
-Test cell), tothe
analysis CFs fault
Operator:
requirements: ofso the number
when N/A selection
Sudden
correction: 1900 loss RF
No ofisrisk_x000D_
Module
triggered
HSUPA_x000D_ configuring
due to minHsRachResSteps
failed appears and hits ==
N/A Summary
Faulty
1
Description
theLRMU900
_x000D_
Impact
Correction
Workaround: ofeffects:
component
does ofthe
to cells_x000D_
not
Operator: theoriginal
_x000D_seefault:_x000D_
and operator
None
bad problem:_x000D_
theversion:
cluster
KPI oncannot full
UOAM
DCS ofmap
throughput HS-RACH
11.0.2_x000D_
71173_x000D_
correct
& quality CFs,
alarms leading
(packet to correct to an HS-RACH
retrans)_x000D_
During
CF
MAL
_x000D_ LTEreset._x000D_
RAT
pre-reservation._x000D_
frequencies(
Workaround:
MO/SBTS_x000D_
SBTS Site BTS reset
RF parameter
Hopping
reset_x000D_ change from
Frequencies) were ADMIN not being Fault correctly
1910 'RFupdated Module
filter
_x000D_
and
How
Faulty input
notified
end
Workaround: power
user/operator
component towards
Rollbackmissing'_x000D_
firstdsp tocould
causing
delivered
normal detect Callthe
in(e.g.
super dropproblem:
at RFCD):
release,
cell_x000D_ Hop
Fault sector_x000D_
1900 raised due to
n/a_x000D_
N/A _x000D_
Summary powerofresults
Dependency
less
Description
Workaround: ofthe
on original
theconfiguration:
restart in SBTS_x000D_
carrier problem:_x000D_
correction:_x000D_ creation
REL4_x000D_ rejection_x000D_
Siter
Dependency
_x000D_
How
Impact
Description
Remove
GRM crash
end after
user/operator
tounnecessary
informs on
End-User:
of the 12
HSUPA hours
ofconfiguration:
NoLTE
call could
WCDMA testing_x000D_
L2detect
drop_x000D_
correction:_x000D_ resource Theservice_x000D_
sector
Asserts_x000D_ the problem:_x000D_
status which
every time is deleted
ESM and recreated
resets_x000D_
_x000D_
Faulty
should
Description
Normal
MAC PS:_x000D_component
be BTS configured
ofoperations
the fault:
andasversion:
correction: RF
involving
RFmodule Hopping CP_LRM_x000D_
_x000D_ deactivation
configuring
enabled Sector._x000D_
offailed
carriers_x000D_ - like LTE RAT
N/A How
Summary
_x000D_
Risk
Set end
reset._x000D_
Impact
fix decode to user/operator
analysis oferror
cadidateSubcellId the
Operator: of theoriginal
in alarm
WCDMA
KPI tocould
problem:_x000D_
impact_x000D_
correction: handler
0xFF detect
cell not
for
_x000D_
andLow the
_x000D_
usableproblem:_x000D_
risk_x000D_
copy when DSSfrom
ServingCellId enabled tempUe & Longin Fiber
Loose
Fault
Faulty
Dependency
_x000D_
in
No 469
use_x000D_
Correction phase
component
risk_x000D_ and and
on
effects:RAC
AlgorithmData::copyParamsFromTempUe, time crash
configuration:
and
first
Low synchronization,
version:
deliveredwill happen_x000D_
risk_x000D_ _x000D_
GTS_x000D_
in(e.g. release,BSC set time is used
CD): instead
SBTS17A_x000D_
candidateCellId of NTPon ue
to invalid
time_x000D_
Description
_x000D_
Risk AHPMDA
analysis
-Interface
setup_x000D_ ofof
effects: the
configured
the fault:_x000D_
correction
Low correction: with: _x000D_
risk_x000D_ NBIOT
NA_x000D_ inband/Guardband LTE cell and normal
N/A _x000D_
Summary
Faulty
LTE
False
Description
cell
Workaround:
Subscribe
Impact
Correction
-Customer
Correction of
invalidVswr
component
toalong ofthe
End-User:
to the
withoriginal
indications
fault:_x000D_
first
GSM
CpriForwardingOffsets,
Disabling
effects:
effects:NA_x000D_
effects: problem:_x000D_
delivered
none_x000D_
_x000D_
Low DSS cellor
risk_x000D_ from
configuration_x000D_
in(e.g.
swappingRFSW and release,
usedthat
after
fiber totoCD):
trigger
short
change n/a_x000D_
fault reporting
multimode_x000D_
slave CpriPort to
How
Fault
-Testend
_x000D_
invalidVswr 1811
469
master._x000D_
-Interface
-Interface
ULPHY: user/operator
requirements: Baseband
RACFL
issue._x000D_
effects:
effects:NA_x000D_
Calculation error.
NA_x000D_
ESM
of bus
could
User configuration
reset
necessary detect
indexes thewere
internal problem:
was rejected
not
messages When
properly nowappears
NTP
balanced sync
properly afterbetween
happens
includes
after
upgrade_x000D_
Faulty
_x000D_
odd and
-Customer
-Customer
also BSC
Description
Impact delayed time
component
toeven Operator:
End-User:
ofUEs
effects: sync
numbers,
the and done version:
correction:_x000D_
effects:NA_x000D_No
from wrong
CallLTE
not incounter
there SBTS._x000D_
were
drops._x000D_
L2
the GTS
Asserts
first more
0_x000D_
value upon even
for
subcell._x000D_ number
M5008C50
invalid user
_x000D_
ueIndex_x000D_ indexes
N/A _x000D_
Summary
Dependency
compared
_x000D_
Risk
DCS
-Testanalysis
-Test Useof tonew
-requirements:NA
requirements: the
odd
onof theoriginal
equationNA problem:_x000D_
configuration:
numbercorrection: user
for DSS N/A_x000D_
indexes_x000D_
lowDIO - minor offset changes
which allows in codecompensation
that only affect for
How
NBIOT_FDD.inbandPRBIndexUL
Faulty
_x000D_ end
Description
notification to user/operator
component
Workaround:_x000D_
Impact
radio time
Risk analysis ofof the
Operator:_x000D_
about
delay fault:_x000D_
first
+chages
the revert could
delivered
the
correction:_x000D_ RTTdetect needs
in(e.g.
in CpriForwardingOffsets therelease,
calculation problem:
to beconstant
corrected
upgrade
CD): in when
n/a_x000D_
_x000D_ WTS fails_x000D_
PDL
to validation
align it with
_x000D_
is
-How
Calldone
Faulty
Dependency
Leap
Analysis
correct
Medium, drop
problem: the
second
component
DIO of correct
is observed
ULPHY the on
of
can BSC bebehavior
configuration:
and
correction
timing_x000D_correctionvalue
atversion:
avoided
RFrisk should
not
Hopping
is to
orn/a_x000D_
the
effects
impacting be updated
MOAM(Rumag)_x000D_
being to
customer have/ end-user_x000D_
sector_x000D_
mitigated
PUSCH the relation
correctly
before
processing Error
whichdisplayed
towards
correction is have on
will
N/A Description
Admin
Summary
_x000D_
IM._x000D_
ready_x000D_
Impact
Correction
impact ifin
tonbandPRBIndexUL=
ofeffects:
ofthe
End-User:
every the original
fault:_x000D_
uoam
SuperCell _x000D_problem:
will
PUSCH 6_x000D_
send Some SRANabout
notification
processing_x000D_ eNBsCpriForwardingOffsets
report wrong SW version
The
_x000D_
in RTPM
Faulty PCA
MO_x000D_
Description
Workaround:_x000D_
One
Risk of the
analysis
Correction Traffica
driver
component Carrier
ofof the isreporting_x000D_
the
effects:_x000D_ unable
first
and
correction:
will not
correction: to register
delivered
version:get _x000D_
created
N/A_x000D_ itself.
SS_RakeReceiver
in(e.g. results The
release, in communication
CD):
less version
SBTS18A with
and physical
148229_x000D_
coverage._x000D_ newer
How
Impact
fix
Lock end
releases_x000D_
_x000D_
Dependency
device
-Interface to user/operator
fails
reservation
And
Correction End-User:_x000D_
with
Unlock on
effects: error
configuration:
mecansim
the
effects:_x000D_ no could
-110._x000D_
sector
_x000D_
N/A_x000D_ to count detect
again to the
n/a_x000D_
properly
clear problem:
the
HS-FACH PDLresources_x000D_
issue._x000D_ validation passes
despite
Impacts
Faulty
_x000D_
Impact
-Interface
-Customer to the
ofOperator:
component the
wrong faultsetting_x000D_
effects:_x000D_
effects: to
first
Call end-user:
delivered
_x000D_
N/A_x000D_should working Some
in(e.g.SRAN release,
fine with eNBs CD):
good report
SBTS18SP
quality wrong _x000D_ SW version
2.2_x000D_
_x000D_
in
RiskRTPM
Impact
Faulty
Dependency
Description
One of
analysis
-Customer
-Test the Traffica
component
to End-User:
requirements: ofon
Carrier of
the thereporting_x000D_
configuration:
effects:_x000D_ and Possible
correction:
will version:
correction:
new
N/A not getUpdate
tests degradation
FCTJ,
n/a_x000D_
created
Low_x000D_
for FCTL
the
results
subsription MALofatservices_x000D_
inthe moment_x000D_
frequencies
for less coverage._x000D_
CpriForwardingOffsetstowards Dsp again MO
Description
Impact
_x000D_
Correction
on
are
-Testupdate
needed to Operator:_x000D_
of the fault:
End-User:
received
effects:_x000D_
requirements: byservicewrong
Bsc._x000D_ PDL rule applied_x000D_
stability_x000D_
_x000D_
Impacts
Faulty
-Interface
The
Workaround:
Impact toofOperator:
component
function thefor fault
effects:_x000D_
None_x000D_
decodingto
first
and operator:
delivered
version:
Unexpected Some
FB_x000D_
Cell Allocation in(e.g.
fault 1910 eNBs
release,
Bitmap report CD):
visible_x000D_ themselves
which providescorrectly
n/a_x000D_ us the to be
SBTS18SP
Impact
_x000D_
Dependency
updated
-Customer toMAL but
Operator:
on
effects:listsome other report
configuration:
stability
frequencies
M5008C50 KPI NBIOT
will themselves
down_x000D_
be
counter iswill
called used_x000D_ to be
again._x000D_
show WN18._x000D_
correct value even when
Change
Impact
Faulty
_x000D_
Workaround:
Description toinEnd-User:
component
minHsRachResSteps SOAM theBSTAT
of-N/A_x000D_ firstnone_x000D_ code that
isdelivered
correction:_x000D_
updated in(e.g. RPTM
to 1_x000D_ release,will get CD): thelegacy_x000D_
parameter for SW
N/A Summary of the original problem:_x000D_
Parameter Editor and relation error will be shown when users only un-activate
test in RF diagnostics test dialog. _x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
How IPSEC
Two end user/operator tunnels established could detect at the thesame problem:_x000D_
time after IPsec tunnel
Check relation error shown or not in Parameter Editor after do this test(when
switchover_x000D_
N/A users onlyof
_x000D_
Summary un-activate
the original test problem:_x000D_
in RF diagnostics test dialog)_x000D_
_x000D_
How
GTS end
crash user/operator
observed when could TRX detect deleted the problem:_x000D_
in a RF Hopping sector_x000D_
Description
_x000D_
S1 links doesn't of therecover fault:_x000D_ automatically after IPSEC tunnel
N/A switchover._x000D_
Summary
Description
Because inofcoding,
of
thethe original
problem:_x000D_
the data problem:_x000D_
between RF diagnostics test dialog and
-_x000D_
During
Parameter 2Gthe Calls implementation
Editor areisplaced shared._x000D_ atofRF maxTotalBandwidth
sector. Traffic tracevalidation is startedrule andit checked
was
Description
Calls
believed
_x000D_ are that workingofonlythe fine._x000D_
fault:_x000D_
one band is possible per RX/TX_PU_L. In case of multiband
N/A -Missing
RX/TXes
Summary
FaultyLock subscription
componentmultiple
of
and thedelete original
bands
first inTRX DEMproblem:
were
delivered with forthus
traffic
removal
in_x000D_
validated
(e.g. trace of ongoing_x000D_
IPSEC
release, as one, CD):objects_x000D_
which led to false
SBTS18A_x000D_
-_x000D_
negatives_x000D_
BTS_OMU_STARTED
GTS crash is observed._x000D_ message not sent to BSC. Hence GSM Carriers are
_x000D_
down
Impactand
Dependency calls onare
to End-User:_x000D_ not possible._x000D_
configuration: n/a_x000D_
N/A How
_x000D_
How
Parameter end
end user/operator
user/operator
Editor
Summary of the original problem: _x000D_ and could
could
relation detect
detect
error the
willthebe problem:_x000D_
problem:_x000D_
shown after do this test._x000D_
-Faulty
If
Description
multiple
_x000D_
BPF2 Cells
component
definition cells
are of the moved
using
forfault:
and the
support toversion:
_x000D_
'Integrated
same band
DEMtofail
TX frequency RAN'
_x000D_ validation
range dueistonot with
GTS Crash_x000D_
correct_x000D_
_x000D_
"CarrierBandwidthNotSupportedByRadio",
After
Impact
_x000D_ site to reset
Operator: GTS is
KPIs not sending
drop_x000D_ BTS_OMU_STARTED it's probably this._x000D_
to BSC because
_x000D_
SCTP
Faulty
Description
How end association
component how problem
user/operator is
first quickdelivered
could anddetect
can beEv_OmusigUp
in(e.g.
detected_x000D_
therelease, come
problem:_x000D_ CD):before DEM_x000D_
N/A Description
Ev_BscGwInitDone
Workaround:
_x000D_
GTS
Summary
SW update crashofprint ofthe
to the
None_x000D_
foundfault:_x000D_
original
SBTS18A in the event
inproblem:_x000D_
logs
SW and
with queueGTS thread.Hence
AHEGA is down
RF modules Ev_OmusigUp
configured in event
at webadmin_x000D_
All
processed
carriers
Impact
_x000D_
Speech
BAND1._x000D_ toQualityfirst
on RX/TX
End-User: and
Tests BcfScare
LTE(Mobile treated
not moved
cells willas
Mobile beifCalls)
to
they St_WaitForOmuSig
were
in 2Gsingle
available._x000D_ lead to band.badand They
MOS thisare event
values all :
validated
become
Description
_x000D_ unconsumed._x000D_
together
of the fault when:_x000D_ checking max total bandwidth, as opposed to
correction:_x000D_
N/A _x000D_
Add
Impact
Traffic
checking
With
Summary an Trace
WB-AMR
Description to
warning
once
Operator:
ofhow is per
the ongoing
themessage(Relation
band._x000D_
original S1 links
values
problem on the now
problem:_x000D_
are
can TRX
OK_x000D_
be ill error
recover
and will
detected:_x000D_ refreshautomatically
be shown timer isif running
test
after is IPSEC
disabled
every tunnel 5 and
Dependency
history
switchover._x000D_
minutes
_x000D_
For
WNCEL NB-AMR test(i.e
are data on
every
all
, configuration:
exists)
5
MOS-Values
down. minutes if
After
Alarm - 1807 Invalid frequency channel for the BTS HW will be RFREQ_A
reset
are _x000D_
traffic NOK.
the trace
existed
SBTS, details
_x000D_ in
it IMneeds
could and un-activate
to
recover be fetched
the test
by inGTS
RF
NA_x000D_
_x000D_
from
DependencyDSP and
diagnostics
problem_x000D_
visible._x000D_ onpopulated
test configuration:_x000D_
dialog._x000D_ at admin for the traffic trace enabled TRX)._x000D_
N/A Workaround:
TRX
Only
How
_x000D_
Summary
WCDMA is
affects
end deletedof multiband
Site
user/operator
cells the from
are reset._x000D_
original BSC
down._x000D_ RX/TXes_x000D_
could without
problem:_x000D_
detect stopping traffic trace from ADMIN for the
the problem:_x000D_
Faulty
TRX
_x000D_
Risk
Impacts
How
After
_x000D_ end component
leading
analysis
activate to
ofthe
touser/operator
MoS_x000D_
the the and
GTS
feature version:
correction: crash._x000D_
could
SR002047 _x000D_
No
detect risk_x000D_
the
on the problem:_x000D_
module AHEGB, there are ghost
Description
Impact
GTS
_x000D_
fibers
Rapid and
Description and to SBTS18A_ENB_1000_001152_000000_x000D_
site End-User:
ghostof
of the
reset thesmod correction:_x000D_
WCDMA
scenario_x000D_ which appears
fault:_x000D_ cells areon notWeb accessible.
EM._x000D_ _x000D_
N/A fixed
_x000D_
Dependency
Analysis
Summary
Description
BPF2 subscription
ofofthe
definition oftheon
the configuration:
in
correction
original
for DEMproblem:_x000D_
fault:_x000D_
support forTXremoval
risk None_x000D_
tofrequency
the customer of IPSEC objects_x000D_
range- Interface
is effects: No impact
not correct_x000D_
_x000D_
Impact
Faulty
Description
How
DSP
Codec
_x000D_ end component
Fatal to
info Operator:_x000D_
user/operator
error/
of
shared the first
crash.
fault:
to delivered
could
EncoderCrash
rapid site
detect
at
form in:_x000D_
core
reset the
AbisFLfrom
scenario_x000D_
problem:_x000D_
ULPHY._x000D_
was not the highest and hence
WCDMA
SBTS18A_ENB_1000_001152_000000_x000D_
Description
Risk
After
_x000D_
vtcTskMgr
lower
Dependency analysis
activate
AMR cells ifon
and
Codec problem
thedon´t
of the
ipsec
feature
used startup
hadbased
correction:
configuration:_x000D_ SR002047
active
being in
on AHEGBcertain
n/a_x000D_
access
lower_x000D_ on the due
configuration
to "Invalid
to /ffs/fs2
module path : frequency
NA_x000D_
AHEGB_x000D_
which blocked channel for
the site
N/A the BTS
Correction
reset_x000D_
_x000D_
How
Summary end HW" thealarm_x000D_
effects:_x000D_
user/operator
of
AHEGA RF modules are affected._x000D_ original could
problem: detect PIC the configuration
problem:_x000D_ set by customer no longer
_x000D_
Impact
Faulty
-Interface
Description
SW
works crash.
Dependency
_x000D_ whencomponent
to End-User:_x000D_
effects:_x000D_
Observed
of
transferring
on and
theconfiguration: onversion:
fault:_x000D_ sites
from FSME duringOAMto
None_x000D_ GTS
normal 12912_x000D_
FSMF_x000D_ work._x000D_
Workaround:_x000D_
Calls
-Customer
RUMAG
_x000D_
_x000D_
Dependency are not
did
Impact to End-User:_x000D_ possible
effects:_x000D_
not
on set due
cpriState
configuration: to GSM
of radio
none_x000D_ carriers
to down._x000D_
G_Passive_x000D_
N/A Not
_x000D_
Faulty
-Test
Summary sure
Description
How
WCDMA end ifcells
requirements:
component ofapplicable.
the
user/operator
how andOther
first
notoriginal
problem
accessible canthan
delivered
problem:_x000D_
could
version: detect
beDSP
for using
in(e.g.
detected_x000D_
the older
release,
problem:
, SBTS16_x000D_
users._x000D_ SW, CD):onlyGTS
Raised artificially
TRUNK
Fault 145 increasing
due to
limits
Impact
_x000D_
Faulty
_x000D_ on
12912_x000D_
Syslog
failed
KPI
Dependency
degraded
PIC to RX/TX_PU_BP_L-multibandMaxTotalBandwidth
shows
componentOperator:_x000D_
allocation_x000D_
on
these
after configuration:
sw
and kind update_x000D_
of
version: prints:_x000D_
SR002047
FTM_x000D_ on the module (if at
AHEGB, all possible)
_x000D_
would
Calls
_x000D_
INF/LTE
_x000D_
Faulty
Impact are
help._x000D_
to not
component possible
Operator:_x000D_ firstdue delivered to GSM in(e.g.carriers release,down._x000D_CD): SBTS16 legacy_x000D_
N/A Impact
Summary
_x000D_
Faulty to user/operator
component
1807 End-User:
ofisofthe theoriginal
raised. first
and No
WCDMA calls
problem:SRAN
L2/RlcSupportUl/cFFFFrFFFFuFFFFFFxFFFFl1F/CRlcAmPduBuffer::Update
Description
How
Fault end fault: could
PIC
delivered
version: are
allocation
detect
cells possible._x000D_
MOAM
in(e.g. the
are failsBTS working
problem:_x000D_
release,
offline.because CD):of
Calls areon TDM
limitation
n/a_x000D_
not (E1)
possible thatthrough
PIC
on can
Workaround:_x000D_
_x000D_
Description
FTIF
RlcVrMs
only
By long
Impact is to
be not
setup
term
failure ofmeasurements
ifthe
restoring
SBTS18A_ENB_1000_000623_000163_x000D_
WCDMA End-User:
cells there correction:_x000D_
- newVrMs
located after
isonone
voice transmission
notDCD
of found
quality
AHEGA KPIs_x000D_
after
RF after
issue_x000D_ failure.
PIC looping Back
allocation_x000D_
module._x000D_ the haulwhole connectivity
dpduArray! lost after
NA_x000D_
Update
_x000D_
transmission
_x000D_
Impact
_x000D_ the
to Operator:
validation
End-User: failure_x000D_ GTS
No rule 3G crashed,
toservice_x000D_
checknetwork carriers unavailable_x000D_
per band_x000D_
N/A _x000D_
Summary
INF/LTE
Dependency
Description
Impact
Faulty component ofofthe
to Operator:
Workaround:_x000D_ on original
theconfiguration:
fault:_x000D_
first
user problem:
delivered
possible LTE1891
FSMF_x000D_
in(e.g.
complains release, Micro-DTX
about CD): voice doesn't work for SBTS
quality_x000D_
Description
Workaround:
Risk
in dual
_x000D_
_x000D_
Impact analysis
end FSMF
Correction:_x000D_ ofTRX
to user/operator ofthe the correction:
toreset
configuration_x000D_
L2/RlcSupportUl/cFFFFrFFFFuFFFFFFxFFFFl1F/CRlcAmPduBuffer::Update
DCS
How
SBTS18A_ENB_1000_000623_000163_x000D_
NA_x000D_ Operator: will _x000D_
correction:_x000D_
becould deleted detect
be only after
the
blocked_x000D_ stopping Traffic
problem:RAT will be Trace on the
down._x000D_
TRX._x000D_
Low
Removed
_x000D_
Faulty
3 cells to component
none_x000D_
were
Workaround:_x000D_
RlcVrR
_x000D_ Ev_BscGwInitDone
failure grouped
- newVrR andinversion: one
not ulComp
foundevent
TCOM_x000D_ and
set looping
after St_WaitForOmuSig
and they the were
whole distributed state.toAdded
dpduArray!_x000D_ two
N/A handling
_x000D_
Summary
FSPs.
Description
_x000D_
Disablig
Workaround:
Impact
Description For of
tothe of Ev_OmusigUp
ulComp
of
End-User:the
MGW
of theoriginal
the
none_x000D_ fault:_x000D_
it none_x000D_
is required
feature
correction: event
problem:_x000D_
and FRS
_x000D_toinhave St_BcfInit
starttimings codec state
and
in ofoffsets
BSC BcfSc._x000D_matched for all
as highest
Correction
_x000D_
Description
During
Faulty
cells
How because
end
Description
Codec._x000D_
Update component effects:_x000D_
recommissioning
Transmission
BPF2_x000D_ ofthey
user/operator
of thefault:_x000D_
the correction:_x000D_
first
share failure on
delivered
couldtheir configuration
ppp detect
ULlink
in(e.g.
data.the
would with
release,
In WCDMA
problem:_x000D_
faulty
go down, CD):
sw DCS
which cells
split and
wouldcellswithout
removes
in timing LTE
Traffic
Carriers
Risk
cells analysis
SBTS
Description
Impact
There
_x000D_ Trace
is inwill
WBTS18_3000_0485_05_x000D_
groups
routes
Muting from
will
to onesuch
notisbe
the
Operator:
of StateChart
of
UE thegrouped
stuck the
happen
way
system. correction:
on
that plan
RFM
atcorrection:_x000D_
the
wrong by
gracefully
These
edge2 band
cells even _x000D_
of Routes
display were
cell when
activation._x000D_ terminated
after
on and checking
inWEBEM_x000D_
needs
muting
one
uplink group and
to the refresh
rule,
configuration
TBs be and oneso
restored
contain timer
cellmultiband
stopped
back_x000D_
is
just was
one cases
in second
byte when
of
N/A TRX
will
None_x000D_
reflect
_x000D_
Summary
group.
Addressed
payload. object
enabled._x000D_
Description
Analysis Reason
This
of reality
of is
ofthe
resource
the deleted._x000D_
causes
the now
original
behind and
leak this
that
correction:_x000D_
correction in-behavior
big
riskifcase
the
problem:_x000D_
PDCP
to the configuration
was
SDUtiming
of folder
customer is
opened /isend-user:
fragmentedotherwise
group calculator
by vtcTskMgr. correct
to_x000D_
well logic
over - pass
_x000D_ which
one
Refresh
How
CPRI
took
Dependency
_x000D_
For end
Workaround:
thousand
Impact
ABisFL
NA radio
into
ipsec, to
totimer
user/operator
consideration
End-User:
RLC
the
deliver on stopped
detection configuration:
none_x000D_
tcpdump
PDU the on
problem
could
that
segments.
n/a_x000D_
is
highest TRXcells
enabled deletion
detect
in
Codec dedicated
n/a_x000D_
Rootwereonly the om
cause
to ensures
if
Encproblem:_x000D_
radios
separate
developer
is
when that no if traffic
RLC
the RF
FSPs
debug
DL trace
sharing
but
bufferoption
_AMR notoperation
is
gets is enabled
that
is full due in
they
received to
occurs
Analysis
some
were
_x000D_
Description
Issue in
segmentation on
other
can ofbe
single
with CMR=NO_DATA_x000D_
enabled._x000D_ deleted
the correction
radios._x000D_
of encountered
the
ulComp
and TRX
fault:_x000D_
causes object_x000D_
group. risk
during to the
As
bookkeeping customer
acommissioning
consequence to go wrong. / end-user_x000D_
AXC
on configurations
SW offsetfinallycalculator
crashes.with
N/A Correction
_x000D_
Summary
handled
Faulty
RFM
hardware
Description
Impact
vtcTskMgr: muting
Description component ofeffects:
totiming
for
Operator:
ofthe
will
LTE
After
how groups
the not
the None_x000D_
original
cells
and happen
correction:
problem PIC
folder problem:_x000D_
separately,
version:
whenpool
will as
usage,thereVTC_FTM_x000D_
Micro
limitation
_x000D_ itnot
solved._x000D_isisno DTX
taking
onLTE
being messages
into
cells._x000D_
FSMF_x000D_
closed. account
Andwere that
thus notthe
there
reaching are will
folder
-Interface
Risk
How
Snapshot
shared
_x000D_
RFs._x000D_
_x000D_
Handle
Even
This
not be analysis
end inUL
though
ensures effects:
user/operator
collection
channels of
OPERATIONAL_PASSIVE
open RLC
under the
state None_x000D_
layer correction:_x000D_
is stuck
in
good
during could
ulComp
receives
Radio when
detect
(shared
reset_x000D_ PDU disconnection
the
while
conditions, problem:_x000D_
channels
segments AbisFL occurs_x000D_
arewillchannels
succesfully not limit that
it needs
the AMR transmit
to store
-Customer
Correction
When
_x000D_
Faulty
Description
codec
Ipsec: inthe
component
debug
Mode effects:
effects:
following
ofREquest
tothe
CpriLinkOperationalPassiveStateSupported
them
Workaround:
data not RlcAmPduBuffer
only Decrease
optiontheir None_x000D_
no
radio
main
will side
fault:_x000D_
first delivered
to #notfor effects_x000D_
connections
ofDSPscells,
UE._x000D_
be longer in(e.g.
but
enabled disable
time exist
also release,
bythan
to inDSPs
PIC, anotsingle
CD):
isnormally.
default. add yet
).Hence
more core
Inlegacy_x000D_
in the
L2DSPs (i.e.
can
end
the 1 will
deliver
shared
fileto FSMF notonly+be1 in
or
N/A -Test
2-Interface
How
Summary
FBBC):
_x000D_
Dependency
SBTS
open requirements:
endstuck effects:
user/operator
1of radio
FHSU_L/RU_L::supportedFeatures
whole
configuration_x000D_
channels PDCP
state andin the
onon
SDUs
main original
Plan
customer with None
NA_x000D_RF could
configuration:_x000D_problem:_x000D_
Activation.
channels
to upper sharing detect
Problem
layer._x000D_
machines_x000D_had enabled,1
the problem:_x000D_
misaligned caused or AXCmore dedicated
byoffsets
OAM whichradio waits
caused forKPI
A-Customer
Trigger
Validation
Impact
R3+R3
certain
connected
drop._x000D_
_x000D_
PDU
Risk
_x000D_ analysistosnapshot
state
bundling effects:
error
configurations,
End-User:
using after
ofofinternal
CPRI
function
the NA_x000D_
collecting
SW
End where
correction: update._x000D_
protocol
LTE User
that and
object
LTE todisconnect
wont
combines
No single
cells
(LNBTS_L).
be _x000D_
risk able
willcore
PDUs ADMIN_x000D_
be
toFBBC_x000D_
present
connect
_x000D_
which have in
to secondary_x000D_
EnB
dropped as RAT fromwill RLC
-Test
_x000D_
would
Then
receiving
Description
Risk
Correction requirements:
dedicated
be down._x000D_
analysis window ofof the
effects: radios
the has Traffic
correction: usingTrace
already
None_x000D_
correction: CPRI
PIC
been ongoing
protocol
Noallocationcreated
Risks when
connected
will
earlier
involved TRX
continue deleted
in order
_x000D_ to even
FBBC if will
to avoid there notare beno
N/A Description
How
Summary
Faulty
Dependencyend
detected._x000D_
RlcAmPduBuffer
DCDs
BBC
_x000D_ user/operator
of
ifcomponent
Correction:_x000D_
-Interface
Correction there ofthe
on theconfiguration:_x000D_
are original
2fault:_x000D_
from
effects:None_x000D_
effects:_x000D_ and could
problem:_x000D_
version:
or getting
more MCDsdetect
_x000D_
full. the problem:_x000D_
_x000D_
after allocation_x000D_
BTS
No
Perform
Cells
Impact
_x000D_SNAPSHOT_CANCEL_IND
Reset
-Customer
-InterfaceontoulCompsw
is does
Operator:update
SBTS17A_ENB_2000_001080_000002_x000D_
Configurations
_x000D_
Bundling triggeredwith
effects:NA_x000D_
effects:: not from
continue_x000D_
willhardware
Connectivity
have
when
None_x000D_ 17A
2the tooldest
for
paths 18A_x000D_
is
LTE created
would
on cells
its
already RXwhen
be lost
Channels
ACKed disconnect
there
between PDUis EnB
which noSN with
LTE
means,
and
is again it will
in be
_x000D_
cells._x000D_
Description
ADMIN_x000D_
Risk
having
backhaul_x000D_
-Testanalysis
receiving
-Customer 2 routes.
requirements:None
window.how of the problem
InHowever,
effects:NA_x000D_ thecorrection:
faultycanthat beLow_x000D_
software, detected:_x000D_
bundling BBC was not able
functionality wasn'tto handleenough thesein this
N/A Description
How
Summary
-Testend
Faulty
Undetected
_x000D_
Analysis
channels
case._x000D_ component
ofuser/operator
ofthe
with
requirements:siteofthe the
2 original
radios._x000D_ fault:_x000D_
correction
routes could
first delivered problem:_x000D_
which detect
risk resulted
reset to the
should in(e.g. the problem:_x000D_
inrelease,
customer
be incomplete
tested CD):_x000D_
/ with
end-user_x000D_
routing configuration
correction
Attempt
TUD70555
Incorrect
_x000D_
Dependency
Correction
being
Workaround: fordefault
component
sent -Recovery
Planhandling
SBTS17A_ENB_2000_001080_000002_x000D_
Faulty on
effects:_x000D_
on value
andreset_x000D_
used
configuration:_x000D_
none_x000D_
murrku version:
side. lead
BBC forLTS,
to'minNumRrcCatM"
is"BTS did'nt
FCTRL_x000D_
creating respond
routing parameter.
in 270s" Incorrect
configuration error_x000D_
file during
default
_x000D_
Description value
No dependency_x000D_
-Interface
routing application of5the used.
effects:_x000D_ Wrong
fault:_x000D_
and the format migration of theforfile minNumRrcCatM
have changed after parameter
TL16A.value The
N/A in
How
Summary
Description
case
Faulty
System
_x000D_
-Customer
changed end
Description
Impact
Dependency of
component
to inuser/operator
of
Airscale_x000D_
module of
the the
End-User:_x000D_
effects:_x000D_
the
of on the original
is
format fault:_x000D_
not
first could
problem:_x000D_
creating
delivered
correction:Default
configuration: of detect
IPin(e.g.
the configuration routes
n/a_x000D_ the
Route problem:
release,
fromfile FSMF
is restored ST_x000D_
CD):
particularly ton/a_x000D_
FBBC
after theIPCP during 3G-4G
StreamId and
WTS
_x000D_
Unable
RF
Faulty waits
sharing to change
component
ModuloIndexRuleId
toggle_x000D_
No
-Test impact_x000D_
requirements: for
while DSP inany
andto
fact
have respond
parameters
version:
it caused
should but
URI havedue
it0._x000D_
HWAPI is been
offline_x000D_
to to ongoing
creating
miss RNW
read plan
routes._x000D_
the configuration being
WTS
Description
activation_x000D_
Impact
_x000D_
Dependency
sent
Faulty towaits to
them.
componentend forofon the
response
user
All offault:_x000D_
configuration:
: none_x000D_
this
and from DSP
resulted
version: CAT-M before
in incomplete
n/a_x000D_ ._x000D_creating routes result
created for for the cells,
N/A SHUTDOWN_RAT_TASK_x000D_
The
_x000D_
Summary
thus,length
Dependency
Faulty
Risk
Impact component
analysis
high of ofthe parameterValue
on
to Operator:_x000D_
UL of
BLER original
configuration:_x000D_
the first problem:
delivered
correction:NA_x000D_
occured. is in(e.g.
_x000D_ more
One than WNCEL
release, its limit,
on
CD): CPRI
caused radiomodule
parsing to does fail.
_x000D_
How
not
3G-4G reach
Correction
LTE
Impact end
KPI toare user/operator
onAir
operator notstate_x000D_
SBTS17A_ENB_0000_000430_000245_x000D_
Faulty component
RF sharing.
effects:NA_x000D_ and
: Restricted
correctlycannot
first could
version:
pegged.
delivered detect
activate ton/a_x000D_
No
in(e.g. the
single-core
plan_x000D_
powerproblem:_x000D_
release, FSMF
consumption
CD): +1 or 2gain
n/a_x000D_ FBBC._x000D_
as
_x000D_
Some
and
If cell
Dependency
at least
-Interface cells
expected_x000D_ remain willonnot disabled
1effects:NA_x000D_
radio go3G-4G
configuration:
has on after
configuration:_x000D_ air afterRF unblock._x000D_
recommisioning.
n/a_x000D_
sharing enabled, CPRI Hard dedicated
reset will be radios will
N/A Summary
Dependency
needed._x000D_
_x000D_
not
Impact
Faulty
-Customer
Workaround:
Theoretically ofeffects:NA_x000D_
be detected._x000D_
component
to End-User: the
on original
configuration:
None_x000D_
every first problem:_x000D_
none_x000D_
delivered
configuration
temporary NA_x000D_
loss in(e.g.
that ofrequires release,
service_x000D_ that CD):_x000D_
ulComp cells are
_x000D_
Description
Fault
Faulty 1858 isofdeactivated.
FL00_FSM3_9999_190205_045234_x000D_
-Test component
Workaround:_x000D_
distributedrequirements:NAto the fault:
separate Race
and FSPs._x000D_
version:Accordingcondition
n/a_x000D_ with onthe BBC new and diagram
FDD CPRI_x000D_fault 4001 should
Faulty
Description
CPRI
not
Impact
_x000D_activate._x000D_
Manually
Please requested
component
to
note of theBBC
Operator:_x000D_
adding
Operator:
that fault:_x000D_
and
iptable
this toversion:
change
correction:_x000D_
rule
stability_x000D_
doesn't in
apply SYSADAPT_x000D_
thetohwlinkType
Primary._x000D_
OAM -configurations
HAS/IPSVC_x000D_ via our withHwportExecutor
vertical u-plane but
N/A Summary
OAM
BBC
_x000D_
Can't
Impact
Faulty wasn't
deploymentswill to try
request
cancomponent ofable
End-User:
handle the
to another
where original
startto simply
Carrier
first
allno
internal problem:_x000D_
snapshot
delivered because
Aggregation
impact_x000D_
ulComptask we
collecting_x000D_
in(e.g.
immediately
cells would weren't
even
release,during though
normally the
CD): owners
plan the feature
n/a_x000D_
share of the
activation
the same is
connector
turned off.
without at
DSP
OAM
the
How
_x000D_
Faulty
Description
waiting
Workaround:
FSPs._x000D_crash
time_x000D_
end
fails
component occurred
foruser/operator
to validate
specific
of first during
some
the correction:_x000D_
none_x000D_ state could
delivered
of LTE high
cells detect load_x000D_
after
in(e.g.
connected the recommisioning
problem:_x000D_
release,internal CD): with Carrier
object._x000D_
FL18A,
_x000D_
Aggregation
[1.
MarkDetail
Workaround:
Impact
SRAN18A_x000D_
the Test
End-User:feature
SBTS17A_ENB_2000_001106_000000_x000D_
to Micro
Operator: No Steps:]_x000D_
DTX WA_x000D_turned
wrong
none_x000D_
traffic on._x000D_
migration
in Primaryofand minNumRrcCatM_x000D_
route to Secondary from where this
_x000D_
Dependency
not
How
will
Risk
No needed
end user/operator
reach
analysis
Configuration
Description LTE inon
of ofdocumentation,
configuration:
RFM_x000D_
the the could detect
correction:
dependency
correction:_x000D_ specification
4+3_x000D_
onNone_x000D_
BBC theside._x000D_
problem:_x000D_
made fault reports and customer
Dependency
_x000D_
made
Unit
Correction
Impacts autonomous
Workaround:
Impact
Description
Solution tickets_x000D_
toisto ofon
Operator:
End-User: -change
effects:_x000D_
to end-user the
trigger configuration:_x000D_
reset nooccurred
stability_x000D_
none_x000D_
: the
correction:_x000D_
PDU parameter
full
bundlingservice inone DSPmanually
_x000D_SN and leads
earlier afterinto sw WCMDA
which caseRAT
update_x000D_ buffer would
Faulty
step
reset_x000D_
URI 1:
_x000D_
Plan
User
Risk
never hascomponent
create
can
analysis
get BTS to
perform is
be ofoutCA of
and
SNAPSHOT_CANCEL_IND
full._x000D_ the power.
ready,
commissioning version:but
correction:_x000D_ RP3-01
version:_x000D_ _x000D_
feature Cable
without switched
when between
stucking in primary
off._x000D_
ADMIN plan and secondary
disconnect_x000D_
activation
HAS_x000D_
cores
_x000D_
Description
Workaround:
Impact
Risk
OAM/
No disconnected._x000D_
to Operator:
analysis
Risk_x000D_
DCS, of
operator Manual
thethe
of
BBC_x000D_ correction:_x000D_
: BTS reset_x000D_
llcorrection:
Cells willconfigured
notno respondrisk_x000D_
at AHHBin 270s._x000D_are OoS_x000D_
MOAM_x000D_
Step
Description
Use
_x000D_
Faulty 2:component
correct
Correction
PS_REL/
Risk analysis Power of the
default
effects:
HWAPI_x000D_
of onthe the
fault:_x000D_
and
value BTS.
no_x000D_ 0 Primary
version:
correction: the core
: setn:a_x000D_
MCI_x000D_ successfully started.
minNumRrcCatM = new default Alarm value indicating (=0)
N/A Summary of the original problem: PM data is not reported in case of
synchronization lost to the external clock source._x000D_
_x000D_
N/A How end user/operator
Summary of the originalcould problem: detect reset thecaused
problem: byPM memory data not leak_x000D_
being provided
if SBTS is not in sync with the external tme source_x000D_
_x000D_
_x000D_
How end user/operator could detect the problem: Run any configuration with
N/A Description
Nokia
Summary radios ofofthe for
the a
original
fault:
month_x000D_ Too
problem:_x000D_
strict implementation of requirement for SBTS
being
_x000D_
Mismatch synchronisedin the RIM with statusthe time parameter source._x000D_in webem and NETACT CM
_x000D_
editor_x000D_
Description of the fault: SOAP Message Traces consuming too much space
N/A in
_x000D_
Description
SBTS causing
Dependency ofon theconfiguration:
memory
problem_x000D_ leak NA_x000D_and increase in cpu usage_x000D_
_x000D_
How
There endareuser/operator
many un-register couldBTS detect trace thehandling
problem:_x000D_ in BTSMED._x000D_
_x000D_
Dependency
change
Faulty RIM status
component on configuration:
and parameter
version: value_x000D_ any configuration with Nokia radio_x000D_
N/A_x000D_
N/A _x000D_
How
Summary end user/operator
of the originalcould problem:_x000D_
detect the problem:_x000D_
Description
User/operator
There
Faultyis
Faulty a field
component
component of thecan
in thefault:_x000D_
see
first
and PM many file,un-registered
delivered
version: BTSMED_FAIL_CM_UL,
MOAM_x000D_
in(e.g. release, BTS trace handling
CD):NA_x000D_ it mean in the number of
BTSMED._x000D_
failures
RIM status
d._x000D_
_x000D_ for the is set CMby Upload
system It value,
leads to should
manyupdate failuresvalue for CM by Upload_x000D_
_R objects, but
N/A related
_x000D_
Summary
Impact _REnd-User:
Faulty component
to ofobjects
the originalhas
first notproblem:_x000D_
:NA_x000D_
deliveredbeen created in(e.g. release, by LTS._x000D_ CD): n/a_x000D_
_x000D_
Description
How
Change endtxBandwidth
user/operator
of the fault:_x000D_ & rxBandwidith
could detect the parameters
problem:_x000D_ from NetAct will be always
Dependency
Connection
execute
failed._x000D_
Impact tothe is
CM
Operator:
End-User:onnotUpload
configuration:
closedLack operation
temporary when NA_x000D_
BTS
of counters_x000D_
loss from is un-registered._x000D_
of Netact, check the PM file, and see if
service_x000D_
N/A Summary
the result for
_x000D_ of the original problem: _x000D_
BTSMED_FAIL_CM_UL is the expected number_x000D_
Provision
Dependency
_x000D_
How end
Workaround:
Impact
Faulty failed._x000D_
to user/operator
component
Operator:on configuration:_x000D_
none_x000D_
and could detect
stability_x000D_
version: n/a_x000D_the problem:_x000D_
No_x000D_
Description
Trigger
_x000D_ NetAct of the CMfault:_x000D_
Provision with txBandwidth & rxBandwidith parameters
N/A Summary
_x000D_
Because
through
How end
Workaround:
Faulty
Description ofaof
xml._x000D_
of
component the
user/operator
code original
none_x000D_
the first
correction: problem:_x000D_
bug,delivered
could
the number
detect
requirement
in(e.g. the
of CM problem:_x000D_
release,upload
on SBTS CD):failures
being and
SBTS18A_x000D_
all the CM Provision
time in sync
After
failures
_x000D_
Do
Faulty the
withprovision
external BTSMED
are
component counted
request
tme source upgrade
firsttogether
with a big
delivered
needs isincompleted,
provision BTS SW
BTSMED_FAIL_CM_UL_x000D_
to
in(e.g. plan._x000D_
be relaxed._x000D_
release, upgrade will be failed
CD):_x000D_
occasionally.
Description
_x000D_
Impact to End-User: of_x000D_
the fault:_x000D_
nokia-imp-18a.1.20190422132801.cb1b35-1.noarch_x000D_
correction:
none_x000D_ Use of correct function API to get the size of
N/A Summary
Dependency
CM
Description
_x000D_
RiskPDL
soapMessageTrace
analysis ofofthe
validation onof original
theconfiguration:
thefault:
error
to problem:_x000D_
Message
withthe
limit
correction: message,_x000D_
no_x000D_
sizethreshold
to 150kb_x000D_
SAFE_x000D_ was small when occurred a big
NetAct
_x000D_
plan._x000D_
How
Impact
Analysis provision
feedback:errorText_x000D_
end to user/operator
Operator:
End-User:
of a plan
the correction wrong with
could
none_x000D_ parameter
detect
to the the
display_x000D_
risk LOGLINK.secondEndpointDN
problem:_x000D_
customer / end-user SAFE_x000D_ on site
fails
Faulty
Risk with
{"Severity":
_x000D_
when analysis
Correction PDL
operator
component validation
"Error",dothe
of
effects: BTS
and
"Assertion":
PM error._x000D_
version:
SW
correction:
data upgrade
willAlways
"263", after
Safe_x000D_
not be "Text":
exist_x000D_
BTSMED
blocked "Whenever
if SBTS SW upgrade,has * RXbeen bandwidth
the issue will
previously
N/A _x000D_
Summary
Dependency
appear
Workaround:
Impact
inAnalysis
sync to and ofoftemporary
occasionally.the
on original
MRBTS-933841/WNBTS-1/WNCEL-33853.rxBandwidth
configuration:
Operator:_x000D_
the restart
correction _x000D_problem:_x000D_
BTS_x000D_
lostof risksync NA_x000D_
to the customer / end-user_x000D_
happens_x000D_ (value: 3.8 MHz) is
How
RSSI end
configured,
_x000D_ increased
User/operator
Faulty
Correction
-Interface user/operator
component it iscan after
effects:_x000D_
effects: seeFXED
required
first
NA_x000D_ could
thatreplacement
delivered
un-registered detect
configured
in(e.g. the
BTS problem:_x000D_
by
release, AREA
rxBandwidth
trace radio
handling
CD): is module._x000D_
supported
legacy_x000D_
in BTSMED._x000D_ by all radio
_x000D_
modules
Faulty
Description
Do provision
-Customer
-Interface component
handling
ofoperation
the fault:_x000D_
effects:_x000D_ the
andcell.",version:
from "Detail":
correction:_x000D_
effects:NA_x000D_ NetAct btsmed_x000D_
with
"Assertion
parameter not met:
N/A How
Summary end
(WNCEL(rxBandwidth
_x000D_
After
Workaround:
Impact
see
-Test_A
-Customer user/operator
ofeffects:_x000D_
LOGLINK.secondEndpointDN
the BTSMED
toobjects the
End-User:
requirements:NA original
n/a_x000D_
to upgrade
update could
problem:_x000D_
Nodefined) setisdetect
impact._x000D_ completed,
byinspliced
system thetoproblem:_x000D_
plan._x000D_ every
the BTS
value for LTS cache data which
provided existed
lists_x000D_
LNADJW
Replace
Faulty
in
_x000D_
BTSMED FXED
reasoningStatus
component
LCELW/CHANNELGROUP/CHANNEL
-Test requirements: restore with first AREA
faileddelivered isand
during notcheck correctly
in(e.g.
BTSMED RSSI/RTWP
cleared._x000D_
release,
by startup.
lCelwDN CD): level._x000D_
BTS
= 18A cache
& 19_x000D_
LCELW.distname) data recovery have
_x000D_
depend
Description
Risk analysis
Impact
(every toonOperator:
the
ofof the
plugin
RMOD/ANTL(ANTL.distname
the fault:_x000D_
load, but
correction:_x000D_
Wrong
correction: counter before =BTS
unsafe_x000D_
value._x000D_
externalcache data recovery, plugin
CHANNEL.antlDN) haveload
N/A How
Summary
Impact
hasn't
PDL
Close
_x000D_
(every end
Description
Correction theto user/operator
validation
been ofeffects:NA_x000D_
the
End-User:
of
RMOD_R(RMOD_R.configDN
trace original
completed.
the
failed fault:_x000D_
connection could
problem:_x000D_
none_x000D_
caused
BTSMED when detect
by incorrect
don't
BTS the problem:_x000D_
=ismake value
external someof parameter
un-register._x000D_ startup service sequence
RIM
[SBTS18A[QT][DUALCORE][FID=4076]
_x000D_ interface
right._x000D_ alarm
ANTL_BP_R.allowedVoltages._x000D_
The problem
Workaround: is not cleareddata
with converting
RMOD.distname)/RMOD_BP_R.supportOfRXBandwidthWCDMA(element
-Interface no_x000D_
effects:NA_x000D_ evenfrom if allDistributed
the defined
15bit wordssite adjacencies
send support
from radio nothaveenabled
to RIM
16bit
+0
status
after
Impact
_x000D_
words
Risk
= planned
external available_x000D_
on to system
analysis
-Customer Operator:
external commissioning_x000D_
of themoduleprovision sideisthe
WNCEL.rxBandwidth
effects:NA_x000D_ correction: failing_x000D_
differences
No_x000D_ will always be 6dB. Additional
+ 0) exist))"}_x000D_
N/A _x000D_
Summary
Dependency
bit is causing
Correction
Description ofeffects:_x000D_
/feedback:errorText_x000D_
-Test ofthe
requirements:NA on
this original
theconfiguration:
6dB problem:_x000D_
difference._x000D_
correction:_x000D_ NO_x000D_
Description
How
Embedded
_x000D_
FXED
-Interfaceend user/operator
is using
BTSMED_FAIL_CM_UL
Workaround: Power
ofUse
effects: the
OBSAI fault:_x000D_
aMeter
no_x000D_
small could
for
interface
just Energy
provision detect
count withthe Efficiency
thenumber
16bit problem:_x000D_
plan._x000D_ words Monitoring
of: noCMissue upload showing
with wrong
failures_x000D_
Startup
Real-time
Faulty
conversion_x000D_
When
Netact
Dependency
_x000D_
-Customer morewith Measurement
component
executes HWF_x000D_
than oneand
on configuration:
effects: CM fault forisSMOD_x000D_
version:
Provision,
no_x000D_ detected
BTSMED
No_x000D_
issue anonincorrect
a18A
18A_x000D_
single 1.0_x000D_
LNADJW
plan, provision reasoningStatus
fails, is
N/A _x000D_
Summary
AREA
not cleared._x000D_
is using
BTSMED_FAIL_CM_UL
Description
-Test ofofthe
requirements: the original
CPRI problem:_x000D_
interfacedoes with
correction:_x000D_
no 15bit words
not increase the :count_x000D_
conversion to 16 bit needs
Description
How
After
Faulty
correction
_x000D_
Remove end
switching user/operator
inoflimitation._x000D_
component
the RX the
from fault:_x000D_
scaling
first
and OBSAI could
delivered todetect
factor_x000D_
version: CPRIin(e.g.
BTSMED, the
, BTS problem:_x000D_
release,operational
SBTS18A but without
CD):1.0_x000D_
SBTS18A
18A_x000D_ cells
1.0_x000D_
RttSmFr
Real-time
mapped
_x000D_
Note
Dependency on
calculation
: _x000D_
Risk analysis Measurement
the ofnew
on failed
RM with
configuration:
the correction:forbecause
SMOD_x000D_
CPRI which
loopingDelay
no dependency
no_x000D_ is not on detected
was taken by SBTS._x000D_
configuration_x000D_ from HWF which
N/A _x000D_
Cells
Summary
Impact
3GPP
Faulty
was
Risk
Analysis mapped
outdated
analysis ofthe
Specification
component
toofEnd-User:theon
of original
hence
thethe
and for
first
correction new problem:_x000D_
none_x000D_
initial RM
version:
UL air
level
correction:NA_x000D_
delivered
risk with
timings
to CPRI
measurement
LTS
in(e.g.
the are Disabled_x000D_
trunk@12576_x000D_
calculation
release,
customer /+/-4dB
failedSBTS18A
CD): but
end-user_x000D_ with expectation
fault 1.0_x000D_ +/-2dB
Description
_x000D_
mpdcchNarBandNumCatM
accuracy
4076._x000D_
Correction
Correction of theMHA_x000D_
without
effects:
effects:_x000D_ fault:_x000D_
NA_x000D_ value is 0 in
Recently
How
CELLC_RAC_RECONFIGURATION_RESP_MSG
Impact
Faulty
_x000D_ end
-Interface
no_x000D_ to added
user/operator
component commit
Operator:_x000D_
End-User:
effects:_x000D_ first could
enabling
delivered
N/A_x000D_ detect sequence
in(e.g. therelease,
problem:_x000D_
mode of_x000D_
transfer broke
CD):n/a_x000D_
N/A SMBus_x000D_
Change
_x000D_
Summary
Impact
_x000D_
NA_x000D_
After
NetAct
-InterfaceBTSMEDtoRF ofmodule
therestart,
original
End-User:_x000D_
provision
effects:_x000D_ a plan in configuration
userproblem:_x000D_
with can't
parameter do from BTS OBSAI
upgradetooccasionally_x000D_
LOGLINK.secondEndpointDN CPRI._x000D_ might
block
_x000D_
How
DSP
Dependency
No
Impact
be
no end
crash
calls
-Customer transfer.
user/operator
tocan
failed._x000D_
_x000D_ that onThey
be results
made_x000D_useintocould
I2C_M_RECV_LEN
configuration:_x000D_
Operator:_x000D_
effects:_x000D_ RAT detect reset_x000D_
the problem: flag toET indicate
testing_x000D_ that the
Description
_x000D_
Impact
exact_x000D_
AREA installed._x000D_
NA_x000D_
Workaround:
-Customer
Cannot to
change how
End-User: problem
NO_x000D_
effects:_x000D_
txBandwidthReduction can&be ofdetected_x000D_
service._x000D_
rxBandwidith parameters (value=3.8) from
N/A Summary
Replaced
Description
How
_x000D_
Impact
number end
Workaround:
no-Test
NetAct_x000D_
_x000D_ of ofthe
toofuser/operator
CPRI the original
RF
Operator:_x000D_
bytes
requirements:_x000D_ tofault:_x000D_
NO_x000D_ module
read problem:_x000D_
could
is not is detect
not
known detected._x000D_
theand problem:_x000D_
the len parameter is always
_x000D_
SRS
fault
Slimalarm
Impact
Cells
set_x000D_
Re-test reconfiguration
Description
Faulty
-Test Carrier 6709
offline_x000D_ offilter
theindoesn't
to Operator:LNADJW
component
requirements:_x000D_ Raw was Alarm
executed
correction:_x000D_
and work
version:_x000D_ rim History
foralarm
AHEGA
by CELLC_RacReconfigurationReq
which
not RF leads
module_x000D_
cleared._x000D_ to RAT reset_x000D_ during
UeCeLevel
_x000D_
toDescription
1. The
modify
Description
noBPF1
Workaround: and restablishment._x000D_
thecontrollerofNo_x000D_
BTSMED
BPF2.
of thecorrection:_x000D_
the fault:_x000D_
isstartup
SBTS18Aexpected service to dynamically
_x000D_ sequence,detect do plugin the real loadnumber_x000D_
firstly, when it
N/A Summary
_x000D_
Description
How
complete,
Correct endthe
Workaround:
Workaround:_x000D_
of
Channels
bytes readof
in
then the
user/operator
of the original
fault:_x000D_ problem:_x000D_
could
CLEAR_DEVICE_REQ::channelDNs
No
which
mapping known
restore should detect
workaround._x000D_
relationship
BTS becache send thefirst
as
todata._x000D_
extract problem:_x000D_
byte ofofwere
value answer._x000D_
parameter passed for deletion of
SRAN
Dependency
Fault
Check
_x000D_
Site
The 6709
ROUTINGENTITY_L SITE
ondid
reset_x000D_
code
ANTL_BP_R.allowedVoltages
Description (L+W+G)
spectrun
-of not check isfor
objects abnormal
EFaultId_DspConcurrentCrashErrAl_x000D_
ontheconfiguration:
analyzer
correction:_x000D_ celln/a_x000D_
I2C_M_RECV_LEN
andfrom DLthe when LTEfile._x000D_
bandwith._x000D_
list doesn't
bpf2.xml 4thflag sector
contain and passed added_x000D_
support 1 to
_x000D_
Description
the_x000D_
channels._x000D_
Risk
Impact
provide analysis
to ofof
End-User:
corrected the the correction:_x000D_
valuecorrection:NO_x000D_
None_x000D_
of parameters
N/A Summary
Faulty
Dependency
How
Description
During
Risk
_x000D_
LNADJW end
Description
Master
Correction ofeffects:NO_x000D_
component
Receive
handling
analysis of the
user/operator
of
reasoningon the
the
of
RMOD_BP_R.supportOfRXBandwidthWCDMA original
configuration:
and
fault:_x000D_
Transfer problem:_x000D_
version:
could
ofcorrection:_x000D_
the CLEAR_DEVICE_REQ,
correction:
status willdetect
Length none_x000D_
UEC_x000D_
now making
NO_x000D_ betheproperly
problem:_x000D_
the ROUTINGENTITY_L
transfer
and end prematurely.
cleared_x000D_ objects
RF
_x000D_
If module
Feature
Added
This_x000D_
pointing
calculation
Correction
Impact
-Customer LTE
toto filter
CNI-440044th
channel
Operator: power
sector
of RttSmFr
effects:
effects:NO_x000D_
RMOD_BP_R.supportOfTXBandwidthWCDMA distnames
NO missing
forcannot
Slim
RSSI/RTWP failed Carrier
be alarm
were
duringdeployed
and on certain
implementation
deleted
initial
SINR even
air
in lim,
KPI carrier
there
timings but
_x000D_
from was isconfigurations
missed
enough
calculation,
those
bpf2.xml_x000D_ in
bbu
for support BPF caused
suppress
by too
Faulty
part._x000D_
raising
patch
channels
_x000D_
Risk
-Test high/too
resources._x000D_
component
changes
of were
analysis faultof4076
requirements:NO low
theand
not
the output
first sopowers._x000D_
version:
deleted._x000D_
code
to delivered
allow
correction: that SS_W1pLRx
recalculation._x000D_
I2C_SMBUS_BLOCK_MAX
in(e.g. release,
Safe_x000D_ - 147370_x000D_
CD): 18A, 18SP, is passed 19, in
N/A _x000D_
Summary
Missing
this_x000D_
19A_x000D_
Workaround:
Correction
Risk analysis ofeffects:
Slim the original
Carrier
None_x000D_
of the LNADJWupdatesproblem:_x000D_
correction:_x000D_ in BPF files
reasoning statusfor specific
will nowRF be modules._x000D_
properly
Parameter
Faulty
_x000D_
Description
How end
case._x000D_
Dependency
cleared_x000D_
Correction
No risk_x000D_componentLNCEL.eutraCelId
user/operator
ofon theconfiguration:
effects:_x000D_ fault:_x000D_
first delivered
could detect for INBAND
in(e.g.
n/a_x000D_ therelease, NB-IoT
problem:_x000D_ CD):cell the value couldn't be
seen._x000D_
SBTS18SP_ENB_2000_000970_000000_x000D_
Dependency
Spectrum
Added
_x000D_
Impact
Description
-Customer
-Interface
Correction LTE
to at 4th
the
End-User:on sector
configuration:_x000D_
antenna
effects:_x000D_
effects:
of the
effects:_x000D_ cannot
none_x000D_connector
correction:_x000D_
Cell are online be deployed is fluctuating even there and the is enough
networkbbu doesn't work
N/A _x000D_
Summary
resources
correctly._x000D_
Problem
Dependency
Faulty
System
N/A_x000D_
-Interface of
visible
component
Module
effects:the
because_x000D_original
when
on when
configuration:Slim
andconnected
No_x000D_ problem:
version: Carrier The
NA_x000D_
n/a_x000D_
through RSSI
is trying CPRItodifference
beshouldactivated between
adjust on scaling RX main
following RFand
factor
Description
RX
Impact AUX,
modules:
when
_x000D_
received
-Customer
-Customer WCDMA in
tofrom of
anRadio
Operator:
End-User: the
IDD-2UD
cells problem:_x000D_
effects:_x000D_
effects: are
wrong
loss
No_x000D_ BB-hop
6 dBallocated
oflower
PM tosector
service_x000D_
data first
, UE
compensate exceeds
overcannotLTEfor 20mapping
cells,
be dbmtheyduring
assigned took
the cs all
up
to proper
15 bit CPRI
call._x000D_
FXEB,FXED,FXEE,FXEF,FHEL,AHEGA,AHEGB,AHEB,AREA._x000D_
remaining
Description
Values
Faulty
band_x000D_
_x000D_
words
N/A_x000D_ to couldn't
-Test requirements:16resources;_x000D_
component of thebefault:
ifbitproblem
DSP seen
first _x000D_
based
words
No because
delivered that oniscertainof
in(e.g.
done INBANDrelease, NB-IoT
configuration
with MSB CD): special
NA_x000D_
n/a_x000D_
alignment. treating
This wayon the 6
N/A _x000D_
Summary
DPD
sbts18
Impact
dB-Test accepted
(see:
introduced of the
to Operator:
requirements: by original
Description
bad the models, problem:
of the
stability_x000D_
bit mapping which _x000D_
fault). included
would Bug bewas positive
not random
canceled orbynegative
theas forgain,
scaling all factor
INBAND
which
Relation
How end
Faulty
Dependency
caused
NB-IoT
Impact
Workaround:
_x000D_ error
the
to
adjustment._x000D_ user/operator
component
cells output observed
values
End-User:on could
while
configuration:_x000D_
and
power
none_x000D_ couldn't
cellversion:
istodown bevalidating
detect, no the
fluctuate._x000D_
n/a_x000D_
seen at DSS
problem:
WebEM
service_x000D_ Featureand Web ongui, SRAN18A
NetAct._x000D_ shows the : when
RSSI
values
DSS
_x000D_ is for
Configuration
Workaround: activated
each no TRX,
whereon dual andcore
LTE
workaround_x000D_
SB18AMP0_PS_LFS_OS_2018_09_0022_x000D_ the
anddifference
Airscale,
WCDMA the between
cells following
belong theto relation
main and
different errorauxisis
N/A noticeable
displayed:_x000D_
Summary
cellsets._x000D_
Dependency
How
Risk end
Impact
Description
_x000D_
Faulty of
component
analysis there._x000D_
ofthe
to user/operator
Operator:onof original
theconfiguration:
the problem:_x000D_
could
correction:_x000D_
first
cell delivered
disabled_x000D_
correction: detect
_x000D_
in(e.g.
tested theon problem:_x000D_
release,
field_x000D_ CD): n/a_x000D_
'Whenever
BTS
This
Operator
_x000D_
Disable is out
phenomenon
Description
Impact
Correction toSRS of
*effects:_x000D_
ofLCELW-0.actDynamicSharedSpectrum
couldn't
End-User: control.
the see Alarm
is none_x000D_
reconfiguration carrier 9407,
some configuration
correction: made8502
INBAND
during the occurred
NB-IoT
UeCeLevel dependant,
pool_size_12 again (value:
butin
cellrestablishment_x000D_
values._x000D_
of 10true)
hard
SS_W1plRx SBTS is equal
to say, evenwhich
same tofor
true,
though
Faulty
R3
Impact
_x000D_
Level anditmeasurement
configurations
_x000D_
Description
Workaround: isto
therequired
component sites
R4_x000D_
End-User: are
ofnone_x000D_
the
could that reachable_x000D_
No _x000D_
fault:_x000D_
and result
version:
accuracy in such
impact._x000D_ DCS
spec situation.
is70006_x000D_
+/-4dB.It So might there also could be dependant
be 1dB on the
N/A all
_x000D_
Summary
power
Risk RMODs
Description
It was
Risk
Impact
difference found
level,
analysis
analysis of with
of
to Operator:
betweenthe
which
that
the
of
of WCDMA
original
indexing
the
thefault:_x000D_ problem:_x000D_
cells
isaccuracy_x000D_
allocated
correction:No
correction:
_x000D_ are
of transmission
for connected
the
none_x000D_ ruletodbthe
radio._x000D_
risk_x000D_ was sameincorrect,Airscale and the same
BBMOD'_x000D_
How
InOn
wrongsome
_x000D_
was
Impact
Faulty end
SBTS18A
Description
Also tocases,
fixed_x000D_
Analysis
Correction user/operator
component
of
Operator:
Real-time
sensitivity effects:
thethe
of when
URI/BTSMED
correction
or first
no
Measurement channel
Filter
correction:
some could
more
delivered
onrisk
interferer DSPdetect
radionumbering
reads
to in(e.g.
the
Include
for the
crashes
doesn't problem:_x000D_
customer in
"set-by-system"
release,
SMOD_x000D_
(PIM) support duecellto
work.
difference model
/ end-user_x000D_
CD):
Cell
pool
channels changes
parameters
bandwidth
could exhaustion_x000D_
for
cause withoutare
which
is
deletion._x000D_
difference reset
set
but
occasional_x000D_
such
Faulty
as
_x000D_
But cell
follows:
wider._x000D_
Correction
-Interface
_x000D_
this should might
configuration
component_R
effects: notis
which
SBTS18A_ENB_1000_000623_000163_x000D_
effects:_x000D_
not be be
aand isable
allowed._x000D_ to go
version:_x000D_
none_x000D_set by
case_x000D_ system OnAirparameterdue to invalid in NIDD handling , and of setinternal
value from
_x000D_
states
This
_ADependency
for
-Customer
Workaround
Risk
-Interface in MCtrl._x000D_
problem
set
analysis by :operation
could
on
effects: configuration:
effects:_x000D_
none_x000D_
of the be seen
parameter_x000D_
none_x000D_
correction: withIDD- the 2UD_x000D_
n:a_x000D_ I- and J-branch RFSW from the first
Description
_x000D_
versions
Because
How
Workaround:
Impact
-Test
Correction
-Customer end toonwards
of
requirements:of
End-User: theisfault:_x000D_
user/operator
mctrl and
None_x000D_
effects:_x000D_ not
lessalso
none creating
could
4Gincapacitythe
detect
lncel_r
master the for
can problem:_x000D_
branch._x000D_
benbiot cells, parameters from them
used_x000D_
BTS
How
-weren't
Faulty
_x000D_ initials
end
Reconfiguration
Description
-Interface
-Test user/operator
component new
of theconnection
visible._x000D_
requirements:
effects:_x000D_ failure could
and version:
correction duewith detect
:to BTSMED,
unexpected
GSM
_x000D_ the BB,problem:_x000D_
but in BTSMED
legacy_x000D_
validation error._x000D_ side, the former
connection
Affected
_x000D_
Description
Impact
Faulty
Fix
-Customer
block tocell
component is
ofwill
Operator:
transfer alive,
thenot inproper
enter
correction:_x000D_
effects:_x000D_first
issue Added OnAir
delivered LTE process state._x000D_
4th
in(e.g. sequence
sector release,
cannot lead beto
CD):_x000D_ the new
utilized as connection
it cannot be
_x000D_
Dependency
Description
was
Faulty
-Testnot
BPF component
deployed_x000D_
When updated,
our working_x000D_
SW
requirements:ofon the configuration:_x000D_
updated
startedfault:_x000D_
firsttoSlim
delivered
support Carrier in(e.g.
AREA for radiorelease, unit,CD): legacy_x000D_
the problem was in the
Description
no
Validation
_x000D_
dependency_x000D_ of thealthough
failed fault:_x000D_
FXEB,FXED,FXEE,FXEF,FHEL,AHEGA,AHEGB,AHEB,AREA_x000D_
RFSW._x000D_ configuration is allowed._x000D_
N/A Summary of the original problem: _x000D_
No connection to MHA after rollback to SBTS18SP, and RETs in Disabled
State on SRAN Sites after power failure or site reset._x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
Description how problem can
stateInfo.reasoningStatus is never
be detectedupdatedRETs to SFP_NotPresent
remain disabledeven afterif HWAPI
reset_x000D_
is reporting SFP Not Present and FaultId_OIC_Pres is set_x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
Description
Impact
Handling to of End-User:_x000D_
of
mode the fault:_x000D_
change notif result is not supported in 18a branch_x000D_
Missing implementation for setting voltage under VU_L according to
N/A_x000D_
_x000D_
N/A _x000D_
Impact
Summary to End-User:_x000D_
of the original problem:_x000D_
voltageRequested_x000D_
Impact
No
_x000D_service
Cat-M to Operator:_x000D_
UEor limited
validation service._x000D_
for Semi Static Repetition during
NetAct
_x000D_
reestablishment_x000D_
Dependency database SFP plugins is_x000D_
on configuration: not correct._x000D_
N/A Impact
_x000D_
Summary
Only AHEGB. to Operator:_x000D_
of the otheroriginal RF has problem:_x000D_
no such problem_x000D_
WCELL's
How
Cm
_x000D_ upload
end user/operator
Workaround:_x000D_ are failed
down._x000D_
after register_x000D_
could detect the problem:_x000D_
Attach
_x000D_ in CatM celland
Faulty component
N/A_x000D_ legacy version: UEs and _x000D_ do reestablishment with
N/A Workaround:_x000D_
UeCeLevel_x000D_
How
Summary end user/operator
MOAM_x000D_
_x000D_ of the originalcould problem:_x000D_
detect the problem:_x000D_
N/A_x000D_
_x000D_
First
Parameters
integrated
Description "idleLBCellReSelPrio",
of theBTS_x000D_
correction:_x000D_ "idleLBCellReSelPrio2CC",
Description
_x000D_
"idleLBCellReSelPrio3CC",
Faulty component
Update SFPofparameter the fault:_x000D_
first delivered
accdg. "idleLBCellReSelPrio4CC",
toin(e.g.
specificationrelease,when CD):_x000D_
SFP is not present
N/A Summary
Checks
Description
n/a_x000D_ ofofthe
"idleLBCellReSelPrio5CC",
if UE isthe original
CatM fault:_x000D_
during
correction: problem:_x000D_
their
reestablishment
_x000D_ internalValueof= UeCeLevel_x000D_
UI_value ( range from 0 to 6,
Certain
_x000D_
Full
step
Added sync conditions
1 )handling
before
don't trigger of may cause
SBTS18A_NIDD_1804_001_00(
mode due high
to incorrect
change current
notif peaks
neschedule
result for
contain
if failed toPA
which PSU
fixthis
caused which
version
0x2330 by
DSP may
BTSMED
). But
Dependency
restart._x000D_
after
cause
Impact SBTS18A_NIDD_1804_001_00,
HW failure.
to End-User: on configuration:
Runtime
_x000D_ operation
_x000D_ depends
their internalValue
on nature = of UI_value
RF signal* and 5
N/A Summary
Cat-M
(_x000D_
linearization
Norange isfrom
service ofavailable_x000D_
the
enabled_x000D_
&
0 to gainoriginal
6.8, control
step problem:_x000D_
0.2
algorithms._x000D_
). About this NIDD change, migration rules
Fault
Dependency
didn't
_x000D_ 6261
implement towards Megaplexer
on configuration:
them during SBTS18A with portNIDD
_x000D_ 49151. EnodeB is unable to connect
adaptation._x000D_
to
How megaplexer._x000D_
N/A_x000D_
_x000D_
Impact
Faulty end to user/operator
component
Operator:and _x000D_ could detect
version: _x000D_ the problem:_x000D_
N/A Summary
Workaround:_x000D_
Usually
_x000D_
N/A_x000D_
KPI degradationend of user
the original
doesn't
after power problem:_x000D_
seeoutageany problem. In certain situations there can be
and recovery_x000D_
BTS
Faulty
_x000D_ Reset
N/A._x000D_
short
How end
overcurrent
component does not
user/operator continue_x000D_
condition
and version:
could either
detect_x000D_
in startup
the problem:_x000D_
or runtime which potentially can
_x000D_
BTSMED_x000D_
break
EnodeB
Faulty
Workaround: PA isPSU._x000D_
component unable_x000D_ to
firstconnect
delivered to megaplexer.
in(e.g. release, the CD):
fault _x000D_
is visible to operator
N/A Description
Summary
In
(fault
that6261)_x000D_
N/A_x000D_
_x000D_
None_x000D_ case ofof the
faulttheoriginal
problem_x000D_
1136 isproblem:_x000D_
correction:_x000D_
typically risen and seen by end customer._x000D_
BTS
Cell
Fix
_x000D_
Faulty assignments
UIReset
and
component does not
internal tofirst
dsp
continue_x000D_
value were
conversion
delivered notin(e.g.
optimal
about causing
parameters
release, CD): problems during routing
"idleLBCellReSelPrio",
_x000D_
creation_x000D_
"idleLBCellReSelPrio2CC",
Description
_x000D_
Impact to End-User:
SRAN18SP_x000D_ of the fault:_x000D__x000D_
correction:_x000D_ "idleLBCellReSelPrio3CC",
N/A _x000D_
Summary
PA
The
How
Set PSU
Call fault
enddamage
drops_x000D_
voltage isofraised
"idleLBCellReSelPrio4CC", the original
user/operator
under due
because
VU_L problem:
tocould
overcurrent_x000D_
== eNodeB _x000D_
"idleLBCellReSelPrio5CC"
detect could
the problem:_x000D_
voltageRequested_x000D_ not establish connection with the
How
Low
_x000D_ DL
end tothroughput
megaplexer_x000D_
Attempt
Impact foruser/operator
Recovery
End-User: _x000D_ could detect the problem:_x000D_
reset_x000D_
_x000D_
Normal
_x000D_
Dependency
Netfilters
Impact
None_x000D_
Risk analysis startup_x000D_
to was on
Operator: notthe
of configuration:_x000D_
able _x000D_to correctly
correction: _x000D_treat the incoming SYN/ACK as
N/A How
Summary
No
Increase end dependency,
related,established
Description
_x000D_
n/a clear user/operator
in ofCDRthe original
how problem
(Call tcpDrops) could
riskproblem:_x000D_
connection
can detect
is higher
be the problem:_x000D_
detected_x000D_
KPI_x000D_ packet._x000D_
with high RF power_x000D_
Network
In therecovery
_x000D_
BTS
Description
Impact BTS-initiated
toconnections
of reset
Operator: software
the fault:_x000D_
doesdid not
_x000D_ not update,
work with
continue_x000D_ BTS expected
will send parameters_x000D_
notification of the removal
_x000D_
of the
FaultyCMrelevant
Dependency
Current
Workaround:
No component
hardware
upload_x000D_on SW_UPDATE_NTF_REQ
_x000D_configuration:_x000D_
graph
and version:_x000D_
usage allows inter-FSP mo to BTSMED after software
through RMOD_x000D_
N/A Description
update
Summary
Only
_x000D_ when
N/A_x000D_
N/A. Legacyis complete.
ofmegaplexer
ofthetheoriginal
fault:_x000D_
problem._x000D_ BTSMED problem:_x000D_
(mTrace)is listens on this event. Once it's received,
configured_x000D_
Reading
BTSMED
Executed
_x000D_
WTS
Dependencywaits
Workaround: boot
will
theforon stop
full-sync
mode,
DSP ato retry
which
command
configuration:_x000D_
_x000D_ respondtaskis needed
that
butforsends
it all
istooffline_x000D_
serviced
establish
the provision
sites
correct (curl
request
network
-i --noproxy
to the
parametes
BTS
'*'
repeatedly.
http://127.0.0.1:9093/debug/cacheRecoveryAll)
Faulty
WTS
FSIH/FBIH
failed._x000D_
Execute waits
Description component In
recoveryof the
for
and response
one field,
and radio
command
first BTSMED
version:_x000D_
from
should
delivered
correction:_x000D_ toDSP didn't
have
trigger before
in(e.g. receive
connection
full creating
release, such
sync_x000D_and to during
a
2 notification
result
CD):_x000D_ fora full-sync
modules_x000D_ so thatof the
N/A provision
SBTSs
Summary
N/A_x000D_ NetAct
requests
ofifthe
SHUTDOWN_RAT_TASK_x000D_
_x000D_
N/A. Legacy
SW checks wasoriginal
iswere
problem._x000D_
UE hanged.
CatMproblem:_x000D_
sent
during_x000D_
to BTS again and again
reestablishment even though the SW
of UeCeLevel_x000D_
update
_x000D_
RF
Faulty
Impactmodule
Description has
component
to filter
been
of thepower
End-User:_x000D_ done._x000D_ missing alarm on certain carrier configurations caused
and version:_x000D_
correction:_x000D_
_x000D_
How
by
Cleantoo
Impact
Faulty
Risk end
DCS_x000D_
N/A_x000D_ high/too
to user/operator
analysis oflow
End-User:_x000D_
unregister
component site
the output
first could
during powers._x000D_
delivered
correction:_x000D_ detect
BTSMED in(e.g. the problem:_x000D_
restart_x000D_
release, CD): _x000D_
N/A Execute
_x000D_
Summary
N/A endthe
N/A_x000D_
How of command_x000D_
the originalcould
user/operator problem: detect _x000D_
the problem:_x000D_
_x000D_
How
GNSSE_R
Faulty
Impact
NetAct end
Risk analysis to user/operator
component
will valuesof thenot
Operator:_x000D_
receive first
the updated_x000D_
SWcould
delivered
correction: detect
update in(e.g. therelease,
request
Safe_x000D_ problem:_x000D_
from BTSMED
CD):_x000D_ for a particular BTS
Description
Spectrum
RV
Impactobject
TL18A_x000D_
Multiple
again and
- Correction toKPIs at
contains
of
the theantenna
Operator:_x000D_
again,
End-User: fault:_x000D_
location
impacted._x000D_
effects: which _x000D_ connector
drives
N/A_x000D_ information
it to send is fluctuating
after
the SWM GPSand devicethe network
provision removal_x000D_
request doesn't
for thework
N/A All
correctly._x000D_
_x000D_
Summary
BTS.
TRX'sof _x000D_
SBTSs
None_x000D_
WCDMA
- Interface getReset of the
faulty do stuck_x000D_
effects: full-sync
original
status
N/A_x000D_ problem:_x000D_
and caused
does not performance issue._x000D_
work properly._x000D_
_x000D_
How
GTS
Impact end
crash
Workaround:_x000D_
Failure
- Customer to user/operator
was observed
End-User:_x000D_
reported effects: on N/A_x000D_
FXED couldduring detect
modules._x000D_multiple
the problem:
site reset._x000D_
_x000D_
Description
Looking
Crash
N/A_x000D_
Dependency
_x000D_
Impact occurred
toatOperator:
Workaround:_x000D_
-Test requirements:NARV_x000D_
ofon the in fault:
one
configuration: of_x000D_
fault:_x000D_
_x000D_ the child _x000D_thread (GTS-SC) of GTS as it was on
N/A Summary
DPD
_x000D_
conditional
When accepted
N/A_x000D_ full-sync
Workaround:_x000D_
mTrace
Manual ofwait
thebad
reset_x000D_
applications original
isbut models,
the
do main
triggered, problem:_x000D_
not which
threadincluded
Hcache
work._x000D_ exited._x000D_
won't positive
inform theor negative
listeners of gain, which
MO changes
caused
Description
_x000D_
Backhaul
to avoidto
N/A_x000D_
Impact the
theportoutput
how
of LED problem
notification
the
Operator:_x000D_ power
has windstorm.
correction: notocanlight._x000D_
fluctuate._x000D_
be detected:_x000D_
ddal hotplug
Hence,get BTSMED
boot mode won'tfunction
received willthewiat for
The
How
_x000D_location
end
availability
notification
Faulty
Workaround:
Description cells user/operator
component of ofvalues
that boot
with the
_x000D_
the 1868 mode
and in alarm_x000D_
GNSSE_R
relevant could
version:
register
correction:_x000D_ detect arethe
SW_UPDATE_NTF_REQ
_x000D_
before notreturn
problem:_x000D_
emptyboot after modeGPS device
movalue._x000D_
has already been
N/A Summary
removal_x000D_
Continuous
How
_x000D_
removed. end
None_x000D_
WTS
Description ofnot
This the
doesuser/operator
BTSMED_x000D_
Dependency BTS
how original
oncommunicate
makes
configuration:
problem the problem:_x000D_
site reset._x000D_
couldretry
will detect
with_x000D_
task DSP
solved._x000D_ theonce
not problem:_x000D_
to beitstopped and thus the provision
is offline_x000D_
Call
_x000D_drop
Backhaul
Risk
request
This phenomenon
analysiswill
Workaround:_x000D_
RF SW builddegradation
port be LED
of theishas
sent
FRM38.11.R23A to service
correction:_x000D_
carrier
BTS againafterand
no light._x000D_
configuration fluctuation
again._x000D_ at site._x000D_
dependant, but hard to say, which
Dependency
_x000D_
None
Faulty
configurations
Description
None_x000D_or
component
small ofon
how delay
the configuration:
configuration:_x000D_
could first
problem during
result
delivered
correction:_x000D_ in
will _x000D_
startup_x000D_
such in(e.g.
situation.
solved._x000D_ release,It might
CD):also _x000D_
be dependant on the
N/A Summary
None_x000D_
NA_x000D_
Dependency
How
Sinceend
SRAN18A_x000D_
power
WTS
_x000D_ level,
shall of
connection the
user/operator
which
proceed original
on configuration:_x000D_
iswith
tracking problem:_x000D_
could
allocated detect
forwas thethe
SHUTDOWN_RAT_TASK_x000D_
of tcp problem:_x000D_
radio._x000D_
not working properly, we put a rule to
Fault
_x000D_
N/A_x000D_
After
accept 1910
link
Description
Correction these isofpackets
being
fluctuation,
effects:_x000D_ raised
call
the correction:_x000D_
without during
quality toconfiguration_x000D_
inspecting be monitoredstate, weforrely BBon Hopping
port, IPenable
and protocol
_x000D_
Faulty
sector.
Impact
Risk
Restrict
Network component
Call
to
analysis
tuples_x000D_ hardware drop
End-User:
component of the quality
and
graph version:_x000D_
_x000D_ gets
version:
correction:
gets search
correctdegraded._x000D_
_x000D_
_x000D_
toboot
not mode allow inter-FSP
value through
N/A How
Summary
_x000D_ end
GTS_x000D_
Faulty
None_x000D_
This
DEM_x000D_
NA problem
RMOD._x000D_ user/operator
componentof the could original
andbe seen could
problem:_x000D_
detect
version:_x000D_
with the the I- and problem:_x000D_
J-branch RFSW from the first
Bandwidth
_x000D_
Description
Fault
versions
BTSMED, 1910
Risk analysis is
onwardsofincorrect
FL18SP_ENB_0000_020062_000000_x000D_
alarm_x000D_
the
SBTS19_x000D_
of the fault:
and for
also
correction: FRGY._x000D_
_x000D_ in the Nomasterrisk._x000D_ branch._x000D_
_x000D_
Faulty
Call
Impact
Risk quality
No decrease component gets
to End-User:_x000D_
analysis Operator:of the
in degraded
the first
_x000D_deliveredafter
correction:_x000D_
security. lapd
in(e.g.
Additionally linkrelease,
fluctuation
we haveCD):_x000D_
at site._x000D_
ipsec protection for such
N/A Impact
Summary
Faulty
_x000D_
Description
No
None_x000D_
SBTS17_x000D_ to End-User:_x000D_
component
connections
Low_x000D_
traffic. ofofthe the original
to fault:_x000D_
first problem:_x000D_
delivered
SBTSs_x000D_ in(e.g. release, CD):_x000D_
N/A_x000D_
Fault
When
_x000D_ 1910
FL18SP_x000D_
Dependency
RUMAG ourisSW
SBTS19_x000D_ is onbeing
setting started raised
configuration:
InvalidVSWRTimeOut
to support during _x000D_configuration_x000D_
AREA before
radio allthe
unit, carriers
problem are was
activated
in the
_x000D_
Yes.
causes This
Workaround:
RFSW._x000D_
Impact
Correction false
to issue activation
is specific
Operator:_x000D_
End-User:_x000D_
_x000D_
effects:_x000D_ of 1910to BBfault._x000D_
Hopping. At least one sector should be
N/A How
Summary
Noneend
configured
_x000D_
Impact
Longiture/latitude
Cells
N/A_x000D_will user/operator
to not ofwith
the original
End-User:_x000D_
Operator:_x000D_
come BB could
problem:
Hopping._x000D_
values
up and is site detect
empty may _x000D_
ongo the
BTS problem:_x000D_
for additional
SM._x000D_ reset as a recovery
Fault
Validation
N/A_x000D_
_x000D_
Dependency
Not
Impact 1910_x000D_
possible
action._x000D_ error
to End-User: to reported
onconfigure when
configuration:_x000D_
_x000D_ more actRedFreqOffset
than 40Mhz bandwidth = 'true', with redFreqOffset
FRGY while = 9.3
_x000D_
and
Faulty
GSM
No ulChBw
according
Workaround:CELLS
component
service
Description of= 20 MHz._x000D_
toavailable
CuDo,
with
_x000D_
the BCCH
andFRGY version:
_x000D_ antennas_x000D_
correction:_x000D_ supports _x000D_ up to 60Mhz._x000D_
N/A Description
_x000D_
Summary
GTS
Provide and
None_x000D_
Impact ofofthe theoriginal
fault:_x000D_ problem:_x000D_
SBTS18A_ENB_1000_001245_000001_x000D_
tocommand
Operator:_x000D_ to recovery programmatic SBTSs hcache _x000D_
Description
In thewill
_x000D_
Impact
Cells
Physical
NetAct BTSMED
Workaround:_x000D_
RUMAG tois
will ofcome
backhaul
not
Operator:
receive the with
End-User:_x000D_
setting problem:
port
up
the the and
_x000D_ LED
SW SBTS17A's
InvalidVSWRTimeOut _x000D_
site
shows
update mayrequest no
goversion,
forbefore in BTSMED
light._x000D_
additional
from A -S
all mode
carriers
reset as
for ,when
are triggerBTS
activated
recovery
a particular the
PDL
BTSMED
againcoding
Impact
WCDMA
N/A_x000D_
causes
Description
action_x000D_
_x000D_
Risk
AREA to
false
analysis
and
module failover,the
and error_x000D_
End-User:_x000D_
of
again, activation
GSM
the
of pm
service
correction: of
malfunctionning_x000D_
thewhich correction: do
1910
drives the fullsync
impacted._x000D_
fault._x000D_
_x000D_
it_x000D_
to send the mechanism
SWM provision , it probably occurred
request for that
N/A _x000D_
send
Summary
DEM pm
Workaround:_x000D_
GSM updates
BTS._x000D_
Safe_x000D_serviceduplicated
of the qualityoriginal
values file to
problem:_x000D_
the nectact._x000D_
iscorrectly_x000D_
impacted (Call drop degraded once problem is
How
_x000D_
LTE
Impact cells
end
Description
Dependency to user/operator
Workaround:_x000D_
N/A_x000D_
occurred)._x000D_
Workaround: down post
Operator:_x000D_
ofon the SRAN18Acould _x000D_
configuration:_x000D_
none_x000D_correction: detect
1.0.2the upgrade
problem: with_x000D_
alarm 1868 'Not Enough
Description
Hardware
Now
GSM
Through
'alarm itCELLS
N/A_x000D_
_x000D_ is
1910
Workaround:_x000D_
Correction
This is hard of of
specific
possibleLCR'
RF
how the
with fault:_x000D_
_x000D_
Module
configuration._x000D_
to
BCCH
problem
effects:_x000D_
to avoid configure
as itFilter
antennas_x000D_
will
happens input
up torandomly
solved:_x000D_power
60Mhzmissing' bandwidth
and is present.
very with FRGY.
WCDMA
situation and
dependant
Since
_x000D_
GSM
Description
Impact
N/A_x000D_
-Interface
(carrier
GNSSE_R BTS
cells
to reconnect
from FXDB
Operator:_x000D_
of the
configuration,
effects:
values areto 900 theMhz
correction:_x000D_
N/A_x000D_
temperature
ok btsmed.When
areetc.)_x000D_
down._x000D_ do the fullsync mechanism ,it will
occurs
How
_x000D_
Impact
For
GSM end
Description pm
to user/operator
configuration
-Customer service duplicated
End-User:_x000D_
how theproblem
ofquality
effects: with isfile could
to
can
correction:_x000D_
old
impacted
N/A_x000D_ transfer
detect
be (Call
transport to
the
detected:
FRI the
dropproblem:_x000D_
will NectAct._x000D_
_x000D_
degraded
not handleonce EIF1problem
connector is
_x000D_
While
N/A_x000D_
Configure
Whenever
type._x000D_doing
occurred)._x000D_
Workaround:_x000D_
-Test requirements:
Description SBTS
actRedFreqOffset
site
of reset
the upgrade
happens,
correction:_x000D_
N/A to= SRAN18A
'true', redFreqOffset
LIM/LIBOAM 1.0.2,
calls wethe observed
9.3 and that
= teardown random
ulChBw
function = of20all
Dependency
Cells
_x000D_
New
In the are
MHz._x000D_
the
N/A_x000D_
registered
DPDcode goingofon
parameters
thedown
configuration:_x000D_
retryand
components. are
task, theySince recover
introduced
add GTS
the forpost
logic to doing
isAREA
also rollback_x000D_
registered
RFSW
detect component,
the ,existence
which tellofthethein
DPD the
_x000D_
Impact
No_x000D_
Risk
Workaround:
not
relevant toSW_UPDATE_NTF_REQ
toanalysis
teardown accept Operator:_x000D_
_x000D_
function,of the
this kind correction:_x000D_
explicitof bad callmodels._x000D_
to stop mo.ofIfthe thischild
mo has thread been is called to breakthen
disappeared, the
Dependency
KPI's
Description
_x000D_
Safe_x000D_
Reset
conditional
stop the affected_x000D_
of retry
thewait on
ofsite
the
task configuration:_x000D_
fault:
will
for correction:
recover
graceful _x000D_
itself._x000D_ the
_x000D_
exit ofissue. No workaround to avoid the
thread._x000D_
N/A Summary of the problem:_x000D_
Plan upload failed caused by BTSMED cache lost after upgrade from
SRAN18A MP1.2 to SRAN18A MP1.3_x000D_
N/A _x000D_ of the original problem:_x000D_
Summary
Technical
SW upgrade description
fails_x000D_of the fault:_x000D_
After
_x000D_
the BTSMED upgrade is completed, the BTS cache data which existed
in BTSMED
How end user/operator
restore failed could
during
detectBTSMED
the problem:
startup._x000D_
BTS cache data recovery
depend
Site doeson not
the work
pluginand load,internal
but before
logs show
BTS cache
'1806 Communication
data recovery, plugin
failure'
load
hasn't been
reported in SMOD
completed.and '10 BTSMED
No connection
don't make
to unit'
somereported
startupinservice
RMOD,sequence
then also
'4019 BTS site autonomous reset as recovery action' reported before these
right._x000D_
two faults in alarm history_x000D_
_x000D_
_x000D_
Dependency on configuration: NO_x000D_
Description
_x000D_ of the fault: There is a deadlock scenario, between two threads
Faulty component
(configuration and andEvent) version:
in TPLBTSMED
task. Problem
18A_x000D_
can occur during runtime. but
_x000D_
was only seen when the system was upgraded or rebooted. _x000D_
Impact to End-User: none_x000D_
_x000D_
_x000D_
Dependency on configuration:IPSEC should be enabled for the problem to
Impact to Operator:_x000D_
occur._x000D_
No
IPSEC
plan is
upload
one ofpossible
few modules after BTSMED
which calls upgrade
TAS handlers
from SRAN18A
as part ofMP1.2
the to
SRAN18A MP1.3_x000D_
Configuration. _x000D_
_x000D_
Workaround:_x000D_
Faulty component and version: FTM_x000D_
1. reset SBTS_x000D_
_x000D_
2. fromcomponent
Faulty BTSMED run firstcommand
delivered in(e.g.
line forrelease,
BTSMED CD):
to recover
SRAN18A_x000D_
cache for a
_x000D_
specific mrbts:_x000D_
Impact to End-User:
curl -i --noproxy loss of service after upgrade_x000D_
'*' http://127.0.0.1:9093/debug/cacheRecovery/mrbts-
_x000D_
350237_x000D_
Impact
_x000D_ to Operator: upgrade fails. BTS site reboot is needed_x000D_
_x000D_
Description of IPSEC
Workaround: the correction:
can be disabled_x000D_
_x000D_
check the MO amount during cache persistence and restore to cover some
_x000D_
exceptional of
Description sceniros
the correction:
, if not matched,
The configuration
trigger fullmanagement
sync._x000D_ thread doesn't
_x000D_
invoke the TAS handlers and the TAS handlers are invoked only from events
Test requirements:_x000D_
thread _x000D_
1.
AsUpgrade
the Config of BTSMED
thread is not frominvoking
SRAN18A the MP1.2
TAS handlers
to SRAN18A
there will
MP1.3_x000D_
be no
2. operate
instance when
CM Upload
TAS thread to check
is stuck
if plan
dueupload
to a deadlock_x000D_
is successful
_x000D_
Risk analysis of the correction: SAFE_x000D_
As the code has been made thread safe now, there should not be any
deadlock scenarios._x000D_
Correction effects: there should not be any functional impact due to the
correction_x000D_
-Interface effects: NA_x000D_
-Customer effects: NA_x000D_
-Test requirements: NA
 (Component Version
/ Net element / SW-
Corrected Fault ID Corrected Fault Name type / Unit)
PR388580,PR390476,PR3 [SBTS18A][Airscale][PET] flooding error SBTS18A_PHY_RX_
90744,PR392719 "PHY_PuschReceiveGroupedRespU was not received 0000_000002_000000
in expected time for" for NB IoT traffic,[SBTS18A] 269137
CAS-185055- [Airscale][PET]
[SRAN18A NPI]UL
: flood
PHYofFATAL
alarm APPLICATION
7115 "Failure inERROR BTSMED e8e281
R8P9,PR385048 Nid:0x1251 between
connection handle_tcp_isr:193
BTS and iOMS TCP orciritical
3rd party
interruption!
tool" Not in CCL
P0 errors:
after upgraded
0x00000002
to BTSMED18A
| P1 errors:
0.0PD,[BTSMED][18A]
0x00000000! ,
CAS-187240-S3L9 [FL18A][AirScale]
[PET]BTSMED
[SRAN18A NPI]can't
corrupted
Nb-Iot
decode
RRC
alarm
Trace
SRfluctuating
isMessage
at loweron level
due
AHCA
to
after RFSW_FM-556
SW upgrade,[FL18A]
NBS
duringsend
commissioning
so fast [Airscale]
of site [AHLJA] [NB-IoT] DSP FRM58.11.R07I
Crash (4341), Baseband autonomous reset (6709) Not in CCL
PR395225 [SBTS18A]Unexpected fault 4001 on WCDMA after DCS 77043 Not in
Upgrade CCL

CAS-187523-D0D8 [SRAN18A NPI] validation error when trying to activate PDL 1509 Not in
LTE3145 slim carrier on FXDD radio CCL_x000D_
WebEM 25817 Not in
CAS-184979-S9K5 [SRAN18A NPI] NBIOT has a lot of RRC reject RX_PHY 271061
CCL
Not in CCL

CAS-174810-H0Y4 AMOB FAN Unit for cooling running on High speed and BM
generating lot of noise. SM18AC5_RP_BM_1
809_001_01 Not in
PR396047 SRAN18A: SBTS in commissioned state after SW CCL
FB1809_SM18AC5
upgrade 0e1f017

PR392131 FSP-13 crashes when fetching snapshot in a continuous CP_LRM 694324

loop with HL 3RAT traffic Not in CCL

PR396281,PR396704 [OAM_SCT][SBTS][FDD][xL18A][R44][R4][SMOKE] FB1809 b83dab1

[fromBB][SMOKE_TOP] Commissioning - FaultId: 4341; Not in CCL
Number: 7101; Name: BTS secondary core autonomous
CAS-171777-Q7T1,CAS- resetCase-UPE_TRXs
BTS as recovery action,[SISO][Automated][RealHW]
of Multiple BSC's getting stuck, GTS 16031 Not in
185755-Z0B2 [Airscale][SBTS18A]RM's
[NPI SRAN18SP] BCCH alarm not detected
is not visible
in expected
in element
time CCL
Manager even decline in KPI can notice . Block .-
CAS-177600-S6V3 RANDOM
unblock solve
2G SECTOR
problem GOING DOWN IN SRAN BTS GSM DSP, Tel
Commit Not in CCL
Not in CCL
PR395916 [SBTS18SP] Error Handler exception after snapshot SYSADAPT 65612
was triggered.

CAS-118399-C0W8 RF module failure and Transmission path failure in BTSRFM-93848

stadium L26 FRM36.07.R46T
Not in CCL
CAS-146398-B6X3,CAS- 2G KPI degraded after SRAN17A 1.1 GTS 16032
BTSRFM-93848Not in
169722-H5W8 implementation,SRAN18_SBTS - Counters FRM36.07.R48T
CCL
TCH_RF_OLD_HO and BSC_O_DROP_CALLS Not in CCL
CAS-159026-J2V8 [FL18 Drop6.0
increased after _FFA]:
SRAN18 ULactivation
noise (PUSCH and PUCCH), bstat 32593
BTSRFM-95904Not in
RSSI and SINR degraded on 16 eNB and 77 eNB CCL
FRM36.07.R49T
clusters with Correction for LTE 3577 Predefined Not in CCL
CAS-163716-H5Y8,CAS- RTWP values shift seen on 3G cells after swapping to RFSW
180531-X2P1 new RM AHEGA,Reduction of UL RTWP after upgrade FRM58.11.R05I
WCDMA18 to SRAN18SP with radio unit swap to Not in CCL
CAS-164134-T9D2 AHEGB
2,5 times increase in TCH drop rate after SRAN 17A GTS 16032 Not in
upgrade CCL

CAS-166574-T5R2,CAS- SRAN18SP NPI: Propagation delay variation on RFSW_FM-630

166624-G1T4,CAS- AHEGB hardware,SRAN18SP NPI: 3G - Radio Link FRM58.11.R09I
180529-W4C8,CAS- Failure increase after swaping old RM to new Not in CCL Not in
CAS-171060-D7N0
180533-F7D9,CAS-182483- multitechno AHEGA/AHEGB
SRAN18SP NPI: Alarm 7745 modules.,Change
CHANNEL FAILURE of CCL 16075
GTS Not in
X0K4 PRACH
RATE ABOVE
propagation
DEFINEDdelayTHRESHOLD
distribution after
raised
WCDMA18
for TRX3 CCL
to SRAN18SP
(site 1035BB) with radio unit swap to AHEGB,Increase
CAS-176204-S6T7,CAS- of the number
FL18SP FSA (GA2)
of Radio
84429
LinkUHFA
Failures
14,24,34
with cause
cell down : MOAM 131427 Not in
179060-S9P3 alarms
‘Radio7653 and 6253,FL18SP
Network FOA 131001
Layer' after upgrade WCDMA18: 3 cells
to CCL
remained
SRAN18SP down
withafter
radiopower-on
unit swapreset / ABIA reset
to AHEGB,SRAN18SP
CAS-177093-Z0R5 Dualband RRH (AHLBA
NPI: Propagation and AHFIB)
delay changed afterPIM Cancellation
upgrade fromRFSW_FM-399
introducing
SRAN18 MP1.1noisetoinSRAN18
FL18 GA3 MP1.2 on AHEGB RM's FRM58.11.R03I
Not in CCL
CAS-177330-D2F1,CAS- [FL18A Drop2_FFA]: MAC PS 504085
186415-N8J8 VS_RRC_reconf_CA_deconfigure_fail_rate increase by Not in CCL
50+% with attempt increasing by ~30% on FL18A
drop2,[NPI][FL18A] active 4CC Ue's are reduced after
Upgrade
CAS-177536-M0D5 [PM Counter][FL18SP LAA][PM]Site AT0216BA sect 8 RFSW_FM-733
carriers 1&2 DRS success=0 FRM58.11.R14I
Not in CCL
CAS-180035-T1V8 SBTS\RF Module gain adjusting failure\TT- BTSRFM-96851
000040144761 FRM38.11.R05A
Not in CCL
CAS-179301-W4J0 Incorrect alarm time FRI 26219 Not in CCL

CAS-181904-G2Y7 FL18A FOA: BTS Autonomous Reset is performed due RROM 690007 Not in
to RROM crash (4383 Virtual node not responding) CCL

CAS-181951-P2F8 Not be able to open SRAN Element Manager from FRI 27568 Not in CCL
NetAct Monitor for 3G WBTS part of SRAN SBTS17A.

CAS-182333- FL18A_FSA_131415: multiple AHIFIC RFSW_FM-495

H6Y1,PR391899 EFaultId_UnexpectedRadioReset observed, FRM58.11.R02I
[FL18MP3.1][CRT][FSMF] AFHIB recovery fails during Not in CCL
CAS-184145-T3L9,CAS- FL18A
CRT run (WDC
FL185G 3.1,FOA): Counterdue
cell disabled M8006C332 is orders
AFHIB lost with UEC 696278 Not in
184836-D9Y4 of magnitude
alarm bigger
0010 failure in than M8006C333,[5G_IW][AT&T]:
optical interface CCL
ERAB_STP_ATT_MCG_NR_PDCP (M8006C332) over-
CAS-185460-Z6P2 NPI SRAN18SP - Plan provisioning is failed due to PDL
pegging ScfValidator 8990
validation failure Not in CCL

CAS-186933-K9C6 S1-Connection Establishment Success Ratio for NB IoT MAC PS 509066

UEs problems after going to FL18 Not in CCL

CAS-187625-L0P8,CAS- [TL18A pilot][PM Counter][M8001C5][FSIH+FZFF-e] UL LTEL2 773725 Not in

188304-M4L5 latency increased after upgrading,,[NPI][FL/TL18A]UL CCL
latency is degraded in Both FDD and TDD after FL18A
CAS-188856- upgrade
NPI SRAN18SP - Plan provisioning failed due to picPool PDL 1458 Not in
Z0T4,PR398426 assignment,SBTS19_FSM4_9999_181209_011513:Har CCL_x000D_
dware errors info show in 3 pic configure about 24 cells WebEm 25590 Not in
CAS-189313- Alarm 10:Failure in optical interface seed after FL18A CCL 136782 Not in
MOAM
P4Q1,PR394570,PR39605 Drop3 upgrade,Fault 10 reporting on AHPMDA after SC CCL
1 autonomous reset,WCDMA on-air, LTE integrated to
CAS-190202-K4M8,CAS- [FOA][FL18A][0.9PD][KPI]
ran, GSM commissioned after HighSWAFRupgrade
and ERAB drops, LTEL2 768897 Not in
193281-C8Q1,CAS- [FL18A Drop5_FFA]: Traffic increase with accessibility CCL_x000D_
195351-D6F5,PR393731 degradation several hours after AZL00219 upgraded to LTEL2 768921 Not in
CAS-190857-B2G5 FL18A
2 LAA cells
drop5,[NPI
remainedSRAN18A]
down after
ERABSF
FL18A isGPLobserved
application
on MOAM
CCL 138446 Not in
sites
on 084006
after some time,WRN/LTE CCL Not in CCL
L2/TeidManager/c3FCDrB197u1E35x4C5l1F/updateTei
CAS-191485-W2H2,CAS- 2 dMapInternal:
out of 3 cellsteid
on AHFIB
alreadyradio
in usedown after SU to MCtrl 68688 Not in
192910- Drop5,Enb Invalid frequency channel for the BTS HW CCL Not in CCL
X2F5,PR396085,PR398121 (1807) after upgrade to drop 6,Alarm 1807 reported
CAS-191826-T2D1,CAS- after SW
OAM stuck
upgrade,AHFIA,
state after change
configuration
cells 1/12/14
errorfrom
1807
2T4R
after MOAM 138120 Not in
192029-N8B8,PR396444 SW2T2R,after
to update 5 days all radios became disable (no CCL
service) and BTS Site Reset could not be performed to
CAS-191935-P2C0 Plan provisioning
recover,RRH doesfailed due to BTS
not recover after didn't
reset respond to SYSADAPT 65449
provision request within 270s Not in CCL

CAS-192259-X7D7,CAS- Ref: EME - S182/BTS going in unsync state in CONVENG 7934 Not
193491-Q3Z6 BTSMED,Unable to perform parameter modification in CCL Not in CCL
remotely from NetAct using XML plan
CAS-192423-K8L6 Cannot provision lower bandwidth e.g. 4.4Mhz in TX for MOAM 138383 Not in
FXDA CCL

CAS-192764-L5Q8,CAS- SBTS can not activate Lean GSM Solution feature.,no BB

194620-N8B4,PR399619 GSM signal after enable CMST,No Downlink I63ae6327f4616eeca2
Transmission happened on AHDB RRH While Lean fe23350026c3f0a3104
CAS-193479-N3C3,CAS- NPI
GSMSRAN18SP
feature on enable.
- WebEm poor perfomance during 5bb 1583
PDL Not inNot
CCLin
195853-B7R5 configuration validation,OAM : SBTS18SP very slowly CCL_x000D_
to provisioning plan or change parameter on some sites webem 26435 Not in
CAS-193620- whether provision
LA03XC094 BETA-via Warning
CMoperation
Alarm or 7101
direct
fault
access
6706,via CCL
FB1809 c8dfd43
L4V7,PR397166,PR398044 4019,
Monitor.1815],WCDMA CELLs stuck in proceduralState Not in CCL_x000D_
,PR398491,PR399281,PR3 Prevalidated after RAT reset WCDMA,Baseband card FB1809_SB18AMP0 -
99671,PR400803,PR40081 eNB
CAS-193707-H4B9,CAS- autonomous
had Spurious
reset as
reset
recovery
during action
SU to (1806)
PT4.4,spurious
after site MOAM Not
138120
in CCLNot in
6,PR403388
193872-S1K1 unblock,Cells
reset after SWActivation
left disabledcells
after
went
RATout autonomous
of service 30 CCL
reset,All
mins afterRATs
upgrade
goestofor
PT4.4
reset during WCDMA RAT reset
CAS-194092-X7K7 from Admin
STBTS faultand
"topSlavePort
WCells arevalue
stuckisinout
'Integrated
of range"to: ref FB1809_SB18AMP0
RAN'.,All WCDMA
Emergency S182 | cells
CAS-191904-N6G6
stuck in "Commissioned" State 8f6a01c2f79abf6644a
after new WCDMA cell addition,GSM and WCDMA 10f51f08471973cd462
disabled after WCDMA RAT reset ,RAT reset LTE c3 Not in CCL Not in
failed,modify 'qosSchedList' the GSM RAT and WCDMA CCL
RAT have restart and GSM cell & WCDMA cell not on
air
CAS-192826-W8R4 [NPI SRAN18A] sIntrasearch wrong value after Migration Rules 26945
conversion to SRAN18A Not in
CCL_x000D_
PR394579 [RP001614][SBTS18A] RET device powered off after ADMIN 26496
Migration Rules Not
26560
in
upgrade from WBTS18 to SBTS CCL Not in
CCL_x000D_
PR393527,PR397053 [SBTS18SPMP2][R4][LTE][RP000375]Syncronization WebEM
DEM 30275
25401 Not in
source switching between 2 SyncE sources is not CCL
CCL_x000D_
working,[SBTS18SPMP2][R4][LTE][RP000375] SyncE ADMIN 25438 Not in
PR387200 Syncronization
[RP1780 DROP2] source
Transport
is not layer
takenconnection
in use afterfailure
BTS in CCL_x000D_
HAS 20327_x000D_
reset
S1 interface
when 2(6202)
syncE is
sources
raised when
are in priority list. DEM 31021
MOAM 138708 Not in
caClusterMemberId=4 CCL_x000D_
PR390037,PR393027,PR3 [OAM_SCT][SBTS][FDD][trunk][R44][SMOKE] Startup DEM 77660
DCS 31940 Not in
93083,PR399199 time exceeded durring Site reset for GSM,[SBTS18A] CCL
[FSMF+FSMF] All cells hosted by AHFIB disabled after
PR388979 primary link removal,[SBTS18A][FSMF+FSMF]
[SBTS18A][FSMF+FSMF][RGT] SRIO LED is gray Fault FRI 26819 Not in CCL
4261 reported
(OFF) on SC (ESM)
for LTE
module
cell after
after
startup
domain with
collision
1 CPRIislink
missing,[CRT][LBT3366][FSMF][LTE-LTE]
resolved
PR391825 [SBTS18A][ASIA]MO
[SBTS18A]RF SharingTOPF_R-1 disappeared
- No cell goes OnAir afterafter
CSDsite DEM 30264 Not in
reset
Cablink Hot Remove CCL

PR390287 [SBTS18A] can't modify lcrid via ADMIN (greyed out) ADMIN 25588 Not in
CCL

PR394178,PR394888,PR3 [Airscale-FSMF][FL18A-GF18 2.0] EEPROM read error MOAM 135670 Not in

95344 (2078) alarm during '100 LTE Site reset' test,[SBTS18A] CCL
[DualCore]Unexpected Fault Id 2078- "Eeprom read
PR391923 error" raised during LTE RAT reset_parameter
[SBTS18SP_P7][CIT][FSMF+FSMF]BTS site change, SYSADAPT 64349
[FL18A][Airscale+3*FRGU+FRPA+2*FXED+3*FRHF]
autonomous reset as recovery action after software Not in CCL
update
[RFS][OAM]BTS report 2078 alarm about "Eeprom read
PR390810 [SBTS18A]
error" Unexpected radio module type can be MOAM 134721 Not in
added from Wizard CCL_x000D_
ADMIN 25334 Not in
PR389133 [SBTS18A][FSMF+FSMF][CR2] Wrong transmission CCL 29730
DEM Not in
distance of RP3-01 connection between SMODs CCL_x000D_
DEM 29940 Not in
PR389194 [CRT][Admin][SBTS][FDD][SBTS18A] Cannot log into CCL_x000D_
ADMIN 26110 Not in
Admin using Google Chrome browser DEM 30376
CCL Not in
CCL
PR390382 [OAM_SCT][SBTS][FDD][xL18A][R44][SMOKE] MOAM 135624
Not in
Commissioning - LTE cells in Validated state - faultID: CCL
4261 visible
PR390397 PortMode parameter value missing after upgrade 18SP Migration Rules 26369
to 18A Not in CCL

PR393309 [SBTS18A] [R3,R4] [RP000384]topFreqSyncSLS HAS 18778 Not in

(M51361C4) counter value is too low CCL

PR393975 Confusing warning "Parameter relations not met" ADMIN 26049 Not in
appears after setting distRefPoint parameter in CCL
TIMINGGROUP MO
PR390368 Inconsistency between reported alarm for fault 23 and FRI 26418 Not in CCL
state of cells on BTS after use of RMOD (AHEH) with
FDSW.
PR391481 Unexpected fault 4341 after BBMOD hot removal FB1809 978e8ab
Not in CCL

PR391524 Fault 145 is not cleared in one of LCGs when resources wts 18530 Not in CCL
for PIC become available.

PR393862 Fault 6261 contains wrong description FRI 26528 Not in CCL

PR394374 [SBTS18A][RGT]FEG is not correctly calculated for DEM 30963 Not in

AHPMDA radio modules after PASSDEV removal CCL

PR394485,PR395006,PR3 [SBTS18A][FSMF] Crash during snapshot,[FL18A] SYSADAPT 65246

95916 [AirScale][CSV-SH]Spurious bts reset show in blackbox, Not in CCL
[SBTS18SP] Error Handler exception after snapshot
PR380934,PR396716 was triggered.
[SBTS18A][Regression] Fault 4076 is not reported on FRI 25048 Not in
FRGU and FRGP.A whan 'actDistributedSite' is set to CCL_x000D_
'true' and RFs are connected by long fibers.,[SISO] fault_4076_EFaultId_
[Automated][RealHW][Airscale][SBTS18A] 4076 fail DistributedSiteSupport
appear despite actDistributedSite parameter set true NotEnabledAl.vsd
16657 Not in
CCL_x000D_
MOAM 134165 Not in
CCL_x000D_
PR381691,PR394421,PR3 [SBTS 18A]RF module failure is raised on WCDMA cells WBTS_APPS_20333
95151,PR395368,PR39556 when configuring cell set of the CNI,[FL18A][FSMF] 1.0 Not in
0,PR395734 [GENERIC][Hangzhou_CST]cann't activate LTE4212 CCL_x000D_
PR385937,PR386130,PR3 due to parameter modification
[SBTS19][FSMF][AHDB] SBTSfailed,[LTE2745][LTE]
Stuck in Commissioned MOAM MCtrl 68050
135396 Not in
86135,PR386518,PR38684 [FDD][Airscale][FL18A][ET][OAM_SCT]Second
State after Site Reset,[SBTS00][Legacy]BTS acted the CCL_x000D_
4,PR387511,PR388123,PR reconfiguration
RNW plan file too is stuck
long time,[TL18A][LTE4630-C]
on activating parameters, MOAM 135395
135724 Not in
PR394400
388602,PR389299,PR3899 [SPRINT][FL18A][1.0PD][Airscale][Irving]
[mMIMO]
[CNI-24657][SBTS18A]
[AirScale+AAHC] [Dualcore]
Configuation
Criticaldata
cannot
faultmissing
4083 CCL 20019
swm Not in
09,PR396749,PR396863 change
after
visibleBTS
inradio
EM
reset,[L18A]
after
configuration
successful
[Airscale+FZFI+FZHR+FZHN]
to fallback
4T4R Closedprocedure.
Loop MimoCells CCL
4x4,[LTE4500]
[LTE3839-A-b]
operational state:
HW
activate
Disabled
configuration
parameters data
failed
missing
whendue import
to
PR394413 SiteConf
SRAN18A: build
SingTx related IP connectivity
failure whentest
sitetriggers
startup,TOP alarm and DEM 30491
delta file,[FL18A][OAM] Not in
[SBTS18SP_2.0][R4][LG][SBTS
sync is lost
[ASIA+ABIA+AHEGB] Regression]:
active parameter failed Site
afterstuck CCL
in "Commissioned"
change configuration state when fresh commissioning of
PR394525 site is done with unconfigured radios connected.
[SBTS18A][RP002128][FSMF+FSMF] WCDMA cell ,[SISO] DEM 30480 Not in
addition causing extension reset fault 4114 stuck
[FHS][MDEA][FL18A][Airscale][LTE3331]BTS CCL_x000D_
during reset after commissioning,[Airscale][FDD][FL18A] DEM 30771 Not in
PR394631 [SBTS18A][Regression]
[LTE3656]MDEA cannot Cablink between
be detected afterSMOD
BTS reset an on MOAM
CCL 136279 Not in
RMOD is not correctly detected on uncommissioned
build FL18A_ENB_0000_000252_000000 ,[FL18A] CCL
BTS with long fiber in use.
[AirScale][PET][AHBCC] Failure in optical after SW
PR390270,PR394627,PR3 [LTE2745][LTE][FDD][Airscale][FL18A][ET][OAM_SCT]
update,[SBTS18A][DualCore][VR] Fault 4352 after non- MCtrl 67735 Not in
94760,PR394765,PR39491 Failure in replaceable
commissioned RMOD baseband
removal and unitBTS
(2019)
siteafter
reset.,hot CCL_x000D_
0 swap with signifficant difference of fiber lengths,
[SISO][FL18A][AIRSCALE][MDEA][LTE3331] MDEA is SOAM_MCI 15858
PR393747,PR394786,PR3 [OAM_SCT][LTE][SBTS][FDD][TDD][trunk][18A][R4]
[SBTS18A][AirScale+AirScale][RP2128]
not detected after Reset Site,[SBTS18SP] LTE and Fb1809 c5d9162
Not in CCL
97022 [R44][2078][fromBB][SMOKE]Eeprom
WCDMA cells in incorrectUnexpected
[QT_branches][Airscale] state after hot read
swap
Fault error,
ID from
10 is Not in CCL
[SBTS18A][FSMr4][CRT]
radio
raisedOBSAI Fault 2078 reported
to radio CPRI,[SBTS18A]GSM
after startup,[TL18SP][LTE4630-A-b] after
dropped
[AirScale]
PR394924 [SBTS18A][FSMr3][FRHB]
after
SBTS
[mMIMO]SCblock
hot
RRU Cell Power
unblock,[QT][SBTS00][FSM4][AG]andFailure
insert/remove,[SBTS18A][RP002128]
cannot be detected (Fault up DCS 77654
All RATs
0010 raised Not in
ID:4090,
[FSMF+FSMF]
in Alarm After
Commissioned ID:7116)
state
radioafter
after configuring
changed
SW dl_act. Supplemental
fromAlarm
OBSAI 7100
to CCL
Downlink RMCarrier
CPRI,2078)
(fault is doeswithnot 3CC DL Carrier Aggregation
operational,[OAM_SCT][SBTS]
PR395257 LTE2557,
[SBTS18A][Admin]The
LTE1804
[FDD][xL18A][R44][SMOKE] snapshot exported from
Commissioning Site and ADMIN 25742 Not in
- GSM
View
LTE Notdoes not provide
OnAir the full content
- availabilityStatus of the existing
- Failed CCL
configuration
CAS-167022-G7V0 ETR-000096376: Pay per incident: On some SRAN SS_HSCH 698110
WBTS we observed cases of HSPA power loss. Not in CCL

CAS-178651-L9L5 Iur drop call_SBTS Local Telecom

145628 Not in
CCL_x000D_
CAS-182225-T9M7 fallas en SBTS con 16 sectores Rake Receiver
CP_LRM 699879
145629
Not in CCLNot in CCL

CAS-183567-V2M8 [FL18SP_ENB_0000_000732_000000] 2nd chain cell FRI 28050 Not in

became disabled after applying object locking CCL_x000D_
parameter when 1st chain cell (FHCA) faulty MOAM/RUMAG
CAS-187047-V7D9 [FL18A Drop3.0 _FFA] Multiple sites reset with fault 140747
UEC 699492
Not inNot in
4383 CCL_x000D_
CCL
fault_1912_EFaultId_
CAS-188355-P1R1,CAS- SRAN : cannot collect snapshot with BTS busy,NPI FrOutOfOrder.vsd
SYSADAPT 67084
193483-F4K1 SRAN18SP - Snapshot collection failed 19637
Not in CCLNot in CCL

CAS-190202-K4M8,CAS- [FOA][FL18A][0.9PD][KPI] High AFR and ERAB drops, LTEL2 777858 Not in
193281-C8Q1,CAS- [FL18A Drop5_FFA]: Traffic increase with accessibility CCL_x000D_
195351- degradation several hours after AZL00219 upgraded to LTEL2 778454 Not in
CAS-192187-X6P1
D6F5,PR393731,PR403706 FL18A FOA - 131016/131048
drop5,[NPI DSP reset/Cells
SRAN18A] ERABSF downon
is observed MOAM
CCL 139690 Not in
after
sites Download
after someof FL18A PT4.3 (site running PT4.2)
time,WRN/LTE CCL_x000D_
L2/TeidManager/c3FCDrB197u1E35x4C5l1F/updateTei MOAM 140677 Not in
CAS-193419-G5N3 [SRAN18A
dMapInternal:NPI]
teidSleeping
already Cell on,[PET][LTE4135][SFN
in use SRAN18A NB-IOT SBTS18A_MP0.X
CCL
site
2cell][3 ANT][FLF18A_ENB_0000_000651_000000] 510327 Not in CCL
SFN master crash during TM Extreme test with fault
CAS-193479-N3C3,CAS- NPI
6708SRAN18SP - WebEm poor perfomance during PDL 1583 Not in
195853-B7R5 configuration validation,OAM : SBTS18SP very slowly CCL_x000D_
to provisioning plan or change parameter on some sites webem 26435 Not in
CAS-193535-K6S8 Cell disabled
whether provision
due toviaunknown
CMoperation
reasonor direct access via MCtrl 69638
CCL Not in
Monitor. CCL

CAS-193970-Y4T3 SDU Data Volume counters for CAT-M Profile is LTEL2 777338 Not in
showing very large value after FL18A - gpl application CCL

CAS-194783-Y9W5,CAS- [mMIMO] [FIT] TL18A NPI mMIMO: Special subframe 6 MOAM 139675 Not in
194818-G4H5 feature can not be activated with AAHE MAA,[mMIMO] CCL_x000D_
[FIT] [LA73XC730A - After SSF6 Activation on AAHC, meta 12327 Not in
CAS-195511-K8C2 cells aretonot
Unable configure
coming UL
up]CA for LTE3864_UL CCL_x000D_
UEC 702385 Not in
CA_5B_10Mhz+5MHz combination. MCtrl 69707
CCL Not in
CCL_x000D_
FRI 27989 Not in
CCL
CAS-196258-S2W8,CAS- More than 100 BTS's self restarted,208_2G sites and BM
196391-K4V8 218_3G sites in multiple BSC/RNC were down SBTS18A_ENB_1000
_000623_000102
CAS-197493-R0Y3 NPI SRAN18SP - Diagnostic Files collected (6450) - FRI in
Not 28226
CCL Not in CCL
FRI crash

CAS-198001- [FL18A_D5.1_RLab] - Cells down and operationally DCS 79722 Not in

Y3G9,PR401186,PR40322 unstable after resetting eNB having LAA configuration, CCL
6,PR403290,PR403304 [FL18A][AirScale][Stabi][0.5PD][UUF]Clear Channel
CAS-198657-H8T9,CAS- Assessment
[FL18A Drop3_FFA]:
Reports Sites
Not Received
AZL06321 (6125)
and reported
AZL06181 on SBTS18A_MP0.X
199047-B1M7,PR405827 AZRAshared:N;DSP
have after upgrade group
to candidate,[SISO][Automated]
autonomous reset as 512151 Not in CCL
[RealHW][FL18A][FSM4][CPRI][LTE4888-A-d]Failure
recovery action alarm,[FL18A Drop5.1_FFA]: DSP in
CAS-198686-Y6N2,CAS- replaceable
group
Verizon autonomous
FL18A
beseband
FOAreset
(GA1.1):
unit
with
(4335)
fault
7652_6709
and
6708fault
onABIA
AZL06057,
4001 are PHY_RX 274894
198694-Y8Q1 reported afterReset
[FL18A][SB][PET][3G-4G][FSME-FSMF]
Autonomous SW update.,[LTE4416][LAA][L18A]
on 131116_121_BELLAIRE,Verizon
DSP group Cells Not in CCL
are toggling
autonomous
FL18A FOA between
(GA1.1):
reset (fault
working
7652_6707
6709)and
during
ABIA
faulty
stability
Autonomous
state testing
,[FL18A]
PR379971,PR397496 [SBTS18A][FL00][CPRI][LAA]
Reset
[FL00][LTE2523][FRGY][Automated]
on 084003_LEONARD_STREET Cell toggle
Alarmduring
"RF Module
startup MOAM 139139 Not in
- cells not reach(4278)
Unauthorized" onAir does not appear after removing CCL
rfmplugin from ENB ,[SBTS18A]Lack of fault 4278 :
PR395935 [SBTS18SP] DSP crash and WCDMA down in Stability
EFaultId_RfModuleUnauthorizedAl DSP_R3 145243
testing Not in CCL_x000D_
DSP_R4 145244
PR401105 [SBTS18SP][R3][L] [SR000375] SYNCE missing- no OAM
Not inEFS
CCL19374
alarms Not in CCL_x000D_
FRI 28054 Not in
CAS-199192-N5M6 eNodeB inter-site CA (LTE3022) is not enabled DEM
CCL 32961 Not in
automatically after recovery from X2 link failure CCL

CAS-201852-X3D7 Flapping alarm "No connection between primary and We had to change
BTS extension system module" on AisScale SBTS LFS because we
needed to use some
PR395015,PR401927 [SBTS19] fault 6282 is raised after the X2 link is setup DEMnew serdes
32538 settings
Not in
by RROM_UNAVAILABLE_NEIGHBOUR_IND, which HW guys have
CCL
[SBTS18A NPI] SBTS-TDD X2 CA fault6282 paramater given us Not in CCL
PR392572 inconsistency
Multiple autonomous site resets with long fiber chaining HAS 19748 Not in
configuration, WCDMA not operational (fault 4001), RF CCL
unit auto reset (fault 1900)
PR396220 [SBTS18SPmMP1.3][Regression]MCPA Power Pooling MOAM 140513 Not in
is not supported with Dual band and triple band AS from CCL_x000D_
Rel5.1 radios GTS 16812 Not in
CAS-183973-J5H5,CAS- Increase in Drop Rate along with RRE and CA Config CCL PS 509995
MAC
190829-Z8F6,PR391604 Fail with CRL23388 activation,Retainability (DRB, QCI1 Not in CCL
and context) degraded after CRL-23388 (fast CA
CAS-131351-W5X1 scheduling) activated,During20
[SWCR.2856] - After SBTS restoration
hours KPI
TRXrun,
goes
massive
to BL- GSM DSP & GTS
calls drop on eNB 715 Cell4 (UHIE)
RSL\\TT-000036453775\\2G Not in CCL Not in
CCL
CAS-150239-Y2S1,CAS- Reported number of eRAB with NBR remains zero after SYSADAPT 61150
168880-G8B6,CAS- LTE1042 activation,SCF reconfiguration causes Not in CCL
181423-L1M6 unnecessary S1 update message, which is malformed
CAS-182913-B6W3,CAS- SBTS 2G present
and causes S1 linknon realfailure,LTE
setup alarms of VSWR,VSWR on RFSW_FM-529
RAT degradation
186607-Z8X9 after successfull
FHDBs on ANT-2plan provision VEG28.02.R34A
Not in CCL
CAS-186159-C7F9 DSP application fatal error bb
d0f4c61fd28620632ed
e18d50cbe5991286f9
CAS-186220-T8Y5 Uplink degradation service after restart 2G BTS. GTS
a59 17342
Not in CCLNot in
CCL

CAS-188564-C3J6,CAS- DSP platform fatal error,RSSI Alarms on AHPMDA DSP

198459-T3C3,PR406432 module,RX Level -128 reported for random TRXs for 643ccdf25738e7b9e8
CMST Site 60b719cda9f31e4c91
CAS-189221-D8H5,CAS- No alarms for BB sub unit HW fault in FSMF,No alarms 5c33 Not
MOAM 142418
in CCLNot in
189233-S3Y3 for BB sub unit HW fault in FSMF (In ref to CAS- CCL
151966-S0L0 || Random Cells going faulty_
CAS-192580-C2K5 Increase in CAT-M
Configuration error-BTS
RRE config
failureserror (Not enough HW UEC 705988 Not in
for LCR) - NA) CCL

CAS-193272- Increased BER detected on the optical connection to DCS 79509 Not in
M3K4,PR400993 Radio Module,Increased BER detected on the optical CCL_x000D_
connection to Radio Module' after LTE SWDL WBTS_BBUS_70140
CAS-193633-X5T7 Dummy SMOD on WebEM after swapping two SMOD 6.0 33492
DEM Not in CCLNot in
position to each other in the AirScale rack CCL_x000D_
MOAM 142483 Not in
CCL_x000D_
MOAM 143582 Not in
CCL
CAS-196442-Y0W9,CAS- CELL SERVICE PROBLEM:' Cell configuration data SYSADAPT 67167
203384-R3Y8 distribution failed',In SRAN getting BTS is not ready due Not in CCL
to ongoing RNW Plan File activation while paramter
CAS-196885-L1G8 changes
Wrong BW showing on cell in MRBTS post upgrade LTE_OPR_REQ_154
from SBTS 82 3.5 Not in
CCL_x000D_
CAS-199859-J8W0,CAS- AHFB and AHIB RRHs fail during reset request ,Low LTE_OPR_REQ_124
RFSW_FM-973
200985- Power RRH - Greyed out with Failure in Optical 55 3.1
FRM58.11.R23I
Not in
B2G3,PR407519,PR41178 interface alarm on the modules (AZRB, AZRA, AHIB, CCL_x000D_
Not in CCL
CAS-202783-Z3K2
6 AHFB),Failure
Site is unstableinafter
optical
thatinterface
with cellsforcrashing
AZRB after
and SWalso LTE_OPR_REQ_108
UEC 706391 Not in
upgrade,fault
seeing C-plane10overload
and fault 110 reported after software 70 3.1
CCL Not in
upgrade CCL_x000D_
CAS-202876-Y3F3 The validation from NetAct's CM Operation manager ADMIN
PDL 1767
27610
Not inNot in
always failed after activated the feature ' LTE486 PLMN CCL_x000D_
CCL
ID selected mobility profiles ' in the SRAN18A site. WebEM 27866 Not in
CAS-203650-N2L9,CAS- Sleepy Cell on Non NBIOT cells,DSP Crash lead to CCL_x000D_
PSFEATURE-54015 -
204142-R5C2,CAS- sleeping cell on MRBTS-138471,After MIMO/power PDL 1868
Not inNot in
204462-T7L3,CAS-204652- changes two cells 7A& 7B of AZL06214 stopped taking CCL_x000D_
CAS-206178-G9M7
Q0T0,PR394560,PR41103 DSP crash(FID6707)
traffic/became -UeStorage::add()
sleepy,Sleepy is full at
Cells on 131285 after SBTS18A_MP0.X
WebEM 28452 Not in
SBTS18A_PHY_RX_
0,PR415230 UeStorage.cpp,
workorder to go line:
from 0x28
Flex UL Comp - Fixed UL 514930
CCL Not in CCL
0006_000004_000000
Comp,Sleeping cells on band 3 visible. RTWP are 0 on - Not in CCL
CAS-206284-P5R9 Problem with
LNCEL-7, return from
LNCEL-8, Test dedicated state
LNCEL-9.,Sleeping cells after MCtrl 71275 Not in
upgrade from FL18A to FL19 0.2TD candidate - CCL
RTWP[dBm]: -140.00 on all antena ports,Cell
PR407404 MacHS DSP crash
configuration during stability
data distribution fail testing DSP_R3 145913
Not in CCL_x000D_
DSP_R4 145914
PR414874,PR414935 SRAN Software update rejected,SRAN Software update SWM Not in 22064
CCL Not in
rejected CCL

CAS-194343-P7R7,CAS- Sleeping Cell,Sleeping cell observed on 85029 & 85062 SBTS18A_PHY_RX_

204072-G4X8,CAS- after NBIOT LNCEL addition,After NB IoT Activation in 5 0006_000003_000000
205728- sites in KcKinney, one new NB IoT cell does not handle 275317 Not in CCL
V8K4,PR391776,PR393679 FID
CAS-196123-M4C8,CAS- NB IoT
: 1807
callsInvalid
due toFrequency
deaf PRACH.,FATAL
Channel for EXCEPTION
the BTS HW MCtrl 70429 Not in
,PR394365,PR396735,PR3 on
197066- Nid:0x2241
FHCC with TYPE:EXTERNAL:
20M bandwidth after upgrade to CCL_x000D_
98375,PR400318,PR40074 FL18A,FID
D2X7,PR396987,PR39815 [0xEA07A]CpuL1DMemoryProtectionFault
: 1807 Invalid Frequency Channel Violated
for the GTS 16918 Not in
CAS-198948-M7Y8
2,PR402754,PR403347,PR
8,PR398931,PR403786,PR memory
BTS
Cells HW
remain
address(L1DMPFAR):0x00000010
occursdown ononFHCB085800
withand
10MHz085829BW.,Alarm
after
Local 1807 HAS CCL_x000D_
21459 Not in
403390,PR404286,PR4050 upgrade
407047 access type:supervisor
appears on
to FL18A
URCC 0.2 afterwith
read
SW4256
upgrade,Configuration
**,Baseband
fault (Fibercard
Delay and CCL MOAM 141752 Not in
82,PR406038 error:
AntennaInvalid
autonomous Round frequency
Trip
reset asDelaychannel
exceeded)
recovery for the(2074)
action BTS HW after(1807) CCL
PR403232 GSMURCC,
from UL cell.,Fault
blocking measurement
URCB2074 andisURKA,Fault:
not working
raise when doingInvalid
on ANT2 Frequency
cell / ANT4
block and BSTAT 32924 Not in
Channel
unblock,SRIOfor theretry
BTSstopped
HW (1807) (2074) occurs
afteron FHCC and CCL_x000D_
Cell
FHCG ,After upgrade
block/unblock FL19, invalid
stress test,FATAL Frequency Channel MANO 141311 Not in
APPLICATION
PR404292,PR411130 Inband
ERROR
for IoT
the BTS test
HWmodel
Nid:0x2281 (1807) A14-1
occurs24on(FRC:1240141050)
ti_em_alloc_with_buffers
FHCB,Cell can't failed! not RROM
onair CCL_x000D_
705259 Not in
working,NBIOTinband
n_buffers:2
and RRU FZNL displayICS
type:197,Failure"1807start uplink testmodel
inConfigre
replaceable errorbaseband failed CCL
:invalid MOAM 141692 Not in
unit (6709),for
frequency BTSBTS reset
HW"required
after upgrade
(4001)to faults
TL19and CCL
CAS-197070-X2Q0 SRAN
multipleBTSkernelUpgrade
errors failed while upgrading
are present on LTE BTS from after VTC
SRAN16.10
WCDMA BTS toreset,FSP
SRAN17Aon forsystem
Packetmodule
over TDM sites FTM_SR18A_MPX_2
autonomous reset as recovery action. Fault 2074 is 019.02.08_0016
PR409366 Failure in Optical
reported,Fatal (FauiltId
found 10) on allFSP-234D-C-CCS
in BTSlog:[b7 RF & BB bus MOAM 142795 Not in
Not in CCL
Reception Error MUKSU (FaultIdF95-LogListener
2019-01-02T15:02:18.040350Z 2016) Raised after CCL
Planned CommissioningCCSEmDispatcherExe: CCSRT
ERR/LFS/LinuxSyslog,
CAS-199819-Y3B8 Cells disabled
ERR: due to unknown problems (4261)6707
fatality : (EAaErrorFatality_System),Fault DCS 81382 Not in
raise after block shared RRU,'BTS reset required(4001)' CCL
due to 'System Module failure(6709)' on two LTE cells
CAS-203560-F1P9 SW
afterUpgrade
LTE cellsfrom SRAN18
block and 0.2 to SRAN18A 0.1 PARAM 27666 Not in
triggers Relation Errors
unblock,AdminApiProcedureTimeoutException during CCL_x000D_
Commissioning when one cell is crashed with 6253 on ADMIN 28328 Not in
CAS-199902-G9Z2 High HARQ configuratin,Fault
Guardband failure rate in NB-IOT 6079sites
DSP group CCL_x000D_
SBTS18A_PHY_RX_
autonomous reset as recovery action is generated on 0006_000005_000000
SC_PARAM 27749
LTE BTS after several WCDMA block/unblock 277285 Not in
Not in CCL_x000D_
CAS-164878-C7F9 [FSMF
loops,CellFL18] Problem with
configuration dataLTE1130 "Dynamic
distribution PUCCH" 706170
failed (6253) CCL_x000D_
RROM Not in
ADMIN 28690
for
CellNB-IOT
disabled due to unknown problem, logs colleceted CCL SBTS18A 516054
(4261) after regaining S1 connectivity. Not in CCL_x000D_
CAS-183300-K6K6 TCH Assignment failure on 1800 after any Fluctuation MOAM 136644 Not in
LTE_UP_8700,
on site CCL_x000D_
LTE_UP_20519
MCTRL 68392
141.0, 6.0 Not inNot
CCLin
CAS-206375-T9B4,CAS- No update of ARP table in sites with HW AirScale SW TRS CCL_x000D_
177804-M5P8 SRAN17A and SRAN18A 0.1,[FSM4 FL18] S1 HO FTM_FL18SP_TL18S
GTS 15887 Not in
increase due to unavailable X2 P_SR18SP_2019.02.
CCL_x000D_
CAS-177804-M5P8,CAS- [FSM4 FL18] S1 HO increase due to unavailable X2,No TRS 27_0334
FRI 27104 Not in
206375-T9B4 update of ARP table in sites with HW AirScale SW FTM_FL18A_TL18A_
CCL
SRAN17A and SRAN18A 0.1 SR18A_CB18A_2019.
02.26_0262 Not in
CCL
CAS-183011-D4F0 To understand the reason for CS code failures SS_HsupaL2 146795
happening after Load based AMR was activated Not in CCL

CAS-185062- VoLTE loss UL following DL 4CA activation,[FL18] MACPS 475532

Z1B1,PR331094,PR336230 [AirScale] [KPI] VoLTE Packet Lost Ratio was increased Not in CCL
by 20-30% with FL18 feature LTE3225 FDD DL CA 5CC
CAS-185946-T7C0,CAS- enabled,[FL18] [Airscale]
[KPI][AT_EWL_FL18] FL18
[KPI]
2.1ERR/LTE
- E-RAB Setup
RX PHYSuccess UEC
203641-T9B7 DEC....Active
Ratio for QCI1UEdecreased
not foundafter
from"Fake
HARQDRX"
data-base
activation, FB1810@707460
[FL18A Feature FNI]E-RAB ADR was degraded after Not in CCL
PR397171 FL18A featureRRH
[SRAN18SP] activation
Energy Efficiency counters not BSTAT 32463 Not in
displayed in WebEM with SRAN configuration with only CCL
2G and 3G RAT (no 4G Lte RAT)
PR400081 [SRAN18A][P8][2FSMF] [automatic retU calibration MOAM 143902 Not in
when RETConfigfile is changed][MRBTS500] CCL
[SBTS18A_ENB_0000_000422_000034]
CAS-189679-X2T8 TX out of order RFSW_FM-1161
FRM38.11.R11A
Not in CCL
CAS-190559-Q5C9 SRAN: BCF object in Monitor do not get proper agent FRI 27566 Not in CCL
automatically

CAS-190461-G3P4 (Single RAN 2G SRAN18)SBTS raised 1910 alarm RFSW_FEATURE-

while only GSM was actived with AHDB configuration 18141
FRM58.11.R15I
CAS-193260- FL18A FBBC not detected - BTS configuration error (not FB1809 1fe6d30
Not in CCL
G7C7,PR399707 enough HW for LCR) (1868),[FL18A][ 1.2PD] Alarm Not in CCL
Inter eNB Communication Failure (6284) is reported
CAS-140326-W9W2,CAS- SRAN17A
after SW upgrade
- RAB DROP 3G - RL fails due to sync CP_LRM 697760
198695-M2T0 lost,SBTS18SP - 3G - Degraded RRC/RAB KPIs for all Not in CCL
cells
CAS-198737-Z3G4,CAS- RF BB bus configuration error (1905),[FL18A Drop7] MOAM 139263 Not in
198750- After SW Upgrade - Cell Power Failure Issue Observed, CCL
X9T7,PR398126,PR398360 [SBTS18A][FSMF] fault 1905 raised on OBSAI RF on
,PR399458,PR399687,PR3 UHFB
CAS-195997-K7T4,CAS- mixed CPRI/OBSAI
RRH signature configuration,
2 'FTP failure' RFongoes
site into UHFB SBTS18A
99689,PR399839,PR40038 WA73XC356
199840-D6M5 autonomous reset,[FL18A][1.0PD][AirScale][S]
,FL18A SW Upgrade Failure Not in CCL
7,PR400779,PR400978,PR [Irving_CST]: Cell Power Failure (4090) Alarm reported
401147,PR402081,PR4022 [NPI
CAS-204570-Q4P2,CAS- after upgrade
FL18A 0.1.1PD]
to FL18A SBTS18A_MP0.X
03,PR403495,PR403702,P [FL18A_ENB_0000_000151_020085][LTE3071]
208505-K2G8 (FL18A_ENB_0000_000487_010040),[TL18A][AirScale] DSP 516396 Not in CCL
R403836,PR404417,PR405 crash at NbTransmissionParamsList.hpp, line: failed
[LTE2745][CRL26850][CPRI+OBSAI]Attached
CAS-205199-S4J8,CAS-
217,PR405324,PR407172 SRAN18SP
0x43,4G900
due to no cell-TMMIML0912
CQI degradation LTEafter Sleeping
found,[SBTS18A][RP002128][Rel4] upgradeCelltoRRC Fault RFSW_FM-1259
206101-V8B3,CAS-207652- SRAN18SP
attempts = 01.3.4,[FL18A
125 is reported for OBSAI 0.2.2]and CPRI Tput RM,
Degradation
4090 is After FRM58.11.R32I
J7D6 SW Upgrade,LTE
reported for LNCEL, CQI degradationconfiguration, RF
CPRI/OBSAI Not in CCL
Stability 3G/4G
goes intoCELLS ARE DOWN
autonomous FOR AHEGA
reset,[SBTS18A MODULE
MP0.x] RFSW_FEATURE-
POST SW UPDATE,[FL18A_D5.2_Rlab]
[RP002074] Unexpected faults: 1905, 125, eNB09:
4090 raised 20139
CRITICAL
after startup Alarm on AZRBMP0.x
in SBTS18A cells BTS Internal
software SW
build,[TL18A] FRM58.11.R31I
CAS-211024-Z6C0 management
FL18A [FOA][KPI]:
Problem eNB138469
code 1850,SNGRM
[AirScale][LTE2745][CRL26850][CPRI+OBSAI]RF - RRC blocking Some on cell FB1809
Not in CCL
AHEGA
138469_2 up/down
module failuredue 1907
to Uplane
after SRAN18A
raised OVLD (M8013C66)
and reset 0.1 as
SWrecovery in c4dfd1818e2f9337349
upgrade,FL18A FOA: 131653: 7653_0010_AZRB
loop,[SBTS18A mMP0.1][Dualcore] ceecb8496c044efc95
CAS-211965-X3Z7 [NPI 18A] Missing
observed,FL18A
[RP001919_LTE3667][IoT]FOAtable borders
: 139962: in Centralized
After 7653_0010_AHBCC
SW RET
update to mMP0.1 Admin
460 Not29499
in CCLNot in
CELL_FAULTY
management
build, fault 1905 observed,[SBTS18A]
raised by FXDD RFs,[LTE4784][FDD]Unexpected fault CCL
1850 affecting AHEGA unit due to NAHKA
[SBTS18A][Airscale][CRT][OAM_SCT] 4090 crash,
Cell power
CAS-211970-L1V5 [NPI 18A]
failure Too narrow
[SBTS18A][AHFIB]
on FXEB radioSW list of Served
corrupted
modules cells antenna
after
on update lines
OBSAI/CPRI fromin ADMIN 29707 Not in
RET commissioning
Factory load,[SISO][Automated][RealHW][LTE2866]
mix configuration.,[SBTS18A][Dualcore][QT] Fault id CCL
[LTE2723]
1905 RF BB Alarm 1850 "BTS internal
bus configuration SW management
error visible at Planned
PR394145,PR396700,PR4 [SRAN18A][I&V-Auto][CR2][T-KIE
problem" TC,[CRT] Attach to7483]
is visible
commissioning GSM on FXED not dem 31419 Not in
00532 [PATHMTUDISCOVERRES_R
possible after update to SBTS18A showsP7,[SBTS18A_MP1] CCL_x000D_
pathMtuDiscoverResult
[R4][WG][DSS] Unexpected OK even
'Fault-125when :TPL returnslevel TAS 31070
Tx power Not in
PR396326,PR398615 TplErrorCategory
[SBST18A][FSMF][AREA]Cell
1],[SBTS19]
too low' is raised during multipleaddition
[FSMr4]
WCellsresults
PMTU in
discovery DCS
reset from CCL 77166 Not in
periodic
is drop
not properly
admin and ofworking,[SBTS00][fsmr4]PMTU
WCells already
are stuckactivein cell ,[SBTS18A]
'Integrated to RAN'.discovery
, CCL
[RP002128][FSMF+FSMF]
timed out is not happening in
[SBTS19][CNI-31973][AirScale] Unexpected
ADMINUE cannot LTEattach
cells reset
to
PR400480 on
[SRAN18A]
GSM AREA
cellsafter
onSBTScell GSM
AHFIB addition
RF remote PS Uplane IP not
module,[FL00][AirScale] GTS 16180 Not in
updated
[PET]Clear correctly
Channel Assessment reports not received CCL
for AZRA radios.,[SISO][Automated][AirScale][FL18A]
PR401429 [SBTS18A][AHGB]][4+4][VR]
Cell Power Failure 4090 and Increased WCDMA throughputs
BER detected are HAS 21422 Not in
degraded afterconnection
on the optical AHGB linkto break
Radio Module,[LTE2745] CCL
[LTE][FDD][Airscale][FL18A][ET][OAM_SCT] 4090 cell
PR402003 [SBTS18A][CR1][FSMr3]
power failure on cell on FXEB RF Module
radio moduleConfiguring
in chainFailed
- RFSW_FM 759
(1900)
OBSAI alarm raised after
and CPRI-N redfreqoffset set to 4.7 on
mix configuration,[CRL27451] Not in CCL
FXJB
[LTE2745][LTE][Airscale][ET][OAM_SCT][FDD] 4090
PR402062 [SBTS19]Wcell
cell power failure setup
on FXEBfailure- OBSAI
after cell inlock/unlock
one timing groupfrom SC_TOAM 701116
GOMS
with AHEB - CPRI-N ,[SBTS19][FSMF+FSMF] UE can Not in CCL
not attach to GSM cells configured on OBSAI RMOD
FXED connected to SC,[SBTS19][FSMF+FSMF] Faults
1905, 4090, 125 observed with RMODs OBSAI and
CPRI in one configuration, LTE and GSM cells are
failed,[FL19][Airscale][PET], AZRA radio down after sw
update
PR402988 [SRAN18SP] Snapshot NOK SYSADAPT 6853
Not in CCL

PR403237,PR406919 [SBTS18SP][FSMF+FSMF][PET] Calls are dropping or RFSW_FM-817

rejected during stability testing,[SBTS19][FSMF][PET] VEG28.02.R33A
WCDMA Calls dropping during stability test on FHDB Not in CCL
PR405167 radio Calls are failing on Node-3 & Node-4 in 4+2
GSM HAS 20980 Not in
configuration with AHDB CCL

PR404691 Fault 125 on several WCDMA cells when DSS is DCS 80104 Not in
activated on both CPRI and OBSAI radio modules CCL

PR406189 ProhibitTimer setting for VoLTE during reestablishment UEC 701654 Not in
CCL

PR408249 RLF HO during SCell Swap LTE_CPLANE_UEC

704429 Not in CCL

PR410652 Decreased number of SUs allocated for WCDMA after DCS 81027 Not in
migration from SBTS16.10 CCL

PR411647,PR412296,PR4 [FL18A][Airscale][PET][1HFB] Flood of SRIO errors CNI-35232 revert -

12492,PR412701,PR41279 causing bearer setup failures (UEC_DB_BEARER_INIT Not in CCL
3,PR412823 failed),[FL18A 2.0][AirScale][CRT] DSP group
PR412908,PR413793,PR4 [FL18A
autonomous1.1][FiVe][FSMF]
reset as recovery Diagnostic
actionFiles
(6292)Collected
alarm Uboot 241dbe1
15051,PR415173,PR41601 after
duringSW upgrade,[FL19][WBTS00][FSME+FSMF][3G- Not in CCL_x000D_
startup,[OAM_SCT][SBTS][FDD][NR][18A][R4]
3,PR416470,PR416535,PR 4G RFS] Spurious
[SMOKE] Alarm 6253 reset triggered
- Cell and "Diagnostic
configuration data files Uboot a688108
416779,PR417273,PR4176
CAS-210803-L7C3,CAS- collected
BFTKS_L
distribution (6450)"
RMOD_R-1 alarmsend/clear
present after a large
failed,[FL18A][AirScale][Fullrack][PET] LTEnumber
LegacyofABIA RFSW_FM-1479
Not in CCL
67,PR417757,PR417956
213825-W1D5,PR420671 SOAM
7116
crash Carrier
SW 65
after Upgrade,[OAM_SCT][LTE][TDD][trunk][R3]
power
hoursmeasurement down not
stability test,[OAM_SCT][SBTS] FRM58.11.R33I
work,SRAN18SP
[FDD][NR][18A][R4][SMOKE]
[NR][fromBB] 1.2 : A plenty
Unexpected alarm of‘Diagnostic
Cells Alarm
stuck7116 with fault Not in CCL
in Prevalidated
Files
PR395531,PR397606 'Rx
SBTS19_[DSS
statesignal
collected' level LG][R3]
failure'during
raised
LTE SW isatnot
for WCDMA,[SBTS18A][CIT][DualCore]GSM
is reported AHEGA
usingRFM,[QT]
update especially
blanked PRBs, cells LTS 17999 Not in
WCEL
[SRAN18A]
are not UARFCN=10788,[SBTS19][QT_branches]
[FL18A][FSMF] [DSS
operational test]
afterAHDB
Diagnostic StartUP DSS
Files feature
Collected
due to faultdo6709
with not work
DSP CCL
Spurious
[DualCore]
concurrent
reset Fault ID
after startup,[TL18SP
crash error103 Carrier4.0] Power
[FSMF]Measurement
[FIVE] 'TRS
CAS-201514-M8J5,CAS- SRAN/
spurious
Does Fault
Not reset'
Work 4261
and
was raised
Seen7115
'Diagnostic Diagnostic
after files
Deltacollected' filesalarms
Commissioning collected MCTRL 72058 Not in
209714-S1B0,CAS-210977- alarms
during SWthenupgrade,[SRAN19][AirScale+FSMF]
not able to fetch snapshot observed in CCL_x000D_
B9C6 SRAN18/TT-000040704779/4G-,Alarm
[PET]:LFS kernel occurs during BTS SWResolution activation,of MCtrl 72292 Not in
CAS-111419-G5T1,CAS- WBTS18
Diagnostic forFiles
[TL00][FSMF][PET]: M1006C311/M1006C186,Voice
collected,[NPI
Spurious reset 18A] after
(4261)
SW dropupdate,due Decoder
CCL 135558
112550-W6Y8,CAS- EFaultId_CellStateAuditAl
to radio 1.0.2][FiVe][Airscale][AMOB]
[FL18A (M1001C146) increased and autoreset
on certain
Spurious sites after
BTS Not in CCL
128109-P2M5,CAS- upgrade
reset duringto WBTS18,M1006C40 is affected on site level
48h stability test,[FL00][FSM3][PET]
CAS-211723-J5C0
191721-W1H1,PR322590 randomly,Re-establishments
[NPI SRAN18A]
Diagnostic LCELL allocation
files collected alarm increased
problem
is active afterafter
after WBTS18
swsw DCS 83059 Not in
2.0
upgarade
upgrade,WCDMA18
to SRAN18A Pilot: RNC_5434A
update,[MT][FL19][GF19][LTE-GSM RAB
RFS][FSMF-FSMF] CCL
Success
Spurious Ratio, VoiceLTE
reset after (CSR) SW (re-estab
update causes incl) fault 6450:
CAS-209997- After upgrade
Diagnostic filestocollected,[OAM_SCT][SBTS][FDD]
SBTS18A, RRC and ERAB drop UEC 707487 Not in
D5V0,PR397923,PR40037 increasing many sites,[mMIMO] Volte/ERAB call drops CCL
[trunk][R33][SMOKE][LR][fromBB][TOP_SMOKE]
9,PR410497 seen because
FaultId: 6450 - of HOs,Full Files
Diagnostic reconfiguration nok after
collected during SW
PR399605,PR400798,PR4 [SBTS18A][Airscale][MIX
LTE3105 triggered RRE,[FiVe][LTE3105]
OBSAI/CPRI][RP002128]
update,[MT][WBTS19][TL00-FL00-FL00][FSME Occasional
+ FSME MCtrl 72790 Not in
14906 X2RLFHO
After
+ FSMF RF +hot Preparation
remove/insert
FSMF + FSMF failures
WCDMA
][3G-4G dueTDD tocells
emptynot SRB
- FDD recovered
CA]list in CCL
MAC_USER_SETUP_REQ_MSG
(disabled
Diagnosticstate) without any
files collected alarm,[SBTS19]
is reported on LTE_TDD after
CAS-211807-P4S3 FL18SP
software 3.0 not allowing Some
[AirScale+AirScale][CIT]
upgrade more thanWCDMA 20Mhz cellsdifference
not on MOAM 146945 Not in
recovered
UHFC RRHafter short link breaks, fault 110 visible, CCL
[SBTS19][RGT][RP002128] WCDMA cell grayed after
CAS-191759-Z5R4 SRAN17A
block one and - SBTS Planother
unblock provisioning
radio module for autoin VPN
short TAS 34323 Not in
feature
period of failed
timewith IPSec
(for cell outage
sector configuration types H). CCL

CAS-188436-S1M3,CAS- FHEA problem - TX Ouput out of order - only those with RFSW_FM-1242
207097-X2Y7 GSM TRXs and more than 2 TRXs - on PA with non- MED28.02.R31A
BCCH TRX,[NPI18A] FHEA Antenna line switched off Not in CCL
CAS-166624-G1T4,CAS- SRAN18SP
due to high VSWR
NPI 3Gon- Radio
PA with
Link
non-BCCH
Failure increase
TRX after RFSW_FM-1479
180533-F7D9,CAS-212900- swaping old RM to new multitechno AHEGA/AHEGB FRM58.11.R33I
W7V4 modules.,Increase of the number of Radio Link Failures Not in CCL_x000D_
CAS-213938- with cause
Cannot upgrade
‘Radio
fromNetwork
SRAN18A Layer'
0.2 to
after
SRAN18A
upgrade0.3.1 CODEC 148487
BTSMED e1f0ddb
D2G7,PR417964 WCDMA18
with netact SW
to SRAN18SP
manager inwith
1 eNB,[Trunk]
radio unit swap to Not in CCL
[BtsMed]scfmigrator.log
AHEGB,UL SINR Degradationhas noafter
update in BtsMed and
modernization
CAS-210416-L6W8 Bulk TRX
imp.log shows
are going
dataMigration
in BL-RSL failed
post NSA plan run GTS 18686 Not in
CCL

PR430602,CAS-217024- remove unnecessary LTE L2 assert from LTE L2 799128

R5P9 QueueCtx_L2RlcCoreUl::sendPowerHeadroomReport_
AllGroups,SRAN site getting hanged resolved post reset
CAS-183990-V9Q6 SINR_PUCCH_MAX (M8005C91) increase by ~15db FL18A_PHY_RX_000
with FL18A drop3 0_000047_000000
281524 Not in CCL
CAS-190654-N6C8 Handover from PLMN 20801/20891 to PLMN20891 UECexe r719306
(defined as equivalent) is not possible Not in CCL

CAS-198546-Y2D2 SRAN18A - gaps in measurements ADMIN 30766 Not in

CCL

CAS-201903-T1P9 NPI- SRAN18A 7114( supp info= Cell Configuration LTE L2 797352
data distribution fails) alarm on AHCA sites Not in CCL

CAS-203396-K8F0 Increase in E-RAB DR OTH eNB after SW upgrade UEC 720430 Not in
CCL

CAS-208102-R2W5 Different Alarm BSC and SBTS FRI 25178 Not in CCL

CAS-209034-M1W9 [NPI SRAN18A] Validation error - issues with assertion PDL 2075 Not in CCL
7466 and 7467 after update to BTSMED 18A MP0.1

CAS-212353-M8M1 SRAN18SP/2.1 - Low CSSR 3G after SW upgrade MOAM 133516 Not in

CCL

CAS-213894-Z2Q5 [NPI SRAN18A] Not enough HW for LCR wrong HW DCS 84370 Not in
allocation for connected FXEA 2xfiber CCL

CAS-214615-V6M9,CAS- [PM Counter]FDD/FL18A/After combined super cell FL18A 522095 Not in

217561-M5D3 enabled, both RTP packet loss rate and uplink QCI1 CCL_x000D_
packet loss rate are high.,[FDD][SRAN18SP] FL18A_PHY_RX_000
CAS-216844-G9W4 [AIRSCALE]
An alarm 7107 uplink
with packet
fault IDloss
'6297"
rateraised
of theatindoor
the sites 0_000048_000000
FB1809
mergedwere
where cell is
activated
high Inter eNB DL CA feature 281655 Not in CCL
e587ddfc2d77665a60
5f704f4d25a44905407
CAS-217024- SRAN site getting hanged resolved post reset,remove 640 L2
LTE Not
799468
in CCL
R5P9,PR430602 unnecessary LTE L2 assert from Not in CCL
QueueCtx_L2RlcCoreUl::sendPowerHeadroomReport_
CAS-210242-P1G9,CAS- AllGroups
Sudden loss of HSUPA in LCG which is restores only CP_GRM 722677
218390-J1D4,PR423710 once site is reset,SRAN18A : SHSTM HSUPA setup Not in CCL
failure with BTSHWFAIL,HSUPA traffic not possible for
CAS-218642-F8C3,CAS- LCG in ESMNPI]
[SRAN18A afterWrong
ESM hot Termremove
MRBTS-1
- hot was
insertsent to CONVENG 9662
221526-Y7W6 Netact in Alarm Text.,Alarm from different MRBTS Not in CCL
shows under MRBTS-1 in NetAct
PR400441,PR416076 [SBTSA18A][mMP][RP002014] Attach to WCDMA cell WTS 22198 Not in
not possible when DSS is enabled & RF is connected CCL_x000D_
with Long Fibers,[SBTS18A MP1.0][FSMF+FSMF] All DCS 84156 Not in
PR413789 WCDMA
[SBTS 19][R4][G]
cells are CS
in fake
call OnAir
dropped(noduring
services
Beam
on them) CCL
RFSW_FM-1424
when AHEGA
switching to BEAM-6
is connected
from beam
via 23km
hopping
optical
region
fiber FRM58.11.R36I
occasionally Not in CCL_x000D_
PR421544 [SBTS19]M5008C50 counter do not update correctly MOAM 147825
CP_LRM 720142
Not in
according to configured HS-FACH baseband resources CCLin CCL
Not

PR423713 [SBTS19][R3][WG] Call drop is observed after deleting GTS 18387 Not in
and recreating RF Hop sector. CCL

PR424377 [SRAN18A][Airscale][NPSCSV]RF module configuring GTS 18937 Not in

failed AHPMDA CCL_x000D_
WBTS_APPS_20330
PR424703 [SBTS18A][FSMF][LG] During LTE RAT reset NIDD 1910
3.0 Not in :CCL
parameter change from ADMIN Fault 1910 'RF Module EFaultId_FrFilterInput
filter input power missing' PowerMissing 58.02
PR425664,PR431560 [SRAN18SP][Airscale]: BTS crashed during a stability SS_RakeReceiver
Not in CCL_x000D_
testing,[SBTS18A][FSMF] All WCDMA cells down 149094 Not in CCL
MOAM (Rumag)
during stability test 147378 Not in CCL
PR426764 Loose phase and time synchronization, BSC time is GTS 18558 Not in
used instead of NTP time CCL_x000D_
DEM 37522 Not in
PR413763,PR414127,PR4 [OAM_SCT][LTE][TDD][trunk][R4][SMOKE] Fault 1811 FB1809 CCL_x000D_
7527fa0
21850,PR426796,PR42821 raised durring HW Reset,[OAM_SCT][LTE][FDD][trunk] Not EFSin22007
CCL Not in
0 [R4][SMOKE] Alarm 1811 Baseband card autonomous CCL
PR427296 reset as recovery
[SRAN18A 1.0][COMPA][FSM3]
action after Hardware
RelationReset,
Errors are not PDL 2075 Not in CCL
[TL19_mMIMO][AirScale+AAHC][CSV-SPRINT]
displayed on Admin if inbandPRBIndexUL is setAfter to 6 on
Software Upgrade to TL19_ENB_0000_000051_000000
SBTS18SP_ENB_2000_001003_000000 for IoT cells
CAS-196456-R3R6 from TL18A_ENB_0000_000518_000000
Some SRAN eNBs report wrong SW version all in
blades
RTPM on BSTAT 34892 Not in
right rack
Traffica reporting.
reported fault 1811 and did not come up, CCL
[SBTS18A][COMPA][DualCore] Unexpected behavior
after software update from SBTS17A 2.3,[FL19]
[0.0.2PD][UUF][AIRSCALE][ABIA][FID:1811]Baseband
card autonomous reset as recovery action after upgrade
CAS-209365-Q9K9 PDL rule violation after RF diagnostic test deactivation admin 30476 Not in
CCL

CAS-216552-T2N6 Two IPSEC tunnels established at the same time after DEM 37501 Not in
IPsec tunnel switchover CCL

PR428035 [SBTS19][R3][WG] GTS crash is observed after TRX GTS 18652 Not in
deletion from RF Hop sector. CCL

CAS-202081-K2N2,CAS- /TDD/TL18SP 3.0/after upgrade to MP3.0,FZFF-E MCTRL 68688 Not in

225763-R7T3 report 1807 alarm,BAND A can't extend〠CCL
‚,SBTS18SP_ENB_2000_000865_000000 WCDMA
CAS-223085-L4X3 cells don´t
GSM cell down
startup
afterinrestarting
AHEGB duewith to
L900
"Invalid
inter-site
frequency GTS 19065 Not in
channel for the BTS HW"
CA+actDlSlimcarrier config
alarm CCL

CAS-226526-X8F4 SRAN18A: AHEGA UARFCN range for Band1 changed SBTS18AMP1.1

after SRAN18A 1.0 and SRAN18A 1.1 SW upgrade. MOAM 150537 Not in
WCDMA cells with uarfcn 10837 down CCL_x000D_
admin 31821 Not in
CAS-175251-T6T0 SRAN17A Acceptance - Bad Speech Quality with GSM https:// CCL
NB-AMR bhgerrit.ext.net.nokia.
com/#/c/101512/
CAS-200624-T4P2 Alarm 7116 WCEL OUT OF USE after alarm 7772, I38f23b8b7e0f9be43d
VTC
7782 HSDPA, HSDPA CONFIGURATION FAILED 13a08cb97df7e261d6
FTM_FL18A_TL18A_
449a Not in CCL
SR18A_CB18A_2019.
CAS-212433-J2Y2 [SBTS18A][SR002074]Ghost fiber on RF Split 04.23_0305
MOAM 147829 Not in
configuration CCL_x000D_
VTC 25039
HAS Not in
CAS-213116-Z6Z9 [NPI SRAN18A] (6708) FTM_SR18A_MPX_2
CCL
FL18A 804353 Not in
EFaultId_ExternallyTriggeredDspFatalErrA 019.04.23_0021
CCL
Not in CCL
CAS-213927-W1G9 WCDMA FSMF Limitation WBTS_CP_10587
21.0 Not in
CCL_x000D_
CAS-214646-G1H4 FL18 2.1.2 mPD3 - Abnormal behavior of frequency MOAM 135790 Not8.0
WBTS_CP_20822 in
layer LTE1800 MHz after hw swap from FSMF+FXEB to CCL Not in
AirScale+AHEB CCL_x000D_
CAS-215398-F5N2 SRAN BTS working on TDM (E1) through FTIF is not VTC CP_LRM 727207
restoring after transmission failure FTM_FL18A_TL18A_
Not in CCL
SR18A_CB18A_2019.
CAS-217818-S9M6 [FDD][FSMF+FSMF] LTE1891 Micro-DTX doesn't work VTC 04.23_0306 Not in
for SBTS in dual FSMF configuration FTM_FL18A_TL18A_
CCL
SR18A_CB18A_2019.
CAS-218875-Z4H9,CAS- Problems with parameter changes,Plan handling leads LTS 04.24_0307
22410 Not in
225875- to impossible CM functionality in SBTS18A,[SBTS19] CCL_x000D_
CCL
X3Q4,PR429217,PR43070 After change the parameters name via AdminUI, the MCTRL 73950 Not in
CAS-222758-W3V2
6 sbts keep stuck in operation
[FDD][FSMF][AHHB] CAS-222758-W3V2
ongoing state.,[FDD]
-AHHB was HAS CCL 25863 Not in
[FSMF] and
disable GSMallonly
cellscommissioned,
configured at AHHB
Activatewere
PlanOoS
is not
after CCL
upgrade from
successful FL18_ENB_0000_030137_000000
after actForceAutoReset parameter change to
CAS-223410- FL18SP_ENB_0000_040064_000000
BTS snapshot is rejected due to busy status
or fromof SBTS, SYSADAPT 55094
M8P6,PR327841 FL18_ENB_0000_030137_000000
[SBTS17][FSMFr3] Technical reporttoprocedure stuck Not in CCL
FL18A_ENB_0000_020060_000000.
forever when reload ADMIN page triggered
CAS-224746-D9M3 [SRAN18A] PDL rule changed for minNumRrcCatM PARAM 29130 Not in
CCL

CAS-225703-Z4Y5 BTS Reset rejected at KKN0156 and LEI0132 WTS 23455 Not in
CCL

CAS-227653-P9L8,CAS- Planhandling lead to "BTS did'nt respond in 270s" error, SYSADAPT/xL18A

230966-G6W2 [SRAN18A]: After BTSMED Upgrade, NetAct Plan 'BTS 71500 Not in CCL
didn't respond to provision request within 270s'
CAS-228032-M4Z6,CAS- [FDD][FSMF] Random Sites coming in zero payload by MCI 20214 Not in
228557-Q8H6 checking on sites, cells showing down without any CCL
alarm,MP_MRBTS-Unable to change any parameters
PR427269 due to ongoing RNW plan activation
[SBTS18][CIT][FSMF]Cells mapped on one AHEGB HAS 25247 Not in
disabled after SBTS block unblock CCL_x000D_
MOAM 149757 Not in
PR426938,PR431001 [SBTS19][2xFSMF][3RP-01]: Secondary core is not OAM
CCL EFS 22795
resetting,[SYNC][2xFSMF][GNSSp][3RP-01]: Recovery Not in CCL_x000D_
action BtsReset 4001 FRI 31572 Not in
PR432781,PR436341 [SRAN17A][FSMF+FSMF][STABI][FID:6709] DSP crash CODEC_TAC
CCL 150360
occurred during stability testing, WCDMA cells down, Not in CCL
[SBTS18SP][FSMF+FSMF][FID:6709][STABI] DSP
crash occurred during stability test, WCDMA cell outage
CAS-224762-D5M7,CAS- SRAN// RNA counters are pegging "0"//4G,FL19 FOA: OM_GEN_SFS_PMM
228108-X4K3,PR441035 84824; PM stats stopped at 12:15 am on May 9th, GT.1024 4.0.1 Not in
[Trunk][PM][Stability]PM files generated all ended with CCL_x000D_
CAS-227536-R2C8,CAS- Spurious
"raw.gz" which
reset due
resulttoinEAaErrorFatality_Supervision
no PM data uploaded to Netact SOAM/branches/
MOAM 152252 Not in
227540-Q2Z0,CAS- toward SysAdapater (suspicious memory leak on maintenance/x18A/
CCL
228382- SysAdapater),Fault 2016 and 10 are raised during pfs/
K2P2,PR435477,PR438331 RIM
CAS-224050-H1M7,CAS- service,WebEM
status mismatch
is Slow between
with poor
WebEM
UI response
and NetAct,The
time', performance_monitori
CONVENG 10185
215411-S3N9 [STABI][FDD][FSMF][FID:4329]
value of LNADJGNB/x2ToGnbLinkStatus Fault 4329 mismatch
appears on ng/Common/
Not in CCL
ARHA radio
between BTSEM
moduleandduring
NetActstability test,SOAP Message PM_Counter_Collectio
CAS-210897-L2V6,CAS- Traces consuming
Specification change toorequest
much space
to SBTSin SBTS
,how to limit the BTSMED
n/ d1e139
210898-W2H4 volume of Trace from SBTS to BTSMED when there Not in CCL_x000D_
PerfMon_PmResultFil
has 3rd server is closed : follow-up emergency RCA OM_GEN_SFS_PER
eCreation.rst 23346
CAS-222585-T8D0 [BTSMED] BTSMED_FAIL_CM_UL
investigation,How to avoid the un-register
fails around
BTS trace
30%?. F_CAP.3117
BTSMED 622fb5
1.0.0
Not in CCL_x000D_
handling from BTSMED : follow-up emergency RCA Not
BSTATin CCL
CCL_x000D_
37295 Not in
investigation OM_GEN_SFS_TRA
CCL
CAS-224906-J0C6 BW parameters changes aren't possible through xml CEMGMNT.3835
BTSMED 110533
(U900 3.8 activation) 1.0.0inNot
Not CCLin
CCL_x000D_
CAS-227631- ‘[SRAN18A] [CDRS]: Provisioning failure with error BTSMED nokia-imp-
LTE_OPR_REQ_199
G7V7,PR423138 'org.apache.axis2.AxisFault: HTTP ( 500 ) Server', 18a.1.2019051315501
19 1.0 Not in
[LTE19][BTSMED19] CM provissioning failed with CCL_x000D_
8.784226-
PA-0015653 CAS-222711-J6Y4-
status: HTTP ( 500 ) BTSMEds of address
Server Error Netact NX from BTSMED d6e64Not in
LTE_OPR_AC_9678
1.noarch.rpm
SRAN18A MP0.3 to SRAN18A MP1.0 failed Not
1.0 inNot
CCL CCLin
CCL_x000D_
CAS-229593-Z9Q8 [SRAN18A] MHA : FLPMDK, FLEGHL RRH : AHHB, BTSMED a6d81f
LTE_OPR_AC_9968
AHPMDA, AHEGB - Plan activation failed on NetAct if Not
1.0 inNot
CCLin
DC power source for each LNA is affected CCL_x000D_
CAS-221524-W7Q6 RSSI increased after FXED replacement by AREA BPF xxx/yyy
LTE_OPR_AC_9969 Not in
CCL_x000D_
1.0 Not in
MOAM 151906 Not in
CCL_x000D_
CAS-224047-G0Z3 VoenPak_RIM alarm is not cleared even if RIM status is CCL
LTS 22964
LTE_OPR_AC_9971 Not in
available for all adjacencies defined in eNB CCL
1.0 Not in
CCL_x000D_
PR436116 [SBTS18A[QT][DUALCORE][FID=4076] Distributed site MOAM
UC: BTS 151102 Not in
Trace Data
support not enabled after planned commissioning CCL
Handling 22067
Not in CCL_x000D_
CAS-219350-M8W0 SR000951: BTS Embedded Power Meter for Energy FB1809
BTSMED d1e139
Efficiency Monitoring showing wrong Real-time 5720ec675777af0480
Not in CCL
Measurement for SMOD af451d9c19228daf56b
PR418101 [SBTS18A MP1.0][MR][FSMF+FSMF] After radio 37b Not
MOAM 149503
in CCLNot in
changed from OBSAI to CPRI, RM is does not detected CCL

PR434549 [FL00][FSMr4]mpdcchNarBandNumCatM value is not UEC 726799 Not in

right in CCL
CELLC_RAC_RECONFIGURATION_RESP_MSG
CAS-221663-H3N6 ABIA with Autonomous Restart SS_W1plRx 151132
Not in CCL

PR438721 [SBTS18A][AHEGA][FDD][CNI-44004] Slim Carrier filter bpf1 2898 Not in

doesn't work for AHEGA RF module CCL_x000D_
moam 152040 Not in
CAS-226093-P9W1 [SRAN18A][FSMF]SRAN SITE (L+W+G) is abnormal DCS 87535
CCL_x000D_ Not in
when LTE 4th sector added CCL
admin 32304 Not in
CCL
CAS-230519-Z9G3,CAS- Tx out of order (1907) and no feedback singal (1920) is RFSW_FM-2467
231639-M0B5,CAS- appearing on random sites and resolved after site FRM58.11.R44I
231680-Q5S0 reset,No feedback signal /Tx out of order and RF Not in CCL
PR431092 module filter power missing alarm appearing
[SRAN18A][Airscale][NPSCSV]the parameteron AREA LTS 23544 Not in
LNCEL.eutraCelId
deployed sites,Fault for1910
INBAND NB-IoT filter
(RF Module cell value
input not
power CCL
displayed
missing) is appearing on AREA
PR421794 [R3][LWG][CNI34364][REGRESSION]:Difference BB
between RX main and RX AUX RSSI DBM in IDD-2UD d808f7ebacc87c9b90
BB-hop sector is exceeding more than 20 dbm during bc5a20d744598fd8fdd
CAS-224878-V8W0 gsm cs call
Relation error observed while validating DSS Feature on PDL 9fa 2676
Not inNot
CCLin
SRAN18A CCL_x000D_
WebEM 31869 Not in
CAS-233063- Alarm 9047 and 8502 occurred on 10 SBTS sites, CCL_x000D_
BTSMED d1e139
C2T9,PR431467,PR432017 [Trunk][Airscale][LTE529]manually add LNADJs on WebEM
Not in CCL
32077 Not in
,PR432035,PR432264,PR4 admin,upload in cm operation but there is no refresh for CCL
32915,PR432924
CAS-209480- LNADJs,[SBTS19A][SyVe]
[TECH Cert SRAN]:WCELLUpload in BL-NO-CELL
from Software
state after MCtrl 75374 Not in
G2M7,PR442521 Manager in NetAct
recomissioning nodeB
not to
working,[SBTS19A][SyVe]
change antenna tranmission Plan CCL
provisioning from[Airscale]
pipe,[SBTS19A] CM ManagerWCDMA doesn't
cellwork,[AD-HOC]
not reach on air
[FDD][FSMF]CMPConfig
state after reconfigurationOpration
back Failed on CMT,
[Trunk][Airscale][LTE2294]SWM upload from
Netact,active SW not updated in softwear manager
after rollback on admin,[LTE3435][LTE][FDD][TRUNK]
[FSMF][BTSMED_IT]servingMplaneDN is empty after
BTS SW provsion
CAS-210156- RETs in Disabled State on SRAN Sites after power MOAM 148623 Not in
J9J2,PR422020 failure or site reset,[COMPA][FSM3] no connection to CCL
MHA after rollback to SBTS18SP
CAS-218355-V6P0 [SRAN18SP][FSMF][Airscale] SFPs deinstalled from MOAM 153134 Not in
modules still visible in database. CCL

CAS-227952-D5T1 Alarm ‘7116 Base station service problem with fault- WTS 24141 Not in
6709 DSP concurrent crash error' CCL

CAS-232731-M6K0 LTE_5025I increase after SW upgrade from FL19 0.3PD UEC, CELLC 736504
to FL19 2.1PD. Not in CCL

CAS-232986-X4R3,CAS- FDD/SRAN18/ CM upload failed after register,CM BTSMED 09c1ff

233703-S2Z3 upload failed after SBTS register Not in CCL

PR441866 [FDD][FSMF][FRGY][XL19]After SW upgrade, UI value Migration Rules

of idleLBCellReSelPrio was changed because of FL19/C_Application/S
migration issue C_PARAM/@29533
CAS-171128-M0Y6,CAS- FXED. RF module fail (1907),/HW/FDD/FL17A/FXED CNI-46878
Not in CCL
194260-H5X7,CAS- report 1907 alarm,High FXED fault rate with alarm TXFRM38.11.R23A
201790-C8H1,CAS- out of order (7100),Does not work FXED due to the low
Not in CCL
CAS-219654-D2X8
205792-D5H1 SRAN\4G
temperature\ Issue 3: fault 6261 towards Megaplexer with
VTC
port 49151 under SRAN18SP 2.0.1 release FTM_FL18A_TL18A_
SR18A_CB18A_2019.
CAS-228597-Y2X0 BTS Reset rejected at KKN0156 and LEI0132 [BBC part WTS 23455
06.13_0326 Not in
Murkku lost synchronization even when BTS in CCL
synchronized issue]
CAS-229443-Z6S9 [TDD][FSIH][FZHM]1868 fault after upgrade from DCS 87954 Not in
TL18SP to TL18A CCL

CAS-228814-F9L5,CAS- FL19 FOA: Low DL throughput observed after upgrade FB1809 3ebc14f
228971-T1Q9,CAS- to 1.2PD,FL19 (WDC 5G FOA): No Pcell traffic, low Not in CCL
229216-G8Y1,CAS- throughput, high dropped call rate with 1.0PD,[FL19
229661-Z7T7,CAS-230272-
CAS-230300-X9K3,CAS- 0.1PD][AIRSCALE]
[SRAN19] Automatic- After
Software
upgrade
Updateto FL19
for 4 1.0PD
sites from BTSMED 7d7d4a
T6D2,CAS-231068-
234416-J0L4 L1800
S19 SDROP-5
cells traffic
to S19
seemsDROP-3,SRAN18A
to be very low or :null.,
Site Not in CCL
J2R0,PR438510 [SRAN19]SW
NSAEM: || CSFB
rollback
spike
automatically
issue observedduringonSRAN18A
AT0309 and
CAS-232031-J4K4 AT4362
1.1.1
ProblemSWsites
after
upgrade
post
execution
SRAN19the Drop-5
full-syncUpgrade,[FL19]
command on BTSMED b98e7b
[1.0PD][KPI] Atlanta TAC 30571 and Cleveland 5
BTSMED Not in CCL
AirScale sites VoLTE SIP BYE 481 drops and CSFB
CAS-230519-Z9G3,CAS- Tx out of order
increase,IP TPUT(1907) and no
DL VOL QCI8feedback singalon
degradation (1920) is RFSW_FM-2467
231639-M0B5,CAS- appearing on random sites and resolved
NVL00484,[FL19][FullRack][PET]DL after site
nonGBR FRM58.11.R44I
231680-Q5S0,CAS- reset,No
Throughput feedback signal to
not reaching /Txsame
out oflevel.
order and RF Not in CCL
CAS-229049-T4J8
226986-T1P9 module filter power missing alarm
[FDD][AIRSCALE][FL18SP] FDD without
appearing
long_lat
on AREA
After DEM 40173 Not in
deployed
SW Upgrade_18SP2
sites,Fault 1910 (RF Module filter input power CCL
missing) is appearing on AREA, [SRAN18A][AREA]
PR445443 [1907]STABI][FL19A][FSMF][EAR]
[T&P Tx out of order and no feedback GTS signal
crash (6450)
alarms on GTS 20364 Not in
multiple
after sitesites
block CCL

CAS-211575-F7M0 Backhaul port LED has no light after 18SP upgrade FRI 32539 Not in
CCL_x000D_
FRI 32631 Not in
CAS-231743-X7Z4 We are experiencing reduction in the incoming GTS
CCL 20373 Not in
Handover causing traffic pattern changes leading for the CCL
call drop degradation since upgrade. Case is solved
CAS-234626- [SRAN18A
after SBTS Valid]
reset. MP1.2 upgrade issue for FXDB RMgmtRP1_CarrierAc
X6V5,PR444050,PR445220 900MHz radio module with all cells failed 2G/3G,[CIT] tivationInObsaiRadio.r
Fault 1910 'RF Module filter input power missing' after st 23791 Not in
CAS-235126-J5M3 Power Reset,[SBTS00][CIT][AIRSCALE+AIRSCALE]
[SRAN] [FDD] FRGY looks not supporting CCL_x000D_
MOAM 154672 Not in
LTE2100+3xWCDMA2100
RMODs Degraded after SWtogether due to faulttoidGSM
update connected 1807 CCL_x000D_
RMgmtRP1_InvalidVs
(cells
Invalid frequency channel for the BTS HW) Admin 33376 Not in
wrTimeoutModification
CAS-237327-Y0T9,CAS- "RF Module filter input power missing" Alarm on CCL
MOAM 154930 Not in
ForAntennaLineWithG
237836-L3K0 FXJB,RF Module filter input power missing CCL
smBcchCarriersInObs
aiRadio.rst 23791
CAS-238905-F9W5 WebEM validation error when enable PDLin3031
Not Not in CCL
CCL_x000D_
LTE1530(Reduced LTE Guard Band) with LTE_OPR_REQ_210
redFreqOffset=9.3MHz 09 1.0 Not in
CAS-238276-B7F4 [SRAN18A Valid]: DB persistence for PM files is missing BTSMED
CCL_x000D_f3f1be
with BTSMed18A connected to SBTS17A Not in CCL
LTE_OPR_AC_10586
1.0 Not in
CAS-237040-C9B8 [FDD][FSMF][FID:1868] :LTE cells down post SRAN18A DCS 89302
CCL_x000D_ Not in
1.0.2 upgrade with alarm 1868 'Not Enough Hardware of CCL MOAM 154930 Not in
LCR' CCL_x000D_
DEM 40580 Not in
CCL
CAS-245296-X9T4 [SRAN18A][BTSMED]: Plan Upload error on SRAN18A BTSMED c96b71
BTS after upgrade of BTSMED to SRAN18A MP1.3 Not in CCL

CAS-240305-S3R1 Site stuck in "resetting site" status after SW Upgrade zu VTC

SRAN18AMP1.2 FTM_FL18A_TL18A_
SR18A_CB18A_2019.
05.29_0321_04.01
Not in CCL
 Change effects
Effects on end-user Effects on operator Other effects New functionality
N/A N/A N/A N/A

N/A N/A N/A N/A

No service interruption Stability increase and no None No

KPI degradations

3G service is uninterrupted 3G stability increase None No

None Validation is OK None No

No more RRC reject and NB RRC KPIs are OK None No

IOT set up is OK

None temperatures and FAN N/A N/A

worked in normal range

Temporary service interruption DSP crash and fault 4131 No No

on disabled cells. seen.

Call drop/no service during KPI degradation N/A N/A

crash after snapshot collecting

Temporary service affected on KPI drop due to unavailable No No

disabled cells. resources

Full capacity is available Service is available , lock None No

works OK and also no
stuck TRXs
SBTS 2G sectors are not going SBTS 2G sectors are not No No
down anymore and no alarms going down anymore and
no alarms
No service untill SBTS reset KPI degradation, alarm NO NO
performed, Cells went down (6450)
which means that traffic will cut EFaultId_TechnicalLogUplo
N/A
off. N/A
adRecommended visible. N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

Better HO Improved HO KPI, no Abis None No

failure.

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

None TOPsynchro is available None No

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

No service untill SBTS reset KPI degradation, alarm No No

performed, Cells went down (6450)
which means that traffic will cut EFaultId_TechnicalLogUplo
N/A
off. N/A
adRecommended visible. N/A N/A
N/A N/A N/A N/A

N/A N/A N/A N/A

Temporary resources not after fallback SBTS is not No No

available. OnAir, no calls can be
performed
N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

N/A N/A N/A N/A

Better 3G throughput No HSPA power loss None No

visible, good KPIs

No more CDR on HOs BTS is not sending None No

anymore value 'NULL' for
any dedicated
None No more random
measurement reports
blocking
and None No
no call drops

No loss of service 2nd chain cell status does None No

not change

4G service is available 4G is stable None No

None Snapshot via webEM can None No

be saved

No more call drops Erab drop & CDR KPIs are None No
back to normal

4G service is OK 4G KPis are good and None No

stable

NB IOT service is available NB IOT : no sleepy cells None No

N/A N/A N/A N/A

No cell down , service is All cells up , no alarm None No

available

None CAT M SDU counters are None No

correctly updated

Service is available No cell down , with SSP6 None No

activated

CA is working CA can be configure None No

properly
Service available TOP can be used and sites None No
are stable

Service is available Stability KPI are OK None No

Service available No reset , sites are stable None No

Service available , no drop Stability KPI is OK None No

4G service is available , no Stability KPIs are good None No

interruption

None Alarm "RF Module None No

Unauthorized" (4278)
appearsafter removing
3G service is available 3G stability
rfmplugin is OK
from ENB None No

None Loss of one SYNCE source None No

will be detected

CA works OK after X2 link After X2 link break scenario None No

break eNB is automatically
recovered.
4G service is complete & stable No unexpected alarm None No
visible, no loss of 4G

CA fully in use CA KPI and parameter None No

validation is OK

Service is stable Better stability None No

None MCPA Power Pooling None No

functionality from Rel5.1
radios is available
Service is OK KPI and service are OK, no none no
CDR increase

Network Availability is not Network Capacity is not None No

impacted anymore. reduced anymore.

None Parameter change is taken No No

into account without BTS
reset
None No false alarms of VSWR No No
and TRX BL-RST anymore

2G service is OK No alarm 7116 "Base No No

station Service problem -
DSP applicationâ€
Voice & UL is OK No uplink degradation
‰fatal error No No
service after restart 2G
anymore._x000D_
BTS
Cells are up and running .
Site stable & on air including 2G KPIs are OK No No
GSM cells

None Alarms are reported No No

correctly

None No confusion when No No

analyzing counter/KPI
results.
None Site on air without any fault. No No

None No dummy module in the No No

WebEM Runtime View
No service interruption. Cells are no longer No No
disabled.

None All necessary parameters No No

are displayed properly and
Bandwidth is displayed
No service interruptions. 9.4MHz
AHFB and
correctky
AHIB RRHs
as No No
previously
does not fail during reset.

Services restored Cells do not crash upon No No

activation of LTE3745

None Plan provisioning from No No

NetAct's CM Operation
Manager is successful
No Service degradation. without
No KPI degradation
BTSMED validation
& no None No
error
sleeping cell.

Services has no interruption Stability KPI is OK, no None No

crash observed

None Site reset performed from None No

main WEBGUI will work
after changing from test
Service is available DSP not crashing
dedicated state to ,normal
cells No No
are on air all the time
state.

Services are stable. Software download is None No

successful.No interruption.

Service is restored. No additional BTS reset. None No

No sleepy cells

Stable service. No service degradation No No

during upgrade

Stable service after upgtrade No KPI degradation. None No

Upgrade leaves all cells up
and running
None Correct results from "Static No No
reference sensitivity level"
test from T-gate.
None NbIoT test model will work. None No

None Upgrading from None No

SRAN16.10 to SRAN18A is
OK . All transmission
Services restored All cells are onair,
connections are okno
after No No
upgrade.
alarms raised

No service degradation No KPI degradation. None No

None No relation errors seen. None No

None Improved UL/DL None No

transmission

Better max rate when needed Peak KPIs are optimum, None No
adding NB-IoT cells should
not increase the
None SBTS works good, 2G calls None
assignedPrachFreqOff. No
possible
No service break After changing the GW in no no
the BTS site, connectivity
still stable
No service break After changing the GW in None No
the BTS site, connectivity
still stable
Users will no more have issues No KPI degradation. None No
connecting to the cells.

Speech quality is OK No speech quality None No

complains

Good set up success rate on E-RAB Setup Success None No

VOLTE Ratio for QCI1

None RRH Energy Efficiency None No

counters are displayed in
WebEM with SRAN
None configuration
When updatingwith
a retconfig
only 2G None No
andvia
file 3GNetAct,
RAT (no the4G Lte
RAT)
operation will not fail
None Proper alarms are raised , None No
no more false alarming

None BCF active SW ID is None No

correct on the Netact

No GSM interruption No alarm, 2G service is OK none No

No loss of service Good KPIs and no cell None No

down

3G Call service not impacted 3G KPIs are OK (Rab None No

CDR)

No loss of service to UE users No loss of service & no None No

outages on cells

None SW upgrade works OK None No

No more loss of service Stability increase None No

Throughput is OK RRH (Galaxy family) No No

RFMs are now OK

Service available , no SW update on RF 5.1 No No

temporary loss of service (AHxx aka Galaxy)
modules is working
No loss of service properly.
RRC no more
No cell
blocking
down. on None No
random cell. KPIs are OK

No impact. Visible borders in None No

Centralized RET
management.
No impact. List used for assigning None No
served antenna lines in
step 41 of Commissioning
No impact. 2nd PMTU Discovery test
Wizard:_x000D_ None No
is workingLine
Antenna OKDevices
in WebEM.
RET
is OK _x000D_
Service is now available after Added
In MHAcell is OK , all cells
commissioning the None No
RAT reset is done are OK afterlist
DC voltage addition
is OK &
RAT reset
GSM PS service ok GSM PS service ok None None

3G throughput is OK 3G KPIs are OK None No

None Correct alarm is reported None No

Service is OK after unblock No cell down after unblock None No

None Snapshot collection is OK None No

No call drop KPIs are OK None No

No dropped calls Calls working on Node-3 & No No

Node-4

No service interruption. All cells onAir. No No

None srProhibitTimerCatM is No No
correct

No call drops. No KPI degradation. No No

No service interruption All cells will be onAir No No

WCDMA resources not WCDMA RAT is only No no

available. partially working. Not all
cells are working on SBTS.
No loss of service No spurious resets None No

RF module up and running , UE RF module fully None None

can be serviced operational.

Service is OK DSS is working OK None No

No problems with LTE cells Fault 4261 not No No

anymore present ,LTE cells doesn't
have problems
No more voice calls issues anymore._x000D_
No KPI degradation on None No
snapshot
RRC re-establishment
collection process
RT
runs normally by BTS
(M1006C186)
Services available on working All LTE cells are working in None No
LTE cells. SBTS configuration.

No more Call drop & access No KPI degradation No None

issues

WCDMA resources are WCDMA cells & KPPIs are None No

available. OK after hot remove/insert

None SW now allows up to None No

55Mhz difference between
the 2 carriers on a UHFC
None Problem
1900 RRH with IP sec and None None
connection to SBTS exists
no more
GSM service is OK Cell is up and no KPI drop None No

CS calls quality no more Good KPis on SINR & call None No

degraded. quality/retainability

None SW update on SBTS None No

succeeds between 2
SBTS18A SW versions.
GSM service is available for All GSM Cells and TRX's No No
End Users. are up after plan activation.

LTE resources are available. Fault 6150 is not visible. No No

LTE RAT is working on
SBTS.
No impact. KPI is reliable and reflect None No.
real SINR
Further PLMN & primary PLMN No KPI degradation due to No. No.
HO is working as specified problems with handovers
when a primary & further
None KPI PMare
PLMN files
defined
are OK None No.

LTE resources are available No KPI degradation due to None No.

LTE cells failure on AHCA
RF module.
No impact. Erab counter collecting is None No
correct, all drops use cases
are registered
No impact. Proper alarms alignement None No
in snapshot versus OAM

No impact. Validation error None No

Resources available for calls No KPI degradations None No

Cell is up and service available 4G KPI is OK , cell is up None No.

on 4G

Calls quality is OK, no packet No more packet loss. None No.

loss

Throughput is on expected KPI degradation due to None No impact.

level with CA enabled. problem with CA activation
is no more visible.
LTE service is OK LTE RAT is working on None No.
SBTS.

HSUPA is OK , call can be 3G KPIs are OK None No.

made

No impact. Alarms from proper None No impact.

MRBTS are mapped in
Netact.
Attach to WCDMA cells is 3G is OK when DSS is None No
possible. enabled & RF is connected
with Long Fibers
CS calls are not interrupted. CS call not dropped during None No
Beam switching to BEAM-6
from beam hopping region.
No impact. M5008C50 counter update No impact. No impact.
correctly according to
configured HS-FACH
No call drop is observed after Call drop KPI
baseband not degraded
resources None No
deleting and recreating RF Hop
sector.
Cells from band 900 are Fault 1900 is not visible on None No
available for user. AHPMDA RF module after
adding 2G cells.
LTE cell is accessble after 4G LTE cell is accessbile after None No
RAT reset parameter change and LTE
RAT reset. No KPI drop.
No calls / attach drop on any No SBTS crash visible None No
cell. during high load ongoing.

No Impact. No more BTS clock tuning None No

inaccuracy when Loose
phase and time
Cell now available for attach synchronization
No unexpected Alarmis used.1811 None. NO
and call. Baseband card
autonomous reset as
No impact. recovery Errors
Relation action are
after None No .
Hardware on
displayed Reset
Admin of SBTS.
if
inbandPRBIndexUL is set
No impact. to 6eNBs
All on IoT
report
cell. themselves None No
correctly to be SBTS18A
software.
No Impact. Problems with "Activate None No
remote RF diagnostic test "
solved
LTE cells will be available. S1 links now ill recover None. No
automatically after IPSEC
tunnel switchover.
No GSM calls drop. No GTS crash is observed None No
after TRX deletion from RF.

WCDMA cells are accessible. WCDMA cells are On Air None None
Services are available. and working.

Calls on GSM cells are not GSM cells are up and None None
dropped. working after site reset.

WCDMA cells are accessible WCDMA cells are online None None
for users. after SW update.

Increased Speech Quality with Good Speech Quality with None No

GSM RAT. GSM. AMR12.2 can be
used.
Calls are possible affected Alarms are cleared and RF None No
cells. module is back to On Air
state after unexpected site
No impact. reset scenario.
Ghost' Fiber is no more None No impact.
visible in WebEM.

No impact. Unexpected internal DSP None No impact.

crash and reset is no more
visible.
No impact. PIC configuration set by None No impact.
customer works when
transferring from FSME to
Call quality and throughput KPI's
FSMFare on proper level. None No
degratation will not be visible. RTWP has been corrected.
No quality of calls
Service is restored even after KPIs are restored after
degradation. None No
transmission failure transmission is up

No impact LTE KPI are correctly None No

pegged

None Plan activation works None No

None Dedicated radios will be None No

detected even if one radio
has RF sharing with 3G
No impact. Snapshot collection will be No impact.
enabled. No.
cancelled when connection
to WebEM will be lost. Next
No impact. snapshot collection
minNumRrcCatM is will None No
succed. migrated
properly

None Reset can be done properly None No

No impact. Provisioning request will None. No.

proceed without any
timeouts.
4G service is OK BTS is no more stuck in None No.
"plan activation failed"
state.
Cells are available for the end All cells will be up and None No.
user after unblock working after SBTS block
and unblock operation.
No impact. Recovery scenario with None No.
RP3-01 cable reconnection
will work as expected. After
Cell is available without any DSP crashstart-up
succesfull will not of None No.
without any breaks. happened
secondary when
core itSBTS is
gets sync
handling highcore
from primary loadand
of traffic.
tuning works normally. No
alarms visible.
No impact. PM upload works as None No.
expected.

Service available Stability is OK None No

No impact. RIM status parameter in No impact. No impact.

WebEM and NETACT CM
editor is the same. There is
None no mismatch.to BTS MED None
Connections No
are OK , no risk of loss

No Impact. CM upload failure problem None No.

is no more visible.

No impact. Bandwidth parameters can No impact. No.

be changed using XML file
by operator.
No impact. Plan activation via NetAct None No impact.
will be successfull.

No impact. When operator do BTS SW None No

upgrade after BTSMED SW
upgrade there will be no
No impact. Plan
issueactivation is
in SW update None No
successful
operation. on NetAct if DC
power source for each LNA
None is affected.
RSSI/RTWP/SINR KPI are None No.
better

No impact. Alarm raised on LNADJW No. No.

object will be propely
cleared.
All RAT's and cells are No telecom outage on any No. No.
available for the end users. RAT. All cells are
operational after startup.
None Fault ID:realtime
SMOD 4076 will not be None No
reported afterisstartup
measurment OK with
HWF.
Cells are available. Attach and All cells mapped to CPRI No. No.
calls are possible. RF module are operational
after replace.
No impact. Transparent for end KPI's related to assigning None No.
user. UE to proper BAND has
increased.
No breaks in services. Cells mpdcchNarBandNumCatM
No unexpected faults which No. No.
availability is 100%. value will
cause RAT not
resets
be 0 and
in
CELLC_RAC_RECONFIG
leads to temporary
No impact. Filter on radio
URATION_RESP_MSG.
breakage is set
of RAT. None No.
properly. Cell bandwidth is
as defined.
All 4G resources can be used 4G sectors are all up & None No
running

Service is OK using new radio No alarms on AREA RF None No

module (AREA) module

None. Parameter No. No.

LNCEL.eutraCelId for
INBAND NB-IoT cell the
None No RSSI
value canincrease
be set. None No

None Validation is correct None No

None Operation can now be None No

executed properly

WNCEL up and running ok now WNCEL up and running ok no no

now
Service recovers quickly after RET is enabled correctly None No
power outage on AHEGB

No NetAct database SFP no no

plugins become normal

No service interruption Fault-6709 not exist no no

anymore and WCELL's are
up and running
No call drops No increase of LTE-5025i None No
(call drops)

None CM upload works OK None No

N/A N/A N/A N/A

N/A TRX's will not get faulty no no

status and will work
properly_x000D_
None No alarms visible with
failure reported on None No
mTrace & Megaplexer. It
FXED modules
works OK
N/A No issue with WCDMA no no
Reset

Cells up and running No alarms 1868 and cells no no

up and running

no No KPI impacts no no

None No automatic SW update no no

None Recovery works OK None No

Service is OK using new radio No alarms on AREA RF None No

module (AREA) module

None No unexpected behaviour N/A N/A

after SW migration from FL
to SBTS18SP
None No GTS crash after site N/A N/A
block

no Physical backhaul port LED no no

shows light now

No reduction in the incoming No reduction in the no no

Handover and no call drop incoming Handover and no
degradation after upgrade call drop degradation after
WCDMA and GSM service up alarm
upgrade 1910 RF Module no no
and running Filter input power missing'
not present and WCDMA
no and
It is possible
GSM cellsto from
configure
FXDB no no
up
900toMhz
60Mhz
are bandwidth
up and
with FRGY.
running
N/A KPI's not affected_x000D_ no no
"RF Module filter input
power missing" alarm is not
no Plan activation
observed anymore.
succeeded. no no

no No BTSMED issues when no no

upgrade from SRAN17A to
SRAN18A
No service interruption. All cells are up and running no no
None Plan Upload error on None No
SRAN18A BTS after
upgrade of BTSMED to
Service is available after SRAN18A
Site not stuck
MP1.3
in "resetting
not None No
upgrade visible
site" status
anymore
after SW
Upgrade t
 Testing instruction for the change
Customer Impact Pre-requirements Test execution
Stability N/A Any NB IoT scenario

Operation & Maintenance N/A SW upgrade to

SBTS18A_ENB_0007_00011
2_000016.
Stability Having AHCA RF modules in SBTS SW update to SBTS18A 0.0.1
configuratio with FDSW.

SW Upgrade/Update WCDMA RAT configured on RF SW update to SBTS18A 0.0.1

module rel 5.1 in configuration. SW.

SW Upgrade/Update Upgrade to SRAN18A 0.0.1 & use LTE3145 slim carrier on

validation FXDD radio activation on
SBTS18A SW
Capacity & Performance Upgrade to SRAN18A 0.0.1 NBIOT configured on SBTS.
Inspect network logs to check
if any errors are visible.
Operation & Maintenance N/A After changing 'Climate
control profiling' parameter to
'Optimized Cooling',AMOB
Operation & Maintenance N/A SW update/upgrade
FAN Unit for cooling running
on High speed and generating
lot of noise.
Capacity & Performance N/A 1) Start 3RAT HL
traffic_x000D_
2) Start fetching continuous
New feature/functionality SW is updated, BTS is not Snapshotfull
Perform viacommissioning
Flame
commissioned. tool_x000D_
using Admin.
3) Wait 10.5h
Capacity & Performance N/A SBTS normal use, perform
lock/unlock , monitor the 2G
cells and TRXs
Stability N/A RANDOM 2G SECTOR
GOING DOWN IN SRAN BTS

Operation & Maintenance N/A Snapshot taking.

Operation & Maintenance N/A Configure SBTS with FRHF

RF module.

Capacity & Performance N/A SBTS SW update from

SBTS16.10 to SBTS17A
onwards.
New feature/functionality N/A Activation of LTE3577 feature
on SBTS.

Operation & Maintenance N/A SWAP RF module to AHEGA

unit.

Capacity & Performance N/A Upgrade site to SBST17A

build from SBST16 where
FHEL radio is installed
Operation & Maintenance N/A Upgrading from SRAN16.10
MP1.0 -- SBTS18SP

Operation & Maintenance N/A Swapping cluster from

SRAN16.10 to SRAN18A

Stability 1 ASIA + 1 ABIA + 3 UHBC + 3 SW update to SBTS18A SW

UHIB

Capacity & Performance N/A The correction has been

tested internally and proved to
be fully functional.
Capacity & Performance N/A SW update to SBTS18A SW.
Capacity & Performance N/A Enable 5CC

Operation & Maintenance N/A SBTS normal use

Operation & Maintenance N/A SBTS normal use

Stability N/A Normal SBTS use

Operation & Maintenance Upgrade to SRAN18A SW SBTS normal use, open

WEBEM

Stability N/A AHFIC radio has taken 9

Unexpected Radio Resets
since the SW upgrade
New feature/functionality N/A Collect counters on SBTS.

Capacity & Performance N/A Plan activation on SBTS

Operation & Maintenance Dependency on configuration: Disable LTE4475 or avoid

LTE4475 is enabled. UEs re-RACH in new
coverage level.
Operation & Maintenance N/A Collect counters on SBTS

Operation & Maintenance N/A In runtime add 3 PIC pools

Operation & Maintenance N/A Step1: BTS is running in dual

core configuration_x000D_
Step2: Trigger fault resulting
Capacity & Performance N/A Normal
in secondary
SBTScoreuse.recovery
reset_x000D_
Step3: Active Alarms as well
New feature/functionality Upgrade to load as their Details
Monitor the network
tab in
SBTS18A_ENB_1000_000623_000 particular
compliance LAA
to requirements
cells
051 or higher. verified_x000D_
configured on AZRB radios.
Operation & Maintenance N/A Apply
SW upgrade
Step4: new GPL
from
Secondary template
FL18A
Core backor
other
Drop 3parameters
to OnAir and serviceschangeon that
trigger
FL18A_ENB_0000_000151_0
it_x000D_cell reset.
Operation & Maintenance N/A 20085
Recommissioning
Step5: toCheck services that and
FL18A_ENB_0000_000487_0
requires
recovery BTSresetReset
counter- change
20055.
LCELL-1,12,14
increment_x000D_ from 2T4R to
Operation & Maintenance N/A Send
Step6:plan
2T2R provisioning
Trigger one morefrom fault
NetAct
resultingforinseveral
secondarysitescore
recovery reset_x000D_
Operation & Maintenance Upgrade to SRAN18A 0.1 SBTS normal
Step7: use
Active Alarms as well
as their Details tab
compliance to requirements
Operation & Maintenance Upgrade to SRAN18A 0.1 Whenever WNCEL-
verified_x000D_
4.txBandwidth
Step8: Secondary is configured
Core backto
(value:
to OnAir4.4andMHz).
services on
New feature/functionality N/A No GSM signal and LTE is
it_x000D_
normal after enable
Step9: Check serviceslean GSM
and
recovery reset counter
Operation & Maintenance N/A Use WebEM and validate
increment
configuration on SBTS.

Operation & Maintenance N/A No activity ongoing on the

site.

Stability N/A Happened in the field. eNB

had SU from PT4.3 to 4.4. It
had Spurious reset + fault 10
Operation & Maintenance Upgrade to SRAN18A 0.1 on some
SBTS normal
of theuse,
RFM's.
TOPThe
is
cells did not come up after
used
Software Activation, hence
manual eNB reset was
needed to bring up the cells.
Operation & Maintenance N/A Software Update to SBTS18A
software.

Operation & N/A SW update from WBTS18 to

Maintenance_x000D_ SBTS18A software.

Operation & Maintenance N/A Configure SBTS with 2 SyncE

reference at the same time
and activate the plan on
Operation & N/A SBTS.
Configure SBTS RP1780
Maintenance_x000D_ feature with
caClusterMemberId=4.
Operation & Maintenance N/A AHFIB RF module hosted by
2 optical link. Removal in
runtime primary optical link.
Operation & DualCore FSMF + FSMF Trigger domain ID collision
Maintenance_x000D_ configuration in use. algorythm on SBTS.

Operation & Maintenance N/A Modify priority_1 to another

value(0 to 128) for TOP_F-R
MO and perform site reset.
Operation & N/A Try to configure lcrid
Maintenance_x000D_ parameter in WebEM.

Operation & Maintenance N/A Perform LTE RAT reset by

changing parameter in
runtime.
Stability N/A Perform SW update to
SBTS18A SW.

Operation & Maintenance N/A Select RF module in

comissioning wizard in
WebEM to add to the
Operation & N/A configuration.
Check WebEM runtime view
Maintenance_x000D_ for RP3-01 connection
between SMODs.
Operation & Maintenance N/A Log into Admin using Google
Chrome browser older than
version 68, Firefox older than
Operation & N/A 60
Perform comissioning on
Maintenance_x000D_ SBTS with:
2xASIA+3xABIA+AMIA+FRG
Operation & Maintenance SBTS FSMF + FTIF + 2 x -T+2xFXEB
Validate plan configuration.
issues no
FBBC_x000D_ error_x000D_
1 x FXED_x000D_ - ensure portMode = RF
Operation & N/A
1 x FXDB_x000D_ (value exists)_x000D_
Connection to ToP master 2
Maintenance_x000D_ 1 x FRGT_x000D_ - upgrade
is disconnected.
to
SBTS SW: SBTS18A_ENB_0000_00029
Operation & Maintenance N/A
SBTS18SP_ENB_2000_000727_0 1) BTS onAir,
1_000000 fromAdmin
WebEM
00000_x000D_ connected to BTS, _x000D_
Transport (all ETH links) configured 2) Adding bbPoolAllocPrioList
Operation & N/ATRMOD only:
on Step
along1:withRMOD with correct
allocCriterion and
Maintenance_x000D_ MRBTS-19050/TNLSVC-1/TNL-1/E SW is connected , BTS
allocPriority
THSVC-1/ETHLK-1/modDN = parameters,_x000D_
startup_x000D_
Operation & Maintenance N/A
MRBTS-19050/EQM-1/APEQM-1/C Step1: 2:BTS
3) Adding
Step RMOD gotpower off
TIMINGGROUP
ABINET-1/TRMOD-1 OnAir,_x000D_
MO with distRefPoint
_x000D_
Step2: 3:BBMOD
parameter.
Step RMOD with ( TCOM FDSW is
Operation & Maintenance N/A master
1. Configure
connected WCDMA) WCDMA
and hot and
powered on
GSM
_x000D_ RAT for BTS. Configure
removed_x000D_
8 WCDMA
Step
Step3: 4:BBMOD
Check cellsof( with
fault
TCOM 4-
23
Operation & Maintenance N/A RXes._x000D_
Step 1: WCDMA)
BTS is (alarm
corresponding
master onairhotwith
name ,
2.
SBTS18A_ENB_0000_00042
Configure
alarm
insterted_x000D_
ID , rmod twostatus
PIC pools
)
2_000000_x000D_
(execute
with 3 cells,
threeandtimes)
one PIC pool
Operation & Maintenance N/A Step
On
withAHPMDA
22:cells._x000D_
BTS MED PASSDEVis not
connected_x000D_
removal
3. Checkinif runtime.
all cells are on Air
Step
and 33:PIC "Fault ID:6261
devices are Failure
Operation & Maintenance N/A Snapshot
in connection
allocated taking.
on between BTS
BB._x000D_
4. Set
and iOMS
up NBICor 3rdparameter
party tool"tois
true on some of
visible
Operation & Maintenance N/A Step 1: Long fibers
LCGs._x000D_
connected,
5. Check if all RF FRGP.A
cells are
connected
degraded status by 23Km withfiber
faultand
145
FRGU connected
'DSP allocation to byPIC40km
not
fiber , BTS
possible due Startup
to DSP , resource
parameter 'actDistributedSite'
unavailable'._x000D_
set to 'true'_x000D_
6. Set up NBIC parameter to
Step
false 2:forCheck
suitable status of link,
check if proper fault is
LCGs._x000D_
Operation & Maintenance N/A The following parameters are
changed in BTSSM for
LTE4212:_x000D_
Operation & Maintenance N/A - DlMimoMode:
1. BTS HW equipment
SingleTX_x000D_ are
(SM/RF/FBBx/TR/)
- Change 2T2R to
detected_x000D_
Operation & Maintenance N/A Trigger
1T2R_x000D_
2. Connect
fallback.
additional non-
- Change otherRadio_x000D_
commissioned related
parameters
3. Disconnectto additional
SingleTX non-
Operation & Maintenance N/A commissioned
Start IP connectivity
Radio_x000D_
test via
4. Reset BTS_x000D_
WebEM
5. BTS states check. BTS HW
Operation & Maintenance N/A equipment
WCDMA cell
(SM/RF/FBBx/TR/)
creation in 3+3
configuration
are detected

Operation & Maintenance N/A Check if all HW was correctly

detected in uncommission
configuration to perform
Operation & Maintenance N/A Unplug SFPs with
commissioning opt links,
afterwards
CPRI-F+OBSAI+CPRI-N from
1 ABIA respective opt ports:
Operation & Maintenance N/A SBTS
1, 3, 5 block/ unblockthem
and connect
once again.

Capacity & Performance N/A 1. Performing Delta

commissioning with
configuration
Operation & Maintenance N/A change:_x000D_
Export Site View from
- removal of RX channels in
snapshot.
Cell 4 under MNL-1/MNLENT-
Capacity & Performance Upgrade to SRAN18A 0.2 SBTS is in normal use,
1/CELLMAPPING-1/LCELL-
monitor 3G KPIs
4/CHANNELGROUP-1/CHAN
NEL-2 and CHANNEL-4 in
Capacity & Performance Upgrade to SRAN18A 0.2 SW Monitoring
order to make anditcheck
a IUR
KPIs and Call downlink
supplemental Drops KPIs
carrier,_x000D_
Operation & Maintenance Upgrade to SRAN18A 0.2 Same
- settingHW theconfiguration
actSdlc and
cell parameters
parameter used
to 'True' onbycell 4
customer.
(supplemental 3 ABIAS, 16 cells
downlink
Operation & Maintenance Upgrade to SRAN18A 0.2_x000D_ Change object locking
carrier),_x000D_
1st chain cell status is faulty (with parameter
- PCell (Cellfor1)2ndUL chain
and DL cell
VSWR alarm). which
bandwidthis enabled.
change from
Stability Upgrade to SRAN18A 0.2 Monitor to
10MHz stability
20 MHz,_x000D_
- addition of CAREL objects in
PCell (Cell 1) with lcrId: 2 and
Operation & Maintenance Upgrade to SRAN18A 0.2 Collect the snapshot
lcrId: 4 (relations withvia
cell 2
WebEM
and cell 4 (cell 4 is a
supplemental downlink
Capacity & Performance Upgrade to SRAN18A 0.2 Normal to
carrier) SBTS
allowuse.
3CC DL CA.
_x000D_
2. Performing DL throughput
Stability Upgrade to SRAN18A 0.2 Monitor
to verify stability
proper 3CCKPIsCA with
2 Scells added, Cell 2 (RX &
TX) and Cell 4 (TX only -
Capacity & Performance Upgrade to SRAN18A 0.2_x000D_ Site is workingdownlink
supplemental with all cells
Configure NB IOT on SBTS on air.
carrier).

Operation & Maintenance N/A Use WebEM and validate

configuration on SBTS.

Operation & Maintenance Upgrade to SRAN18A 0.2 Monitor live network

Operation & Maintenance Upgrade to SRAN18A 0.2 Monitor PDCP SDU Data
Volume counters for CAT-M -
PMQAPID: 7 counters -
Capacity & Performance Upgraded to SRAN18A 0.2 Activate SSP6
M8047C4 and M8047C5

Capacity & Performance Upgrade to SRAN18A 0.2 Configure UL CA for

LTE3864_UL
CA_5B_10Mhz+5MHz
Stability Upgrade to SRAN18A 0.2 , use SBTS is on air up and
TOP as synchro feature running. Monitor stability

Stability Upgrade to SRAN18A 0.2 Monitor network

Stability Upgrade to SRAN18A 0.2 Monitor stability

Stability Upgrade to SRAN18A 0.2 SBTS up and running with

load ongoing. Monitor stability

Stability Upgrade to SRAN18A 0.2 Enable FlexiComp feature

Operation & Maintenance Upgrade to SRAN18A 0.2 1. BTS is uncommissioned -

OK_x000D_
2. Radio FRGY is removing
Stability Upgrade to SRAN18A 0.2 Monitor
from SWstability
on BTS -
OK_x000D_
3. Fault 4278 appears -
Operation & Maintenance Upgrade to SRAN18A 0.2 Trigger
OK_x000D_ faulty situation which
requires
4. Rfmplugin SYNCE withalarm
FRGYtoradio be
reported.
is installed - OK_x000D_
Capacity & Performance Upgrade to SRAN18A 0.2 Trigger
5. Fault X2 4278 linkdisappears
failure in inter-
-
site CA.
OK_x000D_
6. Rmf plugin is removed -
Stability Upgrade to SRAN18A 0.2 Monitor
OK_x000D_ for alarm : "No
connection
7. Fault 4278 between
appears primary
again :
and
check BTS extension system
if valid
Capacity & Performance Upgrade to SRAN18A 0.2 module" isSBTS
Configure flapping CAdespite
over X2
we've
and modify
changed LNADJ-id
the secondary
ASIA and the subrack AMIA.
parameter.
Stability Upgrade to SRAN18A 0.2 1. Commissioned SBTS
_x000D_
startup_x000D_
The alarm flapps for some
2. Replace-5
minutes(3 short fibersonce
minutes) to long
Capacity & Performance Upgrade to SRAN18A 0.2 fibers
Check
every (10kmpower
2-3 days +MCPA
10km)
and one Power
in loses
first
chain,
Pooling 23km
in Dual
all the modules in second
band and
connected chainon
(in
triple
theruntime)_x000D_
band
right siteonofAirScale
the on rel
Capacity & Performance Upgrade to SRAN18A 0.2 3.
5.1
Enable
Perform
radios.CRL23388
AMIA.'_x000D_ site reset bytosetting
take
new
scellFastSchedulingSelect
fiberalarm
So, after delays/timings
4352 into
to
use
1
(EFaultId_NoConnectionToBt
Capacity & Performance Upgrade to SRAN18A 0.3 SBTS normal use on
sExtensionUnitAl) 2G,
is raised,
monitor
LTE cellsnetwork
is down. & monitor
disruptions in transmission
Operation & Maintenance Upgrade to SRAN18A 0.3 Perform
lines as well
LTE1042as SBTS activation
TRXs

Stability Upgrade to SRAN18A 0.3 Monitor live network

Stability Upgrade to SRAN18A 0.3 Create some SingleRAN

object with G-900 only (4-4-4)

Capacity & Performance Upgrade to SRAN18A 0.3 Restart 2G BTS

Stability Upgrade to SRAN18A 0.3 Monitor 2G KPIs

Operation & Maintenance Upgrade to SRAN18A 0.3 Monitor the live network, use
possibly a faulty HW FSMF

Operation & Maintenance CAT M is used Upgrade to SBTS18A 0.3

Capacity & Performance Set up :_x000D_ Upgrade to SBTS18A 0.3

LTE eNB: FSMF + FXFC (2G RF
sharing)+RFs_x000D_
Operation & Maintenance 5MHz
Upgrade
config
to SRAN18A
is done_x000D_
0.3 Have swapped together the
Narrowband Iot Inband is in use two SMOD's (and BBMOD's)
of two different AirScale BTS
in the same subrack
Operation & Maintenance Upgrade to SRAN18A 0.3 Check if LNCEL is added to
cell lock list when adding
object APUCCH_FDD
Operation & Maintenance Upgrade to SRAN18A 0.3 Set the parameters of
LTE1530 feature._x000D_
p
SW Upgrade/Update eNB: full RACK SW Upgrade to SBTS18A 0.3
name="actRedFreqOffset"true
3ASIA+3ABIA+AHIB+AHFB+AZRB /p_x000D_
. p
Stability Upgrade to SRAN18A 0.3 Enable LTE3745
name="redFreqOffset"47/p_x
000D_
p name="dlChBw"10
Operation & Maintenance Upgrade to SRAN18A 0.3 MHz/p_x000D_
Activate the feature 'LTE486
PLMN ID selected mobility
p name="ulChBw"10
profiles'
MHz/p_x000D_ at the test SRAN18A
Capacity & Performance None site.
Upgrade
_x000D_ Firstly,
to SBTS18A
directly configure
0.3,
the
monitor
Check parameters
cells
the BW status
by WebEM,
& for
display
These
transmit/Rx
LNCEL-xx are the steps:_x000D_
: it should be
Stability NB-IoT cell is working. Upgrade to Massive NPRACH reception.
_x000D_
9.4MHz.
SRAN18A 0.3 1. Activate the Mobility
profile selection mode
Operation & Maintenance, Upgrade to SRAN18A 0.3_x000D_ Change/return
(moProfileSelect) site to normal
stability Site is in test dedicated state. state and perform site reset in
parameter_x000D_
main
2. CreateWEBGUI. 2 MOPRs
Stability Upgrade to SRAN18A 0.3 Monitor stability
instance (MOPR-1 & MOPR-
2)_x000D_
3. Configure the Mobility
SW Upgrade/Update N/A SW upgrade
profiles mapping to SRAN18A
list 0.3
:(moPrMappingList)
_x000D_
Step 1) Start HL
parameter._x000D_
Capacity & Performance, Upgrade to SRAN18A 0.3_x000D_ traffic_x000D_
Block
4. Defineand unblock
the value all cells
of the
stability All cells are on-air and no Step
one
listedby
2) one
Waitinfor 100x
traffic
parameters:_x000D_ loop.to
unexpected alarms are visible on stabilize
_x000D_
- for 30mins_x000D_
Mobility profile ID
SW Upgrade/Update Use : FSMF + 2 * FBBC or FHBC
BTS. Upgrade
After
Step every
3) to block
SBTS18A
Download
(moPrId)_x000D_ operation,
SW 0.3 without
wait for
activation
- cell stateprofile
Subscriber to be ID
changed
(spid)_x000D_ and alarm is visible.
SW Upgrade/Update N/A After
Perform
- that,SW
We unblock
didn'tupgrade cell,towait
configure Last
for
SBTS18A
alarm clearance
subscriber 0.3
profile IDand of acell's
state
rangechanged
(spidLast) to parameter
OnAir again.
Capacity & Performance Upgrade to SRAN18A 0.3 1.
due Startup
to the with FSMr4
customer plan+ to
AHDA_x000D_
use the single spid value per
2. Commissioning
mobility profile. GSM cells
Operation & Maintenance Upgrade to SRAN18A 0.3 wit Web
1.Set up Element
configuration: Manager: FSMr4
cell1:
+ AHPC ANT1 TX, ANT1 RX,
ANT2 RX; cell2: ANT3 TX,
1xLTE10MHz+NBIOT
SW Upgrade/Update Upgrade to SRAN18A 0.3 Monitor
ANT3
inband_x000D_
RX,network
ANT4 afterRX (FSMr4
upgrade
+ AHDABTS
2.Enter connected,
to Test 1 optical
fiber 9 Gbit/s
Dedicated state._x000D_
CPRI)_x000D_
Operation & Maintenance Upgrade to SRAN18A 0.3 Perform
3. Starting
3.NBIOT Planned
sensitivity
SRT, T-gate is & T-
CTRL L3_x000D_
ok_x000D_
Commissioning
4. Configuring
4.Check NBIOTT-gate ICS start
for GSM
Capacity & Performance N/A SWmeasurement:
uplink
UL upgrade
testmodel to SBTS18A
measured 0.3
cell is 1 for ANT2 measuring
and 2 for ANT4
SW Upgrade/Update N/A SBTS is upgraded to
measuring_x000D_
SBTS18A
5. Starting 0.3 test (T-CTRL L3 +
SRT in use), in this example
Capacity & Performance Standalone NBIOT only configured, Check syslog
"Static reference sensitivity
no other RAT_x000D_ level" as a test from T-
Upgrade to SRAN18A 0.3 gate_x000D_
Capacity & Performance Upgrade to SRAN18A 0.3_x000D_ Wait for cell
- starting UL setup
carrierwith the -
on ant2
Enabled features:_x000D_ given parameters._x000D_
OK (according to SRT
- LTE2664 Load Based PUCCH Check PUCCH/PRACH radio
messages_x000D_
Capacity & Performance Region_x000D_
Upgrade to SRAN17A 1.3.5 resources
SBTS is intoallocation
- starting normal
measure use.
done
GSMby UL
- LTE3071 NB-IoT_x000D_ eNodeB.
Monitor
carrier on 2GANT2KPIs(SRT
- LTE768 PUCCH blanking messages, T-gate
Operation & Maintenance N/A
_x000D_ Changing
measurement the GW in the BTS
etc.)_x000D_
Configure site
- getting reasonable results
blankedPucch=2_x000D_ from ANT2the GW in the BTS
Operation & Maintenance Upgrade to SRAN18A Changing
Configure NB-IoT to be activated in
site
PRB#0: inbandPRBIndexUL=0
(that is the blanked PRB area)
Operation & Maintenance Upgrade to SRAN18A 1.0 Normal BTS operation with
traffic.

Capacity & Performance Upgrade to SRAN18A 1.0 DL 4CA is activated , VOLTE

is activated_x000D_
actUciOnlyGrants = true and
Capacity & Performance Upgrade to SRAN18A 1.0 TTI-bundling
Set up :_x000D_is used
LTE3692 VoLTE Robustness
Enhancement under
Operation & Maintenance Upgrade to SRAN18 1.0 SBTS normal
evaluation in ause
cluster of 29
sites in live network (UDINE
area). Feature components,
Operation & Maintenance Upgrade to SRAN18A 1.0 i.e. Improved TTIB
RETconfigfile download
Exit, via
Proactiveand
WebEm UL NetAct
Grants and
Fake DRX, have been
Operation & Maintenance Upgrade to SRAN18A 1.0 Monitor the
activated in live
sequence.
networkOn
activation of Fake DRX sub-
feature (20/11/18) a
Operation & Maintenance Upgrade to SRAN18A 1.0 Reconfigure
degradation of 2G-SRAN
LTE_5204c or E-
2G+LTE-SRAN
RAB Setup Success Rate
occurred._x000D_
Operation & Maintenance Upgrade to SRAN18A 1.0 Monitor 1910
network alarm on AHDB
& Erab set
(used for GSM
up & VOLTE only)
KPIs

Capacity & Performance N/A SW upgrade from SBTS18SP

to SBTS18A 1.0

Capacity & Performance Upgrade to SRAN18A 1.0 Monitor 3G KPIs

Capacity & Performance Upgrade to SBTS18A 1.0 SBTS is up and running on

SBTS18A 1.0 SW.

SW Upgrade/Update N/A SW update from SBTS18 to

SBTS18A SW.

Stability Upgrade to SRAN18A 1.0 SBTS up and running with

CAT-M and Inband NB-IoT
cells.
Capacity & Performance Upgrade to SRAN18A 1.0 Perform calls on all cells.

Stability RF 5.1 modules installed on SBTS SW update to SBTS18A 1.0

site.

Capacity & Performance Upgrade to SRAN18A 1.0 SBTS up and running with
LTE RAT. Monitor KPIs

Operation & Maintenance Upgrade to SRAN18A 1.0 Check Centrialized RET

management TAB in WebEM

Operation & Maintenance Upgrade to SRAN18A 1.0 Check Served antenna lines
in RET commissioning.

Operation & Maintenance Upgrade to SRAN18A 1.0 Run Path MTU Discovery test
in WebEM twice

Operation & Maintenance Upgrade to SRAN18A 1.0 Add WCDMA cell in runtime
to SBTS configuration.

Capacity & Performance GSM RAT configured on SBTS Toggle GENA in Airscale
configuration. Upgrade to BSC,_x000D_
SRAN18A 1.0 _x000D_
Capacity & Performance Upgrade to SRAN18A 1.0 GENA=NRP3
-Perform = reset
linkBCF
break
=
GENA=YSM-RF_x000D_
between
-Recover RP3 link between
Operation & Maintenance Upgrade to SRAN18A 1.0 SM-RF _x000D_
1)Perform commissioning with
-Performparamters
enabled voice and for
data
RFcalls
modules that do not support
Operation & Maintenance Upgrade to SRAN18A 1.0 LTE1530
Step1: Reset
(e.gsite
Vegas):_x000D_
SBTS1703_x000D_
1.
Step2: Lock WCELs in
LNCEL_FDD.actRedFreqOffs
OMS_x000D_
et = True_x000D_
Step3:Unlock WCELs in OMS
2. redFreqOffset=4.7_x000D_
2)Verify that Fault
"Configuration and RF Module
mismatch for Reduced LTE
Operation & Maintenance Upgrade to SRAN18A 1.0 Collect s snapshot several
times

Capacity & Performance Upgrade to SRAN18A 1.0 Stability testing, extreme high
load , monitor network

Capacity & Performance Upgrade to SRAN18A 1.0 1) The site is in

commissioned and OnAir
state on
Stability Use many (9) WCDMA cells and let SBTS18A_ENB_1000_00062
BTS startup
at least 3 have DSS enabled. 3_000071._x000D_
Connect them through radios in 2) CS & PS calls are triggered
Operation & Maintenance threes_x000D_
Upgrade to SRAN18A 1.0 and calls are placed
step1:srProhibitTimerCatM=tr
Upgrade to SRAN18A 1.0 successfully
ue in bts andon catm
theUE
Node-5
attach&
Node-6._x000D_
to the cell with
Capacity & Performance Upgrade to SRAN18A 1.0_x000D_ UE 3) Calls
actConvVoiceCatM=true
sendsareReestablishment
switched to Node-
in
Two eNBs are configured. LTE1617 Request
1, Node-2,
the cell1._x000D_
to Node-3,
eNB2. & Node-4
is enabled on both eNBs. Flag step2:UE start ho procedure
SW Upgrade/Update Use configuration with FSMF
'RLFbasedRCRsupported' is + SWenb42
to update to SRAN18A 1.0
cell1(simulated
2FBBC/FBBA
enabled on eNBs. Feature ENB)_x000D_
LTE3105 is enabled on eNBs. UE step3:UE ho failure and start
Stability None
is connected to eNB1 and has at SBTS startup on SBTS18A
reestablishement request
least 2 SCells. UE is 3GPP release 1.0 SW installed.
9 or later compatible.
Stability SBTS is up and running
RRCReconfiguration is inonprogress Perform SW update to newer
SBTS18A
to swap SCells at the UE. SBTS18A 1.0

Stability Upgrade to SRAN18A 1.0 Perform Delta commissioning

Capacity & Performance Upgrade to SRAN18A 1.0 Enable AHDB DSS feature

Operation & Maintenance Upgrade to SRAN18A 1.0 Monitor live network

Change 1: (CAS-111419- Upgrade to SRAN18A 1.0 SBTS up and running. KPI

G5T1,PR322590,CAS- check.
112550-W6Y8,CAS-
Capacity & Performance Upgrade to SRAN18A 1.0
128109-P2M5,CAS- Set up SBTS configuration
191721-W1H1)_x000D_ with:_x000D_
User Plane Quality FBBA1 - LTE 6DSP for LTE
Capacity & Performance Upgrade to SRAN18A 1.0 3x2600up(3x20M)_x000D_
SBTS and running. Check
FBBA2 - reserved for LTE but
KPI's.
not used (should be used for
New feature/functionality Mixed OBSAI / CPRI configuration RF
LTEmodule
3x 1800 hot removed then
in RF module._x000D_ (3x20M))_x000D_
hot insert.
Upgrade to SRAN18A 1.0 FSMF - 2DSP reserved for
Operation & Maintenance Upgrade to SRAN18A 1.0 Try
GSM,to comission UHFCforRRH
4DSP reserved LTE
2x1800
with MHz(lack
difference
of resources
biggerfor
1x1800
than 20MHz.
- LNCEL3)
Operation & Maintenance Upgrade to SRAN18A 1.0 Tests for AutoVPN are
performed

Change 1: (CAS-188436- Upgrade to SRAN18A 1.0 SBTS up and running. No

S1M3,CAS-207097-X2Y7) additional actions to be
triggered.
Capacity & Performance AHEGA/AHEGB modules SW update to SBTS18A 1.0
configured on SBTS site. SW and monitor KPIs

SW Upgrade/Update SW is in SBTS18A 0.2 SW update from SBTS18A

0.2 to SBTS18A 1.0

Operation & Maintenance N/A Trigger BAL modification with

BAL xml from NetAct

Operation & Maintenance N/A SBTS is up and running.

Operation & Maintenance Upgrade to SRAN18A 1.1 Check SINR_PUCCH_MAX

(M8005C91) counter value
after update to SBTS18A SW.
Capacity& Performance Upgrade to SRAN18A 1.0 and Perform Handover for
configure 2 PLMNs (one further and between LTE cells :_x000D_
one primary) Case a: UE is connected to
Operation & Maintenance Upgrade to SRAN18A 1.1 PLMN20891
Collect BTS counters
(source cell is
configured with primary PLMN
measurements.
20801 / further PLMN 20891).
SW upgrade/update None UE sends
SW updateA3
to MR
SBTS18A
on 1.1
neighboring
and monitor (also
KPIs configured
primary PLMN 20801 / further
Operation & Maintenance Upgrade to SRAN18A 1.1 Check value of M8006C264
PLMN 20891)._x000D_
counter
Case b: when
UE is RLF triggered
connected to
X2 handover (source
PLMN20801 failed with
cell is
Operation & Maintenance Upgrade to SRAN18A 1.1 Trigger
tx2overall-expiry.
only GSM related
configured alarm.
with primary
PLMN 20801). UE sends A3
MR on neighboring
SW upgrade/update Prepare upgrade to SRAN18A 1.1 Perform planprimary
(configured validation
PLMNto
SBTS18A 1.1 PLMN 20891)
20801 / further

Capacity & Performance None SW update to SBTS18A 1.1

SW and check CSSR 3G
value.
Capacity & Performance None SBTS SW update to
SBTS18A 1.1

Capacity & Performance Upgrade to SRAN18A 1.1 Make Volte Call under
combined super cell

Capacity & Performance Upgrade to SRAN18A 1.1 Try to enable CA feature on

SBTS.

Capacity & Performance Upgrade to SRAN18A 1.1 SBTS is up and running

Capacity & Performance Upgrade to SRAN18A 1.1 SBTS is up and running.

Operation & Maintenance Upgrade to SRAN18A 1.1 Monitor alarm on NetAct.

Capacity & Performance DSS is enabled & RF is connected Perform attach and call on
with Long Fibers. Upgrade to WCDMA cell.
SRAN18A 1.1
Capacity & Performance Upgrade to SRAN18A 1.1 Perform BEAM switch
between 2 different BEAM's.

Operation & Maintenance Upgrade to SRAN18A 1.1 Collect counters and check
M5008C50 counter value.

Operation & Maintenance Upgrade to SRAN18A 1.1 Delete and recreate RF Hop
sector.

Operation & Maintenance Upgrade to SRAN18A 1.1 The AHPMDA is carrying the
L700-5MHz (MIMO2X2) ///
L800-10MHz (MIMO2X2) +
Operation & Maintenance Upgrade to SRAN18A 1.1 Perform
NB-IoT ///LTE RAT reset
U900-
parameter
TX2RX._x000D_change from
ADMIN.
_x000D_
Stability Upgrade to SRAN18A 1.1 SBTS
Add the up2G-900
and running.
(3TRXHigh
per
load ongoing.
cell) to the existing
configuration on AHPMDA.
Operation & Maintenance Upgrade to SRAN18A 1.1 Scenario: NTP sync happens
after BSC time sync done in
SBTS.
SW upgrade/update Upgrade to SRAN18A 1.1 SBTS up and running. No
specific action to be
performed.
SW upgrade/update Upgrade to SRAN18A 1.1 Try to set inbandPRBIndexUL
to 6 for IoT cell.

Operation & Maintenance Upgrade to SRAN18A 1.1 eNBs are activated with
RTPM feature towards
Traffica.
Operation & Maintenance Upgrade to SRAN18A 1.1 RF diagnostic tests in SBTS
Element Manager

Capacity & Performance Upgrade to SRAN18A 1.1 Trigger IPSEC tunnel

switchover.

Operation & Maintenance Upgrade to SRAN18A 1.1 - WCDMA and 2G RATs

are On-Air with IPV6
configuration. _x000D_
Capacity & Performance Upgrade to SRAN18A 1.1 -
SBTS Calls
startup
arewith
placed
WCDMA
at RF
sector.
cells configured
Calls areonworking
AHEGB
fine._x000D_
RF modules.
Operation & Maintenance GSM RAT configured on SBTS. -Trigger Open
Site"GSM
Reset.Traffic
trace"._x000D_
- Lock TRX-3,7 and BTS-
Operation & Maintenance N/A 3310._x000D_
SW Update to SBTS18A 1.1.1
-SW withLockAHEGA
the TRX-RF modules
29._x000D_
configured in BAND1 on
-SBTS. Delete TRX-7 then
Capacity & Performance Upgrade to SRAN18A 1.2 delete TRX-3.
Perform NB-AMR (same
call and
observation
check qualitywith
anddelete TRX-3
throughput.
then delete TRX-7).
Stability Upgrade to SRAN18A 1.2 Site reset is triggered.

Change 1: (CAS-212433- Upgrade to SRAN18A 1.2 Configure SBTS with

J2Y2) SR002074 feature enabled.

Stability Upgrade to SRAN18A 1.2 SBTS up and running. No

addittional actions to be
triggered.
Operation & Maintenance Upgrade to SRAN18A 1.2 Configure PIC on FSMF in
exactly the same way as in
FSME.
Capacity & Performance Upgrade to SRAN18A 1.2 HW swap from FSMF+FXEB
to AirScale+AHEB on
LTE1800. Check KPI's and
Stability Upgrade to SRAN18A 1.2 Create or monitor
calls quality.
transmission fluctuations

Operation & Maintenance SW update/upgrade to SRAN18A Checking LTE1891 micro-

1.2 DTX feature

Operation & Maintenance Upgrade to SRAN18A 1.2 Perform plan activation after
upgrade

Capacity & Performance At site with following radio Upgrade to SRAN18A

connections:_x000D_ 1.2_x000D_
a single core (i.e. 1 FSMF + 1 or 2 Check if the dedicated radio
Operation & Maintenance FBBC):_x000D_
Upgrade to SRAN18A 1.2 modules Snapshot
Execute using CPRIcollection
protocol
1 radio module with RF sharing connected
from ADMIN, to FBBC
and then
can be
between 3G and 4G enabled, 1 or detected or the
disconnect not.connection
Operation & Maintenance Upgrade
more dedicated
to SRAN18A
radio module
1.2 from between any
Perform BTSConfiguration
and Admin, and
SRAN17A
connected with
usingCAT
CPRIM protocol
configured
to then execute snapshot
Management on MRBTS
single core FBBC. collection
which require
again
Operation & Maintenance Upgrade to SRAN18A 1.2 BTS reset using SBTS18A
'minNumRrcCatM' parameter
update.

Operation & Maintenance Upgrade to SRAN18A 1.2 Trigger CM provisioning by

changing any parameter.

Operation & Maintenance Upgrade to SRAN18A 1.2 SBTS is up and running.

Observe LTE cell
availability._x000D_
Operation & Maintenance Upgrade to SRAN18A 1.2 Change the
Perform SBTSpolarity
blockofand
EAC
alarm from
unblock operation.
"Normally open "
to "Closed " in WebEM. Then
Operation & Maintenance FSMF + FSMF configuration set up. BTS
click isonout of power.
Validate RP3-01
& activate.
Upgrade to SRAN18A 1.2 Cable between primary and
secondary cores
Stability FSMF + FSMF configuration set up. Perform extreme high load on
disconnected.
Upgrade to SRAN18A 1.2 SBTS of traffic.
Operation & Maintenance Upgrade to SRAN18A 1.2 PM files generated every 15
mins,after several days
running PM file name still
Stability Upgrade to SRAN18A 1.2 ended with
Normal SBTS"xml.gz"
usage., such
No as
PM.BTS- actions needed to
additional
2350.20190508.231500.ANY.
be performed.
Operation & Maintenance Upgrade to SRAN18A 1.2 xml.gz RIM parameter status
Check
in WebEM and NETACT.

Operation & Maintenance Upgrade to SRAN18A 1.2 Connect SBTS to BTSMED.

No additional actions are
needed.
Operation & Maintenance Upgrade to SRAN18A 1.2 Trigger many CM upload
operations on MRBTS's via
NetAct and check the failure
Operation & Maintenance Upgrade to SRAN18A 1.2 Perform Bandwidth parameter
ratio.
change for TX and RX for
U900 using XML file.
Operation & Maintenance Upgrade to SRAN18A 1.2 Trigger big plan provisioning
activation via NetAct.

SW upgrade/update Upgrade to SRAN18A 1.2 Perform SW update on SBTS

and then trigger BTSMED SW
update.
Operation & Maintenance In Manage Object ALD/LNA 'DC Execute plan activation for
power source' should be configured MRBTS.
as empty._x000D_
None Upgrade to SRAN18A 1.2 SBTS up and running with
AREA RF module configured.
Compare RTWP values from
Change 1: (CAS-224047- Upgrade to SRAN18A 1.2 previously
1. tRIMpollU
replacedtimerFXED
G0Z3) with AREA.set to 5 minutes
parameter
and reset was performed on
Capacity & Performance SW update/upgrade to SRAN18A SBTS node._x000D_
startup with HWF
1.2 2. Post reset RIM interface
enabled.
error alarm observed on the
Operation & Maintenance Upgrade to SRAN18A 1.2 node._x000D_
Verify SMOD power and
3. After
voltage in some
the real-time
duration , for
measurement
all the adjacencies LNADJW
Operation & Maintenance Upgrade to SRAN18A 1.2 1) BTS is OnAir
configured RIM and status
working._x000D_
became available.
2) Change radio FXDB with
Capacity & Performance Upgrade to SRAN18A 1.2 OBSAI
1. Config
to AHDB
3 cells,withall CPRI
(same band 900) on
numCELevelCatM = the same
port.
2_x000D_
Stability ABIA configured on SBTS. Upgrade SBTS
2. Attach
up and
1 CatMrunning.
Ue inNo
to SRAN18A 1.2 cell1(eutraCelId
additional actions= to 257)
be with
celevel = 0_x000D_
performed.
Operation & Maintenance Upgrade to SRAN18A 1.2 1.
3. SBTS is on air
Reestablish to without
Cell2(eutraCelId
unexpected alarms = 258)
and with
celevel = 0
faults._x000D_
Capacity & Performance Upgrade to SRAN18A 1.2 In
2. L+W+G SRAN
Slim carrier Site, add
is enabled fora
4th sector(disable
10 MHz LTE cell with CA) in
supported
LTE by adding
parameters
an extra RF
Capacity & Performance Upgrade to SRAN18A 1.2 Monitor AREA
(according
module filtermodule
7):_x000D_
actDlSlimCarrier =
true_x000D_
Operation & Maintenance Configure IoT in SBTS Check LNCEL.eutraCelId
blankedPucch = 10_x000D_
configuration. parameter for one of the= IoT
numBlankDlPrbsDown
cell.
5_x000D_
Change 1: (PR421794) Upgrade to SRAN18A 1.2 Measure difference between
numBlankDlPrbsUp =5
RX main and RX AUX RSSI
DBM in IDD-2UD BB-hop
Change 1: (CAS-224878- Upgrade to SRAN18A 1.2 sector is NOT exceeding
Preconditions:_x000D_
V8W0)_x000D_ more than
Aircale DualCore
20 dbmisduring
Operation & Maintenance GSM voice call
used_x000D_
Operation & Maintenance Upgrade to SRAN18A 1.2 Radio with
check the BTS
WCDMA operations
is splitted
between
from NetAct
cores. _x000D_
Steps:DSS is activated from
Operation & N/A WebEM the plan to change
Activate
Maintenance_x000D_ TX/RX from ANT-1 to ANT-2
Capacity & Performance in WBTS
Capacity & Performance RET configured on SBTS site. Perform Power Reset or Site
Upgrade to SRAN18A 1.3 Reset on SBTS and check
RET status.
Operation & Maintenance N/A - Start your system with 1
SFP inserted in one given
RF/EXT port_x000D_
Operation & Maintenance N/A -Monitor
Check the
thatactive
WebEM network
is well
showing inventory info for that
SFP_x000D_
Capacity & Performance Upgrade to SRAN18A 1.3 - Remove
After SW upgrade,
that SFPmonitor
and plug it
into another
ERAB DR(LTE_5025i)
RF/EXT is call
port_x000D_
drops rate
Operation & Maintenance Upgrade to SRAN18A 1.3 - Check
1. Prepare
that WebEM
the has
NE(configured
updated inventory the of the SFP
southbound
now pluggedipinofthe BTSMED),
new
Operation & Maintenance N/A. but
SW never
upgraded
port_x000D_register
fromit,FL18
and put
to
the
FL19_x000D_
plugin
- Check of WebEM
that the NE inis still
BTSMED
Validate
showing idleLBCellReSelPrio
the exact same
Operation & Maintenance SW update/upgrade. Monitoringforthe
beforehand._x000D_
parameter
inventory thatnetwork
SFP in the
2. Waiting
original RF/EXT for the
portNE
creates tcp connection with
Operation & Maintenance Upgrade to SRAN18A 1.3 SBTS
BTSMED,in normal
you can use, check
check by
trace server
command 'netstat -anp | grep
$MPLANE IP'_x000D_
Operation & Maintenance N/A RECOVERY_RESET_IND-1
3. After the connection
created, trigger BTSMED
warm reset._x000D_
Operation & Maintenance N/A SWregister
4. upgradeBTS in netact

Stability N/A Monitoring the live network

Operation & Maintenance N/A Upgrade site from SW1 to

SW2 via WebGUI. After all
the cells are up, site reset
Operation & Maintenance Upgrade to SRAN18A 1.3 Execute command: curl -i --
given.
noproxy '*'
http://localhost:9093/debug/pr
Capacity & Performance Upgrade to SRAN18A 1.3 Monitor AREA module
oblematicCacheRecovery

Operation & Maintenance N/A FDD eNodeB with clock

source from TDD (chained)
lost the longiture/latitude
Operation & Maintenance N/A Site block/unblock
values after 18SP software
in loop
upgrade._x000D_
_x000D_
Operation & Maintenance N/A Monitoring
Step Procedurethe live network
Result
after Alarm_x000D_
SW upgrade
1 Commission FDD eNB
Capacity & Performance N/A SRAN18A
from config1.3 SWwith-out
reset upgrade
FYGB device (FIG.1a for
config reference) No
Operation & Maintenance N/A SRAN18Anone_x000D_
Long/Lat 1.3 SW upgrade.
2 Insert HDMI SI (sync-in)
clock from HDMI SO (sync-
Operation & Maintenance N/A MaxTotalBandwidth
out) source TDD, 30mins validation
or
rule for FRGY
confirm (FRGY
clock sync before
supports
collecting60 MHz bandwidth)
result. No
Capacity & Performance N/A SW upgrade
Long/Lat to SRAN18A 1.3
none_x000D_
3 Replace source with
FYGB device. Wait until
Operation & Maintenance N/A Test
FYGBsome reconfiguration
device is detected with
with different
long/lat frequencies.
none_x000D_
4 Remove/unplug FYGB
Operation & Maintenance N/A Upgrade from SRAN17A
and use source clock fromto
SRAN18A
TDD, wait till FYGB device to
disappear on the BTS view &
Capacity & Performance N/A SBTS
free of upgrade to SRAN18A
clock alarm. still with
1.3
long/lat none_x000D_
5 Upgrade to L18SP No
long/lat none_x000D_
6 Set GNSS Location from
AUTO to MANUAL (FIG.1b
for reference) and fill-up the 3
parameter requirements
manually set values appear in
Operation & Maintenance Upgrade to SRAN18A 1.3.1 Test plan upload

SW update/upgrade Upgrade to SRAN18A 1.2.1 SBTS SW upgrade and

monitor status
g instruction for the change
Expected results Unexpected results Corrected in
No unexpected throughput unexpected throughput drops SRAN18A_2.0PD, which
drops and no missing reports and missing reports from is
from ULPHY to MAC PS ULPHY to MAC PS C5/P8 delivery
No unexpected alarms "7115 Flood of alarm 7115 "Failure in SRAN18A_2.0PD, which
Failure in connection between connection between BTS and is
BTS and iOMS or 3rd party iOMS or 3rd party tool" after C5/P8 delivery
tool" are
SBTS is fully
visible
onafter
air. No
SW upgraded
Alarm 1850to isBTSMED18A
unexpectedly SRAN18A 0.0.1
upgrade.
unexpected alarms are 0.0PD on AHCA RF
reported
reported on configured AHCA modules.RF module is in reset
RF modules.
Fault 4001 is not reported on loop. from 4001 is reported on
Fault SRAN18A 0.0.1
WCDMA resources after SW WCDMA resources which leads
to additional SBTS reset.
Missleading information is not "Slim carrier is not supported on SRAN18A 0.0.1
displayed to the end user in FXDD radio module" validation
WebEM when trying to error is visible which is not valid
No unexpected
configure RRC
and activate NBIOT
outcome has
as aFXDD
lot of is
RRC reject
supporting SRAN18A 0.0.1
connection
LTE3145 reject messages messages
LTE3145. visible.
visible for NBIOT cells.
Temperatures and FAN Temperatures at ~+68'C but SRAN18A 0.0.1
worked in normal range FAN is running in MAX speed

SBTS on-air SBTS stays in commissioned SRAN18A 0.0.1

state

Snapshot gathered Crash during snapshot SRAN18A 0.0.1

succesfully. collection.

BTS is onAir and BTS is not onAir after long SRAN18A 0.0.1
commissioned without any startup and there is a visible
additional faults. additional fault: - FaultId: 4341;
No unexpected behavior. Number:
No BCCH7101;alarms
Name:
on Admin
BTS view SRAN18A 0.0.1
Monitor for several days secondary
(BTS view),core
but alarms
autonomous
are
reset as
visible inrecovery
BSC, NetAct
action;
and poor
All cells on air with no alarms SBTS
GSM KPIs._x000D_
2G sectors are going SRAN18A 0.0.1
_x000D_
down with DSP fatal error alarm,
TRX ID
fault lock/unlock
6707 & 6709
clears the
No unexpected behavior. alarmwent
Cells for some
downtime,
and then
following
it SRAN18A 0.0.1
comes(6450)
alarm back.
EFaultId_TechnicalLogUploadR
No unexpected errors and ecommended
Fault 1907 RFcame
module visible.
failure SRAN18A 0.1
alarms are reported by FRHF and Transmission path failure
unit. reported on FRHF unit.
No KPI drop observed. TCH drop is approximately 1.5% SRAN18A 0.1
and Inter HOSR is approx 2%

No KPI drops observed after Impact on KPIs is a SRAN18A 0.1

activation. consequence of feature
activation.
RTWP values are on proper RTWP values shift seen on 3G SRAN18A 0.1
level after RF module SWAP. cells after swapping to new RM
AHEGA.
No alarms no KPI drops Drop Call Rate KPI has SRAN18A 0.1
increased. Abis failures have
increased
Upgrading ok, no alarms, no Incorrect PRACH delay class SRAN18A 0.1
errors information

No alarms, upgrade ok After a site maintenance SRAN18A 0.1

sometimes an alarm is raised on
BSC indicating high error rate on
No DSP crash, no ABIA reset Cells
the timeslot
are down
of a- concrete
required TRX.
eNB SRAN18A 0.1
and NO CELL DOWN/faulty. reset to recover them.

N/A N/A SRAN18A 0.1

No errors. No KPI drops. KPI drop observed after SW SRAN18A 0.1

update.
VS_RRC_reconf_CA_deconfigu
re_fail_rate increase by 50+%
with attempt increasing by
~30%.
eNB worked normally, no DRS success rate drop SRAN18A 0.1
degradaton on KPI

No unexpected behavior RF module gain adjust alarm SRAN18A 0.1

noticed in Multiple RF MOD,
which get clear after reset but
No unexpected behavior appears again
Customer observed
intermittently.
the alarm SRAN18A 0.1
time reported in NetAct is
different with the time reported
No problem during runtime - After in BTS, 8 days
evenSuddenly
later thanBTS current SRAN18A 0.1
all cells are continuously on time.
Autonomous Reset is performed
air, no unexpected alarms - 4383 (Virtual node not
Able to open SRAN Element Unable responding) to open faultSRAN
is raisedElement SRAN18A 0.1
Manager from NetAct Monitor Manager from NetAct Monitor
for 3G WBTS part of SRAN. for 3G WBTS part of SRAN
No Unexpected Radio Reset AHFIC radio has taken 9 SRAN18A 0.1
expected Unexpected Radio Resets since
the SW upgrade
Size of M8006C332 counter Counter M8006C332 is large, it SRAN18A 0.1
is as expected. is a few orders of magnitude
larger than counter M8006C333
Operation finished Operation finished successfully. SRAN18A 0.1
successfully. Plan Plan provisioning is failed due to
provisioning is working PDL validation failure
The NPDCCH
properly without grant for
issues The NPDCCH grant for SRAN18A 0.1
contention resolution shall be contention resolution will be
send in new CSS. send to NB-IoT UE in USS,
Values of M8001C5 are when UE trigger
M8001C5 showsthe higher
re-RACHvalues SRAN18A 0.1
correct. procedure
after SW upgrade.
for a UL data
transmission in new coverage
Configure is ok. When 3 PIC level, Hardware errors.
for LTE4475. SRAN18A 0.1
pools are configured PIC will
work in all cells which are
assigned
Step1: BTS to is
PICrunning
pools.in dual Step1: BTS is running in dual SRAN18A 0.1
core configuration_x000D_ core configuration - OK_x000D_
Step2: Trigger fault 2080 Step2: Trigger fault 2080 using a
No KPIa degradation.
using faultGenerator in faultGenerator
Traffic increaseinwith WebEM accessibility
- SRAN18A 0.1
WebEM - secondary core secondary core
degradation severalrecovery
hoursreset afteris
recovery reset is performedto
upgraded - OK_x000D_
SBTS18A SW.
performed_x000D_
LAA cells recover as expected Step3: LAA cells Activeremain Alarmsdisabled.
as well as SRAN18A 0.1
Step3:
after newActive
GPLAlarmsis applied
as well
or their Details tab compliance to
as their
other parameters
Details tabchange that requirements verified -
trigger
Site is running
cell reset.
compliance without
to requirements Two cells are faulty after
OK_x000D_ SRAN18A 0.1
unexpected
verified_x000D_ alarms. KPI trend upgrade.
Step4: SecondaryAlarm Configuration
Core back to
is normal.
Step4: Secondary Core back error: OnAir Invalid
and services frequency on itchannel
-
BTS Reset
to OnAir and is services
performed onand BTSfor theReset
OK_x000D_ BTS after HW (1807) is SRAN18A 0.1
startup
it_x000D_ is successful (all cells recommissioning
reported
Step5: Check to theservices
faulty
is stuck
cells.
and - all
are On Check
Step5: Air, no services
unexpected and cells
recoveryare down, no faults are
reset counter
Plan
alarms)provision
recovery reset can be proceed Plan
counter provision
reported,
increment manual canFCT
- OK_x000D_ be proceed
reset has SRAN18A 0.1
with response within 270s.
increment_x000D_ to
will
be
Step6:beforced
timeout(270s)
Trigger to one
recover without
more BTS.fault
Step6: Trigger one more fault response. 2080 using a faultGenerator in
BTS
2080going
using in a sync state in in BTS
faultGenerator WebEM going in unsync core
- secondary state in SRAN18A 0.1
BTSMED
WebEM - secondary core BTSMED
recovery reset is performed -
recovery reset is OK_x000D_
4.4Mhz bandwidth in TX for
performed_x000D_ 4.4Mhz
Step7: Activebandwidth Alarms in TX for as SRAN18A 0.1
as well
FXDA.101
Step7: Active canAlarms
be set as
since
well FXDA.101
their Detailscan't be set after to
tab compliance
configured
as their DetailstxBandwidth
tab is upgrade
requirements to SRAN18A.
verified -
supported
Lean GSMby
compliance can
toall work
radionormally MS
requirements cannot get GSM signal after SRAN18A 0.1
OK_x000D_
after
modulesenable lean GSM
handling
verified_x000D_ under enable
the cell. lean GSM with
Step8: Secondary Core back to
SRAN18A
Step8: Secondary Core back SRAN18A, OnAir and services but LTE on side it -is
No WebEM
to OnAir andperformance
services on normal.
WebEm
NOK_x000D_ After
poor disabling
perfomance leanduring SRAN18A 0.1
degradation
it_x000D_ visible during GSM,
configuration
- FaultGSM10 still side
validation
become
reported onnormal
performing
Step9: Check thatservices
scenario.and too.
RMOD-4 (AHPMDA) Availability
No alarmsreset
recovery expected
counter and all Site
status had alarms Operational
- Offiline, due to fault ids : SRAN18A 0.1
cells should be working fine. 6706,
increment state -4019, 1815. Faults 6706
Disabled_x000D_
and 4019 cleared
- Services on RMOD-4 and then site
No extra reset should happen eNB was left
(AHPMDA)waswith down faults
- SU
Availability1815
took and
statuslonger- SRAN18A 0.1
and the cells should come up. than (4001)
Failed, usual
-Operational
BTS forreset
SU. required.
state -
First
Disabledcell was in disabled state.
No unexpected behaviour, no BTSMED shows a flow of error SRAN18A 0.1
errors appears and BTS MED messages from all of SBTSs
is not overloaded under the BTSMED :_x000D_
2018-12-23T02:27:39,293
5215473 [ElementExecutor-1-
HLayer-11-1] ERROR
com.nokia.imp.conversion.impl.d
omains.ParameterConverter - []:
Can't assign value [0] to
No validation error for any "sIntrasearch" wrong value after SRAN18A 0.1
parameter. conversion to SRAN18A

RET devices are up and RET devices are powered off SRAN18A 0.1
running after SW update to after SW update.
SBTS18A.
SyncE reference switching Only one SyncE reference can SRAN18A 0.1
does not work with 2 x SyncE be use.
reference.
No unexpected S1 link errors Transport layer connection SRAN18A 0.1
visible after startup. failure in S1 interface (6202) is
raised when
Affected cells can be caClusterMemberId=4
All cells hosted by AHFIB SRAN18A 0.1
recovered automatically. disabled after primary link
removal.
SRIO LED state is green / ON SRIO LED state is gray/ OFF SRAN18A 0.1
after domain id collision after domain id collision
resolving. resolving.
TOPF_R-1 exist MO exist MO TOPF_R-1 disappeared SRAN18A 0.1
after site reset. after site reset

lcrid' parameter is modificable Input field related to lcrId is not SRAN18A 0.1
in WebEM. available (cell and nb iot cell
also).
RAT reset performed Unexpected Fault Id 2078- SRAN18A 0.1
successfuly without errors. "Eeprom read error" raised
during LTE RAT
No unexpected reset visible BTS reset_parameter
site autonomous change reset as SRAN18A 0.1
after SW update. recovery action after software
update triggered.
Only supported by NOKIA RF Unexpected radio module type SRAN18A 0.1
modules can be added from can be added from Wizard.
dropdown list.
Correct transmission distance Wrong transmission distance of SRAN18A 0.1
of RP3-01 connection RP3-01 connection between
between SMODs SMODs
Login is possible to WebEM. Cannot log into Admin using SRAN18A 0.1
Google Chrome browser older
than version 68, Firefox older
No unexpected alarms. All than cells
LTE 60 in Validated state after SRAN18A 0.1
services and cells are startup- faultID: 4261 visible
working.
- upgrade completed - upgrade completed SRAN18A 0.1
successfully and all successfully but MRBTS-
parameters kept their value 19050/EQM-1/APEQM-1/CABIN
New connection with ToP ET-1/SMOD-1/portMode
topFreqSyncSLS' (M51361C4) has no SRAN18A 0.1
master 1. longer value_x000D_
counter value is too low which.
portMode = ""_x000D_
1) BTS onAir, Admin 1)
- no OK,_x000D_
error triggered to notice the SRAN18A 0.1
connected to BTS,_x000D_ user
2) OK,_x000D_
about this_x000D_
2) bbPoolAllocPrioList along 3) - after NOKvalidating
- after distRefPoint
plan HW error
Step 1: BTS startup
with allocCriterion , cells
and Step 1:input,
OK_x000D_
is triggered:_x000D_
value confusing SRAN18A 0.1
OnAir_x000D_
allocPriority parameters are Step
"Whenever
"Parameter 2: OK *relations
_x000D_
there exist notMOsmet"
added2:correctly
Step fault 10 is without
reported SMOD_R-*
Validation
Step 3: OK_x000D_
warning
having is shown.
Step1:
unexpected
_x000D_ BTS got errors and (first two
parameter/field
Step 4: NOK executions)_x000D_
Fault 23 is SRAN18A 0.1
OnAir,_x000D_
behavior,_x000D_
Step 3: Fault 23 is Step1:
SMOD_R.configDN
reported BTSwithgot OnAir,_x000D_
alarm '7115
is equal BASEto
Step2: BBMOD (TCOM
3) TIMINGGROUP
reported_x000D_ MO with Step2: STATION
distinguished BBMOD (TCOM
INFORMATION'
name (DN)master
of
master
1. BTS4: is
distRefPoint
Step WCDMA)
Onparameter
Correct Air.alarm
No
hot removed
isare WCDMA)
1.
although
SMOD-1 OK._x000D_ hotcells
all
(found removed
are down.
items) _x000D_
and there SRAN18A 0.1
unexpected
added correctly
reported
_x000D_ alarms._x000D_
for fault 23 according 2.
without -Fault
exist OK._x000D_
Fault 1868
MOs 4001reported
and 10 on for BBMOD
all LTE
2. PIC 4001
unexpected
-to Fault
NIDD devices andare
errors set
on up
10and 3.
cell,
and OK._x000D_
10
GSM on cell
SMOD_R-*/SMOD_BP_R-* RMOD down (connected
without any to
correctly._x000D_
Fault
behavior.
BBMOD ID:6261
and 10 "Failure
on RMOD in 4.
Fault
alarms.
BBMOD)
having OK._x000D_
ID:6261
_x000D_ Failure in WebEM SRAN18A 0.1
is reported
parameter/field
3.
connection
All cells are
(connected between
On AirBTS
to BBMOD) without
isand connection
5.
-[4. OK._x000D_
OK_x000D_ between BTS
Tester analysis:]_x000D_
SMOD_BP_R.unitType is and
within
BTSMED
reported
any inorWebEM_x000D_
3rd party tool"
alarms._x000D_ iOMS
According
Step3:
6.
range or
OK._x000D_3rd
BBMOD
FSM|FSIto party
NIDD tool
( TCOM
: items),
(found master it
should
FEG
Step3:
4. is BBMOD
NBIC be
correctly
visible(calculated
parameter TCOMchanged for FEG is not correctly
http://esnidd053.emea.nsn-
WCDMA)
7. NOK.
is required - faults
hot
that 145 calculated
insterted
SMOD- each cell SRAN18A 0.1
on _x000D_
AHPMDA
master WCDMA) radio modules
correctly._x000D_ after for
hot insterted from AHPMDA
RAT LCG3
1.portMode reset areisradio
-net.net/NIDD/Trans/BtsFault/Det modules
performed
visible.
(undefined) PIC
is-
PASSDEV
_x000D_
5. All WCDMA removalcells are after PASSDEV
ails/9041?
OK_x000D_
devices
configured" removal on BB
are not allocated
-NoRATunexpected
disabled reset
status behavior.
is with fault Cells went down
are and
-packageId=25183&version=69&
for
Allthis
services
group. following
operational - SRAN18A 0.1
performed_x000D_
145._x000D_ alarm (6450)
returnUrl=%2FNIDD%2FTrans
OK_x000D_
- All
6. NBIC
services
parameter changed EFaultId_TechnicalLogUploadR
are operational %2FBtsFault%2FSearchResults
_x000D_
For both RFs fault 4076 is
correctly._x000D_ ecommended
All
(at cell
thirdfrom affected
came visible.
execution)_x000D_
%3FshowInherited%3DFalse RMod are SRAN18A 0.1
triggered
7. BTS is On Air. No alarms not Step1:operational
BTS got (OnAir
%26filterByStatus%3D- fault 4261
- on
are visible. LTE cells , no faults on WCDMA
OK_x000D_
1%26versionFilter%3DLatest
cells)
Step2: on FRGU.(TCOM
BBMOD
%26pagination.SortOrder Customer is not
master
informed
WCDMA) what is wrong _x000D_
hot removed
%3Dasc%26pagination.SortBy with
these
%3DVersion
Fault cells.
10 on Cell on FRGP.A are
RMOD(connected to
OnAir but -may
%26pagination.Start
BBMOD) not work correctly
OK_x000D_
because link length
%3D25%26pagination.Limit
But unexpected Fault23km4341ison not
offcially supported
appearedby
%3D25%26selection.IsSelection
BBMOD RF's
- NOK;
Operational configuration RF module failure is raised on SRAN18A 0.1
WCDMA cells when configuring
LTE and WCDMA cells.
According to SCF BTS in not operational with fault SRAN18A 0.1
configuration HW equipment 4352
and HW topology tree is
detected procedure
Fallback and relatedfinished
objects Critical fault 4083 visible in EM SRAN18A 0.1
are presented
succesfully. SBTS
in ADMIN.
is on air. after successful fallback
Disconnected RF module is procedure. Cells operational
deleted
Test proceeds
from EQM_R
and ends state:reference
TOP Disabled missing alarm is SRAN18A 0.1
subtree._x000D_
normally without extra alarms set and sync is lost
There
and sbts
is no
sync
additional,
is ok non-
commissioned
Operational WCDMA
RF visible.
cell ESM executed unexpected SRAN18A 0.1
without any additional reset additional reset after which
created WCDMa cell was not
Correctly detected HW Cablink connecting RMOD
operational SRAN18A 0.1
through long fiber ( 23km or 10
km) is not properly detected
Operational cells. Not operational cells, services SRAN18A 0.1
execution is impossible.

SBTS unblock successfully, After SBTS block unblock, SBTS SRAN18A 0.1
all cells onAir, no alarms. remains with the following
alarms:_x000D_
No throughput degradation Supplemental
Fault 2078 'Eeprom Downlink
readCarrier SRAN18A 0.1
cell is disabled limiting Carrier
error'_x000D_
Aggregation usability, astoa unit'
Fault 10 'No connection result
Snapshot exported from Site Thethe end-user
snapshotDL exported
throughput
fromisSite SRAN18A 0.1
View contains full existing affected.
View does not provide the full
configuration. content of the existing
No unexpected behavior HSPA power loss._x000D_
configuration SRAN18A 0.2
It was observed that there is
situation where power up
dedicatedMeasurementValueI dedicatedMeasurementValueInf
HSDPA power to max values SRAN18A 0.2
nformation doesn't set max on
ormation
measurementnotAvailable : SBTS._x000D_
measurementnotAvailable :
All 16 cells
shouldn't beare
NULL'
on-air Site reset
Fault
NULL' 124 raised,
is needed random
to make
cells SRAN18A 0.2
changes
are not successfully
active._x000D_ setup
After reset, SBTS was set
2nd chain cell status does not 2nd
HSPA chain
powercelltostatus became
request max SRAN18A 0.2
change. disabled.
value.

All sites are stable resets occurs SRAN18A 0.2

Request shouldn't be rejected error "Request rejected as BTS SRAN18A 0.2

is busy

No KPI degradation. Traffic increase with accessibility SRAN18A 0.2

degradation several hours after
upgraded to SBTS18A SW.
No DSP reset , no cell down Resets and cells are down SRAN18A 0.2
after site is upgraded

Calls on NB IOT cells are Calls are not possible on NB SRAN18A 0.2
working. IOT cell.

No WebEM performance WebEm poor perfomance during SRAN18A 0.2

degradation visible during configuration validation
performing that scenario.
No cell outage,no alarm 4216 alarm raised /cells were in SRAN18A 0.2
disable status

Values are correct Values are too large SRAN18A 0.2

Cells are up with SSP6 Cells are down , no alarm SRAN18A 0.2

UL CA for LTE3864_UL Unable to configure UL CA for SRAN18A 0.2

CA_5B_10Mhz+5MHz LTE3864_UL
configuration is available to CA_5B_10Mhz+5MHz
properly set up.
No unexpected reset is Unexpected recovery reset is SRAN18A 0.2
performed. triggered.

No FRI crash observed. FRI is crashing. SRAN18A 0.2

No unexpected alarms. Failure in replaceable beseband SRAN18A 0.2

unit (4335) and fault 4001 are
reported after SW update.
No unexpected alarms visible. DSP group autonomous reset SRAN18A 0.2
(fault 6709) is raised on SBTS.

Enb with FlexiComp enabled DSP crash SRAN18A 0.2

works without crashes

After removing rfmplugin from Alarm RF Module Unauthorized SRAN18A 0.2

ENB (point 6) Alarm RF (4278) does not appear after
Module Unauthorized (4278) removing rfmplugin from ENB
No unexpected
should be raisedresets or WCDMA cells have been down SRAN18A 0.2
alarms and alarm history shows that
DSP crash occurrs after 78
SYNCE alarm is reported on No SYNCE
hours alarms are reported SRAN18A 0.2
of testing.
SBTS. on SBTS.

eNodeB is automatically eNodeB inter-site CA (LTE3022) SRAN18A 0.2

recovering after recovery x2 is not enabled automatically
link failure after recovery from X2 link
No alarm The alarm "No connection
failure SRAN18A 0.2
between primary and BTS
extension system module" is
Configuration is working flapping
Fault 6282_x000D_
is raised after SRAN18A 0.2
properly after reset. _x000D_ modified.
LNADJ-id
The alarm flaps for some
1. SBTS startup without any 1. OK, site-5
minutes(3 operational
minutes) onceon short SRAN18A 0.2
unexpected alarms on short fibers_x000D_
every 2-3 days and we then lose
fibers, all cells on air_x000D_ 2.
all OK, all hardware
the modules detected
connected on
2. Hardware
MCPA PowerisPooling
detected is correctly,
MCPA
the rightPowerfault
site ofPooling
4001
the visible
is noton SRAN18A 0.2
succesfullywith
supported on used
Dual long
band and WCDMA
supported
AMIA.'_x000D_ cells_x000D_
with Dual band and
fibers,band
triple fault AS
4001fromreported
Rel5.1for 3.
triple
So,OK, band
site
after reset
AS from
alarm 4352Rel5.1
No KPI Degradation
WCDMA
radios cells_x000D_ successful_x000D_
Increase
radios in RRC Drops due to
(EFaultId_NoConnectionToBtsE SRAN18A 0.2
3. Manual site reset 4.
M8013C109
NOK - after site
xtensionUnitAl) wasresets there
raised, LTE
performed without are
(DETECTED_RLF_MAX_DL_R
cellsmultiple autonomous site
were down._x000D_
All TRXes should recover
problems_x000D_ ETR)_x000D_
Some
_x000D_
resets of thefault
with sites reported
4001 as thewith SRAN18A 0.3, SRAN18A
automatically after SBTS
4. BTS operational got
after site Increase
1 or 2 TRXes
reason;
ASIA1 in RRC
and
After stuck
ABIA
maximum in BL-RSL
2 HW allowed
change 1.0
restored.
reset, all cells on air Reestablishment
state
can recover the
autonomous resets
issue.
fault 4001
Parameter change is taken attempts_x000D_
Parameter
still affecting change
whole is not taken
WCDMA SRAN18A 0.3
into account without BTS Increase
into
RAT,account
4 LTEin ERAB
until remain
cells next
Drops BTS
reset_x000D_ reset_x000D_
disabled/offline, AHEB rf unit
No alarmsnumber
Reported ,all sitesofup and
eRAB False
Reported alarm
autonomously present
number of of
resets VSWR
eRAB
with with
fault SRAN18A 0.3
with NBR properly counting
running NBR
and
1900TRXremains
three BL-RST after LTE1042
times.
after LTE1042 activation activation
No alarms ,creation of the alarm 7116 "Base station SRAN18A 0.3
object can be done correctly. Service problem - DSPâ€
No subsequent instability ‰application fatal error"
No service degradation Uplink degradation service after SRAN18A 0.3
restart 2G BTS During the
conversation the voice is
Site normal working ,no distorted
GSM RAT out of service with SRAN18A 0.3
alarms ,no cells down DSP crash alarm 6707/6709

0010 fault should be present no alarms at all SRAN18A 0.3

when there is HW issue and
FSP DSP is not detected in
Same level
FSMF (due of
to M8061C140
HW fault) Some eNBs show high SRAN18A 0.3
quantities of M806C140.

Cell is working, no KPI Alarm: Increased BER detected SRAN18A 0.3

degradation, no abnormal on the optical connection to
alarm. Radio Module (1955) happens
No additional module(dummy) on allactivation
After FXFC withof2G
theRF
plan
sharing.
in SRAN18A 0.3
present, no alarms MRBTS-4907, a dummy module
is present in the WebEM
Runtime View
The anchor LNCEL of The cell lock list is empty in SRAN18A 0.3
APUCCH_FDD is added to DELTA
the cell lock list in DELTA
9.4 MHz is displayed 10MHz is displayed , even if the SRAN18A 0.3
LTE1530 feature is enabled and
also the related parameters are
Site on air and all cells are set. gets on air and but "failure
Site SRAN18A 0.3
operational without extra in optical interface" -alarm is
alarms. raised for LNCEL-12806
No crash Cells areAfter
(AZRB). disabled
autonomous
, fault (4383) SRAN18A 0.3
recovery all cells are
operational.
No BTSMED validation error There is BTSMED validation SRAN18A 0.3
error

Cell is working, no KPI Sleeping cell observed, Rx SRAN18A 0.3

degradation power is 0 on sleeping cells.

Normal operation without Crash occurs with following SRAN18A 0.3

crash. print-out on the NB-IoT
cell:_x000D_
Reset is successful. When site reset performed
UeStorage::add() is full at from SRAN18A 0.3
main WEBGUI have
UeStorage.cpp, line: "no
0x28.
response".
No crashes or unexpected DSP crash after 30 hours of SRAN18A 0.3
behavior testing.

SW download happens Download fails, all cells under SRAN18A 0.3

without any problems FSMF (WCDMA) goes down

After cell block/unblock, only New alarms appeared except for SRAN18A 0.3
alarm 7653 (fault 49) the one mentioned in Expected
appeared/cleared. Every cell results. Baseband card
goes OnAir
Cells are onafter
Air without
unblocking.
any autonomous
FID : 1807 onreset
FHCC as with
recovery
20M SRAN18A 0.3
fault. action (2074)
bandwidth occurred.
alarm is visible.

After SW upgrade, all cells After SW update, the site reset SRAN18A 0.3
should have the same status and we have some cells down
as in the previous load with the with faultID 4256 (Fiber
Correct and reasonable Delay
1) 999_x000D_
and Antenna Round Trip SRAN18A 0.3
results: 1) Sensitivity, 2) Error Delay
2) 100_x000D_
exceeded)
rate and 3) FER/BLER from 3) -9999_x000D_
GSM UL
NBIOT ICS
on case
ANT2can be 4) T-gate
NBIOT ICS
can't
start
measure
uplink signal SRAN18A 0.3
tested. correctly fails
testmodel

No alarms , all connection and SRAN BTS upgrade failed. All SRAN18A 0.3
cells up and running transmission connection are lost
after upgrade.
All cells are on air, no alarms All cells aredown, All RFs not SRAN18A 0.3
raised detected (Fault 10) BB bus
reception error (MUKSU) raised
BTS On-Air without any issue (fault
Cells 2016)
disabled SRAN18A 0.3

SBTS scf is converted without SBTS after upgrade presents a SRAN18A 0.3
error, we do not expect any list of Validation Errors.
validation Errors in between.
No UL/DL transmission Too many UL/DL transmission SRAN18A 0.3
failures failure

There should be no shift in Enabling NB-IoT cell will SRAN18A 0.3

PRACH offset when increase prachFreqOff
comparing same setup with parameter.
No unexpected
NB-Iot enabled to
behaviour. On sites which has 900 and SRAN18A 0.3.1
disabled._x000D_ 1800 in master slave
Parameter prachFreqOff configuration and also on SBCF
No connection
'PRACH lose,offset
frequency no errors
used Connectivity is lost.
sites, after any power or SRAN18A 0.3.1
in PUCCH allocation' should transmission fluctuation on site ,
not change its value. 1800 TCH assignment failure
No connection lose, no errors Connectivity is lost. SRAN18A 1.0
occurs on site.
No abnormal increase in Failures on the cells because of SRAN18A 1.0
counter M1001C836. CS RAB M1001C836.

No degradation on VoLTE UL Actual Result:]_x000D_ SRAN18A 1.0

PDCP transmission rate. A degradation of LTE_5311b E-
UTRAN PDCP SDU Loss Ratio
Fake DRX is expected to in the UL QCI1
LTE_5572f E-UTRAN
from 0.16% E-RABto SRAN18A 1.0
improve VoLTE retainability in QCI1
0.22%Dropis observed
Ratio, RAN consistently
View is
TTIB mode due to longer Out- not
when improved.
DL 4CA Unexpected
is
Of-Sync
RRH Energy
detection
Efficiency
timer use. RRH
activated._x000D_
degradation
Energyof Efficiency
LTE_5204c counters
E- SRAN18A 1.0
counters are displayed in On counter
RAB
are not
Setup
displayed
Success
level, in WebEM
Rate
WebEM with SRAN PDCP_SDU_LOSS_UL_QCI_1_
observed.
with SRAN configuration with
configuration with
RETconfigfile is only 2G and When
FNA(M8026C255)
only 2GREtconfigfile
and 3G RAT isis (no
changed,
4G Lte SRAN18A 1.0
3G RAT (no 4G Lte
downloded.RET calibration
RAT) is there
RAT) is an automatic
increased._x000D_
not mandatory calibration.if
Speech quality not(download
is impactedvia
No alarms ,cells up and netact)
The alarm
the 1907
alarm"TXRETU out falure
of is SRAN18A 1.0
running raised raised from time to time
order"
on different SRAN BTS for no
The BCF active SW ID is The BCF active SW ID is not
reason. SRAN18A 1.0
correct on the Netact updated on the Netact side

No alarm 1910 alarm occurs SRAN18A 1.0

eNB - On-Air without any Cells are down due to SRAN18A 1.0
issues. Configuration error: BTS
configuration error (not enough
No call drops, no service HWafor
On few
LCR)
sites(1868),
issue Not
occurs with SRAN18A 1.0
affected enough DSP
increased callordrops
baseband pool
resources for cell detected.
No unexpected alarms and Fault 1905 appears randomly. SRAN18A 1.0
faults visible. RF unit goes into reset.

SW update should proceed SW update fails on one of the SRAN18A 1.0

without any unexpected connected RRH modules.
alarm.
No crash observed. All cells DSP crash occurred on cell SRAN18A 1.0
are working and operational. which enables Cat-M and
inband NB-IoT.
No CQI degradation after CQI degradation after upgrade. SRAN18A 1.0
upgrade. Thr put is OK Throughput degradadion visible.

RF modules are working Fault 10 / 1850 is reported on SRAN18A 1.0

properly after SW update. RF unit after SW update. Cells
located on that unit are faulty.
No KPI drop due to RRC Unexpected RRC blocking is SRAN18A 1.0
blocks. visible on random cells.

Centralized RET management The table shown in Centralized SRAN18A 1.0

has borders. RET management has missing
borders,
List of Served antenna lines in Antenna Line Devices RET is SRAN18A 1.0
RET commissioning has too narrow, and users cannot
proper size. see what radio module it is.
PMTU Discovery completed At the second attempt, the SRAN18A 1.0
and proper display in ADMIN. following message is
shown:"Cannot trigger PMTU
Other cells are not affected discovery"
LTE cell gets restarted after SRAN18A 1.0
during whole cell addittion adding WCDMA cell in runtime.
scenario.
PS Uplane updated same as By above step, the BSC PS SRAN18A 1.0
PCUM IP in BSC Uplane IP remains same as
BSC CS Uplane ip
3G calls are OK WCDMA throughputs is SRAN18A 1.0
degraded after AHGB link break

FAULT (4393: RF Module configuring failed SRAN18A 1.0

EFaultId_ReducedLteGuardB (1900) alarm is raised instead of
andConfNotMatchingFrHwAl) Fault 4393
is reportedare
1.WCELs in ADMIN
onair_x000D_ WCELs can not be onair and SRAN18A 1.0
2.WCELs are all locked alarm 7771 raised after unlock
_x000D_ operation
3.WCELs can be onair
Collection is OK , no break Snapsht collection is NOK SRAN18A 1.0

No CDR increase KPI degradation visible cells SRAN18A 1.0

(2100 MHz), calls are dropping
or rejected.
Calls switched successfully On switching the calls to Node-3 SRAN18A 1.0
& Node-4, mobiles are
unlatched and all the ongoing
BTS is fully onAir calls goes
BTS are dropped.
fully onAir
Noand
calls
right
are SRAN18A 1.0
possible
after thaton
someNode-3
WCDMA& node-4.
cells
start to fall down with faults 125
the value of reported
the valueon of them. One cell on SRAN18A 1.0
srProhibitTimerCatM should srProhibitTimerCatM
each radio module behavesshould like
be
be equal to 2 that. to 0
equal
Successful RLF HO to eNB2. RFL HO to eNB2 fails. SRAN18A 1.0

SBTS OnAir Decreased number of SUs for SRAN18A 1.0

WCDMA

WCDMA cells will reach on air WCDMA RAT is not fully SRAN18A 1.0
state. Services are available. working on SBTS configuration.

Connection with eNB is Connection with eNB is SRAN18A 1.0

possible, eNB reaches On-Air possible, eNB reach On-Air
state._x000D_ state, visible alarm: Diagnostic
HW should
Delta Commissioning
be detected is and
Ok. Files collected
Fault 103 Carrier
-Fault:
power 6450. SRAN18A 1.0
working
sBTS is OnAir
(no alarms
after visible) measurement does not work is
commissioning
after performing SWDL with seen on Rmod_R-4, some cells
AHDB DSS feature is working
activation. (WCDMA)
DSS is NOTareworking
not onair
, only slim SRAN18A 1.0
properly. carrier feature is working.

No alarms , no any cells Fault 4261 raised,LTE cells SRAN18A 1.0

affected on each RAT have problems

All KPI's on good level, HSPA KPI degradation caused SRAN18A 1.0
including RRC re- by Cell update attempt due to
establishment RT RLC unrecoverable error.
All LTE cells are on air.
(M1006C186) 1 LTE cell is not operational. SRAN18A 1.0
Fault 1868 is raised.

No KPI drop on SBTS18A RRC and ERAB drop observed. SRAN18A 1.0
software.

Affected WCDMA cells will After RF hot remove/insert SRAN18A 1.0

automatically recover after WCDMA cells not recovered
that scenario. (disabled state) without any
Comissioning Wizard allows It is not possible to commission SRAN18A 1.0
alarm.
such configuration. such configuration.
Configuration is rejected and
No issue with SBTS During
cannot tests for AutoVPN the
be applied. SRAN18A 1.0
connection connection to SBTS is lost

No unexpected alarms visible. Unexpected alarm "Antenna SRAN18A 1.0

Cells are ok. line switched off due to high
VSWR" randomly appeared.
KPI related to Radio Link are Radio
Affected
Link
ANTL
Failure
andincreased
cell is on SRAN18A 1.0
OK. AHEGA/AHEGB
disabled. modules.

SW update is succesfull. SW update is failing. SBTS is SRAN18A 1.0

not fully operational on target
SW.
All GSM cells and TRX's are Bulk TRX are going in BL-RSL SRAN18A 1.0.1,
in working state after plan post NSA plan run SRAN18A 1.1
activation from NetAct.
Unexpected internal L2 crash Unexpected L2 internal crash is SRAN18A 1.0.1,
is not visible. No alarms and visible. Recovery action is not SRAN18A 1.1
faults raised. All LTE RAT is working. LTE RAT is down on
working propely.
SINR_PUCCH_MAX SBTS.
SINR_PUCCH_MAX SRAN18A 1.1
(M8005C91) counter value (M8005C91) increase by ~15db.
has not increased.
Handover is triggered in case Handover is not triggered in SRAN18A 1.1
a). Handover is not triggered case a) .
in case b).
No gap in collected counters Occasionally on different site SRAN18A 1.1
reports. measurements are missing.

No unexpected alarms rasied. Fault 6253 'Cell configuration SRAN18A 1.1

SW update performed data distribution failed reported
successfully. on AHCA RF module. LTE cells
Counter M8006C264 is is faulty. M8006C264 is not
Counter SRAN18A 1.1
properly incremented if RLF incremented if RLF triggered X2
triggered X2 handover failed handover failed with tx2overall-
with tx2overall-expiry.
Proper alarm is reported to expiry.
No alarm reported to Customer SRAN18A 1.1
Customer when Acitve raw when Acitve raw alarm seen in
alarm seen in snapshot snapshot
No validation error when Validation error occurs for SRAN18A 1.1
loading plan for SBTS18A 1.1 MRBTS with version SBTS18A
1.1 (during loading of the Plan
CSSR 3G on proper level Low
from CSSR
NetAct)3G after SW SRAN18A 1.1
after upgrade to SBTS18A 1.1 upgrade to SBTS18A.
SW.
No unexpected alarms visible Not enough HW for LCR alarm SRAN18A 1.1
after SW update. Cells are up reported on LTE cell- one
LNCEL down
RTP packet loss rate and Both RTP packet loss rate and SRAN18A 1.1
uplink QCI1 packet loss rate uplink QCI1 packet loss rate
have no big degradation have big degradation compared
compared
No unexpected
to normal
alarmssuper
visible. An
to normal
alarm 7107
superwith
cell.fault ID SRAN18A 1.1
cell.works as expected.
CA '6297" raised at the sites where
were activated Inter eNB DL CA
Unexpected internal L2 crash Unexpected
feature L2 internal crash is SRAN18A 1.1
is not visible. No alarms and visible. Recovery action is not
faults raised. All LTE RAT are working. LTE RAT is down on
working
No issuespropely.
with traffic on SBTS. cell' issue is visible on SRAN18A 1.1
Sleeping
WCDMA cells is visible. Calls 3 WCDMA cells due to SHSTM
are possible. HSUPA setup failure with
Alarms from MRBTS are BTSHWFAIL.
Alarm from wrong MRBTS is SRAN18A 1.1
displayed under the same displayed under MRBTS -1 in
related MRBTS on NetAct. NetAct.
Attach and call on WCDMA Attach to WCDMA cell not SRAN18A 1.1
cell is possible. possible when DSS is enabled &
RF is connected with Long
No CS call drop during that Fibers
CS call dropped during Beam SRAN18A 1.1
operation. switching to BEAM-6 from beam
hopping region.
Counter values are aligned M5008C50 counter do not SRAN18A 1.1
with the specification. update correctly according to
configured HS-FACH baseband
No call drop is observed after Call drop is observed after
resources. SRAN18A 1.1
deleting and recreating RF deleting and recreating RF Hop
Hop sector. sector.
No fault 1900 is visible after After adding the 2G-900 (3TRX SRAN18A 1.1
that operation. per cell), the fault number 1900
RF Module configuring failed
Fault 1910 is not raised. Fault
appears1910 'RF
and Module
hits the U900filtercells SRAN18A 1.1
input power missing' raised
during LTE RAT reset parameter
No unexpected alarms, change
BTS crashed
from ADMIN
during a stability SRAN18A 1.1
crashes visible. testing. SBTS outage.

NTP time should used as BSC time is used which results SRAN18A 1.1
active time source in phase error when BSC time is
not accurate.
No unexpected alarms and Fault 1811 Baseband bus SRAN18A 1.1
foults. configuration was rejected is
visible. SBTS is performing
No relation errors visible. Relation Errors are not
reset. SRAN18A 1.1
displayed on Admin if
inbandPRBIndexUL is set to 6
all eNBs reported correct SW Some eNBs report themselves SRAN18A 1.1
version with RTPM feature correctly to be SBTS18A but
towards Traffica. some other report themselves to
be WN18 (RTPM is not
supported in 3G).
Plan validate must work The plan validate only if we SRAN18A 1.1
change the flag to TRUE

No LTE S1 link outage Several LTE outages happen : SRAN18A 1.1

observed. S1 link doesn't recover
automatically after IPSEC tunnel
GSM RAT is back in On Air switchover.
GTS crash is visible after that SRAN18A 1.1
state after that operation. operation. SBTS is i Integrated
to RAN state.
No Alarms and Faults raised Fault 1807 is raised on WCDMA SRAN18A 1.1
on any WCDMA cell after cells located on AHEGB RF
startup. modules. Cells are not on air.
After site reset SBTS is up Alarms related to connection to SRAN18A 1.1.1,
and running without any BSC are visible. Not all GSM SRAN18A 1.2
unexpected alarms related to Cells and TRX's are working
BSC
WCDMA / GSM.
cells are online after after
Fault site
1807 reset.
is raised. WCDMA SRAN18A 1.1.1,
SW update. Calls are cells are offline. Calls are not SRAN18A 1.2
possible. possible on WCDMA cells
located on AHEGA RF module.
AMR FR should use codec Uplink cannot use codec 12.2 SRAN18A 1.2
12.2 at both direction, and even though radio condition is
MOS value is proper level. good.
SBTS is back to On Air state WCDMA cell remains down after SRAN18A 1.2
after site reset. site reset with 7116 Alarm
visible.
No unexpected cablinks are Unexpected (not connected) SRAN18A 1.2
visible in RuntimeView in cablinks are visible in
WebEM. RuntimeView in WebEM.
No unexpected faults are Fault (6708) SRAN18A 1.2
visible on SBTS during regular EFaultId_ExternallyTriggeredDs
work. pFatalErrA is visible on SBTS.
PIC is working as expected on PIC DSPallocation
reset is triggered.
fails because of SRAN18A 1.2
FSMF. limitation that PIC can only be
setup if there is one DCD after
No KPI degradation visible. Various KPIs are degraded f.e. SRAN18A 1.2
PIC allocation
Calls quality are od good increased call drop rate,
level. negative SINR (PUCCH and
RATs are up and running after RAT PUSCH),is downveryeven
highafter
or absense SRAN18A 1.2
link is up backhaul
of RTWP is onup and antennas,
some running
sleeping cell.
Gain in power consumption is Gain in power consumption is SRAN18A 1.2
expected and _x000D_ expected and _x000D_
KPI LTE_5789a: E-UTRAN KPI LTE_5789a: E-UTRAN
Activation is of
Percentage OKSuppressed Percentage
CM plan provision
of Suppressed
fails with SRAN18A 1.2
OFDM Symbols with Micro timeout from BTSwith
OFDM Symbols side._x000D_
Micro DTX
DTX in RF Module shall be Then
in RF any
Modulefurther CM
shall beplan fails
correctly
The radiopegged
correctly modules can be
whenever with
The
peggedradio
"ongoingmodules
whenever RNWconditions
cannot
Plan File
be are SRAN18A 1.2
detected.
conditions are met to activate detected.
activation"_x000D_
met to activate mDTX feature.
mDTX feature. In webEM activation button is
Snapshot execute Snapshot
grayed outexecute failed in the SRAN18A 1.2
successfully in the second second time.
time.
Operation will be successfully Impossible to perform any SRAN18A 1.2
performed. Configuration Management on
MRBTS
BTS reset is successful BTS reset is rejected SRAN18A 1.2
without any issue

CM provisioning will be Error "BTS did'nt respond in SRAN18A 1.2

successfully performed. 270s" will be displayed. CM
provisioning fails.
Activation succeeds._x000D_ Plan is not getting activated due SRAN18A 1.0.2,
LTE cells are fully operational. to BTS is not ready due to SRAN18A 1.2
Calls are possible. ongoing RNW plan
Cells mapped to AHEGB will activation._x000D_
Some WCDMA cells mapped to SRAN18A 1.2
be online after SBTS unblock LTE cellsare
AHEGB areoffline
downafter
without
SBTSany
operation. alarm raised.
unblock operation.
Calls Cells
are not
are not
After succesfull start-up of After alarm due to fault 1858 is
possible.
operational. SRAN18A 1.2
secondary core it gets sync deactivated, alarm due to fault
from primary core and tuning 4001 is triggered_x000D_
No unexpected
works normally. alarms,
No alarms DSP
The BTScrashes are visible.
perform site reset for SRAN18A 1.2
breakages
visible. observed during Affected cellsand
both primary are secondary
not accessible
handling extreme high load on till
FSMF automatic
even ifrecovery.
there are active
SBTS. cells on primary FSMF. Only
secondary should reset.
Netact can display PM data Netact can't display PM data SRAN18A 1.2
including files with edning
"raw.gz"
SOAP SBTS messages have SOAP MeSBTS causing SRAN18A 1.2
proper size. There is no memory leak and increase in
unexpected memory usage cpu usagessage Traces
because
RIM parameter
of big size
valueofisSOAP
the consuming
RIM status mismatch
too much space
betweenin. SRAN18A 1.2
traces.in WebEM and
same SBTS can
WebEM andrunNetAct
out of ismemory
visible.
NETACT. after long uptime.
Information about SBTS
this parameter
No unexpected BTSMED snapshot
is
BTSMED
missleading.
is
havehugeno(over
limitation
600MB).
for SRAN18A 1.2
crashes caused by high trace, and BTSMED support
message flow / CPU usage. max to 20k BTSs, so if user
Failure ratio for CM upload enbale the
Failure ratiotrace
for CMdataupload
on the SRAN18A 1.2
operations is 0% or has very many BTSsis,and
operations almost
the 30
if trace
low failure ratio. data goto NetAct from BTSMED,
BW parameters changes are it willparameters
BW cause the BTSMED
changes aren't SRAN18A 1.2
possible through XML file outage through XML file (U900
possible
(U900 3.8 activation). 3.8 activation).
Plan activation is successfull. Provisioning failure with error SRAN18A 1.2
No unexpected errors visible 'org.apache.axis2.AxisFault:
during that procedure. HTTP ( 500 ) Server' when
All SW update operations will After
tryingthe BTSMED
to apply upgrade is
big provisioning SRAN18A 1.2
be completed successfully. completed,
activation plan BTSviaSW upgrade
NetAct.
will be failed occasionally.
Plan validation is succeed in In MO ALD\LNA when field SRAN18A 1.2
NetAct. ‘DC power source' is not
empty (associated to an ANTL),
RTWP/RSSI & SINR values activation
RTWP of AREA
of a planis higher
on NetAct
than SRAN18A 1.2
on AREA will be closely fails. RSSI is degraded
FXED.
matching to that on FXED,
pending
Post TrimpollU
the level
timer expiry RIM interface alarm not cleared SRAN18A 1.2
measurement
when all the rimaccuracy
status isspec even if all the defined
which is +/-4dB.
available then theSoRimthere adjacencies have RIM status
interface
No
couldunexpected
alarmdifference
be 1dB should
faults visible
be available.
Fault 4067 visible after the SRAN18A 1.2
cleared
during
between theaccuracy._x000D_
startup. All cells are startup. GSM RAT is not
enabled and working.
Also sensitivity or some operational
Measurements
interferer (PIM) are OK
difference Mismatch in power SRAN18A 1.2
could cause difference but this measurements
should not be a case
1) BTS is operational with new 1) BTS operational without cells SRAN18A 1.2
RM._x000D_ mapped on the new RM with
2) All cells are OnAir._x000D_ CPRI which is not detected by
3) Calls possible.
mpdcchNarBandNumCatM SBTS._x000D_
mpdcchNarBandNumCatM SRAN18A 1.2
value should not be 0 in 2) NOK
value is -0cells
in mapped on the
CELLC_RAC_RECONFIGUR CELLC_RAC_RECONFIGURAT
new RM with CPRI are
ATION_RESP_MSG
ABIA is working without any Unexpected
Disabled. fault 6709 is raised SRAN18A 1.2
ION_RESP_MSG
resets. on ABIA. Affected cells hosted
by that ABIA are temporary
1. OK_x000D_ 1. OK_x000D_
disabled due to reset. SRAN18A 1.2
2. According to requirement 2. Cell DL bandwidth is still 10
WBTS_APPS_20140, Cell MHz.
Cell is up &should
bandwidth running be changed Cells are going down due to SRAN18A 1.0.2,
to 8MHz. fault ID 1868 not enough SRAN18A 1.2
hardware for LCR.
No alarms - No feedback signal_x000D_ SRAN18A 1.2
-Tx out of order_x000D_
-RF module filter power missing
Parameter LNCEL.eutraCelId Parameter LNCEL.eutraCelId for SRAN18A 1.2
for INBAND NB-IoT cell the INBAND NB-IoT cell the value is
value can be set. not editable.
No difference RX main and RX AUX RSSI SRAN18A 1.2
DBM in IDD-2UD BB-hop sector
is exceeding more than 20 dbm
No validation error Validation error :_x000D_ SRAN18A 1.2
'Whenever * LCELW-
0.actDynamicSharedSpectrum
BTS is in control. Operation (value:
BTS is out
true)ofiscontrol.
equal to
Operation
true, it is SRAN18A 1.2
can be executed. required
can not be that
executed.
_x000D_
all RMODs with WCDMA cells
All the Cells are up and are connected
WCELL-361 remains
to the same
in BL-NO- SRAN18A 1.3
running, no alarms Airscale
CELL status
BBMOD'._x000D_
from mcRNC side
WCDMA900 and WCDMA2100
are connected to different
ABIAs, belonging to different
cores.
RETs in enabled State on RETs in Disabled State on SRAN18A 1.3
SRAN Sites after power SRAN Sites after power failure
failure or site reset. or site reset
Once removed from a given Even removed, SFP inventory is SRAN18A 1.3
RF/EXT port, the SFP should still observed on the previous
be considered as not present port. Only the state of the SFP
anymore
No alarms,
andalltherefore
cells up and has changed.
Fault-6709 triggering on multiple SRAN18A 1.3
inventory should not be
running site increasing 3-4 sites per day
reported. and due to which the wcells are
No increase in LTE-5025i LTE-5025i increases
down SRAN18A 1.3

CM upload successful CM upload fails SRAN18A 1.3

Step of idleLBCellReSelPrio Step of idleLBCellReSelPrio was SRAN18A 1.3

was not changed. changed.

No FXED failures occuring FXED units getting faulty SRAN18A 1.3

randomly in different regions

mTraces is OK , server is OK fault 6261 towards third party SRAN18A 1.3

trace server (Megaplexer) was
raised.
No issue with WCDMA Reset WCDMA Reset stuck as WTS SRAN18A 1.3
does not create result for
/MRBTS-1/RAT-1/WTS-1/SHUT
Cells up and running Cell is faulty with 1868 alarm
DOWN_RAT_TASK-1 SRAN18A 1.3

No KPI impacts Multiple KPIs impacted. SRAN18A 1.3

Site came up in SW2 and Site came up in SW2 but after SRAN18A 1.3
stable. ~20 minutes site lost the remote
connectivity and took auto
Problematic cache site full- fallback to SW1.
Problematic cache site full-sync SRAN18A 1.3
sync successful failed or not full-sync

No alarms - No feedback signal_x000D_ SRAN18A 1.3

-Tx out of order_x000D_
-RF module filter power missing
Longiture/latitude values is on Longiture/latitude values is SRAN18A 1.3
BTS SM empty on BTS SM

After site block/unblock reset After site block/unblock reset SRAN18A 1.3
BTS is OnAir with no fault 6450 is visible.
unexpected faults visible.
All LED's should behave Physical backhaul port LED SRAN18A 1.3
according with specifications. shows no light.

No alarms, no KPI After SRAN18A SW upgrade, SRAN18A 1.3

degradation incoming Handover KPIs are
degraded for many cells. This
No alarms. All cells are up SRAN18A
degradation1.3 software
caused upgrade SRAN18A 1.3
traffic
and running. triggers
reduction.unexpected 'alarm 1910
RF Module Filter input power
It should be possible to missing' on FXDB 900MHz
MaxTotalBandwidth validation
radio SRAN18A 1.3
configure more than 40 Mhz rule is failing
module wherewhen configuring
all GSM and
bandwidth whith FRGY and more
WCDMA thancells
40 MHz bandwidth.
will be failed.
No to
up alarms,
60 Mhz.
no KPI's affected "RF Module filter input power SRAN18A 1.3
missing"

No validation errors. Validation error reported when SRAN18A 1.3

actRedFreqOffset = 'true',
redFreqOffset = 9.3 and ulChBw
No alarms, no issues with = 20 MHz.issues when upgrade SRAN18A 1.3
BTSMED
BTSMED from SRAN17A to SRAN18A

All cells are up and running. Random cells are going down. SRAN18A 1.3
Upgrade is Plan upload fails for SRAN18A SRAN18A 1.3.1
successful_x000D_ BTS but is successful for
Plan uploads are successful SRAN17A BTS_x000D_
After SW upgrade is finished, _x000D_
Site does not work and internal SRAN18A 1.3.2
the SBTS has to go in onAir There
logs show
is the'1806
following
Communication
state and no alarms or error:_x000D_
failure' reported in SMOD and
unexpected behavior. PLMN-PLMN/MRBTS-350237
'10 No connection to unit'
SBTS_NICE_ETOILE_x000D_
reported in RMOD, then also
The operation
'4019 BTS sitewas autonomous
unsuccessful
reset
becauseas recovery
the actualaction'
configuration
reported
of the SOAMbeforeBTS these wastwo
notfaults
in alarm history
available. There were 0
successful and 1 failed object
operations._x000D_
MESSAGE : The
operation was unsuccessful
because the actual
configuration_x000D_
of the SOAM BTS was not
available. There were 0
successful and 1 failed object
operations._x000D_
STATUS :
FAILURE_x000D_
VERSION : 1.0_x000D_
SUCCESSFUL MOS :
0_x000D_
FAILED MOS : 1_x000D_
2019-07-17 08:54:47: Error
Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified
herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom
you have entered into the Agreement (as defined below).

This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the
agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used,
copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have n ot
entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility
when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the
documentation.

This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability,
capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document,
and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable e fforts to
ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You
identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia
does not warrant that the use of the software in the Product will be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF
AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTA L OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parti es without
the prior written consent of Nokia.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners.

Copyright © 2016 Nokia. All rights reserved.

Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having
carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information”
part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you
as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and f ollow
the recommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at
Nokia for any additional information.
 erein, and only as specified
up of Companies with whom

the purposes defined in the

his document may be used,
Nokia. If You have not
nated, You may not use this
eof.

ssume full responsibility

mprovement of the

ncerning the suitability,

le” basis in this document,
made all reasonable efforts to
ia will correct errors that You
ection of such error(s). Nokia

ANY WARRANTY OF
TNESS FOR A
EVENT WILL NOKIA BE
CIDENTAL OR
E, BUSINESS
DOCUMENT OR THE
T OR ITS CONTENT.

ed to any third parties without

may be trademarks of their

er.

oduct and only after having

Environmental Information”

e would like to encourage you

roduct packaging and follow

e offer, please contact us at