Full Deploy and profiles
Full Deploy runs the whole sequence — build the stack, upgrade firmware, adopt to a management platform, and verify — in one guided pass, driven by a deployment profile. It’s how a network engineer packages a target configuration so an installer on site just connects and presses go.
Deployment profiles (.icxprofile)
Section titled “Deployment profiles (.icxprofile)”A deployment profile is a file (.icxprofile) that carries every decision for a
switch: the target firmware version, target stack size and topology, the
management platform and its settings, management VLAN and IP assignment, DNS and
NTP, and site details. You load one from the Welcome screen (“Load
Deployment Profile”) or by opening the file.
Once a profile is loaded, the assessment screen shows the switch’s current state side by side with the profile’s targets — firmware (Current / Needs upgrade), stack (Ready / Needs setup), and management (Configured / Needs adoption) — and offers Begin Full Deployment.
The four phases
Section titled “The four phases”Full Deploy runs these in order, and skips any phase that isn’t needed:
| Phase | Runs when | Skipped when |
|---|---|---|
| Build Stack | The profile asks for more than one unit | No stack requested (target size ≤ 1) |
| Upgrade Firmware | Current version is below the target | ”Already at or above <target>”, or no target set |
| Connect to Management | The profile names a platform | No platform in the profile |
| Verify | Always — re-reads the switch and records the final state | — |
The firmware phase is deliberate about the decision: it upgrades only when the current version is genuinely below the target. If the switch is already current it’s skipped, and if the profile’s target can’t be parsed or the current version can’t be read, the phase fails rather than pretending it succeeded.
Safe to run, safe to retry
Section titled “Safe to run, safe to retry”- Nothing is mutated until everything’s checked. Before any destructive phase, Full Deploy confirms every firmware image the upgrade path needs is present — if any are missing it stops up front with “This upgrade needs intermediate firmware image(s) that weren’t provided…”, having changed nothing.
- Retry re-runs from the top. There’s no per-phase resume — Retry Deployment runs the whole pipeline again. Already-applied configuration is re-applied, not duplicated, so a retry after a mid-run failure is safe.
- Leaving cancels it. As with the individual wizards, backing out mid-run cancels the deployment and can leave the switch inconsistent — you’re warned first.
The deployment report
Section titled “The deployment report”When Full Deploy finishes it produces a deployment report with per-phase durations, the before/after firmware versions, the SHA-256 of the firmware image that was served, the management platform, and the final switch state. An adoption that only reached “connection pending” is recorded honestly as configured, connection not yet confirmed — not as a completed adoption.
What you need
Section titled “What you need”- An
.icxprofileprepared for the switch. - The firmware file(s) the profile’s target requires, if an upgrade is part of the plan (see Upgrading firmware).
- A connected switch (serial or SSH).