AAA succeeds on the core path (Permission Denied)

The server is reachable, yet the management path is classified into the wrong authorization domain. The service still works through the primary path, but one dependency only fails when the old component is finally drained away. The primary component still serves traffic, yet the retirement exercise exposes a latent dependency on what is being removed. The main path still works until the exercise finally removes the legacy dependency it had quietly relied on. Normal traffic stayed clean until the exercise finally removed a legacy path that the service still relied on indirectly.

• Identify the primary failure signal in the AAA Server Reachable, OOB Management in the Wrong Realm scenario.
• Separate visible symptoms from the underlying technical dependency.
• Describe the safest recovery path and the follow-up prevention work.

1. Summarize the current impact and the last known change.
2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
3. Separate immediate recovery from permanent prevention work.

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.