Avaya Troubleshooting Routers Průvodce řešením problémů stáhnout pdf (Strana 89)

Troubleshooting a Data Link Connection Problem

5-11

If the Ethernet controller is not a QENET, you can ignore this attribute. If

the Ethernet controller is a QENET, check for underruns or corrupted

frames. (This usually occurs only when you conﬁgure three or more ports

on the QENET.) If underﬂow errors or corrupted frames occur, enable the

attribute wfCSMACDAlignmentMode. This attribute determines whether

the software aligns the frame on a word boundary before giving it to the

QENET.

• wfCSMACDLateCollnRx

This shows the number of late collisions received. A late collision

reception is a collision that takes place after the router receives the ﬁrst 64

bytes of a frame. The length of the Ethernet cable exceeds the speciﬁed

length. Replace it with a compliant cable.

Troubleshooting an FDDI Connection

This section assumes that you have isolated a problem to an FDDI connection. If

not, refer to Chapter 2 to determine whether these instructions apply to your

problem.

Troubleshoot an FDDI connection as follows:

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

the slots experiencing the problem. The Technician Interface command is

log -fftwid -eFDDI -s

<slot_no.>

Example

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

log -fftwid -eFDDI -s3 -s4

Use the Technician Interface to look at the values of the following

attributes in the wfFddiEntry object. The

get command is next to the

attribute name. Or, use the wfLine➔wfFddiTable Quick Get path to

access them.

• wfFDDIOverrunRx (

get wfFddiEntry.16.*)

This shows the number of frames received with internal overrun errors.

The FSI (FDDI System Interface) chip set became overloaded and

dropped packets.

1 2 ... 84 85 86 87 88 89 90 91 92 93 94 ... 253 254

Žádné komentáře

Avaya Troubleshooting Routers Průvodce řešením problémů Strana 89