WEBVTT

1
00:00.000 --> 00:04.260
So what exactly is the data center?

2
00:04.260 --> 00:07.160
As far as us and the networking space are concerned,

3
00:07.160 --> 00:09.960
this is just another place in the network.

4
00:09.960 --> 00:12.400
And when we talked about this earlier on in the course,

5
00:12.400 --> 00:14.440
in regards to network architecture,

6
00:14.440 --> 00:16.440
we were called that this is a,

7
00:16.440 --> 00:19.440
first of all, very critical part of the network.

8
00:19.440 --> 00:21.160
But then the question is why?

9
00:21.160 --> 00:22.880
Why is it so critical?

10
00:22.880 --> 00:24.920
Well, it's because this is where we host

11
00:24.920 --> 00:27.440
our applications and our data.

12
00:27.440 --> 00:30.120
And if there's one thing from a technology perspective
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:27.440 --> 00:30.120
And if there's one thing from a technology perspective

13
00:30.120 --> 00:33.360
that would be considered the lifeblood of an organization,

14
00:33.360 --> 00:36.200
it's going to be our applications in our data.

15
00:36.200 --> 00:39.600
Most of our organizations, most of our companies today

16
00:39.600 --> 00:44.600
simply cannot exist, cannot operate without maybe one of these,

17
00:44.600 --> 00:47.840
if not both of them, are going to be very critical

18
00:47.840 --> 00:50.400
in being able to place orders

19
00:50.400 --> 00:53.280
and for employees to be productive.

20
00:53.280 --> 00:57.720
If we lose our access to our applications

21
00:57.720 --> 00:59.240
or we lose our data,

22
00:59.240 --> 01:03.680
this is going to be a loss of productivity at a minimum
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.240 --> 01:03.680
this is going to be a loss of productivity at a minimum

23
01:03.680 --> 01:07.580
and potentially a loss of revenue, a loss of profit.

24
01:07.580 --> 01:12.580
Some organizations have figured out exactly how many dollars

25
01:12.580 --> 01:14.480
from a US perspective,

26
01:14.480 --> 01:19.480
but how much is lost every single minute that we're down?

27
01:19.480 --> 01:22.400
Because again, loss of productivity is one thing,

28
01:22.400 --> 01:25.260
but we might actually lose out on sales opportunities

29
01:25.260 --> 01:27.400
or whatever the situation is,

30
01:27.400 --> 01:31.200
if we can't run our applications to process whatever it is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:27.400 --> 01:31.200
if we can't run our applications to process whatever it is

31
01:31.200 --> 01:32.700
that we need to process.

32
01:32.700 --> 01:36.120
Now, data centers exist in a lot of different forms.

33
01:36.120 --> 01:39.520
Certainly we might see that we use cloud resources,

34
01:39.520 --> 01:44.520
cloud applications, all kinds of cloud architectures

35
01:44.520 --> 01:48.960
that usually are going to rely on us accessing things

36
01:48.960 --> 01:50.240
through the internet.

37
01:50.240 --> 01:52.600
So our users might simply go out to the internet

38
01:52.600 --> 01:54.720
and access their applications.

39
01:54.720 --> 01:58.600
But even though the cloud has been a very prevalent part

40
01:58.600 --> 02:02.200
of our network build outs over the last, I would say decade
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:58.600 --> 02:02.200
of our network build outs over the last, I would say decade

41
02:02.200 --> 02:05.040
or maybe even longer than a decade at this point,

42
02:05.040 --> 02:07.120
even though cloud is very important,

43
02:07.120 --> 02:12.120
we do still have a lot of on-premise data centers.

44
02:12.120 --> 02:17.120
We usually will see that we have some kind of primary

45
02:17.120 --> 02:19.960
and secondary relationship with our data centers

46
02:19.960 --> 02:21.440
for the sake of having redundancy

47
02:21.440 --> 02:24.040
because uptime is so critical.

48
02:24.040 --> 02:26.920
And so within each one of these data centers,

49
02:26.920 --> 02:31.400
we're going to need some kind of network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:26.920 --> 02:31.400
we're going to need some kind of network.

50
02:31.400 --> 02:34.920
And this network is really what we're trying to drive at here.

51
02:34.920 --> 02:36.600
All of this is great,

52
02:36.600 --> 02:39.640
but within the context of this course in this exam,

53
02:39.640 --> 02:40.800
why do we care?

54
02:40.800 --> 02:44.880
We care because there is an associated network

55
02:44.880 --> 02:46.640
with data centers.

56
02:46.640 --> 02:49.160
So when we think about the data center network,

57
02:49.160 --> 02:51.480
Cisco is going to be really focused in

58
02:51.480 --> 02:53.880
on their Nexus line of switches.

59
02:53.880 --> 02:55.080
That's going to be very important.

60
02:55.080 --> 02:58.560
It's their go to switch for their data center architecture,

61
02:58.560 --> 03:00.600
but they also have a server product
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
02:58.560 --> 03:00.600
but they also have a server product

62
03:00.600 --> 03:03.840
known as the unified compute system, which is UCS.

63
03:03.840 --> 03:06.720
They have fiber channel switches, which are MDS.

64
03:06.720 --> 03:09.520
And for the most part,

65
03:09.520 --> 03:11.280
when we're talking about these technologies,

66
03:11.280 --> 03:13.760
this is focused on the data center

67
03:13.760 --> 03:17.360
and specifically their CCNP data center

68
03:17.360 --> 03:21.080
and even CCIE data center exams.

69
03:21.080 --> 03:24.880
And so when we're talking about learning this in more details,

70
03:24.880 --> 03:27.480
if, hey, you want to learn more about data center,

71
03:27.480 --> 03:31.560
check out the DC core course here on CBT Nuggets.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:27.480 --> 03:31.560
check out the DC core course here on CBT Nuggets.

72
03:31.560 --> 03:33.760
I absolutely love data center technology.

73
03:33.760 --> 03:36.560
This is one of the things I bring up every now and again,

74
03:36.560 --> 03:39.280
because it's very cool technology.

75
03:39.280 --> 03:41.280
And so if you want to learn more about it,

76
03:41.280 --> 03:43.840
we've got that contact here on CBT Nuggets.

77
03:43.840 --> 03:45.560
But again, we do still want to focus in

78
03:45.560 --> 03:48.240
on what exactly is Cisco asking us to study

79
03:48.240 --> 03:49.600
as part of the encore?

80
03:49.600 --> 03:51.400
Because we want to be bringing this up

81
03:51.400 --> 03:52.680
if it wasn't on the blueprint

82
03:52.680 --> 03:55.000
and we can look right at the blueprint and see,

83
03:55.000 --> 03:57.680
okay, Cisco wants us to know about the data center,

84
03:57.680 --> 04:01.120
about device virtualization and virtual switching.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:57.680 --> 04:01.120
about device virtualization and virtual switching.

85
04:01.120 --> 04:03.480
And so all of this is important,

86
04:03.480 --> 04:06.400
but we do need to drive it back to what exactly

87
04:06.400 --> 04:10.000
Cisco expects us to want to understand.

88
04:10.000 --> 04:13.280
Well, again, a lot of what we're driving at here

89
04:13.280 --> 04:14.560
is the networking.

90
04:14.560 --> 04:19.560
And part of this is going to be the virtual networking

91
04:19.560 --> 04:23.160
that exists inside of the data center

92
04:23.160 --> 04:25.600
on top of everything else we've talked about.

93
04:25.600 --> 04:27.040
So in order to understand this,

94
04:27.040 --> 04:29.960
let's talk about some of the basics of the data center.

95
04:29.960 --> 04:32.960
Again, we've got applications in data.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
04:29.960 --> 04:32.960
Again, we've got applications in data.

96
04:32.960 --> 04:35.880
These applications in data are being stored

97
04:35.880 --> 04:39.480
usually on a server.

98
04:39.480 --> 04:41.400
So what exactly is a server?

99
04:41.400 --> 04:46.400
Well, a server is going to serve up some kind of service.

100
04:46.400 --> 04:50.520
Kind of sounds a little redundant there.

101
04:50.520 --> 04:54.320
But functionally it's there to deliver our applications

102
04:54.320 --> 04:56.000
and our data in some format.

103
04:56.000 --> 04:59.320
Maybe we have a storage array that helps us to manage our data,

104
04:59.320 --> 05:04.120
but servers are how users are going to gain access
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
04:59.320 --> 05:04.120
but servers are how users are going to gain access

105
05:04.120 --> 05:06.800
to pretty much everything in the data center.

106
05:06.800 --> 05:10.440
They're going to send their network traffic to the server

107
05:10.440 --> 05:13.160
and the server will send them back

108
05:13.160 --> 05:14.800
whatever it is that we're looking for.

109
05:14.800 --> 05:16.320
Maybe we're trying to download files.

110
05:16.320 --> 05:20.040
Maybe we're trying to access a specific application.

111
05:20.040 --> 05:23.920
Maybe something that has to do with HR,

112
05:23.920 --> 05:27.320
managing payroll, it could be any of these types

113
05:27.320 --> 05:31.080
of applications that keep our organization running.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
05:27.320 --> 05:31.080
of applications that keep our organization running.

114
05:31.080 --> 05:33.440
And so what exactly is a server?

115
05:33.440 --> 05:38.440
It's essentially a super PC, a super powerful PC.

116
05:38.440 --> 05:39.880
However, we want to think about it.

117
05:39.880 --> 05:42.960
And it's going to have a lot of the same resources

118
05:42.960 --> 05:46.240
and hardware components that any PC has.

119
05:46.240 --> 05:50.320
So we think about CPU, we think about memory or RAM,

120
05:50.320 --> 05:55.320
we think about disks, potentially a graphical processing unit

121
05:55.320 --> 05:59.480
or a GPU, as well as network connectivity.

122
05:59.480 --> 06:03.080
All of these are what we put into a server,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
05:59.480 --> 06:03.080
All of these are what we put into a server,

123
06:03.080 --> 06:04.800
except usually in greater quantities.

124
06:04.800 --> 06:08.720
For example, we might have two or even four CPUs

125
06:08.720 --> 06:13.720
in a server and we might have maybe four to eight times

126
06:13.720 --> 06:18.920
the amount of RAM in a server that we do in a standard PC.

127
06:18.920 --> 06:21.360
Disks are interesting because a lot of servers run

128
06:21.360 --> 06:25.360
without disks using something like a storage array

129
06:25.360 --> 06:27.080
on the back end instead.

130
06:27.080 --> 06:30.400
But even GPUs can be useful in certain applications.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
06:27.080 --> 06:30.400
But even GPUs can be useful in certain applications.

131
06:30.400 --> 06:32.840
And then as far as ethernet connectivity

132
06:32.840 --> 06:34.440
is concerned, as you might imagine,

133
06:34.440 --> 06:38.440
we're probably talking about 10 to 25 gigabit per second

134
06:38.440 --> 06:40.560
and we're actually using that throughput,

135
06:40.560 --> 06:43.000
where a lot of PCs might have one or 10 gig

136
06:43.000 --> 06:46.320
and not even remotely touch that throughput

137
06:46.320 --> 06:47.720
and that capability.

138
06:47.720 --> 06:51.480
So we're talking about much, much more resources

139
06:51.480 --> 06:54.840
compared to a PC, but at the same time architecturally,

140
06:54.840 --> 06:59.840
it's still a PC and it's going to run an operating system.

141
06:59.840 --> 07:02.600
In the server world,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
06:59.840 --> 07:02.600
In the server world,

142
07:02.600 --> 07:07.680
we're going to usually see this as one of two options.

143
07:07.680 --> 07:11.600
It's either going to run a Windows server operating system.

144
07:11.600 --> 07:13.920
So this isn't our standard Windows 10,

145
07:13.920 --> 07:17.120
Windows 11 style of PCOS.

146
07:17.120 --> 07:21.040
Instead, we're talking about a Windows server edition

147
07:21.040 --> 07:24.960
or typically we also see a lot of Linux.

148
07:24.960 --> 07:27.800
And this might be Red Hat Enterprise Linux.

149
07:27.800 --> 07:31.040
It could be something that's a little bit more like Ubuntu
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

149
07:27.800 --> 07:31.040
It could be something that's a little bit more like Ubuntu

150
07:31.040 --> 07:32.360
or something along those lines,

151
07:32.360 --> 07:35.320
but either way, these are the operating systems

152
07:35.320 --> 07:37.120
we see in our data centers.

153
07:37.120 --> 07:39.040
We're not going to see any kind of Mac OS,

154
07:39.040 --> 07:40.840
at least at the time of this video,

155
07:40.840 --> 07:42.600
inside our data centers.

156
07:42.600 --> 07:44.640
Now, I don't know about you,

157
07:44.640 --> 07:46.920
but right now as I'm recording this,

158
07:46.920 --> 07:51.920
I deploy and run many applications per operating system.

159
07:51.920 --> 07:55.480
We'll say per PC at the same time.

160
07:55.480 --> 07:57.640
I'm running my recording software.

161
07:57.640 --> 08:00.080
I'm running my drawing software.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

161
07:57.640 --> 08:00.080
I'm running my drawing software.

162
08:00.080 --> 08:01.040
I'm looking around here.

163
08:01.040 --> 08:03.360
I've got my internet browser up.

164
08:03.360 --> 08:05.000
I've got my email application,

165
08:05.000 --> 08:07.200
slack, all kinds of things running.

166
08:07.200 --> 08:12.080
And so this is great for, again, the PC use,

167
08:12.080 --> 08:15.360
but we're not going to be able to do this with our servers.

168
08:15.360 --> 08:19.080
Instead, for servers, we're going to want to run

169
08:19.080 --> 08:23.960
a single application per operating system instance.

170
08:23.960 --> 08:25.800
Now, there's several reasons for this.

171
08:25.800 --> 08:29.160
The biggest one is resource contention.

172
08:29.160 --> 08:33.840
Every enterprise application is going to run,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

172
08:29.160 --> 08:33.840
Every enterprise application is going to run,

173
08:33.840 --> 08:36.880
want full access to all of the resources

174
08:36.880 --> 08:39.840
that are on that particular super PC,

175
08:39.840 --> 08:43.240
this server that we're sitting here talking about.

176
08:43.240 --> 08:46.360
So the resource contention becomes an issue

177
08:46.360 --> 08:49.200
if I deploy multiple applications.

178
08:49.200 --> 08:52.320
And this could be something like CPU and memory,

179
08:52.320 --> 08:57.080
and just saying, hey, this one application's running slow,

180
08:57.080 --> 08:59.160
but we're also running three other applications,

181
08:59.160 --> 09:00.720
and they're all just trying to gain access
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

181
08:59.160 --> 09:00.720
and they're all just trying to gain access

182
09:00.720 --> 09:02.720
to all of the CPU and memory.

183
09:02.720 --> 09:04.880
And that might be a concern.

184
09:04.880 --> 09:07.760
A bigger concern and more of a hard limit,

185
09:07.760 --> 09:09.320
if we want to call it that,

186
09:09.320 --> 09:13.520
is the concept of sharing network ports.

187
09:13.520 --> 09:16.680
So if, for example, I have three applications

188
09:16.680 --> 09:19.000
that are all accessed via the web browser,

189
09:19.000 --> 09:23.120
then we might see that TCP80 or 443,

190
09:23.120 --> 09:25.760
if we're talking secure, HTTP.

191
09:25.760 --> 09:28.960
Well, at that point, those ports are going to be consumed

192
09:28.960 --> 09:30.200
by one of the applications,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

192
09:28.960 --> 09:30.200
by one of the applications,

193
09:30.200 --> 09:32.480
and the other three are out of luck.

194
09:32.480 --> 09:34.800
And so this is where we are going to expect

195
09:34.800 --> 09:37.000
to see some major problems

196
09:37.000 --> 09:39.400
with deploying multiple applications

197
09:39.400 --> 09:42.160
to our server operating system.

198
09:42.160 --> 09:45.280
Even though we've got all kinds of hardware in here,

199
09:45.280 --> 09:47.280
that can help us to run.

200
09:47.280 --> 09:49.000
Maybe a lot of applications,

201
09:49.000 --> 09:54.040
we're still going to find that we run exactly one application

202
09:54.040 --> 09:56.840
on our operating system at a time.

203
09:56.840 --> 09:59.480
Kind of a major part of how we put together

204
09:59.480 --> 10:01.080
our server architectures.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

204
09:59.480 --> 10:01.080
our server architectures.

205
10:02.080 --> 10:06.080
So this leads us to the concept of the bare metal server.

206
10:06.080 --> 10:09.440
The bare metal server is going to be exactly

207
10:09.440 --> 10:10.880
what we've just described.

208
10:10.880 --> 10:13.080
We have a bunch of hardware,

209
10:13.080 --> 10:17.640
and then we're going to deploy an operating system

210
10:17.640 --> 10:18.680
on top of it.

211
10:18.680 --> 10:20.880
But from here, once again,

212
10:20.880 --> 10:23.880
we have this one-to-one relationship,

213
10:23.880 --> 10:28.080
one-to-one relationship with our applications.

214
10:28.080 --> 10:30.480
So I'm going to deploy a set of hardware
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

214
10:28.080 --> 10:30.480
So I'm going to deploy a set of hardware

215
10:30.480 --> 10:33.280
for this specific application

216
10:33.280 --> 10:35.280
is really what it comes down to.

217
10:35.280 --> 10:37.800
And this is going to be good

218
10:37.800 --> 10:39.880
from the perspective of resource contention.

219
10:39.880 --> 10:41.080
I mean, check.

220
10:41.080 --> 10:44.800
We don't have to worry about sharing this hardware

221
10:44.800 --> 10:47.120
with a bunch of other applications.

222
10:47.120 --> 10:50.760
The downside to this is now our efficiency

223
10:50.760 --> 10:52.840
is not going to be very good.

224
10:52.840 --> 10:56.400
Because chances are this application

225
10:56.400 --> 10:58.800
is not going to use all of the resources,

226
10:58.800 --> 11:00.360
at least all of the time.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

226
10:58.800 --> 11:00.360
at least all of the time.

227
11:00.360 --> 11:01.800
There might be some busy periods

228
11:01.800 --> 11:03.320
where it uses more of them,

229
11:03.320 --> 11:05.680
but it's pretty common in a bare metal environment

230
11:05.680 --> 11:08.320
to see that maybe we're consuming,

231
11:08.320 --> 11:13.320
let's just say 40% of the resources of the server.

232
11:13.320 --> 11:18.240
So maybe 40% of the CPU and memory.

233
11:18.240 --> 11:19.760
And this is just one bare metal server.

234
11:19.760 --> 11:21.480
I might have dozens, if not hundreds,

235
11:21.480 --> 11:23.440
of applications in my data center.

236
11:23.440 --> 11:26.480
And so I'm going to need one of these for every single one.

237
11:26.480 --> 11:29.840
So I might have three different bare metal servers

238
11:29.840 --> 11:32.080
while running a single application.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

238
11:29.840 --> 11:32.080
while running a single application.

239
11:32.080 --> 11:35.400
And so this one that we just said is running 40%.

240
11:35.400 --> 11:37.960
Maybe this one over here is running 15%.

241
11:37.960 --> 11:42.120
Meanwhile, this third server over here is running at 95%.

242
11:42.120 --> 11:45.320
So this is completely overloaded and overwhelmed.

243
11:45.320 --> 11:47.800
And hey, wouldn't it be lovely if I could borrow

244
11:47.800 --> 11:50.200
some of the CPU or memory from these other

245
11:50.200 --> 11:52.120
underutilized servers?

246
11:52.120 --> 11:55.440
But yeah, that would be pretty hard for me to share CPU

247
11:55.440 --> 11:57.720
from a completely different piece of hardware.

248
11:57.720 --> 12:00.400
It's really not technically possible.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

248
11:57.720 --> 12:00.400
It's really not technically possible.

249
12:00.400 --> 12:04.200
And so this is the challenge of a bare metal environment.

250
12:04.200 --> 12:09.200
And yet for a good amount of time inside of the data center

251
12:09.200 --> 12:14.360
space, we had no choice because of this requirement

252
12:14.360 --> 12:16.120
to keep a single application running

253
12:16.120 --> 12:18.560
on a single operating system

254
12:18.560 --> 12:21.200
and therefore on a single piece of hardware.

255
12:21.200 --> 12:24.160
So the solution to this is to start to virtualize

256
12:24.160 --> 12:26.040
and we're going to find out exactly how that solves

257
12:26.040 --> 12:29.560
problem in the next video.