PDF(606.1 KB) View with Adobe Reader on a variety of devices
Updated:December 7, 2016
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
In Release 7.6, two Operations Manager servers can be configured as a redundant pair for high availability (HA). Since the Operations Manager is responsible for configuring and coordinating the entire Cisco Video Surveillance deployment, this helps ensure uninterrupted system access for users and administrators.
To configure Operations Manager HA, install two servers: a Master server and a second Peer server. All configurations, data, and logs on the Master server are automatically replicated on the Peer server. If the Master server goes down or is unavailable, the Peer server is ready to take control with minimal impact.
– Overview information and configuration instructions.
– See also the Troubleshooting section in the “Operations Manager High Availability” section for important information.
Camera App Licensing and Management
Cisco VSM 7.6 introduces support for Camera Apps, which can be installed, licensed, updated, monitored, enabled, or disabled using the Operations Manager. These bulk management features allow Camera Apps to be managed in large numbers of cameras.
See the following important notes for more information:
Cisco VSM 7.6 includes major software installation and upgrade improvements using Operations Manager. You can now monitor the installation and upgrade status, including the installation/upgrade progress of Operations Manager and Media Server software, and all other services such as Map Server, Metadata generation, and Federator.
iOS Application for Apple Mobile Devices
Cisco VSM 7.6 includes a new iOS mobile application for Apple devices such as the iPad and iPhone. App features include recorded video playback, thumbnail video preview, and user profiles that allow multiple users to share a single device. See the Apple App Store for more information.
New Cisco VSM Management Console Interface
The Cisco VSM Management Console has been redesigned for improved system maintenance features and functions. The Management Console user interface design is now also similar to the Operations Manager to improve functionality and ease-of-use.
Support for DSP Cameras
Cisco VSM 7.6 supports the new Cisco 6500PD and 7030PD DSP cameras, which include:
Camera App management and licensing.
Integration of camera alerts (such as motion detection, video analytics and camera health) with Cisco VSM.
Additional Connected Edge Storage Features
Cisco Video Surveillance Safety and Security Desktop (Cisco SASD) operators can now copy video from camera storage to Cisco VSM and play back the video using the SASD Alert workspace.
Operations Manager can be used to format SD Cards installed in supported cameras.
Camera health alerts are supported in IP Cameras configured with Connected Edge Storage. Health alerts include of SD Card failures.
Improvements in Network Management of Endpoints
Cisco VSM 7.6 supports NAT for IP cameras and encoders. This allows deployment models where the Media Server is separated from the cameras and encoders by NAT.
The NTP server can be configured on multiple IP cameras and encoders (bulk management).
IP cameras and encoders can be added using a hostname, or an IP address.
Recording and Grooming Improvements
Cisco VSM 7.6 changes the behavior for motion and event based recording when a camera generates events for a long period of time. In previous versions, the default behavior for record on motion/event was to stop recording after two hours. This was by design since events continuing for such a long period of time meant that motion detection or event recording was not properly configured. By stopping recording in this case, Cisco VSM protected the available storage and retention for other cameras. Customer feedback indicated that it was preferred that video continue to be recorded even at the expense of overall system retention time. As a result, Cisco VSM 7.6 changes the behavior in this case to continue recording. See the Important Notes section for more information on how to properly configure motion recording.
Cisco VSM 7.6 includes improved performance when grooming video on heavily loaded Media Servers. The grooming will always complete as long as the overall recording load meets the supported specifications for the system.
The Cisco VSM Map Server can now be co-installed with the Operations Manager.
4x3 and 5x5 Views are now supported.
Views can be configured with secondary streams.
Cisco VSM can be configured with an external NTP server.
Templates are now available for 8 additional Axis IP camera models and 2 additional Axis encoder models.
A separate pop-up video window can be displayed in Cisco SASD.
Multi-pane Views can be created, edited and saved using Cisco SASD.
The CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9 servers support 4TB drives.
Usability improvements to SASD Alert/Event display including sortable alert types and color coded event status.
Getting Started
Cisco VSM Release 7.6.0 is pre-installed on new servers, can be installed as a virtual machine, or used to upgrade an existing deployment.
Table 1 Cisco VSM Installation and Upgrade Options
Option
Description
Notes
Pre-installed
Release 7.6.0 is pre-installed in new installations on the Cisco Connected Safety and Security UCS Platform Series servers CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9.
Cisco Connected Safety and Security UCS Platform Series Servers (Release 7.2 and Higher)
Cisco VSM Release 7.6.0 is pre-installed on new installations of the Cisco Connected Safety and Security UCS Platform Series (CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9) when ordered with the Cisco VSM software installed.
Cisco VSM releases 7.2.x and higher can be upgraded using the Release 7.6.0 system .zip file that includes all required software packages. Installing the.zip file upgrades all components and ensures that all packages are running the required versions.
Note Upgrading from Cisco VSM 7.5.2 to 7.6.0 is not supported. To upgrade from Cisco VSM 7.5.2, upgrade directly to Cisco VSM Release 7.6.1 or 7.7.
To upgrade from Release 7.2.0 or lower, you must first upgrade to Release 7.2.1, 7.2.2 or 7.5, and then upgrade to Release 7.6. See the Release Notes for the release running in your deployment for more 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.
Release 7.2 was pre-installed on the Cisco Connected Safety and Security UCS Platform Series (CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9).
Virtual Machine (VM) installations can also be upgraded using the Cisco VSM Management Console.
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 and higher—Cisco Connected Safety and Security UCS series servers (CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9).
The migration procedure requires assistance from a Cisco representative. To migrate an existing system, you must first migrate the servers and data from Cisco VSM 6.3.2 MR2 and 6.3.3 to Cisco VSM 7.2.x, and then upgrade the system to Release 7.6.0:
1. Contact your Cisco representative for assistance and instructions.
2. Migrate the system from Cisco VSM 6.3.2 MR2 or 6.3.3 to Cisco VSM 7.2.x.
3. Upgrade all physical and virtual Cisco VSM servers to Release 7.6.0 using the Cisco VSM Management Console.
Contact your Cisco representative for more information.
Note Please also see the Cisco VSM 7.5 Release Notes for more other important notes that apply to this release.
Operations Manager HA Supported Configurations
Cisco VSM Operations Manager high availability (HA) is supported with the following hardware and software requirements. For more information, see the following:
Two standalone physical or virtual servers must be installed on the network.
– Supported physical servers: CPS-UCS-1RU-K9 or CPS-UCS-2RU-K9
– Supported virtual machines: VMs deployed using the Cisco VSM release 7.5 or 7.6 OVA templates.
Note Any data on the server used as the Peer server will be deleted and replaced with the data from the Master server.
We recommend two CPS-UCS-2RU-K9 servers for best performance.
Performance issues can occur using the CPS-UCS-1RU-K9 servers for Operations Manager HA since performance issues (such as slowness) may occur.
Do not mix a CPS-UCS-2RU-K9 server with a CPS-UCS-1RU-K9 server.
Additional server requirements and recommendations:
Stand-alone servers—Only stand-alone physical or virtual servers are supported in an HA configuration. The Operations Manager servers can not be co-located with other server services, such as a Media Server.
Operating system—Red Hat 6.4 64 bit OS only (SUSE and Red Hat 5.8 are NOT supported).
We recommend that both servers have the same hardware specifications such as processor, hard disk storage, and other attributes. For example, two CPS-UCS-2RU-K9 servers.
We do not recommend using Cisco UCS E-series platform servers for Operations Manager HA.
Both servers used for HA must be fully up and running prior to configuring HA or replacing the Peer server. Verify that there are no pending jobs (of any kind) in the Peer server.
Split Brain recovery support:
At least one Media Server must be added to the Split Brain Configuration to support recovery if communication between the Master and Peer server is lost.
Subnet—Both servers must be in the same network subnet. This ensures connectivity and data synchronization between the servers.
NIC port—Both servers must be connected to the network using the same NIC port: for example, Eth0. Only a single Ethernet port can be active (either Eth0 or Eth1).
Three IP addresses/hostnames are required:
– An IP address/hostname for the Master server Ethernet (NIC) port.
– An IP address/hostname for the Peer server Ethernet (NIC) port.
– A virtual IP address that is shared by both servers.
Note End-users should always use the virtual IP address to access the Operations Manager since it will still work even in a failover occurs. Users should never use the server Ethernet port (NIC) address since connectivity can be lost if the server is unreachable.
Security certificate requirements:
By default, all Cisco VSM server include a self-signed certificate. Using the self-signed certificate on the Operations Manager server causes a security warning to appear when users log in the Operation Manager.
To avoid this, you can create and install a web server certificate for the Operations Manager servers. The certificate must point to the HA virtual IP address and be installed on both Operations Manager servers (Master and Peer) used in the HA configuration.
The Management Console password for Operations Manager each server. This is the localadmin password used to access the Cisco VSM Management Console, and is set during the initial server setup.
The admin password used to access the browser-based Operations Manager interface.
Firewall Service on a Red Hat Cisco VSM Server
If the firewall service was stopped on a Red Hat Cisco VSM server prior to upgrading to Cisco VSM release 7.6, the Cisco VSM 7.6 upgrade will start the firewall service.
Camera App Licenses Must be Installed Using Operations Manager
There are two types of camera app licenses:
A device-specific license installed directly on a single device. This license does not allow Operations Manager to manage the license or app.
A single or group license that is installed and managed using Operations Manager.
Only one of these license types can be active on the camera device at a time. To use the license(s) managed by Operations Manager, you must first deactivate any device-specific licenses.
Procedure
Step 1 If any camera app licenses are installed on the device, deinstall those licenses using the camera UI.
Camera Apps Are Disabled for When Modifying Templates
Camera video apps may be automatically disabled on Cisco cameras if the camera template is modified in one of the following ways:
1. Camera video apps are automatically disabled on Cisco cameras if a custom template is applied that is configured with a high primary stream resolution (5M) or a frame rate higher than 15fps. This occurs even if camera apps are enabled on the template. A configuration mismatch also occurs on the device. To avoid this, you must configure the camera custom template before enabling the camera apps.
Affected Cameras—Cisco camera models 2830, 2835, 3421, 3520, 3530, 3535, 6020, 6050, 6400, 6030, 6000P, 6400E, 6930, 7030, and 7530E.
2. If the device has camera apps enabled, and the primary stream configuration is changed from Low or Medium to High, or if you enable the secondary video stream, then the camera apps are automatically disabled on the device.
Affected Cameras—Cisco camera models 3421, 3520, 3530, 3535, 2830, and 2835.
To avoid this, you must configure the camera custom template before enabling the camera apps, as described in the following Workaround.
Workaround
1. Disable all video apps that are running on the device.
2. Change the configuration, as necessary:
a. Configure the custom template with high primary stream resolution or a frame rate higher than 15fps.
b. Enable the secondary video stream.
3. Enable all required camera apps in the camera’s custom template.
Backups to Local Disk Support Configuration Data Only
Prior to Cisco VSM release 7.5, automatic backups to local storage could include configuration and historical data. In release 7.5 and later, however, automatic backups to the local disk support configuration data only. When upgrading from release 7.2 or earlier to release 7.5 or later, any automatic backups will be changed to the configuration only option.
Record on Motion Enhancements
In Cisco VSM Release 7.5, Record on Motion recordings are started when as single Motion Start command is received from the camera. Recording continues until a Motion Stop is received. If the camera is not configured correctly, it may detect motion continuously and it will not send a Motion Stop command for a long time. Also, in the rare scenario where a Motion Stop event from the camera is missed, motion recording would continue indefinitely and a large amount of storage would be used.
To address these issues, Cisco VSM Release 7.5 limits the maximum duration for motion recording after a Start command to 2 hours if no stops are received. However, it is possible that valid motion that lasts longer than 2 hours is being seen by the camera, and the video after 2 hours will not be recorded with motion recording in Cisco VSM Release 7.5.
Cisco VSM 7.6 resolves all of these issues by changing Record on Motion in two ways:
Configures Cisco cameras to send Motion Start commands continuously as long as there is motion. Recording starts when a Motion Start is received and it stops after 1 minute if no more Start commands are received.
The 2 hour limit on motion recording has also been eliminated.
Best Practices for Recording on Motion
When using motion recording in Cisco VSM, there are several important considerations that should be followed to properly control the recording of video with motion detection.
Cisco VSM supports configuration for default motion detection settings to allow quick setup of camera motion detection. The motion detection inclusion window is set to the full frame and sensitivity is set to a default value. These settings may or may not be optimal for detecting video in all situations depending on many factors such as lighting, the camera placement and if there is extraneous motion in the scene. For example, if there is an area in the frame where there is always motion, the camera may continuously detect motion and motion recording will continuously record video. Prior to Cisco VSM 7.6, recording would stop by default after 2 hours of continuous motion activity. In Cisco VSM 7.6, that behavior has been changed and motion based recording will continue as long as there is motion activity. This may negatively affect video retention for all cameras on the same Media Server, if this motion recording behavior s not expected.
Review the following best practices and recommendations when using motion recording.
Do not rely solely on the default motion detection settings for motion recording for outdoor cameras without assessing the results. Outdoor scenes are more complex with changes in lighting (day/night), clouds, people, cars, trees, and leaves moving in the wind. For outdoor cameras, it is very common to have extraneous motion that should be ignored because that activity is not of interest. First, adjust the zoom and focus so the camera’s field of view and focus so that the detection settings are optimal for all moving objects in that field of view. Second, the motion detection inclusion and/or exclusion windows should to be set, not just the sensitivity settings. This helps to accurately trigger recording for the important motion activity while ignoring undesired activity. Roads and trees in the background are common causes of unexpected motion activity where motion only in the foreground is desired for controlling recording.
When configuring motion recording, make sure that the camera is detecting motion as expected. Use the Operation Manager’s motion detection configuration page to observe the camera’s motion activity, and ensure the field of view is correct. Make sure that motion is being detected as expected and adjust the inclusion and exclusion windows and settings as needed.
When configuring motion detection for a camera using Operation Manager, always click the Save Motion Config button to save changes before closing the browser or leaving the motion configuration page. If you do not save the motion settings, the motion detection recording will not operate as intended.
Event History Cleared When Upgrading from 7.2 or Earlier
Upgrades from versions 7.2 or earlier will clear all event history (the event history data is not included in the upgrade).
Save View is Removed from the Operations Manager Monitor Page
The Save View option is removed from the Operations Manager Monitor page in Release 7.6.
To create views, use the Operations Manager Views admin page, or the Cisco Video Surveillance Safety and Security Desktop (Cisco SASD) application.
Released Versions
Cisco VSM Release 7.6.0 is released with Build 122i. The component package versions are:
VSOM-7.6.0-120
CDAF-7.6.0-120_120915
VSMS-7.6.0-075d
MPClient-7.6.0-28
SASD-7.6.0-41
VSF-7.6.0-120 (RHEL 6 only)
GeoServer-7.6.0-006 (RHEL 6 only)
MetaDataService-7.6.0-075d (RHEL 6 only)
Supported Hardware Platforms
Cisco VSM Release 7.6.0 runs on the following hardware platforms:
Table 3 Supported Hardware Platforms
Platform Type
Server Models
Installation Method
Physical Server
Cisco Physical Security UCS platform servers:
CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9
Note The CPS-UCS-xRU-K9 servers are available only with Red Hat 6.4 x64 pre-installed. See Red Hat 6.4 Support (64-bit) for more information.
Each server can run one or more services that provide features and functions for the Cisco Video Surveillance system.
Cisco VSM Release 7.6.0 supports the following server services:
Operations Manager—The browser-based Cisco VSM Operations Manager administration and configuration tool. Each deployment requires a single Operations Manager. Two Operations Manager servers can be installed in a redundant configuration.
Media Server—The Cisco Media Server service provides video streaming, recording and storage for the cameras and encoders associated with that server. Media Servers can also be configured for high availability, and provide redundant, failover, and long term storage.
Map Server—Allows Image Layers to be added to location maps and viewed by operators using the Cisco Video Surveillance Safety and Security Desktop application. Map images represent the real-world location of devices and events.
Metadata Server for Motion Analysis—Allows metadata to be added to recorded video, which enables the Video Motion Search in the Cisco SASD desktop application (and for access by 3rd party integrators).
Federator Server—the Federator service is used to monitor video and system health for the cameras and resources of multiple Operations Managers. The Federator interface is accessed using a web browser or the Cisco SASD. Federator desktop application.
Note The Maps, Metadata and Federator server services each require a standalone server in this release. See Table 4 for more information.
Table 4 describes the supported server services and how each is enabled or disabled in this release.
Table 4 Supported Server Services In This Release
Service
Description
Activation Rules
Operations Manager
The browser-based Cisco VSM Operations Manager administration and configuration tool.
Can be added as a stand-alone server, or co-located with other services (such as a Media Server and/or Maps Server).
To Enable:
1. Install the server and complete the Management Console Setup Wizard and select the Operations Manager service.
2. (Optional) Select the Media Server service to create a co-located server. This automatically enable the Media Server service on the default “VSOMServer”.
3. (Optional) Add additional servers to the Operations Manager configuration, and select the Service Type to enable a service on the server.
Note At least one Media Server must be added to the Operations Manager for the system to be functional.
4. Use the Operations Manager to further configure the services and system features.
1. Log in to the Management Console for each server associated with the Operations Manager server and click the Remove button.
Note The Remove button disassociates the server and all server services from the Operations Manager. This allows the server (and running services) to be added and managed by a different Operations Manager.
2. Log in to the Management Console for the Operations Manager server and deselect the Operations Manager service.
Media Server
The Media Server service provides video streaming, recording and storage for the cameras and encoders associated with that server. Media Servers can also be configured for high availability, and provide Redundant, Failover, and Long Term Storage
Can be added as a stand-alone server, or co-located on a single server with the Operations Manager and/or Maps service.
To Enable:
1. Install the server and complete the Management Console Setup Wizard.
2. (Co-located server) Log in to the Operations Manager, select System Settings > Server, and select the default VSOMServer. In the Services section, select the Media Server service.
3. (Stand-alone server) Log in to the Operations Manager and add the server as a Media Server.
4. Select the Media Server Advanced settings to further configure the service, if necessary.
Log in to the Operations Manager, select System Settings > Server, select the server, and deselect the Media Server service.
or
Log in to the Management Console for the server, and click Remove to remove the server from the Operations Manager. Then deselect the service.
Map Server
Allows Image Layers to be added to location maps using the Operations Manager.
Image layers are viewed by operators using the Cisco Video Surveillance Safety and Security Desktop application. Cameras, locations and alerts are displayed on dynamic maps, and map images that represent the real-world location of devices and events.
Use the Operations Manager to activate the service.
Note This service is supported as a stand-alone server on a server running the RHEL 6.4 64 bit OS, or co-located on a Operations Manager server.
To Enable a Stand-Alone Server:
1. Install the server and complete the Management Console Setup Wizard.
2. Log in to the Operations Manager and add the server as a Maps Server.
3. Configure the Location Maps.
To Enable a Co-Located Maps Server:
1. Log in to the Operations Manager.
2. Navigate to the Operations Manager server configuration page. See
3. Select the Maps Server to enable the service on the Operations Manager server.
If the Operations Manager is not co-located with the Maps Server, log in to the Management Console for the server, click Remove to remove the server from the Operations Manager, and then deselect the service.
If the Operations Manager is co-located with the Maps Server, log in to the Operations Manager and deselect the Media Server service.
Image Layer Considerations
Images used for map layers should be optimized to the smallest file size that preserves image quality. Large image files can consume excessive processing power and degrade system performance. For details, refer to the Cisco Video Surveillance Operations Manager User Guide (“Configuring Location Maps” requirements section).
Metadata Server
Allows metadata to be added to recorded video, which enables features such as Video Motion Search in the Cisco SASD desktop application.
Metadata can also be accessed by 3rd party integrators for advanced analytics analysis.
Use the Operations Manager to activate the service.
Note This service is supported as a stand-alone server only, on a server running the RHEL 6.4 64 bit OS.
To Enable:
1. Install the server and complete the Management Console Setup Wizard.
2. Log in to the Operations Manager and add the server as a Metadata Server.
Use the Operations Manager to deactivate the service on the server.
or
Use the Management Console to Remove the server from the Operations Manager, and then deselect the service.
Metadata Server Considerations
Video motion analysis is supported for the primary stream only in this release. JPEG recordings are not supported.
Only one request per camera to generate the luminance metadata is supported by the Metadata server. The second request to generate luminance metadata for the same camera will fail while the previous request is still being processed.
The Metadata server will execute only five parallel request for luminance metadata, remaining requests will be queued and executed in the order they were requested.
VSF
Enables the Federator service used to monitor video and system health for the cameras and resources of multiple Operations Managers. The Federator service can only be enabled on a stand-alone server in this release. Other server services cannot be enabled on the same server as the Federator service. The Federator interface is accessed using a web browser or the Cisco SASD. Federator.
Activated using the Management Console only. Cannot be activated using the Operations Manager.
Note This service is supported as a stand-alone server only, on a server running the RHEL 6.4 64 bit OS.
To Enable:
1. Log in to the Management Console.
2. Install the server and complete the Setup Wizard: select the VSF service.
3. Log in to the Cisco VSM Federator browser-based interface.
4. Continue to the “Using Federator to Monitor Multiple Operations Managers” section.
Table 5 provides information about Cisco devices supported in this release:
Table 5 Supported Devices: Cisco
Medianet. Support
Model
FW Version for Release 7.6 Compatibility
Video Format
Media Types
Audio
Dual Stream
Motion Detection
Firmware Upgrade
Privacy Mask
Edge Storage
Camera App Support
Phase 1
Phase 2
Phase 3
(requires firmware 2.0.0-175)
2400 Series
2.5.2.2
NTSC / PAL
MPEG-4 MJPEG
NA
Yes
Yes
Yes
No
No
No
No
No
No
2500 Series
2.5.2.2
NTSC / PAL
MPEG-4 MJPEG
Yes
Yes
Yes
Yes
No
No
No
No
No
No
2600 Series
4.4.2
NTSC / PAL
H.264 MPEG-4 MJPEG
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
2830
2.5.0-10
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
2835
2.5.0-10
PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
2900 Series
1.6.18
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
No
No
No
No
No
3421V
2.5.0-10
NTSC / PAL
H.264 MJPEG
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
3520
2.5.0-10
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
3530
2.5.0-10
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
3535
2.5.0-10
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
4300
2.4.2-289
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
4300E
3.2.3-218
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
4500
2.4.2-289
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
4500E
3.2.3-218
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
5000 Series
1.6.17
NTSC
H.264 MJPEG
NA
Yes
Yes
Yes
No
Yes
No
No
No
No
6000P
2.5.0-10
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
6020
2.5.0-10
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
6030
2.5.0-10
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
6050
2.5.0-10
NTSC / PAL
H.264
MJPEG
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
6400
2.5.0-10
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
6400E
2.5.0-10
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
6500PD
2.3.2-8
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
6930
2.5.0-10
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
7030
2.5.0-10
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
7030E
2.5.0-10
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
7530PD
2.3.2-8
NTSC / PAL
H.264
MJPEG
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
CIVS-SENC-4P
(encoder)
V1.2.0-4
NTSC / PAL
H.264 MPEG-4 MJPEG
Yes
Yes
Yes
Yes
No
No
No
No
No
No
CIVS-SENC-8P
(encoder)
V1.2.0-4
NTSC / PAL
H.264 MPEG-4 MJPEG
Yes
NA
Yes
Yes
No
No
No
No
No
No
Additional Notes on Cisco Devices
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 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 Cisco VSM. These values can only be changed using the camera web interfaces.
Focus, Auto Focus and Zoom support are not available for Cisco 6000P, 3421V, 3520, 3530, 3535 camera models.
When Cisco 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.
Cisco 3421V and 6050 cameras does not support Contact Closure, Cisco 7030 camera supports 3 input ports. All other Cisco 3000, 6000 series cameras support 1 input port.
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.
The minimum firmware version required to support camera applications is 2.5.0-10.
The minimum firmware version required to support connected edge storage is 2.0.
Supported Devices: Arecont
Table 6 provides information about Arecont devices that this Cisco VSM release supports.
Table 6 Supported Arecont Cameras
Model
Type
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
65220
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
65187
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
Additional Notes on Arecont Devices
AV20185, AV20365, AV12186, AV8365 and AV8185 are 4-channel IP cameras. In order to support multiple video channels from a single device, Cisco VSM 7 models these devices as “Encoders”.
Arecont devices have not yet been qualified to support redundancy in Cisco 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 Cisco VSM or Arecont Camera Web Interface or a third party Media Player.
Supported Devices: Axis
Table 7 provides information about Axis devices that this Cisco VSM release supports.
Table 7 Supported Axis Devices
Model
Type
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
243SA
Encoder
4.45
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
243QBlade
Encoder
4.46.1
NTSC / PAL
MPEG-4 MJPEG
NA
Yes
Yes
Yes
Yes
247S
Encoder
4.42
NTSC / PAL
MPEG-4 MJPEG
Yes
Yes
Yes
Yes
Yes
M3006
IP Camera
5.55.1.2
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
M3007
Panoramic Camera
5.40.13.2
NTSC
H.264 MJPEG
No
Yes
Yes
Yes
Yes
P1214
IP Camera
5.40.12.3
NTSC
H.264 MJPEG
No
Yes
Yes
Yes
Yes
P1353
IP Camera
5.40.19.1
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
P3301
IP Camera
5.40.92
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
P3364
IP Camera
5.40.17.1
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
P3367
IP Camera
5.50.3
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
P3915
IP Camera
5.55.3
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
P7214
Encoder
5.50.2
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Q1604
IP Camera
5.50.3
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Q6045
IP Camera
5.55.11
NTSC
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Q7401
Encoder
5.50.2
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
N/A
Yes
Yes
Yes
Yes
Q7424
Encoder
5.40.10
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
Yes
Additional Notes on Axis Devices
Axis P3301 IP camera and Q7401, Q7404, and Q7406 encoders have been qualified to support redundancy in Cisco VSM 7.0.1.
Axis 233D supports contact closure configuration and events.
Support for 0.1fps MJPEG stream for all supported Axis models.
The following table documents the various Field-Of-Views supported for the Axis M3007 panoramic cameras and support for PTZ and Motion Detection for these Field-Of-Views.
Table 8 Axis M3007 Options
Model
Field Of View
PTZ
Motion Detection
Axis M3007
360 degree view
No
Yes
Panoramic view (180 degree view)
No
No
Double Panoramic view(2 panoramic view of 180 degree)
No
No
Quad view (view area 1,2,3,4)
No
No
View Area 1
Yes
No
View Area 2
Yes
No
View Area 3
Yes
No
View Area 4
Yes
No
The Axis M3007 camera allows the user to configure various mounting options directly in the camera web interface that affects the possible values for Field-Of-Views that can be configured on the camera. The table below provides this mapping:
Table 9 Axis M3007 Field-Of-View Options
Field of View /
Mount Point
Wall
Ceiling
Desktop
360 Degree View
Yes
Yes
Yes
Panoramic View
Yes
Yes
Yes
Double Panoramic View
No
Yes
Yes
Quad View
No
Yes
Yes
View Area 1/2/3/4
Yes
Yes
Yes
Supported Devices: IQinVision
Table 10 provides information about IQinVision devices that this Cisco VSM release supports.
Table 10 Supported IQinVision Devices
Model
Type
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
Yes
IQM32NE-B5
IP Camera
V3.4/5
NTSC
H.264
No
No
No
Yes
Yes
IqeyeA35N
IP Camera
V3.4/5
NTSC
H264
No
No
No
Yes
Yes
Iqeye765N
IP Camera
V3.4/5
NTSC
H264
No
No
No
Yes
Yes
Iqeye755
IP Camera
V3.1/2
NTSC
MJPEG
No
No
No
Yes
Yes
Additional Notes on IQinVision Devices
IQinVision devices have not yet been qualified to support redundancy in Cisco VSM 7.
Support configuring NTP on the IQinVision cameras to synchronize with their Cisco VSM Media Server.
Added support for Firmware upgrade for all supported models.
Added support for Camera Discovery for H.264 models.
Supported Devices: Mobotix
Table 11 provides information about Mobotix devices that this Cisco VSM release supports.
Table 11 Supported Mobotix Devices
Model
Type
Supported FW Version
Video Format
Media Types
Audio
Dual Stream
Motion Detection
Firmware Upgrade
x10
IP Camera
M10 v.2.0
NTSC
MPEG-4 MJPEG
No
No
No
No
Additional Notes on Mobotix Devices
Moboitx M10 and D10 IP cameras running with M10 series firmware work with the x10 Model.
Mobotix devices are not qualified to support redundancy in Cisco VSM 7.
Supported Devices: Panasonic
Table 12 provides information about Panasonic devices that this Cisco VSM release supports.
Table 12 Supported Panasonic Devices
Model
Type
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
SW 458
Panoramic Camera
1.42
NTSC
H.264, MJPEG
No
Yes
Yes
No
SF 438
Panoramic Camera
1.42
NTSC
H.264, MJPEG
No
Yes
Yes
No
NF 302
IP Camera
1.64E0_1.06
NTSC
MPEG-4 MJPEG
No
No
Yes
No
Additional Notes on Panasonic Devices
Panasonic devices have not yet been qualified to support redundancy in Cisco VSM 7.
Only same field of views can be configured on primary and secondary streams on Panasonic cameras SW458/SF438.
The following table documents the various Field-Of-Views supported for the Panasonic SF 458 and SF 438 panoramic cameras and support for PTZ and Motion Detection for these Field-Of-Views.
Table 13 Panasonic SF 458 and SF 438 Field-Of-Views Support
Model
Field Of View
PTZ
Motion Detection
Panasonic SW458 and SF438
Fisheye 360 degree view
No
Yes
Double Panorama view(2 panoramic view of 180 degree)
No
Yes
Panorama view (180 degree view)
No
Yes
Quad view
No
No
Single view
Only with View Area 1
No
Supported Devices: Pelco
Table 14 provides information about Pelco devices that this release supports.
Table 14 Supported Pelco Devices
Model
Type
Supported FW Version
Video Formats
Media Types
Audio
Dual Stream
Motion Detection
Firmware Upgrade
Pelco ExSite
IP Camera
TXB-N-1.9.2.12-20131118-1.2084-O1.10263
NTSC, PAL
H.264, MJPEG
No
Yes
Yes
Yes
Pelco Spectra IV TXB IP (MPEG4)
IP Camera
01.02.0018
NTSC
MPEG4, MJPEG
No
Yes
No
No
Pelco NET5404T
Encoder
1.8.2.18-20121109-1.3081-O3.8503
NTSC, PAL
H.264, MJPEG
Yes
Yes
Yes
No
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 Cisco VSM 7.
Audio volume controls are not supported for NET540XT
For Pelco NET540xT PTZ to work, the analog camera should be chosen as Pelco Analog Camera (pelco_sarix) in Operations Manager and not as Pelco D.
The user needs to directly configure the Serial protocol on the Pelco NET540XT encoder outside of Cisco VSM.
The Pelco Spectra IV TXB-N (H.264 capable model) run Pelco Sarix firmware and can be supported in Cisco VSM as a Pelco Sarix Generic IP camera (additional details in the Generic IP camera section).
Supported Devices: Sony
Table 15 provides information about Sony devices that this release supports.
Table 15 Supported Sony Devices
Model
Type
Supported FW Version
Video Formats
Media Types
Audio
Dual Stream
Motion Detection
Firmware Upgrade
HM662
Panoramic Camera
1.1.1
NTSC / PAL
H.264 MJPEG
No
Yes
No
No
RX 530
IP Camera
3.154
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
Additional Notes on Sony Devices
Sony devices have not yet been qualified to support redundancy in Cisco 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 is opened in the camera’s web interface.
For Sony HM662 Panoramic camera, only the 360 degree view is supported. De-warped views are not supported.
Supported Devices: Generic IP Cameras
Cisco VSM Release 7.6.0 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 Cisco 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 16 Supported Generic Devices
Type
Supported 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
Generic Axis
3.0 / Firmware 5.x
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
Generic Axis
2.0 / Firmware 4.3
NTSC / PAL
MPEG4 MJPEG
Yes
Yes
Yes
Yes
No
Arecont
Arecont Non Panoramic Models
NTSC
H.264 MJPEG
No
Yes
No
Yes
No
IQEye JPEG
V3.1/2
NTSC
MJPEG
No
No
No
Yes
Yes
IQEye H264
V3.4/5
NTSC
H264 MJPEG
No
Yes
No
Yes
Yes
Mobotix
MX Series
NTSC / PAL
MJPEG
No
No
No
Yes
No
Panasonic
-
NTSC / PAL
H.264 MPEG-4MJPEG
No
Yes
Yes
Yes
No
Pelco Sarix
Only IP cameras with Sarix Firmware
NTSC / PAL
H.264 MJPEG
No
Yes
Yes
Yes
No
Sony
6th Generation IP cameras
VMxxx and
VBxxx
NTSC / PAL
H.264 MJPEG
Yes
Yes
No
No
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 version 3.0 capable devices. There are other 4:3 and 16:9 aspect ratio resolutions that are also supported for these devices.
Axis VAPIX 3.0 cameras running firmware version 5.4 or higher support the connected edge storage feature.
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 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.
Some Axis cameras require a special ONVIF user account, which can be created on the camera's web interface before adding an AXIS ONVIF camera to the Operations Manager. This page is at Setup --> System Options --> Security --> ONVIF --> Add
ONVIF camera and VSMS server to which ONVIF camera is being added should have their time synchronized ideally using NTP.
For Sony models, only UDP is supported. Streaming fails if TCP is selected.
For Bosch models, a frame rate of 30 alone is supported, and dual streaming is not supported.
For some Hikvision models, the camera requires a reboot after the codec is changed from Cisco 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 Mobotix Generic Devices
For M12 cameras, if the NTP server on the camera is not configured successfully, motion detection does not work reliably.
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.
We have added support for ‘move command’ and ‘continuous PTZ command’ depending upon whatever supported by the Sony camera. If both supported, ‘continuous PTZ command’ is chosen for PTZ operations. When using a mouse for models that only support ‘move command’, PTZ will require the user to continuously move the mouse for the camera to pan. PTZ behavior with a joystick is closer to other models supporting ‘continuous PTZ’ commands.
Sony 6th generation cameras have a separate have a separate driver and need to added as 6th generation in Cisco VSM. Note that current Sony 6th generation model numbers start with like VM6XX or VB6XX.
Supported Devices: Analog Cameras
This Cisco VSM release provides support for the following analog cameras.
Table 17 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
Pelco Analog Camera
NTSC / PAL
Encoder Dependent (for use with only PelcoNET540xT encoders)
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.
Device Models Validated in Cisco VSM as Generic IP Cameras
Following camera models have been tested as generic IP cameras.
Table 18 Supported Generic IP Cameras
Camera Model
Generic IP Camera Type
Validated Firmware Version
Video Formats
Media Types
Audio
Dual Stream
PTZ
Motion Detection
Firmware Upgrade
Axis 6034-E
ONVIF 2.0
5.41.1.2
NTSC
H.264 MJPEG
Yes
Yes
Yes
No
No
Samsung SND-7080
ONVIF 2.0
2.00_121004
NTSC
H264 MJPEG
No
Yes
No
No
No
Sony CH240
ONVIF 2.0
1.79.00
NTSC
H264 MJPEG
Yes
Yes
No
No
No
Panasonic SW458
ONVIF 2.0
1.42
NTSC
H264 MJPEG
Yes
Yes
No
No
No
Axis 3301
Axis VAPIX 3.0/Firmware 5.x
5.41.2
NTSC / PAL
H264 MJPEG
Yes
Yes
Yes
Yes
No
Axis 3367
Axis VAPIX 3.0/Firmware 5.x
5.50.3
NTSC / PAL
H264 MJPEG
Yes
Yes
Yes
Yes
No
Axis Q6034
Axis VAPIX 3.0/Firmware 5.x
5.41.1.2
NTSC / PAL
H264 MJPEG
Yes
Yes
Yes
Yes
No
Axis 215
Axis VAPIX 2.0 /Firmware 4.3
4.48.4
NTSC / PAL
MPEG4 MJPEG
Yes
Yes
Yes
Yes
No
Arecont AV3115
Arecont
65218
NTSC / PAL
H.264
No
Yes
No
Yes
No
Arecont AV1355
Arecont
65151
NTSC / PAL
H.264
No
Yes
No
Yes
No
IQinVision IQ755
IQEye JPEG
V3.1/2
NTSC
MJPEG
No
No
No
Yes
Yes
IQinVision IQA35N
IQEye H264
V3.4/6
NTSC
H264 MJPEG
No
Yes
No
Yes
Yes
Panasonic NP-502S
Panasonic
1.81
NTSC/ PAL
H.264 MPEG-4 MJPEG
No
Yes
Yes
Yes
No
Panasonic SW458
Panasonic
1.42
NTSC/ PAL
H.264 MJPEG
No
Yes
Yes
Yes
No
Pelco IDS0DN-ADAURX7
Pelco
1.8.2.20-20130211-2.9110-03.9240
NTSC
H264 MJPEG
No
Yes
No
Yes
No
Sony VM 631
Sony 6th Generation IP cameras VMxxx and VBxxx
1.3.0
NTSC/ PAL
H.264 MJPEG
Yes
Yes
No
No
No
Sony CH 240
Sony 2nd, 3rd, 4th and 5th generation Sony IP cameras
1.79.00
NTSC/ PAL
H.264 MPEG-4 MJPEG
Yes
Yes
Yes
Yes
No
Clipping Support By Application
You can create and view video clips using the following Cisco VSM applications:
1.MP4 clips are saved to the server and play immediately after being downloaded to the monitoring PC. Third-party video players (such as VLC) can also be used to view MP4 clips.
2.Create MP4 clips using the Federator Thumbnail Search.
3.Federator clips must be downloaded and played using either Cisco Review Player or VLC.
4.Double click the virtual clip in Federator Clip Search to play the virtual clip.
6.Cisco SASD does not support Virtual Clip search in this release.
7.Create MP4 clips using the Federator Thumbnail Search.
8.Federator clips must be downloaded and played using either Cisco Review Player or VLC.
9.Cisco SASD Federator supports MP4 clips only in this release (virtual clip search is not supported).
10.CVA files can only be opened in applications that support the CVA format (such as the Cisco Review Player).
Note When converting a virtual clip to an MP4 file, only the entire duration of the virtual clip can be saved, not a segment.
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 20 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 20 License Part Numbers
Part
Description
Physical Server Licenses (for Server Services)
FL-CPS-MS-SW7
License for 1 Media Server on a physical server (Cisco UCS or MSP)
FL-CPS-OM-SW7
License for 1 Operations Manager on a physical server (Cisco UCS or MSP)
L-CPS-MS-SW7=
eDelivery license for 1 Media Server on a physical server (Cisco UCS or MSP)
Virtual Machine (VM) Licenses (for Server Services)
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
Cisco VSM Federator Licenses
L-CPS-VSM7-FD=
eDelivery license for one base Cisco VSM 7 Federator
L-CPS-FD-VSOM=
eDelivery license for one Operations Manager in Federator
L-CPS-FD-VSOM-X=
eDelivery license for one Operations Manager Express in Federator
Cisco SASD Licenses
L-CPS-SASD-7=
eDelivery license for 1 SASD with Cisco VSM 7
Camera Licenses
L-CPS-VSM7-1CAM=
eDelivery license for 1 camera connection with Cisco VSM 7
Camera App Licenses
Note The following licenses are used when managing Camera Apps using Cisco VSM Operations Manager. These licenses are different than those used when installing and managing the Camera Apps directly on the device (using the device UI).
L-FL-AA-CA-VSM=
Car Alarm Detection Application for Cisco IP Cameras for VSM
L-FL-AA-GB-VSM=
Glass Break Detection App for Cisco IP Cameras for VSM
L-FL-AA-GS-VSM=
Gun Shot Detection Application for Cisco IP Cameras for VSM
L-FL-C-AP1-VSM=
Tier 1 Cisco Application for Cisco IP Cameras for VSM
L-FL-C-AP2-VSM=
Tier 2 Cisco Application for Cisco IP Cameras for VSM
L-FL-IVVA-T1-VSM=
Tier 1 Cisco IP Camera Intuvision Video Analytic App for VSM
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).
You can add 1 Media Server and 10 non-Cisco cameras without a license for initial setup purposes only. This feature is removed when you add any permanent license.
Procedure
Step 1 Purchase additional licenses:
a. Determine the part number for the license you want to purchase (see Table 20).
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 Cisco 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.
Table 21 describes the different types of software and firmware that are installed on servers, cameras, and encoders.
Table 21 Cisco VSM Software Types
Software Type
Description
System software
System software denotes the Cisco 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.
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.
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.
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”sectionof 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.
Language Packs
Language packs can be added to display the Cisco VSM user interfaces in non-English languages.
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:
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.