ExtremeCloud IQ Site Engine
The Site Engine integration reads ExtremeCloud IQ Site Engine (formerly Extreme Management Center) through its northbound API. It runs on an Integrator inside your network, so Site Engine is never exposed to the CyberOptix CTEM Platform. For devices managed from the cloud, use the ExtremeCloud IQ integration.
It is read-only. The integration only queries the northbound API and never changes anything in Site Engine or on the devices it manages.
What it collects
| Sync | Collects |
|---|---|
| Network discovery | Each device's ports with their status, speed and VLAN, and the VLANs it has an address in, as networks |
| Host discovery | The end systems Site Engine's access control has seen, with the switch and port they were seen on, and each port's discovery-protocol neighbors |
Every sync also reports the devices Site Engine manages, with model, serial number, firmware, management address and site. Devices appear under Attack Surface > Network Devices.
Site Engine's northbound API does not return configuration files, so this integration has no configuration backup or configuration review. End systems are those Site Engine's network access control has seen; switches without access control contribute their neighbors only.
What Site Engine reports is kept as its own record, alongside hosts and subnets rather than written into them.
Create a read-only API client
- Create an authorization group with only the northbound read capabilities: Northbound Interface Read Access, Network Northbound Interface Read Access and Access Control Northbound Interface Read Access.
- Under Administration > Client API Access, add a client in that group. Site Engine issues a client ID and client secret.
Connect it
- Under Integrations, add ExtremeCloud IQ Site Engine with Site Engine's hostname and the client ID and secret.
- In the integration's settings, assign the Integrator that can reach Site Engine. The integration connects on port 8443 unless you set another.
- Enable the syncs you want.
Certificates
Site Engine generates its own certificate when it is installed. The first connection accepts the certificate and records its fingerprint on the integration; every later connection must present the same certificate. If you replace the certificate, clear the pinned fingerprint in the integration's settings so the new one is recorded. A certificate issued by a trusted CA is verified normally and never pinned.