Rhombus use-case briefing

Application delivery & security

Load-balance mission services from code and run them offline

Rhombus deploys an F5 BIG-IP Virtual Edition (VE) on the kit and configures its Local Traffic Manager (LTM) from code. Kit services get one managed front door that runs disconnected once licensed.

Download the one-page brief (PDF)Request a briefing

Why it matters

Health monitors pull an unresponsive back-end from rotation, so the service stays reachable.
Operators reach kit services through stable virtual addresses instead of individual hosts.
Images and F5 extensions install from the kit's local repository, so a forward site never waits on a download.

How it works on Rhombus

The console deploys the VE with a fixed hardware identity, so its license stays tied to the same instance across redeploys.
First-boot automation sets management access and installs F5's automation extensions.
A repeatable playbook provisions LTM and builds networks, pools, health monitors and virtual servers. Running it again changes nothing.
Post-deploy checks confirm the management interface and base configuration. Redeploy rebuilds the VE from code; re-running the playbook restores services.

From deployment to results

Stage the BIG-IP image, license file and F5 extensions in the kit's offline mirror.
Deploy the BIG-IP VE from the console catalog.
Apply the LTM configuration and confirm the checks pass.
Reach services through their virtual servers; redeploy and re-apply to reset.

Defense and government use cases

Front mission applications at forward sites in denied, degraded, intermittent or limited (DDIL) conditions.
Train operators on F5 traffic management using an isolated instance they can rebuild.
Rehearse F5 configuration changes on the kit before applying them to mission systems.

Commercial use cases

Banks and enterprise teams can rehearse BIG-IP changes in isolation before a production window.
Critical infrastructure and operational technology (OT) sites can front local services where connectivity is limited.

Outcomes

Every deploy builds the BIG-IP VE the same way, from code.
A playbook re-run reports no changes when the BIG-IP matches its intended state.
Kit services answer on virtual addresses, with failed back-ends removed from rotation.

Considerations

F5 BIG-IP VE is optional and licensed separately. You supply the image and license, activated from a staged file or once online.
The current build provisions LTM only. SSL Orchestrator (SSL-O) is a separately licensed add-on and is not configured by the current build. Web application firewall, DDoS and access modules are not configured.
Health checks test only that each port answers. Encrypted traffic passes through without decryption.

Integrated tools

F5 BIG-IP VEcommercial

Commercial products are licensed as part of your configuration. Product names are trademarks of their respective owners, and their use does not imply endorsement.