VeEX MPA, User Manual

Page: 262 / 842

OTN Tab
262
4. The incoming SAPI, DAPI, and Operator Specific traces are decoded from the
OTN Overhead, and appear in ASCII format at the bottom of the screen.
5. Expected SAPI or DAPI trace values can also be defined, and the MPA can be
setup to display Trace Identifier Mismatch (TIM) alarms if the incoming SAPI or
DAPI traces do not match what is expected.
6. OTU, ODU, and TCM TIM alarms can be individually enabled from the SET 2
window.
SAPI and DAPI TIM alarms occur when the incoming trace does not match the
expected trace, and the TIM Alarm Reporting has been enabled for that trace.
There are no LEDS associated with TIM alarms; however TIM alarm durations
appear on the Results Scan and Alarm screens.
Measuring Service Disruption Activity
The MPA can measure Service Disruption switching intervals in your network and can
be configured to monitor for a specific event that will cause a service disruption switch.
When this event occurs, the duration in both seconds and frames is logged. These
statistics can be used to determine how long it takes for your network equipment to
react to an service disruption event and switch to a backup path.
The service disruption measurements show a granular accuracy of 1 frame duration.
•
For Ethernet networks, the granular accuracy is: 0.1 ms (100 µs)
•
For SONET and SDH networks, the granular accuracy is: 0.125 ms (125 µs)
•
For OTU 1 networks, the granular accuracy is: 0.049 ms (49 µs)
•
For OTU 2 networks, the granular accuracy is: 0.012 ms (12 µs)
•
For OTU-3 networks, the granular accuracy is: 0.003 ms (3.035 µs)
•
For OTU-3e1 networks, the granular accuracy is: 0.003 ms (2.929 µs)
•
For OTU-3e2 networks, the granular accuracy is: 0.003 ms (2.928 µs)
•
For OTU-4 networks, the granular accuracy is: 0.001 ms (1.168 µs)
To measure Service Disruption activity:
1. Select a protocol processor.
2. Select the Test button.
3. Select the Service Disruptn button. The Service Disruption measurement
screen appears.
MPA_e_manual_D07-00-129P_RevA00