Observer Platform was released February 9, 2016.
How to upgrade Observer Platform
The process for upgrading each product is available by following the information at these links.
New Features
The new features listed here were added with this release.
GigaStor Accelerated Analysis
Faster availability of GigaStor analysis results for IP Host and IP Pairs for targeted data extractions.
Available on all new and existing GigaStor systems.
Observer RESTful API for capture extraction
REST API for packet capture extraction from GigaStor based on a time range. Filters can be applied to extract just the data you desire.
Create and manage packet capture extraction jobs in an automated fashion.
Integrate with other tools to create new workflows.
REST API requires authentication to prevent unauthorized use.
More options for GigaStor Software Edition
New GSE configurations packet capture retention options: 4 TB and 16 TB. These are in addition to the existing 256 GB and 1 TB options.
Trending data management in Apex
Avoid overfilling your operating system drive with Apex trending data.
Retain a configurable number of days worth of trending data and nothing more.
Eliminate the need for manual or scripted deletion of your oldest trending data.
DNS resolution in Apex
Automatically resolve IP addresses into DNS names during dashboard execution. Resolution is performed by Apex and the DNS servers you specify—never your users.
DNS and IP display settings are now configured per widget.
Custom PDF cover in Apex
Added the ability to use a image of your company’s logo (or other image) to brand your Apex reports.
Image must be .svg.
SHA2 support
Added SHA2 certificates. Prior to version 17.1, Observer Platform used SHA1 certificates for internal communication, which occurs on port 25901. Starting with version 17.1, SHA2 certificates are used by default.
Version control of assets from OMS
OMS can control an asset’s version to a specific 17.1 or 17.0 release. OMS itself must be upgraded to 17.1.x before it can provide version 17.1.x upgrades to assets. (In other words, OMS 17.0.x cannot provide 17.1 upgrades to assets.) However, after it has been upgraded, OMS 17.1.x can provide 17.0.x upgrades to assets until you want to upgrade them.
Windows XP and Windows 2003 R2
Support for Windows XP and Windows 2003 R2 has ended for all Observer Platform products.
See the Documentation Change Log for a list of documentation updates listed by product.
Fixed issues
The list below are customer-reported and other notable issues fixed in this release.
Fixed an issue where CSV files saved from Observer were missing packet information.
Observer now correctly identifies cipher suite 0x003D as "TLS_RSA_WITH_AES_256_CBC_SHA256" and cipher suite 0x0035 as "TLS_RSA_WITH_AES_256_CBC_SHA."
Fixed an issue wherein OMS filters were automatically added to Observer local filters if Observer was managed by OMS.
Fixed a crash in ntdll.dll that occurred when trying to view Gantt charts under some circumstances.
Fixed a potential security issue with Observer. When it is managed by OMS and it is minimized it would not always require security credentials to log in.
Fixed an issue with Observer Expert Console Only (ECO) that required it to have system administrator privileges to use some features, such as stream reconstruction and TCP/UDP dump.
Fixed an issue where shared filters did not synchronize as expected.
Fixed an issue with the Save as CSV option in GigaStor Control Panel when using the “2 hours/2 weeks” chart setting that prevented the date and time from being included in the resulting .csv file.
Improved a misleading warning that inferred you could drill down to GigaStor Reports when it was not possible.
Fixed an issue that prevented the graph widget from displaying data properly on the X-axis when using a time range of a week.
Fixed an issue that caused an Uncaught TypeError: Cannot read property 'length' of undefined message that caused dashboard to attempt to reload indefinitely.
Fixed an issue that prevented some Search queries from working.
Fixed an issue that blocked drag-and-drop functionality from working with upgrade policies and assets.
Fixed an issue where a blank asset group may be created in certain cases when upgrading from NIMS.
Fixed an issue that prevented some Search queries from working.
Known issues
The list below represents issues identified by VIAVI about this release that may impact some users.
Windows XP and Windows 2003 R2 assets
This release ends support for Windows XP and Windows 2003 R2; however, those operating systems are supported in version and earlier. If you need to use an Observer Platform product on one of those operating systems, you must use or earlier.
Figure 9: Upgrade path
If you are using OMS 17.0: All 17.0 assets will be able to update to the last 17.0 release:
If you are using OMS 17.1: Upgrade requests from Windows XP or Windows 2003 R2 assets will only allow upgrades to a 17.0 version; other assets will upgrade per their upgrade policy. A log message for each request is logged.
Our recommendation is to apply an upgrade policy that has upgrades disabled for all assets running on an unsupported operating system.
Regrettably, if the asset is using version 15 or version 16, there is no way for OMS to know the operating system because that logic was first added in version 17 and the asset will request a 17.1 upgrade from OMS. The asset will attempt to run the upgrade, which will fail, and leave the asset in a non-running state. If that occurs, to continue using the asset, it must have an upgrade policy applied in OMS that disables upgrades. Also, the original version 15 or version 16 license must be manually reapplied to the asset.
If you are not using OMS and have configured automatic upgrades from the public upgrade server, a Windows XP or Windows 2003 R2 system will pull the latest 17.1 upgrade file. Like a version 15 or 16 system, if you attempt to install the upgrade, it will leave your Observer Platform product in a non-running state and will require that you manually reapply your license.