
TECHNICAL APPENDIX
| TECHNICAL APPENDIX
203
16.11.20
Note about event failure sampling
We have a logical problem related to a group of alarms (in general all ones with the "Timeout" in place of the
"Validation").
I saw in the TDF report (read too late to take an action on the release) that has been considered wrong the behavior of
the timing reported in the PS trap varbinds.
TDF asked that the trap must report the time of the first event out of range and the value in that instant.
The problem is that, with some kind of alarms the failure instant (as well as the wrong sampled value) doesn't exist.
So we have only a moment in which a valid situation or condition isn't happened and that a timer is expired.
Missing this information we decided for this group of alarms to consider the old logic the only one applicable, the same
one you are actually considered "KO".
So in the release 0.6.4. you'll find the same situation for "PS","CT","RT","EON" and in the next step "TMC", "RT+",
"ODA1" ,"ODA2".
The question is:
If I'm rising an alarm because I waited 70 seconds for a 4A block, or a I waited 50 seconds for a PS sequence and my
timer expired, I have only the timeout error as reference, no other values or timings. So the alarm trap time is the same of
the failed timeout event .
So, or this logic is accepted or we have to define how a failure past condition (not sampled) happens. I only have the last
valid event sampled and the timeout instant (nothing more between them).
For example in the CT case , I have the last valid 4A received, or for the PS the last valid completed sequence.
I can't locate future events easily because I have to consider a scanning complex situation.
-------------------------------
In the release 0.6.5 We have modified the logic to sample the failure event in the “Timeout case”. The trap will be sent at
the timeout expiration but the failure time will be considered some seconds after the last valid event seen with the
meaning of “After this time the service stopped to work properly”. This new logic will affect the following alarms
(PS,CT,RT,EON,TMC,RT+,ODA1,ODA2,IH)
Содержание WOLF 1MS
Страница 1: ...WOLF 1MS WOLF 2MS User Manual FM monitoring system and streaming device Rev 1 3...
Страница 10: ...ENG GENERAL DESCRIPTION 10...
Страница 11: ...ENG GENERAL DESCRIPTION 11...
Страница 12: ...ENG GENERAL DESCRIPTION 12...
Страница 14: ...ENG GENERAL DESCRIPTION 14 WOLF 1MS WEB PAGE...
Страница 15: ...ENG GENERAL DESCRIPTION 15 WOLF 2MS WEB PAGE...
Страница 16: ...ENG GENERAL DESCRIPTION 16 WOLF 1MS WOLF 2MS BLOCK DIAGRAM...
Страница 78: ...78 Example 3 RFL2 MASK This schemes shows from left to right the flow of each single Alarm...
Страница 216: ...TECHNICAL APPENDIX TECHNICAL APPENDIX 216...
Страница 218: ...TECHNICAL APPENDIX TECHNICAL APPENDIX 218...
Страница 221: ...TECHNICAL APPENDIX TECHNICAL APPENDIX 221...