Endura™ Network Design Guide Video Security System C1640M-B (3/06)
Contents Welcome to the Endura Network Design Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Illustrations 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 A Block: Encoding, Recording, and Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Using VLANs to Segment the Network into Separate Broadcast Domains for Each Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 TTL Is Set to 1 in VLAN 2 and Keeps UPnP Traffic Within the A Block . . . . . . . . . . . . . . .
Welcome to the Endura Network Design Guide Welcome to the Endura™ Network Design Guide. This document is specifically designed as a guide and reference source for designing Endura networks.
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 profiles dictate. Table A lists the Endura components.
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).
– Sparse Mode is most useful in the following instances: • There are few receivers in a group. Switches send multicast traffic only to the devices that request it. • Senders and receivers are separated by Local Area Network (LAN) links. • The type of traffic 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.
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 benefits: • Blocks control and isolate traffic. • 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.
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 specific VLAN. • The number of A Blocks is unlimited.
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 traffic: The TTL is set to 1.
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 configuration of all Endura components.
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.
NTSC Frame Rates This section describes the National Television System Committee (NTSC) frame rates at high, medium, and low resolution with a dual stream NET5301T encoder. You can select 6, 10, 15, and 30 IPS across all resolutions (CIF, 2CIF, and 4CIF) for each camera. Table B describes the expected performance at high resolution for NTSC frame rates. Table B.
Table C describes the expected performance at medium resolution for NTSC frame rates. Table C. Medium Resolution: NTSC Frame Rates with Dual Stream NET5301T Encoder Description Layout Mode C1640M-B (3/06) Stream/Device Medium Resolution and Supported Frame Rates 1 2 3 4 Stream 1 Bitrates Stream 1-I Stream 2 Birates Stream 2-I WS5050 VCD5000 2CIF/30 IPS 1.5 Mbps 2CIF/2 IPS CIF/15 IPS 800 Kbps CIF/2.5 IPS 2CIF/30 IPS 2CIF/30 IPS 2CIF/15 IPS 1.0 Mbps 2CIF/2.5 IPS CIF/15 IPS 800 Kbps CIF/2.
Table D describes the expected performance at low resolution for NTSC frame rates. Table D. Low Resolution: NTSC Frame Rates with Dual Stream NET5301T Encoder Description Layout Mode Stream/Device 16 Low Resolution and Supported Frame Rates 1 2 3 4 Stream 1 Bitrates Stream 1-I Stream 2 Birates Stream 2-I WS5050 VCD5000 CIF/30 IPS 1.2 Mbps CIF/2 IPS CIF/15 IPS 800 Kbps CIF/2.5 IPS CIF/30 IPS CIF/30 IPS CIF/15 IPS 800 Kbps CIF/2.5 IPS CIF/15 IPS 800 Kbps CIF/2.
PAL Frame Rates This section describes the Phase Alternating Line (PAL) frame rates at high, medium, and low resolution with a dual stream NET5301T encoder. You can select 5, 8.3, 12.5, and 25 IPS across all resolutions (CIF, 2CIF, and 4CIF) for each camera. Table E describes the expected performance at high resolution for PAL frame rates. Table E.
Table F describes the expected performance at medium resolution for PAL frame rates. Table F. Medium Resolution: PAL Frame Rates with Dual Stream NET5301T Encoder Description Layout Mode 18 Stream/Device Medium Resolution and Supported Frame Rates 1 2 3 4 Stream 1 Bitrates Stream 1-I Stream 2 Birates Stream 2-I WS5050 VCD5000 2CIF/25 IPS 1.5 Mbps 2CIF/2 IPS CIF/12.5 IPS 800 Kbps CIF/2.5 IPS 2CIF/25 IPS 2CIF/25 IPS 2CIF/12.5 IPS 1.0 Mbps 2CIF/2.5 IPS CIF/12.5 IPS 800 Kbps CIF/2.5 IPS 2CIF/12.
Table G describes the expected performance at low resolution for PAL frame rates. Table G. Low Resolution: PAL Frame Rates with Dual Stream NET5301T Encoder Description Layout Mode C1640M-B (3/06) Stream/Device Low Resolution and Supported Frame Rates 1 2 3 4 Stream 1 CIF/25 IPS CIF/12.5 IPS CIF/8.3 IPS CIF/5 IPS Bitrates 1.2 Mbps 800 Kbps 450 Kbps 350 Kbps Stream 1-I CIF/2 IPS CIF/2.5 IPS CIF/2 IPS CIF/2 IPS Stream 2 CIF/12.5 IPS CIF/12.5 IPS CIF/12.5 IPS CIF/12.
Examples of Worse-Case Bandwidth Calculation in Playback Mode NOTE: For the examples below, assume that all recorded video is at 4CIF (2 Mbps) at 30 IPS: • In this case, if playback video is displayed in the single layout mode, then the display rate is at 30 IPS. • However, if playback video is displayed in 4 x 4 layout mode, the display rate is at 2 IPS. In this case, the bandwidth is still 2 Mbps.
Examples of Worse-Case Bandwidth Calculation in Live Video Mode Example 1: WS5050 Endura Workstation—Live Video Stream Each WS5050 can display 16 simultaneous playback streams. To calculate the worse-case bandwidth for the WS5050: 1. Find the bandwidth. BW = NS x BR = 16 x 1 Mbps = 16 Mbps 2. Find the overhead. OH = 25% x BW = 16 x 1 Mbps x 25% = 4 Mbps 3. Find the worse-case bandwidth.
ENDURA CORE BLOCK The Core Block is functionally responsible for Network layer 3 tasks, discovery, authentication, and security, and interconnects the A and B blocks (refer to Figure 5). The Core Block is summarized as follows: • There is only one Core Block for each Endura network. • The Core Block contains the SM5000 and the redundant SM5000, which provides authentication and security for Endura network. • The Core Block is on its own VLAN.
ENDURA C BLOCK Figure 7 illustrates how the A, B, Core, and C Blocks concept is implemented to form a complete Endura network. The Endura network is scaled by replicating the A and B Blocks to accommodate the video input and performance requirements for the network application.
Table H. Endura Network Structures (Continued) Entity Function Network Devices Core Block The Core Block is functionally responsible for Network layer 3 tasks, authentication and security, and interconnects the A and B blocks. SM5000, redundant SM5000s, and a layer 3 switch The Core Block is summarized as follows: C Block • There is only one Core Block for each Endura network. • The Core Block provides authentication and security for Endura network. • The Core Block is on its own VLAN.
MANAGED NETWORK CONFIGURATION The managed Endura network supports viewing of live and playback video, recording, and security. As shown in Figure 9, a managed Endura network includes the full assortment of Endura components: NET5301Ts, NET5301Rs, WS5050s, VCD5000s, NVR5100s, the SM5000, and switches. The managed Endura network is designed in a four-part block structure (A Block, B Block, C Block, and Core Block). For more information about the block design concept, refer to Endura C Block on page 23.
Connecting the NVR5100 and SEB5000s The SEB5000 storage expansion box can be connected to the NVR5100 in one of two ways: • A patch cable is used to connect a single SEB5000 directly to an NVR5100 (refer to Figure 10). The NVR5100 and SEB5000 Ethernet port is autosensing. TO A BLOCK SWITCH NVR SEB Figure 10. Using a Patch Cable to Connect the NVR5100 and a Single SEB5000 • A dedicated, gigabit Ethernet switch can be used to expand the video storage of the NVR5100.
Appendix A: Endura Network Configuration Example This section provides an example of how to configure an HP 5300 series chassis switch for an Endura Network. The information is this section is only an example of how to configure an HP 5300 series chassis switch. Although this example is typical, other network configurations can support Endura. For more information about advanced configurations, refer to HP Advanced Traffic Management Guide at www.hp.com/go/procurve.
SETTING UP SWITCH A The following procedure is an example shows how to configure switch A from the HP 5300 series command line interface (CLI). To set up switch A: 1. Access the HP ProCurve switch command line interface (CLI), and log into the switch. The HP ProCurve Switch 5304XL# prompt is displayed. 2. Enter config to access the configuration mode. The HP ProCurve Switch 5304XL(config)# prompt is displayed. a. Enter ip routing to enable IP routing. b.
e. Enter ip pim to enable PIM on VLAN 3. f. Enter ip helper-address 10.3.0.10 to specify where to forward DHCP requests. (In this example, the SM5000 is providing DHCP service for the Endura network.) 7. Enter exit to exit the VLAN configuration mode. 8. Enter write memory to save your configuration. ) NOTE: The helper address in step 5f is not necessary since the system manager/DHCP server is on the same network.
f. Enter ip helper-address 10.3.0.10 to specify where to forward DHCP requests. (In this example, the SM5000 is providing DHCP service for the Endura network. 6. Enter exit to exit the VLAN configuration mode. 7. Enter write memory to save your configuration. EXAMPLE CONFIGURATION FILE FOR SWITCH B Figure 14 shows an example of the configuration file for switch B. ; J4850A Configuration Editor; Created on release #E.08.
Appendix B: WAN Configuration Example This appendix provides a sample configuration for multicasting over a generic routing encapsulation (GRE) tunnel as an example of how to configure an Endura network using WAN connectivity. Much of the information in this appendix is derived from the online document titled Multicasting Over a GRE Tunnel, published by Cisco Systems®. To view this document, go to or click http://www.cisco.com/en/US/tech/tk828/ technologies_configuration_example09186a00801a5aa2.shtml.
CITY A ROUTER (R102) CONFIGURATION FILE r102# version 12.2 ! hostname r102 ! ip subnet-zero no ip domain-lookup !--- It stops IP domain lookup, which improves the show command response time. ! ip multicast-routing !--- Enables IP multicast routing. ! interface Loopback0 ip address 2.2.2.2 255.255.255.255 !--- Tunnel Source interface. ! interface Tunnel0 !--- Tunnel interface configured for PIM and carrying multicast packets to R104. ! ip address 192.168.24.1 255.255.255.
CITY B ROUTER (R104) CONFIGURATION FILE r104# version 12.2 ! hostname r104 ! ip subnet-zero no ip domain-lookup ! !--- It stops IP domain lookup, which improves the show command response time. ! ip multicast-routing ! !--- Enables IP multicast routing. ! interface Loopback0 ip address 4.4.4.4 255.255.255.255 ! !--- Tunnel Source interface. ! interface Tunnel0 ip address 192.168.24.2 255.255.255.252 ! !--- Tunnel interface configured for PIM and carrying multicast packets.
ip mroute 2.2.2.2 255.255.255.255 tunnel 0 ! !--- This Mroute is required for RPF check when sparse mode multicast traffic is !--- flowing from RP (assuming R102 with 2.2.2.2 as RP) towards receiver via tunnel !--- before the SPT switchover. ! line con 0 line aux 0 line vty 0 4 login ! end VERIFYING THE CONFIGURATION Complete the following steps to verify your configuration: 1. Use the show ip igmp groups command to verify that the receiver has sent its IGMP join membership request for group 239.1.1.
3. Use the show ip mroute group-address command to verify that R104 has the (*,239.1.1.20) and (10.1.1.1, 239.1.1.20) entries while it is forwarding multicast packets for group 239.1.1.20 sourced from 10.1.1.1, as shown below. r104# show ip mroute 239.1.1.
TROUBLESHOOTING If your multicast over GRE tunnel is not working, one of the following could be the cause: • Tunnel not UP/UP: The tunnel source and destination do not match on each end of the tunnel. For example, if the tunnel destination on R102 was changed to the IP address 10.2.2.2 instead of 2.2.2.2 while the configuration on R104 remained the same, the tunnel would not come up. To verify the status of the tunnel, use the show interface tunnel 0 command.
Appendix C: Endura Network Requirements Worksheet The Endura Network Requirements Worksheet allows you to identify essential network resources that must be available to support the Endura system. It is recommended that you complete this worksheet before integrating the Endura system into a new or existing network. Please check all that apply.
C1640M-B (3/06)
Index Numerics 1000baseT 7 100baseT 7 4CIF 12 A A Block 10 B Block 12 C Block 23 Core Block 22 TTL, how used 11 EnduraStor 6 EnduraView 13 authentication 22 G B GRE tunnels 31 tunnels, troubleshooting 36 bandwidth, calculating for live video stream 21 for playback video stream 20 quad layout 13 worse-case 13 blocks as a design requirement 10 broadcast domains 10 description of A Block 10 B Block 12 C Block 23 Core Block 22 responsibility of each block 23 provides network structure 5 separated by VLAN
Endura network structure 9 intelligent edge 8 network designs, examples of 24 protocols 7 VLANs 9 NVR (network video recorder) 6 O Open Shortest Path.
REVISION HISTORY Manual # C1640M C1640M-A Date 7/05 12/05 C1640M-B 3/06 Comments Original version. The PC Workstation was renamed to WS5050 Endura Workstation. The VLAN references and descriptions in text and graphics on pages 10, 11, 17, and 19-24 were revised to clarify technical content. Updates the Calculating Bandwidth and Storage Requirements section to add new NTSC and PAL frame rates supported in Version 1.3 across all resolutions (CIF, 2CIF, and 4CIF).
Worldwide Headquarters 3500 Pelco Way Clovis, California 93612 USA USA & Canada Tel: 800/289-9100 Fax: 800/289-9150 International Tel: 1-559/292-1981 Fax: 1-559/348-1120 www.pelco.
