Matthew Stone encountered another unintended consequence of full Internet routing in a VRF design: the TCAM on his 6500 was 80% utilized even though he has the new Sup modules with one million IPv4 routes.
A closer look revealed the first clue: L3 forwarding resources on a Cat6500 are shared between IPv4 routes and MPLS labels (don’t know about you, but I was not aware of that) and half the entries were consumed by MPLS labels:
Read more ...Thanks for reading my news about Internet-in-a-VRF and LFIB explosion at my blog Bros Droid if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.
More Articles :
VMware NSX Architecture Videos Published- The Intricacies of Optimal Layer-3 Forwarding
- Flow Table Explosion with OpenFlow 1.0 (And Why We Need OpenFlow 1.3)
- IPv6-Only Data Centers: Deployment Guidelines
- SIIT – The Magic Behind IPv6-only Data Center
- Overlay Virtual Networks 101
- Forwarding Models in OpenFlow Networks
- ATAoE Is Alive and Well
- TTL in Overlay Virtual Networks
- Configure physical firewalls based on VM groups? Sure, use DSE from Plexxi