Now you can monitor the status of all connected and disconnected peers from /routing bgp session menu. Peer role is now a mandatory parameter, for basic setups, you can just use ibgp, ebgp. It is possible that in setups where peer uses the multi-hop connection local.address must be configured too. Most of the parameters are similar to the previous implementation except that some are grouped in the output and input section making the config more readable and easier to understand whether the option is applied on input or output.īGP connection minimal set of parameters are remote.address, template, connect, listen and local.role Connect and listen to parameters specify whether peers will try to connect and listen to a remote address or just connect or just listen.

It can be used as a template for dynamic peers and apply a similar config to a group of peers. Template contains all BGP protocol-related configuration options. v7 BGP implementation provides with connection, templateand session menus. But keep in mind that there is a complete redesign of the configuration. To re-trigger v6 configuration conversion, load ROSv6 backup with the option force-v6-to-v7-configuration-upgrade=yes.Īll known configurations will upgrade from 6.x to 7.x successfully. This means that if a router was downgraded to ROSv6, the configuration was modified and the router got upgraded back to ROSv7, then the resulting configuration is the one that was present before the downgrade. The routing protocol configuration upgrade is triggered only once.

Routerboard upgrade