WEBVTT

1
00:00.000 --> 00:05.000
So as we jump into troubleshooting our cloud gateways,

2
00:05.000 --> 00:09.000
we're gonna start with AWS.

3
00:09.000 --> 00:12.440
Now AWS has a lot of tools available for us

4
00:12.440 --> 00:14.440
that we can use for logging,

5
00:14.440 --> 00:17.200
for getting alerts and notifications,

6
00:17.200 --> 00:20.160
and we can also have it do certain actions

7
00:20.160 --> 00:22.760
such as email us and such like that

8
00:22.760 --> 00:24.820
in response to these events.

9
00:24.820 --> 00:27.000
So let's go ahead and jump in

10
00:27.000 --> 00:28.800
and take a look at the different tools

11
00:28.800 --> 00:31.720
that are available for us in AWS.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.800 --> 00:31.720
that are available for us in AWS.

12
00:31.720 --> 00:34.400
And then we'll jump into the AWS console

13
00:34.400 --> 00:36.560
and actually take a look at how to configure

14
00:36.560 --> 00:37.880
some of these tools.

15
00:37.880 --> 00:42.840
So the tools available in AWS

16
00:42.840 --> 00:46.200
basically fall into two major categories.

17
00:46.200 --> 00:49.240
The first is the automated tools.

18
00:49.240 --> 00:51.080
So these are of course going to be tools

19
00:51.080 --> 00:54.520
that are going to do their job without our intervention.

20
00:54.520 --> 00:57.120
And some of them of course just make sense.

21
00:57.120 --> 01:00.920
AWS CloudTrail log monitoring.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:57.120 --> 01:00.920
AWS CloudTrail log monitoring.

22
01:00.920 --> 01:03.360
Logging is generally something that's gonna be done

23
01:03.360 --> 01:05.920
without administrative assistance.

24
01:05.920 --> 01:08.960
Now that doesn't mean we don't have to configure these things.

25
01:08.960 --> 01:11.660
It just means that once they're configured,

26
01:11.660 --> 01:14.400
they will perform their job automatically.

27
01:14.400 --> 01:19.400
Another good one here of course is the Amazon CloudWatch alarms.

28
01:19.400 --> 01:22.060
Now CloudWatch we're gonna see in just a moment

29
01:22.060 --> 01:25.280
has some manual tools as well.

30
01:25.280 --> 01:27.160
So some of the things we're gonna set up,

31
01:27.160 --> 01:29.760
again you can see here specifically alarms

32
01:29.760 --> 01:32.320
are part of the automated category,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:29.760 --> 01:32.320
are part of the automated category,

33
01:32.320 --> 01:36.040
but some of the monitoring is of course gonna be manual.

34
01:36.040 --> 01:38.960
And then we have AWS health events

35
01:38.960 --> 01:43.280
which will simply notify us about things such as VPN failure

36
01:43.280 --> 01:45.320
and things along those lines.

37
01:45.320 --> 01:46.880
So as we already sort of said,

38
01:46.880 --> 01:50.000
the other category is manual tools.

39
01:50.000 --> 01:52.280
These are tools that you as the administrator

40
01:52.280 --> 01:55.360
are going to have to use well manually.

41
01:55.360 --> 01:59.160
So the first one here is your CloudWatch homepage.

42
01:59.160 --> 02:02.520
This gives us a nice overview of what's going on.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:59.160 --> 02:02.520
This gives us a nice overview of what's going on.

43
02:02.520 --> 02:05.640
There's a standard default dashboard

44
02:05.640 --> 02:10.200
and there's also a custom dashboard option

45
02:10.200 --> 02:12.360
where we can make our own dashboards

46
02:12.360 --> 02:15.760
to have whatever information we want available on them.

47
02:15.760 --> 02:17.800
We'll take a look at both of these.

48
02:17.800 --> 02:20.540
And then for just a real quick look at things,

49
02:20.540 --> 02:23.780
there's also the Amazon VPC dashboard,

50
02:23.780 --> 02:26.540
which really just gives you sort of an overview

51
02:26.540 --> 02:29.080
of everything going on in the VPC

52
02:29.080 --> 02:31.340
such as your virtual gateways.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:29.080 --> 02:31.340
such as your virtual gateways.

53
02:31.340 --> 02:34.300
So we'll be taking a look at all of these options,

54
02:34.300 --> 02:36.860
not necessarily in the order listed here.

55
02:36.860 --> 02:39.740
So all of this said, let's go ahead and jump in

56
02:39.740 --> 02:41.620
to the AWS console.

57
02:41.620 --> 02:45.180
So here on the AWS console,

58
02:45.180 --> 02:47.060
two things I wanna point out.

59
02:47.060 --> 02:50.380
First, notice for a lot of these topics,

60
02:50.380 --> 02:54.420
the VPC, the CloudWatch, the CloudTrail,

61
02:54.420 --> 02:56.700
AWS health dashboard.

62
02:56.700 --> 03:00.140
I already have these favorited on my quick launch bar
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:56.700 --> 03:00.140
I already have these favorited on my quick launch bar

63
03:00.140 --> 03:03.140
and also they're under recently visited

64
03:03.140 --> 03:07.020
because of course I've been to these things fairly recently.

65
03:07.020 --> 03:09.260
If you don't know how to access any of these

66
03:09.260 --> 03:11.420
as we're going through the demonstration,

67
03:11.420 --> 03:15.460
you can always simply either click on services up here

68
03:15.460 --> 03:18.020
or just search in the search bar

69
03:18.020 --> 03:20.860
and you'll find these things very quickly.

70
03:20.860 --> 03:25.140
So let's begin by looking at CloudTrail,

71
03:25.140 --> 03:28.540
which is essentially one of our major logging options.

72
03:28.540 --> 03:29.980
So I'm just gonna go ahead and launch it

73
03:29.980 --> 03:32.100
from my quick launch bar.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:29.980 --> 03:32.100
from my quick launch bar.

74
03:32.100 --> 03:35.380
This will bring up the CloudTrail initial dashboard.

75
03:35.380 --> 03:38.060
Since I don't have any trails yet,

76
03:38.060 --> 03:41.420
what we wanna do is go ahead and click on a trail.

77
03:41.420 --> 03:45.500
The purpose of this is to create a log of things happening

78
03:45.500 --> 03:47.980
in my AWS account.

79
03:47.980 --> 03:50.860
So we'll go ahead and click on create a trail.

80
03:50.860 --> 03:52.580
And of course, we can do things here

81
03:52.580 --> 03:54.900
like change the trail name.

82
03:54.900 --> 03:59.180
We can also change the trail log bucket and folder,

83
03:59.180 --> 04:02.060
but notice that both of these have defaults.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

83
03:59.180 --> 04:02.060
but notice that both of these have defaults.

84
04:02.060 --> 04:04.180
So if you wanna give it a specific name,

85
04:04.180 --> 04:05.440
you certainly can.

86
04:05.440 --> 04:07.360
If you don't want to, you can just leave it

87
04:07.360 --> 04:09.620
at the default here of management events.

88
04:09.620 --> 04:10.980
That's what I'm gonna do.

89
04:10.980 --> 04:14.220
And we'll just go ahead and hit create trail.

90
04:14.220 --> 04:16.860
So as we can see, this was successful.

91
04:16.860 --> 04:21.700
Also note, by the way, that this is going to an S3 bucket.

92
04:21.700 --> 04:25.520
So just be aware of the fact that you can be billed

93
04:25.520 --> 04:29.540
for the S3 bucket that's being used by CloudTrail.

94
04:29.540 --> 04:32.780
So just keep that in mind as you're setting this up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:29.540 --> 04:32.780
So just keep that in mind as you're setting this up.

95
04:32.780 --> 04:34.700
Next, let's go ahead and click on the name

96
04:34.700 --> 04:37.220
for our CloudTrail.

97
04:37.220 --> 04:39.900
And what we see here is some information about this,

98
04:39.900 --> 04:42.500
such as it's currently logging.

99
04:42.500 --> 04:46.220
Here again, we see that S3 bucket that's being used.

100
04:46.220 --> 04:50.100
And we see other things such as log file validation,

101
04:50.100 --> 04:53.220
whether we're sending an SNS notification,

102
04:53.220 --> 04:55.740
which of course we see is currently disabled,

103
04:55.740 --> 04:58.540
the trail name of course, which is what we named it.

104
04:58.540 --> 05:01.540
But more importantly, as we scroll down here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
04:58.540 --> 05:01.540
But more importantly, as we scroll down here,

105
05:01.540 --> 05:04.020
we can see other things that we can enable.

106
05:04.020 --> 05:06.540
So we can enable CloudWatch logs.

107
05:06.540 --> 05:11.020
If we scroll down further, we can do management events,

108
05:11.020 --> 05:16.020
data events, insight events, and network activity events.

109
05:16.220 --> 05:17.940
So for example, we could come down here,

110
05:17.940 --> 05:22.220
we could hit edit, tell it to log network activity.

111
05:22.220 --> 05:25.740
This is then going to bring up more information,

112
05:25.740 --> 05:29.740
and we can for example, select an event source.

113
05:29.740 --> 05:32.300
Now we're not going to be configuring all of this right now.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
05:29.740 --> 05:32.300
Now we're not going to be configuring all of this right now.

114
05:32.300 --> 05:33.980
So I'm just going to hit cancel,

115
05:33.980 --> 05:36.100
but I just want you to see the other options

116
05:36.100 --> 05:37.740
that are available.

117
05:37.740 --> 05:41.220
So now let's go back to the CloudTrail's dashboard.

118
05:41.220 --> 05:43.940
Here we see our existing trail,

119
05:43.940 --> 05:46.220
and we see that it's currently logging.

120
05:46.220 --> 05:49.020
We can also copy events here to Lake,

121
05:49.020 --> 05:53.500
which is another logging service available through AWS.

122
05:53.500 --> 05:56.780
Now one thing you want to be careful of with trails

123
05:56.780 --> 05:58.900
is when you're done with them,

124
05:58.900 --> 06:02.420
you do have to make sure that they're cleaned up properly.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
05:58.900 --> 06:02.420
you do have to make sure that they're cleaned up properly.

125
06:02.420 --> 06:06.140
So for example, we can go back into our management events,

126
06:06.140 --> 06:09.660
we can hit delete, and it even tells us

127
06:09.660 --> 06:12.660
that we're no longer going to receive log files

128
06:12.660 --> 06:16.260
for the trail, but the ones that were already delivered

129
06:16.260 --> 06:19.340
are not deleted unless you delete them.

130
06:19.340 --> 06:22.860
So even if we delete this, just be aware

131
06:22.860 --> 06:26.300
that even though it says the trail was successfully deleted,

132
06:26.300 --> 06:28.300
you might think you're done with it,

133
06:28.300 --> 06:30.820
but that's not exactly the case.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
06:28.300 --> 06:30.820
but that's not exactly the case.

134
06:30.820 --> 06:33.260
If we come up here to services,

135
06:33.260 --> 06:35.860
we go to S3 over here,

136
06:35.860 --> 06:39.340
notice that I have this S3 bucket

137
06:39.340 --> 06:42.220
that was literally just created.

138
06:42.220 --> 06:44.620
So if I really want to clean up after a trail

139
06:44.620 --> 06:45.940
and I'm done with all the logging,

140
06:45.940 --> 06:48.260
maybe I was just trying to troubleshoot something

141
06:48.260 --> 06:50.740
and capture some specific events,

142
06:50.740 --> 06:54.620
then what I want to do is click on my bucket here

143
06:54.620 --> 06:56.140
and hit delete.

144
06:56.140 --> 06:58.140
Now it's also going to probably yell at us

145
06:58.140 --> 07:01.780
that it's not empty because logging has happened
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
06:58.140 --> 07:01.780
that it's not empty because logging has happened

146
07:01.780 --> 07:03.540
into this bucket.

147
07:03.540 --> 07:06.500
So then what we have to do is we have to empty the bucket.

148
07:06.500 --> 07:07.460
In order to empty it,

149
07:07.460 --> 07:11.540
you have to type permanently delete in this text box

150
07:11.540 --> 07:13.500
and then hit empty.

151
07:13.500 --> 07:16.500
So now it says that we successfully emptied it.

152
07:16.500 --> 07:19.220
Now what we want to do is hit exit,

153
07:19.220 --> 07:23.580
highlight the bucket again, and again hit delete.

154
07:23.580 --> 07:26.460
It is going to make you type the entire name of the bucket

155
07:26.460 --> 07:28.100
before you can delete it.

156
07:28.100 --> 07:31.100
So this is probably someplace you may want to just copy
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

156
07:28.100 --> 07:31.100
So this is probably someplace you may want to just copy

157
07:31.100 --> 07:34.540
and paste, or of course you could type the whole thing in

158
07:34.540 --> 07:36.140
just to make sure.

159
07:36.140 --> 07:38.980
But it does tell you right here what you have to type.

160
07:38.980 --> 07:42.780
So you can just copy that, paste it in,

161
07:42.780 --> 07:44.540
and hit delete bucket.

162
07:44.540 --> 07:46.980
So that takes care of CloudTrail

163
07:46.980 --> 07:50.180
and how to clean up when you're done using it.

164
07:50.180 --> 07:54.420
Next, let's take a look at the AWS Health Dashboard.

165
07:54.420 --> 07:56.060
Again, I have a shortcut to it.

166
07:56.060 --> 07:58.620
If you don't, you can just search for it.

167
07:58.620 --> 08:01.580
Now there's not really a whole lot to say about this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

167
07:58.620 --> 08:01.580
Now there's not really a whole lot to say about this

168
08:01.580 --> 08:03.820
because this again is automated

169
08:03.820 --> 08:06.700
and any events will show up right here,

170
08:06.700 --> 08:09.940
but what events are we talking about?

171
08:09.940 --> 08:14.260
Well, let's jump over to the AWS documentation real quick

172
08:14.260 --> 08:15.980
and take a look.

173
08:15.980 --> 08:20.420
So here in the AWS Site-to-Site VPN User Guide,

174
08:20.420 --> 08:23.820
we see the information of the two event types

175
08:23.820 --> 08:27.100
that are going to be displayed by AWS Health.

176
08:27.100 --> 08:32.060
First, we have the tunnel endpoint replacement notification.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

176
08:27.100 --> 08:32.060
First, we have the tunnel endpoint replacement notification.

177
08:32.060 --> 08:34.140
This event is going to be triggered

178
08:34.140 --> 08:39.140
if one or both of the VPN tunnel endpoints are replaced.

179
08:39.140 --> 08:43.220
So a different device comes online

180
08:43.220 --> 08:45.780
configuring the end of your tunnel.

181
08:45.780 --> 08:50.180
The other notification is the single tunnel VPN notification.

182
08:50.180 --> 08:51.860
As we've seen throughout the course,

183
08:51.860 --> 08:54.500
and we'll see again in just a few minutes,

184
08:54.500 --> 08:59.100
an AWS VPN actually consists of two tunnels,

185
08:59.100 --> 09:01.380
both of which should be up for this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

185
08:59.100 --> 09:01.380
both of which should be up for this

186
09:01.380 --> 09:03.340
to be considered functional.

187
09:03.340 --> 09:05.540
If only one tunnel is up,

188
09:05.540 --> 09:09.260
then you'll get the single tunnel VPN notification

189
09:09.260 --> 09:11.340
under AWS Health.

190
09:11.340 --> 09:12.900
So these are the pieces of information

191
09:12.900 --> 09:17.540
that will be displayed under AWS Health events.

192
09:17.540 --> 09:19.900
So now let's go back over to the console

193
09:19.900 --> 09:23.220
and let's take a look at CloudWatch.

194
09:23.220 --> 09:25.700
So back here, let's go over here and go to CloudWatch.

195
09:25.700 --> 09:28.140
Once again, I have a shortcut

196
09:28.140 --> 09:30.700
or you can just search for it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

196
09:28.140 --> 09:30.700
or you can just search for it.

197
09:30.700 --> 09:33.020
Now when we first come here to CloudWatch,

198
09:33.020 --> 09:37.300
it's going to start with favorites and reasons.

199
09:37.300 --> 09:38.820
This of course can be very handy

200
09:38.820 --> 09:40.780
if you have favorites and reasons,

201
09:40.780 --> 09:42.380
but we don't at the moment.

202
09:42.380 --> 09:44.420
So what we're gonna do is we're gonna jump in

203
09:44.420 --> 09:47.460
and start by taking a look at alarms.

204
09:47.460 --> 09:50.020
But what we're gonna see as we go through here

205
09:50.020 --> 09:53.740
is between the alarms and the dashboards,

206
09:53.740 --> 09:56.500
CloudWatch is gonna give us a quick

207
09:56.500 --> 10:01.500
at a glance insight into what's going on with our tunnels.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

207
09:56.500 --> 10:01.500
at a glance insight into what's going on with our tunnels.

208
10:01.500 --> 10:05.860
If we come down here to alarms, all alarms,

209
10:05.860 --> 10:08.460
we'll see that we currently don't have any.

210
10:08.460 --> 10:12.220
Now, before we can just jump in and start creating alarms,

211
10:12.220 --> 10:15.420
we probably want somewhere to send an alert

212
10:15.420 --> 10:18.940
or notification when the alarm's been triggered.

213
10:18.940 --> 10:20.660
Now, you certainly don't have to,

214
10:20.660 --> 10:22.780
but it's a very common thing to do.

215
10:22.780 --> 10:26.700
So that being the case, let's build that into our design.

216
10:26.700 --> 10:30.380
So for this one, we need to go to SNS.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

216
10:26.700 --> 10:30.380
So for this one, we need to go to SNS.

217
10:30.380 --> 10:33.420
So what we can do is we can just go up here to services,

218
10:33.420 --> 10:36.260
go to simple notification service,

219
10:36.260 --> 10:38.580
and then over here in our pop-out menu,

220
10:38.580 --> 10:40.860
let's go to our dashboard.

221
10:40.860 --> 10:45.620
So at the moment, we have zero topics and one subscription.

222
10:45.620 --> 10:47.860
Now, the reason I have one subscription

223
10:47.860 --> 10:50.620
is I did set one up during testing

224
10:50.620 --> 10:54.500
and it's to a non-valid email address.

225
10:54.500 --> 10:56.980
And it's really sort of interesting.

226
10:56.980 --> 11:00.140
AWS won't let you delete a subscription
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

226
10:56.980 --> 11:00.140
AWS won't let you delete a subscription

227
11:00.140 --> 11:02.060
unless you can verify it.

228
11:02.060 --> 11:04.900
So since it's not a good email address,

229
11:04.900 --> 11:08.140
I can't delete it for 48 hours.

230
11:08.140 --> 11:10.540
So it's sort of stuck there, but that's okay.

231
11:10.540 --> 11:11.980
We'll just make a new one.

232
11:11.980 --> 11:15.220
So what we wanna do is actually come over here to topics.

233
11:15.220 --> 11:17.180
We'll create a topic.

234
11:17.180 --> 11:18.780
Now, if you wanna send an email,

235
11:18.780 --> 11:20.340
and again, there's a lot of different ways

236
11:20.340 --> 11:21.940
we can configure these,

237
11:21.940 --> 11:23.980
but we're gonna do standard

238
11:23.980 --> 11:27.300
so that we can configure an email event very easily.

239
11:27.300 --> 11:30.100
For the name, we're gonna call this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

239
11:27.300 --> 11:30.100
For the name, we're gonna call this

240
11:30.100 --> 11:35.100
VPNSNS, we'll scroll down, and we'll hit create topic.

241
11:35.100 --> 11:38.300
Now, what we see here at the bottom

242
11:38.300 --> 11:41.820
is it's currently saying we have no subscriptions.

243
11:41.820 --> 11:44.940
So what we wanna do is create a subscription.

244
11:44.940 --> 11:48.220
We wanna make sure that the topic ARN is configured.

245
11:48.220 --> 11:51.060
And of course, we only have the one we just created.

246
11:51.060 --> 11:53.140
So it'll be correct.

247
11:53.140 --> 11:57.580
For the protocol, this is where we wanna choose email.

248
11:57.580 --> 11:59.820
So we'll simply choose email,

249
11:59.820 --> 12:02.460
and then tell her where to send the email.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

249
11:59.820 --> 12:02.460
and then tell her where to send the email.

250
12:02.460 --> 12:05.300
We'll do admin@company.com.

251
12:05.300 --> 12:07.460
We'll hit create subscription.

252
12:07.460 --> 12:09.900
Tells us that it was created successfully.

253
12:09.900 --> 12:12.220
So now let's go back to topics.

254
12:12.220 --> 12:14.820
We'll click on our VPNSNS,

255
12:14.820 --> 12:16.620
and we see down at the bottom

256
12:16.620 --> 12:20.180
that it does in fact have a subscription tied to it now.

257
12:20.180 --> 12:22.660
Of course, it says pending confirmation.

258
12:22.660 --> 12:24.260
So it's not gonna really send the email,

259
12:24.260 --> 12:25.660
which of course it can't because

260
12:25.660 --> 12:27.500
that's not a valid email address.

261
12:27.500 --> 12:29.500
But for the purposes of our testing,

262
12:29.500 --> 12:31.340
this will work fine.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

262
12:29.500 --> 12:31.340
this will work fine.

263
12:31.340 --> 12:32.340
So now that we have this,

264
12:32.340 --> 12:35.340
let's go back to the CloudWatch dashboard.

265
12:35.340 --> 12:39.020
We'll click on alarms, all alarms,

266
12:39.020 --> 12:41.340
and we're gonna create an alarm.

267
12:41.340 --> 12:43.540
Here we're gonna choose our metric.

268
12:43.540 --> 12:45.820
We're gonna choose VPN.

269
12:45.820 --> 12:49.220
We're gonna choose across all VPN tunnels,

270
12:49.220 --> 12:52.460
and we're gonna choose the tunnel state.

271
12:52.460 --> 12:55.180
Now as you can see from our chart up at the top,

272
12:55.180 --> 12:57.980
my tunnels have not been very stable lately.

273
12:57.980 --> 12:58.980
This is of course,

274
12:58.980 --> 13:00.900
because I've been setting everything up
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

274
12:58.980 --> 13:00.900
because I've been setting everything up

275
13:00.900 --> 13:02.580
for this demonstration.

276
13:02.580 --> 13:04.460
Right now though, we can see that both tunnels

277
13:04.460 --> 13:09.140
are currently up because the current unit is one.

278
13:09.140 --> 13:12.380
We'll see more how that works in just a few minutes.

279
13:12.380 --> 13:13.660
But now that we've selected that,

280
13:13.660 --> 13:16.220
let's go ahead and hit select metric.

281
13:16.220 --> 13:18.620
And a few things we wanna change here.

282
13:18.620 --> 13:21.580
First, we don't wanna wait five minutes.

283
13:21.580 --> 13:24.540
So we're just gonna change this to 30 seconds.

284
13:24.540 --> 13:26.620
Then we'll scroll down here,

285
13:26.620 --> 13:30.580
and we'll say to let us know if the threshold
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

285
13:26.620 --> 13:30.580
and we'll say to let us know if the threshold

286
13:30.580 --> 13:34.060
is less than one.

287
13:34.060 --> 13:36.500
Once that's configured, we'll hit next.

288
13:36.500 --> 13:39.700
This is where we wanna choose that SNS.

289
13:39.700 --> 13:42.860
Now as I mentioned earlier, this is optional.

290
13:42.860 --> 13:45.700
We could remove this data block right here

291
13:45.700 --> 13:48.320
and not send a notification at all.

292
13:48.320 --> 13:51.220
But again, we want to at least pretend

293
13:51.220 --> 13:54.740
that our email is going to be sent, even though it's not.

294
13:54.740 --> 13:56.820
We'll get to see this alarm trigger,

295
13:56.820 --> 13:59.060
but it's not gonna actually send the email.

296
13:59.060 --> 14:00.900
So what we wanna do is select an existing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

296
13:59.060 --> 14:00.900
So what we wanna do is select an existing

297
14:00.900 --> 14:03.140
because we already created it.

298
14:03.140 --> 14:06.980
Click here and choose our VPN SNS.

299
14:06.980 --> 14:09.660
Notice that it already pulled in the email address

300
14:09.660 --> 14:12.780
from that SNS object.

301
14:12.780 --> 14:14.420
Everything else here should be okay.

302
14:14.420 --> 14:16.780
Of course, you could choose other actions here

303
14:16.780 --> 14:18.340
if you wanted to.

304
14:18.340 --> 14:19.900
We'll hit next.

305
14:19.900 --> 14:23.220
We then have to name the alarm itself.

306
14:23.220 --> 14:26.100
I'm just gonna call this VPN down.

307
14:26.100 --> 14:29.500
You could of course call it VPN status or something like that,

308
14:29.500 --> 14:31.780
but this is gonna trigger when it goes down.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

308
14:29.500 --> 14:31.780
but this is gonna trigger when it goes down.

309
14:31.780 --> 14:33.940
So that's why I'm gonna name it this way.

310
14:33.940 --> 14:35.660
We'll go ahead and hit next.

311
14:35.660 --> 14:38.780
We'll review everything here to make sure it's correct.

312
14:38.780 --> 14:40.580
Notice, and it's a little hard to see,

313
14:40.580 --> 14:45.580
but right now, the blue line and the dotted red line

314
14:45.580 --> 14:47.500
are the same.

315
14:47.500 --> 14:50.220
But if you look up here, it's saying the alarm will trigger

316
14:50.220 --> 14:53.580
when the blue line goes below the red line.

317
14:53.580 --> 14:55.180
Well, right now they're the same.

318
14:55.180 --> 14:56.980
So it's not below.

319
14:56.980 --> 15:00.340
Scrolling down, everything here appears correct
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

319
14:56.980 --> 15:00.340
Scrolling down, everything here appears correct

320
15:00.340 --> 15:01.700
as we intended.

321
15:01.700 --> 15:03.980
So let's hit create alarm.

322
15:03.980 --> 15:05.620
Now we are getting two messages here.

323
15:05.620 --> 15:08.460
One, that it successfully created the alarm.

324
15:08.460 --> 15:10.140
And the other one is telling us

325
15:10.140 --> 15:13.420
that some of the subscriptions are pending confirmation.

326
15:13.420 --> 15:16.020
So it's not gonna actually send the message

327
15:16.020 --> 15:18.060
until the subscription is confirmed,

328
15:18.060 --> 15:19.900
which of course it's not going to be

329
15:19.900 --> 15:22.380
because it's not a valid email address.

330
15:22.380 --> 15:23.220
But that's okay.

331
15:23.220 --> 15:25.260
We're just gonna close these for now.

332
15:25.260 --> 15:27.860
And we're gonna give this just a few minutes

333
15:27.860 --> 15:31.420
to collect information, because right now the state says
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

333
15:27.860 --> 15:31.420
to collect information, because right now the state says

334
15:31.420 --> 15:35.940
insufficient data, and we actually want the state to be okay.

335
15:35.940 --> 15:37.780
So that took right around 30 seconds,

336
15:37.780 --> 15:38.980
which is what would be expected

337
15:38.980 --> 15:41.100
because that's what we set the interval to,

338
15:41.100 --> 15:43.380
and our state went to okay.

339
15:43.380 --> 15:46.020
So of course, you know what we're gonna do next.

340
15:46.020 --> 15:48.940
We're gonna take down one of the tunnels.

341
15:48.940 --> 15:52.780
So here on router one, under interface tunnel one,

342
15:52.780 --> 15:55.020
we will simply do a shut.

343
15:55.020 --> 15:58.060
Now we'll wait a few minutes for the dashboard

344
15:58.060 --> 16:00.340
to realize that one of the tunnels down.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

344
15:58.060 --> 16:00.340
to realize that one of the tunnels down.

345
16:00.340 --> 16:02.100
So let's switch back.

346
16:02.100 --> 16:05.220
So now after about 30 more seconds,

347
16:05.220 --> 16:08.540
we see that now this is in alarm.

348
16:08.540 --> 16:11.540
And if we click on VPN down here,

349
16:11.540 --> 16:14.880
we can actually get more information on this.

350
16:14.880 --> 16:16.940
So we can see that it is in alarm.

351
16:16.940 --> 16:20.620
It gives us the graph of when it dropped below one.

352
16:20.620 --> 16:24.060
So this gives us some good information about the alarm.

353
16:24.060 --> 16:27.940
So that takes care of the automated notifications

354
16:27.940 --> 16:29.260
and monitoring.

355
16:29.260 --> 16:33.140
Next, let's take a look at some of those manual choices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

355
16:29.260 --> 16:33.140
Next, let's take a look at some of those manual choices.