AirWave Glass Release Notes

Transcription

1 AirWave Glass Release Notes

2 Copyright Information Copyright 2018 Hewlett Packard Enterprise Development LP Open Source Code This product includes code licensed under the GNU General Public License, the GNU Lesser General Public License, and/or certain other open source licenses. A complete machine-readable copy of the source code corresponding to such code is available upon request. This offer is valid to anyone in receipt of this information and shall expire three years following the date of the final distribution of this product version by Hewlett- Packard Enterprise Company. To obtain such source code, send a check or money order in the amount of US $10.00 to: Hewlett-Packard Enterprise Company Attn: General Counsel 3000 Hanover Street Palo Alto, CA USA Please specify the product and version for which you are requesting source code. You may also request a copy of this source code free of charge at: March 2019 Rev. 02 AirWave Glass Release Notes

3 Chapter 1 Release Overview AirWave Glass is a software patch release that introduces a new feature and important change. The software update is available online from the top header of the AirWave Glass WebUI and offline as a downloadable.tar file from the Aruba support site. Refer to these release notes for the most up-to-date information. For more information about using the product, see the AirWave Glass Installation and User Guide. These release notes contain the following topics: "What's New in this Release" on page 5 describes what's new in this release. "Resolved Issues" on page 7 describes issues fixed in this release. "Known Issues" on page 10 describes known issues in this release. "Upgrading AirWave Glass" on page 17 describes updating your software. Contacting Support Table 1: Contact Information Main Site Support Site Airheads Social Forums and Knowledge Base North American Telephone arubanetworks.com support.arubanetworks.com community.arubanetworks.com (Toll Free) International Telephone Software Licensing Site End-of-life Information Security Incident Response Team (SIRT) arubanetworks.com/support-services/contact-support/ hpe.com/networking/support arubanetworks.com/support-services/end-of-life/ Site: arubanetworks.com/support-services/security-bulletins/ aruba-sirt@hpe.com Contact Center Online Main Site Support Site ebg_global_supportcenter@al-enterprise.com Service & Support Contact Center Telephone AirWave Glass Release Notes Release Overview 3

4 Table 1: Contact Information (Continued) North America Latin America EMEA (Toll Free) or +1 (650) Asia Pacific Worldwide Release Overview AirWave Glass Release Notes

5 Chapter 2 What's New in this Release AirWave Glass introduces important changes and new features to improve stability and data accuracy. In order for all the Glass discrepancy fixes to work correctly, you must upgrade your managed AMPs to AirWave Important Changes The following changes to functionality don't require user input: Redesigned Overwatch pod manages AirWave to AirWave Glass table mapping, monitors the Overwatch log, and changes Elasticsearch mappings during the upgrade to AirWave Glass Kubernetes monitoring allows Kubernetes to recover from corrupted IP tables. Improved messaging from the managed AMP provides accurate rogue counts in AirWave Glass. By fixing client events, discrepancies in client counts are less likely to appear. Because client association and diassociation is dynamic, you might see a discrepancy between the AMP client count in header statistics and drill down counts in AirWave Glass. Report synchronization on all nodes in a cluster at the same time. Full bootstrapping when you add the managed AMP to AirWave Glass, which is done automatically during upgrade. We no longer support partial bootstrapping, index-based bootstrapping, and auto-bootstrapping. Header statistics at the top of the page automatically refresh in 5-minute intervals. Automatic refreshing of the header statistics and the icon statistics in the Overview dashboard can start at different times. If you add or delete a managed AMP, you will need to wait for the cache to clear in order for client counts to be exact. End user license agreement has been added in AirWave Glass Go to System > License Agreement to view your agreement. When you click in the top header, improved drill-down page displays results labeled "CLIENT" : WIRELESS or "CLIENT" : WIRED. New Features You can view the date and time when the managed AMP was "last heard from" in the WebUI. Go to System > Managed AMPs, then click to view results from search categories, like access points, clients, controllers, VisualRF floors, folders, and rogues. Enhancements to set up and infrastructure with the following new CLI options: glass-version shows the current running version of the server glass-version d shows the current running version of all the servers and all the pods glass-ntp sets up the timezone for the server from the CLI. You need to copy the timezone from list of available timezones into the line. glass-diag runs a script that gathers logs from all the pods and puts them into a zip file in the \temp folder. This command is available only for use by Technical Support. glass-reset keeps the versions of all the pods currently installed without deleting all the downloaded images and pod versions. For example, if you have AirWave Glass installed when you do the reset, the pod versions will be reset to AirWave Glass Resetting the version deletes all Elasticsearch data, so we recommend you proceed in the following order: AirWave Glass Release Notes What's New in this Release 5

6 (1) Remove all managed AMPs. (2) Run the glass-reset command. (3) Run the glass-setup command and set up the network configuration for the AirWave Glass server. After the setup completes, the AirWave Glass WebUI should be accessible, and the pods will be in the versions from when you ran the glass-reset command. (4) Add the managed AMPs. 6 What's New in this Release AirWave Glass Release Notes

7 Chapter 3 Resolved Issues The following issues have been fixed in recent releases of AirWave Glass. Table 2: Issues Resolved in AirWave Glass ID DE32045 Description Symptom: After upgrading the Instant software to , AirWave Glass displayed the old IAP firmware version. Scenario: AirWave Glass displays the correct Instant version after upgrading the firmware. DE31894 Symptom: Only the Save button appeared on the VisualRF page. Scenario: We fixed an issue which prevented floor plans from displaying properly after adding managed AMPs in AirWave Glass. DE31618 Symptom: Device and client count in AirWave Glass and AirWave didn't match. Scenario: Header statistics auto refresh in 5-minute intervals. DE31616 Symptom: AirWave Glass updated Clarity data intermittently. Scenario: Clarity now updates in 15 minutes. DE31589 DE31406 Symptom: When you drill down from the historical client session on the Client Detail page for a client that is not currently online in AirWave, AirWave displays an "Access Denied" error on the device monitoring page. Scenario: When you choose the link of an AP/Device for a currently connected client session, AirWave Glass now opens the AP monitoring page of the managed AMP. DE31588 Symptom: Cient count in header statistics didn't match client count in search results for both wired and wireless clients. Scenario: Now AirWave Glass sends events only for currently connected clients, parses client data properly, and filters client searches to look back 20 minutes. DE31580 Symptom: AirWave Glass displayed a campus on the network map that had been deleted in from VisualRF in AirWave. Scenario: We fixed the issue that could cause AirWave Glass to miss the feeder update. DE31538 Symptom: AirWave Glass displayed the wrong number of down devices. Scenario: We changed an underlying mechanism which checks the database cache and clears down devices. DE31537 Symptom: AP Details page doesn't display information like IP address and client count. Scenario: We improved feeder updates and events so device type and clien count events appear properly. AirWave Glass Release Notes Resolved Issues 7

8 Table 2: Issues Resolved in AirWave Glass (Continued) ID DE30817 Description Symptom: The Type column of the Report Instances page incorrectly listed reports as Apprf_ Dashboard. The AppRF feature was renamed Traffic Analysis in AirWave and has been renamed on all pages in AirWave Glass and later. However, the Report Instances page will still show the report type as "Apprf_ Dashboard" although it is traffic analysis data. Workaround: We changed the report type to "Traffic Analysis" on the Report Instances page. DE30770 Symptom: Search results failed to show a controller. Scenario: AirWave Glass now clears down devices from the database cache after finding that this caused the issue. DE31027 Symptom: If you generate a CSR in AirWave Glass, some information like the common name is missing. Scenario: AirWave Glass includes all certificate attributes now when you generate a CSR. DE27665 Symptom: When opening the AirWave Glass WebUI in the Safari browser, the browser prompted you to choose a client certificate and then displayed an HTTP 400 bad request error. Scenario: We addressed this issue by using the default certificate. Table 3: Issues Resolved in AirWave Glass ID DE31290 DE31491 Description Symptom: The AirWave Glass WebUI and search results now correctly show all available device data after you manually rebootstrap the AirWave Glass server. Scenario: Improvements to internal index processes in AirWave Glass resolve an issue that prevented some devices from properly appearing in the device lists or search results in AirWave Glass. DE31186 Symptom: The VisualRF floor search feature in AirWave Glass shows all floorplans, regardless of the user role of the person performing the search. Scenario: Earlier releases of AirWave Glass could prevent admin users from viewing floorplans in VisualRF if the floorplan was missing user role information. AirWave Glass no longer applies role restrictions to floorplan searches in VisualRF, and displays all available results for all users in the search output. This change to AirWave Glass does not impact the role restrictions AirWave applies to users searching for VisualRF floorplans in AirWave. DE31376 DE31184 Symptom: The AirWave Glass WebUI and search results now correctly show all available VisualRF flooplan data after the AirWave Glass server automatically rebootstraps. Scenario: Improvements to internal index processes in AirWave Glass resolve an issue that prevented some floorplans from appearing in VisualRF after the AirWave Glass server automatically rebootstrapped. Symptom: Graphs on the Home > Client Session page correctly display available client data. Scenario: AirWave Glass resolves an issue where client data failed to appear on the Home > Client Session page of the AirWave Glass WebUI, even if client data was available. 8 Resolved Issues AirWave Glass Release Notes

9 Table 4: Issues Resolved in AirWave Glass 1.2 ID US20068 Description Symptom: AirWave Glass has always required that its managed AMPs use NTP (Network Time Protocol) for proper data synchronization, but it did not warn users about this requirement on the System > Managed AMPs page, when a user attempted to add a AMP. Scenario: AirWave Glass now includes a message on the System > Managed AMPs page to remind users that a managed AMP must be using NTP. DE30630 DE30876 DE30475 DE30573 Symptom: The client and AP statistics AirWave Glass showed shown in the WebUI header varied from the statistics shown in search results Scenario: These issues are resolved by the auto-bootstrapping feature introduced in AirWave Glass 1.2, which ensures that stale and missing index entries are properly removed so all AirWave Glass statistics match those on the managed AMPs. Symptom: The Folder Health tree table on the Home > Folder Health page did not display the full host name of the managed AMPs. Scenario: The Hostname column in the Folder Health tree table how displays a tooltip showing the full host name of the managed AMP when you hover your mouse over any entry in this column. Table 5: Issues Resolved in AirWave Glass ID DE30901 Description Symptom: When you try to add a managed AMP in AirWave Glass, you get the error message: Managed AMP is Invalid. Scenario: AirWave Glass now handles host names that start with a number. Table 6: Fixed Issues in AirWave Glass ID DE30791 Description Symptom: Managed AMPs lose connection with the AirWave Glass server. Scenario: When the managed AMP is unable to connect to the AirWave Glass server, the feeder updater now restarts and the connection remains open. DE30501 Symptom: When you drill down to information on device status, the filtered results included devices that were down whether for maintenance or operational error. Scenario: The drill down feeder now handles the planned down status and correctly reflects the device status received from AirWave. DE30367 Symptom: The Folder Health page might not display all the Top folder statistics for a primary managed AMP. Scenario: All Top folder statistics display properly now. AirWave Glass Release Notes Resolved Issues 9

10 Chapter 4 Known Issues The following known issues may impact this version of AirWave Glass. Table 7: Known issues in AirWave Glass ID DE32295 Description Symptom: After deleting a managed AMP, VisualRF in AirWave Glass still shows search results for VisualRF floors and historical client sessions from the deleted AMP. Reports in AirWave Glass will not have any role filters, and all data will be shown in reports for any user role. Workaround: There is no workaround. DE32274 Symptom: Rogue drill down counts differs from dashboard or header statistics. Workaround: In order for the fixes in AirWave Glass for this issue and all other discrepancies to work correctly, upgrade the software version on the managed AMPs to DE32273 Symptom: The AP/Device column is not shown in Historical Client Sessions results. Workaround: To view the AP/Device column in the Historical Client Session results, click the search icon again. DE32143 Symptom: After upgrading to AirWave Glass or adding managed AMPs in AirWave Glass, the header statistics doesn't display client counts. Workaround: Although we resolved the underlying problem, wait 20 minutes after upgrading to AirWave Glass or adding managed AMPs to allow the system to stabilize. DE32038 Symptom: The Overview dashboard shows trend charts at the top of the page and the Snapshot icons at the bottom of page. Workaround: Clicking on the orange Aruba icon on the upper left corner of any page in the AirWave Glass WebUI, or navigating to another page will return you to the Overview dashboard and resolve the issue. DE31965 Symptom: When you click a rogue statistics icon in the header, the search results showed a different rogue count on the search drill down page than in the header. Scenario: Although we resolved the underlying problem, wait 20 minutes after changing the rogue classification to allow the system to stabilize. DE31958 Symptom: Changing the name of the rogue device on a managed AMP, doesn't get updated in AirWave Glass displays the old name. Workaround: There is no workaround. DE31600 Symptom: Sometimes the offline upgrade might not upgrade the feeder on the managed AMPs. Workaround: This is a very intermittent issue. To recover, run this command on all AirWave Glass nodes in a cluster: docker ps grep infra grep docker-entry awk '{print $1}' xargs docker restart AirWave Glass Release Notes Known Issues 10

11 Table 7: Known issues in AirWave Glass (Continued) ID DE31510 Description Symptom: Client certificates on the feeder might have expired, causing a break in communication with AirWave Glass. Workaround: To workaround this issue: 1. Go to System >Managed AMPs, locate the AMP and click to modify its settings. 2. Select the Regenerate Service Credentials check box to refresh the client certificates and all API secrets on the managed AMP. 3. Enter the Izanami and password used to access the managed AMP. DE30795 Symptom: Duplicate folders shown in the Folder Health dashboard. After adding managed AMPs to AirWave Glass, the Folder Health dashboard might show the top folders from all the AMPs twice. AirWave Glass automatically refreshes the data after 5 minutes. Workaround: Not applicable. DE30754 Symptom: The AirWave Glass CLI shows error messages after a successful Kubernetes firmware update. The error messages displayed subsequent to the "Kubernetes successfully upgraded to v1.5.4" message are expected and should be ignored. Workaround: Not applicable. DE30345 Symptom: After upgrading to AirWave Glass or later, the feeder versions on managed AMPs running ArubaOS versions later than ArubaOS aren't updated because of a change to the schema introduced after AirWave As a result, top header statistics will not be updated, and AirWave Glass will not retrieve certain types of data from the managed AMP. Workaround: We recommend upgrading the managed AMP to AirWave x or later to get the latest feeder when you upgrade to this version of AirWave Glass. DE30272 Symptom: Reports on the cluster are not generated properly, and selecting a in incorrectly generated report may display an error message that includes the following text: "statuscode" : 404, "error" : "Not Found" Workaround: This issue may occur if the internal Reporter and API pods inside the AirWave Glass software appear on different nodes. If you delete the Reporter node, the Kubernetes process automatically recreates the Reporter pod and places it on any one of the nodes. The workaround is to delete the Reporter pod until it lands on the same node as the API pod. Contact Customer support, or use the following procedure to delete the Reporter pod until it gets recreated on the same node as the API pod. 1. Check which nodes the API Pod and Reporter Pod are on using the command: kubectl get pods -- all-namespaces -o wide 2. Delete the Reporter Pod: kubectl delete pod -n glass-system <pod Name> DE30260 Symptom: When you use the Firefox browser to navigate to the Reports Definitions page, AirWave Glass can't load the page and displays an error similar to the following: NotFoundError ( Workaround: Use a different browser, such as Chrome or Safari. 11 Known Issues AirWave Glass Release Notes

12 Table 7: Known issues in AirWave Glass (Continued) ID DE30237 Description Symptom: In the Overview dashboard, AirWave Glass might display the message No Data To Display under the Clarity Failures column although data displays in the Clarity dashboard when you navigate to Home > Clarity. This issue occurs because the Home dashboard refreshes every 5 minutes while the Clarity dashboard refreshes every 15 minutes. Workaround: There is no workaround. DE30203 Symptom: When you schedule a report on the Reports Definitions page and click Generate Now, the report doesn't generate. Workaround: You must click Generate Now, then click Save. DE30103 Symptom: When you click the AP Radio Status Up, AP Radio Status Down, or Noisy Snapshot icons in the Overview Dashboard, the number of search results displayed doesn't match the count displayed in the Snapshot icon. Workaround: There is no workaround. This issue occurs because each AP has 2 radios, and a single AP can appear in both AP Radio Status Up and AP Radio Status Down values if only one radio is up or down. The search results are determined by an index of APs instead of radios. DE29815 Symptom: AirWave Glass loses data for more than 20 minutes after the master node fails over to a master HA node. Workaround: Wait for approximately 35 to 40 minutes while AirWave Glass updates the clients status trend chart on the Home > Overview page. DE29705 Symptom: When a container is newly upgraded and downloaded to a node, docker images don't replicate from one node to the other after failing over. Workaround: There is no workaround. DE29695 Symptom: The AirWave Glass WebUI becomes inaccessible if you remove both master HA nodes from a 3-node cluster. Workaround: There is no workaround. DE29588 Symptom: Failover doesn't work on a 2-node cluster (for example, when you remove a master HA node from a 3-node cluster). Workaround: You must configure a second master HA node in the HA cluster. DE29585 Symptom: You can't add a node using the cluster-setup command after the master node fails over. Workaround: There is no workaround. DE29430 Symptom: Bandwidth trend charts that display many data points on the Folder Health page can be difficult to read. Workaround: There is no workaround. DE29395 Symptom: Total client health metrics do not match with overall client count in a folder, and the By Client Health snapshot and trend charts are inaccurate. Workaround: There is no workaround. AirWave Glass Release Notes Known Issues 12

13 Table 7: Known issues in AirWave Glass (Continued) ID DE29373 Description Symptom: Bandwidth data calculation on the Folder Health page incorrectly reports the average speed of clients in a folder. Workaround: There is no workaround. DE29219 Symptom: Single sign-on (SSO) authentication doesn't work in AirWave Glass if the managed AMP is running AirWave Workaround: An underlying issue with AirWave prevents a remote user from being authenticated. We recommend using AirWave or later with this version of AirWave Glass. DE28307 Symptom: The Client Session dashboard shows a discrepancy between the bandwidth data reported by the connected AMP and AirWave Glass. Workaround: There is no workaround. DE27944 Symptom: On the Home > RF Health page, the label for the X-axis on the Client Speed chart is incorrect, showing 96 Mbps instead of 96+ Mbps. Client speeds can be beyond 96 Mbps. Workaround: None. DE28305 Symptom: The AirWave Glass single-sign on (SSO) feature does not allow AirWave Glass users to open the WebUI of a managed AMP from the VisualRF pages of the AirWave Glass WebUI. Workaround: None. DE28307 Symptom: The Trend graphs on the Home > Overview, Home > RF Health and Home > Client Session pages display an inconsistent scale on the x-axis when viewing data collected over a four-week sampling period. Workaround: None. DE28470 Symptom: When you try to sort reports by name, type, occurrence, or time stamp, nothing happens. Workaround: None. 13 Known Issues AirWave Glass Release Notes

14 Chapter 5 Installing AirWave Glass The following sections of this document describe the software installation requirements, installation procedures, and the comunimcation ports and protocols used by AirWave Glass. Installation Requirements The system requirements are: Memory: 96 GB Hard disk: 1 TB CPU: a minimum of 16 cores VMware requirements are: VMware ESX(i) 5.5 and 6.0 Install VMware Tools in a text-based environment prior to installing AirWave Glass Allocate enough resources to the VM If your VM host is hosting other instances, ensure that the AirWave Glass instance has the highest priority A virtual SCSI disk is recommended over IDE The supported browser versions are: Google Chrome (64-bit) or higher Firefox (64-bit) or higher Safari ( ) or higher Internet Explorer Version or later Installing the OVA File The AirWave Glass software is available for download as an OVA file on the Aruba support site. When you launch the OVA file, you are prompted to complete the installation procedure described in the steps below. Getting Started Perform the following steps to install the software from the CLI. 1. Log in to the server using the default admin user name and password (admin/admin). 2. At the command prompt, issue the command sudo glass-install. 3. After the installation completes, issue the command glass-setup. Step 1: Configuring the AirWave Glass Server This step requires you to enter the network settings for your AirWave Glass server. 1. Each prompt displays default values populated via DHCP, if available: Server IP address Subnet mask Gateway IP address DNS server IP address AirWave Glass Release Notes Installing AirWave Glass 14

15 Secondary DNS server (optional) Server hostname, which is a fully qualified domain name (FQDN) Step 2: Preparing Your Deployment This step requires you to choose your deployment. The following message appears after you configure the AirWave Glass server: Do you want to deploy multi-node Glass cluster (y/n)? Set Up the Single Node 1. If you choose to deploy a single node, enter n. A message similar to the following appears: Verify Setup Hostname : myserver.example.com IP Address : xxx.xxx.xxx.xxx Subnet : xxx.xxx.xxx.xxx Gateway : xxx.xxx.xxx.xxx DNS : xxx.xxx.xxx.xxx Secondary DNS : xxx.xxx.xxx.xxx Multi-node Glass Cluster : false Please enter 'y' if you want to continue the installation or 'n' to modify above input. Do you want to continue (y/n)? 2. Enter y to confirm the configuration settings and continue the installation. The following message appears: Enabling Glass components Configuring Glass services Enable Glass service completed Deploying GLASS apps Configuring post deploy Settings Glass setup completed. Set Up the 3-Node Cluster 1. If you choose to deploy a cluster, enter y to create the 3-node cluster. A message similar to the following appears: Verify Setup Hostname : myserver.example.com IP Address : xxx.xxx.xxx.xxx Subnet : xxx.xxx.xxx.xxx Gateway : xxx.xxx.xxx.xxx DNS : xxx.xxx.xxx.xxx Secondary DNS : xxx.xxx.xxx.xxx Multi-node Glass Cluster : true Please enter 'y' to continue installation or 'n' to modify above input. Do you want to continue (y/n)? 2. Enter y to confirm the configuration settings and continue the installation. 15 Installing AirWave Glass AirWave Glass Release Notes

16 The following message appears: Glass basic setup completed on <IP address of Glass Hostname> Please complete basic setup on all Glass nodes to be deployed as Glass Cluster. After completing basic setup, run cluster-setup command on one of the node to complete Glass cluster configuration. 3. Select 1 to create the new cluster. 4. You are prompted to enter the following virtual network settings for your cluster: Glass virtual IP address Glass cluster hostname, which must be unused by any node in the cluster and a fully qualified domain name (FQDN) 5. You are prompted to enter comma separated IP addresses for the other 2 nodes that will form the 3-node cluster. Follow the onscreen instructions when prompted to finish the cluster setup. 6. After all AirWave Glass nodes are joined to the cluster, validate the cluster configuration using the clustersetup command: Select 1 to show the details of the Master and Master HA nodes. Select 2 to add a node. At the prompt, enter the node IP address. AirWave Glass 1.1 or later supports only 3-node clusters. Select 3 to remove a node. At the prompt, enter the node IP address. 7. Select q to exit the cluster setup session. Communication Ports and Protocols In order to allow traffic between AirWave and AirWave Glass across firewall devices, you need to open the ports described in Table 8. Table 8: Ports and Protocols Port Protocol Description 22 TCP Used for support connection for debugging AirWave-related issues 443 TCP Used for secure web socket communication between the feeder service running on managed AMPs and AirWave Glass. 443 TCP Used to pull images and metadata from the Internet. NOTE: In order for AirWave Glass to pull Kubernetes images from gcr.io and AirWave Glass images from quay.io, you must open port 443 for the following URLs: gcr.io/google_containers, quay.io/arubadevops, and quay.io/coreos. ICMP Used by the feeder service, by running ICMP ping, for checking connectivity between the managed AMPs and AirWave Glass and building secure Java keystores. AirWave Glass Release Notes Installing AirWave Glass 16

17 Chapter 6 Upgrading AirWave Glass AirWave Glass supports online upgrades in deployments that are able to access the AirWave Glass software download servers, as well as an offline upgrade method for deployments that do not have access to the internet, or that are unable to download the software upgrade due to security issues. If you are upgrading from AirWave Glass 1.1.x, you must also run the CoreOS upgrade and then the Kubernetes upgrade after upgrading to AirWave Glass These procedures are described in detail in the following sections of this document: "Online AirWave Glass Upgrades" on page 17 "Offline AirWave Glass Upgrades" on page 18 "Post Installation" on page 18 Online AirWave Glass Upgrades When you run the online software update, the process might take more than 20 minutes and requires multiple clicks through upgrade notification windows. Each click starts the upgrade of a subset of pods. This upgrade is best done during server downtime or less busy hours to avoid AirWave Glass missing messages from the attached managed AMP. You may need to repeat this procedure and perform multiple upgrade cycles until you don't see online upgrade notifications. To ensure that your system receives the most up-to-date software version available, it is recommended that you add coreupdate.central.arubanetworks.com and gcr.io/google_containers to your whitelists. To upgrade to AirWave Glass 1.2.3: 1. Click to download the software. 2. Click the blue Upgrade link in the notification window to run the software. Figure 1: Upgrade Available 3. When the WebUI is up, confirm your upgrade version by checking the notification window. AirWave Glass Release Notes Upgrading AirWave Glass 17

18 Figure 2: Latest Version Offline AirWave Glass Upgrades We provide an offline upgrade for organizations to update the software version without having to connect to the Internet. AirWave Glass has two installation scenarios: If this is your first time running an offline upgrade, follow the steps in "Performing the Offline Upgrade for the First Time" on page 18, and then proceed to "Installing the Offline Upgrade Package" on page 18. However, if your managed AMPs are running AirWave , you can proceed to "Installing the Offline Upgrade Package" on page 18. If this is not your first time performing an offline upgrade, follow the steps in "Installing the Offline Upgrade Package" on page 18. All log messages collected during the upgrade are saved to the /var/log/glass-setup.log file. Performing the Offline Upgrade for the First Time Follow these steps if you're installing the offline upgrade package for the first time to copy the feeder image onto your AirWave servers: 1. Copy the feeder updater tar file to all AirWave servers associated to AirWave Glass. 2. On each managed AMP, load the feeder updater file using the command docker load < feeder_ updater.tar.gz. This process takes a few minutes to complete. 3. Proceed to "Installing the Offline Upgrade Package" on page 18. Installing the Offline Upgrade Package If you've performed the offline upgrade before, or you installed the feeder updater and are ready to install the offline upgrade package: 1. Copy the offline upgrade package tar file to the offline AirWave Glass server. Or copy the files to the master node for clusters. 2. Log in to the AirWave Glass server as admin. 3. Run the glass-upgrade command. 4. Select 3 to run the offline upgrade. 5. At the prompt, enter the file location of the offline upgrade package file. If you are upgrading a cluster, enter the password for each node. 6. After the upgrade completes, select q to quit, then press Enter. Post Installation You can check the AirWave Glass version by pointing the mouse over in theairwave Glass WebUI and the feeder version by navigating to System > Managed AMPs. After verifying your installation, review the following sections and decide whether the tasks are necessary. 18 Upgrading AirWave Glass AirWave Glass Release Notes

19 After an Upgrade to AirWave Glass AirWave Glass includes a simplified way to refresh your certificates. The following procedures describe how to refresh the web proxy and Kubernetes certificates on your AirWave Glass server, as well as the client certificates on your managed AMPs. Refresh Expiring Certificates After upgrading to AirWave Glass 1.2.2, AirWave Glass alerts you to expiring certificates with a warning banner at the top left corner of the WebUI. You can click to expand and to collapse the warning banner. If a certificate expires within 10 to 90 days, AirWave Glass displays the banner shown in Figure 3. This banner is collapsed by default. Figure 3: 10 to 90-Day Notification If a certificate expires in less than 10-days, AirWave Glass displays a banner similar to the example shown in Figure 4. This banner is expanded by default. Figure 4: Less than 10-Day Notification This feature isn't available for custom certificates, or certificates that have already expired. Contact Technical Support if you want to refresh a custom certificate, or your certificates have already expired. To refresh certificates: 1. Log in to the AirWave Glass server with the admin user name and password. 2. At the prompt, run the upgrade tool: glass-upgrade 3. Enter 4 to refresh your certificates. This process takes a few seconds to complete. The following message appears: ================================================================ This option will refresh the kubernetes Certificates and Nginx certificates. If custom certificates are used, they will not be modified. During this operation the system may be inaccessible for a while ================================================================ A message similar to the following appears: AirWave Glass Release Notes Upgrading AirWave Glass 19

20 ================================= Running Nginx certificate refresh ================================= Refresh nginx certs Web-server certificate is about to expire in 90 days Refresh Nginx server cert Delete old kube secret for nginx secret "test-pdtl-arubathena-com" deleted Generating a 2048 bit RSA private key writing new private key to '/var/airwave/glass/build_output/server.key' Create kube secret with nginx cert using server-cert.yaml secret "test-pdtl-arubathena-com" created Restart all webproxy pods pod "webproxy-632vg" deleted pod "webproxy-h2cvh" deleted Finished refreshing nginx certs ====================================== Running kubernetes certificate refresh ====================================== Refresh kubernetes certs 4. When prompted, choose your deployment and enter the admin user name. Is glass in cluster mode? (y/n) Please enter a common admin username for ssh connections(most likely it is admin or awsupport): a. For a single-node deployment, enter n. b. For a 3-node cluster, enter y. If prompted, enter the admin password for each cluster node. Allow several minutes for AirWave Glass to refresh the certificates and, possibly, to generate private keys. 5. Wait for AirWave Glass to complete the process, then press Enter. 6. Select q to quit. Refresh Client Certficates on the Managed AMP Follow these steps to regenerate expired client certifcates in the AirWave Glass WebUI: 1. Navigate to System > Managed AMPs, locate the AMP, and click to modify its settings. 2. Select the Regenerate Service Credentials checkbox to refresh the client certificates and all API secrets on the managed AMP. 3. Enter the user name and password on the managed AMP. After an Upgrade from AirWave Glass A cluster upgrade from AirWave Glass or earlier requires that you upgrade the CoreOS on only the master node in a cluster. This upgrade process takes about 15 minutes to complete, depending on the size of the cluster. The following procedure describes how to upgrade an AirWave Glass cluster from AirWave Glass. This step is only required for upgrades from AirWave Glass or earlier releases. Running the CoreOS Upgrade For a single-node upgrade, you only have to run the upgrade on the single-node. Single-node upgrades will be faster. Refer to "Upgrading a Single-Node" on page 21 for more information. 20 Upgrading AirWave Glass AirWave Glass Release Notes

21 Upgrade the CoreOS before you upgrade Kubernetes. Upgrading the AirWave Glass Cluster To upgrade the cluster to CoreOS : 1. Log in to the master node with the admin user name and password. 2. At the prompt, run the upgrade tool: glass-upgrade 3. Enter 1 to select Core OS upgrade. Figure 5: Running the CoreOS Upgrade 4. Wait for the upgrade to finish completely. When run from the master node, the process will upgrade the CoreOS on all cluster nodes. 5. Reboot the master node first, and then each node in the cluster: sudo reboot 6. After the all the nodes are up, set which partition to use after you change the CoreOS on every node in the cluster, in no particular order: sudo /usr/sbin/coreos-setgoodroot 7. Reboot the master node first, and then each node in the cluster: sudo reboot After the nodes are up, the Kubernetes cluster takes 5 to 10 minutes to stabilize. 8. Confirm the CoreOS version: more /etc/os-release Figure 6: Confirming the CoreOS Version Upgrading a Single-Node To upgrade the single-node to CoreOS : AirWave Glass Release Notes Upgrading AirWave Glass 21

22 1. Log in to the AirWave Glass server with the admin user name and password. 2. At the prompt, run the upgrade tool: glass-upgrade 3. Enter 1 to select Core OS upgrade. Figure 7: Running the CoreOS Upgrade 4. Wait for the upgrade to finish completely, then reboot the AirWave Glass server: sudo reboot 5. After the AirWave Glass server is up, set which partition to use after you change the CoreOS: sudo /usr/sbin/coreos-setgoodroot 6. Reboot the AirWave Glass server: sudo reboot After the AirWave Glass server is up, the Kubernetes cluster takes 5 to 10 minutes to stabilize. 7. Confirm the CoreOS version: more /etc/os-release Figure 8: Confirming the CoreOS Version Running the Kubernetes Upgrade If you are upgrading an AirWave Glass cluster, the process upgrades the master node and cluster nodes all at once. For a single-node upgrade, you only have to run the upgrade on the single-node. To upgrade to Kubernetes Version 1.5.4: 1. Log in to the AirWave Glass server with the admin user name and password. 2. At the prompt, run the upgrade tool: glass-upgrade 3. Enter 2 to run the Kubernetes upgrade. This process takes about 5 minutes to complete. 4. Allow 5 to 10 minutes for the Kubernetes cluster to stabilize. 22 Upgrading AirWave Glass AirWave Glass Release Notes

23 5. Confirm the Kubernetes version: kubectl version Figure 9: Confirming the Kubernetes Version AirWave Glass Release Notes Upgrading AirWave Glass 23