WEBVTT

1
00:00.000 --> 00:07.500
So, the first thing we need to do is make sure that our CML instance is

2
00:07.500 --> 00:08.440
actually ready

3
00:08.440 --> 00:14.640
to receive these custom images that don't come packaged with CML.

4
00:14.640 --> 00:18.440
Specifically of course, we're talking about the files for the SD-WAN

5
00:18.440 --> 00:19.440
controllers.

6
00:19.440 --> 00:22.320
Now, what do we mean by getting it ready?

7
00:22.320 --> 00:28.280
While specifically what I'm referring to is simply the storage space on CML.

8
00:28.280 --> 00:32.680
When you deployed your CML instance, it really depends on how much storage you
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:28.280 --> 00:32.680
When you deployed your CML instance, it really depends on how much storage you

9
00:32.680 --> 00:33.760
gave it.

10
00:33.760 --> 00:38.720
Now the good news is it's pretty easy to add storage to it should you need to.

11
00:38.720 --> 00:41.160
That's what we're going to go over in this section.

12
00:41.160 --> 00:46.560
Now, if your CML instance already has enough storage space, well, you can very

13
00:46.560 --> 00:47.360
safely skip

14
00:47.360 --> 00:51.440
this section and move on to the next video.

15
00:51.440 --> 00:57.440
But for those of you who may need to add space, let's jump in and get started.

16
00:57.440 --> 00:59.520
So we'll simply start off here.

17
00:59.520 --> 01:03.440
This is my virtual machine for CML 2.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:59.520 --> 01:03.440
This is my virtual machine for CML 2.

18
01:03.440 --> 01:10.480
And as you can see here, I actually have two hard disks assigned to this VM.

19
01:10.480 --> 01:16.360
The first is the 32 gig hard drive that CML 2 has by default.

20
01:16.360 --> 01:22.160
And the other one here is a 500 gig hard drive that I added for more storage.

21
01:22.160 --> 01:28.030
Now, if again, you don't have this much assigned to your VM, simply add a new

22
01:28.030 --> 01:29.280
hard drive in

23
01:29.280 --> 01:33.440
whatever virtualization software you're using and we'll show you in just a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
01:29.280 --> 01:33.440
whatever virtualization software you're using and we'll show you in just a

24
01:33.440 --> 01:34.320
moment how to

25
01:34.320 --> 01:37.160
add that to CML 2.

26
01:37.160 --> 01:42.480
But the first step is you have to have the hard drives assigned to the VM.

27
01:42.480 --> 01:48.010
Once we do that, you're going to want to open the cockpit instance that was

28
01:48.010 --> 01:48.720
installed

29
01:48.720 --> 01:51.480
along with your CML 2 image.

30
01:51.480 --> 01:55.520
If you're not sure how to get to that, note the URL right here.

31
01:55.520 --> 02:01.480
You will of course have to substitute the IP address of your CML 2 instance.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:55.520 --> 02:01.480
You will of course have to substitute the IP address of your CML 2 instance.

32
02:01.480 --> 02:07.430
However, other than that, it should be running at port 90 90 forward slash

33
02:07.430 --> 02:08.640
viral to forward

34
02:08.640 --> 02:10.360
slash maintenance.

35
02:10.360 --> 02:15.920
And of course, it's using HTTPS login with whatever username and password you

36
02:15.920 --> 02:18.760
configured during installation.

37
02:18.760 --> 02:20.720
We hit login.

38
02:20.720 --> 02:25.360
And this brings us to the CML 2 system maintenance controls, which is basically

39
02:25.360 --> 02:26.120
a customized

40
02:26.120 --> 02:31.920
version of cockpit that Cisco puts on the CML 2 instance.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
02:26.120 --> 02:31.920
version of cockpit that Cisco puts on the CML 2 instance.

41
02:31.920 --> 02:35.880
From here, we want to go to storage.

42
02:35.880 --> 02:38.400
So we'll simply come over here to storage.

43
02:38.400 --> 02:44.050
And then what we want to do is over here under devices, we want to go to this V

44
02:44.050 --> 02:45.640
G00, which

45
02:45.640 --> 02:48.160
is our volume group.

46
02:48.160 --> 02:51.200
So we simply click on the volume group here.

47
02:51.200 --> 02:56.160
And the important thing is over on the right, under physical volumes.

48
02:56.160 --> 03:03.140
Now, as you can see, I have the 31.5 gig that comes along with CML 2 already
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
02:56.160 --> 03:03.140
Now, as you can see, I have the 31.5 gig that comes along with CML 2 already

49
03:03.140 --> 03:03.960
added.

50
03:03.960 --> 03:09.520
And then I have simply added my 500 gig VMware virtual desk.

51
03:09.520 --> 03:13.760
Now, of course, if I were to hit plus on my system, it's going to tell me that

52
03:13.760 --> 03:14.240
I have

53
03:14.240 --> 03:16.560
no disks available to add.

54
03:16.560 --> 03:20.720
But if you have added one to your instance, here's where you can highlight the

55
03:20.720 --> 03:21.880
disk, add

56
03:21.880 --> 03:22.800
it.

57
03:22.800 --> 03:27.920
And once you do that, you'll have a choice down here at the bottom to then grow

58
03:27.920 --> 03:29.640
that volume.

59
03:29.640 --> 03:34.250
So you simply move the slider all the way up to grow the volume to the maximum
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
03:29.640 --> 03:34.250
So you simply move the slider all the way up to grow the volume to the maximum

60
03:34.250 --> 03:34.440
size,

61
03:34.440 --> 03:39.720
grow the volume, and then it should have this new capacity, which as you can

62
03:39.720 --> 03:40.760
see in my case

63
03:40.760 --> 03:43.640
is 531 gigs.

64
03:43.640 --> 03:47.320
We can also verify this on CML itself.

65
03:47.320 --> 03:50.680
So here I'm connected into the CML workbench.

66
03:50.680 --> 03:53.720
I have our lab open and running.

67
03:53.720 --> 03:58.200
And if we click down here under disk, we can see that when we're looking at the

68
03:58.200 --> 03:58.760
disk,

69
03:58.760 --> 04:04.800
we see that total capacity of 513 gigs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
03:58.760 --> 04:04.800
we see that total capacity of 513 gigs.

70
04:04.800 --> 04:09.640
Notice that we currently have 450 gigs, which is way more than enough.

71
04:09.640 --> 04:16.570
What we're looking for here, by the way, is about 100 to 150 gigs free on our

72
04:16.570 --> 04:17.600
storage.

73
04:17.600 --> 04:21.690
That should be enough for a small lab where we're just going to put out one of

74
04:21.690 --> 04:22.280
each type

75
04:22.280 --> 04:29.680
of controller and maybe a few V edge devices or a few catalyst 8000Vs.

76
04:29.680 --> 04:35.260
So somewhere around 100 to 150, of course, if you have the extra storage space
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
04:29.680 --> 04:35.260
So somewhere around 100 to 150, of course, if you have the extra storage space

77
04:35.260 --> 04:36.120
available,

78
04:36.120 --> 04:38.280
you can allocate as much as you want.

79
04:38.280 --> 04:42.560
Again, in my case, I've allocated 500 gigs to it.

80
04:42.560 --> 04:47.440
One other thing to note about our topology as we jump in, if we look at one of

81
04:47.440 --> 04:48.120
our routers,

82
04:48.120 --> 04:50.680
I'll just pick on router one.

83
04:50.680 --> 04:56.720
Notice that under compute, I have bumped this up to eight gigs of RAM.

84
04:56.720 --> 05:02.860
The default, when you just deploy a new node into CML, the image that Cisco
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:56.720 --> 05:02.860
The default, when you just deploy a new node into CML, the image that Cisco

85
05:02.860 --> 05:04.040
provides gives

86
05:04.040 --> 05:06.600
it four gigs of RAM.

87
05:06.600 --> 05:08.760
Now let me tell you why I did that.

88
05:08.760 --> 05:14.210
I did that simply because when this is up and running and it's been added to SD

89
05:14.210 --> 05:14.920
-WAN as

90
05:14.920 --> 05:22.480
a V edge, well, it actually ends up running about 74 and a half to 75% RAM use.

91
05:22.480 --> 05:26.790
And what that does is that triggers SD-WAN to put an alarm on it and say that

92
05:26.790 --> 05:27.480
we should

93
05:27.480 --> 05:29.360
be watching its RAM use.

94
05:29.360 --> 05:33.720
Well, the fact of the matter is we have plenty of RAM on my server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
05:29.360 --> 05:33.720
Well, the fact of the matter is we have plenty of RAM on my server.

95
05:33.720 --> 05:37.650
So if I just bumped this up to eight gigs, I don't end up getting those

96
05:37.650 --> 05:38.480
warnings.

97
05:38.480 --> 05:43.140
But just so you know, if you don't have enough RAM available, running this with

98
05:43.140 --> 05:43.880
the default

99
05:43.880 --> 05:46.600
four gigs of RAM works perfectly fine.

100
05:46.600 --> 05:51.960
You just might get some RAM warnings or memory usage warnings in SD-WAN.

101
05:51.960 --> 05:56.160
And of course that can be ignored because, well, it's not a production

102
05:56.160 --> 05:57.160
environment.

103
05:57.160 --> 06:00.400
So now that we have this up and running, the next thing to do is going to be to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
05:57.160 --> 06:00.400
So now that we have this up and running, the next thing to do is going to be to

104
06:00.400 --> 06:01.000
actually

105
06:01.000 --> 06:05.320
get these images and upload them to CML2.

106
06:05.320 --> 06:07.240
And that's exactly what we're going to do next.

107
06:07.240 --> 06:15.180
[BLANK_AUDIO]