Traffic-shape configuration issue on gi0/1

[uhmtaeswoo]

Hello, 

I just got task replacement from C3900 to ISR. 

When I check previous c3900 traffic-shape configuration on gigabitinterface0/1, I can not put same commands into ISR. 

So, I tried to find traffic-shape value means on c3900, but there is no traffic-shape commands.

However, the configuration is still on interface gigabitethernet0/1. How did ex-network guy put that into the router? Please advice and How I can do configuration for ISR.  Here are logs. 

Thanks. 

interface GigabitEthernet0/1
bandwidth 10000
ip address 192.168.2.1
ip access-group inet_filter in
ip mtu 1440
ip flow ingress
ip tcp adjust-mss 1272
duplex auto
speed auto
traffic-shape rate 10000000 250000 250000 1000
crypto map crypto-map-asan-MIAP
end

VPN-rtr1(config)#inter gi
VPN-rtr1(config)#inter gigabitEthernet 0/1
VPN-rtr1(config-if)#traffic-sh
VPN-rtr1(config-if)#traffic-sh
VPN-rtr1(config-if)#traffic-sh
VPN-rtr1(config-if)#traffic-sh?
% Unrecognized command
VPN-rtr1(config-if)#

"CISCO3925-CHASSIS", DESCR: "CISCO3925-CHASSIS"

[paul driver]

Hello

You could try class based shaping.

policy-map Traffic-Shape_child
class class-default
fair-queue

policy-map Traffic-Shape_parent
class class-default
shape average 10000000 250000 250000
service-policy Traffic-Shape_child

int x/x
service-policy input Traffic-Shape_parent

[uhmtaeswoo]

Thanks I understood. 

I am still wondering why I can not configure traffic-shape in old router. 

because traffic-shape configuration is still configured on it. 

Anyway,  original traffic-shape is for outbound, isn't it?

Therefore,

int x/x 

service-policy output Traffic-Shape_parent

I guess it is correct..

[Joseph W. Doherty]

Cisco decided since traffic shaping is provided in CBWFQ, and it's Cisco's current QoS framework, they no longer would support the older interface shaping command in later IOS versions. That's likely why it won't accept the command when you try to configure it. As to why it accepts/shows it from a config file, that's a bit surprising, although you might find some message in the syslog. I.e. although you "see" it, it might not actually be functional.