Okay, so now Core 2 is neighbors with Core 1, Core 3, and Ral1.
Which interfaces is he configuring into?
See, he's configured into four different networks here so he has the 1,
2, and 3 covered, but there's nothing on this 4.
So he's connected to Core 1, Core 2; sorry,
Core 1, Core 3, and Ral1, but he's not configured or he's configured,
but he's not becoming neighbors with NYC1,
10.10 .10 .17.
(Typing) I see just a Core 3 and NYC2 of that interface.
(Typing) See, from here, do we see any problem here?
We sort of scrolled by a little too fast, but we'll see.
Yeah,
there's a little command in here so we didn't pick up on real
quick; the dead interval has been changed.
So if you remember back in the modules, we said that the timers for OSPF,
which is different from than some other routing protocols like EIGRP,
the timers have to match in OSPF.
So the hello and the dead timers have to match between the devices for
them to form a neighborship and they do send these along inside the
OSPF packet so if they see a discrepancy,
they're just going to not form a neighborship on it.
The dead interval would normally be 40 for a hello timer of 10,
and the broadcast network type default is 10 and 40.
So all we need to do is go onto this interface and remove that command.
(Typing) And then we see that came up real quick.
Yeah, we took it off and the dead interval goes back to 40,
and he is now adjacent with Core 2.
So now NYC1 is adjacent with Core 2 and Core 3 as
this is the way it's supposed to be, and it's also adjacent with NYC2, which are all its neighbors.