WEBVTT

1
00:00.000 --> 00:03.300
To assist us in reinforcing what we've learned in this skill,

2
00:03.300 --> 00:06.000
I've got a scenario just for you, and here it is.

3
00:06.000 --> 00:10.700
The customer had a tech configure and FQDN filtering rule

4
00:10.700 --> 00:15.300
to block HTTPS access to anything@vmware.com.

5
00:15.300 --> 00:18.500
So I won't say who that tech is, but unfortunately,

6
00:18.500 --> 00:22.300
even though they put that rule in clients on segments 10

7
00:22.300 --> 00:27.400
and segments 20 can still access that domain via HTTPS.

8
00:27.400 --> 00:28.600
And so here's what I'd like you to do.

9
00:28.600 --> 00:31.400
I'd like you to first of all think about what could be wrong
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.600 --> 00:31.400
I'd like you to first of all think about what could be wrong

10
00:31.400 --> 00:32.400
with the rule.

11
00:32.400 --> 00:34.300
For example, just off the top of my head,

12
00:34.300 --> 00:36.800
it could be things like the rule is not enabled

13
00:36.800 --> 00:41.100
or if the rule is configured, maybe it didn't get pushed out to NSX

14
00:41.100 --> 00:44.300
or perhaps something in the rule itself is not correct.

15
00:44.300 --> 00:47.600
So I like to think about, you know, all the things that could be wrong.

16
00:47.600 --> 00:50.800
And then I'd like you to further use the screenshots below this video

17
00:50.800 --> 00:53.700
as part of your troubleshooting and then answer the questions

18
00:53.700 --> 00:56.600
in addition to what could be wrong based on the screenshots.

19
00:56.600 --> 00:58.400
What do you think is wrong?

20
00:58.400 --> 01:01.800
And then once you identify what you think is wrong based on the screenshots,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:58.400 --> 01:01.800
And then once you identify what you think is wrong based on the screenshots,

21
01:01.800 --> 01:06.000
I'd like you to go ahead and also think about if that problem was corrected,

22
01:06.000 --> 01:10.700
what are two different ways that you could use to verify that that domain,

23
01:10.700 --> 01:14.400
anything@vmware.com being accessed via HTTPS,

24
01:14.400 --> 01:18.760
what are two different ways that we could verify that that domain is now being

25
01:18.760 --> 01:19.500
blocked.

26
01:19.500 --> 01:21.400
So then once you've had a few minutes to consider,

27
01:21.400 --> 01:24.100
you know, what could be wrong or what is wrong based on the screenshots

28
01:24.100 --> 01:27.000
and then also how you'd verify after correcting the problem

29
01:27.000 --> 01:28.300
that is now working.

30
01:28.300 --> 01:31.700
Join me in the next video and what we'll do together is compare notes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:28.300 --> 01:31.700
Join me in the next video and what we'll do together is compare notes

31
01:31.700 --> 01:34.300
regarding what we think could be wrong, what is wrong,

32
01:34.300 --> 01:37.100
and then also how to verify once we've corrected the problem

33
01:37.100 --> 01:39.200
that it's now working as expected.

34
01:39.200 --> 01:42.500
So have some fun with this scenario and I'll see you in the follow-up video

35
01:42.500 --> 01:43.700
when you are ready.

36
01:43.700 --> 01:52.920
[BLANK_AUDIO]