Radius floods session-timeout to MA5200 to control how long a user is online, and the user will not get offline once it is the time. A user has been online for 1400 hours.
1. No problem is found in configurations of MA5200.
2. In configuration, the radius protocol of MA5200 is portal and iTELLIN serves as radius equipment. Execute debugging radius packet command, and the radius has flooded the session-timeout; according to the requirements of protocol, once the time is up, the session-timeout value carried by real time accounting packets that radius equipment responds to MA5200 should not be 0, so the users are not cut off.
3. Check the configuration of iTELLIN, and it is configured with standard radius protocol, so it is located that both sides use different radius protocols.
4. Change the radius protocol of MA5200.The problem is solved.
If MA5200 uses standard radius protocols, once the flooded session-timeout is received, MA5200 cuts the users offline. If Radius+1.0/1.1(corresponding toportal/huawei of MA5200), it will trigger real time accounting when the time is up if the session-timeout containing value is received. At the time, the radius server should respond the packet of session-timeout = 0, which indicates the user needs to get offline. So BAS cuts the user offline; otherwise, MA5200 will calculate again according to the value in session-timeout in last accounting response. In this case, MA5200 is set to portal type (viz. Radius+1.1), and iTellin is set to standard protocol. When it is the time for session-timeout, the accounting response packets contains one non-zero value, so the users will not be cut offline.
Regardless of whatever services, it is suggested to synchronize the protocol type for both BAS and Radius.