Pelco C1640M-B User Manual

™

Endura

Network Design Guide

Video Security System

C1640M-B (3/06)

UP n P

Welcome to the Endura Network Design Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Endura Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Endura Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Endura Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Physical Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Network Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Unicast Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Multicast Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Internet Group Management Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Endura Network Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Understanding the Endura Network Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Endura A Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Broadcast Domains and VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Using TTL to Control Network Traffic in Broadcast Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Endura B Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Endura Traffic Summary Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Calculating Bandwidth and Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

NTSC Frame Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

PAL Frame Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Examples of Worse-Case Bandwidth Calculation in Playback Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Examples of Worse-Case Bandwidth Calculation in Live Video Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Endura Core Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Endura C Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Examples of Endura Network Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Unmanaged Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Managed Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Connecting the NVR5100 and SEB5000s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Connecting Multiple NVR5100s and SEB5000s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Appendix A: Endura Network Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Appendix B: WAN Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Appendix C: Endura Network Requirements Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

C1640M-B (3/06)

Setting Up Switch A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Setting Up Switch B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Example Configuration File for Switch B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Network Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

City A Router (R102) Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

City B Router (R104) Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Verifying the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

List of Illustrations

1 A Block: Encoding, Recording, and Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Using VLANs to Segment the Network into Separate Broadcast Domains for Each Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 TTL Is Set to 1 in VLAN 2 and Keeps UPnP T rafﬁ c Within the A Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4 B Block: Decoding and V iewing V ideo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5 Core Block: Authentication and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6 V ideo T rafﬁ c Path Through the Core Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

7 C Block: Encompasses A, B, and Core Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

8 Unmanaged Endura Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

9 Managed Endura Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

10 Using a Patch Cable to Connect the NVR5100 and a Single SEB5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

11 Connecting the NVR5100 and Multiple SE5000Bs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

12 Using VLANs to Connect Multiple NVR5100s and SE5000Bs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

13 Example Endura Network and HP 5304 Switch Conﬁ guration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

14 Example of a Conﬁ guration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

15 Sample Endura Network Over a W AN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

List of T ables

Endura Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

High Resolution: NTSC Frame Rates with Dual Stream NET5301T Encoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Medium Resolution: NTSC Frame Rates with Dual Stream NET5301T Encoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Low Resolution: NTSC Frame Rates with Dual Stream NET5301T Encoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

High Resolution: PAL Frame Rates with Dual Stream NET5301T Encoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Medium Resolution: PAL Frame Rates with Dual Stream NET5301T Encoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Low Resolution: PAL Frame Rates with Dual Stream NET5301T Encoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Endura Network Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

C1640M-B (3/06)

elcome to the Endura Network Design Guide

•

elcome to the Endura

networks.

This guide is designed to help you with the following:

Understand the primary building blocks of the Endura network and the role each one plays

Understand the networking technologies applicable for Endura

Determine which approach to use for networking and which technologies are best for your security network business requirements

Information in this guide is organized as follows:

Network Architecture on page 7

Endura Network Design Considerations on page 8

Understanding the Endura Network Structure on page 9

• Appendix A: Endura Network Conﬁguration Example on page 27

• Appendix B: WAN Conﬁguration Example on page 31

• Appendix C: Endura Network Requirements Worksheet on page 37

™

Network Design Guide. This document is speciﬁ cally designed as a guide and reference source for designing Endura

AUDIENCE

This guide is written for network administrators and engineers who have in-depth networking knowledge and experience.

HOW TO USE THIS GUIDE

If you are new to Endura, the Endura Network Design Guide serves as a high-level tutorial and network design source. If you are experienced with Endura, this guide serves as a reference source.

• If you are new to Endura, you should read this guide from start to ﬁnish to get a good understanding of the Endura system network requirements.

• If you are experienced with Endura, you should always consult this document as a reference source as new information might be available periodically.

• As you read this guide, ensure that you complete the Endura Network Requirements Worksheet. Use this worksheet to validate that your network meets the minimum requirements to support an Endura system. For information on the Endura Network Requirements Worksheet, refer to Appendix C: Endura Network Requirements Worksheet on page 37.

ENDURA OVERVIEW

Endura is a high-quality, high-performance network-based video security system, which is based on a powerful distributed system architecture and hardware/software platform for the total utilization of today’s Ethernet networks. This noncentralized system allows customers to make use of a facility’s network and network infrastructure, representing a signiﬁcant savings in cabling, hardware, and manpower resources.

No longer limited by traditional, centralized approaches, Endura offers an unconstrained platform for designing and implementing video security systems. There is virtually no end to how a system and its components can interact and share video, audio, and control information.

The Endura hardware platform offers all the components necessary for designing, installing, and utilizing complete networked digital video systems. With encoders, decoders, network video recorders, PC workstations, video console displays, storage expansion boxes, and advanced management technologies, customers now have all the tools necessary for building a high-performance video security system—all delivered over an Ethernet network with total access ﬂexibility.

C1640M-B (3/06)

ENDURA COMPONENTS

Endura components take full advantage of leading edge technologies such as Universal Plug and Play (UPnP™), allowing for fast, error-proof installations and set up. Essentially, when an Endura device is added to a system, it announces itself and the services it has available. The existing devices acknowledge the new unit and then begin exchanging information as user preferences and proﬁles dictate.

Table A lists the Endura components. Information in this table is updated periodically and might not describe the latest Endura products.

Table A. Endura Components

Endura Component Description

NET5301T encoder The NET5301T encoder is a high-performance MPEG4 video encoder. It accepts analog video and audio

signals and converts them into digital TCP/IP packets, as well as provides an interface for relays and alarms.

NET5301R decoder The NET5301R is a high-performance video decoder. It converts digital video and audio streams back

into video output for viewing on a composite, S-Video, or VGA monitor.

WS5050 workstation The WS5050 Endura workstation (WS) is a Windows®-compatible system that is used for viewing video

and conﬁguring an Endura system. The WS5050 is supplied with all PC hardware in a stand-alone box.

VCD5000 video console display The VCD5000 video console display (VCD) is a high-performance, multiple-stream decoding unit. It

converts multiple digital MPEG4 streams into video signals to be viewed on either composite, S-Video, or VGA monitors. Up to four decoding cards can be added to this unit. Four models are available that allow users to tailor their viewing systems with up to 64 displays. An unlimited number of video console displays (VCDs) and decoders can be controlled from a single VCD. Using an Endura keyboard or a standard USB-compatible PC mouse and keyboard, users can access the on-screen menus and control an Endura system.

SM5000 system manager The SM5000 system manager (SM) is an integrated hardware/software component that provides

distributed administration of multiple devices. The SM5000 also manages system security, functioning as a key server for user and device authentication.

NVR5100 Series network video recorder The NVR5100 Series network video recorder (NVR) represents a whole new generation of ﬂexibility and

integration for network-based video system recording. It sits at the center of Endura, Pelco’s most advanced integrated video security system. The NVR represents the state of the art in scalability, features, and reliability.

The NVR5100 is capable of continuous, scheduled, alarm/event, and motion recording. Pre- and postalarm, event, and motion recording is also available and is fully programmable on a per-channel basis. The unit maximizes storage efﬁciency using EnduraStor™, a time- and priority-based system that identiﬁes data to be removed when storage reaches capacity.

SEB5000 storage expansion box The SEB5000 storage expansion box (SEB) is a high-performance storage solution. Each SEB box can

add up to 3.9 TB of network storage. Multiple SEBs can be attached to a single NVR unit, providing a very large, very scalable network storage solution.

EnduraStor storage optimization EnduraStor offers the ability to reduce the frame rate of previously recorded video on an Endura system

after a speciﬁed period of time. After captured video has reached a user-deﬁned age, EnduraStor goes to work to “prune” the database and reduce the number of recorded frames. By enabling EnduraStor within the system, a user has the unique ability to dramatically extend recording duration at a lower frame rate.

ENDURA PRODUCT SUPPORT

Pelco provides 24-hour, seven-day-a-week product support designed to assist any customer with a technical problem involving Pelco equipment; just dial (800) 289-9100 or (559) 292-1981 and ask for technical assistance.

6 C1640M-B (3/06)

Network Architecture

The Endura network topology is based on using current networking technology. Pelco suggests that you recommend or select networking devices and technologies that meet or exceed the features and functionality described in this section.

PHYSICAL MEDIA

Physical media used in the Endura network is as follows:

• 100baseT minimum.

• 1000baseT (gigabit) is recommended. One gigabit uplinks are required for some components.

• CAT5e cabling (minimum).

• CAT6 is recommended for gigabit links.

NETWORK PROTOCOLS

This section provides a summary of the networking protocols that are required to implement an Endura network and describes the features/ functionality that the protocols must exhibit.

UNICAST ROUTING PROTOCOLS

Basic unicast connectivity is required to implement an Endura network. At least one of the protocols listed below can be used to meet this requirement:

• Routing Information Protocol (RIP): RIP is a simple routing protocol that is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. It determines a route based on the smallest hop count between source and destination. RIP is a distance vector protocol that routinely broadcasts routing information to its neighboring routers and is known to waste bandwidth. It also has a limit of 15 hops. If a route is advertised as having 16 hops, it is ﬂagged as unreachable.

• Open Shortest Path First (OSPF): OSPF is a routing protocol that determines the best path for routing IP trafﬁc over a TCP/IP network based on distance between nodes and several quality parameters. OSPF is an interior gateway protocol (IGP), which is designed to work within an autonomous system. It is also a link state protocol that provides less router-to-router update trafﬁc than the RIP protocol (distance vector protocol) that it was designed to replace.

• Static routing: This protocol forwards data in a network via a ﬁxed path. Static routing cannot adjust to changing line conditions as can dynamic routing.

MULTICAST ROUTING PROTOCOLS

Multicast routing is required to allow Endura components to communicate with one another. At least one of the protocols listed below can be used to meet this requirement:

• Protocol Independent Multicast (PIM): PIM is a multicast routing protocol that is used in conjunction with an existing unicast routing protocol. PIM comes in two versions: Dense Mode (PIM-DM) and Sparse Mode (PIM-SM).

– Dense mode is most useful in the following instances:

• Senders and receivers are in close proximity to one another.

• There are a few senders and many receivers.

• The multicast trafﬁc volume is high. Dense mode forwards multicast data everywhere, and lets switches prune out trafﬁc that is not requested.

• Multicast data is periodically ﬂooded everywhere.

• The multicast trafﬁc stream is constant.

PIM-DM uses Reverse Path Forwarding and looks a lot like Distance Vector Multicast Routing Protocol (DVMRP). The most signiﬁcant difference between DVMRP and PIM-DM is that PIM-DM works with whatever unicast protocol is being used. Also, PIM-DM does not require any particular unicast routing protocol.

C1640M-B (3/06) 7

– Sparse Mode is most useful in the following instances:

• There are few receivers in a group. Switches send multicast trafﬁc only to the devices that request it.

• Senders and receivers are separated by Local Area Network (LAN) links.

• The type of trafﬁc is intermittent.

PIM-SM is optimized for environments where there are many multipoint data streams. Each data stream is sent to a relatively small number of the LANs in the internetwork. For these types of groups, Reverse Path Forwarding techniques waste bandwidth. PIM-SM works by deﬁning a rendezvous point. When a sender wants to send data, it ﬁrst sends to the rendezvous point. When a receiver wants to receive data, it registers with the rendezvous point. Once the data stream begins to ﬂow from sender to rendezvous point to receiver, the routers in the path will optimize the path automatically to remove any unnecessary hops. PIM-SM assumes that no hosts want the multicast trafﬁc unless they speciﬁcally ask for it.

PIM is able to simultaneously support dense mode for some multipoint groups and sparse mode for others.

• DVMRP: DVMRP is a routing protocol that supports multicast. Stemming from RIP and used in the Internet's Mbone (multicast backbone),

DVMRP allows for tunneling multicast messages within unicast packets. It also supports rate limiting and distribution control based on destination address and is responsible for the following:

– Routes multicast datagrams

– Periodically floods multicast traffic (similar to PIM-DM)

– Allows use of non-multicast aware edge devices

INTERNET GROUP MANAGEMENT PROTOCOL

Internet Group Management Protocol (IGMP) is a communications protocol used to manage the membership of multicast groups. IGMP is a required protocol in the Endura network and is used by IP hosts and adjacent multicast routers to establish multicast group memberships.

The speciﬁcation that deﬁnes how to handle “unknown” multicast groups is not deﬁnitive. In this case, some vendors block multicast streams that have no members, while other vendors will ﬂood this same trafﬁc. Flooding multicast streams that have no members can present a problem in the Endura network because each video stream can be approximately 2 Mbps. In even a relatively small network, ﬂooding Endura trafﬁc can signiﬁcantly reduce network performance and the overall performance of the Endura system.

Endura Network Design Considerations

The Endura network is based on switching and routing technologies. When planning an Endura network, you need to know and understand the difference between the traditional “Core” and “Intelligent Edge” network topology design approach.

• Traditional network design approach

The traditional network design topology is based on a central network core, which is responsible for all routing decisions. This approach requires the use of high-performance and high-cost core network equipment. This approach will work if the speciﬁed core switch is capable of managing all of the following:

– Making all of the unicast routing decisions

– Making all of the multicast routing decisions

– Handling all Endura network traffic: video, audio, PTZ, and UPnP

– Handling all other existing network traffic

This approach may meet your network design requirements. However this approach might not be as scalable as the intelligent edge design, because the volume of network trafﬁc can easily consume the capacity of the core switch.

If network expansion is a future goal, then the intelligent edge design offers a scalable networking solution.

• Intelligent edge design approach

The alternative to the traditional design is the intelligent edge design. This design is based on placing smart switches at the network edge, which reduces the need for a centralized core to make all routing decisions. Instead of a single core switch managing all of the routing and network trafﬁc decisions, in the intelligent edge design, processing is distributed across all managed switches. The intelligent edge design allows the network to scale because managed switches can be easily added to the network without burdening a single core switch. As compared to the traditional design, the intelligent edge design does not use the concept of a “core switch.”

8 C1640M-B (3/06)

Understanding the Endura Network Structure

The primary structure of an Endura network topology is organized into functional entities, which are called “blocks.” Grouping the functional entities into individual blocks provide the following beneﬁts:

• Blocks control and isolate trafﬁc.

• Block design can be physical or logical.

• Each block is separated by VLANs.

• Blocks help determine network requirements.

The block concept makes it easy to understand and implement the Endura network design.

• A Block: The A Block is functionally responsible for encoding, recording, and storage of the video streams entering the Endura network

(both live and playback video).

• B Block: The B Block is functionally responsible for decoding and displaying the video streams, as well as providing the control and

conﬁguration of all Endura components.

• Core Block: The Core Block is functionally responsible for Network layer 3 tasks, authentication and security, and interconnects the A and

B blocks.

• C Block: The C Block includes the entire block structure: A, B, and Core.

VLANS

UPnP

VLANs are an essential network topology requirement in the Endura network.

• Each Endura block is separated by VLANs.

• VLANs are groupings of switch ports creating different network segments for each group.

– Switches using VLANs create the same division of the network into separate broadcast domains are also a more cost-effective

solution.

– It is necessary to use a router when moving between VLANs.

• VLANs reduce the size of the broadcast domain.

• VLANs are used to managed and restrict Endura trafﬁc.

• VLANs operate at layer 2 of the Open System Interconnection (OSI) model.

• All VLANs should be assigned an IP address to support routing.

Endura uses UPnP to enable easy and dynamic connectivity between devices on a network. Devices may dynamically add themselves to a network without the need for user intervention or conﬁguration. UPnP also allows devices on the network to check in with each other periodically. This means the user can know which devices are available at any one time. If a device goes off line, users can be notiﬁed so the problem may be addressed quickly, with minimal down time.

UPnP trafﬁc stays isolated to VLANs because of Time-To-Live (TTL) settings. TTL determines how many network segments a packet can cross into before it is discarded. TTL for UPnP packets is set to 1 so that the UPnP packets do not cross out of their originating block. TTL for video packets is set much higher so that the video packets can traverse the entire network. For more information on TTL is used in the Endura network, refer to

Using TTL to Control Network Trafﬁc in Broadcast Domains on page 11.

C1640M-B (3/06) 9

ENDURA A BLOCK

The A Block is the most important design entity of the network. The A Block is functionally responsible for encoding, recording, and storage of the video streams entering the Endura network (both live and playback video).

The A Block is summarized as follows:

• Each A Block can support up to 48 Encoders and one NVR5100.

• Each A Block is assigned to a speciﬁc VLAN.

• The number of A Blocks is unlimited.

• Each A Block has only one NVR5100 for recording of video streams from all Encoders in the A Block. Additional storage is provided by SEB5000 storage expansion boxes.

Figure 1 shows the Endura components that comprise the A Block. The SEB5000 is shown directly connected to the NVR5100 using a patch cable. If multiple SEB5000s are required, you can use a dedicated, Pelco-approved gigabit Ethernet switch to expand the video storage of the NVR5100. For more information about connecting SEB5000s to the NVR5100, refer to Connecting the NVR5100 and SEB5000s on page 26 and

Connecting Multiple NVR5100s and SEB5000s on page 26.

A BLOCK

LAYER 2 SWITCH

ENCODER

NVR

SEB

INTERFACES WITH THE CORE BLOCK

Figure 1. A Block: Encoding, Recording, and Playback

BROADCAST DOMAINS AND VLANS

In a network, the logical area within which all devices can see each other’s broadcasts is referred to as a broadcast domain. Endura components generate multicast trafﬁc, which in some cases can be treated like broadcast trafﬁc, depending on the switch. For this reason, it is important to isolate these broadcasts and to create a separate broadcast domain for each Endura block on the network. The most efﬁcient approach is to use VLANS to separate the broadcast domains (refer to Figure 2).

A BLOCK

BROADCAST DOMAIN 1

VLAN 3

A BLOCK 1

LAYER 2 SWITCH

CORE SWITCH

LAYER 3 SWITCH

VLAN 1

B BLOCK

BROADCAST DOMAIN 2

VLAN 4

ENCODER

NVR

SEB

VLAN 3

Figure 2. Using VLANs to Segment the Network into Separate Broadcast Domains for Each Block

10 C1640M-B (3/06)

USING TTL TO CONTROL NETWORK TRAFFIC IN BROADCAST DOMAINS

In the Endura network, TTL is used to set the maximum amount of router hops that a packet is allowed to propagate through the network before the packet is discarded. Using TTL provides an effective method to determine how many broadcast domains a given packet can traverse.

• For Endura components (excluding the SM5000), the default TTL settings are as follows:

– UPnP trafﬁc: The TTL is set to 1. In this case, each block is assigned to a specific VLAN, keeping UPnP traffic isolated within that block

(refer to Figure 3).

– Video packets: The TTL is set to 3 so that the video packets can traverse the entire network.

• For the SM5000 in the Core Block, the default TTL setting is 4. In this case, the SM5000 Locator broadcasts can traverse across subnetworks to discover Endura components.

This approach ensures that two networking functions be efﬁciently accomplished:

• Each NVR5100 only records video streams from encoders from which it sees in its block. The NVR5100 sends a query with a TTL of 1, which means it will only discover devices on its VLAN.

• Unnecessary trafﬁc is eliminated from traversing across the Core Block.

Figure 3 illustrates how the broadcast trafﬁc is localized to A Block 1 in broadcast domain 1. In this case, the broadcast trafﬁc from VLAN 1 never traverses the network because TTL is decremented to 0 at the core switch and the packet is dropped.

A BLOCK

VLAN 3

ENCODER

NVR

SEB

LAYER 2 SWITCH

VLAN 3, TTL=1

CORE SWITCH

VLAN 1

TTL = 0

Figure 3. TTL Is Set to 1 in VLAN 2 and Keeps UPnP Trafﬁc Within the A Block

B BLOCK

VLAN 5

C1640M-B (3/06) 11

ENDURA B BLOCK

The Endura B Block generally determines the bandwidth requirements for the network. The B Block is functionally responsible for decoding and displaying the video streams, as well as providing the control and conﬁguration of all Endura components.

The B Block functionality is summarized as follows:

• Based on permissions, can view and control any camera on entire system

• Each B Block is assigned to a speciﬁc VLAN

• The B Block can be replicated any number of times (limited only by network capacity)

• Contains all viewing devices – NET5301R decoders – VCD5000 video console displays – WS5050 Endura Workstations (WS)

Figure 4 illustrates the B Block.

CORE SWITCH

VLAN 2

Figure 4. B Block: Decoding and Viewing Video

LAYER 2 SWITCH

VCD

DECODER

ENDURA TRAFFIC SUMMARY DETAILS

This section provides information that allows you to calculate the bandwidth requirements for the Endura network. The Endura trafﬁc details are summarized as follows:

• Maximum video stream from an NET5301T encoder is 5.0 Mbps plus overhead:

– Up to 3.0 Mbps total for both multicast live streams

• Up to 2 Mbps for stream 1 (4CIF)

• Up to 1 Mbps for stream 2 (CIF)

– Up to 2.0 Mbps for unicast recording stream

For information on calculating the bandwidth, refer to Calculating Bandwidth and Storage Requirements on page 13.

• 5.5 Mbps total with audio and data.

• Network utilization should always be ﬁgured for the worst-case scenario. For information on calculating the worse-case bandwidth, refer to

Calculating Bandwidth and Storage Requirements on page 13.

• Playback is not a stream, but a “burst” of data.

• Each NVR5100 has a 100 Mbps cap on playback data:

– The NVR5100 will use as much of 100 Mbps bandwidth as necessary to transmit the requested clip data.

– The NVR5100 will divide that 100 Mbps up among multiple playback requests if necessary.

• NVR5100 playback is unicast.

• Constant and frequent requests for playback video must be included when determining worse-case bandwidth.

NOTES:

• Live video trafﬁc is only steamed across the network when requested by a view station.

• Throughput needs to be calculated at various points on the network, depending on how many cameras are going to be viewed and at

what size.

12 C1640M-B (3/06)

CALCULATING BANDWIDTH AND STORAGE REQUIREMENTS

You must ensure that the B and C blocks are able to handle the worse-case bandwidth (BWC) requirements. The following examples describe how to calculate the worse-case bandwidth based on the playback video stream.

NOTE: Playback steams are used for calculating worse-case bandwidth requirements because each video stream is played back at the same rate that it was recorded, no matter in what layout mode the video stream is being displayed.

In contrast, when viewing live video, the Endura WS5050, VCD5000, and NET5301R use EnduraView to select the appropriate video stream automatically based on the layout mode.

• WS5050: The WS5050 pulls the highest value stream in either the single camera or quad layout mode.

• VCD5000: The VCD5000 pulls the lowest stream in quad layout mode.

• WS5050 or VCD5000: The WS5050 or VCD5000 pulls the lowest value stream in the 9- or 16-camera layout mode.

• NET5301R Encoder:

– The NET5301R pulls the highest value stream in the single layout mode.

– The NET5301R pulls the lowest value stream in the quad layout mode.

The following examples demonstrate that the playback video mode requires more bandwidth than does the live video mode. Typical applications do not require displaying the maximum amount of simultaneous playback streams. A more realistic application might require more live video streams are displayed than playback video streams. For this reason both playback and live video calculations are shown to aid in calculating bandwidth.

To ensure that your network resources are more than adequate to support the Endura system, it is recommended that you use the bit rate applicable for the playback video mode when calculating worse-case bandwidth requirements.

• For information on calculating bandwidth for the playback video mode, refer to Examples of Worse-Case Bandwidth Calculation in Playback

Mode on page 20.

• For information on calculating bandwidth for the live video mode, refer to Examples of Worse-Case Bandwidth Calculation in Live Video

Mode on page 21.

The worse-case bandwidth, BWC, requirements for live and playback video is given by the equation:

BWC = BW + O

where:

BW = Bandwidth and is given by the equation: BW = NS x B

OH = Overhead and is given by the equation OH = 25% x B

NS = Number of streams.

BR = Bit rate

The above equations are general and assume that all playback streams are of the same quality. For information about BR values, refer to NTSC

Frame Rates on page 14 and PAL Frame Rates on page 17.

W .

C1640M-B (3/06) 13

+ 29 hidden pages

Pelco C1640M-B User Manual

Contents

List of Illustrations

List of T ables

AUDIENCE

HOW TO USE THIS GUIDE

ENDURA OVERVIEW

ENDURA COMPONENTS

ENDURA PRODUCT SUPPORT

Network Architecture

PHYSICAL MEDIA

NETWORK PROTOCOLS

UNICAST ROUTING PROTOCOLS

MULTICAST ROUTING PROTOCOLS

INTERNET GROUP MANAGEMENT PROTOCOL

Endura Network Design Considerations

Understanding the Endura Network Structure

VLANS

UPnP

ENDURA A BLOCK

BROADCAST DOMAINS AND VLANS

USING TTL TO CONTROL NETWORK TRAFFIC IN BROADCAST DOMAINS

ENDURA B BLOCK

ENDURA TRAFFIC SUMMARY DETAILS

CALCULATING BANDWIDTH AND STORAGE REQUIREMENTS