1 25 PDF
1 25 PDF
o F5 name was originally take from the English move Twister F5 tornado related to storm.
o F5 Networks, was originally named the F5 Labs, was established in the Year of 1996.
o In the Year 1997, F5 Network launched its first product a load balancer called BIG-IP.
o F5 Networks, Inc. is an American-based company, headquartered in Seattle, Washington.
o Specializes in Application Delivery Networking (ADN) technology for delivery of web apps.
o Security, performance, availability of servers, data storage devices, and other network.
o Specializes in Application Delivery Networking (ADN) technology and cloud resources.
o Application Delivery Platform is a suite of technologies that handles application services.
o Like load balancing, security controls and traffic management in data centers and cloud.
o Application services platform role is to deliver applications reliably & securely to end users.
o ADN is suite of technologies that, when deployed together, provide application availability.
o ADN is a suite, when deployed together it is provide security, visibility, and acceleration.
o It provides products and services to help companies manage their Internet Protocol traffic.
o It provides products & services to help companies manage their file storage infrastructure.
o F5 products ensure that applications are always secure and perform the way they should.
o Ensure that applications are always secure anywhere, any time & on any device in Network.
o F5 develops software-based technology that helps companies manage their Internet traffic.
o F5 technologies focus on delivery, security, performance & availability of web applications.
o Availability of servers, cloud resources, data storage devices other networking components.
o F5 Networks is the global leader in Application Delivery Networking ADN & Load balancers.
o F5 Networks provide solutions that make applications secure, fast & available for everyone.
o F5 optimizes applications and allows them to work faster and consume the fewer resources.
https://www.f5.com/services/certification
Once you have passed Exam 101 and 201 you can then move onto becoming a technology
specialist in your chosen area. There are four main specialisms which include Local Traffic
Manager (LTM), Global Traffic Manager (GTM), Application Security Manager (ASM) and Access
Policy Manager (APM).
Load Balancer:
o Simple words load balancer is a network device that distributes traffic to other devices.
o A load balancer is a network device that distributing traffic to other network devices.
o Efficiently distributing incoming network traffic across a group of backend servers.
o Distributes client requests or network load efficiently across the multiple servers.
o A load balancer is a device that acts as a reverse proxy and distributes network traffic.
o In other words, clients connect to load balancer believing to connect to an actual server.
o Then, the load balancer contact the backend server providing the required resource.
o Load balancers are used to increase capacity concurrent users & reliability of applications.
o Solution responsible for distributing incoming HTTP requests across multiple servers.
o Hardware or software solution helps to move packets efficiently across multiple servers.
o Load balancers optimizes the use of network resources and prevents network overloads.
o Found in the network and transport layer (IP, TCP, FTP, UDP) and application layer (HTTP).
o The Load balancers are most commonly deployed when a site needs multiple servers.
o Because the volume of requests is too much for a single server to handle efficiently.
o Deploying multiple servers eliminates a single point of failure, making it more reliable.
o However, a load balancer performs advanced checks even at the application layer.
o It performs three interrelated functions; monitoring hosts, acting as proxy & load balancing.
Forward Proxy:
o Takes origin connections from intranet clients & connect to servers outside on internet.
o Forward proxy takes requests from an internal LAN network & forwards them Internet.
o Sometimes, forward proxy may even serve the requesting client with cached information.
o When end user web requests are forwarded to a proxy before going out to the internet.
o And responses go back through the proxy and then back to the user for privacy & control.
o Main purpose of forward proxy server is to help users access the servers over the internet.
o Forward Proxy Server is the most popular proxy mode and it present in almost all networks.
o FP, which forward the request from the intranet clients (browser) to the internet servers.
Half Proxy:
With a Half-Proxy, a client will connect to the proxy and the proxy will establish the session with
the servers. The proxy will then respond back to the client with the information. After that
initial connection is set up, the rest of the traffic with go right through the proxy to the back-
end resources. The proxy may do things like L4 port switching, routing or NAT’ing but at this
point it is not doing anything intelligent other than passing traffic. Basically, the half-proxy sets
up a call and then the client and server does their thing. For protocols like streaming protocols,
you’ll have the initial set up but instead of going through the proxy for the rest of connections,
the server will bypass the proxy and go straight to the client. This is so don’t waste resources on
the proxy for something that can be done directly server to client.
Message Description
Syn Used to initiate and establish a connection. It also helps you to synchronize
sequence numbers between devices.
ACK Helps to confirm to the other side that it has received the SYN.
SYN-ACK SYN message from local device and ACK of the earlier packet.
FIN Used to terminate a connection.
Load Balancer:
o Simple words load balancer is a network device that distributes traffic to other devices.
o A load balancer is a network device that distributing traffic to other network devices.
o Efficiently distributing incoming network traffic across a group of backend servers.
o Distributes client requests or network load efficiently across the multiple servers.
o A load balancer is a device that acts as a reverse proxy and distributes network traffic.
o In other words, clients connect to load balancer believing to connect to an actual server.
o Then, the load balancer contact the backend server providing the required resource.
o Load balancers are used to increase capacity concurrent users & reliability of applications.
o Solution responsible for distributing incoming HTTP requests across multiple servers.
o Hardware or software solution helps to move packets efficiently across multiple servers.
o Load balancers optimizes the use of network resources and prevents network overloads.
o Found in the network and transport layer (IP, TCP, FTP, UDP) and application layer (HTTP).
o The Load balancers are most commonly deployed when a site needs multiple servers.
o Because the volume of requests is too much for a single server to handle efficiently.
o Deploying multiple servers eliminates a single point of failure, making it more reliable.
o However, a load balancer performs advanced checks even at the application layer.
o It performs three interrelated functions; monitoring hosts, acting as proxy & load balancing.
Forward Proxy:
o Takes origin connections from intranet clients & connect to servers outside on internet.
o Forward proxy takes requests from an internal LAN network & forwards them Internet.
o Sometimes, forward proxy may even serve the requesting client with cached information.
o When end user web requests are forwarded to a proxy before going out to the internet.
o And responses go back through the proxy and then back to the user for privacy & control.
o Main purpose of forward proxy server is to help users access the servers over the internet.
o Forward Proxy Server is the most popular proxy mode and it present in almost all networks.
o FP, which forward the request from the intranet clients (browser) to the internet servers.
Half Proxy:
With a Half-Proxy, a client will connect to the proxy and the proxy will establish the session with
the servers. The proxy will then respond back to the client with the information. After that
initial connection is set up, the rest of the traffic with go right through the proxy to the back-
end resources. The proxy may do things like L4 port switching, routing or NAT’ing but at this
point it is not doing anything intelligent other than passing traffic. Basically, the half-proxy sets
up a call and then the client and server does their thing. For protocols like streaming protocols,
you’ll have the initial set up but instead of going through the proxy for the rest of connections,
the server will bypass the proxy and go straight to the client. This is so don’t waste resources on
the proxy for something that can be done directly server to client.
TMM:
TMM is an abbreviation for Traffic Management Microkernel. TMMs are real-time software
microkernels which form the overall L4-L7 intelligence for the data plane.
HMS:
HMS is a short form of Host Management Subsystem. HMS is responsible for system
management and administration functions and runs a version of CentOS (Community
Enterprise Operating System) Linux (which includes the SELinux feature).
Administration:
Operational management is a separate component of the BIG-IP system that uses off the shelf
components & software, starting with Linux operating system. The operational management
side of BIG-IP system does not manage traffic, it provides administrative functionality through
the Linux Shell(bash), TMOS Shell (TMSH) and the BIG-IP system's graphical user interface called
the BIG-IP Configuration utility. The Linux system is used for management tasks, such as the
command line or the web GUI only. The reason for this is simple: an operating system which is
ideal for high speed traffic management operations is not ideal as a general-purpose operating
system. So, it makes sense to use a general-purpose operating system for general purpose
tasks, like management, and leave the traffic management to the operating system designed
for that purpose—TMOS.
The BIG-IP system includes the TMOS Shell (tmsh) that can be used to manage the system from
the command line. You can enter tmsh to configure the BIG-IP system and view statistics and
performance data. tmsh is the shell replacement for BIG-IP’s bigpipe command. TMOS Shell or
TMSH is very nice CLI. It is easy to configure and navigate.
On this page you require 4 steps to get Key and download F5 LTM Image
https://www.f5.com/trials/big-ip-virtual-edition
Click on First Step 1. Login or register, if you don’t have account in next page you can create a
new account if you already have account login with username and password.
Servers Option:
For Servers use small Linux OS, which require less memory and much less degree disk space are
SliTaz4 and TTYLinux.
SliTaz4:
Size: 128MB RAM/IDE HD 256MB
Root Account Password: root
SSH account: vmware
SSH password: vmware
TTYLinux:
Size: 32MB RAM/IDE HD 32MB
ROOT Account Password: root
https://www.michellelaverick.com/download/
http://www.minimalinux.org/ttylinux/Documents/single/temp.html
EVE-GUI-Server Dockers:
EVE-GUI-Server is Server-Side Docker which can be used as www, FTP, TFTP sever. It contains
the Firefox web browser and other many tools to used default username: root password: eve
TTYLinux:
ttylinux, a small GNU/Linux system available for several CPU architectures. This small system
has an 8 MB file system and runs on i486 computers within 28 MB of RAM, but provides a
complete command line environment and is ready for Internet access. To download
https://www.michellelaverick.com/download/
The column on the left represent file on local machine and the column on the right represent
files and folder on remote machine.
Save the configuration by fixing the permissions using the following command on EVE-NG.
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Add an object’ and select the Network make Type Management(Cloud0) and press Save button.
It will get the IP address from DHCP server if available or you can set static IP address. Type the
command to see IP Address: ifconfig mgmt
Unzip the folder (TTYLinux.zip) there will be three files inside, we require TTYLinux-disk1.vmdk
Now. Let’s convert the vmdk file to qcow2 extension through CLI command.
cd /opt/unetlab/addons/qemu/linux-ttylinux/
/opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 TTYLinux-disk1.vmdk hda.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
To configure HTTP web page type below command and write the HTML tags.
vi /home/thttpd/index.html
<html>
<head>
<title>This is Server 1</title>
</head>
<body>
<h1 style="color:blue;">THIS IS SERVER 1</h1>
</body>
</html>
The column on the left represent file on local machine and the column on the right represent
files and folder on remote machine.
Save the configuration by fixing the permissions using the following command on EVE-NG.
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Click on Control Panel click on Network set the IP address to Yes to get IP from DHCP server.
Tiny Core comes with an application called tce-load, which is utilized for loading Tiny Core repo
packages. If you have active Internet connection, you can use this to download and install any
package from the repo in this case we want to download openssh.
tce-load -w -i openssh
cd /usr/local/etc/init.d/
./openssh start
sudo vi /opt/bootlocal.sh
# press Esc, i to Edit
# Copy index file to webserver directory
cp /mnt/sda1/wwwsite/index.html /usr/local/httpd/bin/index.html
cd usr/local/httpd/bin
./busybox httpd -p 80 -h /usr/local/httpd/bin/
cd /usr/local/etc/init.d/
./openssh start
cd /etc/init.d/services/
./tftpd start
after restart type Tinycore Linux IP in the browser http://192.168.114.173 it will open the page.
Now you can use Tinycore Linux as Web HTTP server and SSH Server.
Images Description
F5 BIG-IP LTM Bigip-16.0.1-0.0.3
Cisco Switches i86bi_linux_l2-ipbasek9-ms.high_iron_aug9_2017b.bin
Clients Linux-slax-9.11.0 and Windows 10 64 VL19
Web Servers Linux-ttylinux, Linux-tinycore-6.4 and Windows XP
Management Cloud Management Cloud0
The next prompt will ask you if you want to use the automatic configuration, choose No.
Enter desired IP address for the management interface and click OK.
To access the BIG-IP from any network, configure a default gateway, click Yes. You will be
prompted to enter the IP address of the default gateway and click OK
With a browser on your PC, navigate to the IP address of the management interface in HTTPS
(HTTP wont’ work). Ignore the certificate warning, and the F5 LTM login page will appear. Type
username admin/Abc@admin1 the password which is set earlier through configuration.
It is asking license, which is mandatory in F5. So, click “Activate” to put the license.
All you need to start is your license code, you should have received it via email. Insert your
license key here. Paste your registration key in the “Base Registration Key” method. Then, if
your F5 appliance has Internet connectivity you can use the Automatic Activation Method.
If you are going manual, the F5 will generate a big text. You need to copy this text and paste it
on the F5 Licensing Server. To access it, simply click on the link mentioned on Step 2. The F5
website will generate a license text, and you will have to past in the box on the bottom
(“License”). Once done that, click Next to continue.
Dedicated:
For example, if we select LTM with Dedicated provisioning means LTM will block its required
resources and not allow sharing with other modules, even LTM is not using the resources. BIG-
IP allocates all the resources to this module. You won’t be able to use other modules on this
BIG-IP appliance if you use this. This setting specifies that this is the only active module. If you
select the Dedicated setting for one module, the system resets other modules to the None
(Disabled) setting.
Nominal:
Specifies that, when first enabled, a module gets the least amount of resources required. Then,
after all modules are enabled, the module gets additional resources from the portion of
remaining resources. Nominal indicates that we launch LTM with the bare minimum and
increase the resources as we need them. This setting allocates CPU, memory, and disk space in
a way that is applicable for most typical configurations.
Minimum:
Specifies that when the module is enabled, it gets the least amount of resources required. No
additional resources are ever allocated to the module. BIG-IP allocates the minimum resources
the module needs to operate, and no more than that: resources will never increase. This setting
allocates the smallest amount of CPU, memory, and disk space to the corresponding module.
None(Disabled):
This setting indicates that there is no allocated CPU, memory, or disk space. When you select
the None (Disabled) setting, the system allocates no CPU, memory, or disk space to the module.
This is a typical setting for unlicensed modules. Depending on what you select or change, the
system might require a reboot after provisioning or deprovisioning a module
User Administration:
The BIG-IP system is preconfigured with two system accounts that are for use by BIG-IP system
administrators to perform the initial BIG-IP configuration. These are the root and admin
accounts. By default, the root account only has command line access means terminal access,
and the admin account only has GUI access. The admin user can also be configured to have
command line access, but the root user cannot be configured for GUI access. The passwords for
these users are default and admin, respectively, and should be changed either at this stage of
setup or later on.
Finally:
F5 BIG-IP appliance is ready to work as LTM device, and we can configure everything we need. If
you did things right, the management page will look something like the one below. You can see
on the left that we have the LTM Module configuration page (Local Traffic).
Identification Area:
The identification area contains system identification information such as the host name, Fully
Qualified Domain Name ,management IP address, date and time. The current status of the
system and whether it is in active or standby state and Current Configuration Synchronization
State. All these are F5 BIG-IP System and User information.
F5 Logo:
Click on the logo to take you to Starting Page of F5 BIG-IP Local Traffic Manger.
Partition:
Partition is a logical container or storage area where you create a defined set of BIG-IP system
objects such as pools, nodes, profiles, and IRules. Partition is similar to local Disks C,D etc in
Windows Operating Systems. During BIG-IP system installation, the system automatically
creates a partition named Common. At a minimum, this partition contains all of the BIG-IP
objects that the system creates as part of the installation process. Until you create other
partitions on the system, all objects that you or other users create or manage automatically
reside in partition Common. Some users, such as those with the user role of Administrator, can
also create, update, and delete objects in partition Common. No user can delete partition
Common itself.
Body Area:
The body is the screen area where the configuration settings display. On right side the whole
body of the page is called Body Area which show much information of clicked menu item or list.
Menu Bar:
The menu bar, which is below the identification area, and above the body, provides links to the
additional configuration objects within each major object.
Log Out:
If you want to Log Out from the F5 BIG-IP System click on the Right-Side top Corner green
button with white link written Log out.
Assign IP Address Network Mask, Broadcast, Gateway and Name Servers click Apply.
cd /mnt/sda1/wwwsite/
sudo vi index.html
<html>
<head>
<title>This is Server 1</title>
</head>
<body style="background-color:red;">
<h1 style="color:yellow;">THIS IS SERVER 1</h1>
</body>
</html>
The next prompt will ask you if you want to use the automatic configuration, choose No.
Enter desired IP address for the management interface and click OK.
To access the BIG-IP from any network, configure a default gateway, click Yes. You will be
prompted to enter the IP address of the default gateway and click OK
With a browser on your PC, navigate to the IP address of the management interface in HTTPS
(HTTP wont’ work). Ignore the certificate warning, and the F5 LTM login page will appear. Type
username admin/Abc@admin1 the password which is set earlier through configuration.
Creating Pool:
From the F5 home page, click Local Traffic > Pools > Pool list. From the Pool List page, click
Create. Enter the following information in the New Pool page. From the Configuration drop-
down list, select Basic. In the Name field, enter a name for the pool. Optionally, in the
Description field, enter a brief description for your pool. For Health Monitors, select the
appropriate health monitor from the Available list, and move it to the Active list. You need
health monitors to ping the defined URLs at a defined interval and check whether the node is
alive. In the Resources area, select the appropriate load balancing method from the Load
Balancing Method drop-down list default Round Robin. Click the Members Tab. Click Add. Click
Node List. From the Address drop-down list, click to select the node that you want to add to the
pool. Enter the service port number. Keep the default configurations. Click Finished.
Click the Resources tab, from the Default Pool drop-down list select the pool you have created.
Click Finished.
Navigate to Server-2 Docker desktop click on WWW folder inside open html folder right click on
index.html file open with Pluma copy past below html click Save.
<html>
<head>
<title>This is Server 2</title>
</head>
<body>
<h1 style="color:blue;">THIS IS SERVER 2</h1>
</body>
</html>
Navigate to Server-3 Docker desktop click on WWW folder inside open html folder right click on
index.html file open with Pluma copy past below html click Save.
<html>
<head>
<title>This is Server 3</title>
</head>
<body>
<h1 style="color:green;">THIS IS SERVER 3</h1>
</body>
</html>
From the F5 home page, click Statistics > Dashboard> > Module Statistics > Local Traffic. In
Statistics Type in dropdown select Nodes to see the traffic in and out.
Tagged:
Tagged means the VLAN dot1q header is going to be added to the frame and sent to the
downstream device. This is normally done to trunk interfaces (Cisco terminology "Trunk") on a
switch so it knows what VLAN the frame belongs to. Tagged = 802.1q tagging means multiple
VLANS on an interface. it is possible to configure an interface as both Tagged and Untagged.
The port is tagged meaning, it is a trunk port.
Untagged:
Untagged means the frame gets sent out the port with no VLAN information. You would do this
on an access port (Cisco terminology). Untagged = 1 VLAN per interface. The ports is untagged
in this case, you are configuring an access port.
Configure Interface:
o To Configure Interfaces in F5 BIG-IP LTM with IP Addresses first need to create VLAN.
o After create VLAN in F5 BIG-IP LTM associate this VLAN with the physical interface.
o Second Create Self IP (which is an IP Address) and Associate this Self IP with the VLAN.
o Self IP is IP Addresses to be associated with VLAN which is then associated with Interface.
New Node:
Node List:
Objects Description
Status Displays the current status of the node.
Name Displays the node name. Click a name to open properties.
Description Displays descriptive text that identifies the node.
Application Displays the name of the application associated with the object.
Address Displays the IP address of the node.
FQDN Displays the fully-qualified domain name of the node.
Ephemeral Displays whether the node is an ephemeral node.
Partition/Path Specifies the partition or path to which the node belongs
Objects Description
Health Monitors Specifies the health monitors that monitor this node. Use the Move
buttons (<< and >>) to adjust monitor use.
Active Specifies health monitors that system currently uses to monitor node.
Available Specifies the health monitors that are configured on the system, and that
you can use to monitor this node.
Availability Specifies, if you activate more than one health monitor.
Requirement
All Specifies that all active health monitors must be successful before the
node is considered up.
At Least Specifies that the number of monitors you specify in Health Monitor(s)
must be successful before the node is considered up.
Node Statistics:
Pools:
o In F5 BIG-IP Local Traffic Manger Pools define logical groups of devices to send traffic to.
o Pool is logical set of devices, such as web servers, that group together to receive & process.
o Configuration object groups pool members together to receive & process network traffic.
o In F5 BIG-IP Local Traffic Manger When create pool, you assign pool members to the pool.
o Pool is a logical group of pool members which received and process traffic for Virtual Server.
o Pool can be added to virtual server using two methods, default pool options & using IRules.
Objects Description
Name Specifies the name of the pool.
Description Specifies descriptive text that identifies the pool.
Health Monitors Specifies an association between a health or performance monitor
and an entire pool rather than with individual pool members.
Active Lists the health monitors that are already assigned to the pool.
Available Lists the health monitors that are available to add to the pool.
Load Balancing Specifies the load balancing method. The default is Round Robin.
Method
Priority Group Specifies whether the system load balances traffic according to the
Activation priority number assigned to the pool member.
New Members For each pool, specifies servers that are to be members of that pool.
Node List Presents a list of existing nodes that are each defined by an IP
address, where you can choose the new member.
Service Port Specifies the service port number of the member or click Select to
select a service port from a list of available service ports.
Objects Description
Statistics Type Specifies object for which the screen displays statistics information.
Data Format Specifies how the system presents the statistics information.
Normalized Rounds values to the nearest whole number.
Unformatted Presents the actual value, including all decimal places.
Auto Refresh Automatically updates screen information at the interval you specify.
Stop Click Stop to halt the automatic update and disable Auto Refresh.
Refresh Click Refresh to update information on the screen.
Status Displays the current status of the pool or pool member.
Pool/Pool Displays a list of currently defined pool or pool members.
Member
Partition/Path Specifies partition or path to which the pool or pool member belongs
Bits Represents the cumulative number of bits that have been received from
(In) or sent to (Out) the pool or pool member.
Packets Represents the cumulative number of Ethernet packets that have been
received from (In) or sent to (Out) the pool or pool member.
Connections Represents info about connections using this pool or pool member.
Requests Displays cumulative number of requests that have been made to node.
Requests Queue Displays the depth and maximum age of the requests in the queue.
No pool members are currently available but any one of them could
become available later, with no user action required. An example of an
unavailable pool member becoming available automatically is when the
number of concurrent connections to the pool member no longer exceeds
the value defined in the pool members Connection Limit setting.
All pool members are unavailable and therefore cannot accept traffic. A
reason for a pool member being unavailable is that an associated EAV
monitor has detected that the pool member is unavailable. When pool
status is red, user action is usually required.
The status of at least one pool member is unknown, and no other pool
members are available. Sample reasons for unknown pool-member status
are: One or more pool members has no associated monitor. Monitor
results are not available yet. The pool members IP address is
misconfigured. The parent node has been disconnected from the network.