Traces - otn, Otux, odux, and tcm buttons, Sm/pm tti traces – EXFO FTB-800 Series for FTB-1 User Manual

Page 383

Advertising
background image

Test Results

NetBlazer

373

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 ODUx button. For ODUx when TCM is enabled (see
Modify TCM on page 213), 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 213).

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 -

OTN on page 373.

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).

Advertising
This manual is related to the following products: