WEBVTT

1
00:00.000 --> 00:07.550
So now that we have our nodes properly deployed into our topology, the next

2
00:07.550 --> 00:07.880
thing we want

3
00:07.880 --> 00:13.290
to do is to fire these servers up, verify that everything's working, and that

4
00:13.290 --> 00:13.800
we can

5
00:13.800 --> 00:15.800
connect into the devices.

6
00:15.800 --> 00:20.280
I will tell you right up front, we are going to have an issue here.

7
00:20.280 --> 00:24.260
Now I'll show you how to fix that issue, of course, and I'll show you how to

8
00:24.260 --> 00:25.120
fix it

9
00:25.120 --> 00:29.830
on the manager that we've already deployed and how to make it a little bit of a

10
00:29.830 --> 00:30.840
more permanent
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:29.830 --> 00:30.840
more permanent

11
00:30.840 --> 00:36.190
fix in case you decide to tear this lab apart or build another topology later,

12
00:36.190 --> 00:36.880
that way

13
00:36.880 --> 00:39.120
you don't have to fix this every time.

14
00:39.120 --> 00:43.150
But let's go ahead and jump in, fire up these machines, take a look at what the

15
00:43.150 --> 00:43.680
problem

16
00:43.680 --> 00:49.400
is, and of course, take a look at how to fix it.

17
00:49.400 --> 00:54.360
So the first thing we want to do here is start off all four of our servers.

18
00:54.360 --> 00:59.000
So let's just go ahead and right click on each one and start each node.

19
00:59.000 --> 01:01.720
We'll give these just a few minutes to boot up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:59.000 --> 01:01.720
We'll give these just a few minutes to boot up.

20
01:01.720 --> 01:06.460
We'll skip ahead to then, but we're also going to want to get connected into

21
01:06.460 --> 01:07.440
the console.

22
01:07.440 --> 01:14.290
So you can either use the built-in terminal server in CML 2.7, or you can go

23
01:14.290 --> 01:15.240
ahead and

24
01:15.240 --> 01:20.000
just right click on each device, connect to the console, and it'll pop up in

25
01:20.000 --> 01:20.680
the panes

26
01:20.680 --> 01:22.840
down at the bottom of this screen.

27
01:22.840 --> 01:26.960
You can connect whichever way you want, but just so we have a nice full screen,

28
01:26.960 --> 01:27.480
I'm going

29
01:27.480 --> 01:32.440
to do it using secure CRT and the terminal server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:27.480 --> 01:32.440
to do it using secure CRT and the terminal server.

30
01:32.440 --> 01:37.080
So here we are on the console of our manager server.

31
01:37.080 --> 01:40.880
Let's go ahead and log in with the default admin admin.

32
01:40.880 --> 01:43.240
It's going to make us change the password.

33
01:43.240 --> 01:47.640
So we'll change it to our 1234 QWR.

34
01:47.640 --> 01:50.760
It's going to ask us what we want for the persona.

35
01:50.760 --> 01:53.360
We're going to choose compute and data.

36
01:53.360 --> 01:55.560
We'll say yes for sure.

37
01:55.560 --> 01:58.040
Then it's going to ask us which drive to use.

38
01:58.040 --> 02:03.280
We want to use SDB, the one that has 256 gigs of storage.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:58.040 --> 02:03.280
We want to use SDB, the one that has 256 gigs of storage.

39
02:03.280 --> 02:04.440
So we'll select two.

40
02:04.440 --> 02:06.640
It asks us if we want to format it.

41
02:06.640 --> 02:08.320
We'll say yes.

42
02:08.320 --> 02:13.420
And now it's going to format the drive, set up the database, install the needed

43
02:13.420 --> 02:14.440
components,

44
02:14.440 --> 02:16.880
and then it's going to reboot the server.

45
02:16.880 --> 02:22.080
So let's jump ahead to where this device is fully installed and rebooted.

46
02:22.080 --> 02:25.360
Okay, so it's been about five minutes.

47
02:25.360 --> 02:30.800
And as you can see, our VManage or our manager is back up and running.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:25.360 --> 02:30.800
And as you can see, our VManage or our manager is back up and running.

48
02:30.800 --> 02:33.520
However, we do have a small problem.

49
02:33.520 --> 02:40.030
Let's take a look at what happens if we do a request NMS all status to see the

50
02:40.030 --> 02:40.720
status

51
02:40.720 --> 02:43.840
of the network management server services.

52
02:43.840 --> 02:46.360
Let's take a look at what happens here.

53
02:46.360 --> 02:52.000
First thing to note is that as of right now, all of these are not running.

54
02:52.000 --> 02:56.000
If we scroll through the whole list, they are not running yet, which means it

55
02:56.000 --> 02:56.480
hasn't

56
02:56.480 --> 03:00.120
even begun to start these services.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:56.480 --> 03:00.120
even begun to start these services.

57
03:00.120 --> 03:03.440
That means we're going to have to wait just a few more minutes.

58
03:03.440 --> 03:06.520
So what we're going to do is we're just going to let this sit here for a good

59
03:06.520 --> 03:07.720
five minutes

60
03:07.720 --> 03:14.200
and make sure that all of these services either start or at least attempt to

61
03:14.200 --> 03:15.120
start.

62
03:15.120 --> 03:17.040
So now it's been five minutes.

63
03:17.040 --> 03:19.800
Let's go ahead and repeat this command again.

64
03:19.800 --> 03:24.040
So we see here now that a lot of the services are up and running.

65
03:24.040 --> 03:28.380
We can see roughly an average of about a hundred and sixty seconds or so that

66
03:28.380 --> 03:28.760
most of

67
03:28.760 --> 03:30.280
these have been up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
03:28.760 --> 03:30.280
these have been up.

68
03:30.280 --> 03:35.210
However, if we scroll back up this list, there's two important things here that

69
03:35.210 --> 03:35.920
we want to

70
03:35.920 --> 03:36.920
note.

71
03:36.920 --> 03:41.970
First is the NMS application server, which is actually the web front end that

72
03:41.970 --> 03:42.560
we need

73
03:42.560 --> 03:47.640
to access is yet to start for the status.

74
03:47.640 --> 03:52.440
The reason is this NMS configuration database.

75
03:52.440 --> 03:56.830
Notice that it's only been running for 16 seconds, which is of course

76
03:56.830 --> 03:58.400
considerably less

77
03:58.400 --> 04:00.480
than all these other services.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
03:58.400 --> 04:00.480
than all these other services.

78
04:00.480 --> 04:03.840
The reason for that is it keeps restarting.

79
04:03.840 --> 04:07.630
If we looked at this command a couple of times, we would see it all the time

80
04:07.630 --> 04:08.400
somewhere with

81
04:08.400 --> 04:13.490
an average of about five to twenty seconds that it's been running and then it

82
04:13.490 --> 04:14.080
simply

83
04:14.080 --> 04:15.600
restarts.

84
04:15.600 --> 04:23.220
The reason it's doing this is by default, the manager is not given enough RAM

85
04:23.220 --> 04:23.680
in its

86
04:23.680 --> 04:25.680
node definition.

87
04:25.680 --> 04:31.120
Let's go back over and take a look at CML 2.7.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
04:25.680 --> 04:31.120
Let's go back over and take a look at CML 2.7.

88
04:31.120 --> 04:36.070
So here in CML, if we go back to tools and we go back to node and image

89
04:36.070 --> 04:37.320
definitions,

90
04:37.320 --> 04:44.130
if we take a look at the SDWAN manager and we scroll down to RAM, notice that

91
04:44.130 --> 04:45.160
by default,

92
04:45.160 --> 04:47.880
it's given 16 gigs of RAM.

93
04:47.880 --> 04:52.240
And the fact of the matter is that's simply not enough.

94
04:52.240 --> 04:58.170
If I had to guess during testing, Cisco probably booted up the management

95
04:58.170 --> 04:59.240
server, saw that

96
04:59.240 --> 05:03.520
it came up with the console prompt and assumed everything was okay.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
04:59.240 --> 05:03.520
it came up with the console prompt and assumed everything was okay.

97
05:03.520 --> 05:09.660
The problem is it can't actually start the VManage software or the catalyst SDW

98
05:09.660 --> 05:10.480
AN manager

99
05:10.480 --> 05:11.840
software.

100
05:11.840 --> 05:15.600
So what we need to do is actually increase this amount of memory.

101
05:15.600 --> 05:17.980
Now there's two ways we can fix this.

102
05:17.980 --> 05:21.640
The first is to fix this node definition.

103
05:21.640 --> 05:25.320
In order to do that, we'll have to scroll back up to the top.

104
05:25.320 --> 05:28.040
We'll have to turn this off of read only.

105
05:28.040 --> 05:31.160
It's of course going to warn us that we have to be careful.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
05:28.040 --> 05:31.160
It's of course going to warn us that we have to be careful.

106
05:31.160 --> 05:32.920
We'll hit OK.

107
05:32.920 --> 05:37.480
We'll scroll back down to memory and we'll change this number.

108
05:37.480 --> 05:40.160
Now I'm going to change it to 32 gigs.

109
05:40.160 --> 05:42.480
I have not tried other numbers.

110
05:42.480 --> 05:48.260
If you don't have enough RAM in your server to give it 32 gigs, you could maybe

111
05:48.260 --> 05:49.120
try 24

112
05:49.120 --> 05:50.120
gigs.

113
05:50.120 --> 05:51.360
I have not tried other numbers.

114
05:51.360 --> 05:54.120
I just turn it up to 32 gigs.

115
05:54.120 --> 05:56.440
But then we scroll to the bottom.

116
05:56.440 --> 05:59.160
At the very bottom, we hit update.

117
05:59.160 --> 06:02.440
And I would suggest coming all the way back up here to the top.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
05:59.160 --> 06:02.440
And I would suggest coming all the way back up here to the top.

118
06:02.440 --> 06:06.800
And we probably want to turn this back on to read only.

119
06:06.800 --> 06:11.880
So that'll take care of any SDWAN managers that we deploy in the future.

120
06:11.880 --> 06:16.520
However, it doesn't help the one that we have currently running.

121
06:16.520 --> 06:19.440
So let's go back to our topology.

122
06:19.440 --> 06:22.600
Now once again, there's a couple of ways we could fix this.

123
06:22.600 --> 06:26.820
We could simply delete our current manager and just rebuild it, which we sort

124
06:26.820 --> 06:27.280
of have

125
06:27.280 --> 06:30.680
to do anyway, because what we're going to have to do is we're going to have to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
06:27.280 --> 06:30.680
to do anyway, because what we're going to have to do is we're going to have to

126
06:30.680 --> 06:30.880
right

127
06:30.880 --> 06:32.520
click on it.

128
06:32.520 --> 06:34.400
We're going to have to stop it.

129
06:34.400 --> 06:36.280
And here's the thing.

130
06:36.280 --> 06:41.120
If we highlight this and look at RAM, it will not let us change it.

131
06:41.120 --> 06:43.120
I can't click on this.

132
06:43.120 --> 06:47.000
In order to change it, we actually have to wipe the node.

133
06:47.000 --> 06:50.090
We could do that either by right clicking on it or we can just click on wipe

134
06:50.090 --> 06:50.560
right up

135
06:50.560 --> 06:53.520
here since we already have this window open.

136
06:53.520 --> 06:55.440
We'll confirm it.

137
06:55.440 --> 07:00.820
Now we can change the RAM and notice as soon as we wipe it, when we look at the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

137
06:55.440 --> 07:00.820
Now we can change the RAM and notice as soon as we wipe it, when we look at the

138
07:00.820 --> 07:01.440
RAM, it's

139
07:01.440 --> 07:06.440
now set to the 326768 from the template we just updated.

140
07:06.440 --> 07:10.800
However, we did have to wipe it, which means we have to rebuild it.

141
07:10.800 --> 07:16.560
So let's go ahead and hit start on it again and go through the same process.

142
07:16.560 --> 07:21.990
So now we've rebooted and reconfigured the manage, let it boot up and run for

143
07:21.990 --> 07:22.720
about five

144
07:22.720 --> 07:24.320
to 10 minutes.

145
07:24.320 --> 07:30.990
And as we can see now, our NMS configuration database is up and running for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
07:24.320 --> 07:30.990
And as we can see now, our NMS configuration database is up and running for

146
07:30.990 --> 07:31.800
actually a

147
07:31.800 --> 07:34.960
little bit longer than most of our other services.

148
07:34.960 --> 07:41.180
And most importantly, we see that the NMS application server is now up and

149
07:41.180 --> 07:42.240
running.

150
07:42.240 --> 07:48.130
So now that we've added this extra RAM to the SDWAN manager, we can see that

151
07:48.130 --> 07:49.240
the services

152
07:49.240 --> 07:51.360
are now stable.

153
07:51.360 --> 07:55.490
There shouldn't be any problem with the other servers, but let's verify just to

154
07:55.490 --> 07:56.080
make sure

155
07:56.080 --> 07:57.600
that they're up and running.

156
07:57.600 --> 08:00.400
So let's go over to our validator.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

156
07:57.600 --> 08:00.400
So let's go over to our validator.

157
08:00.400 --> 08:02.640
Here we can see the validator is up and running.

158
08:02.640 --> 08:08.960
If we do a show var, we see that it is on 20 dot 13 dot one, as it should be.

159
08:08.960 --> 08:11.680
Let's verify our controllers.

160
08:11.680 --> 08:14.320
Controller one again will do our show var.

161
08:14.320 --> 08:16.080
It's correct.

162
08:16.080 --> 08:18.040
And controller two.

163
08:18.040 --> 08:23.500
So we see that our controllers are up, our validators up, and now V manager one

164
08:23.500 --> 08:24.360
is working

165
08:24.360 --> 08:26.520
correctly.

166
08:26.520 --> 08:33.920
So in this video, we saw how to get all the nodes up and operating in CML 2.7.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

166
08:26.520 --> 08:33.920
So in this video, we saw how to get all the nodes up and operating in CML 2.7.

167
08:33.920 --> 08:41.720
Again, the main thing we saw here is that by default, the node definition for

168
08:41.720 --> 08:42.360
SDWAN

169
08:42.360 --> 08:46.800
manager, well, it's not exactly correct.

170
08:46.800 --> 08:48.880
It needs a little bit more RAM.

171
08:48.880 --> 08:52.800
Now there's a good possibility that Cisco will, of course, fix this in the

172
08:52.800 --> 08:53.400
future, but

173
08:53.400 --> 08:58.550
at least on the current version, we do need to bump up the RAM just a little

174
08:58.550 --> 08:59.000
bit for the

175
08:59.000 --> 09:04.980
services to actually be able to come online, start and be stable as they need
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

175
08:59.000 --> 09:04.980
services to actually be able to come online, start and be stable as they need

176
09:04.980 --> 09:05.520
to be.

177
09:05.520 --> 09:09.270
Now that this is functional, the next thing we need to do is put a baseline

178
09:09.270 --> 09:10.160
configuration

179
09:10.160 --> 09:14.040
on these devices and get them communicating with each other.

180
09:14.040 --> 09:16.240
That's exactly what we're going to tackle next.