
Troubleshooting a Data Link Layer Problem
308656-14.00 Rev 00
5-21
5.
Watch the LEDs on the back of the MCT1 module. If the Sync LED keeps
flashing, the line build out (LBO) is not in sync. This indicates impedance
or resistance on the line. Ask the T1 carrier if you should set it to long
haul or short haul, and configure the LBO parameter accordingly.
The Sync LED stays on when the framer is in sync with the carrier’s clock.
6.
Make sure that you set the LBO appropriately.
For example, 0.0 dB is short haul (up to 133 ft).
7.
Use the MCT1 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 Port1 Ext Loop or Port2 Ext Loop.
These settings are equivalent to Sync External.
The internal clocking of the MCT1 link module is the same as the internal
clocking of the T1 link module. The MCT1 Slave and Loop settings are
equivalent to the T1 master clock in 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 MCT1 log events.
MCT1 uses the wfDS1E1 MIB entries. Therefore, the entity name associated
with MCT1 is DS1E1, not MCT1.
MCT1 uses the wfSyncEntry object; T1 uses the wfLogicalLineEntry object.
12.
Enter the Technician Interface
loadmap
<slot_no.>
command and make
sure that the software loaded the
munich.exe
and
mct1e1.exe
files. If it did
not, use the Image Builder to add them to the router software image, and
transfer the image to the memory card.
Komentáře k této Příručce