If this is the case, and you are adding more users to reach the average 70%
benchmark remember that most service providers will grantee 50% of your
total circuit, so anything over 50% could be tagged as discard eligible (red
Frames) and dropped. Causing lots of re-sends to complete a TCP connection
and thus latency...
--
Michael Damkot CCNP
Technical Trainer
Network Support Engineer II
""Provost, Robert"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> scenerio - site A is on a 56k line using 10% of the bandwidth. If you add
> more users and are now at 70% bandwidth, do the users notice slower
> connections even though the line is not over utilized and you are getting
no
> FECN/BECN, or dropped packets?
>
>
>
> -----Original Message-----
> From: Farhan Ahmed [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 30, 2001 12:03 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Frame Relay - slow link? overutilized? [7:14163]
>
>
> auh--
> u have a big setup..
> most of the frame relay problem happens of remote site pushing too much
data
> that the central site can handle
> u r using default queing strategy.
> and u send me only the remote site config
>
> u need to ccalculate what is the total cir and Be(excess bust speed of all
> remote sites comming into your vc
> u need to provide fine details
>
>
> Best Regards
>
> Have A Good Day!!
>
> *******************************************
> Farhan Ahmed*
> MCSE+I, MCP Win2k, CCDA, CCNA, CSE
> Network Engineer
> Mideast Data Systems Abudhabi Uae.
>
> *******************************************
>
>
>
> Privileged/Confidential Information may be contained in this message or
> Attachments hereto. Please advise immediately if you or your employer do
> not consent to Internet email for messages of this kind. Opinions,
> Conclusions and other information in this message that do not relate to
the
> Official business of this company shall be understood as neither given nor
> Endorsed by it.
>
>
> > -----Original Message-----
> > From: Provost, Robert [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, July 30, 2001 7:22 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Frame Relay - slow link? overutilized? [7:14163]
> >
> >
> > Here is the sh int after cleared counters and 5 minute wait.
> > We have 320+
> > sites. Most sites are 56k lines, some frac T1, some DSL.
> > Most have one PVC
> > back to HQ. HQ has three routers on the Frame w/a total of 7 T1s.
> >
> > Thanks for your help,
> >
> > Rob
> >
> >
> > router#sh int
> > Ethernet0 is up, line protocol is up
> > Hardware is QUICC Ethernet, address is 0001.42a5.c6ec (bia
> > 0001.42a5.c6ec)
> > Internet address is 10.253.X.X/24
> > MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255,
> > load 1/255
> > Encapsulation ARPA, loopback not set, keepalive set (10 sec)
> > ARP type: ARPA, ARP Timeout 04:00:00
> > Last input 00:00:01, output 00:00:00, output hang never
> > Last clearing of "show interface" counters 00:07:13
> > Queueing strategy: fifo
> > Output queue 0/40, 0 drops; input queue 0/75, 0 drops
> > 5 minute input rate 0 bits/sec, 0 packets/sec
> > 5 minute output rate 0 bits/sec, 0 packets/sec
> > 186 packets input, 19777 bytes, 0 no buffer
> > Received 177 broadcasts, 0 runts, 0 giants, 0 throttles
> > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
> > 0 input packets with dribble condition detected
> > 438 packets output, 207446 bytes, 0 underruns
> > 0 output errors, 0 collisions, 0 interface resets
> > 0 babbles, 0 late collision, 0 deferred
> > 0 lost carrier, 0 no carrier
> > 0 output buffer failures, 0 output buffers swapped out
> > Serial0 is up, line protocol is up
> > Hardware is QUICC Serial (with onboard CSU/DSU)
> > Description: router DLCI 200
> > MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255,
> > load 1/255
> > Encapsulation FRAME-RELAY IETF, loopback not set, keepalive
> > set (10 sec)
> > LMI enq sent 44, LMI stat recvd 44, LMI upd recvd 0, DTE LMI up
> > LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
> > LMI DLCI 1023 LMI type is CISCO frame relay DTE
> > Broadcast queue 0/64, broadcasts sent/dropped 25/0,
> > interface broadcasts
> > 18
> > Last input 00:00:00, output 00:00:00, output hang never
> > Last clearing of "show interface" counters 00:07:14
> > Input queue: 0/75/0 (size/max/drops); Total output drops: 0
> > Queueing strategy: weighted fair
> > Output queue: 0/1000/64/0 (size/max total/threshold/drops)
> > Conversations 0/10/256 (active/max active/max total)
> > Reserved Conversations 0/0 (allocated/max allocated)
> > 5 minute input rate 1000 bits/sec, 1 packets/sec
> > 5 minute output rate 0 bits/sec, 0 packets/sec
> > 421 packets input, 167457 bytes, 0 no buffer
> > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
> > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
> > 117 packets output, 9694 bytes, 0 underruns
> > 0 output errors, 0 collisions, 0 interface resets
> > 0 output buffer failures, 0 output buffers swapped out
> > 0 carrier transitions
> > DCD=up DSR=up DTR=up RTS=up CTS=up
> >
> > Serial0.1 is up, line protocol is up
> > Hardware is QUICC Serial (with onboard CSU/DSU)
> > Description: HQ DLCI 100
> > Internet address is 10.254.X.X/30
> > MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255,
> > load 1/255
> > Encapsulation FRAME-RELAY IETF
> >
> > -----Original Message-----
> > From: Farhan Ahmed [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, July 30, 2001 10:52 AM
> > To: 'Provost, Robert'; [EMAIL PROTECTED]
> > Subject: RE: Frame Relay - slow link? overutilized? [7:14163]
> > Importance: High
> >
> >
> > send me sh int
> > clear counters before sending and wait for 5 min to get new stats
> >
> > your router is not receiving lmi packets properly
> > how many sites u have?
> >
> > Num Status Enq. Sent 401101 Num Status msgs Rcvd 400894
> > > Num Update Status Rcvd 0 Num Status Timeouts 2
> >
> > Best Regards
> >
> > Have A Good Day!!
> >
> > *******************************************
> > Farhan Ahmed*
> > MCSE+I, MCP Win2k, CCDA, CCNA, CSE
> > Network Engineer
> > Mideast Data Systems Abudhabi Uae.
> >
> > *******************************************
> >
> >
> >
> > Privileged/Confidential Information may be contained in this
> > message or
> > Attachments hereto. Please advise immediately if you or your
> > employer do
> > not consent to Internet email for messages of this kind. Opinions,
> > Conclusions and other information in this message that do not
> > relate to the
> > Official business of this company shall be understood as
> > neither given nor
> > Endorsed by it.
> >
> >
> > > -----Original Message-----
> > > From: Provost, Robert [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, July 30, 2001 6:18 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Frame Relay - slow link? overutilized? [7:14163]
> > >
> > >
> > > We have a frame relay network with some sites complaining
> > > about slowness
> > > issues. Everyone is blaming the bandwidth without testing.
> > > Is there anyway
> > > I can prove what is causing the latency? Here are some
> > > outputs from the
> > > remote site router. Can someone help me decipher?
> > >
> > > Thanks,
> > > Rob Provost
> > >
> > > router#sh run
> > > Building configuration...
> > >
> > > Current configuration:
> > > !
> > > version 12.0
> > > service timestamps debug uptime
> > > service timestamps log uptime
> > > service password-encryption
> > > !
> > > hostname router
> > > !
> > > enable password X XXXXXXXXXXXXXXX
> > > !
> > > ip subnet-zero
> > > !
> > > !
> > > !
> > > interface Ethernet0
> > > ip address 172.16.1.1 255.255.255.0
> > > ip helper-address 10.1.1.2
> > > no ip directed-broadcast
> > > !
> > > interface Serial0
> > > description router DLCI 200
> > > no ip address
> > > no ip directed-broadcast
> > > encapsulation frame-relay IETF
> > > service-module 56k clock source line
> > > service-module 56k network-type dds
> > > frame-relay lmi-type cisco
> > > !
> > > interface Serial0.1 point-to-point
> > > description HQ DLCI 100
> > > ip address 10.254.12.6 255.255.255.252
> > > no ip directed-broadcast
> > > frame-relay interface-dlci 100
> > > !
> > > router rip
> > > version 2
> > > network 10.0.0.0
> > > !
> > > ip classless
> > > ip route 0.0.0.0 0.0.0.0 10.254.12.5
> > > !
> > > !
> > > line con 0
> > > transport input none
> > > line vty 0 4
> > > password X XXXXXXXXXXXXXXXXX
> > > login
> > > !
> > > end
> > >
> > > router#sh interfaces serial 0
> > > Serial0 is up, line protocol is up
> > > Hardware is QUICC Serial (with onboard CSU/DSU)
> > > Description: router DLCI 200
> > > MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255,
> > > load 1/255
> > > Encapsulation FRAME-RELAY IETF, loopback not set, keepalive
> > > set (10 sec)
> > > LMI enq sent 401099, LMI stat recvd 400892, LMI upd recvd
> > > 0, DTE LMI up
> > > LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
> > > LMI DLCI 1023 LMI type is CISCO frame relay DTE
> > > Broadcast queue 0/64, broadcasts sent/dropped 276474/0, interface
> > > broadcasts 2
> > > 09741
> > > Last input 00:00:00, output 00:00:00, output hang never
> > > Last clearing of "show interface" counters never
> > > Input queue: 0/75/0 (size/max/drops); Total output drops: 0
> > > Queueing strategy: weighted fair
> > > Output queue: 0/1000/64/0 (size/max total/threshold/drops)
> > > Conversations 0/10/256 (active/max active/max total)
> > > Reserved Conversations 0/0 (allocated/max allocated)
> > > 5 minute input rate 1000 bits/sec, 1 packets/sec
> > > 5 minute output rate 1000 bits/sec, 1 packets/sec
> > > 4243911 packets input, 2199323988 bytes, 0 no buffer
> > > Received 0 broadcasts, 0 runts, 2 giants, 0 throttles
> > > 52784 input errors, 35055 CRC, 9168 frame, 0 overrun, 0
> > > ignored, 8561
> > > abort
> > > 1472502 packets output, 215379554 bytes, 0 underruns
> > > 0 output errors, 0 collisions, 69 interface resets
> > > 0 output buffer failures, 0 output buffers swapped out
> > > 1 carrier transitions
> > > DCD=up DSR=up DTR=up RTS=up CTS=up
> > >
> > > router#sh controllers serial
> > >
> > > QUICC Serial (with onboard CSU/DSU) unit 0
> > > idb at 0x25158A8, driver data structure at 0x251710C
> > > SCC Registers:
> > > General [GSMR]=0x2:0x00000030, Protocol-specific [PSMR]=0x0
> > > Events [SCCE]=0x0000, Mask [SCCM]=0x001F, Status [SCCS]=0x0006
> > > Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E
> > > Interrupt Registers:
> > > Config [CICR]=0x00368461, Pending [CIPR]=0x0000C004
> > > Mask [CIMR]=0xC8000012, In-srv [CISR]=0x00000000
> > > Command register [CR]=0x6C0
> > > Port A [PADIR]=0x0000, [PAPAR]=0xCCC3
> > > [PAODR]=0x0000, [PADAT]=0xF5FE
> > > Port B [PBDIR]=0x00F13F, [PBPAR]=0x0010CE
> > > [PBODR]=0x000000, [PBDAT]=0x034ADD
> > > Port C [PCDIR]=0x000A, [PCPAR]=0x0000
> > > [PCSO]=0x0830, [PCDAT]=0x03C4, [PCINT]=0x0000
> > >
> > > SCC GENERAL PARAMETER RAM (at 0xFF00F00)
> > > Rx BD Base [RBASE]=0x560, Fn Code [RFCR]=0x18
> > > Tx BD Base [TBASE]=0x5A0, Fn Code [TFCR]=0x18
> > > Max Rx Buff Len [MRBLR]=1528
> > > Rx State [RSTATE]=0x18008240, BD Ptr [RBPTR]=0x590
> > > Tx State [TSTATE]=0x18000348, BD Ptr [TBPTR]=0x5A0
> > >
> > > SCC HDLC PARAMETER RAM (at 0xFF00F38)
> > > CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8
> > > Errors: CRC [CRCEC]=0, Aborts [ABTSC]=1, Discards [DISFC]=0
> > > Nonmatch Addr Cntr [NMARC]=0
> > > Retry Count [RETRC]=0
> > > Max Frame Length [MFLR]=1526
> > > Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=63837
> > > User-defined Address 0000/0000/0000/0000
> > > User-defined Address Mask 0x0000
> > >
> > >
> > > buffer size 1524
> > > BRGC1=101B0, BRGC2=0, BRGC3=0, BRGC4=0
> > > modem_signal_addr FF01566
> > > MASK: DSR=1, DTR=2,RTS=8.CTS=400,DCD=800
> > > txbrgc=FF015FC, rxbrgc=FF015FC
> > > BRG [DTE]: rx_sicr_clk=7, tx_sicr_clk=6
> > > BRG [DCE]: rx_sicr_clk=7, tx_sicr_clk=3
> > > CLK SRC: sync=4000, async=4000
> > > RX ring with 8 entries at 0xFF00560, Buffer size 1524
> > > Rxhead = 0xFF00578 (3), Rxp = 0x2517134 (3)
> > > 00 pak=0x251D0E0 buf=0x279A480 status=9000 pak_size=0
> > > 01 pak=0x251CEDC buf=0x2799DC4 status=9000 pak_size=0
> > > 02 pak=0x251B99C buf=0x27953B0 status=9000 pak_size=0
> > > 03 pak=0x25AC584 buf=0x27B24B0 status=9000 pak_size=0
> > > 04 pak=0x25AD19C buf=0x27B4D18 status=9000 pak_size=0
> > > 05 pak=0x25AC788 buf=0x27B2B6C status=9000 pak_size=0
> > > 06 pak=0x25AC380 buf=0x27B1DF4 status=9000 pak_size=0
> > > 07 pak=0x251CCD8 buf=0x2799708 status=B000 pak_size=0
> > >
> > > TX ring with 2 entries at 0xFF005A0, tx_count = 1
> > > tx_head = 0xFF005A0 (0), head_txp = 0x2517184 (0)
> > > tx_tail = 0xFF005A8 (1), tail_txp = 0x2517188 (1)
> > > 00 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0
> > > 01 pak=0x25606F4 buf=0x279EBC8 status=BC00 pak_size=600
> > > QUICC SCC specific errors:
> > > 8561 input aborts on receiving flag sequence
> > > 0 throttles, 0 enables
> > > 0 overruns
> > > 0 transmitter underruns
> > > 0 transmitter CTS losts
> > >
> > > LXT441 (CSU/DSU) registers at 0xD040000
> > > Mode=0x10, Call=0x00, Loopback=0x00 (Forced=none), Reg3=0x00
> > > Reg4=0x00, Reg5=0x00, Reg6=0x00, Reg7=0x9F
> > > Last Interrupt Status=0x20 (Int Enable=0x61)
> > > Handshake Signal Status=0x6B (R9=0x6B, Forced=none)
> > > Status=0x3D, Regb=0x59, Rx Code=0x00 (Last valid=0x00, Rx
> > Enable=0x3D)
> > > BPV=0x6A, Rege=0x00, Regf=0x00
> > >
> > > Glue logic (also RDL) registers at 0xD080000
> > > SSR0=0x23 (Rev 2, RDL ERROR), SCR0=0x1F
> > > SCR1=0xA0 (RDL Loop Up Detection, Actual=0xA0)
> > > router#sh frame lmi
> > >
> > > LMI Statistics for interface Serial0 (Frame Relay DTE) LMI
> > > TYPE = CISCO
> > > 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 401101 Num Status msgs Rcvd 400894
> > > Num Update Status Rcvd 0 Num Status Timeouts 207
> > > router#
>
> [GroupStudy.com removed an attachment of type application/octet-stream
which
> had a name of Farhan Ahmed.vcf]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=14221&t=14163
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
