Release Notes for AutoMesh 7.17(N).0.0

Transcription

1 Release Notes for AutoMesh Software and firmware: HotView Pro software and HotPort firmware Effective date: 1/23/2015 Hardware compatibility: The table below lists the product-specific software in this release: Product Version HotPort 5020-LNK HotPort 5020-E HotPort 5020-M HotPort 7000 HotPort HotPort (N).0.0 FMC-2000 HotPoint AP (N).0.0 HotView Pro This release supports PostgreSQL Database versions 9.1 to 9.4. Upgrade table You can upgrade to Automesh from the versions listed in the following table FMC-2000 HotView Pro HotPoint 5xxx 7.16(M1) (M1) (M1) (N) (M1) (N) NA -- NA Additionally HotPoint 5xxx can be upgraded directly from the version mentioned in the following table: Firmware Hotview Version Version 5.54(E) New Features Automatic Profile Switching (APS) In a linear mobility deployment, a Mobility Node (MN) considers a set of parameters to decide the best radio to attach to, in order to achieve the best possible throughput. This set is called a profile and is dependent on the direction of movement of the MN. Prior to this release, it was

2 required to manually change the profile on the MN using a CLI each time an MN reverses its direction of movement. APS enables a MN to: 1. Detect a change in the direction of movement and antenna orientation. 2. Change its profile automatically; without any user intervention. Mobility Configuration Toolkit (MCT) MCT is a collection of tools that helps to quickly deploy and debug a linear mobility installation. It helps in RF planning and troubleshooting, node and antenna placement, traffic analysis and linear mobility configuration. o Coverage graph: A pre-deployment tool useful for visualizing the RF coverage for mobility deployments. o Throughput graph: A post-deployment tool useful for troubleshooting throughput and performance related issues for mobility deployments. HotView Server Redundancy HotView Server Redundancy provides high availability to manage and monitor meshes in case of HotView Server system failure. The active HotView Pro Server will have the capability of managing the network. On switch over the redundant HotView Pro Server can be used to load and manage the network. Firmware Rollback Firmware Rollback feature provides a way to downgrade a mesh node to immediate previous firmware that was running on the node. This feature is available from 7.17 onwards. E.g. if a mesh is upgraded from 7.16(M1) to 7.17 release, the firmware can be rolled back to 7.16(M1). Please note that the configurations on the node will also be restored to the state just before the current upgrade i.e. corresponding to the rolled back firmware. Licensing Enhancements 1. Users can now replace multiple licenses on multiple nodes (which are to be replaced due to hardware failures) at once by generating a Request for Transfer File. The same needs to be authorized on the licensing server and the Request Approved File will be sent back to the customer. 2. There will be a single reboot for all the licenses applied on nodes provided that the node is currently loaded in HotView. 3. License Backup and Restore feature to restore the backed up license to the new HotView server system, in case of server system crash. 4. Licensing Master and Slave model will enable the capability of applying licenses to nodes through multiple HotView servers. WDS Client Roaming - This feature is intended for WDS clients and helps in identifying and connecting to the best WDS server visible to the WDS client. This provides the twin benefits of redundancy and also a better network link resulting in improvement in overall network throughput. Enhancements on SNMP o Addition of mesh id and HotPort name in native trap. o Native SNMP traps can be sent via available links (Ethernet / Wireless). o Improved SNMP trap community string to configure up to 32 characters. Bug Fixes The following issues have been resolved: Page 2 of 6

3 Port 2 in Mobile Node Redundancy setup will send untagged packets on trunk port. A mobile node will not attach to a static node after a period disconnect from the mobility controller. While running UDP Iperf Test in Hotview Pro between 7000 and 5020-M, throughput results will show values exceeding 25 Mbps. Problems with sorting alarms based on time by default and reporting all alarms. Known Issues, limitations, and Notes Firmware Rollback In case firmware needs to be rolled back on 7xxx mobile nodes the same can be done by making the mobile node as head node. Using the Switch Firmware option in HV, it is possible to switch firmware from 7.17 to 7.16(M1), (but not vice versa). HV Redundancy This feature is supported for meshes with the following platforms: FMC2000, 7xxx, 7xxx-900, 6xxx, 5020-M, 5020-E, 5020-LNK. Other features Telnet to mobile node option from Mobility View is removed. If High Security was configured on the mesh, upon upgrading from to , it gets reset to Low Security. User can configure the high-security again on Operating 5020 nodes on a mesh with interop enabled is not supported. Before configuring Mobile Node redundancy, both nodes of the MNR pair need to be loaded as head node at least once in HotView after applying the licenses on the MNs. The maximum size of linear mesh supported on 7xxx is 15 nodes (or 14 hops). If using Java-8 64-bit, edit the PATH in Windows System Environment variables before starting HV installer as below : E.g. - Remove the entry -> C:\ProgramData\Oracle\Java\javapath - Add the entry (Path of java.exe file) -> C:\Program Files\Java\jre1.8.0_25\bin In a congested environment, it is not recommended to configure a fixed high data rate on mobile nodes On setups where FMC redundancy is configured, SSH should not be disabled HotPoint 5000s (APs) When configuring a static IP on the access point, the subnet mask supported is Since this feature was not working properly, the option to configure both the 2.4 and 5 GHz frequencies on both radios of 5000 Series HotPoint AP has been removed. Upgrade Procedures This section contains the upgrade procedures for each product type Mesh Upgrade Procedures Static Mesh Page 3 of 6

4 Login to the Mesh using HotView Pro version (e.g ) corresponding to the firmware on the nodes Take a backup of the mesh-wide and node configurations, mesh analytics data, and database Close the existing HotView Pro Install the new HotView Pro version 10.17(N).0.0 and launch it Verify that no DB related errors are seen which ensures that the database tables update happened smoothly Load the mesh into HotView Pro 10.17(N).0.0 and ensure that all mesh nodes are loaded Upgrade the mesh, Gateway Server, Gateway Interface, and Access Points via the upgrade scheduler. In case of redundant GWS in the mesh, it is recommended to upgrade both GWS nodes at the same time. If the mesh has redundant GWS the recommended sequence for upgrade is as follows: o Upgrade both GWS and R-GWS to the target image at the same time o OR o After R-GWS is upgraded, unplug the R-GWS from the common switch connecting to GWS and load GWS in Hotview and proceed with GWS upgrade. After upgrade the nodes will reboot and load back into HotView Ensure that all nodes are running the latest firmware Mobility Mesh Login to the FMC & Mesh using HotView Pro version (e.g ) corresponding to the firmware on the devices (e.g ) Take a backup of mesh-wide configuration, node configurations and FMC configuration Take a backup of mesh analytics data (applicable for HotView Pro and upwards) If using database, take DB backup, taking care to choose the role and format as tar when using PostgreSQL 9.1. The role field is the same user configured in DB screen of HV Server and PostgreSQL Close the existing HotView Pro (e.g ) Install HotView Pro 10.17(N).0.0 and launch it Verify that no DB related errors are seen which ensures that the database tables update happened smoothly Load the FMC & Mesh into the new HotView Pro 10.17(N).0.0 and ensure that all devices are loaded Disconnect the secondary(standby) FMC Upgrade the active/primary FMC to the latest image Disconnect the primary FMC, and reconnect the secondary FMC Once the secondary FMC becomes Active upgrade it to Reconnect both FMCs to the setup After the FMCs come up in the HotView Pro, proceed to upgrade the mobile node(s) through the FMC Upgrade the mesh, Gateway Server, Gateway Interface, and Access Points via the upgrade scheduler. In case of redundant GWS in the mesh, it is recommended to upgrade both GWS nodes at the same time. If the mesh has redundant GWS the recommended sequence for upgrade is as follows: o Upgrade both GWS and R-GWS to the target image at the same time o OR o After R-GWS is upgraded, unplug the R-GWS from the common switch connecting to GWS and load GWS in Hotview and proceed with GWS upgrade. After upgrade the devices will reboot and load back into HotView Ensure that all devices are running the latest firmware 5020-LNK Login to the 5020-LNK network using existing HotView Pro (e.g ) corresponding to the firmware on the 5020-LNK nodes (e.g ) Page 4 of 6

5 Backup all configurations and take a database backup Close the existing HotView Pro (e.g ) and install the HotView Pro 10.17(N).0.0 and launch the software Verify that no DB related errors are seen which ensures that the database tables update happened smoothly Add the 5020-LNK nodes as a new Mesh and upgrade to release After upgrade the nodes will reboot and load back into HotView Ensure that the nodes are running the latest firmware HotPoint-5000 Upgrade Procedures Upgrade using HotView Pro Log into the Hotpoint5xxx using Hotview Pro corresponding to the firmware running on the 5xxx HotPoint devices Take a backup of all HotPoint devices and database Close the existing HotView Pro, install the new HotView Pro 10.17(N).0.0 and launch it Verify that no DB related errors are seen, which ensure that the database tables update happened correctly Add the HotPoint 5000 APs in the new HotView Pro 10.17(N).0.0 Upgrade the HotPoint-5000 units to firmware 5.56(N).0.0 by initiating upgrade via the upgrade scheduler After upgrade the HotPoint-5xxx devices will reboot Ensure that each HotPoint-5xxx is running the latest firmware Upgrade Procedure using AP HTTP Open a web browser and enter an AP s IP Address in address bar and press Enter Login with the username and Password as admin and firetide respectively Go to Maintenance -> Upgrade and then click on choose file to select the desired firmware file Click on the Apply Button to begin This process can take between 2-3 minutes to complete Check the firmware version via the web interface to confirm the change Upgrade Procedure using script Save upgrade_ zip on your system and extract the zip content An upgrade_ folder will be created Navigate into this folder and open the IP_LIST.cfg file using Notepad Add the IP Address of each IP that you intend to upgrade (a unique IP Address per line) Save and close the file Double-click on the AP_FW_Upgrade.exe file to start the upgrade procedure This process can take between to 4-5 minutes to complete and the HotPoint-5xxx devices will reboot After upgrade, verify that the latest firmware version is getting displayed via HotView Pro/ HTTP Appendix A System requirements: The following Operating Systems, Java versions, and database versions have been tested and verified with this release: Operating System Java Version DB version Windows 7 Professional 32 Bit OS Java 1.7 update 14, update 51, update 60, update 67 PostgreSQL 9.1, PostgreSQL9.3 Page 5 of 6

6 Windows 7-64-bit-OS Windows 8 Professional 64- bit OS Windows Server bit OS Windows Serve bit-os Fedora bit OS Java 1.6 update 02, update 37 Java 1.7 update 45, update 147 Java 1.8 update 25 Java 1.7 update 71 Java 1.7 update 21 Java 1.8 update 25 Java 1.8 update 25 PostgreSQL9.4 Page 6 of 6