FNA Refresh: Installation Guide
FNA Refresh: Installation Guide
INSTALLATION GUIDE
May 2019
* Please note a switch may or may not be included in your shipment dependent upon your type of refresh
** Shipment of 100G optics is dependent upon FNA traffic levels
*** Number of servers and related items will vary depending on deployment size
Below you will find the refresh options (chapter 2, sections (a) and (b)), their requirements and instructions.
Additionally, a special case scenario of a switch swap is also covered in this chapter (section (c)). Lastly, all
hardware troubleshooting actions are covered in the FNA Operations Troubleshooting Guide location on
Network Partner Portal (NPP).
Overall Requirements
1. Installation schedules and downtime must be communicated well ahead of time via NPP and email to all
concerned teams.
2. ISP is responsible for the arrangement of LOA’s for FB managed sites.
3. If setting up new physical space, rack and stack the new cluster(s) prior to draining the old cluster(s).
4. Please wait for the signal from FB to power down the old cluster(s).
5. The MSP will provide all instructions for the ERAD and COD processes.
6. For any issues or questions, please contact Facebook via the Network Partner Portal (NPP).
This Hardware Refresh requires additional space and power at the ISP location. The new cluster will be placed
adjacent to the existing equipment. The legacy cluster will be decommissioned upon successful turn-up of the
newly installed cluster. The new hardware, cluster name, IP allocations, upstream ports from ISP, are all brought
up together in parallel to the legacy cluster it is replacing. Note that the new cluster will have a new name/ID and
new IP addresses, as stated in the diagram below.
Requirements
As the name suggests, we will replace servers in batches and repeat until all the old equipment has been
completely replaced. New and old hardware, reuse IP space, reuse physical space. Replace servers or batch by
referring to old and new server serial mapping provided through NPP notification. The servers will be identified
for each phase of replacements by indication or flashing the LED lights.
Note: During the BGP transition, the cluster continues to serve from the cache without interruption to
your users. Your NOC may see BGP alarms.
Requirements
Once the gear lands, wait for notification from FB with detailed instructions and replace the servers in the first
batch. Look for old server to new server replacement mapping by label/serial numbers.
Please follow this instruction carefully to avoid any chances of duplicate IP addressing scenario:
1. Make sure the DAC cables from old servers are connected the new servers.
2. Wait for the LED signal from FB confirming the ready for next batch.
3. Repeat above until all batches have been replaced.
4. Timeline for each batch 3-4 hours.
5. Smart hands support to uninstall and reinstall servers in batches
6. Locate the serial number on new and old devices. Serial numbers can be located on the top of the server for
all generations, or on the sliding tab on the front of the server for G8 and G10 only. (Figures 2b 1 – 4)
7. The batch number will be identified for each phase of replacements. Once the gear lands, wait for notification
from FB and replace the servers in the first batch/server. Look for old server to new server replacement
mapping by label/serial numbers. Please follow this instruction carefully to avoid any chances of duplicate IP
addressing scenario.
8. For any issues or questions, please contact Facebook via the Network Partner Portal (NPP)
1) Rack Drain/Un-install
a) The Facebook deployment engineer will schedule and coordinate the drain of the old cluster.
b) The Facebook deployment engineer will confirm that the drain has been completed and instruct to
progress with the un-installation of the old hardware.
c) Uninstall the old hardware.
Figure 2c-3
Figure 2c-6
If there are any issues during the verification of your FNA installation, please refer to the troubleshooting section
of this guide or contact Facebook via the Network Partner Portal (NPP).
Figure 4-1
Figure 4-2a
The point-to-point connection is configured on the Link-Aggregation Control Protocol (LACP) interface. Make
sure the following parameters are configured as follows:
1. Set a static route to the allocated subnets via the link-aggregation interface.
2. Set the appropriate maximum transmission unit (MTU) for your router software:
3. For Cisco IOS XR router software, set the MTU to 1514. Cisco IOS SR software includes both the L2 and L3
overhead in the interface MTU command.
4. For all other router software, set the MTU to 1500.
The FNA must have internet connectivity before BGP peering can be established. The BGP peering session does
not need to be routing before the FNA has internet connectivity.
The FNA kit is preconfigured with the IP addresses that were specified in the order. If IP addresses need to be
changed at any time, refer to Section (c) of chapter.
For any issues or questions, please contact Facebook via the Network Partner Portal (NPP).
1. Use the IPv4 and IPv6 addresses originally indicated in the FNA order form.
2. (Optional) Enable Graceful Restart (GR). Enabling GR is not required, but it is recommended.
3. Enable External BGP (EGBP) Multihop.
4. Use the peering Autonomous System Number (ASN): 63293
5. Configure your router’s BGP settings.
6. FNA’s prefix should be announced to all Facebook peering connections.
7. All servable Facebook netblocks should be announced for network traffic optimization (completed by the
latency-based routing sampling).
Routes advertised to the FNA must be present in the global routing table with the same destination Autonomous
System (AS). FNA applies inbound filtering to reject the following address spaces: default route, bogons, FC 1918
Facebook’s IP, CGNAT, and prefixes smaller than /30 for IPv4 and smaller than /64 for IPv6.
After the BGP settings are saved, the FNA cluster will begin downloading application data. Within about two
business days, BGP peering will be established:
8. The connection will be coming from the 16th IP address in each allocated subnet (192.168.1.16,
2001:db8::10).
9. FNA will not advertise any routes / prefixes.
For any issues or questions, please contact Facebook via the Network Partner Portal (NPP).
Hardware Troubleshooting
For all hardware troubleshooting, please refer to the FNA Operations Troubleshooting Guide available on
NPP.
Connectivity Troubleshooting
If any issues are encountered during the creation of the USB boot disk or IP configuration, see the following
methods for general troubleshooting.
For any issues or questions, please contact Facebook via the Network Partner Portal (NPP).
1. To remove the hard drive from each server you will need to locate the red button on each server. It is located
on the left side of the server (Figure 6-1). Depress the red button. The hard drive door will open. Remove the
hard drive (Figure 6-2). It is very important to maintain each hard drive with their respective cluster
identification in a secure location prior to ERAD and COD. (Repeat step 1 for each server)
2. To remove the flash cards from each server, you will need to slide each server out of its respective cabinet. To
slide the server out of the rack, pull down tabs on the bottom of each server, there are two of them, one on
each side of the server (Figure 6-3 & 6-4). You should see a screw with a star shaped pattern when you pull
down on the tabs. Unscrew both screws in the counter clockwise direction. Should now be able to slide the
server out of the rack.
Note: A slow counter-clockwise rotation with a Philips screwdriver will unscrew if you don’t have the correct
star shaped bit.
3. Slide the server out of the cabinet. The server will catch when it is completely pulled out of the cabinet.
Locate the black tab on the top of server, toward the rear, (Figure 6-5). Lift the black tab and remove the top
cover of the server.
Figure 6-5
5. To remove the flash card(s), there are two rotating-spring loaded pins that will need to be unlocked. There
are two pins per flash card. These pins are located on the on the left side of each flashcard as shown in Figure
6-8. Lift the tab on the top of the pin and unscrew. The pins only rotate about a quarter turn to loosen.
Figure 6-8
6. Once the pins have been loosened. Pull out the flash card holder (Figure 6-9).
Figure 6-9
With the flashcard holder removed, there is a small screw holding the card in place as shown in Figure 6-10.
The screw has the similar star pattern as the screws that are on the front of each server. Use the same
method to unscrew the flashcards from the holder. Remove the flashcards (Figure 6-11). Maintain flashcards
with their respective server and cluster identification numbers for the purposes of ERAD and COD. (Repeat
steps 3-6 for each server)
For any issues or questions, please contact Facebook via the Network Partner Portal (NPP).
1. For all issues and questions at any point during the process, please contact Facebook via the Network
Partner Portal (NPP).
2. For all escalations during the process, please contact Facebook Network Appliance Operations and
Deployment via email at [email protected].