WEBVTT

1
00:00.000 --> 00:04.000
Well, these days we love analytics.

2
00:04.000 --> 00:07.200
The more data we have, the more we can analyze that data,

3
00:07.200 --> 00:10.200
and ultimately this leads to an entire conversation

4
00:10.200 --> 00:12.680
around network assurance and the idea

5
00:12.680 --> 00:15.800
that we can very quickly resolve issues.

6
00:15.800 --> 00:19.400
Well, first of all, very quickly identify the issues

7
00:19.400 --> 00:22.000
and then very quickly resolve the issues

8
00:22.000 --> 00:27.360
ideally in a proactive methodology.

9
00:27.360 --> 00:29.800
Meaning I don't wait for a problem to happen.

10
00:29.800 --> 00:33.400
I see the problem happening because of my analytics.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:29.800 --> 00:33.400
I see the problem happening because of my analytics.

11
00:33.400 --> 00:35.360
I know I'm about to have a problem

12
00:35.360 --> 00:38.000
or maybe I'm just now starting to experience one

13
00:38.000 --> 00:40.440
as I can go out there and look for the resolution,

14
00:40.440 --> 00:42.240
hopefully before users even notice

15
00:42.240 --> 00:44.080
that there was a problem.

16
00:44.080 --> 00:49.080
So Cisco has a product known as our SD-WAN analytics.

17
00:49.080 --> 00:56.640
And this is an optional module in the SD-WAN space.

18
00:56.640 --> 00:58.600
Now we say it's an optional module.

19
00:58.600 --> 01:00.800
We say, well, why wouldn't we just deploy it?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:58.600 --> 01:00.800
We say, well, why wouldn't we just deploy it?

20
01:00.800 --> 01:04.400
Well, because this is going to require an additional license

21
01:04.400 --> 01:06.000
and so it will cost a little bit more

22
01:06.000 --> 01:08.400
to run it in our infrastructure.

23
01:08.400 --> 01:14.400
And by the way, this used to be a product known as V-ANNELITICS.

24
01:14.400 --> 01:24.400
So Cisco continues to replace our V language a little bit here.

25
01:24.400 --> 01:27.200
I know we just saw the tele-quality of experience

26
01:27.200 --> 01:30.400
as yet to be swapped out, at least at the time of this video.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
01:27.200 --> 01:30.400
as yet to be swapped out, at least at the time of this video.

27
01:30.400 --> 01:32.600
But they do continue to re-brand,

28
01:32.600 --> 01:34.400
to get rid of the Veptella name.

29
01:34.400 --> 01:36.600
So it's SD-WAN analytics.

30
01:36.600 --> 01:39.600
But if you are interested in reading white papers

31
01:39.600 --> 01:43.800
and the like, then it might show up under V-ANNELITICS as well.

32
01:43.800 --> 01:47.200
So the idea here is that it's going to provide insights

33
01:47.200 --> 01:52.200
into the data that's being collected by our SD-WAN devices.

34
01:52.200 --> 01:55.500
So a few examples of this would be to take a look

35
01:55.500 --> 02:01.000
at utilization trends, which circuits are being consumed
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:55.500 --> 02:01.000
at utilization trends, which circuits are being consumed

36
02:01.000 --> 02:04.200
the most, which applications are consuming the most bandwidth.

37
02:04.200 --> 02:07.800
These kinds of conversations can help us to do proper planning

38
02:07.800 --> 02:12.600
and again to potentially proactively identify some issues.

39
02:12.600 --> 02:15.900
We also have capacity projections.

40
02:15.900 --> 02:19.900
I love this idea where they're going to,

41
02:19.900 --> 02:22.800
or this platform is going to look at the data

42
02:22.800 --> 02:27.700
and do a little bit of potentially bandwidth forecasting.

43
02:27.700 --> 02:32.600
To say, all right, we have a maybe 100 meg circuit.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
02:27.700 --> 02:32.600
To say, all right, we have a maybe 100 meg circuit.

44
02:32.600 --> 02:36.900
And based on our analytics, we think that as our bandwidth

45
02:36.900 --> 02:39.600
is becoming more and more used,

46
02:39.600 --> 02:42.700
that this is only going to last us another three months.

47
02:42.700 --> 02:44.900
That we might want to call our service provider

48
02:44.900 --> 02:49.100
and ask about increasing this to maybe a 200 or 250 megabit

49
02:49.100 --> 02:50.700
per second circuit.

50
02:50.700 --> 02:53.000
And that way it's not a big surprise

51
02:53.000 --> 02:55.700
when all of a sudden we're driving a bunch of traffic one day.

52
02:55.700 --> 02:57.200
Hopefully we can get ahead of that

53
02:57.200 --> 03:00.900
and get a bigger circuit provisioned.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:57.200 --> 03:00.900
and get a bigger circuit provisioned.

54
03:00.900 --> 03:03.700
We can also continue to monitor that VIP telequality

55
03:03.700 --> 03:06.600
of experience, and we can track that over time.

56
03:06.600 --> 03:09.100
And so hopefully once we have a baseline,

57
03:09.100 --> 03:12.100
we'll know that, all right, yeah, that looks good

58
03:12.100 --> 03:14.700
that we have a VQO, we have eight.

59
03:14.700 --> 03:17.200
But traditionally, we're bouncing between nine and 10.

60
03:17.200 --> 03:20.500
So something is a little bit wrong, even though on the surface,

61
03:20.500 --> 03:23.200
it might actually look fine.

62
03:23.200 --> 03:26.200
On top of all of this, we can do a little bit

63
03:26.200 --> 03:29.900
of security monitoring via Cisco Talos,

64
03:29.900 --> 03:32.700
which is their security cloud platform.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:29.900 --> 03:32.700
which is their security cloud platform.

65
03:32.700 --> 03:39.200
So we can analyze in real time some amount of threat monitoring.

66
03:39.200 --> 03:45.400
This is really useful, and it demonstrates a little bit

67
03:45.400 --> 03:48.800
of the power of going with something

68
03:48.800 --> 03:51.400
like a Cisco solution for SD-WAN

69
03:51.400 --> 03:54.600
because they have integrations into so many other platforms.

70
03:54.600 --> 03:57.200
It's not just about the SD-WAN solution,

71
03:57.200 --> 03:58.900
but the fact that we can integrate

72
03:58.900 --> 04:01.800
into their security platform, for example.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:58.900 --> 04:01.800
into their security platform, for example.

73
04:01.800 --> 04:05.500
And speaking of which, we do have another platform

74
04:05.500 --> 04:10.000
that Cisco acquired, and that is Thousand Eyes.

75
04:10.000 --> 04:14.900
Thousand Eyes is a monitoring platform

76
04:14.900 --> 04:16.300
that lives in the cloud.

77
04:17.500 --> 04:21.100
That is going to help us to gain deep insights

78
04:21.100 --> 04:24.800
into what's happening in our network.

79
04:24.800 --> 04:27.800
And the way it does is pretty interesting.

80
04:27.800 --> 04:32.600
It deploys agents into three primary locations
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:27.800 --> 04:32.600
It deploys agents into three primary locations

81
04:32.600 --> 04:34.200
to our endpoints.

82
04:34.200 --> 04:37.100
So that would be our user laptops

83
04:37.100 --> 04:40.800
and desktop PCs and the like,

84
04:40.800 --> 04:44.000
to our enterprise devices, such as switches

85
04:44.000 --> 04:47.800
and access points and even our virtual machine hosts

86
04:47.800 --> 04:50.900
and the like, and then also to the cloud.

87
04:50.900 --> 04:55.900
Meaning that if I'm monitoring a particular application,

88
04:55.900 --> 04:57.560
let's say I'm trying to figure out

89
04:57.560 --> 04:59.800
why there's a problem with this application,

90
04:59.800 --> 05:02.300
I'm going to get the view from the endpoint that says,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:59.800 --> 05:02.300
I'm going to get the view from the endpoint that says,

91
05:02.300 --> 05:04.600
hey, I can't reach that application.

92
05:04.600 --> 05:08.100
And the enterprise devices in my networks

93
05:08.100 --> 05:10.000
that say, hey, these sites are fine,

94
05:10.000 --> 05:12.000
but these other sites are not fine.

95
05:12.000 --> 05:15.000
And then also from the cloud, which might tell us

96
05:15.000 --> 05:17.500
whether my network is even the problem.

97
05:17.500 --> 05:19.440
Because maybe we're having problems,

98
05:19.440 --> 05:23.560
but so is everybody else outside of our organization.

99
05:23.560 --> 05:25.600
And so it's a really great architecture.

100
05:25.600 --> 05:27.560
And I love the name Thousand Eyes

101
05:27.560 --> 05:29.660
because it describes very well what they're doing.

102
05:29.660 --> 05:32.460
They're deploying these agents as their eyes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:29.660 --> 05:32.460
They're deploying these agents as their eyes

103
05:32.460 --> 05:35.600
throughout the entire world via the cloud,

104
05:35.600 --> 05:38.200
but then also drilling down as granularly

105
05:38.200 --> 05:40.240
as to our individual endpoints,

106
05:40.240 --> 05:42.200
so we can track what's happening.

107
05:42.200 --> 05:46.840
So this is another integration that we can make

108
05:46.840 --> 05:49.040
into SD-WAN.

109
05:49.040 --> 05:51.480
So if we look at Cisco SD-WAN,

110
05:51.480 --> 05:56.320
we can get onto our V-manage

111
05:56.320 --> 05:58.900
and we can say, you know what,

112
05:58.900 --> 06:03.900
deploy Thousand Eyes agents onto our SD-WAN edges.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
05:58.900 --> 06:03.900
deploy Thousand Eyes agents onto our SD-WAN edges.

113
06:03.900 --> 06:09.640
With just a few simple clicks,

114
06:09.640 --> 06:12.760
this architecture starts to get built out

115
06:12.760 --> 06:16.520
because deploying agents to our enterprise devices

116
06:16.520 --> 06:18.520
can be a little bit cumbersome,

117
06:18.520 --> 06:21.400
but with the fact that I can just log into V-manage

118
06:21.400 --> 06:23.400
and have it automate that deployment

119
06:23.400 --> 06:27.000
to all my WAN devices and then gain all of the insights

120
06:27.000 --> 06:28.860
that I'm getting from Thousand Eyes,

121
06:28.860 --> 06:32.040
hey, that's actually very, very powerful,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
06:28.860 --> 06:32.040
hey, that's actually very, very powerful,

122
06:32.040 --> 06:34.440
especially when I combine it with the analytics

123
06:34.440 --> 06:37.400
I'm getting from SD-WAN analytics.

124
06:37.400 --> 06:39.920
Now, the one downside to this is that

125
06:39.920 --> 06:40.960
this doesn't come free,

126
06:40.960 --> 06:45.360
these Thousand Eyes agents require Thousand Eyes licensing

127
06:45.360 --> 06:49.520
and we already mentioned that SD-WAN analytics

128
06:49.520 --> 06:50.520
requires licensing.

129
06:50.520 --> 06:52.400
So if we're gonna do both of these solutions,

130
06:52.400 --> 06:54.440
we're gonna need to purchase some licensing out there

131
06:54.440 --> 06:56.680
and that's a conversation to have with Cisco,

132
06:56.680 --> 06:59.400
but these platforms all integrate with one another

133
06:59.400 --> 07:02.040
and they can provide some very powerful insights
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
06:59.400 --> 07:02.040
and they can provide some very powerful insights

134
07:02.040 --> 07:03.920
that ultimately are going to bring us back

135
07:03.920 --> 07:05.600
to this conversation.

136
07:05.600 --> 07:07.840
How quickly can I identify a problem?

137
07:07.840 --> 07:09.680
How quickly can I resolve that problem?

138
07:09.680 --> 07:12.200
And if I can be proactive and anticipating

139
07:12.200 --> 07:14.120
when there are going to be problems,

140
07:14.120 --> 07:18.720
that is a massive conversation that every organization

141
07:18.720 --> 07:21.520
is having because of the immense benefits and value

142
07:21.520 --> 07:22.520
that it provides.