cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
250
Views
0
Helpful
1
Replies

Congestion Issues on frame relay WAN links

t.whiten
Level 1
Level 1

I am having congestion issues with remote sites on a new frame relay network. I am using a 3725s w/ 2 FULL T1s at the host site and 2610s at 7 remote locations. Every remote site has 512K bandwidth and 384CIR. The following is the frame config from the host and remote sites along with the SH FRAME-RELAY output after a single file transfer. I am recieving BECN's at the host and FECN's and the remotes which tells me there is congestion at the remote sites. I have tried to apply some traffic shaping but still having congestion issues. The customer ran the same applications previously with another carrier without problems. The difference here is new carrier new routers.

****Remote Site****

interface Serial0/0

no ip address

encapsulation frame-relay IETF

frame-relay traffic-shaping

frame-relay lmi-type ansi

!

interface Serial0/0.1 point-to-point

description ****512K/384K FR TO EASLY MAIN****

ip address 10.1.2.2 255.255.255.252

no cdp enable

frame-relay class SLOW

frame-relay interface-dlci 104

map-class frame-relay SLOW

frame-relay traffic-rate 384000 512000

frame-relay fair-queue

frame-relay fragment 640

****HOST****

interface Serial0/0

no ip address

encapsulation frame-relay IETF

frame-relay traffic-shaping

frame-relay lmi-type ansi

!

interface Serial0/0.1 point-to-point

description ****512K/384K FR TO EASLY MAIN****

ip address 10.1.2.2 255.255.255.252

no cdp enable

frame-relay class SLOW

frame-relay interface-dlci 104

map-class frame-relay SLOW

frame-relay traffic-rate 384000 512000

frame-relay fair-queue

frame-relay fragment 640

****This is the SH FRAME_RELAY command after one 1M file transfer****

****REMOTE****

DLCI = 104, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.1

input pkts 2120 output pkts 1747 in bytes 1358160

out bytes 407778 dropped pkts 0 in pkts dropped 0

out pkts dropped 0 out bytes dropped 0

in FECN pkts 605 in BECN pkts 0 out FECN pkts 0

out BECN pkts 0 in DE pkts 117 out DE pkts 0

out bcast pkts 3 out bcast bytes 951

5 minute input rate 34000 bits/sec, 5 packets/sec

5 minute output rate 11000 bits/sec, 3 packets/sec

pvc create time 8w1d, last time pvc status changed 3d22h

ANDERSON_GVLLE_ST#

****HOST****

DLCI = 104, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.1

input pkts 1730 output pkts 2107 in bytes 407242

out bytes 1356137 dropped pkts 0 in FECN pkts 0

in BECN pkts 312 out FECN pkts 0 out BECN pkts 0

in DE pkts 0 out DE pkts 0

out bcast pkts 2 out bcast bytes 744

5 minute input rate 4000 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

pvc create time 00:47:56, last time pvc status changed 00:47:56

EASLEY_MAIN#

1 Reply 1

rjackson
Level 5
Level 5

In my experience FECNs and BECNs are normal during file transfers. You are not dropping packets so it seems like traffic shaping is only going to slow things down.

It is also my understandinfg that the purpose of shaping is to make pvcs share the bandwidth in proportions that you desire. To just use BECNs you should use adaptive shaping becn.

I'll be watching to see what the experts say.