An F5 support renewal should be considered alongside the specific hardware, software version and operational role of the platform. “End of support” is not one universal date for every F5 system. F5 publishes separate lifecycle milestones for hardware and software, and the dates depend on the model or release. Before renewing, identify what you own, what support remains available and what decision the renewal needs to give you time to make.
Start with an accurate inventory
Record the appliance model or virtual edition, serial or entitlement details, BIG-IP version and maintenance release, current support contract end date, deployed modules and important dependencies. Confirm whether the service is production, test or disaster recovery, and which applications or traffic paths depend on it.
A product name alone may not be enough. Hardware and software lifecycles can differ. A system may still have a support contract while the software version has reached a separate milestone, or a particular software release may be supported only on specific hardware. Check the compatibility guidance for the exact combination.
Understand which lifecycle milestone matters
F5 describes several lifecycle stages, including End of Sale, End of New Software Support, End of Software Support, End of Support Contract Renewal, End of RMA, End of Technical Support and End of Life. These terms describe different consequences. For example, a software support milestone and the final end of technical support are not interchangeable.
F5's published policies describe general milestone rules and product-specific dates. Do not apply a generic offset to a particular appliance without checking the matching announcement or lifecycle table. The F5 product support policies and hardware lifecycle policy explain the framework. The BIG-IP software support policy provides release-specific information.
Confirm what renewal actually buys
Read the renewal proposal and the applicable support agreement. Check the period covered, the products and serial numbers included, the support tier, any renewal deadline and what happens after the contract end date. Ask whether a proposed extension is available for your exact hardware and software combination.
Do not assume that renewing support will restore software maintenance or security fixes for a release that has already passed its applicable development or support milestone. F5's policies distinguish between ongoing technical assistance and software maintenance. Verify the effect for the specific product rather than relying on a general statement about “support”.
Also confirm whether the renewal quote includes all required components and entitlements. If a third party is involved, make sure the scope, escalation path and ownership of the vendor case are clear.
Compare the realistic options
Depending on the environment, an organisation may renew, upgrade software, replace hardware, migrate a workload, redesign the relevant traffic path or retire a function that is no longer needed. These are not interchangeable options. Each depends on the application, throughput, availability, security, architecture, licensing, operational skills and approved change window.
A migration should be assessed against the existing configuration and requirements. Consider traffic flows, health checks, certificates, security policies, logging, dependencies, rollback requirements and how the change will be tested. Avoid assuming that a cloud service or another appliance is a direct replacement without validating the design.
Plan before an expiry date creates pressure
An inventory and lifecycle review give the organisation time to make an informed decision. Identify the decision owner, the business services affected, any required procurement and the resources needed for a change. If a migration is chosen, allow time for design, testing, approvals and a fallback plan.
Create a record of the decision and its assumptions. If renewal is a short-term bridge while a replacement is assessed, state who owns the next step and by when. Otherwise, a temporary renewal can become a recurring decision without a long-term plan.
Questions to ask before signing
- Which exact hardware and software versions are in scope? - What lifecycle milestone applies to each component, and where is the official date published? - What support functions continue during the proposed term? - Are software updates, fixes or replacements available under the relevant policy? - What dependencies and entitlements must be included? - What is the operational plan if the system reaches a milestone during the renewal period? - If the service will change, who owns design, testing, approval, rollback and handover?
Make the renewal a deliberate decision
A renewal can be sensible when it supports a documented operational plan. It is less useful when the organisation does not know which product or version it is renewing, what lifecycle milestone applies or what it intends to do next. Start with the inventory and the workload, then compare renewal and replacement options against business requirements.
Read what platform management should cover and how to assess an IT vendor or partner. For network assessment and delivery, see AltTab networking and connectivity.