WEBVTT

0:00:08.420000 --> 0:00:13.460000
 So after all of this theory of OSPF we've
 been talking about, let's finally

0:00:13.460000 --> 0:00:16.420000
 get around actually configuring
 this thing.

0:00:16.420000 --> 0:00:19.460000
 So let's talk about
 implementing OSPF.

0:00:19.460000 --> 0:00:24.200000
 So the initial configuration
 of OSPF is pretty simple.

0:00:24.200000 --> 0:00:26.740000
 Few things I want to call to
 your attention right here.

0:00:26.740000 --> 0:00:31.740000
 So you would start out by configuring
 at the global configuration level

0:00:31.740000 --> 0:00:36.860000
 your command router OSPF
 and then a process ID.

0:00:36.860000 --> 0:00:41.920000
 Now I want to make a distinct difference
 between a process ID and an autonomous

0:00:41.920000 --> 0:00:51.820000
 system number. In EIGRP at the global
 configuration level, come on, you

0:00:51.820000 --> 0:01:02.680000
 typed router EIGRP and then you had
 to put your autonomous system number

0:01:02.680000 --> 0:01:08.440000
 right here. And whatever number you
 put there as your autonomous system

0:01:08.440000 --> 0:01:13.180000
 number was very important because that
 number had to match on all the

0:01:13.180000 --> 0:01:18.120000
 routers. In EIGRP when a router sends
 out an EIGRP hello packet, it includes

0:01:18.120000 --> 0:01:22.480000
 the autonomous system number as part
 of that hello packet and those things

0:01:22.480000 --> 0:01:27.980000
 have to match. Well in this particular
 case, a process ID is not sent

0:01:27.980000 --> 0:01:30.420000
 in any OSPF packets.

0:01:30.420000 --> 0:01:33.540000
 It's simply a locally
 significant value.

0:01:33.540000 --> 0:01:36.660000
 That's it. Now you might be wondering
 Keith, what do you mean a locally

0:01:36.660000 --> 0:01:37.540000
 significant value?

0:01:37.540000 --> 0:01:41.720000
 When I use that term locally significant,
 that means only this router,

0:01:41.720000 --> 0:01:45.000000
 only this device needs to
 be aware of that number.

0:01:45.000000 --> 0:01:48.720000
 It's not shared with
 any other device.

0:01:48.720000 --> 0:01:53.240000
 So most of the time when people configure
 OSPF they use process ID number

0:01:53.240000 --> 0:01:56.620000
 one, you can use whatever
 you want.

0:01:56.620000 --> 0:02:00.000000
 I mean theoretically on router
 one you can use process one.

0:02:00.000000 --> 0:02:01.760000
 On router two you can
 use process two.

0:02:01.760000 --> 0:02:04.860000
 On router 99 you can
 use process 99.

0:02:04.860000 --> 0:02:06.340000
 It doesn't really matter.

0:02:06.340000 --> 0:02:08.460000
 It does not have to match.

0:02:08.460000 --> 0:02:12.460000
 The main thing to remember is unless
 you have a real good reason for doing

0:02:12.460000 --> 0:02:17.580000
 so, you should only have one process
 of OSPF running in your router and

0:02:17.580000 --> 0:02:22.300000
 that's it. As an example, let
 me contrast that with EIGRP.

0:02:22.300000 --> 0:02:27.080000
 Once again with EIGRP, if I had a router
 right here, let's say this is

0:02:27.080000 --> 0:02:35.100000
 router X, Y and Z.

0:02:35.100000 --> 0:02:47.700000
 Let's say that Y and Z were part of
 company YZ and then all of a sudden

0:02:47.700000 --> 0:02:51.940000
 we acquire a new company.

0:02:51.940000 --> 0:02:59.500000
 This is an acquisition.

0:02:59.500000 --> 0:03:07.820000
 Maybe we were already doing EIGRP in
 company XYZ or I should say YZ and

0:03:07.820000 --> 0:03:11.960000
 previously we were using autonomous
 system number 200.

0:03:11.960000 --> 0:03:14.540000
 So all of the routers
 here were using 200.

0:03:14.540000 --> 0:03:18.500000
 All of a sudden this new acquisition
 we have, well they were also using

0:03:18.500000 --> 0:03:24.300000
 EIGRP but they were using autonomous
 system number 77.

0:03:24.300000 --> 0:03:31.080000
 So for the time being router Y actually
 has to have two instances of EIGRP.

0:03:31.080000 --> 0:03:35.520000
 You have to type router EIGRP 200 and
 so that's how he can exchange routes

0:03:35.520000 --> 0:03:39.660000
 with his own internal company and then
 also in router Y you'd have router

0:03:39.660000 --> 0:03:46.080000
 EIGRP 77. Totally different process
 that he can run with router X.

0:03:46.080000 --> 0:03:48.300000
 Now those two processes
 will not share routes.

0:03:48.300000 --> 0:03:51.000000
 They will be separate in router Y.


0:03:51.000000 --> 0:03:55.240000
 We would have to redistribute between
 the two processes till one process,

0:03:55.240000 --> 0:03:58.720000
 send his routes into the other and
 the other process, send his routes

0:03:58.720000 --> 0:04:02.000000
 back. That's something we'd have
 to do manually in router Y.

0:04:02.000000 --> 0:04:05.760000
 Otherwise they will stay separate and
 unique as if they were two completely

0:04:05.760000 --> 0:04:07.820000
 different routing protocols.

0:04:07.820000 --> 0:04:12.320000
 So that's the only time when you would
 really need two instances of the

0:04:12.320000 --> 0:04:16.060000
 same routing protocol
 running in one router.

0:04:16.060000 --> 0:04:18.820000
 Well that also holds
 true with OSPF.

0:04:18.820000 --> 0:04:23.000000
 In OSPF you should only have to have
 a single process running in your

0:04:23.000000 --> 0:04:27.300000
 router. Only if you're in a situation
 like this would you possibly need

0:04:27.300000 --> 0:04:31.500000
 more than one process but at the CCNA
 level just think to yourself I'm

0:04:31.500000 --> 0:04:35.680000
 only going to type router OSPF
 some number and that's it.

0:04:35.680000 --> 0:04:37.600000
 And I'm never going to do that command
 again, I'm never going to have

0:04:37.600000 --> 0:04:40.120000
 to create another process.

0:04:40.120000 --> 0:04:42.200000
 One process is enough.

0:04:42.200000 --> 0:04:45.820000
 And then use your network command.


0:04:45.820000 --> 0:04:50.840000
 Now in EIGRP you had the option
 of using a wildcard mask.

0:04:50.840000 --> 0:04:53.360000
 In OSPF it's not an option.

0:04:53.360000 --> 0:04:58.340000
 In OSPF you have to include a wildcard
 mask after your prefix.

0:04:58.340000 --> 0:05:03.080000
 And then you also include the word
 area and then the area number.

0:05:03.080000 --> 0:05:07.260000
 So for as an example of that you might
 type network, I'm just going to

0:05:07.260000 --> 0:05:15.240000
 shorten it, 25.70.00 and then a wildcard
 mask that would be appropriate

0:05:15.240000 --> 0:05:22.760000
 for that. And then I would tell my
 router okay any links that you have

0:05:22.760000 --> 0:05:28.660000
 on yourself that begin with 25.70 those
 links are going to be part of

0:05:28.660000 --> 0:05:34.800000
 area one. So that's an example of
 how you type the network command.

0:05:34.800000 --> 0:05:39.920000
 Now the router will come up with a
 router ID by itself but as you saw

0:05:39.920000 --> 0:05:43.100000
 in the last video where we talked about
 designated routers and backup

0:05:43.100000 --> 0:05:47.380000
 designated routers you might want to
 deterministically set the router

0:05:47.380000 --> 0:05:53.100000
 ID so that you can influence which router
 will become the DR or the BDR.

0:05:53.100000 --> 0:05:57.260000
 And remember every segment that
 needs a DR is a unique segment.

0:05:57.260000 --> 0:06:00.900000
 In other words if I'm a router with two
 ethernet segments on this segment

0:06:00.900000 --> 0:06:05.340000
 there's going to be a DR it might
 be me, might be somebody else.

0:06:05.340000 --> 0:06:08.860000
 And on this segment right here that's
 also ethernet there's going to be

0:06:08.860000 --> 0:06:12.540000
 another DR, might be me,
 might be somebody else.

0:06:12.540000 --> 0:06:18.360000
 But every broadcast segment or non-broadcast
 multi-access segment needs

0:06:18.360000 --> 0:06:26.900000
 a DR and a BDR. Along those same lines
 you could also influence the IP

0:06:26.900000 --> 0:06:29.280000
 OSPF priority on an interface.

0:06:29.280000 --> 0:06:35.280000
 Remember the default priority of OSPF
 on an interface is 1, the default

0:06:35.280000 --> 0:06:41.400000
 is 1. If you set the priority to 0
 that actually means this router can

0:06:41.400000 --> 0:06:46.660000
 never become a DR on that interface
 it is disqualified from becoming a

0:06:46.660000 --> 0:06:53.260000
 DR. Now like it says here both the router
 ID and the priority if you change

0:06:53.260000 --> 0:06:58.540000
 them you need to restart your OSPF process
 it will not take those changes

0:06:58.540000 --> 0:07:03.780000
 on the fly. And then here's some verification
 commands we can use to see

0:07:03.780000 --> 0:07:05.380000
 what OSPF is doing.

0:07:05.380000 --> 0:07:08.760000
 So let's actually do an example
 of this in the lab.

0:07:08.760000 --> 0:07:12.560000
 So I'm going to be using
 this topology right here.

0:07:12.560000 --> 0:07:17.640000
 And the routers that you see with the
 light blue circles router 1 switch

0:07:17.640000 --> 0:07:22.460000
 1 router 2 switch 3 and router 4 they
 have already been pre-configured

0:07:22.460000 --> 0:07:26.360000
 for OSPF. So they are already up and running
 and I'm just going to configure

0:07:26.360000 --> 0:07:32.280000
 OSPF from scratch on switch
 2 and router 3.

0:07:32.280000 --> 0:07:35.360000
 Now before I do that let's for example
 let's go to router 2 and now let's

0:07:35.360000 --> 0:07:38.220000
 go to router and issue some verification
 commands to see what he looks

0:07:38.220000 --> 0:07:41.700000
 like already router 2.

0:07:41.700000 --> 0:07:49.260000
 Okay so what command would I type to
 see if this router has become fully

0:07:49.260000 --> 0:07:53.760000
 adjacent with any other OSPF neighbors
 or if he's learned of any OSPF

0:07:53.760000 --> 0:07:57.260000
 neighbors in any other
 transitory state.

0:07:57.260000 --> 0:08:05.000000
 Hopefully you said show IP OSPF neighbor
 and you can see he's got one

0:08:05.000000 --> 0:08:10.640000
 neighbor 1.2.1.1 that is switch 1.


0:08:10.640000 --> 0:08:13.800000
 So remember when switch 1 was coming
 up with his router ID first thing

0:08:13.800000 --> 0:08:15.800000
 you said was do I have
 any loopbacks?

0:08:15.800000 --> 0:08:20.560000
 No no I don't. Okay what interfaces
 do I have that are either up up up

0:08:20.560000 --> 0:08:24.140000
 down or down down these
 two right here.

0:08:24.140000 --> 0:08:27.800000
 All these two interfaces which one has
 the highest IP address that would

0:08:27.800000 --> 0:08:30.580000
 be this 1 2 1 11.

0:08:30.580000 --> 0:08:35.980000
 So switch 1 said I'm going to create
 my OSPF router ID of 1.2.1.11 and

0:08:35.980000 --> 0:08:38.220000
 that's what we can see right here.


0:08:38.220000 --> 0:08:41.080000
 What do you think the router ID
 is going to be of router 1?

0:08:41.080000 --> 0:08:44.580000
 It should be a loopback right because
 the very first thing it's looked

0:08:44.580000 --> 0:08:50.300000
 at is a loopback so let's go to router
 1 and take a look which is also

0:08:50.300000 --> 0:08:54.920000
 going to answer the question of when
 I'm on a local router how can I tell

0:08:54.920000 --> 0:08:56.600000
 what its router ID is.

0:08:56.600000 --> 0:09:03.280000
 You can just do the command show IP
 OSPF show IP OSPF and right at the

0:09:03.280000 --> 0:09:09.120000
 top it says here is my router ID and
 this case just like we thought it's

0:09:09.120000 --> 0:09:11.460000
 the loopback interface.

0:09:11.460000 --> 0:09:15.440000
 So show IP OSPF shows you a lot of good
 stuff as you can see right here

0:09:15.440000 --> 0:09:25.120000
 and once again we will give us
 some information about OSPF.

0:09:25.120000 --> 0:09:28.860000
 Shows you what your locally significant
 process idea is I just use the

0:09:28.860000 --> 0:09:31.220000
 number 1 on all of mine.

0:09:31.220000 --> 0:09:39.340000
 It shows you what neighbors you have,
 the administrative distance of OSPF.

0:09:39.340000 --> 0:09:44.120000
 Going back here once again because router
 1, switch 1 and router 2 have

0:09:44.120000 --> 0:09:48.300000
 already been pre-configured router 2 should
 have learned about this loopback

0:09:48.300000 --> 0:09:55.500000
 network 1 11 1 11 1 11 and he should
 have learned about 1 11 0 as OSPF

0:09:55.500000 --> 0:10:00.500000
 routes. So let's take a look in his
 OSPF routing table of router 2.

0:10:00.500000 --> 0:10:08.060000
 Show IP route and there we can see
 there is that loopback network that

0:10:08.060000 --> 0:10:13.140000
 was learned via OSPF and here is that
 other network that was learned via

0:10:13.140000 --> 0:10:19.180000
 OSPF. I know it's when a route is prefaced
 with just the letter O that

0:10:19.180000 --> 0:10:25.280000
 means that it is an OSPF
 intra area route.

0:10:25.280000 --> 0:10:26.260000
 What does that mean?

0:10:26.260000 --> 0:10:30.820000
 That means that this route actually
 lives in the same area where this

0:10:30.820000 --> 0:10:32.800000
 local router is.

0:10:32.800000 --> 0:10:37.700000
 In other words router 2 says okay the
 1 11 11 11 11 and the 1 11 1 they

0:10:37.700000 --> 0:10:51.460000
 both reside in Now let's go ahead and
 configure switch 2 for OSPF and

0:10:51.460000 --> 0:10:54.240000
 if you haven't already taken a screenshot
 of this I would recommend that

0:10:54.240000 --> 0:10:57.460000
 you do so so you can follow along.


0:10:57.460000 --> 0:11:02.720000
 So in switch 2 what I'm going to do is
 I'm going to have 3 network statements.

0:11:02.720000 --> 0:11:05.620000
 I'm going to configure OSPF and I'm
 going to put the 2 2 2 network in

0:11:05.620000 --> 0:11:11.380000
 the area 1. I'm going to put the 2 3
 2 network in the area 0 and I'm going

0:11:11.380000 --> 0:11:14.900000
 to put the 3 2 3 network
 also in area 0.

0:11:14.900000 --> 0:11:18.560000
 So my configuration will consist
 of a total of 4 commands.

0:11:18.560000 --> 0:11:23.960000
 Router OSPF 1 followed by 3 network
 statements and that will be all I

0:11:23.960000 --> 0:11:26.460000
 need for switch 2.

0:11:26.460000 --> 0:11:34.380000
 Router OSPF and you can see here my
 process ID locally significant value

0:11:34.380000 --> 0:11:37.240000
 you've got quite a range of
 values you can choose from.

0:11:37.240000 --> 0:11:40.000000
 Most people usually
 just start with 1.

0:11:40.000000 --> 0:11:46.860000
 I'm going to say network 2 2 2 0 with
 the appropriate wildcard mask and

0:11:46.860000 --> 0:11:55.080000
 that's going to be an area 1 network
 2.3.2.0 that's going to be an area

0:11:55.080000 --> 0:12:02.020000
 0. So right there the fact that I have
 put 1 link in area 1 and 1 or more

0:12:02.020000 --> 0:12:07.720000
 links in area 0 means this router is
 now an area border router and network

0:12:07.720000 --> 0:12:13.440000
 3.2.3.0 also an area 0.

0:12:13.440000 --> 0:12:18.720000
 Now how could I tell that this router,
 now remember it's a switch but

0:12:18.720000 --> 0:12:22.400000
 it's a multi layer switch I've enabled
 it for routing so I'm just calling

0:12:22.400000 --> 0:12:27.200000
 it a router. How do I know this
 device is running OSPF?

0:12:27.200000 --> 0:12:34.580000
 Well once again show IP protocols and
 if OSPF shows up here which it does

0:12:34.580000 --> 0:12:39.740000
 I know it's running OSPF it also says
 right here it is an area border

0:12:39.740000 --> 0:12:44.360000
 router so he knows that he's an area
 border router and this shows me the

0:12:44.360000 --> 0:12:51.140000
 various networks where I've activated
 OSPF with the network command.

0:12:51.140000 --> 0:12:56.420000
 So now I'll just go ahead and put my
 light blue circle on switch 2 since

0:12:56.420000 --> 0:12:59.200000
 I've just finished OSPF for him.

0:12:59.200000 --> 0:13:05.940000
 So at this point if we go into let's
 say router 4, router 4 should now

0:13:05.940000 --> 0:13:13.260000
 have at least a couple of networks
 that are OSPF intra area routes.

0:13:13.260000 --> 0:13:17.160000
 He should have learned about the 2.3
.2 network and he should have learned

0:13:17.160000 --> 0:13:22.000000
 about the 3.2.3 network as intra area
 routes so these two routes should

0:13:22.000000 --> 0:13:27.860000
 show up just simply as O's in R4 and
 then R4 should also have learned

0:13:27.860000 --> 0:13:32.960000
 about all these routes over here in
 area 1 and in R4's routing table all

0:13:32.960000 --> 0:13:38.820000
 of these will show up as OIA in the
 routing table OIA standing for inter

0:13:38.820000 --> 0:13:44.380000
 area routes routes that originated
 in some other area the router 4 is

0:13:44.380000 --> 0:13:45.840000
 not connected to.

0:13:45.840000 --> 0:13:47.260000
 Let's take a look at router 4.

0:13:47.260000 --> 0:13:56.220000
 Show IP routes. There we have it.

0:13:56.220000 --> 0:14:01.700000
 There are routes that are part of his
 own area and OSPF is a metric uses

0:14:01.700000 --> 0:14:06.800000
 cost. It uses cost which is based on
 interface bandwidth just like the

0:14:06.800000 --> 0:14:10.900000
 spanning tree protocol the metric of OSPF
 is cost it just uses a completely

0:14:10.900000 --> 0:14:16.700000
 different formula but the higher
 the bandwidth the lower the cost.

0:14:16.700000 --> 0:14:22.300000
 And here we see inter area routes learned
 from a different area and those

0:14:22.300000 --> 0:14:28.300000
 have a slightly higher cost because
 they're a little bit further away.

0:14:28.300000 --> 0:14:33.100000
 And at this point I think one other thing
 I want to show you you can actually

0:14:33.100000 --> 0:14:38.840000
 look at the database that contains your
 OSPF LSA's show IP OSPF database

0:14:38.840000 --> 0:14:42.820000
 and shows you your
 different LSA's.

0:14:42.820000 --> 0:14:47.800000
 Now at the CCNA level you like I said
 you don't have to know about the

0:14:47.800000 --> 0:14:51.320000
 specific kinds of LSA's you don't have
 to know what their names and type

0:14:51.320000 --> 0:14:55.580000
 numbers are. You don't even really need
 to be able to interpret the output

0:14:55.580000 --> 0:14:56.500000
 of this command.

0:14:56.500000 --> 0:15:00.040000
 I just wanted to show you that it is
 available to you and once you get

0:15:00.040000 --> 0:15:04.080000
 to the CCNP level and you start learning
 about the details of LSA's then

0:15:04.080000 --> 0:15:07.800000
 you'll start going into gory detail about
 the output of show IP OSPF database

0:15:07.800000 --> 0:15:10.740000
 and some various keywords
 that you can add to it.

0:15:10.740000 --> 0:15:13.520000
 But I just want you to walk away from
 this video knowing that you can

0:15:13.520000 --> 0:15:19.200000
 go into the database and
 see various things.

0:15:19.200000 --> 0:15:24.800000
 And other than that we have gone through
 all of these show commands here.

0:15:24.800000 --> 0:15:28.340000
 Oh show IP OSPF interface we haven't
 taken a look at that one yet.

0:15:28.340000 --> 0:15:33.340000
 Show IP OSPF interface.

0:15:33.340000 --> 0:15:39.780000
 And you can see it'll show you every
 interface that has been activated

0:15:39.780000 --> 0:15:42.420000
 for OSPF because of
 a network command.

0:15:42.420000 --> 0:15:44.720000
 It shows you the interface.

0:15:44.720000 --> 0:15:47.560000
 It shows you what kind
 of network it is.

0:15:47.560000 --> 0:15:50.100000
 Remember we talked about that in a previous
 section this is a broadcast

0:15:50.100000 --> 0:15:53.340000
 interface. It shows
 you the OSPF cost.

0:15:53.340000 --> 0:15:55.960000
 Remember cost is based
 on bandwidth.

0:15:55.960000 --> 0:15:59.500000
 If I went into the interface and I changed
 the bandwidth that would affect

0:15:59.500000 --> 0:16:01.920000
 the OSPF cost value.

0:16:01.920000 --> 0:16:05.320000
 So OSPF's metric is much
 simpler than EIHRP.

0:16:05.320000 --> 0:16:09.780000
 EIHRP used all sorts of factors to come
 up with a complex metric called

0:16:09.780000 --> 0:16:12.340000
 distance. OSPF doesn't do that.

0:16:12.340000 --> 0:16:15.660000
 OSPF just factors bandwidth and that's
 it and it comes up with a cost

0:16:15.660000 --> 0:16:21.100000
 value. It also shows you on a link
 who the designator router is.

0:16:21.100000 --> 0:16:22.620000
 So you can see that.

0:16:22.620000 --> 0:16:27.520000
 You can see this particular device router
 4 is the backup designated router

0:16:27.520000 --> 0:16:30.380000
 and you can see your
 interface priority.

0:16:30.380000 --> 0:16:36.380000
 A lot of good information from
 the output of this command.

0:16:36.380000 --> 0:16:41.840000
 And for troubleshooting OSPF probably
 one of the best debug is debug IP

0:16:41.840000 --> 0:16:47.920000
 OSPF adjacency. That is a great debug
 to find out you know why do I not

0:16:47.920000 --> 0:16:48.720000
 have a neighbor.

0:16:48.720000 --> 0:16:51.920000
 If I'm looking at topology diagram
 and I say well router 1 and router

0:16:51.920000 --> 0:16:56.120000
 2 should be neighbors with each other
 but when I do show IP OSPF neighbor

0:16:56.120000 --> 0:16:58.740000
 they're not seeing each other.

0:16:58.740000 --> 0:16:59.840000
 Great debug to turn on.

0:16:59.840000 --> 0:17:05.080000
 Debug IP OSPF adjacency will tell you
 what's going on and why they are

0:17:05.080000 --> 0:17:11.280000
 not neighbors. Debug IP packets I would
 recommend that you not use that

0:17:11.280000 --> 0:17:16.080000
 debug. That debug can be very verbose
 to give you gobs of output in just

0:17:16.080000 --> 0:17:17.800000
 a couple of seconds.

0:17:17.800000 --> 0:17:19.520000
 Probably not a good idea
 to turn that one on.

