MPX Node v1.6.1 - Release Notes and Update Instructions
Scope
This document applies to the following Omnia MPX Node devices;
- Omnia MPX Node Decoder - part number 2001-00522-000
- Omnia MPX Node Encoder - part number 2001-00529-000
Description
This firmware update is advised for all users of MPX Nodes. Changes include the addition of SNMP features, support for update file encryption, memory and log storage optimizations and other internal improvements.
Version 1.6.1 (May 2023) Release Notes
Security
While Telos has consistently recommended that MPX Node be run in a secure VPN environment, we know that some customers choose to run their units on the public Internet, leaving themselves open to probes and exploits. As with our previous 1.5 release, changes in our latest release help harden the system against hackers and bad actors, proactively reducing user risk. Security changes include:
- Support for Encrypted update files
Stability
Support has seen a couple of rare cases where the GUI may become inaccessible (even while the product continues to pass the MPX signal), requiring a remote session from Telos Support or a power cycle to clear it. Stability upgrades include:
- Upgraded log rotation, log compression and automatic deletion of old logs to prevent storage from filling up
- System file check eliminates 0 byte files
New User Features
- The addition of SNMP for both Encoder and Decoder units, and a new GUI section to support it. More comprehensive notes on SNMP can be found here
Preparing to update
Download the Update File
Version 1.6.0 can only be installed on units running version 1.3.37 or higher.
If your MPX Node is running any lower software version (1.3.35 or below), you must install version 1.3.37 first before installing 1.6.0. This intermediate step installs an update component that must be present before you can install higher releases.
Note that version 1.6.0 marks the introduction of encrypted update package files. For users who have participated in our beta program and have already installed a 1.6.0 beta, you will now need to upgrade using the encrypted .epkg file type. Other users can use the .pgk type. All future releases will migrate to .epkg delivery, and your browser should present the appropriate .pkg vs .epkg type based on your current installed version.
- Download 1601-00585-008 v1.3.37
- Download 1601-00593-012 v1.6.1 (pkg file type)
- Download 1601-00604-012 v1.6.1 (epkg file type)
Save the update files to a convenient location on your computer.
Installing the Update
The MPX Node has a dual software bank update system. You can safely update the bank that is NOT active while the unit is online without disrupting programming, then choose a convenient time to switch to the new firmware. Software updates are always uploaded to the inactive bank.
- Using your web browser, navigate to the main web page of your MPX Node.
- Log in with your username and password.
- From the left side menu, click on System Setup.
- At the bottom of the System Setup page, click on the SELECT FILE button.
- Using the dialog box that opens (this will differ depending on your operating system), browse for and select the file you previously downloaded.
- Click the UPLOAD button. A progress bar will show you the status of the upload. Once complete, the version number in the Firmware bank that is inactive will reflect the new version number.
- Click the Make Active link on the bank that contains the new version.
- A confirmation screen will prompt you to proceed with a reboot.
Release History:
Version 1.6.1 (May, 2023)
- Restored missing config file that could result in a 404 error when upgrading from pre 1.6.0 versions
Version 1.6.0(April, 2023)
- Changed system to run web GUI, µMPX app, and packet duplicator as non-root users
- Added update package encryption at build and decryption at install.
- Added MIB-II compliant SNMP.
- Added detailed error handling to the software bank manager and the UI when updating.
- Updated log processing system to handle more cases of large logs.
- Added file system check for /config partition on every boot.
- Added zero byte file check, delete it if zero.
- Decoder Dashboard GUI change: Statistics now displays as a percentage of packets received, rather than a number (from 0 to 1024).
Version 1.5.0 (August, 2022)
- Password system reworked
- Internal security hardening
- Login authorization required for all software endpoints
- Removal of accounts used for demo purposes.
- Required acceptance of our End User License Agreement (EULA).
Stability
Support has seen a couple of rare cases where the GUI may become inaccessible (even while the product continues to pass the MPX signal), requiring a remote session from Telos Support or a power cycle to clear it. Stability upgrades include:
- Upgraded log rotation, preventing logs from taking up too much storage
- Internal service failure detection and automatic restart.
New User Features
- More granular settings for MPX level output and uMPX Delay settings
- Finer resolution mouse wheel control support of all sliders
Version 1.3.35 (April 6, 2020)
Features
- Multicast is now a supported option and can be enabled via a license key applied to the Decoder
- Additional streams can be added via a license key applied to the Encoder
For more information on enabling new features, please refer to these Help Docs links:
- Activating an MPX Node Licensed Features
- Setting up Multicast:
- Configuring MPX Nodes for redundant streams
Enhancements
- Each network interface supports its own unique gateway
- DNS is now user-configurable
- Internal log files are now accessible on the standard system page
- Slider controls now operate more smoothly
- Ability to set Encoder stream DSCP and TTL settings implemented
- improved sonic performance
With major changes to the Network stack, MPX Node is now capable of sending/receiving redundant streams over separate networks. Sending to the same IP address on both Net1 and Net2 provides packet redundancy to the decoder.
Version 1.1.5 (Jan 9, 2020)
Features
- Maintenance release only, no new features in this version.
Fixes
- Fixes a rare issue where an ill-timed reboot could result in corruption of the flash memory.