Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

Re: Different WAN and LAN speed ...


I have always seen this and just wanted to know how it works .... The question is that the WAN routers speed is say

100MB and it is connected to an access switch, 4506 which has gig ports on it.

My question is that if say that there are 72 over gig ports on the 4506 and it is uses the 10MB link, wouldn't the link

be badly saturated say if the 72 ports are quite highly utlized and its traffic is going to this WAN router ?

How does this work ?

Pls advice,


- InternetB -

Community Member

Re: Re: Different WAN and LAN speed ...

Yes, only if the WAN traffic is more then you will have to see the utilization on the serial interface and need to plan if you need to upgrade the wan bandwidth to E1 or E3 lines.

You have various montoring tools to check the utilization of WAN link with respect to times/ type of traffic.etc.

you then have QoS setting also that need to be configured appropriately for traffic flow over WAN. These can be used to optimally utilize and prioritize imp traffice orver non-imp traffic.

Super Bronze

Re: Re: Different WAN and LAN speed ...

You can encounter congestion at any point where you oversubscribe bandwidth.

Take an example where we have hosts connected to your switch at 1,000 Mps (gig), a WAN router connected to it at 100 Mbps (FastEthernet), and the WAN router having a 1 Mbps link. With this setup, even a single host can easily push data faster than either the WAN link can handle, or the WAN router's connection to the switch can handle.

What often happens, though, is most traffic runs over TCP. TCP starts by only sending a couple of packets and waits to see if the host received them. If so, the TCP sender will double the number of packets, and see if they are received. Without going into all the details of TCP flow control, TCP may keep doing this packet transmission doubling until it sees drops. When it sees drops, it decreases the number of packets it sends and starts to increase them again, although in the latter case, usually by a packet at a time.

What's happening, TCP will try to use all the minimal bandwidth along the path. What you might see is the 1 Mbps link hits 100%, but you don't see the 100 Mbps link hit more than an average of 1%. Your WAN link will become badly saturated, but not the Ethernet link to the router.

Saturation isn't always bad. TCP will deliver its data at the reduced bandwidth rate that's available to it.

However, to avoid any saturation on the WAN link, you would need to size it (and the router connection to the switch) to handle the concurrent number of gig flows you expect. If your 72 gig ports were only busy about 10%, your WAN path might avoid any congestion with 8 to 10 gig of bandwidth.

With TCP traffic, you can size bandwidth for what you want the effective bandwidth to be. Choice is yours.

With non-TCP traffic, things might change. Non-TCP might not have any flow control and would require the 8 to 10 gig of WAN bandwidth to work well or it might not work at all.

For example, you might run a 100 GB backup over a 5.6 Kbps dial-up modems (will take some time!!!) sucessfully, but might need a DS-3 to support Cisco TelePresense.

CreatePlease to create content