Avaya Troubleshooting Routers Guia de Resolução de Problemas descarregar pdf (Página 95)

Troubleshooting a Data Link Connection Problem

5-17

Troubleshooting an MCT1 Connection

This section assumes that you have isolated a problem to an MCT1 (multichannel

T1) connection. If not, refer to Chapter 2 to determine whether these instructions

apply to your problem.

A includes instructions on reading MCT1 log messages.

Do the following if the connection is MCT1:

1. Filter the log to display only messages from the MCT1 entity running on

the slots experiencing the problem. The Technician Interface command is

log -fftwid -eMCT1 -s

<slot_no.>

Example

If you are ﬁltering events from Slots 3 and 4, you enter

log -fftwid -eMCT1 -s3 -s4

Check the following MCT1 MIB entries by entering the following

Technician Interface commands:

get wfDrivers.14.0

Or, use the following Quick Get path to this attribute:

wfSoftwareConﬁg➔wfDrivers➔wfMunichLoad.

get wfLinkModules.17.0

Or, use the following Quick Get path to this attribute:

wfSoftwareConﬁg➔wfLinkModules➔wfMCT1E1Load.

3. Make sure that the Line Type and Line Coding supplied by the T1

provider match the associated settings in the MCT1 conﬁguration.

4. Make sure the DS0s (Directory Service 0) channels match at both the

router and the central ofﬁce.

5. Watch the LEDs in the back of the MCT1. If the Sync LED keeps

ﬂashing, the LBO (line build out; impedance or resistance on a line) is not

in sync. Ask the T1 carrier if you should set it to long haul or short haul,

and conﬁgure the LBO parameter accordingly.

Note: Appendix A includes instructions on reading MCT1 log messages.

1 2 ... 90 91 92 93 94 95 96 97 98 99 100 ... 253 254

Sem comentários

Avaya Troubleshooting Routers Guia de Resolução de Problemas Página 95