1 00:00:00,580 --> 00:00:07,300 At the moment this network is working correctly as an example for keeping the Lubeck of route one and 2 00:00:07,300 --> 00:00:18,340 it can paying gigabit 0 0 1 to one can paying the loopback of wrote a four and can paying 3 00:00:20,970 --> 00:00:23,820 the gigabit 00 interface on 4. 4 00:00:24,120 --> 00:00:35,010 But in the same way as you have with OSPF version 2 you can enable passive interfaces so if we use the 5 00:00:35,010 --> 00:00:41,930 command passive interface default that will make all interfaces passive. 6 00:00:41,970 --> 00:00:43,800 In other words the rudder. 7 00:00:43,830 --> 00:00:51,050 Rudder 3 will not to form neighbor relationships on these interfaces or send updates out of those interfaces 8 00:00:51,710 --> 00:00:54,510 so you can see both relationships have come down. 9 00:00:55,450 --> 00:00:56,020 Show 10 00:00:59,010 --> 00:01:07,440 IPV six was a neighbor the unknown neighbor relationships Rodda one is no longer able to ping wrote 11 00:01:07,510 --> 00:01:08,010 a full 12 00:01:11,220 --> 00:01:14,640 on Rodda to we can see that the neighbor relationship has gone down. 13 00:01:14,750 --> 00:01:18,100 Show IPV six OSPF neighbor. 14 00:01:18,210 --> 00:01:21,780 We only have one neighbor relationship. 15 00:01:22,110 --> 00:01:28,740 So from a troubleshooting point of view if you can't ping through an OSPF network check that the neighbor 16 00:01:28,740 --> 00:01:30,350 relationships are established. 17 00:01:30,510 --> 00:01:37,530 If the neighbor relationships aren't established check that OSPF is enabled on all the relevant interfaces 18 00:01:38,010 --> 00:01:39,960 in the right areas. 19 00:01:40,050 --> 00:01:45,370 So make sure that your areas are configured correctly on the relevant interfaces. 20 00:01:46,680 --> 00:01:49,070 Sarada 3 doesn't have a neighbor relationship. 21 00:01:49,080 --> 00:01:54,450 Make sure that OSPF is enabled on the relevant interfaces. 22 00:01:54,450 --> 00:02:02,070 If it is enabled on the interfaces check your configuration and make sure that you haven't got passive 23 00:02:02,070 --> 00:02:04,920 interfaces. 24 00:02:05,050 --> 00:02:10,960 So as an example here we can see that all interfaces have gone passive or we could use the command show 25 00:02:10,960 --> 00:02:13,000 IPV 6 SPF interface 26 00:02:16,030 --> 00:02:26,090 I notice we have the Southport no Hallo's passive interface and we can see that on gigabit at 0 1 and 27 00:02:26,120 --> 00:02:28,700 we can see that on gigabit 00. 28 00:02:28,970 --> 00:02:33,900 So check that passive hasn't been configured on the Rodda. 29 00:02:33,950 --> 00:02:40,820 So in this example what I'll do is disable the passive interface on gigabit 00 30 00:02:44,080 --> 00:02:51,100 so no passive interface interface gigabit 00. 31 00:02:51,440 --> 00:02:54,430 And what we should see is that a neighbor relationship is formed and there you go. 32 00:02:54,430 --> 00:03:01,160 So do show IPV six OSPF neighbor we can see a neighbor relationship has been established on gigabit 33 00:03:01,250 --> 00:03:02,380 0 0. 34 00:03:02,990 --> 00:03:09,620 And we could do something similar on gigabit to 0 1 and notice the neighbor relationship has come up. 35 00:03:09,670 --> 00:03:18,730 So be careful with passive interface you can set up one passive interface like gigabit 0 1 or you can 36 00:03:18,730 --> 00:03:29,650 enable passive interfaces or globally and then disable them to do show run pipe began. 37 00:03:29,710 --> 00:03:30,310 SPF 38 00:03:33,270 --> 00:03:40,950 notice the configuration we've enabled default passive interfaces all interfaces will be passive but 39 00:03:40,950 --> 00:03:46,800 then we've overwritten the passive option on the interface and the interface. 40 00:03:46,800 --> 00:03:55,690 Typically you only enable passive interfaces on links to external networks or to user facing villans 41 00:03:55,760 --> 00:04:02,800 as an example where you don't want your users to learn always be a froths Another issue may be that 42 00:04:03,040 --> 00:04:06,280 OSPF wasn't enabled on an interface. 43 00:04:06,280 --> 00:04:18,400 Do show run interface gigabit 0 1 if this command wasn't configured the relationship would not form 44 00:04:18,790 --> 00:04:20,950 on that interface. 45 00:04:21,070 --> 00:04:31,740 So do show IPV six SPF neighbor shows us that no neighbor relationship exists on gigabit 0 1 and that's 46 00:04:31,740 --> 00:04:36,900 where this command to show IPV 6 OSPF interface breach is very useful. 47 00:04:36,900 --> 00:04:47,030 We can see very quickly that OSPF was not enabled on those interface. 48 00:04:47,030 --> 00:04:49,750 Now what happens if the wrong area was used. 49 00:04:50,150 --> 00:05:02,650 Dush IPV 6 OSPF neighbor no neighbor relationship is established but no we are getting a warning message 50 00:05:03,100 --> 00:05:04,960 about an area mismatch. 51 00:05:05,230 --> 00:05:09,940 We received an update with the incorrect area. 52 00:05:10,270 --> 00:05:16,030 So our local area is three but the remote area is two. 53 00:05:16,300 --> 00:05:19,990 So we are warned by the Rada about that problem. 54 00:05:20,110 --> 00:05:26,770 So we need to configure the right area and as soon as we do that a neighbor relationship is established. 55 00:05:26,800 --> 00:05:33,400 So be aware that the same troubleshooting options exist in a whisper version 3 as you have an always 56 00:05:33,400 --> 00:05:39,200 be version to the show commands or very similar output is very similar. 57 00:05:39,220 --> 00:05:46,120 The logic is very similar but using IP version 6 addresses and protocols rather than IP version 4.