Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, October 02, 2000 11:57 PM
To: [EMAIL PROTECTED]
Subject: RE: ospf bandwidth question
"Whenever you have BECNS or FECNS it could be that a powerful link is
sending
data down a n
---
[EMAIL PROTECTED] on 03/10/2000 03:36:40 pm
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:(bcc: JENNY MCLEOD/NSO/CSDA)
Subject: Re: ospf bandwidth question
In a message dated 10/3/00 12:16:20 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes
29/09/2000 06:05:13 pm
Please respond to "Yee, Jason" [EMAIL PROTECTED]
To: "'Stull, Cory'" [EMAIL PROTECTED]
"'[EMAIL PROTECTED]'" [EMAIL PROTECTED]
cc: (bcc: JENNY MCLEOD/NSO/CSDA)
Subject: RE: ospf bandwidth question
CRC errors could be due to modem
In a message dated 10/3/00 12:16:20 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
Hmm... not so sure about that. I'm told by an unreliable source (my telco
:-)
that if you're sending from a large access speed to a smaller access speed,
traffic exceeding the CIR + EIR (i.e traffic
CRC errors could be due to modem clocking rate not configured properly etc.
FECNs are generated when data is sent out a congested interface; they
indicate to a DTE that congestion was encountered. Traffic is marked with
BECN if the queue for the opposite direction is deep enough to trigger FECNs
If you don't have the information that OSPF uses to calculate it's metrics
set properly, then OSPF may be overutilizing this link when other paths are
available.
With that said, are you getting a lot of CRC errors? CRC errors are not
normal, and may indicate a problem with your CSU/DSU, or
6 matches
Mail list logo
