Cisco Cisco IOS Software Release 12.0 S

This feature is supported only on ingress interfaces or subinterfaces of the Cisco 12000 4-port 
Gigabit Ethernet ISE line card. 

Nested policy maps (also known as, hierarchical policy maps) are not supported. 

Do not use the ACL-based rate-limit, continue, and set actions with this feature. 

Percentage-based policing is not supported. 

Only the transmit and drop actions are supported for the rate-limit command. 

Random-detect and police cannot be configured in the same class if rate-limit is also configured 
on the interface. 

The implementation of the police and rate-limit interface configuration commands described in this 
feature are not supported for IPv6. 

Any Transport over MPLS (AToM) is not supported. 

When applied to Service Provider edge and core routers (termed PE and P routers respectively), 
Cisco IOS Modular Quality of Service CLI (MQC) configurations can police and shape service provider 
bandwidth in accordance with service level agreements (SLAs). For installations in which the customer 
edge router(CE) is unmanaged, service providers may choose to classify and police traffic on the ingress 
interfaces of the PE routers. Hierarchical MQC policy maps can ordinarily be configured for these cases, 
but hierarchical policy maps are not supported on the ingress interfaces of the Cisco 12000 4-port 
Gigabit Ethernet ISE line card. 

Beginning with Cisco IOS Release 12.0(30)S1, you can combine the rate-limit interface configuration 
command with a flat policy map to attain the same result as a 2-level hierarchical policy for policing 
ingress interfaces. In addition, the rate-limit command can now be applied to Gigabit Ethernet 
subinterfaces. An example of a 2-level hierarchical policy map is shown in the left column of 

. 

The implementation for the Cisco 12000 4-port Gigabit Ethernet ISE line card is shown in the right 
column.