WEBVTT

1
00:00.000 --> 00:07.120
So now we are finally up to the point where we're actually able to add our

2
00:07.120 --> 00:08.400
routers or

3
00:08.400 --> 00:11.720
edge devices into our environment.

4
00:11.720 --> 00:16.600
So of course we're going to be using the Cisco Catalyst 8000V.

5
00:16.600 --> 00:23.990
There are a ton of devices that Cisco of course supports as edge devices in SD-

6
00:23.990 --> 00:24.640
WAN.

7
00:24.640 --> 00:27.480
And that list is growing all the time.

8
00:27.480 --> 00:31.760
So the best thing to do of course is to check out Cisco's website to check the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:27.480 --> 00:31.760
So the best thing to do of course is to check out Cisco's website to check the

9
00:31.760 --> 00:32.760
latest compatible

10
00:32.760 --> 00:35.400
devices with SD-WAN.

11
00:35.400 --> 00:40.960
Now that said, it's time for us to configure our on-prem router one to join our

12
00:40.960 --> 00:41.560
SD-WAN

13
00:41.560 --> 00:44.940
environment and become our first edge device.

14
00:44.940 --> 00:50.480
So let's jump into the command line on router one.

15
00:50.480 --> 00:54.530
One of the first things we're going to have to do here on router one, much like

16
00:54.530 --> 00:54.920
what we

17
00:54.920 --> 00:59.940
had to do on our controllers is we need to get the certificate for our

18
00:59.940 --> 01:01.840
certificate authority,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:59.940 --> 01:01.840
certificate authority,

19
01:01.840 --> 01:06.280
in other words V-Manage over here onto router one.

20
01:06.280 --> 01:09.520
Now so far we've been doing that with SCP.

21
01:09.520 --> 01:15.680
Unfortunately SCP is not one of our built-in commands on iOS Xe.

22
01:15.680 --> 01:20.990
Now just as a note, there is something called the guest shell here on iOS Xe

23
01:20.990 --> 01:22.080
which we could

24
01:22.080 --> 01:28.200
enable, it's a Linux sub-shell and we could use that to do the SCP and so on.

25
01:28.200 --> 01:32.890
However, there may be an easier way, it's really your choice but let me show
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:28.200 --> 01:32.890
However, there may be an easier way, it's really your choice but let me show

26
01:32.890 --> 01:33.440
you the

27
01:33.440 --> 01:37.880
alternative method to get this certificate onto router one.

28
01:37.880 --> 01:41.800
What we want to do is we want to go back to our notepad where we have our

29
01:41.800 --> 01:42.680
certificate

30
01:42.680 --> 01:44.120
saved.

31
01:44.120 --> 01:50.010
And what we're going to do is turn this certificate into a tickle script that

32
01:50.010 --> 01:51.080
we can paste into

33
01:51.080 --> 01:52.080
the routers.

34
01:52.080 --> 01:55.040
So we really only have to add a few lines.

35
01:55.040 --> 01:59.840
The first thing we want to do is at the top we're going to add a few lines.

36
01:59.840 --> 02:04.840
The first thing is to send the router into tickle shell.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:59.840 --> 02:04.840
The first thing is to send the router into tickle shell.

37
02:04.840 --> 02:09.440
The next thing is to do a put to open a file.

38
02:09.440 --> 02:12.320
Then we're going to open this with a bracket.

39
02:12.320 --> 02:17.160
We say open and we're going to give it a file name in quotes.

40
02:17.160 --> 02:23.440
So this is going to be boot flash colon CA dot CRT.

41
02:23.440 --> 02:28.880
We're going to close the quotes and we're going to tell it to write that file

42
02:28.880 --> 02:29.120
out and

43
02:29.120 --> 02:31.280
close the brackets.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
02:29.120 --> 02:31.280
close the brackets.

44
02:31.280 --> 02:34.280
Then we're going to open a set of braces.

45
02:34.280 --> 02:36.760
This is where the certificate is going to be.

46
02:36.760 --> 02:39.480
And as you can see of course we already have it here.

47
02:39.480 --> 02:45.650
So now we go down to the bottom and after the end certificate we close the

48
02:45.650 --> 02:46.640
brace and

49
02:46.640 --> 02:50.560
we can then tell it to exit out of the tickle shell.

50
02:50.560 --> 02:56.320
Now this is only going to work properly if you paste this all in together.

51
02:56.320 --> 02:58.560
That's why we're doing it in notepad.

52
02:58.560 --> 03:01.560
So then what we want to do is copy all of this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:58.560 --> 03:01.560
So then what we want to do is copy all of this.

53
03:01.560 --> 03:10.880
So we highlight it, we copy it, then we go back to router one and we paste this

54
03:10.880 --> 03:11.720
in.

55
03:11.720 --> 03:17.280
So now if we do a DIR we should see right here that we have this CA dot cert

56
03:17.280 --> 03:17.720
and to make

57
03:17.720 --> 03:20.120
sure it has the proper context.

58
03:20.120 --> 03:24.040
Let's do a more on the CA dot cert so we can look at it and we can see that

59
03:24.040 --> 03:25.440
this now contains

60
03:25.440 --> 03:27.120
our certificate.

61
03:27.120 --> 03:31.640
So now we have the certificate file over here on router one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
03:27.120 --> 03:31.640
So now we have the certificate file over here on router one.

62
03:31.640 --> 03:37.800
The next thing we have to do is change router one to be in controller mode.

63
03:37.800 --> 03:42.500
And this is fairly straightforward, all we do is we say controller mode and you

64
03:42.500 --> 03:42.880
know

65
03:42.880 --> 03:45.440
there's only really three settings here.

66
03:45.440 --> 03:49.440
Disable, enable and reset.

67
03:49.440 --> 03:52.440
We're clearly going for the enable option here.

68
03:52.440 --> 03:54.240
So we're going to say enable.

69
03:54.240 --> 03:57.240
Now it is going to give us a little bit of a warning here.

70
03:57.240 --> 04:01.180
It's telling us that it's going to erase and VRAM which means all of the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:57.240 --> 04:01.180
It's telling us that it's going to erase and VRAM which means all of the

71
04:01.180 --> 04:02.200
configuration

72
04:02.200 --> 04:05.800
is going to be gone and it's going to reload it.

73
04:05.800 --> 04:09.840
So it says make sure the boot variable points to a valid image which it does.

74
04:09.840 --> 04:13.520
This is just a default installation so it's going to be okay.

75
04:13.520 --> 04:18.220
We hit enter and it gives us another warning telling us that the bootstrap

76
04:18.220 --> 04:19.080
config file

77
04:19.080 --> 04:24.520
which is needed for zero day boot is missing and it says do you want to abort.

78
04:24.520 --> 04:29.680
However the default answer is no so it's going to let us do it no problem.

79
04:29.680 --> 04:33.080
This is okay it just means we're going to have to put the initial configuration
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
04:29.680 --> 04:33.080
This is okay it just means we're going to have to put the initial configuration

80
04:33.080 --> 04:33.760
on it

81
04:33.760 --> 04:35.480
after it reboots.

82
04:35.480 --> 04:37.440
So we'll just hit enter.

83
04:37.440 --> 04:41.320
We get disconnected from the device as it reboots.

84
04:41.320 --> 04:45.540
So let's go ahead and connect to the console of router one so we can see what's

85
04:45.540 --> 04:47.280
going on.

86
04:47.280 --> 04:51.000
So here on the console we can see that it is rebooting.

87
04:51.000 --> 04:52.640
This is going to take some time.

88
04:52.640 --> 04:54.760
In fact quite a bit of time.

89
04:54.760 --> 05:00.700
So what we're going to do in the meantime is switch over to vmanage and we'll
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
04:54.760 --> 05:00.700
So what we're going to do in the meantime is switch over to vmanage and we'll

90
05:00.700 --> 05:01.240
add our

91
05:01.240 --> 05:06.600
serial file dot viptela for our authorized device list.

92
05:06.600 --> 05:10.480
So here from the dashboard we'll go to our main menu.

93
05:10.480 --> 05:12.760
We'll go to configuration.

94
05:12.760 --> 05:14.920
We'll go to devices.

95
05:14.920 --> 05:22.520
This time we'll stay here on the WAN edge list and we'll upload the WAN edge

96
05:22.520 --> 05:23.640
list.

97
05:23.640 --> 05:26.280
Here we will browse to our file.

98
05:26.280 --> 05:32.130
We'll choose our serial file dot viptela file, we'll say open, we'll tell it to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
05:26.280 --> 05:32.130
We'll choose our serial file dot viptela file, we'll say open, we'll tell it to

99
05:32.130 --> 05:32.800
validate

100
05:32.800 --> 05:37.880
the uploaded edge list and send this to the controllers.

101
05:37.880 --> 05:43.830
So let's say upload, it says are you sure, we'll say okay, tells us that it

102
05:43.830 --> 05:44.440
uploaded

103
05:44.440 --> 05:49.590
it successfully and it uploaded 30 devices, which is good because that's what

104
05:49.590 --> 05:50.080
we had in

105
05:50.080 --> 05:51.640
our file.

106
05:51.640 --> 05:53.560
Now we hit okay.

107
05:53.560 --> 05:58.550
You see here that we have a success, it pushed that serial list out to all of

108
05:58.550 --> 05:59.640
our devices,

109
05:59.640 --> 06:03.320
our vmanage, our vbond and our vsmart.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
05:59.640 --> 06:03.320
our vmanage, our vbond and our vsmart.

110
06:03.320 --> 06:07.800
So now if we go back, here is our list of devices.

111
06:07.800 --> 06:14.390
Now what we need to do is copy the chassis serial number and the serial number

112
06:14.390 --> 06:15.320
or token.

113
06:15.320 --> 06:18.200
We have to scroll over a little bit to see that.

114
06:18.200 --> 06:22.700
So this serial number or token field and again you'll have to expand it to see

115
06:22.700 --> 06:23.000
the

116
06:23.000 --> 06:24.760
whole thing.

117
06:24.760 --> 06:30.000
But we need to copy this for one of our C8000Vs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
06:30.000 --> 06:35.520
In my case, I'm just going to choose the first 8000V on my list here.

119
06:35.520 --> 06:40.830
So for example, I'm going to copy this right here and I'm going to keep these

120
06:40.830 --> 06:41.520
handy in

121
06:41.520 --> 06:46.120
notepad for the next section where we go to add this in.

122
06:46.120 --> 06:52.120
So once again, you need to copy this token and the corresponding serial number

123
06:52.120 --> 06:53.640
out front

124
06:53.640 --> 06:56.520
and keep those handy in notepad.

125
06:56.520 --> 06:59.160
Then we wait for router one to complete booting.

126
06:59.160 --> 07:04.640
Again, it's going to take some time, probably about five to ten minutes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

126
06:59.160 --> 07:04.640
Again, it's going to take some time, probably about five to ten minutes.

127
07:04.640 --> 07:09.720
So we'll keep these numbers handy and skip ahead till router one is fully

128
07:09.720 --> 07:10.720
booted.

129
07:10.720 --> 07:14.600
So after quite some time, our platform is back up.

130
07:14.600 --> 07:18.170
What we're looking for to make sure that it's fully booted is this line right

131
07:18.170 --> 07:18.720
here where

132
07:18.720 --> 07:21.680
it says all daimens are up.

133
07:21.680 --> 07:26.640
So we also notice that we have some errors here from licensing and things like

134
07:26.640 --> 07:27.280
that.

135
07:27.280 --> 07:29.480
That's going to be perfectly normal at this point.

136
07:29.480 --> 07:33.680
It has no IP addresses, no way to contact the smart licensing server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
07:29.480 --> 07:33.680
It has no IP addresses, no way to contact the smart licensing server.

137
07:33.680 --> 07:37.620
So a lot of these errors during the initial boot can be ignored because it's

138
07:37.620 --> 07:38.440
not configured

139
07:38.440 --> 07:39.440
yet.

140
07:39.440 --> 07:42.430
So let's go ahead and press enter to get started since it just kicked us out of

141
07:42.430 --> 07:43.640
the console.

142
07:43.640 --> 07:48.400
And then we'll log in with the default admin admin.

143
07:48.400 --> 07:52.460
It's going to of course make us change the password just like our controllers

144
07:52.460 --> 07:52.720
did.

145
07:52.720 --> 07:55.680
So we'll put in our typical password we've been using.

146
07:55.680 --> 07:59.200
One, two, three, four QWR.

147
07:59.200 --> 08:02.520
We can see that it successfully set the new password.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

147
07:59.200 --> 08:02.520
We can see that it successfully set the new password.

148
08:02.520 --> 08:05.730
So now that we're up and running, one of the first things we're going to want

149
08:05.730 --> 08:06.360
to do is

150
08:06.360 --> 08:12.440
update that root search chain with the boot flash CA dot cert file that we

151
08:12.440 --> 08:13.080
created a

152
08:13.080 --> 08:14.680
few minutes ago.

153
08:14.680 --> 08:22.090
So the way this works, the command on this platform is request platform

154
08:22.090 --> 08:23.480
software SD

155
08:23.480 --> 08:29.640
WAN root cert chain install and then the path.

156
08:29.640 --> 08:33.640
So boot flash call and CA dot cert.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

156
08:29.640 --> 08:33.640
So boot flash call and CA dot cert.

157
08:33.640 --> 08:38.300
Now this also takes just a few seconds, but notice that it has successfully

158
08:38.300 --> 08:39.000
installed

159
08:39.000 --> 08:41.120
the root certificate chain.

160
08:41.120 --> 08:46.120
So now we can build our basic configuration or our baseline.

161
08:46.120 --> 08:48.920
So the first thing we want to do is go into configuration mode.

162
08:48.920 --> 08:55.200
So conf T except that's not supported once we're in controller mode.

163
08:55.200 --> 09:00.040
Now the good news is when you type conf T it tells you it's not supported and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
08:55.200 --> 09:00.040
Now the good news is when you type conf T it tells you it's not supported and

164
09:00.040 --> 09:00.560
it tells

165
09:00.560 --> 09:05.480
you which command to use, which is config dash transaction.

166
09:05.480 --> 09:09.530
The reason for this is they're sort of forcing you to understand that any

167
09:09.530 --> 09:10.720
configuration you

168
09:10.720 --> 09:17.410
make here on the command line is transactional, meaning anything that SD WAN

169
09:17.410 --> 09:19.000
then pushes down

170
09:19.000 --> 09:24.200
to this router is going to overwrite anything we do here at the CLI.

171
09:24.200 --> 09:29.160
So this is just a temporary config, if you will, we're going to be pushing

172
09:29.160 --> 09:29.960
config down

173
09:29.960 --> 09:32.960
to this device from SD WAN later.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

173
09:29.960 --> 09:32.960
to this device from SD WAN later.

174
09:32.960 --> 09:36.040
So let's go ahead and do it the way they tell us to.

175
09:36.040 --> 09:41.920
So config transaction and then we'll begin with our baseline configuration.

176
09:41.920 --> 09:44.400
So we'll put in our host name.

177
09:44.400 --> 09:47.040
This is on Prem R one.

178
09:47.040 --> 09:50.300
And by the way, we get a lot of messages on the console here and just while we

179
09:50.300 --> 09:51.000
're working,

180
09:51.000 --> 09:52.880
I don't want that to interrupt us.

181
09:52.880 --> 09:57.670
So I'm going to say no logging console, probably not something you would

182
09:57.670 --> 09:58.760
normally want to put

183
09:58.760 --> 09:59.760
on these devices.

184
09:59.760 --> 10:04.080
However, I'm going to put it on just for the sake of us doing the lab.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

184
09:59.760 --> 10:04.080
However, I'm going to put it on just for the sake of us doing the lab.

185
10:04.080 --> 10:08.000
So we're not constantly getting interrupted by console messages.

186
10:08.000 --> 10:10.760
Then let's start configuring our interfaces.

187
10:10.760 --> 10:14.000
So first we have gigabit ethernet one.

188
10:14.000 --> 10:15.600
We'll set the IP address on this.

189
10:15.600 --> 10:19.680
It's two, four dot one eight six dot 19 dot 10.

190
10:19.680 --> 10:21.920
This is a slash 24.

191
10:21.920 --> 10:23.640
We'll bring it up next.

192
10:23.640 --> 10:26.960
We'll configure gigabit ethernet two.

193
10:26.960 --> 10:31.640
Now keep in mind gigabit ethernet two is actually a trunk.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
10:26.960 --> 10:31.640
Now keep in mind gigabit ethernet two is actually a trunk.

194
10:31.640 --> 10:36.400
So all we want to do here is a no shot to bring the interface up.

195
10:36.400 --> 10:44.240
Then we actually want to go into interface gigabit two dot 100 for VLAN 100.

196
10:44.240 --> 10:49.080
We'll set the encapsulation to dot one to 100.

197
10:49.080 --> 10:53.930
And by the way, just a quick note here, when we're in controller mode, the

198
10:53.930 --> 10:55.040
routers actually

199
10:55.040 --> 10:59.920
get a little more picky about the commands you put in.

200
10:59.920 --> 11:06.400
For example, if I back up and I said either two dot one Q, 100, it doesn't like
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

200
10:59.920 --> 11:06.400
For example, if I back up and I said either two dot one Q, 100, it doesn't like

201
11:06.400 --> 11:07.000
it.

202
11:07.000 --> 11:08.360
It gives me an error.

203
11:08.360 --> 11:11.560
And it yells at me saying, I don't know what that is.

204
11:11.560 --> 11:12.840
Oh, okay.

205
11:12.840 --> 11:19.320
But if I go back and I change it to a capital Q, it's perfectly fine.

206
11:19.320 --> 11:23.940
Now if you've been working with iOS and iOS XE for quite some time now, you

207
11:23.940 --> 11:24.560
know that

208
11:24.560 --> 11:31.520
aside from things like names and passwords, iOS is not generally case sensitive
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

208
11:24.560 --> 11:31.520
aside from things like names and passwords, iOS is not generally case sensitive

209
11:31.520 --> 11:31.640
.

210
11:31.640 --> 11:37.720
However, once we're in controller mode, like I said, it gets a little more pick

211
11:37.720 --> 11:38.040
y about

212
11:38.040 --> 11:40.800
exactly how you put commands in.

213
11:40.800 --> 11:44.840
But now of course, this sub interface needs an IP address.

214
11:44.840 --> 11:48.160
This is going to be on the 10 dot 100 dot 10 network.

215
11:48.160 --> 11:52.000
And it's going to be dot one because it's effectively our default gateway.

216
11:52.000 --> 11:55.760
We can exit out of here and now we can put it around.

217
11:55.760 --> 11:59.920
This is if you need a default gateway for this particular network.

218
11:59.920 --> 12:03.280
Once again, everything at this point is on the same network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

218
11:59.920 --> 12:03.280
Once again, everything at this point is on the same network.

219
12:03.280 --> 12:05.200
So I don't really need to do this.

220
12:05.200 --> 12:09.880
However, the default gateway in my environment towards the internet is 204 dot

221
12:09.880 --> 12:11.120
186 dot 19

222
12:11.120 --> 12:12.720
dot one.

223
12:12.720 --> 12:16.780
The next thing we want to do is configure the system, which are more SD when

224
12:16.780 --> 12:18.760
related commands.

225
12:18.760 --> 12:22.040
This is where we'll set things like the system IP.

226
12:22.040 --> 12:25.520
So again, we'll make this 10 dot 255 dot 255.

227
12:25.520 --> 12:28.640
Since this is routed one, we'll make this dot one.

228
12:28.640 --> 12:30.600
This is at headquarters.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

228
12:28.640 --> 12:30.600
This is at headquarters.

229
12:30.600 --> 12:33.360
So we'll set the site ID to 100.

230
12:33.360 --> 12:35.680
We need to set the organization name.

231
12:35.680 --> 12:38.800
And of course, this has to match everything else.

232
12:38.800 --> 12:41.640
So we'll put in our organization name.

233
12:41.640 --> 12:43.840
We have to tell it where our V bond server is.

234
12:43.840 --> 12:48.560
Remember, that's a 10 dot 100 dot 10 dot 216.

235
12:48.560 --> 12:51.940
Just to make sure everything's going OK so far, let's just do a commit since we

236
12:51.940 --> 12:52.240
've put

237
12:52.240 --> 12:54.720
quite a few things in already.

238
12:54.720 --> 12:56.680
So the commit was successful.

239
12:56.680 --> 13:00.360
Now let's go ahead and configure our SD WAN parameters.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

239
12:56.680 --> 13:00.360
Now let's go ahead and configure our SD WAN parameters.

240
13:00.360 --> 13:06.300
So the first thing we want to do is go into interface gigabit ethernet 2 dot

241
13:06.300 --> 13:07.520
100.

242
13:07.520 --> 13:14.480
We want to set this as a tunnel interface and set the encapsulation to IP sec.

243
13:14.480 --> 13:19.960
We also need to make an interface tunnel 2.

244
13:19.960 --> 13:22.360
Now it doesn't necessarily have to be tunnel 2.

245
13:22.360 --> 13:27.120
I'm just making it tunnel 2 because it's related to gigabit ethernet 2.

246
13:27.120 --> 13:30.920
However, one thing is very critical here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

246
13:27.120 --> 13:30.920
However, one thing is very critical here.

247
13:30.920 --> 13:33.880
You have to make it a capital T.

248
13:33.880 --> 13:36.960
So interface tunnel 2.

249
13:36.960 --> 13:42.780
For this, we're going to tell it to do IP unnumbered off gigabit ethernet 2 dot

250
13:42.780 --> 13:44.000
100.

251
13:44.000 --> 13:50.640
We're also going to set that as our tunnel source.

252
13:50.640 --> 13:54.680
And we're going to set the tunnel mode to SD WAN.

253
13:54.680 --> 13:59.160
We'll commit those changes, exit configuration.

254
13:59.160 --> 14:05.040
And now what we're going to do is actually add this to the SD WAN environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

254
13:59.160 --> 14:05.040
And now what we're going to do is actually add this to the SD WAN environment.

255
14:05.040 --> 14:16.250
So the way this works, we say to request platform software SD WAN V edge cloud

256
14:16.250 --> 14:17.840
activate

257
14:17.840 --> 14:19.800
chassis number.

258
14:19.800 --> 14:25.630
This is where we need to paste in the chassis number that we got from V manage

259
14:25.630 --> 14:26.640
earlier.

260
14:26.640 --> 14:28.920
We also have to put in the token.

261
14:28.920 --> 14:34.560
Again, you're going to want to copy and paste this from notepad hit enter.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

261
14:28.920 --> 14:34.560
Again, you're going to want to copy and paste this from notepad hit enter.

262
14:34.560 --> 14:37.480
This again will take just a few seconds.

263
14:37.480 --> 14:42.640
It will take a little bit for this router to come online in SD WAN.

264
14:42.640 --> 14:47.960
So at this point, I would probably just wait about five minutes before moving

265
14:47.960 --> 14:48.600
on to the

266
14:48.600 --> 14:49.920
next section.

267
14:49.920 --> 14:51.160
So that's what we're going to do.

268
14:51.160 --> 14:56.610
I'm simply going to pause the video here, wait five minutes, and then we'll

269
14:56.610 --> 14:57.120
move on.

270
14:57.120 --> 14:59.040
So it has been a few minutes.

271
14:59.040 --> 15:06.090
Notice here on the SD WAN overview page, we now have one WAN edge listed as
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

271
14:59.040 --> 15:06.090
Notice here on the SD WAN overview page, we now have one WAN edge listed as

272
15:06.090 --> 15:07.960
being reachable.

273
15:07.960 --> 15:13.550
Now, something else to note here on the dashboard, if we scroll down a little

274
15:13.550 --> 15:14.280
bit, we have this

275
15:14.280 --> 15:17.960
pane called WAN edge health.

276
15:17.960 --> 15:23.040
Notice that right now it says zero devices, no data to display.

277
15:23.040 --> 15:25.680
That's because this just came online.

278
15:25.680 --> 15:29.780
This will take a little bit of time to gather and collect information to have

279
15:29.780 --> 15:30.600
some history
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

279
15:29.780 --> 15:30.600
some history

280
15:30.600 --> 15:32.160
to display here.

281
15:32.160 --> 15:37.640
So we'll see this filled in a little bit later as we move through the course.

282
15:37.640 --> 15:39.560
We'll see this begin to populate.

283
15:39.560 --> 15:44.800
In fact, we'll come back and revisit this after I let this sit for some time.

284
15:44.800 --> 15:48.760
But in the meantime, some other places that we can check.

285
15:48.760 --> 15:54.400
If we go to our menu, we can go to monitor devices.

286
15:54.400 --> 15:59.750
Now this is going to show us all of the devices that's in that authorized

287
15:59.750 --> 16:01.000
device list.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

287
15:59.750 --> 16:01.000
device list.

288
16:01.000 --> 16:02.720
So that's not very convenient.

289
16:02.720 --> 16:06.450
We could scroll down through here, of course, and find the one we're looking

290
16:06.450 --> 16:06.720
for.

291
16:06.720 --> 16:10.920
But probably the easiest thing to do if you're not troubleshooting, of course,

292
16:10.920 --> 16:11.320
if you're

293
16:11.320 --> 16:15.280
troubleshooting, you want to see all the devices and see if they're down.

294
16:15.280 --> 16:18.470
But if we're just trying to see what's in our inventory and working, we can

295
16:18.470 --> 16:18.960
click on

296
16:18.960 --> 16:21.440
this little pop out on the side.

297
16:21.440 --> 16:25.780
We could click on, for example, reachable and say, just show me the things that

298
16:25.780 --> 16:27.160
are up.

299
16:27.160 --> 16:28.800
This will filter the list.

300
16:28.800 --> 16:34.380
And now it's only showing us our three controllers and our new on-prem router
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

300
16:28.800 --> 16:34.380
And now it's only showing us our three controllers and our new on-prem router

301
16:34.380 --> 16:35.800
one, which it sees

302
16:35.800 --> 16:38.160
as a C8000V.

303
16:38.160 --> 16:41.200
It sees that the site ID is set to 100.

304
16:41.200 --> 16:43.600
It has its system IP.

305
16:43.600 --> 16:44.600
Health is good.

306
16:44.600 --> 16:46.880
Reachability is good.

307
16:46.880 --> 16:52.360
It's connected to one V smart controller and it just came up.

308
16:52.360 --> 16:59.240
Once again, CPU load, memory utilization, these will fill in over time.

309
16:59.240 --> 17:03.320
So if we were to come back and look at this later, this would be populated.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

309
16:59.240 --> 17:03.320
So if we were to come back and look at this later, this would be populated.

310
17:03.320 --> 17:07.240
It just takes a little bit of time to gather that history.

311
17:07.240 --> 17:10.240
Now of course, we can also check this at the command line.

312
17:10.240 --> 17:12.920
So let's go back over to router one.

313
17:12.920 --> 17:14.280
Now we did get timed out here.

314
17:14.280 --> 17:16.400
So let's log back in.

315
17:16.400 --> 17:21.260
We are still on the console because as of right now, I did not configure my out

316
17:21.260 --> 17:22.400
of band management

317
17:22.400 --> 17:23.400
network.

318
17:23.400 --> 17:26.320
We'll do that later in the course.

319
17:26.320 --> 17:31.100
But for now, we're here on on-prem router one and a couple of commands we can
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

319
17:26.320 --> 17:31.100
But for now, we're here on on-prem router one and a couple of commands we can

320
17:31.100 --> 17:31.560
do for

321
17:31.560 --> 17:33.080
verification.

322
17:33.080 --> 17:40.560
Let's do a show SD-WAN control and we can do local properties.

323
17:40.560 --> 17:46.200
This will give us some information about this device connecting in to SD-WAN.

324
17:46.200 --> 17:49.320
So we can see things like it's connected as a V edge.

325
17:49.320 --> 17:52.360
We see our organization name is correct.

326
17:52.360 --> 17:56.080
We see that the root CA chain status is installed.

327
17:56.080 --> 17:58.600
The certificate status is installed.

328
17:58.600 --> 17:59.600
It's valid.

329
17:59.600 --> 18:02.880
We see the valid dates for the certificate.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

329
17:59.600 --> 18:02.880
We see the valid dates for the certificate.

330
18:02.880 --> 18:07.210
Then a little bit further down, we can see things like our site ID, our domain

331
18:07.210 --> 18:08.080
ID, the

332
18:08.080 --> 18:10.360
protocol, the system IP.

333
18:10.360 --> 18:12.800
We see that chassis number.

334
18:12.800 --> 18:15.800
We see our assigned serial number.

335
18:15.800 --> 18:20.140
And of course, a lot more information here that can be useful when troubles

336
18:20.140 --> 18:21.080
hooting.

337
18:21.080 --> 18:24.840
Way down here at the bottom, we also see connections.

338
18:24.840 --> 18:30.640
But we can see that using a slightly different command instead of saying local
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

338
18:24.840 --> 18:30.640
But we can see that using a slightly different command instead of saying local

339
18:30.640 --> 18:30.720
properties.

340
18:30.720 --> 18:32.600
We could just say connections.

341
18:32.600 --> 18:35.600
This is an easier way to get that information.

342
18:35.600 --> 18:38.320
And this way we get to see all of the connections.

343
18:38.320 --> 18:42.800
Now we've seen this before in the previous video.

344
18:42.800 --> 18:47.750
However, once again, if we really want to see this in its true format, we are

345
18:47.750 --> 18:48.200
going to

346
18:48.200 --> 18:54.920
have to zoom out quite a bit to actually get everything on the page.

347
18:54.920 --> 18:58.040
Both of these outputs are again very wide.

348
18:58.040 --> 19:03.040
So in order for it not to overlap and make it almost unreadable, we have to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

348
18:58.040 --> 19:03.040
So in order for it not to overlap and make it almost unreadable, we have to

349
19:03.040 --> 19:03.840
zoom it out

350
19:03.840 --> 19:09.080
to the point that, well, it's not unreadable, but it's more challenging.

351
19:09.080 --> 19:13.720
So here again is that same information that we saw on our controllers in the

352
19:13.720 --> 19:14.400
previous

353
19:14.400 --> 19:19.460
video, where we see again the peer type protocols, their various IP addresses

354
19:19.460 --> 19:21.400
and port numbers,

355
19:21.400 --> 19:26.640
organizational names, the uptime, and that it's actually up.

356
19:26.640 --> 19:29.240
So this is working properly.

357
19:29.240 --> 19:33.850
So what I'm going to do now is I'm going to let this sit for just a little
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

357
19:29.240 --> 19:33.850
So what I'm going to do now is I'm going to let this sit for just a little

358
19:33.850 --> 19:34.600
while, and

359
19:34.600 --> 19:39.620
then I'll come back and show you those fields that needed some time to populate

360
19:39.620 --> 19:39.840
just so

361
19:39.840 --> 19:44.560
you can get an idea what they're supposed to look like once they've populated.

362
19:44.560 --> 19:48.160
So it's been a little while that this device has been up and running now.

363
19:48.160 --> 19:50.160
So I did a refresh.

364
19:50.160 --> 19:56.240
And as we can see, the CPU load and the memory utilization are now filled in.

365
19:56.240 --> 20:00.980
Furthermore, if we click on the host name over here, it'll bring up a more
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

365
19:56.240 --> 20:00.980
Furthermore, if we click on the host name over here, it'll bring up a more

366
20:00.980 --> 20:02.200
detailed view

367
20:02.200 --> 20:06.080
of this device, and it'll tell us things like reboots.

368
20:06.080 --> 20:09.800
There's of course one where we just put it into controller mode.

369
20:09.800 --> 20:14.180
It'll show us things like the modules, the temperature sensors, USB ports,

370
20:14.180 --> 20:15.480
power supplies,

371
20:15.480 --> 20:19.740
fans, those, of course, are going to be not applicable because this is running

372
20:19.740 --> 20:20.440
in a virtual

373
20:20.440 --> 20:21.720
environment.

374
20:21.720 --> 20:27.840
So the router has no visibility into things like power supplies and fans.

375
20:27.840 --> 20:31.720
You would have to instead monitor the server that it's running on, of course.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

375
20:27.840 --> 20:31.720
You would have to instead monitor the server that it's running on, of course.

376
20:31.720 --> 20:36.400
Also note down here under the CPU and memory, we get some nice charts.

377
20:36.400 --> 20:40.560
And if you want, you can actually put your mouse over any one of these points

378
20:40.560 --> 20:40.760
and it

379
20:40.760 --> 20:45.310
will give you more detailed information on what was happening at that exact

380
20:45.310 --> 20:45.720
date and

381
20:45.720 --> 20:46.720
time.

382
20:46.720 --> 20:51.360
We see the detailed CPU utilization and memory utilization.

383
20:51.360 --> 20:55.050
So again, you can just scroll through here and get the information at different

384
20:55.050 --> 20:55.480
points

385
20:55.480 --> 20:56.800
in time.

386
20:56.800 --> 21:01.420
So this of course can be very useful information for troubleshooting if these
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

386
20:56.800 --> 21:01.420
So this of course can be very useful information for troubleshooting if these

387
21:01.420 --> 21:02.880
things are constantly

388
21:02.880 --> 21:04.800
high.

389
21:04.800 --> 21:10.240
So this takes care of adding our on-prem router one into our environment.

390
21:10.240 --> 21:15.150
And it also concludes everything that we need to cover in this skill, except of

391
21:15.150 --> 21:15.640
course

392
21:15.640 --> 21:17.120
for the challenge.

393
21:17.120 --> 21:21.430
So go ahead, work your way through the challenge, and I'll see you in the

394
21:21.430 --> 21:22.840
solution video after

395
21:22.840 --> 21:24.000
you complete the challenge.

396
21:24.000 --> 21:34.000
[BLANK_AUDIO]