I85PREP
⌘ K
ExtremeCloud IQ Site Engine (XIQ-SE) study materials
ExtremeCloud IQ Site Engine (XIQ-SE) study resources

ExtremeCloud IQ Site Engine (XIQ-SE): Site Engine Installation, Upgrade, and Initial Configuration

ExtremeCloud IQ Site Engine (XIQ-SE) · Work through your exam, one topic at a time.

All guide sections

Site Engine Installation, Upgrade, and Initial Configuration

Domain 2 covers standing up the server and moving it safely between releases: pre-flight checks, console configuration, the order of first-run tasks, and the supported upgrade path.

Before the first boot

  • Confirm virtualisation support and resources (vCPU, RAM, disk for the deployment tier), a second NIC if HA is planned, static addressing, forward and reverse DNS records, NTP reachability and correct time zone.
  • Decide the FQDN now. Changing it later invalidates certificates and breaks call-home configuration already pushed to devices.

Console and first-run tasks

  • The console setup menu sets hostname, IP/mask/gateway, DNS, NTP and the administrative password; everything else is done from https://.
  • Work in order: install the licence, configure server options (SMTP, syslog forwarding, session timeout), add SNMP profiles and CLI credentials, create the site hierarchy, run discovery, then schedule backups before you need one.
  • Create named admin accounts and groups immediately; the built-in admin is for build-out, not daily operation.

Upgrades

  • Read the release notes first: upgrades follow a supported path and skipping intermediate major releases is not supported - step through each required version.
  • Take a full backup and record the current version and licence state.
  • Upload the upgrade package from the UI or console, let services stop and the appliance reboot, hard-refresh the browser, and update the thick client to the same build.
  • In an HA pair, upgrade the standby, verify login and polling, fail over, then upgrade the former primary.

Worked example

A server on 22.11 must reach 24.x and the notes list 23.7 as a required hop. The sequence is: backup, upgrade to 23.7, verify discovery, polling and login, then upgrade to the 24.x target, updating clients after each hop, and only then re-enable scheduled reporting. Jumping straight to 24.x is unsupported and typically leaves the database partially migrated.

Traps that cost marks

  • Upgrading the client before the server.
  • No backup, or a backup never test-restored.
  • Ignoring disk-space and memory pre-checks.
  • Restoring a backup onto a different major release.
  • Forgetting to re-verify HA state and licences after reboot.
  • Leaving the appliance on DHCP or without NTP.