Traces - otn, Otux, odux, and tcm buttons, Sm/pm tti traces – EXFO FTB/IQS-85100G Packet Blazer for FTB-500/IQS-600 User Manual
Page 252
Test Results
242
FTB/IQS-85100G
Traces - OTN
Traces - OTN
From the Test menu, tap Results, Traces, and the OTN sub-tab.
OTUx, ODUx, and TCM Buttons
Tap on either OTUx, or an ODUx button. For ODUx when TCM is enabled
(see Modify TCM on page 141), tap on a TCMx button to select a TCM level.
SM/PM TTI Traces
Note: The TTI Traces are configurable for SM (OTUx), PM (ODUx), and TCM
(ODUx when TCM is enabled; refer to Modify TCM on page 141).
Received Message
SAPI indicates the received TTI (Trail Trace Identifier) Source Access
Point Identifier.
DAPI indicates the received TTI Destination Access Point Identifier.
Operator Specific indicates the received TTI Operator Identifier.
Expected Message
Note: The following settings are coupled with the Expected Message from Traces -
SAPI allows editing the expected Source Access point Identifier (TTI
bytes 1 to 15). Available when the SAPI OTU/ODU-TIM check box is
selected. The default setting is EXFO OTU SAPI for OTUx, and EXFO
ODU SAPI for ODUx. The TTI byte 0 is set to NULL (all 0’s).
DAPI allows editing the expected Destination Access point Identifier
(TTI bytes 17 to 31). Available when the DAPI OTU/ODU-TIM check box
is selected. The default setting is EXFO OTU DAPI for OTUx, and EXFO
ODU DAPI for ODUx. The TTI byte 16 is set to NULL (all 0’s).