Bandwidth Restricting On Serial Link

[Steve30]

Hi All,

I have a serial connection between two sites. A cisco 3640 (Site A) and cisco 1720 (Site B).
Site B site has a mix of thin client terminals (Citrix Metaframe) and fat (Windows 2000) PC's.

As the serial line is 256K I experience problems when the fat clients download/send large email attachments over the WAN to Site A where the mail server resides.

I need to restrict bandwidth on the link for the fat clients to 50% of the available bandwidth. All the fat clients at site B have a static IP address.

How is the best way to do this ?

Many thanks.

 

[computerhighguy]

Why would you want to restrict bandwidth? You really want to setup a policy map so certain traffic (you can do this by destination and source using an access-list) has priority over other traffic. Here is an example we use to priotitze Cisco VoIP traffic for CCM and traffic for our e-mail server. By doing it this way, your routers prioritize traffic yuou speficy while still allowing your FAT clients to use the rest of the bandwidth. If there is no priority traffic at the time, they can use the whole 256K line (until some priority traffic starts to flow again). You might also want to consider things like header compression and compression in general ifyou routers can handle it.

class-map match-all Signalling
match ip dscp ef
class-map match-all Exchange
match access-group name Exchange_Traffic
class-map match-all Voice
match ip dscp af31
!
!
policy-map VoIP
class Voice
priority percent 40
class Signalling
bandwidth percent 15
class Exchange
bandwidth percent 15
class class-default
fair-queue

interface Ethernet1
service-policy output VoIP

ip access-list extended Exchange_Traffic
remark AL for Exchange Traffic
permit ip any host 10.x.x.250
permit ip any host 10.x.x.33


It is what it is!!
__________________________________
A+, Net+, I-Net+, Certified Web Master, MCP, MCSA, MCSE, CCNA, CCDA, and few others (I got bored one day)

 

[UnaBomber]

On our sites we use packetshapers to do this, don't know what your budget is, but for QoS and CoS I would recomend using Packetters...

Same idea as using QoS on your Router, where you can assign a percentage of your full bandwidth per application, or service, and have this burstable to full amount when your link is not been used by "priority" applications...

We use this to maintain SSH and Telnet access accross our WAN for accessing our ERP system therefore no matter how much email etc is eating the bandwidth orders can be entered