Hmmm...  well, in 16.5 hours it only dropped one keepalive and had one error
out of 307000 packets, which isn't too bad.  there shouldn't be any at all,
but one bad packet in 300k isn't going to hurt that much.

The line certainly doesn't appear to be over-utilized by any stretch.

Hmmm... I'd still blame the telco, but that's my number one rule anyway. :-)
One thing that is worth trying is to disconnect all the relevant cables and
reconnect them a few times, especially the cable from the CSU/DSU to the
network jack.  This actually resolved a problem that we had that neither I
or the telco could figure out.  That T-1 is now running perfectly clean and
it was experiencing 5-10% errors before.

HTH,
John

>  Gladly, I think the frame error coincided with a line proto bounce
>  I think it may be environmental at site - maybe 
>  
>  Serial0/0 is up, line protocol is up 
>    Hardware is PowerQUICC Serial
>    Description: 128k Frame Relay Service Y216077142N
>    MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, 
>       reliability 255/255, txload 1/255, rxload 6/255
>    Encapsulation FRAME-RELAY IETF, loopback not set
>    Keepalive set (10 sec)
>    LMI enq sent  5960, LMI stat recvd 5959, LMI upd recvd 0, DTE LMI up
>    LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
>    LMI DLCI 0  LMI type is ANSI Annex D  frame relay DTE
>    Broadcast queue 0/64, broadcasts sent/dropped 28365/0, interface
broadcasts 27328
>    Last input 00:00:00, output 00:00:00, output hang never
>    Last clearing of "show interface" counters 16:33:25
>    Queueing strategy: fifo
>    Output queue 0/40, 0 drops; input queue 0/75, 0 drops
>    5 minute input rate 42000 bits/sec, 20 packets/sec
>    5 minute output rate 11000 bits/sec, 17 packets/sec
>       307661 packets input, 75148222 bytes, 0 no buffer
>       Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
>       1 input errors, 0 CRC, 1 frame, 0 overrun, 0 ignored, 0 abort
>       315493 packets output, 34616802 bytes, 0 underruns
>       0 output errors, 0 collisions, 1 interface resets
>       0 output buffer failures, 0 output buffers swapped out
>       0 carrier transitions
>       DCD=up  DSR=up  DTR=up  RTS=up  CTS=up
>  
>  >>> John Neiberger <[EMAIL PROTECTED]> 03/14 11:09 am >>>
>  Could we also see a copy of "show interfaces"?  I didn't see anything
>  obviously wrong with what you already posted, except that the logs are
out
>  of order.  Well, I'm not sure what those LMI status timeouts mean.  It's
not
>  dropping keepalives, though.  Hmmm...  Yes, please post some more
interface
>  info.
>  
>  And do you have any other information? Have you replaced the CSU/DSU?
Have
>  you replaced both cables attached to it? Have you tried a different port
on
>  the router, or a different router?
>  
>  John
>  
>  >  Hi All
>  >  
>  >  I've a FR site 32/64Kbit that flaps intermittantly
>  >  The carrier has check it & says nothing is wrong, cable has been
replaced
>  >  
>  >  detail below:
>  >  
>  >  router#sh fr pvc
>  >  
>  >  PVC Statistics for interface Serial0/0 (Frame Relay DTE)
>  >  
>  >                Active     Inactive      Deleted       Static
>  >    Local          1            0            0            0
>  >    Switched       0            0            0            0
>  >    Unused         0            0            0            0
>  >  
>  >  DLCI = 16, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
>  Serial0/0.16
>  >  
>  >    input pkts 251505        output pkts 254458       in bytes 60629859 

>  >    out bytes 29044923       dropped pkts 794         in FECN pkts 0    

>  
>  >    in BECN pkts 0           out FECN pkts 0          out BECN pkts 0   

>  
>  >    in DE pkts 10933         out DE pkts 0         
>  >    out bcast pkts 26559      out bcast bytes 2862020   
>  >    Shaping adapts to BECN
>  >    pvc create time 15:31:26, last time pvc status changed 02:16:23
>  >  
>  >  router#sh fr lmi
>  >  
>  >  LMI Statistics for interface Serial0/0 (Frame Relay DTE) LMI TYPE =
ANSI
>  >    Invalid Unnumbered info 0             Invalid Prot Disc 0
>  >    Invalid dummy Call Ref 0              Invalid Msg Type 0
>  >    Invalid Status Message 0              Invalid Lock Shift 0
>  >    Invalid Information ID 0              Invalid Report IE Len 0
>  >    Invalid Report Request 0              Invalid Keep IE Len 0
>  >    Num Status Enq. Sent 5588             Num Status msgs Rcvd 5588
>  >    Num Update Status Rcvd 0              Num Status Timeouts 49
>  >  
>  >  Mar 14 10:22:01: Serial0/0(in): Status, myseq 162
>  >  Mar 14 10:22:01: RT IE 1, length 1, type 1
>  >  Mar 14 10:22:01: KA IE 3, length 2, yourseq 195, myseq 162
>  >  Mar 14 10:22:11: Serial0/0(out): StEnq, myseq 163, yourseen 195, DTE
up  
>  
>  >  Mar 14 10:22:11: datagramstart = 0x1B759D4, datagramsize = 14
>  >  Mar 14 10:22:11: FR encap = 0x00010308
>  >  Mar 14 10:22:11: 00 75 95 01 01 01 03 02 A3 C3 
>  >  
>  >  Mar 14 10:16:51: Serial0/0(in): Status, myseq 131
>  >  Mar 14 10:16:51: RT IE 1, length 1, type 0
>  >  Mar 14 10:16:51: KA IE 3, length 2, yourseq 164, myseq 131
>  >  Mar 14 10:16:51: PVC IE 0x7 , length 0x3 , dlci 16, status 0x2 
>  >  Mar 14 10:17:01: Serial0/0(out): StEnq, myseq 132, yourseen 164, DTE
up
>  >  Mar 14 10:17:01: datagramstart = 0x1B75254, datagramsize = 14
>  >  Mar 14 10:17:01: FR encap = 0x00010308
>  >  Mar 14 10:17:01: 00 75 95 01 01 01 03 02 84 A4 
>  >  
>  >  Mar 14 10:19:51: Serial0/0(in): Status, myseq 149
>  >  Mar 14 10:19:51: RT IE 1, length 1, type 0
>  >  Mar 14 10:19:51: KA IE 3, length 2, yourseq 182, myseq 149
>  >  Mar 14 10:19:51: PVC IE 0x7 , length 0x3 , dlci 16, status 0x2 
>  >  Mar 14 10:20:01: Serial0/0(out): StEnq, myseq 150, yourseen 182, DTE
up
>  >  Mar 14 10:20:01: datagramstart = 0x1B759D4, datagramsize = 14
>  >  Mar 14 10:20:01: FR encap = 0x00010308
>  >  Mar 14 10:20:01: 00 75 95 01 01 01 03 02 96 B6 
>  >  
>  >  Mar 14 10:20:51: Serial0/0(in): Status, myseq 155
>  >  Mar 14 10:20:51: RT IE 1, length 1, type 0
>  >  Mar 14 10:20:51: KA IE 3, length 2, yourseq 188, myseq 155
>  >  Mar 14 10:20:51: PVC IE 0x7 , length 0x3 , dlci 16, status 0x2 
>  >  Mar 14 10:21:01: Serial0/0(out): StEnq, myseq 156, yourseen 188, DTE
up
>  >  Mar 14 10:21:01: datagramstart = 0x1B74AD4, datagramsize = 14
>  >  Mar 14 10:21:01: FR encap = 0x00010308
>  >  Mar 14 10:21:01: 00 75 95 01 01 01 03 02 9C BC 
>  >  
>  >  Mar 14 10:21:51: Serial0/0(in): Status, myseq 161
>  >  Mar 14 10:21:51: RT IE 1, length 1, type 0
>  >  Mar 14 10:21:51: KA IE 3, length 2, yourseq 194, myseq 161
>  >  Mar 14 10:21:51: PVC IE 0x7 , length 0x3 , dlci 16, status 0x2 
>  >  Mar 14 10:22:01: Serial0/0(out): StEnq, myseq 162, yourseen 194, DTE
up
>  >  Mar 14 10:22:01: datagramstart = 0x1B74D54, datagramsize = 14
>  >  Mar 14 10:22:01: FR encap = 0x00010308
>  >  Mar 14 10:22:01: 00 75 95 01 01 01 03 02 A2 C2 
>  >  
>  >  
>  >  Any help appreciated
>  >  
>  >  Thankyou
>  >  
>  >  David
>  >  
>  >  _________________________________
>  >  FAQ, list archives, and subscription info:
>  http://www.groupstudy.com/list/cisco.html 
>  >  Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

>  
>  
>  
>  
>  
>  _______________________________________________________
>  Send a cool gift with your E-Card
>  http://www.bluemountain.com/giftcenter/ 
>  
>  
>  _________________________________
>  FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
>  Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]





_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/


_________________________________
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