WEBVTT

1
00:00.000 --> 00:08.800
So for our IPsec VPN, we're going to be using pre-shared keys with our iKV2

2
00:08.800 --> 00:10.440
configuration.

3
00:10.440 --> 00:15.680
Now I'm going to use a relatively long random key here, but you could feel free

4
00:15.680 --> 00:15.960
to just

5
00:15.960 --> 00:20.960
use something like Cisco 123 given that this is just a lab environment.

6
00:20.960 --> 00:27.710
However, that said, we're also going to need our inside and outside addresses

7
00:27.710 --> 00:28.560
for both

8
00:28.560 --> 00:32.540
on-prem R1 and Azure R1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:28.560 --> 00:32.540
on-prem R1 and Azure R1.

9
00:32.540 --> 00:37.090
Some components need the public IP address and some of these components are

10
00:37.090 --> 00:38.000
going to need

11
00:38.000 --> 00:39.840
the private IP address.

12
00:39.840 --> 00:44.910
So please be sure to have that information handy as we jump into these various

13
00:44.910 --> 00:46.000
videos configuring

14
00:46.000 --> 00:48.120
our IPsec VPN.

15
00:48.120 --> 00:54.120
That said, let's jump in and begin configuring our key rings.

16
00:54.120 --> 00:57.760
So we'll start off here on on-prem R1.

17
00:57.760 --> 01:00.440
Of course, we'll simply go into configuration mode.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:57.760 --> 01:00.440
Of course, we'll simply go into configuration mode.

18
01:00.440 --> 01:04.520
The first thing we want to do is just create our keychain.

19
01:04.520 --> 01:09.960
So we do this by saying crypto iKV2 key ring and then we give it a name.

20
01:09.960 --> 01:12.480
We'll just call ours azure keys.

21
01:12.480 --> 01:14.200
We'll hit enter.

22
01:14.200 --> 01:16.840
The next thing we have to do is configure up here.

23
01:16.840 --> 01:18.720
So this is just giving it a name.

24
01:18.720 --> 01:21.480
So in this case, we'll just call it azure tunnel one.

25
01:21.480 --> 01:23.120
We'll hit enter.

26
01:23.120 --> 01:26.680
Then we put in the IP address of the peer.

27
01:26.680 --> 01:29.480
This is going to be the public IP address.

28
01:29.480 --> 01:34.210
So if you don't know what this is, you can of course get this from the Azure
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:29.480 --> 01:34.210
So if you don't know what this is, you can of course get this from the Azure

29
01:34.210 --> 01:35.000
dashboard,

30
01:35.000 --> 01:39.520
but it should be the outside address of Azure R1.

31
01:39.520 --> 01:42.120
Next we put in our pre-shared local key.

32
01:42.120 --> 01:45.420
And again, this is where you can use something simple or you can use a more

33
01:45.420 --> 01:46.440
complicated string

34
01:46.440 --> 01:47.440
like I'm using.

35
01:47.440 --> 01:50.920
It really doesn't make any difference being a lab environment.

36
01:50.920 --> 01:55.400
Normally, of course, best practice would be to use a long randomly generated

37
01:55.400 --> 01:56.000
key like

38
01:56.000 --> 01:57.480
I'm using.

39
01:57.480 --> 02:00.360
You also have to put the remote key in here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:57.480 --> 02:00.360
You also have to put the remote key in here.

40
02:00.360 --> 02:02.920
And this is what I mentioned during the introduction.

41
02:02.920 --> 02:07.110
These could technically be different as long as you put them in inverted on the

42
02:07.110 --> 02:08.440
other side.

43
02:08.440 --> 02:12.920
So that my local Azure remote and your remote is my local essentially.

44
02:12.920 --> 02:16.030
But in my experience, there's not really too much of a reason to make these

45
02:16.030 --> 02:16.720
different.

46
02:16.720 --> 02:20.200
So I'm just going to make them the same on both sides.

47
02:20.200 --> 02:22.600
We'll go ahead and exit out of configuration.

48
02:22.600 --> 02:26.600
And now we'll go do the same thing on Azure R1.

49
02:26.600 --> 02:30.320
So again, we go into configuration, create our key ring.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:26.600 --> 02:30.320
So again, we go into configuration, create our key ring.

50
02:30.320 --> 02:33.680
We can use the same name on both sides or it can be different.

51
02:33.680 --> 02:36.200
This is a locally significant name.

52
02:36.200 --> 02:38.240
We'll create our peer.

53
02:38.240 --> 02:40.600
We'll put in the IP address.

54
02:40.600 --> 02:44.640
Remember, this is the public address of your headquarters.

55
02:44.640 --> 02:48.120
We'll put in both of our keys and exit configuration.

56
02:49.120 --> 02:54.320
So in this video, our goal was simply to create our key ring for our Ike

57
02:54.320 --> 02:55.980
version 2 pre-shared

58
02:55.980 --> 02:57.280
keys.

59
02:57.280 --> 03:01.800
Keep in mind when you're configuring these for the peer address, you're going
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
02:57.280 --> 03:01.800
Keep in mind when you're configuring these for the peer address, you're going

60
03:01.800 --> 03:02.360
to use the

61
03:02.360 --> 03:08.060
outside or public address of the peer, particularly if it's in a net

62
03:08.060 --> 03:09.480
environment.

63
03:09.480 --> 03:13.780
So now that this is configured, our next step is going to be to configure the

64
03:13.780 --> 03:14.440
other three

65
03:14.440 --> 03:18.120
components that we need for Ike version 2.

66
03:18.120 --> 03:19.920
check that out in the next video.

67
03:19.920 --> 03:29.920
[BLANK_AUDIO]