WEBVTT

1
00:00.000 --> 00:07.040
So next up, we want to spend just a few moments here to take a look at some of

2
00:07.040 --> 00:08.160
the guidelines

3
00:08.160 --> 00:13.240
when deploying the catalyst 8000V into Microsoft Azure.

4
00:13.240 --> 00:16.880
Now what we really want to focus on, there's two different deployment models

5
00:16.880 --> 00:17.480
that we can

6
00:17.480 --> 00:18.560
use.

7
00:18.560 --> 00:22.190
There's also two different licensing models which are available to either

8
00:22.190 --> 00:23.760
deployment model.

9
00:23.760 --> 00:26.280
And then there's also a couple little things that we just want to make sure we

10
00:26.280 --> 00:26.720
're clear

11
00:26.720 --> 00:30.120
on before we begin actually deploying the router.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:26.720 --> 00:30.120
on before we begin actually deploying the router.

12
00:30.120 --> 00:35.160
So let's jump in and take a look at that information.

13
00:35.160 --> 00:39.490
So the first thing we want to be aware of is there are in fact two different

14
00:39.490 --> 00:40.280
deployment

15
00:40.280 --> 00:45.480
models when we're deploying the 8000V into Azure.

16
00:45.480 --> 00:50.200
The first is to deploy it simply as a virtual machine.

17
00:50.200 --> 00:55.480
Now some of the attributes of using a virtual machine is it is going to be

18
00:55.480 --> 00:56.440
deployed with

19
00:56.440 --> 01:01.040
a single network interface card or a neck.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:56.440 --> 01:01.040
a single network interface card or a neck.

20
01:01.040 --> 01:05.600
Now generally speaking, we don't want to use a router with a single network

21
01:05.600 --> 01:06.080
card.

22
01:06.080 --> 01:10.480
There are some uses for that of course, but they're not incredibly common.

23
01:10.480 --> 01:15.360
But here's the thing, this is only during the deployment.

24
01:15.360 --> 01:20.850
We can certainly add more network cards based on our needs after the deployment

25
01:20.850 --> 01:21.160
.

26
01:21.160 --> 01:25.440
This is just when you're going through the actual deployment itself.

27
01:25.440 --> 01:30.690
And probably the most important thing about this virtual machine model is it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:25.440 --> 01:30.690
And probably the most important thing about this virtual machine model is it

28
01:30.690 --> 01:32.200
can be deployed

29
01:32.200 --> 01:39.640
into an existing resource group, more specifically, meaning a non empty

30
01:39.640 --> 01:41.640
resource group.

31
01:41.640 --> 01:46.000
So if you already have an existing deployment or maybe this is your second

32
01:46.000 --> 01:47.640
catalyst 8000V

33
01:47.640 --> 01:52.430
that you're deploying, the virtual machine model here would actually be your

34
01:52.430 --> 01:53.240
only choice

35
01:53.240 --> 01:57.200
if you want to put it in that same resource group.

36
01:57.200 --> 02:01.430
So this is going to be a fairly common deployment model based on whether you're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:57.200 --> 02:01.430
So this is going to be a fairly common deployment model based on whether you're

37
02:01.430 --> 02:02.360
trying to deploy

38
02:02.360 --> 02:05.640
this into an existing resource group.

39
02:05.640 --> 02:11.480
In the case of our demonstration here today in this skill, I in fact already

40
02:11.480 --> 02:12.800
have a resource

41
02:12.800 --> 02:17.060
group and I don't want to get rid of that resource group because I've already

42
02:17.060 --> 02:17.760
had certain

43
02:17.760 --> 02:22.640
quotas extended in that resource group by Microsoft.

44
02:22.640 --> 02:27.360
So if I were to delete my existing resource group, I would lose those quota

45
02:27.360 --> 02:28.360
extensions.

46
02:28.360 --> 02:32.160
So I am going to be using an existing resource group in my case.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:28.360 --> 02:32.160
So I am going to be using an existing resource group in my case.

47
02:32.160 --> 02:34.760
So we'll be using the virtual machine model.

48
02:34.760 --> 02:40.980
However, if this is your first deployment of the catalyst 8000V, there's also

49
02:40.980 --> 02:41.600
what's

50
02:41.600 --> 02:44.120
called a solution model.

51
02:44.120 --> 02:51.520
Now this one you can deploy with two, four or eight network cards.

52
02:51.520 --> 02:54.720
You'll make this choice as you go through the deployment.

53
02:54.720 --> 02:58.240
They'll simply be a drop down of how many network cards do you want.

54
02:58.240 --> 03:03.360
It'll default to two and you can of course choose if you want four or eight.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:58.240 --> 03:03.360
It'll default to two and you can of course choose if you want four or eight.

55
03:03.360 --> 03:06.200
But again, here's sort of a caveat with this one.

56
03:06.200 --> 03:13.910
It must be deployed into either a new or as I said before, empty resource group

57
03:13.910 --> 03:13.960
.

58
03:13.960 --> 03:17.770
So this is great for your first deployment, but it's not going to be so good

59
03:17.770 --> 03:18.320
for your

60
03:18.320 --> 03:20.120
second one.

61
03:20.120 --> 03:23.810
And something else to note here is as you go through this deployment model, it

62
03:23.810 --> 03:24.240
is going

63
03:24.240 --> 03:29.540
to deploy with a single vnet and it's going to use a separate subnet for every

64
03:29.540 --> 03:30.240
network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:29.540 --> 03:30.240
network

65
03:30.240 --> 03:31.440
card.

66
03:31.440 --> 03:34.920
So that's part of what makes this a solution.

67
03:34.920 --> 03:39.120
You're going to be creating all of these things at the same time.

68
03:39.120 --> 03:40.560
How many subnets?

69
03:40.560 --> 03:45.110
Well again, that's going to depend on how many network cards you chose up here

70
03:45.110 --> 03:45.360
during

71
03:45.360 --> 03:46.840
the deployment.

72
03:46.840 --> 03:49.680
This is all together on one deployment page.

73
03:49.680 --> 03:54.100
Now we will take a look at the solution as we go through, but as I mentioned,

74
03:54.100 --> 03:54.560
we will

75
03:54.560 --> 03:58.200
actually be deploying the virtual machine.

76
03:58.200 --> 04:03.880
The next thing to be aware of are the two different models for licensing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:58.200 --> 04:03.880
The next thing to be aware of are the two different models for licensing.

77
04:03.880 --> 04:07.320
And this is very similar in all of our cloud deployments.

78
04:07.320 --> 04:11.160
It really is more about licensing of the catalyst 8,000 v.

79
04:11.160 --> 04:14.200
The first is pay as you go.

80
04:14.200 --> 04:21.390
This simply means that you pay for your usage of the catalyst 8,000 v to

81
04:21.390 --> 04:22.800
Microsoft.

82
04:22.800 --> 04:25.320
Microsoft passes those payments on to Cisco.

83
04:25.320 --> 04:26.880
They have an agreement.

84
04:26.880 --> 04:32.080
So basically what it means is you are not paying a flat rate for the catalyst 8
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:26.880 --> 04:32.080
So basically what it means is you are not paying a flat rate for the catalyst 8

85
04:32.080 --> 04:33.960
,000 v.

86
04:33.960 --> 04:35.440
You're going to pay as you go.

87
04:35.440 --> 04:39.480
Therefore, you'll only pay for what you actually use.

88
04:39.480 --> 04:43.160
The other deployment model is to bring your own license.

89
04:43.160 --> 04:47.820
This is assuming that you've already bought your own license from a Cisco rese

90
04:47.820 --> 04:48.400
ller.

91
04:48.400 --> 04:52.960
In other words, you already own the catalyst 8,000 v.

92
04:52.960 --> 04:56.680
You're just going to be deploying it in Azure.

93
04:56.680 --> 05:02.200
That simply means that you will only be paying Microsoft for the use of the VM
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
04:56.680 --> 05:02.200
That simply means that you will only be paying Microsoft for the use of the VM

94
05:02.200 --> 05:02.920
that you're

95
05:02.920 --> 05:06.400
actually running the catalyst 8,000 v on.

96
05:06.400 --> 05:11.580
So you'll still pay your hardware fees, so to speak, but you won't be paying

97
05:11.580 --> 05:12.000
for the

98
05:12.000 --> 05:13.880
catalyst 8,000 v.

99
05:13.880 --> 05:18.090
So again, the pay as you go is sort of a bundle that includes the virtual

100
05:18.090 --> 05:19.560
machine and the licensing

101
05:19.560 --> 05:21.080
for the catalyst.

102
05:21.080 --> 05:24.190
And again, you can turn that on, turn that off whenever you want, and you only

103
05:24.190 --> 05:24.520
pay for

104
05:24.520 --> 05:25.600
usage.

105
05:25.600 --> 05:30.760
And then the bring your own license, you flat out own the catalyst 8,000 v.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
05:25.600 --> 05:30.760
And then the bring your own license, you flat out own the catalyst 8,000 v.

106
05:30.760 --> 05:34.080
Well, as much as you own anything else that you're licensing.

107
05:34.080 --> 05:38.840
But then you simply pay separately for the use of the VM itself.

108
05:38.840 --> 05:41.400
Now a few other things to be aware of here.

109
05:41.400 --> 05:46.530
The first is that all of our deployments, whichever model you choose, will use

110
05:46.530 --> 05:47.640
storage service

111
05:47.640 --> 05:49.920
encryption or SSE.

112
05:49.920 --> 05:54.160
So the contents of the storage will be encrypted.

113
05:54.160 --> 05:56.840
Let's talk about IP addresses for a minute.

114
05:56.840 --> 06:01.000
These can be either DHCP or static.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
05:56.840 --> 06:01.000
These can be either DHCP or static.

115
06:01.000 --> 06:06.470
So in other words, it can either pull its address from Azure as a DHCP client,

116
06:06.470 --> 06:07.000
or you can

117
06:07.000 --> 06:08.400
statically configure it.

118
06:08.400 --> 06:14.360
However, there is a caveat to the static configuration.

119
06:14.360 --> 06:22.030
Your static configuration is going to have to match whatever you tell Azure the

120
06:22.030 --> 06:22.520
address

121
06:22.520 --> 06:24.120
is going to be.

122
06:24.120 --> 06:26.690
And if you're not familiar with Azure, you'll see how this works as we go

123
06:26.690 --> 06:28.440
through this skill.

124
06:28.440 --> 06:32.780
But one of the things we have to do when we're configuring our router is tell
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
06:28.440 --> 06:32.780
But one of the things we have to do when we're configuring our router is tell

125
06:32.780 --> 06:33.480
it what its

126
06:33.480 --> 06:35.680
addresses are going to be.

127
06:35.680 --> 06:40.160
Now once again, they can either be dynamic or static on the Azure side as well.

128
06:40.160 --> 06:42.600
I'm talking about the router here.

129
06:42.600 --> 06:49.460
But regardless of how you set the address in Azure itself, that has to match on

130
06:49.460 --> 06:50.960
the router.

131
06:50.960 --> 06:55.240
In other words, you can't have Azure thinking that the address is one thing and

132
06:55.240 --> 06:55.680
the router

133
06:55.680 --> 06:58.760
be configured for something else.

134
06:58.760 --> 07:04.550
One final thing to be concerned with in regards to our networking is IP forward
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
06:58.760 --> 07:04.550
One final thing to be concerned with in regards to our networking is IP forward

135
07:04.550 --> 07:05.560
ing must

136
07:05.560 --> 07:09.000
be enabled on the interfaces.

137
07:09.000 --> 07:13.900
If you don't do this, it can't function as a router because well IP forwarding

138
07:13.900 --> 07:14.520
is sort of

139
07:14.520 --> 07:15.520
routing.

140
07:15.520 --> 07:18.040
So this feature must be enabled.

141
07:18.040 --> 07:23.520
It will not be by default with the VM or the virtual machine model.

142
07:23.520 --> 07:27.400
So as we go through, you'll see that we have to actually turn this on.

143
07:27.400 --> 07:29.240
So this is going to be very key.

144
07:29.240 --> 07:32.240
This is something we're not going to want to forget to do.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
07:29.240 --> 07:32.240
This is something we're not going to want to forget to do.

145
07:32.240 --> 07:35.910
Or you're going to spend a decent amount of time troubleshooting why your

146
07:35.910 --> 07:37.120
catalyst 8000

147
07:37.120 --> 07:42.240
V is not forwarding traffic as you expect it to.

148
07:42.240 --> 07:46.790
So in this video, we jumped in and we took a look at some of the configuration

149
07:46.790 --> 07:47.640
guidelines

150
07:47.640 --> 07:53.920
for the catalyst 8000 V being deployed into the Microsoft Azure environment.

151
07:53.920 --> 07:56.440
Keep in mind some of our major factors here.

152
07:56.440 --> 07:59.480
We have to decide which deployment model we want to use.

153
07:59.480 --> 08:03.080
Of course, which licensing model we wish to use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

153
07:59.480 --> 08:03.080
Of course, which licensing model we wish to use.

154
08:03.080 --> 08:07.360
And there's a few things here to remember as far as IP addressing goes.

155
08:07.360 --> 08:12.130
We'll of course be seeing all of these in more detail as we jump in in our next

156
08:12.130 --> 08:12.680
video

157
08:12.680 --> 08:17.830
and start preparing our Azure environment for the deployment of the catalyst 8

158
08:17.830 --> 08:18.760
000 V.

159
08:18.760 --> 08:28.760
[BLANK_AUDIO]