
afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters.alone - input and output of each session are processed in its own process, most likely the best option when there are a lot of cores and a lot of peers.affinity and output.affinity, they allow control in which process input and output of active session will be processed:

If for any reason you need to tweak or add new instances it can be done in /routing id menu. The default BGP template by default is set to use the "default" ID. RouterOS adds a default ID which picks instance-id from any interface's highest IP. Let's consider a basic example where we want to resolve 8.8.8.8 only in the routing table named myTable to the gateway 172.16.1.1:Īdd name=myAsTemplate as=65500 output.filter-chain=myAsFilterĪnother important aspect of the new routing configuration is the global Router ID, which sets router-id and group peers in one instance. The routing rule configuration is the same except for the menu location (instead of /ip route rule, now it is /routing rule). And fib parameter should be specified if the routing table is intended to push routes to the FIB. The main difference from v6 is that the routing table must be added to the /routing table menu before actually referencing it anywhere in the configuration.


ip routeand /ipv6 route menus are used to add static routes and for simplicity show only basic route attributes.įor more in-depth information on routing see this article ( IP Routing).Īnother new change is that most common route print requests are processed by the routing process which significantly improves the speed compared to v6. From a configuration point of view, the biggest differences are routing table limit increase, routing table monitoring differences, and how routes are added to specific routing tables (see next example) v7 introduces a new menu /routing route, which shows all address family routes as well as all filtered routes with all possible route attributes. By default, all routes are added to the "main" routing table as it was before.
