WEBVTT

1
00:00.000 --> 00:01.000 align:middle line:84%


2
00:01.000 --> 00:03.730 align:middle line:90%
Sometimes a technology or
some new widget will show

3
00:03.730 --> 00:05.800 align:middle line:90%
and we'll think,
yeah it's all right,

4
00:05.800 --> 00:09.620 align:middle line:90%
until we see how it solves
a problem or the application

5
00:09.620 --> 00:10.348 align:middle line:84%
it was built for.

6
00:10.348 --> 00:12.640 align:middle line:90%
And once we see the need for
it we're like, oh my gosh,

7
00:12.640 --> 00:14.270 align:middle line:90%
where have you been
hiding all my life.

8
00:14.270 --> 00:16.062 align:middle line:90%
So, in this video I'd
like to chat with you

9
00:16.062 --> 00:19.330 align:middle line:90%
about some of those aha
moments regarding why FlexVPN

10
00:19.330 --> 00:21.670 align:middle line:90%
could step in and be
used as a technology

11
00:21.670 --> 00:23.480 align:middle line:84%
to meet a business need.

12
00:23.480 --> 00:25.265 align:middle line:90%
So, let's start
off with two sites.

13
00:25.265 --> 00:27.640 align:middle line:90%
We have site 1 over here on
the left and site 2 over here

14
00:27.640 --> 00:28.420 align:middle line:84%
on the right.

15
00:28.420 --> 00:30.520 align:middle line:90%
And if they want to have
a secure communications
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:28.420 --> 00:30.520 align:middle line:90%
And if they want to have
a secure communications

16
00:30.520 --> 00:32.680 align:middle line:90%
path over this
transit network, it

17
00:32.680 --> 00:34.180 align:middle line:90%
could be internet
or something else,

18
00:34.180 --> 00:36.620 align:middle line:90%
we could build a
site to site tunnel.

19
00:36.620 --> 00:38.860 align:middle line:90%
So, great we've done that
several different ways.

20
00:38.860 --> 00:41.320 align:middle line:90%
We've used crypto maps in
the past in the previous sets

21
00:41.320 --> 00:44.930 align:middle line:90%
of videos, we've used day
a tunnel interface, VTI,

22
00:44.930 --> 00:47.560 align:middle line:90%
a virtual tunnel
interface, fantastic.

23
00:47.560 --> 00:50.300 align:middle line:90%
And so, that's a pretty
simple task, no big deal.

24
00:50.300 --> 00:53.120 align:middle line:90%
We really don't need FlexVPN
for that functionality.

25
00:53.120 --> 00:54.950 align:middle line:90%
We can do it with
traditional methods.

26
00:54.950 --> 00:57.820 align:middle line:90%
However, what if there is
some kind of a big emergency

27
00:57.820 --> 00:59.920 align:middle line:90%
and all of a sudden we
need all of our employees

28
00:59.920 --> 01:01.520 align:middle line:84%
to connect from home.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
00:59.920 --> 01:01.520 align:middle line:84%
to connect from home.

29
01:01.520 --> 01:05.830 align:middle line:90%
So, we have Bob, and Lois,
and others who are all now

30
01:05.830 --> 01:07.420 align:middle line:90%
connecting from
their homes and they

31
01:07.420 --> 01:09.800 align:middle line:90%
need to connect into
our corporate network.

32
01:09.800 --> 01:12.130 align:middle line:90%
So, in addition to
the site-to-site VPN,

33
01:12.130 --> 01:15.640 align:middle line:90%
we now need remote access
VPNs and the remote access VPN

34
01:15.640 --> 01:17.920 align:middle line:90%
is going to involve
authentication as well.

35
01:17.920 --> 01:19.480 align:middle line:90%
So, when Bob or
Lois connects we're

36
01:19.480 --> 01:21.200 align:middle line:90%
going to have to
involve AAA, a RADIUS

37
01:21.200 --> 01:23.620 align:middle line:90%
server, or some type of
server on the back end that

38
01:23.620 --> 01:26.470 align:middle line:90%
can authenticate
them, allow them in,

39
01:26.470 --> 01:28.840 align:middle line:90%
including using
pools of addresses

40
01:28.840 --> 01:31.540 align:middle line:90%
or handing out dynamic IP
addresses for their journey
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:28.840 --> 01:31.540 align:middle line:90%
or handing out dynamic IP
addresses for their journey

41
01:31.540 --> 01:32.675 align:middle line:84%
on the network.

42
01:32.675 --> 01:34.300 align:middle line:90%
So, if we want a
solution that supports

43
01:34.300 --> 01:36.910 align:middle line:90%
the site-to-site tunnels
and the remote access VPNs,

44
01:36.910 --> 01:38.770 align:middle line:90%
we need something--
something more than just

45
01:38.770 --> 01:40.210 align:middle line:84%
our traditional options.

46
01:40.210 --> 01:44.080 align:middle line:90%
Also, what if we have
similar sites and these sites

47
01:44.080 --> 01:45.760 align:middle line:90%
all have a hub and
spoke configuration

48
01:45.760 --> 01:48.220 align:middle line:90%
with IPsec tunnels
and we said, oh we

49
01:48.220 --> 01:50.140 align:middle line:90%
need these two spokes,
these two sites,

50
01:50.140 --> 01:52.860 align:middle line:90%
to be able to talk directly to
each other including this guy

51
01:52.860 --> 01:53.600 align:middle line:84%
right here.

52
01:53.600 --> 01:55.642 align:middle line:90%
Now, one of the solutions
that we can do for that

53
01:55.642 --> 01:58.642 align:middle line:90%
is DMVPN, dynamic
multipoint VPNs,

54
01:58.642 --> 02:01.100 align:middle line:90%
and we've got a whole separate
set of videos based on that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
01:58.642 --> 02:01.100 align:middle line:90%
and we've got a whole separate
set of videos based on that.

55
02:01.100 --> 02:02.650 align:middle line:90%
And the big part
there is that it

56
02:02.650 --> 02:07.622 align:middle line:90%
uses multipoint sharing tunnel
interfaces and uses an HRP.

57
02:07.622 --> 02:09.830 align:middle line:90%
But what if we need to do
all these at the same time?

58
02:09.830 --> 02:11.920 align:middle line:90%
We need remote access,
we need site-to-site,

59
02:11.920 --> 02:14.240 align:middle line:90%
we need spoke-to-spoke,
can we do it.

60
02:14.240 --> 02:18.430 align:middle line:90%
And the answer is
yes, if we use VPN.

61
02:18.430 --> 02:22.480 align:middle line:90%
And even though FlexVPN does
have more modular components,

62
02:22.480 --> 02:25.060 align:middle line:90%
that's a good thing because
then we can mix and match.

63
02:25.060 --> 02:27.310 align:middle line:90%
And we can train a
device that, OK when

64
02:27.310 --> 02:30.430 align:middle line:90%
a remote user's connecting in,
based on where it's coming from
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:27.310 --> 02:30.430 align:middle line:90%
a remote user's connecting in,
based on where it's coming from

65
02:30.430 --> 02:32.200 align:middle line:84%
and the authentication, do this.

66
02:32.200 --> 02:34.330 align:middle line:90%
Or if they site-to-site
tunnel do that.

67
02:34.330 --> 02:37.360 align:middle line:90%
Or if it's a dynamic
spoke-to-spoke communication

68
02:37.360 --> 02:40.310 align:middle line:90%
using NHRP, it can
handle that as well.

69
02:40.310 --> 02:41.830 align:middle line:90%
And the goal is to
be able to handle

70
02:41.830 --> 02:44.440 align:middle line:90%
all of these types of
scenarios without having

71
02:44.440 --> 02:46.870 align:middle line:90%
to have separate dedicated
devices or appliances

72
02:46.870 --> 02:48.230 align:middle line:84%
for each function.

73
02:48.230 --> 02:50.230 align:middle line:90%
So, if we were to summarize
we could say this,

74
02:50.230 --> 02:54.278 align:middle line:90%
can FlexVPN do this regarding
IPsec communications

75
02:54.278 --> 02:54.820 align:middle line:84%
and security.

76
02:54.820 --> 02:56.350 align:middle line:90%
The answer is yes
and that includes

77
02:56.350 --> 02:59.080 align:middle line:90%
remote access, site-to-site,
AAA integration,

78
02:59.080 --> 03:03.790 align:middle line:90%
and a big part of FlexVPN is
that it uses IKE version 2.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
02:59.080 --> 03:03.790 align:middle line:90%
and a big part of FlexVPN is
that it uses IKE version 2.

79
03:03.790 --> 03:06.428 align:middle line:90%
And that's a big deal because
it's more interoperable.

80
03:06.428 --> 03:07.720 align:middle line:84%
So, if you have other vendors--

81
03:07.720 --> 03:10.487 align:middle line:90%
Check Point and Palo Alto--
and other gears and devices

82
03:10.487 --> 03:12.070 align:middle line:90%
that want to connect
into your network

83
03:12.070 --> 03:15.370 align:middle line:90%
and be part of the VPNs, well
if they support IKE version

84
03:15.370 --> 03:18.250 align:middle line:90%
2, which most of them
do, Cisco's FlexVPN

85
03:18.250 --> 03:20.590 align:middle line:90%
is built on IKE
version 2 as well.

86
03:20.590 --> 03:22.027 align:middle line:90%
That makes it more
interoperable.

87
03:22.027 --> 03:23.860 align:middle line:90%
So, now that we have
kind of a taste of some

88
03:23.860 --> 03:26.558 align:middle line:90%
of the functionality that
FlexVPN can bring to the table,

89
03:26.558 --> 03:28.600 align:middle line:90%
in the next video I'd like
to share with you some

90
03:28.600 --> 03:30.310 align:middle line:90%
of the individual
components and building
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
03:28.600 --> 03:30.310 align:middle line:90%
of the individual
components and building

91
03:30.310 --> 03:34.390 align:middle line:90%
blocks that are used when
implementing FlexVPN solutions.

92
03:34.390 --> 03:36.890 align:middle line:90%
So, I'll see you there
in just a moment.

93
03:36.890 --> 03:39.550 align:middle line:90%
Meanwhile, I hope this has
been informative for you

94
03:39.550 --> 03:42.900 align:middle line:90%
and I'd like to thank
you for viewing.