Table Of Contents
Release Notes for Cisco Video Surveillance Manager, Release 7.2
What's New in this Release
Getting Started
Cisco Physical Security UCS Platform Series Servers (Release 7.2)
Upgrading from Release 7.0 and 7.2
Special Instructions for Linux Red Hat
Recovery/Factory Image
Migrating from Cisco VSM Release 6.3.x
Important Notes
Medianet 2.0 Support
Medianet Metadata
Metadata Requirements
Metadata Restrictions
Performance Monitoring and Mediatrace
Requirements
Enabling Performance Monitoring and Mediatrace
LiveAction (Monitoring Application)
Restrictions
Released Versions
Supported Hardware Platforms
Supported Devices
Supported Devices: Cisco
Supported Devices: Arecont
Supported Devices: Axis
Supported Devices: IQinVision
Supported Devices: Panasonic
Supported Devices: Pelco
Supported Devices: Sony
Supported Devices: Generic IP Cameras
Supported Devices: Analog Cameras
Minimum Supported Firmware for IP cameras and Encoders
Obtaining and Installing Licenses
Understanding the VSM Software Types
Obtaining VSM Software
Caveats
Using the Software Bug Toolkit
Open Caveats
Resolved Caveats
Related Documentation
Release Notes for Cisco Video Surveillance Manager, Release 7.2
Revised: October 4, 2013
This document provides important information for Release 7.2 of the Cisco Video Surveillance Manager (Cisco VSM).
This document includes the following sections:
•
What's New in this Release
•Getting Started
•Important Notes
•Medianet 2.0 Support
•Released Versions
•Supported Hardware Platforms
•Supported Devices
•Minimum Supported Firmware for IP cameras and Encoders
•Obtaining and Installing Licenses
•Understanding the VSM Software Types
•Obtaining VSM Software
•Caveats
•Related Documentation
What's New in this Release
Cisco VSM Release 7.2 is a feature update of Cisco VSM 7 that also includes fixes for various defects (see the "Resolved Caveats" section).
The new features in this release include the following:
•Windows 8 Support—Windows 8 is now supported for Operations Manager and SASD. Windows 8 RT version is not supported.
•Internet Explorer 10 Browser Support—IE 10 is supported on Windows 7 and Windows 8.
•SASD Thumbnail Video Search—SASD adds support for Thumbnail Video Search.
•Clipping Improvements—VSM 7.2 provides a number of improvements to clipping. This includes an improved user experience in the Video Client in Operations Manager and SASD for selecting the time range for the clip and creating the clip and a clip search pop-up window in Operations Manager that shows the clips on the VSM server, their status and provides tools for downloading them from the server and deleting them.
•Medianet: Metadata, Performance Monitoring, Mediatrace—VSM 7.2 supports a number of Medianet features that are new for this release. In VSM 7.2, Medianet-capable Cisco IP cameras support tagging their video streams with Medianet Metadata. This allows the network to apply QoS policies to these streams for preferential routing. VSM 7.2 also supports Medianet Performance Monitoring and Mediatrace for capturing network statistics of video streams between the cameras/encoders and the VSM Media Servers. See the section below for more detail on how to use Medianet with VSM 7.2 and the limitations.
•iSCSI Support—VSM 7.2 when deployed on UCS in a VM will support external iSCSI storage. iSCSI is not supported for non-VM deployments.
•Android Video Viewer—VSM 7.2 includes an Android application for viewing live video from VSM. Android 4.0.3 or newer is supported.
•Backup and Restore Enhancements—Operations Manager now supports Backup/Restore of the Operations Manager data through the Operations Manager UI.
•Centralized Driver Pack Management—Driver packs can now be managed from the Operations Manager rather than from the Management Console of the Media Servers. This allows driver packs to up upgraded centrally through the Operations Manager.
•Multicast UDP Ports—VSM 7.2 now adds support for specifying the port numbers to be used with UDP Multicast when configuring cameras and encoders.
•Additional Generic Drivers—VSM 7.2 includes new Generic Drivers for Sony, Panasonic, iQeye and Pelco-Sarix cameras. See the sections below for more information and other new supported devices for VSM 7.2
Getting Started
Cisco VSM Release 7.2 is being delivered for the following:
•As upgrades of Cisco VSM 7.0 and 7.0.1 deployed in VMs and on Cisco MSP servers.
•Pre-installed in new installations on the Cisco Physical Security UCS Platform Series servers CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9.
•As an .OVA file to install a new virtual machine (VM) instance of the server.
Tip After an .OVA virtual machine is installed, you can use the Cisco VSM Management Console to perform future upgrades of the system software.
The following sections provide information about getting started with this Cisco VSM release. There are different options depending on your deployment:
•Cisco Physical Security UCS Platform Series Servers (Release 7.2)
•Upgrading from Release 7.0 and 7.2
•Recovery/Factory Image
•Migrating from Cisco VSM Release 6.3.x
Cisco Physical Security UCS Platform Series Servers (Release 7.2)
Cisco VSM Release 7.2 is pre-installed on the Cisco Physical Security UCS Platform Series (CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9).
•See the Cisco Physical Security UCS Platform Series User Guide for supported features, installation and setup instructions.
•After the server appliance is installed, see the Cisco Video Surveillance Management Console Administration Guide to perform the initial Cisco VSM setup.
•For additional server hardware documentation, see the Cisco UCS C-Series Server Documentation (Roadmap).
Upgrading from Release 7.0 and 7.2
Previous Cisco VSM releases can be upgraded using the Release 7.2 system .zip file that includes all required software packages (including the Cisco Media Server, Operations Manager, Management Console, Cisco Video Surveillance Safety and Security Desktop client and other components). Installing the .zip file upgrades all components and ensures that all packages are running the required versions.
The upgrade is performed using the browser-based Cisco VSM Management Console, and should not be performed using the Linux CLI.
See Cisco Video Surveillance Management Console Administration Guide for detailed information.
Note•Release 7.0 was pre-installed on the Cisco Multiservices Platform (Cisco MSP) servers, including the CPS-MSP-1RU-K9, CPS-MSP-2RU-K9, CIVS-MSP-1RU, CIVS-MSP-2RU and CIVS-MSP-4RU.
•Virtual Machine (VM) installations can also be upgraded using the Cisco VSM Management Console.
Special Instructions for Linux Red Hat
If you are upgrading from VSM 7.0 and your Cisco VSM server is running the Linux Red Hat operating system, complete the following steps before you begin the upgrade process. These steps update the date that the password was last set for the root user.
Note If you are upgrading from VSM 7.0.1, you will have previously have performed this step and it is not necessary to perform it again.
Procedure
Step 1 Use an SSH client to access the Cisco VSM server and log in as the localadmin user.
Step 2 Enter the following command to update the date that the root user password was last set, where date is the current date in yyyy-mm-dd format:
[localadmin@linux ~]# sudo chage -d date root
Recovery/Factory Image
You can also create a bootable USB flash drive that can be used to recover an installation or perform a a factory installation of Cisco VSM 7 on a supported physical server that shipped with Cisco VSM 7 pre-installed. This includes:
•Release 7.2.0—Cisco Physical Security UCS series servers (CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9).
•Release 7.0.0—Cisco Physical Security Multiservices platform servers (CPS-MSP-1RU-K9, CPS-MSP-2RU-K9, CIVS-MSP-1RU, CIVS-MSP-2RU and CIVS-MSP-4RU)
For more information, see the Cisco Video Surveillance Manager Flash Drive Recovery Guide for your server platform.
Note There is no USB recovery image for Release 7.0.1. You must recover the system to 7.0 and then upgrade the RPMs to 7.0.1 When using Cisco VSM 7.0.1, use the recovery image for release 7.0.0, and then upgrade the system software to Release 7.0.1 using the Cisco VSM Management Console.
Migrating from Cisco VSM Release 6.3.x
You can migrate from Cisco VSM 6.3.2 MR2 and 6.3.3 to Cisco VSM 7.2. The migration procedure requires assistance from a Cisco representative. Contact your Cisco representative for more information.
Important Notes
Issues may be encountered when using VSM with high latency network links such as data transmitted through satellite links. When the latency through the network from VSM to a camera or exceeds 500 ms, problems may be experienced that are dependent on the model of the camera and the video mode in use. In particular, there are known issues when Economical Streaming mode is used with .1FPS video sent from a camera via a high latency network link to a remote VSM server.
Please contact Cisco for recommendations on deployments requiring use of high latency network connections.
Medianet 2.0 Support
Release 7.2 adds support for the Medianet metadata and Mediatrace.
Refer to the following topics for more information:
•Medianet Metadata
–Metadata Requirements
–Metadata Restrictions
•Performance Monitoring and Mediatrace
–Requirements
–Enabling Performance Monitoring and Mediatrace
–LiveAction (Monitoring Application)
–Restrictions
Medianet Metadata
The metadata infrastructure allows end points to identify a data flow through the network. Network administrators use this data to classify network traffic (such as video) and implement quality of service (QoS) features.
In Cisco VSM Release 7.2, metadata can be generated for data flowing from Cisco IP cameras to the Cisco Media Servers, and from the Cisco Media Servers to the Cisco VSM workstation clients. Metadata must be enabled on all supported devices as summarized in the "Metadata Requirements" section.
Once enabled, no user interaction is required. The metadata is reported in the background and you must use a monitoring tool to view results. Release 7.2 supports the LiveAction desktop application described in the "Performance Monitoring and Mediatrace" section.
Tip For more information, see the Cisco website "Media Awareness" at: http://www.cisco.com/web/solutions/trends/medianet/media_awareness.html
Metadata Requirements
Medianet metadata must be supported on all intermediate nodes in the data path, including routers, switches, IP cameras, Cisco Media Servers and monitoring workstations.
In Cisco VSM Release 7.2, Medianet metadata is supported on the following devices:
:
Table 1 Medianet Metadata Supported Devices
|
Device
|
Description
|
Cisco routers and switches |
The Cisco VSM application and attributes (Media Server, endpoints, and clients) are supported on the following: •Cisco Integrated Services Routers (ISR) G2—Cisco IOS version 15.4(1)T •Cisco ASR 1000 Series Aggregation Services Routers (ASR)—Cisco IOS version 15.4(1)S •Cisco Catalyst Series Switches—3000 and 4000 series switches require Cisco IOS version 15.2(2)E •Cisco Catalyst Series Switches—6000 series switches require Cisco IOS version 15.2(1)SY Note Prior IOS versions, currently supported metadata values can be viewed and used for classification. |
Cisco IP cameras |
See the "Supported Devices: Cisco" section for the cameras that support Medianet 2 features. Note Cisco devices must be running the minimum supported firmware version to support Medianet 2 features. |
Cisco Media Servers |
Metadata is supported on servers running release 7.2 or higher. To enable metadata on a server running the Cisco Media Server service: 1. Log in to the browser-based Cisco VSM Operations Manager. 2. Select System Settings > Servers. 3. Select a server. 4. Select the Enable Metadata checkbox (under the Medianet heading). Note Metadata is disabled by default. No user interaction is required for metadata tagging, once enabled. |
Workstation clients used to monitor video |
Browser-based clients running the Cisco Multi-Pane client software an ActiveX client) with the MSI utility installed. MSI is enabled on the workstation by installing the MSI client software: 1. Log in to the browser-based Cisco VSM Operations Manager. 2. Select the Operations tab. 3. Select "MSI Installation Package" (under the "Software" heading). 4. Double-click the installer package on your workstation and complete the on-screen instructions. Notes •Metadata is supported on Windows 7-based workstations running the 32-bit Cisco Multi-Pane client. •Metadata is not supported on Cisco SASD in Release 7.2. •No user interaction is required for metadata tagging, but the MSI utility must be installed to enable the feature. Related documentation: •See Client Workstation Restrictions. •Cisco Mobile Video Surveillance Operations Manager User Guide •See the Cisco Video Surveillance Monitoring Workstation Performance Baseline Specification for more information about the Cisco Multi-Pane client software. |
Metadata Restrictions
Cisco Media Server
Medianet metadata must be enabled on each Cisco Media Server using the browser-based Cisco VSM Operations Manager.
•Medianet metadata is disabled by default.
•Metadata is not generated or propagated by the Media Server for flows created prior to enabling this feature. Flows created prior to enablement must be re-established with Medianet feature enabled.
Cisco Routers and Switches
Cisco IOS routers and switches running IOS version earlier than 15.4(1)T are limited to 100 flows per source IP addresses (see CSCuf35612 for more information).
Since the Cisco Media Server is the only Cisco VSM device that creates a large number of flows, this 100 limit restriction can be mitigated on large scale deployments by using separate Medianet enabled routers or switches between the device-to-Media Server segments and the Media Server -to-clients segments. This can enable up to 250 camera streams per Media Server and 60 clients per Media Server.
Network Restrictions
•Medianet metadata is not supported across Network Address Translation (NAT) boundaries.
Client Workstation Restrictions
•Medianet metadata for VSM Client is only supported in 32bit mode on Windows 7.
•Medianet metadata is not supported on the Cisco Video Surveillance Safety and Security Desktop (Cisco SASD) application.
Performance Monitoring and Mediatrace
Cisco Performance Monitoring
Cisco Performance Monitoring is a Medianet feature that measures the performance of RTP, TCP and IP traffic on supported Medianet network devices. Cisco Performance Monitoring allows administrators to collect performance metrics on supported endpoints or intermediate nodes for monitoring video quality conditions.
In Cisco VSM Release 7.2, Performance Monitoring information can be collected on Cisco Media Servers, Cisco IP cameras, and all Medianet enabled intermediate nodes in the path (such as routers and switches).
Cisco Mediatrace
Cisco Mediatrace allows administrators to trace the video hop by hop across the network to detect problems along the data path.
Mediatrace can be collected between cameras, Cisco Media Servers and all Medianet-enabled intermediary nodes (such as routers and switches) on a hop by hop basis.
Requirements
To use Mediatrace and Performance Monitoring, you must:
•Enable Medianet metadata on supported devices, including each Cisco Media Server. Medianet metadata is disabled by default. (see the "Medianet Metadata" section).
•Enter the Media Services Interface (MSI) password on the Cisco VSM servers (see the "Enabling Performance Monitoring and Mediatrace" section).
•Install the LiveAction monitoring application (see the "LiveAction (Monitoring Application)" section).
Enabling Performance Monitoring and Mediatrace
To enable Mediatrace and Performance Monitoring, you must enter the Media Services Interface (MSI) password on each Cisco VSM server (using the browser-based Cisco VSM Operations Manager) and camera (using the camera UI). This same password is used to enable monitoring of the Media Server(s) and camera(s) in the LiveAction monitoring software.
Network Router Usage Notes
•You can also (optionally) enable Mediatrace on the routers that carry the video data, which allows the routers to behave as a Mediatrace responders. Router that do not support Mediatrace are not included in LiveAction data collection and reports.
Procedure
To enable Mediatrace and Performance Monitoring, do the following:
Step 1 Enable metadata on all Media Servers and cameras.
See the "Medianet Metadata" section.
Step 2 Define an MSI password.
The password can be any string defined by the user, and is entered on all servers and camera endpoints that will be monitored, and in the LiveAction monitoring software.
Step 3 Enter the MSI password in the Cisco VSM server configuration page to which the RTP (video stream) flows to:
a. Log in to the browser-based Cisco VSM Operations Manager.
b. Select System Settings > Servers.
c. Select a server.
d. Enter the MSI Password (under the Medianet heading).
Note The MSI username is read-only and cannot be changed.
Step 4 Configure the MSI password on all cameras that support Performance Monitoring and Mediatrace.
•The camera is the device where the RTP (video stream) originates.
•Cameras with a valid password can be added to LiveAction as an MSI endpoint.
•See the camera documentation for instructions to use the device configuration interface.
Step 5 In LiveAction, add the Media Server(s) and camera(s) as MSI endpoints.
The data flows can be tracked and viewed for devices that are added to LiveAction. See https://marketplace.cisco.com/catalog/products/2620 for more information.
LiveAction (Monitoring Application)
In Cisco VSM Release 7.2, Mediatrace data can be collected and analyzed using the LiveAction Management Server v3.0.
•For additional LiveAction information, go to:
https://marketplace.cisco.com/catalog/products/2620
•For a video summary of LiveAction features, go to:
http://www.actionpacked.com/solutions/medianet
•To download LiveAction Management Server v3.0 go to:
http://actionpacked.com/download/liveaction/dl-links-v3-0m
Restrictions
•Performance Monitoring is not supported on Cisco VSM clients or Cisco SASD. Mediatrace is not supported between Cisco Media Servers and Cisco VSM clients or Cisco SASD.
•Only UDP based flows are supported in the Cisco Media Servers. UDP is the default setting for Cisco video cameras. There is no metadata support for TCP based flows in this release.
Released Versions
Cisco VSM Release 7.2 is released with Build 20. The component package versions are:
•VSMS—7.2.0-20d
•VSOM—7.2.0-20
•VSMC—7.2.0-017
•AxClient—7.2.13
•SASD—7.2.13
Supported Hardware Platforms
Cisco VSM Release 7.2 runs on the following hardware platforms:
Supported Devices
The following sections provide information about the devices that this version of VSM supports:
•Supported Devices: Cisco
•Supported Devices: Arecont
•Supported Devices: Axis
•Supported Devices: IQinVision
•Supported Devices: Panasonic
•Supported Devices: Pelco
•Supported Devices: Sony
•Supported Devices: Generic IP Cameras
•Supported Devices: Analog Cameras
Supported Devices: Cisco
Table 3 provides information about Cisco devices supported in this release:
Table 3 Supported Devices: Cisco
|
Model
|
Minimum FW Version for Release 7.2 Compatibility
|
Video Format
|
Media Types
|
Audio
|
Dual Stream
|
Motion Detection
|
Firmware Upgrade
|
Medianet 1.0 (r7.0 features)
|
Medianet 2.0
(firmware 1.4.1 required)
|
2400 Series |
2.5.1 |
NTSC / PAL |
MPEG-4
MJPEG |
NA |
Yes |
Yes |
Yes |
No |
No |
2500 Series |
2.5.1 |
NTSC / PAL |
MPEG-4
MJPEG |
Yes |
Yes |
Yes |
Yes |
No |
No |
2600 Series |
4.4.1-1 |
NTSC / PAL |
H.264
MPEG-4
MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
2830 |
1.2.2-20 |
NTSC |
H.264
MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
2835 |
1.2.2-20 |
PAL |
H.264
MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
2900 Series |
1.6.18 |
NTSC / PAL |
H.264
MJPEG |
Yes |
Yes |
Yes |
Yes |
No |
No |
3421V |
1.2.1-73 |
NTSC / PAL |
H.264
MJPEG |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
3520 |
1.2.1-73 |
NTSC / PAL |
H.264
MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
3530 |
1.2.1-73 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
4300 |
2.4.1-275 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
4300E |
3.2.2-204 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
4500 |
2.4.1-275 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
4500E |
3.2.2-204 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
5000 Series |
1.6.17 |
NTSC |
H.264 MJPEG |
NA |
Yes |
Yes |
Yes |
No |
No |
6000 series |
1.2.1-73 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
6930 |
1.2.2-20 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
7030 |
1.2.1-73 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
CIVS-SENC-4P |
V1.2.0-4 |
NTSC / PAL |
H.264 MPEG-4 MJPEG |
Yes |
Yes |
Yes |
Yes |
No |
No |
CIVS-SENC-8P |
V1.2.0-4 |
NTSC / PAL |
H.264 MPEG-4 MJPEG |
Yes |
NA |
Yes |
Yes |
No |
No |
Notes
•Medianet support:
–VSM 7.2 supports new Medianet features including Metadata, Performance Monitoring, and Mediatrace. These features are supported in the Cisco 2830, 2835, 3421, 3520, 3530, 6000 series, 6930, 7030 camerasThe minimum supported firmware version for this feature is 1.4.1. See the "Medianet 2.0 Support" section for more information. Cameras with the previous supported firmware version will support only the Medianet 1.0 features from Cisco VSM Release 7.0.1.
–The Cisco 2600 series, 4300, 4300E, 4500, and 4500E cameras support only the Medianet 1.0 features in VSM 7.0 and 7.0.1.
•Cisco 4500 and 4500E support video analytics.
•Redundancy is supported for all Cisco devices some exceptions for the 2400, 2500, 2900 and 5000 series. The 2400, 2500, 2900 and 5000 series do not support sending events to the redundant server such as motion detection and contact closure events.
•Cisco 5000 series does not support motion detection at video bit-rates above 4,000 (4 Mbps). The "H" video preset in Templates has been chosen to not exceed this, so motion detection will work.
•The Cisco 5000 and 2900 camera series do not allow changes to the authentication settings (username/password) or networking settings (DHCP/Static, DNS, etc.) through VSM. These values can only be changed using the camera web interfaces.
•The camera controls focus, auto focus and zoom support are not available for Cisco 6000P, 3421V, 3520, 3530 camera models.
•When VSM manages a Cisco 6930, 2830, or 2835 camera, it automatically enables the HTTP protocol on the camera and uses this protocol to send PTZ commands to the camera. Other configuration commands continue to use the HTTPS protocol.
•The Cisco 2830, 2835, 3000 series, 6000 series and 7030 cameras now support MJPEG primary streams. The minimum supported firmware version for this feature is 1.4.1.
•Resolution support:
–Support for 352 x 208, 704 x 400, and 768 x 432 resolutions for both primary and secondary streams on Cisco 3000 Series, 6000 Series, and 7030 cameras. The minimum supported firmware version for this feature is 1.3.2-8.
–Additional resolutions are also available for the 6930 cameras (requires 1.4.1 firmware and VSM 7.2): 1536 x 864, 1472 x 832, 768 x 432, 704 x 400, 352 x 208, 320 x 192, 192 x 112 and 160 x 96. The minimum supported firmware version for this feature is 1.4.1.
–Support for 1536x864, 1472x832, 720x576, 704x576, 352x288 for the Cisco 6000 series and 7030 models, support for 2560x1920 resolutions for the Cisco 7030.
–Support for 1Mbps bitrate for the 1920 x1080 resolution on Cisco 6000 Series and 7030 cameras. The minimum supported firmware version for this feature is 1.3.2-8.
•Support for 1.5 Mbps bitrate for certain resolutions on Cisco 2830, 2835, 3000 Series, 6000 Series and 7030 cameras. The minimum supported firmware version for this feature is 1.3.2-8.
•Contact closure:
–Cisco 3000, 6000 series cameras support 1 input port.
–Cisco 7030 camera supports 3 input ports.
–Cisco 6930, 2830 and 2835 cameras support all 4 contact closures.
–Cisco 3421V cameras do not support contact closure.
•In PTZ Tour Configuration, the configured transition time configured includes the time that it takes the camera to move from the one preset position to the next preset position in addition to the time that the camera is expected to stay in the preset position. If the transition time is configured to a value that is less than the time that it takes the camera to move from one preset position to the next, the camera moves between the first and second presets positions only, instead of touring between all preset positions that are configured in the tour.
Supported Devices: Arecont
Table 4 provides information about Arecont devices that this VSM release supports.
Table 4 Supported Devices: Arecont
|
Model
|
Type
|
Minimum Supported FW Version
|
Media Types
|
Dual Stream
|
Motion Detection
|
Firmware Upgrade
|
AV2115 |
2MP IP Camera |
65218 |
H.264 MJPEG |
Yes |
Yes |
No |
AV5155 |
5MP IP Camera |
65152 |
H.264 MJPEG |
Yes |
Yes |
No |
AV5115 |
5MP IP Camera |
65218 |
H.264 MJPEG |
Yes |
Yes |
No |
AV10XX5 |
10MP IP Camera |
65218, 65202 |
H.264 MJPEG |
Yes |
Yes |
No |
AV8185DN |
4 Sensor 2MP Panoramic IP Camera |
65183 |
H.264 MJPEG |
Yes |
Yes |
No |
AV8365DN |
4 Sensor 2MP Panoramic IP Camera |
65170 |
H.264 MJPEG |
Yes |
Yes |
No |
AV12186DN |
4 Sensor 3MP Panoramic IP Camera |
65184 |
H.264 MJPEG |
Yes |
Yes |
No |
AV20365DN |
4 Sensor 5MP Panoramic Camera |
65170 |
H.264 MJPEG |
Yes |
Yes |
No |
AV20185DN |
4 Sensor 5MP Panoramic Camera |
65183 |
H.264 MJPEG |
Yes |
Yes |
No |
Notes
•AV20185, AV20365, AV12186, AV8365 and AV8185 are 4-channel IP cameras. In order to support multiple video channels from a single device, VSM 7 models these devices as "Encoders".
•Arecont devices have not yet been qualified to support redundancy in VSM 7.
•Secondary streams are not supported in H, M, L template settings for Arecont Devices. However secondary stream can be configured using Custom templates.
•Arecont cameras divide the Maximum FPS the camera supports by the number of streams. This could result in lower FPS when both primary and secondary streams are configured for these cameras.
•Arecont AV10XX5, AV5115, AV2115 support VBR and multicast streaming.
•There is a restriction with motion detection for Arecont multi-sensor cameras. False motion events are generated if both half and full resolution size images are requested simultaneously using VSM or Arecont Camera Web Interface or a third party Media Player.
Supported Devices: Axis
Table 5 provides information about Axis devices that this VSM release supports.
Table 5 Supported Devices: Axis
|
Model
|
Type
|
Minimum Supported FW Version
|
Video Format
|
Media Types
|
Audio
|
Dual Stream
|
Stream Mirroring
|
Motion Detection
|
Firmware Upgrade
|
233D |
IP Camera |
4.48.4 |
NTSC / PAL |
MPEG-4 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
241Q |
Encoder |
4.47.5 |
NTSC PAL |
MPEG-4, MJPEG |
No |
Yes |
Yes |
Yes |
Yes |
241S |
Encoder |
4.40 |
NTSC PAL |
MPEG-4, MJPEG |
No |
Yes |
Yes |
Yes |
Yes |
243SA |
Encoder |
4.45 |
NTSC / PAL |
MPEG-4 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
243QBlade |
Encoder |
4.46 |
NTSC / PAL |
MPEG-4 MJPEG |
NA |
Yes |
Yes |
Yes |
Yes |
Q7401 |
Encoder |
5.20.3 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Q7404 |
Encoder |
5.20 |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Q7406 |
Encoder |
5.11.1 |
NTSC / PAL |
H.264 MJPEG |
NA |
Yes |
Yes |
Yes |
Yes |
247S |
Encoder |
4.42 |
NTSC / PAL |
MPEG-4 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
P3301 |
IP Camera |
5.40.92 |
NTSC |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
Yes |
Note
•Axis P3301 IP camera and Q7401, Q7404, and Q7406 encoders have been qualified to support redundancy in VSM 7.0.1.
•Axis 233D supports contact closure configuration and events.
•Support for 0.1fps MJPEG stream for all supported Axis models.
Supported Devices: IQinVision
Table 6 provides information about IQinVision devices that this VSM release supports.
Table 6 Supported Devices: IQinVision
|
Model
|
Type
|
Minimum Supported FW Version
|
Video Format
|
Media Types
|
Audio
|
Dual Stream
|
Stream Mirroring
|
Motion Detection
|
Firmware Upgrade
|
IQ032SI-V11 |
IP Camera |
V3.4/5 |
NTSC |
H.264 |
No |
No |
No |
Yes |
No |
IQM32NE-B5 |
IP Camera |
V3.4/5 |
NTSC |
H.264 |
No |
No |
No |
Yes |
No |
IQA35N |
IP Camera |
V3.4/5 |
NTSC |
H264 |
No |
No |
No |
Yes |
No |
IQ765N |
IP Camera |
V3.4/5 |
NTSC |
H264 |
No |
No |
No |
Yes |
No |
IQ755 |
IP Camera |
V3.1/2 |
NTSC |
MJPEG |
No |
No |
No |
Yes |
No |
Notes
•IQinVision devices have not yet been qualified to support redundancy in VSM 7.
•Support configuring NTP on the IQinVision cameras to synchronize with their VSM Media Server.
Supported Devices: Panasonic
Table 7 provides information about Panasonic devices that this VSM release supports.
Table 7 Supported Devices: Panasonic
|
Model
|
Type
|
Minimum Supported FW Version
|
Video Formats
|
Media Types
|
Audio
|
Dual Stream
|
Motion Detection
|
Firmware Upgrade
|
NP 244 |
IP Camera |
1.80 E4 |
NTSC |
MPEG-4 MJPEG |
NA |
No |
Yes |
No |
NS 202A |
IP Camera |
2.74P0 |
NTSC |
MPEG-4 MJPEG |
No |
No |
Yes |
No |
NP 304 |
IP Camera |
1.64E0_1.06 |
NTSC |
MPEG-4 MJPEG |
No |
No |
Yes |
No |
NF 302 |
IP Camera |
1.64E0_1.06 |
NTSC |
MPEG-4 MJPEG |
No |
No |
Yes |
No |
Note
Panasonic devices have not yet been qualified to support redundancy in VSM 7.
Supported Devices: Pelco
Table 8 provides information about Pelco devices that this release supports.
Table 8 Supported Devices: Pelco
|
Model
|
Type
|
Minimum Supported FW Version
|
Video Formats
|
Media Types
|
Audio
|
Dual Stream
|
Motion Detection
|
Firmware Upgrade
|
Pelco NET5401T |
Encoder |
1.9.2.1-20130619-3.3081-O3.9819 |
NTSC, PAL |
H.264, MJPEG |
Yes |
Yes |
Yes |
No |
Additional Notes on Pelco Devices
•Pelco devices have not yet been qualified to support redundancy in VSM 7.
•Audio volume controls are not supported for NET5401T.
Supported Devices: Sony
Table 9 provides information about Sony devices that this release supports.
Table 9 Supported Devices: Sony
|
Model
|
Type
|
Minimum Supported FW Version
|
Video Formats
|
Media Types
|
Audio
|
Dual Stream
|
Motion Detection
|
Firmware Upgrade
|
RX 530 |
IP Camera |
3.14 |
NTSC / PAL |
H.264 MPEG-4 MJPEG |
Yes |
Not supported |
Yes |
No |
RX 570 |
IP Camera |
3.15 |
NTSC / PAL |
H.264 MPEG-4 MJPEG |
Yes |
Not supported |
Yes |
No |
RX 550 |
IP Camera |
3.14 |
NTSC / PAL |
H.264 MPEG-4 MJPEG |
Yes |
Not supported |
Yes |
No |
Notes
•Sony devices have not yet been qualified to support redundancy in VSM 7.
•These Sony devices do not support motion detection with the H.264 media type.
•The Sony SNC-RX5x0 cameras stop streaming video when the Object Detection window in the camera's web interface.
Supported Devices: Generic IP Cameras
VSM 7.2 provides the following device drivers to support IP cameras from various vendors. The functionality they support will depend on the particular device that they are used with. They are intended to provide a quick and easy way to support devices for which there isn't yet a specific driver available for VSM. Since these drivers may not be tested with a specific device, some issues may be encountered. When using these drivers with a device, failover and redundancy are not supported.
Note The vendor specific generic driver should always be used before a non-vendor specific driver such as ONVIF.
Table 10 Supported Devices: Generic IP Cameras
|
Type
|
Minimum Supported FW Version
|
Video Formats
|
Media Types
|
Audio
|
Dual Stream
|
PTZ
|
Motion Detection
|
Firmware Upgrade
|
ONVIF |
2.0 |
NTSC / PAL |
H.264 MPEG-4 MJPEG |
Yes |
Yes |
Yes |
No |
No |
Axis |
VAPIX 3.0/Firmware 5.x |
NTSC / PAL |
H.264 MJPEG |
Yes |
Yes |
Yes |
Yes |
No |
Axis |
VAPIX 2.0 /Firmware 4.3 |
NTSC / PAL |
MPEG4, MJPEG |
Yes |
Yes |
Yes |
Yes |
No |
Arecont |
Arecont Non Panoramic Models |
NTSC |
H.264, PAL |
No |
Yes |
No |
Yes |
No |
IQEye JPEG |
V3.1/2 |
NTSC |
MJPEG |
No |
No |
No |
Yes |
No |
IQEye H264 |
V3.4/5 |
NTSC |
H264, MJPEG |
No |
Yes |
No |
Yes |
No |
Panasonic |
- |
NTSC PAL |
H.264, MPEG-4, MJPEG |
No |
Yes |
Yes |
Yes |
No |
Pelco Sarix |
Only IP cameras with Sarix Firmware |
NTSC PAL |
H.264 MJPEG |
No |
Yes |
Yes |
Yes |
No |
Sony |
2nd, 3rd, 4th and 5th generation Sony IP cameras |
NTSC PAL |
H.264, MPEG-4, MJPEG |
Yes |
Yes |
Yes |
Yes |
No |
Additional notes on Axis Generic Devices
•5MP, 3MP and 2MP resolution support has been added to Generic Axis VAPIX version 3.0 capable devices. There are other 4:3 and 16:9 aspect ratio resolutions that are also supported for these devices.
Additional notes on ONVIF devices
•ONVIF Compliant cameras have some variations in how they have implemented the ONVIF specification. Hence there may be compatibility issues when using this ONVIF driver with a particular device.
•Audio Multicast issues are observed on most of the ONVIF cameras. Hence do not enable audio when multicast is enabled for video.
•Capture Mode settings required to support certain resolutions on most cameras cannot be changed using the ONVIF APIs. So, it is assumed that the camera is in the desired capture mode before adding it to the Operations Manager using ONVIF driver.
•For information to configure ONVIF with Axis devices, see the Axis Communications website at: http://www.axis.com/techsup/faq/index.php/?action=artikel&&cat=175&id=115393.
•Before adding an ONVIF camera to a Media Sever server the camera's time should be synchronized with the Media Server or the same NTP time source as the Media Server.
•For Sony models, only UDP is supported. Streaming fails if TCP is selected.
•With Bosch ONVIF devices VSM must configure the camera with a frame rate of 30 frames per second, and dual streaming is not supported.
•For some Hikvision models, the camera requires a reboot after the codec is changed from VSM.
Additional notes on Arecont Generic Devices
•Arecont Generic Device support does not include support for the Arecont Panoramic models
•Dual stream with 1080p and its quarter resolution(960x528) cannot be configured for Arecont AV2115 models when added using a generic arecont device XML.
•When generic arecont device XML is used, VBR applies for only AVxx15, AVxx25, AVx255 models as per Arecont. For other models, maximum bit rate from the camera may exceed the configured value.
Additional notes on IQinVision Generic Devices
•JPEG generic driver: HML will work only for 5M cameras namely 755, 705,805,855.
•H264 generic driver: Only below combinations works for IQinVision M3x, D3x, 03x series: H-H, H-M, H-L, M-M, M-L, L-L
•IQinVision 805 Model is not rendering more than 2 fps in our tests.
•VBR mode is not supported for H264, 1080p stream
Additional notes on Panasonic Generic Devices
•Support for Panasonic camera WV-NP1004 for firmware Ver1.25P0 or later.
•Only MJPEG stream supported as secondary stream.
•Secondary stream is not supported if primary stream is MJPEG stream.
•4:3(800x600) capture mode not supported
Additional notes on Pelco Generic Devices
•Some valid streaming combinations may not get saved. In such cases try turning secondary off and try to save again.
Additional notes on Sony Generic Devices
•The Sony 1st generation cameras (like RZ30N) are not supported.
•For 2nd Generation cameras, motion detection is not supported.
•Our tests with the RZ25P, we could not get the camera to consistently respond to configuration APIs and this particular model is not supported with this driver.
•For all the Sony cameras supporting dual streams, primary and secondary should be configured with same transport type i.e. both should be either unicast or multicast.
•For the some Sony cameras, we have noticed failures when the attempting to change configurations multiple times in quick succession, retrying the same configuration change after 5 minutes will succeed.
Supported Devices: Analog Cameras
This VSM release provides support for the following analog cameras.
Table 11 Supported Devices: Analog Cameras
|
Type
|
Video Formats
|
Serial Protocol Support
|
Generic |
NTSC / PAL |
No |
Bosch |
NTSC / PAL |
Yes |
Panasonic |
NTSC / PAL |
Yes |
Generic Pelco-D |
NTSC / PAL |
Pelco-D |
Generic Pelco P |
NTSC / PAL |
Pelco P |
Pelco Min-Spectra |
NTSC / PAL |
Pelco-D |
Cyberdome I |
NTSC |
Yes |
Cyberdome II |
NTSC |
Yes |
Notes on Cyberdome devices
•The Cyberdome I and Cyberdome II devices also have On Screen Display Menu support.
Minimum Supported Firmware for IP cameras and Encoders
Table 12 describes the minimum firmware versions for cameras and encoders in this release of Cisco VSM.
Table 12 Supported Camera and Encoder Firmware
|
Manufacturer
|
Model
|
Minimum Supported Firmware Versions
(Compatible with Release 7.2)
|
Cisco |
2400 Series Cameras |
2.5.1 |
Cisco |
2500 Series Cameras |
2.5.1 |
Cisco |
2600 Series Cameras |
4.4.1-1 |
Cisco |
2830 Camera |
1.2.2-20 |
Cisco |
2835 Camera |
1.2.2-20 |
Cisco |
3000 Series Cameras |
1.2.1-73 |
Cisco |
3421V Cameras |
1.2.1-73 |
Cisco |
4300 Camera |
2.4.1-275 |
Cisco |
4500 Camera |
2.4.1-275 |
Cisco |
4300E Camera |
3.2.2-204 |
Cisco |
4500E Camera |
3.2.2-204 |
Cisco |
2900 Series Cameras |
1.6.18 |
Cisco |
5000 Series Cameras |
1.6.17 |
Cisco |
6000 Series Cameras |
1.2.1-73 |
Cisco |
6930 Camera |
1.2.2-20 |
Cisco |
7030 Camera |
1.2.1-73 |
Cisco |
CIVS-SENC-4P encoder |
1.2.0-4 |
Cisco |
CIVS-SENC-8P encoder |
1.2.0-4 |
Arecont |
AV10XX5 |
v65218, v65202 |
Arecont |
AV20185 |
v65183 |
Arecont |
AV20365 |
v65170 |
Arecont |
AV2115 |
v65218 |
Arecont |
AV5115 |
v65218 |
Arecont |
AV5155 |
v65152 |
Arecont |
AV8185DN |
v65183 |
Arecont |
AV8365DN |
v65170 |
Axis |
233D |
v4.48.4 |
Axis |
243SA |
v4.45 |
Axis |
243Q |
v4.46 |
Axis |
Q7401 |
v5.20.3 |
Axis |
Q7404 |
v5.20 |
Axis |
Q7406 |
v5.11.1 |
Axis |
247S |
v4.42 |
Axis |
P3301 |
5.40.92 |
Axis |
Q6035 |
v5.25 |
Axis |
241Q |
v4.47.5 |
IQinVision |
IQ032S |
v3_4_5 |
IQinVision |
IQM32NE-B5 |
v3_4_5 |
IQinVision |
IQ755 |
v3.1.2 |
IQinVision |
IQ765N |
v3_4_5 |
IQinVision |
IQA35N |
v3_4_5 |
IQinVision |
IQD32S |
v3_4_5 |
IQinVision |
IQ705 |
v3.1.2 |
IQinVision |
IQ711 |
v3.1.2 |
IQinVision |
IQ852 |
v3.1.2 |
IQinVision |
IQ853 |
v3.1.2 |
IQinVision |
IQ855 |
v3.1.2 |
IQinVision |
IQA22S |
v3.1.2 |
Panasonic |
NP244 |
1.80 E4 |
Panasonic |
NS202A |
2.74P0 |
Panasonic |
NP304 |
1.64E0_1.06 |
Panasonic |
NF302 |
1.64E0_1.06 |
Panasonic |
NP-502S |
np502_166E_cam_110 |
Panasonic |
SC-385 |
sc385_166E_cam_139 |
Pelco |
Net5401 |
1.9.2.1-20130619-3.3081-O3.9819 |
Pelco |
ISX0C |
1.8.2.18-20121109-1.9080-A1.8503 |
Pelco |
SD4E23 |
1.8.2.11-20120623-1.2084-O1.8120 |
Pelco |
SD5118 |
1.8.2.18-20121126-1.9310-A1.8726 |
Sony |
RX530 |
V3.14 |
Sony |
RX570 |
V3.15 |
Sony |
RX550 |
V3.14 |
Sony |
DM110 |
V1.11 |
Sony |
RZ25 |
V1.40 |
Sony |
RZ30 |
V3.14 |
Sony |
EP580 |
V1.78 |
Sony |
CH240 |
V1.77 |
Axis |
P3301 |
5.40.9.2 |
Axis |
6032e |
5.41.1.3 |
Bosch AutoDome |
700IP |
39500570 |
Pelco |
D5118-AD74029 |
1.8.2.18-20121126-1.9310-A1.8726 |
Samsung |
SND-7080 |
2.00_121004 |
Sony |
CH240 |
1.77.00 |
Sony |
EP520 |
1.78.00 |
Panasonic |
SF335 |
Application: 1.66
Image data: 2.02
|
Obtaining and Installing Licenses
To install a license, purchase the license and obtain the license file, then upload the file to the Operations Manager.
Table 13 lists the part numbers for the Cisco VSM licenses. Multiple camera and VSMS licenses can be included in a single license file. For example, a single license file might include support for 25 additional cameras and two additional VSMS devices.
Table 13 License Part Numbers
|
Part
|
Description
|
FL-CPS-MS-SW7 |
License for one Media Server on a physical server (Cisco UCS or MSP) |
FL-CPS-OM-SW7 |
License for one Operations Manager on a physical server (Cisco UCS or MSP) |
L-CPS-MS-SW7= |
eDelivery License for one Media Server on a physical server (Cisco UCS or MSP) |
L-CPS-OM-SW7= |
eDelivery License for one SASD on a physical server (Cisco UCS or MSP) |
L-CPS-SASD-7= |
eDelivery License for 1 SASD with VSM 7 |
L-CPS-VSM7-1CAM= |
eDelivery License for 1 camera connection with VSM 7 |
L-CPS-VSMS7-B-VM= |
eDelivery License for one Media Server on a VM running on a Cisco UCS B Series |
L-CPS-VSOM7-B-VM= |
eDelivery License for one Operations Manager on a VM running on a Cisco UCS B Series |
L-CPS-VSMS7-C-VM= |
eDelivery License for one Media Server on a VM running on a Cisco UCS C Series |
L-CPS-VSOM7-C-VM= |
eDelivery License for one Operations Manager on a VM running on a Cisco UCS C Series |
L-CPS-VSMS7-E-VM= |
eDelivery License for one Media Server on a VM running on a Cisco UCS E-Series |
L-CPS-VSOM7-E-VM= |
eDelivery License for one Operations Manager on a VM running on a Cisco UCS E-Series |
Notes
•A license for 10,000 Cisco cameras is included by default (you do not need to purchase and install an additional license for Cisco cameras).
•By default, you can add one Media Server and 10 non-Cisco cameras without purchasing or installing an additional license.
Procedure
Step 1 Purchase additional licenses:
a. Determine the part number for the license you want to purchase (see Table 13).
b. Purchase the licence by contacting your Cisco sales representative or any Cisco reseller. For more information, visit http://www.cisco.com/en/US/ordering/index.shtml.
c. When the purchase is complete, you are issued a Product Authorization Key (PAK) in paper form, or in an e-mail message.
Step 2 Obtain the license file:
a. Locate the Product Authorization Key (PAK) that was created with the purchase.
b. In a web browser, open the Cisco Product License Registration web page.
http://www.cisco.com/go/license/
c. Follow the on-screen instructions to complete the form and enter the Product Authorization Key (PAK). When you are done, a license file with the extension .lic is sent to your e-mail address.
d. Transfer the file to the drive of the PC used for the configuration.
Step 3 Install the license file in VSM:
a. Log in to the Operations Manager.
b. Select System Settings > Software Licensing.
c. Click Add and select the license file located on your local drive.
d. Click Save to install the file and activate the additional capacity.
The additional capacity is available immediately. You do not need to restart the server or take additional steps.
Understanding the VSM Software Types
Table 14 describes the different types of software and firmware that are installed on servers, cameras, and encoders.
Table 14 VSM Software Types
|
Software Type
|
Description
|
System software |
System software denotes the VSM software, including Media Server, Operations Manager, Cisco VSM Management Console, Safety and Security Desktop and Multipane clients. All servers running the Operations Manager and associated Media Server services must run the same software version. Use the Cisco VSM Management Console to update System Software, as described in the Server Upgrade section of Cisco Video Surveillance Management Console Administration Guide. |
OVA image (for VM installations) |
OVF template files are used to install the system software as a virtual machine (VM) on a supported Cisco Unified Computing System (UCS) platform. •OVA template files are downloaded from the Cisco website. •The file format is .ova. For example: Cisco_VSM-7.2.0-331d_ucs-bc.ova •See the Cisco Video Surveillance Virtual Machine Deployment and Recovery Guide for UCS Platforms for instructions to install the .ova image and perform the initial VM setup. •After the VM setup is complete, use the Management Console to complete the configuration. |
USB Recovery Disk image |
Use the USB Recovery Disk image to create a Cisco VSM 7 Recovery Flash Drive (for example, on a USB stick). The recovery disk can be used do the following: •Repair: reinstalls the Operating System files and partitions without erasing video files stored on the server. You must backup the Cisco VSM database before using the recovery image, and then restore the database after the recovery process is complete. This action also preserves the RAID configuration. •Factory Restore: Restores the server to its factory default settings, reinstalls the operating system, and clears and reconfigures the RAID. This action deletes all data, configurations, software and video files from the appliance, and then reinstalls the operating system and Cisco VSM software. Perform this procedure only if necessary. See the Cisco Video Surveillance Manager Flash Drive Recovery Guide for more information. |
Device firmware |
Device firmware is provided by the device manufacturer. The firmware for Cisco devices can be upgraded using Operations Manager. Firmware for other manufacturers is upgraded using a direct connection. See the "Upgrading Camera and Encoder Driver Firmware" section of the Cisco Video Surveillance Operations Manager User Guide for instructions to upgrade Cisco device firmware, or refer to the device documentation. |
Device driver packs |
Device driver packs are the software packages used by Media Servers and the Operations Manager to interoperate with video devices, such as cameras. Driver packs are included with the Cisco VSM software, or may be added to a server at a later time to add support for new devices or features. •Install new driver packs to add support for additional devices. •Upgrade existing driver packs to enable support for new features. Note We strongly recommend upgrading driver packs using the Operations Manager interface (see the "Driver Pack Management" section of the Cisco Video Surveillance Operations Manager User Guide). This allows you to upgrade multiple servers at once. Driver packs must be upgraded to the same version on each server where the Media Server and Operations Manager services are enabled or a driver pack mismatch error occurs. Templates cannot be revised when a driver pack mismatch error is present. •The Management Console interface can also be used to upgrade the driver packs for a single server at a time. See the "Driver Pack Management" section of the Cisco Video Surveillance Operations Manager User Guide. |
Language Packs |
Language packs can be added to display the VSM user interfaces in non-English languages. Language packs are added using the Server Upgrade page of the Cisco VSM Management Console. You must upgrade the language packs on all servers in your deployment. See the Server Upgrade section of Cisco Video Surveillance Management Console Administration Guide for more information. |
Obtaining VSM Software
Complete the following procedure to obtain software and other information for the following VSM products and components:
Procedure
Step 1 Go to the following URL.
http://www.cisco.com/go/physicalsecurity
Step 2 Click View All Products.
Step 3 Click the appropriate category (such as the Cisco IP Camera model).
Step 4 Click Download Software and follow the on-screen instructions.
Tip You can also navigate to the Cisco Video Surveillance Manager download page and select an option for Video Surveillance Device Driver Software or Video Surveillance Media Server Software.
Caveats
This section includes the following topics:
•Using the Software Bug Toolkit
•Open Caveats
•Resolved Caveats
Using the Software Bug Toolkit
You can use the Bug Toolkit to find information about most caveats for Cisco VSM releases, including a description of the problems and available workarounds. The Bug Toolkit lists both open and resolved caveats.
To access Bug Toolkit, you need the following items:
•Internet connection
•Web browser
•Cisco.com user ID and password
To use the Software Bug Toolkit, follow these steps:
Procedure
Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/.
Step 2 Log in with your Cisco.com user ID and password.
Step 3 To look for information about a specific problem, enter the bug ID number in the Search for bug ID field, then click Go.
Step 4 To look for information if you do not know the bug ID number:
a. Choose Security from the Select Product Category menu.
b. Choose the desired product from the Select Product menu.
c. Choose the version number from the Software Version menu.
d. Under Advanced Options, choose Use default settings or Use custom settings. The default settings search for severity 1, 2, and 3 bugs, open and fixed bugs, and only bugs containing bug details. Use the custom settings to change the severity and status parameters, or to search for keywords within the bug headline and description.
Open Caveats
Table 15 lists caveats that are open in this release.
Table 15 Open Caveats
|
ID
|
Description
|
CSCtz36101 |
Expand/Collapse mode for video not working when PTZ is enabled from MPC |
CSCtz60444 |
MS should not allow FmUpgrade and ServerUpgrade at the same time |
CSCtz67269 |
FmUpg and driver pack upgrade should not be allowed to run concurrently |
CSCub06627 |
SASD-Crash when total number of panes from multiple processes exceeds 48 |
CSCub70689 |
Bulk Soft deleting 101 cameras, 6 cameras failed |
CSCuc07318 |
Client: Hard to re-size the Motion Window with low resolution |
CSCuc23160 |
Medianet camera not removed from MS cache |
CSCuc37050 |
DHCP camera will not stream after MS goes down & up with IP change |
CSCue26428 |
Memory Leaks in SecureTcpSocket for HttpServer |
CSCue36418 |
Media Server keeps sending Chassis Intrusion Event |
CSCue53069 |
Audio not clear for Generic VAPIX2 drivers enabled camera |
CSCue69485 |
Perf: Queue overflow & frame drops seen when MS backup is initiated |
CSCue81572 |
Virtual MS has critical alert - Load Avg above threshold |
CSCue84002 |
medianet: failover MS entry is not push to the camera NVRAM |
CSCue86163 |
Cameras' NTP entries not updated after MS's interface IP addr changes |
CSCuf08169 |
Serial PTZ connection on both Cyberdome I&II cannot be set at same time |
CSCuf39097 |
init_xxx scripts need to log failures to ims.log |
CSCug47472 |
Critical hardware error when no hardware data reported |
CSCug72403 |
Make event notifications "not fail" when bad XML encountered |
CSCug82414 |
SDT reports 0 values for all health data causing VSM critical event |
CSCuh31987 |
multicast port range validation is not happening for onvif devices |
CSCuh34004 |
Sometimes after being downloaded clip shows wrong time and does not play |
CSCuh90217 |
VSOM Global Settings doesn't work, when non-Admin user login to Win 8 |
CSCui02832 |
UpdateCamera operation with 24 cameras take 2 hrs to complete |
CSCui02955 |
Cisco 29xx JPEG video freeze and jump |
CSCui12720 |
Missed RTP packets from 2830 camera |
CSCui28694 |
Sony RZ25P fails to configure HML stream intermittently |
CSCui38584 |
RUS: Review Player Tamper Proof Tool exposes password on RUS client |
CSCui45429 |
SASD Smooth video settings: issues with Cisco and onvif cameras |
CSCui54480 |
VSOM doesn't prompt to reset password |
CSCui58382 |
SASD Thumbnail: Need an error msg when creating clip with duped name |
CSCui63138 |
VSOM do not display 3M bitrate for 15FPS in 283x camera |
CSCui65920 |
SASD Light: Cannot launch Wall if it's created by LDAP user |
CSCui66256 |
Cannot delete In-Progress Clip- Invalid clip type/state error |
CSCui67961 |
VSOM 7.0.x - After oversubscription error triggered, server still Red X |
CSCui69759 |
Error when enable all 4 ports on 4P encoder |
CSCui80758 |
VSMC does not display the status of FC port 0 |
CSCui80940 |
VSMC requires a service restart to see updated FC link status |
Resolved Caveats
Table 16 lists caveats that are resolved in this release.
Table 16 Resolved Caveats
|
ID
|
Description
|
CSCtr68068 |
scheduler process crashed in VSMS-7.0.1-12d- (updated) |
CSCub47178 |
No reason provided for clipping failed in SASD and no info in vsom |
CSCuc43145 |
Streams outage after MS reboot/eth1- DHCP (eth1 netwk conn avail later) |
CSCue47056 |
Configuration mismatch caused by DNS setting white space |
CSCue56548 |
Getting multiple Motion Start events in SASD after cisco service restart |
CSCue59108 |
Upgrade fails if upgradeinputfile exists in input directory |
CSCue71673 |
Device state not propagated when redundant/failover is stopped/started |
CSCue76469 |
Frames are sometimes dropped when the CPS-2RU server is oversubscribed. |
CSCue76506 |
Vsmdbg reports sed unknown option error |
CSCue76531 |
Perf: Slow purging events results into event overload alert in VSOM |
CSCue76541 |
Transfer of remote backups uses incorrect path |
CSCue76541 |
Transfer of remote backups uses incorrect path |
CSCue76702 |
Perf: GUI show connection loss while VSOM backup is in progress |
CSCue76909 |
Server upgrade fails with root user disabled |
CSCue76909 |
Server upgrade fails with root user disabled |
CSCue76909 |
Server upgrade fails with root user disabled |
CSCue85207 |
Pane in unavailable after Full Screen Mode is closed from the task bar |
CSCue90576 |
SASD Monitor doesn't start, if Unattended config begins&ends too quickly |
CSCue91821 |
User guides are not able to open in vsom -> operations page |
CSCue93232 |
Migration: speedo and megablock is missing in the model_version.csv |
CSCue93368 |
VSOM GUI pages don't reflect added/deleted item and need to be refreshed |
CSCue94872 |
Onvif PTZ camera: Presets are not saved after restart of media server |
CSCue98751 |
SASD MonitorWinSvc is placed in different dir than the rest of SASD |
CSCue98946 |
VSOM restore via VSMC does not handle backup from previous version |
CSCuf01458 |
AV is not sync after resolution change on H264 & MPEG4 codec MP4 clip |
CSCuf01833 |
Bosch Onvif: Video stream gets disconnected every 2-3 minutes |
CSCuf04700 |
Cannot replace cam if there is more than one soft-del dev with same ID |
CSCuf27499 |
No hardware status (Fan Speed, temperature & etc.) on SLES10SP1 |
CSCuf28191 |
Support-report partition table type not shown in RedHat |
CSCuf37751 |
msi.log on VM flooded with messages about bad msi.log file location |
CSCuf51907 |
Migrate SMD files with E0 before importing into VSMS database |
CSCuf61447 |
Change template on model type sorted list does not work in bulk actions |
CSCuf82292 |
Recovery 2.2 - /media2 will not be checked while upgrading to 7.0.1 |
CSCug40838 |
VSMS MySQL server start fails due to previous mysql upgrade error |
CSCug41083 |
Minimum password length setting does not affect password requirements |
CSCug46631 |
Viewing video in different VSOM pages does not resolve hostname/IP |
CSCug46637 |
NTP change on VSMS from VSOM causing reboot without a warning |
CSCug46666 |
IQeye driver not showing firmware version in VSOM camera page |
CSCug46701 |
Driver upgrade via VSMC on RHEL 5.3 fails with OS mis-match error |
CSCug46755 |
VSM upgrade fails with corrupted VSMS database |
CSCug47478 |
Verify amqbroker is present and deployed during startup |
CSCug54794 |
Userlist is exposed on trying to login as user who exists only in LDAP |
CSCug55044 |
Activex control not properly disposed |
CSCug57843 |
Cannot access the location if one of the user-group has excludes |
CSCug59511 |
Unable to move location if higher level location contains a view |
CSCug59860 |
VSOM 7.0: VSMC and VSOM UI should prevent Dual Homing of VSOM Server |
CSCug62977 |
VSM 7.x install log file in incomplete |
CSCug63316 |
LDAP and Usergrp pages are rendered slowly with large number of filters |
CSCug69336 |
Modified frame rate for Pelco-Sarix cameras (cisco_ipc5000.xml) |
CSCug72119 |
VSMS checks Arecont motion detection to frequently |
CSCug75242 |
Cannot change SMTP server settings in co-located server |
CSCug80036 |
VSOM ftp backup to remote host fails |
CSCug80666 |
Error While deleting the schedules from MS |
CSCug82940 |
PlayForward does not happen after PlayReverse is done to the beginning |
CSCug88134 |
SASD Unattended Fullscreen mode doesn't switch video properly |
CSCug90460 |
xvcrman core dump |
CSCug95633 |
Memory leaks in MediaOut by calls end before or at RTSP tear down |
CSCuh08765 |
Too frequent ptz requests to Cisco 2900 cameras in 7.0.1 |
CSCuh17990 |
SASD users require write access to application program files directory |
CSCuh25975 |
VSM 7: AXIS camera Motion Windows need to be matched to a Rotated Image |
CSCuh27006 |
Increase the timeout in cisco driver in all HTTP connection to camera |
CSCuh28970 |
VSM 7.0.1 After Failover fails back, primary missing location Entry |
CSCuh33944 |
HttpServer process crashed handling SSL handshake |
CSCuh38592 |
video data removed when database not found |
CSCuh44595 |
Cannot add PTZ tour on replaced cameras |
CSCuh47553 |
After soft delete, still schedule jobs are present in MS DB |
CSCuh50676 |
Do not allow users to configure server hostname of localhost |
CSCuh58215 |
H264 parser causes core dump if invalid data is received |
CSCuh64126 |
PTZ Tour Configuration UI doesn't handle all presets |
CSCuh73606 |
VSMC Does not display streams correctly on redundant VSMS |
CSCuh79261 |
Upgrade Active MQ CPP Client to 3.7.0 + patch |
CSCui04233 |
Hostname can be configured as FQDN and domain shouldn't be populated. |
CSCui15733 |
Soft-deleted analog camera keeps serial controller association |
CSCui25297 |
non super users not able to view past recordings after camera replace |
CSCui25713 |
Cannot use camera address 1 with Pelco P protocol |
CSCui28868 |
Umsdevice with non-ptz analog camera configured for encoder serial port |
CSCui31081 |
Smd2db crashes processing corrupted smd file |
CSCui33240 |
ExportUID script only exports the first 500 cameras |
Related Documentation
See the following locations for the most current information and documentation:
Cisco Video Surveillance 7 Documentation Roadmap
Descriptions and links to Cisco Video Surveillance documentation, server and storage platform documentation, and other related documentation.
http://www.cisco.com/go/physicalsecurity/vsm/roadmap
Cisco Physical Security Product Information:
www.cisco.com/go/physicalsecurity/
Cisco Video Surveillance Manager Documentation Website
www.cisco.com/go/physicalsecurity/vsm/docs
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Release Notes for Cisco Video Surveillance Manager, Release 7.2
© 2013 Cisco Systems, Inc. All rights reserved.
Feedback