WEBVTT

1
00:00.000 --> 00:05.240
Next up is the V-bond server.

2
00:05.240 --> 00:10.510
Now, in the previous video, we already sort of alluded to some of the job of

3
00:10.510 --> 00:11.040
the V-bond

4
00:11.040 --> 00:16.680
server, but basically this is the connection manager for SD-WAN.

5
00:16.680 --> 00:18.920
You can call it the meeting point.

6
00:18.920 --> 00:21.880
This is where everything connects initially.

7
00:21.880 --> 00:26.540
The V-bond server then tells all the devices where everything else on the

8
00:26.540 --> 00:27.480
network is, and

9
00:27.480 --> 00:30.200
then they go form the proper connections.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:27.480 --> 00:30.200
then they go form the proper connections.

10
00:30.200 --> 00:35.530
This is also the only device that is required to have a public IP address for

11
00:35.530 --> 00:36.240
doing things

12
00:36.240 --> 00:38.280
such as zero-day deployment.

13
00:38.280 --> 00:44.780
So let's go ahead and take a look at a little bit more detail on the V-bond

14
00:44.780 --> 00:45.120
server.

15
00:45.120 --> 00:51.280
So the V-bond server is the connection manager for SD-WAN.

16
00:51.280 --> 00:56.140
This is where all of the devices initially connect in order to learn where the

17
00:56.140 --> 00:57.160
other devices

18
00:57.160 --> 00:59.400
are that they need to connect to.

19
00:59.400 --> 01:05.200
So essentially, this is coordinating the initial bring-up, in other words, the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:59.400 --> 01:05.200
So essentially, this is coordinating the initial bring-up, in other words, the

20
01:05.200 --> 01:06.920
first connection

21
01:06.920 --> 01:12.420
between things like the V-Smart controllers, the WAN edge devices.

22
01:12.420 --> 01:17.500
It also helps the V-Smart controllers find where the V-Manage server is.

23
01:17.500 --> 01:22.600
So it really coordinates all of the connections between all of the devices

24
01:22.600 --> 01:23.520
because it's the

25
01:23.520 --> 01:27.520
device that knows where everything is and is reachable.

26
01:27.520 --> 01:29.880
We'll get to that in just a moment.

27
01:29.880 --> 01:35.640
It also validates, makes sure that they are the correct devices and authentic
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:29.880 --> 01:35.640
It also validates, makes sure that they are the correct devices and authentic

28
01:35.640 --> 01:36.480
ates those

29
01:36.480 --> 01:39.480
devices as they join the network.

30
01:39.480 --> 01:44.600
So again, this is the first point of entry for a device coming into our SD-WAN

31
01:44.600 --> 01:45.800
environment.

32
01:45.800 --> 01:48.940
They first contact the V-bond server.

33
01:48.940 --> 01:52.300
Then we get to configuration of SD-WAN.

34
01:52.300 --> 01:58.460
We'll find out that one of the pieces of the zero-day configuration is to tell

35
01:58.460 --> 01:58.660
it what

36
01:58.660 --> 02:04.980
the address of the V-bond server is because this is the first point of contact.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:58.660 --> 02:04.980
the address of the V-bond server is because this is the first point of contact.

37
02:04.980 --> 02:11.420
Now because of that, this is going to require a public IP address.

38
02:11.420 --> 02:16.820
Now you can also get away with a one-to-one NAT mapping.

39
02:16.820 --> 02:20.600
If you're not familiar with what that means, it means that you're going to take

40
02:20.600 --> 02:21.260
one public

41
02:21.260 --> 02:25.780
IP address on the outside of your NAT device.

42
02:25.780 --> 02:28.700
And you're going to map that all ports.

43
02:28.700 --> 02:34.630
You're going to map that to the internal private address of the V-bond server,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
02:28.700 --> 02:34.630
You're going to map that to the internal private address of the V-bond server,

44
02:34.630 --> 02:34.940
which

45
02:34.940 --> 02:40.970
means effectively that one outside public address effectively belongs

46
02:40.970 --> 02:42.420
completely to the

47
02:42.420 --> 02:44.020
V-bond server.

48
02:44.020 --> 02:48.650
So we can get away with a one-to-one NAT mapping, but it is really recommended

49
02:48.650 --> 02:49.180
that it just

50
02:49.180 --> 02:54.620
has that public address that you are going to NAT it to to begin with.

51
02:54.620 --> 03:00.940
Now as far as communication goes, every V-bond server is going to maintain and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
02:54.620 --> 03:00.940
Now as far as communication goes, every V-bond server is going to maintain and

52
03:00.940 --> 03:01.700
create a

53
03:01.700 --> 03:03.900
DTLS tunnel.

54
03:03.900 --> 03:08.740
And we're going to build this to any other V-bond servers in the domain.

55
03:08.740 --> 03:13.170
This again would be to sort of team them or cluster them together so they have

56
03:13.170 --> 03:13.700
the same

57
03:13.700 --> 03:19.060
information and they can act for load sharing and redundancy.

58
03:19.060 --> 03:23.560
We're going to use that same DTLS technology and we're going to use that

59
03:23.560 --> 03:24.900
between the V-bond

60
03:24.900 --> 03:28.580
server and the WAN edge devices.

61
03:28.580 --> 03:34.040
So DTLS tunnels are what V-bond is going to use for its communication to get
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
03:28.580 --> 03:34.040
So DTLS tunnels are what V-bond is going to use for its communication to get

62
03:34.040 --> 03:34.780
everything

63
03:34.780 --> 03:36.580
up and running.

64
03:36.580 --> 03:40.860
Now like we said, V-bond is the connection manager.

65
03:40.860 --> 03:46.920
This means that it's going to orchestrate the connection between V-Smart and

66
03:46.920 --> 03:47.820
the WAN edge

67
03:47.820 --> 03:49.380
devices.

68
03:49.380 --> 03:54.350
And since it's orchestrating this connection, this is actually going to allow V

69
03:54.350 --> 03:55.980
-bond to handle

70
03:55.980 --> 04:02.540
NAT traversal for this connection between V-Smart and the WAN edge devices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:55.980 --> 04:02.540
NAT traversal for this connection between V-Smart and the WAN edge devices.

71
04:02.540 --> 04:09.010
This is why V-bond is the only one that actually needs a public IP address

72
04:09.010 --> 04:09.740
because it's going

73
04:09.740 --> 04:15.860
to handle the connections and any NAT that's needed in order to allow V-Smart

74
04:15.860 --> 04:16.620
to talk to

75
04:16.620 --> 04:18.740
the WAN edge device.

76
04:18.740 --> 04:24.420
And if you remember in our previous video, we talked about this already, how V-

77
04:24.420 --> 04:25.860
bond manages

78
04:25.860 --> 04:32.850
those connections to multiple V-Smart controllers allowing for our load
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
04:25.860 --> 04:32.850
those connections to multiple V-Smart controllers allowing for our load

79
04:32.850 --> 04:36.100
balancing and our redundancy.

80
04:36.100 --> 04:40.990
So V-bond is what's going to manage which V-Smart are connecting to which WAN

81
04:40.990 --> 04:43.660
edge devices.

82
04:43.660 --> 04:48.560
So in this video, we just got a quick introduction to the V-bond server, which

83
04:48.560 --> 04:49.980
again is essentially

84
04:49.980 --> 04:53.540
the connection manager for SD WAN.

85
04:53.540 --> 04:59.240
Now one thing we didn't put in here specifically, like we did with V-Manage and

86
04:59.240 --> 05:00.460
V-Smart is this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
04:59.240 --> 05:00.460
V-Smart is this

87
05:00.460 --> 05:04.380
is actually not running on a Linux server.

88
05:04.380 --> 05:08.670
This is still a virtual device usually, however it's going to be running on one

89
05:08.670 --> 05:09.460
of our virtual

90
05:09.460 --> 05:11.300
router platforms.

91
05:11.300 --> 05:13.860
So that is going to be one small difference.

92
05:13.860 --> 05:18.660
But from that perspective, it is still a virtual machine and we can still run

93
05:18.660 --> 05:19.780
it in our virtualized

94
05:19.780 --> 05:20.780
environment.

95
05:20.780 --> 05:25.890
Now, we've discussed our WAN edge devices quite a bit at this point, but we

96
05:25.890 --> 05:26.500
haven't

97
05:26.500 --> 05:30.140
actually talked too much about what they actually are.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
05:26.500 --> 05:30.140
actually talked too much about what they actually are.

98
05:30.140 --> 05:33.060
So let's go ahead and talk about that in the next video.