WEBVTT

1
00:00.000 --> 00:07.470
So now that we have all of our nodes up and running, the next step, of course,

2
00:07.470 --> 00:07.920
is to put

3
00:07.920 --> 00:14.130
a baseline configuration on them, configuring our VPN zero and our VPN 512

4
00:14.130 --> 00:16.040
management interface

5
00:16.040 --> 00:20.250
so that these devices can communicate with each other and we can get into them

6
00:20.250 --> 00:20.840
to manage

7
00:20.840 --> 00:22.400
them properly.

8
00:22.400 --> 00:26.120
So that's we're going to go ahead and configure in this video.

9
00:26.120 --> 00:31.560
And of course, we've seen these configurations before in a previous skill.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:26.120 --> 00:31.560
And of course, we've seen these configurations before in a previous skill.

10
00:31.560 --> 00:35.770
This time, all we're really going to be changing are the host names to sort of

11
00:35.770 --> 00:36.520
reflect the

12
00:36.520 --> 00:40.280
newer names that Cisco's using for these products.

13
00:40.280 --> 00:42.160
So let's go ahead and jump in.

14
00:42.160 --> 00:45.820
We're mostly just going to be pasting these configurations in and verifying

15
00:45.820 --> 00:46.480
that we have

16
00:46.480 --> 00:47.720
reachability.

17
00:47.720 --> 00:53.880
So let's go ahead and start with our SD WAN manager.

18
00:53.880 --> 00:59.290
So here on the manager one console, let's go ahead and paste in our baseline

19
00:59.290 --> 01:00.520
configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:59.290 --> 01:00.520
configuration.

20
01:00.520 --> 01:03.520
And in case it's been a while since you've looked at this, let's just give it a

21
01:03.520 --> 01:03.760
quick

22
01:03.760 --> 01:05.060
overview.

23
01:05.060 --> 01:08.840
So we're setting the host name to manager one.

24
01:08.840 --> 01:13.520
We're setting the system IP, the site ID, our organization name.

25
01:13.520 --> 01:17.960
Don't forget that, of course, has to match on everything.

26
01:17.960 --> 01:19.520
Then we're setting our clock.

27
01:19.520 --> 01:24.850
We're setting the V bond servers address, which is, of course, now the valid

28
01:24.850 --> 01:25.320
ator, but

29
01:25.320 --> 01:28.920
it's still called V bond in the configuration.

30
01:28.920 --> 01:34.800
Then we're configuring our VPN zero interface, which again, for the manager is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:28.920 --> 01:34.800
Then we're configuring our VPN zero interface, which again, for the manager is

31
01:34.800 --> 01:35.680
if zero.

32
01:35.680 --> 01:38.720
So we're giving it an IP address, bringing it up.

33
01:38.720 --> 01:43.640
And for now, configuring it not to be a tunnel interface.

34
01:43.640 --> 01:48.400
Remember we need to get certificates issued before we can bring this up as a

35
01:48.400 --> 01:48.880
tunnel.

36
01:48.880 --> 01:53.290
Then we're configuring our VPN 512 management interface, putting that on our

37
01:53.290 --> 01:55.400
management network,

38
01:55.400 --> 01:57.720
also bringing that online.

39
01:57.720 --> 02:03.760
And for both of our VPNs, we're setting an IP default route to the appropriate
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:57.720 --> 02:03.760
And for both of our VPNs, we're setting an IP default route to the appropriate

40
02:03.760 --> 02:04.800
gateway,

41
02:04.800 --> 02:09.440
where then, of course, committing and quitting, which, of course, commits the

42
02:09.440 --> 02:10.280
configuration

43
02:10.280 --> 02:13.280
and quits out of configuration mode.

44
02:13.280 --> 02:18.200
So now we're going to do the same basic thing for validator one.

45
02:18.200 --> 02:21.600
So as you can see, this configuration is almost the same.

46
02:21.600 --> 02:24.480
We have, of course, a few notable differences.

47
02:24.480 --> 02:27.640
First, of course, the host name is different.

48
02:27.640 --> 02:32.240
Clearly the IP addresses are going to be different on the V bond line.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
02:27.640 --> 02:32.240
Clearly the IP addresses are going to be different on the V bond line.

49
02:32.240 --> 02:37.320
Notice that we say local since this is the validator.

50
02:37.320 --> 02:42.720
Then of course, the interfaces themselves are slightly different for VPN zero.

51
02:42.720 --> 02:45.360
It's interface gigabit zero zero.

52
02:45.360 --> 02:50.000
And for VPN 512, it's ethernet zero.

53
02:50.000 --> 02:54.800
Other than that, this is primarily the same configuration.

54
02:54.800 --> 03:00.160
Controller one and controller two will be the same as manager one, because they
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:54.800 --> 03:00.160
Controller one and controller two will be the same as manager one, because they

55
03:00.160 --> 03:00.600
use the

56
03:00.600 --> 03:02.320
same interfaces.

57
03:02.320 --> 03:05.160
So let's go ahead and configure controller one.

58
03:05.160 --> 03:08.000
So there's the configuration for controller one.

59
03:08.000 --> 03:10.320
Let's do controller two as well.

60
03:10.320 --> 03:15.340
Again, these are pretty much identical aside from the obvious of the IP

61
03:15.340 --> 03:17.280
addresses themselves.

62
03:17.280 --> 03:21.880
So now that all of these have a baseline configuration, let's do some

63
03:21.880 --> 03:22.960
validation.

64
03:22.960 --> 03:25.720
Let's go over to manager one.

65
03:25.720 --> 03:29.960
From here, let's do a ping to 10 dot 100 dot 10 dot 216.

66
03:29.960 --> 03:31.840
That's the validator.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:29.960 --> 03:31.840
That's the validator.

67
03:31.840 --> 03:34.400
We can see that that's successful.

68
03:34.400 --> 03:36.760
Let's try to 17.

69
03:36.760 --> 03:42.720
That's of course, controller one to 18 is controller two.

70
03:42.720 --> 03:48.200
So we can see that we have reachability to all of the devices over VPN zero.

71
03:48.200 --> 03:50.960
Now let's try the management network.

72
03:50.960 --> 03:54.760
Let's do a ping from VPN 512.

73
03:54.760 --> 03:56.600
And we'll just ping the management gateway.

74
03:56.600 --> 04:00.080
We'll just say to ping one on two dot one six eight dot one dot one, which is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:56.600 --> 04:00.080
We'll just say to ping one on two dot one six eight dot one dot one, which is

75
04:00.080 --> 04:00.960
my management

76
04:00.960 --> 04:02.640
gateway.

77
04:02.640 --> 04:05.280
And we see we have reachability there as well.

78
04:05.280 --> 04:10.480
So theoretically, our management network should be working properly as well.

79
04:10.480 --> 04:15.930
If all of this is working properly, we should now be able to open our browser

80
04:15.930 --> 04:16.960
and navigate

81
04:16.960 --> 04:19.880
to the SD WAN manager.

82
04:19.880 --> 04:22.000
Let's verify that that's working.

83
04:22.000 --> 04:26.480
So here we see we get the login screen for catalyst SD WAN.

84
04:26.480 --> 04:31.720
We should be able to log in with admin and our password that we configured.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:26.480 --> 04:31.720
We should be able to log in with admin and our password that we configured.

85
04:31.720 --> 04:36.040
This is going to give us a lot of initial login splash screens.

86
04:36.040 --> 04:38.520
Let's just go ahead and close this for now.

87
04:38.520 --> 04:41.600
I'm just going to say do not show again.

88
04:41.600 --> 04:45.840
It's going to ask us to put in the credentials for our Cisco smart account.

89
04:45.840 --> 04:49.680
I'm also not going to configure this right now.

90
04:49.680 --> 04:52.280
So we'll simply say skip for now.

91
04:52.280 --> 04:57.180
We also get some banners up here warning us about the default login credentials

92
04:57.180 --> 04:57.360
and the

93
04:57.360 --> 05:01.710
fact that it doesn't have a V edge list yet, the organization name is not
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
04:57.360 --> 05:01.710
fact that it doesn't have a V edge list yet, the organization name is not

94
05:01.710 --> 05:02.800
configured.

95
05:02.800 --> 05:06.680
These are things that we're going to fix in the upcoming videos.

96
05:06.680 --> 05:10.280
So for now, we can simply dismiss these banners.

97
05:10.280 --> 05:16.800
And then we end up here on the catalyst SD WAN monitor overview homepage.

98
05:16.800 --> 05:18.400
So everything's up and working.

99
05:18.400 --> 05:19.960
We have reachability.

100
05:19.960 --> 05:25.840
However, there is one more cool thing we can do with CML 2.7.

101
05:25.840 --> 05:29.120
Now that these device types are actually supported.

102
05:29.120 --> 05:31.840
So let's go back over to CML.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:29.120 --> 05:31.840
So let's go back over to CML.

103
05:31.840 --> 05:35.400
What we can do now that they're supported is we can go to each device.

104
05:35.400 --> 05:37.800
We'll start with manager one.

105
05:37.800 --> 05:42.780
We can now go over to the configuration tab and actually tell it to fetch the

106
05:42.780 --> 05:43.920
configuration

107
05:43.920 --> 05:45.920
off of the device.

108
05:45.920 --> 05:50.440
This will now pull the config off of that device so that if we want to rebuild

109
05:50.440 --> 05:50.800
this

110
05:50.800 --> 05:53.880
or anything, we have the configuration.

111
05:53.880 --> 05:56.480
We can do this for each of our devices now.

112
05:56.480 --> 06:01.150
Again, we simply click on the device, tell it to fetch the configuration and it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
05:56.480 --> 06:01.150
Again, we simply click on the device, tell it to fetch the configuration and it

113
06:01.150 --> 06:01.480
'll pull

114
06:01.480 --> 06:04.640
the configuration off of that device.

115
06:04.640 --> 06:06.840
So we'll just pull all of them.

116
06:06.840 --> 06:14.200
And now we have our baseline configuration for each device here in CML.

117
06:14.200 --> 06:20.380
So in this video, we simply got our baseline configuration with IP addresses

118
06:20.380 --> 06:21.320
for our VPN

119
06:21.320 --> 06:28.220
zero and our VPN 512 interfaces configured and tested as well as making sure

120
06:28.220 --> 06:29.000
that the

121
06:29.000 --> 06:33.880
web interface is accessible on our SD WAN manager.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
06:29.000 --> 06:33.880
web interface is accessible on our SD WAN manager.

122
06:33.880 --> 06:38.920
We also took an opportunity here to back up all of our configurations.

123
06:38.920 --> 06:45.240
Now that CML 2.7 supports these devices, this option is available.

124
06:45.240 --> 06:50.410
On previous versions, yes, we could actually put these custom nodes into older

125
06:50.410 --> 06:51.080
versions

126
06:51.080 --> 06:52.800
of CML.

127
06:52.800 --> 06:57.290
But the downside was there was no way to save the configuration because CML

128
06:57.290 --> 06:57.920
didn't know

129
06:57.920 --> 07:01.640
how to handle those particular node types.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
06:57.920 --> 07:01.640
how to handle those particular node types.

130
07:01.640 --> 07:05.700
Well now that all this is up and running, our next step is going to be to

131
07:05.700 --> 07:06.720
actually add

132
07:06.720 --> 07:11.040
our different controllers into SD manager.

133
07:11.040 --> 07:15.100
For that, we're going to have to issue some certificates and add them into the

134
07:15.100 --> 07:15.760
graphical

135
07:15.760 --> 07:17.000
interface.

136
07:17.000 --> 07:19.040
So let's go ahead and do that next.

137
07:19.040 --> 07:44.480
[ Silence ]