WEBVTT

1
00:00.000 --> 00:06.680
Next up is creating our node definitions.

2
00:06.680 --> 00:11.950
We have our images uploaded to the server, however we have to tell CML how to

3
00:11.950 --> 00:12.640
actually

4
00:12.640 --> 00:15.040
run each of those images.

5
00:15.040 --> 00:19.700
How much RAM, how much CPU, how many network interfaces, all of these different

6
00:19.700 --> 00:20.540
parameters

7
00:20.540 --> 00:22.440
have to be set up.

8
00:22.440 --> 00:24.780
And they have to be set up correctly.

9
00:24.780 --> 00:30.220
I would strongly recommend following these guidelines exactly if you want these
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:24.780 --> 00:30.220
I would strongly recommend following these guidelines exactly if you want these

10
00:30.220 --> 00:30.740
images

11
00:30.740 --> 00:32.260
to boot.

12
00:32.260 --> 00:36.690
Doing things like mapping the interfaces incorrectly can cause the images to

13
00:36.690 --> 00:38.220
maybe come up but

14
00:38.220 --> 00:40.780
not have the proper interfaces.

15
00:40.780 --> 00:44.700
So this is one of those places where attention to detail is probably going to

16
00:44.700 --> 00:46.420
be pretty important.

17
00:46.420 --> 00:52.660
So let's go ahead and jump in and take a look at how to configure those nodes.

18
00:52.660 --> 00:57.760
So once again, we'll start off in our lab here on the CML workbench.

19
00:57.760 --> 01:03.200
Once again, we go to tools, we go to node and image definitions, but this time
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:57.760 --> 01:03.200
Once again, we go to tools, we go to node and image definitions, but this time

20
01:03.200 --> 01:03.740
we're

21
01:03.740 --> 01:07.420
going to start right here on the node definitions.

22
01:07.420 --> 01:11.220
We need to add definitions for each of our controllers.

23
01:11.220 --> 01:15.060
So we can either do an add or an import.

24
01:15.060 --> 01:19.380
Now if we're going to do an import, we are going to need the files for that.

25
01:19.380 --> 01:24.780
And those are provided above this video, if you'd rather just do an import.

26
01:24.780 --> 01:28.220
We'll do an add for the first one so you can see how it works.

27
01:28.220 --> 01:30.780
And then we'll simply import the other two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:28.220 --> 01:30.780
And then we'll simply import the other two.

28
01:30.780 --> 01:33.260
That way you get an example of both.

29
01:33.260 --> 01:35.820
So starting off, let's hit add.

30
01:35.820 --> 01:38.500
And we have to go down and fill out each of these fields.

31
01:38.500 --> 01:40.820
So we'll start with vmanage.

32
01:40.820 --> 01:43.540
So for the ID, we'll do vmanage.

33
01:43.540 --> 01:47.780
For the description, we'll do vmanage server.

34
01:47.780 --> 01:49.900
Now this is very important.

35
01:49.900 --> 01:56.860
For the nature, you must choose router for all of the controllers.

36
01:56.860 --> 01:59.980
Otherwise they will not function correctly.

37
01:59.980 --> 02:04.720
So again, the nature is always going to be router because these are at the end
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:59.980 --> 02:04.720
So again, the nature is always going to be router because these are at the end

38
02:04.720 --> 02:05.140
of the

39
02:05.140 --> 02:07.860
day router images.

40
02:07.860 --> 02:12.140
For the user interface, we'll leave this set to visible.

41
02:12.140 --> 02:14.100
Let's scroll down a little bit.

42
02:14.100 --> 02:17.740
For the prefix, we'll do vmanage dash.

43
02:17.740 --> 02:23.390
That way as we create each one, it will enumerate them as we add these to our

44
02:23.390 --> 02:24.540
topology.

45
02:24.540 --> 02:27.860
For the icon, this is really pretty much preference.

46
02:27.860 --> 02:29.580
We'll choose server.

47
02:29.580 --> 02:33.250
This is how it's going to represent itself in the menu of nodes when we go to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:29.580 --> 02:33.250
This is how it's going to represent itself in the menu of nodes when we go to

48
02:33.250 --> 02:33.820
choose to

49
02:33.820 --> 02:35.620
put one in.

50
02:35.620 --> 02:40.220
For the label, we'll call it Viptel of Vmanage.

51
02:40.220 --> 02:44.070
For our Linux native simulation, for the domain driver, we're going to change

52
02:44.070 --> 02:46.420
this to KVM.

53
02:46.420 --> 02:50.300
For the simulation driver, this will be server.

54
02:50.300 --> 02:53.700
For the hard drive, this will be IDE.

55
02:53.700 --> 02:58.750
Once again, if you don't choose IDE here, then vmanage won't be able to see the

56
02:58.750 --> 02:59.300
storage

57
02:59.300 --> 03:03.260
drive that we're going to give it here in just a few moments.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:59.300 --> 03:03.260
drive that we're going to give it here in just a few moments.

58
03:03.260 --> 03:06.300
For the server, the recommendation is 32 megs.

59
03:06.300 --> 03:08.820
So we'll say 32,000.

60
03:08.820 --> 03:12.580
For the CPUs, it's recommended to give it 6.

61
03:12.580 --> 03:17.580
For the CPU limit, it's allowed to use 100% of the CPU.

62
03:17.580 --> 03:19.380
We'll scroll down.

63
03:19.380 --> 03:23.420
For the network driver, we're going to choose Vert.io.

64
03:23.420 --> 03:28.620
Again, that is the driver that Vmanage will recognize.

65
03:28.620 --> 03:34.190
Now for the data disk size, the recommendation is to set this somewhere around
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
03:28.620 --> 03:34.190
Now for the data disk size, the recommendation is to set this somewhere around

66
03:34.190 --> 03:35.260
100.

67
03:35.260 --> 03:39.710
It really does depend on how many V-smart controllers and such you plan on

68
03:39.710 --> 03:40.380
using, but

69
03:40.380 --> 03:44.660
100 should cover pretty much anything you want to deploy.

70
03:44.660 --> 03:48.840
You could actually probably go a little smaller if you're simply doing this for

71
03:48.840 --> 03:50.460
this course.

72
03:50.460 --> 03:54.110
If you're building it to use this environment for other things, then you may

73
03:54.110 --> 03:54.660
want to go

74
03:54.660 --> 03:56.260
a little larger here.

75
03:56.260 --> 03:58.860
We're just going to configure it to 100.

76
03:58.860 --> 04:02.970
Do not change the boot disk size because that's going to be coming from the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:58.860 --> 04:02.970
Do not change the boot disk size because that's going to be coming from the

77
04:02.970 --> 04:05.220
image itself.

78
04:05.220 --> 04:07.650
Most of the rest of these are going to stay the same until we get down to

79
04:07.650 --> 04:08.380
interfaces.

80
04:08.380 --> 04:10.460
So let's go down to interfaces.

81
04:10.460 --> 04:12.420
We are going to have a loopback.

82
04:12.420 --> 04:16.700
The loopback name is going to be system.

83
04:16.700 --> 04:19.700
The number of serial ports is going to be one.

84
04:19.700 --> 04:24.900
Number of default physical interfaces is going to be two.

85
04:24.900 --> 04:28.820
The first interface is going to be ETH zero.

86
04:28.820 --> 04:31.500
Then we're going to add an interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
04:28.820 --> 04:31.500
Then we're going to add an interface.

87
04:31.500 --> 04:34.940
Interface one is going to be ETH one.

88
04:34.940 --> 04:40.300
We'll also set the boot timeout to 300 seconds.

89
04:40.300 --> 04:44.100
Scrolling down, we'll leave all of these settings at their default.

90
04:44.100 --> 04:48.500
For the configuration generator, we'll set this to server.

91
04:48.500 --> 04:52.340
Once all of that is properly set, we simply hit create.

92
04:52.340 --> 04:55.180
It's now created this new image definition.

93
04:55.180 --> 04:58.460
We could change and modify it from here if we want to.

94
04:58.460 --> 05:00.500
We can also go back.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:58.460 --> 05:00.500
We can also go back.

95
05:00.500 --> 05:01.100
If we go back here to our list and scroll down, we see that we now have our V

96
05:01.100 --> 05:07.060
itella VManage

97
05:07.060 --> 05:11.060
server listed here as an available node.

98
05:11.060 --> 05:16.260
Now let's move on to VBond, but for this one, we're going to do an import.

99
05:16.260 --> 05:18.220
So we'll say import.

100
05:18.220 --> 05:19.860
We'll choose the import definition.

101
05:19.860 --> 05:23.100
Again, these are the files provided above.

102
05:23.100 --> 05:27.340
So we will choose the VBond file, hit open.

103
05:27.340 --> 05:31.580
It tells us that it's been imported, so we can say go to no definition.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
05:27.340 --> 05:31.580
It tells us that it's been imported, so we can say go to no definition.

104
05:31.580 --> 05:35.990
And here we can simply go down over the list, make any changes that we want to

105
05:35.990 --> 05:36.500
make.

106
05:36.500 --> 05:40.740
We can verify that all of these things match up.

107
05:40.740 --> 05:47.340
One important thing to note here under interfaces that's important on the VBond

108
05:47.340 --> 05:47.940
server is that

109
05:47.940 --> 05:55.540
interface zero is still ETH zero, but interface one is now GE zero zero.

110
05:55.540 --> 06:00.580
This is the interface that's ultimately going to become VPN zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
05:55.540 --> 06:00.580
This is the interface that's ultimately going to become VPN zero.

111
06:00.580 --> 06:02.260
Also the timeout is a little bit lower.

112
06:02.260 --> 06:07.170
There's a couple other minor changes here that you can look over, but this file

113
06:07.170 --> 06:07.660
has all

114
06:07.660 --> 06:09.300
of the necessary changes.

115
06:09.300 --> 06:13.940
Again, if we had changed anything here, we could simply hit update here at the

116
06:13.940 --> 06:14.660
bottom,

117
06:14.660 --> 06:20.530
but since we haven't, we can simply go back to tools, back to images, and now

118
06:20.530 --> 06:21.180
we have

119
06:21.180 --> 06:24.940
the Viptella VBond, VBond server.

120
06:24.940 --> 06:28.540
So finally, we'll import our VSmartController.

121
06:28.540 --> 06:31.300
We'll simply do it the same way.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
06:28.540 --> 06:31.300
We'll simply do it the same way.

122
06:31.300 --> 06:35.400
Again, we could scroll down, make sure everything is properly configured, which

123
06:35.400 --> 06:37.180
it is.

124
06:37.180 --> 06:41.580
Notice the interfaces on this are much more like VManage.

125
06:41.580 --> 06:44.940
They're both ETH zero and ETH one.

126
06:44.940 --> 06:47.500
Everything else is set properly.

127
06:47.500 --> 06:52.180
So again, we can go back to tools, node and image definitions.

128
06:52.180 --> 06:58.330
And if we scroll down, we now have our node definitions for all three

129
06:58.330 --> 06:59.980
controllers.

130
06:59.980 --> 07:04.420
So as you can see, this is a fairly straightforward process.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
06:59.980 --> 07:04.420
So as you can see, this is a fairly straightforward process.

131
07:04.420 --> 07:08.870
We just have to make sure that we have the proper parameters, which again, are

132
07:08.870 --> 07:09.420
listed

133
07:09.420 --> 07:15.720
both above this video and in the files that are provided if you just want to do

134
07:15.720 --> 07:16.980
the import.

135
07:16.980 --> 07:20.600
You can of course tweak any of those parameters, but I would generally

136
07:20.600 --> 07:22.060
recommend staying away

137
07:22.060 --> 07:26.860
from tweaking things such as the interfaces because if they're not correct,

138
07:26.860 --> 07:27.540
these devices

139
07:27.540 --> 07:30.460
will not boot with the proper interfaces.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

139
07:27.540 --> 07:30.460
will not boot with the proper interfaces.

140
07:30.460 --> 07:36.040
Now, the last piece we're going to need is our image definitions to tie the

141
07:36.040 --> 07:37.540
disk images

142
07:37.540 --> 07:40.220
into these node definitions.

143
07:40.220 --> 07:43.220
So that's the last piece we need to tie this together.

144
07:43.220 --> 07:45.780
Let's go ahead and build those in the next video.