FNA Edge Network Appliance

TECHNICAL OVERVIEW

April 2022
Copyrights and Trademarks
© 2022 Meta All rights reserved.

FNA: Overview | 2
Table of Contents

Copyrights and Trademarks ................................................................................................ 2

What is FNA? .................................................................................................................................... 4

Content Type and Transit.................................................................................................... 4
Latency Based Routing ........................................................................................................ 6

Key Benefits ...................................................................................................................................... 6

Qualification ..................................................................................................................................... 7

Equipment Details ......................................................................................................................... 7

Ordering & Delivery ...................................................................................................................... 9

Terms of Service Agreement ............................................................................................... 9
Ordering Requirements ....................................................................................................... 9

Equipment Replacement ......................................................................................................... 11

Network Partner Portal ........................................................................................................... 12

FNA: Overview | 3
What is FNA?
FNA is Meta’s content caching program. FNA provides Internet Service Providers (ISPs) with an
efficient means of delivering Meta’s services from within their network. Upon deployment, an
ISP will offload a significant amount of Meta content from its backbone network and vastly
improve the Meta user experience.

The FNA kit consists of a Top of Rack (ToR) switch and from two to twenty servers. The
hardware is suitable for deployment in data centers, colocation facilities, and outside plant
environments (the industry standard 19-inch form factor allows integration into most network
environments).

Content Type and Transit

Most Meta traffic consists of static content, such as images, video and live streaming. Without
FNA, this content is delivered via peering or transit routes connected to FB-CDN AS32934.

FNA: Overview | 4
FNA deployments allow ISPs to directly deliver Meta’s services, including static content, from
within their data centers, head-ends, or Points of Presence (PoPs). This approach reduces round-
trip time (RTT) for Meta content and reduces the overall utilization of the ISP's backbone network
and traffic. In a typical FNA deployment, approximately 70 to 80% of Meta traffic can be offloaded
from the ISP's backbone network with only a single FNA node.

FNA interoperates with networks using the following methods common to most content caching
applications:

• The external Border Gateway Protocol (eBGP) is used to signal subscriber prefixes
• Cache-miss / cache-fill and data monitoring is handled via the network operator's peering
sessions with Meta (where available)
• FNA prefers to cache-fill via IPv6, even when a client request is received via IPv4

As Meta traffic volume grows, FNA can become essential to an ISP's capacity management
strategy.

FNA: Overview | 5
Latency Based Routing
Upon installation of an FNA kit, a latency-based routing test is performed to optimize traffic
routing. This test evaluates the round-trip latency of the specific ISP network. This is
accomplished by sending a comprehensive sample (every FNA servable netblock) of static
content from the netblock population announced. This test makes it possible for Meta to
observe and construct the most optimal routing path. In this manner, each FNA deployment is
custom fit to the ISP's needs.

The accuracy of the latency-based routing service is dependent upon the percentage of FNA
servable netblocks announced. Providing a large percentage of the servable netblock
population allows the service to construct more optimal (low latency) routing paths. A small
percentage of netblocks announced (for example, a test netblock) does not allow the test to
function as intended, and traffic may be routed in a seemingly random course. Therefore, it is
important that every FNA servable netblock is advertised to Meta to optimize routing paths for
the FNA deployment.

Key Benefits

The following are some immediate benefits an ISP can expect after deploying an FNA kit
within their network facility:

• Meta content delivery latency reduction

◦ Reduction in page load times
◦ Increase in access speed
◦ Reduction in overall RTT

• Increased backbone capacity life cycle in exchange for minimal infrastructure resources
◦ FNA offloads a significant amount of Meta traffic from an operator's backbone network
◦ Equipment footprint is relatively small regarding space and power requirements

• Greater traffic management and control

◦ Meta can actively monitor FNA nodes to mitigate most network failure scenarios

FNA: Overview | 6
• Utilization of system and network monitoring tools
◦ The Network Partner Portal (NPP) enables an ISP to view operational data, such as caching
insights and peering capacity

Qualification

Meta considers these criteria when qualifying an ISP for the FNA program. If you have any
questions, contact FNA ([email protected]) for clarification.
• The ISP is considered an 'eyeball' ISP (i.e., not a transit ISP), as there is a significant number of
people directly connected to its autonomous system (AS).
• The installation site has a significant amount of Meta traffic.
• The ISP can deliver Meta content from the deployment location in an efficient manner.
• The latency for Meta content delivery installation site is above average for the region.
• The ISP can allocate the required IPv4 and IPv6 address space for the FNA kit.
• The installation site is in a developing market / high-growth region.

Equipment Details
Each deployment consists of a Top of Rack (ToR) switch and minimum two servers, augmenting
capacity is accomplished by deploying additional groups of two servers. A single node supports
up to 20 servers connected through a single ToR switch.

The following table provides summarized equipment information and facility requirements for the
hardware included with an FNA order.

FNA: Overview | 7
Equipment Notes
Equipment Notes

• A minimal installation requires at least two 10G uplinks connected

Switch to the ISP network device as a Link Aggregation Control Protocol
(LACP) group.
• Maximum uplink is either 12 x 10GE or 4 x 100G
• Recommended uplink is as many 10G ports as servers in the
cluster (up to 12), and multiple 100G for deployments with 12 or
more servers.
• When upgrading a cluster with additional servers, the switch uplink
should be upgraded as well.
• Switches occupy 1 Rack Unit. Dimensions (W x H x L): 48.3 x 4.4 x
40.64 cm
• Operating temperature: 0C to 40C

• The minimum cluster size consists of 2 servers

Servers • Deployments are scaled for 12+ months of traffic growth.
• Redundancy is built into each FNA node.
• Full N+1 redundancy is achieved through deploying a second, equal
size node at the same site, ideally connected to a different ISP
router.
• Servers occupy 2 Rack Units. Dimensions (W x H x L): 44.54 x 8.73 x
67.94 cm
• Weight: Max 24.5 kg Min 17.1 kg
• Operating temperature: 10C to 35C, above 30C system may fail or
shutdown if any fan fails

Cables and Interconnects

• Power cables are provided with each FNA kit order (AC only).
• Network cables (DAC) are provided for connectivity between each
server and the switch (standard length 3 meters).
• Uplink optical transceivers (long reach or short reach) for the FNA
switch are included.
• Fiber jumpers for uplink connectivity from the ToR switch to the
ISP router are not included.

FNA: Overview | 8
Ordering & Delivery

Terms of Service Agreement

Meta is responsible for delivery and maintenance of FNA equipment within the ISP's network.

The following outlines requirements prior to the order being confirmed and delivered:

1. Before the order is confirmed, Meta asks the ISP to review and accept Meta's Edge Terms
of Service (TOS). This agreement commits Meta to deliver and maintain the equipment at
no cost to the ISP.
2. The ISP commits to providing adequate facility resources, including power, space, cooling, and
network connectivity.

Ordering Requirements
The installation site should provide the following minimum space, power, and network
requirements for the FNA kit. Include this information when ordering in the Network Partner
Portal, URL: (https://partners.facebook.com/network).

Ordering requirements and notes

Category Requirement Notes
Routing ISP must have its own Public • You will connect to Meta’s
Autonomous System Number AS63293
(ASN) • To optimize the FNA deployment,
announce all your prefixes to the
FNA
• Prefixes may be advertised to more
than one FNA node for the purpose
of load balancing
• Each FNA requires access to AS32934
for cache-fill / cache-miss traffic
• AS32934 prefixes do not need to be
advertised to FNA
• Current implementation of FNA does
not advertise prefixes to the ISP
• FNA does not support ASN reserved

FNA: Overview | 9
 for private use (RFC 6996)
• FNA does not currently support private
/ non-routable prefixes (RFC 1918 and
RFC 6598)
• Smallest IP prefix size accepted in the
BGP session with an FNA cache are /30
for IPv4 and /64 for IPv6
• We hold a limit on the number of
prefixes allowed to be advertised to the
FNA: 50k for IPv4 and 8k for ipv6
• We do not support MD5 on FNA
IP Addressing Provide IP addressing for each • The ISP must advertise the FNA kit
FNA kit, as follows: prefixes to the internet, with no port
filtering.
Caching:
• IPv4: Public routable /26
• IPv6: Public routable /64

Router to Switch Addressing

(point to point link)
• IPv4: Public routable /29, /30,
or /31
• IPv6: Public routable /125,
/126, or /127

Space (Rack Unit) • 2RU required per server • A minimum deployment consists of 1
• 1RU required per switch switch and 2 servers, and requires 5RU

• ISP can choose between AC • Typical power draw for a minimum

Power or DC configurations. deployment with 2 servers and one
• Connect each device to 2 switch is ~0.8 kW
redundant power feeds • Typical power draw for a
deployment with 4 servers and one
switch is ~1.4 kW
• Refer to FNA Operations Guide for
more details.
Cables For AC deployments, choose the • Meta will provide AC power cables
necessary power cable type • Meta will provide switch to server
cables
• ISP is responsible for DC cabling
Uplink • Select bandwidth (10G or • Minimum uplink is 2 x 10G
100G) • Maximum uplink is 12 x 10G or 4 x
• Select optic type (SR/SR4 or 100G
LR/LR4) • FNA does not support 1G/25G/40G/50G
• Select number of uplinks ports

FNA: Overview | 10
 Provide an engineering contact Provide a name, title, email address,
who can answer technical and international phone number (we do
questions about the network not support toll free numbers)
Provide a shipping and installation Provide a name, title, email address,
contact with technical knowledge and international phone number (we
of the installation site (may be the do not support toll free numbers)
Contacts and same as the engineering contact)
Addresses
Provide a network operations Provide a name, title, email address,
center (NOC) contact and international phone number (we
do not support toll free numbers)
Provide installation site • Provide facility name and complete
information location address
• Specify a shipping address if different
from the installation address

Equipment Replacement

In the case of equipment failure, Meta will coordinate the delivery of replacement
components, and will initiate a Return Merchandise Authorization (RMA) of faulty
components from the ISP's site. If you notice that a piece of equipment is not working as
usual, you can reach out to us by creating a support ticket in the Network Partner Portal.

After the equipment has been in use for a few years, it might be necessary to replace the
switch and/or servers for new devices. This process is known as Refresh, and just like with the
initial deployment, Meta and its partners will take care of shipping the new devices to you, as
well as removing the old ones. When an FNA cluster is due for a refresh, we will reach out to
the ISP to coordinate it.

FNA: Overview | 11
Network Partner Portal
Once an ISP participates of Meta’s caching program, they
have access to the Network Partner Portal (NPP); a one-
stop solution for FNA management resources.

Some of the tools and dashboards the portal offers include:

• Request new caches and upgrades
• Track orders
• Manage your cache fleet
• Request and manage peering sessions
• Request support from our NOC
• Dashboards, metrics and information about your network
◦ Traffic snapshots for backbone offload
◦ Throughput and retransmission rates
◦ Autonomous system information
◦ Peering session status

For more details on how to use the portal, see the Portal User Guide in the Documents section
of NPP.

FNA: Overview | 12