VeEX MPA User Manual page 213

Multi-protocol analyzer
Table of Contents

Advertisement

MPA_e_manual_D07-00-129P_RevA00
Protocol Tabs
Testing overhead Traces:
Received SAPI
Trace
Expected SAPI
Trace
Received DAPI
Trace
Expected DAPI
Trace
OTN Receive - A/D OH
The A/D OH settings apply to the additional layer of overhead bytes for lower ODU rate
payloads that are multiplexed up to a higher OTU Interface rate.
The Receive A/D OH screens become enabled when configured for a multi-level or
multi-channel ODTU Add/Drop mapping.
See the
OTN Receive - OTN OH
Add/Drop overhead bytes.
213
MSI bytes are only available when the OTN Interface is
configured for an ODTU Add/Drop mapping.
Displays the Source Access Point Identifier (SAPI) trace
received on the incoming signal for OTU, ODU and TCM1-
TCM6 OH bytes.
The Expected SAPI Trace is a User Defined setting that can
be compared to the received SAPI Trace. When a specific
OH section's TIM Alarm Reporting is Enabled, then that
section's SAPI alarm will increment if the received SAPI
Trace is different than the Expected SAPI Trace setting.
Displays the Destination Access Point Identifier (DAPI) trace
received on the incoming signal for OTU, ODU and TCM1-
TCM6 OH bytes.
The Expected DAPI Trace is a User Defined setting that can
be compared to the received DAPI Trace. When a specific
OH section's TIM Alarm Reporting is Enabled, then that
section's DAPI alarm will increment if the received DAPI
Trace is different than the Expected DAPI Trace setting.
section for a description of each of the received

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents