BIG-IP v15.1 reached End of Software Development (EoSD) and End of Technical Support (EoTS) on December 31, 2024. Make sure your BIG-IP Fleet is running v16.1 at a minimum to ensure access to technical support and software patches beyond this date. Learn more ›
BIG-IP’s newer software versions are inherently more secure and comprise innovative new security capabilities. Prioritize regularly upgrading your BIG-IP to mitigate harmful vulnerabilities and cyberthreats.
Keep your software up to date to gain access to cutting-edge capabilities and minimize risk exposure. At a minimum, we recommend implementing BIG-IP v16.1 across your BIG-IP fleet, while the latest v17.1 release will reward you with protection against evolving threats and vulnerabilities.
Reasons to upgrade:
Reasons to upgrade:
Reasons to upgrade:
Protect against sophisticated app-layer threats including malicious bots, L7 DoS, API attacks, and OWASP Top 10 attacks.
Enforce unified global access controls for users, devices, applications, and APIs to ensure secure, authorized access for both remote and internal employees.
Provide high performance decryption of inbound and outbound SSL/TLS traffic, enabling security inspections to expose threats and prevent attacks.
Automatically provision and configure BIG-IP with declarative APIs using the CI/CD and automation tools you’re familiar with.
Optimize and secure your containers and microservices by extending BIG-IP application services.
Optimize user experience and performance through full HTTP/2 proxy support, including native monitoring and session persistence.
Deploy across a diverse array of supported cloud environments with consistent services and policies.
Decrease operational costs in the cloud with significantly reduced image size, while leveraging accelerated boot procedures to reduce spin-up time and better accommodate dynamic, auto-scaling architectures.
Take advantage of acceleration technology, including SR-IOV, advanced NIC adapters, and hardware offloading to deliver greater scalability and blazing-fast user experiences.
Augment your cloud apps and environment using native security, automation, and telemetry solutions.
Achieve FIPS 140-2 Level 1, 2, and 3 compliance with an embedded software cryptographic module and integrations with physical HSMs.
Choose from multiple licensing options that align to your preferred purchasing model, including perpetual, utility, subscription, and enterprise licensing agreements.
Modernizing your BIG-IP infrastructure has never been easier. With the Journeys Migration Utility you can effortlessly modify existing BIG-IP configurations to be compatible with new physical or virtual BIG-IP instances, helping simplify and accelerate your migration experience.
It’s vital to keep track of the key lifecycle dates for your BIG-IP assets—especially End of Software Development (EoSD) and End of Technical Support (EoTS) dates. Beyond software’s EoSD date, you won’t be able to receive security patches or software fixes, and after the EoTS milestone, you won’t have access to the technical support you might need.
Key lifecycle dates for BIG-IP software versions ›
Key lifecycle dates for BIG-IP appliances ›
Note: Lifecycle information for BIG-IP Virtual Editions is aligned with the version of BIG-IP in use. For BIG-IP version 15.x, EoSD and EoTS is 31 December, 2024.
Upgrade the software on your BIG-IP appliances and VEs manually with these easy-to-follow step-by-step instructions, or learn how to automate your upgrades with BIG-IQ or Ansible in this DevCentral video.
If you need additional help planning and executing your upgrade, or performing post-upgrade verification and support, F5 Professional Services can provide expert assistance.
BIG-IP Next is the next-generation of BIG-IP software that has been purpose-built to meet the app delivery and security requirements of vast and complex app portfolios spanning core, cloud, and edge locations. It’s the same BIG-IP you know and trust, simply modernized and optimized to simplify operations, enhance performance, and strengthen security.
See an example migration with the Journeys Migration Utility.