PDF(1.0 MB) View with Adobe Reader on a variety of devices
Updated:January 21, 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.
A new setting was added to allow cameras with duplicate IP addresses to be added to the Cisco VSM Operations Manager configuration.
Duplicate IP addresses may be required in deployments with multiple sites. The IP cameras at each site may use the same pool of IP addresses as the cameras at another site.
To enable duplicate addresses:
1. Log in to the Operations Manager browser-based interface.
2. Go to the System Settings > Settings page.
3. Select Allow Duplicate IP.
Note This option is deselected (disabled) by default. If Allow Duplicate IP is deselected, and a camera is added with same IP address as an existing camera, the new camera will display an ID collision issue. Cameras manually added will be placed in the Enabled: Critical state. Discovered cameras will be placed in the Pending Approval list. See the Cisco Video Surveillance Operations Manager User Guide for more information.
Cisco VSM Federator is a new application that allows users to monitor video and system health from up to 500 Operations Managers (Cisco VSM Operations Manager instances).
In this release, VSM adds support for the following map services.
Geographic map images are provided using Map Service Providers such as Google, Bing or OpenStreetMap.
Building maps are supported by installing and configuring an optional Map Server to the Operations Manager configuration. The Map Server is used to display building maps as layers over the geographic map. GIS coordinates can be assigned to the cameras to accurately place them on the maps. The Operations Manager is used to add and edit the maps and map images, including placing building maps and cameras on the map. See the “Supported Server Services” section for more information.
The following table describes the different parts of the solution and guidance on their use.
Table 1 Map Solutions
Map Component
Description
Map Services Providers
To use Geographic maps (streets and geographic features), you must configure the Operations Manager to use a Map Service Provider such as OpenStreetMap, Bing, Google etc. To use a Map Service Provider you must have network access to the Service Providers. Cameras can be placed directly on the Geographic map if building map images are not used. In this case, there is no need to deploy the Map Server for building maps and additional map layers.
Building Maps and Map Server
If building maps are needed, you must deploy and configure the Map Server with VSM 7.5 or higher. The map server supports adding additional layers to the map display and cameras can also be placed on these layers. The layers can be images of anything such as building floor plans, campus maps, or specialized map images for a deployment. For multi-floor buildings, layers can be placed on top of one another. Building maps can also be associated with Locations in the location hierarchy in the Operations Manager.
When this is done, selecting the location in the map display in the Cisco SASD hierarchy will cause the map to center on that location and display the building map. When a Map Service Provider has been selected for Geographic maps, the building maps will be displayed on top of them.
You cannot use an external Map Service Provider for Geographic maps if there is no external network access.
However, you can still use building map images if the Map Server has been deployed. There is no display of the Geographic maps under the building maps, but the building maps can still be used and cameras placed on them.
This release adds support for metadata recording and streaming, which can be used by external video analytics systems to record and search video analytics metadata.
APIs are available for integration with 3rd party video analytics software. API support is available through Cisco DevNet ( http://developer.cisco.com/)
Cisco Video Surveillance Safety and Security Desktop (Cisco SASD) includes significant updates for this release including performance improvements, a new visual design, new features and new applications.
The Cisco SASD Video, Alert and Video Wall workspaces found in previous releases are included.
The Map workspace has been updated to display GIS maps.
Map editing is now performed in Operations Manager.
A new application Cisco SASD Advanced Video Player provides the Video and Video Wall workspaces only. It is intended for operational users that need only video viewing features.
Video Motion Search
Cisco SASD adds a new feature for searching for motion in previously recorded video. The feature uses the new video metadata capability to generate and record motion metadata for a video segment. The user can then define and perform multiple searches of this metadata to locate motion based on different search criteria. Results are returned in a video thumbnail display.
Cisco SASD Federator is a new application for use with Operations Manager Federator (Federator allows users to monitor video and system health from multiple Operations Managers).
Cisco SASD Federator supports many of the same features of Cisco SASD, including the Video, Alerts, and Thumbnail Search workspaces. Cisco SASD Federator also supports video clipping and clip management.
Dynamic Proxy is a new feature that replaces the proxy-to-proxy function present in Cisco VSM 6.X.
Dynamic Proxy allows users to access video streams from remote sites that have limited outbound bandwidth. The video can be delivered to multiple users without placing additional load on the remote site.
This is particularly useful for distributed deployments organized as remote and central sites. Dynamic Proxy provides the concept of “Sites” with users that are inside and outside the site. Access by these users is managed dynamically so that video is either streamed directly from a media server hosting a camera without any bandwidth limitations, or through a Media Server that is used to share access and limit bandwidth over a network link between a remote and central site.
Connected Edge Storage
Cisco VSM Release 7.5 (or higher) and Cisco 3000/6000/7000 series cameras with firmware release 2.0 support recording on the camera. Recordings are later copied to the Media Server manually or automatically. This feature is known as “Connected Edge Storage”.
Camera storage is supported by specific Cisco and Axis camera models, and with 8GB, 16GB and 32GB SD cards. Consult the camera documentation for recommendations on SD cards and expected lifetimes.
When Connected Edge Storage is enabled, video is recorded on the camera continuously.
“Auto-Merge recordings”—Automatically copies video data to fill recording gaps in the Media Server archive after a network outage or Media Server downtime.
Manual Copy—Manual copying can be done from the Operations Manager GUI or by an external application using Cisco VSM APIs.
Cisco 3000/6000/7000 series cameras with firmware release 2.0 add support for in-camera “Apps”. Camera applications can be uploaded and installed in the camera to add new functions that integrate with Cisco VSM Release 7.5 or higher. Events and Alerts are sent from the “Apps” to Cisco VSM where they can be displayed and used to trigger actions.
Virtual Clipping
Cisco VSM Release 7.5 adds support for creating virtual clips,. Virtual clips include a time range for longer retention. Operations Manager allows you to search for virtual clips, play them and converting them to.mp4 clips. See the “Clipping Support By Application” section for more information.
Clipping Enhancements
Cisco VSM Release 7.5 improves the user interface and features for creating clips. Multiple clips can be processed at the same time and a clip management screen (Clip Search) is included in the Operations Manager and Cisco SASD for viewing the status of clips that are underway, searching for clips, and viewing clips.
Cisco VSM Release 7.5 adds new capabilities for centrally managing a Cisco VSM deployment using the Operations Manager. This includes Software Management for VSM servers, management of new Release 7.5 server services (such as Maps and Metadata), and backups of multiple servers. A Media Server backup configuration can also be applied to multiple servers at once (using Bulk Actions).
Multiple Browsers and Platforms
Cisco VSM Release 7.5 supports basic live video display using the Chrome and Firefox web browsers on Windows and Linux workstations. The Chrome, Firefox and Safari browsers are supported on Mac workstations.
This browser support is in “Beta” for Release 7.5 to gather feedback on the platforms and browsers that are most important to users.
Cisco VSM Release 7.5 adds a Privacy Mask feature for the Health Care market. When enabled using the video client UI, all live video from a camera is blocked and cannot be viewed by any operator or monitor, or recorded by the Cisco Video Surveillance system. This feature is typically used with the “Virtual Sitter” feature for health care providers, allowing operators to temporarily block video from a Cisco Video Surveillance camera when the patient requires privacy. A timer feature is included to remind the operator to enable the video again when needed.
Several models of panoramic cameras are supported is this release. Camera templates add the ability to select which particular panoramic viewing mode should be used with the cameras.
This release supports a dual-login feature for extra security.
Dual Login requires that a second user (such as a manager) enter their credentials to approve a user’s access. When the user logs in, a second prompt appears for the manager’s credentials. This optional feature can be used when explicit approval is required whenever a user logs in.
Red Hat 6.4 Support (64-bit)
Cisco VSM Release 7.5 is available with Red Hat 6.4 x64 (a 64-bit version of Red Hat Linux) on pre-installed CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9 servers.
This allows a larger maximum storage partition size for video in Cisco VSM Release 7.5:
Cisco VSM Release 7.5.2 is being delivered for the following:
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.
As upgrades of Cisco VSM 7.0, 7.0.1, and 7.2.x and 7.5.0 deployed in VMs and on Cisco Video Surveillance servers. Servers include the Cisco Multiservices Platform (Cisco MSP) and the Cisco Connected Safety and Security UCS Platform Series servers.
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 Connected Safety and Security UCS Platform Series Servers (Release 7.2 and Higher)
Cisco VSM Release 7.5.2 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 7.5 software installed.
Previous Cisco VSM releases can be upgraded using the Release 7.5.2 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.
The upgrade is performed using the browser-based Cisco VSM Management Console, and should not be performed using the Linux CLI.
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.
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 roo t
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 7.5.1—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, and then upgrade the system to Release 7.5.2:
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.
3. Upgrade all physical and virtual Cisco VSM servers to Release 7.5.2 using the Cisco VSM Management Console.
Contact your Cisco representative for more information.
Scheduled Recording Stops With Periods of No Recording
Cameras will stop recording video at 4 am if:
A template is configured with a time period that is configured as
No Recording, and
A camera is assigned to the template during the scheduled no recording period.
If this occurs, recording will stop at 4 am until the next scheduled recording period.
To avoid this issue:
Do not configure templates with
No Recording periods. Use only schedules that include time periods where recording should occur.
For example, a template can include a schedule that has time periods for Weekdays (8 am to 5 pm), and Weekends (6 am to 11 pm). Define the continuous or motion recording that should occur during these times. Recording will not occur outside of the scheduled time periods.
or
If a template includes a
No Recording time period, add new or existing cameras to the template at a time that is outside the “no recording” period.
For example, if a template includes a schedule from 8 pm to 1 am that is configured for no recording, add new or existing cameras to the template outside this time (such as 7 pm or 2 am). If you add a camera to this template within the “no recoding” period, such as at 9 pm, then the camera recordings will stop at 4 am every day until the next configured recording period.
See Cisco VSM Release 7.5.1 caveat CSCup55776 for more information.
Video Wall Configuration After Upgrading to Release 7.5 from 7.2
Unattended Mode client configurations created in the Release 7.2 Cisco SASD do not apply to the new Release 7.5 (or higher) SASD Wall. After upgrading the Cisco SASD software on a client PC that was running SASD Unattended Mode, you must use the Cisco SASD Wall Configurator to setup the displays (by reconfiguring the Video Walls used with VSM Release 7.2).
When upgrading to Release 7.5 from Release 7.2 or lower, you must migrate the map images from the previous system and reconfigure the map image layers. The Cisco VSM mapping system has been replaced with GIS map support which is not compatible with the earlier map support. Accessing cameras on maps now requires the use of a Cisco VSM Map Server.
When a Cisco VSM deployment is upgraded to a release prior to Release 7.5, a.zip file is created on the Operations Manager that contains all of the map images previously added (using Cisco SASD).
Directory— /usr/BWhttpd/vsom_be/images/
Filename— mapsFromOldVersion.zip
Note The image filename format is <locationName>.<file extension>. Cisco VSM does not store the original image filenames.
Note This procedure is necessary only for upgrades from a release prior to 7.5. For upgrades from Release 7.5 or higher, the map image migration is automatic.
Procedure
Step 1 Complete the upgrade to Cisco VSM Release 7.5 or higher.
Step 2 Use a file utility (such as WinSCP) to manually copy the /usr/BWhttpd/vsom_be/images/mapsFromOldVersion.zip file from the Operations Manager server to a monitoring workstation.
Important Performance Considerations with Connected Edge Storage
Number of Supported Cameras
Due to bandwidth considerations, the number of cameras that can be supported by a Media Server will drop in half when all of the cameras on that server are configured with the “Auto-Merge recordings” option. We recommended a maximum of 10 cameras on a single Media Server be configured with “Auto-Merge recordings”. See the Cisco Video Surveillance Operations Manager User Guide for more information and configuration instructions.
Note ● Cisco VSM Release 7.5 can support up to 100 cameras configured with “Auto-Merge recordings” on a single Media Server depending on the model of server and video data rate.
See the “Auto-Merge Calculator” tool for guidance on using “Auto-Merge recordings” with more than 10 cameras on a single Media Server (to download the tool, go to the Cisco Video Surveillance Manager download page, select “Video Surveillance Manager Stand-alone Tools”, and download the “Auto-Merge Calculator” tool).
For cameras with camera storage configured with Manual Copy, there is no limit to the number of cameras on a single Media Server imposed by camera storage. The normal limits of 250 cameras and limits on recording bandwidth depending on video configurations of the cameras and server type still apply.
For example, when a camera configured with “Auto-Merge recordings” reconnects to the Media Server after a network outage, live video recording will resume and the camera will begin copying locally-stored video to the Media Server (to fill the recording gaps on the Media Server). Video is also copied from the camera at a rate that is at least 25% faster than real-time so that all of the video from an outage is copied from the camera before it is overwritten. This means that after an outage, the total bandwidth from the camera to the Media Sever is more than 2X the video data rate until all of the video from the outage has been copied from the camera. Since the Media Server has a limit on total recording bandwidth, the use of “Auto-Merge recordings” will reduce the total number of cameras that can be supported on a Media Server. If all of the cameras on the Media Server are configured with “Auto-Merge recordings”, the number of supported cameras will drop by more than half.
Example Video and SD Card Configurations
The following tables show examples of video configurations and SD card sizes for 1RU and 2RU servers, and the maximum outage that can be supported by the “Auto-Merge Recordings” feature. If the outage exceeds the maximum, recorded video in the camera from the outage period will be lost.
Table 2 Video Configurations and SD Card Sizes: 1RU Servers
CPS-UCS-1RU and CPS-MSP-1RU Servers
Video and SD Card Configuration
Standard Cameras
Auto-Merge Cameras
Max Outage Duration (Hours)
6 Mbps 30 FPS 32GB SD Card
0
4
11.00
6 Mbps 30 FPS 16GB SD Card
0
4
5.00
6 Mbps 30 FPS 8GB SD Card
0
4
2.00
4Mbps 30 FPS 32GB SD Card
0
6
16.50
4Mbps 30 FPS 16GB SD Card
0
6
8.00
4Mbps 30 FPS 8GB SD Card
0
6
3.50
2Mbps 30 FPS 32GB SD Card
5
10
23.50
2Mbps 30 FPS 16GB SD Card
5
10
16.00
2Mbps 30 FPS 8GB SD Card
5
10
7.50
1Mbps 15FPS 32GB SD Card
20
10
23.50
1Mbps 15FPS 16GB SD Card
20
10
23.50
1Mbps 15FPS 8GB SD Card
20
10
15.00
Table 3 Video Configurations and SD Card Sizes: 2RU Servers
CPS-UCS-2RU, CPS-MSP-2RU, UCS B,C Series Servers
Video and SD Card Configuration
Standard Cameras
Auto-merge
Cameras
Max Outage Duration (Hours)
6 Mbps 30 FPS 32GB SD Card
10
10
11.00
6 Mbps 30 FPS 16GB SD Card
10
10
5.00
6 Mbps 30 FPS 8GB SD Card
10
10
2.00
4Mbps 30 FPS 32GB SD Card
25
10
16.50
4Mbps 30 FPS 16GB SD Card
25
10
8.00
4Mbps 30 FPS 8GB SD Card
25
10
3.50
2Mbps 30 FPS 32GB SD Card
75
10
23.50
2Mbps 30 FPS 16GB SD Card
75
10
16.00
2Mbps 30 FPS 8GB SD Card
75
10
7.50
1Mbps 15FPS 32GB SD Card
175
10
23.50
1Mbps 15FPS 16GB SD Card
175
10
23.50
1Mbps 15FPS 8GB SD Card
175
10
15.00
Additional Limitations
MJPEG streams are not supported with the Connected Edge Storage feature.
The maximum supported video bit rate for camera storage is 6Mbps.
For Auto-Merge recordings, only video recorded in the last 24 hours can be auto-merged.
When camera storage is used, the camera reserves 1GB of space on the SD card for buffering and it is not available for video recording. For example, only 15 GB is available on a 16GB SD card.
Browser and Platform Support: Release 7.5.0 to 7.5.2
VSM 7.5 provides basic live video display through the following:
Internet Explorer, Chrome and Firefox on Windows
Chrome and Safari on the Mac
This feature is in “Beta” for this release in order to get feedback on which platforms and browsers are most important to our users. It is intended for casual video viewing such as verifying a video configuration on a camera and occasional access from systems that do not have one of the SASD applications installed. It is not intended for critical operational use and is not recommended that Chrome, Firefox or Safari browsers be left running for long periods of time when displaying video from VSM 7.5. Only live video is supported in this release and the VLC Plugin is used for video display. VLC may not be able to display some cameras including some with multi-megapixel resolutions and some MPEG-4 streams.
Supported Browsers
Table 4 Supported Browsers in Release 7.5.0 to 7.5.2
Platform
Supported OS
Supported Browser
Mac OS
OS X 10.8 and later
Safari 7.0.1 and later
Chrome 32.0 to 44
Windows
Windows 7 and 8
Internet Explorer (IE) 10 and 11
Internet Explorer (IE) 9 (VSM 7.5.0 and 7.5.1 only)
Firefox 20.0 or later
Chrome 32.0 to 44. Later versions are not supported.
Note You must manually enable VLC browser support in Chrome browsers v42 to 44. Learn more
The following are known issues when monitoring video with browsers and applications other than Internet Explorer:
Downloading the VLC Player and VLC Plug-in
To view video with Chrome, Firefox or Safari, download and install the VLC media player or Web plugin for your specific operating system platform. Before you start, uninstall any previous versions of VLC that you may have installed.
To install VLC media player for Windows or Linux, go to: http://www.videolan.org/vlc/#download and download the version for your specific platform. Follow the instructions provided on the VideoLan site to install it.
For MacOS, Cisco worked with the VLC developers to update the MacOS browser plugin to support the latest browsers and Mac OS versions. The Mac plug-in is available for download from Cisco.com.
Step 2 Drag “VLC Plugin.plugin” to the Internet “Plug-ins folder” for your browser.
Note If you have any issues, verify that the firewall settings on your PC or browser are not blocking the video.
.
Chrome Web Browser and VLC Video Player Plug-in Considerations
If video from a camera is interrupted by a network issue or configuration change for that camera, it will not automatically resume streaming in the VLC plugin. It is necessary to manually reload the camera to cause display to resume.
JPEG streams with high resolutions such as 5M cannot be played on the Arecont 5M cameras (such as the Arecont 5155).
The VLC player sometimes crashes while viewing a rotating view. You must reload the Chrome page or restart he browser.
MPEG4 streams do not play properly on Chrome using the VLC plugin.
Cameras must be reloaded in the Monitor Video page if network connectivity is lost while viewing video. Otherwise, the last viewed frame is displayed when network connectivity is restored.
Users cannot save the current view from the Monitor Video page (the Save As option is disabled when viewing the Current View).
Accepting Firefox Browser Security Warnings
When using browsers such as Firefox and Chrome, you may be prompted to confirm connection security exceptions. Accept these warnings and any security exceptions. This allows you to proceed to the Cisco VSM monitoring pages.
For example, when accessing a Cisco VSM Operations Manager for the first time using the Firefox browser, you must respond to a series of security prompts, as shown in Figure 1.
Perform the following procedure the first time you log on to a Cisco VSM Operations Manager. This security check is performed one time, and is not repeated on subsequent logins.
Step 1 Launch the Firefox web browser and log on to the Cisco VSM Operations Manager.
Step 2 Click Get Certificate.
Step 3 Select I Understand the Risks.
Step 4 Click Add Exception.
Step 5 Click Confirm Security Exception.
Step 6 Click Finish.
Step 7 Close the blank Firefox window.
Step 8 Continue using the Cisco VSM Operations Manager.
Figure 1 Firefox Browser Security Prompts
High Latency Network Links
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 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.
Resolving a Chassis Intrusion Alert
If a Cisco VSM server's chassis lid is opened, a “Chassis Intrusion” alarm will be generated in the Operations Manager. The chassis intrusion alarm will continue to be declared until it is explicitly cleared.
To clear the alarm, you must log in to the server and run the following command:
# sudo /usr/sbin/sdt -r "Chassis Intrusion"
Default View Must Be Redefined
The Default Views for Video Walls defined in Release 7.2 or earlier are not included when upgrading to Release 7.5 or higher. You must re-define the Default View for each Video Wall in the upgraded Release 7.5 deployment.
Audio for Virtual Clips
MP4 clips created from a Virtual Clip may not include the audio originally recorded with the virtual clip. This is because the virtual clip retention time may not be the same as the audio recording (the Media Server does not mark the audio recording while creating a virtual clip).
Note Virtual Clips do not support Metadata.
Medianet Considerations
Support for Dynamic Proxy
Medianet is not supported for Dynamic Proxy in Cisco VSM Release 7.5. As a result, Mediatrace will not show any statistics or performance information between intermediary node(s) (router/switch) and the Dynamic Proxy server for media Server to Dynamic Proxy flows.
Mediatrace and Performance Monitoring
VSM 7.5 adds support for Mediatrace and Performance Monitoring from the Media Server to the client workstation. This is disabled by default since it consumes resources on the client workstation while it is running. Consult the Cisco Video Surveillance Operations Manager User Guide for instructions to enable use this feature. We recommended that it be enabled only for troubleshooting a video and network performance issue at the client workstation. When you are done, it should be disabled again. Leaving it enabled for more than 24 hours could impact client software performance and stability.
Note Mediatrace and Performance monitoring are not supported on Media Servers with two Ethernet ports enabled.
Dynamic Proxy Considerations
When using Dynamic Proxy, observe the following:
The maximum number of viewers per Dynamic Proxy stream is 20 viewers.
The maximum latency between a Media Server and Dynamic Proxy Server is 4 seconds. This is long enough to allow the use of a satellite link between a central site and remote location.
The Dynamic Proxy server supports only live video. Access to recorded video goes directly to the Media Server where the recorded video is stored. This doesn’t benefit from bandwidth savings through the proxy server.
Camera Controls like PTZ are not supported through the Dynamic Proxy server. These commands go directly to the Media Server that is hosting the camera that is the intended target of the command.
Proximity based DP Server selection is not supported. This means if a user logs in from the Milpitas Site and is accessing a camera in San Jose and if there are Dynamic Proxy servers in North Carolina and one in San Jose, the Operations Manager will randomly pick one of the DP Servers.
A camera can only be proxied by a single Dynamic Proxy Server at a time.
Dynamic Proxy Frames to Skip
Observe the following guidelines to define the number of frames to skip when configuring a Dynamic Proxy server.
Table 5 Frames To Skip (Site Settings)
Setting
Description
MJPEG Max Framerate To Skip
(Optional) Stream thinning to be carried out for MJPEG streams. Must be set based on bandwidth availability.
All MJPEG frames are IFrames. Depending on the frame rate of the original stream, skip values are supported when the cumulative frame rate is greater than or equal to 0.1 fps. Therefore, the maximum value is 10 times the MJPEG stream's framerate.
The supported values are from 1 - 300.
For example, if the original frame rate of the MJPEG stream is o_fr, then the “MJPEG Max Framerate To Skip” can be any value, x, where o_fr/x >= 0.1 fps.
For example, for 10fps, it is 100, for 30 fps, it is 300, for 0.1fps, it is 10, etc.
Note This setting is enabled only if the Dynamic Proxy service is enabled.
Max IFrames To Skip
(Optional) The number of IFrames to skip for a video feed.
The minimum and maximum skip rates vary depending on the video stream format:
MPEG4/H.264 Streams
The minimum and maximum values are 1– 9 (true only for cameras sending 1IFrame per second).
MPEG4 and H264, setting skip results in a stream with only IFrames. Most cameras send 1 IFrame per second. If the stream (regardless of frame rate) is sending 1 IFrame per second, the maximum skip is 9.
Note This setting is enabled only if the Dynamic Proxy service is enabled.
Released Versions
Cisco VSM Release 7.5.2 is released with 7.5.2-08i. The component package versions are:
Cisco_GeoServer-7.5.2-001
Cisco_MPClient-7.5.0-25
Cisco_SASD-7.5.0-27
Cisco_VSF-7.5.2-2
Cisco_VSMC-7.5.2-003
Cisco_VSMS-7.5.2-010d
Cisco_VSOM-7.5.2-2
Supported Hardware Platforms
Cisco VSM Release 7.5.2 runs on the following hardware platforms:
Table 6 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.
Upgrade existing VM installations using the Management Console.
Supported Server Services
Each server can run one or more services that provide features and functions for the Cisco Video Surveillance system.
Cisco VSM Release 7.5.2 introduces the following new server services:
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 7 for more information.
Table 7 describes the supported server services and how each is enabled or disabled in this release.
Table 7 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 a Media Server service.
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 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 de-select 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 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 Map 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 de-select the 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. We recommend images no larger than the following maximum sizes.
Vector (shape files)—maximum size 80 MB
JPEG images— maximum size 19 MB and resolution 60 MP
PNG images— maximum size 68 MB and resolution 32 MP
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 de-select 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.
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 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 and 3050 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.
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-xx.
The minimum firmware version required to support connected edge storage is 2.0.
Supported Devices: Arecont
Table 9 provides information about Arecont devices that this VSM release supports.
Table 9 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
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
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, 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 10 provides information about Axis devices that this VSM release supports.
Table 10 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
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
M3007
Panoramic Camera
5.40.13.2
NTSC
H.264/MJPEG
No
Yes
Yes
Yes
Yes
P3301
IP Camera
5.40.92
NTSC
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 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 11 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 12 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 13 provides information about IQinVision devices that this VSM release supports.
Table 13 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 VSM 7.
Support configuring NTP on the IQinVision cameras to synchronize with their VSM Media Server.
Added support for Firmware upgrade for all supported models.
Added support for Camera Discovery for H.264 models.
Supported Devices: Panasonic
Table 14 provides information about Panasonic devices that this VSM release supports.
Table 14 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 VSM 7.
Added support for two Panoramic models SW 458, and SF 438
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 15 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 16 provides information about Pelco devices that this release supports.
Table 16 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 VSM 7.
Audio volume controls are not supported for NET540XT
Added support for Pelco NET5404T and Pelco Exsite Explosion Proof IP camera.
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 VSM.
The Pelco Spectra IV TXB-N (H.264 capable model) run Pelco Sarix firmware and can be supported in VSM as a Pelco Sarix Generic IP camera (additional details in the Generic IP camera section).
Supported Devices: Sony
Table 17 provides information about Sony devices that this release supports.
Table 17 Supported Sony Devices
Model
Type
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 is opened in the camera’s web interface.
Supported Devices: Generic IP Cameras
Cisco VSM Release 7.5.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 18 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
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
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.
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 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.
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 VSM. Note that current Sony 6th generation model numbers start with like VM6XX or VB6XX.
Supported Devices: Analog Cameras
This VSM release provides support for the following analog cameras.
Table 19 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 20 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 P3301
ONVIF 2.0
5.40.9.2
NTSC
H.264 MJPEG
Yes
Yes
Yes
No
No
Axis 6032e
ONVIF 2.0
5.41.1.3
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
Pelco D5118-AD74029
ONVIF 2.0
1.8.2.18-20121126-1.9310-A1.8726
NTSC
H264 MJPEG
No
Yes
Yes
No
No
Sony CH240
ONVIF 2.0
1.77.00
NTSC
H264 MJPEG
Yes
Yes
No
No
No
Sony EP520
ONVIF 2.0
1.78.00
NTSC
H264 MJPEG
Yes
Yes
No
No
No
Panasonic SF335
ONVIF 2.0
1.66
H264 MJPEG
No
Yes
No
No
No
5532
Generic Axis 3.0/Firmware 5.x
5.41.2
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
3367
Generic Axis 3.0/Firmware 5.x
5.50.3
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
Q6035
Generic Axis 3.0/Firmware 5.x
5.25
NTSC / PAL
H.264 MJPEG
Yes
Yes
Yes
Yes
No
Axis 215
Generic Axis 2.0 /Firmware 4.3
NTSC / PAL
MPEG4, MJPEG
Yes
Yes
Yes
Yes
No
AV3115
Arecont
65218
NTSC
H.264, MJPEG
No
Yes
No
Yes
No
AV1355
Arecont
65151
NTSC
H.264, MJPEG
No
Yes
No
Yes
No
IQ755
IQEye JPEG
V3.1/2
NTSC
MJPEG
No
No
No
Yes
Yes
IQ765N
IQEye H264
V3.4/5
NTSC
H264,
No
Yes
No
Yes
Yes
MJPEG
NP-502S
Panasonic
1.81
NTSC PAL
H.264, MPEG-4,
No
Yes
Yes
Yes
No
MJPEG
SC-384
Panasonic
1.44
NTSC PAL
H.264, MPEG-4,
No
Yes
Yes
Yes
No
MJPEG
SF-385
Panasonic
1.44
NTSC PAL
H.264, MPEG-4,
No
Yes
Yes
Yes
No
MJPEG
SD4E23
Pelco
1.9.2.1.20130613-1.2084-01.9797
NTSC
H264
No
Yes
No
Yes
No
VM 631
Sony 6th Generation IP cameras VMxxx and VBxxx
1.3.0
NTSC, PAL
H.264 MJPEG
Yes
Yes
No
No
No
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
CH 180
Sony 2nd, 3rd, 4th and 5th generation Sony IP cameras
1.77
NTSC PAL
H.264, MPEG-4, MJPEG
Yes
Yes
Yes
Yes
No
EP 520
Sony 2nd, 3rd, 4th and 5th generation Sony IP cameras
1.78.00
NTSC PAL
H.264, MPEG-4, MJPEG
Yes
Yes
Yes
Yes
No
RX530N
Sony 2nd, 3rd, 4th and 5th generation Sony IP cameras
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.
Table 22 Medianet Feature Support in Cisco VSM Releases
Release
Support
Release 7.0.0 and higher
Supports Camera Discovery and Auto-Smart Ports.
Release 7.2.0 and higher
Supports Medianet metadata and Mediatrace.
Release 7.5.0 and higher
Supports Media Services Interface (MSI) version 4.0 on Media Servers and the video client (the 64-bit video client uses the 64-bit MSI).
This allows performance monitoring and Mediatrace on TCP flows between the Media Server and browser-based or Cisco SASD client wokstations.
– Media Server and Clients—the MSI must be upgraded to v4.0.
– Cameras—camera firmware version 2.0.0-175 or higher is required.
– The Network Management System (such as LiveAction) must be upgraded to the latest version to communicate with the MSI endpoints (Media Server, monitoring clients, and cameras).
Note Only inbound DSCP is supported in MSI. Outbound DSCP is not supported in MSI 4.0 (the value will always be 0).
Mediatrace is supported on all Cisco VSM ActiveX monitoring clients (including the Cisco SASD).
Note Mediatrace and Performance monitoring are not supported on Media Servers with two Ethernet ports enabled.
Cisco Cameras That Support Privacy Mask
The following Cisco cameras support the “Privacy Mask” feature, which is typically used with the “Virtual Sitter” feature.
IP Cameras that Support “Connected Edge Storage” (On-Device Storage)
The following table summarizes the camera models that support the “Connected Edge Storage” feature for on-device recording storage with Cisco VSM.
Note ● See the camera device documentation for instructions to enable video storage on the device, or to install and format the storage media (such as an SD card).
To install a license, purchase the license and obtain the license file, then upload the file to the Operations Manager.
Table 24 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 24 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
L-CPS-VSM7-FD=
eDelivery license for one base 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
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 24).
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 25 describes the different types of software and firmware that are installed on servers, cameras, and encoders.
Table 25 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.
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 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.
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.