This article provides a cause and solution for the 'subscriber-mgr-activation-failed
counter increasing.
When checking the terminate code, the subscriber-mgr-activation-failed
counter keeps increasing.
labroot@mxvc-router> show network-access aaa terminate-code brief
Terminate-code:
RADIUS Custom Usage-Count Type Code
9 no 136 ppp subscriber-mgr-activation-failed
{master:member1-re0}
labroot@mxvc-router>
When checking the authd (general-authentication-service ) traceoption, the log shows this account login failure is due to 'ppp subscriber-mgr-activation-failed'
.
Nov 2 16:17:14.899602 UserAccess:test1@domian session-id:52 state:log-out mxvc-router#ae0.demux0.10000100:100# reason: ppp subscriber-mgr-activation-failed
And RADIUS returned ​Virtual-Router (Juniper-ERX-VSA):
Nov 2 16:17:14.703527 radius-access-accept: Framed-Protocol received: 1
Nov 2 16:17:14.703544 radius-access-accept: Framed-IP-Address received: 10.10.10.81
Nov 2 16:17:14.703559 radius-access-accept: Framed-IP-Netmask received: 255.255.255.248
Nov 2 16:17:14.703574 radius-access-accept: Virtual-Router (Juniper-ERX-VSA) received: WIFI-s
Nov 2 16:17:14.703589 Framework - module(radius) return: SUCCESS
Also, it was observed that the routing-instance was deactivated:
labroot@mxvc-router> show configuration routing-instances WIFI-s
##
## inactive: routing-instances WIFI-s
##
instance-type vrf;
interface lo0.363;
route-distinguisher 10.20.30.1:12550;
vrf-target target:10.20.30.1:12550;
vrf-table-label;
{master:member1-re0}
labroot@mxvc-router>
Activate the routing-instance configuration.
RADIUS will return the correct VSA attribute for Virtual-Router (Juniper-ERX-VSA)