Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:16,920 --> 00:00:19,230
Okay so let's complete this lab.
2
00:00:19,500 --> 00:00:24,310
The first step is to verify links using GDP and LDP.
3
00:00:24,920 --> 00:00:25,890
So on call 1
4
00:00:30,160 --> 00:00:32,700
shows GDP numbers after the moment.
5
00:00:32,710 --> 00:00:41,520
We don't see any neighbors show IP interface brief interfaces are up but no neighbors are displaying
6
00:00:43,420 --> 00:00:48,690
shows GDP CTP is enabled on the switch.
7
00:00:48,690 --> 00:00:50,670
What about switch to
8
00:00:55,360 --> 00:00:56,550
shows GDP.
9
00:00:56,560 --> 00:01:08,030
Neighbors noticed the problem CTP is not enabled on switch to now in the real world CTP is enabled on
10
00:01:08,030 --> 00:01:17,850
Cisco devices by default if its not enabled use the command CTP run in global config mode so shows GDP
11
00:01:17,850 --> 00:01:25,680
numbers now shows us that we don't have any neighbors but we are seeing some output that's different
12
00:01:26,070 --> 00:01:28,580
to what we saw previously.
13
00:01:28,780 --> 00:01:39,460
So what I'll do initially is simply make sure that CTP is enabled on all devices shows GDP neighbors
14
00:01:39,990 --> 00:01:49,410
GDP is not enabled so CTP run do something similar on access to
15
00:01:53,070 --> 00:02:00,770
shows GDP neighbors not enabled so CTP run access 3
16
00:02:05,640 --> 00:02:12,420
before I enable it let's confirm not enabled CTP run.
17
00:02:12,460 --> 00:02:24,210
Okay A BACK ON CALL 1 show GDP neighbors notice we are now seeing our neighbors so we can confirm that
18
00:02:24,210 --> 00:02:33,540
CO 2 is connected to our local interfaces gigabit one zero twenty three and one zero 24 CO 2 is using
19
00:02:33,870 --> 00:02:42,530
this port gigabit 123 to connect to our gigabit once there are twenty three quarters gigabit ones there
20
00:02:42,530 --> 00:02:52,150
are 24 interfaces connected to our gigabit there are 24 interface that looks good access one is connected
21
00:02:52,150 --> 00:02:58,980
via gigabit one zero twenty three to our local interface gigabit 1 0 1.
22
00:02:59,230 --> 00:03:00,310
So that looks good.
23
00:03:01,920 --> 00:03:04,390
Access to gigabit ones there are 23.
24
00:03:04,400 --> 00:03:12,740
This interface is connected to gigabit ones there are two also looks good access 3 gigabit ones there
25
00:03:12,740 --> 00:03:21,020
are twenty three is connected to our gigabit 1 0 3 interface so that also looks good so the CTP output
26
00:03:21,110 --> 00:03:29,290
looks correct on call 1 CTP doesn't run on servers so we don't see the server in the output.
27
00:03:29,660 --> 00:03:31,960
What about court 2.
28
00:03:32,030 --> 00:03:33,290
So in court to
29
00:03:36,170 --> 00:03:41,390
show CTP neighbors call 1 looks correct.
30
00:03:41,580 --> 00:03:50,520
Access 1 is using gigabit ones there are 24 to connect to our local 1 0 1 interface that looks good.
31
00:03:50,880 --> 00:03:59,270
Access 2 and 3 are doing something similar so that looks good what we aren't seeing here is the router
32
00:03:59,960 --> 00:04:06,390
so let's check the router.
33
00:04:06,530 --> 00:04:17,610
Sure CTP neighbor CTP is not enabled so CTP run show CTP neighbor now may take it a while.
34
00:04:17,610 --> 00:04:26,760
Just remember with CTP it sends updates out every 60 seconds so it could take up to 60 seconds for you
35
00:04:26,760 --> 00:04:28,980
to see a neighbor relationship.
36
00:04:28,980 --> 00:04:31,410
So you just need to be patient.
37
00:04:31,800 --> 00:04:39,420
Don't assume there's a problem if you don't see a neighbor immediately wait at least a minute and there
38
00:04:39,420 --> 00:04:43,690
you go we can see the broader on court too.
39
00:04:43,770 --> 00:04:47,740
We can see that it's a rotter we can see that it's an eyesore.
40
00:04:47,970 --> 00:04:56,770
We can also see that the other switches in the topology are 36 60s back an eyesore may take it a while
41
00:04:57,170 --> 00:05:06,840
so come back to that on access 1 show CTP neighbor it's got to neighbor relationships want to call 1.
42
00:05:06,950 --> 00:05:08,360
Want to call too.
43
00:05:08,440 --> 00:05:13,180
That looks good typically you don't have to do it both ways.
44
00:05:13,200 --> 00:05:18,690
If you see the neighbor relationship on one side you'll see it on the other side.
45
00:05:18,810 --> 00:05:20,340
That's not always true.
46
00:05:20,340 --> 00:05:27,660
However when you have multi vendor environments HP switches as an example will receive CTP messages
47
00:05:27,690 --> 00:05:28,850
but not send it.
48
00:05:29,490 --> 00:05:32,740
So you may want to check things on both sides.
49
00:05:33,090 --> 00:05:40,440
But remember that when you have multiple vendors or if there's an access list blocking CTP coming interests
50
00:05:40,460 --> 00:05:45,090
which you may see it only on one side that looks good.
51
00:05:45,120 --> 00:05:51,380
So access 3 is seeing call 1 and 2 and again back on Access 2.
52
00:05:51,450 --> 00:05:56,280
We can see call 1 and call 2 so that CBP.
53
00:05:56,580 --> 00:05:58,320
But we're not finished yet.
54
00:05:58,350 --> 00:06:00,930
We need to check an old DP.
5449
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.