[f-nsp] MLXe XMR Outbound Route Optimization (AKA Cisco OER/pfr)
Fabio Mendes
fabio.mendes at bsd.com.br
Sat Feb 4 12:31:21 EST 2012
PfR goes beyond congestion.
QoS configs are static and they denpend on the path chosen by the routing
protocol. If the path has a considereable delay, as long as adjacencies are
not affected, no routing protocol will reroute part of traffic (eg VoIP
traffic) to a different path automagically.
PfR offers the abillity to pick a diferent path to diferent
traffic/traffics if the one chosen by the routing protocol goes out of the
policy.
I'm no Cisco pimp, in fact, I've been working with Foundry/Brocade products
for quite a time but I must recognize that they don't have this kind of
inovation.
When it comes about features and inovation Cisco, is centuries ahead.
2012/2/4 George B. <georgeb at gmail.com>
> My personal feeling is that if you are resorting to such gymnastics to
> avoid congestion, then there might be problems at layer 8 in the
> organization and you are really just routing around that.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20120204/59cf08fb/attachment.html>
More information about the foundry-nsp
mailing list