WEBVTT

00:00:00.080 --> 00:00:05.680
there's nothing more annoying for me and my staff than troubleshooting Wi-Fi

00:00:03.480 --> 00:00:10.519
issues so when Juniper Networks told us they wanted to sponsor a video featuring

00:00:07.879 --> 00:00:15.480
the solution to our problems how could we possibly res like how do I go wrong

00:00:13.000 --> 00:00:21.600
with that so they sent us over some of their ap43 Wi-Fi 6 access points and an

00:00:18.520 --> 00:00:24.119
ex 4400 switch claiming they've done it

00:00:21.600 --> 00:00:29.279
they' figured it out the future of networking and the hardware that's

00:00:26.800 --> 00:00:35.040
impressive but the real star of the show is mar Mar Vis the virtual Network

00:00:31.920 --> 00:00:37.320
assistant driven by missed AI Marvis

00:00:35.040 --> 00:00:40.920
combines machine learning and AI with a conversational interface that

00:00:38.800 --> 00:00:44.640
understands natural language queries this should save technicians hours of

00:00:43.200 --> 00:00:49.039
time that would otherwise be spent checking dashboards and using other

00:00:46.360 --> 00:00:54.920
troubleshooting tools certainly seems like a good idea but what I and probably

00:00:52.199 --> 00:01:02.199
all of you also want to know is how smart is Marvis smarter than me probably

00:01:00.079 --> 00:01:05.120
but we can't end the video here so we're going to have to try it

00:01:12.000 --> 00:01:21.280
anyway so we started by casually installing two of their ap43 wireless

00:01:18.320 --> 00:01:25.759
access points and these things are basically the bang inist I'm looking at

00:01:23.320 --> 00:01:30.759
the data sheet here it's like limited lifetime warranty got a humidity and

00:01:28.400 --> 00:01:37.000
pressure and temperature sensor built into it it's Wi-Fi 6 but not just that

00:01:33.720 --> 00:01:39.280
it's 4x4 with four spatial streams

00:01:37.000 --> 00:01:43.399
Dynamic packet capture automatic RF optimization high accuracy indoor

00:01:41.200 --> 00:01:48.280
location so it has Bluetooth on it so you can actually tell exactly where

00:01:45.520 --> 00:01:51.880
everything connected to it is it's crazy so once we were done installing a couple

00:01:50.000 --> 00:01:56.119
of these we set up our wireless network and added a floor plan which was

00:01:54.159 --> 00:02:00.560
surprisingly intuitive and easy to use given the ones that I have tried before

00:01:58.960 --> 00:02:04.640
and now we're just going to go ahead and pull up the management dashboard which

00:02:02.240 --> 00:02:08.399
you can see scales beautifully across my dual monitors maybe we'll just make it a

00:02:06.759 --> 00:02:13.319
little bit smaller there we go that's more like

00:02:09.800 --> 00:02:16.480
it there we go so this one has nobody

00:02:13.319 --> 00:02:19.160
connected to it cuz James isn't even

00:02:16.480 --> 00:02:22.280
here today and then this one right here has three look at that you wow you can

00:02:21.239 --> 00:02:29.560
actually like see whoa that is exactly where look

00:02:26.200 --> 00:02:31.640
that's exactly where plof is standing uh

00:02:29.560 --> 00:02:35.480
oh so coming back to the floor plan we got a bit of a problem one of our APS is

00:02:33.680 --> 00:02:41.680
flashing purple I click it wait oh is Jake not

00:02:39.680 --> 00:02:45.360
done breaking it yet he's supposed to break it so that we can see how to fix

00:02:43.440 --> 00:02:48.560
it it doesn't just like that's the problem that's the problem when you're

00:02:46.720 --> 00:02:55.680
trying to do a video about like oh troubleshooting is that like usually

00:02:51.640 --> 00:02:57.560
things work you know from juniper so you

00:02:55.680 --> 00:03:02.680
have to kind of come up with contrived ways to break it on your own there it is

00:03:00.640 --> 00:03:08.440
now it's broken thanks Jake it's broken

00:03:06.159 --> 00:03:13.519
now now I'm not going to give too many details about how we're hand wavy fixing

00:03:11.480 --> 00:03:18.799
this but I will say that this gave us a really solid clue as to where to look

00:03:16.280 --> 00:03:23.519
and what we needed to do was dig into our DNS server in this case that's the

00:03:21.120 --> 00:03:28.000
same box as our router and figure out well why the heck that access point

00:03:26.400 --> 00:03:33.519
isn't actually getting an internet connection and it turns out that the

00:03:30.080 --> 00:03:35.760
admin thanks Jake fat fingered a three

00:03:33.519 --> 00:03:39.360
where there should have been a two so now what will probably happen in a

00:03:37.280 --> 00:03:43.319
moment here is it's going to come back online let's try and use Marvis for this

00:03:41.840 --> 00:03:46.599
I can't figure out how to I can't figure out how to reset it it should be working

00:03:44.920 --> 00:03:50.760
now so let's see if Marvis can help me with it uh troubleshoot device James

00:03:49.319 --> 00:03:55.680
desk AP oh that is so cool look at that

00:03:53.879 --> 00:04:00.360
coverage heat map I like it now that we fixed the

00:03:58.200 --> 00:04:05.159
problem I mean we still can't connect to it because like we can't tell it to

00:04:02.560 --> 00:04:09.720
reboot itself and get new DHCP information because we're not connected

00:04:06.920 --> 00:04:17.280
to it but fortunately look at this it's all like oh no lus I have a problem I am

00:04:13.400 --> 00:04:18.840
blinking yellow six seven seven times

00:04:17.280 --> 00:04:23.040
then we're going to go consult the handy key in the software and find out what

00:04:20.519 --> 00:04:28.680
the devil that means oh look at that okay it still says no DNS response man

00:04:26.600 --> 00:04:31.840
that is like so perfectly helpful to find the problem we had I'm just going

00:04:30.440 --> 00:04:37.680
to go ahead and give it a quick unplug and replug it's funny how no matter how

00:04:34.720 --> 00:04:45.600
much AI we add that's still the way to fix so many problems did you try turning

00:04:40.880 --> 00:04:48.720
it off and turning it back on

00:04:45.600 --> 00:04:52.960
again let's give it a sec

00:04:48.720 --> 00:04:58.360
here wow red and orange and a bunch of

00:04:52.960 --> 00:05:01.960
it's got RGB it has RG B on an access

00:04:58.360 --> 00:05:05.400
point Juniper you madlads that's one

00:05:01.960 --> 00:05:08.160
challenge down but of course what I want

00:05:05.400 --> 00:05:12.000
to know is who's wasting network resources watching YouTube videos on

00:05:10.160 --> 00:05:16.840
their phones when they should be watching YouTube videos on their

00:05:14.840 --> 00:05:20.080
desktops I mean I don't actually care if they watch YouTube videos that's

00:05:18.039 --> 00:05:23.520
scripted into the video by the by the writer but I mean it's sort of part of

00:05:21.759 --> 00:05:28.639
our homework sometimes to watch YouTube videos but they should do it over a wire

00:05:26.240 --> 00:05:36.199
instead of taking up air bandwidth so I can say the site name is

00:05:34.039 --> 00:05:41.800
LMG uh can you tell me something you want to

00:05:37.639 --> 00:05:45.680
troubleshoot okay um let's go with uh

00:05:41.800 --> 00:05:50.039
okay he has a Galaxy A50 so I'm try

00:05:45.680 --> 00:05:52.160
searching for that hey there we go cool

00:05:50.039 --> 00:06:00.199
let's click some client insights wow all right yeah got a good solid

00:05:55.520 --> 00:06:02.000
connection speed here and wow you know

00:06:00.199 --> 00:06:06.919
I think my bigger concern is not actually your YouTube consumption here

00:06:03.960 --> 00:06:14.000
plof how on Earth have you managed to do 211 megabytes of Reddit in the

00:06:11.160 --> 00:06:20.759
last what what is this day who it's text plof that's my lunch

00:06:18.400 --> 00:06:23.520
break that's your lunch oh I guess there's video on

00:06:23.919 --> 00:06:29.199
Reddit now it's time to do our next challenge here and we're supposed to

00:06:27.680 --> 00:06:33.120
click Second Challenge so this is a desktop computer that's actually right

00:06:30.800 --> 00:06:39.479
on the other side of this window and we go in here and nothing is

00:06:35.840 --> 00:06:41.639
immediately out of the ordinary but oh

00:06:39.479 --> 00:06:48.160
connected time two seconds oh okay hold on client insights uhoh we've got 66

00:06:45.639 --> 00:06:51.080
total client events with 15 of them bad so this is one of those things where

00:06:49.680 --> 00:06:58.520
you're sitting at the help desk and someone's like oh I can't get on the Wi-Fi and you go well gee let me have a

00:06:55.800 --> 00:07:03.520
look at your device here real quick Karen

00:07:00.120 --> 00:07:06.240
and oh okay you got an authorization

00:07:03.520 --> 00:07:11.039
failure over and over and over again I think you might have forgotten your

00:07:07.960 --> 00:07:13.560
password so here's your password write

00:07:11.039 --> 00:07:17.639
it down but actually don't write it down cuz that's even

00:07:15.560 --> 00:07:21.280
dumber most of the time it's not this cut and dried though so you'll have

00:07:19.599 --> 00:07:25.319
things like a problem device that's constantly disconnecting or running into

00:07:23.199 --> 00:07:31.240
issues so that's where being able to sort by good client events neutral and

00:07:28.759 --> 00:07:35.199
bad ones is is really really useful and you can grabb tons of great information

00:07:33.080 --> 00:07:38.560
from the packet captures and Mist actually has this great Dynamic pcap

00:07:37.000 --> 00:07:42.680
feature that's a blessing to anyone who's sick of trying to replicate issues

00:07:40.560 --> 00:07:46.159
so it'll actually actively capture data when an error occurs and then store it

00:07:44.479 --> 00:07:50.759
in the cloud meaning that you've already got the logs and you can access them

00:07:48.120 --> 00:07:55.840
without having to go on site now let's head over to

00:07:52.639 --> 00:07:58.879
roaming oh there it is roaming oh cool

00:07:55.840 --> 00:08:02.080
okay so here's a common issue you can

00:07:58.879 --> 00:08:04.159
actually see the roaming data between

00:08:02.080 --> 00:08:08.599
your access points for that particular client so okay plof is usually at the

00:08:07.039 --> 00:08:14.840
Mac desk and then I don't know maybe he had a meeting with James or something and connected to his AP and then he's

00:08:11.759 --> 00:08:16.919
back on this one so you can sometimes

00:08:14.840 --> 00:08:22.120
get into situations where you've got someone who keeps swapping bands to 2.4

00:08:19.080 --> 00:08:24.039
GHz or they get terrible RSSI values

00:08:22.120 --> 00:08:27.560
from certain APS and that's all nicely visualized for you uh or if you have a

00:08:26.240 --> 00:08:32.240
device that keeps swapping back and forth from one AP to another which can

00:08:30.080 --> 00:08:36.279
kind of like a high latency feeling for them or it can cause issues during video

00:08:34.080 --> 00:08:41.200
calls something like this can really help you get to the bottom of something

00:08:38.080 --> 00:08:43.080
funky that's going on of course what we

00:08:41.200 --> 00:08:49.320
really want to know is can all of this save me or more accurately Jake time

00:08:46.920 --> 00:08:53.720
well RPS are hooked up to an ex 4400 switch which offers flow-based Telemetry

00:08:51.360 --> 00:08:58.120
power over Ethernet PE Plus+ and fast PoE micro segmentation and endtoend

00:08:55.920 --> 00:09:02.839
campus fabric for a ton of scalability so what this means for our next test is

00:09:00.440 --> 00:09:06.480
that all the extra Telemetry should be able to tell us exactly what's going

00:09:04.600 --> 00:09:09.480
wrong without us having to go take a look for our

00:09:10.640 --> 00:09:18.200
ourselves and what's supposed to be the problem with this one oh ha I could have

00:09:15.839 --> 00:09:23.519
figured that out if I had just actually clicked on the thing yes we have 22 bad

00:09:21.079 --> 00:09:27.120
DNS failures fantastic now a common mistake when

00:09:25.720 --> 00:09:31.480
setting up a new mobile device on a network is just entering the DNS

00:09:28.880 --> 00:09:35.440
credentials in correctly you might think you entered it correctly while you're

00:09:33.320 --> 00:09:41.519
just just following instructions famous last words but unfortunately you were

00:09:38.200 --> 00:09:43.600
wrong I I dream of the day when more it

00:09:41.519 --> 00:09:47.040
tasks can be handed off to someone less experienced and there's like me and

00:09:45.480 --> 00:09:51.320
there's zero worry about the network going down because of a rookie mistakes

00:09:49.079 --> 00:09:55.519
wrong permissions client can't connect Network's suddenly down so with Marvis

00:09:53.480 --> 00:09:58.920
and Juniper Networks the idea is that your team can leverage M AI to

00:09:57.120 --> 00:10:02.680
proactively notify and correct issues before you get a ticket enabling your

00:10:00.640 --> 00:10:06.600
technicians to look like Heroes so thanks Juniper for hooking us up and

00:10:04.600 --> 00:10:11.760
giving us an exclusive look at all of maris's newest features if you guys are

00:10:09.760 --> 00:10:15.000
an IT professional looking for an easier solution let us know in the comments and

00:10:13.480 --> 00:10:18.600
if you like this video make sure you check out our horrible server deployment

00:10:17.000 --> 00:10:22.399
from last year it'll definitely make you cringe your whole face will fall off

00:10:20.839 --> 00:10:26.839
from cringe it will go numb and then fall off