Introduction

This document describes the new features, open caveats, and resolved caveats in Cisco Virtual Media Recorder (VMR) Release 1.4.2_042.

Compatibility:

Software Upgrade

For instructions on upgrading VMR, see the Cisco Virtual Media Recorder Release 1.4.2 Deployment Guide.

New Features

The following is a list of new features for VMR Release 1.4.2.

Table 1. New Features in VMR 1.4.2

Feature

Description

Important Notice:VMR and V2PC integration is no longer supported in VMR 1.4.2.

Integration between VMR and V2PC is no longer supported in VMR 1.4.2.

Password expires after 6 months (New) Your VMR password now expires after 6 months. Upon login to VMR Dashboard, you will be prompted to change your password. See Cisco Virtual Media Recorder User Guide.
Added api-host-FQDN to VMR inventory file (New) When logging into VMR Dashboard, you now enter https://<vmr-api-host-FQDN>:9110, where <api-host-FQDN> is the FQDN configured as the value for vmr-api-host in VMR deployment inventory file (yourinventory.ini) and 9110 is the port. See Cisco Virtual Media Recorder User Guide

Known Issues

This section lists open and resolved issues for Cisco VMR Release 1.4.2_042. The issues describe unexpected behavior in VMR software releases. Severity 1 bugs are the most serious issues; severity 2 bugs are less serious. Severity 3 bugs are moderate issues, and only selected severity 3 bugs are included in this section.

Open Issues

The following is a list of open issues in Release 1.4.2. Bug details are displayed in the Bug Search.

Table 2. Open Issues in VMR 1.4.2

Bug ID

Description

Playback of HTTP URLs in an HTTPS Dashboard may fail. As a workaround, configure the browser as described in the Troubleshooting chapter in the Cisco Virtual Media Recorder Deployment Guide.

CSCvj65508

Upgrade fails due to lost Zookeeper data. See workaround in the Cisco Virtual Media Recorder Deployment Guide, Troubleshooting chapter.

CSCvj86124

Upgrade from VMR standalone to vmr-bundle (1.4.1 or 1.4.2) will complete but the dash-origin pods will fail in rolling update due to a mismatch in the dash-origin deployment template; VMR standalone will have duplicate entries for MANIFEST_LOAD_TIMEOUT. See workaround in the Cisco Virtual Media Recorder Deployment Guide, Troubleshooting chapter.

CSCvm85222

During the cyclic reconstitution/rearchive loop, PUTCOPY/DELETE 500 errors may occur in COS due to multiple putcopy segments after installing VMR 1.4.2. See workaround in the Cisco Virtual Media Recorder Deployment Guide, Troubleshooting chapter.

CSCvm93805

A 413 Request Entity Too Large error may occur during bulk recording/delete requests in VMR. This error occurs because the default value for the maximum recordings request is set to 60. See workaround in the Cisco Virtual Media Recorder Deployment Guide, Troubleshooting chapter.

Closed Issues

The following is a list of closed issues in Release 1.4.2.

Table 3. Closed Issues in VMR 1.4.2

Bug ID

Description

CSCvi48336

[Archive Agent - RecGC - Bulk Delete] RECGC_GRP_SIZE is incorrectly configured

CSCvg58653

DO Errors: no segments passed in during AS builder

CSCvj99749

DO panics during location query

CSCvj02989

Blink Logs Thresholds are not exposed.

CSCvi77151

MA log missing count of total IRIDS in log

CSCvk63001

DO - handling of 404, causes 302 redirect to MPE with no URL

CSCvk76322

DO sends 502 to client

CSCvm01065

Clear group id if segment tracking is disabled

CSCvm36848

VF MA doesn't mark recordings as ErrorCode=1

CSCvm52261

VMR Dashboard times out with API error

Related Documentation

Refer to the following documents for additional information about VMR 1.4.2: