F5 Lingo

DeenaFirst off I do not recommend doing this yourself if you have never configured an BIG-IP before because it's a lot of ground to cover. If you must configure it yourself you should be able to use the following article. One big piece to keep in mind is if you will be deploying your BIG-IP in path or out of path, by this I mean in order for your client to reach the BIG-IP and ultimately the servers does it have to go through the BIG-IP or no? If you deploy this out of path (one arm mode) this will require SNAT so if you have to preserve the client IP for the server to see that will no longer be possible.

https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-system-initial-configuration-11-6-0.html

Aside from that a gotcha after setup is making sure you record your master key otherwise your backups are useless if a failure ever occurs. I do not recommend carving out your BIG-IP into multiple route domains or partitions unless absolutely necessary because it adds unnecessary complexity, especially if you are new to BIG-IPs. The following are the sections of the BIG-IPs and a general description of what is configured in each section.

Local Traffic: This is where you configure load balancing
Network: This is where you configure all device IPs except the management interface IP, VLANs, and routing
System: This is where you configure almost everything for the management of the device such as SNMP, DNS, NTP, SSH, code upgrades, licensing, and so on.

This next article is a study guide for the BIG-IP but it might help you understand the device a bit better as well.

https://clouddocs.f5.com/training/community/f5cert/html/class1/class1.html