Pass Cisco ENCOR 350-401 Exam in First Attempt Easily

Architecture

1. CCNP Enterprise Certification

I'm going to walk you through the CCNP enterprise certification, and we'll see what the changes are that Cisco is putting into this coming fib. There is a complete strategy change within the certification that you can see inside the CCNP enterprise. We know that Cisco certifications are always valuable; you will get a much larger salary hike, which means that compared to other certifications in the market, you will get much more reputation, and they are highly valuable certifications. We have complete a sort of certification means different type of certification like associate. professional and expert, and as per your certification, even you can negotiate with the companies in terms of salary and other aspects; as per your certification, they will think that you have the right knowledge.

Skill. You are very skilled in the It. You're a skilled IT 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 pay you. You can see that 99% of organizations use certification to make hiring decisions because these certifications are structured in such a way that they are going to test your different levels of skills. So, for example, if you see the older certification stack that we have, that means now it's the 28th of Fab, so now this becomes old, and now in the next slide I will show you the new one that will be available on the 24th of Fab. So with this old certification, you can see most of the people at the moment.

At this point in time, we have associate-level certification, professional-level certification, and expert-level certification, and different types of technologies are there. So for example, in the areas of routing, switching, security service providers, and wireless, this has been changed 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 CCNA, which is the associate level certification, is the basic for all the professionals, and then again, you can go for the expert level, but CCNA becomes the basic for the professional level. Now, this CCNA will be useful for enterprise service providers, data centers, collaboration, and security, and you should have expert level certifications in those areas.

Now again, Cisco has other certifications as well, such as DevOps, and their tracks are different, but you can see that 95% or maybe 90% of things relate to associate CCNA, then professional, and then expert. Now, if you've done your CCI, you know that before this program, you have the theory and the lab, and that is an eight-hour, very difficult type of exam, and you must have a very high percentage, for example, a mark of 75 in all the sections, to pass your CCI. Now, compared to the CCNP exam, this is also a very skilled type of thing that they are going to ask you, meaning they are going to check your knowledge inside that particular domain.

Here you can see that you have the Enterprise Core, Security Core, Service Provider Core, Collaboration Core, and Data Center Core. So things have been grouped strategically inside different type of core. So you have one foundation, you have one core, and then you can choose the expert level or, more precisely, the specialist level. So you have the core. First of all, you can see that you have the CCNA and then you have core in these, say for example, five domains. So you need core knowledge, and then you can go and get your CCNP, and then you can go and get your CCI. So from your code now you can see that you don't have written and a lab exam, although your core after your course, you can go and write your lab exam. Okay? So choose between two lab exams inside this enterprise course. And what are two lab exams? If I go back, you can see that you have enterprise infrastructure. You have enterprise wireless, correct? So like that, you have to choose. Now if you're in the security area, choose your concentration, which means you do your core, 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 clear what to do at what point of time. Again, you can see that you have an enterprise security service provider for everything, you have the core exam, and you can go and have your CCNP.

That means CCNP has two people: one is the core and one is the concentration, or one is the focused exam, and then you can go and write the lab exam. So, for example, for Enterprise, you have Enterprise Labs related to wireless and the CCI infrastructure where you have different things like SDWAN and Sta. Those new things are also added. All right, so now you can see that today means again that today is the 27th or 28th. So now we are on this certification track. So 24 February we have Enterprise course, that is mandatory. and then you can choose one. There is advanced routing, SDWAN, and Enterprise Wireless wireless implementation. Like that, you can choose the certifications summary that Cisco has tried to reduce the number of amount of certificates and it has been focused and grouped well logically inside single single technology or inside single group.

And even they have removed the CCI notation as well. So you can do your CCNP code and write your CCI; you can do your CCNP core, and then you can go and focus on any of the specialized exams, like, for example, enterprise design, etc. All right, so this is the track: everyone has a home; everyone gains; everyone maintains their certification; everyone is awarded badges. So obviously, by the end of the day, once you complete the track, you can see that you have different types of badges. You have a specialist, then you have CCNA, then you have CCNP, and then you have CCIE. so you can start your journey. And then you can slowly move your career from this list to the expert list. And that's the goal. And once you complete your CCI in one particular domain, then you can move to the other domain. Okay? So there is a wealth of knowledge available.

And if you want to get it, if you want to become an expert, start with a completed technology and then move on to the technology. That will be the strategy. This particular course is focused on CCNP Enterprise, and once we have one of the core topics, then we'll go and check the SDWAN. Alternatively, we can go and check the other stuff as well, like design, advance routing, and enterprise automation. But at this point in time, we can check CCNP, Enterprise, and the SDWAN, because the combination of Enterprise and SDWAN will give you a vintage. At the moment, SDWAN is very hot in the market. It's very demanding. And if you combine these two core technologies plus SDWAN, the market value will be very good. What are the core skills you need? We will see that we have complete slaves. You can go and check. So now, this was the past where you had routes, trips, arcs, and other stuff. Now in the future. Now present. This is the present. So you have Enterprise core batch, you have a specialist, then you have the advanced routing batch, wireless batch for individual exam.

Also, you will get that exam certificate, but better that you go to the club. So CC and P Enterprise with any of the four Correct? All right. So now here again, you can see the summary that we have. For example, if you want CCNP Enterprise, you can do the core and the advanced. Or you can do the core. You can do wireless, any of these two. You can do the code, and then you can do the design. And here you can see that CCNP Enterprise Enterprise. Enterprise. Okay? And just try to explain how it is equivalent to CCNP, RNS, CCNP, wireless, and CNDP1. Suppose if you want to do CNDP1, you do the code and then design, and you are the DP. If you want to do CCNP and wireless, do all three. And then you have CCNP and wireless. If you want to do CCNPRNS, do these two. And usccnprns. If you want to be CCNP and SDWAN, you doCore and SDWAN, and you are the CCNP and SDWAN. All right? So that was the certification changes, and I hope you understand what kind of changes and certifications we need to obtain to meet our CCNP requirements. And from there, we can go and prepare for CCIE as well.

2. Topic

Hi everyone. Welcome to the CCNP Enterprise Core course. This course is divided into six different parts. Here you can see, starting from architecture, virtualization, infrastructure, network assurance, security, and automation. This link will take you to the details of these topics and their subtopics. I hope this course will be informative, and you will gain new knowledge from this course. Thank you.

3. 1.0 Architecture Part01

Let us begin with 10, which is the architecture, and what do we need to learn from it? We need to understand the design principle, the resiliency, the scalability, the redundancy, the vanguard deployment options, et cetera. So you can see that you have a long list starting from 1.1, then one, two, three, and then 4567 up to 1.1217, and you can now see that inside one four, you must understand the design principle 1.5, and you must understand the DNA or St access design principle. You have this QS wired and wireless in 1.5. And then 1.7 is taken from the old curriculum. Even in this 1.6, that is the QS, which is also taken from the old curriculum. So it's a combination of the old CCNP and whatever new technologies we have, and I'll explain why in the upcoming maybe third or maybe fourth slide. You'll understand that.

Now let's cover point number one up to now and what the agenda is for that. So you must understand enterprise network design concepts such as tier 23, fabric, fabric capacity, planning, and so on. And then the high availability and redundancy, like firstoff, redundancy protocol and SSO We'll see that because although this is only 0/1 A and B, we have multiple videos to cover these topics because again, this is a big topic. So let's try to understand this 1.1 and let's try to figure out what type of design principle we have and why we are using it. Once we understand why we are using it, that will solve our purpose. So we should understand why we need this. Now, let's say this van transport technology In this slide, you can see the evolution of the architecture and design principles. So, perhaps 25 years ago, when Cisco invented routers and switches and tried to connect different types of networks, we had the bridge and the fix.

You can see that if we go back and check the ARPANET and their principles and the TCPIP discovery and revolution, you can see that when the protocol was first invented and then again when Cisco came into the picture and revolutionised the entire network domain or industry. So, starting in 1990, when we had the multi-protocol and business support model for it, we had protocols like OSP and BGP. Those are the commercial protocols. You can still see that we are using rip, rip in some places. Again the old traditional methodology, evenwe are using frame relay. In some places, we still use frame-relay or extra 25, and so on. But now we are moving.

So, if you look at the journey from 1990 to 2000, where we have a missing critical network that supports real-time traffic, we don't have even one minute of downtime, and so on. It's a highly missing critical network. And if we are dealing with those topologies, how are we going to build those topologies? Again, from 2000 to 2020, you can see the evolution of STN and companies beginning to deploy it, whether it's van or land or campus automation or DNA, and so on. So now this is the complete movement. Again, this is the movement of a network. So, if you know the architecture principle, what we used in the mid-nineties or 2000 and what we will use in 2020 are both covered in this score. So we can start from our fundamental BGP OSPA or otherrouting protocols and then we can move and check that whattype of protocol has been used inside SDWAN or DNA.

So for example, BGP OSPF we are using here in theexisting network and OMP and T lock we can use inSdn or List we can use Nd and etcetera. Okay, so we should have a clear picture, and if you're doing the migration from your existing network to the upcoming network, if you know your existing network and the upcoming technology and network, then you can do the migration and fewer issues will arise. All right. So this will be your summary slide. What we are moving what we have at this point in time and what we need in the upcoming network cycle.

I mean when we are refreshing the cycle or when we are migrating the cycle, and what type of challenges we have here. You can see that. Again. The small thing means everywhere in all the placesyou will find the same type of challenges. The challenges are not small, but in terms of gathering the facts, that's 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 SDWAN or in the next chain network? So we know that scalability is one of the biggest issues; it means you can't scale. So you have this, and we can discuss a lot about the scalability.

Now, when we are talking about scalability, we mean scalability not only in terms of your network or how many devices you have, but scalability in terms of your routing capability, your IPsec capability, or even whether you can go and do some sort of deployment over the cloud. Just scalability plus cloud integration means you canmix these things and you can think allin a single bucket then how you're goingto integrate with IoT internet of things? Because, again, this is a huge topic, and we know that Cisco DNA, digital network architecture, or state access, they have the capability to understand it. Even Cisco is making IoT-related products as well. So, if we can integrate IoT devices into enterprise networks, how quickly will things change? What is next?

Can you do the automation programming? Do you have single pane of glass fromwhere you are managing all the devices? Okay, so if I go back and summarise these topics again, I told you that all these problems and the complexity that we have are common at this point in time, and if you see the existing network, we are still using the access, distribution, and core routing layers, or the L three layers. So we have some sort of C and then P and then P and then the network; they are divided into multiple virtual routing instances, forwarding instances, etc. So you can go and support network-level virtualization as well. So what I'll do is quickly mark here what the most common issue we have in the current network. I will not add costs at this time.

Leave this alone; we can talk about cost later because cost may be one of the motivators for making or doing the reference in the network. So what we want is scalability, and we want scalability in routing as well as IPsec. And that's why we have DMVPN versus SD and IPsec. or the new SDN, IPsec. Second thing, what we want as anetwork that we want integrated security. So at the moment I bring up my controllers, control plane, data plane, et cetera, I should have one solid, common, unified, secure fabric. So that's why this is also very important. Clearly, what you want is that the overall cloud integration means that it is now to again, which has some cost implications. So companies don't want to go to the central Harvard Data Center, and then they want to go and use either the IA direct internet access or direct cloud access; rather, from a branch, they want to do local breakout, and then they want to use the resources hosted over the internet or in the cloud.

So that's again important in cloud integration. Now, these things you have, apart from that one veryimportant thing here I will add it, that is possiblein the existing network as well in the same solutionis by default, that is the segmentation. So once you do the segmentation, the scalability, the security, the cloud integration, and the segmentation, apart from that, you want other features like full visibility, monitoring, a single pane of glass from which to do all these monitoring tasks, solid reporting, an easy way to do the troubleshooting, etc.

Correct? So these are the things and these are the terms we have, and we should consider these things within the architecture principle. So let's stop here, and in the next section let's continue the same architecture principle, and I will add some more valuable points in the upcoming sessions.

4. 1.0 Architecture Part02

Let us continue our discussion and understand more than what we have discussed earlier. So we have discussed that yes, we have different technologies in terms of evolution networks, so we can check the 2010 network and then 2020 and going forward. So what is the major change and how are we going to reduce the complexity in terms of design and deployment? That's actually very interesting. So we can see here that as MPLS evolves and the MPLS network gains popularity at that point in time, you can see how you can visualize the network.

So you can clearly see in the diagram that you have a hub network and then a spoke somehow, this design is giving some sort of idea that in an upcoming iteration we will use some sort of spine and leaf structure. Sometimes it is referred to as a cloth fabric. So you have your leaf. You have your spine. all the leaves. They are connected to the spine, and these leaves are not connected to each other, and that is what we are achieving now when you are achieving this type of topology or network where you have all the devices by default, we are one hop away at that point in time, are you able to do the segmentation for segmentation? We have already VRF, virtual routing and forwarding and this is now from the years. So we are using the VRF technology, and later on you will come to know that in SDWAN we are using VPN, which is nothing but the VR.

Only the name of the term is going to be used as a VPN, but logically or technically, they are also doing virtual routing and forwarding. So now the complexity will increase. When you have multiple devices, when you have different types of traffic and you mark those traffic as different type of VRS how you're going to do the routing or maybe overlay routing et cetera et cetera. This is still the network we are using in the existing one. It is possible but the thing is that we need to write actually the more line of quotes, more number of configuration you needed. Okay, but still, we are using them, and you can see that we have multiple technologies like VR flight or MPLS VPN because BGP is a nice protocol that is supporting all sorts of address families related to VRF and even other address families as well.

Now, again, in this design principle, how are we going to deploy the network? Do I have a single-provider design? Do I have a dual-provider design? Again, going from single to dual will obviously increase the cost, as will the high ability and redundancy feature, but the cost will increase regardless, or you will use the overlay network design, which is actually the future. Cisco has started their overlay network design, which technically means we are doing this independent of transport. So either you have dual or three or four different types of ISPs, you don't care, and you are creating a tunnel on top of that. That's the overlay tunnel. And Cisco has introduced their intelligent van, where they are using DMVPN as an overlay tunnel. But again, we are using Ivan and DnVPN, although so many companies are using it. But again, you have to write any number of quotes or more than one lengthy configuration. So Cisco is informing all of their existing networks that starting with Iban, they can migrate to Cisco SDWAN. Okay, why? Because again, you can see the cons of increased design complexity and additional technology needed for SLA over commodity transport. So there are some extra overhead that is there also the design and the solution is neat and clean and beautiful.

But you still have some things you can't do in the St. Van, as well as the automation and STM solutions in the Iowan. So that's why this movement is there. Let me quickly show you some of the slides related to single carrier and double carrier, or dual carrier. So here, you can see how your network may look like that. So although you have different link but you have single carrier. Suppose if one of the carrier, because obviously you have single carrier but suppose if that carrier will go down at that time you have lost. That is why it is listed here in the context of feature velocity bound to a single carrier: it does not protect against MPLS cloud failure with a single provider.

Obviously if that cloud will go down, I don't have resiliency or ability that I can go by the other carrier. This is obviously something I have on my dual carrier. But again, the complexity is there, and the cost is there. So you can compare the pros and cons. The disadvantage is that by increasing bandwidth and paying for bandwidth twice, overall design complexity may be reduced to the carriers' common denominator. Overall, you're increasing resiliency.

But cost-wise, there is an issue. Now, considering this diagram and this diagram, and again considering the overlay network design, if we have this out of all these three, that will be the exact solution we are looking for, and that's why we are looking forward to an SDWAN solution. Again, we can see all these things inside Section one five. So let me quickly show you those four. So we have one four and one five places where we can address those design issues and how HTML and the DNA or staff will solve these issues together. That, too, we can discuss in the upcoming sections.

5. WAN Overlay Technologies

We are still in the basic section, where we are learning what types of existing terminologies we have and then what new things we are going to learn in the new CCNP curriculum. Let's discuss the virtual overlay technologies. We have layer two overlay and layer three overlay within this. This overlay technology or terminology is not new. Actually, this is coming from older technologies.

Now we'll see these overlay terms appear again and again in the SD band and the DNA—and possibly in ACI—the data center topic. So now we have something called "underlay," which is your physical infrastructure structure. And then on top of that, you are creating virtual dynamic tunnels. This can be layer two. This can be layer three. Layer 2 tunnel examples demonstrate the possibility of using the Layer 210 link protocol L2TP. Version three you may have OTV or VXLAN. That's the very popular term. We have VXLAN and this will learn more and more in the upcoming session.

When we are talking about layer three overlays, we have IPsec, we have GRE, we have 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 two fabric or that you are extending layer three fabric. Or to extend the fabric, either you need layer two or you need layer three address families or addresses, etcetera, in the SDWAN, or what is there in DNA is that we are going to automate this process. So you don't have to worry, for example, in SDWAN about creating IP set panels like in I, when we're creating the Gmvpn phase three channels here, about creating the IPC tunnel. At the moment you bring up the fabric, automatically, those panels will be formed. Now, when we are talking about the tunneling technology packet, on a normal packet, we have the payload and the IP header. In GRE again, you have the payload and the IP header, and then you have extra overhead for GRE. Right? In IP set mode, either you're using IP set mode in transport or tunnel mode. In transport mode, you have less overhead in terms of packets, but in internal mode, that is much more secure.

And by default, most of the technology is using the IPsec tunnel mode, where you have the inner header and the outer header. So at that point of time, obviously, your header size will increase, but the level of security will also increase. Correct? I'm not going deep inside IPsec and how IPsec is working or GRE and how GRE is working. We have just started the course, and as per the agenda, whenever these things come up and it says in the exam or in the curriculum that we have to go deep dive in this particular topic, I'll go deep in this, that I will do the packet capture, that I will analyses the packet, et cetera, et cetera. But at the moment, we are just getting familiar with these technologies. These technologies already exist, so what new ones will we see in the new enterprise setup or in the CCMP enterprise? Now, for example, consider the locator ID separation protocol or the identifier separation protocol.

Now, if you understand the list, So for example, I already told you that you have land-based STM. So in the STM solution, you have three things. You have land or SDN for land, and then you have SDN for a data center as well. So, data center. Now for land, the common term is staxis. Obviously I'm talking only in terms of Cisco. So in Cisco, we have DNA, which is a name, but the staff is the technology. In Van, we have SDWAN, and in the datacenter, we have application-centric infrastructure, or ACI. If you go and learn all of these technologies, you will notice that they all have some sort of leaf spine structure. So, if I have two spines and then leaves like this, I'll take one more leaf to demonstrate the redundancy. All these leaves will go and connect with the spine; leaf after leaf, they will never connect.

These spines, they are working as a route reflector, means these spines, they have the database. So now these leaves—whatever endpoints or whatever devices are connected with these lifts in DNA—are referred to as an edge node or edge device. So these edge devices, whatever network, whatever entries, Mac address, IP address, et cetera, et cetera, whatever they have, they are sharing with their spine or their parent. Now this spine in DNA is a mapping system, or mapping resolver. Now this is fine in ACI; this is a term inside ACI. When you analyse SDWAN, you'll usually find something called a "V smart controller," which has all of the routing information in its database. He is the controller, the control-plane device, and he's working as a route reflector in ACI.

Also, these spines are working as a route reflector. And suppose you don't know all this technology; there is a chance that you will get confused. That's what I'm telling you: okay, Nestiva and the VA Smart in ACI are fine. In DNS, it's actually the control plane device. Sometimes we refer to this as a control plane router, maybe a border router, et cetera. So again, we'll see later on. But at this point in time, what you can understand is that you have some common authority. You have common authority just like DNS servers, where they have all the topology information and all the database information. You think that you have the database information. Now these end points they haveoff loaded with the information. As a result, they lack complete topology information. They know their local systems, local endpoints, and local entries. Once they have their local entries, they are teaching (or they are telling the common authority) that this local system I have this local IP Mac, I have you please store at you. Likewise, he will also tell you, "Okay, please store it with you." And when this guy wants to communicate with this guy and he doesn't know how to reach it, he will send the query packet to him.

I want to reach there. And he will reply in such a way that they can now communicate directly. Okay, so these are acting as proxies on behalf of, and most technology, including most TN technology, follows the same analogy. All right? So now we can understand all the different technologies. For example, if you know of other non-Cisco technologies as well, for example, NSA or any other staff solution, they may also find the same type of thing happening. And then once you start comparing this technology, it will become easier to learn and understand because, again, every day, some new things will come, and it's almost impossible to learn and memories all those things. So it's better that you start comparing different technologies, and then we can learn them easily.

Hide