WEBVTT

1
00:00.000 --> 00:07.040
So our final step here is going to be to jump in and verify that everything is

2
00:07.040 --> 00:08.800
working as we expect.

3
00:08.800 --> 00:14.400
So we'll verify our control connections and our routing on Azure R1.

4
00:14.400 --> 00:18.680
And then of course, we have to verify that we have connectivity all the way

5
00:18.680 --> 00:20.880
from on-prem workstation 1,

6
00:20.880 --> 00:25.800
all the way out to Azure workstation 1, the machine that we built at the

7
00:25.800 --> 00:27.200
beginning of this skill.

8
00:27.200 --> 00:30.400
So let's jump into the command line and do some verification.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:27.200 --> 00:30.400
So let's jump into the command line and do some verification.

9
00:30.400 --> 00:38.340
So the first thing we want to look at here on Azure R1 is we'll do a show SD-W

10
00:38.340 --> 00:39.600
AN control connections.

11
00:39.600 --> 00:45.170
Now this of course is a very wide command. So let's go ahead and zoom out a

12
00:45.170 --> 00:46.080
little bit here.

13
00:46.080 --> 00:50.880
This makes it of course a little bit difficult to read, but you should be able

14
00:50.880 --> 00:51.520
to read it on

15
00:51.520 --> 00:56.590
your local system. What we're really looking for here is that we currently have

16
00:56.590 --> 00:58.000
a DTLS connection up

17
00:58.000 --> 01:04.940
with vSmart, vBond and vManage. The next thing we want to check is we'll do a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:58.000 --> 01:04.940
with vSmart, vBond and vManage. The next thing we want to check is we'll do a

18
01:04.940 --> 01:06.960
show SD-WAN OMP

19
01:06.960 --> 01:12.830
peers. What we can see here is that we have one OMP neighborhood up with our v

20
01:12.830 --> 01:14.320
Smart controller.

21
01:14.320 --> 01:19.530
This of course would be perfectly normal. The vSmart controller remember acts a

22
01:19.530 --> 01:20.080
bit like a

23
01:20.080 --> 01:25.150
BGP route reflector. So it collects all of the information about the available

24
01:25.150 --> 01:25.680
routes

25
01:25.680 --> 01:30.530
and then disseminates that out to all of the edge routers. So in this case,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:25.680 --> 01:30.530
and then disseminates that out to all of the edge routers. So in this case,

26
01:30.530 --> 01:31.280
since we only have

27
01:31.280 --> 01:36.350
one controller, we would only have the one neighbor ship. We can also verify

28
01:36.350 --> 01:37.120
the routes.

29
01:37.120 --> 01:44.580
The most important route we're looking for here is the 10.10.10.0/24. That's

30
01:44.580 --> 01:45.200
the on-prem

31
01:45.200 --> 01:51.690
network available through on-prem R1 and R2. Notice that we also have a route

32
01:51.690 --> 01:53.840
for 10.20.10.0.

33
01:53.840 --> 01:58.960
That's actually our AWS network. We're not really dealing with that in this

34
01:58.960 --> 02:00.240
skill. However,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:58.960 --> 02:00.240
skill. However,

35
02:00.240 --> 02:04.560
notice that we have the routes for it nonetheless. So these are the routes that

36
02:04.560 --> 02:05.280
we're learning through

37
02:05.280 --> 02:11.630
OMP. If we do a show VRF, we can zoom back in on that a little bit. We see that

38
02:11.630 --> 02:13.040
we do in fact have

39
02:13.040 --> 02:20.940
VRF 10 and our Gigabit 2 interface is in that VRF as it should be. And finally,

40
02:20.940 --> 02:21.600
let's do a show

41
02:21.600 --> 02:27.440
IP route for VRF 10. And what we're seeing here is that we have an M route

42
02:27.440 --> 02:28.640
indicating that it's

43
02:28.640 --> 02:37.700
learned from OMP for the 10.10.10.0/24 as well as those networks from the AWS
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
02:28.640 --> 02:37.700
learned from OMP for the 10.10.10.0/24 as well as those networks from the AWS

44
02:37.700 --> 02:40.080
environment site 20,

45
02:40.080 --> 02:47.120
which is 10.20.10.0/24. So we see that we've learned all of our routing. So if

46
02:47.120 --> 02:47.760
this is all

47
02:47.760 --> 02:53.470
working correctly, let's verify our end-to-end connectivity. So hopping over

48
02:53.470 --> 02:54.880
here to workstation

49
02:54.880 --> 03:02.300
one, which is the on-prem workstation, let's do a ping for 10.30.10.100. And
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:54.880 --> 03:02.300
one, which is the on-prem workstation, let's do a ping for 10.30.10.100. And

50
03:02.300 --> 03:04.000
what we're going to see

51
03:04.000 --> 03:09.170
is this is not going to work. The reason this is not going to work is the

52
03:09.170 --> 03:10.480
default gateway

53
03:10.480 --> 03:17.840
on the Azure side is not correct. The workstation is still pointing to

54
03:17.840 --> 03:19.600
Microsoft's internet gateway

55
03:19.600 --> 03:26.580
rather than pointing to our C8000V. So in order to fix that, we have to jump

56
03:26.580 --> 03:28.160
back in to the Azure

57
03:28.160 --> 03:34.660
dashboard. So here in Microsoft Azure, I've actually gone to the home tab. And
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
03:28.160 --> 03:34.660
dashboard. So here in Microsoft Azure, I've actually gone to the home tab. And

58
03:34.660 --> 03:36.400
I actually have an entry

59
03:36.400 --> 03:41.640
here for route tables. If you don't have an entry here for route tables, you

60
03:41.640 --> 03:42.880
can again search for

61
03:42.880 --> 03:46.180
it in the box up at the top. But we're just going to go ahead and click on

62
03:46.180 --> 03:46.880
route tables.

63
03:46.880 --> 03:52.710
And what we want to do is create a route table. This is going to be for our SD

64
03:52.710 --> 03:53.840
WAN resource group

65
03:54.800 --> 04:01.200
in the same region. And I'm just going to call this subnet 10, because that's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
03:54.800 --> 04:01.200
in the same region. And I'm just going to call this subnet 10, because that's

66
04:01.200 --> 04:01.920
the subnet. This

67
04:01.920 --> 04:06.070
is going to be the routing table for. Let's go ahead and say review and create

68
04:06.070 --> 04:07.760
and then create.

69
04:07.760 --> 04:14.000
Once this has been deployed, let's go to the resource over here on the left, we

70
04:14.000 --> 04:15.040
'll open up settings,

71
04:15.040 --> 04:21.640
we'll go to routes, and we're going to add a route. The route name, we can

72
04:21.640 --> 04:23.040
simply call it default.

73
04:23.840 --> 04:29.220
For the destination type, we'll do an IP address. The destination is going to

74
04:29.220 --> 04:30.240
be the default.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
04:29.220 --> 04:30.240
be the default.

75
04:30.240 --> 04:35.680
For the next top, we want to choose a virtual appliance. And we want to put in

76
04:35.680 --> 04:36.240
our virtual

77
04:36.240 --> 04:42.500
appliance address. That of course is the address of the C8000V. Let's go ahead

78
04:42.500 --> 04:43.440
and hit add.

79
04:43.440 --> 04:49.820
Now that we have add, let's click subnets. We're going to associate this with

80
04:49.820 --> 04:50.800
subnet 10.

81
04:51.600 --> 04:57.160
We'll hit OK. This has been updated. So let's go back to the command line. We

82
04:57.160 --> 04:57.840
can see here

83
04:57.840 --> 05:04.150
that after just a few seconds, it now begins to ping. So now we have end-to-end
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

83
04:57.840 --> 05:04.150
that after just a few seconds, it now begins to ping. So now we have end-to-end

84
05:04.150 --> 05:05.280
connectivity

85
05:05.280 --> 05:13.620
through VPN 10. Everything is working as we designed. So in this video, we

86
05:13.620 --> 05:14.720
simply verified

87
05:14.720 --> 05:18.730
that everything is working as we designed. We have all of our control

88
05:18.730 --> 05:20.960
connections and OMP peers

89
05:20.960 --> 05:27.670
up on Azure R1. And we have full end-to-end connectivity from on-prem work

90
05:27.670 --> 05:28.800
station one

91
05:28.800 --> 05:34.390
all the way out to Azure workstation one, which we deployed earlier. So this is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
05:28.800 --> 05:34.390
all the way out to Azure workstation one, which we deployed earlier. So this is

92
05:34.390 --> 05:35.600
in fact working

93
05:35.600 --> 05:40.130
as we designed. So that concludes everything that we need to cover in this

94
05:40.130 --> 05:42.160
skill, except for the

95
05:42.160 --> 05:47.400
challenge. In this challenge, we're simply going to have you deploy a redundant

96
05:47.400 --> 05:47.920
router

97
05:47.920 --> 05:54.240
into Microsoft Azure to act as a backup to Azure R1. So go ahead and give that

98
05:54.240 --> 05:55.040
a shot.

99
05:55.040 --> 06:03.840
And I'll see you on the solution video on the other side.