I85PREP
⌘ K
ExtremeCloud IQ Certification study materials
ExtremeCloud IQ Certification study resources

ExtremeCloud IQ Certification: Onboarding, Configuration and Device Management

ExtremeCloud IQ Certification · Work through your exam, one topic at a time.

All guide sections

Onboarding, Configuration and Device Management

Onboarding, Configuration and Device Management covers how devices enter ExtremeCloud IQ, how they are organized, and how configuration and firmware are delivered and verified.

Getting devices into inventory

  • Add devices manually or by CSV import using the serial number (and MAC where required). A device must be in the correct tenant inventory before it can connect.
  • Cloud-enabled devices initiate an outbound connection to XIQ. For APs this is often automatic once they have management connectivity; switches and routers may need the correct cloud management configuration or cloud connector.
  • If a device is already claimed in another account, onboarding fails until it is released.

States and assignment

  • A newly added device is unassigned until it is placed in a Cloud Config Group and given a Network Policy.
  • Connected means the management tunnel is up and telemetry is arriving. Assigned but disconnected points to network, DNS, firewall, or credential problems.
  • Configuration templates and firmware policies let you standardize settings and stage upgrades rather than touching each device.

Worked example

You must onboard ten branch APs with a standard SSID and firmware baseline. Reasoning: import the serial numbers into the branch tenant; create or reuse a Branch Cloud Config Group; attach the approved Network Policy; set a firmware compliance policy to the tested version; then verify each device moves from unassigned to connected and reports the expected policy and firmware. If one AP stays disconnected, check its DHCP scope, DNS resolution, and outbound firewall before changing configuration.

Traps that cost marks

  • Importing a serial number into the wrong tenant or Cloud Config Group.
  • Assuming a device is configured just because it appears in inventory; assignment and policy attachment are separate steps.
  • Ignoring firmware compliance and then troubleshooting features that depend on a newer release.
  • Forgetting that a factory reset may be needed after a failed cloud connection attempt.