SecureSync 2400 ReleaseNotes For SW - Ver1.7.0
SecureSync 2400 ReleaseNotes For SW - Ver1.7.0
This update provides added benefits through new features, enhancements to existing
functionality, as well as software fixes and security updates, as described in this document.
Note: if your unit is currently on a software version below 1.4.1, it is necessary to upgrade to
1.4.1 before proceeding further (see image below). The upgrade to 1.4.1 comes with significant
system changes and does not allow downgrading to earlier versions. Refer to the upgrade
warnings section of the 1.4.1 release notes in this document for specific information.
For your convenience, older legacy releases are also described in this document.
Table of Contents
Table of Contents ............................................................................................................................................................................................... 2
Version 1.7.0
• Added support for the DER file type for uploading HTTPS certificates.
• Repaired inconsistencies in the REST API variables and documentation.
• Added support for special characters “:” “;” and “-“ to SNMP contact field.
• PTP status is now recorded in the daemon log.
• Expanded NTP Symmetric Key Strings to allow up to 40 hexadecimal characters. MD5 keys
can optionally allow up to 20 ASCII characters instead.
• Corrected PTP slave functionality within the G.8265.1 profile to accept profile-specific clock
classes.
• Fixed issue performing SNMP GET on the sysSetManualTime object.
• Corrected allowed constellation combination inconsistencies on the Web UI and CLI so that
settings align with receiver capabilities.
• Repaired time jumps occurring on PTP masters when applying leap seconds.
• On multicast, a PTP master now properly enters passive mode when not best in domain.
• Added prompting error messages for incomplete Web UI fields on the NTP setup page.
• Fixed an issue with units not completing Sanitization state as expected.
• Repaired HAVE QUICK Input 0 (via the 15-pin multi-I/O) sync issue.
• Fixed loss of GNSS signal when changing constellations via the front panel information
menu.
• Corrected Disciplining State Fault error message when GNSS is disabled on Low Phase
Noise units.
• Fixed issue with the timing system to reduce errors during receiver configuration.
• Corrected an intermittent LDAP certificate upload path issue.
• Added endpoints
o Added Set Global TACACS+ Configuration endpoint with required variable
user_group to configure user permission level.
• Changes to existing endpoints
o LDAP bindpw field is no longer automatically populated on Get LDAP Settings and
Set LDAP Settings responses.
• Added required variables
o When adding a TACACS+ server in Add TACACS+ Server endpoint, the button
variable is now required in the request body with the value "add_tacacs_server".
o Added required variable user_group to the Set Global RADIUS Configuration
endpoint for user permission levels.
o Added required variable disable_cert_check to Configure LDAP Settings
endpoint to enable LDAP-S without a valid certificate.
Known Issues
• Option cards 1204-49 and 1204-4A are limited to install on slots 1 & 2 only.
• This software version DOES NOT ALLOW downgrades before version 1.4.1.
• ASCII time code format ICD-153c is supported only on the -02 and -1F option cards, and only
if the unit has a SAASM receiver installed. This format is not supported on the main board
interface (from 1.3.0).
• The clean command does not reset the GNSS position. It is recommended to unplug the
receiver, reset the receiver in the Web UI, and then run the clean command to reset the
GNSS position (from 1.3.0). The Sanitize functionality can also serve this purpose.
• PTP over a VLAN interface is not currently functional (from 1.4.1).
• PTP Power Profile (IEEE C37.238) is unable to pass the Alternate Time Offset Indicator and
Total Time Inaccuracy TLVs through the system when PTP interfaces are configured as both
a master and a slave (from 1.4.1).
• The SFP fiber link-state on models AVAGO AFBR-5710PZ and FTLF8519P2BNL are not
working properly (from 1.4.1).
• PTP Power Profile (IEEE C37.238) is only able to sync to an EdgeSync master when set to
mixed Unicast mode (from 1.4.1).
• Changing the system timescale will require PTP to be manually restarted (from 1.6.0).
• Telecom Quality Level clock classes are not supported for G.8265.1 PTP masters (from
1.7.0).
• GNSS receiver constellation configuration changes may intermittently fail to succeed.
Customers are advised to confirm constellation selections and retry the operation if the
changes were not successful (from 1.7.0).
Version 1.6.0
• The extension board now has version and upgrade capability. Information on the extension
board version can be found on the Upgrade page of the Web UI.
• Added password entry to Open LDAP server configuration.
• Enabled configuration of the alternate timescale displayname for a PTP Power System
profile master.
• Added support for querying the Broadshield jamming and spoofing state via SNMP.
• Added the speed over ground measurement to the RMC NMEA message type.
• In order to support vlan network tasks, users are now encouraged to use interface names
(eth0, eth1) instead of indexing via CLI commands.
• Added IPv6tables editing to admin accounts.
• Added support for specifying the delay asymmetry between outgoing and incoming paths to
counteract timing offsets introduced by the asymmetry.
• Spaces are now accepted characters in all compatible fields for LDAP setup in the Web UI.
• Fixed a Known Issue with the tcpdump command functionality, which was found to have
incorrect ownership, thereby preventing users from deleting files, even with admin rights.
(from 1.4.1).
• Fixed a Known Issue: DHCPv6 may not perform as expected. It is recommended to use
either static or stateless (SLAAC) IPv6 addressing, particularly with network time
distribution (from 1.2.0). The fix limits support to the default DHCPv6 prefix length of 64.
• Fixed the Known Issue: The restore factory defaults function clean does not currently reset
the Network Access control rule (from 1.4.1).
• Corrected a defect with duplicate log entries in the oscillator log.
• Fixed an issue wherein usernames were not being carried over by config bundles.
• Corrected an error that prevented deletion of config bundles created through the CLI.
• Added the unit serial number to the manifest log.
• Fixed an issue with timescale adjustments on ASCII references set via the Web UI.
• Added the In Sync message to the Events log.
• Fixed a problem with NTP peers, configured using hostnames instead of IP addresses, not
appearing correctly.
• Corrected an error in a chart on the Web UI GSPD Setup page that incorrectly sorted
elevation values.
• Corrected the default Receiver Mode to Standard (instead of Mobile).
• Corrected a PTP UTC offset of 0 sent from master to slave.
• Repaired an error in which disabling a master Ethernet port did not end the synchronization
of slaves to that port appropriately.
• Fixed the removal of local clocks in the unit configuration via the clearcfg command.
• Removed filtered offset thresholding in PTP to limit reference invalidation and increase
fidelity. Network instability is noted in the logs instead of the filtered offset.
• Corrected an incorrect 37 s PTP offset timestamp from master to slave when adjusting the
timescale setting.
• Fixed an issue with Ethernet connectivity if the default interface is not enabled
• Repaired upgrade logging functionality to ensure record on non-clean upgrade.
• Removed the possibility of creating a local clock without a name.
• Fixed an error with authentication logs not reaching the remote logging server.
• Fixed a failure of an NTP client to sync to another server.
• Fixed an incorrect 37 s PTP offset seen on the slave after loss of connection to master.
• Corrected an issue with initialization phase of LPN Rubidium oscillators.
• Resolved error on the front panel which only displayed the right fan speed but not the left.
• Fixed a bug which prevented the IP address on the front panel from updating.
• Corrected certain internal communications with SRO-100 oscillators.
• Fixed a memory leak problem with certain front panel screens being active.
Known Issues
• Option cards 1204-49 and 1204-4A are limited to install on slots 1 & 2 only.
• This software version DOES NOT ALLOW downgrades before version 1.4.1.
• ASCII time code format ICD-153c is supported only on the -02 and -1F option cards, and only
if the unit has a SAASM receiver installed. This format is not supported on the main board
interface (from 1.3.0).
• The clean command does not reset the GNSS position. It is recommended to unplug the
receiver, reset the receiver in the Web UI, and then run the clean command in order to
reset the GNSS position (from 1.3.0).
• PTP over a VLAN interface is not currently functional (from 1.4.1).
• PTP Power Profile (IEEE C37.238) is unable to pass the Alternate Time Offset Indicator and
Total Time Inaccuracy TLVs through the system when PTP interfaces are configured as both
a master and a slave (from 1.4.1).
• The SFP fiber link-state on models AVAGO AFBR-5710PZ and FTLF8519P2BNL are not
working properly (from 1.4.1).
• PTP Power Profile (IEEE C37.238) is only able to sync to an EdgeSync master when set to
mixed Unicast mode (from 1.4.1).
• Changing the system timescale will require PTP to be manually restarted.
Version 1.4.3
Notes
• Units with Hot Swap Power will display a Timing System Hardware Alarm (major) after
upgrading to this release if one or more power supplies is disconnected or not functional.
• Fixed a bug occurring on cold boot that provided PTP slaves an incorrect timescale offset.
• Corrected a corrupt database sometimes caused by power removal during boot sequence.
• Fixed an issue with LPN-Rb oscillator units seen occasionally at startup.
Known Issues
• Option cards 1204-49 and 1204-4A are limited to install on slots 1 & 2 only.
• This software version DOES NOT ALLOW downgrades before version 1.4.1.
• ASCII time code format ICD-153c is supported only on the -02 and -1F option cards, and only
if the unit has a SAASM receiver installed. This format is not supported on the main board
interface (from 1.3.0).
• The clean command does not reset the GNSS position. It is recommended to unplug the
receiver, reset the receiver in the Web UI, and then run the clean command in order to
reset the GNSS position (from 1.3.0).
• PTP over a VLAN interface is not currently functional (from 1.4.1).
• The SFP fiber link-state on models AVAGO AFBR-5710PZ and FTLF8519P2BNL are not
working properly (from 1.4.1).
• The restore factory defaults function clean does not currently reset the Network Access
control rule (from 1.4.1).
• PTP Power Profile (IEEE C37.238) is unable to pass the Alternate Time Offset Indicator and
Total Time Inaccuracy TLVs through the system when PTP interfaces are configured as both
a master and a slave (from 1.4.1).
• PTP Power Profile (IEEE C37.238) is only able to sync to an EdgeSync master when set to
mixed Unicast mode (from 1.4.1).
• The tcpdump command has incorrect ownership, blocking all users from deleting files. To
remove files, the user can update to the same or a newer version. To prevent this scenario,
you can execute tcpdump as sudo tcpdump -Z <user> ..., (for example: sudo
tcpdump -Z spadmin -i eth0 -w file.pcap). This will cause the captured file to be
created with ownership of the specified user, allowing said user to delete (from 1.4.1).
• DHCPv6 may not perform as expected. It is recommended to use either static or stateless
(SLAAC) IPv6 addressing, particularly with network time distribution.
Version 1.4.1
Notes
• CAUTION: The 1.4.1 software does not allow downgrading. After applying this upgrade
bundle, the unit cannot switch to an earlier version of the software without being returned
to Orolia for reprogramming.
• This software version will upgrade BOTH system partitions to version 1.4.1 in order to
solidify significant system changes. Future standard upgrade files will only upgrade one
partition at a time.
• Some upgrade scenarios may cause a loss of user settings. See the Known Issue Upgrade
warnings for loss of or altered configurations for more information.
• Units with Hot Swap Power will display a Timing System Hardware Alarm (major) after
upgrading to this release if one or more power supplies is disconnected or not functional.
• Added missing journal logging for pin configuration, network settings, and NTP and PTP
configuration changes.
• Added statistics database to log bundles.
• The Authentication logging option was added to the Local Logging panel of the Web UI to
allow user configuration.
• Improved the performance and stability of network timing.
• Set System Time Message, Daytime Protocol, and Time Protocol settings to default to OFF.
Configuration enabling these features will persist through this upgrade.
• Added the ability for the user to reset PTP statistics.
• Improved Web UI behavior for PTP configuration.
• Assigned a Major Hardware alarm (called Timing System Hardware Error) in the event of the
Hot Swap Power Supply failure. This alarm will also be triggered if you disconnect or unplug,
but do not remove, a power supply sled.
• Implemented the FP_lock and FP_unlock CLI commands to effectively lock and unlock the
front panel.
• Added support for updated hardware (version 2) on the 1204-50 card.
• Fixed the Known Issue: When configured as a slave, the on-unit PTP will sometimes
incorrectly remain in a Sync state when the Master has gone out of sync (found in 1.3.0).
• Fixed the Known Issue: The 4A/49 option card user configurations will be lost when
performing an upgrade that is not “clean”. The card can be reconfigured and will function,
but any new configuration will not persist after a power cycle of the unit. Cleaning the unit
configuration (or performing a clean upgrade) will allow new configuration to persist
correctly. An applied configuration bundle saved from an earlier software version will
encounter the same difficulty (found in 1.3.0).
• Fixed the Known Issue: Any changes to the Logging Configuration (for instance, turning on
Local Logging) will not take effect without restarting the unit (found in 1.3.0).
• Fixed the Known Issue: If a user configures the time zone via the front panel, the
configuration will be lost after upgrade or config bundles are applied (found in 1.3.0).
• Fixed the Known Issue: The Reference Priority configuration is sometimes not restored
properly from configuration bundles and will have to be reconfigured following upgrades or
application of a config bundle from pre-1.3.0 software (found in 1.3.0).
• Fixed the Known Issue: When multiple major or minor alarms are present, the front panel
LED alarm status light will not activate. All other alarm behavior, including notifications,
operates as expected (found in 1.3.0).
• Resolved network timing and communication performance issues with the Belfuse SFP-
1GBT-05 in ETH1.
• Limited simultaneous UI selection of QZSS with incompatible GNSS signals in order to
prevent cross-correlation.
• Corrected an issue occurring when changing certain network settings that required
resetting DHCP to resolve.
• Fixed a Web UI 500 error seen when setting the default network interface for IPv6.
• Fixed a Web UI issue that allowed users to incorrectly set the PPS source field for ASCII
inputs delivered through the 15-pin connector.
• Edited Web UI settings to correct outdated branding.
• Repaired an issue with the detection of the General Purpose Output being incorrectly
identified as a Square Wave output.
• Corrected a Web UI error providing users with an incorrect “pulse width” field which does
not apply to 1PPS and 1PPM Output modes.
• Fixed an issue with the pin matrix failing to reset on a clean upgrade.
• Fixed a rare error with Rubidium oscillators in which the disciplining was incorrect.
• Resolved an omission in the Web UI upgrade log in which upgrade validation failures were
not displaying correctly.
• Fixed a problem with the receiver mode reporting incorrectly.
• Corrected a minor issue with ZDA NMEA message type displaying on the front panel when
used with ASCII output.
• Repaired Web UI issue not correctly displaying the 1204-4A and 1204-49 cards.
• Repaired a few minor errors occurring in the rare circumstance that the reference table is
fully emptied by the user.
Known Issues
• Option cards 1204-49 and 1204-4A are limited to install on slots 1 & 2 only.
• This software version DOES NOT ALLOW downgrades. If you put this software on your
system, and later need to return your unit to a software version that came before version
1.4.1, it will be necessary to return your unit to Orolia for reprogramming (from 1.3.0).
• ASCII time code format ICD-153c is supported only on the -02 and -1F option cards, and only
if the unit has a SAASM receiver installed. This format is not supported on the main board
interface (from 1.3.0).
• The clean command does not reset the GNSS position. It is recommended to unplug the
receiver, reset the receiver in the Web UI, and then run the clean command in order to
reset the GNSS position (from 1.3.0).
• PTP over a VLAN interface is not currently functional.
• The SFP fiber link-state on models AVAGO AFBR-5710PZ and FTLF8519P2BNL are not
working properly.
• The restore factory defaults function clean does not currently reset the Network Access
control rule.
• Upgrade warnings for loss of or altered configurations:
o On software versions before 1.3.0, SNMP, GPSD, and LDAP settings are preserved
on upgrade but not correctly transferred in configuration bundles. These services
will need to be re-enabled following the application of a configuration bundle.
o On software versions before 1.3.0, certain front panel settings for the Local Clock
and the Lock Keyboard function do not persist after upgrade.
o Upon upgrading to 1.4.1 or applying a configuration bundle from an earlier version,
the System Time Message feature will be set to ON, regardless of previous setting.
Following a Clean upgrade to 1.4.1, the System Time Message, Daytime Protocol, and
Time Protocol features will be configured to OFF (the new default state).
o If your current software is on 1.1.0a or earlier, a direct upgrade to 1.4.1 will fail unless
the clean option is selected. To prevent configuration loss, users are advised to save
a configuration bundle, perform a clean upgrade to 1.4.1, and apply the saved config
file.
• PTP Power Profile (IEEE C37.238) is unable to pass the Alternate Time Offset Indicator and
Total Time Inaccuracy TLVs through the system when PTP interfaces are configured as both
a master and a slave.
• PTP Power Profile (IEEE C37.238) is only able to sync to an EdgeSync master when set to
mixed Unicast mode.
• The tcpdump command functionality was found to have incorrect ownership, thereby
preventing users from deleting files, even with admin rights. To remove these files, the user
can update to the same or a newer version. To prevent this scenario, you can execute
tcpdump as sudo tcpdump -Z <user> ..., (for example: sudo tcpdump -Z spadmin
-i eth0 -w file.pcap). This will cause the captured file to be created with ownership of
the specified user, allowing said user to delete the file.
Version 1.3.0
Notes
• CAUTION: The 1.3.0 software does not allow downgrading. After applying this upgrade
bundle, the unit cannot switch to an earlier version of the software without being returned
to Orolia for reprogramming.
• Fixed the Known Issue: “In version 1.2.2, the 2400 cannot be configured to operate as both a
PTP slave and NTP client.”
• Fixed the Known Issue: “When switching PTP configuration between master and slave,
occasionally the change will not take effect unless manually disabling/reenabling PTP on
that interface.”
• Fixed the Known Issue: “The following option cards are currently limited in use to only slots 1
& 2: 1204-2F, 1204-13, 1204-23, 1204-49, 1204-4A, and 1204-30.” Two option cards (1204-
49 and 1204-4A) are still limited to install on slots 1 & 2 only. All other option cards are
available for use in any slot.
• Fixed the Known Issue: “STANAG 4430 HVK EXTENDED EDITION 1 is not currently
functional.”
• Fixed the Known Issue: “Units with more than four 1204-15 IRIG OUT cards installed at once
may experience failures and difficulty with programming the outputs.”
• Improved Galileo configuration to follow ublox receiver recommendations.
• Resolved an error with the gpsreset command
• Corrected an issue with certain services (LDAP, GPSD) that were preserved on an upgrade
but not during configuration bundle upload.
• Corrected an error in which the temperature alarm configuration was not properly
transferred on upgrade.
• Added a missing timescale selection field in the IRIG Output configuration.
• Corrected the Signature Control functionality in GP Output configurations.
• Added a missing toggle to enable/disable the System Time Message.
Known Issues
• Option cards 1204-49 and 1204-4A are still limited to install on slots 1 & 2 only.
• This software version DOES NOT ALLOW downgrades. If you put this software on your
system, and later need to return your unit to a software version that came before version
1.3.0, it will be necessary to return your unit to Orolia for reprogramming.
• When configured as a slave, the on-unit PTP will sometimes incorrectly remain in a Sync
state when the Master has gone out of sync.
• ASCII time code format ICD-153c is supported only on the -02 and -1F option cards, and only
if the unit has a SAASM receiver installed. This format is not supported on the main board
interface.
• The 4A/49 option card user configurations will be lost when performing an upgrade that is
not “clean”. The card can be reconfigured and will function, but any new configuration will
not persist after a power cycle of the unit. Cleaning the unit configuration (or performing a
clean upgrade) will allow new configuration to persist correctly. An applied configuration
bundle saved from an earlier software version will encounter the same difficulty.
• The clean command does not reset the GNSS position. It is recommended to unplug the
receiver, reset the receiver in the Web UI, and then run the clean command in order to
reset the GNSS position.
• Any changes to the Logging Configuration (for instance, turning on Local Logging) will not
take effect without restarting the unit.
• If a user configures the time zone via the front panel, the configuration will be lost after
upgrade or config bundles are applied.
• The Reference Priority configuration is sometimes not restored properly from configuration
bundles and will have to be reconfigured following upgrades or application of a config
bundle from pre-1.3.0 software.
• When multiple major or minor alarms are present, the front panel LED alarm status light will
not activate. All other alarm behavior, including notifications, operates as expected.
Version 1.2.2
• Fixed a one second offset found in PTP synchronization between the master and slave.
• Corrected an issue with PTP slaves incorrectly reporting as in-sync despite no longer
receiving messages from the master.
• Corrected an issue with PTP slaves incorrectly reporting as in-sync despite the designated
master no longer being in sync.
Known Issues
• In version 1.2.2, the 2400 cannot be configured to operate as both a PTP slave and NTP
client.
• When switching PTP configuration between master and slave, occasionally the change will
not take effect unless manually disabling/reenabling PTP on that interface.
Version 1.2.1
• Fixed an issue with a memory leak when specific pages were viewed on the front panel. This
includes pages viewed that timed out while open. This leak can be found in all previous
software versions and is automatically cleared upon a reboot, including when updating to
software version 1.2.1.
Known Issues
• The following option cards are currently limited in use to only slots 1 & 2: 1204-2F, 1204-13, 1204-
23, 1204-49, 1204-4A, and 1204-30.
• On units that have manually-set time as a PTP Master and then are switched to using a valid
reference, the Slave time does not correctly switch to the reference but will instead stay on
manual time. If switching between manually-set time and an external reference, the PTP master
must be restarted for the slaves to properly follow the new time source.
• When restoring configurations, the GNSS Constellations configuration is on rare occasions not
loading correctly.
Version 1.2.0
*Amendment issued on 2021/11/4: Thermal control of the cooling fans was added in this release.*
• Fixed an issue wherein the NTP and PTP references were incorrectly handled through the
Reference Monitoring chart in the Web UI.
• Corrected 1PPS and 10 MHz alignment
• Fixed a problem with errors on IRIG Outputs.
• Repaired routing to allow destination-based addressing
• Repaired an issue with the GNSS config file sometimes not saving correctly
• Fixed an error with phase validation reference monitoring.
• Resolved a problem occurring when manually set time was removed but the system did not
resync to correct references.
• Fixed an issue with the command clearlogs causing a break in the NTP stats recording
process
• Corrected a defect with log rotation functionality that caused potential storage problems.
• The net4 command now no longer returns Interface not Activated
• Repaired MTU settings changes in the Web UI
• Fixed a problem in which the listed event times in the Web UI were incorrectly displayed.
• Corrected a known issue in which the 1204-4A card configuration was not properly
transferred through the config bundle.
Known Issues
• Units with more than four 1204-15 IRIG OUT cards installed at once may experience failures and
difficulty with programming the outputs.
Version 1.1.0a
• Fixed an issue wherein the NTP status page did not display client throughput.
• Repaired a problem with ASCII Input Time validity in the GGA format.
• Corrected front panel problems: a difficulty displaying leap seconds, a problem halting and
clearing configurations, an issue with disabling output through the front panel, a problem
with the display of the IP address, and added a front panel test menu.
• Fixed a few minor Web UI errors involving display of option cards
• Repaired a few CLI command issues with the clean command, between IPv4 and IPv6
commands, portset/ portget, and gw4set/ gw6set. Confirmed consistency of CLI
commands and underlying network configuration functions.
Version 1.0.2
Log on to the Web UI and navigate to Tools > Upgrade/Backup and click on Update System
Software in the Actions panel.
Click the Choose File button and select the upgrade file location; click Upload.
Click the Perform Upgrade checkbox. If desired, select the Clean Upgrade checkbox as well.
Click on the Submit button. The upgrade will begin immediately. The unit will reboot during this
process; it will be necessary to begin a new Web UI session.
For more information on this process or any other feature or function of the SecureSync 2400,
refer to the main user manual.
https://www.orolia.com/support/
- End of document -