Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1331
Views
5
Helpful
5
Replies

option Bandwith in interface Tunnel for QoS

Go to solution
georgd
Level 1
Level 1

‎06-15-2010 04:03 AM - edited ‎03-04-2019 08:46 AM

Config in Cisco3845 IOS c3845-advipservicesk9-mz.124-24.T2.bin:

policy-map child
class TOS1
    bandwidth percent 45
policy-map parent
class class-default
    shape average 2000000
  service-policy child

interface Tunnel1201
bandwidth 300
tunnel bandwidth transmit 270
tunnel bandwidth receive 270
service-policy output parent

....

interface Tunnel1201
bandwidth 2000
tunnel bandwidth transmit 2000
tunnel bandwidth receive 2000
service-policy output parent

....

show policy-map interface tu 1201

Tunnel1201

  Service-policy output: parent

    Class-map: class-default (match-any)
      233 packets, 103581 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 233/32154
      shape (average) cir 1000000, bc 4000, be 4000
      target shape rate 1000000

      Service-policy : child

        Class-map: TOS1 (match-all)
          0 packets, 0 bytes
          5 minute offered rate 0 bps, drop rate 0 bps
          Match:  precedence 1
          Queueing
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 0/0
          bandwidth 45% (540 kbps)

sh policy-map interface tu 1202
Tunnel1202

  Service-policy output: parent

    Class-map: class-default (match-any)
      264 packets, 122815 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 264/36432
      shape (average) cir 1000000, bc 4000, be 4000
      target shape rate 1000000

      Service-policy : child

        Class-map: TOS1 (match-all)
          0 packets, 0 bytes
          5 minute offered rate 0 bps, drop rate 0 bps
          Match:  precedence 1
          Queueing
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 0/0
          bandwidth 45% (540 kbps)

Qwestion:

Why the same bandwith (540 kbps) on both interfaces?

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
belovell
Level 1
Level 1

‎06-15-2010 06:37 AM

The bandwidth statement in your QoS config is a percentage of the shaper in your parent class not the "bandwidth xxxx" on the interface. So it will be the same on both interfaces. This is really how it should be as the "bandwidth xxxx" statement on the interface has no bearing on QoS or traffic. It just changes the EIGRP bandwidth metric for the tunnel.

-Ben

View solution in original post

0 Helpful
5 Replies 5

Go to solution
belovell
Level 1
Level 1

‎06-15-2010 06:37 AM

The bandwidth statement in your QoS config is a percentage of the shaper in your parent class not the "bandwidth xxxx" on the interface. So it will be the same on both interfaces. This is really how it should be as the "bandwidth xxxx" statement on the interface has no bearing on QoS or traffic. It just changes the EIGRP bandwidth metric for the tunnel.

-Ben

0 Helpful

Go to solution
georgd
Level 1
Level 1
In response to belovell

‎06-15-2010 10:04 PM

policy-map child
class TOS1
    bandwidth percent 45

policy-map parent-2
class class-default
    shape average 3000000
  service-policy child

interface Tunnel1201
bandwidth 2000
tunnel bandwidth transmit 2000
tunnel bandwidth receive 2000
qos pre-classify
tunnel mode ipsec ipv4
tunnel protection ipsec profile AES
service-policy output parent-2
...

sh policy-map interface tu 1201
Tunnel1201

  Service-policy output: parent-2

    Class-map: class-default (match-any)
      3 packets, 527 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 3/414
      shape (average) cir 3000000, bc 12000, be 12000
      target shape rate 3000000

      Service-policy : child

        Class-map: TOS1 (match-all)
          0 packets, 0 bytes
          5 minute offered rate 0 bps, drop rate 0 bps
          Match:  precedence 1
          Queueing
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 0/0
          bandwidth 45% (540 kbps)

bandwith 45%=540kbps

bandwith 100%=540/45*100=1200kbps

the "shape" command has no effect, if shape > 1200kbps.

tunnel source gigabitEthernet 0/0.20

0 Helpful

Go to solution
georgd
Level 1
Level 1
In response to georgd

‎06-17-2010 06:22 AM

It's bug or feature.

On IOS 124-9.T this is not!

0 Helpful

Go to solution
belovell
Level 1
Level 1
In response to georgd

‎06-17-2010 02:42 PM 

georgd@hotmail.ru
It's bug or feature.
On IOS 124-9.T this is not!

I'm not sure I completely understand this. What version are you trying this on?

bandwidth 45% (540 kbps) <--- this does seem wrong as your shape rate has increased.

Did you edit the policy in place? Have you tried removing and re-adding the policy-map?

-Ben

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card