
Troubleshooting a Data Link Layer Problem
308656-14.00 Rev 00
5-23
6.
Make sure that you set the LBO appropriately.
For example, 0.0 dB is short haul (up to 133 ft).
7.
Use the FT1 built-in bit error rate test (BERT) and line loop-up,
loop-down, and payload loopbacks for troubleshooting. (This feature is
available only with Site Manager in dynamic mode.)
Note that only one port can be in BERT mode at a time.
Payload loopbacks are available in extended superframe (ESF) line type mode
only.
8.
Make sure that the clocking is set to Internal or Port1 Ext Loop. These
settings are equivalent to Sync External.
The internal clocking of the FT1 link module is the same as the internal
clocking of the T1 link module.
9.
Make sure that the cyclic redundancy check (CRC) matches the carrier’s
specifications (16 or 32).
10.
Make sure that the value of the Inter Frame Time Fill parameter matches
idles (0xFF) or flags (0x7E) with the remote end of the link.
11.
Check the events from the entity DS1E1 (multichannel T1/E1 driver
service) to view the FT1 log events.
FT1 uses the wfDS1E1 MIB entries. Therefore, the entity name associated
with FT1 is DS1E1, not FT1.
FT1 uses the wfSyncEntry object; T1 uses the wfLogicalLineEntry object.
Troubleshooting a Synchronous Connection
This section assumes that you have isolated a problem to a synchronous
connection. If not, refer to Chapter 2 to determine whether these instructions
apply to your problem.
Troubleshoot a synchronous connection as follows:
1.
Filter the log to display only messages from the Sync entity running on
the slots experiencing the problem.
The Technician Interface command is as follows:
log -fftwid -eSYNC -s
<slot_no.>
Comentarios a estos manuales