Learn about more about VRK Key Payloads, adding single or multiple VRK bundles, editing VRK bundles, deleting VRK bundles, and more about VRK certificates.
A new configuration VRK Key Payloads Deletion Threshold is introduced in Administration > Estate Configuration > System Configuration. The System Configuration screen is displayed. Select the System from the Category drop-down list. The threshold value is configured to delete VRK key payloads from VHQ server on successful download. The value is in number of days and can range from 1 to 365 days.
VRK key payloads when failed to download to the device within the specified number of days (where the days are configurable in VHQ, and a default value is of 30 days), the VHQ server will do the following:
A new configuration Failed VRK Key payload Rescheduling Timeout is introduced in Administration > Estate Configuration > System Configuration. The System Configuration screen is displayed. Select the System from the Category drop-down list. The number of days is configured after which the failed jobs cannot be rescheduled. The value is in number of days and can range from 1 to 30 days.
NOTE:
1. The VRK download feature will be supported for V/OS devices (Mx9xx, Raptor, and UX) and Vx eVo devices. This feature will be licensed as part of the license for the VHQ Diagnostics module.
2. The Key Bundles are referred as VRK Bundles in VHQ.
3. Before uploading the Bundles, you must check for the device serial number. The device must not be in deleted or blacklisted status for the Bundle to be processed.
4. You must ensure that the device file format supports .tgz and .zip files.
5. In order to process VRK Bundle for inactive devices, you must check for the system configuration Include Inactive Devices for Scheduling. Setting the flag to True will result in processing of the bundle for the inactive devices.
You must upload or add the VRK Bundle to VHQ to be downloaded to the device. You can also upload multiple VRK Bundles to the VHQ in a single step.
To upload or add VRK Bundle:
NOTE: The device file must be in proper format (.tgz and .zip files). The validation takes place on the backend server and the key payloads are validated against the device serial number and device model.
7. Click Add VRK Bundles. The VRK Bundles are uploaded to the VHQ.
The VRK Bundle Library screen lists multiple records, one for each file name and all these records can have the same bundle name. You can look into the specific file name within a specific bundle name, using the column filter feature.
VHQ allows you to upload the same VRK bundle file that was uploaded earlier with a different VRK Bundle name and adds a log VRK bundle exists with different bundle name in Import log.
However, if you try to upload the VRK bundle file that is already present in VRK library, with the existing Bundle name, VHQ doesn’t allow you to upload the file and adds a log VRK Bundle already exist in Import log.
To know the status of the file, click on Download column, under the Device Management > Import/Export > Import tab against the relevant file name.
For uploading multiple bundles, a new configuration Maximum Number of VRK Files Allowed per Upload is introduced in Administration > Estate Configuration > System Configuration. Select System from the Category drop-down list.
The configuration allows maximum number of VRK files to be uploaded into the VHQ and the value can range from 1-200 files. The value can be edited and restored. The uploading of multiple VRK Bundle files must not exceed the configured value.
To upload multiple bundles, follow Steps 1 to Step 7 as mentioned above.
You can edit the VRK Bundles.
To edit VRK Bundle:
You can delete VRK Bundle.
To delete VRK Bundle:
NOTE:
- Deleting the VRK Bundle with Bundle Status In Progress will completely delete the bundle.
- Deleting the VRK Bundle with Bundle Status Processed will delete the records from bundle library.
The VRK Bundle Library displays all the VRK Bundles uploaded to VHQ. The screen lists the following columns mentioned below:
Column |
Description |
Bundle Name |
Indicates the VRK Bundle name. By default, the VHQ use the following bundle name VRK_bundle_YYYYMMDD_HHMMSS, where YYYYMMDD_HHMMSS will represent the date and time (in GMT). The VRK bundle name and VRK bundle file name must be unique. |
File |
Indicates the bundle file in .zip or .tgz format. |
File Size(KB) |
Indicates the bundle file size in KB format. |
Tags |
Indicates the tag. |
Bundle Status |
Indicates the processing of the VRK Bundle whether the bundle is in progress or processed. |
Uploaded By |
Indicates the bundle uploaded by. |
Uploaded On |
Indicates the file downloaded on the specific date and time. |
Schedule Information |
Indicates when the file is scheduled to download. |
Logs |
Indicates the complete detail of the bundle in the processed status. Click to download the bundle logs. |
Details |
Indicates the bundle details. Click View Details link to view the KeyBlobCount, Success Count, Failed Count, and Pending Count.
|
Once the VRK Bundle file is processed, the logs for the particular file are ready to be downloaded. The below screen indicates the log file.
The log file contains the VRK Bundle file that is uploaded to and processed in VHQ.
BMX_1-15-0000-8631_131137458506_log.csv– <Indicates VRK Bundle File Name>_Unique Number generated for file time in UTC_log.csv.
VRK Certificates provide an ideal authentication method for securely access of information. The security based certificates are stored on the device and extracted on device registration and post repair once VHQ agent is uploaded. The security based certificates consist of two components: the private key that is stored on the device, and the public key that is installed on the server.
VHQ Server requests for VRK Certificate on every registration (or re-registration) and stores it per device in the VHQ database. For devices that are already registered in VHQ server, and the VRK Cert of device is not stored in the VHQ database for a given device, the VHQ server collects the VRK Cert from the device during the next maintenance window.
VRK certificate is collected from the device on KEM and once every 24 hours during the maintenance window.
NOTE:
1. If a RSA public certificate does not exist for a specific device in VHQ server, then VHQ GUI indicates that VRK certificate has not been collected from the device.
2. The latest VRK Certificate, if present, is displayed.
You can export VRK certificate of multiple devices into a single compressed file (.zip), and specify the name of the zip file. The selection of devices for which the VRK Cert is exported, based on the VHQ search features of quick search, advanced search and column filtering in the VHQ search screen.
To export VRK Certificates:
The request to export data is submitted to VHQ server and the VRK certificate can be downloaded from the Export tab of Import/Export under the Device Management tab. You must specify the locations for the file to be downloaded. The file is in the form of spreadsheet.
NOTE:
- The exported zip file should have VRK Cert (.crt) files for all the selected devices. Each VRK Certificate file within the ZIP file must be named as “{terminal serial number}_vrk.crt”. Separate zip files with different names should be created that contain the VRK Certs for the Vx devices and Mx (V/OS) devices.
- Since the VRK Cert information may NOT available in the VHQ server for some of the selected devices, the export wizard indicates that the created zip file will only include the VRK Cert from the devices for which this information is available. The export log file should clearly indicate the devices for which the VRK Cert information is NOT exported and NOT included in the zip file.
You can monitor the VRK downloads in two ways thorough:
The VRK Bundle job status provides the information on status of VRK key payloads for each device serial number. This helps you to determine the success/ failed/ cancelled/pending/in progress VRK downloads for a specific VRK Bundle.
To view the VRK download job status, go to Device Management > Manage Downloads > VRK Download Job Status screen.
The screen includes:
Column |
Description |
Serial# |
Indicates the device serial number. |
Device ID |
Indicates the device ID. |
Hierarchy Path |
Indicates the device hierarchy path. |
Model |
Indicate the device model. |
Job Name |
Indicates the Job name |
Job Status |
Indicates the status of the job send to the device. The job status includes Cancel Requested, Cancelled, Failed, InProgress, Schedule Sent, Scheduled, Scheduling and Successful status. |
Bundle Name |
Indicates the VRK bundle name. |
Bundle File |
Indicates the VRK bundle file. |
VRK Payload |
Indicates the VRK payloads. The payloads contain one or more sets of key files that are to be downloaded to specific devices, as identified by the device serial number. |
Download Schedule |
Indicates the date and time of payloads to be scheduled for downloaded to the device. |
Schedule Information |
Indicates the date and time of payload downloaded to the device. |
Reason For Failure |
Indicates the reason for the failure of payloads to be downloaded to the device. |
Submitted On |
Indicates the job submitted for VRK Payload. |
Results |
Indicates the job details. |
You can cancel the job schedule from the VRK Download Job Status screen.
To cancel the download:
The VRK Detailed Download status screen displays the status per device per key payload.
You can view the download status in Device Management > Manage Downloads > VRK Detailed Download Status.
The VRK Detailed Download Status screen allows you to Reschedule the VRK failed download for the devices.
NOTE: No automatic download retry option will be provided for failed VRK downloads.
To reschedule VRK failed download:
You can view the download history information of the key payloads for a device in the relevant Device Profile tab.
To view the download history in Device Profile:
You can also Reschedule the failed downloads from Device Profile tab.