cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
398
Views
0
Helpful
4
Replies

Bandwidth Sharing - Scenario

ronald.ramzy
Level 1
Level 1

Hi,

ISP provided 6MB Internet connection through UTP Cable.

I need to share 6MB connection between 3 internal departments.

Currently I have terminated 6MB on Cisco 2800 series Router.

All three departments are now connected to common backbone switch on different VLAN.

What steps are needed to accomplish the bandwidth sharing.

((Connection_Details))

(1) Connected to ISP via 2800 series Router and to LAN on Cisco 4500

(2) BackBone Switch# 4500

(3) Dep#1 is connected via Fiber on Cisco 4500. ( Dept#1 has 2960 switch )

(4) Dep#2 is connected via Fiber on Cisco 4500. ( Dept#1 has 2960 switch )

(5) Dep#3 is connected via Fiber on Cisco 4500. ( Dept#1 has 2960 switch )

It becomes more complex when department will use the bandwidth for internet browsing / Mail relaying and VPN or Web_Hosting.

4 Replies 4

Laurent Aubert
Cisco Employee
Cisco Employee

Hi,

Do you mean that you want to manage the 6Mb

allocation in case of congestion ?

Is the 2800 natting your outgoing traffic to the Internet ?

Thanks

Laurent.

Hi,

On 2800 the ISP (UTP) link is terminating.(you can consider as internet router )

Total Bandwidth is 6MB and I have to give dedicated 2MB to each department.

and I have to provide Bandwidth utilization report via MRTG or SolarWinds

Any suggestion

"Any suggestion"

Yes, don't divide bandwidth per dept.

I would recommend shape for 6 Mbps (less 5 to 15% to allow for Ethernet overhead) outbound with FQ. Inbound, do the same if you can implement same on ISP's egress (unlikely).

If you really want to divide outbound bandwidth, you could:

(NB: syntax might be off - syntax also for recent IOS versions - assume you can provide missing pieces of CBWFQ)

policy-map aparent

class class-default

shape average 5400000

service-policy achild

policy-map achild

class dept1

bandwidth remaining percent 33

class dept2

bandwidth remaining percent 33

class dept3

bandwidth remaining percent 33

or

policy-map apolicy

class dept1

shape average 30 percent

bandwidth remaining percent 33

class dept2

shape average 30 percent

bandwidth remaining percent 33

class dept3

shape average 30 percent

bandwidth remaining percent 33

interface Ethernet #

service-policy output aparent (or apolicy)

For inbound, if you can't do ISP's egress, you can police/rate-limit your ingress, but seldom works as well as you desire.

Hi,

It's important to know if you are doing Port Address Translation on the 2800 because if it's the case. NAT occurs before Queuing and you loose the real source IP address for the classification.

As a workaround you will need to use qos-group.

HTH

Laurent.

Review Cisco Networking products for a $25 gift card