Pass Cisco ENWLSD 300-425 Exam in First Attempt Easily

Introduction to Designing Wireless Enterprise Networks Training ENWLSD

1. CH00-V01 About The Instructor

Hello and welcome to our first chapter. In this chapter, we will talk about different custom requirements and how to obtain them, and we will talk about some design needs that occur throughout the wireless infrastructure two times. So first of all, we will understand how to determine the design type. Is it a new design? Is it an upgrade? We will talk about it. We will go with the reason for using wireless networks and an evolving workplace. You will understand how to identify project members and what different project members are that can have an effect on the design. And we will also understand the different project members that we will need throughout the deployment and site survey. We will go over different Cisco design methodologies, and then you'll understand how to go through design documents that are already provided by Cisco. There are some pretty nice, well-dated designs that were created by Cisco, and that will help you a lot both for the deployment and the vote, for understanding the existing infrastructure and coming up with a plan to refresh it or coming up with a newer design. We will also talk about the wireless design for just data and understand how the wireless network needs to change. We can also talk about the demands actually how they changed. Then in the next part, we will talk about different standards for wireless design. We will understand the MIMO. Multiple inputs, multiple outputs Different ho. 211 Mdns. Eleven kevr. And we will understand the different challenges of setting up wireless networks for hospitality, healthcare, education, retail, and warehouses. So we will basically go through different design needs for different environments. Next up, after coming up with a design, we will understand how to gather customer information. What are the questions that we need to ask, and what are the things that we cannot get answers to, even if we have the meetings with the customer? We talk with the customer a lot, but there are some secret questions that we need to ask because with them we can get a better design. We will go with the design documentation, we will understand the custom questionnaire, and the secret source and the secret questions will be part of this. And we will understand what the statement of work means and how we can get it and prepare it for our customer. Next up, we will talk about the site survey, how to start the site survey, what are the precautions and requirements that we will need from the customer, and do we have access to the site? Do we have the address, even? Who will chaperone us throughout the site survey? We will understand predictive site surveys and another type, which will be passive and active site surveys. Why do we need them? How can we do them? What are the differences between them? Then we will go with a site survey, different deliverables that we will give to the customer, and we will talk about different design demands. So why do we need mesh network design? Why do we need high-density network design? What makes a network design a high-dance network design? What makes a network design security sensitive network design"? What can we think about being cautious about security sensor network designs? These videos will be talking about the demands of the actual design, not the actual design itself. what makes it a high-density network design. So, in chapter one, we will cover a lot of ground, but don't worry, I will go over each topic one by one so that by the end of chapter one, you will have a better understanding of each topic. Thank you for watching, and let's see you on a set of tiles to run.

Hide

Wireless Enterprise Network Design Fundamentals

1. CH01-00 Introduction to Chapter 1

Hello and welcome to our chapter One. In this chapter, we will talk about different custom requirements, how to obtain them, and some design needs that occur throughout the wires and infrastructure lifecycle. First of all, we will understand how to determine the design type. Is it a new design? Is it an upgrade? We will talk about it. You will go with the reason for using wireless networks and the evolving workplace. You will understand how to identify project members and what different project members are that can have an effect on the design. And we will also understand the different project members that we will need throughout the deployment and site survey. We will go over different Cisco design methodologies, and then you'll understand how to go through design documents that are already provided by Cisco. There are some pretty nice, well-dated designs that are created by Cisco, and those will help you a lot, both for the deployment and for understanding the existing infrastructure and coming up with a plan to refresh it or come up with a newer design. We will also talk about wireless design for just data and how the wireless network needs to be changed. We can also talk about the demands actually how they changed. Then on the next part we will talk about different standards for wireless design. You will understand the MIMO, multiple input, multiple output, different two eleven M admins. And we will understand the different challenges of setting up wireless networks for hospitality, healthcare, education, retail, and warehouses. So we will basically go through different design needs for different environments. Next up, after coming up with the design, we will understand how to gather customer information. What are the questions that we need to ask, and what are the things that we cannot get answers to, even if we have the meetings with the customer? We talk with the customer a lot, but there are some secret questions that we need to ask because with them we can get a better design. We'll go over the design documentation, understand the customer questionnaire, the secret source, the secret questions, and what "statement of work" means and how we can obtain it and prepare it for our customer. Next up, we will talk about the site survey, how to start the site survey, what are the precautions and requirements that we will need from the customer, do we have access to the site, even the address, and who will shop around us throughout the site survey? We will understand the predictive site survey and another type, which will be passive and active site surveys, why we need them, how we can do them, and what the differences are between them. Then we will go with a site survey, different deliverables that we will give to the customer, and we will talk about different design demands. So why do we need mesh network design? Why do we need a dense network design? What makes a network design a high-density network design? What makes a network design a security sensor network design? What can we think about being cautious about security-sensitive network designs? These videos will talk about demands. Not the actual design, but the demands of it. what makes it a high-density network design. So in Chapter One, we will deal with lots of metal. But don't worry, I will go over them one by one so you will get a better understanding of each topic at the end of chapter one. Thank you for watching, and I'll see you at the start of chapter one.

2. CH01-V01 Determine The Design Type

Hello and welcome to our new lesson. In this lesson, we will determine the design type. So what kind of designs that we can have. First of all, we can have a new design. What is that? A new design is the one that we can also refer to as the Greenfield design. And in this design, you will design it from the start. So there is no WiFi in the existing building. And in some situations, there isn't even a building. So you will not have the building materials installed. You will not have the elevators and stairwells, and if you don't have such materials and if you don't have such building constructs, then you have to include the interference that can happen from those infrastructures. Because when those structural components are installed, you may encounter issues with RF signals, attenuation, and interference caused by an elevator shaft that was not present when you first visited the building. This doesn't occur too much or too often, but as a wireless designer, you have to know how you need to act in such situations. You should also count the interference because there aren't any building materials, so there aren't any cameras, there aren't any microwaves, and there aren't any RFID sensors. So you have to consider all that. And when you design a new wireless environment, you need to understand the type of new infrastructure. Are you creating a campus RS? Is this a campus design? Is this to be used through a wide-area network? Do we have any data centre connection? And what are the security precautions that you will use all together, all of them in one design, such as on a campus or in a wide area data center—all of them in one design? so that you have to think about different architectures. You have to consider them. And you also need to understand why we need it, why we need this wireless design in the first place. For that environment, will we use some applications that will need some real-time data? Or will it be just emails, just web browsing? You have to understand the need, the need for again, the need for speed. Do you need eleven ACs? Do you need Even Ax? What do you need? What kind of users will you have on that campus? Is it just students? Or is it something that is based on the Internet? So you have to consider all that. and another type of design is the upgrade design. So in the upgrade design, there is already an existing WiFi deployment. You might need to replace that deployment or augment it somehow to make it better. And even the previous deployment didn't have to be Cisco; it could be another vendor. So you have to understand some of the design concerns related to them too. But what we need to focus on is how to get the customer's needs and put them in place from a Cisco perspective. You must understand the customer's requirements in terms of Rs, bandwidth, how much coverage is required, where it should be located, is it necessary to cover the auditory environment, and how frequently you will require roaming in order to design the network in such a way that layer 3 roaming is required frequently. A better design needs minimum roaming. So you might have high availability for your wireless and controllers, but you don't have to get access points. Enroll and register for different controllers. So you will need to keep this as minimum as possible. You need to have the maximum coverage; you need to provide efficient and usable benefits. But just putting them lots of benefits will not even help because it will mean that you will pay a lot of dollars, a lot of euros, a lot of strolling. So you have to pay too much money. You don't want that. You have to use bandwidth efficiently. You have to put some code of service into the bandwidth usage per client, maybe per SSID. So you might want to put more emphasis on certain SSIDs, and you might also want to get the RF environment as clean as possible. So what are your customer's needs? And you also need to understand that WiFi networks are using only a couple of shared frequencies. So if you are sharing something, that means you are prone to interference, because other people will use it too. And also, there are some technologies that will use certain frequencies, such as 2.4 GHz. So if you have a microwave that will use it, or a Bluetooth ble that will use it, or a microwave ble, they will all use this frequency. And you have to make your design less much interference prone. You have to think about certain issues. And you know, 5 G and is less prone to such noise, so it also has more available channels and less channel overlap. And you can even increase the channel size. Taking it from 20 mega to 40 mega and even up to 80 mega will make a huge difference for your files. So you have to consider all those things and all those issues. And after you determine the design type, whether it's a new design, which is a green field, or an upgrade design, which is sort of a brown field design, then you have to start thinking about what to implement, what not to implement, and how to continue the design phase. All of this will be covered in other videos, but in this one, we learned about some concerns about new and upgraded designs. Thank you for joining.

3. CH01-V02 The Reason For Using Wireless Networks

Welcome to our new lesson. In this lesson, you will answer the question about the reason for using wireless networks. So you are in a meeting and you are asked to design the wireless network, but before all of this happens, you have to answer the question of why they need to use WiFi or why they need to use a wireless network. Maybe they are already using wireless networks—but why should they use your design? Why should they believe in you? Why should they believe in your vision? So you need to persuade the customer; you need to persuade the stakeholders to believe in your vision and understand your perspective. First of all, you need to ask them, "Which skills does your WiFi have?" So what kind of WiFi do they have? Do they need AC? So you should also understand what kind of security mechanisms they are using. Are they using ATO-2 and 1X for security? What is the algorithm that they are using for key management? And you should understand the root requirement for the customer's project. And generally what I faced with in the real world is that the customer doesn't even understand fully how WiFi can help them. It's not just about getting the speed or not using cable. You don't have to use cable or rely on slow wireless, but how fast can it go and what design tips and tricks do you need for a better wireless design? And do they know the standards for wireless? Do they know their ABCs such as do they know WiFi Alliance? Do they know I triple the standards for wireless? Do they know all that? Maybe they don't even know what to ask. So if you don't know some subject well enough, you don't even know which questions you need to ask. So you need to help them understand how WiFi can help their organization. And in some networks—in some enterprise networks—they have designs that will help their network for the next five years, but some customers don't have that. So you need to help them understand what they will need in five years' in the future. So will they need much more speed than they currently have? Will they need to have better coverage? Will they need to have more security? What kind of endpoints do they have? So are they considering buying endpoints that will be supporting WiFi 6, the hardest topic in the environment today? If they are using WiFi for six clients in the next year, then they will need to go to Ax because they need to be able to use it as efficiently as possible. And as you know, WPA2 even had some serious issues. So they need to upgrade to WPA Three; can their devices support that? If they have a legacy wireless network, most probably they won't, and you have to let them know which problems you can help solve with WiFi. So maybe they are using some guest clients; maybe they need to provide some WiFi to their guests. Are they aware of that? Or maybe they are operating a coffee shop and just giving away free WiFi will increase their sales because people will spend more time in their environment. Maybe if they just use a better wireless system, they can have a better and more efficient inventory code system. So maybe they need to use handheld devices that can use WiFi so that they can scan personnel without having to just go and enter everything into their computers and use a handheld scanner. They'll just solve it and solve their problems. Perhaps they have some inventory that is severely lacking. So maybe they need to use some RFID tags. So using some RFID tags will let them know exactly where their devices are and help them not miss them because they will know exactly where they are. So you have to understand the customer's needs, and you have to get the customer to believe in your vision for wireless. So it will be better when they believe in your vision and understand your design. Because if they don't know wireless, if they don't know those ultra police channels, if they don't know what they will need in five years, then it will be very hard for them to go up to 812 eleven ax speeds because what will they need it? They will look at you like you are talking about some alien technology, which you are not because maybe 5G is the hottest topic, but WiFi 6 will be the most improved topic in the next five years. So everybody will use it; all the vendors are deploying such networks, and you will have clients that will support WiFi 6 easily, and you will just support a total of eleven N speeds. WiFi 6 means that your network will have nearly cable speeds. Even alternating current will provide nearly cable speed. So your real-time video conferences will be in high resolution, and your real-time multicast traffic will be on your network, so you will be able to support it easily. You have to understand the customer, and then get the customer to understand and believe in the vision that you have for wireless design. So when you design something brand new, when you design something that is beyond the current age, then they will not be opposing your design; they will be cheering for you because now they know what they need. You have to get them understand what they need before even they need it. That's actually the reason to use so much judgement in your designs. So in this video, we went way beyond talking about the reason for using wireless networks. But I think it will be beneficial for you to understand how to get your customer on your side and let them understand what they need and why do they need it. What kind of skills does their current infrastructure have? So what kinds? You can give them those benefits by improving their design and letting them meet higher standards for their wireless network. Thank.

4. CH01-V03 Identifying Project Members

Hello and welcome to our new lesson. In this lesson, we will talk about how to identify the project members. So in a design environment, you will have many different project numbers. You might be needing to meet with the directors, and you might need to talk about certain business and design decisions with the project sponsors and decision makers. You need to have some access to certain areas. So you need to talk about security, operations, management, and some employees and customers. So you need to understand the team shot, you need to understand the project members who will make the decisions, who are the decision makers. You cannot get them all in one room, and you cannot get meetings with all of them together, but you need to talk about them, even if it is necessary to talk with them separately, because you need to understand the needs of the IT department and also the existing infrastructure, and nobody other than the IT department can tell you all that information. And you have to understand the project needs and you have to understand the purpose of the project. So you have to talk about the decision-makers and project sponsors. Then you have to talk with security management and security operations, because you will need access to each of the places, each part of the facility, because you will maybe need to do some site surveys, you will need to go and check on some employees' needs, and you will need to understand the existing infrastructure and see where the access points are distributed. You need to do some site surveys to define the locations and get the exact location for the deployment of your access points. And you need to talk with managers that are related to projects, so they can be some department managers or some warehouse managers for the charge during the times that the facility is operating at full capacity. So you need to understand the scheduling. And it will be a great idea to get a sort of team chart so that you understand who is depending on who is the decision maker, who are the decision makers, and whom you should talk with for the IT department. And one mistake that I see in the real world is that sometimes the sales engineers or the account managers try to determine the project budget. And if you try to do it way before then, it wouldn't be wise, right? Because you don't know the stakeholders, you don't know the project goal, and you don't know the process that will need to be followed, whether it's an upgrade or a new design, So talking about the money is something that people like to do, but it's a mistake. And as a design engineer, as maybe CCNP Wireless Engineer, CC Wireless Engineer, you need to focus on the customer needs and you need to stop talking about or stop considering the budget. Of course, it will be in effect later on, but without going too much into the budget issues. You must comprehend the requirements, as well as comprehend and identify the project members, because focusing solely on the budget will have a negative impact on everyone, both your company and the people on whom you will be implementing the project, because no one wants to pay more than necessary. But if you are doing something just to keep the budget low, then it will not be a good design, it will not be good for your purpose or the project goal, and it will not be covering all the aspects of your needs. So you need to understand and identify stakeholders; you need to reconcile some conflicting views for the project sponsors because you have to get them to believe in your vision; you have to get them to believe in your design; and you have to understand their concerns. You must also notify employees and customers of your presence during the site survey, because if you are simply going through the holes with a computer and trying to understand, trying to get a site survey, it will cause people to call security. I would do that because if I see somebody new going with a computer and trying to do something while going with that computer, as you were driving with wireless, you have to understand that. So you have to inform the employees; you have the employee; you have to let the customers know your presence. So you will be depending on the managers to inform their own employees. And you should also get some user-sample employees to come to your project meetings because they will be using the design and the network that you designed, and you have to understand their concerns and their usage. Are they using too many real-time applications? Are they having problems with the current wireless infrastructure because of those COS issues or because of some bandwidth issues? Maybe they are having some RF interference issues in the kitchen, or for some employees who are sitting in rooms next to elevator shafts, they might be having some RF issues. So you have to consider all of that. And of course, you can just side-survey the whole area and try to get as much data as you can. But talking with the user himself or herself will be much more effective for you in the initial stages, of course. So it's a very important key aspect to identify the project members, whether they are the decision makers, whether they are the ones that will give you the infrastructure for the information technology, or whether they will give you access to facilities, buildings, and even the users who will use your design in the end. Thank you for watching.

5. CH01-V04 Cisco Design Methodology

Hello and welcome to our new lesson. In this lesson, we will talk about Cisco design methodology. So in your WiFi design you have some purposes, and one of those is to let the customer be able to successfully implement and operate your Cisco technologies. You want to optimise their performance throughput, and you want to give them some productivity means so that they will have better productivity for their stuff—for the right stuff. And you need to give them something in return, because they gave you an investment, they made an investment on your Cisco products or on your wireless design. So in return, you have to give them some scalability, you have to give them security on your wireless design, and resilience and high availability will be your main aims. And to get them all in order, Cisco just made up a new design lifecycle approach. This is PPDI. Prepare, plan, design, implement, operate, and optimize. So in your Cisco lifecycle services approach, you will define some activities such as those six ones, and by using them, you will have a better design and a more efficient design methodology. With the help of that, you will increase the return on investment, increase scalability, increase availability, and enjoy many different benefits for a wireless network, actually for the customer's wireless network. So what are those six phases? The first phase is, of course, the preparation phase. In that phase, you look at the requirements and identify the wireless local area network products and solutions that will satisfy the needs of your customer. In the second phase, after you get those requirements, you need to plan, and in that plan phase, you assess the customer network, whether you are building a new design or updating an existing design, and you will just plan which solutions, which wires, and which solutions you will implement. And under the design phase now, you will design the network, the wireless network, for different services, for different wires and solutions, with many products, because every vendor has different products and different portfolios for controllers and access points, and even some software that will be integrating with your VLCs, integrating with your access points, or with your existing network infrastructure. And you need to design them in such a way that they will work together just perfectly. On the implement phase, you will do what the word just says: you will implement the design, you will deploy that wireless solution, and after you deploy the wireless solution, you need to keep that wild sign solution that you redesigned operating the way you designed it. So you need to maintain the health of your wireless design, and you need to do some repairs and replace some components that turn out to be faulty. You also need to resolve some of your problems, troubleshoot them, and you need to open some cases for operational purposes and for maintenance purposes. And after you do such things, you need to optimise your network, because you cannot just foresee everything from the start. And you can, of course, make a great design, but there will be some concerns. There will be some issues that will be specific to the network of that customer. So after you complete all those five steps, you need to optimise your design. You need to optimise your way you implemented. That is in solution so that you can meet the needs, performance needs, and challenges identified throughout those five steps. Once you've optimised that, you'll be ready for the next project, the next phase. So just because you went to step six, it doesn't mean that you will stop here. You will go back to the prepare phase because you need to prepare your network for the next five years. You need to prepare new designs. You need to prepare new projects for new upcoming technologies so that you'll be able to plan them, design them, implement them in your network. Then you'll be able to operate them. So in this video, we went over and talked about the Cisco design methodology, which is WPDI: prepare, plan, design, implement, operate, and optimise, and how we can use all those six steps in our design lifecycle. Thank you for watching.

6. CH01-V05 Cisco Design Documents

And welcome to our new lesson. In this lesson we will talk about Cisco design documents. So we have different type of documents for Cisco design and you can use them to improve your own design methods, improve your own design documents, and you can also let them guide you to learn the technology behind what is happening on your wireless technologies. Wireless Solutions. First of all, we have Cisco Well dated designs. You will see it as CVDs and CVDs include many features, applications and technologies for your customer needs. Basically they have two different types, basically they have two different types technology and solution guides. For the technology design guides, you will have deployment details, information about well dated products and so forth. And you will also have the best practices for the solution design guys. You will get the necessary references in the existing CBDs and you will be able to integrate what you will learn them. They will have some product features and you will get some cross references between Cisco products and also some information about third party tools and how you can integrate them with your own Cisco solution. Both of those Cisco validated design guides will give you a test starting point for initial points of your design and how to deploy that system in terms of configuration and in terms of integration. And you will have some information related to tests such as the use cases, how specific technology can be used in a certain deployment. You will have the scope of the technology, you will have some to come up with a design that will have much more reliable and faster deployment. And for the next document we can talk about Cisco SR and guides. These SRMD guides are called as solution reference Network design guides and they will again give you guidelines, best practices and some design recommendations on how to design that certain technology, or how to design your wise network and even deploy that solution to your own design to accompany your design. And again you will have two options for that, which will be the current one and which will be the archived one. The current documents will be the recently updated documents and you can use them for the latest software, but you will also be able to reach the archive documents, which will be documents that will not be updated anymore. But if you are using older versions of operating systems for your Wi-Fi controllers. For your network devices. Network hardware or any software that will be going with your design. You can even use them because sometimes you have customer that already has certain software deployed and they want you to integrate with that and you cannot just update it because maybe they don't have any support contract and you need to go with that in your own design. Maybe. Just maybe will update it in the next year in another project. But you need to integrate with that old software in your current design so what are you going to do? Just deny the project? No, you will do it and have a plan for the next year. But you will be applying the Archive design guides. And also we have some configuration guides for each product. They will give you step by step instructions on how to configure certain hardware and software. And you will also have certain configuration examples, some technical details related to those products and software. And you will also have some deployment examples for those deployment guides. By using those guides, design guides and some Cisco Valdes designs, you will have a better understanding for each technology and how to get all those ingredients and make the best cake possible. So you'll be just like a cook and you need to put the eggs in, you need to put the flour in, and you need to mix with certain speed and you need to get the cake down, you need to bake it. So all those things are just like having a wire scent controller. Configuring each AP with certain operational mode, integrating some third party tools with your design and getting it all deployed. So you need to understand the technology behind the software and solution that you will use in your design. So that is what school design documents are all about. Thank you for watching.

Hide