Version: Independent of version
Symptoms: PPPoE users under MA5200 used Radius authentication policy. When Radius failed, it was changed to non-authentication, but it failed also, prompting error734.
1. Check the reason why the user gets offline, and it is: CM l2tp session fail.
Originally, the domain was configured with l2tp group 1 and l2tp-user radius-force. It requires radius to determine whether the user is l2tp user. When radius fails, it is impossible to judge if the user is of L2tp. They should be L2TP users according to the configuration, but the authentication for common PPPoE users at LNS fails, so the session cannot set up, and users cannot access network.
2. Both common users and reliable network subscribers are in the same domain. When radius fails, only one type of users could operate well: if common users need to operate normally, it needs to delete the relevant setting for l2tp in domain; if it is necessary, if reliable network subscribers have to operate normally, it needs to set such L2TP parameters including LNS at MA5200.
Although the domain that the user locates is configured with non-authentication and non-accounting, the domain contains the configuration of l2tp group 1 and l2tp-user radius-force. When Radius fails, the users in the domain become l2tp users by default. Thus, common users have to pass authentication according to the flow of l2tp users in dialup, and the authentication fails, incapable of communicatiing with server.
It is suggested to authenticate the users of two parts in two different domains as to avoid such a problem.