Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
>
<!-- Based on FlexiBTS Alarm Handling Spec. v. 3.1 and FlexiBTS System M
odule HW Alarms Specification v. 3.1
Notes!
A) IsMemberType uses CLogName to find out the logical name of the unit a
nd thus the string used in that call
may differ from the ones used in other rule functions. For example optic
al if is OptIF in CLogName and OIC in DB.
B) comments are allowed inside rules - between rule steps. insert commen
ts rather there, including PR number and reason for change.
version history:
================
lt_1103#0.128 / 30.08.2012 / Hu Qing
PR 95402ESPE04: LTE447: After RP3 cable re-connection RF module stays in
configuring mode Necessary Information Missing.
Allow main optIf reset when fault 1811 reported on it. Condition: 10 resets
per 30 minutes.
lt_1103#0.127 / 13.08.2012 / Jacek Mioduski
PR NA05233739: RL30 - Buffer over/underflow in clock crossing logic (205
4) on RF Sharing site, 10MHz LTE (40W) , 5Mhz GSM 20W
no use of handling fault 2054 on uncommissioned OIC
lt_1103#0.126 / 31.07.2012 / Jacek Mioduski
PR NA05229094: [LGuplus DVT RL30 2.0]alarm 1955 occurred in chained FXCA
instead of first FXCA in MP2.0
if 1955 comes while 32 is handled then suppress 1955
lt_1103#0.125 / 19.07.2012 / Jacek Mioduski
PR NA05233739: RL30 - Buffer over/underflow in clock crossing logic (205
4) on RF Sharing site, 10MHz LTE (40W) , 5Mhz GSM 20W
added handling of 2054 Cancel in FDDC
lt_1103#0.124 / 13.07.2012 / Jacek Mioduski
PR 80828ESPE01: LN3.0 1.4 RP3 alarm 0010 and 4046 generated when changin
g optical cable from opt1 to opt2 from slave RRH
added filtering time 60s (according to RISE) for fault 4064
lt_1103#0.123 / 28.06.2012
PR NA05123254: [LG U+_Jungbu_RL30] Disabled Cell without any Alarm
dont make reset for FR which is disconnected and if cell is already faul
ty then supress 1868
lt_1103#0.122 / 28.06.2012 / Wei Jianbin
PR 35601ESPE05: No alarm 10 when an incompatible FTLB is hot removed
When alarm 10 is processed, alarm 23 should not suppress it according to PR
34897ESPE05:"Fault 23 shall not suppress fault 10 anymore."
lt_1103#0.121 / 19.06.2012 / Zhang Xu
PR 75878ESPE01: No alarm is reported after evHWDetectionFailed for all FSPCs
if BTS status is uncommissioned, process is ignore and ShutdownFSP is not ex
ecuted.
lt_1103#0.120 / 04.06.2012 / Wojciech Mazur (accepted by Jacek Mioduski)
PR 110622ESPE02: Cells down after sw update to RL30 2.0
Fixed generic_group_delay
lt_1103#0.119 / 14.05.2012 / Wei Jianbin
PR 34894ESPE05: Fault 1868 is seen when fault 10 is active
1868 cancel handling is missing,if fault 10 is active.
lt_1103#0.119 / 09.05.2012 / Przemyslaw Dobroc
PR 34788ESPE05: No fault (1868) when fault (23) is active
Corrected handling of 1868. Merged change from LN4.0.
lt_1103#0.118 / 16.03.2012 / Jacek Mioduski
PR 89860ESPE04: After cancelling alarm 1907, 1906 is send and cancelled
to SEM
Dont check alarms in CheckAlarmNumber by fault_Id
lt_1103#0.117 / 29.02.2012 / Jacek Mioduski
PR 33193ESPE05: Unexpected alarm "Cell power failure" (4090) is generate
d after alarm "RF module failure" (1907) is cleared
If FR has reset then buffer/remove in FDU faults for Cells related to th
at FR
lt_1103#0.116 / 27.02.2012 / Jacek Mioduski
PR 89945ESPE04: Alarm 1905 is send twice (severity also wrong), when O&M
handles RX first
if 1905 comes on RX then give it timeout of 2s in FDU so 1905 for TX cou
ld first be handled in FDDC
lt_1103#0.115 / 24.02.2012 / Tomasz Antczak
NA05068011 added fault 4113 handling
lt_1103#0.114 / 07.02.2012 / Lukasz Tekieli
PR 86680ESPE04: Power switch off when Alarm id 1835 was generated
Switch power off after feg recalculation
lt_1103#0.114 / 07.02.2012 / Jacek Mioduski
PR 89101ESPE04: Filtering time is too long, Alarm id 1906
changed filtering time for 1906 Start from 180s to 90s
lt_1103#0.113 / 07.02.2012 / Jacek Mioduski
PR 89099ESPE04: Alarm id 1906 is not send to SEM
bug fix related to PR 87333ESPE04: handle 1906 if 2000 didn't occur
lt_1103#0.112 / 01.02.2012 / Tomasz Grabiszewski
PR 88189ESPE04: Wrong FRHA Fault name (alarm id 1912)
fix problem with detecting pluginunit after sending fault 1912 from 0x9D
00
lt_1103#0.111 / 31.01.2012 / Tomasz Grabiszewski
Corrected Rules errors with RulesRegression.
lt_1103#0.110 / 31.01.2012 / Lukasz Pabis
PR 59592ESPE03: Alarm id4090 after FRHA autonomous reset
Rule CellAlarms_Cancel corrected.
Handling of the 4090 cancel fault corrected.
lt_1103#0.110 / 28.01.2012 / Jacek Mioduski
Bug fix
lt_1103#0.89 / 15.11.2011 / Jacek Mioduski
PR 71061ESPE01: LTE447: LTE cells down during GSM cell parameter change
if 1930 then update object only by SendDirectAlarm
lt_1103#0.88 / 15.11.2011 / Jacek Mioduski
PR 85301ESPE04: After RF module SFP hot remove, alarm id 10 occured
Bug fix
lt_1103#0.87 / 14.11.2011 / Lukasz Tekieli
PR 85517ESPE04: Faraday recovery actions do not work
In OseFatalError_Start Added rule step 154 and 159 for proper triggering
of gpio reset
lt_1103#0.86 / 09.11.2011 / Lukasz Tekieli
PR 83866ESPE04: 1835 (below current) alarm is not reported
PR 84045ESPE04: Alarm 1835 not send to SEM
PR 84284ESPE04: Alarm ID 1835 not send to SEM(WMHC)
PR 84364ESPE04: Alarm id 1834 not send to SEM
Added filtering feg recalculation in MHAAlarms_start steps 10-12
lt_1103#0.85 / 08.11.2011 / Jacek Mioduski
PR 85301ESPE04: After RF module SFP hot remove, alarm id 10 occured
Fault 10 for FR should be ignored if 2000 or 2001 is on its OIC
lt_1103#0.84 / 07.11.2011 / Jacek Mioduski
PR 85170ESPE04: RF Loss of secondary optical interface alarm although ca
ble is connected
If comes 1930 with fault source FR then send alarm for secondary OIC con
nected to this FR
lt_1103#0.83 / 07.11.2011 / Tomasz Antczak
NA05020674 [RL30] VSWR alarm mismatch between FSME(RawAlarmHistory.txt)
and BTSSM.
added rehandling fault 1837 for antennalines
lt_1103#0.82 / 06.11.2011 / Tomasz Antczak
PR 68997ESPE01 FRHA1 unit auto reset if second FRHA2 bloc/unblocked, LN2
.0 EP4.0
PR 83639ESPE04 [LTE1106-b] Unit Autonomous Reset As Recovery Action (625
9) Raised After Slave Unit In Chain Is Hot Inserted Back Into Configuration
time changed from 40 to 90 in wasunitfaulty for fault 6259
lt_1103#0.81 / 04.11.2011 / Lukasz Gemborowski
PR 70554ESPE01: LTE447: Fan broken alarm is not cancelled from BTSSM and
OMS
Fault 1933 handling corrected.
lt_1103#0.80 / 03.11.2011 / Jacek Mioduski
PR NA05016145: [RL30] No alarm or Incorrect alarm display regarding Fail
ure in optical RP3 Interface
case #1: if fault is handled while handling of 32 for its faulty unit th
en stop handling such fault
lt_1103#0.79 / 31.10.2011 / Tomasz Antczak
PR 68997ESPE01 FRHA1 unit auto reset if second FRHA2 bloc/unblocked, LN2
.0 EP4.0
PR 83639ESPE04 [LTE1106-b] Unit Autonomous Reset As Recovery Action (625
9) Raised After Slave Unit In Chain Is Hot Inserted Back Into Configuration
wasunitfaulty added for fault 6259
lt_1103#0.78 / 30.10.2011 / Tomasz Antczak
PR 31069ESPE05: [LTE655-a] FRHA 1+1+1 H made extra self reset after LN2.
0 4.0 to LN3.0 P7 SW update to be OnAir
added 10 sec timeout after alarm was sent
lt_1103#0.77 / 28.10.2011 / Lukasz Gemborowsli
PR 69433ESPE01: incorrect alarm "Failure in Optical RP3 interface (10)"
in stead of 1926.
do not handle fault 10 if 1926 is active on the sam FR unit.
lt_1103#0.76 / 28.10.2011 / Lukasz Gemborowski
PR 84714ESPE04: LTE604-b: (1934) EFaultId_FrFanReducedSetSpeed is active
but SiteInfo.xml does not reflect that the RF Module or RF FANGROUP is degraded
.
behavior of fault 1934 changed (unit state -> degraded, module -> degrad
ed)
lt_1103#0.75 / 28.10.2011 / Song Jiangbo
PPR 84538ESPE04: Fan failure id 1933 not sent to BTS Manager
UnitType FR_FAN is not in FM map, FR_FAN is belong to FANGROUP unittype, and
n FM map only have FANGROUP and no FR_FAN . FaultId 1933 is belong to 3050 group. Cha
nge "FR_FAN" to "FANGROUP"
lt_1103#0.74 / 27.10.2011 / Jacek Mioduski
PR 55436ESPE03: RF Loss of secondary optical interface alarm cancel alth
ough cable is not connect
If 1930 comes for Optical Interface then dont send alarm if there is sti
ll active 1930 for FR connected to this Optical
lt_1103#0.73 / 27.10.2011 / Tomasz Antczak
PR 84909ESPE04: LBT1166: Fault name is missing for fault 4090
added fault text for fault 4090
lt_1103#0.72 / 20.10.2011 / Lukasz Tekieli
PR 97319ESPE02: FSP memory dumps missing from technical report
OseFatalError_start repaired rule to always collect FSP memory dumps
lt_1103#0.71 / 19.10.2011 / Lukasz Tekieli
PR 69310ESPE01: LN2.0 4.0 - FXCA: RET motor jammed alarm (1842) causing
FXCA restart (1806)
PR 83848ESPE04: Baseband bus failure (1906) and Failure in optical RP3 i
nterface (1806) are reported after triggering (1843) EFaultId_ActuatorJamAl
Corrected handling of fault 4046 start and added handling 4046 cancel
lt_1103#0.70 / 19.10.2011 / Tomasz Antczak
PR 31069ESPE05: [LTE655-a] FRHA 1+1+1 H made extra self reset after LN2.
0 4.0 to LN3.0 P7 SW update to be OnAir
Changed plugin unit from FR to FSM for fault 4099
lt_1103#0.69 / 18.10.2011 / Tomasz Antczak
PR 31221ESPE05 H-Type FRIE: eNB not OnAir with FaultID 4003 and 4099 aft
er updated to P7 from LN2.0 4.0
added ignoring of reset counter in case of fault 4099 workaround
lt_1103#0.68 / 04.10.2011 / Lukasz Tekieli
PR 94532ESPE02: Plan with specified ID XXX does not exist
PR 94973ESPE02: SW upgrade failed from LN2.0_ENB_1009_453_04 to LN2.0_EN
B_1009_454_16
Handling 4102 fault implemented
lt_1103#0.67 / 01.10.2011 / Jacek Mioduski
PR 55333ESPE03: RF-Sharing: LN2.0 3.4: TX Failure in MIMO after site res
et
Don't handle 1815 after BTS reset
lt_1103#0.66 / 28.09.2011 / Lukasz Gemborowski
PR 68591ESPE01: [LTE452] Front End Gain is not recalculated on FRGQ afte
r 1836 alarm
FEG recalculation in case of fault 1836 in ASIG mode should be always do
ne.
lt_1103#0.65 / 27.09.2011 / Jacek Mioduski
PR 81600ESPE04: After FTM is rebooted, Site EM failed to Reconnect withi
n the 8 minutes recommended Timer
If SEM won't fetch file SiteEM.xml in 8min then do recovery EnableDirect
BTSManagerConnection
lt_1103#0.64 / 22.09.2011 / Tomasz Antczak
TUD62566 :RL20 Pilot: After FHEA hard power rst RET alarms not cleared a
lthough RET active
added clearing of faults on RET when fault 10 is received and
InformAntennaLineStatus recovery on cancel fault for RET
lt_1103#0.63 / 22.09.2011 / Lukasz tekieli
PR 83438ESPE04: LTE89: VSWR Minor alarm (1838) shows up as critical seve
rity
Wrong rulestep number in AntennaLineAlarams_start, two times 46
lt_1103#0.62 / 15.09.2011 / Tomasz Antczak
PR 83118ESPE04: Alarm 4076(EFaultId_DistributedSiteSupportNotEnabledAl)
Text Description is Missing in Site Manager
text for fault 4076 missing - only description
lt_1103#0.61 / 14.09.2011 / Tomasz Antczak
PR 81857ESPE04: State of the FSP 0x14 updated only to "Degraded" after 1
811-fault of the faraday
1811 cancel removed and gpio setting to true before GPIO recovery
lt_1103#0.60 / 12.09.2011 / Tomasz Antczak
PR 82891ESPE04: "Failure in optical RP3 interface"-alarm (id 10) is canc
elled for FRHA4
also missing filtering time for fault 6259
lt_1103#0.59 / 11.09.2011 / Tomasz Antczak
PR 81840ESPE04: Alarm 4057 EfaultId_RfSwitchedOffAl (as a result of 1837
EFaultId_VSWRMajorAl) is NOT generated to BTS SEM
removed fault 4057 cancel handling and moved 10 sec filtering time for t
his fault to FDDC
lt_1103#0.58 / 09.09.2011 / Jacek Mioduski
PR 82848ESPE04: 52-alarm is sent twice
Fixed bug (wrong numbering of rulesteps) in Customer_alarms_start
lt_1103#0.57 / 08.09.2011 / Tomasz Antczak
PR 82797ESPE04: LTE91- Alarm (6259) RF module Failure generated whenever
module(FHCA) is Blocked from BTSSM
added 10 sec filtering time for fault 6259
PR 84106ESPE02: LTE450: Alarm 6264 "No MME Capacity Assigned by Core Net
work" is missing when relative capacity of all MMEs is set to 0
Added handling of fault 6264.
f_lt_td#0.99 / Id: FlexiFDrules.txt 28819 2011-03-10 10:19:11Z bkaminsk
/ Bartosz Kaminski
PR 74503ESPE04 When the last FSP become faulty because of incompatible S
W version, another FSPs change alarm from 7651 to 7650 after 10 min
Corrected handling of fault 23 in fddc DirectAlarm_Start.
f_lt_td#0.98 / Id: FlexiFDrules.txt 27811 2011-03-08 05:32:44Z liama / M
a Liang
PR 71403ESPE04: WN7.0 Flexi R1 Regression test:Failed to login Site Mana
ger after reset without FTM
Implementation of Fault 10 recovery SEM connect to BTS.(CN3826)
f_lt_td#0.97 / Id: FlexiFDrules.txt 27811 2011-03-08 05:32:44Z liama / L
ukasz Pabis
LTE782-d_FM (Neighbour Information Handling from many sources)
Implementation of the 6265 fault added.
f_lt_td#0.96 / Id: FlexiFDrules.txt 26434 2011-03-01 10:35:15Z brodzki /
Krzysztof Brodzki
PR 73708ESPE04: WN7.0 FlexiRel1 :Cancelled fault (10) visible in SiteMan
ager, when faulty ESM removed
Corrected handling of fault 74
f_lt_td#0.95 / Id: FlexiFDrules.txt 26372 2011-03-01 08:39:25Z brodzki /
Krzysztof Brodzki
PR NA04856907: changed handling of fault 1933
f_lt_td#0.94 / 28.02.2011 / Jouni Kemppainen
PR 73589ESPE04 FEG is recalculated after 1869 has been cleared
- removed recovery action for 1869 in RULE MHAAlarms_start
f_lt_td#0.93 / 22.02.2011 / Jouni Kemppainen
PR 73589ESPE04 FEG is recalculated after 1869 has been cleared
- removed recovery action for 1869 in RULE Customer_alarms_cancel
f_lt_td#0.92 / 22.02.2011 / Mikko Salonen
PR 23316ESPE06 ALMAG FEG recalculation is not triggered by fault 1870 ge
nerated on WMHD
Corrected handling of fault 1870 in case of AISG WMHD
f_lt_td#0.91 / Id: FlexiFDrules.txt 29759 2011-03-16 08:54:23Z pabis /
Wang Gongjin
PR 70367ESPE04: remove the canceled fault (32) for CANCEL_DELAY
Corrected handling of fault 32
f_lt_td#0.90 / Id: FlexiFDrules.txt 29759 2011-03-16 08:54:23Z pabis /
Lukasz Pabis
PR 73022ESPE04: Failure in optical RP3 interface (0010) was not generate
d when fault id 94 was active
Fault 10 should be handled although fault 94 is active. Step 3 added to
NoConnectionToUnit_start
f_lt_td#0.89 / Id: FlexiFDrules.txt 23797 2011-02-16 10:57:38Z pabis / L
ukasz Pabis
PR 73568ESPE04: Baseband Bus failure (1815: EFaultId_BbBus_SyncFailedAl)
is not reported forward
t occur to faraday
Changes in Customer_alarms_start. Added warm FSP reset in case of 4019 f
ault
f_lt_td#0.38 / Id: FlexiFDrules.txt 7963 2010-12-01 09:59:51Z witecki /
Kamil Witecki
PR 70222ESPE04: if it is REL1, 458 should perform FSP reset, otherwise it pe
rforms Faraday reset,
428 should perform always FSP reset other fault will perform Faraday reset a
s earlier
f_lt_td#0.37 / Id: FlexiFDrules.txt 7465 2010-11-30 12:48:26Z pabis / L
ukasz Pabis
PR 61356ESPE04: Single Faraday reco reset is not done after faraday cras
h for postmortem.bin collection
Added FaradayResetForPostmortemMemDump and TransferPostmortemFile recove
ry actions in OseFatalError_Start
f_lt_td#0.36 / Id: FlexiFDrules.txt 7222 2010-11-29 11:51:16Z pabis / Lu
kasz Pabis
CN4456_2 (Automated System Recovery on MHA failure)
Changes in MHAAlarms_start and Customer_alarms_cancel.
FEG recalculation is not executed in case of WMHC, WMHD or when MHA conn
ection is external.
f_lt_td#0.35 / Id: FlexiFDrules.txt 8372 2010-12-02 11:36:40Z mioduski /
Tomasz Antczak
PR 79321ESPE02: RL15_FM_Orignal EAC alarm is always set after toggling a
larm cleared
WasAlarmNumber is ommited for EAC cancel faults
f_lt_td#0.34 / Id: FlexiFDrules.txt 7113 2010-11-27 14:46:04Z tantczak /
Tomasz Antczak
69787ESPE04 LTE168-a: "GTP-U Path Failure"-alarm (id 6150) is sent when
faraday having GTP-u data path supervision fails
70125ESPE04
LTE168-a: FSP state change to "FAULTY" lasts too long ti
me in case of single faraday failure
Changed bahavior of fault 180 for FARADAY for LTE according to WBTS_RECO
V_70106 -one farday faulty whole fsp faulty
f_lt_td#0.33 / Id: FlexiFDrules.txt 7113 2010-11-27 14:46:04Z tantczak
/ Tomasz Antczak
PR 69418ESPE04 LTE168-a: BTS recovery reset not executed (all three FSPs
are FAULTY)
Changed fault 1806 behavior when fault source is FSP and all FSP are ala
rming
f_lt_td#0.32 / Id: FlexiFDrules.txt 6116 2010-11-23 09:30:37Z stoparek
/ Wojciech Stoparek
PR 53144ESPE01: BaseBand bus failure 425
removed checking if 425 fault was reported for more than 10 times
f_lt_td#0.31 / Id: FlexiFDrules.txt 5992 2010-11-22 13:21:20Z walerian
/ Alek Walerianczyk
PR 73963ESPE02: Changed wait timeout to 300000 only for fault 1868
f_lt_td_main#0.30 / 19.11.2010 / Alek Walerianczyk
PR 67077ESPE04: Changed wait timeout to 300000 in generic_group_delay RU
LE (110),removed (102) -according to new RISE requirements
decision for correct alarm number is done. NOTE, this correction should be done
to PARA
in future so that PARA sets volatility to false for pluginunit-attribute
.
f_lt_td_22#0.29 / 28.09.2010 / Wojciech Stoparek, Maciej Tokarz, Jacek M
ioduski
Wojciech Stoparek: PR 65171ESPE04: FXEA: Fault 4046 is not canceled afte
r RET is calibrated properly
fixed 4046 fault handling so it is removed from FDDC fault list when 184
2 fault is active
Maciej Tokarz: PR 67233ESPE04 FXEA: Alarm 1870 can't be cleared after fa
ult cancel - added handling of fault 1870 cancel
Jacek Mioduski: PR 66951ESPE04: LTE168-a: 1806 CommunicationFailureAl no
t reported in test dedicated -state
- if reset has been made then send alarm
Jacek Mioduski: PR 67207ESPE04: "Temperature alarm"-alarm (id 1927) sent
with wrong severity (7655)
- changed severity of alarm
f_lt_td_22#0.28 / 22.09.2010 / Tomasz Antczak
Tomasz Antczak: PR 61838ESPE04: "Faulty" RF module can not be blocked
added handling of fault 4070
f_lt_td_22#0.27 / 16.09.2010 / Tomasz Antczak
Tomasz Antczak: 66746ESPE04 LTE168-a: 1906-alarm comes after FSP MCU spo
ntaneous restart
added new rulestep WasUnitFaulty
f_lt_td_22#0.26 / 13.09.2010 / Tomasz Antczak
PR 65171ESPE04: FXEA: Fault 4046 is not canceled after RET is calibrated
properly
Added supressing fault 4046 when 1842 is active
f_lt_td_22#0.25 / 11.09.2010 /Tomasz Antczak, Lukasz Pabis
Tomasz Antczak: 64991ESPE04: FRMB 1 HW incompatible fault is clear and "
OnAir" after software updated, but no transmitting and receiving power
fault 1868 handling changed - no checking if faults 10 and others are ac
tive for unit
Lukasz Pabis: PR 64428ESPE04: LTE547: No Antenna tilt control feed volta
ges from FFMB.
Added 4069 fault handling.
Tomasz Antczak: PR 66424ESPE04: [LTE655] FSP1&2 SW incompatible SW versi
on detected alarms not cleared after recovery from FCM fallback
Added canceling of alarms with different severity for fault 23 cancel (s
earch for 53519)
f_lt_td_22#0.24 / 07.09.2010 / Roman Bryling, Tomasz Antczak
Roman Bryling: 25257ESPE05, 40003ESPE03 - severity of fault 4064 changed
from degraded to faulty
Tomasz Antczak: PR 74284ESPE02: RL10_FM: 10 EFaultId_NoConnectionToUnitA
l should cancel all active alarms from the same unit
Added checking if FSPs in the same CG are faulty in Customer_alarms_star
t for fault 1906
f_lt_td_22#0.23 / 06.09.2010 / Lukasz Gemborowski, Tomasz Antczak
PR 66467ESPE04: LTE-168a No recovery actions done after faraday crash
Sent alarm changed back to -1 in case of fault 6201, alarm is decided no
w correctly by FDCL decideAlarmLevel()
Tomasz Antczak - added handling of fault 6202 and 6203 (feature)
PR 68635ESPE Tomasz Antczak 1907 FrTxOutOfOrder alarm from FRIE when FSP
C is restarted spontaneously
Changed step 2 in Customer_alarm_start
f_lt_td_22#0.10 / 19.07.2010 / Tomasz Antczak, Przemyslaw Wydra
Przemyslaw Wydra: PR 63992ESPE04: BTS reference clock missing (1898)
Check if ClockGPS_InUse is equal to NotInUse added.
Tomasz Antczak: PR 64495ESPE04: No alarm about missing FSPC - added hand
ling for fault 4068
f_lt_td_22#0.9 / 14.07.2010 / Tomasz Antczak
Tomasz Antczak: 70420ESPE02: No 7653 CELL FAULTY (FR) alarm when fault 2
016: EFaultId_Muksu_SMTimeOffAl is generated from RF link
Piotr Adaszynski: PR 64769ESPE04: CN4332: eNB is going configured state
without reset when S1 link is broken - fixed BTS reset triggering
f_lt_td_22#0.8 / 13.07.2010 / Roman Bryling, Lukasz Pabis
Roman Bryling: 64623ESPE04 severity of faults 1871, 1872, 1873, 1874 cha
nged to working becaus notification alarm expected
Lukasz Pabis: PR 64709ESPE04: Wrong alarm text, Radio Module Switched Of
f (fault 4057)
Piotr Adaszynski: cn4332 - BTS reset triggered by 6201 when faultLocation=0
f_lt_td_22#0.7 / 08.07.2010 / Przemyslaw Wydra, Jacek Mioduski, Tomasz A
ntczak
Przemyslaw Wydra: PR 64222ESPE04: Alarm 4057 does not shut the cell down
Correct 4057 handling, bug in distinguish between Medusa and non-Medusa
fixed.
PR 63360ESPE04: ALMAG: Wrong WMHC behaviour when licences deleted - adde
d writing state of all MHA in cell to FDCL
PR 63706ESPE04: FXDA: Alarm (1932) not detected and reported in SEM
Fault 1932 handling added.
70420ESPE02: No 7653 CELL FAULTY (FR) alarm when fault 2016: EFaultId_Mu
ksu_SMTimeOffAl is generated from RF link
Changed subrack to bs in case of fault 2016 doallunitsreport rulestep
f_lt_td_22#0.6 / 05.07.2010 / Roman Bryling
Roman Bryling: fault 4064 added
f_lt_td_22#0.5 / 05.07.2010 / Przemyslaw Wydra, Roman Bryling
PR 63969ESPE04 - LTE155-a: RF Module Failure alarm is not cancelled in B
TS after clearing alarm EFaultid_FrTxOutOfOrder (Fault 1907) via Tassu
PR 50314ESPE01 bug fixed in Customer_alarms_cancel added IsStoredInFdcl for
Subunit and orginalFaultId
PR 63748ESPE04 - bug in Fan_delay fixed
f_lt_td_22#0.4 / 29.06.2010 / Tomasz Antczak, Przemyslaw Wydra, Jacek Mi
oduski, Roman Bryling
PR 64100ESPE04: LTE 899a: Alarm id 1869: EFaultId_MinorTMAFaultAl cancel
not work
Added checking if fault is stored to the main unit (step 48 in Customer_
alarms_cancel)
PR 62878ESPE04 & PR64019ESPE04 - Added different reset behavior scenario
s for faults 1815 and 476 on LTE (warm reset) and WCDMA (cold reset). (step 151
in rule Customer_alarms_start)
PR 62434ESPE04 - System module cold start does not work
PR 64087ESPE04: added checking in FanFailure_Start and FanFailure_Cancel
if unit type is FANGROUP
PR 18599ESPE06: bug fixed in Customer_alarms_cancel.
mmissioned FR modules.
f_lt_22#0.93 / 09.06.2010 / W1 (Tomasz Antczak, Maciej Tokarz, Lukasz Pa
bis)
PR NA04701543: Changed handling of fault 10 for ext ALD (added steps 33,
34)
PR 62807ESPE04: Filtering time need to be adde to 4057: EfaultId_RfSwitc
hedOffAl failure
Added filtering time 3 min 10 sec for 4057 (timeout for 1837 + 10 sec)
FBIA Hot Remove and EFaultId_ConnectionToUnitLostAl (4052) - added Shutd
ownFSP as recovery action
in NoConnectionToUnit_start rule (step 76)
PR 39453ESPE03: Fault EFaultId_NtpTimeNotSetAl (26) was not raised up
f_lt_22#0.92 / 08.06.2010 / Przemyslaw Wydra
PR 63227ESPE04: LTE 654-c: O&M does not reconize 6262 EFaultId_InvalidVe
ndorSpecificFile alarm
Fault 6262 handling added.
f_lt_22#0.91 / 07.06.2010 / Lukasz Gemborowski
PR 60891ESPE04: DirectAlarm_Cancel changed handling of 1833 cancel.
f_lt_22#0.90 / 06.06.2010 / Tomasz Antczak
PR 63171ESPE04: LTE85 - "Power level not supported" text is missing from
Configuration error alarm
Changed rule working - added setting faulttext for fault 4008.
f_lt_22#0.89 / 04.06.2010 / Przemyslaw Wydra
PR 62171ESPE04: eNB reco reset is not done in case (4019) KeepAlivePolli
ngError for FCM MCU
FSM (extension module) reset when the extension module's FCM is faulty f
or fault 4019 added.
f_lt_22#0.88 / 02.06.2010 / Przemyslaw Wydra
PR 62802ESPE04: FRIE: Fault name missing for alarm id=1928 in SiteManage
r
Alarm text for fault 1928 added.
f_lt_22#0.87 / 02.06.2010 / Tomasz Antczak
63064ESPE04, 63077ESPE04, 60132ESPE04, 63066ESPE04
- corrected Customer_alarms_start step 95
NA04701543 MHA and RET alarm timing issue
- added checking if reset is triggered before timeout for external ALD f
or fault 10
68795ESPE02 (6200) EFaultId_SctpPathAl alarm
- removed handling of 6200 fault
f_lt_22#0.86 / 02.06.2010 / Piotr Adaszynski
PR 17454ESPE06 changed EAC alarms numbers for MEDUSA, additional lines a
dded
f_lt_22#0.85 / 02.06.2010 / Maciej Tokarz
PR 62328ESPE04: FRIE: Alarm id=94 UnknownUnitType is not handled in prop
er way by BTS:
-Chenged true step in 4; IsMemberInt from 23 to 21
f_lt_22#0.84 / 01.06.2010 / Lukasz Gemborowski
PR 60685ESPE04: aidditional checking of MHA type in OverCurrent_Start
ps mapped)
f_lt_22#0.56 / 22.04.2010 / Jacek Mioduski
PR 48017ESPE01: GPS Receiver alarm: Almanac status (4011)
- Bug fix - wrong step-rule
f_lt_22#0.55 / 20.04.2010 / Piotr Adaszyski
PR 59446ESPE04 filtering time for fault 1858 added
f_lt_22#0.54 / 19.04.2010 / Tomasz Antczak
Removed changes related to PR 65766ESPE02
f_lt_22#0.53 / 19.04.2010 / Jacek Mioduski
CN 4243: bug fixed
f_lt_22#0.52 / 19.04.2010 / Przemyslaw Wydra
PR 47886ESPE01: Alarm 133 is not reported by Site Manager
Needless recovery action for fault 134 and fault 134 removed.
f_lt_22#0.51 / 17.04.2010 / Przemyslaw Wydra
PR 60659ESPE04: Unspecified alarm (6316) is active during cell block
Fault text for fault 6316 added.
f_lt_22#0.50 / 17.04.2010 / Tomasz Antczak
PR 65766ESPE02: Recovery action not conducted after fault 2005 EFaultId_
OIC_SyncChAl sent to the system bus
added FR or extension reset in case of fault 2005
corrected Customer_alarms_cancel for hot insert FR scenario - step 50
f_lt_22#0.49 / 13.04.2010 / Jacek Mioduski
CN 4243: added handling for fault 1941
f_lt_22#0.48 / 12.04.2010 / Tomasz Antczak
58883ESPE04: Incompatible SW alarm (EFaultId_IncompatibleSwVersionAl) fo
r filter is not handled correctly
Added additional timeout for FF to aviod additional alarms
46500ESPE01: Flexi Rel2 with ESM exceeds reset time limit in Block/Unblo
ck test
Corrected rule CustomerAlarm_Cancel, EACStart, DirectAlarm_start
59386ESPE04: fault 88: filtering time changed from 6min to 3min
f_lt_22#0.47 / 09.04.2010 / Lukasz Gemborowski
- PR 38119ESPE03: Flexi BTS, RF module fan alarm is reported wrong sever
ity if both fans are broken
Alarm changed from 7652 to 7651 for FR FANGROUP
f_lt_22#0.46 / 09.04.2010 / Marko Huusko
NA04688750: DirectAlarm_Cancel modified to send cancel alarm for faults
133 and 134 correctly
f_lt_22#0.45 / 01.04.2010 / Lukasz Pabis
added handling for fault 142
f_lt_22#0.44 / 30.03.2010 / Przemyslaw Wydra
PR 60079ESPE04: EFaultId_PowerLevelNotSupportedAl(4008) is not generated
when power level defined in the RNW file is not supported by the HW
Fault 4008 handling added.
f_lt_22#0.43 / 23.03.2010 / Przemyslaw Wydra
hecked
f_lt_12#0.11 / 23.03.2009 / Antti Kemppainen
- PR 49235ESPE04: Corrected Generic_group_delay
f_lt_12#0.10 / 19.03.2009 / Martti Kallio
- PR 47957ESPE04: "AntLine to ""AntennaLine"
f_lt_12#0.9 / 17.03.2009 / Martti Kallio
- PR 47957ESPE04: "AntennaLine" replaced with "AntLine"
f_lt_12#0.8 / 16.03.2009 / Antti Kemppainen
- CN3756 changes: Removed fault 418 from 3000 group.
- fault 418 mapped to Customer_alarm_start and Customer_alarm_cancel
- Modified Customer_alarm_start: Added GPIO recoveryaction for faraday f
aults.
f_lt_12#0.7 / 12.03.2009 / Saara Maatta
- fault 4019 handling removed (remvoved 10416ESPE07)
f_lt_12#0.6 / 11.03.2009 / Saara Maatta
- PR 48983ESPE04: fault 41: start delay 10s
f_lt_12#0.5 / 03.03.2009 / Saara Maatta
- PR 48801ESPE04: fault 10: stop handling if alarm has already been sent
f_lt_12#0.4 / 27.02.2009 / Saara Maatta
- PR 29602ESPE03: fault 1836: read DcFeeding
f_lt_12#0.3 / 27.02.2009 / Saara Maatta
- PR 48793ESPE04: fault 1811: after shutdown send alarm, no BTS reset
f_lt_12#0.2 / 20.02.2009 / Saara Maatta
- PR 10416ESPE07: fault 4019 handling added
f_lt_12#0.1
- PR 48111ESPE04: fault 135: send always 7655
f_lt_eu_12#0.45
- PR 45041ESPE04 and 47244ESPE04: fault 1836: FEG recalculation is reque
sted every affected MHA
f_lt_eu_12#0.44
- PR 47978ESPE04: customer alarms start for FSP faults: no reset allowed
, then shutdown FSP
f_lt_eu_12#0.43
- PR 32735espe01: readSwConfTable: by default flagName is converted to i
nt and it's value is checked
f_lt_eu_12#0.42
- PR 47054ESPE04: faults 42 and 43: start delay none
f_lt_eu_12#0.41
- PR 47272ESPE04: fault 1839: mapped LNAs to FF
f_lt_eu_12#0.40
- PR 47759ESPE04 and 47707ESPE04: fault 1836: fault source FF
f_lt_eu_12#0.39
f_lt_eu_12#0.22
- fault 4011 added
f_lt_eu_12#0.21
- corrected customer alarm cancel
f_lt_eu_12#0.20
- PR 46588ESPE04: customer alarm cancel: added is stored in FDCL
- remove set text from antenna_fault
f_lt_eu_12#0.19
- PR 45944ESPE04: log file name include fault source and unitSubIndex
- Remove extra faults from working severity mapping
- Mapped FF3 to TMA faults
f_lt_eu_12#0.18
- fault 1887: corrected severity mapping
f_lt_eu_12#0.17
- PR 46568ESPE04: fault 418: write unit state
f_lt_eu_12#0.16
- PR 45450espe02, 45992espe02:
- fault 1887: ANT set as sub unit. operating mode is checked and
if mode is current mode, only faulty unit is updated.
WMHC: both branches are set to faulty state.
- fault 1887 cancel: both MHAs set to working state
f_lt_eu_12#0.15
- PR 46234ESPE04: fault 48: added StoreDumpsToMaster to extension FSM
f_lt_eu_12#0.14
- PR 45878ESPE04: customer alarms not checked FSM status before FSM rese
t
- PR 43002ESPE04: StoreDumpsToMaste use subunit 1
f_lt_eu_12#0.13
- PR 45110ESPE02: 4004 added
f_lt_eu_12#0.12
- PR 44972ESPE02: Corrected step 37 in RULE Customer_alarms_cancel. CORE
_FR added to 3rd argument.
f_lt_eu_12#0.11
- fault 313 and 314 handling removed
f_lt_eu_12#0.10
- CN3688: 4015 added
f_lt_eu_12#0.9
- PR 45050espe04: fault 10 start: exist and SWState are updated even if
23 is active
f_lt_eu_12#0.8
- fault 10: FSP handling neighbours faraday chip
f_lt_eu_12#0.7
- faults 2009 and 2013 added
- fault 10: FSP exist updated
f_lt_eu_12#0.6
- PR 45566ESPE04: fault 476: If there is RP3 failure then FSP card must
be reset
- Faults 594 and 1806: warm reset
f_lt_eu_12#0.5
- PR 45031espe04: fault 133: severity changed to degraded. if all RXs of
cell are alarming, RXs are set to faulty state.
f_lt_eu_12#0.4
- PR 28139espe03: fault 1898 start: GPS reset added
- 1303 check removed from EAC handling
f_lt_eu_12#0.3
- PR 45749espe04: fault 32 start: FDU fault buffering started always on
faulty unit
- PR 28146espe03: fault 2052 handling corrected
f_lt_eu_12#0.2
- PR 44716espe04:
- fault 32 start: removal of self from FDM is removed
- fault 32 start: handling stopped if fault is already stored in
FDCL
- fault 10 start: handling stopped if reset is requested
f_lt_eu_12#0.1
- Branches updated
-->
<FAULT_DIAGNOSTICS>
<FD_SECTION OWNER="ruleloader" >
<ENGINE_VER>2</ENGINE_VER>
</FD_SECTION>
<FD_SECTION OWNER="fdm" >
<FDCL>off</FDCL>
</FD_SECTION>
<FD_SECTION OWNER="fdu" >
<!-- fault text for known faults. these should be given by the c
omponent who generates the fault,
but all components are not able to do that.
Note that text for licence faults can't be given here be
cause FDU doesn't know anything about licences -->
<FAULT_TEXT>
("Unit initialization failure"; 12; 13; 4040;)
("Commissioning parameter mismatch"; 87;)
("Missing NBAP Cell parameters, defaults are used"; 88;)
("SW does not support commissioning file"; 90;)
("Unknown product code"; 93;)
("Unknown HW resource"; 94;)
("Unit not supported by current BTS SW version"; 95;)
("Telecom configuration failure"; 109; 110; 111; 119;)
("Cell power parameter out of range"; 126;)
("Invalid frequency channel for the BTS HW"; 1807;)
("Incorrect carrier candidates"; 1808; 1864;)
("Transmission parameters missing"; 1825; 1826;)
("Antenna line device configuration failure"; 1848; 1888
;)
("Incoherency in cell configuration"; 1856;)
("Incoherency with RF Modules"; 1857;)
("Faulty configuration of system modules"; 1858;)
("Waiting for RF connections"; 1859;)
("Not enough DSP resources per cell"; 1861;)
("Not enough HW for LCR"; 1868;)
("External Filter missing from LCR"; 1892;)
("RNW parameter mismatch"; 1896;)
("Invalid Configuration file"; 4036;)
("Incoherency In Cell Configuration"; 4044; 4000;)
("Power level not supported"; 4008;)
("FSP reset"; 4068;)
</FAULT_TEXT>
<!-- if delay is different in startup and in onair, the values a
re given in FDPP rules
give default value of 1min for fault 1815. -->
<START_DELAY>
("1000"; 6150; 6200; 6201; 6202; 6203; 6204; 6303; 6304;
6308; 6317;)
("2000"; 1815;)
("2000"; 2030;)
("3000"; 1811; 4003;)
("5000"; 126; 1819; 2003;)
("10000"; 41; 94; 1836; 1955; 2000; 2001; 2004; 2007; 20
08; 2009; 4069; 6259;)
("20000"; 124;)
("30000"; 12; 13; 16; 109; 110; 111; 119; 138; 214; 215;
216; 217; 218; 594; 1818; 1820; 1821; 1822;
1847; 1875; 1876; 1839; 1869; 1870; 1903; 1904;
1905; 1908; 1911; 1912; 1921; 1926; 2006; 2017;
2020; 2010; 2044; 4045; 4046;)
("40000"; 2011; 2019; 2027;)
("45000"; 2018;)
("60000"; 2; 9; 125; 428; 1807; 1827; 1860; 1910; 2045;
4011; 4064;)
("90000"; 1844; 1906;)
("179000"; 1837;)
("180000"; 88; 103; 115; 116; 304; 414; 446; 1838; 2005;
4057;)
("300000"; 142; 425; 2016; 1868;)
("360000"; 2002; 4000;)
("420000"; 1816; 1899;)
("480000"; 1817;)
("600000"; 133; 134;)
("900000"; 0; 1; 1850; 1858; 4068;)
("1200000"; 26;)
</START_DELAY>
<CANCEL_DELAY>
("1000"; 6150; 6200; 6201; 6202; 6203; 6204; 6303; 6304;
6308; 6317;)
("5000"; 2003;)
("30000"; 414; 446; 1869; 1870; 1930; 2016;)
("60000"; 133; 134; 425; 4011; 4064;)
("90000"; 1809;)
("300000"; 1899;)
("420000"; 1816;)
("900000"; 0; 1; 4068;)
</CANCEL_DELAY>
(5;
(6;
(7;
(9;
)
(RULE LNA_faults
(0; MapObjectFDU(FF; FF; @FaultSource; Detecting
Unit) -2; -2)
(1; MapObjectFDU(FF; MixedFF; @FaultSource; Faul
tyUnit; @FaultText) -1; -1)
)
<!-- set correct FAN as faulty unit depending on given u
nit id and current unit id -->
(RULE FAN_faults
(0; IsMemberInt (@UnitIndex; 16) -2; 20)
(6; IsMemberInt (@FaultSource; 201) -2; 8)
(7; SetFaultyUnit (4145) -1; -1)
(8; IsMemberInt (@FaultSource; 202) -2; 10)
(9; SetFaultyUnit (4146) -1; -1)
(10; IsMemberInt (@FaultSource; 1197) -2; -1)
(11; SetFaultyUnit (4144) -1; -1)
(20;
(21;
(22;
(23;
(24;
(25;
(26;
(40;
(41;
(42;
(43;
(44;
(45;
(46;
)
<!-- set various data for faults -->
(RULE ChangeSource
<!-- fault 10 FSP or Faraday: set sub unit as 0
-->
(0; IsMemberInt (@FaultId; 6150; 6201; 6202; 620
3; 6204; 6303; 6304; 6308; 6317) -2; 3)
(1; IsMemberType (@FaultSource; FCM; FSP; FARADA
Y) -2; 3)
(2; SetFaultyUnit (0) -1; -1)
(3; IsMemberType (@FaultSource; FSP; FARADAY) -2
; 5)
(4; IsMemberInt (@FaultId; 10; 4052) -2; 9)
(5; SetSubUnit (0) -2; -2)
<!-- fault 10, 32, 48, 4070: set faulty unit as
FSM or FR -->
(9; IsMemberInt (@FaultId; 10; 23; 30; 32; 48; 9
4; 1806; 1885; 1930; 4052; 4070; 6259) -2; 69)
(10; IsMemberInt (@FaultSource; 16) -2; 12)
(11; SetFaultyUnit (173) 69; 69)
(12; IsMemberInt (@FaultSource; 32) -2; 14)
(13; SetFaultyUnit (174) 69; 69)
(14; IsMemberInt (@FaultSource; 48) -2; 20)
(15; SetFaultyUnit (175) 69; 69)
(20; IsMemberInt (@FaultSource; 157) -2; 22) <!- CORE FR1_1_1 -->
(21; SetFaultyUnit (40192) 69; 69)
(22; IsMemberInt (@FaultSource; 158) -2; 24) <!- CORE FR1_2_1 -->
(23; SetFaultyUnit (40448) 69; 69)
(24; IsMemberInt (@FaultSource; 159) -2; 26) <!
-- CORE FR1_3_1 -->
(25; SetFaultyUnit (40704) 69; 69)
(26; IsMemberInt (@FaultSource; 188) -2; 28) <!
-- CORE FR1_4_1 -->
(27; SetFaultyUnit (48128) 69; 69)
(28; IsMemberInt (@FaultSource; 176) -2; 30) <!
-- CORE FR1_1_2 -->
(29; SetFaultyUnit (45056) 69; 69)
(30; IsMemberInt (@FaultSource; 177) -2; 32) <!
-- CORE FR1_1_3 -->
(31; SetFaultyUnit (45312) 69; 69)
(32; IsMemberInt (@FaultSource; 178) -2; 34) <!
-- CORE FR1_1_4 -->
(33; SetFaultyUnit (45568) 69; 69)
(34; IsMemberInt (@FaultSource; 179) -2; 36) <!
-- CORE FR1_2_2 -->
(35; SetFaultyUnit (45824) 69; 69)
(36; IsMemberInt (@FaultSource; 180) -2; 38) <!
-- CORE FR1_2_3 -->
(37; SetFaultyUnit (46080) 69; 69)
(38; IsMemberInt (@FaultSource; 181) -2; 40) <!
-- CORE FR1_2_4 -->
(39; SetFaultyUnit (46336) 69; 69)
(40; IsMemberInt (@FaultSource; 182) -2; 42) <!
-- CORE FR1_3_2 -->
(41; SetFaultyUnit (46592) 69; 69)
(42; IsMemberInt (@FaultSource; 183) -2; 44) <!
-- CORE FR1_3_3 -->
(43; SetFaultyUnit (46848) 69; 69)
(44; IsMemberInt (@FaultSource; 184) -2; 46) <!
-- CORE FR1_3_4 -->
(45; SetFaultyUnit (47104) 69; 69)
(46; IsMemberInt (@FaultSource; 189) -2; 48) <!
-- CORE FR1_4_2 -->
delay. -->
(73; IsMemberInt (@FaultId; 30) -2; 77)
(74; IsMemberType (@FaultSource; FF; EXTFF; TILT
; MHA) -2; 150)
(75; IsCancelFDFC () 150; -2)
(76; SetStartDelay (120000) 150; 150)
<!-- fault 1815: FSP start: 1min delay. others 1
s delay. -->
(77;
(78;
(79;
(80;
</RULES>
</FD_SECTION>
)
<!-- delay for Rbus error
0 Fault check in update fault is done with detecting uni
t level correlation with other faults:
3: 1815
2)
(33; IsActiveFaultFDU (2019; @FaultSource) -1; 2)
(34; IsActiveFaultFDU (2020; @FaultSource) -1; 7
0)
(36;
(37;
(38;
(39;
0)
(40; IsMemberInt (@FaultId; 2005) -2; 46)
(41; IsActiveFaultFDU (2000; @FaultSource) -1; 2)
(42; IsActiveFaultFDU (2001; @FaultSource) -1; 2)
(43; IsActiveFaultFDU (2002; @FaultSource) -1; 2)
(44; IsActiveFaultFDU (2003) -1; -2)
(45; IsActiveFaultFDU (1815; @FaultSource) -1; 7
0)
(46; IsMemberInt (@FaultId; 2014) -2; 49)
(47; IsActiveFaultFDU (1821; @FaultSource) -1; 2)
(48; IsActiveFaultFDU (1819; @FaultSource) -1; 7
0)
(49; IsMemberInt (@FaultId; 2011) -2; 53)
(50; IsActiveFaultFDU (2005; @FaultSource) -1; 7
0)
(53;
(54;
(70;
(80;
(91;
(92;
(93;
15-16: 114: 19
start delays:
25: use delay given in FDU rules -->
(RULE generic_direct_delay
(0; IsMemberInt (@FaultId; 6150; 3030) 2; -2)
(1; UpdateFault () 71; -2)
(2; AddFaultCounter () -2; -2)
(4; IsCancel () -2; 15)
(5; IsMemberInt (@FaultId; 1930) -2; 11)
(6; CreateNewFault (4075; CANCEL; 4113; -1; -1;
working) -2; -2)
(7; CreateNewFault (4075; CANCEL; 4114; -1; -1;
working) -2; -2)
(8; CreateNewFault (4075; CANCEL; 4115; -1; -1;
working) -2; -2)
(9; CreateNewFault (4075; CANCEL; 4116; -1; -1;
working) -2; -2)
(10; CreateNewFault (4075; CANCEL; 4117; -1; -1;
working) -2; -2)
(11; WaitTimeout (@CancelDelay) 48; 48)
(15;
(16;
(17;
(18;
(RULE vswr_delay
(0; UpdateFault () 51; -2)
(1; AddFaultCounter () -2; -2)
(2; IsCancel () -2; 20)
(3; IsActiveFaultFDU (1810; @FaultSource) 5; -2)
(4; IsMemberInt (@FaultId; 4057) -1; -2)
(5; WaitTimeout (@CancelDelay) 50; 50)
(20; IsActiveFaultFDU (1810; @FaultSource) 50; 2)
(21; WaitTimeout (@StartDelay) -2; -2)
(50; SendForward () -1; -1)
(51; AddFaultCounter () -1; -1)
)
<!-- rule for 1809
when cells are enabled (cancel) enable DlAntCarriers.
when disabled, disable DlAntCarriers.
if recovery action fails, print error. -->
(RULE CellActiveAl_delay
(0; UpdateFault () 51; -2)
(1; AddFaultCounter () -2; -2)
(2; IsCancel () -2; 25)
(4; ExecuteRecoveryAction (-1; EnableDlAntCarrie
rsState; ""; @FaultSource) -2; 6)
(5; WaitTimeout (@CancelDelay) 50; 50)
(6; RulesPrint ("Enabling of DL Antenna carriers
state failed [0x%X]"; @FaultSource) -1; -1)
(25; ExecuteRecoveryAction (-1; DisableDlAntCarr
iersState; ""; @FaultSource) -2; 27)
(26; WaitTimeout (@StartDelay) -2; -2)
(27; RulesPrint ("Disabling of DL Antenna carrie
rs state failed [0x%X]"; @FaultSource) -1; -1)
(50; SendForward () -1; -1)
(51; AddFaultCounter () -1; -1)
)
<!-1s delay for cancel of ResetAl
2: send to DB -->
(RULE ResetAl_1sDelay
(0; IsCancel () -2; 2)
(1; WaitTimeout (@CancelDelay) -2; -2)
(2; SendForward () -1; -1)
)
(RULE DirectSend
(0; AddFaultCounter () -2; -2)
(1; IsMemberInt (@FaultId; 4011) -2; 5)
(2; IsCancel () -2; 5)
(3; IsMemberStr (@FaultText; "Control Interface
not available") -2; 5)
(4; CreateNewFault (32; CANCEL; @FaultSource; -1
; -1; working) -2; -2)
(5; SendForward () -1; -1)
)
<!-- DeleteFault rule deletes processed fault -->
(RULE DeleteFault (0; AddFaultCounter () -1; -1))
and
in
fau
app
2)
(38; IsMemberInt (@FaultId; 1929; 4003; 4047; 40
48;) -2; 40)
(39; SendDirectAlarm (7655; @FaultSeverity; @Fau
ltActivity; @FaultSource; @GroupId) -1; -1)
<!-- update link state. send alarm after 6min de
lay. -->
(40; IsMemberInt (@FaultId; 17) -2; 50)
(41; WriteDBObject (link; linkstate; false; @Fau
ltSource; -1; ""; ""; CNBAP) -2; -2)
(42; WaitTimeout (360000) -2; -2)
(43; SendDirectAlarm (-1; @FaultSeverity; @Fault
Activity; @FaultSource; @GroupId) -2; -2)
<!-- Check if CNBAP has been down for 20 minutes
, OAM IUB is disconnected, and BTS Manager connection is not available -->
(44; WaitTimeout (840000) -2; -2)
(45; IsActiveFault (17; @FaultSource) -2; -1)
(46; ReadDBObject (link; linkstate; true; @Fault
Source; -1; ""; ""; -1; OAM) -1; -2)
(47; ReadDBObject (bs; emconnected; true; -1) -1
; -2)
<!-- Read from sw_conf_table if site reset is al
lowed -->
(48; ReadSwConfTable (SiteResetAllowed; 1) -2; 1)
<!-- Site reset recovery is performed -->
(49; ExecuteRecoveryAction (-1; SiteReset; "") 1; -1)
<!-- do BTS reset -->
(50; IsMemberInt (@FaultId; 132) -2; 60)
(51; ExecuteRecoveryAction (-1; BTSReset; "") -2
; 53)
; -1)
<!-- if fault source FF for fault 23 add delay t
o avoid sending lower severity alarms - PR 58883ESPE04 -->
(100; IsMemberInt (@FaultId; 23) -2; 110)
(101; IsMemberType (@FaultSource; FF) -2; 121)
(102; WriteDBObject (unit; state; severity; @Fau
ltSource; -1; ""; ""; ""; @FaultSeverity) -2; -2)
(103; AllowInterrupt (true) -2; -2)
(104; WaitTimeout (5000) -2; -2)
(105; AllowInterrupt (false) -2; -2)
(106; IsCommissioned (@FaultSource) 108; -2)
(107; WaitTimeout (30000) -2; -2)
(108; IsStoredInFDCL (-1; @FaultSource; @UnitSub
Index; @FaultId; @FaultSeverity) -2; -1)
<!-- ignore if GPS is not commissioned. PR 51796
espe02 -->
(110; IsMemberInt (@FaultId; 4011) -2; 116)
(111; IsMemberStr (@FaultText; "Almanac status")
-1; -2)
(112; ReadDBObject (bs; ClockGPS_InUse; NotInUse
; -1) -1; -2)
(113; IsMemberStr (@FaultText; "Control Interfac
e not available") -2; 120)
(114; WriteDBObject (unit; exist; false; @FaultS
ource) -2; -2)
(115; WriteDBObject (unit; SWState; lost; @Fault
Source) -2; -2)
<!-- no use of handling fault 2054 on uncommissi
oned OIC - PR NA05233739 -->
(116; IsMemberInt (@FaultId; 2054) -2; 120)
(117; ReadDBObject (unit; commissioned; true; @F
aultSource) 120; -2)
(118; RemoveActiveFault (@FaultSource; -1; -1; @
FaultId) -1; -1)
<!-- handle alarms specific for TUP in LTE -->
(120; IsMemberInt (@FaultId; 4030; 6200; 6261; 6
264; 6302) -2; 122)
(121; SendDirectAlarm (7651; @FaultSeverity; @Fa
ultActivity; @FaultSource; @GroupId) -1; -1)
(122; IsMemberInt (@FaultId; 1942; 4011; 6300; 6
306; 6307) -2; 130)
(123; SendDirectAlarm (7652; @FaultSeverity; @Fa
ultActivity; @FaultSource; @GroupId) -1; -1)
<!-- send alarm -->
(130; SendDirectAlarm (-1; @FaultSeverity; @Faul
tActivity; @FaultSource; @GroupId) -2; -2)
(131; IsMemberInt (@FaultId; 4091) -2; -1)
(132; ExecuteRecoveryAction (-1; BtsResetTimeInc
reased; "") -1; -1)
)
<!-- handling for directly reported fault cancels -->
(RULE DirectAlarm_Cancel
<!-- cancel using master FCM -->
(0; IsMemberInt (@FaultId; 1833) -2; 11)
PR 79602ESPE04 -->
IsMemberInt (@FaultId; 49) -2; -1)
CancelAlarms (@FaultSource) -2; -2)
RemoveActiveFault (@FaultSource) -2; -2)
WriteDBObject (cell; state; resetting; @Fau
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ultActivity; @FaultSource;
ultActivity; @FaultSource;
ultActivity; @FaultSource;
ultActivity; @FaultSource;
)
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ltActivity; @FaultSource;
ultActivity; @FaultSource;
ultActivity; @FaultSource;
ultActivity; @FaultSource;
ultActivity; @FaultSource;
)
00; -2)
(335; ExecuteRecoveryAction (-1; SiteReset; "")
-2; 400)
(336; IsMemberInt (@OrigId; 1806) -2; 338)
(337; SendDirectAlarm (7650; @FaultSeverity; TRA
NSIENT; @FaultSource; 52; -1; -1; Site) -1; -1)
(338; SendDirectAlarm (7652; @FaultSeverity; TRA
NSIENT; @FaultSource; 52; -1; -1; Site) -1; -1)
<!-- do FSM reset for extension modules and BTS
reset for master modules -->
(339; IsMemberInt (@OrigId; 300; 1806; 1820; 182
8; 1852; 2002; 2003; 2014; 2017; 2018; 2047; 2049; 2052; 4019; 4040) -2; 341)
(340; IsMemberType (@FaultSource; FCM; FSP; FARA
DAY; FSM) 343; 400)
(341; IsMemberInt (@OrigId; 1806; 2005) -2; 354)
<!-- PR 81209ESPE02: Add FSM to do BTS recovery
reset for 1806 -->
(342; IsMemberType (@FaultSource; FCM;FSM) -2; 4
00)
(343; IsMasterWAM (@FaultSource; subrack; CORE_F
SM) 362; -2)
<!-- if extension module is telecom master do bt
s reset -->
(344; ReadDBObject (bs; tcommaster; 32; -1) 362;
-2)
(345; ResetCounterCompare (@FaultSource; 3600; 1
; subrack; CORE_FSM) -2; 347)
(346; IsResetRequested (@FaultSource; subrack; C
ORE_FSM) -1; 370)
NSIENT; 32; 52; -1; -1; Unit)
-2)
(6; InformFDUOfReset (@FaultSource; cancel; subu
nits; CORE_FR) -2; -2)
<!-- FSP: end buffering on Faradays -->
(7; IsMemberType (@FaultSource; FSP) -2; 11)
(8; InformFDUOfReset (@FaultSource; cancel; subr
ack; Chip) -2; -2)
(9; InformFDUOfReset (@FaultSource; cancel; subr
ack; TUPChip) -2; -2)
<!-- CN4141 (ConfigureBB is not implemented in L
TE) -->
<!--(10; ExecuteRecoveryAction(-1; ConfigureBB;
""; @FaultSource; false) -2; -2)-->
<!-- if BS is faulty and 7650 is active, check n
eed for BTS/Site reset -->
(11; CheckObjectStatus (-1; FAULTY; -1; ""; "";
bs) -2; 50)
(12; WasAlarmNumber (7650) -2; 50)
<!-- cancel alarm -->
(13; ReadDBObject (unit; AldConnection; external
; @FaultSource) -2; 15)
<!-- if alarm is canceled from external device,
no BTS/Site reset is needed -->
(14; SendDirectAlarm (7652; @FaultSeverity; @Fau
ltActivity; @FaultSource; @GroupId) -1; -1)
(15; ReadDBObject (unit; pluginunit; true; @Faul
tSource) 17; -2)
(16; SendDirectAlarm (-1; @FaultSeverity; @Fault
Activity; @FaultSource; @GroupId) 30; 30)
(17; SendDirectAlarm (-1; @FaultSeverity; @Fault
Activity; @FaultSource; 3003) -2; -2)
<!-- if BS is not faulty anymore, do BTS or site
reset -->
(30; CheckObjectStatus (-1; FAULTY; -1; ""; "";
bs) -1; -2)
(33; IsMemberInt (@FaultSource; 225) -2; 37)
(34; ReadDBObject (bs; bsstatus; NotCommissioned
; -1) 70; -2)
(35; ExecuteServiceAction (@UnitIndex; SiteReset
; "") -2; 70)
(36; SendDirectAlarm (7652; @FaultSeverity; TRAN
SIENT; @FaultSource; 52; -1; -1; Site) -1; -1)
(37; ExecuteRecoveryAction (-1; BTSReset; "") -2
; 70)
(38; SendDirectAlarm (7652; @FaultSeverity; TRAN
SIENT; @FaultSource; 52; -1; -1; BTS) -1; -1)
<!-- cancel alarm -->
(50; ReadDBObject (unit; AldConnection; external
; @FaultSource) -2; 52)
(51; SendDirectAlarm (7652; @FaultSeverity; @Fau
ltActivity; @FaultSource; @GroupId) -1; -1)
(52; ReadDBObject (unit; pluginunit; true; @Faul
tSource) -2; 54)
(53; IsMemberType (@FaultSource; FSP) 55; -2)
1; 48372; 48373; 48378; 48625; 48626; 48627; 48628; 48629; 48634; 48881; 48882;
48883; 48884; 48885; 48890; 49137; 49138; 49139; 49140; 49141; 49146; 54513; 545
14; 54515; 54516; 54517; 54522; 54769; 54770; 54771; 54772; 54773; 54778; 55025;
55026; 55027; 55028; 55029; 55034; 55281; 55282; 55283; 55284; 55285; 55290; 47
601; 47602; 47603; 47604; 47605; 47610; 47857; 47858; 47859; 47860; 47861; 47866
; 48113; 48114; 48115; 48116; 48117; 48122; 65265; 65266; 65267; 65268; 65269; 6
5274) -2; -1) <!-- FAN ids from FR1-5 and FRs in chain -->
(31; DoAllUnitsReport (@OrigId; @FRID; -1; FR_FA
N; subunits) -2; 320)
(32; SendDirectAlarm (7655; FAULTY; CANCEL; @FRI
D; @GroupId; -1; -1; ""; -1; 1917; subunits; FANGROUP) -2; -1)
(35; WriteDBObject (unit; state; FAULTY; @FRID;
-1; subunits; FR_FAN) 200; 200)
<!-- FSM FAN and FANGROUP: send alarm -->
(150; IsMemberType (@FaultSource; FCM) 152; 151)
(151; SendDirectAlarm (7655; WORKING; @FaultActi
vity; @FaultSource; @GroupId) 153; 153)
(152; SendDirectAlarm (7651; WORKING; @FaultActi
vity; @FaultSource; @GroupId) -2; -2)
(153; IsMemberInt (@OrigId; 1934; 1935) -1; -2)
<!-- tell CLIC to turn FAN led on -->
(154; ExecuteRecoveryAction (-1; SetFanLED; "";
1; @UnitIndex) -1; -1)
<!-- FR FANGROUP: send alarm -->
(200; ReadDBObject (unit; commissioned; true; @F
RID) 201; 202)
(201; SendDirectAlarm (7655; @FaultSeverity; @Fa
ultActivity; @FRID; @GroupId; -1; -1; ""; -1; -1; subunits; FANGROUP) -1; -1)
<!--Alarm 7655 is always sent for faults 1917 an
d 1933-->
(202; SendDirectAlarm (7655; @FaultSeverity; @Fa
ultActivity; @FRID; @GroupId; -1; -1; ""; -1; -1; subunits; FANGROUP) -1; -1)
<!-- FR FAN: send alarm -->
(320; SendDirectAlarm (7655; @FaultSeverity; @Fa
ultActivity; @FaultSource; @GroupId) -1; -1)
)
<!-- FAN fault cancel handling -->
(RULE FanFailure_Cancel
<!-- 1917 is handled from step 10 onwards -->
(0; IsMemberInt (@OrigId; 1917) 8; -2)
<!-- cancel alarm -->
(1; IsMemberType (@FaultSource; FCM) 4; 2)
(2; SendDirectAlarm (7655; WORKING; @FaultActivi
ty; @FaultSource; @GroupId) -2; -2)
<!-- tell CLIC to turn off FAN led -->
(3; ExecuteRecoveryAction (-1; SetFanLED; ""; 0;
@UnitIndex) 8; 8)
(4; SendDirectAlarm (7651; WORKING; @FaultActivi
ty; @FaultSource; @GroupId) -2; -2)
<!-- tell CLIC to turn off FAN led -->
(5; ExecuteRecoveryAction (-1; SetFanLED; ""; 0;
@UnitIndex) -2; -2)
(6; WriteDBObject (unit; state; severity; @Fault
Source ; -1; subrack; FSM_FAN; ""; @FaultSeverity) -2; -2)
50; -2)
(39; IsActiveFault (1816) 250; 256)
(50; ReadDBObject (bs; ClockGPS_InUse; NotInUse;
-1) -1; 256)
<!-- send alarm. either based on BS state or sen
d directly 7652. -->
(250; SendDirectAlarm (-1; @FaultSeverity; @Faul
tActivity; @FaultSource; @GroupId) 299; 299)
(256; SendDirectAlarm (7652; @FaultSeverity; @Fa
ultActivity; @FaultSource; @GroupId) 299; 299)
<!-- GPS reset as recovery for PPS fault. -->
(299; IsMemberInt (@FaultId; 1898) -2; -1)
<!-- reset isn't performed in LTE -->
(300; ReadDBObject (cabinet; cabinetid; 19; -1)
-1; -2)
<!-- keep ten minutes delay before each reset ->
(301; WaitTimeout (600000) -2; -2)
(302; ExecuteResetAction (226; ""; -1; GPS) -2;
-2)
(303; WaitTimeout (600000) -2; -2)
(304; ExecuteResetAction (226; ""; -1; GPS) -2;
-2)
(305; WaitTimeout (600000) -2; -2)
(306; ExecuteResetAction (226; ""; -1; GPS) -1;
-1)
)
<!-- cancel handling for ref clock faults -->
(RULE RefClockMissing_Cancel
<!-- 1898: allow interrupts -->
(0; IsMemberInt (@FaultId; 1898) -2; 5)
<!-- delay kept in FDDC -->
(1; WaitTimeout (300000) -2; -2)
<!-- cancel alarm using normal and working sever
ity. normal severity is used with all fault ids. -->
(5; SendDirectAlarm (7652; WORKING; @FaultActivi
ty; @FaultSource; @GroupId) -2; -2)
(6; SendDirectAlarm (-1; @FaultSeverity; @FaultA
ctivity; @FaultSource; @GroupId; -1; -1; ""; -1; 1816) -2; -2)
(7; SendDirectAlarm (-1; @FaultSeverity; @FaultA
ctivity; @FaultSource; @GroupId; -1; -1; ""; -1; 1898) -2; -2)
(8; SendDirectAlarm (-1; @FaultSeverity; @FaultA
ctivity; @FaultSource; @GroupId; -1; -1; ""; -1; 1899) -2; -2)
<!-- rehandle faults. degraded alarm is sent aga
in as working. -->
(9; RemoveActiveFault (@FaultSource; -1; -1; @Fa
ultId) -2; -2)
(10; WaitTimeout (30000) -2; -2)
(11; RehandleFaults (subrack; @FaultSource) -1;
-1)
)
<!-- handling for BBBus configuration failed -->
(RULE BasebandBusConfFailed_Start
<!-(60;
(61;
(62;
(63;
)
(RULE FRReset_Start
(0; IsMemberInt (@OrigId; 1956) 2; -2)
(1; ResetCounterCompare (@FaultSource; 3600; 2;
subrack; CORE_FR) -1; -2)
(2; WriteDBObject (unit; state; severity; @Fault
Source; -1; ""; ""; ""; @FaultSeverity) -2; -2)
(3; SendDirectAlarm (7652; @FaultSeverity; TRANS
IENT; @FaultSource; 52; -1; -1; Unit) -2; -2)
(4; ExecuteResetAction (@FaultSource; subrack; C
ORE_FR; fr) -1; -1)
)
<!-- Rehandle VSWR and cell power faults of same cell ->
(RULE CellInactive_Cancel
(0; RehandleFaults (cell; @FaultSource; -1; FF;
-1; 1837; 1838) -2; -2)
(1; RehandleFaults (cell; @FaultSource; -1; TX;
-1; 125) -1; -1)
)
(RULE VSWRTuning_Start
<!-- cancel 1838 and 1837. after rehandling they
are sent as notifications -->
(0; SendDirectAlarm (-1; FAULTY; CANCEL; @FaultS
ource; 1837; -1; -1; ""; -1; 1837) -2; -2)
(1; SendDirectAlarm (-1; DEGRADED; CANCEL; @Faul
tSource; 1838; -1; -1; ""; -1; 1838) -2; -2)
(2; SendDirectAlarm (-1; WORKING; CANCEL; @Fault
Source; 4057; -1; -1; ""; -1; 4057) -2; -2)
(3; SendDirectAlarm (-1; FAULTY; CANCEL; @FaultS
ource; 4057; -1; -1; ""; -1; 4057) -2; -2)
(4; SetCellState (@FaultSource; ENABLED; ALL) -1
; -1)
<!-- keep 5s delay before rehandling. then cell
will be activated before 1837 is handled again. -->
<!-- (50; WaitTimeout (5000) -2; -2) -->
<!-- (51; RehandleFaults (unit; @FaultSource; -1
; -1; -1; 1837; 1838) -1; -1) -->
)
<!-- cancel notifications of 1838 and 1837, after rehand
ling they are sent normally -->
(RULE VSWRTuning_Cancel
(0; SendDirectAlarm (-1; WORKING; CANCEL; @Fault
Source; 1837; -1; -1; ""; -1; 1837) -2; -2)
(1; SendDirectAlarm (-1; WORKING; CANCEL; @Fault
Source; 1838; -1; -1; ""; -1; 1838) -2; -2)
(2; RehandleFaults (unit; @FaultSource; -1; -1;
-1; 1837; 1838; 4057) -1; -1)
)
<!-enable cells. cell should be enabled in TestDedicated st
ate.
1897 1928 1929 1942 1955 2054 4000 4001 4003 401
1 4030 4035 4036 4047 - 4048 4072 4088 4091 4102 4110 6261 6263 6264 6267 6300 6
302 6306 6307 6450 6265)
(RULEMAP UnitBlockedAl_Start StartRule 48 4070)
(RULEMAP CellAlarms_Start StartRule 38 39 49 96 1853 187
8 1879 1880 1883 4008 4012 4013 4090)
(RULEMAP BTSBlockedAl_Start StartRule 50)
(RULEMAP EACStartRule StartRule 1400 - 1425)
(RULEMAP Customer_alarms_start StartRule 9 95 1818 1892
1922 1930 3000 3010 3020 3030 3040 3060 3070 3090 3511 4068 4072 4076)
(RULEMAP AntennaLineAlarms_start StartRule 1837 1838 184
2 - 1846 3100 4046 4057)
(RULEMAP MHAAlarms_start StartRule 1834 1835 1869 1870 3
120)
(RULEMAP RbusAlarm_start StartRule 425)
(RULEMAP OverCurrent_Start StartRule 1836 4045 4069)
(RULEMAP NoConnectionToUnit_start StartRule 10 4052)
(RULEMAP FanFailure_Start StartRule 3050)
(RULEMAP RefClockMissing_Start StartRule 1816 1898 1899)
(RULEMAP BasebandBusConfFailed_Start StartRule 1811)
(RULEMAP LicenceMissingAl_Start StartRule 140 1814 1833
1885 4002 4037 4056)
(RULEMAP OseFatalError_Start StartRule 418)
(RULEMAP BTSReset_Start StartRule 4099)
<!-- RnD faults -->
(RULEMAP UnitResetAl_Start StartRule 32)
(RULEMAP UnitDeleted_start StartRule 74)
(RULEMAP SiteReset_Start StartRule 89 142 1855)
(RULEMAP ResetResource_Start StartRule 128 317)
(RULEMAP FRReset_Start StartRule 1956 4113)
(RULEMAP EnablingFD StartRule 1813)
(RULEMAP VSWRTuning_Start StartRule 1810)
(RULEMAP TestDedicated_Start StartRule 72)
(RULEMAP CellDisabled_Start StartRule 4034)
(RULEMAP UpdateObjectState_Start StartRule 1887 4084)
(RULEMAP S1_X2_Alarms_Start StartRule 6150 6201 - 6204 6
303 6304 6308 6317)
(RULEMAP CellSetupFailed_Start StartRule 6253)
<!-- Mapping for RD and unknown alarms -->
(DEFAULT_RULE DeleteStart StartRule)
<!-- ****** Cancel Alarm Mappings ****** -->
(RULEMAP EACCancelRule CancelRule 1400 - 1425)
(RULEMAP DirectAlarm_Cancel CancelRule 17 - 19 23 24 26
27 37 28 115 116 124 130 133 134 138 140 1814 1833 1839 1860 1865 1885 1877 1895
1897 1928 1929 1930 1955 4000 4002 4003 4011 403
5 4036 4037 4056 4088 4110 6261 6264 6267 6302)
(RULEMAP UnitBlockedAl_Cancel CancelRule 48 4070)
(RULEMAP CellAlarms_Cancel CancelRule 38 39 49 96 1853 1
878 1879 1880 1883 4008 4012 4013 4090)
(RULEMAP Customer_alarms_cancel CancelRule 9 418 425 181
8 1834 1835 1837 1838 1842 - 1846 1869 1870 1892 1922 3000 3010 3020 3030
3040 3060 3070 3090 3100 3120 3511 4046
4068 4072)
(RULEMAP NoConnectionToUnit_cancel CancelRule 10 4052)
(RULEMAP FanFailure_Cancel CancelRule 3050)
(RULEMAP RefClockMissing_Cancel CancelRule 1816 1898 189
9)
<!-- RnD faults -->
(RULEMAP
(RULEMAP
(RULEMAP
(RULEMAP
(RULEMAP
(RULEMAP
(RULEMAP