Traffic bound to the CPU that is received on VPRN access interfaces is policed/rate-limited and is added to the CPU queues. The software allocates a policer per IP application, or a set of IP applications, for rate-limiting CPU bound IP traffic from all VPRN SAPs. The policer CIR/PIR values are set to appropriate values based on feature scaling. CIR/PIR values are not user configurable. The policers are shared by the IP application/set of IP applications traffic received on all access SAPs across all services. Queues for CPU bound IP traffic from all VPRN SAPs are software allocated. The queues are either shared by a set of IP applications or allocated to a single IP application across all services and routing instances. The queues are shaped to an appropriate rate based on feature scaling. The shaper rate is not user configurable. The queues and shaper rate are shared by traffic of the IP application/set of IP applications received on all access SAPs. The queue instances and policers used for traffic received on network port IP interfaces are different for traffic received from access port IP interfaces. Also, the network CPU queues are given higher priority than the access CPU queues. This provides better security and mitigates the risk of access traffic affecting the network side.
The instance of queues and policers used for traffic received on network port IP interfaces is different from the ones used for traffic received from access port IP interfaces. Additionally, the network CPU queues are prioritized over access CPU queues to provide better security and mitigate the risk of access traffic affecting the network side.
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, the IP DSCP value for self-generated traffic is user-configurable.
On the 7210 SAS-D and 7210 SAS-K 2F1C2T, IP DSCP marking of self-generated traffic is not user-configurable and is assigned by the software.