Why You Need a Cloud Native and AI-Driven Network

0:00 missed and now miss juniper the whole

0:02 philosophy of

0:04 user experience being the new uptime

0:07 came from customers such as you you are

0:09 the folks who have guided us

0:11 who've helped build this company and

0:13 always say this company and the ai

0:16 driven enterprises juniper is all about

0:19 being built by you

0:22 for you

0:23 what does that mean and i'm very i'm for

0:25 those of you who know me i'm very very

0:27 clear

0:28 in my philosophy what does that mean

0:30 number one

0:31 we are on a mission

0:34 to unleash the network for the next

0:35 decade

0:36 you all

0:38 are request your humble support to be on

0:41 this journey with me no i'm not going to

0:43 give you any coding exercises right now

0:46 but i'm definitely going to be coming to

0:47 you for guidance

0:49 because the second part about our

0:51 philosophy as we drive user experience

0:54 is very simply when you look at us when

0:57 you look at my team when you look at

0:59 sudhir tom sunani sanjoy jacob even our

1:02 ceo rami even our cio for us we want to

1:06 be a part of extended engineering team

1:09 that's the way it works now

1:12 as i set the stage for user experience

1:16 what is extremely critical

1:19 is as you drive user experience as you

1:22 drive a level of assurance which is

1:24 unheard of in the industry

1:26 you cannot just do it on parts of the

1:28 network you could start with wi-fi

1:31 extend to wired go to sd-wan and to the

1:34 cloud you have to be able to look at

1:36 everything across the network which is

1:39 what we refer to as client to cloud

1:44 there's a key reason when i speak about

1:46 user experience and i speak about client

1:48 to crowd i bring up and that came from

1:51 one of our customers who's actually

1:52 sitting right here today and he's going

1:54 to share some of his experiences

1:56 they said sujai it is fine when you

1:59 speak about user experience let's say

2:01 where's leslie i always oh let's again

2:04 she's on email while i'm speaking can

2:05 you guys believe it

2:07 anyway

2:08 okay

2:10 let's see if she has a problem while

2:12 she's trying to connect to the network

2:14 she can call network i.t and they can

2:16 try to do something about it

2:18 but then as that erstwhile company once

2:20 told me three years back branno maybe

2:23 four years back

2:24 so jay a user can complain

2:27 but a robot

2:29 when it fails

2:31 it doesn't complain

2:32 it stops working

2:34 as that robot stops working

2:37 10 other robots around it stopped

2:38 working too

2:40 and in less than five minutes

2:42 you've just taken down a distribution

2:44 center and probably impacted 25 to 50

2:46 million dollars of business

2:49 this is the business why assurance

2:51 becomes so critical client to cloud

2:54 fully assured

2:55 but as you start embarking on this

2:58 journey for client to cloud

3:00 there are two things which become

3:02 extremely critical

3:05 and i mean it

3:06 number one it's all about a cloud native

3:09 architecture i know everybody in this

3:11 room is like okay man here he go again

3:13 yet another cloud native architecture

3:15 but let's just speak about very simple

3:18 principles

3:19 we were the first ones in 2015 2016

3:22 brock friday sitting right there he said

3:24 sujay over my dead body will you write

3:27 monolithic code architectures again what

3:30 are those architectures by the way he's

3:32 the one who came out with that in 2004

3:34 because he was the co-founder of

3:35 airspace too

3:36 but ignoring that what was those

3:38 architectures monolithic architecture

3:40 put on a controller and then brad when

3:42 crack hap sorry brian when crack

3:44 happened you couldn't do much about it

3:46 you had to upgrade that whole code on

3:48 the controller a micro services based

3:50 architecture which we introduced was

3:52 very simply you disaggregate all the

3:55 functions

3:56 into many task workers and they all are

3:59 working one is association one is

4:01 authentication one is dhcp one is

4:03 location one is guest

4:05 you start looking at these and as they

4:07 start working if they have a problem

4:11 you just change that part of the

4:13 function out

4:14 you patch it up you're done your service

4:16 mic does not get impacted

4:20 that was the first most important thing

4:22 about a cloud native architecture

4:25 just a raise of hands if i can how many

4:28 of you remember

4:29 crack k-r-a-c-k

4:32 okay

4:34 keep your hands raised

4:36 if you were able to remediate that issue

4:38 in a week

4:40 so you fixed it in a week any raise of

4:42 hands where it took you months to

4:44 remediate the crack issues across your

4:45 network

4:47 and you're not the only ones they're

4:48 many it's okay i'm not gonna call out

4:50 who you work for but now you're on the

4:53 bright side of miss juniper so you're

4:55 fine but if you look at the crack issue

4:58 when that happened

4:59 we have customers

5:01 who were trying to remediate crack

5:03 not for weeks not for months but for

5:06 years

5:07 the miss juniper universe of crack

5:11 was remediated in less than eight hours

5:15 globally

5:16 welcome to the cloud native architecture

5:19 the second thing which i always speak

5:20 about and many of you know this

5:23 we say christmas comes to miss juniper

5:26 every wednesday

5:28 because guess what happens every

5:29 wednesday

5:30 there's a production push on the cloud

5:33 this is a cloud native architecture

5:38 the second part

5:39 is

5:40 to deliver on that client to cloud that

5:42 assurance that maniacal assurance beyond

5:44 cloud native you also need a

5:47 well-stocked ai toolkit

5:49 it's extremely critical but there are

5:52 certain things i just want to make sure

5:54 we understand

5:56 to be able to leverage ai i mean there's

5:58 a lot of ai washing in the industry

6:01 we frankly feel honored that we have the

6:03 partnership with customers and prospects

6:04 such as yourself and are guided well by

6:06 industry analysts who keep us honest on

6:09 what's happening but this is one key

6:11 difference which is very important

6:14 ai for us was built from the ground up

6:17 if you think about a tesla

6:19 it was built from the ground up where is

6:21 sudhir

6:22 sudhir

6:23 just recently converted to a tesla after

6:26 five years of convincing him

6:28 but

6:29 if you think about it it was built taran

6:31 from the ground up to be an eevee okay

6:34 you cannot there are many amazing cars

6:37 whether you are a toyota honda benz bmw

6:40 you break your pick you cannot put an

6:42 ipad on these cars and call it an ev

6:46 it has to be built from the ground up so

6:48 when that ai toolkit is talked

6:51 bob friday built the architecture from

6:53 the ground up to be ai driven

6:57 now

6:58 as we started looking at this we

7:00 introduced the first

7:03 network assistant to the industry

7:07 marvis

7:09 how many of you heard about marvis if i

7:11 can just get a raise of hands

7:13 wow that's pretty cool maybe after the

7:15 session we'll talk and i will give you

7:18 the science that went behind the naming

7:20 of marvis

7:22 some of you may know it already but as

7:24 you start looking at marvis the key part

7:26 why we did this

7:28 was if you speak to bob friday

7:31 to explain to him what is ai in a

7:33 sentence he will say

7:36 i train the machine

7:38 to think like a human being

7:41 i train the machine

7:42 to sit down with network i.t and huddle

7:46 together to solve a problem that's

7:48 marvis

7:50 when you start talking to marvis more

7:51 and more

7:53 you can ask very simple things i mean

7:55 many of us have had these you know

7:57 issues happen in a network we all huddle

7:59 together there's a conference call we

8:01 suddenly find out that we don't even

8:03 know where the problem is we don't know

8:04 what's the blast vector we don't know

8:06 who's impacted

8:08 simple questions difficult answers

8:10 call up markers bring marvis bring it in

8:12 and say hey how's my network doing

8:15 you can ask walk up to marvis and say

8:17 hey

8:18 taka is complaining in japan what's

8:21 going on with his issue simply said

8:24 marvis comes and says

8:25 having a roaming issue

8:27 great

8:28 now

8:29 this is something by the way we i know

8:32 we had some servicenow folks

8:34 in the audience and they were moved up

8:36 thank you so much hi sanjeev

8:38 so if you think about it this is

8:39 something which we learned from

8:41 servicenow is where i say company built

8:44 based on the feedback we get from

8:46 customers

8:47 they had this program and please allow

8:49 me to say it

8:50 about program called race to zero

8:53 and this was how do you maniacally

8:55 reduce the trouble tickets from over a

8:58 hundred per month to they wanted zero i

9:00 was a startup i said yes i can do it

9:02 we're down to at least two or three so

9:04 that's not bad but fundamentally they

9:06 weren't the ones who said train marvis

9:09 that every morning all i want to say is

9:11 how many unhappy users are there in your

9:13 network you know exactly and you start

9:15 getting proactive right you start

9:17 getting proactive and trying to address

9:19 these things so if you think about

9:20 marvis it was literally bringing it as

9:23 bringing ai as an interface where you

9:26 have

9:26 a digital concert sitting next to you

9:29 helping you with what's going on we're

9:31 not going to talk about all the back-end

9:32 stuff it does i'll leave that for sudhir

9:34 when he comes for his demos

9:36 but now

9:38 people ask and say ai really is your ai

9:42 real ai

9:43 and i say two simple things

9:45 number one

9:48 when you christian have an issue on your

9:50 wireless network

9:52 or a wired network or an access network

9:54 or now sd van

9:56 when you call juniper

9:59 customer support

10:01 the first person

10:03 who takes care of that call

10:06 is marvis

10:09 this is a religion

10:11 in our organization

10:13 and if marvis is not able to answer if

10:15 it's able to answer the question

10:16 fantastic if marvis is not able to

10:19 answer the question here is another huge

10:21 change which we have done in our

10:23 organization

10:24 the data science team

10:26 is co-located with the customer success

10:29 team

10:30 so what happens now marvis is not able

10:33 to answer the question it gets escalated

10:35 to customer success the customer success

10:38 person sits with the data science team

10:40 and as the customer success person is

10:42 remediating the problem the data

10:44 scientist is modeling that problem back

10:48 into marvels

10:49 this is ai driven support i know this

10:51 slide may become a bit difficult to

10:54 understand sometimes but this is the way

10:56 we track the efficacy of marvis

10:59 fundamentally in very simple terms

11:01 many of you have seen the growth of

11:03 juniper mist i mean ramya ceo just spoke

11:05 about enterprise being our largest

11:07 vertical in q1 within juniper

11:10 but think about it

11:11 our number of network devices under the

11:14 miss cloud

11:16 have gone up not a hundred times not a

11:19 thousand times not a ten thousand times

11:22 way beyond that

11:24 but here's the best part

11:26 number of customer success engineers

11:29 less than 10 compared to two years back

11:32 this is ai driven support so when i hear

11:35 about hey you know i was just here and

11:38 another company came in which is orange

11:39 and color another company came in which

11:41 has this blue thing in their slides

11:43 they said the same thing

11:45 and i just say okay why don't you go and

11:46 ask them

11:47 how much do they use their own ai engine

11:51 to troubleshoot their problems

11:53 then we'll have a discussion so very

11:55 simply and i'm totally totally totally

11:57 out of time

11:58 but here's something which i wanted to

12:00 say

12:00 i started this discussion with client to

12:02 cloud

12:04 i spoke about things you probably

12:05 already know cloud native ai driven

12:09 but here is

12:10 the most important part

12:13 i am on a mission

12:15 my team is on a mission

12:17 our ceo is on a mission our cio supports

12:20 us on that mission and many of you in

12:22 this room i know who have been our

12:24 customer supporters on this mission

12:26 but this mission is about a journey

12:29 to unleash the network for the next

12:31 decade

12:33 whether it's wi-fi shyt we need to start

12:36 looking at sd-wan yes wi-fi wired that's

12:38 old news now we need to start looking at

12:40 that but as we go over this journey

12:44 i

12:44 really humbly request you all

12:48 to be a part of this journey

12:50 because guess what

12:52 you know

12:53 maybe after 20 30 40 years when you're

12:55 in hawaii having a drink and you're

12:57 retired

12:58 don't you want to leave the legacy that

13:00 you assured the network for the next

13:01 decade because let me tell you people

13:04 say ah that's not for me

13:08 that is for you

13:10 we are the people who run the network

13:12 we are the ones who make these business

13:14 outcomes happen

13:16 and to get this reliability and the

13:18 agility of outlook getting the business

13:20 services

13:21 in production

13:23 we need to think about the network for

13:25 the next decade so with that i humbly

13:28 request you to partner with us on this

13:30 journey

13:37 you