A typo during manual entry can sometimes trigger this if the mistyped number belongs to another active account. How to Resolve the Issue
| Impact Area | Severity | Explanation | |-------------|----------|-------------| | Availability | High | Device appears offline to clients even if it’s alive | | Debuggability | Medium | Misdirection makes logs misleading | | Security | Low-Medium | Possible traffic leakage to wrong IP (if that IP is reassigned to another host) | | Operations | High | Manual cleanup required if automated process missing | a stale record of the device was found in the redirector.
The Redirector is a cloud-based service that "directs" a hardware device to its specific management instance when it first connects to the internet. Because a device can only be managed by one account at a time, a "stale record" exists if the device was: A typo during manual entry can sometimes trigger
When the redirector hits a "stale record" error, it doesn't just fail. It flags that specific Device ID as "Inconsistent." It flags that specific Device ID as "Inconsistent
This error typically occurs when trying to onboard an (formerly Aerohive) access point into ExtremeCloud IQ (XIQ) . It indicates that the device's serial number is already linked to a different management account (instance) in the manufacturer's global backend database, known as the Redirector . Why Does This Error Happen?
backend devices server device1 10.2.3.4:8080 check inter 5s rise 2 fall 3
A stale device record in a redirector is a state inconsistency problem caused by missing deregistration, long TTLs, or broken health checks. It degrades availability and misdirects traffic. The fix involves immediate manual cleanup, then implementing TTL reduction, health checks, and a device heartbeat/deregistration protocol. Long-term, shift to service discovery with real-time consistency.