WEBVTT

1
00:00.000 --> 00:08.740
So now that we have our catalyst 8000V configured and we verified that the

2
00:08.740 --> 00:11.000
catalyst itself can reach the internet,

3
00:11.000 --> 00:16.270
you may be wondering why do we have a separate video here on connectivity and

4
00:16.270 --> 00:18.000
is subnet 10 working?

5
00:18.000 --> 00:23.420
Well, we may find that we have a problem here with our internal networks being

6
00:23.420 --> 00:25.000
able to get out to the internet.

7
00:25.000 --> 00:28.000
Let's go ahead and take a look at what's going on.

8
00:29.000 --> 00:37.000
So as we saw in the previous video, we can ping 8.8.8.8 with no problem.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:29.000 --> 00:37.000
So as we saw in the previous video, we can ping 8.8.8.8 with no problem.

9
00:37.000 --> 00:42.340
However, if we were to source that from our gigabit to interface, what we see

10
00:42.340 --> 00:45.000
is that it actually doesn't work.

11
00:45.000 --> 00:52.750
As it's being sourced from the inside network, the 10.30.10.254, we can't reach

12
00:52.750 --> 00:54.000
the internet.

13
00:54.000 --> 00:59.300
The reason for this is actually quite simple. The Azure internet gateway is

14
00:59.300 --> 01:05.000
currently doing that to hide everything behind the public address of Azure R1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:59.300 --> 01:05.000
currently doing that to hide everything behind the public address of Azure R1.

15
01:05.000 --> 01:11.000
That is the address for its gigabit 1 interface that's assigned in Azure.

16
01:11.000 --> 01:15.520
Well, in order for this to work, we're going to have to have router 1, not

17
01:15.520 --> 01:21.000
everything from the inside interfaces going out to the internet,

18
01:21.000 --> 01:27.960
so that the Azure gateway sees everything as coming from the Azure R1 interface

19
01:27.960 --> 01:30.000
here on this router.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
01:30.000 --> 01:35.280
So this is a very simple process. All we have to do is configure net on all of

21
01:35.280 --> 01:39.000
the interfaces that are going to be inside.

22
01:39.000 --> 01:44.070
Now, if we were to do a show run for interface gigabit 1, notice that part of

23
01:44.070 --> 01:49.020
the baseline configuration that Cisco puts on here is to actually have gigabit

24
01:49.020 --> 01:50.000
1.

25
01:50.000 --> 01:55.260
Already configured as IP NAT outside, almost like they saw this was coming,

26
01:55.260 --> 01:56.000
right?

27
01:56.000 --> 02:01.260
So what we have to do is simply configure our NAT ACL, set gigabit 2 for our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:56.000 --> 02:01.260
So what we have to do is simply configure our NAT ACL, set gigabit 2 for our

28
02:01.260 --> 02:07.300
inside, and then set our IP NAT inside statement to do an overload on the gigab

29
02:07.300 --> 02:09.000
it 1 interface.

30
02:09.000 --> 02:12.000
So let's just go ahead and put this configuration in.

31
02:12.000 --> 02:17.530
So this will configure NAT for the overload if we exit out of here and we do

32
02:17.530 --> 02:19.000
our ping again.

33
02:19.000 --> 02:24.200
Now it's successful. And if we do a show IP NAT translation, we see here that

34
02:24.200 --> 02:31.840
it's translated its own inside local address, the 10.30.10.254 to the inside
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
02:24.200 --> 02:31.840
it's translated its own inside local address, the 10.30.10.254 to the inside

35
02:31.840 --> 02:36.000
global address, the 10.30.1.254.

36
02:36.000 --> 02:39.000
So it can go out to the internet.

37
02:39.000 --> 02:44.310
So one more thing we have to do to get our jump box and our SRV one workstation

38
02:44.310 --> 02:50.160
talking to each other, we're going to have to configure the routing in Azure to

39
02:50.160 --> 02:52.000
have subnet 10.

40
02:52.000 --> 02:59.000
Now point to Azure R1 here instead of pointing to the Microsoft Azure gateway,

41
02:59.000 --> 03:04.000
which since we set that as a private subnet, it wouldn't be anyway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
02:59.000 --> 03:04.000
which since we set that as a private subnet, it wouldn't be anyway.

42
03:04.000 --> 03:08.270
So let's go ahead and take a look what we have to do with the routing on the

43
03:08.270 --> 03:12.000
Azure side. So here in Azure, we want to go to route tables.

44
03:12.000 --> 03:16.510
And again, if you don't have a shortcut for this, just use the search bar up at

45
03:16.510 --> 03:17.000
the top.

46
03:17.000 --> 03:22.000
Notice we again have no route table here. So we're going to just create one.

47
03:22.000 --> 03:25.500
Like most things we have to select our resource group and then we'll give this

48
03:25.500 --> 03:31.000
a name. I'm just going to call it RT_subnet10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
03:25.500 --> 03:31.000
a name. I'm just going to call it RT_subnet10.

49
03:31.000 --> 03:35.780
This is going to be our route table for subnet 10. Do we want this to propagate

50
03:35.780 --> 03:40.150
a gateway route? No, we don't because we're going to be setting this up

51
03:40.150 --> 03:41.000
ourselves.

52
03:41.000 --> 03:45.140
So we're going to say no, we're going to say review and create everything here

53
03:45.140 --> 03:48.000
looks good. We'll hit create.

54
03:48.000 --> 03:52.480
So this is created, but what we have right now is an empty route table. So now

55
03:52.480 --> 03:55.000
we have to go to the resource.

56
03:55.000 --> 04:00.600
We see it's currently an empty routing table. So now we want to add a route for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
03:55.000 --> 04:00.600
We see it's currently an empty routing table. So now we want to add a route for

57
04:00.600 --> 04:04.000
the route name. We'll just make it default.

58
04:04.000 --> 04:08.640
That's what this is going to be as a default route. Destination type is going

59
04:08.640 --> 04:10.000
to be an IP address.

60
04:10.000 --> 04:15.030
The destination citer address is 0, 0, 0, 0 slash 0. That's the default. Of

61
04:15.030 --> 04:21.000
course, for the next hop type, we want to set this to be a virtual appliance.

62
04:21.000 --> 04:25.130
For the virtual appliance address, we want to put in the address of our

63
04:25.130 --> 04:33.000
catalyst 8,000 V. So this is 10.30.10.254. We'll go ahead and hit add.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
04:25.130 --> 04:33.000
catalyst 8,000 V. So this is 10.30.10.254. We'll go ahead and hit add.

64
04:33.000 --> 04:36.960
Notice by the way, we have a warning to ensure that we have IP forwarding

65
04:36.960 --> 04:41.000
enabled, which of course we do. So all of this should be fine.

66
04:41.000 --> 04:46.470
The next thing we have to do is apply this route table to our subnet. Now we

67
04:46.470 --> 04:52.280
can go back to the subnet to do it or we could just click right here on subnets

68
04:52.280 --> 04:54.000
and then click associate.

69
04:54.000 --> 04:57.000
Then over here on the right, we can click the subnet that we want to put it on.

70
04:57.000 --> 05:01.000
So we'll say subnet 10, of course, and we'll hit OK.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
04:57.000 --> 05:01.000
So we'll say subnet 10, of course, and we'll hit OK.

71
05:01.000 --> 05:07.050
Now that that's configured, that should configure SRV one to now send all of

72
05:07.050 --> 05:12.000
its traffic to the catalyst 8,000 V. So that's what we want.

73
05:12.000 --> 05:18.920
Now let's SSH into our jump box. So what we're going to need here on the jump

74
05:18.920 --> 05:23.080
box is to add a route that is going to route everything for the private

75
05:23.080 --> 05:29.000
networks, the 10.0.0.0.0 slash 8 through the gateway,

76
05:29.000 --> 05:35.960
which is in fact our Azure R1 or our catalyst 8,000 V. So let's go ahead and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
05:29.000 --> 05:35.960
which is in fact our Azure R1 or our catalyst 8,000 V. So let's go ahead and

77
05:35.960 --> 05:41.000
put this route in. We can verify this with the route minus end.

78
05:41.000 --> 05:48.840
And what we see here is we now have this route for 10.0.0.0 pointing to 10.30.1

79
05:48.840 --> 05:50.000
.254.

80
05:50.000 --> 05:54.740
However, everything else the rest of the internet basically is still going to

81
05:54.740 --> 06:00.970
10.30.1.1. Now of course, we don't normally want to have to put static routes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
05:54.740 --> 06:00.970
10.30.1.1. Now of course, we don't normally want to have to put static routes

82
06:00.970 --> 06:05.000
on workstations and such, but this being 4 out of band management.

83
06:05.000 --> 06:09.190
We do sort of need this jump box to do a little bit of unusual routing so that

84
06:09.190 --> 06:13.520
we can still get to it from the outside internet, but it can still go the

85
06:13.520 --> 06:16.000
proper direction to get to the inside.

86
06:16.000 --> 06:22.430
If all of this has worked correctly, we should now be able to ping SRV 1 at 10.

87
06:22.430 --> 06:25.000
30.10.100.

88
06:25.000 --> 06:33.030
As we see here, it worked. So now we have full reachability to subnet 10
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
06:25.000 --> 06:33.030
As we see here, it worked. So now we have full reachability to subnet 10

89
06:33.030 --> 06:35.000
through Azure R1.

90
06:35.000 --> 06:40.670
So in this video, we did a little bit of configuration to do netting for subnet

91
06:40.670 --> 06:46.000
10 so that it can go through the Microsoft Azure Internet gateway.

92
06:46.000 --> 06:51.120
And we set up a little bit of routing so that subnet 10 now goes through our

93
06:51.120 --> 06:58.250
catalyst 8,000 V and our jump box goes through the catalyst 8,000 V for private

94
06:58.250 --> 07:01.000
addresses starting with 10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
06:58.250 --> 07:01.000
addresses starting with 10.

95
07:01.000 --> 07:06.790
Now all we have to do is connect into SRV 1 itself and make sure everything's

96
07:06.790 --> 07:09.000
working from the server.