March 7th 2019 Updates

Network Programmability – Guest Portal Required Fields

The Guest Portal defines the landing page customers are directed to when you configure a WLAN with portal configurations. To improve customization, starting this week we are allowing you to set any custom portal field as a required field. You are not limited to setting Name, email, and Company name as the only required fields. Now you can set required fields on your guest WLANS for anything, such as phone number, meeting room, who the guests are meeting with, etc. Use this new information to monitor those connected to your guest WiFi.

Navigate to Network > WLANS to create a WLAN with Guest Portal sign-on. In the Form Fills section, specify which Custom Fields need to be required. Give the appropriate name for each label in the Customize Label section

   

The required fields will now be displayed as such on the login page:

 

Marvis – Virtual Network Assistant

Improved Correlation Charts

The troubleshoot command on Marvis allows you to get a comprehensive overview of any issues experienced by a particular Site, AP, or Client. Expanding on the Correlation section will expose the Probable Causes and Scope of Impact graphs, which show the correlation between Clients, APs, WLANs, etc. This allows you to determine any of the problem areas and pinpoint what the specific issue corresponds with. As an added visual, we’ve segmented these Correlation graphs to show Weak, Medium, and Strong degrees of correlation.

Learn more about Marvis here: https://www.mist.com/documentation/category/marvis/

 

Dashboard Changes in the UI – Coming Next Week!

Heads up! You will see a new look on the Mist Dashboard next week for a more intuitive look and feel. Also, Marvis will now be on the main menu of our sidebar for easier access. The Marvis header button will still be active for typing any quick queries without leaving your current page.

 

Bug Fix – Replace AP function

The Replace AP function is a useful tool when swapping out an AP on your site and retaining all the previous settings on the new AP. An issue was found and resolved where this function did not correctly retain Organization Labels associated to the replaced AP.