WEBVTT

1
00:00.000 --> 00:07.680
Now, before we just jump right in and begin our configuration, we do need to

2
00:07.680 --> 00:08.560
talk about

3
00:08.560 --> 00:13.950
some of the restrictions, limitations, and caveats of running the Cisco

4
00:13.950 --> 00:15.840
catalyst 8000V

5
00:15.840 --> 00:19.560
edge router inside of AWS.

6
00:19.560 --> 00:24.780
Now some of these are just things that Cisco does not fully support.

7
00:24.780 --> 00:29.110
It doesn't necessarily mean they won't function, and a lot of the things that

8
00:29.110 --> 00:29.960
commands are

9
00:29.960 --> 00:33.300
actually in the router, whether they function or not.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.960 --> 00:33.300
actually in the router, whether they function or not.

10
00:33.300 --> 00:38.700
Again, they're mostly things that either don't work or are not supported.

11
00:38.700 --> 00:45.150
Now that said, all of this sort of thing is very time sensitive, meaning these

12
00:45.150 --> 00:45.560
things

13
00:45.560 --> 00:49.380
are accurate as of the time of this recording.

14
00:49.380 --> 00:53.710
But of course, you always want to keep an eye on readmees and release notes for

15
00:53.710 --> 00:54.420
different

16
00:54.420 --> 00:58.790
releases of the software, because some of these restrictions and limitations

17
00:58.790 --> 00:59.080
may be

18
00:59.080 --> 01:00.560
lifted in the future.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:59.080 --> 01:00.560
lifted in the future.

19
01:00.560 --> 01:03.180
So always consult your documentation.

20
01:03.180 --> 01:07.380
But in the meantime, let's take a look at some of these restrictions as they

21
01:07.380 --> 01:07.980
stand right

22
01:07.980 --> 01:10.740
now.

23
01:10.740 --> 01:15.360
So our first topic here isn't exactly a restriction or caveat, but it does have

24
01:15.360 --> 01:17.420
to do with licensing.

25
01:17.420 --> 01:23.600
And when we deploy the C8000V, there are two different licensing models

26
01:23.600 --> 01:24.540
available that

27
01:24.540 --> 01:26.860
we just want to discuss real quickly.

28
01:26.860 --> 01:32.740
The first is the pay as you go or P-A-Y-G.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:26.860 --> 01:32.740
The first is the pay as you go or P-A-Y-G.

29
01:32.740 --> 01:39.220
This is simply a way to pay for the 8000V as you use it.

30
01:39.220 --> 01:44.020
So you get billed a certain amount per hour, and if at some point you stop

31
01:44.020 --> 01:45.460
using the router,

32
01:45.460 --> 01:47.420
then you stop paying for it.

33
01:47.420 --> 01:50.060
So this is sort of an on-demand payment.

34
01:50.060 --> 01:56.620
And then of course, the other choice is you can bring your own license or BYOL.

35
01:56.620 --> 01:59.580
And this one I think is fairly self-explanatory.

36
01:59.580 --> 02:04.960
You purchase your license from Cisco, and then you install your license onto
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:59.580 --> 02:04.960
You purchase your license from Cisco, and then you install your license onto

37
02:04.960 --> 02:06.420
the 8000V that

38
02:06.420 --> 02:09.380
you deploy into AWS.

39
02:09.380 --> 02:14.510
So you could of course choose whichever of these two payment models works for

40
02:14.510 --> 02:14.860
you as

41
02:14.860 --> 02:19.180
we go through our demonstration, we'll be doing the bring your own license

42
02:19.180 --> 02:20.220
because we're simply

43
02:20.220 --> 02:23.180
going to be using a demonstration license.

44
02:23.180 --> 02:27.620
So this is the one we're going to use, but of course you can do pay as you go

45
02:27.620 --> 02:28.300
if that works

46
02:28.300 --> 02:30.740
better for your environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:28.300 --> 02:30.740
better for your environment.

47
02:30.740 --> 02:36.260
Next, let's talk about a few of the restrictions that we have with the 8000V,

48
02:36.260 --> 02:37.420
specifically of

49
02:37.420 --> 02:40.820
course when we deploy it on AWS.

50
02:40.820 --> 02:47.180
First is that routing protocols are only supported over a tunnel.

51
02:47.180 --> 02:51.430
Now of course, we're going to be building a tunnel in our next skill, and we at

52
02:51.430 --> 02:51.780
that

53
02:51.780 --> 02:54.740
point will in fact use a routing protocol.

54
02:54.740 --> 02:59.380
However, technically it's only supported over the tunnel.

55
02:59.380 --> 03:07.060
Also the AMI, which is the Amazon image, does not support any remote management
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:59.380 --> 03:07.060
Also the AMI, which is the Amazon image, does not support any remote management

56
03:07.060 --> 03:08.740
, specifically

57
03:08.740 --> 03:13.860
using the Cisco Prime Network Services controller.

58
03:13.860 --> 03:18.620
So if that's something you use, you are not going to be able to use that with

59
03:18.620 --> 03:20.020
the 8000V.

60
03:20.020 --> 03:27.020
As we mentioned, there also are some technologies which again are not supported

61
03:27.020 --> 03:27.060
.

62
03:27.060 --> 03:32.240
Now again, these things may actually be present, so we may have the commands
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
03:27.060 --> 03:32.240
Now again, these things may actually be present, so we may have the commands

63
03:32.240 --> 03:33.900
for these available,

64
03:33.900 --> 03:39.110
but that doesn't mean that they're either fully functional or supported by

65
03:39.110 --> 03:39.420
Cisco.

66
03:39.420 --> 03:44.300
So we have a few different categories, the first of which is basic routing.

67
03:44.300 --> 03:47.100
We don't support OSPF.

68
03:47.100 --> 03:50.820
Now again, this is not running over a tunnel.

69
03:50.820 --> 03:53.540
Over the tunnel, we do.

70
03:53.540 --> 04:01.640
As far as the data center interconnect or the DCI, it doesn't support OTV or W
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:53.540 --> 04:01.640
As far as the data center interconnect or the DCI, it doesn't support OTV or W

71
04:01.640 --> 04:02.540
CCP version

72
04:02.540 --> 04:03.740
2.

73
04:03.740 --> 04:10.560
If you're not familiar with these, OTV is a layer 2 tunneling protocol and WCCP

74
04:10.560 --> 04:11.380
is for

75
04:11.380 --> 04:13.420
web caching.

76
04:13.420 --> 04:20.320
Under the category of MPLS, well, it doesn't support MPLS in general, and along

77
04:20.320 --> 04:21.460
with that,

78
04:21.460 --> 04:29.540
it doesn't support ethernet over MPLS, VRFs, or virtual private land service.

79
04:29.540 --> 04:34.580
Now again, what's supported and what can we use?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
04:29.540 --> 04:34.580
Now again, what's supported and what can we use?

80
04:34.580 --> 04:39.450
We're going to actually see that when we deploy the 8000V, it actually comes

81
04:39.450 --> 04:42.020
with a VRF already

82
04:42.020 --> 04:43.580
pre-configured.

83
04:43.580 --> 04:45.820
So again, do they work?

84
04:45.820 --> 04:48.300
Yes, are they fully supported?

85
04:48.300 --> 04:49.540
No.

86
04:49.540 --> 04:56.220
As far as redundancy, we don't support HSRP or hot standby routing protocol.

87
04:56.220 --> 05:06.420
And for WASS, we don't support the integrated AppNav, the XEWCCP version 2.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
04:56.220 --> 05:06.420
And for WASS, we don't support the integrated AppNav, the XEWCCP version 2.

88
05:06.420 --> 05:10.640
So again, if that's something you use, be aware that it's technically not

89
05:10.640 --> 05:11.580
supported.

90
05:11.580 --> 05:17.500
Now there are also a few caveats with deploying the 8000V.

91
05:17.500 --> 05:20.940
So again, there's just a few of them, not a whole lot.

92
05:20.940 --> 05:24.860
However, some of them may be important for you to understand.

93
05:24.860 --> 05:32.750
First, you cannot apply NAT or PAT on the same interface that you have
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
05:24.860 --> 05:32.750
First, you cannot apply NAT or PAT on the same interface that you have

94
05:32.750 --> 05:33.580
configured for

95
05:33.580 --> 05:35.580
a crypto map.

96
05:35.580 --> 05:38.820
Now there's two different workarounds for this.

97
05:38.820 --> 05:44.580
The first is you can of course use something other than a crypto map.

98
05:44.580 --> 05:48.300
You could use SVTI or DMVPN.

99
05:48.300 --> 05:52.740
There are other choices other than using a crypto map.

100
05:52.740 --> 05:57.380
Or if you really want to use a crypto map, the other choice is you can of

101
05:57.380 --> 05:58.660
course configure

102
05:58.660 --> 06:01.420
a two router solution.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:58.660 --> 06:01.420
a two router solution.

103
06:01.420 --> 06:06.470
Of course, AWS would like that method because then you're paying for two

104
06:06.470 --> 06:07.700
routers because

105
06:07.700 --> 06:13.140
regardless of your licensing, you're still paying the AWS instance fees.

106
06:13.140 --> 06:14.940
So don't forget that.

107
06:14.940 --> 06:19.050
But the idea here is you configure one of those routers for NAT and then the

108
06:19.050 --> 06:19.660
other one

109
06:19.660 --> 06:21.340
for the crypto map.

110
06:21.340 --> 06:26.140
So you simply separate the two functions on to two different routers.

111
06:26.140 --> 06:31.580
Now this one we did sort of already mentioned that you cannot configure HSRP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
06:26.140 --> 06:31.580
Now this one we did sort of already mentioned that you cannot configure HSRP.

112
06:31.580 --> 06:34.900
Here we're sort of just giving you more of the reason for it though.

113
06:34.900 --> 06:41.620
You can just sort of generically say that AWS does not allow running HSRP.

114
06:41.620 --> 06:47.680
But more specifically, we have the actual reason down below here that AWS

115
06:47.680 --> 06:49.380
blocks broadcasts

116
06:49.380 --> 06:58.420
and multicasts and HSRP uses multicast for its hellos to actually communicate.

117
06:58.420 --> 07:04.260
So this would apply to HSRP and VRRP in case that's something you use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
06:58.420 --> 07:04.260
So this would apply to HSRP and VRRP in case that's something you use.

118
07:04.260 --> 07:09.170
Neither one of these are going to work because they don't support unicast for

119
07:09.170 --> 07:10.740
their communication.

120
07:10.740 --> 07:13.380
So we can't do something like neighbor statements.

121
07:13.380 --> 07:16.420
Again, at least not right now.

122
07:16.420 --> 07:21.400
Another caveat here and we will be doing this because this is from their

123
07:21.400 --> 07:22.780
documentation where

124
07:22.780 --> 07:28.900
it says it is recommended that you disable the source and destination check on

125
07:28.900 --> 07:30.820
the 8000V
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
07:28.900 --> 07:30.820
the 8000V

126
07:30.820 --> 07:31.820
interfaces.

127
07:31.820 --> 07:36.300
Now this doesn't mean really on the 8000V.

128
07:36.300 --> 07:43.460
It means on the 8000V interfaces in AWS.

129
07:43.460 --> 07:46.340
And again, we'll look at how to do that.

130
07:46.340 --> 07:49.340
The reason I'm pointing out this is from the documentation.

131
07:49.340 --> 07:51.900
They say it's recommended.

132
07:51.900 --> 07:57.660
In my experience with this, it won't actually receive routed traffic because it

133
07:57.660 --> 07:59.060
's not for

134
07:59.060 --> 08:02.500
the direct source or destination.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
07:59.060 --> 08:02.500
the direct source or destination.

135
08:02.500 --> 08:04.300
So they say recommended.

136
08:04.300 --> 08:09.540
I'm saying from my experience, you pretty much need to do this.

137
08:09.540 --> 08:11.060
Also just some little things.

138
08:11.060 --> 08:14.340
Ether channel is not supported.

139
08:14.340 --> 08:17.020
We really shouldn't have a need to use it anyway.

140
08:17.020 --> 08:20.060
However, it is not supported.

141
08:20.060 --> 08:22.460
And we already mentioned they blog multicast.

142
08:22.460 --> 08:29.980
Well, multicast can work if you use the Amazon transit gateway solution.

143
08:29.980 --> 08:36.740
But for now, just be aware of these limitations, restrictions and caveats.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

143
08:29.980 --> 08:36.740
But for now, just be aware of these limitations, restrictions and caveats.

144
08:36.740 --> 08:41.330
So now that we have those limitations out of the way, let's go ahead and jump

145
08:41.330 --> 08:43.260
in to AWS

146
08:43.260 --> 08:47.000
begin to configure our environment to support the 8,000 V.