Introduction

This document describes the new features, open caveats, and resolved caveats in Cisco Virtual Media Recorder (VMR) Release 1.3.3_053. This version of the document includes an update to the Open Caveats.

Release Identifier

  • 1.3.3_053

  • Compatible with V2PC v3.3.3

  • Requires OpenShift v1.5 and Cisco Cloud Object Store (COS) v3.18

Purpose

This release provides the latest version of VMR software that interfaces with Cisco Virtualized Video Processing Controller (V2PC), Cisco Virtual Media Packager (VMP), Cisco Cloud Object Storage (COS), and Cisco Virtual Session Resource Manager (VSRM).

Software Upgrade

For instructions on upgrading the VMR application instance controller (AIC) and VMR Services, see the Cisco Virtual Media Recorder Release 1.3.3 Deployment Guide.

New Features

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

Table 1. New Features in VMR 1.3.3_053

Feature

Description

MemSQL Health Monitoring

Each MemSQL node includes a monitoring service for reporting the health of the MemSQL cluster on anexternal Sensus server. The monitoring includes base node checks and specific MemSQL checks.

Caveats

This section lists open and resolved caveats for Cisco VMR Release 1.3.3_053. Caveats describe unexpected behavior in VMR software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only selected severity 3 caveats are included in the caveats document.

Open Caveats

The following is a list of open caveats in Release 1.3.3_053. Bug details are displayed in the Bug Search.

Table 2. Open Caveats in VMR 1.3.3_053

Bug ID

Description

Update to Pre-installation Procedure (New)

The Cisco Virtual Media Recorder 1.3.3 Deployment Guide contains an outdated cisco-vmr.cfg.template in the Pre-installation Procedure, Step 11. The updated file file is provided in this version of the Release Notes. See Updated Pre-installation Procedure.

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.

CSCvi53846

For the alarm "stream_no_ma_check", only one alarm displays in Uchiwa instead of number of alarms as per channel. See the workaround described in the Cisco Virtual Media Recorder User Guide.

Updated Pre-installation Procedure

The Pre-installation Procedure in the Installing VMR in Standalone Mode chapter of the Cisco Virtual Media Recorder 1.3.3 Deployment Guide includes the outdated cisco-vmr.cfg.template in Step 11. If you want to configure the Sensu server, you must complete all the fields in the sensuServerIP section of the template.

{
     "reconpath": "rio/recon",
     "archivepath": "rio/archive",
     "activepath": "rio/active",
     "siteId": "ciscok8s",
     "locality": "VMR_RECORDER_MGR",
     "vsrm": "1.1.1.17:80",
     "k8sMaster": "1.1.1.2",
     "objstorePassword": "cisco123",
     "objstoreUsername": "cisco",
     "objectstore": [
          "1.1.1.3",
                "1.1.1.4"
     ],
     "consulIP": "",
     "dbPassword": "",
     "dbUsername": "root",
     "databasePort": 3306,
     "databaseIP": [
          "1.1.1.33",
          "1.1.1.34",
          "1.1.1.35"
     ],
     "databaseMasterPort": 3306,
     "databaseMasterIP": "1.1.1.33",
     "dockerRegIp": "1.1.1.58"
     "platformInfo": {
          "path": "platform/resources/config",
          "packageName": "cisco-k8s-upic",
     }
     "bulkDelete": "false",
     "objStoreVip": "",
     "optimizeObjStore": "proxy",
     "usePutCopy": true,
     "adaptationBaseURL": true,
     "maxChannels": 7,
     "jitpServicePort": 9080,
     "rioApiPort": 9449,
     "dataPlaneVip": "",
     "haproxyVip": "1.1.1.22",
     "vmrServiceIp": "1.1.1.22",
     "vmrServiceFqdn": "vmr02.com",
     "openshiftRouterPort": 80,
     "openshiftPlatform": "Yes",
     "jitpServiceHost": "http://vmrstandalonempe.pe1.com/vmrstandalonempe/",
     "rioApiHost": "vmrstandalone.com",
     "sensuServerIP": "",
        "sensuServerPort": "5672",
        "sensuServerVHost": "sensu",
        "sensuServerUsername": "ivpuser",
        "sensuServerPassword": "ivp123",

     "httpsProxy": "",
     "httpProxy": "",
     "logServerType": "X1_ELK",          ###Set LOG Server Type as ELK, KAFKA or X1_ELK based on your server type###
     "logServer": "192.0.2.0",           ###Set LOG Server IP for ELK or X1_ELK server types###
     "elasticsearchPort": 4000,           ###Set Port to be used for ELK or X1_ELK server types###
     "kafkaDefaultTopic": logs,           ###Set Default Topic for KAFKA server type###
     "kafkaIhPort": 192.0.2.1:2181      ###Set Zookeeper Endpoint for KAFKA server type. <IP>:<PORT> pairs. Can be a 
                                            comma separated list###
}

Resolved Caveats

The following is a list of resolved caveats in Release 1.3.3_053.

Table 3. Resolved Caveats in VMR 1.3.3_053

Bug ID

Description

CSCvi08121

Intermittent issue A8 interface sends "STARTED" twice for 1 recording, missing "COMPLETE"

CSCvi28143

Fix get segment api to return correct groupid

CSCvi03571

Fix to pass port from HA to API

CSCvi17654

GUI backend support for profile name

CSCvi51767

Rolling upgrade fails in start_vmr_k8s_svc.sh

Related Documentation

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

  • Cisco Virtual Media Recorder 1.3.3 User Guide

  • Cisco Virtual Media Recorder 1.3.3 Deployment Guide

  • Open Source Used in Cisco Virtual Media Recorder