VADSU Timers and Thresholds--Need better understanding please

[kevin906]

I have read the manuals about VADSU and setting timers and thresholds but the wording is not very clear as to what it actually does.

See the examples below. These alarms were all legitimate so no problem there.
My issue is how the VADSU setting affect when to trigger the alarms.
The VADSU table in question is shown at the bottom of the screen.
Time1 is 1800 seconds-30 minutes
Time2 is 300 seconds-5 minutes

Do these timers represent a value that means don't do anything unless the problem has existed for 5 minutes or 30 minutes?
Do these timers represent a value that means don't consider the alarm cleared/off until the problem has not reappeared in these time frames.
ALFE states threshold value can be set as an absolute value or a percentage value.
In this case it's 10% and 20%. This outage affected 100% of the CO trunks so that makes sense.
ALFE then states the alarm is signaled if the threshold value is not exceeeded for a specific time period (validation time).
This is where I am totally lost--the threshold values WERE exceeded and the alarms triggered.
What kind of inverse logic is at play here?
Any input is most welcome.


A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 02:57:23
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 03:26:53

A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 03:39:03
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 03:43:04


A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 03:43:34
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 03:43:49

A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 03:45:50
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 03:50:35


A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 03:58:23
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 04:03:08



A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 04:20:13
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 04:24:58


+==============================================================================+
| ALARM GROUP: PERIPHERAL SWU ALARMS |
+===+=====+=====+=====+=====+=====+=====+=====+===+==+==+======================+
|AL.|THRS1|THRS2| ERR.|ERRS.|TOTAL|TIME1|TIME2|TME|PR|HW| NAME |
|NO.|IN % |IN % | ABS.|IN % | |[SEC]|[SEC]|[H]| |CO| |
+---+-----+-----+-----+-----+-----+-----+-----+---+--+--+----------------------+
| 0| 10| 20| 0 | 0| 157| 1800| 300| 0| 0|SU|CO TRUNK/EXCH LINE |

 

[Iamnothere]

The "Threshold 1" category represents the percentage of failure that may lead to a MINOR alarm, while "Threshold 2" represents the percentage of failure that may lead to a MAJOR alarm. When System Dependability detects a fault, that fault will not trigger an alarm if neither the Threshold 1 or Threshold 2 percentage is reached. "TIME 1" is the timer for Threshold 1 (MINOR alarms) and "Time 2" is associated with Threshold 2 (MAJOR alarms). Example: If there are one hundred "Central Office" trunks configured in the system, and 15 of these trunks fail, then 15% of the system's CO trunks have failed. In your VADSU "CO Trunk/Exch Line" alarm, this 15% failure would fall into the "Threshold 1" category (MINOR). Since the Minor threshold percentage value (10%) has been reached, then the associated Timer ("TIME 1") starts. If the fault clears itself, or the problem is resolved before the associated Timer expires, an alarm is not generated. If the problem is NOT resolved, and the associated Timer expires, an alarm is generated.

Many of the alarm threshold values and timer values in AMO VADSU may be modified using CHA-VADSU; some values are fixed.

Based on your post, your trunk failures qualified as a MAJOR ALARM because more than 20% (Threshold 2) of the trunks in the system failed; therefore a Major alarm should have been generated after the Time 2 timer expired (5 minutes).

A Threshold can be set as a specific value. This type of alarm configuration is typically known as "Single Device Failure", where the failure of a specific device/PEN can trigger an alarm. The timer for Single Device Failure is "TIME".




Good Luck!

 

[kevin906]

iamnothere, thanks for this. This confirms what I thought, however these alarms are triggered at the same time of the event detection.
It appears the timers are not considered. I will find some examples of this and post them to the thread. I have been working on the product since 1993 and have observed this behavior. Maybe the further details from the Hista log will offer further clarity on what I am missing or understanding.

 

[kevin906]

This is from the Hista file where the alarms are triggering less than one minute after an event.
This is where the timers involved seem to be ignored. Alarm events are occurring sooner than 1800 and 300 seconds.
There were no F5411 or F5412 errors prior to the first event at 02:56:44.
As the alarms clear and return the timers look to be ignored.

F5609 INSTRIAL BPB CIRCUIT BACK IN SERVICE 01-04-031-20 SLMA2P 2015-11-20 02:16:01
F5609 IN SERV BPB CIRCUIT BACK IN SERVICE 01-04-031-20 SLMA2P 2015-11-20 02:36:01
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-085-01..25 TMDN64P 2015-11-20 02:56:44 >>Layer 1 errors detected
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-085-01..25 TMDN64P 2015-11-20 02:56:46
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-04-055-01..25 TMDN64P 2015-11-20 02:57:00
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-025-01..25 TMDN64P 2015-11-20 02:57:02
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-04-055-01..25 TMDN64P 2015-11-20 02:57:02
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-01-025-01..25 TMDN64P 2015-11-20 02:57:03
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-025-01..25 TMDN64P 2015-11-20 02:57:04
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-01-025-01..25 TMDN64P 2015-11-20 02:57:05
A9000 NO ACT BPB NMCALARM MINOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 02:57:08 >>Alarm less than one minute later
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-04-097-01..25 TMDN64P 2015-11-20 02:57:12
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-04-097-01..25 TMDN64P 2015-11-20 02:57:15
A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 02:57:23 >>Alarm less than one minute later
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:03:15
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:03:17
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:04:09
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:04:11
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:06:11
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:06:13
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:08:16
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:08:18
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:17:31
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:17:33
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:19:37
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:19:39
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 03:26:53
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:38:38
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:38:40
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:38:43
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:38:45
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:38:54
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:38:56
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:38:58
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:39:01
A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 03:39:03
F5414 OUT SERV BPB CIRCUIT L2 ERROR 01-03-085-1-24 TMDN64P 2015-11-20 03:42:57
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:43:02
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 03:43:04
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:43:04
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:43:25
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:43:27
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:43:29
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:43:32
A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 03:43:34
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 03:43:49
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:45:30
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:45:33
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:45:43
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:45:45
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:45:48
A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 03:45:50
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:45:50
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:45:52
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:45:54
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 03:50:35
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:58:04
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-085-01..25 TMDN64P 2015-11-20 03:58:07
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:58:11
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-04-055-01..25 TMDN64P 2015-11-20 03:58:14
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-025-01..25 TMDN64P 2015-11-20 03:58:16
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-01-025-01..25 TMDN64P 2015-11-20 03:58:20
A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 03:58:23
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 04:03:08
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-085-01..25 TMDN64P 2015-11-20 04:19:49
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-085-01..25 TMDN64P 2015-11-20 04:19:52
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-04-055-01..25 TMDN64P 2015-11-20 04:19:57
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-04-055-01..25 TMDN64P 2015-11-20 04:19:59
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-03-025-01..25 TMDN64P 2015-11-20 04:20:06
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-03-025-01..25 TMDN64P 2015-11-20 04:20:08
F5411 STATIST BPB CIRCUIT L1 SPOR ERROR 01-01-025-01..25 TMDN64P 2015-11-20 04:20:12
A9001 NO ACT BPB NMCALARM MAJOR ALARM ON CO TRUNK/EXCH LINE 2015-11-20 04:20:13
F5412 OUT SERV BPB CIRCUIT L1 ERROR 01-01-025-01..25 TMDN64P 2015-11-20 04:20:14
A9003 NO ACT BPB NMCALARM MAJOR ALARM OFF CO TRUNK/EXCH LINE 2015-11-20 04:24:58

 

[Iamnothere]

I know two US Hicom/HiPath/OpenScape 4000 techs named "Kevin" who go back that far: one in California, and one in Virginia. If either is you, then you know me well. If neither is you, then you still may know me!
Either way, please do not guess via this forum. Yes, STA-HISTA should show that the Fault occurred at X o'clock, and the Alarm was created at X + <VADSU timer>.
This info may not have been presented precisely if you attended Hicom training in 1993. The instructors were learning while teaching. Today the VADSU/VADSM/SIGNL/AFR AMOs are taught in the "Troubleshooting" course.


Good Luck!

 

[kevin906]

Posting text version as well

 

[kevin906]

I worked out of the Chicago office. Attended the 9757 class in Santa Clara in spring '91. In that class with several Irving TAC folks. 9006.1 class Irving Feb. '94.

 

[Iamnothere]

What I explained previously was the basics of AMO VADSU. In addition to the "canned" alarm settings, there is also "Logical" alarms. Within the Logical alarms category, there are two types of alarms that may be causing the quick generation of the Alarms.
If you have an AMO Reference Guide, find the brief sections about "Special Alarms" "Directional Alarms". Special alarms are generated AUTOMATICALLY by the system, based on the unique LCR configuration in your system. Special Alarms abide by their own Threshold and Timer settings.

There is also the possibility to MANUALLY create unique "Directional" alarms. First you create the alarm itself, using a specific range of alarm numbers (see AMO Reference Guide). Then you assign the new Logical/Directional alarm to the trunk itself, using the appropriate AMO (TACSU or TDCSU). You should be able to see the Logical alarms (including Directional alarms), and all the trunk PENs that are assigned to unique Directional alarms by performing DIS-VADSU; - look at the lower section of the output.

It is possible that your trunk failures not only fall into the Peripheral SWU alarm category, but are also included in the SPECIAL Alarms (my guess), and/or customized "Directional" alarms.



Good Luck!

 

[kevin906]

Yes, I am familiar with the special and directional alarms. This is a 9006.6 system. There are none of these setup in the system. So I guess this remains a mystery.
VADSU only contains the basic table entries.