WEBVTT

1
00:00.000 --> 00:04.800
It's time to swing our focus over to talk specifically about Cisco's software

2
00:04.800 --> 00:06.440
defined access solution.

3
00:06.440 --> 00:10.860
So when we're talking about Cisco SDA, it's actually built on traditional Cisco

4
00:10.860 --> 00:11.600
hardware.

5
00:11.600 --> 00:18.560
We're talking about switches and routers as well as wireless LAN controllers

6
00:18.560 --> 00:19.080
and

7
00:19.080 --> 00:22.200
access points.

8
00:22.200 --> 00:27.240
All of the same hardware that Cisco sells for a traditional network

9
00:27.240 --> 00:27.760
architecture,

10
00:28.040 --> 00:30.040
that's what we're going to use for SDA.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:28.040 --> 00:30.040
that's what we're going to use for SDA.

11
00:30.040 --> 00:35.600
We're talking about Cisco Catalyst 9300s and ISRs and

12
00:35.600 --> 00:41.600
9100 and 9800 access points and wireless LAN controllers.

13
00:41.600 --> 00:46.200
So all of this that we've maybe potentially already purchased as part of a

14
00:46.200 --> 00:47.120
traditional architecture

15
00:47.120 --> 00:49.920
can be migrated into SDA.

16
00:49.920 --> 00:52.320
But it's also going to be built on

17
00:52.320 --> 00:54.760
controllers that Cisco has for us.

18
00:54.760 --> 00:56.760
And those controllers,

19
00:57.560 --> 01:02.960
yes, Polaro, are going to be a pair that is Catalyst Center.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:57.560 --> 01:02.960
yes, Polaro, are going to be a pair that is Catalyst Center.

20
01:02.960 --> 01:08.120
Catalyst Center had a different name for a long time.

21
01:08.120 --> 01:12.880
It used to be known as DNA Center or DNAC or D-NAC.

22
01:12.880 --> 01:17.510
A lot of people used to pronounce it, but now it has been rebranded to Catalyst

23
01:17.510 --> 01:17.880
Center.

24
01:17.880 --> 01:21.960
And we have the Identity Services Engine or ICE.

25
01:21.960 --> 01:26.720
Catalyst Center is going to manage the Layer 2, Layer 3 network,

26
01:26.720 --> 01:29.600
the Fabric, a whole lot of other components.

27
01:29.600 --> 01:32.880
ICE is all about managing the security.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:29.600 --> 01:32.880
ICE is all about managing the security.

28
01:32.880 --> 01:38.880
Furthermore, I mentioned before that one of the advantages to SDA is our admins

29
01:38.880 --> 01:44.240
are going to log into a single point of management, a single pane of management

30
01:44.240 --> 01:44.680
, if you will.

31
01:44.680 --> 01:48.200
And that in this case is going to be Catalyst Center.

32
01:48.200 --> 01:51.840
So what about ICE? Well, ICE is going to integrate

33
01:52.720 --> 01:57.330
into Catalyst Center for us, making it so that we don't have to log into both

34
01:57.330 --> 01:58.960
platforms to manage SDA.

35
01:58.960 --> 02:05.080
Now Cisco breaks down SDA operation into four different layers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:58.960 --> 02:05.080
Now Cisco breaks down SDA operation into four different layers.

36
02:05.080 --> 02:09.890
And we're not talking about OSI model type of layers, we just walked through S

37
02:09.890 --> 02:10.560
DA when,

38
02:10.560 --> 02:13.320
if you're working your way through this course sequentially, you just heard

39
02:13.320 --> 02:16.120
about four different layers of operation and SDA.

40
02:16.120 --> 02:19.960
And these are four different layers relative to the SDA.

41
02:19.960 --> 02:23.760
The WAN layers, which again are all different from OSI.

42
02:23.760 --> 02:28.840
Either way, when we're breaking down SDA, we do have a physical layer,

43
02:28.840 --> 02:31.400
and then we have a network layer,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
02:28.840 --> 02:31.400
and then we have a network layer,

44
02:31.400 --> 02:35.640
but we also have the controller layer,

45
02:35.640 --> 02:39.440
as well as the management layer.

46
02:39.440 --> 02:44.280
So we're going to go ahead and go through each one of these and talk briefly

47
02:44.280 --> 02:46.440
about the responsibilities of each one.

48
02:46.440 --> 02:49.560
Let's go ahead and start with the physical layer.

49
02:50.280 --> 02:55.050
The physical layer is all about these devices here, all of the devices that

50
02:55.050 --> 02:56.720
make up the fabric.

51
02:56.720 --> 02:59.760
It's how we build out our physical network components.

52
02:59.760 --> 03:04.170
And what we'll find is that these different devices can be deployed into
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:59.760 --> 03:04.170
And what we'll find is that these different devices can be deployed into

53
03:04.170 --> 03:06.520
specific roles within the network.

54
03:06.520 --> 03:10.720
So these roles include a fabric edge node.

55
03:10.720 --> 03:16.660
The fabric edge node is effectively what we're going to turn every access layer

56
03:16.660 --> 03:17.800
switch into,

57
03:18.040 --> 03:21.280
at least as far as the switches that connect into the fabric.

58
03:21.280 --> 03:26.800
So these are the devices in our diagram that sit here at the edge,

59
03:26.800 --> 03:31.230
and they form their VX line tunnels to one another, and they have networks
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
03:26.800 --> 03:31.230
and they form their VX line tunnels to one another, and they have networks

60
03:31.230 --> 03:33.200
attached to them as well.

61
03:33.200 --> 03:37.220
So again, for the most part, when we're thinking about fabric edge nodes, we

62
03:37.220 --> 03:40.800
should be thinking about the access layer switches.

63
03:40.800 --> 03:44.920
The next role to be aware of here, we've got a few of them.

64
03:45.920 --> 03:49.400
We've got fabric edge nodes. We also have the control plane node,

65
03:49.400 --> 03:53.360
which will often see abbreviated as the CP node.

66
03:53.360 --> 03:59.560
The control plane node is responsible for mapping our subnets to one another.

67
03:59.560 --> 04:01.920
So we're going to have this control plane node out here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
03:59.560 --> 04:01.920
So we're going to have this control plane node out here.

68
04:01.920 --> 04:07.000
And when a packet comes in, this switch needs to figure out what to do with it.

69
04:07.000 --> 04:10.280
So it checks in with the control plane node has a quick exchange.

70
04:10.280 --> 04:14.520
And then it knows to forward it over here to the ultimate destination.

71
04:14.880 --> 04:21.280
So this is all about our subnet and especially our device mappings.

72
04:21.280 --> 04:27.530
Given that this is a stretched layer to environment, I might have a specific

73
04:27.530 --> 04:31.000
device over here and specific device on the left here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
04:27.530 --> 04:31.000
device over here and specific device on the left here.

74
04:31.000 --> 04:33.000
These devices are part of the same subnet.

75
04:33.000 --> 04:37.880
And so when we're talking about sharing control plane information, it's not

76
04:37.880 --> 04:38.920
about sharing the subnet.

77
04:38.920 --> 04:41.560
It's about sharing the actual device mappings.

78
04:42.240 --> 04:45.400
Now, we might also have a fabric border node.

79
04:45.400 --> 04:54.080
The fabric border node is going to be what sits at the end of our SDA fabric.

80
04:54.080 --> 04:57.760
So we've got sort of the rest of the world out here.

81
04:57.760 --> 05:05.580
All of the non SDA environment, the core of the network, for example, all of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
04:57.760 --> 05:05.580
All of the non SDA environment, the core of the network, for example, all of

82
05:05.580 --> 05:10.200
this, this is going to connect in through the border node.

83
05:11.640 --> 05:13.640
We'll say border node here.

84
05:13.640 --> 05:16.560
So I'm going to bring this into the border node.

85
05:16.560 --> 05:23.200
And this serves sort of as number one, a gateway to the rest of the world.

86
05:23.200 --> 05:28.870
But because it's a gateway, we can also think of it as sort of a default route

87
05:28.870 --> 05:34.960
or a default destination for all of our SDA devices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
05:28.870 --> 05:34.960
or a default destination for all of our SDA devices.

88
05:35.320 --> 05:39.160
If we don't know where we're supposed to send a packet, we're going to send it

89
05:39.160 --> 05:42.600
to the border node and hope it can get us to where we're trying to go.

90
05:42.600 --> 05:46.480
Now, as part of this, we're also going to find that our wireless land

91
05:46.480 --> 05:51.690
controllers, as well as our access points, they're going to also natively

92
05:51.690 --> 05:55.000
connect in via this physical layer.

93
05:55.000 --> 05:57.960
So we have native connection to the fabric.

94
05:58.560 --> 06:03.100
And yet they follow slightly different rules, but it's pretty fascinating to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
05:58.560 --> 06:03.100
And yet they follow slightly different rules, but it's pretty fascinating to

95
06:03.100 --> 06:06.680
see that our access points are going to be VX land capable.

96
06:06.680 --> 06:11.970
And they're going to send our client traffic into the SDA world via VX land

97
06:11.970 --> 06:13.200
themselves.

98
06:13.200 --> 06:17.800
And so it's pretty fun conversation to have about what's happening with our

99
06:17.800 --> 06:19.240
wireless devices.

100
06:19.240 --> 06:22.320
But the wireless devices don't just sit off to the side.

101
06:22.320 --> 06:25.960
They are active participants in the SDA fabric.

102
06:27.000 --> 06:29.720
Now, from here, we're going to talk about the network layer.

103
06:29.720 --> 06:34.760
And the network layer is broken down into three different components.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
06:29.720 --> 06:34.760
And the network layer is broken down into three different components.

104
06:34.760 --> 06:39.820
And really, these are the planes of operation, which are going to sound a

105
06:39.820 --> 06:42.000
little more traditional on some level.

106
06:42.000 --> 06:48.600
We have, for example, the data plane and the data plane is going to be run by V

107
06:48.600 --> 06:49.320
X land.

108
06:49.320 --> 06:54.080
Because it's all about forwarding traffic from source to destination and our VX

109
06:54.080 --> 06:56.440
land tunnels is how we're going to accomplish that.

110
06:57.000 --> 06:58.320
We also have a control plane.

111
06:58.320 --> 07:01.520
This is what I meant by it, signing a little bit more traditional.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
06:58.320 --> 07:01.520
This is what I meant by it, signing a little bit more traditional.

112
07:01.520 --> 07:05.840
And our control plane is going to be managed by Lisp.

113
07:05.840 --> 07:11.200
Lisp is all about sharing our subnet and again, our device mappings.

114
07:11.200 --> 07:15.780
So this exchange right here between our fabric edge node and the control plane

115
07:15.780 --> 07:16.280
node.

116
07:16.280 --> 07:22.410
This is run or managed by Lisp and this communications path between our fabric

117
07:22.410 --> 07:23.600
edge nodes.

118
07:23.600 --> 07:26.160
This is managed by VX land.

119
07:26.520 --> 07:28.280
And we'll see more details of this coming up.

120
07:28.280 --> 07:31.800
But here's where things start to look a little less traditional.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
07:28.280 --> 07:31.800
But here's where things start to look a little less traditional.

121
07:31.800 --> 07:34.640
We also have what Cisco calls the policy plane.

122
07:34.640 --> 07:42.920
And this is managed by Cisco trust sec, which can be abbreviated as CTS.

123
07:42.920 --> 07:47.040
Cisco trust sec is all about the security components.

124
07:47.040 --> 07:51.510
We mentioned that we care greatly about security and we're going to manage this

125
07:51.510 --> 07:52.160
via ice,

126
07:52.160 --> 07:56.840
the identity services engine and Cisco trust sec, allowing for policy

127
07:56.840 --> 07:57.920
enforcement to happen

128
07:57.920 --> 08:02.160
by the switches rather than some centralized forwarding mechanism.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
07:57.920 --> 08:02.160
by the switches rather than some centralized forwarding mechanism.

129
08:02.160 --> 08:07.040
Now, next we have a couple of other layers here.

130
08:07.040 --> 08:11.400
We have the controller layers we mentioned and the controller layer is going to

131
08:11.400 --> 08:13.600
consist of these two devices here,

132
08:13.600 --> 08:15.120
Cadillac Center and ice.

133
08:15.120 --> 08:19.000
And we'll be talking a little bit more about those controllers.

134
08:19.000 --> 08:23.080
But in the end, they are SDN controllers managing this whole environment.

135
08:23.080 --> 08:28.280
And they can be deployed as physical appliances or virtual appliances.

136
08:28.280 --> 08:32.200
And lastly, we have the management layer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
08:28.280 --> 08:32.200
And lastly, we have the management layer.

137
08:32.200 --> 08:37.440
The management layer is how we manage our infrastructure.

138
08:37.440 --> 08:42.560
And so this is primarily going to be focused on using our web graphical user

139
08:42.560 --> 08:43.120
interface

140
08:43.120 --> 08:48.430
to communicate with the controllers, but also our ability to use those rest

141
08:48.430 --> 08:49.040
APIs.

142
08:49.040 --> 08:54.480
And the more we can leverage these rest APIs and network programmability,

143
08:54.480 --> 08:58.560
the better off we're going to be as far as managing our large environments and

144
08:58.560 --> 09:01.040
simply put and taking advantage
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
08:58.560 --> 09:01.040
simply put and taking advantage

145
09:01.040 --> 09:03.520
of modern network management.

146
09:03.520 --> 09:07.120
So this is how Cisco SDA comes together.

147
09:07.120 --> 09:12.080
It's a mixture of traditional Cisco network devices with some specific

148
09:12.080 --> 09:13.040
controllers.

149
09:13.040 --> 09:18.000
And the way they integrate and the network protocols that we end up deploying

150
09:18.000 --> 09:22.720
is going to form this fabric and allow us to seamlessly manage this environment

151
09:22.720 --> 09:26.720
and build out this access layer fabric.