[AUDIO LOGO]
So, so far, we have enabled MPLS traffic engineering
on our core interfaces.
We've enabled RSVP on those same interfaces
and configured what we want to reserve for bandwidth,
both total and per flow.
So our next step is going to be to configure
the IGP to actually support MPLS TE extensions.
So let's go ahead and jump in.
We'll take a look real quickly, of course, at our topology just
to remember which routers we're working with here.
And then we'll jump into the command line
and get this operational.
So once again, we are still on MPLS topology 1.
Now for this video, we're going to have
to focus on something a little bit different
since we're talking about the IGP.
So in this environment, we are actually running OSPF.
And specifically since we usually configure this by area,
we're going to have to be aware that our underlying IGP is OSPF
and everything is in area 0.
So again, we'll be configuring all of our routers.
So we have to configure router 1, router 2, router 3, router
4, and router 5 for OSPF to support traffic engineering
extensions.
Now we actually don't have any IS-IS in this environment
right now.
But at the end, we will bring up a slide with the configuration
that we would use for IS-IS.
So we'll see that configuration as well.
But we'll actually be configuring OSPF.
So that said, let's go ahead and jump over to the command line,
and we'll just go ahead and start on router 1.
So let's start simply by going into configuration mode,
into our router OSPF process, and then we
simply say mpls traffic engineering
and configure our router ID to loopback 0.
This can technically be different from the normal OSPF
router ID.
But generally, you would want to make it the same.
Then as we mentioned, we're going
to configure this per area.
So we'll go into area 0 and simply
turn on mpls traffic-engineering.
We'll commit the changes, exit configuration mode.
And we can verify this with a show ospf
mpls traffic-engineering link.
And what do we see here?
We see that area 0 has two MPLS TE links.
Those are, of course, the two interfaces
that we have enabled in the area,
as well as being traffic engineering enabled.
We can see that it gives us the interface address.
We see the admin metric for TE is set to 1.
And, of course, various other information
here, such as the affinity bit is currently set to zero.
So lots of information that we can get out of this command.
Let's go ahead and configure router 2.
This is going to be essentially the same configuration.
So go ahead and put in all that configuration.
And again, we'll verify it.
Once again, we see that we have two MPLS TE links in area 0.
So that brought in both of our interfaces here.
Next, let's do router 3.
Now we see here on router 3 that this of course,
includes four links because it has four interfaces.
And let's wrap up our IOS XR with router 4.
Again this configuration is almost identical.
So we'll just go ahead and paste this configuration.
And then we'll verify it.
And again, just like router 3, router 4
has four MPLS TE links.
So, so far, this is looking good.
Now let's configure IOS XE on router 5.
So once again, of course, configuration
mode, router ospf 1.
Here it's going to be mpls traffic-eng.
And again, we'll set it to loopback 0.
We essentially repeat the same command,
but enable it for the area as well.
So again, slightly different configuration here
on IOS XE, but the same basic process.
We're setting the router ID and enabling traffic engineering
for the area.
Let's go ahead and exit out of this
and verify the links here as well.
So we'll say show ip ospf mpls traffic engineering link.
And here, of course, we see that we have those two links enabled
for MPLS TE.
Now that we have this configured,
why don't we take a look at Wireshark
and look at a packet capture of these OSPF packets
exchanging the traffic engineering information?
So what we've captured here on Wireshark
is the actual OSPF neighborship coming up
between router 1 and router 3.
We're filtering this by OSPF.
And what we're going to do is we're
going to focus on packet 71 here going from router 1
to the OSPF multicast address.
If we look at our decoding window,
we can see that under open shortest Path first,
this is an LSA update packet.
And we see that it's LSA type 10, it's an opaque LSA.
Let's open that and see more detail.
So what we're looking for here specifically
is it's a link state ID opaque type traffic engineering LSA.
We can also see down here at the bottom
that the MPLS traffic engineering LSA
has more of a breakdown to it.
We can open that up.
And what we see here is all of this information related
to traffic engineering, including things
like the interface IP address.
Once again, we see that traffic engineering metric.
We see the maximum bandwidth available,
the maximum reservable bandwidth available.
So, of course, the maximum bandwidth
is the interface itself.
And then, of course, the maximum reservable bandwidth we can see
is that two megs that we configured on our devices.
So we can see all of this information being
exchanged in OSPF LSAs between our MPLS TE enabled neighbors.
So let's go ahead and jump back over to the command line.
So that's really all there is to configuring MPLS TE support
under OSPF as our IGP.
Now as I mentioned earlier, since we
don't have IS-IS running in this particular environment,
let's go ahead and at least look at the commands that
would be needed to enable IS-IS if that were our core protocol.
So first, let's take a look at our IOS XR configuration.
So, of course, just like before the first thing we do
is go into our IS-IS process.
We configure our net number if this is not already configured
on our device.
This is required in order to do traffic engineering.
So if it's not configured, we are
going to have to configure it.
Then, of course, we go into our address family,
either IPv4 four or IPv6, we're just
showing the IPv4 example here.
And three things we really need to do.
First, we need to turn on metrics style wide.
This is needed in order to support traffic engineering.
It's needed to support IPv6.
It's actually needed for a lot of things.
So really you want metrics style wide on with IS-IS in, well,
every scenario that I can think of.
But generally speaking, you just want to enable it.
The other two things we have to do
is turn on traffic engineering for whatever level database
it is that we want to support traffic engineering in.
This can, of course, be either level 1, level 2,
or as we're doing here, level 1, 2 to cover both.
And just like before in OSPF, we really
want to set the router ID as well.
Of course, in this example, I'm just using loopback 0.
But of course, you could use whatever interface you prefer.
Now if we look at our IOS XE configuration,
we'll see that this is almost identical.
So the first thing is we go into the router IS-IS process,
and then we can simply just turn on MPLS traffic engineering.
And again turn it on for whatever level database
it is we want to support.
We, of course, once again set our router ID.
In this example, I'm again setting it to loopback 0
just like we did on IOS XR.
And just like IOS XR, we need the metric style wide on IOS XE
as well because that's not about the operating system,
it's about the protocol.
So as you can see, this is actually
fairly similar to what we had to do in OSPF.
The only difference here is instead of specifying an area,
we specified the level of the database
that we want to enable traffic engineering for.
So in this video, we took what we
could consider the final step in actually preparing our core
to run MPLS traffic engineering.
And that is we simply enabled the traffic engineering
extensions for our underlying IGP.
We actually configured it on the command line for OSPF.
And then, of course, we saw over here
how to configure it for IS-IS.
Now all of this brings us up to the point
that we're actually finally ready to build some MPLS TE
tunnels.
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.