I would suggest that you open a case with the TAC; this looks like it may be a new bug.
It appears that you are running some very recent 12.2T code; a routine was added to make a copy of the authorization data. However, it looks like that copy was either lost or not referenced for the callback. The important debug is here:
*Mar 1 01:58:28: Se1/0:20 PPP/AAA: Saving a copy of the authorization data
*Mar 1 01:58:44: Se1/0:30 PPP/AAA: Using authorization data from a prior call
It looks like we don't use the authorization data, though; it looks like we go back to the AAA server, where that fails again.
Sorry, but I can't think of a possible workaround at this point.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...