Searching...

Matching results

    Release Notes for AM/AMM 2.17

    1 Release Information

    AirLink Manager (AM)/AirLink Mobility Manager (AMM) 2.17 is a major release of the AirLink Manager Platform that introduces a new configuration management approach, introduces certificate management capabilities for the AirLink MG90, improves the High Availability capabilities of the platform, adds support for the AirLink RV55, and provides new features in support of both MG and ALEOS devices in the product.

    After completing an upgrade of the AM/AMM, Sierra Wireless recommends that all users refresh their browser cache before accessing AMM 2.17. To continue to improve the security posture of the AM/AMM platform, this release also disables the auto-login capabilities that were previously included in the AM/AMM.

    These release notes include the details for AM/AMM 2.17, AMMER 1.0.4 and AVTC 1.01.

    1.1 Officially Released Versions

    These release notes are inclusive of all AMM R2.15.x+ versions.

    AM/AMM 2.17 was officially released to General Availability on February 28, 2020.

    1.2 Platform Support

    AM/AMM 2.17 has been tested on Dell R240 and R630 servers and on VMWare ESXi.

    1.3 Browser Support

    AMM 2.17 has been tested on Google Chrome and Firefox. Users that attempt to use a browser that is not supported will get a warning and may experience some issues.

    1.4 Sierra Wireless Gateway Support

    For oMG gateways, AMM 2.17 supports up to oMG R3.15.1 and MG90 4.x+. For AirLink gateways, AMM 2.17 supports ALEOS firmware version 4.4.3 and higher. Some features of AM/AMM 2.17 require later versions of the ALEOS or MG software.

    AMM 2.17 also supports:

    • GNX6: G604.08.01 and higher (limited support)
    • GNX3-UMTS: G303.08.83 and higher (limited support)
    • AirLink RV55 (new)
    • Calamp LMU2631CV model (limited support)

    2 Key Features and Enhancements

    2.1 Configuration Management – Templates

    AM/AMM 2.17 redefines the approach to managing device configurations, including the introduction of templates that can be created directly in the management system. Specific features include:

    Configuration Templates: allows you to create, manage, and deploy device configurations directly from the AMM. Users can create a configuration from an existing known configuration on a device, or build something new from scratch.

    Set Device-Specific Parameters: As part of the template, settings that require device-specific parameters are set through the configuration template wizard using an integrated CSV import/export.

    Create and Target Configurations for Offline Devices: Remote configuration of devices can be done through the new Configuration Template and Configuration Control screens while gateways are offline. This functionality allows you to define templates which can be deployed either manually or automatically when the target devices are online.

    Simplified Device States: The new Configuration Control screen displays a more user-friendly interface and a reduced set of device configuration states. You can click on states to “drill down” on them to get more information and view more detailed legacy states.

    Export Configuration Templates: Users can export configuration templates from one AM/AMM instance and import them into another.

    Device Requirements for Template Support: The new configuration management that uses the Templates feature is supported for all of our currently-shipping AirLink devices. As AM/AMM also supports older hardware, there are some limitations as to the device and firmware versions that can be supported:

    • AirLink MG90
      • Supports MGOS 4.3+
    • AirLink Gateways and Routers Running ALESO
      • 4.4.5 or later (AirLink GX400/440, ES440 and LS gateways)
      • 4.9.0 or later (AirLink GX/ES450, RV, MP and LX gateways and routers)
    • The oMG2000/500 class of routers are not supported with the new Configuration Management features. Customers should continue to use the existing configuration management capabilities.

    Note: Many features in the AM/AMM are controlled by user access rights. When new features are deployed, they may not be immediately available to all users. As Configuration Management capabilities in previous releases of AM/AMM were not always exposed to all users (particularly on hosted AMMs), you may not have access to the new Template features once your system is upgraded to AM/AMM 2.17. If you do not see the new features, but want them enabled, please contact Sierra Wireless Customer Support and they will enable these new features on your user account.

    2.2 Certificate Management (MG90)

    AMM 2.17 introduces the first phase of managing device certificates for the AirLink MG90. The Certificate Management screen allows you to trigger the bulk generations and transfer of certificate signing requests (CSRs) and signed certificates from/to gateways.

    The Certificate Management features require MGOS 4.3+.

    2.3 High Availability (HA)

    AM/AMM 2.17 introduces an improved HA capability that provides an active standby deployment that uses a “hot” standby AM/AMM server to increase reliability and simplify the backup process for deployed AM/AMM servers. This feature requires an AM or AMM Enterprise license to leverage multiple server instances.

    2.4 Gateway Tree UI Improvements

    The Gateway Tree is the primary user interface to organize and view devices in the management system. This release introduces the ability to filter by both heartbeat and platform. The Gateway Tree now also includes a checkbox that automatically selects all visible nodes throughout the tree hierarchy. This can be used in conjunction with the filter options to select a certain group of devices for which you want to invoke an operation.

    2.5 User Creation Improvements

    This release streamlines and simplifies the process for creating new users. Many of the default parameters are set by default, making it easier to set up new AM/AMM users and ensure their basic user rights are set correctly.

    2.6 On-line Documentation

    As of AM/AMM 2.17, all user documentation has been moved online at https://source.sierrawireless.com/airvantage/amm/ . Sierra Wireless will no longer produce PDF versions of our AM/AMM documentation.

    The AirLink® RV55 is the industry’s most rugged, compact, LTE-A Pro router. Simple to install, and easy to manage, the RV55 cellular router is designed for connecting critical remote assets and infrastructure, and vehicles. The RV55 is especially well suited for SCADA, distribution management systems, and service vehicle fleets.

    The RV55 is also available with Wi-Fi to provide secure, vehicle area networking (VAN) for the mobile workforce and service fleets. The RV55 is designed to meet the harsh environmental and performance requirements of industrial and mobile installations, delivering superior reliability and uninterrupted operation in outdoor or vehicle environments. The RV55 is a certified device that is “Band 14 and FirstNet Ready”.

    AM/AMM 2.17 is required to support the AirLink RV55.

    3 Minor Feature Enhancements

    There are many minor new features added in AM/AMM 2.17.

    3.1 “What’s New” Feature

    To better inform customers of the features in a new release, AM/AMM 2.17 includes a “What’s New” feature that appears to all users when they log on to the platform. This new information screen will appear on every new release the first time a user logs in to the AM/AMM. The user has two options to close the dialog once they have reviewed the new information:

    • The Got it button prevents the pop-up showing on following logins
    • The Close button closes the dialog but allows the pop-up window to continue to appear on subsequent logins

    3.2 Cancel Software Upgrade

    This release adds the ability for the AM/AMM user to cancel software upgrades that have been triggered from the AM/AMM. The ability to cancel has dependencies on platform, firmware versions, and the upgrade stage that a device is currently on. There will be situations where a software upgrade may not be able to be canceled. As part of this implementation the AM/AMM provides a detailed explanation of what can or cannot be done when a user attempts to cancel a software upgrade from the Software Distribution page.

    3.3 Renamed the “Config > Deploy > Deploy” Menu to Configuration > Deployment > Configuration Control

    As part of the introduction of Templates and the changes to the configuration management process, the menu items names have been changed. This reflects the new processes and is consistent with new terminology and the new pages introduced with the new configuration management processes.

    For customers that cannot automatically download new gateway software packages on their AM or AMM, we have added a link to the repository so those users can more easily download the software they need and upload it to their AM or AMM.

    3.5 Removed Latitude and Longitude from Default AM/AMM Thresholds

    Latitude and Longitude were added as default Stats in a previous release of AM/AMM. As default Stats cannot be removed and the Dashboard has limited space, this causes issues for many customers. Users can always add the Stats to their Dashboard if this data is important to them.

    3.6 Provide Full Control Over the Software Repository

    Admin users can now delete versions of gateway software from the repository.

    3.7 Dead Reckoning (DR) Available as a Stat

    With this release, DR state can be enabled as a Stat and reported on the Dashboard.

    3.8 GPIO Inputs Supported as Stats for ALEOS-based Devices

    With the release of AMMER 1.0.4, we now send digital and analog input state and value transitions for ALEOS-based devices. These can be mapped to Stats and used in a similar way as the GPIO from an MG-based device.

    3.9 Removal of the Nav Application

    As was communicated to all customers, Sierra Wireless retired the Nav application in the AM/AMM and have now removed this feature from AM/AMM 2.17.

    4 New ALEOS Application Framework (AAF) Applications

    4.1 AMMER 1.0.4

    AMMER 1.0.4 is an incremental update to the AMMER AAF application that is needed to support advanced features on the AM/AMM for ALEOS devices. There were three new features added in AMMER 1.0.4 to support AM/AMM features in AM/AMM 2.17:

    • Provide Management Tunnel Status and Address Events
    • Send Dead Reckoning configuration state and status to the AM/AMM
    • GPIO input line status needs to be forwarded individually to the AM/AMM

    4.2 AVTC 1.0.1

    Airlink Vehicle Telemetry Configuration (AVTC) is an AAF application that contains details on the collection of proprietary vehicle configuration information. AVTC contains only configuration data and GNX companion firmware. It has no executable component and it is safe to install AVTC on any compatible AirLink device where vehicle telemetry is in use. AVTC is a companion application and requires AVTA or AMMER to report information to ALMS or AMM respectively.

    5 Addressed Problems

    Customer Reported Field Issues

    Reference Problem Description
    7338

    Addressed an issue where the Top Client report was using excessive memory.

    8640

    Addressed an issue where MG90s with a serial number ending of B104 were unable to be added to an AMM server.

    8475

    Addressed an issue where the Link Utilization report shows different results for different start times.

    8452

    Addressed an issue wherein Browse log files …, ALEOS uploaded messages files (i.e., messages1, messages2, etc.) could only be seen by users whose time zone had been set to Pacific Time.

    7989

    Addressed an issue where once an ALEOS device has started downloading software from the AMM, the software update feature can no longer be canceled from management server side. We are now able to command the device to abort the update while it’s downloading software, or its software is downloaded, or installation has started.

    7453

    Addressed an issue where the AM/AMM will not register new gateways without manual intervention after experiencing a temporary database connection issue.

    7219

    Addressed an issue where the master configuration script for an AM/AMM installation generated an error when configured with a GoDaddy-signed server certificate. There are no validation errors if the currently installed certificate is signed by Comodo or GoDaddy, as both CAs are fully supported by ALEOS devices.

    7116

    Addressed an issue where remote ACEmanager access was not going through a reverse proxy, breaking certificate validation in HTTPS.

    6940

    Removed the check on software package installation.

    When a software release is used in AM/AMM, which is either installed or targeted for upgrade on at least one gateway, users will now be able to purge such a software release. The AMM will warn users that this will affect their gateways’ software distribution. Once the software is purged, any gateway’s individual upgrade repo pointing to it will be removed.

    6752 Addressed an issue introduced in AM/AMM 2.16.2 that caused sorting issues of the Heartbeat on the Dashboard.
    6533 Addressed an issue where the Copy Config feature could overwrite the odometer setting on ALEOS devices.
    6525

    Addressed an issue where creating an account that only had access to the Dashboard would allow the user to access additional tabs.

    6478 Addressed an issue where the ALEOS gateway software in an AM/AMM repository could no longer be used for upgrades after an AMM IP address change.
    6416 Addressed an issue where the AMM will occasionally erroneously indicate an in sync configuration on a device that is not in sync.
    6269 Removed references to InMotion from emailed reports.
    5583

    Improved the OpenVPN authentication process to address a known issue.

    ALEOS gateways (serial number) must now be present in the authunits file in order to establish a management tunnel, which is required for remote ACEmanager and remote console access. This behavior is now identical to MGOS (previously, only MGOS needed to be present in the authunits file).

    Addressed CIS Compliance Audit Issues

    Reference Problem Description
    7320 This release improves the security of the AM/AMM by ensuring that secure options are in place for various file partitions.
    7331

    As the AM/AMM does not support IPv6, this release disables all IPv6 settings.

    7329 This release improves the security of the AM/AMM by ensuring that NFS and RPC are not enabled.
    7328 This release improves the security of the AM/AMM by ensuring that warning banners are configured properly.
    7327 This release improves the security of the AM/AMM by ensuring that GPG keys are configured.
    7319 This release improves the security of the AM/AMM by ensuring that mounting of various unused filesystems are disabled.

    Software Distribution Issues

    Reference Problem Description
    8650 Addressed an issue where the Download button that is supposed to be in the Admin > Software > Repository on the AM server was not showing.
    6048

    Improved support for canceling on-demand software upgrades.

    Users can now cancel software upgrades in the AMM. However, depending on the platform, firmware versions, and upgrade stage a device is currently on, its software upgrade may not be able to cancel. The AM/AMM will provide detailed reasons when a user attempts to cancel an upgrade from the Software Distribution page.

    GNX Issues

    Reference Problem Description
    7907 The AMM can now support new GNX serial number formats without the need for a new software release.

    Security Vulnerabilities

    Each AMM release addresses any security vulnerabilities discovered since the previous release. This release addressed vulnerabilities as identified in 428 CVE tickets.

    • CVE-2019-14869
    • CVE-2018-19519
    • CVE-2019-14821
    • CVE-2019-15239
    • CVE-2019-11135
    • CVE-2019-0154
    • CVE-2019-0155
    • CVE-2018-12207
    • CVE-2019-14287
    • CVE-2019-13638
    • CVE-2018-20969
    • CVE-2019-14835
    • CVE-2019-14811
    • CVE-2019-14812
    • CVE-2019-14813
    • CVE-2019-14817
    • CVE-2019-1010238
    • CVE-2019-0217
    • CVE-2019-0220
    • CVE-2019-14744
    • CVE-2018-7191
    • CVE-2018-20836
    • CVE-2019-3901
    • CVE-2019-11487
    • CVE-2019-12381
    • CVE-2019-12382
    • CVE-2018-20169
    • CVE-2014-4014
    • CVE-2018-19824
    • CVE-2015-1465
    • CVE-2019-13233
    • CVE-2019-14283
    • CVE-2019-14284
    • CVE-2019-13631
    • CVE-2019-11833
    • CVE-2019-11810
    • CVE-2019-3900
    • CVE-2019-11599
    • CVE-2019-3460
    • CVE-2019-3459
    • CVE-2019-5489
    • CVE-2018-18281
    • CVE-2018-15594
    • CVE-2019-11811
    • CVE-2008-4609
    • CVE-2010-3865
    • CVE-2015-1210
    • CVE-2015-1211
    • CVE-2015-0312
    • CVE-2015-2150
    • CVE-2019-9947
    • CVE-2019-9948
    • CVE-2019-9740
    • CVE-2018-14647
    • CVE-2018-0739
    • CVE-2018-0732
    • CVE-2017-3736
    • CVE-2017-3737
    • CVE-2018-5407
    • CVE-2018-10897
    • CVE-2018-14526
    • CVE-2017-13089
    • CVE-2017-13090
    • CVE-2019-5953
    • CVE-2007-5191
    • CVE-2018-11784
    • CVE-2016-6325
    • CVE-2016-5425
    • CVE-2018-1049
    • CVE-2019-3842
    • CVE-2018-16865
    • CVE-2018-16864
    • CVE-2018-15688
    • CVE-2018-15686
    • CVE-2016-7795
    • CVE-2017-1000367
    • CVE-2017-1000368
    • CVE-2019-8457
    • CVE-2015-3416
    • CVE-2015-3415
    • CVE-2015-3414
    • CVE-2014-8118
    • CVE-2015-7236
    • CVE-2019-9947
    • CVE-2019-9948
    • CVE-2019-9740
    • CVE-2019-9636

    • CVE-2018-14647
    • CVE-2018-1061
    • CVE-2016-5699
    • CVE-2016-0772
    • CVE-2017-16844
    • CVE-2015-3256
    • CVE-2017-9287
    • CVE-2015-3276
    • CVE-2016-3191
    • CVE-2015-3217
    • CVE-2015-5073
    • CVE-2015-2328
    • CVE-2018-18311
    • CVE-2019-1559
    • CVE-2009-0733
    • CVE-2009-0723
    • CVE-2019-11477
    • CVE-2018-7191
    • CVE-2019-11833
    • CVE-2019-11810
    • CVE-2018-20836
    • CVE-2019-3900
    • CVE-2019-3901
    • CVE-2019-11811
    • CVE-2019-11599
    • CVE-2019-11487
    • CVE-2019-3460
    • CVE-2019-3459
    • CVE-2019-7221
    • CVE-2019-6974
    • CVE-2018-18397
    • CVE-2019-12381
    • CVE-2019-12382
    • CVE-2019-11479
    • CVE-2019-11478
    • CVE-2019-5489
    • CVE-2015-8551
    • CVE-2018-20169
    • CVE-2018-14646
    • CVE-2018-18690
    • CVE-2014-4014
    • CVE-2014-4171
    • CVE-2018-18559
    • CVE-2018-17972
    • CVE-2018-14634
    • CVE-2018-18281
    • CVE-2018-19824
    • CVE-2018-14633
    • CVE-2018-15594
    • CVE-2008-4609
    • CVE-2010-3865
    • CVE-2018-1091
    • CVE-2017-7889
    • CVE-2017-7645
    • CVE-2017-7495
    • CVE-2017-7308
    • CVE-2017-7294
    • CVE-2017-5970
    • CVE-2017-18203
    • CVE-2017-17449
    • CVE-2017-15265
    • CVE-2017-15274
    • CVE-2017-9242
    • CVE-2017-8824
    • CVE-2017-7895
    • CVE-2017-7533
    • CVE-2017-7541
    • CVE-2017-7187
    • CVE-2017-6951
    • CVE-2017-6214
    • CVE-2017-2671
    • CVE-2017-2647
    • CVE-2017-18344
    • CVE-2017-18208
    • CVE-2017-17805
    • CVE-2017-16939
    • CVE-2017-15129
    • CVE-2018-8781
    • CVE-2018-5344
    • CVE-2018-13405
    • CVE-2018-1130
    • CVE-2017-9076
    • CVE-2017-9077
    • CVE-2017-8797
    • CVE-2017-7477
    • CVE-2017-6074

    • CVE-2017-5551
    • CVE-2017-2636
    • CVE-2017-2618
    • CVE-2017-17448
    • CVE-2017-15649
    • CVE-2018-5750
    • CVE-2018-1120
    • CVE-2018-10675
    • CVE-2018-10878
    • CVE-2017-9074
    • CVE-2017-9075
    • CVE-2017-8890
    • CVE-2017-7542
    • CVE-2017-7616
    • CVE-2017-6001
    • CVE-2017-5986
    • CVE-2017-2583
    • CVE-2017-2596
    • CVE-2017-17558
    • CVE-2017-14106
    • CVE-2017-12193
    • CVE-2017-11600
    • CVE-2017-10661
    • CVE-2017-1000252
    • CVE-2016-9793
    • CVE-2016-9083
    • CVE-2016-9084
    • CVE-2016-8645
    • CVE-2016-8646
    • CVE-2016-8630
    • CVE-2016-7117
    • CVE-2016-6327
    • CVE-2016-6197
    • CVE-2016-5696
    • CVE-2016-4997
    • CVE-2016-4998
    • CVE-2016-4794
    • CVE-2016-4565
    • CVE-2016-4470
    • CVE-2016-2847
    • CVE-2016-2069
    • CVE-2016-10208
    • CVE-2016-10088
    • CVE-2017-12190
    • CVE-2017-12192
    • CVE-2017-12188
    • CVE-2017-11176
    • CVE-2017-1000410
    • CVE-2017-1000407
    • CVE-2016-9794
    • CVE-2016-9806
    • CVE-2016-9555
    • CVE-2016-9576
    • CVE-2016-8666
    • CVE-2016-8633
    • CVE-2016-6828
    • CVE-2016-7039
    • CVE-2016-6480
    • CVE-2016-6198
    • CVE-2016-5412
    • CVE-2016-3156
    • CVE-2016-2053
    • CVE-2016-10147
    • CVE-2016-0758
    • CVE-2015-8970
    • CVE-2017-12154
    • CVE-2017-1000112
    • CVE-2017-1000111
    • CVE-2016-9588
    • CVE-2016-8655
    • CVE-2016-8650
    • CVE-2016-7914
    • CVE-2016-7913
    • CVE-2016-7910
    • CVE-2016-7097
    • CVE-2016-7042
    • CVE-2016-6136
    • CVE-2016-5829
    • CVE-2016-5195
    • CVE-2016-4581
    • CVE-2016-3841
    • CVE-2016-3134
    • CVE-2016-10200
    • CVE-2015-8845
    • CVE-2015-8767

    • CVE-2015-8543
    • CVE-2015-8539
    • CVE-2015-8374
    • CVE-2015-8104
    • CVE-2015-8215
    • CVE-2015-7613
    • CVE-2015-5366
    • CVE-2015-5283
    • CVE-2015-4700
    • CVE-2015-3339
    • CVE-2015-2925
    • CVE-2015-1805
    • CVE-2015-1421
    • CVE-2015-1465
    • CVE-2015-1333
    • CVE-2015-1210
    • CVE-2015-1211
    • CVE-2015-8812
    • CVE-2015-8844
    • CVE-2015-8660
    • CVE-2015-6526
    • CVE-2015-5307
    • CVE-2015-5364
    • CVE-2015-5157
    • CVE-2015-4170
    • CVE-2015-3636
    • CVE-2015-3331
    • CVE-2015-3212
    • CVE-2015-2666
    • CVE-2015-2150
    • CVE-2015-1212
    • CVE-2015-1209
    • CVE-2015-0797
    • CVE-2015-0275
    • CVE-2015-0274
    • CVE-2019-13233
    • CVE-2018-16597
    • CVE-2019-14283
    • CVE-2019-14284
    • CVE-2019-13631
    • CVE-2016-0728
    • CVE-2015-5156
    • CVE-2016-5828
    • CVE-2015-0312
    • CVE-2016-1833
    • CVE-2016-1836
    • CVE-2016-1834
    • CVE-2016-1837
    • CVE-2016-1838
    • CVE-2016-1839
    • CVE-2016-1762
    • CVE-2016-1840
    • CVE-2016-4449
    • CVE-2016-3627
    • CVE-2016-5131
    • CVE-2016-4447
    • CVE-2015-7497
    • CVE-2015-7500
    • CVE-2015-7499
    • CVE-2015-7498
    • CVE-2015-5312
    • CVE-2017-8779
    • CVE-2016-3632
    • CVE-2016-3991
    • CVE-2016-3990
    • CVE-2016-3945
    • CVE-2015-8870
    • CVE-2015-8784
    • CVE-2015-1547
    • CVE-2019-3863
    • CVE-2019-3857
    • CVE-2019-3855
    • CVE-2019-3856
    • CVE-2019-3862
    • CVE-2019-3861
    • CVE-2019-3858
    • CVE-2016-0787
    • CVE-2019-13115
    • CVE-2015-5302
    • CVE-2015-8472
    • CVE-2015-8126
    • CVE-2016-3698
    • CVE-2018-14498
    • CVE-2016-6313
    • CVE-2016-5419

    • CVE-2017-13080
    • CVE-2017-13082
    • CVE-2017-13088
    • CVE-2017-13087
    • CVE-2017-13078
    • CVE-2017-13077
    • CVE-2015-8370
    • CVE-2017-7869
    • CVE-2017-7507
    • CVE-2019-9169
    • CVE-2018-1000001
    • CVE-2018-11236
    • CVE-2018-11237
    • CVE-2015-5277
    • CVE-2015-1781
    • CVE-2015-7547
    • CVE-2018-11235
    • CVE-2017-1000117
    • CVE-2018-19475
    • CVE-2018-19476
    • CVE-2018-15910
    • CVE-2018-19477
    • CVE-2018-16540
    • CVE-2019-3838
    • CVE-2018-15908
    • CVE-2018-15909
    • CVE-2018-19134
    • CVE-2017-8291
    • CVE-2016-8602
    • CVE-2016-7977
    • CVE-2018-10194
    • CVE-2019-3835
    • CVE-2019-6116
    • CVE-2018-16863
    • CVE-2019-3839
    • CVE-2018-18073
    • CVE-2018-18284
    • CVE-2018-19134
    • CVE-2018-11235
    • CVE-2017-1000117
    • CVE-2018-19475
    • CVE-2018-19476
    • CVE-2018-15910
    • CVE-2018-19477
    • CVE-2018-16540
    • CVE-2019-3838
    • CVE-2018-15908
    • CVE-2018-15909
    • CVE-2018-19134
    • CVE-2017-8291
    • CVE-2016-8602
    • CVE-2016-7977
    • CVE-2018-10194
    • CVE-2019-3835
    • CVE-2019-6116
    • CVE-2018-16863
    • CVE-2019-3839
    • CVE-2018-18073
    • CVE-2018-18284
    • CVE-2018-19134
    • CVE-2018-10906
    • CVE-2016-5384
    • CVE-2018-1000007
    • CVE-2018-1000122
    • CVE-2018-1000120
    • CVE-2018-1000301
    • CVE-2015-3143
    • CVE-2015-3148
    • CVE-2018-1000876
    • CVE-2016-7543
    • CVE-2017-7488
    • CVE-2018-6485
    • CVE-2017-15670
    • CVE-2017-15804
    • CVE-2017-15906
    • CVE-2016-1908
    • CVE-2016-10708
    • CVE-2017-3738
    • CVE-2017-3737
    • CVE-2017-3736
    • CVE-2015-3416
    • CVE-2015-3414
    • CVE-2014-9761
    • CVE-2015-8778
    • CVE-2015-8779

    Outstanding Problems

    There are a number of known issues discovered after code freeze that will be addressed in a future AM/AMM release.

    Reference Problem Description
    8656 / 8633

    The AMM is not differentiating the various FirstNet SIM Status messages in both the Event Viewer and Stats page.

    This makes it impossible to determine if there is a FirstNet SIM installed from the AMM. In a future release the AMM will separate these messages and report two stats (one for MiniUSBSS3-FirstNetSIM, and another for MiniUSBSS4-FirstNetSIM) rather than a single FirstNetSIM stat.

    8565

    Improved support for Time Zone and DST rule changes. The plan is to update the current list of time zones from the underlying operating system in order to support the latest time zone and DST policy changes

    7621 The AM/AMM is not properly managing the LinkX-CallUpTime stat during WAN link switches.
    7358 The Statistics Graph report has the title Engine Coolant Temperature (Fahrenheit) when units are in Celsius.
    7216

    There are unexpected directories found in /home/inmotion/ftp/MHS_logs/ for systems with GNX devices connected.

    6756 The Heartbeat value in an exported dashboard does not match the HTML display in the system
    6523 Some gateways do not show up on the AM/AMM Dashboard due to pagination issues. When the page size is changed from 250 to a number greater than all of the gateways available, the devices will reappear.
    6522

    There is a known issue where inconsistent gateway data can be displayed when multiple LCI windows are opened to different MGOS devices.

    It is recommended that only one MGOS LCI screen be opened at a time.

    6225

    The Main Battery “link” on the dashboard does not allow you the flexible report change that the Statistical Graph report does.

    5947

    The Operational State should update based on the Ignition On event.

    5718

    Due to errors in handling daylight savings, the Bandwidth Consumption reports display high data usage during daylight savings.

    5647

    The Configuration Audit report shows different settings due to different Friendly Names.

    5640 The AM/AMM needs to self-recover from memory exhaustion.
    5569

    The Configuration Audit report generates confusing/misleading VPN information.

    4989 When the Statistics Graph report is generated for stats whose values depend on the user’s measurement units setting (i.e., Imperial or metric), the actual display units may not agree with those displayed in the graph’s title, which makes the report confusing.
    8680

    There is a XSS vulnerability on several of the Admin > Options pages that causes code to run on the User Activity page.

    Various

    The following security issues were identified after code freeze on the AM/AMM 2.16.2 release – CVE-2018-20852, CVE-2019-13115, CVE-2018-7191, CVE-2018-20836, CVE-2019-11487, CVE-2018-20169, CVE-2018-19824, CVE-2019-13233, CVE-2019-13631, CVE-2008-4609, CVE-2019-8457, CVE-2019-9169, CVE-2016-5131, CVE-2018-12433, CVE-2018-12438, CVE-2019-1010180, CVE-2018-20685, CVE-2019-11068, CVE-2016-4610, CVE-2016-4609, CVE-2016-4608, CVE-2019-11068, CVE-2016-4610, CVE-2016-4609, CVE-2016-4608, CVE-2018-18064, CVE-2016-4472, CVE-2015-1283,

    For most of these issues, the impact to AM/AMM is considered low and/or RedHat has not provided a fix in time for inclusion with AM/AMM 2.16.2. This will be included in the next AM/AMM release.

    AMMER

    188 There is a known issue where AMMER cannot report VPN up/down state for all VPNs.
    185 Improve AMMER to report the status of a SCAN tool on the CAN bus to AM/AMM.
    184 Improve AMMER to support the discovery and reporting of proprietary CAN Bus data to AM/AMM.

    TOP