WEBVTT

1
00:00.000 --> 00:02.000
All right, so the first step in our game plan

2
00:02.000 --> 00:05.280
is to verify our existing topology that won't take too long.

3
00:05.280 --> 00:08.280
Let's take a look at the routing table here on our Tier 0 gateway.

4
00:08.280 --> 00:09.880
And one of the easiest ways of doing that

5
00:09.880 --> 00:13.320
would be to go to an SSH session over to one of our edge nodes

6
00:13.320 --> 00:16.960
and look at the routing table for that Tier 0 gateway from the edge node.

7
00:16.960 --> 00:18.080
So let's start there.

8
00:18.080 --> 00:21.400
Also, before we jump into the CLI, if we go to networking here in the NSX

9
00:21.400 --> 00:22.240
manager

10
00:22.240 --> 00:26.000
and then take a look at our network topology and we zoom in here,

11
00:26.000 --> 00:30.080
we double click on our Tier 0 gateway, it'll show us the fabric view.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:26.000 --> 00:30.080
we double click on our Tier 0 gateway, it'll show us the fabric view.

12
00:30.080 --> 00:32.280
And here we can just confirm and make it a little bit bigger.

13
00:32.280 --> 00:36.080
Here we can confirm that for this Tier 0 gateway 0,

14
00:36.080 --> 00:39.200
that we're using Edge 1, which is currently active and Edge 2,

15
00:39.200 --> 00:40.400
which is currently standby.

16
00:40.400 --> 00:43.800
So we're going to make an SSH session over to Edge 1

17
00:43.800 --> 00:46.240
to verify our connectivity to that external segment

18
00:46.240 --> 00:48.200
and also to verify the current routing table.

19
00:48.200 --> 00:48.960
So here's Edge 1.

20
00:48.960 --> 00:51.360
Let's do a get gateways and press Enter.

21
00:51.360 --> 00:54.200
So here is our services router right here.

22
00:54.200 --> 00:55.600
That's VRF number 4.

23
00:55.600 --> 01:00.880
And then here is the distributed router for our Tier 0 gateway right here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:55.600 --> 01:00.880
And then here is the distributed router for our Tier 0 gateway right here,

24
01:00.880 --> 01:02.200
this row right here.

25
01:02.200 --> 01:04.640
Also, let me open up a second window to this Edge device.

26
01:04.640 --> 01:08.760
I'd like to do a few commands from the VRF number 1, which is our distributed

27
01:08.760 --> 01:09.200
router,

28
01:09.200 --> 01:13.200
and also some commands from our services router, which is VRF 4.

29
01:13.200 --> 01:15.040
So here in Edge 1, I've got two windows open.

30
01:15.040 --> 01:18.680
And I'm going to go ahead and type a command down here of get gateways, press

31
01:18.680 --> 01:19.080
Enter.

32
01:19.080 --> 01:22.480
And then that's going to serve it up to both of my SSH sessions here

33
01:22.480 --> 01:24.800
to the NSX CLI on the Edge.

34
01:24.800 --> 01:28.440
So up here at the top, let me go ahead and go into VRF 1.

35
01:28.440 --> 01:30.200
And that's our distributed router.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:28.440 --> 01:30.200
And that's our distributed router.

36
01:30.200 --> 01:33.520
So we'll go ahead and type in VRF space 1, press Enter.

37
01:33.520 --> 01:35.560
And there's the prompt to reflect that right there.

38
01:35.560 --> 01:40.100
And then on the second window here, let's go into VRF 4, which is our services

39
01:40.100 --> 01:40.720
router.

40
01:40.720 --> 01:45.280
So we'll type VRF not 5, but 4, VRF 4, and press Enter.

41
01:45.280 --> 01:46.920
And there's our prompt there as well.

42
01:46.920 --> 01:50.440
So now if we do commands like get forwarding, I'd like to show you something

43
01:50.440 --> 01:53.440
that's pretty important to realize, and that is that the distributed router

44
01:53.440 --> 01:56.000
and the services router from this output here,

45
01:56.000 --> 01:59.560
they look like they are both sharing a lot of the same routing information.

46
01:59.560 --> 02:03.440
But behind the scenes, there are some addresses that are only applicable,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
01:59.560 --> 02:03.440
But behind the scenes, there are some addresses that are only applicable,

47
02:03.440 --> 02:05.360
for example, to the services router.

48
02:05.360 --> 02:07.000
And that's our from our routing perspective.

49
02:07.000 --> 02:10.920
We can forward packets that need to go to a services router to that device.

50
02:10.920 --> 02:13.440
So if we scroll down in both of these and take a look,

51
02:13.440 --> 02:15.720
so the command is the same, get forwarding on both.

52
02:15.720 --> 02:18.400
But this is VRF 1 at the top and VRF 4 here on the bottom.

53
02:18.400 --> 02:21.400
If I notice the routing perspective looks the same,

54
02:21.400 --> 02:25.760
but there are some commands that are specific to the services router

55
02:25.760 --> 02:28.760
that don't work on the actual distributed router.

56
02:28.760 --> 02:31.400
For example, if we use command get route and press Enter,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:28.760 --> 02:31.400
For example, if we use command get route and press Enter,

57
02:31.400 --> 02:33.400
that doesn't work on the distributed router,

58
02:33.400 --> 02:37.920
but it does work like a champ here on the services router, which is the VRF 4.

59
02:37.920 --> 02:40.320
So we're going to focus on that, let me expand that.

60
02:40.320 --> 02:43.880
And currently here in VRF 4, we have our OSPF-learned route.

61
02:43.880 --> 02:48.880
So the little O there from our previous skill represents an OSPF-learned route.

62
02:48.880 --> 02:52.880
And there is the default administrative distance associated with OSPF.

63
02:52.880 --> 02:56.680
Then we have a couple routes that are connected to our T1 gateways,

64
02:56.680 --> 02:59.040
which have been advertised up to our Tier Zero gateway.

65
02:59.040 --> 03:02.120
And that's why we know about them here at our Tier Zero gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
02:59.040 --> 03:02.120
And that's why we know about them here at our Tier Zero gateway.

66
03:02.120 --> 03:04.880
And then we have an OSPF-learned route that we did as an example

67
03:04.880 --> 03:08.240
of sharing routes from a physical router, running OSPF,

68
03:08.240 --> 03:11.720
and advertising that route over here to our Tier Zero gateway.

69
03:11.720 --> 03:16.200
The next two are the router to router subnets between Tier Zero and gateway A

70
03:16.200 --> 03:17.320
and gateway B.

71
03:17.320 --> 03:18.920
And then we have our backplane network.

72
03:18.920 --> 03:21.930
Think of it like the logical subnet that we're going to use to communicate

73
03:21.930 --> 03:22.720
between

74
03:22.720 --> 03:26.200
our distributed router and services router here on gateway zero.

75
03:26.200 --> 03:29.320
And then we have a directly connected network 192.1.81,

76
03:29.320 --> 03:32.400
which is our connection to that physical external network segment
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:29.320 --> 03:32.400
which is our connection to that physical external network segment

77
03:32.400 --> 03:34.720
and it's using Uplink 279 for that one.

78
03:34.720 --> 03:37.880
So from here, if we wanted to verify we have reachability to that address,

79
03:37.880 --> 03:41.200
we could go ahead and do a ping from this services router VRF.

80
03:41.200 --> 03:44.320
So I'll ping to that address and that's looking good.

81
03:44.320 --> 03:47.760
And let's also go ahead and ping the IP address of our default gateway,

82
03:47.760 --> 03:50.000
which is our physical router on the physical networks.

83
03:50.000 --> 03:53.880
We'll do a ping to 192.168.1.1.

84
03:53.880 --> 03:55.120
And that looks good.

85
03:55.120 --> 03:56.760
So I'll do a control C there.

86
03:56.760 --> 03:59.600
And also in this VRF, for the services router,

87
03:59.600 --> 04:02.000
if we did a get a space in the question mark,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:59.600 --> 04:02.000
if we did a get a space in the question mark,

88
04:02.000 --> 04:04.560
we have several options, including route, which we looked at earlier.

89
04:04.560 --> 04:07.480
We also have an option to look at BGP information.

90
04:07.480 --> 04:10.680
So here if we type in get BGP space question mark,

91
04:10.680 --> 04:12.840
and let's go ahead and ask for neighbor information,

92
04:12.840 --> 04:15.920
space question mark and summary and press enter,

93
04:15.920 --> 04:20.280
it's now showing us a summary of all the BGP neighbors it knows about.

94
04:20.280 --> 04:24.600
So currently our tier zero gateway has no BGP neighbors configured yet.

95
04:24.600 --> 04:26.240
And as a result, we have no neighbors.

96
04:26.240 --> 04:29.190
But what we have done is verified our basic connectivity to this external

97
04:29.190 --> 04:29.520
network.

98
04:29.520 --> 04:31.320
And I'd actually like to do one more thing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
04:29.520 --> 04:31.320
And I'd actually like to do one more thing.

99
04:31.320 --> 04:35.560
And that is I'd like to verify that our tier zero gateway can ping

100
04:35.560 --> 04:38.360
the IP address of .121, which will be,

101
04:38.360 --> 04:41.840
once it's all configured, will be our external BGP neighbor.

102
04:41.840 --> 04:43.520
So let's ping that as well as a test.

103
04:43.520 --> 04:47.040
So do a ping to 192.168.1.121.

104
04:47.040 --> 04:49.520
And survey says we're getting a response.

105
04:49.520 --> 04:51.400
Fantastic. So we'll do a control C.

106
04:51.400 --> 04:54.280
And that concludes our verification of the current infrastructure.

107
04:54.280 --> 04:57.480
All right. So with our existing topology verified,

108
04:57.480 --> 05:01.160
our next logical step then is to configure our tier zero gateway
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
04:57.480 --> 05:01.160
our next logical step then is to configure our tier zero gateway

109
05:01.160 --> 05:05.240
and tell it that it belongs in a ton of system 777.

110
05:05.240 --> 05:07.680
We're also going to go ahead and tell it that we have a peer

111
05:07.680 --> 05:10.360
that we wanted to connect to at .121,

112
05:10.360 --> 05:12.720
who's in the autonomous system of 673.

113
05:12.720 --> 05:14.880
So we'll do all of that in the next video.

114
05:14.880 --> 05:16.440
I'll see you there in just a moment.