Section 1 - Configuration

Uno cial - F5 Certi cation Exam Prep Material (../../index.
html) > F5 101 - App Delivery Fundamentals Exam Study Guide -

Created 03/06/20 (../class1.html)
Source (../../_sources/class1/modules/module1.rst.txt) | Edit on (https://github.com/f5devcentral/f5-agility-labs-cert)
Section 1 - Con guration¶
The setup and con guration of an F5 device requires a solid understanding of network
infrastructure and how networks are designed and built. It doesn’t matter if you are deploying an
F5 appliance in a private data center, an F5 Viprion chassis in a private cloud or an F5 virtual
edition in the public cloud, you need to have a mastery of networking. Even in today’s agile IT
landscape where infrastructure is code and the ability to deploy F5 infrastructure on bare metal
using F5 Declarative Onboarding (DO) or other tools like Hashicorp’s Terraform is common place,
you can’t write the code to automate the build on the network if you don’t understand how
networks work.
Objective - 1.01 Explain, compare, and contrast the OSI layers¶
1.01 – Given a set of requirements, con gure VLANs
https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-implementations-13-0-
0.html (https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-
implementations-13-0-0.html)
https://clouddocs.f5.com/cli/tmsh-reference/v13/modules/net/net-vlan.html
(https://clouddocs.f5.com/cli/tmsh-reference/v13/modules/net/net-vlan.html)
Con guring VLANs in BIG-IP
There are many di erent deployment scenarios that will each demand their own unique
con guration and this content in the TMOS Implementations link will go over a few of them. This
exam will possibly provide a deployment scenario and ask how to create or modify a VLAN to meet
the scenario requirements. An exam candidate should understand that if the setup wizard is used
in the BIG-IP GUI it is going to create two VLANs named External and Internal. This two VLAN
con guration is a simple type of deployment that can be used in labs and is a great way to
depiction the network ow in a full proxy architecture operating system like BIG-IP TMOS, but it is
not always what is needed in the real world. An exam candidate should be aware of how to create
VLANs in the GUI without using the wizard and also using TMSH Command Line. There are
examples in the F5 Clouddocs link and more on the F5 Support website. For me, VLANs should be
created on the BIG-IP with a descriptive name and tag numbers that match the descriptive name
and tag number in the connected Layer-2 switch. VLAN Tagging will not necessarily be enabled but
the tag number will be con gured in the switch and can also be con gured in the BIG-IP even with
tagging disabled.
1.01 – Assign a numeric tag to the VLAN if required
https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-routing-
administration-13-1-0/5.html#guid-23a8cd0a-ec10-49e7-82c9-dfd78b13b0d6
(https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-routing-
administration-13-1-0/5.html#guid-23a8cd0a-ec10-49e7-82c9-dfd78b13b0d6)
Assigning a tag number to the vlan
About tagged interfaces
You can create a VLAN and assign interfaces to the VLAN as single- or double-tagged interfaces.
When you assign interfaces as tagged interfaces, you can associate multiple VLANs with those
interfaces.
A VLAN tag is a unique ID number that you assign to a VLAN, to identify the VLAN to which each
packet belongs. If you do not explicitly assign a tag to a VLAN, the BIG-IP system assigns a tag
automatically. The value of a VLAN tag can be between 1 and 4094. Once you or the BIG-IP system
assigns a tag to a VLAN, any message sent from a host in that VLAN includes this VLAN tag as a
header in the message.
Important: If a device connected to a BIG-IP system interface is another switch, the VLAN tag that
you assign to the VLAN on the BIG-IP system interface must match the VLAN tag assigned to the
VLAN on the interface of the other switch.
1.01 - Determine appropriate layer 3 addressing for VLAN
Layer 3 addressing for VLAN
Normally in the OSI model, the term VLAN is a Layer 2 con guration object and IP Addressing is a
Layer 3 con guration object. What is meant by this Objective Example is when a BIG-IP has a Layer
2 VLAN con gured, it must also have an IP address on the Layer 3 IP subnet associated to that
VLAN to participate in the network communications. If there are two BIG-IP units in an HA pair each
using must have a unique IP in the IP subnet on that VLAN as well as a shared IP that will oat to
the active unit in the pair.
The only time the BIG-IP would not have an IP associated to the VLAN is if the associated VLAN
interface ports are to be used to bridge a Layer 2 VLAN through the F5 device. This is a rare
con guration case and essentially makes the BIG-IP a simple Layer 2 switch for those ports
associated to the VLAN.
VLAN association with a self IP address
Every VLAN must have a static self IP address associated with it. The self IP address of a VLAN
represents an address space, that is, the range of IP addresses pertaining to the hosts in that
VLAN. When you ran the Setup utility earlier, you assigned one static self IP address to the VLAN
external, and one static self IP address to the VLAN internal. When sending a request to a
destination server, the BIG-IP system can use these self IP addresses to determine the speci c
VLAN that contains the destination server.
The self IP address with which you associate a VLAN should represent an address space that
includes the IP addresses of the hosts that the VLAN contains. For example, if the address of one
host is 11.0.0.1 and the address of the other host is 11.0.0.2, you could associate the VLAN with a
self IP address of 11.0.0.100, with a netmask of 255.255.255.0.
1.01 - Specify if VLAN is tagged or untagged
Setting VLANs as Tagged or Untagged
There can be confusion on this topic, especially if you have a Cisco background. What F5 calls
“VLAN tagging”, Cisco calls “Trunking”. The di erence in con guration naming standards is not
what causes the confusion because regardless of the descriptive name they both mean the same
thing. The system is following the 802.1q standard and adding a 4-byte VLAN tag value to the
Ethernet frame that will allow the upstream switch as well as the BIG-IP to determine the correct
VLAN to place an incoming frame onto when received, thus providing the capability to pass more
than one VLAN’s tra c on the interface. The confusion comes in when we start to discuss Link
Aggregation. Cisco calls link aggregation a “Port Channel” and F5 calls it “Trunking”.
About untagged interfaces
You can create a VLAN and assign interfaces to the VLAN as untagged interfaces. When you
assign interfaces as untagged interfaces, you cannot associate other VLANs with those interfaces.
This limits the interface to accepting tra c only from that VLAN, instead of from multiple VLANs. If
you want to give an interface the ability to accept and receive tra c for multiple VLANs, you add
the same interface to each VLAN as a tagged interface.
About tagged interfaces
You can create a VLAN and assign interfaces to the VLAN as single- or double-tagged interfaces.
When you assign interfaces as tagged interfaces, you can associate multiple VLANs with those
interfaces.
A VLAN tag is a unique ID number that you assign to a VLAN, to identify the VLAN to which each
packet belongs. If you do not explicitly assign a tag to a VLAN, the BIG-IP system assigns a tag
automatically. The value of a VLAN tag can be between 1 and 4094. Once you or the BIG-IP system
assigns a tag to a VLAN, any message sent from a host in that VLAN includes this VLAN tag as a
header in the message.
Important: If a device connected to a BIG-IP system interface is another switch, the VLAN tag that
you assign to the VLAN on the BIG-IP system interface must match the VLAN tag assigned to the
VLAN on the interface of the other switch.
About single tagging
This gure shows the di erence between using three untagged interfaces (where each interface
must belong to a separate VLAN) versus one single-tagged interface (which belongs to multiple
VLANs).
Solutions using untagged (left) and single-tagged interfaces (right)

The con guration on the left shows a BIG-IP system with three internal interfaces, each a separate,
untagged interface. This is a typical solution for supporting three separate customer sites. In this
scenario, each interface can accept tra c only from its own VLAN.
Conversely, the con guration on the right shows a BIG-IP system with one internal interface and an
external switch. The switch places the internal interface on three separate VLANs. The interface is
con gured on each VLAN as a single-tagged interface. In this way, the single interface becomes a
tagged member of all three VLANs, and accepts tra c from all three. The con guration on the right
is the functional equivalent of the con guration of the left.
Important: If you are connecting another switch into a BIG-IP system interface, the VLAN tag that
you assign to the VLAN on the BIG-IP system must match the VLAN tag on the interface of the
other switch.
About double tagging (This functionality is rarely used in Enterprise architectural design)
For BIG-IP systems with ePVA hardware support, the system includes support for the IEEE
802.1QinQ standard. Known informally as Q-in-Q or double tagging, this standard provides a way
for you to insert multiple VLAN tags into a single frame. This allows you to encapsulate single-
tagged tra c from disparate customers with only one tag.
Double tagging expands the number of possible VLAN IDs in a network. With double tagging, the
theoretical limitation in the number of VLAN IDs expands from 4096 to 4096x4096.
When you implement double tagging, you specify an inner tag that encapsulates all of the single-
tagged tra c. You then designate all other tags as outer tags, or customer tags (C-tags), which
serve to identify and segregate the tra c from those customers.
A common use case is one in which an internet service provider creates a single VLAN within
which multiple customers can retain their own VLANs without regard for overlapping VLAN IDs.
Moreover, you can use double-tagged VLANs within route domains or vCMP guests. In the latter
case, vCMP host administrators can create double-tagged VLANs and assign the VLANs to guests,
just as they do with single-tagged VLANs. For a vCMP guest running an older version of the BIG-IP
software, double-tagged VLANs are not available for assignment to the guest.
Note: On systems that support double tagging, if you con gure a Fast L4 local tra c pro le, you
cannot enable Packet Velocity Asic (PVA) hardware acceleration.
Objective - 1.02 Given a scenario, determine switch, router, and application connectivity
requirements¶
1.02 - Explain the function and purpose of a router, of a rewall and of a switch
https://en.wikipedia.org/wiki/Router_(computing (https://en.wikipedia.org/wiki/Router_(computing))
Routers
A router is a networking device that forwards data packets between computer networks. Routers
perform the tra c directing functions on the Internet. Data sent through the internet, such as a web
page or email, is in the form of data packets. A packet is typically forwarded from one router to
another router through the networks that constitute an internetwork (e.g. the Internet) until it
reaches its destination node.
A router is connected to two or more data lines from di erent IP networks. When a data packet
comes in on one of the lines, the router reads the network address information in the packet
header to determine the ultimate destination. Then, using information in its routing table or routing
policy, it directs the packet to the next network on its journey.
Firewalls
In computing, a rewall is a network security system that monitors and controls incoming and
outgoing network tra c based on predetermined security rules. A rewall typically establishes a
barrier between a trusted internal network and untrusted external network, such as the Internet.
Switches
A switch is a device in a computer network that connects other devices together. Multiple data
cables are plugged into a switch to enable communication between di erent networked devices.
Switches manage the ow of data across a network by transmitting a received network packet only
to the one or more devices for which the packet is intended. Each networked device connected to
a switch can be identi ed by its network address, allowing the switch to direct the ow of tra c
maximizing the security and e ciency of the network.
A switch is more intelligent than an Ethernet hub, which simply retransmits packets out of every
port of the hub except the port on which the packet was received, unable to distinguish di erent
recipients, and achieving an overall lower network e ciency.
An Ethernet switch operates at the data link layer (layer 2) of the OSI model to create a separate
collision domain for each switch port. Each device connected to a switch port can transfer data to
any of the other ports at any time and the transmissions will not interfere.[a] Because broadcasts
are still being forwarded to all connected devices by the switch, the newly formed network
segment continues to be a broadcast domain. Switches may also operate at higher layers of the
OSI model, including the network layer and above. A device that also operates at these higher
layers is known as a multilayer switch.
Segmentation involves the use of a switch to split a larger collision domain into smaller ones in
order to reduce collision probability, and to improve overall network throughput. In the extreme
case (i.e. micro-segmentation), each device is located on a dedicated switch port. In contrast to an
Ethernet hub, there is a separate collision domain on each of the switch ports. This allows
computers to have dedicated bandwidth on point-to-point connections to the network and also to
run in full-duplex mode. Full-duplex mode has only one transmitter and one receiver per collision
domain, making collisions impossible.
The network switch plays an integral role in most modern Ethernet local area networks (LANs). Mid-
to-large sized LANs contain a number of linked managed switches. Small o ce/home o ce
(SOHO) applications typically use a single switch, or an all-purpose device such as a residential
gateway to access small o ce/home broadband services such as DSL or cable Internet. In most of
these cases, the end-user device contains a router and components that interface to the particular
physical broadband technology. User devices may also include a telephone interface for Voice
over IP (VoIP).
1.02 - Interpret network diagrams
Interpret network diagrams
Network diagrams visualize the components involved in a computer network and their
connections, which can include a wide variety of both generic and speci c symbols.
An example may look like this:
Network diagrams will be used on this exam to represent question scenarios and as basic
reference information for questions. The ability of a candidate to assess the presented diagrams,
comprehend the information they provide and apply the information to the questions is critical.
Objective - 1.03 Given a set of requirements, assign IP addresses¶
1.03 - Given a set of requirements, assign IP addresses
administration-13-0-0/5.html (https://techdocs.f5.com/kb/en-us/products/big-
ip_ltm/manuals/product/tmos-routing-administration-13-0-0/5.html)
Assigning IP Addresses
con guration and this content in the Techdocs will explain the types of IP addresses needed by the
BIG-IP system. This exam will possibly provide a deployment scenario and ask how to assign IP
addresses to the BIG-IP system. BIG-IP systems can have multiple IP addresses because the
system can and usually does have a presence on multiple networks. The out-of-band management
interface requires an IP address. The BIG-IP will have an IP address on each VLAN it is con gured
to participate on as well as a oating IP, if it is a part of an HA pair. This was discussed in section
1.01 of this document. A functional IP address may have to be determined from a diagram that may
re ect an IP subnet for each network. The candidate should be able to determine available IP
addresses from a given subnet.
1.03 - Interpret address and subnet relationships
https://www.cisco.com/c/en/us/support/docs/ip/routing-information-protocol-rip/13788-3.html
(https://www.cisco.com/c/en/us/support/docs/ip/routing-information-protocol-rip/13788-3.html)
IP subnets and addresses
A network mask helps you know which portion of the address identi es the network and which
portion of the address identi es the node. Class A, B, and C networks have default masks, also
known as natural masks, as shown here:
A network mask helps you know which portion of the address identi es the network and which
portion of the address identi es the node. Class A, B, and C networks have default masks, also
known as natural masks, as shown here:
Class A: 255.0.0.0
Class B: 255.255.0.0
Class C: 255.255.255.0
An IP address on a Class A network that has not been subnetted would have an address/mask pair
similar to: 8.20.15.1 255.0.0.0. To see how the mask helps you identify the network and node parts
of the address, convert the address and mask to binary numbers.
8.20.15.1 = 00001000.00010100.00001111.00000001
255.0.0.0 = 11111111.00000000.00000000.00000000
Once you have the address and the mask represented in binary, then identifying the network and
host ID is easier. Any address bits that have corresponding mask bits set to 1 represent the network
ID. Any address bits that have corresponding mask bits set to 0 represent the node ID.
1000. 10100. 1111.

8.20.15.1 = 00000001
255.0.0.0 = 00000000
11111111. 0. 0.

Net id Host id
Understanding Subnetting
Subnetting allows you to create multiple logical networks that exist within a single Class A, B, or C
network. If you do not subnet, you are only able to use one network from your Class A, B, or C
network, which is unrealistic.
Each data link on a network must have a unique network ID, with every node on that link being a
member of the same network. If you break a major network (Class A, B, or C) into smaller subnets,
it allows you to create a network of interconnecting subnets. Each data link on this network would
then have a unique network/sub-network ID. Any device, or gateway, connecting n
networks/subnets has n distinct IP addresses, one for each network / sub-network that it
interconnects. In order to subnet a network, extend the natural mask using some of the bits from
the host ID portion of the address to create a sub-network ID. For example, given a Class C
network of 204.17.5.0, which has a natural mask of 255.255.255.0, you can create subnets in this
manner:
11001100. 10001. 101.

204.17.5.0 00000000
255.255.255.224 11100000
11111111. 11111111. 11111111.
subnet
By extending the mask to be 255.255.255.224, you have taken three bits (indicated by “sub”) from
the original host portion of the address and used them to make subnets. With these three bits, it is
possible to create eight subnets. With the remaining ve host ID bits, each subnet can have up to
32 host addresses, 30 of which can actually be assigned to a device since host ids of all zeros or
all ones are not allowed (it is very important to remember this). So, with this in mind, these subnets
have been created.
204.17.5.0 255.255.255.224 host address range 1 to 30

1.03 - Understand public/private, multicast addressing, and broadcast
https://tools.ietf.org/html/rfc1918 (https://tools.ietf.org/html/rfc1918)
Public and Private IP addresses
This link to RFC1918 describes address allocation for private internets. In summary, IPv4 has a
relatively small number of available IP addresses, when you think about every IP addressable node
in the world. To initially try to relieve the pressure on the available IP address space the RFC1918
set the standard for Private IP addresses. This basically provided the ability for a few ranges of IP
addresses to be reserved for private networks. Which meant that since they were not routed
publicly on the Internet, the reserved private IP address ranges could be used within each private
internet or what is referred to as an intranet without a ecting the rest of the Internet. The IP
address subnets that are routed on the Internet are considered public IP space and these reserved
IP ranges are considered private.
RFC1918 - Private Address Space
The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP
address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 pre x)
172.16.0.0 - 172.31.255.255 (172.16/12 pre x)
192.168.0.0 - 192.168.255.255 (192.168/16 pre x)
We will refer to the rst block as “24-bit block”, the second as “20-bit block”, and to the third as “16-
bit” block. Note that (in pre-CIDR notation) the rst block is nothing but a single class A network
number, while the second block is a set of 16 contiguous class B network numbers, and third block
is a set of 256 contiguous class C network numbers.
An enterprise that decides to use IP addresses out of the address space de ned in this document
can do so without any coordination with IANA or an Internet registry. The address space can thus
be used by many enterprises. Addresses within this private address space will only be unique
within the enterprise, or the set of enterprises which choose to cooperate over this space so they
may communicate with each other in their own private internet.
As before, any enterprise that needs globally unique address space is required to obtain such
addresses from an Internet registry. An enterprise that requests IP addresses for its external
connectivity will never be assigned addresses from the blocks de ned above.
In order to use private address space, an enterprise needs to determine which hosts do not need
to have network layer connectivity outside the enterprise in the foreseeable future and thus could
be classi ed as private. Such hosts will use the private address space de ned above. Private hosts
can communicate with all other hosts inside the enterprise, both public and private. However, they
cannot have IP connectivity to any host outside of the enterprise. While not having external
(outside of the enterprise) IP connectivity private hosts can still have access to external services via
mediating gateways (e.g., application layer gateways).
All other hosts will be public and will use globally unique address space assigned by an Internet
Registry. Public hosts can communicate with other hosts inside the enterprise both public and
private and can have IP connectivity to public hosts outside the enterprise. Public hosts do not
have connectivity to private hosts of other enterprises.
https://en.wikipedia.org/wiki/Multicast_address (https://en.wikipedia.org/wiki/Multicast_address)
Multicast Addressing
A multicast address is a logical identi er for a group of hosts in a computer network that are
available to process datagrams or frames intended to be multicast for a designated network
service. The CIDR notation for this group is 224.0.0.0/4. The group includes the addresses from
224.0.0.0 to 239.255.255.255. Address assignments from within this range are speci ed in RFC
5771.
The address range is divided into blocks each assigned a speci c purpose or behavior.
IP multicast address range Description Routable

224.0.0.0 to 224.0.0.255 Local subnetwork[1] No
224.0.1.0 to 224.0.1.255 Internetwork control Yes
224.0.2.0 to 224.0.255.255 AD-HOC block 1[2] Yes
232.0.0.0 to 232.255.255.255 Source-speci c multicast[1] Yes
233.0.0.0 to 233.251.255.255 GLOP addressing[4] Yes
234.0.0.0 to 234.255.255.255 Unicast-pre x-based Yes
239.0.0.0 to 239.255.255.255 Administratively scoped[1] Yes
Multicast addresses in IPv6 use the pre x 00::/8. IPv6 multicast addresses can be structured the
new format RFC 3306, updated by RFC 7371..
General multicast address format (new)
Bits 8 4 4 4 4 8 64 32
Field pre x 1 scope 2 reserved plen network pre x group
ID
Broadcast IP
RFC 919 de nes the need for a broadcast IP address on each LAN. This is essentially a reserved IP
address in every subnet that when used as a destination IP address would allow the sending
system to speak to everyone in the subnet at the same time. Much like an all f’s MAC address at
layer 2. The IP reserved and is always the highest IP of the subnet (example 192.168.1.255/24).
1.03 - Explain the function and purpose of NAT and of DHCP
https://support.f5.com/csp/article/K41572395 (https://support.f5.com/csp/article/K41572395)
Purpose of NAT
A Network Address Translation (NAT) is a mapping of one IP address to another IP address. This
mapping can be a translation of source, destination, or both. A NAT can be outbound or inbound.
Outbound NAT
Outbound NAT translates an internal source address to a public address. A NAT can also be used
to translate an internal node’s IP address to an Internet routable IP address.
Inbound NAT
Inbound NAT translates a public destination address to an internal address. When an external client
sends tra c to the public IP address de ned in a NAT, BIG-IP translates that destination address to
the internal node IP address.
Purpose of DHCP
The Dynamic Host Con guration Protocol (DHCP) provides con guration parameters to Internet
hosts. DHCP consists of two components: a protocol for delivering host-speci c con guration
parameters from a DHCP server to a host and a mechanism for allocation of network addresses to
hosts.
DHCP is built on a client-server model, where designated DHCP server hosts allocate network
addresses and deliver con guration parameters to dynamically con gured hosts. Throughout the
remainder of this document, the term “server” refers to a host providing initialization parameters
through DHCP, and the term “client” refers to a host requesting initialization parameters from a
DHCP server.
A host should not act as a DHCP server unless explicitly con gured to do so by a system
administrator. The diversity of hardware and protocol implementations in the Internet would
preclude reliable operation if random hosts were allowed to respond to DHCP requests. For
example, IP requires the setting of many parameters within the protocol implementation software.
Because IP can be used on many dissimilar kinds of network hardware, values for those
parameters cannot be guessed or assumed to have correct defaults. Also, distributed address
allocation schemes depend on a polling/defense mechanism for discovery of addresses that are
already in use. IP hosts may not always be able to defend their network addresses, so that such a
distributed address allocation scheme cannot be guaranteed to avoid allocation of duplicate
network addresses.
DHCP supports three mechanisms for IP address allocation. In “automatic allocation”, DHCP
assigns a permanent IP address to a client. In “dynamic allocation”, DHCP assigns an IP address to
a client for a limited period of time (or until the client explicitly relinquishes the address). In “manual
allocation”, a client’s IP address is assigned by the network administrator, and DHCP is used simply
to convey the assigned address to the client. A particular network will use one or more of these
mechanisms, depending on the policies of the network administrator.
Dynamic allocation is the only one of the three mechanisms that allows automatic reuse of an
address that is no longer needed by the client to which it was assigned. Thus, dynamic allocation is
particularly useful for assigning an address to a client that will be connected to the network only
temporarily or for sharing a limited pool of IP addresses among a group of clients that do not need
permanent IP addresses. Dynamic allocation may also be a good choice for assigning an IP
address to a new client being permanently connected to a network where IP addresses are
su ciently scarce that it is important to reclaim them when old clients are retired. Manual
allocation allows DHCP to be used to eliminate the error-prone process of manually con guring
hosts with IP addresses in environments where (for whatever reasons) it is desirable to manage IP
address assignment outside of the DHCP mechanisms.
The format of DHCP messages is based on the format of BOOTP messages, to capture the BOOTP
relay agent behavior described as part of the BOOTP speci cation [7, 21] and to allow
interoperability of existing BOOTP clients with DHCP servers. Using BOOTP relay agents eliminates
the necessity of having a DHCP server on each physical network segment.
https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-13-1-
0/19.html (https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-
implementations-13-1-0/19.html)
Managing IP addresses for DHCP clients
When you want to manage Dynamic Host Con guration Protocol (DHCP) client IP addresses, you
can con gure the BIG-IP system to act as a DHCP relay agent. A common reason to con gure the
BIG-IP system as a DHCP relay agent is when the DHCP clients reside on a di erent subnet than
the subnet of the DHCP servers.
About the BIG-IP system as a DHCP relay agent
A BIG-IP virtual server, con gured as a Dynamic Host Con guration Protocol (DHCP) type, provides
you with the ability to relay DHCP client requests for an IP address to one or more DHCP servers,
available as pool members in a DHCP pool, on di erent +virtual local area networks (VLANs). The
DHCP client request is relayed to all pool members, and the replies from all pool members are
relayed back to the client.
A sample DHCP relay agent con guration
For example, a DHCP client sends a broadcast message to the destination IP address
255.255.255.255, which is the destination address con gured on the virtual server. A DHCP type
virtual server automatically uses port 67 for an IPv4 broadcast message or port 547 for an IPv6
broadcast message. The BIG-IP virtual server receives this message on the VLAN with self IP
address 10.20.0.1 and relays the DHCP request to all DHCP servers: 10.10.0.3 and 10.10.0.7.
All DHCP servers provide a DHCP response with available IP addresses to the BIG-IP virtual server,
which then relays all responses to the client. The client accepts and uses only one of the IP
addresses received.
Note: In this example, there is no hop between the DHCP client and the BIG-IP relay agent.
However, a common topology is one that includes this hop, which is often another BIG-IP system.
1.03 - Determine valid address IPv6
http://www.ciscopress.com/articles/article.asp?p=2803866
(http://www.ciscopress.com/articles/article.asp?p=2803866)
IPv6
This Cisco Press link is better reading than the RFC2373 for a clear understanding of IPv6 address
representation. I doubt that you will be required to know how to do IPv6 subnetting or any in depth
IP calculations during this exam but being able to recognize valid representations of IPv6
addresses will be essential. You should familiarize yourself with IPv6. Remember that the BIG-IP
operating system is native IPv6.
IPv6 addresses are 128 bits in length and written as a string of hexadecimal digits. Every 4 bits can
be represented by a single hexadecimal digit, for a total of 32 hexadecimal values. The
alphanumeric characters used in hexadecimal are not case sensitive; therefore, uppercase and
lowercase characters are equivalent. Although IPv6 address can be written in lowercase or
uppercase, RFC 5952, A Recommendation for IPv6 Address Text Representation, recommends that
IPv6 addresses be represented in lowercase. As described in RFC 4291, the preferred form is
x:x:x:x:x:x:x:x. Each x is a 16-bit section that can be represented using up to four hexadecimal digits,
with the sections separated by colons.
Objective - 1.04 State the service that ARP provides¶
1.04 - Identify a valid MAC address
https://en.wikipedia.org/wiki/MAC_address (https://en.wikipedia.org/wiki/MAC_address)
MAC Address
A media access control address (MAC address) is a unique identi er assigned to a network
interface controller (NIC) for use as a network address in communications within a network
segment. This use is common in most IEEE 802 networking technologies, including Ethernet, Wi-Fi,
and Bluetooth. Within the Open Systems Interconnection (OSI) network model, MAC addresses are
used in the medium access control protocol sublayer of the data link layer. As typically
represented, MAC addresses are recognizable as six groups of two hexadecimal digits, separated
by hyphens, colons, or without a separator. In hexadecimal the broadcast address would be
FF:FF:FF:FF:FF:FF.
MAC addresses are primarily assigned by device manufacturers and are therefore often referred to
as the burned-in address, or as an Ethernet hardware address, hardware address, and physical
address. Each address can be stored in hardware, such as the card’s read-only memory, or by a
rmware mechanism. Many network interfaces however support changing their MAC address. The
address typically includes a manufacturer’s organizationally unique identi er (OUI). MAC addresses
are formed according to the principles of two numbering spaces based on Extended Unique
Identi ers (EUI) managed by the Institute of Electrical and Electronics Engineers (IEEE)
1.04 - De ne ARP and explain what it does
http://linux-ip.net/html/ether-arp.html (http://linux-ip.net/html/ether-arp.html)
ARP
ARP de nes the exchanges between network interfaces connected to an Ethernet media segment
in order to map an IP address to a link layer address on demand. Link layer addresses are
hardware addresses (although they are not immutable) on Ethernet cards and IP addresses are
logical addresses assigned to machines attached to the Ethernet. Link layer addresses may be
known by many di erent names: Ethernet addresses, Media Access Control (MAC) addresses, and
even hardware addresses.
Address Resolution Protocol (ARP) exists solely to glue together the IP and Ethernet networking
layers. Since networking hardware such as switches, hubs, and bridges operate on Ethernet
frames, they are unaware of the higher layer data carried by these frames. Similarly, IP layer
devices, operating on IP packets need to be able to transmit their IP data on Ethernets. ARP
de nes the conversation by which IP capable hosts can exchange mappings of their Ethernet and
IP addressing.
ARP is used to locate the Ethernet address associated with a desired IP address. When a machine
has a packet bound for another IP on a locally connected Ethernet network, it will send a broadcast
Ethernet frame containing an ARP request onto the Ethernet. All machines with the same Ethernet
broadcast address will receive this packet. If a machine receives the ARP request and it hosts the
IP requested, it will respond with the link layer address on which it will receive packets for that IP
address.
Once the requestor receives the response packet, it associates the MAC address and the IP
address. This information is stored in the ARP cache.
1.04 - State the purpose of a default gateway
https://en.wikipedia.org/wiki/Default_gateway (https://en.wikipedia.org/wiki/Default_gateway)
Default Gateway
A default gateway is the node in a computer network using the internet protocol suite that serves
as the forwarding host (router) to other networks, when no other route speci cation matches the
destination IP address of a packet.
Objective - 1.05 Given a scenario, establish required routing¶
1.05 - Given a scenario, establish required routing
Possible Required Routing
con guration and when deploying the BIG-IP system or adding to the network con guration of the
system additional routes may be needed for proper communications. This exam will possibly
provide a deployment scenario and ask what additional routes need to be added to the BIG-IP’s
con guration for the deployment to work correctly.
1.05 - Explain why a route is needed

administration-13-1-0/10.html (https://techdocs.f5.com/kb/en-us/products/big-
ip_ltm/manuals/product/tmos-routing-administration-13-1-0/10.html)
Routing and Why Routes Are Needed
Routing is the process of selecting a path for tra c between networks or across multiple networks.
If a network device needs to communicate with another device o of its local area network (LAN), it
must know a way to get there. For a node with a single network interface on a LAN, it will normally
just be to the router acting as a default gateway for the IP subnet. But some network devices have
multiple network interfaces on di erent networks to use or have the responsibility of routing tra c
in the network and the next hop to get to a particular destination may be out a particular interface.
The list of which way to go to get to the di erent destination IP addresses is known as a route
table. Static routes can be added to a systems route table which will allow it to know which way to
go to get to all of the IP subnets in a network, but the management of such a large table would be
daunting and very ine cient. And if a device failed in the path to a destination, the system would
lose communications with the destination until the path recovered or was manually edited by an
administrator to use a di erent path that may be available. This is where dynamic routing attempts
to solve the administrative ine ciency problem by constructing routing tables automatically, based
on information learned by routing protocols. This allows devices on the network to act nearly
autonomously in avoiding network failures and blockages.
The BIG-IP system may need to have static routes de ned to make tra c ow out a particular
network interface rather than to the default gateway to reach the intended destination. An example
would be needing to monitor an application or node that is not on the locally attached subnets of
the system and the default gateway has no path to the destination but a separate router on
another local subnet can reach the destination.
By enabling and con guring any of the BIG-IP advanced routing modules, you can con gure
dynamic routing on the BIG-IP system. You enable one or more advanced routing modules, as well
as the Bidirectional Forwarding Detection (BFD) protocol, on a per-route-domain basis. Advanced
routing module con guration on the BIG-IP system provides these functions:
Dynamically adds routes to the Tra c Management Microkernel (TMM) and host route tables.
Advertises and redistributes routes for BIG-IP virtual addresses to other routers.
When BFD is enabled, detects failing links more quickly than would normally be possible using
the dynamic routing protocols’ own detection mechanisms.
The BIG-IP advanced routing modules support these protocols.
Dynamic routing protocols
Protocol Description Daemon IP version

Name supported
BFD Bidirectional Forwarding Detection is a protocol that oamd IPv4 and
detects faults between two forwarding engines IPv6
connected by a link. On the BIG-IP system, you can
enable the BFD protocol for the OSPFv2, BGP4, and IS-
IS dynamic routing protocols speci cally.
BGP4 Border Gateway Protocol (BGP) with multi-protocol bgpd IPv4 and
extension is a dynamic routing protocol for external IPv6
networks that supports the IPv4 and IPv6 addressing
formats.
IS-IS Intermediate System-to-Intermediate System (IS-IS) is isisd IPv4 and
a dynamic routing protocol for internal networks, based IPv6
on a link-state algorithm.
OSPFv2 The Open Shortest Path First (OSPF) protocol is a ospfd IPv4
dynamic routing protocol for internal networks, based
on a link-state algorithm.
OSPFv3 The OSPFv3 protocol is an enhanced version of ospf6d IPv6
OSPFv2.
PIM The Protocol Independent Multicast (PIM) protocol is a pimd IPv4 and
dynamic routing protocol for multicast packets from a IPv6
server to all interested clients.
RIPv1/RIPv2 Routing Information Protocol (RIP) is a dynamic routing ripd IPv4
protocol for internal networks, based on a distance-
vector algorithm (number of hops).
RIPng The RIPng protocol is an enhanced version of RIPv2. ripngd IPv6
1.05 - Explain network hops
Network Hops
Network hops refers to the number of networking devices between the sending unit and the nal
destination of the communication. Some or all of these devices can make changes to the datagram
in the ow and some dynamic routing protocols use hop count as a metric in determining the best
path.
1.05 - Given a destination IP address and current routing table, identify a route to be used
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-
2003/cc779122(v=ws.10 (https://docs.microsoft.com/en-us/previous-versions/windows/it-
pro/windows-server-2003/cc779122(v=ws.10))?redirectedfrom=MSDN
Route Tables
Every computer that runs TCP/IP makes routing decisions. The IP routing table controls these
decisions. To display the IP routing table on computers running Windows Server 2003 operating
systems, you can type “route print” at a command prompt.
The following table shows an example of an IP routing table. This example is for a computer
running Windows Server 2003, Standard Edition with one 100 megabit per second (Mb/s) network
adapter and the following con guration:
IP address: 10.0.0.169
Subnet mask: 255.0.0.0
Default gateway: 10.0.0.1
The routing table is built automatically, based on the current TCP/IP con guration of your
computer. Each route occupies a single line in the displayed table. Your computer searches the
routing table for an entry that most closely matches the destination IP address.
Your computer uses the default route if no other host or network route matches the destination
address included in an IP datagram. The default route typically forwards an IP datagram (for which
there is no matching or explicit local route) to a default gateway address for a router on the local
subnet. In the previous example, the default route forwards the datagram to a router with a
gateway address of 10.0.0.1.
Because the router that corresponds to the default gateway contains information about the
network IDs of the other IP subnets within the larger TCP/IP Internet, it forwards the datagram to
other routers until the datagram is eventually delivered to an IP router that is connected to the
speci ed destination host or subnet within the larger network.
The following sections describe each of the columns displayed in the IP routing table: network
destination, netmask, gateway, interface, and metric.
Network destination
The network destination is used with the netmask to match the destination IP address. The
network destination can range from 0.0.0.0 for the default route through 255.255.255.255 for the
limited broadcast, which is a special broadcast address to all hosts on the same network segment.
Gateway
The gateway address is the IP address that the local host uses to forward IP datagrams to other IP
networks. This is either the IP address of a local network adapter or the IP address of an IP router
(such as a default gateway router) on the local network segment.
Interface
The interface is the IP address that is con gured on the local computer for the local network
adapter that is used when an IP datagram is forwarded on the network.
Metric
A metric indicates the cost of using a route, which is typically the number of hops to the IP
destination. Anything on the local subnet is one hop, and each router crossed after that is an
additional hop. If there are multiple routes to the same destination with di erent metrics, the route
with the lowest metric is selected.
Objective - 1.06 De ne ADC application objects¶
1.06 - De ne ADC application objects
https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-basics-13-0-0.html
(https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-basics-13-0-0.html)
https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-pro les-reference-13-1-
0.html (https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-pro les-
reference-13-1-0.html)
Application Delivery Controller Objects
The BIG-IP system uses con guration-based objects within the system con guration to represent
the di erent functional parts that control the ow and process of the application as it passes
through the BIG-IP. From Virtual Servers that act as the listener which takes in the inbound
connection and depicts how the tra c will be processed through the use of Pro les and then
passed to the Pool which handles the load distribution across the Pool Members made up of
Nodes that represent the application servers themselves, every object has a purpose.
Understanding all of the di erent types of objects, how they are used, and their functional purpose
will be necessary knowledge for this exam.
1.06 - De ne load balancing including intelligent load balancing and server selection
https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-basics-13-0-
0/4.html#guid-7e02015c-5f5d-4381-ab5e-086292039ba1 (https://techdocs.f5.com/kb/en-
us/products/big-ip_ltm/manuals/product/ltm-basics-13-0-0/4.html#guid-7e02015c-5f5d-4381-ab5e-
086292039ba1)
Distribution of Load
The amount of connections and utilization that an application may have coming in from its core
base of users can often far exceed the throughput capacity of a single server hosting the
application. The need for distributing the inbound requests and processing load of responses
across a group of servers running the same application or service is self-evident. The trick to
distributing the load is nding the right load balancing solution and then implementing it in the
most e ective manner. While making sure the functions of the applications are not being broken as
users are sent all across the servers in the group.
Load balancing is an integral part of the BIG-IP system. Con guring load balancing on a BIG-IP
system means determining your load balancing scenario, that is, which pool member should
receive a connection hosted by a particular virtual server. Once you have decided on a load
balancing scenario, you can specify the appropriate load balancing method for that scenario.
A load balancing method is an algorithm or formula that the BIG-IP system uses to determine the
server to which tra c will be sent. Individual load balancing methods take into account one or
more dynamic factors, such as current connection count. Because each application of the BIG-IP
system is unique, and server performance depends on a number of di erent factors, we
recommend that you experiment with di erent load balancing methods, and select the one that
o ers the best performance in your particular environment.
Default load balancing method
The default load balancing method for the BIG-IP system is Round Robin, which simply passes each
new connection request to the next server in line. All other load balancing methods take server
capacity and or status into consideration.
If the equipment that you are load balancing is roughly equal in processing speed and memory,
Round Robin method works well in most con gurations. If you want to use the Round Robin
method, you can skip the remainder of this section, and begin con guring other pool settings that
you want to add to the basic pool con guration.
BIG-IP system load balancing methods
The BIG-IP system provides several load balancing methods for load balancing tra c to pool
members.
Method Description When to use

Round This is the default load Round Robin method works well in most
Robin balancing method. Round con gurations, especially if the equipment that
Robin method passes each you are load balancing is roughly equal in
new connection request to processing speed and memory.
the next server in line,
eventually distributing
connections evenly across
the array of machines being
load balanced.
Ratio The BIG-IP system distributes These are static load balancing methods,
(member) connections among pool basing distribution on user-speci ed ratio
Ratio (node) members or nodes in a static weights that are proportional to the capacity of
rotation according to ratio the servers.
weights that you de ne. In
this case, the number of
connections that each system
receives over time is
proportionate to the ratio
weight you de ned for each
pool member or node. You
set a ratio weight when you
create each pool member or
node.
Dynamic The Dynamic Ratio methods The Dynamic Ratio methods are used
Ratio select a server based on speci cally for load balancing tra c to
(member) various aspects of real-time RealNetworks RealSystem Server platforms,
Dynamic server performance analysis. Windows platforms equipped with Windows
Ratio (node) These methods are similar to Management Instrumentation (WMI), or any
the Ratio methods, except server equipped with an SNMP agent such as
that with Dynamic Ratio the UC Davis SNMP agent or Windows 2000
methods, the ratio weights Server SNMP agent.
are system-generated, and
the values of the ratio
weights are not static. These
methods are based on
continuous monitoring of the
servers, and the ratio weights
are therefore continually
changing.
Note: To implement Dynamic

Ratio load balancing, you
must rst install and
con gure the necessary
server
software for these systems,
and then install the
appropriate performance
monitor.
Fastest The Fastest methods select a The Fastest methods are useful in
(node) server based on the least environments where nodes are distributed
Fastest number of current sessions. across separate logical networks.
(application) These methods require that
you assign both a Layer 7 and
a TCP type of pro le to the
virtual server.
Note: If the OneConnect

feature is enabled, the Least
Connections methods do not
include idle connections in
the
calculations when selecting a
pool member or node. The
Least Connections methods
use only active connections
in their calculations.
Least The Least Connections The Least Connections methods function best
Connections methods are relatively simple in environments where the servers have similar
(member) in that the BIG-IP system capabilities. Otherwise, some amount of
Least passes a new connection to latency can occur. For example, consider the
Connections the pool member or node case where a pool has two servers of di ering
(node) that has the least number of capacities, A and B. Server A has 95 active
active connections. connections with a connection limit of 100,
while server B has 96 active connections with a
much larger connection limit of 500. In this
feature is enabled, the Least
case, the Least Connections method selects
Connections methods do not
server A, the server with the lowest number of
include idle connections in
active connections, even though the server is
the
close to reaching capacity. If you have servers
with varying capacities, consider using the
Weighted Least Connections methods instead.
Least Connections methods
use only active connections
in their calculations.
Weighted Similar to the Least Weighted Least Connections methods work

Least Connections methods, these best in environments where the servers have
Connections load balancing methods di ering capacities. For example, if two servers
(member) select pool members or have the same number of active connections
Weighted nodes based on the number but one server has more capacity than the
Least of active connections. other, the BIG-IP system calculates the
Connections However, the Weighted Least percentage of capacity being used on each
(node) Connections methods also server and uses that percentage in its
base their selections on calculations.
server capacity. The
Weighted Least Connections
(member) method speci es
that the system uses the
value you specify in
Connection Limit to establish
a proportional algorithm for
each pool member. The
system bases the load
balancing decision on that
proportion and the number of
current connections to that
poolmember. For example,
member_a has 20
connections and its
connection limit is 100, so it is
at 20% of capacity. Similarly,
member_b has 20
connections and its
connection limit is 200, so it
is at 10% of capacity. In this
case,the system select
selects member_b. This
algorithm requires all pool
members to have a non-zero
connection limit speci ed.
The Weighted Least
Connections (node) method
speci es that the system
uses the value you specify in
the node’s Connection Limit
setting and the number of
current connections to a
node to establish a
proportional algorithm. This
algorithm requires all nodes
used by pool members to
have a non-zero connection
limit speci ed. If all servers
have equal capacity, these
load balancing methods
behave in the same way as
the Least Connections
methods.

feature is enabled, the
methods do not include idle
connections in the
methods use only active
connections in their
calculations.
Observed With the Observed methods, The need for the Observed methods is rare,
(member) nodes are ranked based on and they are not recommended for large pools.
Observed the number of connections.
(node) The Observed methods track
the number
of Layer 4 connections to
each node over time and
create a ratio for load
balancing.
Predictive The Predictive methods use The need for the Predictive methods is rare,
(member) the ranking methods used by and they are not recommend for large pools.
Predictive the Observed methods,
(node) where servers are rated
according to the number of
current connections.
However, with the Predictive
methods, the BIG-IP system
analyzes the trend of the
ranking over time,
determining whether a
node’s performance is
currently improving or
declining. The servers with
performance rankings that
are currently improving,
rather than declining, receive
a higher proportion of the
connections.
Least The Least Sessions method The Least Sessions method works best in
Sessions selects the server that environments where the servers or other
currently has the least equipment that you are load balancing have
number of entries in the similar capabilities.
persistence table. Use of this
load balancing method
requires that the virtual
server reference a type of
pro le that tracks persistence
connections, such as the
Source Address A nity or
Universal pro le type.
Note: The Least Sessions

methods are incompatible
with cookie persistence.
Ratio Least The Ratio Least Connections

Connections methods cause the system to
select the pool member
according to the ratio of the
number of connections that
each pool member has
active.
1.06 - Explain features of an application delivery controller
https://en.wikipedia.org/wiki/Application_delivery_controller#ADC_Vendors
(https://en.wikipedia.org/wiki/Application_delivery_controller#ADC_Vendors)
Application Delivery Controllers
A common misconception is that an Application Delivery Controller (ADC) is an advanced load-

balancer. This is not an adequate description. An ADC is a network device that helps applications
to direct user tra c in order to remove the excess load from two or more servers. In fact, an ADC
includes many OSI layer 3-7 services which happen to include load-balancing. Other features
commonly found in most ADCs include SSL o oad, Web Application Firewall, NAT64, DNS64, and
proxy/reverse proxy to name a few. They also tend to o er more advanced features such as
content redirection as well as server health monitoring.
1.06 - Explain bene ts of an application delivery controller
https://devcentral.f5.com/s/articles/6-reasons-you-need-an-application-delivery-controller-now
(https://devcentral.f5.com/s/articles/6-reasons-you-need-an-application-delivery-controller-now)
Some of the Bene ts of an ADC
An application delivery controller can solve many problems that arise in your application
environment
E ciency
An application delivery controller (ADC) can improve the e ciency of the servers for which it
manages application requests. By o oading compute intensive processing like SSL or TCP/IP
connection management an ADC reduces the overhead associated with assembling and serving
responses to application requests and makes better use of the resources (RAM, CPU, I/O) on each
server. Making your infrastructure more e cient is also a great way to “go green”.
Performance
The performance of your applications can be improved dramatically through the deployment of an
ADC. Whether it’s because of compression, caching, protocol optimizations, connection
management or intelligent load balancing algorithms, an ADC improves the overall performance of
your applications.
Reliability
If you rely on applications for business processes or as a revenue stream, the last thing you want is
for those application to be unavailable. An ADC provides reliability by ensuring that requests are
sent only to available servers, redirecting requests when a server is down for maintenance or
nally hit the wall and died.
If you’re large enough to have two data centers, an ADC with global load balancing capabilities
furthers assurance of reliability by redirecting requests from the primary data center to a secondary
in the event of a disaster - whether that’s a natural disaster (earthquake, re, ood) or man-made
(oops - was that our DS3 I just ripped out?).
Security
We’re not talking about advanced security options like web application rewalls or secure remote
access products such as an SSL VPN, we’re just talking basic security here. DDoS protection, rate
limiting, blacklisting, whitelisting, authentication, resource obfuscation, SSL, content encryption -
the bare minimum security you need to protect your applications and the servers on which they’re
deployed. An ADC provides the core security functions you need to ensure your site is safe.
Capacity
Capacity is about how much throughput, how many requests, how many users you can support. It’s
nearly impossible to support thousands of concurrent users with a single server, unless it’s one
really really really big server. You need more than one server, and in order to architect a solution
that uses a pool of servers you need something to mediate and direct those requests - to balance
the load across those servers. That means you need an ADC, because the core purpose of an ADC
is to perform load balancing and ensure that you can serve everyone who wants to be served.
Scalability
Scaling up to meet demand is di cult, doing so without re-architecting your infrastructure or

scheduling down-time is even more di cult. By including an ADC in your architecture from the very
beginning, the process becomes a simple one. Add a new server, add it to the ADC and voila!
You’ve just scaled up and can instantly support more users and more requests without requiring
downtime or moving around network cables.

Section 1 - Configuration

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Section 1 - Configuration

Uploaded by

Copyright:

Available Formats

Uno cial - F5 Certi cation Exam Prep Material (../../index.

html) > F5 101 - App Delivery Fundamentals Exam Study Guide -

Section 1 - Con guration¶

Objective - 1.01 Explain, compare, and contrast the OSI layers¶

1.01 – Given a set of requirements, con gure VLANs

Con guring VLANs in BIG-IP

1.01 – Assign a numeric tag to the VLAN if required

Assigning a tag number to the vlan

About tagged interfaces

1.01 - Determine appropriate layer 3 addressing for VLAN

Layer 3 addressing for VLAN

VLAN association with a self IP address

Setting VLANs as Tagged or Untagged

About tagged interfaces

About single tagging

Solutions using untagged (left) and single-tagged interfaces (right)

1.02 - Interpret network diagrams

Interpret network diagrams

An example may look like this:

1.03 - Given a set of requirements, assign IP addresses

1.03 - Interpret address and subnet relationships

IP subnets and addresses

1000. 10100. 1111.

11001100. 10001. 101.

204.17.5.0 255.255.255.224 host address range 1 to 30

1.03 - Understand public/private, multicast addressing, and broadcast

Public and Private IP addresses

RFC1918 - Private Address Space

10.0.0.0 - 10.255.255.255 (10/8 pre x)

172.16.0.0 - 172.31.255.255 (172.16/12 pre x)

192.168.0.0 - 192.168.255.255 (192.168/16 pre x)

IP multicast address range Description Routable

General multicast address format (new)

1.03 - Explain the function and purpose of NAT and of DHCP

Managing IP addresses for DHCP clients

About the BIG-IP system as a DHCP relay agent

A sample DHCP relay agent con guration

Objective - 1.04 State the service that ARP provides¶

1.04 - Identify a valid MAC address

1.04 - De ne ARP and explain what it does

1.04 - State the purpose of a default gateway

Objective - 1.05 Given a scenario, establish required routing¶

1.05 - Given a scenario, establish required routing

Possible Required Routing

1.05 - Explain why a route is needed

Routing and Why Routes Are Needed

The BIG-IP advanced routing modules support these protocols.

Dynamic routing protocols

Protocol Description Daemon IP version

1.05 - Explain network hops

Objective - 1.06 De ne ADC application objects¶

1.06 - De ne ADC application objects

Application Delivery Controller Objects

Default load balancing method

BIG-IP system load balancing methods

Method Description When to use

Note: To implement Dynamic

Note: If the OneConnect

Weighted Similar to the Least Weighted Least Connections methods work

Note: If the OneConnect

Note: The Least Sessions

Ratio Least The Ratio Least Connections

Application Delivery Controllers