Service Level Expectations in Juniper Mist

0:00 let's compare simplifying operations

0:02 with missed Wi-Fi is finally predictable

0:05 reliable and measurable

0:08 set Monitor and enforce service levels

0:10 based on what's right for your users not

0:13 by some arbitrary vendor metrics track

0:16 thresholds to make sure service levels

0:18 are being met in real time and trending

0:21 in a positive direction contrast this to

0:23 the first generation Cloud providers

0:25 this is what we can see about a client

0:27 not much this is what we could see about

0:30 an AP again not much so with the release

0:33 of Meraki health I thought I would check

0:35 in and experience the future

0:38 let's take a look 72 percent failed

0:40 client connections and sub 10

0:42 milliseconds Network latency okay

0:46 let's look by client type that's odd it

0:49 knows what types of devices but it is

0:51 saying zero let's move on and go click

0:54 on this one client and oh no just an

0:57 event log again nothing actionable here

1:00 could you at least tell me a little bit

1:02 about the DHCP server

1:04 let's look at connections

1:06 this looks promising but what is this

1:09 really telling me

1:10 the number of connections succeeding at

1:13 this step

1:15 okay I guess you know the magnitude of

1:18 your issues now like I have a big DHCP

1:20 problem so it must be here

1:23 nope another event log

1:26 there must be something under this

1:27 single connection

1:29 nope another event log Last Hope latency

1:33 kinda interesting

1:35 but this is based on dscp tags so if

1:39 everything is tagged correctly then I

1:41 guess you would have some data but my

1:43 MacBook Air has been running 4K YouTube

1:45 video for the past two hours but I guess

1:48 that doesn't count so latency by AP and

1:51 latency by client

1:53 I guess that might be interesting also

1:55 but I was kind of hoping for actionable

1:59 this is a great example of Miss

2:01 Innovation and Wi-Fi assurance

2:04 missed SLE dashboard is showing you

2:06 exactly what your users are experiencing

2:09 not red yellow green