Pass F5 101 Exam in First Attempt Easily

Introduction

1. About the Exam

About the exam. F5 101 exam is the first exam to take. It is required to achieve F5 Bibi Certified Administrator or F5 CA is also required to achieve a new certification Five Certified Technical Professional in Sales or F5. CDP sales. Let me make things clear. Passing F5 100 and one exam doesn't get you anything but the eligibility to take the 200 level exams. So if you pass F5 101 and then you pass Five two, one, you will get F5 C Eight. But if you pass F5 202 Exam, you will get F5 CTP sales. There is no prerequisite, so anyone can take the exam. But I know many candidates already have experience in networking, security and even managing Five big IP devices. But I welcome and strongly recommend for you to take these exams even if you don't have any experience in F5 or Data Center technologies. So this is for anyone who is interested, especially in Data Center, because Datacenter has many different technologies running. So for a F5 101 it is good because it's an entry level exam. But we talk about many different areas and technologies such as networking, security, applications and features like load balancing, help, monitors and so forth. So there are no value dumps available. There are many certification and exams out there. There are also many paper search individuals. So these are individuals who have certifications, but they lack knowledge skillsets and they only use the certification to get promoted or get hired for better position. For F5 is different because first there are no valid dumps. Whatever you see in the internet are not real at all. For F5 exams. It is challenging. And if you pass the exam and if you get certified, that means you did a cheat and you did it your own. So the exam is based on version 13 one we have already lab prepared and outfit VIP devices are already deployed and running. In this version the exam is 90 minutes long. But for nonnative English countries like myself, I'm in Southeast Asia, they provide us additional 30 minutes. That would be a total of 120minutes or 2 hours of exam. It's a total of 80 questions. Multiple choice. If you see radio boarding option, that means it's a single answer. But if you see a checkbox, that would mean it's a multiple answer. But they will provide you how many answers required per question. Booking an exam will be discussed later.

2. Audience and Expectations

Who can attend this course? Anyone? Whether you're new to F5 or have been working with F5 big IP devices for a few years already, this is for you. You. This is also for network engineers or aspiring network engineers. This is also for anyone who's preparing for 101 exam, but obviously for network analysts. Well, part of this course talks about F5, how it handles network traffic for web administrators that is currently working with Apache or NGINX. And you want to understand how Fi works as a proxy or a web server. This is also for security engineers and application security specialists. So F5 can be a d doll solution. It can also be a web application firewall or Waif’s if you are specializing or you will be specializing or F5 as Hua, it would be recommended to start with the basics of F5 Big IP for those who are looking for promotion. So F5 Big IP as absolution is not just a network device. It’s also a security appliance that is running on Linux. It enables many different features such as load balancing, monitors, profiles so it's full fledged application delivery controller. It also has special features such as automation and programmability and can be integrated to many third party services and devices. So if you understand F5 deep enough, you will get that promotion. You are rooting for course content. So this F5 101 exam preparations based out of the official F5 101 application delivery fundamental Blueprint. We’re going to revise a little, but it will not be less than what we have in the blueprint. We’re also going to do lab demonstrations. There are not much of configuration requirement in the blueprint. But I believe for you to better understand the technologies configuration in our F5 VIP appliance is something that it can be helpful and beneficial in passing the exam practice exams will also be provided every time you finish section expectations so something different in discourse or at least the way I deliver courses and trainings is that often use whiteboard a lot. Meaning most of our discussion will be based out of whiteboard. When I say most, this is majority more than half. And for this course I am expecting 60% will be white. Board based discussion. We’re also going to use lab configuration demonstration both CLI, Five GUI or I will also be using tools such as Wireshark or filler and that will be about 25%. Only 15% will be used for slides. And something that I would like to tell you before we start the discussion we're focusing on that F5 101 X but there are some concerns end that will be based on F5 201. This is okay because after you pass F5101, you will take F5 201 anyway.

3. F5 101 Exam Blueprint

Let's review the official blueprint of our F 5101 exam. As you can see, we have four sections. The first section is about configuration ration and this is related to configuring many different technologies. But if you look at the first item up to the last item, you will see that majority of all of these topics are related to networking, configuring, VLAN, determining switch, routers and connectivity requirements, assigning, IP address, establishing, routing all of these are network related discussions except for this one. Now, what we're going to do in this course is we're going to separate ADC or application delivery controller in another discussion. So I will put this here separate part. Okay. Now for section two troubleshooting. It defines there that we need to understand many different layers of troubleshooting requirements layer one. Layer two is all about layer three. And as you can see here, identifying application network errors, that's fine. This section is all about troubleshooting. But what we're going to do in this course is we're going to move the troubleshooting discussion in the last part. Why Because in order for us to effectively analyze and troubleshoot, we have to understand the basics of networking, the basic of Application Delivery controllers well as many different applications. So I'm going to put here put it on last part. Section three, Maintenance. So in this section we're going toned to understand reviewing basic statistics. Also need to understand how we upgrade our Fi device and its software, interpret traffic flow, service status and system health. I don't have any problem with this section. Now for section four knowledge. As you can see on the first two items, explain common uses for ICMP and Map functionality to OSI model. So most of these majority of these items are related to networking. So what we're going to do in this course is we're going to move everything network related discussion to the first part. Now, OSI model consists of layer one to layer seven and the layer four to layer seven which is related to application it should belong to the rest of these items it should belong to with security applications as well such as VPN, TLS, SSL, DNS, NTP, Syslog, SNMP, et cetera. What is not related or not should not be included in this application is this High Availability. So in our work course, what I'm going to do is High Availability should be part of the application delivery discussion.

4. Course Flow

Course flow. How I rewrite the course is still the same, but a bit different compared to our F5 101 blueprint because of the sequence. So for part one, Network Basics, we're going to talk about not much of layer one because we're not going to talk about speed configuration or speed settings, duplex configuration, or even different types of physical parts. We are going to focus more on layer two, layer Four technologies. We’re going to talk about switching VLAN stagging trucking for layer three routing. We’re going to talk about static versus dynamic routing protocols, and even IP addressing and subletting for transport layer. We’re going to talk about the difference between TCP versus UDP. We're also going to talk about network address translation and DHCP. And lastly, we're going to demonstrate how we configure network components in our F5 PDIP appliance. I separated the application, Delivery Controller road discussion from Network Basics because I don’t want to mix topics. And again, our Fib or ADC is not just a network device. Before we begin discussing ADC and load balancing concept, we will talk about proxy servers first. We will also talk about other features such as monitors, persistence, and many others. Also, we will demonstrate the configuration of our F5 big IP device features. We will also talk about high availability and how it works in an application delivery controller perspective. For part three, Maintaining Application Delivery Controller, we’ll talk about monitors, how to view statistics and status of different objects. We will also introduce F5. I help. And we are also going to show you how to analyze and interpret traffic flow traversing to our Fi VIP device. Part Four Applications and Security Technologies In part one to three, it involves some configuration demonstrations. But here in part four, it's all conceptual. We’re not going to configure VPN, DNS, NTP, Color SNMP in our F5 big IP device. How about http? Well, Http is one of our core topics for this course. Http, configuration and especially troubleshooting will be discussed in the next part. Part five troubleshooting network and applications. I saved the best for last. There are many questions in our F5 101exams that is related to troubleshooting and analysis, so this is probably the most important part. We will talk about Http codes and errors. We’re also going to provide troubleshooting examples in most layers of the OSI models. Layer one to layer four, we're also going to troubleshoot Web and other application as well.

Hide

F5 BIG-IP Lab

1. F5 BIG-IP Lab Overview

In this section. I will now provide you with an overview of what our five-big IP lab typology looks like. I will also show you how to access IS, our five-big IP device. Are the clients free to download resources for this section?

2. Lab Details

Five big IP lab details: So there's only one piece of hardware we're going to use in this lab, and this is where our hypervisor is going to run. I am using an Intel loop, and this is where our VMware ESXi is installed. We sometimes refer to this as the mini computer or mini desktop, and I also refer to it as a mini server. But it has only one network adapter or network port. Okay? It has an HDMI port as well and it has four USB's. It's tiny, low powered and easy to use. Again, this is where our VMware Six is directly installed. You can use any hardware such as old PC or laptop or even old servers. Under software we have F5 big IP virtualization running in version 13 one. We also have VMware bespver client. This is the software that we will use to access our VMware ESXi. We have training server. This server is sitting behind our F5 VIP I.e. also have Windows Client and Windows Client. This is the one who will send data traffic to our F5 big IP device to test application and load balancing software applications. Most of these are installed in our Windows Seven clients. These are Google Chrome which is the preferred web browser Wireshark and filler. These are software application that will be used for traffic analysis. We also have party. This is an application for us to access our F5 big IP device via SSH to control and configure the Claw also have Remote Desktop connection to glasses our Windows client.

3. Lab Topology

Lab topology. We have three networks in our lab topology, and these are all used by our five devices. The first is internal. We are using 170 216 00:16, and this is where our training servers are also connected. We also have our external network, and we are using the 10:01 network. This is the network where our Windows client sends data traffic to our 5-gigabit IP device. The most important network is the management network because this is where we access both the bigIP device and the Windows client. Here I am using one of the I 216-81-0240f courses in your lab. You can use any network, but for the sake of demonstration we will be using this one. Now my laptop sits on this network, so I'm just going to add it here and connect it to the 192-168-1024 network. And I will be assigning an IP address; let's say 55. Assuming everything is configured correctly and I can reach both the big IP device and the Windows client, I can now manage them. All I need to do is open a party and fill in the information like SSH 422, and I can now access my big IP device via CLI. Using SSH, I can also open a web browser and point it to HTTPS and the IP address of fibtip192-16-8131, and I will be able to access my bigIP device through the web browser via HTTPS. If I want to access the Windows 7 client, all I need to do is open my remote desktop connection (219-2168 three).

4. Lab Setup

We will not discuss how to build our F5 lab environment in this course because I have already published one, which you can find here on Udemy under the title Building a Big IP Lab for Free. Feel free to enrol at any time. Oh, the cost is zero. It's totally free. So before you begin enrolling and watching this course, I just want to remind you guys that a hyper advisor is required.

Hide

Networking Basics

1. Network Basics Overview

In this section, we're going to talk about the basics of networking from layer one to layer four of the OSI model. We're going to talk about Vladimir Lance tagging, IP addressing, routing, network address, translation, and many more. If you are already confident with advanced-level knowledge of networking, feel free to jump to our practice exam. And if you pass, you may now move to the next section. You can download resources for this section. Hello.

2. Switching Concepts Part 1

All right, so we're going to start our network basic discussion with the use of our whiteboard. Okay, so I'm going to first add our host. This is TCA. I'm also going to assign a logical address. This is a layer three address which we're going to discuss more on the next topics. But this is what we call the IP address. I'm going to assign 170, 2160 one. And this is going to be used and identifier on the layer three as we send traffic over the network. Now we also have another address. This is for the physical. Sometimes we call it hardware address. But the real name for this is Mac address. Now the Mac address has a different format versus the IP address. It’s using 48 bit or twelve hexadecimal value. And I'm going to show you an example.123-45-6789 APC. There you go. So this is our Mac address. As you can see, we have twelve hexadecimal value. Now we have two parts for the Mac address. The first half, which is equivalent to six hexadecimal value. This is what we call their or the Organization unit identifier. This is the ID of the manufacturer. So manufacturers and vendors like Microsoft, intel and even F5 have their own Oui. Now the second half would be the Oui specific Identifier. This is assigned by the vendor manufacturer and this can be anything because this is just an ID of P or Unknown this is just standalone device. Obviously we specify an ID, but it cannot communicate yet because it doesn't have any other nodes to connect with or still not connected to our network. So the first thing that I am going to do is I’m going to add the second node, which is the PCB, and I'm also going to add an IP address, 172.Let me just correct this. All right, one 72160. Two is the IP address of the PCB and also I am going to connect them two together. So this is it. PCA PCB both connected together. This is already considered as network. This is the bare minimum of a network where point to point connectivity between two hosts are communicating. And let me tell you, as soon as they communicate to each other, they can now send traffic. But on our discussion, we're going to talk about layer by layer. The traffic that is sent over this wire is layer one or the physical layer of the overs. Okay, so I'm going to specify here, this is layer one. Now layer one is the transmission of raw or unstructured bits. So the transmission unit is bits and itis sent over the physical connectivity between hosts. At least in this example, it's between hosts. Later on we're going to expand our network. Right now another question and discussion is about the ports or the network cards. Is it layer one or layer two? All right, so what we discuss regarding the information we have the 170, 216 layer three operating in layer three, the Mac address. We have the 123-45-6789 ABC. This Mac address information is operating in layer two. Now here's the question. If we're talking about wire, physical and mechanical and ports, how about the network interface or the network adapter? Is it functioning as layer one or layer two? Now let's have a look. So let's say this is our network adapter, PCB network adapter. And we're also going to draw the actual port. This is where you connect your cable, your copper cable with RJ 45. Okay? This is layer one because it' sport, it's physical layer one. But inside our network adapter we have logic, gate, circuit IC, and we have chips as well. Now one of the chips we have a burning Mac address, which is our hardware address. And as I mentioned earlier, Misaddress operates in layer two. So the network adapter itself is allayer one and layer two component. And maybe someone's thinking, how about the IP address? Well, IP address is not burned in in the chip. IP address is something that is configured using your device operating system. And we're going to talk about IPad dressing as well as subletting later. All right, so this is our host, host B, communicating host to host. Now we're going to extend our network. What I'm going to do next is I'm going toad a network device in the middle and I'm going to erase the line in between and I'm going toad arrows to make look like a real switch icon. I’m also going to connect another device. This is our server. I’m going to name this server I’m also going to assign an IPad dress, going to assign 170, 2160 three. And I'm also going to provide the three hosts Mac address. Now we're not going to use the 48 bitmask address format because I'm a little lazy. Not just kidding. It’s a bit difficult to add this value. But we're still going to discuss the same concept. What I'm going to do is instead of twelve hexadecimal value, I will just shorten it to four. Okay? So for server C, the Mac address value is CCC. For PCB, the value would be BBB. For PCA, the value would be quadruple A. There you go. Another thing is I still need to assign the interface name one, the port or the interface connected to PCA.E two for PCB and E three for the server C. Okay? So this is our network. Now what we want also to learn in this discussions how this host sends traffic together and how the central device, our network device, which in this case the switch, can learn traffic from source to destination. OK, so PCA needs to send traffic to server Chow does it work? Before we talk about the learning and how traffic is being forwarded, let's introduce first the two tables. The first table that we need to introduce is called the count table, or the Content Addressable Memory table. And this is where we add or update the address of the host, as well as the mapping to the interface. We also have another table. We call this the ARP table. Now, the ARP table is where we mount theme address and the IP address of the host. Now let's start the actual operation. CA sends traffic and the Switch receive it via Ethernet One. Now, assuming everything is clear, all tables are empty, the connections are fresh, we still don’t know where to get to the destination. And look, the count table is empty. The first thing the Switch will do after receiving the traffic is add the source host information. In this case, it's PCA in the countable, it will add the megados AAA. And since it is received from interface E one, I will map it to E one. All right, so the Switch knows where the source PCA is connected. Now, since the PCA wants to send this traffic to server C, and the Switch still doesn't know where server is connected, what will the Switch do is it will broadcast traffic to all active interface, all active. In our example, the only active interfaces E one, E two, E three. But no, Switch doesn't broadcast the traffic by E one. Because this is the original traffic came from CA, is initiating the traffic from E one. So the broadcast is only applicable to Ethernet two and Ethernet three. Now, PCB by Ethernet Two is not the real destination. So you will not respond. Who will respond is server Chits will respond back to the Switch telling the switch, hey Switch, Mr. Switch, here is my information, my Mac address. And the Switch will say, okay, this is your Mac address, you're the 170 2160 three, and I’m going to map you to E three. That’s the broadcast works. It’s an announcement. The Switch tells all of the connected device who owns 170 216 three. And if there's a response, it will be added in the comp table. Now take note that as we add this information tithe comp table, it is also added to the actable because the Switch needs to know how can we map the IP address to the Mac address. So the CCC Mac address is also mapped toes well as Mac address AAA 172 dot 160. All right, so that's how it sends traffic from the source to destination. Now, if you're thinking, how about TCP? If he sends traffic to server C, is it the same? Well, yes, but there will be no broadcast anymore because Switch already figured out or identify where servers is connected. What it will do is it will just simply add Babb and map it to Ethernet Two. And also the Mac address will be added tithe Arc table, map it to 170 216 two. So that's how simple it is. Okay, so with that being said, we were able to understand how the map learning works. Now, from the real testing, let’s say you're in the real world. Everything is empty and you want to send traffic from PCA to PCC or PCB to server C. How does it work? Really well, most of the time you will do traffic test using ping or ICMP. Now, let's say we are pinging from PCA to server Chat you will experience, excuse me, is the first attempt will be unsuccessful. So the first attempt will be unsuccessful, but the succeeding attempt or attempts rather should all be successful there. Why is that? Why is the first attempt unsuccessful? Well, the reason because this is when we were doing the Mac learning. Were we forwarding layer to flooding or broadcast? This is the part that the switch still doesn’t know how to get to server C.Good. All right. Now, this is our network, right? This is where host A, B and C are connected. This is also what we called the broadcast domain and the broadcast domain. This is where our nodes reach each other via layer to connectivity. And broadcast domain is used for discovery. And you cannot send simply broadcast domain from one to the other. We’re going to talk about that later. Now it's with that being said, we talk about how map learning works, broadcast domain and this is considered our local area network.

Hide