WEBVTT

1
00:00.000 --> 00:04.070
So one aspect that's really critical to success oftentimes is to plan out stuff

2
00:04.070 --> 00:04.960
before you do it.

3
00:04.960 --> 00:08.340
In that way, we're not just haphazardly putting in commands, we actually have a

4
00:08.340 --> 00:08.720
strategy.

5
00:08.720 --> 00:13.210
So as far as our game plan for BGP, let's go ahead and set up our Tier Zero

6
00:13.210 --> 00:13.520
Gateway,

7
00:13.520 --> 00:19.040
which is currently connected to this 192.168.1 network. Also, as a reminder,

8
00:19.040 --> 00:23.280
anytime we're connecting our NSX-Routed environment to an external network that

9
00:23.280 --> 00:27.780
connectivity between the NSX and the physical world, that's going to use these

10
00:27.780 --> 00:28.400
services

11
00:28.400 --> 00:32.400
of one or more of our edge nodes. So if we're doing active standby or active
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.400 --> 00:32.400
of one or more of our edge nodes. So if we're doing active standby or active

12
00:32.400 --> 00:32.800
active,

13
00:32.800 --> 00:36.720
either way, we're going to be using the services of our edge node or nodes for

14
00:36.720 --> 00:37.760
that functionality.

15
00:37.760 --> 00:41.240
So we've already put the connectivity to the physical network in place a couple

16
00:41.240 --> 00:42.080
of skills ago,

17
00:42.080 --> 00:46.880
and now regarding BGP, let's do the following. This little router right here

18
00:46.880 --> 00:47.600
that we used with

19
00:47.600 --> 00:51.860
OSPF, it's at .1. And actually, we had the scenes that say 4 to 8 firewall that

20
00:51.860 --> 00:52.560
's doing layer three

21
00:52.560 --> 00:57.280
services, but we have a .1 address on that 192.168.1 network. So as far as our

22
00:57.280 --> 00:58.080
game plan goes,

23
00:58.080 --> 01:02.420
we'd be wise to take a moment and just verify our existing topology that we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:58.080 --> 01:02.420
we'd be wise to take a moment and just verify our existing topology that we

24
01:02.420 --> 01:03.040
really do still

25
01:03.040 --> 01:07.160
have access to this external network segment. So our first order of business is

26
01:07.160 --> 01:07.520
going to be

27
01:07.520 --> 01:11.230
verifying the existing topology. And then once we've verified that, let's go

28
01:11.230 --> 01:11.840
ahead and start the

29
01:11.840 --> 01:15.820
configuration for our Tier Zero Gateway and set it up for BGP and for the

30
01:15.820 --> 01:17.600
autonomous system number.

31
01:17.600 --> 01:20.460
Let's use autonomous system because it's just to my lab environment. Let's use

32
01:20.460 --> 01:21.200
autonomous system

33
01:21.200 --> 01:26.980
number 777. Does it feel lucky? I hope so because it's getting 777. Now, as

34
01:26.980 --> 01:27.360
part of that

35
01:27.360 --> 01:30.880
configuration behind the scenes, it's really going to be leveraging our Edge 1
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:27.360 --> 01:30.880
configuration behind the scenes, it's really going to be leveraging our Edge 1

36
01:30.880 --> 01:31.360
and Edge 2

37
01:31.360 --> 01:34.930
transport nodes for any BGP connectivity that we're going to have with the

38
01:34.930 --> 01:35.920
outside world.

39
01:35.920 --> 01:42.960
So just as I note, we're going to use Edge 1 at .61 and Edge 2 at .62 for the

40
01:42.960 --> 01:43.920
actual pairing.

41
01:43.920 --> 01:48.080
And for the external BGP neighborhood to the external network, because we've

42
01:48.080 --> 01:48.480
already used

43
01:48.480 --> 01:52.440
this device once, let's go ahead and let me add a new device to our topology.

44
01:52.440 --> 01:52.960
So I'm going to go

45
01:52.960 --> 01:57.580
ahead and put a device right here. And this is going to be a Cisco device that

46
01:57.580 --> 01:59.120
's running BGP.

47
01:59.120 --> 02:03.450
So for BGP on this device, let's go ahead and use BGP with the autonomous
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:59.120 --> 02:03.450
So for BGP on this device, let's go ahead and use BGP with the autonomous

48
02:03.450 --> 02:06.640
system number 6783.

49
02:06.640 --> 02:11.120
So as far as our game plan, we'll go ahead and peer with that Cisco device. And

50
02:11.120 --> 02:12.000
its IP address

51
02:12.000 --> 02:19.680
is .121 on this external network. So we'll say peer with .121 on that 192.1.81

52
02:19.680 --> 02:20.240
network.

53
02:20.240 --> 02:25.840
And also that that peer is going to be an autonomous system 6783. So our Tier 0

54
02:25.840 --> 02:26.880
gateway will be an

55
02:26.880 --> 02:31.380
AS777. The device we're peering with with BGP is going to be an autonomous
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:26.880 --> 02:31.380
AS777. The device we're peering with with BGP is going to be an autonomous

56
02:31.380 --> 02:32.720
system 6783,

57
02:32.720 --> 02:35.640
which means that once we have that BGP neighborhood in place, it'll be an

58
02:35.640 --> 02:37.440
external BGP

59
02:37.440 --> 02:42.410
neighborhood. And any routes we learn should have the associated administrative

60
02:42.410 --> 02:42.880
distance

61
02:42.880 --> 02:46.880
that's associated with an external BGP learned route. Now in BGP, it takes two

62
02:46.880 --> 02:47.840
to tango. So

63
02:47.840 --> 02:52.920
once we configure the Tier 0 gateway and tell it that it's in AS777 and that it

64
02:52.920 --> 02:53.680
's got an external

65
02:53.680 --> 02:57.710
neighbor that we want to peer up with, we also need to configure the external B

66
02:57.710 --> 02:58.640
GP neighbor. So

67
02:58.640 --> 03:02.770
let's say on external BGP config. And I'll put a little arrow here saying we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:58.640 --> 03:02.770
let's say on external BGP config. And I'll put a little arrow here saying we're

68
03:02.770 --> 03:03.600
going to peer

69
03:03.600 --> 03:08.020
back with this Tier 0 gateway, which is at autonomous system 777. So then once

70
03:08.020 --> 03:08.640
we've set up that

71
03:08.640 --> 03:12.820
BGP relationship between Tier 0 and this BGP speaker up here, we should

72
03:12.820 --> 03:14.000
probably pause for a

73
03:14.000 --> 03:18.420
moment and just verify that the E BGP neighbor ship exists and that is

74
03:18.420 --> 03:19.680
functional. And we can

75
03:19.680 --> 03:24.010
verify the external BGP neighbor ship, both here at the Tier 0 gateway by

76
03:24.010 --> 03:24.880
connecting to one of our

77
03:24.880 --> 03:28.530
edge nodes and looking at the information there for the services router

78
03:28.530 --> 03:29.920
function. And we can also

79
03:29.920 --> 03:33.730
take a look at the BGP neighbor ship from the perspective of the external
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
03:29.920 --> 03:33.730
take a look at the BGP neighbor ship from the perspective of the external

80
03:33.730 --> 03:34.560
router. In this case,

81
03:34.560 --> 03:38.710
it's going to be a Cisco device running BGP in autonomous system 6783. So once

82
03:38.710 --> 03:39.520
we verified our

83
03:39.520 --> 03:43.340
external BGP neighbor ship between these two devices, I propose then that we

84
03:43.340 --> 03:44.640
start to add routes that

85
03:44.640 --> 03:49.200
we're going to advertise inside of BGP to each other. So let's start off with

86
03:49.200 --> 03:50.480
advertising routes

87
03:50.480 --> 03:54.430
from Gateway 0, that's our Tier 0 gateway. And we'll verify those shared routes

88
03:54.430 --> 03:55.440
show up here

89
03:55.440 --> 03:59.000
inside this Cisco BGP router. And then secondly, let's also do it the other

90
03:59.000 --> 03:59.760
direction. We'll

91
03:59.760 --> 04:03.530
advertise some routes from our external router and make sure those routes show
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:59.760 --> 04:03.530
advertise some routes from our external router and make sure those routes show

92
04:03.530 --> 04:04.560
up here in the

93
04:04.560 --> 04:08.210
routing table on our services router at our Tier 0 gateway. So as we dig into

94
04:08.210 --> 04:08.960
this game plan,

95
04:08.960 --> 04:12.560
looks pretty logical step by step. So in our next video, let's take a moment

96
04:12.560 --> 04:13.600
and just verify our

97
04:13.600 --> 04:17.360
existing topology as we begin to execute our game plan.