Clients are unable to view the captive portal page while connecting to one of the MDs in the cluster

MVP Expert
MVP Expert
Problem:

Issue:

Clients connecting to Guest SSID configured with custom captive portal page are unable to view the captive portal page

Issue is seen only when the clients connect to AP in one of the MD's in the cluster

When the clients connect to AP on another MD in the same cluster, they are being redirected to captive portal page

 

NOTE:

This issue is seen if the MD is newly added to the cluster or if the files are not synced across to the MD's after added to the cluster however in both scenarios the custom captive portal page must be synced to the affected MD without affecting other working MD's in cluster

There is other reasons the captive portal page goes missing in the MD however that's outside the purview of this article as we will concentrate only on fixing the missing custom captive portal page in the MD

 



Diagnostics:

Captive Portal Visibility in Folder Level Configuration:

  1. In the webUI, click on the folder where the custom captive portal page is uploaded
  2. Navigate to Configuration - Roles & Policies - Click on the Initial role used for captive portal authentication
  3. Scroll Down and click on "show Advanced View" and click on Captive portal
  4. Scroll Down and make sure "Internal Captive Portal with Authentication" is highlighted and a path exists under "Files for Login Page"

 

 

  1. Click on "preview" and make sure the custom page pops-up in the new tab
  2. Also make sure there is no pending configuration 

 

Captive Portal Page visibility in Working MD's:

  1. In the webUI, click on the working MD where the captive portal page works 
  2. Navigate to Configuration - Roles & Policies - Click on the Initial role used for captive portal authentication
  3. Scroll Down and click on "show Advanced View" and click on Captive portal
  4. Scroll Down and make sure "Internal Captive Portal with Authentication" is highlighted and a path exists under "Files for Login Page"
  5. Click on "preview" and make sure the custom page pops-up in the new tab

 

 

As seen above, both the folder level configuration and one of the MD have correct configuration and upload path. Now let's look at the configuration in the non-working MD. 

Captive Portal Page visibility in Non-Working MD's:

  1. In the webUI, click on the working MD where the captive portal page works 
  2. Navigate to Configuration - Roles & Policies - Click on the Initial role used for captive portal authentication
  3. Scroll Down and click on "show Advanced View" and click on Captive portal
  4. Scroll Down and make sure "Internal Captive Portal with Authentication" is highlighted and a path exists under "Files for Login Page"
  5. You will notice there is upload path however the clients are not getting the captive portal page
  6. Click on Preview doesn't populate the custom page

 

 

Hence it appears, the custom captive portal page is missing or HTML file is not pushed in one of the MD's in the cluster from /MM. These kinds are issues are seen due to config sync issue between MM and MD. 



Solution

Resolution:

  • In order to resolve this issue in the MD, we can upload the custom captive portal page again in /MM node so that it gets pushed to all the devices in the cluster.
  • However in order to resolve the issue without affecting the working MD and MM, we can execute the below command in the non-working MD where the custom page is missing.
  • Once the command is executed, it will pull the custom captive portal page from MM. 

 

Use the sync-files command to pull the custom captive portal profile from /MM node:

 

Before executing the command, we must have the below information.

  • Correct path where the custom captive portal page is uploaded which we can get by executing the below command in MD path on MM:

 

  • Execute the below command manually on /MD path on MM which will pull the custom captive portal page from /MM node:

 

  • Verify that actual MD has received the command by checking for "show configuration effective | include sync-files"

 

The "sync-files" should have downloaded the custom captive portal page from /MM which should fix the issue of clients not getting the captive portal page while associating to one of the AP in one of the MD's. 

 

NOTE: "Sync-Files" will work only if the custom page resides on /MM. If the custom page is missing in /MM node, this command will not resolve the issue. 

Version history
Revision #:
2 of 2
Last update:
‎08-08-2019 11:08 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: