[AUDIO LOGO]
So now, it's time to join our two domains together with BGP.
And get our environment ready to support traffic engineering,
both tunnels and policies.
So we're going to set up BGP and PCEP in this video.
So we're definitely going to have
to take a look at the diagram this time.
Talk about what we're going to build.
This is going to be involving our route reflector,
different address families that we're
going to be running two different devices.
So let's go ahead and take a look at that topology.
Talk about what it is we're going to be building.
And then, of course, we're going to jump onto the command line,
get this all set up and working, and do some verification.
So we're still on MPLS topology 5,
since we're building on what we've done in previous videos.
Also, note as we jump in here, routers 2, 6, and 8
have been pre-configured just so we
don't have to configure all of the devices.
And routers 3 and 4 don't need any configuration.
So we don't have to configure those either.
But what we are going to be configuring is BGP on route
reflector 1, it's going to be running address family link
state with routers 1, 2, 5, and 6.
And it's going to be running address family IPv4
unicast on routers 7 and 8 to exchange
the routes between the two different domains.
And then of course, we'll also be setting up PCEP.
So let's go ahead and jump in and get started.
We'll start on route reflector 1.
And keep in mind, as we're configuring it,
we should see routers 2, 6, and 8 come up
as we configure the route reflector side.
Because again, those devices are already configured.
So let's go ahead and jump in to the route reflector.
So actually, before we jump right into the route reflector,
let's start on the PE routers and verify that we don't have
any routes to the other domain.
So for example, we'll do a show IP route here for 100.8.8.8.
This is a network that we're going
to make available from the OSPF domain, obviously, on router 8.
And we see that this subnet is currently not in our table.
And if we go to router 8, here, we
do a show IP route for 100.7.7.7.
And this is in the same situation.
So before we start joining these together,
I just want to make sure we understand that as we start,
we have no reachability between domains.
So that said, let's go ahead and start our configuration up
on the route reflector.
So let's begin by creating router BGP.
And we'll just use AS-100.
We'll set our router ID.
This router is effectively acting
like router 11 in our topology.
And then let's activate our address families.
So we need address family, link-state, link-state
and address family IPv4 unicast.
Next, let's set up a neighbor group
for our link-state neighbors just because we're
going to have a few of them.
And it'll simplify the configuration.
This is, of course, optional.
We could just configure the neighbors individually.
But again, this simplifies the configuration
just a little bit.
So we'll create our neighbor group.
We'll call it ls_peers.
And the things we want to configure in here.
Let's configure the remote AS to be 100.
We're just going to use iBGP.
We'll set our update source to be loopback zero.
And we'll activate the address family, link-state, link-state.
So next, let's configure our neighbors.
So we'll say neighbor 10.1.1.1.
And tell it to use the neighbor group ls_peers.
We'll do the same thing for neighbor two, neighbor five,
and neighbor six.
Next, let's configure our IPv4 neighbors.
So that's going to be routers 7 and 8.
We could, of course, use a neighbor group for those
as well.
But this is going to be a simpler configuration.
So we'll just go right into neighbor 10.7.7.7.
And here, we'll simply say that it's a remote AS-100.
The update source is loopback zero.
And the address family is IPv4 unicast.
Then under the address family, we
do want to set these up to be route reflector clients.
So next, we'll do the same thing, but for router 8.
That should be everything.
So let's commit our changes.
So we see here, we're getting a failure to commit.
And if we do a show config failed,
it's telling us that neighbor 10.8.8.8 is not a neighbor.
It says, we have no remote AS defined.
So let's scroll up here just a minute.
And what we see is that, yes, in fact,
when we typed neighbor 10.8.8.8, we
went right to update source loopback zero, right
into the address family, and configured the route reflector
client.
But we missed putting in the remote AS.
So let's go ahead and correct that.
And let's try our commit again.
So that's looking a lot better.
It took the commit.
And we see some of those neighbors starting to come up.
We said that routers 2, 6, and 8 are already pre-configured.
And we see that all of those have come up.
So this looks like a good configuration
now on the route reflector.
Let's go ahead and move on then to router 1.
So router 1 is going to be running the link-state address
family.
And we need to get the link-state information
from ISIS into BGP.
So let's configure that first.
To do that, we simply go into router ISIS 1.
And we tell it to distribute its information
into BGP link-state.
That's all we should have to do on the ISIS side.
So now, let's go into router BGP 100.
We'll set our BGP router ID and configure our address family.
Again, the only one we need is link-state, link-state.
Next, let's configure our neighbor.
This is going to be the route reflector, which
is 10.11.11.11.
Let's not forget our remote AS this time.
So remote AS-100.
We'll set our update source.
And we'll activate that address family for this neighbor.
That should be it.
Let's commit our changes.
Exit configuration.
And here, we see that neighbor 11 has come up.
So far this is looking good.
Let's go configure router 5 next.
Now, remember router 5 is running OSPF.
So for this one, we have to go into router OSPF 1
and say distribute link-state.
So slightly different command, but the same idea.
We need to take the OSPF link-state information
and send it into BGP.
Now, we'll configure our router BGP 100.
Of course, set our router ID.
Now, since we don't need it, we can turn off the IPv4 address
family.
This is, of course, optional.
You don't have to do this.
But we can say no BGP, default IPv4 unicast.
That just turns off the default IPv4 unicast address family,
since we're not going to be using it here on router 5.
Then we'll configure our neighbor 10.11.11.11.
And we'll do that remote AS-100.
We'll set the update source to our loopback zero.
Then we'll go into the address family, link-state, link-state.
And we'll activate this neighborship for that address
family.
We see here that our neighbor 10.11.11.11 has come up.
So once again, this is looking pretty good.
Let's go ahead and verify this information
on each of our routers to make sure everything's
up and running.
We'll just start on router 1, so that we're
going in a logical order.
So the command we're going to use for verification
is show BGP link-state, link-state summary.
And what we're looking for is each of these devices
should be up with the route reflector.
We can see here that router 1 is up.
If we look at router 2, router 2 is also up.
Router 5 also up.
And finally, router 6.
We see router 6 is up as well.
It also wouldn't hurt to verify on the route reflector,
just so we can see what that looks like.
Of course, we know if one side's up,
the other side's up as well.
But just to see what the command looks like,
we see that here on the route reflector.
It has neighborships for the link-state address
family to routers 1, 2, 5, and 6, which is
exactly what we're looking for.
We can also see that it's already
received some prefixes from each of these devices as well.
We'll get to that in a little bit.
Now, what we haven't done yet is configure our address family
IPv4 on router 7.
So let's go configure router 7 to just be
a standard IPv4 client for BGP.
So again, we'll do router BGP 100.
We'll set our router ID.
We'll configure our neighbor.
So we put in the remote AS.
And we'll say, update source loopback zero.
We can see that neighborship already came up.
So is the update source loopback zero strictly necessary?
No, but that's a whole other conversation.
So let's just put it in for good measure,
even though we see the neighborship was already up.
So let's go ahead and exit configuration.
So now that we have BGP up and running,
where we need it with the correct address families.
So we have link-state address family running
towards routers 1, 2, 5, and 6.
And we have IPv4 address family running with routers 7 and 8.
Now, let's go ahead and configure PCEP.
Once again, we'll start on the route reflector,
since that's going to be the PCE.
So this is actually a very simple configuration.
All we do is type PCE to go into PCE configuration.
Tell it what address to actually run on.
We want it to run on its loopback interface.
So it's going to be 10.11.11.11.
And simply commit the changes.
Now, we can do a show PCE IPv4 peers or rather peer.
And we can see that as of right now,
there are no neighborships, which, of course, makes sense.
We haven't configured the other routers yet.
So the PE routers are going to be the PCCs.
So let's go over and configure router 7.
So our first command is going to be MPLS traffic engineering
PCC to tell it it's a client.
And then tell it its peer or its server, if you will,
is 10.11.11.11.
Then we have to tell it what to report.
So we'll say MPLS traffic engineering PCC report all.
We'll exit our configuration.
And let's take a look at some show commands.
Let's do a show PCE client peer.
We see that as of right now, our peer 10.11.11.11
is currently up.
So this looks good.
If we wanted some more detail, you can simply
add detail to the end of this.
As you can see, this takes a moment.
But it'll give us a lot more information about that server.
So again, we see our peer address,
that it's chosen it as the best PCE.
It is currently up.
Of course, we see how long it's been up for.
And again, a bunch of statistics as far as peer keepalives.
And statistics as far as types of messages
that have been sent and received.
Show PCE client LSP is another good command to look at.
Although, as of right now, we don't have any LSPs or label
switch paths up and running.
So we'll review this, again, once we've
done some policies and tunnels.
So next up would be to configure router 8.
Router 8 is the same configuration.
So we'll just paste it in.
And of course, we see the console message
that the server came up.
But let's verify it anyway.
We'll just do a show PCE client peer.
And yes, we see the 10.11.11.11 is, in fact, up.
Of course, we can also do verification
from the route reflector or the PCE.
So let's start with a show PCE peer, which is actually
show PCE IPv4 peer.
And what we see is that our two neighbors, router 7 and 8
are, in fact, both up.
Let's do a show PCE IPv4 topology.
And let's start with a summary.
Here, we see all the information it's learned about the summary
so far.
How many nodes are in the topologies, prefixes.
We can see all of this information
that it's learning about our environment.
Rather than summary, we could also ask for a particular node.
And notice, it's learning all of the traffic engineering
information about each of these nodes.
Importantly, it's learning things
like the metric, the TE values, the latency, the bandwidth,
reservable and so on.
All of that critical information for traffic engineering.
We should be getting this from router 8 as well.
We can see here that we are.
And we should be getting it from the other routers
as well because the router is in the middle also
need to report information.
And we can see that we're getting information
about node 10.2.2.2 as well.
So we should have information about all the devices
in our topology.
And as we can see, we do.
So this is working as it should.
In this video, we set up BGP link-state address family
between routers 1, 2, 5, and 6 and our route reflector.
And we set up BGP for address family IPv4
between our PE devices, routers 7 and 8.
Then we set up PCEP between the route reflector and our PEs,
again, router 7 and 8, to exchange the traffic
engineering information with the route reflector acting
as the PCE.
Now, all of this working doesn't do us any good,
unless we actually build traffic engineering policies
and tunnels.
And that's right.
That's what we're going to do next.
Until then, I hope this has been informative for you.
And I'd like to thank you for viewing.