At the moment this network is working correctly as an example for keeping the Lubeck of route one and
it can paying gigabit 0 0 1 to one can paying the loopback of wrote a four and can paying
the gigabit 00 interface on 4.
But in the same way as you have with OSPF version 2 you can enable passive interfaces so if we use the
command passive interface default that will make all interfaces passive.
In other words the rudder.
Rudder 3 will not to form neighbor relationships on these interfaces or send updates out of those interfaces
so you can see both relationships have come down.
Show
IPV six was a neighbor the unknown neighbor relationships Rodda one is no longer able to ping wrote
a full
on Rodda to we can see that the neighbor relationship has gone down.
Show IPV six OSPF neighbor.
We only have one neighbor relationship.
So from a troubleshooting point of view if you can't ping through an OSPF network check that the neighbor
relationships are established.
If the neighbor relationships aren't established check that OSPF is enabled on all the relevant interfaces
in the right areas.
So make sure that your areas are configured correctly on the relevant interfaces.
Sarada 3 doesn't have a neighbor relationship.
Make sure that OSPF is enabled on the relevant interfaces.
If it is enabled on the interfaces check your configuration and make sure that you haven't got passive
interfaces.
So as an example here we can see that all interfaces have gone passive or we could use the command show
IPV 6 SPF interface
I notice we have the Southport no Hallo's passive interface and we can see that on gigabit at 0 1 and
we can see that on gigabit 00.
So check that passive hasn't been configured on the Rodda.
So in this example what I'll do is disable the passive interface on gigabit 00
so no passive interface interface gigabit 00.
And what we should see is that a neighbor relationship is formed and there you go.
So do show IPV six OSPF neighbor we can see a neighbor relationship has been established on gigabit
0 0.
And we could do something similar on gigabit to 0 1 and notice the neighbor relationship has come up.
So be careful with passive interface you can set up one passive interface like gigabit 0 1 or you can
enable passive interfaces or globally and then disable them to do show run pipe began.
SPF
notice the configuration we've enabled default passive interfaces all interfaces will be passive but
then we've overwritten the passive option on the interface and the interface.
Typically you only enable passive interfaces on links to external networks or to user facing villans
as an example where you don't want your users to learn always be a froths Another issue may be that
OSPF wasn't enabled on an interface.
Do show run interface gigabit 0 1 if this command wasn't configured the relationship would not form
on that interface.
So do show IPV six SPF neighbor shows us that no neighbor relationship exists on gigabit 0 1 and that's
where this command to show IPV 6 OSPF interface breach is very useful.
We can see very quickly that OSPF was not enabled on those interface.
Now what happens if the wrong area was used.
Dush IPV 6 OSPF neighbor no neighbor relationship is established but no we are getting a warning message
about an area mismatch.
We received an update with the incorrect area.
So our local area is three but the remote area is two.
So we are warned by the Rada about that problem.
So we need to configure the right area and as soon as we do that a neighbor relationship is established.
So be aware that the same troubleshooting options exist in a whisper version 3 as you have an always
be version to the show commands or very similar output is very similar.
The logic is very similar but using IP version 6 addresses and protocols rather than IP version 4.