For more information, refer the Metropolis
®
AMU User Operations Guide.
Round Trip Delay Monitor
An Round Trip Delay Monitor can be enabled or disabled for a certain set of user
specified parameters which define an “Ethernet Service Route”. For each Ethernet
Service Route, a frame delay monitor can be enabled. The following counters are
included in this monitor.
•
mRTD: Minimum round-trip delay recorded in the binning period (milliseconds)
•
aRTD: Average round-trip delay over the binning period (milliseconds)
•
xRTD: Maximum round-trip delay recorded in the binning period (milliseconds)
•
p900RTD: Upper 90-percentile of round-trip delay over the binning period
(milliseconds)
•
p990RTD: Upper 99-percentile of round-trip delay over the binning period
(milliseconds)
•
p999RTD: Upper 99.9-percentile of round-trip delay over the binning period
(milliseconds)
•
sRTDM: Number of succesful RTD measurement frames transmitted
•
uRTDM: Number of unsuccesful RTD measurement frames transmitted.
Note that an RTD measurement frame is considered successful if a valid response
corresponding to the transmission frame was received from the targetted node.
Note that this feature is only applicable to the ESW4_E14 option card.
For more information, refer the Metropolis
®
AMU User Operations Guide.
Threshold Limit Notifications for Round Trip Delay Monitor
Users can individually enable or disable threshold limit notifications for each active
Round Trip Delay Monitor on any or each of the following parameters.
•
aRTD - 15 minute bin
•
xRTD - 15 minute bin
•
uRTDM - 15 minute bin
•
aRTD - 24 hour bin
•
xRTD - 24 hour bin
•
uRTDM - 24 hour bin.
Each Round Trip Delay Monitor has its own set of thresholds. In case one of the
thresholds is crossed while the threshold limit is being enabled, a corresponding alarm
is raised or cleared for the Round Trip Delay Monitor. Users can provision “Set” and
“Clear” threshold limits for these counters. Note that this feature is only applicable to
the Round Trip Delay Monitor feature.
Product description
Performance Monitoring
....................................................................................................................................................................................................................................
2-56
Lucent Technologies - Proprietary
See notice on first page
365-312-847R4.0
Issue 4, November 2006