WEBVTT

1
00:00.000 --> 00:09.930
Cisco's SD-WAN offers a really cool feature to incorporate these co-locations

2
00:09.930 --> 00:12.000
into our WAN environment.

3
00:12.000 --> 00:16.000
It's called Cloud On-RAMP for co-location.

4
00:16.000 --> 00:22.990
And what this feature does is it allows for seamless integration between our

5
00:22.990 --> 00:26.000
enterprise, our co-location,

6
00:26.000 --> 00:31.810
and infrastructure as a service and software as a service offerings from our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

6
00:26.000 --> 00:31.810
and infrastructure as a service and software as a service offerings from our

7
00:31.810 --> 00:33.000
providers.

8
00:33.000 --> 00:38.670
So in this video, let's jump in, take a look at some of the details on how this

9
00:38.670 --> 00:44.310
works, as well as the architecture and all of the pieces that make up this

10
00:44.310 --> 00:46.000
feature.

11
00:46.000 --> 00:54.040
Cloud On-RAMP for co-location is a feature that allows V-Manage to both

12
00:54.040 --> 00:58.000
provision and manage the routers at a co-location.

13
00:58.000 --> 01:03.000
Now in order to do this, there are quite a few moving parts.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:58.000 --> 01:03.000
Now in order to do this, there are quite a few moving parts.

14
01:03.000 --> 01:09.000
But first, let's talk about Cisco's definition of a co-location.

15
01:09.000 --> 01:14.130
Now we've talked about what co-location is, but Cisco does have a very specific

16
01:14.130 --> 01:20.560
definition, which is a stack of computing and networking fabric that brings up

17
01:20.560 --> 01:27.000
multiple virtual networking functions and multiple service chains on them.

18
01:27.000 --> 01:32.930
And to go along with that definition, they have some characteristics for the co
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
01:27.000 --> 01:32.930
And to go along with that definition, they have some characteristics for the co

19
01:32.930 --> 01:34.000
-location.

20
01:34.000 --> 01:42.050
The first is the ability to connect branch users or endpoints to a hybrid cloud

21
01:42.050 --> 01:44.000
or data center.

22
01:44.000 --> 01:50.000
So again, could be partially cloud providers and partially co-locations.

23
01:50.000 --> 01:56.510
And as we said, it does use V-Manage as the orchestrator here that's

24
01:56.510 --> 02:01.000
responsible for provisioning the devices in the co-location.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
01:56.510 --> 02:01.000
responsible for provisioning the devices in the co-location.

25
02:01.000 --> 02:08.120
And the last characteristic is that each co-location does not have visibility

26
02:08.120 --> 02:14.000
of the other co-locations either at the same site or across sites.

27
02:14.000 --> 02:17.000
Each one is independent.

28
02:17.000 --> 02:21.000
Now this feature does have a lot of different components.

29
02:21.000 --> 02:28.000
So let's go ahead and talk about those components of On-RAMP for co-location.

30
02:28.000 --> 02:34.000
The first component is the cloud services platform or the CSP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
02:28.000 --> 02:34.000
The first component is the cloud services platform or the CSP.

31
02:34.000 --> 02:37.000
This is actually a server.

32
02:37.000 --> 02:43.910
This is a C-series UCS server, which is the hardware that's going to be running

33
02:43.910 --> 02:45.000
this feature.

34
02:45.000 --> 02:53.320
Next is the network function virtualization infrastructure software or the NFV

35
02:53.320 --> 02:54.000
IS.

36
02:54.000 --> 03:00.200
This is essentially the hypervisor that's going to be running on the CSP to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
02:54.000 --> 03:00.200
This is essentially the hypervisor that's going to be running on the CSP to

37
03:00.200 --> 03:04.700
support the software we're going to be talking about for the rest of these

38
03:04.700 --> 03:06.000
components.

39
03:06.000 --> 03:11.000
For example, the virtual network functions or the VNFs.

40
03:11.000 --> 03:18.100
The virtual network functions are the modules that we're actually trying to run

41
03:18.100 --> 03:20.000
on our NFVIS up here.

42
03:20.000 --> 03:24.000
These are generally going to be running as Docker containers.

43
03:24.000 --> 03:27.000
We'll see this more in the architecture in just a moment.

44
03:27.000 --> 03:33.630
But this can be anything from routers to firewalls, either Cisco or third party
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
03:27.000 --> 03:33.630
But this can be anything from routers to firewalls, either Cisco or third party

45
03:33.630 --> 03:34.000
.

46
03:34.000 --> 03:38.000
So there's a lot of different things that we can support for the VNFs.

47
03:38.000 --> 03:44.000
Of course, at some point, our virtual network has to meet the physical network.

48
03:44.000 --> 03:48.000
So we also have the physical network functions or the PNFs.

49
03:48.000 --> 03:53.070
And this is where the hardware comes in that we actually use to connect all of

50
03:53.070 --> 03:56.000
this into our actual physical network.

51
03:56.000 --> 04:01.000
That physical network is going to be the network fabric.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
03:56.000 --> 04:01.000
That physical network is going to be the network fabric.

52
04:01.000 --> 04:06.000
This is going to consist of two Cisco catalyst, 9500 series switches.

53
04:06.000 --> 04:10.310
That's at least what's currently supported in this environment for the physical

54
04:10.310 --> 04:12.000
network functions.

55
04:12.000 --> 04:16.800
There will also be a management network, which is going to be for our out of

56
04:16.800 --> 04:18.000
band management.

57
04:18.000 --> 04:23.000
The virtual network functions also have to be networked together.

58
04:23.000 --> 04:28.040
This is going to be handled by these 9500 series switches, connecting them

59
04:28.040 --> 04:30.000
together through various VLANs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
04:30.000 --> 04:34.930
And of course, the physical network functions also have to have network

61
04:34.930 --> 04:40.000
connectivity, also handled by those 9500 series switches.

62
04:40.000 --> 04:46.610
Then these various services, the VNFs are going to get changed together to

63
04:46.610 --> 04:49.000
function and forward traffic between them.

64
04:49.000 --> 04:53.890
That's part of what the catalyst 9500s are going to be doing linking these

65
04:53.890 --> 04:56.000
different services together.

66
04:56.000 --> 05:01.000
Next, we have the Cisco co-location manager, which is what's actually in charge
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
04:56.000 --> 05:01.000
Next, we have the Cisco co-location manager, which is what's actually in charge

67
05:01.000 --> 05:08.210
of managing those catalyst 9500 series switches that are acting as the network

68
05:08.210 --> 05:09.000
fabric.

69
05:09.000 --> 05:14.000
There's also the Cisco network services orchestrator or the NSO.

70
05:14.000 --> 05:20.910
And of course, as we've mentioned, we have complete orchestration using NSO

71
05:20.910 --> 05:23.000
through Cisco V Manage.

72
05:23.000 --> 05:27.900
So all of this ties back into SD WAN, which is what's managing this entire

73
05:27.900 --> 05:29.000
operation.

74
05:29.000 --> 05:35.510
So now that we know the basic overall components, let's take a look at how all
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
05:29.000 --> 05:35.510
So now that we know the basic overall components, let's take a look at how all

75
05:35.510 --> 05:38.000
of these fit together.

76
05:38.000 --> 05:43.990
So our first component here is the management through the plug and play cloud,

77
05:43.990 --> 05:49.650
V bond and V Manage for the orchestrator of all of the management of this

78
05:49.650 --> 05:51.000
entire system.

79
05:51.000 --> 05:55.000
Next is the Cisco co-lo manager.

80
05:55.000 --> 06:02.230
This is a software stack that actually runs on the NF VIS, which is actually
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
05:55.000 --> 06:02.230
This is a software stack that actually runs on the NF VIS, which is actually

81
06:02.230 --> 06:04.000
represented down here.

82
06:04.000 --> 06:10.410
Remember, this is the hypervisor and Cisco co-lo manager is running on top of

83
06:10.410 --> 06:13.000
that as a Docker container.

84
06:13.000 --> 06:19.000
This is what then manages those catalyst 9500 series switches.

85
06:19.000 --> 06:24.120
Again, this includes the day zero configuration, configuring V lands and system

86
06:24.120 --> 06:25.000
settings.

87
06:25.000 --> 06:30.000
This is what allows communication between the service chains.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
06:30.000 --> 06:36.000
Part of this component is the network services orchestrator or the NSO.

89
06:36.000 --> 06:43.190
The job of this module is to take the intent configuration from the Cisco co-lo

90
06:43.190 --> 06:49.570
manager and actually convert that into a device specific configuration for

91
06:49.570 --> 06:55.000
these catalyst 9500 series switches that are part of our environment.

92
06:55.000 --> 07:00.000
So again, this is what's in charge of configuring the actual switches.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
07:00.000 --> 07:10.680
Now some other components to discuss here. Again, we have the Cisco cloud

94
07:10.680 --> 07:12.390
services platform, which in general is the server or the hardware that all of

95
07:12.390 --> 07:13.000
this is running on.

96
07:13.000 --> 07:19.960
We've sort of already mentioned the NF VIS, which is the hypervisor that runs

97
07:19.960 --> 07:23.000
on this x86 CSP platform.

98
07:23.000 --> 07:27.950
This is the software that provides your virtual machine life cycle management

99
07:27.950 --> 07:33.130
service chaining virtual machine image management platform management plug and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
07:27.950 --> 07:33.130
service chaining virtual machine image management platform management plug and

100
07:33.130 --> 07:35.000
play for bootstrapping.

101
07:35.000 --> 07:41.000
It handles authentication authorization and accounting and it handles syslog.

102
07:41.000 --> 07:46.750
So there's a lot of components here to the NF VIS, but essentially it's the

103
07:46.750 --> 07:52.170
hypervisor that's running and is then going to support all of our virtual

104
07:52.170 --> 07:59.590
network functions, such as things like virtual firewalls, virtual routers, and

105
07:59.590 --> 08:00.000
so on.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
08:00.000 --> 08:06.330
And as we sort of already mentioned, the Cisco co-lo manager itself also runs

107
08:06.330 --> 08:11.000
on this virtualization platform as a Docker container.

108
08:11.000 --> 08:16.200
Now, of course, each of these VNFs are going to need to be able to talk to each

109
08:16.200 --> 08:19.000
other for a lot of our functionality.

110
08:19.000 --> 08:24.310
And that's what we refer to as service chaining that again is going to be

111
08:24.310 --> 08:31.100
handled by our catalyst 9500 series switches down here at the bottom, allowing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
08:24.310 --> 08:31.100
handled by our catalyst 9500 series switches down here at the bottom, allowing

112
08:31.100 --> 08:34.000
communication between the VNFs.

113
08:34.000 --> 08:40.640
This service chaining is going to be done at layer two, using VLAN destination

114
08:40.640 --> 08:44.000
MAC address based service chaining.

115
08:44.000 --> 08:50.920
And also note that this can be done either for VNFs running on the same cloud

116
08:50.920 --> 08:58.450
services platform or between platforms, simply meaning that we could have this

117
08:58.450 --> 09:00.000
ASA V on the left.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
09:00.000 --> 09:07.000
Talk to this CSA 1000 V over here on the right.

119
09:07.000 --> 09:10.000
This would be a perfectly allowed configuration.

120
09:10.000 --> 09:17.010
To actually allow this, the catalyst 9500s are again doing the network fabric,

121
09:17.010 --> 09:23.840
forwarding that traffic between the VNFs using the VLANs and those layer two

122
09:23.840 --> 09:25.000
lookups.

123
09:25.000 --> 09:29.000
A couple other components that aren't listed here directly on the diagram.

124
09:29.000 --> 09:33.390
We do have a management network, which is, of course, a dedicated management
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
09:29.000 --> 09:33.390
We do have a management network, which is, of course, a dedicated management

125
09:33.390 --> 09:38.990
network, which connects the NF VIS software directly into our management

126
09:38.990 --> 09:40.000
network.

127
09:40.000 --> 09:45.520
And we have the physical network functions again ties directly into the

128
09:45.520 --> 09:52.000
catalyst 9500s, allowing all of this to talk to the physical network.

129
09:52.000 --> 09:59.940
So overall, this is the architecture and the components for the cloud on ramp

130
09:59.940 --> 10:02.000
for co-location.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
09:59.940 --> 10:02.000
for co-location.

131
10:02.000 --> 10:08.000
So in this video, we talked a bit about cloud on ramp for co-location.

132
10:08.000 --> 10:14.000
We talked about its components and how each of these fit into the architecture.

133
10:14.000 --> 10:20.410
Remember that all of this runs on the cloud services platform, which is the

134
10:20.410 --> 10:27.000
hardware component, and then runs on top of NF VIS, which is the hypervisor,

135
10:27.000 --> 10:32.410
allowing all of these other components, specifically our virtual network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

135
10:27.000 --> 10:32.410
allowing all of these other components, specifically our virtual network

136
10:32.410 --> 10:38.000
functions to run on top of cloud on ramp for co-location.

137
10:38.000 --> 10:44.460
So now that we've talked a bit about co-locations, in the next video, let's

138
10:44.460 --> 10:48.000
jump in and take a look at cloud exchanges.