Release Notes 2.20 (December 7th, 2018)

about.png

Viakoo Release Notes 2.20

(December 7th, 2018)

Viakoo Release 2.20 is a significant step forward for the Viakoo Service with the introduction of Camera Firmware Upgrade Manager capability. For customers who add this capability to their subscription, you will see a new “Firmware” tab that not only allows users to remotely upgrade supported devices to new versions of firmware, they also get a high level dashboard to understand infrastructure that is in or out of compliance with firmware standards.

In addition, 2.20 introduces a variety of smaller improvements such as event-time filters for device overviews, recommendation strings in alert emails, and improvements to company, region and site tables, allowing for better visibility to infrastructure. Finally, 2.20 contains a variety of performance and quality improvements

For more information, please read below for details.

Camera Firmware Upgrade Manager

For users with CFUM subscriptions, ‘Firmware’ tab will appear in the your Viakoo Dashboard for your company, regions and sites.

Overview_1.pngNote: If you do not see the Firmware tab, ask your Viakoo representative for details to upgrade your subscription.

Three Sub-Tabs

Under the “Firmware” tab, there are three primary sub-tabs:

  • Compliance to provide a high-level dashboard view and an easy way to view inventory
  • Upgrade Jobs to provide a view of executed, running and scheduled upgrade jobs.
  • Profiles to show and define firmware compliance definitions down to each make and model of camera

Overview_2.png

Compliance View

The Compliance subtab provides a global scope of your firmware compliance of your devices from whatever your current navigation context might be.

Overview_4.png

Any device in your infrastructure can be in one of 3 compliance states:

  • Compliant-Compliant.pngCOMPLIANT(GREEN) - It is running a version of firmware that has been approved for its context based on published firmware profiles.
  • Compliant-NonCompliant.pngNONCOMPLIANT(RED) - It is not running a “Compliant” version of firmware OR it is running a version that is explicitly “Not Compliant” based on published profiles.
  • Compliant-Unknown.pngUNKNOWN(GREY) - Either it is a model which has no explicit “Compliant” or “Not Compliant” profile definition; or it is a model of camera or VMS that does not support collecting firmware values at this time.

The COMPLIANCE sub-tab provides a view of all cameras and their compliance levels as well as a breakdown by camera manufacture (make). By clicking on the inner circle of any camera make, you can drill down to view all the models of the selected manufacturer.

Overview_5.png

Since firmware levels and firmware files are associated with individual models of devices, not only does this view summarize the compliance status of your inventory for each model of the chosen manufacturer, the system supports this process by letting you launch upgrade jobs or add firmware profiles directly from this point.

Launching Upgrade Jobs

You can launch an upgrade job directly from the compliance view by simply selecting a make and then click the “Upgrade Cameras” button for the model of camera you wish to upgrade.

Launching_Jobs_1.png

This takes you a control that makes you select on from the available published versions of firmware (firmware profile) defined and tested for the given make and model of camera. This is necessary because you may have more than one available firmware files for a given make & model of camera, or you not have any, in which case you’ll have to go through the process of submitting and testing firmware profiles (see “Getting Started”).

Launching_Jobs_2.png

After you select a firmware profile to use in an upgrade job, you will be given a chance to configure the job itself. The control transforms into a view that allows you to:

  1. Give the job a label (title) so you can recognize it later,
  2. Schedule when you want the job to run (could be right away),
  3. Select all or individual cameras that should be in the upgrade job.
  4. then Submit the job or Cancel it.

Launching_Jobs_3.png

Because the list can be quite large, you may want to filter the list down to cameras at a particular site or running on a recorder. The filter button allows you to prune the list of cameras to just those that meet clear criteria. In this way, a 1000 cameras can be paired down to a manageable few to select from.

Launching_Jobs_4.png

Monitoring Upgrade Jobs

Upgrade jobs take time since upgrading a single camera can take several minutes to start and several minutes to complete. When you launch an upgrade job, the upgrade status of a device can be in one of the following states:

  • PENDING - waiting to begin the upgrade process
  • IN PROGRESS - upgrade command has been issued to the device and the system is waiting for the upgrade to complete.
  • SUCCESS - the camera has completed the upgrade and is now running the new version of firmware.
  • REVERTED - the camera is functioning but something has interrupted the process such that it is still running the firmware it was running prior to the upgrade. This can happen if the login credentials for the camera don’t work (e.g., incorrect user name or password)or the camera rejects the firmware and rolls back to the version it was running before the upgrade, or
  • FAILED - if after the upgrade has started, it fails to return to life.
  • CANCELLED - If a user ABORTS (“STOPS”) and upgrade job before the upgrade can begin.

Upgrade_Status_1.png

This translates into outcome displays to indicate when jobs are pending, what’s happening to jobs that are in progress and what happened for jobs that have completed.

Upgrade_Jobs_1.png

Each row in the Upgrade Jobs overview gives a summary of a separate job that is broken down as follows:

Upgrade_Jobs_2.png

Clicking on a job will take you to a detailed job review where you can examine the outcome of the job on each individual device.

Upgrade_Jobs_3.png

From this view, you can see the progress of each individual device as it upgrades and review details about each completed job.

Profiles

The Profiles sub-tab of CFUM provides a summary of all published profiles for the current context (see above). For Firmware Administrators (i.e., users whose role is Administrator(FW) for the current context), this is also the place they can go to create, test and publish new Firmware Profiles as well as set or unset compliance using published profiles.

Firmware_Profiles_2.png

For Staff users or Administrative users who are not Firmware Administrators, they will see a more reduced form of this view:

Firmware_Profiles_3.png

For more information about Camera Firmware Update Manager, please refer to the online documentation.

 

Miscellaneous Fixes and Improvements

Device Overview Event Filtering

In Release 2.20, Device Overviews now have a time filter on events. Since there can be a significant number of events associated with a device, the time filter defaults to a single day of events. If needed, you can select a week, month or quarter (3-months) of event data to display.

DeviceOverview_Time_Filter_1.png

As you ask for more event data, compresses the view to improve viewability. First, it collects event data on a per-day basis and shows a limited number of days. Click on the “Show More” to show more days. Click on any day to reveal the events from that day.  

DeviceOverview_Time_Filter_2.png

Other Fixes and Improvements

  • Ticket hints (recommendations) are now included in alert emails.
  • Bug preventing CSV exports from performance with large amount of data has now been fixed.
  • KPI Report now displays to the current moment.
  • Device selection pop-up in performance graphs now consistently disappears when you click away from it.
  • Company, Region and Site tables now include device counts and product policy settings. Site tables also include site creation dates.
  • Problem that precipitated short-duration threshold tickets has now been corrected.
  • Changing a device to IGNORE now immediately “resolves” any open tickets associated with the device.
  • Issue with devices having a bad or incorrect “Last Updated” time has now been corrected.
  • Recorder status is no longer affected by REMOVED or MOVED devices.
  • “Recording to C: Drive” tickets now resolve when configuration changes to record to a non-system partition.
  • Issues leading to incorrect Site status has now been corrected.
  • Exports of tables that may have names with commas (‘,’) characters would format incorrectly in spreadsheets. This has now been corrected.

 

More information

If you have any questions, comments, bug reports, or suggestions, please reach out to us through the live-chat feature or contact us at feedback@viakoo.com.

We love hearing from you!

-Team Viakoo

1 (855) 585-3400

 

 

Have more questions? Submit a request

Comments

Powered by Zendesk