Skip to main content

Quickstart

This is the fastest path to your first correlated problems in the Ozone Orchestrator console. Follow the six steps below and you should reach first value in about 20 minutes. It is opinionated on purpose: one happy path, no side quests. The deeper reference pages are linked at each step if you need them.

What you need
  • Access to the Ozone Orchestrator console at ozone.techforcz.com, with permission to create a registration token.
  • A hypervisor to run the appliance on: vSphere, KVM, or VirtualBox.
  • Enough headroom on that host to size the collector VM (see the installation guide).
  • Outbound TCP 443 from the collector to the Orchestrator, and the ability to open it on your firewall.

1. Get your collector image and a registration token​

Sign in to the Ozone Orchestrator console. Download the Ozone Data Collector OVA image, then generate a one-time registration token from the console. The token is what binds this appliance to your tenant, so keep it handy for step 4. It is single-use and short-lived, so generate it close to when you plan to enrol.

2. Import the OVA and size the VM​

Import the OVA into your hypervisor and size the VM for your expected device count. Do not undersize it: the collector correlates events locally, and correlation needs CPU and memory. Full sizing guidance and per-hypervisor import notes are in Installation.

3. Open outbound TCP 443 to the Orchestrator​

The collector dials out only. It never needs an inbound port from the internet. Allow outbound TCP 443 from the appliance to the Orchestrator so it can enrol, forward problems, and pull upgrades. If you route egress through a proxy, configure that too. See Firewall for the exact egress rules.

4. Enrol the collector with the one-time token​

Boot the appliance and open its operator WebUI on TCP 3000 on the LAN. Paste the registration token from step 1 to enrol. The collector completes a mutual handshake with the Orchestrator, registers itself against your tenant, and appears in the fleet view. Full details, including what to do if the token has expired, are in Enrollment.

5. Add your first devices​

You have two ways to start collecting, and you can mix them:

  • Onboarding wizard. In the collector WebUI, run the onboarding wizard to add devices actively. It walks you through credentials and reachability for SNMP, SSH, Redfish, IPMI, WinRM, virtualization platforms, cloud accounts, and more.
  • Point sources at the appliance. For passive telemetry, point your network gear at the appliance's LAN listener ports: syslog on 514/udp, SNMP traps on 162/udp, NetFlow v5 on 2055/udp, NetFlow v9 on 9995/udp, IPFIX on 4739/udp, sFlow on 6343/udp. No per-device onboarding needed for these.

The full protocol and platform catalog, along with every listener port, is in Collection Methods.

6. Watch problems appear in the Orchestrator console​

As telemetry flows in, the collector correlates raw events into deduplicated problems locally and forwards only aggregated counts and enriched problems to the Orchestrator. Open the Orchestrator console and watch problems populate. Raw telemetry stays on your network; only the correlated, enriched result crosses the boundary.

Next steps​