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

ExtremeCloud IQ Site Engine (XIQ-SE): Wireless Management and ExtremeCloud IQ Integration

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

All guide sections

Wireless Management and ExtremeCloud IQ Integration

Domain 6 covers the wireless side of XIQ-SE - controllers, AP adoption, radio and SSID visibility - and how the on-premises server coexists with ExtremeCloud IQ in the cloud.

What XIQ-SE manages

  • Controllers are added under Wireless with management credentials: ExtremeCloud IQ Controller (formerly ExtremeCloud Appliance) and WiNG controllers. APs are learned through their controller, so an AP never appears before its controller is managed.
  • Visibility includes AP inventory and status, SSIDs, radio profiles, clients and roaming, per-AP alarms such as AP down or excessive retries, rogue and neighbour detection with AirDefense, and floor-plan location with heat maps.

Adoption and discovery

  • APs locate controllers through DHCP option 43, DNS resolution of the controller name, a statically configured controller address, or cloud discovery for cloud APs. Adoption also requires compatible AP firmware and controller capacity or licensing.
  • Regulatory domain and radio profile govern legal channels and power. A wrong country setting leaves radios unusable no matter how cleanly adoption completes.

Cloud integration

  • ExtremeCloud IQ (cloud) and XIQ-SE (on-prem) can be linked so cloud dashboards and assurance tooling consume on-premises data; registration uses a token or connector configured on the server and a matching entry in the cloud tenant.
  • Ownership stays single-plane: an AP adopted by a cloud controller is not managed from XIQ-SE and vice versa. Moving an AP between planes means unadopting or resetting it, not just adding credentials.

Worked example

New APs power up but sit unassigned. The controller sees them and XIQ-SE sees the controller, so the fault is adoption: the DHCP scope has no option 43 and DNS has no controller record, so the APs never learned where to go. Add option 43 or the DNS entry pointing at the controller management address, reboot the APs, then confirm firmware compatibility before suspecting licensing.

Traps that cost marks

  • Expecting cloud-managed APs to appear in on-prem inventory.
  • Mixing WiNG APs with an ExtremeCloud IQ Controller.
  • Option 43 entered in the wrong format (hex versus dotted string).
  • Wrong regulatory domain blocking radios.
  • AP-down alarms firing with no wireless licence so no detail exists.
  • Heat maps generated without AP placement or plan calibration.