FAQ-What's the difference between two reasons of "web user request" and "user request to offline" which cause MA5200F/G web authentication users to drop offline?

Publication Date:  2012-07-27 Views:  65 Downloads:  0
Issue Description
Q: What's the difference between two reasons of "web user request" and "user request to offline" which cause MA5200F/G web authentication users to drop offline?

Alarm Information

No


Handling Process
A: For the same web authentication user, it leaves MA5200F/G because of the following two possible reasons:

web user request: It gets offline since it receives the request of logout from WEB authentication server, and it is normal. A typical operation user could click logout (cancellation) on successful web authentication page to leave. Additionally, failure to detect heartbeat could cause a user to get offline, because the heartbeat of WEB authentication user is between WEB authentication server and client; when WEB authentication server receives not response for several times when transmitting heartbeat packets, it will think that the user has been left, and will send logout request to MA5200F/G, at which point the MA5200F/G records the offline reason as web user request;

user request to offline: It gets offline for request from client, including typical operations such as that PC releases address if it is a WEB authentication user. 

Root Cause
No

END