Cisco 2800 tunnel bandwidth limiting

[SharpNetSol]

Hi there,

I'm new to the forum and to Cisco having spent most of my working life in Nortel land. I am looking for advice as to how to limit bandwidth for the following tunnel config -

!

bridge irb

!

!

!

interface Tunnel1

ip unnumbered Loopback0

ip route-cache flow

keepalive 5 4

tunnel source Loopback0

tunnel destination 192.168.253.2

bridge-group 1

!

interface Loopback0

ip address 192.168.254.2 255.255.255.255

ip route-cache flow

!

interface FastEthernet0/0

description Public ADSL line

no ip address

ip route-cache flow

duplex full

speed 100

bridge-group 1

!

interface FastEthernet0/1

no ip address

shutdown

duplex auto

speed auto

!

The tunnel is currently carrying internet traffic going across Vsat with no limitation but we are about to move it to a fibre link and the internet circuit we are going to use is much larger than the current setup and so we will need to limit the bandwidth.

Any advice greatly appreciated.

[SharpNetSol]

Will a simple bandwidth statement in that config do the job ie 'bandwidth 1024' ?

[Joseph W. Doherty]

Disclaimer

The   Author of this posting offers the information contained within this   posting without consideration and with the reader's understanding that   there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In   no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising  out  of the use or inability to use the posting's information even if  Author  has been advised of the possibility of such damage.

Posting

No it won't.  The bandwidth statement just sets a logical value, although other "things" can use it.

Normally you limit bandwidth by policing on an ingress interface, might be physical or logical (tunnel).

For egress interfaces, you can police too, or perhaps shape.

Since you're bridging, unsure policers/shapers would work as they do on routed ports.

[SharpNetSol]

Thanks for replying Joesph. So think because we are bridging it may not be possible to police / shape the traffic on this tunnel? So I should perhaps look at a different means of keeping this traffic isolated and shaped across our link?

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

Again, not sure, when using bridging.

Quickest way to check might be to simply place a service policy on bridged tunnel or physical interface and see if it works as desired.

Are you familiar with using in/out service policies?