today we discussed an interesting situation: assume we have a Nexus 7000 equipped with two M- and one F-linecards. Hosts in VLAN 100 and VLAN 200 are connected to the F-linecard only. Now hosts from VLAN 100 need to communicate with hosts in VLAN 200 - and vice versa. So the routing must be done by SVIs for VLAN 100 and VLAN 200 handled on the M-linecards. Which of the two M-linecards is now doing inter-vlan routing?
In short, both cards. Without going into too much detail, the various flows will be load balanced accross each of the M1 line cards, similar in principle to how traffic is load balanced on a port-channel hash.
thanks for your feedback... this means also: since the m-linecards have a 80Gbps fabric-connaction and we are load-balancing accross two of them we would achieve a L3 performance of 160Gbps - right? If yes, does this concept scale higher - something like 4*M = 320 Gbps L3 performance - or x*M = x*80 Gbps L3 performance?
Your understanding is indeed correct, although the load sharing is as important to spread the load over the forwarding engines as it is over the fabric (for scenarios where you have a heavy amount of local switching).
I do not have the functional specification in front of me, but based on the M1 architecture I would expect it to scale to 8 M1 cards. Although keep in mind that these M1 line cards would be shared between all F1 cards, rather than dedicated to specific modules.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.