WEBVTT

1
00:00.000 --> 00:07.300
So before we jump in with our actual deployment of the catalyst 8000 v into

2
00:07.300 --> 00:08.920
Google Cloud,

3
00:08.920 --> 00:13.440
let's spend just a minute here talking about some of the restrictions or cave

4
00:13.440 --> 00:14.520
ats limitations

5
00:14.520 --> 00:17.160
of doing that deployment.

6
00:17.160 --> 00:21.790
Now there are quite a few and keep in mind that like anything else limitations

7
00:21.790 --> 00:22.920
are of course

8
00:22.920 --> 00:28.520
time sensitive meaning that they could very well be fixed in the future.

9
00:28.520 --> 00:31.770
So what we're discussing right now or of course just limitations and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.520 --> 00:31.770
So what we're discussing right now or of course just limitations and

10
00:31.770 --> 00:32.840
restrictions at the

11
00:32.840 --> 00:34.800
time of this recording.

12
00:34.800 --> 00:39.210
So again, just keep in mind that maybe these things will be fixed in the future

13
00:39.210 --> 00:39.440
, but for

14
00:39.440 --> 00:45.800
now let's jump in and take a look at some of these restrictions.

15
00:45.800 --> 00:50.110
So let's begin by talking about licensing and the interesting thing is

16
00:50.110 --> 00:51.200
licensing is only

17
00:51.200 --> 00:58.610
available in one model currently on Google Cloud and that is the bring your own

18
00:58.610 --> 00:59.480
license

19
00:59.480 --> 01:01.840
or BYOL.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:59.480 --> 01:01.840
or BYOL.

20
01:01.840 --> 01:06.360
The pay as you go license is not currently available.

21
01:06.360 --> 01:09.200
Now again that could of course change in the future.

22
01:09.200 --> 01:12.780
I'm guessing that there's just some sort of billing arrangement that has to

23
01:12.780 --> 01:13.920
happen between

24
01:13.920 --> 01:16.080
Google and Cisco.

25
01:16.080 --> 01:20.680
But as of right now the only choice is the bring your own license.

26
01:20.680 --> 01:25.770
But then we have some actual restrictions as far as what we can do or not do

27
01:25.770 --> 01:26.720
while we're

28
01:26.720 --> 01:29.440
deploying the 8000 V.

29
01:29.440 --> 01:35.360
The first one is honestly a little bit questionable meaning I've had this be a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:29.440 --> 01:35.360
The first one is honestly a little bit questionable meaning I've had this be a

30
01:35.360 --> 01:36.440
problem and I've

31
01:36.440 --> 01:38.800
had it not be a problem.

32
01:38.800 --> 01:42.950
But there's a choice when you're doing the deployment to list the number of

33
01:42.950 --> 01:43.720
additional

34
01:43.720 --> 01:47.200
interfaces that you wish to deploy.

35
01:47.200 --> 01:50.970
Of course it's going to have one interface for short during deployment but you

36
01:50.970 --> 01:51.840
need to choose

37
01:51.840 --> 01:56.360
down at the bottom how many additional interfaces you wish to deploy.

38
01:56.360 --> 02:00.540
So of course if you wanted say for example two interfaces you're going to have
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:56.360 --> 02:00.540
So of course if you wanted say for example two interfaces you're going to have

39
02:00.540 --> 02:01.120
to choose

40
02:01.120 --> 02:03.760
one additional interface.

41
02:03.760 --> 02:09.480
Also you have to put each one of those interfaces into a separate VPC.

42
02:09.480 --> 02:13.230
Now we mentioned this of course when we were talking about our game plan and

43
02:13.230 --> 02:13.480
that's of

44
02:13.480 --> 02:19.790
course what we're going to do but you can put multiple nicks into two separate

45
02:19.790 --> 02:20.520
subnets

46
02:20.520 --> 02:23.060
in the same VPC.

47
02:23.060 --> 02:27.420
If you attempt to do that during the actual deployment you'll get an error from

48
02:27.420 --> 02:28.520
the deployment

49
02:28.520 --> 02:33.530
telling you that each nick must be in its own separate network and by that it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:28.520 --> 02:33.530
telling you that each nick must be in its own separate network and by that it

50
02:33.530 --> 02:35.960
means VPC.

51
02:35.960 --> 02:40.840
The other thing that's a little bit interesting is after you tell it what's the

52
02:40.840 --> 02:41.800
number of additional

53
02:41.800 --> 02:48.680
interfaces you wish to deploy you then have to remove any that you're not using

54
02:48.680 --> 02:49.120
from the

55
02:49.120 --> 02:50.640
deployment.

56
02:50.640 --> 02:54.050
And again this will make a little more sense as we're looking at it and going

57
02:54.050 --> 02:55.140
through it

58
02:55.140 --> 03:00.400
but it's going to default to adding seven additional interfaces.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:55.140 --> 03:00.400
but it's going to default to adding seven additional interfaces.

59
03:00.400 --> 03:05.910
And even if you set this to say one or maybe two it's still going to have seven

60
03:05.910 --> 03:06.800
interfaces

61
03:06.800 --> 03:08.120
down here.

62
03:08.120 --> 03:14.060
You are going to have to remove five of them so that what you're left with is

63
03:14.060 --> 03:14.620
just the

64
03:14.620 --> 03:19.280
two which is matching this number up here.

65
03:19.280 --> 03:24.370
So you have to ensure that the number of additional interfaces matches the

66
03:24.370 --> 03:25.440
number of actual

67
03:25.440 --> 03:29.380
nicks down at the very bottom of the deployment page.

68
03:29.380 --> 03:33.700
And if there's more which unless you're doing seven additional there will be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
03:29.380 --> 03:33.700
And if there's more which unless you're doing seven additional there will be

69
03:33.700 --> 03:34.400
you have to

70
03:34.400 --> 03:36.400
actually remove those.

71
03:36.400 --> 03:42.100
Now sort of a more interesting issue is that currently there is no way to

72
03:42.100 --> 03:43.320
assign an IP

73
03:43.320 --> 03:48.120
address to the interface during deployment.

74
03:48.120 --> 03:53.360
All you can do is choose a VPC and a subnet.

75
03:53.360 --> 03:57.930
There's no choice to either manually put in an IP address or to choose a

76
03:57.930 --> 03:59.800
reserved address.

77
03:59.800 --> 04:05.280
Google Cloud does have a place where you can go and you can reserve both
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
03:59.800 --> 04:05.280
Google Cloud does have a place where you can go and you can reserve both

78
04:05.280 --> 04:06.480
private and public

79
04:06.480 --> 04:07.960
addresses.

80
04:07.960 --> 04:12.440
And then when you go reconfigure a virtual machine you can assign one of those

81
04:12.440 --> 04:14.600
reserved addresses.

82
04:14.600 --> 04:18.720
Unfortunately there's no choice to do that during deployment.

83
04:18.720 --> 04:21.440
Again at least not currently.

84
04:21.440 --> 04:24.840
And if you try to change it after the fact.

85
04:24.840 --> 04:30.290
So if it's after deployment and you go in and you try to change the IP address
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:24.840 --> 04:30.290
So if it's after deployment and you go in and you try to change the IP address

86
04:30.290 --> 04:31.200
it'll actually

87
04:31.200 --> 04:33.200
let you go through and do it.

88
04:33.200 --> 04:38.220
But then you get an error telling you that changing that field is not supported

89
04:38.220 --> 04:38.280
.

90
04:38.280 --> 04:44.710
So at that point it will actually let you choose to either manually put one in

91
04:44.710 --> 04:45.440
or to choose

92
04:45.440 --> 04:48.280
a reserved address that you created.

93
04:48.280 --> 04:53.080
But once you've made that change and you hit save you get an error.

94
04:53.080 --> 04:57.490
And I will demonstrate these as we go through the deployment so you can see

95
04:57.490 --> 04:58.480
this yourself.

96
04:58.480 --> 05:02.680
Now sort of another interesting thing that we have to do here is we have to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
04:58.480 --> 05:02.680
Now sort of another interesting thing that we have to do here is we have to

97
05:02.680 --> 05:04.440
create our own

98
05:04.440 --> 05:06.200
SSH keys.

99
05:06.200 --> 05:09.680
So basically what we're going to do is we're going to be making a public

100
05:09.680 --> 05:10.680
private key pair on

101
05:10.680 --> 05:11.880
our Windows machine.

102
05:11.880 --> 05:16.800
And of course you could do this on Mac OS or on Linux as well.

103
05:16.800 --> 05:19.320
We're just going to happen to be doing it on Windows.

104
05:19.320 --> 05:23.170
But we're going to have to create our own keys and at bare minimum we're going

105
05:23.170 --> 05:24.200
to need one

106
05:24.200 --> 05:31.120
for the admin user which of course is the default user on the catalyst 8000 V.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
05:24.200 --> 05:31.120
for the admin user which of course is the default user on the catalyst 8000 V.

107
05:31.120 --> 05:34.000
So we're going to have to create that.

108
05:34.000 --> 05:37.560
And probably this one is sort of optional.

109
05:37.560 --> 05:41.800
But you'll probably want one for your Google account name as well.

110
05:41.800 --> 05:48.010
And the reason for that is this is the name that it's going to put on any Linux

111
05:48.010 --> 05:48.600
or Windows

112
05:48.600 --> 05:51.120
deployments and things like that.

113
05:51.120 --> 05:54.040
That's what it's going to use for the default account name.

114
05:54.040 --> 05:59.710
So for our Linux distributions we're going to want an SSH key pair to log into

115
05:59.710 --> 06:00.360
those as
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
05:59.710 --> 06:00.360
those as

116
06:00.360 --> 06:01.640
well.

117
06:01.640 --> 06:05.790
So these are some things that we want to keep in mind as we're going through

118
06:05.790 --> 06:06.240
and doing

119
06:06.240 --> 06:08.520
our deployment.

120
06:08.520 --> 06:13.970
So in this video we talked about some of the restrictions, limitations, caveats

121
06:13.970 --> 06:14.640
on deploying

122
06:14.640 --> 06:17.760
the 8000 V into Google Cloud.

123
06:17.760 --> 06:20.720
And again, some of these may get changed in the future.

124
06:20.720 --> 06:24.660
We don't know for sure of course, but just keep these things in mind at least

125
06:24.660 --> 06:25.200
at the time

126
06:25.200 --> 06:26.880
of this recording.

127
06:26.880 --> 06:29.280
These are all things we have to remember.

128
06:29.280 --> 06:34.910
So that said, let's jump in in the next video and get our environment ready for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
06:29.280 --> 06:34.910
So that said, let's jump in in the next video and get our environment ready for

129
06:34.910 --> 06:36.040
the 8000

130
06:36.040 --> 06:36.240
V.

131
06:36.240 --> 06:46.240
[BLANK_AUDIO]