WEBVTT

1
00:00.000 --> 00:05.000
So now we have the final moment of truth.

2
00:05.000 --> 00:09.680
We're going to boot these devices up, make sure that they boot properly, and

3
00:09.680 --> 00:09.840
that they

4
00:09.840 --> 00:12.440
have their correct interfaces.

5
00:12.440 --> 00:17.280
Now we're also going to have to do a little bit of configuration on vManage

6
00:17.280 --> 00:17.760
just so it

7
00:17.760 --> 00:22.870
can properly deploy, and so we can log in and verify that everything's

8
00:22.870 --> 00:24.080
functional.

9
00:24.080 --> 00:28.490
Also as part of this process, I'm going to show you how to access the console

10
00:28.490 --> 00:29.120
port on

11
00:29.120 --> 00:30.840
these devices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.120 --> 00:30.840
these devices.

12
00:30.840 --> 00:35.030
Now as I'm showing you that, it's going to be important to remember that we're

13
00:35.030 --> 00:35.340
able

14
00:35.340 --> 00:42.330
to do this because CML has a built-in terminal server that we can connect to

15
00:42.330 --> 00:43.460
and use that

16
00:43.460 --> 00:46.520
to piggyback into the console ports.

17
00:46.520 --> 00:50.630
So I'll show you the syntax for doing that and how to change it for each

18
00:50.630 --> 00:52.320
different device.

19
00:52.320 --> 00:57.370
So all of that said, let's jump in and get our vManage server up and running,

20
00:57.370 --> 00:57.920
and then

21
00:57.920 --> 01:03.800
we'll fire up VBond and VSmart.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:57.920 --> 01:03.800
we'll fire up VBond and VSmart.

22
01:03.800 --> 01:06.920
So we'll start off by booting up vManage.

23
01:06.920 --> 01:10.780
We'll simply right-click on that node, say Start, and then we're going to

24
01:10.780 --> 01:11.520
switch over

25
01:11.520 --> 01:13.880
to Secure CRT.

26
01:13.880 --> 01:18.000
We'll connect to the console and ensure that this is booting up.

27
01:18.000 --> 01:20.680
So we can see here that it is in fact booting up.

28
01:20.680 --> 01:24.200
Now this is going to take a few moments, but while it is, let me show you how

29
01:24.200 --> 01:24.720
you can

30
01:24.720 --> 01:27.760
connect to the console on these devices.

31
01:27.760 --> 01:33.210
If I go to File, Connect, and I look at the properties for this console, there
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:27.760 --> 01:33.210
If I go to File, Connect, and I look at the properties for this console, there

32
01:33.210 --> 01:33.600
's sort

33
01:33.600 --> 01:35.640
of two things we need to notice.

34
01:35.640 --> 01:42.640
First is that if we look at SSH itself, we're connecting to the CML to server

35
01:42.640 --> 01:43.760
itself.

36
01:43.760 --> 01:46.720
In my case, that's an internal address, of course.

37
01:46.720 --> 01:50.960
I have it at 192.168.1.200.

38
01:50.960 --> 01:55.520
And it's connecting on the standard SSH port of 22.

39
01:55.520 --> 02:00.280
So what makes this special is what's under the login actions.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:55.520 --> 02:00.280
So what makes this special is what's under the login actions.

40
02:00.280 --> 02:05.300
And what we see is the first thing it's looking for when it connects is the

41
02:05.300 --> 02:07.560
word consoles.

42
02:07.560 --> 02:10.880
Then it's opening this string.

43
02:10.880 --> 02:14.840
And if we look at this string, the way it's formatted is it's forward slash,

44
02:14.840 --> 02:15.400
and then

45
02:15.400 --> 02:22.560
the name of your lab, forward slash, the name of the device, forward slash, the

46
02:22.560 --> 02:23.200
port you

47
02:23.200 --> 02:25.160
wish to connect to.

48
02:25.160 --> 02:29.000
On these devices, port zero is the console.

49
02:29.000 --> 02:33.160
So this is how we connect to the console on these different devices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:29.000 --> 02:33.160
So this is how we connect to the console on these different devices.

50
02:33.160 --> 02:35.320
Now two things about this.

51
02:35.320 --> 02:39.440
Number one, of course, if you choose to rename the lab, you would have to

52
02:39.440 --> 02:41.600
change that string.

53
02:41.600 --> 02:47.680
Also if you rename the devices, you would need to modify that string as well.

54
02:47.680 --> 02:51.400
Then for the rest of this, I simply have it looking for a specific string of

55
02:51.400 --> 02:52.360
characters,

56
02:52.360 --> 02:56.550
which comes up right at the end after you connect, and it's sending a carriage

57
02:56.550 --> 02:57.320
return.

58
02:57.320 --> 03:03.010
And then it's logging in with the username admin and my super secret password
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:57.320 --> 03:03.010
And then it's logging in with the username admin and my super secret password

59
03:03.010 --> 03:03.840
123 for

60
03:03.840 --> 03:09.480
capital Q capital W er, which isn't really all that super secret.

61
03:09.480 --> 03:12.280
I just use this, of course, for labs.

62
03:12.280 --> 03:15.280
And that's why I don't even bother to hide it.

63
03:15.280 --> 03:20.750
So if you wanted to make this for other sessions, you could simply copy this

64
03:20.750 --> 03:21.720
and then change

65
03:21.720 --> 03:26.480
the name of the device you're connecting to in each of those other sessions.

66
03:26.480 --> 03:32.120
But this is how we can connect to the console of a device running in CML.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:26.480 --> 03:32.120
But this is how we can connect to the console of a device running in CML.

67
03:32.120 --> 03:34.760
So now let's go back to our brute process.

68
03:34.760 --> 03:37.160
We'll simply cancel out of this.

69
03:37.160 --> 03:41.940
Now because of that login script you just saw, this is actually trying to send

70
03:41.940 --> 03:42.880
the password

71
03:42.880 --> 03:45.120
that I change this to.

72
03:45.120 --> 03:49.840
And as of right now, it's still going to be the default of admin admin.

73
03:49.840 --> 03:52.720
That's why it's got that incorrect login there.

74
03:52.720 --> 03:53.800
It wants me to set it.

75
03:53.800 --> 03:57.960
And this is where I'm going to put in the one, two, three, four Q, W, E, R.

76
03:57.960 --> 04:02.680
And then V Manage is going to ask us a very important question.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:57.960 --> 04:02.680
And then V Manage is going to ask us a very important question.

77
04:02.680 --> 04:07.720
What is our persona going to be on this device?

78
04:07.720 --> 04:13.360
The persona basically means how is this device going to operate?

79
04:13.360 --> 04:16.520
What components is it going to run?

80
04:16.520 --> 04:19.440
And as you can see, there's pretty much three choices.

81
04:19.440 --> 04:23.810
It can either run compute and data, which means it's going to be the management

82
04:23.810 --> 04:24.320
server

83
04:24.320 --> 04:29.280
and the database, or you can split these two components up.

84
04:29.280 --> 04:35.180
Now this is more of an SD-WAN topic, but for scalability you can separate the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:29.280 --> 04:35.180
Now this is more of an SD-WAN topic, but for scalability you can separate the

85
04:35.180 --> 04:35.840
data from

86
04:35.840 --> 04:40.800
the compute and you would of course have one device serving as the database

87
04:40.800 --> 04:41.640
server and

88
04:41.640 --> 04:45.640
the other device functioning as the manager itself.

89
04:45.640 --> 04:49.440
This is a relatively small environment and we want both functions.

90
04:49.440 --> 04:53.480
So we're just going to say one, it's then going to say, are you sure?

91
04:53.480 --> 04:55.760
We'll say yes, we are.

92
04:55.760 --> 05:00.400
Then it asks us what to use for that database storage.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
04:55.760 --> 05:00.400
Then it asks us what to use for that database storage.

93
05:00.400 --> 05:05.740
Well in this case, we only have that 100 gig device that we added when we were

94
05:05.740 --> 05:06.520
creating

95
05:06.520 --> 05:08.240
our node definition.

96
05:08.240 --> 05:09.800
So that's what we want to use.

97
05:09.800 --> 05:13.520
We're just going to say one to select SDB.

98
05:13.520 --> 05:16.280
It's going to ask us if we want to format it.

99
05:16.280 --> 05:22.280
We'll say yes, we'll hit enter and this is going to again take a few moments.

100
05:22.280 --> 05:24.240
It's going to format the drive.

101
05:24.240 --> 05:27.800
It's going to expand some packages onto that drive that it needs.

102
05:27.800 --> 05:31.610
It's going to reboot the server and then it's going to come back up, restart
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:27.800 --> 05:31.610
It's going to reboot the server and then it's going to come back up, restart

103
05:31.610 --> 05:32.000
all of

104
05:32.000 --> 05:36.080
its services and then we'll be able to log in again.

105
05:36.080 --> 05:39.120
This is going to take probably about five minutes.

106
05:39.120 --> 05:44.050
So we will wait and we'll fast forward and come back online as soon as it's

107
05:44.050 --> 05:44.800
back up to

108
05:44.800 --> 05:46.680
the login prompt.

109
05:46.680 --> 05:52.350
So this has fully rebooted come back up and we can go ahead and log in and we

110
05:52.350 --> 05:52.960
see that

111
05:52.960 --> 05:55.440
we're connected to VManage.

112
05:55.440 --> 05:59.110
Now the first thing to note is right here it is showing us that it is the

113
05:59.110 --> 06:00.240
correct version.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
05:59.110 --> 06:00.240
correct version.

114
06:00.240 --> 06:02.920
So it's 20 dot 10 dot one.

115
06:02.920 --> 06:09.850
And if we do a show interface, we can see that we have VPN zero with our ETH

116
06:09.850 --> 06:11.040
zero interface

117
06:11.040 --> 06:17.840
and at least for now we have our ETH one interface also in VPN zero.

118
06:17.840 --> 06:22.200
So this is unconfigured, but we do see that we have our interfaces.

119
06:22.200 --> 06:25.760
So next let's go ahead and boot up the bond.

120
06:25.760 --> 06:29.280
So we can actually start V bond and be smart together.

121
06:29.280 --> 06:33.950
Let's just right click on both nodes and go to start and then we'll switch back
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
06:29.280 --> 06:33.950
Let's just right click on both nodes and go to start and then we'll switch back

122
06:33.950 --> 06:34.360
over

123
06:34.360 --> 06:36.640
to the consoles for the console.

124
06:36.640 --> 06:38.880
We'll start on V bond.

125
06:38.880 --> 06:41.960
So here we see that V bond is in the process of booting.

126
06:41.960 --> 06:45.400
Let's go ahead and open the console to be smart as well.

127
06:45.400 --> 06:49.610
And while we're waiting for some output here, notice that this is going through

128
06:49.610 --> 06:51.200
the CML2

129
06:51.200 --> 06:52.480
console server.

130
06:52.480 --> 06:55.480
So that is how we're getting into these consoles.

131
06:55.480 --> 07:00.040
So here we see that it's booted up, but still waiting to process some services.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

131
06:55.480 --> 07:00.040
So here we see that it's booted up, but still waiting to process some services.

132
07:00.040 --> 07:03.280
So let's go back over and check on V bond.

133
07:03.280 --> 07:08.140
So V bond is also still initializing and we're getting that incorrect login

134
07:08.140 --> 07:09.200
once again,

135
07:09.200 --> 07:14.160
because my login script is trying to send the password that I use, not the

136
07:14.160 --> 07:15.080
default.

137
07:15.080 --> 07:17.800
So once again, we'll give these just a few moments.

138
07:17.800 --> 07:22.200
We'll jump ahead to where this says that the system is ready.

139
07:22.200 --> 07:24.880
So now V bond is saying the system is ready.

140
07:24.880 --> 07:27.400
Let's go ahead and log in.

141
07:27.400 --> 07:29.480
Again, it's going to fail because of my login script.

142
07:29.480 --> 07:31.480
So we'll just do it again.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
07:29.480 --> 07:31.480
So we'll just do it again.

143
07:31.480 --> 07:33.680
The default again is admin admin.

144
07:33.680 --> 07:37.280
And now we're going to change it to the password that I use.

145
07:37.280 --> 07:38.600
Now we're on V edge.

146
07:38.600 --> 07:43.080
Again, we can see the version is correct 20 dot 10 dot one.

147
07:43.080 --> 07:48.100
And if we do our show interface here, we see that VPN zero does in fact have

148
07:48.100 --> 07:48.800
gigabit

149
07:48.800 --> 07:56.680
zero slash zero and our interface is zero is in VPN 512.

150
07:56.680 --> 07:59.080
Again nothing else is configured at this point.

151
07:59.080 --> 08:02.860
That's just what we want to make sure is we have the correct interfaces up and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
07:59.080 --> 08:02.860
That's just what we want to make sure is we have the correct interfaces up and

152
08:02.860 --> 08:03.640
configure.

153
08:03.640 --> 08:06.680
So now let's jump over and check V smart.

154
08:06.680 --> 08:07.960
We'll log in again.

155
08:07.960 --> 08:12.150
It's going to send the wrong password just because of my login script and we'll

156
08:12.150 --> 08:12.600
change

157
08:12.600 --> 08:15.800
it to the password that we want to use.

158
08:15.800 --> 08:20.700
As that's done, of course, we verify the version 20 dot 10 dot one and we do

159
08:20.700 --> 08:23.080
our show interface.

160
08:23.080 --> 08:28.440
And we see that just like V manage, we have our e zero and our e one, both

161
08:28.440 --> 08:29.760
currently part

162
08:29.760 --> 08:31.960
of VPN zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

162
08:29.760 --> 08:31.960
of VPN zero.

163
08:31.960 --> 08:36.990
So these are up and running with the correct versions and the correct

164
08:36.990 --> 08:38.320
interfaces.

165
08:38.320 --> 08:42.760
So now that our devices are booted up running as they're supposed to, we're now

166
08:42.760 --> 08:43.360
ready to

167
08:43.360 --> 08:48.600
move on and start actually configuring the SD WAN environment, which is what we

168
08:48.600 --> 08:49.040
're going

169
08:49.040 --> 08:52.840
to be doing in the next skill for now.

170
08:52.840 --> 08:57.600
That concludes everything we need to cover here, except for our challenge.

171
08:57.600 --> 09:00.160
So jump in, give the challenge a shot.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

171
08:57.600 --> 09:00.160
So jump in, give the challenge a shot.

172
09:00.160 --> 09:01.000
Good luck.

173
09:01.000 --> 09:02.800
And I'll see you in the solution.