WEBVTT

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


2
00:00.500 --> 00:03.265 align:middle line:90%
Now that we have a full picture
of what DNA Center does,

3
00:03.265 --> 00:04.890 align:middle line:90%
we've now seen some
of the capabilities

4
00:04.890 --> 00:07.350 align:middle line:90%
and talked about what the
SD-Access fabric does.

5
00:07.350 --> 00:10.560 align:middle line:90%
It's now time to talk about
how DNA Center does it.

6
00:10.560 --> 00:12.960 align:middle line:90%
We're going to talk about
the four workflows that

7
00:12.960 --> 00:16.200 align:middle line:90%
are basically how you go through
the process of deploying,

8
00:16.200 --> 00:19.260 align:middle line:90%
operating, and optimizing your
network within DNA Center.

9
00:19.260 --> 00:22.020 align:middle line:90%
This is going to give you
a lot of context as to what

10
00:22.020 --> 00:23.760 align:middle line:90%
someone who works
with DNA Center

11
00:23.760 --> 00:25.238 align:middle line:90%
is really going to
be working with.

12
00:25.238 --> 00:27.030 align:middle line:90%
So we'll actually see
it from the front end

13
00:27.030 --> 00:29.183 align:middle line:90%
as we explore the four
workflows of DNA Center.

14
00:29.183 --> 00:30.600 align:middle line:90%
And then in the
next Nugget, we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:29.183 --> 00:30.600 align:middle line:90%
And then in the
next Nugget, we're

15
00:30.600 --> 00:33.510 align:middle line:90%
going to wrap up with a secret
fifth workflow, the platform.

16
00:33.510 --> 00:34.450 align:middle line:84%
Let's get going.

17
00:34.450 --> 00:37.920 align:middle line:90%
So how does DNA Center
do what DNA Center does?

18
00:37.920 --> 00:41.970 align:middle line:90%
You see, even though this
greatly simplifies how we work

19
00:41.970 --> 00:45.420 align:middle line:90%
with our network-- it greatly
simplifies the complexity

20
00:45.420 --> 00:48.060 align:middle line:90%
of a large enterprise network
with hundreds or thousands

21
00:48.060 --> 00:49.080 align:middle line:84%
of devices--

22
00:49.080 --> 00:50.255 align:middle line:84%
it's still complicated.

23
00:50.255 --> 00:54.030 align:middle line:90%
It's still got a lot of work
to deploy an SD-Access fabric

24
00:54.030 --> 00:55.770 align:middle line:90%
and get all this
monitoring done.

25
00:55.770 --> 00:59.850 align:middle line:90%
But luckily for us, DNA
Center has built-in automation

26
00:59.850 --> 01:01.330 align:middle line:84%
all over the place.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:59.850 --> 01:01.330 align:middle line:84%
all over the place.

27
01:01.330 --> 01:05.220 align:middle line:90%
So as long as you follow
their four workflows,

28
01:05.220 --> 01:08.460 align:middle line:90%
it should be able to reach
out to all of these devices,

29
01:08.460 --> 01:09.900 align:middle line:90%
get them brought
into the network

30
01:09.900 --> 01:13.050 align:middle line:90%
and provisioned with the
correct configurations upfront.

31
01:13.050 --> 01:15.180 align:middle line:90%
The cooler thing about
it is because of all

32
01:15.180 --> 01:17.940 align:middle line:90%
of these workflows and
this automation capability,

33
01:17.940 --> 01:21.930 align:middle line:90%
we can actually take system
defaulted devices, completely

34
01:21.930 --> 01:24.060 align:middle line:90%
fresh out of the
box, still prompting,

35
01:24.060 --> 01:27.120 align:middle line:90%
would you like to configure
this network device, yes or no?

36
01:27.120 --> 01:29.880 align:middle line:90%
You leave it in that system
defaulted configuration

37
01:29.880 --> 01:33.360 align:middle line:90%
and DNA Center can still
reach out to those devices
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:29.880 --> 01:33.360 align:middle line:90%
and DNA Center can still
reach out to those devices

38
01:33.360 --> 01:37.410 align:middle line:90%
and bring them into the network
using plug and play technology.

39
01:37.410 --> 01:40.950 align:middle line:90%
Again, it circles back
to the four workflows

40
01:40.950 --> 01:42.570 align:middle line:84%
to make these things happen.

41
01:42.570 --> 01:44.580 align:middle line:90%
So let's talk about
what these workflows do.

42
01:44.580 --> 01:46.800 align:middle line:84%
The first workflow is design.

43
01:46.800 --> 01:49.597 align:middle line:90%
And this is where you start
thinking about how are we

44
01:49.597 --> 01:51.930 align:middle line:90%
actually going to design the
connectivity of our network

45
01:51.930 --> 01:52.680 align:middle line:84%
devices to each other?

46
01:52.680 --> 01:54.480 align:middle line:90%
And that's not exactly
what design does.

47
01:54.480 --> 01:58.290 align:middle line:90%
Design is actually the
actual layout of your campus.

48
01:58.290 --> 02:00.210 align:middle line:84%
We're talking geography here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
01:58.290 --> 02:00.210 align:middle line:84%
We're talking geography here.

49
02:00.210 --> 02:04.140 align:middle line:90%
For instance, in my New York
site, what IP address block

50
02:04.140 --> 02:05.970 align:middle line:90%
are we going to
allocate to New York?

51
02:05.970 --> 02:07.790 align:middle line:90%
Where will it find
its DHCP server?

52
02:07.790 --> 02:09.960 align:middle line:90%
Where will it find
its DNS server?

53
02:09.960 --> 02:15.180 align:middle line:90%
And what image, what iOS version
should devices in New York

54
02:15.180 --> 02:16.960 align:middle line:90%
even be using in
the first place?

55
02:16.960 --> 02:19.150 align:middle line:90%
These are all things
that we set up in design.

56
02:19.150 --> 02:21.540 align:middle line:90%
Then the next
workflow is policy.

57
02:21.540 --> 02:22.560 align:middle line:84%
You've seen policy.

58
02:22.560 --> 02:24.750 align:middle line:90%
This is where we define
our business intent

59
02:24.750 --> 02:29.640 align:middle line:90%
with virtual networks or ACLs,
like, our scalable group ACLs.

60
02:29.640 --> 02:31.920 align:middle line:90%
Then we have the
provision workflow.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:29.640 --> 02:31.920 align:middle line:90%
Then we have the
provision workflow.

61
02:31.920 --> 02:34.300 align:middle line:90%
And this is where the
rubber meets the road.

62
02:34.300 --> 02:37.710 align:middle line:90%
This is where we actually
perform LAN automation.

63
02:37.710 --> 02:40.710 align:middle line:90%
This is where we bring new
devices into the network

64
02:40.710 --> 02:43.980 align:middle line:84%
and deploy our fabric overlay.

65
02:43.980 --> 02:46.680 align:middle line:90%
This is the SD-Access
fabric that implements

66
02:46.680 --> 02:48.960 align:middle line:84%
the LISP and VXLAN overlays.

67
02:48.960 --> 02:51.810 align:middle line:90%
Beyond that, this is a very
big talking point, especially

68
02:51.810 --> 02:53.100 align:middle line:84%
for the security track.

69
02:53.100 --> 02:55.440 align:middle line:90%
During the provisioning
workflow, especially when

70
02:55.440 --> 02:57.630 align:middle line:90%
we're deploying
the fabric overlay,

71
02:57.630 --> 02:59.970 align:middle line:90%
our devices will be
provisioned to use something

72
02:59.970 --> 03:02.190 align:middle line:84%
called Cisco TrustSec.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
02:59.970 --> 03:02.190 align:middle line:84%
called Cisco TrustSec.

73
03:02.190 --> 03:05.280 align:middle line:90%
This is how our devices
can implement our policies.

74
03:05.280 --> 03:07.200 align:middle line:90%
This is how our
devices can learn

75
03:07.200 --> 03:10.590 align:middle line:90%
about what groups users
are allowed to be a part of

76
03:10.590 --> 03:12.390 align:middle line:90%
and what they're allowed
to communicate to.

77
03:12.390 --> 03:14.760 align:middle line:90%
This is how it knows what
virtual network they should

78
03:14.760 --> 03:17.340 align:middle line:90%
belong to and which
groups within it

79
03:17.340 --> 03:18.810 align:middle line:90%
they are allowed
to communicate to.

80
03:18.810 --> 03:21.240 align:middle line:90%
Our macro and micro
segmentation policies

81
03:21.240 --> 03:23.100 align:middle line:84%
come down to Cisco TrustSec.

82
03:23.100 --> 03:25.610 align:middle line:90%
And our devices, when
deploying the fabric overlay,

83
03:25.610 --> 03:28.920 align:middle line:90%
will learn that they should
communicate to Cisco ISE

84
03:28.920 --> 03:31.530 align:middle line:90%
in order to implement
Cisco TrustSec.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:28.920 --> 03:31.530 align:middle line:90%
in order to implement
Cisco TrustSec.

85
03:31.530 --> 03:34.330 align:middle line:90%
And the last workflow is
the assurance workflow,

86
03:34.330 --> 03:37.665 align:middle line:90%
which we've also seen, which is
how we can operate and optimize

87
03:37.665 --> 03:39.540 align:middle line:90%
our network by monitoring
and troubleshooting

88
03:39.540 --> 03:40.938 align:middle line:84%
any events that go on.

89
03:40.938 --> 03:42.480 align:middle line:90%
So with that all
said, let's actually

90
03:42.480 --> 03:45.430 align:middle line:90%
jump into the front end and take
a look at these four workflows.

91
03:45.430 --> 03:46.920 align:middle line:90%
Let's start off
from the home page

92
03:46.920 --> 03:49.410 align:middle line:90%
here and jump into
the design workflow.

93
03:49.410 --> 03:51.750 align:middle line:90%
You can see here, we've
got our global hierarchy.

94
03:51.750 --> 03:53.880 align:middle line:90%
This is where we're talking
about those geographies

95
03:53.880 --> 03:54.660 align:middle line:84%
yet again.

96
03:54.660 --> 03:55.740 align:middle line:84%
Now, I'm in Louisiana.

97
03:55.740 --> 03:57.330 align:middle line:90%
And I've deployed a
little fabric here

98
03:57.330 --> 03:59.100 align:middle line:84%
within the Louisiana fabric.

99
03:59.100 --> 04:01.310 align:middle line:90%
So you can see I can
expand these down.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
03:59.100 --> 04:01.310 align:middle line:90%
So you can see I can
expand these down.

100
04:01.310 --> 04:04.740 align:middle line:90%
And my fabric is designed such
that there's a Louisiana tier.

101
04:04.740 --> 04:06.640 align:middle line:90%
Then within that,
we've got our cities.

102
04:06.640 --> 04:08.730 align:middle line:90%
And then within that,
we've got some buildings

103
04:08.730 --> 04:10.810 align:middle line:90%
and the actual
floors themselves.

104
04:10.810 --> 04:12.720 align:middle line:90%
So our first step in
the design workflow

105
04:12.720 --> 04:16.047 align:middle line:90%
is just to set up what is
the hierarchy of our topology

106
04:16.047 --> 04:16.839 align:middle line:84%
in the first place?

107
04:16.839 --> 04:17.709 align:middle line:84%
What are our buildings?

108
04:17.709 --> 04:18.667 align:middle line:84%
What are our locations?

109
04:18.667 --> 04:19.740 align:middle line:84%
What are their addresses?

110
04:19.740 --> 04:23.550 align:middle line:90%
Once you've defined the site
hierarchy within DNA Center,

111
04:23.550 --> 04:26.130 align:middle line:90%
you can then start assigning
the actual network settings

112
04:26.130 --> 04:27.100 align:middle line:84%
to each of these.

113
04:27.100 --> 04:29.550 align:middle line:90%
So my New Orleans site
can find it's ISE server

114
04:29.550 --> 04:30.840 align:middle line:84%
at these IP addresses.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
04:29.550 --> 04:30.840 align:middle line:84%
at these IP addresses.

115
04:30.840 --> 04:33.660 align:middle line:90%
It can see things, like, where
the DHCP server and the DNS

116
04:33.660 --> 04:34.350 align:middle line:84%
servers are.

117
04:34.350 --> 04:38.860 align:middle line:90%
And what should it be using for
a syslog or SNMP server, NTP

118
04:38.860 --> 04:39.780 align:middle line:84%
services?

119
04:39.780 --> 04:41.050 align:middle line:84%
You get the idea.

120
04:41.050 --> 04:43.650 align:middle line:90%
You can even set the time zone
that these locations should

121
04:43.650 --> 04:44.910 align:middle line:84%
be specified in.

122
04:44.910 --> 04:47.850 align:middle line:90%
We can specify what
credentials should be assigned

123
04:47.850 --> 04:49.690 align:middle line:84%
to each of our network devices.

124
04:49.690 --> 04:52.560 align:middle line:90%
How can DNA Center access
these network devices?

125
04:52.560 --> 04:54.990 align:middle line:90%
And how can we access
these network devices?

126
04:54.990 --> 04:56.310 align:middle line:84%
We set this up right here.

127
04:56.310 --> 04:58.380 align:middle line:90%
We specify a
username and password

128
04:58.380 --> 05:02.810 align:middle line:90%
that can be used for SSH, or
SNMP, HTTP, and even NetConf.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
04:58.380 --> 05:02.810 align:middle line:90%
that can be used for SSH, or
SNMP, HTTP, and even NetConf.

129
05:02.810 --> 05:05.750 align:middle line:90%
Beyond that, we specify,
we allocate IP addresses

130
05:05.750 --> 05:08.540 align:middle line:90%
that should be used for
each of our virtual networks

131
05:08.540 --> 05:10.310 align:middle line:84%
within each of our sites.

132
05:10.310 --> 05:13.430 align:middle line:90%
We make all these reservations
now in the design workflow,

133
05:13.430 --> 05:16.580 align:middle line:90%
even though we don't associate
them to the final deployment

134
05:16.580 --> 05:18.210 align:middle line:84%
until the provision workflow.

135
05:18.210 --> 05:20.110 align:middle line:90%
So this sets up the
design workflow,

136
05:20.110 --> 05:23.240 align:middle line:90%
where we're just laying
out how our topology should

137
05:23.240 --> 05:24.740 align:middle line:84%
look in the first place.

138
05:24.740 --> 05:26.600 align:middle line:90%
The policy workflows,
we've already seen,

139
05:26.600 --> 05:30.200 align:middle line:90%
is where we can define our micro
and macro segmentation policy.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

139
05:26.600 --> 05:30.200 align:middle line:90%
is where we can define our micro
and macro segmentation policy.

140
05:30.200 --> 05:32.420 align:middle line:90%
With the macro
segmentation policy,

141
05:32.420 --> 05:35.510 align:middle line:90%
we define the virtual networks
and which users should be

142
05:35.510 --> 05:37.160 align:middle line:84%
within which virtual network.

143
05:37.160 --> 05:39.200 align:middle line:90%
With a micro
segmentation policy,

144
05:39.200 --> 05:41.810 align:middle line:90%
we say within that
virtual network,

145
05:41.810 --> 05:44.390 align:middle line:90%
what groups are allowed to
communicate to each other?

146
05:44.390 --> 05:46.400 align:middle line:90%
But it's not just
based on users.

147
05:46.400 --> 05:49.910 align:middle line:90%
We can still do the
classical IP braced ACLs,

148
05:49.910 --> 05:51.350 align:middle line:84%
just like we've always seen.

149
05:51.350 --> 05:53.990 align:middle line:90%
So we could block traffic
from one subnet to another.

150
05:53.990 --> 05:56.390 align:middle line:90%
We can also set
application policies, which

151
05:56.390 --> 05:59.380 align:middle line:90%
is where we define things,
like, QoS and class

152
05:59.380 --> 06:00.680 align:middle line:84%
of service treatments.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

152
05:59.380 --> 06:00.680 align:middle line:84%
of service treatments.

153
06:00.680 --> 06:05.030 align:middle line:90%
And lastly, we can also set
up any traffic copy scenarios,

154
06:05.030 --> 06:08.090 align:middle line:90%
where if we need to do any
packet captures or wire

155
06:08.090 --> 06:10.520 align:middle line:90%
sharking, especially when
certain events are triggered,

156
06:10.520 --> 06:12.920 align:middle line:90%
this is where we can set
up those policies, too.

157
06:12.920 --> 06:15.650 align:middle line:90%
So this is where we define
our business intent.

158
06:15.650 --> 06:18.620 align:middle line:90%
And this is largely
coming from ISE.

159
06:18.620 --> 06:20.210 align:middle line:90%
Now, provision is
where the rubber

160
06:20.210 --> 06:21.900 align:middle line:84%
meets the road, like I said.

161
06:21.900 --> 06:25.770 align:middle line:90%
This is where we define all of
the devices in our inventory.

162
06:25.770 --> 06:28.160 align:middle line:90%
One of the coolest things
about Cisco DNA Center

163
06:28.160 --> 06:31.940 align:middle line:90%
is we can just point it in
the direction of our network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
06:28.160 --> 06:31.940 align:middle line:90%
is we can just point it in
the direction of our network

164
06:31.940 --> 06:36.410 align:middle line:90%
devices and it can discover all
of the devices in our network.

165
06:36.410 --> 06:39.230 align:middle line:90%
For instance, in my case,
I specified this device

166
06:39.230 --> 06:42.680 align:middle line:84%
right here as my seed node.

167
06:42.680 --> 06:44.930 align:middle line:90%
I said just start
with this device

168
06:44.930 --> 06:46.970 align:middle line:90%
and figure out the
rest from there.

169
06:46.970 --> 06:49.550 align:middle line:90%
And it can actually
use things like CDP

170
06:49.550 --> 06:51.650 align:middle line:84%
to detect who the neighbors are.

171
06:51.650 --> 06:53.900 align:middle line:90%
Then it jumps from one
box to the next box

172
06:53.900 --> 06:56.360 align:middle line:90%
until it's discovered
the entire network.

173
06:56.360 --> 06:59.420 align:middle line:90%
If we wanted to, we can
provision the entire network.

174
06:59.420 --> 07:02.750 align:middle line:90%
We can bring it in from
a factory defaulted state
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

174
06:59.420 --> 07:02.750 align:middle line:90%
We can bring it in from
a factory defaulted state

175
07:02.750 --> 07:05.130 align:middle line:84%
using LAN automation.

176
07:05.130 --> 07:08.000 align:middle line:90%
So we tell DNA Center
what IP address ranges

177
07:08.000 --> 07:11.000 align:middle line:90%
it can use in order to
bring all of these devices

178
07:11.000 --> 07:13.520 align:middle line:90%
into the network and
create connectivity, create

179
07:13.520 --> 07:15.590 align:middle line:84%
policies, create AAA settings.

180
07:15.590 --> 07:18.690 align:middle line:90%
It does all of that
for us from scratch.

181
07:18.690 --> 07:21.220 align:middle line:90%
Again, what we really have
to do is just point it

182
07:21.220 --> 07:23.660 align:middle line:90%
in the direction, just
give it a starting point

183
07:23.660 --> 07:24.950 align:middle line:84%
to start automating.

184
07:24.950 --> 07:26.750 align:middle line:84%
And it does the rest for us.

185
07:26.750 --> 07:28.460 align:middle line:90%
Once these devices
are all brought

186
07:28.460 --> 07:30.710 align:middle line:90%
into the network, what we
can do is we just jump over
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

186
07:28.460 --> 07:30.710 align:middle line:90%
into the network, what we
can do is we just jump over

187
07:30.710 --> 07:32.030 align:middle line:84%
to the fabric section.

188
07:32.030 --> 07:35.270 align:middle line:90%
And this is where we actually
deploy our SD-Access fabric.

189
07:35.270 --> 07:37.970 align:middle line:90%
Within the SD-Access fabric
configuration section,

190
07:37.970 --> 07:41.900 align:middle line:90%
all we do is we tell DNA Center
which virtual networks should

191
07:41.900 --> 07:43.520 align:middle line:84%
be within this site.

192
07:43.520 --> 07:47.000 align:middle line:90%
That way when users plug in,
they can communicate to ISE

193
07:47.000 --> 07:49.370 align:middle line:90%
and be assigned to the
correct virtual network

194
07:49.370 --> 07:52.520 align:middle line:90%
with the correct Cisco
TrustSec segmentation policies

195
07:52.520 --> 07:53.420 align:middle line:84%
assigned to it.

196
07:53.420 --> 07:55.170 align:middle line:90%
And then lastly is the
assurance workflow,

197
07:55.170 --> 07:56.212 align:middle line:84%
which we've already seen.

198
07:56.212 --> 07:57.710 align:middle line:90%
This is where we
can actually see

199
07:57.710 --> 07:59.510 align:middle line:90%
what the health and
status of not only

200
07:59.510 --> 08:02.600 align:middle line:90%
our network devices,
but also our clients,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

200
07:59.510 --> 08:02.600 align:middle line:90%
our network devices,
but also our clients,

201
08:02.600 --> 08:04.490 align:middle line:90%
such as wired and
wireless health.

202
08:04.490 --> 08:06.890 align:middle line:90%
And we can troubleshoot
any problems from there,

203
08:06.890 --> 08:09.223 align:middle line:90%
trying to figure out why
things are and aren't working.

204
08:09.223 --> 08:11.390 align:middle line:90%
In fact, it looks like I've
got some troubleshooting

205
08:11.390 --> 08:12.950 align:middle line:84%
to do on my own end here.

206
08:12.950 --> 08:15.710 align:middle line:90%
But also, if you have
the correct licensing,

207
08:15.710 --> 08:18.090 align:middle line:90%
and NetFlow and
telemetry is enabled,

208
08:18.090 --> 08:20.990 align:middle line:90%
you can also do things
like deep packet inspection

209
08:20.990 --> 08:25.220 align:middle line:90%
to figure out what applications
are our users using?

210
08:25.220 --> 08:26.240 align:middle line:84%
And we can assign them.

211
08:26.240 --> 08:28.820 align:middle line:90%
Are they business
critical applications?

212
08:28.820 --> 08:31.190 align:middle line:84%
Or are they things like Netflix?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

212
08:28.820 --> 08:31.190 align:middle line:84%
Or are they things like Netflix?

213
08:31.190 --> 08:34.610 align:middle line:90%
DNA Center can then report on
the health of our applications

214
08:34.610 --> 08:36.690 align:middle line:84%
within the sites themselves.

215
08:36.690 --> 08:38.570 align:middle line:90%
So we can see things,
like, oh my gosh,

216
08:38.570 --> 08:41.659 align:middle line:90%
Office 365 is a business
critical application.

217
08:41.659 --> 08:44.210 align:middle line:90%
And users in this
particular building

218
08:44.210 --> 08:47.420 align:middle line:90%
are having problems
with just Office 365.

219
08:47.420 --> 08:49.940 align:middle line:90%
We can actually
investigate granular items

220
08:49.940 --> 08:54.290 align:middle line:90%
like that in almost real time
because DNA Center enables

221
08:54.290 --> 08:58.220 align:middle line:90%
us to take control over these
situations, in total visibility

222
08:58.220 --> 09:00.060 align:middle line:90%
into what's going
on with our network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

222
08:58.220 --> 09:00.060 align:middle line:90%
into what's going
on with our network.

223
09:00.060 --> 09:02.150 align:middle line:90%
So that introduces what
the four workflows are

224
09:02.150 --> 09:04.942 align:middle line:90%
and how we actually design
and build an SD-Access fabric.

225
09:04.942 --> 09:06.650 align:middle line:90%
I hope this has been
informative for you.

226
09:06.650 --> 09:09.010 align:middle line:90%
And I'd like to thank
you for viewing.