WEBVTT

1
00:00.000 --> 00:04.480
So this part in our journey that we're going to configure this external BGP

2
00:04.480 --> 00:05.000
speaker.

3
00:05.000 --> 00:09.750
So I do have BGP capabilities on this Fortigate firewall, which is a .1, but I

4
00:09.750 --> 00:10.120
thought just

5
00:10.120 --> 00:14.570
to mix it up a little bit, let me bring in a Cisco device that we can run BGP

6
00:14.570 --> 00:15.040
on.

7
00:15.040 --> 00:19.240
So it's reachable at .121 on the 192.1 state, one network.

8
00:19.240 --> 00:23.440
And for connectivity to this little router here, I have a console connection

9
00:23.440 --> 00:23.640
from my

10
00:23.640 --> 00:25.040
management computer.

11
00:25.040 --> 00:28.200
So we can go ahead and do the configuration right there from a CLI.

12
00:28.200 --> 00:29.200
So that's what we're going to do right now.

13
00:29.200 --> 00:32.450
We're going to configure this BGP router to tell it that it's in the autonomous
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.200 --> 00:32.450
We're going to configure this BGP router to tell it that it's in the autonomous

14
00:32.450 --> 00:32.760
system

15
00:32.760 --> 00:33.760
6783.

16
00:33.760 --> 00:40.120
We'll specify that it has a peer, a couple of peers actually at .61 and .62.

17
00:40.120 --> 00:43.560
And those two peers, which are edge one and edge two respectively, those are in

18
00:43.560 --> 00:44.200
autonomous

19
00:44.200 --> 00:45.200
system 777.

20
00:45.200 --> 00:46.200
All right.

21
00:46.200 --> 00:49.550
So let's go to the command line interface on this Cisco device and let's

22
00:49.550 --> 00:51.600
configure BGP.

23
00:51.600 --> 00:52.760
And here we go.

24
00:52.760 --> 00:57.460
So I named this our 6783 just to help remind us that this is the router going

25
00:57.460 --> 00:58.560
to be supporting

26
00:58.560 --> 01:01.320
the autonomous system 6783 as far as BGP goes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:58.560 --> 01:01.320
the autonomous system 6783 as far as BGP goes.

27
01:01.320 --> 01:06.520
And I'm going to do a show IP protocols just to see what routing protocol.

28
01:06.520 --> 01:07.520
Nothing.

29
01:07.520 --> 01:10.480
So I have no dynamic routing protocols on this Cisco device whatsoever.

30
01:10.480 --> 01:14.000
This happens to be a Cisco catalyst multi-layer switch, by the way.

31
01:14.000 --> 01:17.500
Those type in configure space terminal, which takes us into configuration mode

32
01:17.500 --> 01:17.960
on the Cisco

33
01:17.960 --> 01:18.960
device.

34
01:18.960 --> 01:24.440
And let's create a logical routing process for BGP, autonomous system 6783.

35
01:24.440 --> 01:28.670
And to do that on the Cisco device, the command is router, BGP space, and then

36
01:28.670 --> 01:29.360
the autonomous

37
01:29.360 --> 01:31.280
system member that we want to use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:29.360 --> 01:31.280
system member that we want to use.

38
01:31.280 --> 01:32.880
And so we want to use 6783.

39
01:32.880 --> 01:37.170
We'll press enter and now we're in router configuration mode for BGP as part of

40
01:37.170 --> 01:37.800
autonomous

41
01:37.800 --> 01:38.800
system 6783.

42
01:38.800 --> 01:42.040
So to specify our neighbors, the command is neighbor.

43
01:42.040 --> 01:43.400
And so we'll type in neighbor.

44
01:43.400 --> 01:49.440
And then the edge one is going to be at 192.168.1.61.

45
01:49.440 --> 01:53.640
And if we just space in the question mark, we'll then see lots of options here.

46
01:53.640 --> 01:58.440
We want to specify that that device is in the remote autonomous system.

47
01:58.440 --> 02:02.050
So we'll type in remote dash as and that remote as that we're going to be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:58.440 --> 02:02.050
So we'll type in remote dash as and that remote as that we're going to be

48
02:02.050 --> 02:02.800
connecting

49
02:02.800 --> 02:07.560
to where edge one lives is 777 and we'll press enter.

50
02:07.560 --> 02:11.520
And I'm going to just pause right here for a moment because if that is

51
02:11.520 --> 02:12.480
successful on

52
02:12.480 --> 02:15.630
this Cisco device, they should get a little message saying, Hey, your BGP adjac

53
02:15.630 --> 02:16.120
ency is

54
02:16.120 --> 02:17.440
up, which is right there.

55
02:17.440 --> 02:18.440
That's great news.

56
02:18.440 --> 02:19.760
So let's go ahead and do it again.

57
02:19.760 --> 02:23.880
But this time I want to appear with dot 62 and press enter.

58
02:23.880 --> 02:28.040
And again, I'll wait for the console message to come up indicating that we have

59
02:28.040 --> 02:28.840
a neighborhood

60
02:28.840 --> 02:30.440
now with dot 62.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:28.840 --> 02:30.440
now with dot 62.

61
02:30.440 --> 02:32.000
And that may take just a minute.

62
02:32.000 --> 02:33.000
And there it is.

63
02:33.000 --> 02:34.000
All right, fantastic.

64
02:34.000 --> 02:37.940
So now if we were to exit out of configuration mode here on the Cisco device

65
02:37.940 --> 02:38.560
into a show

66
02:38.560 --> 02:43.810
IP BGP summary and press enter, it's going to show us that we've got two BGP

67
02:43.810 --> 02:45.120
neighbors.

68
02:45.120 --> 02:48.720
And as far as over here on the far right, as far as how many prefixes we've

69
02:48.720 --> 02:49.160
learned

70
02:49.160 --> 02:51.440
from those neighbors, we have learned zero.

71
02:51.440 --> 02:55.980
And that's because by default, the actual gateway zero isn't advertising any

72
02:55.980 --> 02:57.280
routes via

73
02:57.280 --> 02:59.400
BGP yet over to us.

74
02:59.400 --> 03:03.830
And we could also look from the perspective of the gateway zero and see what
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
02:59.400 --> 03:03.830
And we could also look from the perspective of the gateway zero and see what

75
03:03.830 --> 03:04.600
the BGP status

76
03:04.600 --> 03:06.080
is from its perspective.

77
03:06.080 --> 03:09.430
So let's make a road trip over to our tier zero gateway at the CLI and we'll

78
03:09.430 --> 03:10.320
take a look.

79
03:10.320 --> 03:15.160
So I've just connected over via SH to our edge one edge transport node.

80
03:15.160 --> 03:17.440
And from here, let's do a get gateways.

81
03:17.440 --> 03:19.840
And here is our services router right there.

82
03:19.840 --> 03:21.880
It is VRF number four.

83
03:21.880 --> 03:24.080
So we just type in VR for press enter.

84
03:24.080 --> 03:27.850
That's one of the easiest ways of working with and seeing the details regarding

85
03:27.850 --> 03:28.120
that

86
03:28.120 --> 03:29.280
services router.

87
03:29.280 --> 03:32.450
So from here, if we did a get space in a question mark, if we scroll up here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:29.280 --> 03:32.450
So from here, if we did a get space in a question mark, if we scroll up here,

88
03:32.450 --> 03:33.240
there's an option

89
03:33.240 --> 03:34.240
for BGP.

90
03:34.240 --> 03:37.200
So we'll type in get space BGP space question mark.

91
03:37.200 --> 03:40.790
And then we have an option for neighbor, we'll type that in as well, a space

92
03:40.790 --> 03:41.920
question mark

93
03:41.920 --> 03:44.120
and let's use summary and press enter.

94
03:44.120 --> 03:47.300
But a Bing, but a boom, we have a neighborhood ship with this device at dot 121

95
03:47.300 --> 03:47.520
.

96
03:47.520 --> 03:50.040
This is from edge one from the services router there.

97
03:50.040 --> 03:53.800
And we are currently not learning any prefixes or networks from that neighbor.

98
03:53.800 --> 03:57.960
And we're also not advertising any prefixes as of yet to that neighbor.

99
03:57.960 --> 04:01.670
So regarding our game plan, as far as configuring the external BGP component
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
03:57.960 --> 04:01.670
So regarding our game plan, as far as configuring the external BGP component

100
04:01.670 --> 04:02.960
here, that is done.

101
04:02.960 --> 04:08.420
We now have BGP neighborhoods between this external device and the edge one, we

102
04:08.420 --> 04:08.840
also

103
04:08.840 --> 04:11.240
have one between ourselves and edge two.

104
04:11.240 --> 04:16.120
So effectively, we've also just verified that external BGP neighborhood ship.

105
04:16.120 --> 04:17.120
So fantastic.

106
04:17.120 --> 04:22.190
So our next logical step then is to start advertising some routes via BGP

107
04:22.190 --> 04:23.040
between these

108
04:23.040 --> 04:24.040
peers.

109
04:24.040 --> 04:27.040
And so we're going to start off based on our game plan by advertising some

110
04:27.040 --> 04:27.560
routes from

111
04:27.560 --> 04:30.520
the tier zero gateway up to this BGP speaker.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
04:27.560 --> 04:30.520
the tier zero gateway up to this BGP speaker.

112
04:30.520 --> 04:32.080
And we'll do that in the next video.

113
04:32.080 --> 04:34.080
I'll see you there in just a moment.