Certify TMOS and F5OS Releases

Every F5 release changes something that matters to you: a TLS default, an iRule command, an APM policy element, a monitor behaviour. TMOS 17.1 is still the release most estates run, 17.5 and 21.1 are the long-term releases they are moving to – 21.1 with a rewritten 64-bit control plane – and F5OS versions its own lifecycle underneath. Certifying a release means proving, in a lab that looks like production, that your applications survive it.

How a certification runs

• Scope – the features, iRules, policies and integrations your estate actually depends on, extracted from your configurations rather than assumed.
• Lab reproduction – Virtual Editions or tenants built from your UCS archives, with anonymised data where required, so results reflect your configuration.
• Regression suite – automated functional tests per application (health monitors, persistence, SSL profiles, access policies, WAF policies) plus performance baselines against the current release.
• Integration tests – AS3 and Declarative Onboarding versions, Terraform and Ansible pipelines, BIG-IQ, Telemetry Streaming destinations and SNMP monitoring, so automation does not break on upgrade day.
• Security review – the vulnerabilities the release fixes, the ones it does not, and the hardening changes it introduces.

What you receive

A JustADC Release Certification Report: every test case with expected and actual results, a pass or fail per feature, the known issues that apply to you with their workarounds, and a recommended upgrade path – including engineering hotfix status and the F5OS version each tenant release requires.