Hello everyone,
This post talks about the issue that portal authentication is slow, as part of the Troubleshooting Series on the Forum. Please find the solution below.
Physical Network Topology
Figure 1-1 Network where Portal Authentication Is Slow
![]()
Fault Description
After a user associates its terminal with Wi-Fi, a Portal page is displayed. The user enters the user name and password and clicks Login. The authentication is successful after about 20 seconds.
![]()
Troubleshooting Procedure
The terminal initiates authentication on the Portal page. The Agile Controller searches for the corresponding authentication device from the device management module based on the terminal IP address. If the access terminal IP lists configured for multiple authentication devices overlap, the Agile Controller sends Portal packets to all authentication devices which meet the requirements and waits for responses from all these devices. Therefore, the authentication is slow.
Solution:
1. If two authentication devices work in hot standby mode, you need to configure Standby device IP address for the standby device, as shown in the following figure.
![]()
2. If the IP addresses of the terminals managed by multiple access devices do not overlap, the values of the Access terminal IP list field should not overlap.
3. If VRRP is configured for the access devices, you only need to configure the virtual IP address on the Agile Controller.
Root Cause
On the Device Management menu of the Agile Controller, the Access terminal IP list field on the Authentication Parameters tab page has overlapping values for different authentication devices.
![]()
![]()
That is all I want toshare with you! Thank you!