[AUDIO LOGO]
Now that we have our customer VRFs configured,
it's time to set up and configure multi-protocol BGP
in our core network between our route reflector and our PE
routers.
Much like we did with the VRFs, we'll
go ahead and configure this to support
IPv4 and IPv6 at the same time.
And we'll go ahead and use some peer templates and such
to make this a little bit easier to configure as we go.
So as per usual, let's take a look at our topology diagram,
draw out what we're going to be building, and then
jump into the command line and get multi-protocol BGP up
and running.
So what we're going to be configuring
in this part of our demonstration,
we're going to be configuring multi-protocol BGP
neighborships between router 1, router 2, router
5, and the route reflector.
So our logical IBGP neighborships
will look like our orange lines here.
So let's go ahead and jump into the command line.
This time, we'll start on router reflector 1.
So let's begin by configuring BGP.
We have to create the actual instance,
so we'll do router bgp 100.
We'll set our bgp router-id.
The route reflector is essentially
acting as router 12 in our environment,
so we'll set the router ID to 10.12.12.12, which is also
its loopback interface that we're going
to be using for our peering.
Now something else we can do to optimize our environment here,
we can actually disable the default IPv4 address
family on iOS XE.
We don't need to form a BGP neighborship for IPv4, just
for VPNv4 and VPNv6.
Now this step isn't entirely necessary,
but if we're not going to be doing
regular IPv4 routes in our core, then there's
really no need for that extra neighborship.
So let's go ahead and just turn that off.
It's simply no bgp default ipv4.
Now the next thing we want to do is create some peer templates.
So the first thing we'll do is we'll create
a template for our peer-policy.
And we'll just call this PP_PE for Peer-Policy
towards our Provider Edge routers.
What things do we need to say towards the PEs?
Well, one thing we're going to need
is to say that they're route-reflector-clients,
since this is the route reflector.
The other thing we have to do is configure this
to send communities.
We'll go ahead and configure it to send both communities,
extended and standard, even though we only really need
extended to support our layer 3 VPNs.
The next thing we're going to need
is a peer-session template.
We'll call this PS_PE for Peer-Session
to the Provider Edges.
Things we want to configure in here
is that they are in remote-as 100.
And we'll set the update-source to lo0.
So this should take care of our peer templates,
both for the policy and for the session.
Now all we have to do is configure
our neighbors to actually use these templates.
So we'll start with nei 10.1.1.1, which is router 1.
And we will tell it to inherit peer-session PS_PE.
We have to repeat the same thing for router 2 and router 5.
Next, we'll go into our address-family, specifically
for vpnv4.
First thing we have to do is activate our neighbors
and tell it to inherit our peer-policy.
We'll do both of these commands for all of the other routers,
so router 2 and router 5.
Now we want to configure this for IPv6 as well.
But a real easy way to do that is if we say do sho run.
And look for the section for BGP.
What we're going to do is we're going
to say address-family vpnv6.
And we're going to copy and paste
this configuration because it's going to be the same.
But before we do that, I also want
to point out that notice that iOS XE went ahead and added
that send-community extended on each of our neighbor statements
for 1, 2, and 5.
So I still like to put it in the peer-template
just so it's there.
But notice that iOS does take care
of the send-community for us.
Now what we want to do is copy and paste all of this
into the VPNv6 section.
So we'll simply highlight all of that configuration
and simply paste it in.
We'll do our sho run s bgp again.
And we'll just make sure that all of that information
went under VPNv6 as well as VPNv4
so we can see that it's correct.
We'll go ahead and exit configuration
on the route reflector.
And now let's go ahead and configure the clients.
So here on router 1, again, router bgp 100.
We'll set our BGP router ID.
We'll activate our two address families.
Then we'll configure our neighbor, which is 10.12.12.12.
And for that neighbor, we'll set the remote-as to 100,
set the update-source to our lo0 interface,
and activate the address families
for these individual neighbors.
We'll commit those changes and exit configuration.
We can also see here that neighbor 10.12.12.12
has come up.
Now router 2's configuration is going
to be almost identical except, of course,
for the BGP router ID, so we'll just
go ahead and copy and paste.
So we have the configuration paste in.
And once again, we see that router 12 has come up.
Finally, let's configure router 5.
At this point, we've configured BGP on iOS XE
quite a few times.
So although this is specific here,
I think if we just paste the configuration in,
we can just talk about what we've configured.
So we'll paste in the configuration.
So as we can see, the neighbor has come up here.
And as far as the configuration, it's
a fairly standard BGP configuration.
We did turn off that default address family for iOS XE.
And then, of course, we set up our neighbor
10.12.12.12 with the remote-as, the update-source.
And then, of course, we activated it
and said send-community both under both the VPNv4
and the VPNv6 address families.
So this all looks really good.
Let's do our verification up on the route reflector
because it should see all the neighbors.
So on the route reflector here, we'll simply
do a sh bgp vpnv4 uni all summ.
And we can see that we do, in fact, have neighbors 1, 2,
and 5 currently up in AS 100.
Now, again, we haven't sent any prefixes yet,
so under the state prefix received field, of course,
it's zeros, but this does indicate that our neighborships
are up and working for VPNv4.
We can do the exact same command simply change this v6.
And we can see that those neighbors are ready to exchange
address family VPNv6 as well.
So that takes care of configuring multi-protocol BGP
in our core.
So in this video, we simply saw how
to configure multi-protocol BGP in our core
to support Layer 3 VPN.
We set up support for both VPNv4 and VPNv6 addressing.
We see it was really just the exact same config,
just change which address family we're putting
the configuration under.
We also saw how to use our route reflector
and how we can simplify the configuration there
by using some peer templates.
Now we're ready to set up our CE-PE protocol
so we can actually start getting some routes from the customers
to pass through to the other side.
And that's exactly what we get to do next.
Until then, I hope this has been informative for you,
and I'd like to thank you for viewing.