1
00:00:09,290 --> 00:00:15,740
This is one of multiple IP version 6 troubleshooting videos in this topology.

2
00:00:15,770 --> 00:00:21,860
We've been told that to write a one on the left is not able to ping the looped back of rudder three

3
00:00:21,860 --> 00:00:23,360
on the right.

4
00:00:23,480 --> 00:00:34,310
So let's verify that ping 2001 face 3 We're getting an unreachable message so let's have a look at the

5
00:00:34,310 --> 00:00:35,090
writing table.

6
00:00:35,090 --> 00:00:36,860
Show IP vs 6 rot.

7
00:00:37,070 --> 00:00:46,310
We've got a default route to write it to so when we use a trace route to that address.

8
00:00:46,600 --> 00:00:50,650
Notice the traffic gets to write it too but gets no further.

9
00:00:50,650 --> 00:01:01,860
So we're getting unreachable messages let's have a look at write to ping 2001 face 3.

10
00:01:01,970 --> 00:01:07,140
Notice the output no valid front for destination.

11
00:01:07,550 --> 00:01:09,360
So let's have a look at the writing table.

12
00:01:09,410 --> 00:01:11,770
So show IP vs 6 round.

13
00:01:11,840 --> 00:01:17,270
Do you see a raft in the routing table for the loop back of rudder 3.

14
00:01:17,330 --> 00:01:21,670
This is a connected and local rat connected local.

15
00:01:21,680 --> 00:01:26,030
There is no static ROT FOR THE LOOP BACK OF router 3.

16
00:01:26,030 --> 00:01:28,870
This is a static route for the loop back over auto 1.

17
00:01:28,910 --> 00:01:33,960
So show run pipe include route.

18
00:01:34,120 --> 00:01:41,560
So here's the static route to write a one here's a default prompt pointing to or out of three.

19
00:01:41,590 --> 00:01:43,830
So what do you think is the problem here.

20
00:01:43,840 --> 00:01:48,200
We have a static Grant configured but it's not showing up in the writing table.

21
00:01:48,250 --> 00:01:52,220
What's the problem let's have a look at our interfaces.

22
00:01:52,220 --> 00:01:54,580
Show IP the six interface.

23
00:01:54,740 --> 00:01:58,420
Brief Can you see the problem in the sound.

24
00:01:58,430 --> 00:01:58,780
Put

25
00:02:01,820 --> 00:02:05,710
notice gigabit to zero one is administratively down.

26
00:02:05,900 --> 00:02:06,680
That's a problem.

27
00:02:06,680 --> 00:02:09,330
So interface gigabit 0 1.

28
00:02:09,440 --> 00:02:16,170
No shut show IP vs 6 round.

29
00:02:16,420 --> 00:02:21,570
Suddenly we see the default rot in the IP routing table.

30
00:02:21,910 --> 00:02:28,990
And if we're paying 2001 face 3 the ping succeeds on the site.

31
00:02:28,990 --> 00:02:32,590
When we do the trace route notice it succeeds.

32
00:02:32,710 --> 00:02:39,460
So right no one is able to ping the loop back of rudder 3.

33
00:02:39,470 --> 00:02:48,070
Now don't forget IP vs 6 is a layer 3 protocol in the same way that IP version four is a layer 3 protocol

34
00:02:48,880 --> 00:02:54,260
layer 3 protocols rely on layer 2 protocols and layer 1 protocols.

35
00:02:54,430 --> 00:02:57,670
So show CTP neighbors would allow us to verify and check.

36
00:02:57,700 --> 00:03:04,930
Layer 1 and layer 2 and we could also look at the interfaces on the router by using commands such as

37
00:03:04,930 --> 00:03:10,960
Show interface gigabit 0 1 that would allow us to check if the interfaces are pop

38
00:03:13,550 --> 00:03:16,680
or show IP vs 6 interface gigabit.

39
00:03:16,700 --> 00:03:18,200
0 1.

40
00:03:18,200 --> 00:03:24,260
This would show us whether the interface is up and also allow us to verify IP addresses configured on

41
00:03:24,260 --> 00:03:25,910
that interface.

42
00:03:25,910 --> 00:03:31,160
One of the hardest parts was troubleshooting networks is to narrow down where the problem is in the

43
00:03:31,160 --> 00:03:32,150
network.

44
00:03:32,150 --> 00:03:38,750
It could be something as simple as an interface shut down or a cable that's unplugged or a damaged cable

45
00:03:39,220 --> 00:03:44,000
higher layer protocols rely on the lower layer protocols.

46
00:03:44,000 --> 00:03:50,380
So you need to use the OSA model in your troubleshooting to help you find where the problem is.

47
00:03:50,390 --> 00:03:52,410
This wasn't a layer 3 issue.

48
00:03:52,460 --> 00:03:56,460
In other words it's not a routing issue or an IP version 6 issue.

49
00:03:56,630 --> 00:03:58,790
It was a physical issue.

50
00:03:59,000 --> 00:04:01,130
The interface on the rudder was shut down.

51
00:04:01,850 --> 00:04:03,740
Opa enjoyed this video.

52
00:04:03,740 --> 00:04:06,710
If it was of benefit to you please like it.

53
00:04:06,710 --> 00:04:09,420
And please subscribe to my YouTube channel.

54
00:04:09,470 --> 00:04:12,990
I wish you all the very best.