Raul- ask your provider for status reports. We get them from Qwest weekly,
documenting our Frame & ATM connections. You would want to pay special
attention to the Ingress & Egress values. This would reveal a busy Telco
switch or even a Zero CIR circuit as the culprit. If your a Touch America
customer- good luck :o)
All the best
Phil
----- Original Message -----
From: "John Neiberger"
To:
Sent: Tuesday, August 07, 2001 6:41 PM
Subject: Re: Need some advice on a Frame Relay Latency issue [7:15146]
> If you are seeing inconsistent and unusually long ping response times
> between two routers connected to a frame relay network--especially if
> you're not seeing physical errors--it's probably the frame relay
> provider. This exact situation has happened at least three times in the
> last year with Qwest. Sometimes it takes quite a bit of prodding to get
> them to search out the offending equipment, but don't let them continue
> to say it's your equipment just because they're lazy and don't want to
> do some troubleshooting. :-)
>
> Regards,
> John
>
> >>> "Raul De La Garza" 8/7/01 1:12:48 PM
> >>>
> Hello everyone.
>
> I have a peculiar problem with one of my company's FR circuits. We
> have
> been trying to troubleshoot this issue ever since we purchased FR to
> replace
> point-to-point HDLC. This circuit has a 256K CIR and 512K port speed.
>
> Bandwidth utilization is low and never approaches the CIR. The remote
>
> router's CPU and memory utilization are also very low. At present,
> only
> weighted fair queueing is enabled. We have tried priority queueing and
>
> traffic shaping to no avail. User response times are extremely high
> ranging
> anywhere between 80ms to over 2000ms!
>
> Also, we are routing IP (no ip routing protocol, I have set a default
> route
> back to corporate as this remote office is one of a few spokes in our
> hub-and-spoke topology) and we are routing IPX using EIGRP.
>
> The central site FR router is a 3640 with two T1 WICs with integrated
> DSUs.
> The remote site router is a 2501 connected to an ADC Kentrox DataSMART
> 658
> T1 DSU.
>
> Our FR vendor claims that his tests running from DCE to DCE receive a
> consistent response time of 70ms. However, the vendor has noted that
> when
> ICMP messages are sent to the remote router some are responded to very
>
> quickly but most do take an unusually great amount of time in
> responding.
> This the vendor found when placing a sniffer on the local loop.
>
> So it seems that there may be a config issue or a hardware issue at our
>
> remote site. Any words of wisdom you can provide would be greatly
> appreciated.
>
> Following are the configs for the remote router and the central
> router.
>
> ************REMOTE****************
>
> Clrwtr_Frame#sh run
> Building configuration...
>
> Current configuration:
> !
> ! Last configuration change at 14:09:24 UTC Tue Aug 7 2001
> ! NVRAM config last updated at 14:28:59 UTC Tue Aug 7 2001
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> service password-encryption
> !
> hostname Clrwtr_Frame
> !
> boot system flash 1:aaa0862.bin
> logging monitor informational
> enable secret 5
> !
> ip subnet-zero
> no ip finger
> no ip domain-lookup
> ipx routing 00d0.58ad.759a
> ipx gns-round-robin
> !
> !
> !
> interface Ethernet0
> ip address 10.48.2.1 255.255.255.0
> no ip directed-broadcast
> no ip route-cache
> no ip mroute-cache
> ipx input-sap-filter 1005
> ipx encapsulation SAP
> ipx network C0480021
> !
> interface Serial0
> no ip address
> no ip directed-broadcast
> encapsulation frame-relay
> no ip route-cache
> no ip mroute-cache
> !
> interface Serial0.1 point-to-point
> bandwidth 256
> ip address 10.201.0.73 255.255.255.252
> no ip directed-broadcast
> no ip route-cache
> no ip mroute-cache
> ipx network C2010073
> frame-relay interface-dlci 17
> !
> interface Serial1
> no ip address
> no ip directed-broadcast
> no ip route-cache
> no ip mroute-cache
> shutdown
> !
> interface Dialer0
> no ip address
> no ip directed-broadcast
> no ip route-cache
> no ip mroute-cache
> !
> ip classless
> ip route 0.0.0.0 0.0.0.0 10.201.0.74
> !
> access-list 99 permit 10.1.4.200
> access-list 1005 deny C0480021 3
> access-list 1005 deny C0480021 7
> access-list 1005 deny C0480021 47
> access-list 1005 permit FFFFFFFF
> priority-list 1 protocol ip high tcp 5900
> priority-list 1 protocol ipx low
> priority-list 1 protocol ip medium tcp 1352
> priority-list 1 protocol ip high tcp telnet
> priority-list 1 protocol ip medium udp 1352
> priority-list 1 protocol ip normal
> priority-list 1 protocol ip high tcp 12000
> priority-list 1 protocol ip high tcp 13000
> priority-list 1 protocol ip high tcp 1494
> priority-list 1 default low
> !
> !
> ipx router eigrp 18
> network all
> !
> !
> !
> snmp-server community tup2go RO
> snmp-server community redpings RW 99
> snmp-server community public RO
> banner exec ^C
> ***************************************************
> * *
> * Welcome to Clrwtr_Frame! *
> * *
> * For assistance, call Cisco TAC *
> * or contact xxxxxx's MIS Network Staff *
> * *
> * IS Manager: xxxxxx xxxxxxx xxx.xxx.xxxx *
> * Sen. Eng: xxxx xx xx xxxxx xxx.xxx.xxxx *
> * *
> ***************************************************
> ^C
> banner motd ^C
> Property of Emcare Incorporated
>
> All violaters will be prosecuted to the full extant of the law.
>
> ^C
> !
> line con 0
> exec-timeout 0 0
> password 7
> login
> transport input none
> line aux 0
> exec-timeout 3 0
> password 7
> login
> modem InOut
> transport input all
> stopbits 1
> speed 38400
> flowcontrol hardware
> line vty 0 4
> password 7
> login
> !
> ntp clock-period 17180034
> ntp server 10.1.1.2
> end
>
> **************CENTRAL*********************
>
> Dallas_3640#sh run
> Building configuration...
>
> Current configuration:
> !
> ! Last configuration change at 17:38:47 UTC Thu Aug 2 2001
> ! NVRAM config last updated at 16:51:37 UTC Thu Aug 2 2001
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> service password-encryption
> !
> hostname Dallas_3640
> !
> boot system flash 1:c3640-d-mz.120-7.bin
> no logging console
> logging monitor errors
> enable secret 5
> !
> !
> !
> !
> !
> ip subnet-zero
> no ip domain-lookup
> !
> ipx routing 0002.1630.7501
> ipx gns-round-robin
> !
> !
> !
> interface Ethernet0/0
> description Connected to Dallas Ethernet
> ip address 10.1.1.2 255.255.0.0
> no ip directed-broadcast
> ipx input-sap-filter 1005
> ipx encapsulation SAP
> ipx network 2
> !
> interface Serial0/0
> description T1 DATA1
> no ip address
> no ip directed-broadcast
> encapsulation frame-relay
> no ip mroute-cache
> no fair-queue
> service-module t1 remote-alarm-enable
> frame-relay traffic-shaping
> frame-relay qos-autosense
> !
> interface Serial0/0.1 point-to-point
> description Connected to Clearwater
> bandwidth 256
> ip address 10.201.0.74 255.255.255.252
> no ip directed-broadcast
> ipx network C2010073
> frame-relay interface-dlci 22
> !
> interface Serial0/0.3 point-to-point
> description Connected to Santa Barbara
> bandwidth 128
> ip address 10.201.0.78 255.255.255.252
> no ip directed-broadcast
> ipx network C2010077
> frame-relay class clearwater
> frame-relay interface-dlci 20
> !
> interface Serial0/0.5 point-to-point
> description Connected to St. Louis (Woodfield)
> bandwidth 256
> ip address 10.201.0.66 255.255.255.252
> no ip directed-broadcast
> frame-relay class stlouis
> frame-relay interface-dlci 23
> !
> interface Serial0/1
> description T1 DATA2
> no ip address
> no ip directed-broadcast
> encapsulation frame-relay
> no fair-queue
> service-module t1 remote-alarm-enable
> frame-relay traffic-shaping
> frame-relay lmi-type cisco
> frame-relay qos-autosense
> !
> interface Serial0/1.1 point-to-point
> description Connected to Atlanta
> bandwidth 256
> ip address 10.201.0.34 255.255.255.252
> no ip directed-broadcast
> ipx network C2010033
> frame-relay class stlouis
> frame-relay interface-dlci 28
> !
> interface Serial0/1.2 point-to-point
> description Connected to Elmhurst
> bandwidth 256
> ip address 10.201.0.30 255.255.255.252
> no ip directed-broadcast
> ipx network A0000121
> frame-relay class stlouis
> frame-relay interface-dlci 19
> !
> interface Serial0/1.3 point-to-point
> description Connected to Horsham
> bandwidth 256
> ip address 10.201.0.26 255.255.255.252
> no ip directed-broadcast
> ipx network C2010025
> frame-relay class stlouis
> frame-relay interface-dlci 25
> !
> interface Serial0/1.4 point-to-point
> description Connected to San Jose
> bandwidth 128
> ip address 10.201.0.90 255.255.255.252
> no ip directed-broadcast
> ipx network C2010089
> frame-relay class clearwater
> frame-relay interface-dlci 30
> !
> interface Serial0/1.5 point-to-point
> description Connected to (Spartanburg)
> bandwidth 128
> ip address 10.201.0.86 255.255.255.252
> no ip directed-broadcast
> ipx network C2010085
> frame-relay class clearwater
> frame-relay interface-dlci 29
> !
> router eigrp 18
> redistribute static
> network 10.1.0.0 0.0.255.255
> network 10.0.0.0
> !
> ip classless
> ip route 0.0.0.0 0.0.0.0 10.1.1.24
> ip route 10.11.0.0 255.255.0.0 Serial0/1.3
> ip route 10.48.0.0 255.255.255.0 10.25.0.14
> ip route 10.48.2.0 255.255.255.0 10.201.0.73
> ip route 10.48.4.0 255.255.255.0 Serial0/0.3
> ip route 10.50.1.0 255.255.255.0 Serial0/1.1
> ip route 10.202.35.0 255.255.255.0 Serial0/0.5
> ip route 10.202.36.0 255.255.255.0 Serial0/1.2
> ip route 10.202.40.0 255.255.255.0 10.1.1.38
> ip route 10.202.42.0 255.255.255.0 10.1.1.38
> ip route 10.202.43.0 255.255.255.0 Serial0/1.4
> ip route 185.245.0.0 255.255.0.0 10.1.1.1
> no ip http server
> !
> !
> map-class frame-relay clearwater
> frame-relay traffic-rate 128000 256000
> no frame-relay adaptive-shaping
> !
> map-class frame-relay stlouis
> frame-relay traffic-rate 256000 512000
> no frame-relay adaptive-shaping
> !
> map-class frame-relay clrwtr-becn
> frame-relay adaptive-shaping becn
> access-list 1005 deny 2 3
> access-list 1005 deny 2 7
> access-list 1005 deny 2 47
> access-list 1005 permit FFFFFFFF
> priority-list 1 default low
> !
> !
> ipx router eigrp 18
> network all
> !
> !
> ipx router rip
> no network C2010025
> no network C2010073
> no network C2010033
> no network C2010089
> no network C2010077
> no network A0000121
> !
> !
> !
> snmp-server engineID local 000000090200000216307511
> snmp-server community tup2go RO
> snmp-server community redpings RW 99
> snmp-server community public RO
> snmp-server enable traps snmp
> snmp-server enable traps config
> snmp-server enable traps syslog
> snmp-server enable traps frame-relay
> snmp-server enable traps rtr
> banner exec ^C
>
> ***************************************************
> * *
> * Welcome to Dallas_3640! *
> * *
> * For assistance, call Cisco TAC *
> * or contact xxxxxxxx MIS Network Staff *
> * *
> * IS Manager: xxxxxx xxxxxxx xxx.xxx.xxxx *
> * Sen. Eng: xxxx xx xx xxxxx xxx.xxx.xxxx *
> * *
> ***************************************************
> ^C
> banner motd ^C
>
>
>
>
>
>
>
>
>
>
> WARNING!
>
> Use of this network is restricted to authorized users. User activity is
>
> monitore
> d and recorded ^C
> !
> line con 0
> exec-timeout 0 0
> password 7
> login
> transport input none
> line aux 0
> password 7
> login
> modem Dialin
> line vty 0 4
> password 7
> login
> !
> ntp clock-period 17180195
> ntp server 10.1.1.33
> end
>
> Thank you,
>
> Raul De La Garza
> CCDP NNCSS MCSE CNE
>
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at
> http://explorer.msn.com/intl.asp
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=15202&t=15146
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
