In order to configure BGP over SVR, you first need to configure a Routing Interface. This is similar to a loopback interface that you might find on most other non-128T routers. Configuring the routing interface triggers your conductor to autogenerate tenants, services, and service routes that enable the BGP over SVR to work.

You will find Routing Interface under Routing Instances. All you need to do is give it a name, something that is meaningful to you, and then give it an IP address. The IP address can be any unique address. Unlike normal loopback BGP peering, this IP address does not need to be routable on the transport network as these IP addresses will never see the wire.

BGP Instance

Next you just configure a BGP instance with the router’s local AS and a router id which matches the routing interface IP. For each BGP over SVR peer, you will use the neighbor address of the neighbor routing interface IP address. You set your normal BGP peer configuration options such as timer and address families that are needed. Lastly, you need to make sure you set next-hop-self to true. You’ll find that under the IPv4-unicast address address-family under the BGP peer.

Now you just need to do the same thing on your 128T peer. After you complete configuring your 128Ts, Validate and Commit your configuration. Now, in order to get BGP over SVR to work, the 128T will automatically configure some services, service-routes, and tenants for you. Just look at your config for anything that starts with _bgp.

To prove it is working, issue the command:

show bgp​