![Metrodata NetTESTER NT1003 User Manual Download Page 109](http://html1.mh-extra.com/html/metrodata/nettester-nt1003/nettester-nt1003_user-manual_1779476109.webp)
METRODATA NetTESTER FAMILY USER MANUAL
76-02-107 Rev.A
Page 109 of 133
24 hours
Recommended setting for FLR, FTD and IFDV alarms.
30 days
Recommended setting for Availability alarm.
14.3.5.2.3
Minimum Data
Menu Tree: Main Set-Up /
P
erf Monitoring / [peer] / S
L
A / S
L
A Alarms /
A
vailability / Min
D
ata
Minimum Data defines how much valid performance data must have been logged
before the SLA alarm can be generated. This is intended to prevent spurious alarm
generation based on very small amounts of data.
For availability, the default setting is 24 hours, but in order to get a more rapid
response shorter periods are available.
15m
Recommended setting for FLR, FTD and IFDV alarms.
30m
1h
3h
6h
12h
24h
Recommended setting for Availability alarm.
14.3.6
Monitor Alarm
Menu Tree: Main Set-Up /
P
erf Monitoring / [peer] /
M
onitor Alarm
An issue with SLA alarms is that performance data (especially for Availability) must
be averaged over a long time period and hence the alarms are relatively slow to
respond to short-term problems.
To address this, a separate 'Monitor' alarm system is supported, with a default
window size of 1 minute, and with configurable threshold values for the performance
parameters that are typically much high than the SLA equivalents. This means that
the monitor alarms are much better suited to detecting more severe but shorter-term
problems than marginal infringements of the SLA.
The Monitor alarm menu is shown below: