⚠ Estimated sizing.
Numbers below are derived from public Keysight documentation + real field deployments. Verify with Keysight Professional Services before committing to a customer SOW. Keysight does not publish official tiered sizing; every tier cell is editable to match PS guidance.
Customer Context GLOBAL
KVO Appliance CENTRAL
KVO role: centralizes CLM lifecycle, visibility fabric, and sVM orchestration across all sites. One instance serves the whole customer.
Sites MULTI-SITE
Add one card per data center / production site. Each site has its own CLM and ESXi hosts. sVMs are deployed 1-per-host.
Fleet-Wide Totals
Total sVMs Deployed—
Total Sensor vCPU—
Total Sensor RAM—
Total Sensor Disk—
Total Virtual Traffic—
Monitored VMs—
License & Components
Throughput License (Gbps)—
License Pack Option A—
License Pack Option B—
CLM Instances—
KVO Instances1
Sites—
Sizing Tier Reference EDITABLE
Defaults shown below. Edit any cell to override with Keysight PS guidance. Active tier per site is highlighted.
Per-Host Throughput
vCPU
RAM (GB)
Disk (GB)
NICs
Notes
⚠ Estimated — verify with Keysight PS.
Tier 2 (4 vCPU / 8 GB / 40 GB / 3 NICs) is calibrated against a real-world 100 Gbps production reference deployment. Other tiers are inferred.
Markdown BOM DELIVERABLE
Complete Bill of Materials with executive summary, sizing decision, license requirements, network prerequisites, and deployment checklist. Drops into email, Confluence, Jira, or SOW.
Loading...
CSV for SOW SOW
One row per component per site. Drop into Keysight SOW templates or any spreadsheet. Opens cleanly in Excel, Numbers, Google Sheets.