You need to look at multiple factors when checking for dropped traffic.  You
say forget DE and such but this is actually important when checking for this
type of information.  Discard Eligible packets are not guaranteed to cross
the pvc.  Do you know what your CIR rate is from your carrier?  They only
guarantee this amount..  If you send over this amount for an extended amount
of time (which many customers do) then you can definitely lose traffic..

Like someone already mentioned, clear you counters on both ends and monitor.
You may also want to do extended pings based on your pvc size during a time
when traffic on your system is low.

Thanks,

Mike Munoz




-----Original Message-----
From: Rizzo Damian [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 15, 2001 10:15 AM
To: [EMAIL PROTECTED]
Subject: Frame relay and dropped packets... [7:4529]


Hi all,
 
              We have reason to believe we are experiencing Dropped packets
between us and our remote branch. What I need 
Is proof, so I can go to my manager and say, "here, look at this". He
believes just because he looks at the router and does a "show frame pvc" and
the Dropped Pkts statistic is 0, that there are no packets being dropped.
Logical Assumption, but I've been told that just isn't the case. Let me
throw this out to the group....Forget about the FECN's, BECN's and the DE
pkts...If you were to telnet to both routers and look at the statistics of
the point-to-point DLCI and compare the Output pkts on one end to the Input
pkts on the other end, and if you see a discrepancy of 500,000....correct me
if I'm wrong here, but wouldn't that symbolize Dropped packets???    Thanks!
 
  
    -Rizzo
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=4544&t=4529
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to