WEBVTT

1
00:00.000 --> 00:08.180
So as we saw in our previous video, we got an error when trying to apply our

2
00:08.180 --> 00:08.880
centralized

3
00:08.880 --> 00:16.640
policy because our controllers are not in vManage or SDWAN Manager mode.

4
00:16.640 --> 00:18.640
But what exactly does that mean?

5
00:18.640 --> 00:24.390
Well what it means is that vManage is not in control of the configuration on

6
00:24.390 --> 00:26.920
our controllers.

7
00:26.920 --> 00:31.620
It's in charge of the configuration on our edge devices because we apply the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:26.920 --> 00:31.620
It's in charge of the configuration on our edge devices because we apply the

8
00:31.620 --> 00:32.200
template

9
00:32.200 --> 00:33.600
to those.

10
00:33.600 --> 00:34.760
Well guess what?

11
00:34.760 --> 00:37.240
This simply means the same thing.

12
00:37.240 --> 00:42.640
We need to apply a template, but this time to our controllers.

13
00:42.640 --> 00:47.870
Right now our controllers just have a basic configuration that we put on when

14
00:47.870 --> 00:48.520
we first

15
00:48.520 --> 00:53.440
built them, but it's not being managed by vManage itself.

16
00:53.440 --> 00:55.840
It's just a static configuration.

17
00:55.840 --> 00:58.960
Now the cool thing is this is very easy to do.

18
00:58.960 --> 01:03.200
All we need to do is take the current configuration that we put on there,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:58.960 --> 01:03.200
All we need to do is take the current configuration that we put on there,

19
01:03.200 --> 01:04.600
convert that to a CLI

20
01:04.600 --> 01:09.360
template, and then just apply that CLI template right back to the controller.

21
01:09.360 --> 01:13.160
So we're not actually changing its configuration in any way.

22
01:13.160 --> 01:18.800
We're just putting that configuration under the control of vManage.

23
01:18.800 --> 01:25.240
That way it can then add these centralized policies to that configuration.

24
01:25.240 --> 01:28.950
So this is a fairly straightforward process, but it is something we have to go

25
01:28.950 --> 01:29.640
through.

26
01:29.640 --> 01:36.910
So let's jump in and get started with putting these controllers into vManage
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
01:29.640 --> 01:36.910
So let's jump in and get started with putting these controllers into vManage

27
01:36.910 --> 01:37.800
mode.

28
01:37.800 --> 01:43.420
So here in SD-WAN Manager, I'm going to start on the Monitor Devices page

29
01:43.420 --> 01:44.160
because before

30
01:44.160 --> 01:48.840
we put this in vManage mode, we want to make sure that our controllers are

31
01:48.840 --> 01:51.120
online and stable.

32
01:51.120 --> 01:57.370
As we can see here, our one vSmart controller is in fact online, so that being

33
01:57.370 --> 01:58.120
the case,

34
01:58.120 --> 02:03.320
we now go over to configuration and we go to templates.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:58.120 --> 02:03.320
we now go over to configuration and we go to templates.

35
02:03.320 --> 02:08.280
Now under templates, all I have right now is the template that's applied to the

36
02:08.280 --> 02:08.600
edge

37
02:08.600 --> 02:12.640
devices at the headquarters site.

38
02:12.640 --> 02:17.530
We want to do is come up here and say Create Template, but instead of from

39
02:17.530 --> 02:18.800
feature template,

40
02:18.800 --> 02:23.960
which is what we commonly do, we're going to choose a CLI template.

41
02:23.960 --> 02:30.880
From our dropdown for a selected device model, we are going to choose vSmart.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
02:23.960 --> 02:30.880
From our dropdown for a selected device model, we are going to choose vSmart.

42
02:30.880 --> 02:35.690
For the template name, I'll simply call it vSmartHQ since this is at the

43
02:35.690 --> 02:36.760
headquarters

44
02:36.760 --> 02:42.680
location and for the description, I'll just call it headquarters controllers.

45
02:42.680 --> 02:45.840
Now here's the key of what we want to do.

46
02:45.840 --> 02:50.410
We want to use this section here in the middle that says to load the running

47
02:50.410 --> 02:51.240
config from

48
02:51.240 --> 02:53.120
a reachable device.

49
02:53.120 --> 02:56.160
This is of course part of why we wanted to make sure that it was reachable

50
02:56.160 --> 02:56.800
before we

51
02:56.800 --> 02:57.800
started.

52
02:57.800 --> 03:02.490
So what we want to do is click on this dropdown and it's going to show us our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:57.800 --> 03:02.490
So what we want to do is click on this dropdown and it's going to show us our

53
03:02.490 --> 03:02.960
one and only

54
03:02.960 --> 03:05.920
controller in this environment.

55
03:05.920 --> 03:11.030
We'll go ahead and click on that and what we see here is that it's gone out and

56
03:11.030 --> 03:11.680
pulled

57
03:11.680 --> 03:15.320
the configuration off that device.

58
03:15.320 --> 03:19.640
This is all we need to do is simply create this template and then apply it back

59
03:19.640 --> 03:20.080
to the

60
03:20.080 --> 03:21.400
device.

61
03:21.400 --> 03:24.080
So we'll simply go ahead and hit add.

62
03:24.080 --> 03:27.960
Then over here on the right, we'll simply click on the dropdown next to that

63
03:27.960 --> 03:28.440
and say

64
03:28.440 --> 03:30.400
attach devices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:28.440 --> 03:30.400
attach devices.

65
03:30.400 --> 03:34.040
The device we want to attach of course is our controller.

66
03:34.040 --> 03:37.340
And of course that's the only thing listed because it knows that this is a

67
03:37.340 --> 03:38.000
controller

68
03:38.000 --> 03:39.280
template.

69
03:39.280 --> 03:44.320
So we'll say controller, we'll add it to our list and hit attach.

70
03:44.320 --> 03:47.440
We'll go ahead and hit configure devices.

71
03:47.440 --> 03:54.460
To verify this, we can go to configuration, devices, control components and we

72
03:54.460 --> 03:55.200
see here

73
03:55.200 --> 04:01.700
for our vSmart controller, it is now being managed by our template for vSmart
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:55.200 --> 04:01.700
for our vSmart controller, it is now being managed by our template for vSmart

74
04:01.700 --> 04:03.440
at headquarters.

75
04:03.440 --> 04:07.400
So this means we should now be able to apply our policy.

76
04:07.400 --> 04:10.360
So we'll come back over here to configuration.

77
04:10.360 --> 04:12.400
We'll go to policies.

78
04:12.400 --> 04:17.040
Our policy is still listed here and now we'll activate it.

79
04:17.040 --> 04:20.080
Tells you it's going to be pushed out to our vSmart controller.

80
04:20.080 --> 04:22.360
Notice of course, no error this time.

81
04:22.360 --> 04:26.240
We'll hit activate and activate.

82
04:26.240 --> 04:31.040
We can see here that now our policy deployment has been successful and if we go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
04:26.240 --> 04:31.040
We can see here that now our policy deployment has been successful and if we go

83
04:31.040 --> 04:31.640
back to our

84
04:31.640 --> 04:37.880
policies, we see here that activated is now listed as true.

85
04:37.880 --> 04:43.280
Therefore, our policy has been properly deployed.

86
04:43.280 --> 04:49.780
So in this video, we simply saw how to put the vSmart controllers into vManage

87
04:49.780 --> 04:50.320
mode by

88
04:50.320 --> 04:55.270
simply applying a CLI template to the device so that it's configuration is now

89
04:55.270 --> 04:55.960
under the

90
04:55.960 --> 05:01.220
control of vManage rather than simply being locally configured on the vSmart
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:55.960 --> 05:01.220
control of vManage rather than simply being locally configured on the vSmart

91
05:01.220 --> 05:02.120
controller

92
05:02.120 --> 05:03.760
itself.

93
05:03.760 --> 05:09.130
That concludes everything that we need to cover in this skill, leaving us with

94
05:09.130 --> 05:10.760
just the challenge.

95
05:10.760 --> 05:15.300
So go ahead and give that a shot and I'll see you in the solution video on the

96
05:15.300 --> 05:15.800
other

97
05:15.800 --> 05:16.240
side.

98
05:16.240 --> 05:24.500
[BLANK_AUDIO]