On 12/21/2015 5:26 PM, Andrew Qu wrote:
[Andrew] I thought the routing tables will be eventually populated to
forwarding engine which is mostly done by HW (NPU/FPGA/ASICs) in
most networks.
We have Linux/Quagga routers running OSPF, and as I mentioned above we
want to be able to route different classes (protocols, ports, dscp) of
traffic differently. This should happen on all routers in the
network. This depends on the ability of OSPF to build different spf
trees based on different metrics for each link.
[Andrew] my question was not clear. developing MTR in OSPF as control
plane is a partial solution to the end user, network forwarding
engines in any form must forward the packet
according the MTR table which is different than plain (vpn, ip/prefix)
FIB table. my question is really that how the entire network is
designed to carry out MTR forwarding when each router
build up MTR tables.
Thanks for clarifying. Linux kernel is the forwarding engine in our
case, so it is all software routers. All routers run the same software
so they all have a "consistent" view of the network and they all should
support MTR. Of course MTR-OSPF covers interactions and route exchange
between MTR and non-MTR routers so we should be able to handle that case.
--Jafar
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
