
Troubleshooting a Data Link Layer Problem
308656-14.00 Rev 00
5-7
PVC Problems
For PVC problems, do the following:
1.
If the connecting switch does not support signaling, verify that signaling
is disabled.
2.
Check the log for
failed to register
messages.
This message usually indicates an oversubscribed interface. Add the peak cell
rate (PCR) and sustainable cell rate (SCR) values of each PVC to verify that
the combined value does not exceed the cell rates you have configured on the
interface.
3.
If the PVC terminates at a non-Nortel Networks IP device, define an
adjacent host entry using the outgoing VPI/VCI number of the device as
the MAC address.
4.
Using the VCL MIB objects, verify the configured cell and frame
statistics for each VC.
5.
If the interface is running LLC/SNAP encapsulation, check the
wfAtmMpeEntry MIB object for PID errors.
6.
Verify that the PVC is not a termination point for a C100 connection
(such as C100 Turbo or Circuit Saver).
Troubleshooting ATM LANE
This section assumes that you have isolated a problem to the ATM LAN emulation
(LANE) protocol. Troubleshoot ATM LANE problems as follows:
1.
Use the Events Manager or the Technician Interface to enable extended
debugging in the wfAtmLec MIB objects.
The Technician Interface command is as follows:
g wfAtmLecConfigEntry.29.3
2.
Filter the log to display messages of all severity levels for the slots
experiencing the problem.
Enter the following Technician Interface command:
log -fftwid -eATM -eATM_SIG -eATM_LE -s
<slot_no.>
Komentarze do niniejszej Instrukcji