Velocity • Durability

16. Troubleshooting

Symptom Likely Cause/Fix
Browser shows a certificate warning on first visit. Expected: the realm uses a self-signed certificate by default. Click through it once per browser; it will not reappear on that browser.
System Performance chart (Dashboard) or an Events table spins forever and never loads rows. No telemetry/events have been generated yet in that realm; not a UI bug. The Audit Log tab (a different feed) on the same page loads correctly, confirming the page itself is working.
A tenant shows Setup Incomplete, or Create Volume fails with “The tenant holds no issued subnet address…”. The tenant is missing a setup step. Click the status chip to see the Finish setup checklist, then assign a StorageSet and create a network configuration for the tenant (see 9.2.2 and 9.2.4).
“Failed to delete tenant: Cannot delete tenant while it still owns subnets”. Delete the tenant’s network configuration on its Networking tab (and any volumes), then delete the tenant (see 9.5.5).
“Failed to create the network configuration: The usable-address window holds fewer addresses than the realm primary pool…”. The network is too small for the realm’s nodes. Widen the Network CIDR or the Address Range (see 9.2.4).
A page shows “404 Page not found” (“The page you’re looking for doesn’t exist or has been moved.”). The address does not match a Vantage page, for example a mistyped URL or an old bookmark. Click Back to Dashboard, then navigate with the sidebar.
“Add Storage” on a StorageSet says “No unassigned nodes available.” Every node in the realm is already claimed by a StorageSet. Free up nodes (remove them from their current StorageSet) or add new hardware/VPODs to the realm before retrying.
Signed in to Vantage but PanActive Manager still asks you to sign in. Expected: the two UIs keep separate sessions. Sign in to PanActive Manager with the same credentials; it will not disturb your Vantage session.
Hardware sidebar item does nothing when clicked. Expected in a virtual realm: it’s disabled by design (“Hardware is unavailable for virtual realms”). It should be active on physical VDURA hardware.
A burst of critical/warning alerts (e.g. Director-Node software processes reported down) appears in the top bar right after adding storage to a StorageSet, then clears on its own within a minute or two. Normal, transient churn while VPODs activate and Director-Node services restabilize; not necessarily a real problem. Confirm it clears rather than assuming it’s benign every time.
“Add StorageSet”/Create Volume won’t let a tenant use a StorageSet. The built-in platform tenant gets implicit, unlimited access to every StorageSet; any other tenant needs an explicit + Add StorageSet action with a Hard Quota on its own detail page first (see 9.2) before it can place volumes there.