A unified, cross-device inventory of every virtual server Versus has discovered — and, one click in, a live dashboard plus generated Ansible, AS3, and TMSH representations of that VS.
Switch the workspace switcher at the top of the sidebar to Application Delivery Controller, then open Local Traffic → Virtual Servers (URL: /applications/virtual-servers). This view aggregates virtual servers from every ADC and Cloud WAF / Bot device in inventory — F5 BIG-IP, NetScaler, and others — into one searchable list, rather than requiring you to check each device separately.
Data reflects the state of your ADCs and Cloud WAF / Bot platforms as of their last discovery run; each row's Last Sync column shows how fresh that is.
Each row shows:
Common)— until assigned—A single search box (Search VIPs, devices, or destinations...) filters the list by free text across VS name, device, and destination — there is no separate multi-field filter panel on this view.

Click any row to navigate to a dedicated detail page for that VS (not a slide-in panel) — the URL changes and a back arrow returns you to the list. The header repeats the VS name, its status badge, partition, owning device, destination, and last-sync time, and offers a Refresh Now button with a countdown to the next automatic refresh.
The page is organized into six tabs:
tmsh configuration, including full iRule source
The Overview tab is a live operational dashboard for the VS, not just a config summary:
unknown status usually means the health monitor hasn't reported a result yet, not that the backend is down — check the monitor definition and its polling interval if a member sits at unknown for longer than expected.The remaining tabs render the same virtual server as infrastructure-as-code, generated live from Versus's synced database snapshot — useful both for review and as a starting point for GitOps:
f5networks.f5_modules.bigip collection, with VS, pool, and pool-member variables filled inTenant/Application/serviceMain structure matching the VS's actual pool, monitor, and TLS configurationtmsh config block for the VS's pool and any attached iRules, including the full iRule source — useful for a quick read without opening the BIG-IP CLIEach of the Ansible and AS3 tabs offers a JSON Editor / Form Editor (or Editor / Form Editor) toggle, plus Save to Repo and Git Push actions — until saved, a banner reads Not yet saved — content is auto-generated from DB.



| Status Badge | Colour | Meaning |
|---|---|---|
| offline | Red | VS did not respond as expected at last discovery |
| unknown | Grey | No health result yet — monitor hasn’t reported, or discovery hasn’t run since the VS was added |
Exact status values reflect whatever the device's own health evaluation reports at discovery time — a VS whose pool members are all passing health checks reports differently from one that is administratively disabled.