WEBVTT

1
00:00.000 --> 00:05.000
So for our final step, we want to jump in and do some verification.

2
00:05.000 --> 00:10.000
So let's start off on the command line of GCP R1.

3
00:10.000 --> 00:13.000
We'll start by verifying our control connections.

4
00:13.000 --> 00:16.000
We'll then verify our routing table.

5
00:16.000 --> 00:19.000
And then we'll jump over to our on-prem workstation

6
00:19.000 --> 00:22.000
and verify that we have connectivity.

7
00:22.000 --> 00:26.540
So let's go ahead and jump in and make sure that everything is working the way

8
00:26.540 --> 00:28.000
we expect.

9
00:28.000 --> 00:36.000
So here on GCP R1, let's start by looking at our SDWAN control connections.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.000 --> 00:36.000
So here on GCP R1, let's start by looking at our SDWAN control connections.

10
00:36.000 --> 00:39.000
This, of course, is a rather wide command.

11
00:39.000 --> 00:41.000
So I want to zoom out a little bit on this.

12
00:41.000 --> 00:44.000
It unfortunately makes it a little bit difficult to read,

13
00:44.000 --> 00:47.000
but it should be very readable on your local screen.

14
00:47.000 --> 00:52.000
The main thing we're looking for is that we have a DTLS peer

15
00:52.000 --> 00:57.000
with the VSmart controller, VBond, and VManage.

16
00:57.000 --> 01:01.000
So all of our control connections look to be up and functional.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:57.000 --> 01:01.000
So all of our control connections look to be up and functional.

17
01:01.000 --> 01:05.000
We'll also take a look at our SDWAN OMP peers.

18
01:05.000 --> 01:10.000
We see here that we have one OMP peer up with the VSmart controller.

19
01:10.000 --> 01:12.000
That would be correct.

20
01:12.000 --> 01:17.000
Remember that we only create an OMP peer with the smart controllers

21
01:17.000 --> 01:21.000
because they are acting sort of like BGP route reflectors

22
01:21.000 --> 01:25.000
in that they collect all the routes from the other edge devices

23
01:25.000 --> 01:30.000
and then disseminate that information out to the other edges.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
01:30.000 --> 01:34.000
So in this case, since we only have one VSmart controller,

25
01:34.000 --> 01:37.000
we would only expect to see one peering.

26
01:37.000 --> 01:40.000
We can also verify the OMP routes.

27
01:40.000 --> 01:43.000
This is going to start off by showing us a legend

28
01:43.000 --> 01:47.040
and then it's going to show us all of the information that we have learned

29
01:47.040 --> 01:48.000
through OMP.

30
01:48.000 --> 01:53.000
Now, the thing we care about the most right now is the on-prem route,

31
01:53.000 --> 01:59.000
which is the 10.10.10.0/24, and we can see that we have that.

32
01:59.000 --> 02:04.000
Now, we also have routes from 10.20 and 10.30.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:59.000 --> 02:04.000
Now, we also have routes from 10.20 and 10.30.

33
02:04.000 --> 02:09.230
Those are actually the AWS environment and the Microsoft Azure environment,

34
02:09.230 --> 02:11.000
respectfully.

35
02:11.000 --> 02:15.190
So we could reach them as well, but right now we're just focusing on getting to

36
02:15.190 --> 02:17.000
the on-prem device.

37
02:17.000 --> 02:21.000
We could also verify our VPN by doing a show VRF.

38
02:21.000 --> 02:24.000
For this command, we can zoom in a little bit again.

39
02:24.000 --> 02:30.990
Notice that we have a VRF 10 representing our VPN and our gigabit two interface
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
02:24.000 --> 02:30.990
Notice that we have a VRF 10 representing our VPN and our gigabit two interface

40
02:30.990 --> 02:34.000
is in that VRF as it should be.

41
02:34.000 --> 02:40.000
We can, of course, also verify a show IP route for VRF 10.

42
02:40.000 --> 02:46.960
And we can see all of those OMP routes have been installed into this VRF for

43
02:46.960 --> 02:48.000
the VPN.

44
02:48.000 --> 02:56.940
Again, most importantly, the 10.10.10.0/24 with two possible paths, one through

45
02:56.940 --> 03:01.000
on-prem R1, and the other one through on-prem R2.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
02:56.940 --> 03:01.000
on-prem R1, and the other one through on-prem R2.

46
03:01.000 --> 03:07.720
So now that our routing looks good here on GCP R1, let's jump over to the on-

47
03:07.720 --> 03:12.000
prem workstation and see if we actually have reachability.

48
03:12.000 --> 03:18.000
So let's go ahead and ping the 10.40.10.100, which is our workstation.

49
03:18.000 --> 03:21.000
And what we see is that it's not actually working.

50
03:21.000 --> 03:25.860
And this would be because remember that the workstation is still pointing its

51
03:25.860 --> 03:33.000
default gateway to the Google Internet gateway, not to our C8000V.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
03:25.860 --> 03:33.000
default gateway to the Google Internet gateway, not to our C8000V.

52
03:33.000 --> 03:38.000
So what we need to do is we need to update our routing in Google Cloud.

53
03:38.000 --> 03:44.250
So in Google Cloud, we want to go to our menu, we want to go to VPC network,

54
03:44.250 --> 03:46.000
and we want to go to routes.

55
03:46.000 --> 03:50.180
This is going to start by showing us our effective routes, but we want to

56
03:50.180 --> 03:52.000
actually modify the routes.

57
03:52.000 --> 03:55.000
So we want to go to route management.

58
03:55.000 --> 03:58.000
Under route management, we're going to create a route.

59
03:58.000 --> 04:00.000
We can just call this default.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
04:00.000 --> 04:03.000
For the network, it is going to be the client network.

61
04:03.000 --> 04:05.000
So that part's correct.

62
04:05.000 --> 04:07.000
It is going to be a static route.

63
04:07.000 --> 04:11.000
For the destination IPV for range, it's of course going to be the default.

64
04:11.000 --> 04:16.260
And for the next hop, we want to click on the drop down and we'll specify the

65
04:16.260 --> 04:18.000
IP address of an instance.

66
04:18.000 --> 04:24.000
For the next hop, it's 10.40.10.2.

67
04:24.000 --> 04:29.000
Because remember that dot two is the address given to our catalyst 8000V.

68
04:29.000 --> 04:31.000
Let's go ahead and hit create.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
04:29.000 --> 04:31.000
Let's go ahead and hit create.

69
04:31.000 --> 04:35.740
Now that we successfully have the route, let's jump back over to the command

70
04:35.740 --> 04:36.000
line.

71
04:36.000 --> 04:39.000
And we see that it's already working.

72
04:39.000 --> 04:45.010
So now we have a successful connection from our on-prem devices all the way

73
04:45.010 --> 04:47.000
into Google Cloud.

74
04:47.000 --> 04:51.000
So in this video, we just did some verification.

75
04:51.000 --> 04:57.000
We verified our control connections and our routing tables on GCP R1.

76
04:57.000 --> 05:01.190
And then of course, we came over here to our workstation and verified that our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
04:57.000 --> 05:01.190
And then of course, we came over here to our workstation and verified that our

77
05:01.190 --> 05:05.000
reachability all the way in to GCP workstation one

78
05:05.000 --> 05:07.000
is functional.

79
05:07.000 --> 05:10.890
Had to make a little bit of a routing change for the workstation, but now it's

80
05:10.890 --> 05:12.000
up and running.

81
05:12.000 --> 05:17.130
So that concludes everything we need to cover in this skill, except for the

82
05:17.130 --> 05:18.000
challenge.

83
05:18.000 --> 05:22.890
For this challenge, we're simply going to have you deploy a redundant router

84
05:22.890 --> 05:24.000
into Google Cloud

85
05:24.000 --> 05:29.000
and then verify that our routing is actually using both paths.

86
05:29.000 --> 05:31.000
So go ahead and give that a shot.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
05:29.000 --> 05:31.000
So go ahead and give that a shot.

87
05:31.000 --> 05:34.400
and I'll see you in the solution video on the other side.

88
05:34.400 --> 05:44.400
[BLANK_AUDIO]