Qos bandwidth percent (ZT)

To be able to verify the potential differences between 12.2 and 12.3 I
upgraded one of my routers to 12.3(6) mainline:

R3#sh ver
Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3640-IS-M), Version 12.3(6), RELEASE SOFTWARE(fc3)<snip>

I subsequently configured a service policy on a regular ethernet
interface and started assigning bandwidth percentages to some classes:

R3(config)#policy-map TEST
R3(config-pmap)#exit
R3(config)#int e 0/0
R3(config-if)#service-policy output TEST
R3(config-if)#exit
R3(config)#class-map CLASS-1
R3(config-cmap)#match access-group 1
R3(config-cmap)#class-map CLASS-2
R3(config-cmap)#match access-group 2
R3(config-cmap)#class-map CLASS-3
R3(config-cmap)#match access-group 3
R3(config-cmap)#class-map CLASS-4
R3(config-cmap)#match access-group 4
R3(config-cmap)#policy-map TEST
R3(config-pmap)#class CLASS-1
R3(config-pmap-c)#bandwidth ?
<8-2000000> Kilo Bits per second
percent % of total Bandwidth
remaining % of the remaining bandwidth

R3(config-pmap-c)#bandwidth percent 50
R3(config-pmap-c)#class CLASS-2
R3(config-pmap-c)#bandwidth percent 15
R3(config-pmap-c)#class CLASS-3
R3(config-pmap-c)#bandwidth percent 10
R3(config-pmap-c)#class CLASS-4
R3(config-pmap-c)#bandwidth percent 10
I/f Ethernet0/0 class CLASS-4 requested bandwidth 10%, available only
0%
R3(config-pmap-c)#^Z
R3#

As you can see the router now prevents me from assigning more than 75%
in total because the percentage now refers to the TOTAL bandwidth, not
the available bandwidth.

You can also see that very clearly from the show commands:

R3#sh policy-map int e 0/0
Ethernet0/0

Service-policy output: TEST

Class-map: CLASS-1 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group 1
Queueing
Output Queue: Conversation 265
Bandwidth 50 (%)
Bandwidth 5000 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0

Class-map: CLASS-2 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group 2
Queueing
Output Queue: Conversation 266
Bandwidth 15 (%)
Bandwidth 1500 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0

Class-map: CLASS-3 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group 3
Queueing
Output Queue: Conversation 267
Bandwidth 10 (%)
Bandwidth 1000 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0

Class-map: CLASS-4 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps
Match: access-group 4

Class-map: class-default (match-any)
71 packets, 6750 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
R3#

It simply states that 15% equals 1500 kbps, since on this IOS version
the bandwidth percentage refers to the TOTAL bandwidth, while the new
command 'bandwidth remaining percent' is relative to the AVAILABLE
bandwidth.

So I guess that there is actually a difference in the operation of the
'bandwidth percent' command depending on the IOS version.