本文发表在 rolia.net 枫下论坛picking a proprietary protocol or not depends on what kind of boxes are running on your network, most of enterprise network nowadays consists 80% of cisco equipment . then why not running eigrp on these networks?
running eigrp can't expend network anymore? are you trying to be funny or just pure ignorance? if you trying to say MPLS requires link state protocol for path calculation, then let me ask you how many enterprise networks are running MPLS on their Core network? on backbone, yes. but very rarely on the core. althrough if it's running on the backbone, in most case it's handled by ISP, you can't really do much on your CE router.
"I guess cisco itself might have stopped develop eigrp". not sure what kind of crack you were smoking when you said that. as cisco's dominance of the market for enterprise networks, in what mind would cisco stop developing eigrp? perhaps you should take look at the new features have been added into eigrp. let me just name a few here, so you won't be as arrogant and ignorant. have you heard of neighbor startup enhancements? bidirectional forwarding detection? graceful shutdown? non-stop forwarding? in my opinion, non-stop forwarding is a great implementation for any network that consists cisco equipment.
i'm not saying eigrp is the greatest protocol in the world, but it has it's advantages. for instance, when comparing convergence speed between eigrp and link state protocols, eigrp is way on the top of the game if every path had the feasible successors. even for ospf and isis with tuned timers, their convergence speed are still slower.
okay, that's it for now, if you want more, i can bring it on as long as you like it.更多精彩文章及讨论,请光临枫下论坛 rolia.net
running eigrp can't expend network anymore? are you trying to be funny or just pure ignorance? if you trying to say MPLS requires link state protocol for path calculation, then let me ask you how many enterprise networks are running MPLS on their Core network? on backbone, yes. but very rarely on the core. althrough if it's running on the backbone, in most case it's handled by ISP, you can't really do much on your CE router.
"I guess cisco itself might have stopped develop eigrp". not sure what kind of crack you were smoking when you said that. as cisco's dominance of the market for enterprise networks, in what mind would cisco stop developing eigrp? perhaps you should take look at the new features have been added into eigrp. let me just name a few here, so you won't be as arrogant and ignorant. have you heard of neighbor startup enhancements? bidirectional forwarding detection? graceful shutdown? non-stop forwarding? in my opinion, non-stop forwarding is a great implementation for any network that consists cisco equipment.
i'm not saying eigrp is the greatest protocol in the world, but it has it's advantages. for instance, when comparing convergence speed between eigrp and link state protocols, eigrp is way on the top of the game if every path had the feasible successors. even for ospf and isis with tuned timers, their convergence speed are still slower.
okay, that's it for now, if you want more, i can bring it on as long as you like it.更多精彩文章及讨论,请光临枫下论坛 rolia.net