ASR 1001-x throughput

[satish.txt1]

ASR 1001-x comes with 2.5 default throughput, We are planning to terminate 10G link on ASR1001-x but we have legit traffic only 1G but sometime we getting 5GB around DDoS so if i use ACL to drop that bad traffic on ingress interface in that case how does 2.5G restricted throughput will affect me? 

Does cisco restrict throughput based on ingress traffic or egress traffic? 

[Reza Sharifi]

2.5 is the total throughput of the box which includes ingress and egress interfaces.

HTH

[satish.txt1]

This is what i found. Doesn't it saying it apply only to egress?

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

My understanding has been ASRs bandwidth limit apply to bandwidth crossing the backplane, but counting the aggregate of egress is about the same.  In either case, I would think bandwidth blocked by an interface ingress filter shouldn't count.

[satish.txt1]

You mean say, in my case i don't need to buy $20k license to get 10GE throughput because my requirement is all about dropping bad traffic at ingress interface while we under attack, and legit traffic is around 1Gbps only (egress). 

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

Correct, as that's how I understand it should work.