WEBVTT

1
00:00.000 --> 00:10.280
So now let's jump in and put a baseline configuration on our vSmart, vManage,

2
00:10.280 --> 00:12.660
and vBond servers.

3
00:12.660 --> 00:17.020
So our main focus here is going to be just things like setting the hostname and

4
00:17.020 --> 00:17.920
configuring

5
00:17.920 --> 00:24.340
our underlay network for VPN zero, which is what we use for our control plane

6
00:24.340 --> 00:25.160
tunnels

7
00:25.160 --> 00:30.950
and will also configure VPN 512, which is basically like the out of band
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:25.160 --> 00:30.950
and will also configure VPN 512, which is basically like the out of band

8
00:30.950 --> 00:33.280
management interface.

9
00:33.280 --> 00:38.940
Now for this particular video, I will be using IP addresses that work in my lab

10
00:38.940 --> 00:40.040
environment

11
00:40.040 --> 00:42.720
because I have a lot of lab devices.

12
00:42.720 --> 00:46.440
If these IP addresses, of course, don't work in your environment, feel free to

13
00:46.440 --> 00:46.920
change the

14
00:46.920 --> 00:48.360
IP addresses.

15
00:48.360 --> 00:52.250
But this is the basic configuration that we need to put on these devices to get

16
00:52.250 --> 00:52.600
them

17
00:52.600 --> 00:53.720
up and running.

18
00:53.720 --> 00:56.120
So let's go ahead and jump into the command line.

19
00:56.120 --> 00:59.720
Remember, these are completely unconfigured at this point.

20
00:59.720 --> 01:02.920
So we will have to be using console access.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:59.720 --> 01:02.920
So we will have to be using console access.

21
01:02.920 --> 01:05.840
Let's jump in.

22
01:05.840 --> 01:09.680
So we'll start off here on the console of vManage.

23
01:09.680 --> 01:13.400
And of course, the first thing we want to do is go into configuration mode.

24
01:13.400 --> 01:16.840
And then we're going to go into system configuration mode.

25
01:16.840 --> 01:21.000
And here's where we set things like we can set the hostname.

26
01:21.000 --> 01:25.760
Now the current hostname is vManage and we're going to keep it almost the same.

27
01:25.760 --> 01:29.760
We'll simply capitalize the M. That's how Cisco usually writes it.

28
01:29.760 --> 01:32.280
So we'll just say hostname vManage.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:29.760 --> 01:32.280
So we'll just say hostname vManage.

29
01:32.280 --> 01:39.480
Now notice if you're familiar with things like iOS and iOS Xe, this is similar.

30
01:39.480 --> 01:42.820
Of course, you can also tell by the fact that we went into system that it's, of

31
01:42.820 --> 01:43.280
course,

32
01:43.280 --> 01:45.000
a little bit different.

33
01:45.000 --> 01:48.280
Also notice that the hostname hasn't changed yet.

34
01:48.280 --> 01:51.240
We have to actually commit these changes.

35
01:51.240 --> 01:55.020
But let's just keep going because we can put all of our changes in at once and

36
01:55.020 --> 01:55.720
then commit

37
01:55.720 --> 01:56.720
them.

38
01:56.720 --> 02:01.040
The next thing we want to do is you want to set the system IP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:56.720 --> 02:01.040
The next thing we want to do is you want to set the system IP.

39
02:01.040 --> 02:03.520
Now once again, you can sort of do whatever you want here.

40
02:03.520 --> 02:08.800
I'm going to use 10.255.255.215.

41
02:08.800 --> 02:12.320
That's because this is the same IP address I'm going to use for the interfaces,

42
02:12.320 --> 02:13.000
meaning

43
02:13.000 --> 02:17.560
my vManage host is going to be .215.

44
02:17.560 --> 02:20.720
The rest of that address, of course, will be different, but I'm going to keep

45
02:20.720 --> 02:21.480
215 as the

46
02:21.480 --> 02:23.200
host portion.

47
02:23.200 --> 02:26.680
We also want to put it in an SD-WAN site.

48
02:26.680 --> 02:28.640
So we'll set the site ID.

49
02:28.640 --> 02:29.880
This is going to be our headquarters.

50
02:29.880 --> 02:33.160
We'll just make this site ID 100.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:29.880 --> 02:33.160
We'll just make this site ID 100.

51
02:33.160 --> 02:37.120
Another common thing to put in is admin tech on failure.

52
02:37.120 --> 02:40.940
Of course, one of the most important things is going to be the organization

53
02:40.940 --> 02:41.440
name.

54
02:41.440 --> 02:48.360
Our organization name, as we put in before, is a any underscore SD-WAN.

55
02:48.360 --> 02:52.630
This of course has to match what we set up on Cisco and it's going to have to

56
02:52.630 --> 02:53.400
match what

57
02:53.400 --> 02:55.760
we set in our certificates.

58
02:55.760 --> 02:58.240
So we have our organization.

59
02:58.240 --> 03:01.520
Another common thing to do is set the time zone.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
02:58.240 --> 03:01.520
Another common thing to do is set the time zone.

60
03:01.520 --> 03:04.480
In my case, it's America.

61
03:04.480 --> 03:10.240
And although this is not where I am, New York is the appropriate time zone.

62
03:10.240 --> 03:13.800
I'm simply on the east coast of the United States.

63
03:13.800 --> 03:16.880
The next thing we want to do is configure the VBOM server.

64
03:16.880 --> 03:22.440
That's going to be at 10.100 because we're putting this on VLAN 100 dot 10 dot.

65
03:22.440 --> 03:25.360
And again, I'm going to make that to 16.

66
03:25.360 --> 03:31.000
So the VBOM server is going to be one IP address higher than RV manage.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:25.360 --> 03:31.000
So the VBOM server is going to be one IP address higher than RV manage.

67
03:31.000 --> 03:34.840
Next thing we want to do is start configuring our VPN zero.

68
03:34.840 --> 03:38.320
So we'll go into VPN zero configuration mode.

69
03:38.320 --> 03:41.240
And we have to assign an actual interface to it.

70
03:41.240 --> 03:43.760
This is going to be a zero.

71
03:43.760 --> 03:46.280
We need to set its IP address.

72
03:46.280 --> 03:50.200
Again, it's going to be 10 dot 100 dot 10 dot 215.

73
03:50.200 --> 03:53.200
And this is going to be a slash 24.

74
03:53.200 --> 03:56.800
We'll bring that interface up with a no shutdown.

75
03:56.800 --> 04:02.160
And we also want to make sure we configure this as no tunnel interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
03:56.800 --> 04:02.160
And we also want to make sure we configure this as no tunnel interface.

76
04:02.160 --> 04:07.550
We can't bring up the tunnel interface on VPN zero until we actually have our

77
04:07.550 --> 04:08.840
certificates.

78
04:08.840 --> 04:14.560
So we will be turning this no tunnel interfaces back off, but not yet.

79
04:14.560 --> 04:17.640
Also I don't really need this in my environment.

80
04:17.640 --> 04:22.360
However, if you do need a default route here, you could say something like IP

81
04:22.360 --> 04:23.080
route, zero

82
04:23.080 --> 04:28.650
zero zero zero slash zero and point it to its next hop, which if I was going to

83
04:28.650 --> 04:29.320
have one

84
04:29.320 --> 04:33.320
here would be 10 dot 100 dot 10 dot one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:29.320 --> 04:33.320
here would be 10 dot 100 dot 10 dot one.

85
04:33.320 --> 04:37.390
Again in my environment for now, everything on VPN zero is going to be on the

86
04:37.390 --> 04:39.240
same subnet.

87
04:39.240 --> 04:41.360
We'll exit that configuration.

88
04:41.360 --> 04:46.870
And now we'll go into VPN 512, which again is our out of band management

89
04:46.870 --> 04:47.960
interface.

90
04:47.960 --> 04:52.810
For this one, we're going to assign interface, if one, the IP address is going

91
04:52.810 --> 04:57.920
to be 192.168.1.215/24.

92
04:57.920 --> 04:59.840
That's for my network.

93
04:59.840 --> 05:02.520
We'll bring this up with a no shut.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
04:59.840 --> 05:02.520
We'll bring this up with a no shut.

94
05:02.520 --> 05:06.190
And in my environment, I actually do need a default route for this network

95
05:06.190 --> 05:06.480
since I'm

96
05:06.480 --> 05:09.760
managing it off of that management network.

97
05:09.760 --> 05:14.440
And that default route is going to be to 192.168.1.1.

98
05:14.440 --> 05:20.070
Now we could just commit at this point, but notice that we can do an end quit,

99
05:20.070 --> 05:20.320
which will

100
05:20.320 --> 05:24.880
commit our changes and take us out of configuration mode.

101
05:24.880 --> 05:27.800
Notice that now our host name is correct.

102
05:27.800 --> 05:31.480
So everything we put here on V manage should be correct.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:27.800 --> 05:31.480
So everything we put here on V manage should be correct.

103
05:31.480 --> 05:35.000
Let's go ahead and jump over to the console of our V bond server.

104
05:35.000 --> 05:37.760
We'll go into configuration mode.

105
05:37.760 --> 05:43.100
And this is going to be exactly the same configuration aside from the IP

106
05:43.100 --> 05:44.440
addresses are going to

107
05:44.440 --> 05:46.840
be dot 216.

108
05:46.840 --> 05:52.560
And when we specify our V bond server, we're going to specify that it's the

109
05:52.560 --> 05:53.960
local server.

110
05:53.960 --> 05:56.480
Other than that, it's the same configuration.

111
05:56.480 --> 05:58.680
So let's just paste it in.

112
05:58.680 --> 06:02.700
So again, the real change aside from the fact that all of the addresses end in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
05:58.680 --> 06:02.700
So again, the real change aside from the fact that all of the addresses end in

113
06:02.700 --> 06:04.040
dot 216 instead

114
06:04.040 --> 06:10.460
of dot 215 is this line right here, the V bond where it's pointing to its own

115
06:10.460 --> 06:11.440
address.

116
06:11.440 --> 06:13.440
And it says local.

117
06:13.440 --> 06:19.040
That's telling this device that it is the V bond server.

118
06:19.040 --> 06:21.480
Everything else here looks correct.

119
06:21.480 --> 06:23.880
So let's do our commit and quit.

120
06:23.880 --> 06:26.440
We see that our host names changed.

121
06:26.440 --> 06:31.000
And I seem to always get that error telling me that an item already exists.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
06:26.440 --> 06:31.000
And I seem to always get that error telling me that an item already exists.

122
06:31.000 --> 06:34.320
And I'm fairly certain that's because the one interface that I'm putting in is

123
06:34.320 --> 06:34.760
already

124
06:34.760 --> 06:35.760
in the VPN.

125
06:35.760 --> 06:37.680
So it's not really an issue.

126
06:37.680 --> 06:41.120
It takes our configuration and everything works fine.

127
06:41.120 --> 06:45.880
So let's go over to be smart next in the configuration mode.

128
06:45.880 --> 06:51.140
Once again, we'll just paste in the configuration, making sure everything is

129
06:51.140 --> 06:51.720
correct here.

130
06:51.720 --> 06:53.920
And we'll do our commit and quit.

131
06:53.920 --> 06:55.920
So let's do some verification.

132
06:55.920 --> 06:58.480
Let's jump back over to V manage.

133
06:58.480 --> 07:00.800
And let's just verify a few things here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
06:58.480 --> 07:00.800
And let's just verify a few things here.

134
07:00.800 --> 07:08.600
First, let's try a ping to 10 dot 100 dot 10 dot 216, which should be V bond.

135
07:08.600 --> 07:11.160
We can see that's working successfully.

136
07:11.160 --> 07:14.440
We should also be able to ping to 17.

137
07:14.440 --> 07:16.720
That's also working successfully.

138
07:16.720 --> 07:22.320
And we should be able to ping our default gateway for our management network.

139
07:22.320 --> 07:31.720
So we can say ping from VPN 512 to the 192 dot 168 dot 1 dot 1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

139
07:22.320 --> 07:31.720
So we can say ping from VPN 512 to the 192 dot 168 dot 1 dot 1.

140
07:31.720 --> 07:33.520
So that's successful.

141
07:33.520 --> 07:38.290
And if everything on my network is working correctly, I should now be able to

142
07:38.290 --> 07:38.880
open the

143
07:38.880 --> 07:42.440
graphical interface on V manage.

144
07:42.440 --> 07:49.200
So let's open up Firefox and navigate to V manages IP address.

145
07:49.200 --> 07:53.840
So here we can see I've opened the IP address of my V manage server.

146
07:53.840 --> 08:01.130
Now just so you know, when you see me navigate to 192 dot 168 dot 2 dot 215,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

146
07:53.840 --> 08:01.130
Now just so you know, when you see me navigate to 192 dot 168 dot 2 dot 215,

147
08:01.130 --> 08:02.240
that's simply

148
08:02.240 --> 08:06.560
because I have not this being done in my lab environment.

149
08:06.560 --> 08:13.000
That address simply gets natted to the 192 dot 168 dot 1 dot 215 address.

150
08:13.000 --> 08:15.920
I do this mostly for portability.

151
08:15.920 --> 08:19.520
But now that we're connected to our V manage server, we should be able to log

152
08:19.520 --> 08:19.960
in.

153
08:19.960 --> 08:23.200
The default username is going to be admin.

154
08:23.200 --> 08:31.440
And the password should be what we configured the 1234 capital Q capital W er.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
08:23.200 --> 08:31.440
And the password should be what we configured the 1234 capital Q capital W er.

155
08:31.440 --> 08:33.600
We'll go ahead and log in.

156
08:33.600 --> 08:35.360
We see that we're connected.

157
08:35.360 --> 08:37.800
We're in our SD WAN interface.

158
08:37.800 --> 08:41.120
Now of course, we do have some messages up here at the top.

159
08:41.120 --> 08:44.400
The first one is the warning about the login credentials.

160
08:44.400 --> 08:47.980
And we're not going to be fixing that in this skill.

161
08:47.980 --> 08:52.640
So that first error message, we can simply dismiss the secondary message is

162
08:52.640 --> 08:53.720
telling us

163
08:53.720 --> 08:57.000
that it failed to create a V edge list.

164
08:57.000 --> 09:02.000
Well, that one will actually be fixing through the rest of this skill.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

164
08:57.000 --> 09:02.000
Well, that one will actually be fixing through the rest of this skill.

165
09:02.000 --> 09:06.400
But that takes care of what we need to do in this video.

166
09:06.400 --> 09:12.130
So the next thing we have to do is configure some form of certificates in our

167
09:12.130 --> 09:13.560
environment.

168
09:13.560 --> 09:18.600
We'll talk about more detail on that in the next video and get them created and

169
09:18.600 --> 09:19.320
installed.