CCNP Enterprise 350 -401 ENCOR - Cisco CCNP Enterprise - day 1/3 - Master Class
Hello, everyone, thanks for joining subscribing my YouTube channel. Today, we are going to learn about Scanbuy Encore Enterprise School. This is one of the school paper and there are two benefits.
First of all, if you are looking for your CNP certification, so this paper is must you have to pass this paper and then you can go and use any of the elective paper. I'm going to explain this in a few minutes so you will understand the new certification track related to this. And that's the benefit. No. One, the benefit. Number two is now school has removed CCI written.
So if you are looking for CCI in Enterprise, you have to pass. This can be Incoll. To of us, it is very important if you are looking for professional level certification is very important and this is a number one if you are looking for CCI certification.
This is, again, very important and this is the state's number one. So please continue to complete this video and gain the knowledge related to Scanbuy. Encore. So what is this libbers, Ill-considered, Slavin's that is covering architecture, virtualization, infrastructure, network assurance, security and automation? Actually, this level is quite robust. And in this training course, what they try to do that I have covered each and every single topic in greater detail. So, for example, if we are talking about the architecture, so I have covered architecture related to the campus area network, then architecture related to to design and the industry.
One small piece of software defined access as well, Kyra, as you'll find in detail and whatever topics that you are seeing here in the list, each and every topic point by point I have covered in this curriculum, then virtualization also has been covered in detail. Even I have gone beyond these slivers and then I have added virtualization that is core for reinvaded networking or for being raped. So that things also I have added in these sections that infrastructure.
So if you go and check these interest levels, you'll find that the core of this picture itself is the infrastructure module. So in this module, you'll find that you have to know about the layer to technology layer through technology, wireless and then IP services. And this is actually one of the lengthiest modules we have in this particular curriculum.
This is really important where you are learning to layer through wireless and IP services so that that will again add the tools inside your core fundamental of the network and technology. Then we have the network assurance. Is that that you have to configure the basic troubleshooting and monitoring and then finally we have the security topic again, the security topic is as it is that we have in the in the old scampers when they can see. So you have to know about the acoustic pop.
Some of the wireless security covers, some of the upcoming security as well as well. And then finally, we have 15 percent workers for automation, which we should know and understand the python. Jason Epis, how the apps are working, Cisco, EMC scripts, then finally the puppet Ansible and solve this track. So in general, you will find this libres is quite robust and even challenging as well, because not only we have to know the. Existing or reconsider all your stuff as well, but you have to understand that new stuff sells well and Cisco has figured this thing in the mind that maybe tomorrow we have to migrate your van to the Strand or your land to a city is the axis or next year. So all these things has taken care in this country, enterprise, Slovis, either Scanbuy curriculum or its SCCA curriculum.
IT and everything has been taken care of in Cisco has formed this out after this Slovis. They have taken care of this thing in the mind that the Iraqis that you are supporting the existing network or the Iraqis that you are doing that migration or the Americans that you are supporting. The brand new upgraded Estevan Oreste is the network. I am going to walk you through the city and enterprise signification and we will see that a what are the changes that Cisco is putting are from this coming from inside the certification? There is complete a strategic change you can see inside this enterprise. We know that Cisco certifications are always valuable, you will get much salary hike means compared to other certifications in the market, you will get much more a reputation and they are highly valuable certifications.
We have complete sort of certification means different type of certification, like associate professional and expert. And as for your certification, even you can negotiate with the companies in terms of salary and other other aspects. So they ask for your certification. They will think that you have the right knowledge, skills. You you are very skilled in the I.T., your skill, I.T. professional, and then you can go and ask
for the salary because you are able to take the responsibility. So that's the reason the company will be there. You can see that 99 percent of our organization, you signification to make hiring decision because these certifications are structured in a way that they are going to test your different level of skills.
So, for example, if you see the all the certification is that we have means now it's 28 eight fab. So now this is become old. And now and the next slide, I'll show you the new that will be available from 24th of February.
So this is like a vacation. You can see most of the people at the moment at this point of time, they have we have associate level certification, professional label, then the expert level and different type of technologies are there. So, for example, routing, switching, security service provider, wireless, others. Now, this has been change in this.
So now you can see that certification has been simplified, but on the other hand, that will become much more focused. So now this corner, that is the associate level certification, this is the basic for all the professionals. And then again, you can go for the expert, but this can become basic for the professional level.
Now, this is the and they will serve the purpose for enterprise service provider, datacenter collaboration and security. And Ballylee, you may have the expert level certifications in that particular domain. Now, again, Cisco has a certification as well, and that is the docs of their track is different. But you can see that 95 percent or maybe 90 percent of things relates with Associates, ICANN, then the professional and an expert. Now, here you can see that.
If you can use this, yeah, so you know that in SCCA, you initially means before this program you have the theory and the lab and that is hour our very different type of exam. And there you you must need really high percentages. For example, 75 to 80 percent of marks in all the sections to pass your ccra I comparative to CCI exam is also really highly skilled type of things that they are going to ask you. That means they are going to check your death knowledge inside that particular room in here. You can see that you have the enterprise core security because it for the core collaboration data center core.
So things has been grouped strategically inside a different type of core. So you have one foundation, you have one core, and then you can choose the. Exploitable or the more precisely, the specialist level. So you have the core, first of all, you can see that we have the scanner and then you have Kurr in these.
So, for example, five domain. So you need core knowledge and then you can go and get your copy and then you can go and get the. Okay. So from your code now you can see that you don't have written an exam, although your core after your core you can go and write your lab exam. OK, the choose between two lovebirds inside this enterprise school and ordered to leave exam, if I go back, you can see that do you have enterprise infrastructure? You have enterprise wireless. Right, to like that, you have to choose now if you're in the security, choose your concentration means you're doing OK or choose your concentration and then take the lab like that.
You have all the tracks. You can see that from the slide, it's very much clear and what to do at what point of time, again, here you can see that we have enterprise security service provider for everything. You have charism and you can go and have your contingencies and be has to prepare when you score and when one is the concentration or one is the focus, for example. And then you can go and write the some. So, for example, for Enterprize, you have enterprize love related to violence and the CCRA infrastructure where you have different things like as you and Asgeir, those new things are also agat.
All right. So now you can see that to means again today it's 27 or 28. So now we are in this signification track to 24th of February. We have Enterprize goal that is mandatory and then you can choose one. So they advance routing or Esteban or Enterprize, wireless or wireless implement like that.
We can choose this irrigations summary that is good has try to reduce the number of amount of certificates and it has been focused and grouped will logically inside a single single technology or inside a single single group. And it's still an even they have removed the CCI rating as well. So you can do your CCN picture and you can write Yoki, you can do your CCN picture, and then you can go and focus on any of the specialized exam, like, say, for example, Estevan or Enterprize designer Chikara. All right, so this is the track everyone has it on, everyone gains, everyone maintains their certification, everyone awarded badges. So obviously by the end of the year, once you complete the track, you can see that you have different type of badges, you have a specialist, then you have Cynthiana, that you have CNP and then you have CCI. So you can start your journey and then you can slowly move your career from a specialist to the expert.
And that's the goal. And once you complete your Kenay up to CCRA in one particular domain, then you can move to the other domain. OK, so there is a wealth of knowledge available and if you want to gain it, if you want to become expert, go to one technology completed and then move to the technology. That will be the strategy. This particular course is focused on this ENP enterprise, and once we have one of the core topic, then we'll go and check the Estevan. Alternatively, we can go and check the other stuff as well, like a design advance routing, enterprise automation, but at this point of time we can check Scanbuy Enterprise and the Estevan because the combination of Enterprise and Estevan will give you wreckage at the moment as given is very hard in the market.
It's very demanding. And if we combine like these two good, we given to market value will be a very good order. Quarter skills you need. We'll see that we have complete slovis. You can go and check. So now this was the past where you have you should ask and other jobs now in the future.
Now present. I call this this is the present. So you have Enterprize Colebatch. You have a specialist. Then you have the advanced routing batch, a wireless badges for individual examples, so you will get that exam certificate, but better that will go and club sources can be enterprize with any of the four, correct? All right, so now here again, you can see the summary that we have back, if you want to see be enterprize, you do the cover and you can do the advance or you can do the cover, you can do wireless.
Any of these two, you can do the cover and then you can do the design. And here you can see that this the NBA Enterprise, Enterprise, Enterprise. OK, and just try to tell that how it is equivalent to Frisian Brinsden Wirelesses. And give me the support if you want. Good news is the A.P., you do the core and then design and you are there. DP, if you want to reduce campaign violence and they do all these three and then you see in being violent, if you want to do this and be do these two and the US enduring, if you want to be continuously when you do call and issue and then you are the second is man.
All right. So this was the certification changes. And I hope that you understand that. What type of changes, what certifications we have to obtain our new Scanbuy. And from there we can go and prepare for Skyy as well. Hi, everyone, welcome to Camp Enterprise Core, cause this course is divided into six different parts.
You can see that striking from architecture, virtualization, infra network, excellent security and automation will find the detail of these topics and the subtopics in this particular link. I hope this course will be informative and it will gain new knowledge from this course. Thank you. Let start with 1.0, that is the architecture and what are the things we have to learn in this, we
need to understand the design principle, the resiliency, the scalability, the redundancy device, deployment options, etc.. So here you can see that we have a long list actually starting from one point one, then one or two, three, and then four, five, six, seven, up to one point one to one or seven. You have now here you can see that inside one door you have to understand the first design principle, one point five, you have to understand about DNA or the access design principle. One point five, you have this skewers both in wired and wireless and then one point seven is taken from the old curriculum.
Even into this one point six, there is a cure that is also taken from the old curriculum. So it's again, the mix of the old Kenbi plus whatever new technologies we have and why we have some type of mix that I will explain to you in the upcoming maybe third or maybe for Slagle Earnestine there. Now let's cover point number one. Door one a up to be.
And what is the agenda for that? So you have to understand the enterprise network design, such as the year two three, what is fabric, fabric, capacity, planning, etc, and then the viability and redundancy, like offering a redundancy protocol. And so we'll see that because all of this is my only point, one door to one, A and B, but we have multiple videos to cover this topic because again, this is a big topic. So let's try to understand this one point one and let's try to figure out that what type of design principle we have and why we have to.
Once we understand that, why we are using this, that will solve our purpose. We should understand that why why we need this. Now, let's see this. When transport technologies and this like you can see that the evolution of the architecture and design principle. So only network, we have the fix and the bridge network maybe 35 years back when Cisco has invented routers and again the switches and they try to connect different type of network.
We can see that actually if we go from a back behind that, say, if we go and check the ARPANET and their principal and the DCP discovery and their evolution, you can see that when the protocol first invented and then again when Cisco came into the picture and they have revolutionized the complete network domain or the industry. So here you can see that from 1990 when we have the AMICA protocol and the business support model for I.T. and at that time we have various protocols like Lesbia BGP. Those are the commercial protocol.
They are still in some of the places you can see that we are using IP with this. Again, the organizational methodology even we are using primarily still some places we are losing Ramlila or extra extra to private sector, but now we are moving. So if you see the journey from 1990 to 2000 where we have mission critical network, where we are supporting realtime traffic, we don't have even one minute of downtime, et cetera, et cetera, means it's a highly critical network. And if we are dealing those topologies, how we are going to build those capabilities.
And again, if you move from 20 years, 2000 to 2020, now, you can see that the evolution of Estienne and companies, they are sky deployment DTN either is Esteban or LAN or campus automation or DNA, etc.. Up to now, is this a complete movement? Again, this is the movement of network. So if you know the architecture principle that what we are using in mid 90s are 2000 and now what we are going to use in 2020, actually each and everything has covered in this score.
So we can start from our fundamental DGP USP for other routing protocols and then we can move and check that whatever protocol has been used inside Esteban or the unit. So, for example, if you ask me if we are using here in the existing network and OMB anti-lock, we can using this to list, we can use Indian, etc.. OK, so we should have the clear picture. And if you're doing the migration from existing network to the upcoming network, so if you know your existing network, if you know the upcoming technology and network, then, well, you can do the migration and a number of issues will be there. OK, so this will be your summary slide.
What we are moving, what we have at this point of time and what we need in the upcoming network cycle. I mean, when we are referencing the signal, when we are migrating the signal and what type of challenges we have here, you can see. That's again, the. A small thing means everywhere in all the places you will find the same type of challenges, the challenges are not as small. But in terms of gathering, the facts are so common.
So what are the common factors you want to improve or what are the challenges you have that you don't want inside the restaurant or in the next network? So we know that the scalability is one of the biggest issue means you can't scale. So you have this clear ability. And we can discuss a lot, a lot and talk about this gullibility now when we are talking about scalability, the scalability, not only in terms of your network or how many devices you have, but a scalability in terms of routing capability, your IP capability, or even you can go and do some sort of deployment over the cloud to scalability. Plus, cloud integration means you can mix these things and you can think all in a single book then how you are going to integrate with Iot Internet of Things, because again, this is a big, huge topic. And we know that Cisco DNA testing network architecture is the access they have the capability to understand.
Even Cisco is making the Iot related products as well. So we have the chance that we can integrate Iot devices inside the Enterprise Network. Then what is the faster it changes? What is the next? Can you do the automation programming to have a single pane of glass from where you are managing all the devices? Yeah. So if I go and summarize these topics again, I told you that all this problem and the complexity that we have, they are common at this point of time.
And if you see the existing network is still we are using the access distribution and core routing list or ultrareligious. So we have some sort of C and then B and then B and then the network, they are divided into multiple routing and sensors are forwarding a virtual routing, forwarding and sensors, etc., etc. So you can go and support the network level virtualization as well. So what I will do.
Let me quickly here that what is the common issue we have in the existing network? I will not add cost at the moment to leave this, we can discuss cost. Helicon is this cost aspect because you may find that cost is also one of the driver to make or to do the difference in the network. The what we want, we want the scalability.
And this is scalability. We want in routing and we want in IP sake as well. And that's why we have the NBN was as new as developments like our nearest neighbour.
Second thing, what we want as a network that we want integrated security. So at the moment I bring up my controllers and all blended airplane etc, I should have one solid, common, unified, secular fabric. So that's why this is also very, very important. Thirdly, what we want we want that the overall cloud integration means now it is to again, this is this have some cost effect to companies.
They don't want to go to the central hub or data center and then they want to go and use either be either directly direct access or direc cloud access, rather, from branch. They want to do local breakout, local breakout, and then they don't want to use the resources host to host it over Internet or the cloud. So that's again, important and cloud integration. Now, these things you have apart from that one very important thing, I will agree that it is possible in the existing network as well in the existing solution is a big effort.
That is the segmentation. So once you do the segmentation, the scalability, security, cloud integration and segmentation, apart from that, you want other features, like you should have full visibility, then you want monitoring. You want a single pane of glass from where you want to do all this monitoring. You want solid reporting, you want easy way to do the double shooting, cetera, et cetera. So these are the things and these are the terms we have.
And we should consider these things inside the architecture principle. So let's just drop her and in the next section, let's continue the same architecture principle and I'll add some more valuable points in the upcoming sessions. Let us continue our discussion and understand more that what we have discussed earlier, so we have discussed that, yes, we have different technology means in terms of evolution of network. So we can check the 1990 network in 2000 and 2010 and then 2020 and coming forward.
So what is the major change and how we are going to reduce the complexity in terms of design deployment that actually it's very interesting. So here you can see that with the evolution of Impalas and when the ambulance network start gaining the popularity at that point of time, you can see that how you can visualize the network. So here in the diagram, you can clearly see that you have hub network and then you have a Spok. Somehow this design, this is giving some sort of idea that in upcoming iteration we are going to use some sort of a spine and leave structure sometimes, which is referred as a class fabric.
So you have your leave, you have your spine, all the leaves, they are connected with the spines. And these Alief, they are not connected to each other. And that's the thing we are achieving now, again, when you're achieving this type of quality or this type of network where you have all the devices by default, we are one hop away at that point of time. How are you able to do the segmentation for segmentation? We have already we are if virtual routing and forwarding and this is now from the U.S. So we are using
the we are a technology. And later on you will come to know that in when we are using VPN, that is nothing. But we are only in a name or the term going to be used as a weapon. We logically or technically also they are also we are virtual routing forwarding. So now the complexity will increase when you have multiple devices, when you have different type of traffic and you mark those traffic as different type of reroof. How you're going to do the routing or maybe overlay routing, et cetera, et cetera.
This is a still we are using in the existing network. It is possible, but the thing is that the we need to rate actually the more line, of course, more number of configuration you need. OK, but still we are using and you can see that we have multiple technologies like we are in flight or ambulance VPN because BGP is a nice protocol which is supporting all sort of, I guess, family related to Yariv and even other adult families as well. Now, again, in this design principle, how we are going to deploy the network, do I have a single program design? Do I have dual provider design? Again, if you go from single to do well, obviously the cost will increase.
The viability and the redundancy feature will increase by any means. The cost will increase or you are going to use the overlay network design. And this is actually the future. Cisco has started their overlay.
Network design means technically we are telling this independent of transport. So I really have two or three or four different type of Espy's. You don't care. You are creating tunnel on top of that. That's the only tunnel. And Cisco has introduced their intelligent design where they are using D.M. VPN.
As a Overlake Daniel. OK, but again, we are using I and the MVP and all so many companies, they are using it, but again, you have to write a number of codes are more number of lendee configuration. So Cisco is filling all the existing network that from Ivan. You you can migrate to Cisco, Estevan.
OK, why? Because, again, you can see the cones that increase design, complexity, additional technology needed for lower commodity transport. So there are some extra overhead that is there, although the design and the solution is neat and clean and beautiful. But still, you have some extra things that you can do in the Esteban and the automation and the solution that is there in the event.
So that's why this movement is there are let me quickly show you some of the slides related to a single carrier and double carrier. Will, curious where you can see your network may look like that. So although you have different link, but you have a single carrier, suppose if one of the carrier, because I believe you have a single carrier, but suppose if that carrier will go down at that time you have loss and that's why it is listed here in the can on that bond to a single carrier for future velocity does not protect against ampules cloud failure with a single provider. Obviously if that cloud will go down, I don't have resiliency or ability that I can go where the other carrier, obviously this thing I have in their area. But again, the complexity there, the cost is there.
So you can compare here the pros and cons. The con is that increased bandwidth being for bandwidth, price increase, overall design, complexity maybe reduced to common denominator between the carriers is overall you're increasing the resiliency, but cost wise, it is issue now concerning this diagram and this diagram. And again, considering the overlay network design, if we have this out of all these three. So that will be the exact solution we are looking for. And that's why we are looking forward for Esteban's solution. Again, we can see this all these things inside Section one, dark fiber.
So let me assure you that when dark for so we have wondered for and wondered why we are we can access those design issues and how Estevan and their DNA oreste is combined together and they are going to solve these issues that also we can discuss in the upcoming sections. We are still in the basic situation where we are learning what type of existing terminologies we have and then what are the new things we are going to learn in the new school curriculum. So let's discuss the Iran overlay technologies inside this. We have a layer to overlay, and it really means this overlay technology or terminology is not new.
Actually, this is coming from the old technologies. Now you'll see in the Esteban and the DNA and maybe in A.S.A., in the data center topic, that this overlay terms will come up again and again and again. So now we have something called Underlay that is your physical infrastructure. And then on top of that, you're creating virtual dynamic tunnels.
This can be layer to this can be layer three layer to contain examples here. You can see that you may have led to the leak protocol, a two DPI version, three you may have or TV or Weixel. And that's the very popular item we have Reglan. And this will learn more and more in the upcoming session. When we are talking about layer three overlays, we have I think we have GRB, we have a list as well.
Now, this list I'm going to cover in the next slide, but at least you can understand that you are extending layer to fabric or you're extending layer to fabric or to extend the fabric. Either you need layer two or you need layer three, I guess families or Agnes's, et cetera. Now, what is there in the Strand or what is there in DNA is that we are going to automate this process.
So you need not to worry. So, for example, in Estevan to create the IP centennials like now when we are creating the DNA will be in phase the nose here. We are not to worry to create the ABC channel at the moment to bring up the fabric automatically those channels will get formed. You know, when we are talking about the tunneling technology, a normal IP packet on an old packet, we have the payload and the IP header injury. Again, you have the payload and the IP are there and then you have extra overhead for Gary.
Rest in peace accord, either you're using, I think, security in transport or general mode in transport mode, and you have less overhead in terms of package but internal mode that is much more secure. And by default, most of the technology they are using the IPCA tunnel mode where you have the inner and outer. So at that point of time, obviously your header sites will increase, but the level of security will also get increase.
I'm not going deep inside the APC and how I Piecyk is working in the area and how that is working. It's just the only we have just started the course. And as for the agenda, whenever these things will come and it will tell in the exam or in the curriculum that we have to go deep, dive in this particular topic, I'll go deeper in this that I will do the back of capturers, will analyse the package, et, etc. But at the moment we are just getting familiarity with these technologies. All already these technologies are existing and what new we are going to get in the new enterprise sector or in the enterprise.
And now, for example, let's look at the idea separation protocol or antivirus ablation protocol. Now, if you understand less so, for example, I already told you that you have a Plan B as well as field solution. You have three things. You have Lannes or Estienne for lan as the end for one, and then you have a stand for data center as well as data center. Now, for land, the common term is the access, obviously, I'm talking only in terms of Cisco. So in this case, we have DNA.
Is the name by the axis, is the technology in when we have. It's given an indication that we have application application centric infrastructure is here. Now, if you go and learn all this technology, you will find that everywhere you have some sort of Leavis fine type of a structure to suppose if I have to find.
And beliefs like this. So, again, I'll take one more leave so I can show you the redundancy. So all in all, these lives will go and connect with this fine and leave and leave, they will never connect these finds. They are working as a loud Reflektor means these spines.
They have their database. So now these beliefs, whatever endpoints or whatever devices are connected with these leaf's. In the end, they act as ignored or as devices or these devices, whatever network, whatever increase Macarius, IP address, etc, etc., whatever they have.
They are sharing with their spine or their parent. Now, this is fine and DNA is mapping system or mapping the resolver. Now, this is fine and Isiah's is finally this finally. And that means ESEA knowing that Stephen Loosley, if you analyze, you'll find that there's something called Reichsmark controller who has all the database for all the routing information. He's the controller, the controlling device, and he's working as a robot reflected in ESEA.
Also, these finds are working as a real conflict. And suppose if you're not doing all this technology, so there are channels that you can you will get confused that what I am telling that next year and the year, Martin, A.S.A. is fine in DNA. It's it's actually the control playing device. Sometimes we are telling this as a control plane, Rothko's maybe border Outr, et cetera. So, again, we'll see later on.
But what at this point of time, you can mark our understand is that you have some common authority. He has a command authority, just like DNS server, where they have all the all the information, all the database information, you think that you have the database information. Now, these endpoints, they have offloaded with the information. So they don't have entire topology information. They know their local system or local endpoints.
Local employees, once they have their local increase, they are teaching or they are telling the common authority that this local system I have this local IP Mac, I have you play the store at you. Likewise, he will also tell, OK, you play the store with you. And when this guy wants to communicate with this guy and he don't know how to reach it, he will send the query back to him. I want to reach there and he will reply in a way that now they can communicate directly. OK, so these are working as a proxy on behalf of and most of the technology, most of the history and technology. We have the same analogy.
All right, so now we can understand all the different technology, if you see, for example, if in no other nonsensical technology as well, for example, in a six hour deal or any other solution there also you'll find the same type of thing is happening, OK? And then once you start comparing this technology, it will become easier to learn and understand because again, every we some new thing will come and it's almost impossible to learn and memorize all those things. So better you start comparing different technology and then we can learn it easily. Insects and wonder to one A, we need to discuss about quality of service as well. Now we are going to see their design aspect of this because we should understand the core quality of service things and then we should understand the skill and quality of service things. Now, the basic principle will not change. So how we are going to do the classification marking, policing, shipping, scheduling, etc., those
things will not change. So what are the things are going to change the way that we are going to implement to the devices and those things are going to be changed in the years to end. So I have already uploaded complete calls as to when they can go and check how we are going to use this as this queue is actually inside the student now at this point of time. Let's discuss.
Let's focus that. What are the basic components of quality of service? So here you can see that we have three important thing, classification and marking. You classify the traffic you market.
We have polishing, polishing and something like you have some sort of a strict rule with the traffic. So if certain limit your threshold will breach, it will start dropping the packet. And then we have this scheduling, including arguing and dropping means you want to give some sort of buffer in case if we have congestion means you don't want to directly drop the traffic, but you have some sort of buffer for that. Now, here on top, you can see that you have different type of class of traffic. So I have this class of traffic.
Then I have a real class of traffic, telepresence and data. Now, for all these type of traffic, they have a different requirement. So some of the traffic Europeanists, some of the traffic artistically with some of the traffic that we have, a league high latency, some can tolerate the delay, et cetera, et cetera. So now you can see in the bottom that if there was traffic, you have Europea priority, but latency should be less than one particular segment. Otherwise, this was a will altogether. There is no meaning for that means whenever we are sending device back packet.
You think that particularistic with 150 milliseconds, if it is not delivered between that time, it will get lost. Something like that. I can say that Jeter should be less than 30 millisecond loss, should be less than one percent. Now, why we are discussing this, because the first fundamental of QE is classification and marking.
So you can do the classification of the graphic and you are understanding that what is the last latency and the requirement for different type of traffic, including that what type of protocol they are supporting. So you can say this is why we're doing telepresence. They have Europea means they are very much a Real-Time Extra Real-Time traffic. But you want trustworthiness as well. You want security as well.
And that's why you have the business traffic or you have business data that is using GCP protocol. And I where you can see in the bottom that you have mission-critical application, maybe SFP, maybe any type of database, et cetera, et cetera. Now, the bottom line that you're are seeing here, that is actually important when you are going to create that U.S. policy, in other words, when you are going to create the policy, if you breach certain well, as a specified in the bottom, then that policy can take some decision to then include changing the route, et cetera, et cetera.
And that's it. And this particular feature has been optimized in the U.N. solution. So here it is very much coding this. We have to understand the protocol means the device should understand the protocol. According to that, you have to write the code and then it will take action. Correct.
So first thing is that to do the classification of traffic, there are several method in key words that you can go and deployed here. You can see one of the example for that. So you're creating the policy map. Then you have glass wires because this is high priority traffic.
You are giving priority for wires, you are giving priority for video. Then you have the critical data. You are giving 15 percent for that. You are using some random detect DCP based again, there are different type of drop.
Make it a methodology means you are going to use a random early detection. You are going to use DILG up so those methods you can use again, you can see the data Benwood percent percentage is 90 percent. This is again, just an example. You're a scavenger graphic.
You are giving less bandwidth percentage network critical. You are giving this three percent is actually Trijicon. So bottom line is that that you need to write the code for all the devices inside your enterprise infrastructure and then you have to configure it manually one by one by one. See, suppose if you have same type of hardware at thousand places, you have to write this code, or at least you have to do the computers to all those thousand devices rather than if you do this thing where the Estevan, it's like you have once you created the template, you can push from the management plan to all the devices. Right.
And here you can see that how this cute look like. So the important thing here is that you need to do the classification and then you have to map with the Q So classification or forwarding glasses to Q mapping. That will be the step number one again and say this is for Lolek and secure our Class-Based record where you really are adding the words with you, etc..
Now we have a nice example here that is clearly, clearly telling us that traffic shaping so without yapping how it looked like was he applied the shipping then? How it looked like? Was he applying the shipping then? And this typically delayed this traffic is moving most and preventing the unnecessary job. If it is for lesser, it will chop up and quickly drop the traffic again. We have another example.
This, of course, this is your configuration. And once you apply it, obviously you have one bandwidth pipe. And generally we are applying this policy to the one person interface. I suppose if you have 300 MBBS, a speaker.
Correct. So you have one gig interface, but as for your equipment, you have 300 MEPA. So you know how you are going to use that classes and how you're going to allocate that 300 and the speed with priority, with some scheduling with some agreed to the device that you can see here in the example. And again, we are meeting this as a child, jayasekara under inside the parent. Inside the parent.
We have the shipping. We have some overlimit. Yeah, so this is the way that we can go and apply the hug and we have a nice example here, that you have your Enterprize devices, you have your Impalas devices, which means in inbound, whatever policy you want to apply.
And these examples that you're seeing here is the standard one that Cisco is recommending the if you want to learn more about us, you can go and check the U.S. Cisco Skills Deployment guides. And there are tons of tons of information we have over Cisco. You are all that we can go and get it. But this is something like a standard format to all the companies that have this type of existing network where they want to apply you.
Now, you can say that you kind of like you through the ISP side to or to work you as you have to. There used to be said the same thing you want to match to your site as well. And I say, if you go and check the E and F configurations for outbound policy against the outworn policies and you think your Class-Based plus base to work at work, you Remarque realtime traffic Class-Based where you actually get together and then you can go and check the service provider in the bottom. So what is there in the outbound. What is there in the inbound. So obviously my outbound will be the inbound for the service provider.
Correct. So we are going to manage this enterprise network and then according to our viewers, we can cancel the service provider and we can tell them, OK, you can map these distance Giuseppi these this policy from your side as well. As long as we have the common agreement, the common configuration things will be better in this design. A strategy that you are seeing here. There is a major change in the years to end now to reduce the cost for these two men and pay less because, you know, there can be less. Cost is too much.
What customers are doing, instead of using 100 MBP assemblies, they are using one gig Internet. So you will see even here also, I mean, upcoming sections. I will give you some slight design related things, sort the stuff that you can compare later on in your study as well, that what is existing, the design means what is existing hybrid design and then assembles.
And then when we are moving to the next generation is different type of network, what design possibilities we have. And then you can argue that Bookmobiles has this advantage and then it has described Xhaka, but now it is the big enterprise. They are using the Internet connection primarily. They can do both. They are using one gig and maybe two big Internet interfaces, and then they are load balancing the traffic. All right, so if you have got your I.P. I.Q., is conservation on top, you can see that we have normal
Beckert without us. Obviously we know that in IP higer we have use type of service. Now, if you're curious, with Guarisco, you have your inner ear, you have your got there, you have your outrigger, and then you can see this gilliss propagating from inside to outside. Likewise, if you have a basic encapsulation where we have inherited an outrigger in case of a hypothetical mode. So you can see that we are retaining the Kulis marking. All right, so these are examples related to us, and just like this is, again, a very much high level, but we should understand and as per our curriculum, for example, this is something that we should know these variations.
We should know that what we have in the existing and what we are going to have in the upcoming has given us. All right. So let's stop here. And decision is quite interesting because we are going to discuss about the rent and the land architecture designs and actually we have a strike at the schools and we are talking about design principle. What is interesting, what is going to become or what is the demand or DNA, etc., as far as the scope
of the can be examined now? Thing is, they're so I have one dedicated slide, I'll come after two to three minutes to this particular blank slide. Let me quickly walk you through two, three slides so we know that there is demand. The drastic demand in the networking means there are so many things that try to connect with the network means we have Iot, we have so many hand-held devices. We we are managing a different type of mobility features and mobility devices. We are managing everything maybe from the cloud so we can integrate with the cloud.
We have different different applications. We want to do the visibility for the applications to manage all these devices. The complexity will be very high. If you directly go into the cloud, your service will increase. So you should provide security even from the inside or outside.
So great circa. So the bottom line is this, that you have demand because you have to integrate different type of devices inside your networking infrastructure and then you add to that complexity will increase. Managing manageability will be the challenge, in that case, your security, or you may have the holes in the security. So everything should be integrated, should be put out. And what will be the solution to the solution is that instead of using the monolithic, instead of using the existing way to manage the I.T. infrastructure, you can check the Estienne software defined type
of architecture. Now, what Estienne will provide, at least at this point of time, is that you can focus on application. So is the true capability of his client is that now we can build the policy based infrastructure? Now what does it mean? So. For that reason, I have this particular slide, so I'm going to draw one very nice difference in between all the technologies that we have, all the technology related to this event.
And this will give you a nice idea about different type of complexity that we have in existing and where we are moving, actually. So, for example, we have land. We have then and we know that we have a center as well.
Now for all these devices, if we are connecting land, obviously you have land. If you have multiple ASV, you can go and connect with the land and then somewhere you may have your data center. This is something like your existing network where you have spread branches and you're using existing methodologies to manage your I.T. infrastructure.
Now, what is the different? When I am going to use Estienne approach in to manage the land RANAAN Data Center for Land, we have something called in there or is the axis. And we know that we have Cisco up there last year and we're data center, we have A.S.A. now, we know at this point of time that all these infrastructure, all this component of the I.T. infrastructure, they have control plan, they have a management plan, they have data plan, they have a policy plan somewhere. You will find the plane as well.
So who is the control plane for the in the management flow management plan for the energy airplane and policy plan, etc.. So now this thing you have to study and you can compare different different technologies to the control plane is again, you will see that list is the protocol. Who is managing the current call or who is providing the control plane information. But for that you have border routers.
Paretsky When we have whimp overlay management protocol, who's managing this? But the controller is smart. ESEA We know that we have a spine and leaf architecture and we know that we have the coop protocol. Maybe you have Impey and BTP protocol to manage the control information right where the word management plan for management plan. We have a dynamic center that is nothing but a big epic enterprise model. This A.S.A., they are also using EPIK, but this epic and this epic is a hundred percent different. This is for your DNA.
Aldeen at this point of time we can do this and this is therefore you take us into manageability then to testimony in this too. And you have Ibanez in the dataplan. You are going to use the Bigland. You have each Peralta's.
Whereas when you get a plane is nothing but a basic tenants, but we are using we are seeing the Cisco Systems, Crowder's or whatever this is, you have Leakiness final structure. So your life will be your Nexus devices here in this final. Those are the Nexus devices that we can check the reference to. But to squeeze using I reglan something you can tell that intelligently, Excelon, because they are they have this one for for having the contact information as well. Maybe policy information has some extra bits are there in that we learn from it in the policy plan, who is the policy player in the ice? We are integrating with DNA. So ICE is the policy plan for us to when you're real smart, is the policy plan and policy a guinea pig is the policy plan because there you can go and build the policy and then you're pushing two different types of devices.
This is the reference and we can see and you can think that, oh my God, my existing network is better than than what these stuff. So now you have to learn, understand DNA is different. And if you are doing your data center study, you have to learn ACIM and network programming as well. OK, so this is the story we have for all the upcoming technology. At least you will learn the. Castellan, and the DNA, plastic things I haven't shown you will be bringing in the picture, I will check later on in their DNA section.
Again, this is the DNA framework that we are constantly, constantly learning the network, and then you can take the decision, we'll discuss more and more about this framework in the upcoming session. But at least you can see that you can manage the entire network from the cloud management. Then you have this full automation capability. You have analytic engine inside your DNA is the big newsiest box that the boxes are. You have full visibility because these devices, these are Catalyst's devices that we are using or the hardware that we are using for DNA.
They are very smart, intelligent, and they have programming chip inside that. And you could actually tell them to feature before default will be there. So we have the full visualization for all those events and things that are happening with Hilferty and that we can visualize the network. Then we have the full programming facilities, either for the physical or the virtual infrastructure. Everything is integrated inside the security. We know that we have the policy plan that is nothing but ice from where we can push the policy through their DNA devices.
So the principles are open, programmable API and obviously we can do everything that whatever we can do with this. I agree. We can do with the API as well. Now, here you can see in the diagram that you have the the NSA and directs your management plan. You have S.V. access. And so DNA is a term and it's the access is the technology actually that is used.
Then you have the hardware as a catalyst 90 and then you have the security features that you have in encrypted traffic analytics. It's a big thing and is a big thing as the rand is also big because now whatever we have a strategy, we have to rethink our strategy all. We have to redo the strategy.
And if you compare or if we try to compare that what we have done in the existing network and what we are doing here in the DNA or and so actually there's not much scope of comparison. We should think that is the new thing we are learning and then we can start from scratch. All right.
So let's just drop her. And the next election is interesting. That is our core existing technology that I'm going to discuss in campus design and other topics are also there decision.
We are going to discuss about the technology that we know, the multilayer campus design and obviously in the upcoming election, we'll discuss more about the upcoming technologies. So we know that we have our core layer distribution layer and access layer. And again, I have slides for all this layer so we can go and discuss there. But everything is going on connected to the core and then restricting decision that how to sing and where to send disseminated out, etc..
So here you can see the score is connected with the devices again at the distribution layer. And then you have the access layer where we have the one where you have the Internet means you may have hybrid technology where you are connecting with the Internet and you're connecting with your data center as well. Again, this is one of the campus design.
And maybe at this point of time, 80 to 90 percent of campus design is like this one, because now we are slowly moving to the DNA of the adoption grid at this point of time for DNA. Oreste access is not that huge, but we are expecting that it is coming one to two years or maybe two to three years healthy. Much more adoption for us. The access. OK, so this is the core that you have, the core distribution and access layer.
And again, if you split this guy and find that you should have the structure, modularity and hierarchy, that you have the core access and core distribution and access layer, and where we are going to connect your computer circuits, where you are going to connect with your Internet, where you are going to connect your IP telephony services, etc.. OK, so let's quickly check that all these layers, what they're offering, what exactly they are looking for. So here you can see the diagram left and right, you have the boxes and how it looks like. So you have the core distribution distribution and then you have access, access like that. You can think we have dedicated sunlight for all these layers.
So Baker will check all these lights one by one. So what's the use of the access layer or access layer is doing? You have L2, L3 features, you can go and use the higher public security, QSI with Oscar, etc. You can go and you Skewness, you have IGB plus fonderie. You have broadcast on Maitake.
Ask Bondy's as well if you want. We can suppress those requests, but you can go and use various Calpol for optimization method for loop prevention. If you are using a methodology, we are using a methodology you can use routing protocol like easier BWP, etc. If we are doing hireable and redundancy, we can use BGP that will in this case are using Cisco proprietory for calculation group protocol. Generally we are using a less appealing aggregation control protocol. If you have if you are using your Radio Flex lead, etc..
OK, so this is something where you have your trust. Bondie really want to protect your network. Obviously you want to protect your network to all the places, but this is the place where the endpoint will come and connect.
So at this point of time, at this particular level, you want higher security, you want segmentation, you want Mexican people, you frager's, speaker card, et cetera. Right now, next you have the distribution layer. Distribution layer is there. This is the second type on backbone or second level of backbone we have where you want to apply some more mature policy and higher mobility features. So that's why we have the capability load balancing.
Yes, we can do the aggregation of all the access at the level of distribution means you have less number of devices that is there in the distribution label. And compared to the access there, even in access layer you can use to Cassidys or tweak as it is, which is in distribution layer, you can use Hawkie or maybe a six. Now Cisco is requesting everyone to use nine K model of switch so you can choose those recommended are the supported models in terms of hardware capability.
They can do that out some radiation, faster convergence and it is RPG gloopy that we have the protection for first pregnancy protocol. It is RPG, LBB, BRP in upcoming session. So we'll discuss more in the upcoming session about that caller obviously is the core is the backbone you want, Hiyam, ability and the scalability for the Coulier. They have the they are the aggregator point for all the roads.
And again, if you go and refer this diagram, this particular diagram, you can understand that things are converging towards Squali. And then from Coulier, you can distribute those crowds to the other locations as well. Again, you can see in this diagram how it looks like so you have layer to access.
You may have rotary access, you may have virtual city. Etc., Then you have the distribution level, which is everything is coming to the core, and then it is going to one of the branch of the data center or other branches. So this is the network that we are very much familiar, and again, with respect to resign, you will find that there are variations that we need to consider.
Obviously, there is the evolution for the hardware, for all the devices. There is evolution or there is upgradation for the software, also for all these devices. So how much virtualization these devices are supporting? How much hardware? I think that difference means how much throughput as a customer or as a user I want from these infrastructure. So according to that, the hardware can be implemented and it's recommended that even if we have this network and you want to upgrade the switches in this network, you Cisco nine switches. So in the future, if we want to migrate to DNA, you have some sort of switch as we do the supporting DNA. That's the strategy now.
It is all the companies are using. So they are not ordering for the legacy or the old hardware ARANETA rather than they are going for the new hardware. So in future, if they want to migrate, they can use that strategy again. As for design perspective, you can see that you may have layer three distribution interconnection or you may have layer to distribution and interconnection means you want to stretch the boundary up to distribution layer.
So this. Regular wire, regular senior, those are elderly and this blue collar connection, their polling booths are a to go in and that's why is telling that what we want to you want to access. So obviously in the bottom, in the access which you have, the villans you want to interview, in the will and voting you have the obviously by the S2P will be running there. You have the it is your deal.
BP, you want some other channel, you have some people, you so all type of brilliance and you have some of the companies they are using leered to Bondi up to the distribution layer so there can see the difference. Let me you the difference. So you have literally this recolour link in between the distribution switches. They are using a routing protocol to forward the traffic. And that's true actually. If you see any of the upcoming network or any of the solution, you'll find that even for layer two carrier or even FFOLLIOTT also we are using routing.
So, I mean, for example, if you go and check Cisco, LCI, application centric infrastructure, where you have Lifan is fine. They are connected behind the scene, but they are using layer to type of routing. And strategy means megadoses also can doubt that you don't check. That's true that the routing is bigger than that we are doing in terms of switching for high level network or for a scalability reason. And that is again one of the design aspect.
We have to suppose if we have two different Fabrica stretch fabric, you don't want to extend the L2, although you can extend the L2 by routing is always preferred on top of the eight to 10. So for example, the L2 tunnel is not preferred over L3 internal highlight in the routing his preferred design rather than stretching the to this also supported model. This is not for the reason that we are talking that LTE supported model only supported. This is something that which is given the capability of say, for example, we assess virtual switching systems. So there are parallel enhancement in the network because if we have switches, if we connect, obviously you know that as per their priority and packages to choose who is the absolute switch, who is the second you switch it at all priority and everything.
Now, what we can do in this case that you don't want these triangles in the network, what do you want? You want a straight line. So you collapse these two switches inside one unit and then the bottom switch is also they can think. So this diagram will be like this.
Or maybe this diagram will be like this mistruth, which is they are connected back to back physically. They can be like this very logically. They will be like this. That's sort of like if you're using this type of technology and then that's the evolution you have.
If you see the data center evolution, you'll find that it started with six five zero zero. Then it moves to a Nexus seven, the Nexus nine, and then now Nexus nine case that started with normal. This type of network will move to, for example, VSS, then move to VPC, then move to lift the spine and then lift weights. Financier. OK, so evolution is there up to you, which network or which type of Ostrander network or design you are supporting, you will find this type of network as well, will find this type of network as well. Both are supporting an existing model we have at this point of time.
So you can have these devices in the same unit and these distribution devices. So you have. For example, one control and two data channel and these devices, they are working as easy, like multitasks, Internet, etc, means we're eliminating a two loop rather than you have a separate line in the network. All right, so decision is actually becoming Laimbeer. Let me stop here.
Next section will continue from here. Let us continue the previous section, and we have seen that we are hoping that we can use L3 distribution link or we can use LKA as a distribution link in between that, if we are using a tool capability, we have options that we can go and use virtual switching system where we want to reduce the number of Frangos in a network. Now here you can see the convergence time with respect to Iris Peevski or our previous tipplers, then the routing protocol like whispy of an ERP. And that's the thing that we are considering, that when we are using the routing protocols there, convergence is faster. They are not using the blocking interfaces.
Like if you are using a human interface, then Skype will run automatically and 50 percent of Lync will be unutilized. So those things are not there. That's why he always this routing design will be preferred with the seating design or eco design, how it will be looking like inside the DNA that we are going to discuss in the upcoming session. But if you see this diagram from this diagram, let me try to explain a few of the things.
So here you can see that you have Barder broken. So for example, Barbiere, then you have edge devices. Maybe they can do a switching and routing board. So you have these devices as well. Now, with the use of these devices and bless this apps that we are seeing here, that they are near to the end point. So now these rotors are now these is devices.
They are not learning the entire routing table intact, although not everything. But they are knowing that what is connected to them and then they are sending those information to Miles An are. So we have this resolver or we have the servers where they are pointed to or now they are sending all the information to the global routing deal like that.
You can think you have one DNS and their DNS having the information from where to where. I have to reach to those. All the information that the NSA has are having. Then you have the access point that you can see and then you have the WC that all the access point control information are all the access point, those are managed. We have the ability we are going to discuss this also. So we have the underlying architecture and we have the overlay architecture and infra.
And this engineering overlay in conjunction they are working for is the access. Here you can see that the IP challenge, new services, you have the mobility services, the scalability, flexible and programming infrastructure. Those are the things that you'll find is our DNA or is the access. We have the controller, we have the control pl