WEBVTT

1
00:00.000 --> 00:00.500 align:middle line:84%


2
00:00.500 --> 00:03.300 align:middle line:90%
Cisco's DNA Center is a new
software-defined networking

3
00:03.300 --> 00:08.250 align:middle line:90%
solution that's primarily
targeted at large enterprises.

4
00:08.250 --> 00:11.520 align:middle line:90%
Think about college campuses
and things like that.

5
00:11.520 --> 00:13.920 align:middle line:90%
The goal, like most
software-defined networking

6
00:13.920 --> 00:18.180 align:middle line:90%
solutions, is to
simplify how we deploy,

7
00:18.180 --> 00:21.713 align:middle line:90%
operate, and optimize a
network infrastructure.

8
00:21.713 --> 00:23.130 align:middle line:90%
So in this particular
Nugget, what

9
00:23.130 --> 00:26.520 align:middle line:90%
we're going to talk about is
what does DNA Center really do?

10
00:26.520 --> 00:28.060 align:middle line:90%
What is the return
on investment?

11
00:28.060 --> 00:29.490 align:middle line:84%
What's the value that it brings?

12
00:29.490 --> 00:32.280 align:middle line:90%
And we're also going to
introduce the core concepts
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.490 --> 00:32.280 align:middle line:90%
And we're also going to
introduce the core concepts

13
00:32.280 --> 00:33.418 align:middle line:84%
of the SD-Access fabric.

14
00:33.418 --> 00:35.460 align:middle line:90%
In the next Nugget, we'll
dig a little bit deeper

15
00:35.460 --> 00:38.070 align:middle line:90%
into the SD-Access fabric
and talk about how it

16
00:38.070 --> 00:39.990 align:middle line:84%
applies to our security roles.

17
00:39.990 --> 00:40.960 align:middle line:84%
Let's get going.

18
00:40.960 --> 00:42.900 align:middle line:90%
So I know, this diagram
looks pretty familiar.

19
00:42.900 --> 00:44.070 align:middle line:90%
You're going, wait,
no, we're here

20
00:44.070 --> 00:45.630 align:middle line:90%
to talk about DNA
Center, not Firepower.

21
00:45.630 --> 00:46.547 align:middle line:84%
Just hang on, hang on.

22
00:46.547 --> 00:49.350 align:middle line:90%
This is the same diagram
from the previous skill

23
00:49.350 --> 00:52.500 align:middle line:90%
where we were talking about
APIs and software-defined

24
00:52.500 --> 00:53.080 align:middle line:84%
networking.

25
00:53.080 --> 00:53.580 align:middle line:84%
Guess what?

26
00:53.580 --> 00:56.550 align:middle line:90%
The principles of
software-defined networking,

27
00:56.550 --> 00:59.520 align:middle line:90%
they apply to DNA
Center just the way

28
00:59.520 --> 01:01.710 align:middle line:90%
they do with Firepower
Management Center.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
00:59.520 --> 01:01.710 align:middle line:90%
they do with Firepower
Management Center.

29
01:01.710 --> 01:04.170 align:middle line:90%
So before I bring up
the DNA Center diagram,

30
01:04.170 --> 01:07.260 align:middle line:90%
just recall for a second
what we're trying to do here.

31
01:07.260 --> 01:12.890 align:middle line:90%
We, the end user, are logging
into one single pane of glass

32
01:12.890 --> 01:15.270 align:middle line:90%
and deploying changes
to the network

33
01:15.270 --> 01:18.000 align:middle line:90%
from this little
management portal here.

34
01:18.000 --> 01:20.220 align:middle line:90%
And those changes
will get pushed down

35
01:20.220 --> 01:21.600 align:middle line:84%
to all the different devices.

36
01:21.600 --> 01:25.410 align:middle line:90%
And they communicate
programmatically using APIs.

37
01:25.410 --> 01:28.320 align:middle line:90%
But also recall that we
had directions for APIs.

38
01:28.320 --> 01:30.570 align:middle line:90%
There were east
and westbound APIs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:28.320 --> 01:30.570 align:middle line:90%
There were east
and westbound APIs.

39
01:30.570 --> 01:33.180 align:middle line:90%
There was the north
and southbound APIs.

40
01:33.180 --> 01:36.000 align:middle line:90%
And those things
really, really matter

41
01:36.000 --> 01:38.100 align:middle line:90%
when we're talking
about DNA Center

42
01:38.100 --> 01:43.200 align:middle line:90%
because DNA Center is a
total comprehensive solution

43
01:43.200 --> 01:45.030 align:middle line:84%
for large enterprises.

44
01:45.030 --> 01:46.800 align:middle line:90%
Now it's time to
change diagrams.

45
01:46.800 --> 01:49.230 align:middle line:90%
DNA Center approaches
the challenges

46
01:49.230 --> 01:52.140 align:middle line:90%
of the large enterprise with
a different or more creative

47
01:52.140 --> 01:53.760 align:middle line:84%
way of thinking things now.

48
01:53.760 --> 01:56.760 align:middle line:90%
What we're really talking about
when we talk about DNA Center

49
01:56.760 --> 01:59.940 align:middle line:84%
is intent-based networking.

50
01:59.940 --> 02:01.890 align:middle line:90%
And this is very
similar to the things
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
01:59.940 --> 02:01.890 align:middle line:90%
And this is very
similar to the things

51
02:01.890 --> 02:03.600 align:middle line:90%
that we've talked
about in the past.

52
02:03.600 --> 02:06.060 align:middle line:90%
What we're trying to
do here is we tell

53
02:06.060 --> 02:08.350 align:middle line:84%
DNA Center what is our intent.

54
02:08.350 --> 02:10.800 align:middle line:90%
What do we intend for
the network to do?

55
02:10.800 --> 02:12.660 align:middle line:84%
What is a basic behavior?

56
02:12.660 --> 02:14.950 align:middle line:84%
Like users in group A--

57
02:14.950 --> 02:16.680 align:middle line:90%
I'm just going to
put group A here--

58
02:16.680 --> 02:20.370 align:middle line:90%
should never be able to
talk to users in group B.

59
02:20.370 --> 02:24.118 align:middle line:90%
So this communication
is not allowable.

60
02:24.118 --> 02:26.160 align:middle line:90%
Just think about that
fundamentally for a second.

61
02:26.160 --> 02:28.740 align:middle line:90%
Someone in group A can
never talk to group

62
02:28.740 --> 02:32.880 align:middle line:90%
B. That's all we really have
to specify in DNA Center
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:28.740 --> 02:32.880 align:middle line:90%
B. That's all we really have
to specify in DNA Center

63
02:32.880 --> 02:36.780 align:middle line:90%
because when we express
our intent into DNA Center,

64
02:36.780 --> 02:41.370 align:middle line:90%
it handles pushing that
business intent down

65
02:41.370 --> 02:42.480 align:middle line:84%
to the individual devices.

66
02:42.480 --> 02:46.650 align:middle line:90%
It handles things like the ACLs
and the policies and the login

67
02:46.650 --> 02:47.610 align:middle line:84%
information.

68
02:47.610 --> 02:49.250 align:middle line:84%
That's the point of DNA Center.

69
02:49.250 --> 02:51.420 align:middle line:90%
And that's the point of
intent-based networking.

70
02:51.420 --> 02:53.328 align:middle line:90%
But it gets a lot more
complicated than that.

71
02:53.328 --> 02:54.870 align:middle line:90%
And that's what
we're going to set up

72
02:54.870 --> 02:56.970 align:middle line:90%
throughout the next
particular set of Nuggets.

73
02:56.970 --> 03:00.420 align:middle line:90%
The key things that you should
know right now about DNA Center
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
02:56.970 --> 03:00.420 align:middle line:90%
The key things that you should
know right now about DNA Center

74
03:00.420 --> 03:03.993 align:middle line:90%
is how it approaches handling
the enterprise network.

75
03:03.993 --> 03:05.410 align:middle line:90%
So what we're going
to do is we're

76
03:05.410 --> 03:06.930 align:middle line:90%
going to start with
this bottom tier

77
03:06.930 --> 03:09.600 align:middle line:90%
first, the intent-based
infrastructure.

78
03:09.600 --> 03:12.120 align:middle line:90%
We see we've got a little
picture of wireless access

79
03:12.120 --> 03:13.200 align:middle line:84%
point symbols.

80
03:13.200 --> 03:15.180 align:middle line:90%
We see we've got
some switch symbols.

81
03:15.180 --> 03:17.070 align:middle line:90%
We see we've got
some router symbols.

82
03:17.070 --> 03:19.230 align:middle line:90%
And then this is like a
generic anything else.

83
03:19.230 --> 03:21.330 align:middle line:84%
They call these extended nodes.

84
03:21.330 --> 03:25.170 align:middle line:90%
But these could be things,
like, firewalls or even servers.

85
03:25.170 --> 03:27.330 align:middle line:90%
What we're really talking
about with intent-based

86
03:27.330 --> 03:29.520 align:middle line:90%
infrastructure,
we're really saying

87
03:29.520 --> 03:34.020 align:middle line:90%
that these devices have
the capabilities to deploy
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:29.520 --> 03:34.020 align:middle line:90%
that these devices have
the capabilities to deploy

88
03:34.020 --> 03:35.520 align:middle line:84%
our business intent.

89
03:35.520 --> 03:39.900 align:middle line:90%
And these devices all run
usually some form of IOS XE.

90
03:39.900 --> 03:41.580 align:middle line:90%
At the time of this
recording, they

91
03:41.580 --> 03:46.770 align:middle line:90%
prefer you to be on something
like IOS XE 16.9 or 16.12.

92
03:46.770 --> 03:49.470 align:middle line:90%
Really, at the end of the day,
what we're talking about here

93
03:49.470 --> 03:53.160 align:middle line:90%
is the Catalyst 9K
series of devices.

94
03:53.160 --> 03:55.530 align:middle line:90%
The Catalyst 9K
series of devices

95
03:55.530 --> 03:58.080 align:middle line:90%
have hardware
components that help

96
03:58.080 --> 04:00.330 align:middle line:90%
us deploy this intent,
which is the ways
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
03:58.080 --> 04:00.330 align:middle line:90%
us deploy this intent,
which is the ways

97
04:00.330 --> 04:02.380 align:middle line:84%
that it can enforce this policy.

98
04:02.380 --> 04:04.920 align:middle line:90%
In fact, for many
Catalyst 9K devices,

99
04:04.920 --> 04:07.650 align:middle line:90%
when you purchase
Catalyst 9K devices,

100
04:07.650 --> 04:11.340 align:middle line:90%
it is required that you
purchase some form of DNA

101
04:11.340 --> 04:13.060 align:middle line:84%
Center licensing with it.

102
04:13.060 --> 04:15.570 align:middle line:90%
So it all begins with
the devices themselves.

103
04:15.570 --> 04:18.930 align:middle line:90%
They have to be able to
implement DNA Center's policies

104
04:18.930 --> 04:19.860 align:middle line:84%
and implementations.

105
04:19.860 --> 04:21.360 align:middle line:90%
And really what
we're saying is they

106
04:21.360 --> 04:23.940 align:middle line:90%
have to implement
our business intent.

107
04:23.940 --> 04:25.980 align:middle line:90%
Then we have the
systems themselves.

108
04:25.980 --> 04:29.340 align:middle line:90%
Well, this is, of course,
a DNA Center appliance.

109
04:29.340 --> 04:32.790 align:middle line:90%
The DNA Center appliance
is a standalone appliance.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
04:29.340 --> 04:32.790 align:middle line:90%
The DNA Center appliance
is a standalone appliance.

110
04:32.790 --> 04:36.630 align:middle line:90%
This is a server built
on Cisco UCS hardware.

111
04:36.630 --> 04:39.660 align:middle line:90%
And this is what we,
the end users, log into.

112
04:39.660 --> 04:42.120 align:middle line:90%
This is where, just like
Firepower Management Center,

113
04:42.120 --> 04:44.130 align:middle line:90%
where we interact
with the network.

114
04:44.130 --> 04:47.430 align:middle line:90%
We interact with it on the
Cisco DNA Center appliance.

115
04:47.430 --> 04:48.930 align:middle line:90%
Now, of course,
there is the ability

116
04:48.930 --> 04:50.610 align:middle line:90%
to make these
appliances redundant.

117
04:50.610 --> 04:53.820 align:middle line:90%
You do have to have a
minimum of three of them

118
04:53.820 --> 04:55.320 align:middle line:84%
in order to make them redundant.

119
04:55.320 --> 04:56.940 align:middle line:84%
You can't have two devices.

120
04:56.940 --> 05:00.070 align:middle line:90%
But the key here is that we,
the end user, the administrator,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
04:56.940 --> 05:00.070 align:middle line:90%
But the key here is that we,
the end user, the administrator,

121
05:00.070 --> 05:03.520 align:middle line:90%
the network architect, will log
into DNA Center from the DNA

122
05:03.520 --> 05:06.880 align:middle line:90%
Center appliance and tell it
what our business intent is.

123
05:06.880 --> 05:08.590 align:middle line:90%
We'll be able to
design our network.

124
05:08.590 --> 05:10.810 align:middle line:90%
We'll be able to monitor
our network, provision

125
05:10.810 --> 05:12.520 align:middle line:84%
and onboard new devices.

126
05:12.520 --> 05:15.550 align:middle line:90%
And all of that is done from
the DNA Center front end.

127
05:15.550 --> 05:19.630 align:middle line:90%
But notice here, this little
s is "systems," not "system."

128
05:19.630 --> 05:22.060 align:middle line:90%
We've only talked about
the DNA Center appliance.

129
05:22.060 --> 05:24.610 align:middle line:90%
And this is where we're
going to build into what

130
05:24.610 --> 05:25.960 align:middle line:84%
DNA Center really does.

131
05:25.960 --> 05:28.240 align:middle line:90%
The big surprise is
coming at the end.

132
05:28.240 --> 05:31.390 align:middle line:90%
Other systems that we will
rely on in order for DNA Center
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
05:28.240 --> 05:31.390 align:middle line:90%
Other systems that we will
rely on in order for DNA Center

133
05:31.390 --> 05:35.770 align:middle line:90%
to work is Cisco's Identity
Services Engine product,

134
05:35.770 --> 05:36.910 align:middle line:84%
or Cisco ISE.

135
05:36.910 --> 05:40.810 align:middle line:90%
Cisco ISE, in many ways,
is like Active Directory,

136
05:40.810 --> 05:44.440 align:middle line:90%
where it is a repository
of users and passwords

137
05:44.440 --> 05:46.870 align:middle line:84%
and permissions and privileges.

138
05:46.870 --> 05:48.520 align:middle line:90%
But beyond that,
it's also a place

139
05:48.520 --> 05:51.800 align:middle line:90%
where we can store network
device information.

140
05:51.800 --> 05:55.960 align:middle line:90%
So what DNA Center does is
it integrates very tightly

141
05:55.960 --> 05:57.160 align:middle line:84%
with Cisco ISE.

142
05:57.160 --> 05:59.260 align:middle line:90%
It really can't
operate without it.

143
05:59.260 --> 06:01.450 align:middle line:90%
And thanks to Cisco
ISE's capabilities,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

143
05:59.260 --> 06:01.450 align:middle line:90%
And thanks to Cisco
ISE's capabilities,

144
06:01.450 --> 06:03.850 align:middle line:90%
we now have a way to
keep track of what

145
06:03.850 --> 06:06.580 align:middle line:90%
nodes are in our
inventory and are

146
06:06.580 --> 06:08.680 align:middle line:84%
allowed to be in our network.

147
06:08.680 --> 06:10.150 align:middle line:90%
But beyond that,
we also have a way

148
06:10.150 --> 06:13.660 align:middle line:90%
of keeping track of what people
are accessing our network,

149
06:13.660 --> 06:15.950 align:middle line:84%
what groups do they belong to?

150
06:15.950 --> 06:18.500 align:middle line:90%
But more importantly, we
were talking about devices.

151
06:18.500 --> 06:20.440 align:middle line:90%
So we can now keep
track of which

152
06:20.440 --> 06:23.470 align:middle line:84%
devices are these users using?

153
06:23.470 --> 06:25.630 align:middle line:90%
Are they bringing
their own iPhone?

154
06:25.630 --> 06:27.760 align:middle line:90%
Are they sitting down
at a desktop computer?

155
06:27.760 --> 06:30.430 align:middle line:90%
When they plug into the network
and they type in their username
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
06:27.760 --> 06:30.430 align:middle line:90%
When they plug into the network
and they type in their username

156
06:30.430 --> 06:34.270 align:middle line:90%
and password, Cisco ISE can
capture this authentication

157
06:34.270 --> 06:36.550 align:middle line:90%
and associate them
with their devices.

158
06:36.550 --> 06:38.680 align:middle line:90%
Beyond that, it can
talk to DNA Center

159
06:38.680 --> 06:40.840 align:middle line:90%
and say, this user
just authenticated.

160
06:40.840 --> 06:43.450 align:middle line:90%
What business intent
would you like

161
06:43.450 --> 06:45.430 align:middle line:84%
for me to carry out with them?

162
06:45.430 --> 06:47.770 align:middle line:90%
What resources should
they be allowed

163
06:47.770 --> 06:49.640 align:middle line:84%
to access in the first place?

164
06:49.640 --> 06:52.720 align:middle line:90%
That's why DNA Center
talks so closely with ISE

165
06:52.720 --> 06:53.698 align:middle line:84%
and vice versa.

166
06:53.698 --> 06:55.240 align:middle line:90%
But taking it a step
further, there's

167
06:55.240 --> 06:57.250 align:middle line:90%
more systems that we
can integrate with,

168
06:57.250 --> 06:58.990 align:middle line:84%
like IPAM solutions.

169
06:58.990 --> 07:01.390 align:middle line:90%
This would be like
Infoblox or BlueCat.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

169
06:58.990 --> 07:01.390 align:middle line:90%
This would be like
Infoblox or BlueCat.

170
07:01.390 --> 07:03.670 align:middle line:90%
So with all of these new
network devices coming

171
07:03.670 --> 07:06.922 align:middle line:90%
into a large enterprise
and all of these users

172
07:06.922 --> 07:08.380 align:middle line:90%
that are now
accessing the network,

173
07:08.380 --> 07:10.540 align:middle line:90%
we need a way to
cleanly organize

174
07:10.540 --> 07:12.370 align:middle line:90%
which IP addresses
can be assigned

175
07:12.370 --> 07:14.620 align:middle line:90%
to which regions of
our environment, like,

176
07:14.620 --> 07:16.720 align:middle line:84%
sites or geographic locations.

177
07:16.720 --> 07:18.910 align:middle line:90%
Or what types of
devices should we

178
07:18.910 --> 07:20.920 align:middle line:84%
allocate for iPhones and iPads?

179
07:20.920 --> 07:23.320 align:middle line:90%
This is where the IPAM
solution comes in.

180
07:23.320 --> 07:26.120 align:middle line:90%
And DNA Center communicates
closely with that.

181
07:26.120 --> 07:29.020 align:middle line:90%
You can see now how the three
interact with each other.

182
07:29.020 --> 07:31.990 align:middle line:90%
A user may authenticate using
a certain type of device
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

182
07:29.020 --> 07:31.990 align:middle line:90%
A user may authenticate using
a certain type of device

183
07:31.990 --> 07:33.280 align:middle line:84%
or in a certain location.

184
07:33.280 --> 07:35.200 align:middle line:90%
DNA Center can
communicate to IPAM

185
07:35.200 --> 07:38.110 align:middle line:90%
about what kind of addressing
and services do they need.

186
07:38.110 --> 07:40.790 align:middle line:90%
And all of that information
is carried out that way.

187
07:40.790 --> 07:43.130 align:middle line:90%
But then on top of that
sits the platforms.

188
07:43.130 --> 07:45.940 align:middle line:90%
And this is where we're
really talking about APIs.

189
07:45.940 --> 07:47.980 align:middle line:90%
This is how DNA
Center communicates

190
07:47.980 --> 07:52.252 align:middle line:90%
to IPAM or ISE or, more
importantly, other devices

191
07:52.252 --> 07:53.710 align:middle line:90%
that we're trying
to interact with.

192
07:53.710 --> 07:55.780 align:middle line:90%
This could be things
like our own applications

193
07:55.780 --> 07:58.750 align:middle line:90%
that we're custom building
or other systems and services

194
07:58.750 --> 08:01.270 align:middle line:90%
that we need to interact
with, like, NetFlow or Syslog
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

194
07:58.750 --> 08:01.270 align:middle line:90%
that we need to interact
with, like, NetFlow or Syslog

195
08:01.270 --> 08:01.793 align:middle line:84%
Collector.

196
08:01.793 --> 08:04.210 align:middle line:90%
This is where we start talking
about the northbound versus

197
08:04.210 --> 08:07.270 align:middle line:90%
southbound versus eastbound
versus westbound API.

198
08:07.270 --> 08:10.670 align:middle line:90%
Now, the big thing that DNA
Center really, really brings

199
08:10.670 --> 08:12.670 align:middle line:90%
to the table, one of the
most incredible things,

200
08:12.670 --> 08:14.800 align:middle line:84%
is DNA Center Assurance.

201
08:14.800 --> 08:16.930 align:middle line:90%
Once you have your
entire network

202
08:16.930 --> 08:19.090 align:middle line:90%
stood up with your
business intent,

203
08:19.090 --> 08:20.800 align:middle line:90%
with all of your
policies and people

204
08:20.800 --> 08:23.230 align:middle line:90%
are now onboarded
into the network,

205
08:23.230 --> 08:26.320 align:middle line:90%
how do we keep track of
such a large enterprise?

206
08:26.320 --> 08:29.410 align:middle line:90%
Again, think about a large
college campus environment

207
08:29.410 --> 08:32.169 align:middle line:90%
where there's dozens
upon dozens of buildings
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

207
08:29.410 --> 08:32.169 align:middle line:90%
where there's dozens
upon dozens of buildings

208
08:32.169 --> 08:34.450 align:middle line:84%
and tens of thousands of users.

209
08:34.450 --> 08:36.668 align:middle line:90%
And each of them has
four or five devices

210
08:36.668 --> 08:37.460 align:middle line:84%
that they're using.

211
08:37.460 --> 08:40.150 align:middle line:90%
So there could be hundreds
of thousands of devices.

212
08:40.150 --> 08:42.610 align:middle line:90%
By the time we find out
that there's a problem,

213
08:42.610 --> 08:43.450 align:middle line:84%
it may be too late.

214
08:43.450 --> 08:44.920 align:middle line:84%
It may be days past.

215
08:44.920 --> 08:47.680 align:middle line:90%
DNA Center Assurance is one
of the most incredible things

216
08:47.680 --> 08:51.430 align:middle line:90%
about it because all of these
people, all of these devices,

217
08:51.430 --> 08:55.120 align:middle line:90%
all of these network nodes and
everything, they all stream

218
08:55.120 --> 08:57.160 align:middle line:84%
data back to DNA Center.

219
08:57.160 --> 08:59.930 align:middle line:90%
This is that telemetry that
we were talking about again.

220
08:59.930 --> 09:01.810 align:middle line:90%
They're constantly
sending data back
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

220
08:59.930 --> 09:01.810 align:middle line:90%
They're constantly
sending data back

221
09:01.810 --> 09:05.330 align:middle line:90%
to DNA Center, which is storing
it in a gigantic database.

222
09:05.330 --> 09:07.240 align:middle line:90%
But then it gets
crazier and cooler.

223
09:07.240 --> 09:10.480 align:middle line:90%
DNA Center learns
about your network.

224
09:10.480 --> 09:14.170 align:middle line:90%
It uses machine learning
and artificial intelligence

225
09:14.170 --> 09:17.260 align:middle line:90%
to determine what's
normal and what's expected

226
09:17.260 --> 09:18.610 align:middle line:84%
within your environment.

227
09:18.610 --> 09:22.150 align:middle line:90%
And it can detect when
anomalies or problems occur,

228
09:22.150 --> 09:26.290 align:middle line:90%
and proactively monitor and
troubleshoot and alert you

229
09:26.290 --> 09:27.710 align:middle line:84%
when these problems occur.

230
09:27.710 --> 09:30.280 align:middle line:90%
But beyond that, because
it's storing this data
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

230
09:27.710 --> 09:30.280 align:middle line:90%
But beyond that, because
it's storing this data

231
09:30.280 --> 09:34.210 align:middle line:90%
in a database, it can
keep a historical record

232
09:34.210 --> 09:36.110 align:middle line:84%
of your entire network.

233
09:36.110 --> 09:37.600 align:middle line:90%
So maybe you go
to bed one night.

234
09:37.600 --> 09:39.183 align:middle line:90%
And when you wake
up the next morning,

235
09:39.183 --> 09:42.350 align:middle line:90%
12 hours later, you find out
that a problem has occurred.

236
09:42.350 --> 09:45.940 align:middle line:90%
You can now look historically
at your assurance data

237
09:45.940 --> 09:48.850 align:middle line:90%
and figure out what
happened 12 hours ago.

238
09:48.850 --> 09:51.130 align:middle line:90%
And look, I appreciate a
good whiteboard as much

239
09:51.130 --> 09:51.920 align:middle line:84%
as the next guy.

240
09:51.920 --> 09:54.900 align:middle line:90%
But what we really should do is
we should actually take a look.

241
09:54.900 --> 09:57.220 align:middle line:90%
We should peek into
DNA Cente for a moment.

242
09:57.220 --> 09:59.910 align:middle line:90%
I actually happen to have
a DNA Center appliance

243
09:59.910 --> 10:02.100 align:middle line:84%
within my own little lab here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

243
09:59.910 --> 10:02.100 align:middle line:84%
within my own little lab here.

244
10:02.100 --> 10:04.620 align:middle line:90%
And I'm glad that we can
show it off now and actually

245
10:04.620 --> 10:07.290 align:middle line:90%
show you a little bit about
what DNA Center looks like

246
10:07.290 --> 10:08.550 align:middle line:84%
and how does it behave.

247
10:08.550 --> 10:12.090 align:middle line:90%
We actually have dedicated
training content to DNA Center.

248
10:12.090 --> 10:14.610 align:middle line:90%
It's called implementing
an SD-Access fabric

249
10:14.610 --> 10:15.650 align:middle line:84%
within DNA Center.

250
10:15.650 --> 10:17.762 align:middle line:90%
What does that SD-Access
fabric thing even mean?

251
10:17.762 --> 10:19.470 align:middle line:90%
That's what the next
Nugget is all about.

252
10:19.470 --> 10:22.012 align:middle line:90%
But let me clear the screen here
and bring up my web browser.

253
10:22.012 --> 10:23.160 align:middle line:84%
Look, this is DNA Center.

254
10:23.160 --> 10:24.420 align:middle line:84%
Let me get logged in.

255
10:24.420 --> 10:25.420 align:middle line:84%
And here we go.

256
10:25.420 --> 10:27.690 align:middle line:84%
Now I am online in DNA Center.

257
10:27.690 --> 10:30.390 align:middle line:90%
And quickly, I can see
my assurance snapshots.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

257
10:27.690 --> 10:30.390 align:middle line:90%
And quickly, I can see
my assurance snapshots.

258
10:30.390 --> 10:33.360 align:middle line:90%
We have all sorts of
issues that it's already

259
10:33.360 --> 10:35.010 align:middle line:84%
raising to me right now.

260
10:35.010 --> 10:38.310 align:middle line:90%
I have four P1 issues--
this is priority one--

261
10:38.310 --> 10:39.900 align:middle line:84%
and one P2 issue.

262
10:39.900 --> 10:43.110 align:middle line:90%
This was a way that I can log
in and immediately see what's

263
10:43.110 --> 10:44.770 align:middle line:84%
going on within my environment.

264
10:44.770 --> 10:47.040 align:middle line:90%
I also see that I have
several network devices that

265
10:47.040 --> 10:48.360 align:middle line:84%
are not in a very good state.

266
10:48.360 --> 10:52.210 align:middle line:90%
I have a 57% health score
on my network devices.

267
10:52.210 --> 10:54.750 align:middle line:90%
So by jumping over to the
Assurance section real quick,

268
10:54.750 --> 10:56.190 align:middle line:90%
this is where we
can start digging

269
10:56.190 --> 10:59.730 align:middle line:90%
in to what's really going on
within my entire SD-Access

270
10:59.730 --> 11:00.390 align:middle line:84%
fabric.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

270
10:59.730 --> 11:00.390 align:middle line:84%
fabric.

271
11:00.390 --> 11:02.160 align:middle line:90%
It looks like my
distribution layer

272
11:02.160 --> 11:03.960 align:middle line:90%
and some access switches
are showing down.

273
11:03.960 --> 11:05.820 align:middle line:90%
All of this is
stuff that now I'm

274
11:05.820 --> 11:08.940 align:middle line:90%
being alerted to that I can
start to begin to troubleshoot.

275
11:08.940 --> 11:11.130 align:middle line:90%
But like I said, we
can jump through time

276
11:11.130 --> 11:12.370 align:middle line:84%
and see what's going on here.

277
11:12.370 --> 11:14.870 align:middle line:90%
So I can look at things like
what happened in the last three

278
11:14.870 --> 11:17.460 align:middle line:90%
hours, what happened in the
last 24 hours, what's happened

279
11:17.460 --> 11:19.080 align:middle line:84%
in the last seven days.

280
11:19.080 --> 11:22.120 align:middle line:90%
And I can drill down
into all of these items.

281
11:22.120 --> 11:23.380 align:middle line:84%
But it doesn't stop there.

282
11:23.380 --> 11:25.690 align:middle line:90%
We also have things
like client health.

283
11:25.690 --> 11:29.760 align:middle line:90%
So when a user gets logged into
the network for the first time,

284
11:29.760 --> 11:33.420 align:middle line:90%
we can actually see what their
individual health status is.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

284
11:29.760 --> 11:33.420 align:middle line:90%
we can actually see what their
individual health status is.

285
11:33.420 --> 11:35.400 align:middle line:90%
By far, one of the
coolest things you can do

286
11:35.400 --> 11:37.620 align:middle line:90%
is if someone were to
call in to our help desk

287
11:37.620 --> 11:40.770 align:middle line:90%
and tell us, hey, so-and-so is
having problems in the network,

288
11:40.770 --> 11:42.840 align:middle line:90%
we can actually click on
the Search button here

289
11:42.840 --> 11:45.657 align:middle line:90%
and just search for their
name, like, Bob Smith.

290
11:45.657 --> 11:47.490 align:middle line:90%
And when their name
pops up, we can actually

291
11:47.490 --> 11:51.030 align:middle line:90%
click on their name and see what
their historical experience has

292
11:51.030 --> 11:53.160 align:middle line:90%
been for the last
seven days and which

293
11:53.160 --> 11:55.020 align:middle line:84%
devices are they working with.

294
11:55.020 --> 11:58.410 align:middle line:90%
You see, this is how it's all
integrating with IPAM and ISE.

295
11:58.410 --> 12:02.160 align:middle line:90%
Now we have a total snapshot
into our entire environment,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

295
11:58.410 --> 12:02.160 align:middle line:90%
Now we have a total snapshot
into our entire environment,

296
12:02.160 --> 12:05.700 align:middle line:90%
not just talking about
network devices anymore.

297
12:05.700 --> 12:08.280 align:middle line:90%
We're now able to look
into applications.

298
12:08.280 --> 12:11.860 align:middle line:90%
We're now able to look
into users' experiences.

299
12:11.860 --> 12:14.268 align:middle line:90%
This is a total
enterprise environment.

300
12:14.268 --> 12:15.810 align:middle line:90%
And again, think
about how this could

301
12:15.810 --> 12:19.140 align:middle line:90%
benefit the very large
enterprise, like, hospitals

302
12:19.140 --> 12:20.940 align:middle line:84%
or college campuses.

303
12:20.940 --> 12:22.950 align:middle line:90%
But it gets way
cooler than that when

304
12:22.950 --> 12:25.890 align:middle line:90%
we start talking about
how intent is deployed

305
12:25.890 --> 12:27.570 align:middle line:84%
with the SD-Access fabric.

306
12:27.570 --> 12:29.800 align:middle line:90%
And that's what the
next Nugget's all about.

307
12:29.800 --> 12:31.508 align:middle line:90%
In the meantime, this
has been setting up
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

307
12:29.800 --> 12:31.508 align:middle line:90%
In the meantime, this
has been setting up

308
12:31.508 --> 12:32.402 align:middle line:84%
what DNA Center does.

309
12:32.402 --> 12:34.110 align:middle line:90%
I hope this has been
informative for you.

310
12:34.110 --> 12:36.650 align:middle line:90%
And I'd like to thank
you for viewing.