WEBVTT

1
00:00.000 --> 00:06.440
So now that we've verified our environment in SD-WAN Manager,

2
00:06.440 --> 00:09.080
now let's jump into the command line.

3
00:09.080 --> 00:13.620
Now, for this video, I'm going to be focusing primarily on

4
00:13.620 --> 00:18.300
on-prem router one and our local on-site workstation

5
00:18.300 --> 00:20.840
that's trying to get to the various servers

6
00:20.840 --> 00:23.040
out behind our cloud providers.

7
00:23.040 --> 00:27.040
Keep in mind, however, that we could also jump into the various routers

8
00:27.040 --> 00:30.800
at the cloud providers, do the same tests from there,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:27.040 --> 00:30.800
at the cloud providers, do the same tests from there,

9
00:30.800 --> 00:33.880
and of course, make sure you keep these commands handy

10
00:33.880 --> 00:38.440
as we go through the upcoming skills to do your verifications there as well.

11
00:38.440 --> 00:42.280
So let's jump into the command line and take a look at some useful commands

12
00:42.280 --> 00:44.600
to make sure our environment's functional.

13
00:44.600 --> 00:51.360
So we'll jump into the command line here on on-prem R1,

14
00:51.360 --> 00:56.440
and as you can see, I do have the font size set rather small on this.

15
00:56.440 --> 01:00.040
That's going to unfortunately make this difficult to read.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:56.440 --> 01:00.040
That's going to unfortunately make this difficult to read.

16
01:00.040 --> 01:05.040
However, you'll see that based on these outputs, we sort of have to.

17
01:05.040 --> 01:08.240
Now, again, the most important thing here is learning the commands,

18
01:08.240 --> 01:12.040
getting an idea of the output, and when you do them on your local screen

19
01:12.040 --> 01:16.180
while performing the labs, you should be able to read these commands perfectly

20
01:16.180 --> 01:16.640
fine.

21
01:16.640 --> 01:21.440
But the first one we're going to take a look at is show SD-WAN control

22
01:21.440 --> 01:22.640
connections.

23
01:22.640 --> 01:25.840
This will show us the connections out to the various controllers.

24
01:25.840 --> 01:29.640
So that means we're just going to have the connection to the V-Smart,

25
01:29.640 --> 01:31.840
the V-Bond, and the V-Manage.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:29.640 --> 01:31.840
the V-Bond, and the V-Manage.

26
01:31.840 --> 01:35.440
So it's just going to be that one connection to each of our controllers.

27
01:35.440 --> 01:39.440
Of course, we only have the one V-Smart in this environment.

28
01:39.440 --> 01:44.840
But we can see here the peer type, the protocol, the peer system IP address,

29
01:44.840 --> 01:50.440
what site it's in, the domain ID, the public and private IP addresses.

30
01:50.440 --> 01:53.840
Now, for some of these, you can see these are internal addresses

31
01:53.840 --> 01:58.840
because I'm at the location of the V-Smart and the V-Manage.

32
01:58.840 --> 02:01.840
That's the same place that on-prem R1 is.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:58.840 --> 02:01.840
That's the same place that on-prem R1 is.

33
02:01.840 --> 02:05.840
However, V-Bond is behind a different address.

34
02:05.840 --> 02:07.840
We talked about this earlier.

35
02:07.840 --> 02:13.840
So that's actually the outside address where the V-Bond server is located.

36
02:13.840 --> 02:16.840
That's also why we have it protected.

37
02:16.840 --> 02:21.840
And of course, the most important thing is we see that the current state is up.

38
02:21.840 --> 02:28.840
Another really good command is the show SD-WAN IPsec Outbound Connections.

39
02:28.840 --> 02:32.840
This is going to show us all of the connections out to the other routers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
02:28.840 --> 02:32.840
This is going to show us all of the connections out to the other routers.

40
02:32.840 --> 02:37.840
And of course, the external destination IP addresses.

41
02:37.840 --> 02:42.840
These are all the different devices that are currently deployed at AWS,

42
02:42.840 --> 02:45.840
Azure, and GCP.

43
02:45.840 --> 02:50.840
Of course, there's an opposite to that command where we change the out to an in

44
02:50.840 --> 02:55.830
and we simply see the other side of these connections where those external

45
02:55.830 --> 02:55.840
devices

46
02:55.840 --> 03:00.840
are making connections in here to on-prem router one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:55.840 --> 03:00.840
are making connections in here to on-prem router one.

47
03:00.840 --> 03:04.840
So again, both of these give us really good information about our connections.

48
03:04.840 --> 03:10.840
They're source and destination ports, the SPI number for IPsec.

49
03:10.840 --> 03:15.840
We can see here the tunnel MTUs, things like the T-Lock color.

50
03:15.840 --> 03:19.840
So we see that I'm using all Biz internet for these connections.

51
03:19.840 --> 03:23.840
We can see the encryption being used by IPsec and so on.

52
03:23.840 --> 03:27.840
A lot of good information here to see about our various tunnels.

53
03:27.840 --> 03:31.840
So moving on to routing protocols, specifically OMP,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
03:27.840 --> 03:31.840
So moving on to routing protocols, specifically OMP,

54
03:31.840 --> 03:35.840
we can also do a show SD-WAN OMP peers.

55
03:35.840 --> 03:39.840
Now again, this one, we will only be connected to the V smart controller

56
03:39.840 --> 03:43.840
because that's the one that is acting sort of as a route reflector.

57
03:43.840 --> 03:48.840
Remember that all of our routes go to V smart and then V smart is responsible

58
03:48.840 --> 03:51.840
for disseminating that out to all the other routers.

59
03:51.840 --> 03:55.840
So the fact that we have one connection here to our one V smart would be

60
03:55.840 --> 03:56.840
correct.

61
03:56.840 --> 03:58.840
And of course, we see that it's up.

62
03:58.840 --> 04:01.840
Then of course, we can look at the routes themselves.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
03:58.840 --> 04:01.840
Then of course, we can look at the routes themselves.

63
04:01.840 --> 04:04.840
Now we'll look at the actual routing table in just a moment,

64
04:04.840 --> 04:09.840
but we can actually look at the show SD-WAN OMP route command.

65
04:09.840 --> 04:11.840
And again, this is a wide one.

66
04:11.840 --> 04:17.340
It's going to start off by giving us the legend about what everything below

67
04:17.340 --> 04:17.840
means.

68
04:17.840 --> 04:22.840
And then here we can see the full table of all of the routes it's learning

69
04:22.840 --> 04:25.840
from our various cloud providers.

70
04:25.840 --> 04:33.840
So in this case, the 10.20, the 10.30 and the 10.40 are the client subnets
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
04:25.840 --> 04:33.840
So in this case, the 10.20, the 10.30 and the 10.40 are the client subnets

71
04:33.840 --> 04:39.840
that our servers are on behind AWS, Azure and GCP.

72
04:39.840 --> 04:42.840
These other things are just transit links.

73
04:42.840 --> 04:44.840
Sometimes they show up.

74
04:44.840 --> 04:49.840
Sometimes they don't depending on how the provider implements the network

75
04:49.840 --> 04:51.840
based on cloud on ramp.

76
04:51.840 --> 04:58.840
So for example, all these 10.203s, those are all coming from Microsoft Azure.

77
04:58.840 --> 05:03.840
So as you can see, it sort of leaks a few more of those transit networks,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
04:58.840 --> 05:03.840
So as you can see, it sort of leaks a few more of those transit networks,

78
05:03.840 --> 05:04.840
if you will.

79
05:04.840 --> 05:10.840
The 10.204 is coming specifically from GCP.

80
05:10.840 --> 05:18.840
And notice there's not a 10.202, which is what will be coming from AWS.

81
05:18.840 --> 05:22.840
So AWS doesn't really show the transit links.

82
05:22.840 --> 05:24.840
Microsoft shows a few more.

83
05:24.840 --> 05:26.840
GCP just shows the one.

84
05:26.840 --> 05:33.340
Now, of course, the status column here is what we're going to compare to our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
05:26.840 --> 05:33.340
Now, of course, the status column here is what we're going to compare to our

85
05:33.340 --> 05:33.840
legend

86
05:33.840 --> 05:35.840
up here at the top.

87
05:35.840 --> 05:39.840
But the main thing we want to look at here right now is that all of these are

88
05:39.840 --> 05:41.840
installed in the routing table.

89
05:41.840 --> 05:47.840
But if I do a show IP route, notice it has a static default route to get to the

90
05:47.840 --> 05:48.840
internet.

91
05:48.840 --> 05:53.840
It's own locally connected interface out gigabit one, but that's it.

92
05:53.840 --> 05:58.840
That's because all of these O and P routes are, of course, for a VPN.

93
05:58.840 --> 06:04.840
VPNs get implemented as VRFs in the catalyst.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
05:58.840 --> 06:04.840
VPNs get implemented as VRFs in the catalyst.

94
06:04.840 --> 06:06.840
8,000 V software.

95
06:06.840 --> 06:14.840
So if I were to do a show VRF here, notice that we have a VRF 10, which is our

96
06:14.840 --> 06:15.840
VPN

97
06:15.840 --> 06:16.840
network.

98
06:16.840 --> 06:23.840
So if I were to instead say show IP route for VRF 10, this is where we're

99
06:23.840 --> 06:29.840
going to see all of these routes that are flagged with a lowercase M.

100
06:29.840 --> 06:34.840
Notice that the lowercase M means that it was learned through OMP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
06:29.840 --> 06:34.840
Notice that the lowercase M means that it was learned through OMP.

101
06:34.840 --> 06:39.840
So, of course, aside from the connected and local route, all of these are OMP

102
06:39.840 --> 06:40.840
learned routes.

103
06:40.840 --> 06:45.840
So everything here from a connectivity standpoint looks like it's working

104
06:45.840 --> 06:46.840
perfectly fine.

105
06:46.840 --> 06:51.840
So, of course, that means that we should test connectivity through the entire

106
06:51.840 --> 06:52.840
network.

107
06:52.840 --> 06:54.840
So let's go over to workstation one.

108
06:54.840 --> 06:57.840
We'll ping 10 dot 20 dot 10 dot 100.

109
06:57.840 --> 07:00.840
That's our server on the AWS cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
06:57.840 --> 07:00.840
That's our server on the AWS cloud.

110
07:00.840 --> 07:02.840
So we see that this is working.

111
07:02.840 --> 07:09.840
Notice that our average round trip time is right around 154 milliseconds,

112
07:09.840 --> 07:13.840
which is actually better than what our tunnels were being listed as

113
07:13.840 --> 07:14.840
earlier.

114
07:14.840 --> 07:18.840
So the traffic itself is getting through a little faster.

115
07:18.840 --> 07:22.840
These are still not good round trip times for the ping.

116
07:22.840 --> 07:27.840
However, if we consider the fact that all of this is being virtualized

117
07:27.840 --> 07:31.840
and all this kind of stuff, it's relatively decent, but these are not
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
07:27.840 --> 07:31.840
and all this kind of stuff, it's relatively decent, but these are not

118
07:31.840 --> 07:32.840
good times.

119
07:32.840 --> 07:37.840
But that said, all we need to do is change this 20 to a 30 to test

120
07:37.840 --> 07:39.840
Microsoft Azure.

121
07:39.840 --> 07:44.840
Notice the average ping going out to Azure is right around the same,

122
07:44.840 --> 07:46.840
148 milliseconds.

123
07:46.840 --> 07:50.840
And let's do Google cloud, which is 10 dot 40 network.

124
07:50.840 --> 07:54.840
That would made it through a little bit faster at 113.

125
07:54.840 --> 07:57.840
Again, none of these are very good times.

126
07:57.840 --> 08:02.840
However, we see that they are all functional and they are all working
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

126
07:57.840 --> 08:02.840
However, we see that they are all functional and they are all working

127
08:02.840 --> 08:07.840
and all of these make for really good ways to test our environment

128
08:07.840 --> 08:10.840
once we get cloud on ramp up and running.

129
08:10.840 --> 08:15.840
So now that we've discussed what cloud on ramp is talked about,

130
08:15.840 --> 08:19.840
some of the things we have to change in our environment to get to

131
08:19.840 --> 08:23.840
our environment to get this working and then did a little bit of

132
08:23.840 --> 08:27.840
exploring and verification in a functional environment connected

133
08:27.840 --> 08:29.840
to all three clouds.

134
08:29.840 --> 08:33.840
That pretty much covers what we need to discuss in this skill.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
08:29.840 --> 08:33.840
That pretty much covers what we need to discuss in this skill.

135
08:33.840 --> 08:36.840
That leaves us with just the challenge.

136
08:36.840 --> 08:38.840
So give it a try.

137
08:38.840 --> 08:39.840
Good luck.

138
08:39.840 --> 08:42.840
And I'll see you in the solution video on the other side.

139
08:42.840 --> 08:56.780
♪ ♪