Cisco CIVS-SP8ECISP-2000, CIVS-SG1ADISP-C16, CIVS-SP8ECISP-6000, CIVS-SP12-ISP-6000, CIVS-SG1ADISP-FE Design Manual

Cisco Video Surveillance Stream Manager Hybrid Design Guide

Design Guide

Table of Contents

Chapter 1: Video Surveillance Overview...............................................................................1-1

Video Surveillance Components ...............................................................................................1-1

Cameras...............................................................................................................................1-2

Transmission Media..............................................................................................................1-2

Baluns...................................................................................................................................1-4

Matrix Switches.....................................................................................................................1-5

Recording.............................................................................................................................1-7

Chapter 2: Cisco Stream Manager Hybrid Solution.............................................................2-1

Hybrid Solution Components.....................................................................................................2-2

Integration Steps .......................................................................................................................2-3

Step 1: Remove legacy recording systems...........................................................................2-4

Step 2: Introduce a Cisco Data Converter ............................................................................2-4

Step 3: Introduce a Cisco Hybrid Decoder............................................................................2-5

Step 4: Cisco Stream Manager Modules ..............................................................................2-6

Viewing Live and Recorded Video.............................................................................................2-6

Live Viewing Operation.........................................................................................................2-6

Recorded Viewing Operation................................................................................................2-7

Chapter 3: Failover and Recovery.........................................................................................3-1

Matrix-based N+N Redundancy ................................................................................................3-1

How a Failure is Detected .........................................................................................................3-2

Single Port Failure.....................................................................................................................3-4

Recovering from a Failure.........................................................................................................3-4

Retrieving Video from a Failover ISP.........................................................................................3-4

Failover and Recovery with two Failover ISPs ..........................................................................3-5

Chapter 4: Third-Party Equipment Support..........................................................................4-1

Chapter 5: Basic Configuration .............................................................................................5-1

Configuring the Integrated Services Platform............................................................................5-1

Configuring the Cisco Hybrid Decoder ......................................................................................5-3

Hybrid Decoder Pools................................................................................................................5-5

Time Synchronization................................................................................................................5-7

Configuring Failover with a Matrix Switch..................................................................................5-9

Configure the Failover Integrated Services Platform ............................................................5-9

Configure Video Loss Detection .........................................................................................5-12

Configure the Stream Manager Administration and Monitoring Module..............................5-13

Chapter 6: Manufacturer-Specific Configurations ...............................................................6-1

Integration with a Bosch Matrix Switch and Keyboard...............................................................6-1

Cisco Data Converter ...........................................................................................................6-2

Cisco Hybrid Decoder...........................................................................................................6-3

Configuring the Bosch LTC 8200 Matrix Switch....................................................................6-3

Allegiant Master Control Software ........................................................................................6-3

Upgrading the Bosch IntuiKey Keyboard..............................................................................6-5

Failover Configuration with a Bosch LTC 8200 Matrix Switch ..............................................6-9

Integration with an American Dynamics Matrix Switch............................................................6-11

Power Supply/Data Converter ............................................................................................6-12

Failover Configuration with an American Dynamics Matrix Switch.....................................6-13

Integration with a Pelco Matrix Switch and Keyboard..............................................................6-14

Power Supply/Data Converter ............................................................................................6-15

Integrated Services Platform BIOS Setup...........................................................................6-16

Pelco CM9760-KBD Keyboard Setup................................................................................. 6-16

Pelco CPU Setup................................................................................................................6-17

Failover Configuration with a Pelco Matrix Switch..............................................................6-19

Appendix A: Network Communications ..................................................................................I

TCP/UDP Ports Required for Video Playback...............................................................................I

TCP/UDP Ports Required During a Failover................................................................................III

Appendix B: Glossary ..............................................................................................................V

Design Guide

Chapter 1: Video Surveillance Overview

Video surveillance has been a key component of many organizations’ safety and security groups for decades. As an application, video surveillance has demonstrated its value and benefits countless times by:

●

Providing real-time monitoring of a facility's environment, people, and assets.

●

Recording the movements inside and outside a facility's environment for delayed viewing.

Many traditional video surveillance deployments are purely analog and have not yet been able to benefit from a converged network approach. Rather than looking at a massive forklift upgrade, a Cisco hybrid deployment provides an interim solution that allows customers to implement a staged migration to a fully converged IP-based solution.

Cisco

video surveillance products can integrate with existing closed-circuit television (CCTV) systems, including matrix switches, keyboard controllers, and displays to enable new digital recording capabilities. A Cisco hybrid solution allows the user interface to remain unchanged and provides an easy migration path to a Cisco Virtual Matrix Switch solution, where the IP network infrastructure provides a dynamic transport of video streams.

Note: The Video Surveillance Solutions Reference Network Guide provides detailed information about the Cisco Virtual Matrix Switch design. This document is available here

http://www.cisco.com/go/srnd

Video Surveillance Components

A typical analog video surveillance system includes the basic system components that are shown in Figure 1. In this system, video streams are monitored concurrently by using a matrix switch as an aggregation device. This approach allows video streams from different cameras to be s witched to analog CCTV monitors by using special-purpose keyboard controls. Analog cameras, either fixed or pan-tilt-zoom (PTZ), typically are connected to the matrix switch by using coaxial cables for video transmission and serial cables for PTZ command and control.

Figure 1. Typical Analog Video Surveillance System

1-1

Design Guide

Cameras

Analog cameras are a key component of a traditional video surveillance solution. They capture images in the environment and convert them to analog video. Each surveillance environment has unique camera and positioning requirements. Installing a camera in the proper environment (with proper lighting, field of view and power) can be one of the most challenging tasks of implementing the solution.

Selecting the proper camera for the system also is important. A wide variety of cameras are available to meet specific deployment requirements. These devices include cameras with PTZ functionality, day/night capabilities, vandal-resistance, weather-proofing, and many other features.

Serial PTZ data can be transmitted either in a point-to-point fashion or by using a multidrop bus. With a multidrop bus, cameras can be configured with unique system dome IDs and can be daisychained by using the same set of electrical wires.

Transmission Media

To transmit video signals from analog cameras, different media can be used. Coaxial cable is one of the most common cable types, but twisted pair and fiber optic cable have also become popular.

Coaxial Cable A coaxial cable consists of a center conductor that is protected by an insulating spacer and a shield, which in most cases consists of a metallic web of conductors. The entire assembly is wrapped with a plastic insulating layer. Proper cable selection and installation is important because cable-related issues are the most common cause of video problems in a CCTV installation.

All coaxial cables have characteristic impedance. CCTV equipment typically uses coax ial cable with impedance of 75 Ohms. Cables are available in different Radio Guide (RG) types. RG specifies how radio frequency signals travel through a 75 Ohm coaxial cable. Table 1 lists the typical RG cables that are used in CCTV environments.

Table 1. Coaxial Cable Types

Type Impedance (Ohms) Diameter (mm) Distance (feet)

RG-6/U 75 6 1,000–1,500 RG-11B/U 75 10 2,000–2,500 RG-59B/U 75 6.15 750–1,000

RG-59 is one of the most commonly used cables because it is small in diameter and easy to work with. RG-11 is the largest in diameter and harder to work with, but it supports longer distances.

Fiber Optic Cable Fiber optic cable is relatively new in CCTV installations, but it has quickly become popular because it can span longer distances and accommodate more bandwidth than coaxial cable. Advantages of fiber optic cable include:

●

Wider signal frequency bandwidth than coaxial cable. Ability to carry light-modulated signals for longer distances than coaxial cable. Immune to nearby signals and electromagnetic interference (EMI), so it provides a lower bit

error rate. Multiple signals can travel on a single fiber with distances beyond 2,000 feet.

1-2

Design Guide

Multi-mode and single-mode are the most common fiber types in use. In multi-mode fiber, light waves are dispersed into numerous rays, called modes, which provide high speeds over medium distances. In single-mode fiber, only one light ray or mode is used to provide a transmission rate that is up to 50 times higher than multi-mode fiber.

The exact distance that can be supported by fiber cable is a function of many factors including the type of cable, signal frequency, bandwidth, and the number of splices and connectors that exist across the entire transmission distance. Multi-mode fiber typically is used in LANs with distances up to 500 meters, but it can be extended up to 5 km. Single-mode fiber is more expensive than multi-mode fiber and is more commonly used in long-haul applications with deployments of up to 60 km. Table 2 describes the more common types of fiber connectors.

Table 2. Fiber Connectors

Connector Insertion Loss Repeatability Fiber Type

●

0.15 db (SM)

●

0.10 db (MM)

●

0.20-0.45 dB

●

0.20 dB

●

0.10 dB

●

SM, MM

●

SM, MM

●

SM, MM

●

0.40 dB (SM)

●

0.50 dB (MM)

●

0.40 dB (SM)

●

0.20 dB (MM)

Unshielded Twisted Pair Twisted pair cable also is an alternative to coaxial cable installations because it is easier to instal l and less expensive. Twisted pair cable is used primarily in building or campus telecommunications installations of data and voice networks.

The Electronic Industries Association (EIA) standards define the performance of UTP (unshielded twisted pair) and cable using CATx designations. The typical categories of interest are Cat5, Cat5e, and Cat6 cabling. Most twisted pair cable plants use Cat5 cable or higher, because Cat5 provides better transmission than older UTP cables. For raw analog video, even 1% video loss can be significant. Shielded Twisted Pair (STP) cable is common in the CCTV market. In fact, STP is frequently specified for use by some vendors for their implementations. Be careful with grounding and interference when using STP and avoid mixing STP and UTP in a common cable plant.

Table 3 outlines some of the characteristics of these categories. Most twisted pair cable plants use Cat5 cable or higher, because Cat5 provides better transmission

than older UTP cables. For raw analog video, even 1% video loss can be significant. Shielded Twisted Pair (STP) cable is common in the CCTV market. In fact, STP is frequently specified for use by some vendors for their implementations. Be careful with grounding and interference when using STP and avoid mixing STP and UTP in a common cable plant.

Table 3. Twisted Pair Cable

Category Type Distance Bandwidth Typical Network Use

Cat5 UTP 100 m 100 MHz 100Base-T Cat5e UTP 100 m 100 MHz Gigabit Ethernet Cat6 UTP 100 m 250 MHz 10 Gigabit Ethernet Cat7 ScTP 100 m 600 MHz Up to Gigabit Ethernet

1-3

Design Guide

Baluns

Most existing analog camera deployments have been installed with coaxial cable, but n ewer installations are introducing twisted pair and fiber optic cables. Because twisted pair is easier to install, a simple solution for new cable deployments is the use of baluns to allow twisted pair cables to transmit video signals, power, and Pan, Tilt, and Zoom (PTZ) data to analog cameras with coaxial connectors.

Baluns interconnect different cables that are not compatible, such as coaxial and twisted pair. Figure 2 shows how a balun can transmit power, video and PTZ data to a camera by using a single twisted pair cable. When using twisted pair cabling, a balun is required at each end of the cable.

By deploying Cat5 or later twisted pair cable, the same cable infrastructure can support future deployment of network devices such as wireless access points and IP cameras.

Figure 2. Baluns

A wide variety of baluns are available from third-party manufacturers to support a range of applications. The example in Figure 2 shows a Cat5 cable, but other baluns can be used to convert from Cat5 to coaxial. Be aware that baluns are unmanaged devices that introduce another point of failure and can be difficult to troubleshoot.

Serial Connectivity In a CCTV environment, PTZ data is transmitted using serial communications. Table 4 sh ows the most common serial protocols and some of the relevant characteristics of each:

Table 4. Serial Cables

Specification RS232 RS422 RS485

Maximum Cable Length 20 m 500 m 1,200 m Maximum Data Rate for RS232 20 kb/s Maximum Data Rate for RS422/RS485

(50 m–1,200 m) Receiver Input Voltage Range +/– 15V –10V to +10V –7V to +12V

Mode of Operation Single-ended Differential Differential

10 Mb/s–200 kbps 10 Mb/s–20 0kbps

RS-232C is a serial communications standard that is used to interface serial devices over cable lengths of up to 20 meters. RS-232C was originally intended to support modem and printer applications, but it has been expanded to support other applications. RS-422 communications can carry data over longer distances and at higher rates and resist noise interference better than RS232C.

1-4

Design Guide

RS-485 is a variation of the RS-422 standard and is based on a master-slave architecture, in which the master initiates all transactions and the slave only transmits when instructed to do so by the master. RS-485 allows up to 32 devices to communicate at distances up to 500 meters, but the number of devices and distance can be extended using repeaters. A variety of connectors are supported, including RJ11, RJ45, DB9 and DB25.

RS-485 offers a multi-drop capability, in which up to 32 cameras may be configured with unique IDs to receive serial data. Figure 3 shows an example with four cameras that use the same RS-485 bus to transmit PTZ data. A multi-drop configuration typically requires two terminations, one at each end of the network.

Up-the-coax transmission, where electrical signals such as PTZ data communications are transmitted over the same coaxial cable is not supported.

Figure 3. Multi-drop Bus Configuration

Matrix Switches

In a traditional video surveillance environment, a matrix switch is the core element of the soluti on. A matrix switch acts as an array of video inputs and outputs, allowing users to control the display of different cameras and to switch control of PTZ functions. Figure 4 shows a traditional CCTV system with a matrix switch, where analog video streams are aggregated, controlled, and dispersed to different monitor displays by using analog switching technology.

Figure 4. Traditional Matrix Switch

A typical matrix switch can be programmed to display a video stream from any camera on any monitor either manually or by using automatic switching sequences. Some matrix switches include salvo switching capabilities, which allow any number of monitors to be selected to switch as a synchronized group. Also common is the ability to interface with external alarms or contact closures and to display video that is triggered by designated events.

1-5

Design Guide

Matrix switches can scale from a small system with a few cameras to an enterprise-class switch that can support thousands of cameras and hundreds of monitors.

In a large matrix switch environment, the system may be configured with many components, including:

●

Main CPU bay—A modular system that contains the system processor, power supply, and several video input and output modules.

●

Video input module—Accepts input from cameras and other video sources.

●

Video output module—Provides outputs to monitors and VCRs.

●

Monitor expansion bay—Provides connectivity to several monitors. Typically required in deployments with more than 32 monitors and can also accommodate several keyboards.

●

PTZ data distribution unit—Communicates with PTZ cameras typically by using RS-422 data transmission.

The high-level example in Figure 5 shows how a matrix switch system can grow to accommodate many cameras, monitors, and recording devices. In this design, a centralized monitoring facility houses all keyboards and CCTV monitors, which requires the cable infrastructure to be routed to a single location. While this configuration is able to grow to a large number of devices, the cable infrastructure does not allow video to be viewed from other stations at the facility or from remote locations.

Figure 5. Traditional Matrix Switch

1-6

Design Guide

Recording

Most video surveillance environments require recording capability either to meet regulatory requirements or to facilitate the investigation of events that have occurred.

Many traditional installations that relied on video cassette recorders (VCRs) now record events on hard disks instead of VHS tapes. VCR recording systems are cumbersome and can make timely retrieving of video difficult. Other drawbacks include:

●

VCRs typically are dedicated to provide only recording or pla yback. To view video during an investigation, separate record and playback devices are required.

●

Device failures can go undetected for a long time. VCR or DVR technology usually does not have device monitoring capabilities that notify an operator when a device fails. In contras t, network-based recording provides management features to immediately send alerts when a failure occurs.

●

To review recorded video from a remote location, tapes must be sent to the investigation center or an officer must visit the remote facility. In a network-based environment, video streams can be transmitted immediately to any network location for review.

With the declining availability of VCRs and to address recording limitations, other technologies have emerged to enhance video surveillance recording. For the most part, DVR are stan d-alone set-top boxes with video inputs and basic recording software.

Solutions that are based on digital video recorders (DVRs) address some limitations of VCRs, however, they do not provide the scalability and flexibility that an IP-network-based s ystem solution can provide such as integration with other business systems, greater access to video, and the use of video analytics for safety, customer satisfaction, and operator productivity.

While tape-free DVR recording provides an upgrade in functionality over traditional VCRs , the technology still exposes limitations, such as:

●

To view recorded events, a PC-based system typically is required, which prevents an operator from using a familiar CCTV keyboard interface.

●

The cable infrastructure is centralized and typically relies on the same cable infrastructure that was used to support a VCR installation.

●

Only a few channels are recorded per device.

1-7

Design Guide

Chapter 2: Cisco Stream Manager Hybrid Solution

In a Cisco hybrid solution, a matrix switch seamlessly integrates with a Cisco Video Surveillance digital recording system and provides a staged transition to digital video without changing an interface that is familiar to users. This integration also provides a foundation for migrating to a complete IP infrastructure. As part of this integration, operators can view recorded video from analog monitors instead of using a separate viewing station that is dedicated to video revi ew. This integration also allows operators to continue using familiar keyboards and joysticks and im proves response time when users investigate events. In a multi-display environment, operators can simultaneously investigate a recorded event and monitor other cameras.

The Cisco hybrid solution offers several benefits to an environment with a traditional matrix switch including:

●

Compatibility with a wide range of matrix switches and keyboards. Table 6 and Table 7 on Page 4-1 provide a list of supported matrix switches, cameras, and keyboards.

●

Enhanced keyboard functionality that provides immediate video revie w by using customized key sequences. An operator can also play back video from a specific date and time.

●

Recorded video from several cameras may be reviewed at the same time on multiple monitors.

●

Simultaneous review and recording of a single video stream.

●

Support for redundant recorders for high-availability of recorded video streams.

●

Extensive control for review of recorded video, including instant replay, fast forward, rewind, pause, frame advance/reverse, digital zoom, time/date search, still JPEG snapshot image capture, and more.

●

System interoperability, which allows operators to use keyboards and joysticks from thirdparty manufacturers.

●

A migration path to a complete Cisco virtual matrix switch design.

Note: The Video Surveillance Solutions Reference Network Guide provides more details about the Cisco Virtual Matrix Switch Design. This document is available here:

http://www.cisco.com/go/srnd

2-1

Design Guide

Hybrid Solution Components

A Cisco hybrid solution is an ideal upgrade for organizations that use video matrix switches. W ith minimum affect on the existing system, a hybrid solution can add digital recording and instant retrieval features, improving system and operator efficiency. The recording systems are the only components that are replaced. The matrix switch, video cameras, and keyboards remain.

Figure 6 shows a complete hybrid solution that is integrated with a third-party matrix switch.

Figure 6. Cisco Hybrid Design

In this design, an Integrated Services Platform (ISP) records video streams and performs digital playback operations that are requested by an operator. The Cisco system integrates with the thirdparty matrix switches and keyboards that are listed in Table 6 and Table 7 on Page 4-1.

In a hybrid solution, the following Cisco components are introduced to perform digital recording and retrieval:

●

Cisco ISP. This device performs digital recording and playback of video streams. The Cisco Video Surveillance Stream Manager Software that runs on the ISP supports a modular deployment and provides features for high-availability and system expans ion.

●

Cisco data converter. A Cisco data converter is required to integrate some matrix switches with the Cisco hybrid solution. The data converter converts serial signals between RS-232 and RS-485/RS-422. Cisco offers several data converter models to match various thirdparty matrix switches. A data converter is required for each keyboard that needs access to playback features.

●

Cisco hybrid decoders. The hybrid decoder accepts digital recorded video from an ISP and decodes it into analog video, which is passed to the matrix switches. The hybrid decoder connects to a dedicated analog video input port on the matrix switch. The number of hybrid decoders in a solution should match the number of keyboards that require simultaneo us playback functionality. Note that the hybrid decoder is a different product than the IP gateway decoder.

●

Cisco Stream Manager Client Viewing Module. This PC-based application may be used to display live or recorded video streams from the ISP.

2-2

Table 5 lists the Cisco products that are used in a hybrid solution.

Table 5. Cisco Part Numbers

Part Number Description

Integrated Services Platforms

CIVS-SP8ECISP-2000 Cisco VS Integrated Services Platform with 8 encoders, 2TB RAID (expandable)–2RU CIVS-SP8ECISP-6000 Cisco VS Integrated Services Platform, 8 input, 6TBytes (RAID5) CIVS-SP12-ISP-6000 Cisco VS Integrated Services Platform, 12 input, 6TBytes (RAID5)

Hybrid Decoders

CIVS-SG1ADISP-C16 Cisco VS 1 port ISP Decoder Card for FE & GE Chassis CIVS-SG1ADISP-FE Cisco VS 1 port Standalone ISP Decoder

Data Converters

CIVS-KYBD2232= Cisco VS KEYBOARD 232 to RS422/485 ADAPT GENERIC CIVS-KYBD2232-AD= Cisco VS KEYBOARD 232 to RS422/485 ADAPT American Dynamics CIVS-KYBD2232-B= Cisco VS KEYBOARD 232 to RS422/485 ADAPT FOR BOSCH CIVS-KYBD2232-P= Cisco VS KEYBOARD 232 to RS422/485 ADAPT FOR PELCO CIVS-KYBD2232-U= Cisco VS KEYBOARD 232 to RS422/485 ADAPT FOR Ultrak

Stream Manager Client Viewing Module

CIVS-SM-CL30= Stream Manager Client Viewing Module

Design Guide

Integration Steps

Integrating the Cisco hybrid solution with an existing video surveillance environment requires on ly a few steps. A typical environment includes a matrix switch that functions as the central connecting point for all analog cameras, keyboards, monitors, and recording devices.

As shown in Figure 7, each device in the system requires a unique port on the matrix switch, either for input or output. The matrix switch can display video streams from different cameras on different CCTV monitors and direct video streams to recording devices.

Figure 7. Existing Matrix Switch

The following sections explain the general steps for integrating the Cisco hybrid solution with an existing video surveillance environment.

2-3

Design Guide

Step 1: Remove legacy recording systems

The first integration step is to remove legacy recording systems and introduce a Cisco ISP. The ISP provides 8 or 12 encoding ports (depending on the model) that connect directly to cameras and allow the ISP receive and record video streams simultaneously.

Video streams that are sent to the matrix switch need to be routed through the ISP. A simple way to direct the video streams from the cameras is to use video distribution amplifiers or other looping methods such as looping ports on a matrix switch.

As shown in Figure 8, a video distribution amplifier receives four video streams from analog cameras and splits each signal into two streams. Four coaxial cables connect to input ports on the matrix switch and four coaxial cables connect directly to the encoder ports on the ISP.

Note: The ISP is connected to the IP Network, but this connection is not shown in this figure simplicity.

Figure 8. Legacy recording systems

Step 2: Introduce a Cisco Data Converter

A Cisco data converter is inserted between the matrix switch and the CCTV keyboard to allow the ISP to intercept keyboard commands that identify when an operator wants to switch from live to recorded video. For some systems, the data converter switches serial signals from RS232 to either RS-485 or RS-422 via a dip switch setting. The Stream Manager Software that runs on the ISP interprets the command structure and determines if a command is intended for the matrix switch or intended to display digital playback video.

2-4

Design Guide

Figure 9 shows how a Cisco data converter connects to the ISP, the keyboard, and the matrix switch. Note that the keyboard is no longer connected to the matrix switch.

Figure 9. RS-232–RS485 Data Converter

Step 3: Introduce a Cisco Hybrid Decoder

When a playback feature is requested, the hybrid decoder retrieves the video stream from the proper ISP and delivers it to the proper matrix switch port. The background processing is transparent to operators.

A shown in Figure 10, a hybrid decoder connects via a 10/100BASET Ethernet port to the IP network and via a coaxial cable to the matrix switch. An input port from the matrix switch is reserved to act as the input from the hybrid decoder. When an operator requests a playback feature from the keyboard, the matrix switch is instructed to switch video from the reserved input port to the current monitor port.

Figure 10. Cisco Hybrid Decoder

2-5

Design Guide

Step 4: Cisco Stream Manager Modules

Figure 11 shows a complete hybrid system integrating with a matrix switch to provide playback functionality. The system can easily scale to support thousands of cameras and allows operators to use other Stream Manager utilities for added functionality.

While the hybrid solution can work without the Cisco Stream Manager Client Viewing Module, this Windows-based software provides a flexible way to view streams from any network location. In addition, the software allows exporting video streams to a video file for review.

The Cisco Stream Manager Administration and Monitoring with Failover Module provides system health information and alarm capabilities for all Cisco Video Surveillance devices in the network. This module is required in a failover environment, as explained in the next chapter.

Figure 11. Hybrid Design Solution

Viewing Live and Recorded Video

When an operator presses a key sequence on the keyboard to retrieve recorde d video, the ISP, data converter, and hybrid decoder provide the functionality to identify the request and display the video on the appropriate monitor.

Live Viewing Operation

For live viewing operations, the ISP monitors for special key sequences that indicate a request for video playback. If no playback requests are received, the Stream Manager software that is running on the ISP sends the serial commands back to the matrix switch. This step typically takes less than one second and an operator does not notice any delay when switching video streams on the matrix switch.

2-6

Design Guide

Recorded Viewing Operation

When an operator requests a playback feature, the ISP detects the request and responds with the proper playback feature. Figure 12 shows the interaction between the ISP, data converter, and hybrid decoder when an operator who is using Monitor 1 requests to view recorded video from Camera 5 by pressing the Instant Replay button.

Note: Appendix A provides additional details about the network communication that takes plac e during a video playback and describes the TCP/UDP port numbers that are used.

The hybrid decoder is connected to the matrix switch on input port 16 and video for Camera 5 is recorded on the ISP named ISP_2.

Figure 12. Example—Playing Recorded Video

In Figure 12, live viewing is taking place and no playback requests have been received. Keyboard control commands are passed through the ISP to the matrix switch transparently until an operator requests the playback of recorded video. Here is an example of the processes that occur when an operator requests playback:

1. While viewing video from Camera #5, an operator presses a key sequence requesting an

instant replay of Camera#5. ISP_1 receives this key sequence and detects that the user wants to play recorded video. The default rewind time is 30 seconds, but this value may be changed as shown on Page 5-12.

2. Through the data converter, ISP_1 reads the currently selected camera from the matrix switch

and sends a device discovery request for an available hybrid decoder.

3. If a hybrid decoder is available, ISP_1 sends the peripheral ID (Camera#5) and start date/time

to the hybrid decoder. If no hybrid decoders are available, the request terminates and no visual changes take place on an operator’s monitor.

4. The hybrid decoder sends to all recorders, via multicast, a discovery request for the ISP that

has recorded peripheral ID 5 at the specified start date/time.

5. ISP_2 responds to the hybrid decoder and a new TCP session is established between ISP_2

and the hybrid decoder.

2-7

Design Guide

6. Because the hybrid decoder is configured for input port 16 on the matrix switch, ISP_1

instructs the matrix switch to switch video from port 16 to the monitor that is selected (switch video input #16 to monitor #1). The monitor displays the recorded video on Monitor 1.

ISP_1 waits for user input and processes features such as fast-forward and rewind. When an operator presses a key sequence to stop the digital video, ISP_1 instructs the hybrid decoder to terminate the session with ISP_2 and instructs the matrix switch to resume live video from camera 5 to monitor 1.

Note: Tests in a lab environment show that the average retrieval time for playback video is approximately 1.5 seconds and that it takes approximately one second to go back to live viewing after an operator stops digital playback.

2-8

Design Guide

Chapter 3: Failover and Recovery

Traditionally, the CCTV industry has considered recorders to be a single point of failure and has avoided recording many video streams on a single device to minimize risk. The Cisco Integrated Services Platform provides recording for many of video cameras and introduces high-av ailability features that record video streams during failure events.

Matrix-based N+N Redundancy

To enhance system-level redundancy, Cisco provides a matrix-bas ed N+N redundancy solution, which allows one or more recorders to act as failover recorders for any number of primary recorders.

If a primary ISP fails, the streams that it was recording are recorded by a failover ISP. The failover ISP can also record single encoder ports during a failure. Playback features that were available before the failure, such as time/date search and instant replay, remain available to the operator. Figure 13 shows how an ISP can act as a failover ISP for other ISPs.

Figure 13. Matrix-Based N+N Redundancy

The following equipment and software is required to provide redundancy:

●

Cisco equipment:

◦ At least one dedicated failover ISP. This ISP acts as the failover unit for other ISPs in the

environment. It must be configured in failover mode and to record only when a failure is detected. The number of video streams to be backed up depends on the number of

3-1

available encoder ports (8 or 12) on the failover ISP. More than one ISP may be configured as a failover ISP for any number of primary ISPs.

◦ The Cisco Stream Manager Administration and Monitoring with Failover Module. This

Windows-based software provides system health information, including information about server and bandwidth use of all Cisco Video Surveillance devices in a network, and central alarm capabilities. The Administration and Monitoring with Failover Module initiates a failover when either a single encoder port or an entire ISP fails, redirecting video streams to a failover ISP. The module also maintains a history log of failure events.

●

Third-party equipment:

◦ A supported matrix switch (see Table 6 on Page 4-1) with available monitor output ports.

The monitor output ports are connected to the encoder ports of the ISP and become active when a failure is detected. The number of available monitor output ports must be equal to or greater than the number of video streams to be backed up.

◦ A serial cable to connect the matrix switch to the failover ISP. For more detailed

information about matrix switches, see the “Manufacturer-Specific Configurations” chapter. One serial cable can support failover for more than one failover ISP.

Design Guide

◦ A CCTV keyboard that is dedicated to selecting video streams and requesting digital

playback features.

To minimize the potential affect of power failures when using redundant devices, follow traditional networking designs and use several electrical circuits.

How a Failure is Detected

The Administration and Monitoring with Failover Module must be active and able to reach all ISPs that are in the environment, including the failover ISP. When the Administration and Monitoring with Failover Module detects a failure on an ISP, it polls the affected device three times, and then redirects the video streams to the failover ISP. The refresh interval for polling is a system-wide configuration option on the Stream Manager Administration and Monitoring with Failover Module, and may be changed from the default value.

Figure 14 shows a deployment in which ISP_3 is dedicated as a failover ISP and records video streams if a failure occurs.

3-2

Figure 14. Failover Scenario

Design Guide

The following events take place if ISP_2 fails:

1. The Administration and Monitoring with Failover Module sends discovery request messages

every five seconds to maintain a list of available Cisco Stream Manager video surveillance devices on the network. If a device does not respond to these discovery requests, the Administration and Monitoring with Failover Module waits three times longer than the refresh interval before logging a failure. The default refresh interval is 60 seconds, but this value may be configured as shown on Page 5-17. When the system logs a failure, it displays a notification on the Administration and Monitoring screen and generates an audib le alert.

2. The Administration and Monitoring with Failover Module sends a discovery request for

available failover ISPs. ISP_3 responds and specifies the number of free channels that it has available for failover recording.

3. The Administration and Monitoring with Failover Module informs the failover ISP which video

streams need to be recorded. A new message is sent every three seconds with details on which port to back up, until the failover ISP reports that there are no longer free channels for recording.

4. Through the serial cable between the matrix switch and the failover ISP_3, ISP_3 instructs the

matrix switch to redirect video streams to the output ports that are reserved for failover.

5. The redirected video streams are recorded on the failover ISP.

6. If an operator requests video playback during a failure, the retrieval steps are the same as

Step 1 through Step 6 that accompany Figure 12 on Page 2-8. These steps explain how video is retrieved from ISP_3.

Note: If the data converter was connected to ISP_2, recording on the failover ISP would still take place, but an operator would not be able to request playback video by using that keyboard. An

3-3

Design Guide

alternate keyboard that is connected to any ISP on the network could retrieve recorded video. During a failure, the Stream Manager Client Viewing Module cannot retrieve recorded video from the failover ISP.

Note: In a system that is configured with a 20 second refresh rate, typical recovery times are approximately 75–80 seconds. During this time, video streams from the failed device are lost.

Single Port Failure

The failover solution can also monitor when a single port on an ISP fails or loses video. Such a situation can occur for several reasons, such as a hardware malfunction or a faulty cable.

When a single port loses video, the following steps take place:

1. The ISP is still able to communicate on the network, so it reports the port failure event directly

to the Administration and Monitoring with Failover Module, sending a video loss alarm that specifies the peripheral ID of the failed port. Figure 36 on page 5-14 illustrates this configuration.

2. The Administration and Monitoring with Failover Module informs the failover ISP which video

stream needs to be recorded.

3. The failover ISP notifies the matrix switch (through the serial cable) to redirect video streams to

the first available output port that is reserved for failover.

4. The redirected video stream is recorded on the failover ISP.

5. If an operator requests video playback during a failure, the retrieval steps are the same as

Step 1 through Step 6 that accompany Figure 12 on Page 2-8. These steps explain how video is retrieved from the failover ISP.

Recovering from a Failure

The failover ISP continues to record until the failure is corrected. When a failed device becomes operational, it begins to record video streams and responds to discovery requests from the Administration and Monitoring with Failover Module. After receiving these responses for approximately 10 seconds, the Administration and Monitoring with Failover Module redirects video streams to the primary ISP.

The failover ISP instructs the matrix switch to stop sending video on the output ports and the Administration and Monitoring with Failover Module notifies each failover port to stop recording. It does it in sequence, by notifying one port and waiting for three seconds before notifying the next port. The primary ISP resumes recording video.

Video streams that were recorded on the failover ISP remain on the failover ISP and are not transferred to the primary ISP.

Retrieving Video from a Failover ISP

After the primary ISP is restored, video playback or exporting is performed on the primary ISP. To retrieve video that was recorded during a failure, an operator performs the steps that accompany Figure 12 on Page 2-8. When doing so, an operator also must specify the start time and date for the desired video.

As shown in Figure 15, if operators requests to review video streams that fall within the time of the failure, video is retrieved from the failover ISP. The video can be played until the point where the

3-4

+ 46 hidden pages

Cisco CIVS-SP8ECISP-2000, CIVS-SG1ADISP-C16, CIVS-SP8ECISP-6000, CIVS-SP12-ISP-6000, CIVS-SG1ADISP-FE Design Manual

Specifications and Main Features

Frequently Asked Questions

User Manual