Device blocking and global session limit issues

Prerequisites and authority

Start with read-only checks and authorized records. Capture evidence before changes. Stop and escalate when data replacement, financial changes or wider outages are possible.

Device block or global session limit fails

Basic

Confirm the selected device belongs to the customer and distinguish its application session from its router connection. Check MAC randomization and active connections across routers.

Intermediate

The approved block target is immediate disconnection plus prevention of reconnection. If blocking changes only a database flag, record a target-behavior defect. Check the router disconnect operation and subsequent authentication result.

Advanced

For concurrency, inspect customer-wide live sessions, unexpired pending reservations, duplicate/stale sessions and outage reconciliation. New admissions at capacity are rejected without evicting established sessions; each router does not receive a separate full allowance. Device blocking targets the selected MAC, with pending enforcement visible during outages or ownership conflicts. Unblocking does not automatically connect a device.

Use supported disconnect/reconciliation after correcting the dependency. Do not reduce lifetime registered-device limits as a substitute for enforcing concurrency.

Check blocking, reconnect rejection, authorized restoration and cross-router session limits separately. Record customer, device, session and router identifiers with timestamps, then escalate unexpected results to support without changing limits or deleting history to hide the failure.