WEBVTT

1
00:00.000 --> 00:07.800
So now that our devices are added into VManage and we have certificates issued

2
00:07.800 --> 00:09.280
to each one,

3
00:09.280 --> 00:13.920
we can now authenticate our VPN0 tunnels.

4
00:13.920 --> 00:17.310
These are the control tunnels that are going to be formed between VSmart

5
00:17.310 --> 00:18.200
controllers and

6
00:18.200 --> 00:19.360
so on.

7
00:19.360 --> 00:22.440
So in order to do this, we have to do a little bit of configuration.

8
00:22.440 --> 00:26.550
It's actually not very much, but the real thing is we want to make sure that

9
00:26.550 --> 00:27.240
the devices

10
00:27.240 --> 00:32.210
then bring up their control tunnels and everything is being learned by VManage
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.240 --> 00:32.210
then bring up their control tunnels and everything is being learned by VManage

11
00:32.210 --> 00:33.120
properly.

12
00:33.120 --> 00:37.770
So let's go ahead and make that small configuration change and verify that

13
00:37.770 --> 00:39.280
everything's working

14
00:39.280 --> 00:42.440
as it should.

15
00:42.440 --> 00:48.570
So let's begin here on the overview or dashboard page for SDWAN and a few

16
00:48.570 --> 00:49.600
things we want to

17
00:49.600 --> 00:51.000
take a look at.

18
00:51.000 --> 00:57.240
First, under certificate status, notice that we now have zero warnings.

19
00:57.240 --> 01:00.800
I didn't necessarily particularly point this out before.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:57.240 --> 01:00.800
I didn't necessarily particularly point this out before.

20
01:00.800 --> 01:04.870
However, every time we've come in here up till now, there has been a

21
01:04.870 --> 01:06.120
certificate warning

22
01:06.120 --> 01:07.280
here.

23
01:07.280 --> 01:12.320
That's now cleared with all of the proper certificates being installed.

24
01:12.320 --> 01:19.030
Also note that over here under controllers, even though we've added VBond and V

25
01:19.030 --> 01:19.880
Smart, it's

26
01:19.880 --> 01:24.280
still only showing one VManage controller.

27
01:24.280 --> 01:29.880
This is because those devices are not yet properly talking to the system.

28
01:29.880 --> 01:32.440
We can see this a little bit more.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:29.880 --> 01:32.440
We can see this a little bit more.

29
01:32.440 --> 01:41.680
If we go to our menu, we go to configuration, devices, controllers, and notice

30
01:41.680 --> 01:42.560
that VBond

31
01:42.560 --> 01:48.140
and VSmart still have basically no information listed.

32
01:48.140 --> 01:52.700
We don't know their host name, their system IP, their site ID.

33
01:52.700 --> 01:59.140
And most importantly, we can see right here that the device status is not in

34
01:59.140 --> 02:00.000
sync.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
02:00.000 --> 02:03.560
VManage, of course, will always be in sync with itself.

36
02:03.560 --> 02:10.680
So leaving VManage out of it, other devices will not go to the in sync status

37
02:10.680 --> 02:11.440
until their

38
02:11.440 --> 02:16.520
VPN zero interfaces are up as tunnels.

39
02:16.520 --> 02:19.460
So that's of course what we're here to configure.

40
02:19.460 --> 02:23.460
To do this, we need to go over to the command line on the devices.

41
02:23.460 --> 02:28.970
We're going to start this time with VBond just because its configuration is a

42
02:28.970 --> 02:29.540
little

43
02:29.540 --> 02:30.820
bit different.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
02:29.540 --> 02:30.820
bit different.

44
02:30.820 --> 02:35.100
So we'll start on VBond, then we'll configure VManage and VSmart because their

45
02:35.100 --> 02:36.060
configuration

46
02:36.060 --> 02:37.340
is the same.

47
02:37.340 --> 02:41.220
So let's jump over to the command line on VBond.

48
02:41.220 --> 02:47.160
So here on VBond, we're going to configuration mode, we'll go into VPN zero, we

49
02:47.160 --> 02:47.680
'll go into

50
02:47.680 --> 02:53.360
interface, gigabit ethernet zero slash zero, and we'll tell it to use this as a

51
02:53.360 --> 02:55.600
tunnel interface.

52
02:55.600 --> 03:01.800
We'll also set the encapsulation to IPsec and we'll commit and quit.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:55.600 --> 03:01.800
We'll also set the encapsulation to IPsec and we'll commit and quit.

53
03:01.800 --> 03:05.360
Next, let's jump over to VManage.

54
03:05.360 --> 03:07.720
Like I said, this is just a little bit different.

55
03:07.720 --> 03:10.360
We still go into configuration mode.

56
03:10.360 --> 03:17.540
We still go into VPN zero, but this one is going to be interface eth zero.

57
03:17.540 --> 03:22.850
We enable that for the tunnel interface, but we don't have to change the encaps

58
03:22.850 --> 03:23.180
ulation.

59
03:23.180 --> 03:25.140
So we'll commit and quit.

60
03:25.140 --> 03:28.540
And then we do the same thing on VSmart one.

61
03:28.540 --> 03:36.830
So one more time, it's configuration mode VPN zero interface eth zero tunnel
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
03:28.540 --> 03:36.830
So one more time, it's configuration mode VPN zero interface eth zero tunnel

62
03:36.830 --> 03:38.020
interface

63
03:38.020 --> 03:39.860
commit and quit.

64
03:39.860 --> 03:44.960
Now that this is configured, let's go back over to VManage.

65
03:44.960 --> 03:52.020
Notice as soon as we switch back, we already have information on these devices.

66
03:52.020 --> 03:53.880
We've pulled in the host name.

67
03:53.880 --> 03:58.100
So now we know about VBond, VManage and VSmart one.

68
03:58.100 --> 04:01.300
We've pulled in all of the system IP addresses.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
03:58.100 --> 04:01.300
We've pulled in all of the system IP addresses.

69
04:01.300 --> 04:10.140
So we see our 216 for VBond, our 215 for VManage and our 217 for VSmart one.

70
04:10.140 --> 04:14.070
All of them are in the same site ID, of course, which we're using for

71
04:14.070 --> 04:15.180
headquarters.

72
04:15.180 --> 04:21.450
But most importantly, notice that the device status for all of these is now in

73
04:21.450 --> 04:22.100
sync.

74
04:22.100 --> 04:25.240
So this is looking very good.

75
04:25.240 --> 04:30.740
If we go back to our dashboard, you can get there by the way, by going to your
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
04:25.240 --> 04:30.740
If we go back to our dashboard, you can get there by the way, by going to your

76
04:30.740 --> 04:31.840
menu, monitor,

77
04:31.840 --> 04:34.760
overview, if you want to get back there.

78
04:34.760 --> 04:42.720
Notice that now under controllers, we have one VBond, one VSmart and one VMan

79
04:42.720 --> 04:43.560
age.

80
04:43.560 --> 04:47.200
So so far, everything is looking very good.

81
04:47.200 --> 04:51.340
There's also some tools we can use from the command line to make sure that the

82
04:51.340 --> 04:51.920
control

83
04:51.920 --> 04:54.120
connections are up properly.

84
04:54.120 --> 04:57.480
So let's start on VSmart and VManage.

85
04:57.480 --> 05:00.560
Once again, VBond is a slightly different command.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:57.480 --> 05:00.560
Once again, VBond is a slightly different command.

86
05:00.560 --> 05:04.360
So let's start with VSmart and VManage.

87
05:04.360 --> 05:11.160
So here on VSmart, let's do a show, control connections.

88
05:11.160 --> 05:17.120
And as you can see, this is a little bit wide for this particular font size.

89
05:17.120 --> 05:19.600
It's wrapping around quite a bit.

90
05:19.600 --> 05:23.400
If I were to zoom out a little bit.

91
05:23.400 --> 05:28.880
So if we change the font size down like this, we can see that it all fits on

92
05:28.880 --> 05:29.920
one line.

93
05:29.920 --> 05:34.160
Now unfortunately, of course, this makes it rather difficult to read.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
05:29.920 --> 05:34.160
Now unfortunately, of course, this makes it rather difficult to read.

94
05:34.160 --> 05:36.880
This is a very wide output.

95
05:36.880 --> 05:41.380
And of course, it's much more difficult to read when the columns all start

96
05:41.380 --> 05:42.160
getting in

97
05:42.160 --> 05:43.840
or mixed with each other.

98
05:43.840 --> 05:45.440
But what can we see here?

99
05:45.440 --> 05:48.360
We can see what type of peer it is.

100
05:48.360 --> 05:51.400
We can see what peer protocol is being used.

101
05:51.400 --> 05:57.240
We can see those peer system IP addresses, the site ID for that peer, the

102
05:57.240 --> 05:58.840
domain ID, the

103
05:58.840 --> 06:04.030
peer private IP address, the peer private port, the peer public IP address,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
05:58.840 --> 06:04.030
peer private IP address, the peer private port, the peer public IP address,

104
06:04.030 --> 06:04.680
which in

105
06:04.680 --> 06:08.660
this case, the private and the public are the same because we're not doing that

106
06:08.660 --> 06:09.120
within

107
06:09.120 --> 06:10.920
the environment.

108
06:10.920 --> 06:12.320
Same thing with the ports.

109
06:12.320 --> 06:16.580
They're going to be the same because we're not doing port address translation

110
06:16.580 --> 06:16.800
either.

111
06:16.800 --> 06:21.210
We see our organization name, the remote color, which we did not bother to

112
06:21.210 --> 06:22.240
configure on any

113
06:22.240 --> 06:23.400
of these.

114
06:23.400 --> 06:29.150
The current state is up and these have been up for at this point about four

115
06:29.150 --> 06:30.240
minutes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
06:29.150 --> 06:30.240
minutes.

116
06:30.240 --> 06:33.000
So again, it unfortunately gets rather small.

117
06:33.000 --> 06:37.600
However, it is a very nice output with a lot of good information.

118
06:37.600 --> 06:40.640
Let's go do the same thing on V manage.

119
06:40.640 --> 06:43.600
Once again, it's show control connections.

120
06:43.600 --> 06:48.590
And if we zoom out far enough, we can fit everything on one screen without it

121
06:48.590 --> 06:49.280
wrapping

122
06:49.280 --> 06:50.440
around.

123
06:50.440 --> 06:54.920
So again, not necessarily the most convenient output.

124
06:54.920 --> 07:00.440
However, again, if you're in front of the screen looking at it, it is readable.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
06:54.920 --> 07:00.440
However, again, if you're in front of the screen looking at it, it is readable.

125
07:00.440 --> 07:02.680
It just gets a little bit small.

126
07:02.680 --> 07:06.840
Maybe if you have a 40 inch screen, it might be a little bit better.

127
07:06.840 --> 07:11.200
But again, this is just how it gives you the output.

128
07:11.200 --> 07:17.360
Again, good output just maybe could be formatted a little narrower.

129
07:17.360 --> 07:20.000
Let's take a look at this on V bond as well.

130
07:20.000 --> 07:23.720
Again, the command on V bond is a little bit different.

131
07:23.720 --> 07:29.520
This one is show orchestrator connections.

132
07:29.520 --> 07:35.610
But as you can see, it has the same problem with the width of the output
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
07:29.520 --> 07:35.610
But as you can see, it has the same problem with the width of the output

133
07:35.610 --> 07:36.120
because as we

134
07:36.120 --> 07:39.400
can see, it's the exact same output.

135
07:39.400 --> 07:41.000
It's just a different command.

136
07:41.000 --> 07:47.840
We have all of the same columns and everything is still the same information.

137
07:47.840 --> 07:51.320
So the commands a little bit different, but the output's the same.

138
07:51.320 --> 07:55.520
Now, of course, the main takeaway in all of this is all of these control

139
07:55.520 --> 07:56.280
tunnels are

140
07:56.280 --> 08:02.680
up between our V manage, our V smart and our V bond.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

140
07:56.280 --> 08:02.680
up between our V manage, our V smart and our V bond.

141
08:02.680 --> 08:07.400
So now that our VPN zero interfaces are up as tunnels, we can see that

142
08:07.400 --> 08:09.480
everything's connected.

143
08:09.480 --> 08:13.000
It's used our certificates for the authentication.

144
08:13.000 --> 08:17.200
Everything is up and working as it should be as far as the controllers are

145
08:17.200 --> 08:18.080
concerned.

146
08:18.080 --> 08:23.920
Now, of course, our next step is going to be to bring in a WAN edge device.

147
08:23.920 --> 08:28.120
And for that, we're going to use the Cisco catalyst 8000 V.

148
08:28.120 --> 08:30.200
So that's going to be our next step.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
08:28.120 --> 08:30.200
So that's going to be our next step.

149
08:30.200 --> 08:35.450
We're going to take our on-prem router one, which is, of course, a catalyst

150
08:35.450 --> 08:36.720
8000 V.

151
08:36.720 --> 08:41.800
And we're going to convert that from standalone or autonomous mode to

152
08:41.800 --> 08:43.520
controller mode.

153
08:43.520 --> 08:46.320
And then we're going to bring it into our environment.

154
08:46.320 --> 08:49.240
So that's what we're going to do in the next video.

155
08:49.240 --> 08:58.500
[BLANK_AUDIO]