Innovexus Documentation
Everything you need to deploy, operate and recover an Innovexus appliance — from the first console boot to day-two administration.
The Innovexus appliance ships as an OVA (virtual appliance) and an ISO
(bare-metal / custom-VM installer). It is a closed appliance: you manage the
operating system through a purpose-built administrator CLI on the console or SSH,
and everything else through the web interface at https://<your-fqdn>/.
These pages explain both surfaces.
Install & first-boot setup
Import the OVA or install from ISO, then walk the console setup wizard: admin password, network, time, hostname and certificate.
Workspaces & navigation
How the web console is organized: the NOC, SOC and ADMIN workspaces, the three-row header, and who sees what.
NOC workspace
Devices, groups, backups, telemetry, upgrades and network access control — with the device-side CLI snippets.
SOC workspace
Intelligence feeds, the vulnerability queue, endpoint agents, compliance and live session oversight.
Admin workspace
Identities and roles, AD/LDAP, MFA, PKI trust, the credential vault and the AAA daemons.
Appliance CLI reference
Every command available at the innovexus> prompt — service
control, diagnostics, configuration and maintenance.
RADIUS survivability & standby
The fail mode that never rejects, the switch-side critical-auth templates we ship, and the cold-standby recovery procedure.
Verified vendor support
What is verified on hardware versus templated from vendor docs — enforcement, rotation and the limits, stated plainly.
Recovery & break-glass
Lost the CLI admin password? Lost the web super admin? The recovery key and the reset chain that always gets you back in.
FIDO2, passkeys & YubiKeys
Why phishing-resistant login needs an FQDN and trusted HTTPS, how to install the appliance root CA, and what to do about a lost token.
TLS certificates & PKI
The appliance-signed certificate chain, importing your own certificate, Let’s Encrypt, and the PKI trust store.
Time, NTP & DNS
Set NTP servers, timezone and DNS at setup, from the CLI, or later from the web UI — and why the clock matters more than you think.
Backups & export
What the nightly snapshot contains, taking one on demand, and pulling it off the appliance over SCP.
Status & troubleshooting
Reading show status, what running / initiating / failed mean,
and how to diagnose “connection refused” in the browser.
Bridge Agent updates
How agent releases reach your appliance, choosing the active version for your organization, endpoint update prompts, and version compliance.
Conventions used in these docs
- The console means the appliance’s own screen — the hypervisor console window for a VM, or the attached monitor for bare metal. A few recovery operations work only there, never over the network.
- The CLI is what you reach by logging in as
adminon the console or over SSH. It is not a Linux shell — it is a fixed set of appliance commands (reference). - The web UI is
https://<your-fqdn>/, where all product features live. Web administrator accounts are separate from the CLIadminaccount. - In terminal snippets, bold text is what you type; everything else is appliance output.