Shaping is designed to work Outbound on an interface, not inbound.
If you want to limit traffic in both directions on an interface you need to look at policing.
The information above does not include the details on the Access List called 'ACL_RateLimit_512KB'
If you wanted to create a Policy which policed an interface down to 512Kb for a specific subnet of 192.168.1.0 /24, you would first create the access list:
ip access-list extended ACL_RateLimit_512KB
permit ip any 192.168.1.0 0.0.0.255
permit ip 192.168.1.0 0.0.0.255 any
Bear in mind, you need to ensure you have both lines above because we need to match on both the source address (for outbound packets) and the destination address (for inbound packets).,
You then create your class maps:
class-map match-any CLASS_EgressLimit_512KB
match access-group name ACL_RateLimit_512KB
class-map match-any CLASS_IngressLimit_512KB
match access-group name ACL_RateLimit_512KB
We are referencing the same access list for both class maps but this is not an issue really.
Then we create our policy maps:
policy-map POLICY_EgressLimit_512KB
class CLASS_EgressLimit_512KB
police 512000
policy-map POLICY_IngressLimit_512KB
class CLASS_IngressLimit_512KB
police 512000
Then we apply the policing both inbound and outbound on the interface:
interface gi0/6
service-policy output POLICY_EgressLimit_512KB
service-policy inbound POLICY_IngressLimit_512KB
Bear in mind that Policing is fairly brutal, it will not queue packets like shaping does, it will just drop them if they do not conform.
As you are doing this on a switch (as opposed to a Router), there is a chance that the commands above may not work.
Hope this helps!
