WEBVTT

1
00:00.000 --> 00:04.600
So based on our plan, our next step is to advertise some routes from this BGP

2
00:04.600 --> 00:05.280
router

3
00:05.280 --> 00:07.680
so that our tier zero router could learn about it.

4
00:07.680 --> 00:10.740
So we could advertise routes like the default route or we could advertise

5
00:10.740 --> 00:11.440
specific routes.

6
00:11.440 --> 00:16.250
So as far as verification and testing, let's create a new loopback interface up

7
00:16.250 --> 00:16.760
on this

8
00:16.760 --> 00:22.400
BGP router with the address of 88.88.88.88.88.

9
00:22.400 --> 00:25.510
We'll make that a slash 24-bit network and we'll also go ahead and make that

10
00:25.510 --> 00:26.360
out of loopback

11
00:26.360 --> 00:30.720
8 and then we'll take a further step and we'll advertise that 88.88.88.88.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:26.360 --> 00:30.720
8 and then we'll take a further step and we'll advertise that 88.88.88.88.

12
00:30.720 --> 00:34.480
Etc. in BGP and as a result, that route that 88.88. etc.

13
00:34.480 --> 00:38.520
network should show up as a route on our tier zero gateway.

14
00:38.520 --> 00:42.840
So let's head over to our external BGP router and let's set it up.

15
00:42.840 --> 00:45.640
So here we are at our external router router 673.

16
00:45.640 --> 00:48.600
Let me do a quick check with the interface addresses.

17
00:48.600 --> 00:52.930
Let's show IP interface brief and I'll say please exclude any interfaces that

18
00:52.930 --> 00:53.360
have the

19
00:53.360 --> 00:56.800
word UNA in it for unassigned.

20
00:56.800 --> 01:00.440
And so I just have one interface with an IP address and that's great.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:56.800 --> 01:00.440
And so I just have one interface with an IP address and that's great.

21
01:00.440 --> 01:02.600
So I just want to create a new loopback interface.

22
01:02.600 --> 01:07.460
We'll make interface loopback 88 based on our plan and give it the IP address

23
01:07.460 --> 01:10.440
of 88.88.88.88

24
01:10.440 --> 01:14.460
with a mask of three octets on and one octet off for equivalent of a 24-bit

25
01:14.460 --> 01:15.160
mask press

26
01:15.160 --> 01:17.280
enter, but a Bing, but a boom.

27
01:17.280 --> 01:21.400
We now have this logical loopback address of 88, etc.

28
01:21.400 --> 01:23.960
Now let's advertise that as part of BGP.

29
01:23.960 --> 01:27.240
So we'll type in router BGP 673.

30
01:27.240 --> 01:30.290
That's our autonomous system number and then we'll say network and we'll
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:27.240 --> 01:30.290
That's our autonomous system number and then we'll say network and we'll

31
01:30.290 --> 01:31.640
advertise the 88

32
01:31.640 --> 01:33.920
network and it is a 24-bit network.

33
01:33.920 --> 01:37.680
So we use the keyword mask there and specify it's a 24-bit mask just like that.

34
01:37.680 --> 01:41.040
Then we do a show IP BGP summary and press enter.

35
01:41.040 --> 01:43.720
It's now going to show us here we have our two neighbors.

36
01:43.720 --> 01:46.080
That's edge one and edge two respectively.

37
01:46.080 --> 01:49.740
And if we do a show IP protocols, it's going to show us our dynamic routing

38
01:49.740 --> 01:50.480
protocols.

39
01:50.480 --> 01:53.970
So here are our two neighbors and we're using the routing information from this

40
01:53.970 --> 01:54.360
one.

41
01:54.360 --> 01:57.320
That's because its routes have a shorter AS path.

42
01:57.320 --> 02:01.620
And if we use the command show IP BGP, IBB4 unit cast, that'll show us the BGP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:57.320 --> 02:01.620
And if we use the command show IP BGP, IBB4 unit cast, that'll show us the BGP

43
02:01.620 --> 02:02.160
table.

44
02:02.160 --> 02:04.880
So there is, I just want to verify it made it into BGP.

45
02:04.880 --> 02:08.060
So there's our 88, 88 network and it's currently showing the next top of the

46
02:08.060 --> 02:08.920
whole zeros and

47
02:08.920 --> 02:14.120
that's because that is directly connected here to this router, our 673.

48
02:14.120 --> 02:18.720
So the next question is, is this route yes or no for 88, 88, etc.

49
02:18.720 --> 02:23.120
So we're going up over on our services router for gateway zero.

50
02:23.120 --> 02:26.280
So to verify that, we'll connect once again over to our edge transport node,

51
02:26.280 --> 02:27.240
edge one.

52
02:27.240 --> 02:29.640
Let's do a gate gateways, press enter.

53
02:29.640 --> 02:32.840
And then let's go into VR after number four for our services router.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:29.640 --> 02:32.840
And then let's go into VR after number four for our services router.

54
02:32.840 --> 02:35.520
We'll type in VRF or press enter.

55
02:35.520 --> 02:38.840
And then from here, let's do a get BGP, a space in the question mark.

56
02:38.840 --> 02:43.060
Let's type in neighbor, a space in the question mark, keyword summary and press

57
02:43.060 --> 02:43.160
enter.

58
02:43.160 --> 02:46.800
And that's showing us currently that we are advertising two prefixes as the 10,

59
02:46.800 --> 02:47.200
10, and

60
02:47.200 --> 02:52.000
20 networks and now shows that we are receiving or learning about one prefix.

61
02:52.000 --> 02:55.840
And if we did a get route and press enter here in the services router.

62
02:55.840 --> 02:57.800
So there's our command right there at the top.

63
02:57.800 --> 03:01.080
This is showing us that we now have a BGP learned route.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:57.800 --> 03:01.080
This is showing us that we now have a BGP learned route.

64
03:01.080 --> 03:05.120
That's the B right there, meaning that we learned that via BGP, there's the

65
03:05.120 --> 03:06.120
actual prefix

66
03:06.120 --> 03:09.840
that we learned, the 24 bit network, 88, 88, 88, 88.

67
03:09.840 --> 03:13.690
Here's showing the administrative distance of 20 because that's the admission

68
03:13.690 --> 03:14.160
of distance

69
03:14.160 --> 03:17.160
associated with an external BGP learned route.

70
03:17.160 --> 03:22.100
And there's the next top 192, once you get one dot 121, which is the IP address

71
03:22.100 --> 03:22.320
of our

72
03:22.320 --> 03:23.320
BGP speaker.

73
03:23.320 --> 03:28.410
So from here, we should be able to do a ping to this IP address, 88, 88, 88,

74
03:28.410 --> 03:29.000
and then if

75
03:29.000 --> 03:31.780
we get the host part right, which is also 88, we should be able to get a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
03:29.000 --> 03:31.780
we get the host part right, which is also 88, we should be able to get a

76
03:31.780 --> 03:32.400
response.

77
03:32.400 --> 03:36.680
So we'll do a ping to 88, et cetera, just like that press enter.

78
03:36.680 --> 03:40.120
And sure enough, that's our BGP router on the other side on the physical

79
03:40.120 --> 03:41.120
network responding

80
03:41.120 --> 03:42.120
back to us.

81
03:42.120 --> 03:43.960
So we'll do a control C to stop that.

82
03:43.960 --> 03:47.680
Another way of seeing the routing table would be a get forwarding press center.

83
03:47.680 --> 03:50.880
So here with the get forwarding command, there's our route as well.

84
03:50.880 --> 03:54.110
It's not showing us in this output exactly how it was learned, but the get

85
03:54.110 --> 03:54.880
route command

86
03:54.880 --> 03:56.960
that we did earlier that does show us.

87
03:56.960 --> 04:00.480
We also have options from the graphical user interface and the NSX manager to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:56.960 --> 04:00.480
We also have options from the graphical user interface and the NSX manager to

88
04:00.480 --> 04:01.120
see the routing

89
04:01.120 --> 04:02.360
tables as well.

90
04:02.360 --> 04:05.240
So here in our networking currently, we're looking at our tier zero gateways.

91
04:05.240 --> 04:09.770
We expand that and we scroll down, we go down to the BGP and then click here

92
04:09.770 --> 04:10.240
where it

93
04:10.240 --> 04:13.760
says BGP neighbors, it's going to show us our current status.

94
04:13.760 --> 04:20.750
So currently we have a BGP adjacency with 192.1.1.21, who's in the remote AS of

95
04:20.750 --> 04:21.960
6783?

96
04:21.960 --> 04:25.760
And if we close that and look at the routing table on our tier zero gateway,

97
04:25.760 --> 04:26.200
one way of

98
04:26.200 --> 04:28.720
doing that would be to go back to our network topology.

99
04:28.720 --> 04:30.040
So there's our topology.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
04:28.720 --> 04:30.040
So there's our topology.

100
04:30.040 --> 04:31.360
Here's our tier zero gateway.

101
04:31.360 --> 04:34.320
If we go ahead and click on that over here on the right, if we had download the

102
04:34.320 --> 04:34.840
routing

103
04:34.840 --> 04:38.090
or forwarding table, another difference there is the routing table should

104
04:38.090 --> 04:38.840
include all the

105
04:38.840 --> 04:39.840
routes it has.

106
04:39.840 --> 04:43.080
Well, the forwarding table is the actual routes that it's going to use.

107
04:43.080 --> 04:45.780
So the thing of the forwarding table, like the best of the best, the actual

108
04:45.780 --> 04:46.240
routes we're

109
04:46.240 --> 04:47.240
going to use.

110
04:47.240 --> 04:49.420
So if you want to download those or look at them, we can click right here and

111
04:49.420 --> 04:50.000
it's asking,

112
04:50.000 --> 04:51.600
okay, where do you want to pull these from?

113
04:51.600 --> 04:54.400
Because we have several devices that have that information.

114
04:54.400 --> 04:58.200
For example, we have it on edge one, we've got a replica of that over on edge

115
04:58.200 --> 04:58.680
two.

116
04:58.680 --> 04:59.680
Where do you want to see it?

117
04:59.680 --> 05:02.870
So we'll go ahead and use the drop down and let's go ahead and pull it from
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
04:59.680 --> 05:02.870
So we'll go ahead and use the drop down and let's go ahead and pull it from

118
05:02.870 --> 05:03.440
edge one and

119
05:03.440 --> 05:04.920
click on download.

120
05:04.920 --> 05:09.100
So it downloaded it to my management computer as a CSV and here are the routes

121
05:09.100 --> 05:09.720
which are

122
05:09.720 --> 05:13.240
including the IPv4 routes and also the IPv6 routes.

123
05:13.240 --> 05:16.760
So there's our default route that we are learning via OSPF.

124
05:16.760 --> 05:20.520
Here's the route to the 88 network that we're now learning here through BGP and

125
05:20.520 --> 05:20.720
the other

126
05:20.720 --> 05:22.040
routes that we looked at previously.

127
05:22.040 --> 05:32.040
[BLANK_AUDIO]