DHCP, DNS, NTP, and RADIUS
Checks for a client wireless network, AP management network, site, user context, or SSID context.
Integrations and handoff
Technical results other systems can actually use.
Control structures scope, status, technical evidence, and root-cause context so APIs and reports can reuse them. ITSM handoff is kept clearly separate from an actually enabled remote-delivery path.
API and structured results
Run targeted checks. Process structured results.
The API can trigger checks for a defined scope and return machine-readable results.
PoE, speed, duplex, and counters
Validate every AP in a building or individual Ethernet interfaces and switch ports.
Onboarding and reachability
Site Engine onboarding, policy context, cloud communication, and the effects of firewall rules or SSL inspection.
Structured finding
Not merely an alert. A case with context.
- Status and severity
- Site, building, AP, client, SSID, and VLAN
- executed checks and runtimes
- technical evidence and root-cause correlation
- affected infrastructure and recommended action
- link to the report or investigation
ITSM foundation
Prepared for controlled ITSM workflows.
The ServiceNow outbox prepares incident candidates locally with an auditable record. Automatic remote incident creation or updates are not currently available as a production feature, so other ITSM targets are not presented as finished integrations.
Prepared ITSM flow
From a DNS failure to a structured incident candidate.
- Monitor detects that a RADIUS hostname cannot be resolved through a site's DNS resolver.
- Control evaluates scope and severity.
- Control bundles the site, resolver, target, error message, and evidence into a structured technical finding.
- The prepared ServiceNow outbox can form a local incident candidate; remote delivery remains disabled.
- The responsible team receives a clear technical basis for reporting, API processing, or a later ITSM handoff.