VeEX UX400, User Manual

Page: 198 / 209

Go back to top Go back to TOC
7.6.3 Trace Identifier (Trail Trace Identifier)
Tap the Trace Identifier icon to display the screen shown below. There are tabs for Tx and RX settings of the TTI.
Expected SAPI:
The received trace will be compared against this string, if they don't match a TIM alarm would be declared
Received SAPI:
This field shows the trace being received. Users can use the COPY button to transfer the same string to the Expected SAPI and make them match.
TIM (Trace Identification Mismatch):
TIM evaluation can be turned ON or OFF. If the evaluation is turned off, the receive trace would not be compared against the
expected string and the TIM alarm would not be raised. If set to ON a TIM alarm will be declared if the expected and received strings don't match.
Trace Identifier (Trail Trace Identifier) TX & RX
Trail Trace Identifier
TTI similar to the J0 byte in SONET/SDH, is used to identify the signal from the source to the
destination within the network. The TTI contains the so called Access Point Identifiers (API) which
are used to specify the Source Access Point Identifier (SAPI) and Destination Access Point Identifier
(DAPI). The APIs contain information regarding the country of origin, network operator and
administrative details.
Go back to top Go back to TOC
7.6.4 TCM Tasks (Tandem Connection Monitoring)
Tap the TCM Tasks icon to display the screen shown below.
TCM Tasks
UX400 10G e-Manual D07-00-058P RevA00 Page 198 of 209