CME-5000 / CME-5010 CME-5100 / CME-5110 - …€¦ · B.3 802.1Q VLAN Support ... MENCAP products...

Copyright © Comtech EF Data, 2007. All rights reserved. Printed in the USA. Comtech EF Data, 2114 West 7th Street, Tempe, Arizona 85281 USA, 480.333.2200, FAX: 480.333.2161

CME-5000 / CME-5010 CME-5100 / CME-5110

Digicast DVB IP Micro Encapsulator (MENCAP) CME-5000 – Digicast MENCAP

CME-5010 – Digicast MENCAP 10K CME-5100/CME-5110 – 1:1 Redundancy

(with CME-1600 Redundancy Switch) Installation and Operation Manual

Part Number MN/MENCAPEDC.IOM Revision A

May 10, 2007

Comtech EF Data is an ISO 9001Registered Company

AGILE DOC ID ER-MENCAPEDC-EAA THIS DOCUMENT IS NOT SUBJECT TO REVISION/UPDATE! AGILE CO7331 1

Errata A Comtech EF Data Documentation Update

Subject: Changes to 4.2.10 Route Statistics, p. 4-19.

Date: March 13, 2009

Original Manual Part Number: MNMENCAPEDC.IOM Rev A

Errata Number / Agile Document ID: ER-MENCAPEDC-EAA Agile

CO Number: CO7331

Change Specifics:

This information will be incorporated into the next revision.

Min The Minimum MPE/IP encapsulated bandwidth for this route, since the statistics were last cleared.

Max

The Maximum MPE/IP encapsulated bandwidth for this route, since the statistics were last cleared.

Average

The Average MPE/IP encapsulated bandwidth for this route, over the last 10 seconds.

NOTE: The Statistics web page does not display statistics indicating the incoming bandwidth (bit rate).

AGILE DOC ID ER-MENCAPEDC-EAA THIS DOCUMENT IS NOT SUBJECT TO REVISION/UPDATE! AGILE CO7331 2

Notes:

Table of Contents

PREFACE.................................................................................................................................. VII

Customer Support.....................................................................................................................................vii

About this Manual ...................................................................................................................................viii Reporting Comments or Suggestions Concerning this Manual.............................................................viii

Related Documents ..................................................................................................................................viii

Conventions and References ..................................................................................................................... ix Cautions and Warnings............................................................................................................................ ix Metric Conversion ................................................................................................................................... ix Recommended Standard Designations ..................................................................................................... x Trademarks ............................................................................................................................................... x

Electromagnetic Compatibility (EMC) Compliance................................................................................ x Emissions Compliance ............................................................................................................................. x EN61000 Compliance............................................................................................................................... x

Safety Compliance ..................................................................................................................................... xi EN60950.................................................................................................................................................. xi Low Voltage Directive (LVD) ................................................................................................................ xi

Warranty Policy ........................................................................................................................................xii Limitations of Warranty .........................................................................................................................xii Exclusive Remedies...............................................................................................................................xiii

CHAPTER 1. INTRODUCTION...........................................................................................1–1

1.1 Introduction................................................................................................................................ 1–1

1.2 Standard Features...................................................................................................................... 1–2

1.3 Performance ............................................................................................................................... 1–3

1.4 MENCAP Redundancy (CME-5100 & CME-5110) ............................................................... 1–3 1.4.1 Introduction ......................................................................................................................... 1–4 1.4.2 Configuration ...................................................................................................................... 1–4 1.4.3 Operation............................................................................................................................. 1–4

1.5 Specifications.............................................................................................................................. 1–5

i

Digicast Micro Encapsulator (MENCAP) Revision A MN/MENCAPEDC.IOM

1.6 Terminology ............................................................................................................................... 1–8

CHAPTER 2. INSTALLATION & INITIAL CONFIGURATION.................................................2-1

2.1 Major Assembly ..........................................................................................................................2-1

2.2 Unpacking....................................................................................................................................2-2

2.3 Installation...................................................................................................................................2-3 2.3.1 Standalone Installation .........................................................................................................2-3 2.3.2 Redundancy Installation.......................................................................................................2-4

2.4 Initial Configuration...................................................................................................................2-5 2.4.1 Standalone Configuration.....................................................................................................2-5 2.4.2 Redundancy Configuration ..................................................................................................2-6

CHAPTER 3. INTERFACE PINOUTS.................................................................................3–1

3.1 Introduction................................................................................................................................ 3–1

3.2 MENCAP 50 (CME-5000 and CME-5010).............................................................................. 3–1 3.2.1 DC Power ............................................................................................................................ 3–1 3.2.2 RJ-12 Terminal.................................................................................................................... 3–2 3.2.3 RJ-12 Redundancy .............................................................................................................. 3–2 3.2.4 RJ-45 Ethernet ..................................................................................................................... 3–2 3.2.5 BNC ASI (Out-A and Out-B)............................................................................................. 3–2

3.3 CME-1600 Redundancy Switch................................................................................................ 3–3 3.3.1 DC Power ............................................................................................................................ 3–3 3.3.2 BNC ASI (Typical Out-A and Out-B) ............................................................................... 3–3 3.3.3 RJ-12 Primary Redundancy ................................................................................................ 3–3 3.3.4 BNC Primary ASI (Typical In-A and In-B)....................................................................... 3–4 3.3.5 RJ-12 Secondary Redundancy ............................................................................................ 3–4 3.3.6 BNC Secondary ASI (Typical In-A and In-B)................................................................... 3–4

CHAPTER 4. DEVICE MANAGEMENT VIA USER INTERFACES .....................................4-1

4.1 Introduction.................................................................................................................................4-1

4.2 Web Interface ..............................................................................................................................4-1 4.2.1 Administrative Configuration...................................................................................................4-2 4.2.2 Network Configuration ........................................................................................................4-4 4.2.3 Egress Configuration............................................................................................................4-5 4.2.4 PSI Configuration.................................................................................................................4-6

4.2.4.1 Option DVB-C NIT Submenu.....................................................................................4-8 4.2.4.2 Option DVB-S NIT Submenu .....................................................................................4-9 4.2.4.3 Option DVB-T NIT Submenu ...................................................................................4-10

4.2.5 SMPTE-325M Configuration.............................................................................................4-11 4.2.6 Route Configuration...........................................................................................................4-12

ii


4.2.7 Advanced Route Configuration..........................................................................................4-14 4.2.8 IGMP Configuration ..........................................................................................................4-16 4.2.9 Redundancy Configuration ................................................................................................4-17 4.2.10 Route Statistics...................................................................................................................4-18

4.3 Terminal Interface ....................................................................................................................4-19 4.3.1 Main Menu .........................................................................................................................4-20 4.3.2 Redundancy Configuration Menu ......................................................................................4-21 4.3.3 Administration Menu .........................................................................................................4-21

4.3.3.1 Port Number Configuration .......................................................................................4-21 4.3.4 Stats Menu..........................................................................................................................4-22

4.3.4.1 Route Stats Menu ......................................................................................................4-22 4.3.4.2 Ethernet Stats Menu ..................................................................................................4-23 4.3.4.3 DMA Stats Menu.......................................................................................................4-23

4.3.5 Egress Configuration Menu ...............................................................................................4-24 4.3.6 Network Configuration Menu ............................................................................................4-24 4.3.7 SMPTE 325M Configuration Menu...................................................................................4-25 4.3.8 Route Configuration Menu.................................................................................................4-25

4.3.8.1 Advanced Route Configuration Menu.......................................................................4-26 4.3.9 PSI Configuration Menu ....................................................................................................4-26 4.3.10 IGMP Configuration Menu ................................................................................................4-27

4.4 Telnet Interface .........................................................................................................................4-27

4.5 Trivial File Transfer Protocol (TFTP) ....................................................................................4-28

4.6 Simple Network Management Protocol (SNMP) ...................................................................4-29

APPENDIX A. SOFTWARE UPGRADE ............................................................................ A–1

A.1 Introduction............................................................................................................................... A–1

A.2 Web Interface ............................................................................................................................ A–2

A.3 Telnet or Terminal Interface ................................................................................................... A–3

APPENDIX B. IP ROUTING SUPPORT..............................................................................B-1

B.1 Introduction................................................................................................................................ B-1

B.2 Route Configuration .................................................................................................................. B-1 B.2.1 Unicast Routing................................................................................................................... B-1 B.2.2 Multicast Routing................................................................................................................ B-2

B.3 802.1Q VLAN Support .............................................................................................................. B-3

B.4 Section Packing .......................................................................................................................... B-3

B.5 1,024 Routes................................................................................................................................ B-4

iii


B.6 10,000 Routes.............................................................................................................................. B-4

B.7 Multicast Zones .......................................................................................................................... B-4

B.8 IP Copy ....................................................................................................................................... B-5

B.9 Quality of Service (QoS)............................................................................................................ B-5

B.10 MPE/IP ....................................................................................................................................... B-6

APPENDIX C. MENCAP 50 PRIVATE MIB ELEMENTS................................................... C–1

C.1 Admin Menu.............................................................................................................................. C–1

C.2 Network Menu........................................................................................................................... C–2

C.3 Egress Menu .............................................................................................................................. C–2

C.4 PSI Menu ................................................................................................................................... C–2 C.4.1 DVB-C NIT.........................................................................................................................C–3 C.4.2 DVB-S NIT .........................................................................................................................C–3 C.4.3 DVB-T NIT.........................................................................................................................C–4

C.5 SMPTE-325M Menu................................................................................................................. C–4

C.6 Routing Table ............................................................................................................................ C–5

C.7 Advanced Routing Table.......................................................................................................... C–6

C.8 IGMP Menu............................................................................................................................... C–7

C.9 Redundancy Menu.................................................................................................................... C–7

C.10 Statistics Table .......................................................................................................................... C–8

APPENDIX D. TROUBLESHOOTING ............................................................................... D–1

Tables Table 1-1. Digicast MENCAP 50 Specifications......................................................................................1–6 Table 1-2. Digicast MENCAP Redundancy – CME-1600 Switch Specifications....................................1–7 Table 2-1. Digicast MENCAP 50 Standalone Configuration ....................................................................2-1 Table 2-2. Digicast MENCAP Redundancy Configuration......................................................................2-1

iv


Figures Figure 1-1. Digicast MENCAP 50 – Front Panels.....................................................................................................1–1 Figure 1-2. Digicast MENCAP 50 (CME-5000 or CME-5010) ................................................................................1–3 Figure 1-3. Digicast MENCAP Redundancy (CME-5100 or CME-5110) ................................................................1–3 Figure 1-4. Digicast MENCAP Redundancy (CME-5100 or CME-5110) ................................................................1–4 Figure 1-5. Digicast MENCAP Redundancy (CME-5100 or CME-5110) ................................................................1–5 Figure 1-6. Digicast MENCAP 50 Rear Panel (typical)............................................................................................1–5 Figure 1-7. Digicast MENCAP 50 – CME-1600 Redundancy Switch......................................................................1–5 Figure 2-1. Digicast MENCAP Redundancy (CME-5100 or CME-5110) – Rear View ........................................... 2-2 Figure 2-2. LED Status of CME-1600 Redundancy Switch (after configuration)..................................................... 2-7 Figure 3-1. MENCAP 50 Connection Interfaces – Rear Panel (Typical) ..................................................................3–1 Figure 3-2. CME-1600 Redundancy Switch Connection Interfaces..........................................................................3–3 Figure 4-1. Connecting to the MENCAP 50.............................................................................................................. 4-1 Figure 4-2. Home (“Splash”) page ............................................................................................................................ 4-2 Figure 4-3. Administrative Configuration page......................................................................................................... 4-2 Figure 4-4. Network Configuration page................................................................................................................... 4-4 Figure 4-5. Egress Configuration page ...................................................................................................................... 4-5 Figure 4-6. PSI Configuration page........................................................................................................................... 4-6 Figure 4-7. PSI Configuration page – DVB-C NIT submenu option ........................................................................ 4-8 Figure 4-8. PSI Configuration page – DVB-S NIT submenu option......................................................................... 4-9 Figure 4-9. PSI Configuration page – DVB-T NIT submenu option....................................................................... 4-10 Figure 4-10.SMPTE-325M Configuration page ...................................................................................................... 4-11 Figure 4-11. Route Configuration page ................................................................................................................... 4-12 Figure 4-12. Advanced Route Configuration page .................................................................................................. 4-14 Figure 4-13. IGMP Configuration page................................................................................................................... 4-16 Figure 4-14. Redundancy Configuration page......................................................................................................... 4-17 Figure 4-15. Route Statistics reporting page............................................................................................................ 4-18 Figure 4-16. Terminal Menu Hierarchy................................................................................................................... 4-20 Figure 4-17. Main Menu.......................................................................................................................................... 4-20 Figure 4-18. Redundancy Configuration Menu ....................................................................................................... 4-21 Figure 4-19. Administration Menu .......................................................................................................................... 4-21 Figure 4-20. Stats Menu .......................................................................................................................................... 4-22 Figure 4-21. Route Stats Menu................................................................................................................................ 4-22 Figure 4-22. Ethernet Stats Menu............................................................................................................................ 4-23 Figure 4-23. DMA Stats Menu ................................................................................................................................ 4-23 Figure 4-24. Egress Configuration Menu ................................................................................................................ 4-24 Figure 4-25. Network Configuration Menu............................................................................................................. 4-24 Figure 4-26. SMPTE 325M Configuration Menu.................................................................................................... 4-25 Figure 4-27. Route Configuration Menu ................................................................................................................. 4-25 Figure 4-28. Advanced Route Configuration Menu ................................................................................................ 4-26 Figure 4-29. PSI Configuration Menu ..................................................................................................................... 4-26 Figure 4-30. IGMP Configuration Menu................................................................................................................. 4-27 Figure 4-31. Starting Telnet Session........................................................................................................................ 4-27 Figure 4-32. Main Menu via Telnet......................................................................................................................... 4-28 Figure A-1. TFTP Download (via Web)...................................................................................................................A–2 Figure A-2. TFTP Upgrade (via Terminal)...............................................................................................................A–3 Figure A-3. TFTP Upgrade Complete (via Terminal) ..............................................................................................A–4 Figure B-1. Multicast Mapping (IP to MAC) ............................................................................................................B-2 Figure B-2. Section Packing ………………………………………………………………………………….….…B-3

v


This page is deliberately left blank.

vi

Preface

Customer Support

Contact the Comtech EF Data Customer Support Department for:

• Product support or training • Reporting comments or suggestions concerning manuals • Information on upgrading or returning a product

A Customer Support representative may be reached at:

Comtech EF Data Attention: Customer Support Department 2114 West 7th Street Tempe, Arizona 85281 USA

480.333.2200 (Main Comtech EF Data number) 480.333.4357 (Customer Support Desk) 480.333.2161 FAX

To return a Comtech EF Data product (in-warranty and out-of-warranty) for repair or replacement:

• Contact the Comtech EF Data Customer Support Department. Be prepared to supply the Customer Support representative with the model number, serial number, and a description of the problem.

• Request a Return Material Authorization (RMA) number from the Comtech EF Data Customer Support representative.

• Pack the product in its original shipping carton/packaging to ensure that the product is not damaged during shipping.

• Ship the product back to Comtech EF Data. (Shipping charges should be prepaid.) For Online Customer Support:

An RMA number request can be requested electronically by contacting the Customer Support Department through the online support page at www.comtechefdata.com/support.asp:

• Click on “Return Material Authorization” for detailed instructions on our return procedures.

• Click on the “RMA Request Form” hyperlink, then fill out the form completely before sending.

• Send e-mail to the Customer Support Department at [email protected]. For information regarding this product’s warranty policy, refer to the Warranty Policy, p. xii

vii

http://www.comtechefdata.com/support.asp

mailto:[email protected]

Digicast Micro Encapsulator (MENCAP) Revision A Preface MN/MENCAPEDC.IOM

About this Manual

This manual provides installation and operation information, functional capabilities, and performance specifications for the Comtech EF Data (CEFD) Digicast Micro Encapulsator (MENCAP) product lines: The CME-5000 MENCAP 50, CME-5010 MENCAP 50 10K, and CME-5100 & CME-5110 MENCAP Redundancy. This publication additionally provides information on how to connect these Digicast MENCAP products to other data transport equipment. This is a technical document intended for earth station engineers, technicians, and operators responsible for the operation and maintenance of the Digicast MENCAP product lines.

Reporting Comments or Suggestions Concerning this Manual

Comments and suggestions regarding the content and design of this manual are appreciated. To submit comments, please e-mail the Comtech EF Data Technical Publications Department at [email protected].

Related Documents

The following documents are listed for reference:

• A/53 ATSC Digital Television Standard

• A/65 ATSC Program and System Information Protocol for Terrestrial Broadcast and Cable Standard

• A/90 ATSC Data Broadcast Standard

• A/92 ATSC Delivery of IP Multicast Sessions over ATSC Data Broadcast

Standard

• ETSI EN 300 468 – Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB Systems

• ETSI EN 301 192 – Digital Video Broadcasting (DVB); DVB Specification for

Data Broadcasting

• ETSI EN 50083-9 – European Standard Cable Networks for Television Systems, Sound Signals and Interactive Services: Part 9 Interfaces for CATV/SMATV Headends and Similar Professional Equipment for DVB/MPEG-2 Transport Streams

• IEEE 802.3 – Telecommunications and Information Exchange Between Systems –

Local and Metropolitan Networks Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specification

viii

mailto:[email protected]


• ISO/IEC 13818-1 Information Technology – Generic Coding of Moving Pictures

and Associated Audio: Systems. Recommendation H.222.0 Part 1

• ISO/IEC 13818-6 Information Technology – Generic Coding of Moving Pictures and Associated Audio: Extensions for DSM-CC. Recommendation H.222.0 Part 6

• SMPTE 325M Digital Television: 1999 – Opportunistic Data Broadcast Flow

Control

Conventions and References

Cautions and Warnings

IMPORTANT or NOTE indicates a statement that is associated with the task being performed or information critical for proper equipment function.

IMPORTANT

CAUTION indicates a hazardous situation that, if not avoided, may result in minor or moderate injury. CAUTION may also be used to indicate other unsafe practices or risks of property damage.

WARNING indicates a potentially hazardous situation that, if not avoided, could result in death or serious injury.

\

Examples of Multi-Hazard Formats

Metric Conversion

Metric conversion information is located on the inside back cover of this manual. This information is provided to assist the operator in cross-referencing non-Metric to Metric conversions.

ix


Recommended Standard Designations

Recommended Standard (RS) Designations are interchangeable with the designation of the Electronic Industries Association (EIA).

Trademarks

Windows is a trademark of the Microsoft Corporation. Other product names mentioned in this manual may be trademarks or registered trademarks of their respective companies and are hereby acknowledged. Comtech EF Data neither endorses nor otherwise sponsors any such production or services referred herein.

Electromagnetic Compatibility (EMC) Compliance

This is a Class B product. In a domestic environment, it may cause radio interference that requires the user to take adequate protection measures.

Emissions Compliance

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the Federal Communications Commision (FCC) rules, and EN55022 Class B requirements.

These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.

EN61000 Compliance

This equipment meets the EMC/immunity characteristics for the limits and methods of measurement for information technology equipment as per EN61000-4-2, EN61000-4-3, EN61000-4-4, EN61000-4-5 and EN61000-4-11. This equipment meets the EMC/immunity characteristics for the limits and methods of measurement of mains harmonics & flicker for information technology equipment as per EN61000-3-2 and EN61000-3-3.

x


Safety Compliance

EN60950

Applicable testing is routinely performed as a condition of manufacturing on all units to ensure compliance with safety requirements of EN60950.This equipment meets the Safety of Information Technology Equipment specification as defined in EN60950.

Low Voltage Directive (LVD)

The following information is applicable for the European Low Voltage Directive (EN60950):

<HAR> Type of power cord required for use in the European Community.

!

CAUTION: Double-pole/Neutral Fusing ACHTUNG: Zweipolige bzw. Neutralleiter-Sicherung

International Symbols:

Symbol Definition Symbol Definition

~ Alternating Current

Protective Earth / Safety Ground

Fuse

Chassis Ground

NOTE

For additional symbols, refer to Cautions and Warnings listed earlier in this Preface.

xi


Warranty Policy

Comtech EF Data products are warranted against defects in material and workmanship for a period of two years from the date of shipment. During the warranty period, Comtech EF Data will, at its option, repair or replace products that prove to be defective. For equipment under warranty, the owner is responsible for freight to Comtech EF Data and all related customs, taxes, tariffs, insurance, etc. Comtech EF Data is responsible for the freight charges only for return of the equipment from the factory to the owner. Comtech EF Data will return the equipment by the same method (i.e., Air, Express, Surface) as the equipment was sent to Comtech EF Data. All equipment returned for warranty repair must have a valid RMA number issued prior to return and be marked clearly on the return packaging. Comtech EF Data strongly recommends all equipment be returned in its original packaging. Comtech EF Data Corporation’s obligations under this warranty are limited to repair or replacement of failed parts, and the return shipment to the buyer of the repaired or replaced parts.

Limitations of Warranty

The warranty does not apply to any part of a product that has been installed, altered, repaired, or misused in any way that, in the opinion of Comtech EF Data Corporation, would affect the reliability or detracts from the performance of any part of the product, or is damaged as the result of use in a way or with equipment that had not been previously approved by Comtech EF Data Corporation. The warranty does not apply to any product or parts thereof where the serial number or the serial number of any of its parts has been altered, defaced, or removed. The warranty does not cover damage or loss incurred in transportation of the product. The warranty does not cover replacement or repair necessitated by loss or damage from any cause beyond the control of Comtech EF Data Corporation, such as lightning or other natural and weather related events or wartime environments. The warranty does not cover any labor involved in the removal and or reinstallation of warranted equipment or parts on site, or any labor required to diagnose the necessity for repair or replacement.

xii


The warranty excludes any responsibility by Comtech EF Data Corporation for incidental or consequential damages arising from the use of the equipment or products, or for any inability to use them either separate from or in combination with any other equipment or products. A fixed charge established for each product will be imposed for all equipment returned for warranty repair where Comtech EF Data Corporation cannot identify the cause of the reported failure.

Exclusive Remedies

Comtech EF Data Corporation’s warranty, as stated is in lieu of all other warranties, expressed, implied, or statutory, including those of merchantability and fitness for a particular purpose. The buyer shall pass on to any purchaser, lessee, or other user of Comtech EF Data Corporation’s products, the aforementioned warranty, and shall indemnify and hold harmless Comtech EF Data Corporation from any claims or liability of such purchaser, lessee, or user based upon allegations that the buyer, its agents, or employees have made additional warranties or representations as to product preference or use. The remedies provided herein are the buyer’s sole and exclusive remedies. Comtech EF Data shall not be liable for any direct, indirect, special, incidental, or consequential damages, whether based on contract, tort, or any other legal theory.

xiii


Notes:

xiv

Chapter 1. INTRODUCTION

CME-5000 (MENCAP 50) CME-5010 (MENCAP 50 10K)

Figure 1-1. Digicast MENCAP 50 – Front Panels

1.1 Introduction

The Comtech EF Data (CEFD) Digicast Micro Encapsulator – referred to throughout this manual as “the MENCAP 50” – is the most economical IP Encapsulator (IPE) available in the market today and provides unparalleled price versus performance. The MENCAP 50 encapsulates Ethernet/IP Unicast or Multicast packets, as specified by DVB Multiprotocol Encapsulation (MPE) recommendation (documented in ETSI EN 301 192) and formats the sections into MPEG-2 transport packets for transmission over an Asynchronous Serial Interface (ASI) link.

11

Digicast Micro Encapsulator (MENCAP) Revision A Introduction MN/MENCAPEDC.IOM

The MENCAP 50 is available in the following configurations:

• CME-5000 Digicast MENCAP 50 Standalone Unit

• CME-5010 Digicast MENCAP 50 10K Standalone Unit with 10,000 IP route capability

• Digicast MENCAP 1:1 Redundancy configurations: o CME-5100 features two CME-5000 units o CME-5110 features two CME-5010 units o CME-1600 Redundancy Switch featured in both configurations

1.2 Standard Features

Based on an embedded architecture, utilizing a MIPS CPU and eCOS Operating System, the MENCAP 50 provides the following features:

• High Reliability – supports 1:1 redundancy • Support for Multicast and Unicast IP datagrams • MPE Section Packing and Non-Section Packing on a route-by-route basis • Support for all valid PIDs in 8192 range • Support for Promiscuous Mode • Multicast Zones • IP Copy • 1,024 Routes • Support for 10,000 Routes (with CME-5010 MENCAP 50 10K option) • QoS on a route-by-route basis (min/max bandwidth) • MPEG-2 188/204-byte operation • Aggregate throughput of 73 Mbps with 1,500 byte IP packets • Maximum configurable egress rate 85Mbps • Program Specific Information (PSI) - PAT/PMT support • NIT support for DVB-T, DVB-C, DVB-S • Basic ATSC Tables • ATSC A/90 data broadcast • ATSC A/92 IP multicast over ATSC data broadcast • SMPTE 325M • TCP to UDP for Kencast Fazzt Guaranteed File Broadcast (GFB) • IGMP for Multicast Route Announcements • Configurable Telnet and HTTP ports for security • Color LEDs for status monitoring and rapid fault isolation • Support for 802.1Q VLAN Tags • Management (monitor, control and configuration):

o Web Interface o Terminal Interface o Telnet o TFTP for remote field software/firmware upgrade o SNMP V2 (Private and MIB II) Support

12


Figure 1-2. Digicast MENCAP 50 (CME-5000 or CME-5010)

1.3 Performance

The MENCAP 50 provides the following performance characteristics:

Item Value

Maximum Egress Rate Setting 85 Mbps 188-Byte Mode and 67.2 Mbps 204-Byte Mode

Maximum Packets per Seconds (Minimum Packet Size 64 Bytes)

15,000 PPS

Maximum Bits Per Second (Maximum Packet Size 1,518 Bytes)

73 Mbps 188-Byte Mode and 67.2 Mbps 204-Byte Mode (with a maximum burstable rate of 80 Mbps)

Egress Clock Accuracy Better than +/- 1 Kbps (KHz)

Latency Less than 10 ms

1.4 MENCAP Redundancy (CME-5100 & CME-5110)

Figure 1-3. Digicast MENCAP Redundancy (CME-5100 or CME-5110)

13


1.4.1 Introduction

The MENCAP 50 supports a 1:1 redundant configuration in a single 19” rack (1RU) chassis (Figure 1-4). This provides for automatic failover in the event of failure of the Primary Encapsulator. For networks with high availability demands, the redundant package provides a cost-effective solution.

1.4.2 Configuration

The redundant unit consists of two MENCAP 50’s (CME-5000 or CME-5010) connected to and monitored by a CME-1600 Redundancy Switch. The mirrored ASI outputs of each MENCAP 50 are connected to the Redundancy Switch and based on the ‘primary/ secondary’ status of each encapsulator; the primary unit is allowed to pass traffic to the next device in the communications path. In addition to the ASI outputs, the MENCAP 50’s are each connected to the Redundancy Switch via a serial RS-232 interface to communicate operational status to the redundancy switch. The Ethernet ports are connected to a hub or switch on the LAN.


1.4.3 Operation

The design of the CME-1600 Redundancy Switch ensures high reliability and low probability of single point of failure. The CME-1600 monitors the status of the primary and secondary MENCAP 50 IPEs and, in the unlikely event of primary failure, will switch over the communications path to the secondary unit. The status of an IPE is indicated by the corresponding LED; namely, solid green indicating operational, flashing green indicating failed. The CME-1600 detects when a failed IPE has been restored to operational status. The CME-1600 can be configured to operate in “Auto” or “Manual” modes. In Auto mode, the CME-1600 detects a failed IPE and switches automatically to the backup; in Manual mode, the automatic failover feature is disabled. A pushbutton-activated switchover is required to activate the backup IPE.

14



1.5 Specifications

Table 1-1 outlines the technical specifications for both MENCAP 50 standalone units. Table 1-2 describes the CME-1600 Redundancy Switch specifications. For detailed MENCAP 50 and Redundancy Switch connector pin assignment information, refer to Chapter 3 – Interface Pinouts.

Figure 1-6. Digicast MENCAP 50 Rear Panel (typical)

a) Side Panel – Secondary b) Rear Panel c) Side Panel – Primary

Figure 1-7. Digicast MENCAP 50 – CME-1600 Redundancy Switch

15


Table 1-1. Digicast MENCAP 50 Specifications

Parameter Specification Dimensions 7.125 L x 8.125 W x 1.72 H (18.1L x 20.6W x 4.4H cm) Weight < 6 lbs (2.7 kg) Power 2.5 mm with screw type connector

ASI Copper Output Dual Mirrored BNC (75Ω) Ethernet (10/100BaseT) RJ-45

Terminal Redundancy

RJ-12

Blue PWR Power Red ALARM Alarm Green M-ACT MPE data activity Amber E-ACT Ethernet traffic/activity

Physical

LEDs

Green E-LINK Ethernet connection to hub/switch operational Power Input / Consumption 48 to 248 VAC 50/60 Hz converted to +5VDC @ 2.5A / < 7 W

ASI (Copper) EN50083-9 Ethernet (10/100BaseT) IEEE 802.3u

Console RS-232

Electrical

Redundancy RS-232 Temperature

Operating 32° to 104° Farenheit (0° to 40° Celsius) Storage (Non-operating) -22° to 150° Farenheit (-30° to 65° Celsius)

Humidity Operating 10% to 75% Non-condensing Storage

Relative humidity to 95% with temperature ≤ 95° Farenheit (35° Celsius) (Non-operating) Altitude Operating Up to 10,000 feet (3048 m) above sea level

Environmental

Storage Survival up to 50,000 feet (15240 m) above sea level for up to 15 hours (Non-operating)

16


Table 1-2. Digicast MENCAP Redundancy – CME-1600 Switch Specifications

Parameter Specification

Dimensions (Switch only) 12.5 L x 2.75 W x 1.75 H (31.8 L x 7 W x 4.4 H cm) (RU1)

Weight 2.4 lbs. (1.1 kg) Power 2.5 mm with screw type connector ASI Copper Input (2X) ASI Copper Output

Dual Mirrored BNC (75Ω)

Redundancy (2X) RJ-12 Blue PWR Power Green PRI Primary Green AUTO Auto Redundancy mode Green SEC Secondary

LEDs (Switch only)

Red ALARM Alarm PRI Primary - force primary online AUTO Fully redundant operation

Physical

Pushbuttons (Switch only)

SEC Secondary force secondary online Power Input / Consumption 48 to 248 VAC 50/60 Hz converted to +5VDC @ 2.5A / < 3W

ASI EN50083-9 Ethernet (10/100BaseT) IEEE 802.3u

Electrical

Redundancy RS-232 Temperature

Operating 32° to 104° Farenheit (0° to 40° Celsius) Storage

-22° to 150° Farenheit (-30° to 65° Celsius) (Non-operating) Humidity Operating 10% to 75% Non-condensing

Storage (Non-operating) Relative humidity to 95% with temperature ≤ 95° Farenheit (35° Celsius)

Altitude

Environmental

Operating Up to 10,000 feet (3048 m) above sea level Storage (Non-operating) Survival up to 50,000 feet (15240 m) above sea level for up to 15 hours

17


1.6 Terminology

The following table defines the acronyms referred to throughout this manual:

Acronym Definition ASI Asynchronous Serial Interface ATSC Advanced Television Systems

Committee BNC Bayonet Nut Connector CEFD Comtech EF Data Corporation CIDR Classless Inter-Domain Routing CPU Central Processing Unit DHCP Dynamic Host Configuration

Protocol DTE Data Terminal Equipment DVB Digital Video Broadcasting EN Norme European (European

Standard) ETSI European Telecommunications

Standards Institute IEEE Institute for Electrical and

Electronics Engineers GUI Graphical User Interface HTML HyperText Markup Language HTTP HyperText Transport Protocol IANA Internet Assigned Number

Authority ICMP Internet Control Message

Protocol IGMP Internet Group Management

Protocol IP Internet Protocol IPE IP Encapsulator IRD Integrated Receiver Decoder LAN Local Area Network LED Light Emitting Diode MAC Medium Access Control

Acronym Definition Mbps Mega bits per second MENCAP Micro Encapsulator MGT Master Guide Table MIB Management Information Base MPE Multiprotocol Encapsulation MPEG Moving Pictures Experts Group NIC Network Interface Card NIT Network Information Table ODI Opportunistic Data Insertion OID Object Identifier OS Operating System PAT Program Association Table PID Program Identifier PMT Program Map Table PSI Program Specific Information QoS Quality of Service RMA Return Materials Authorization RSW Redundancy Switch SI Service Information SM Subnet Mask SMPTE Society of Motion Picture &

Television Engineers SNMP Simple Network Management

Protocol TCP Transmission Control Protocol TFTP Trivial File Transfer Protocol UDP User Datagram Protocol VCT Virtual Channel Table VLAN Virtual Local Area Network

18

Chapter 2. INSTALLATION & INITIAL CONFIGURATION

2.1 Major Assembly

The MENCAP 50 is available in two configurations - standalone and redundant.

Table 2-1 lists the components provided with a standalone configuration; Table 2-2 lists the components provided with a redundant configuration. In the event any listed item is missing, please contact Comtech EF Data Customer Support.

Table 2-1. Digicast MENCAP 50 Standalone Configuration Quantity Description

1 CME-5000 MENCAP 50 or CME-5010 MENCAP 50 10K

1 SPU24-102 Power Supply 1 IEC AC Power Cord 1 CA-TERMINAL Terminal Cable 1 CD (includes this manual and the Quick Start reference) 1 Quick Start Sheet

Table 2-2. Digicast MENCAP Redundancy Configuration Quantity Description

FOR CME-5100: CME-5000 MENCAP 50 2 FOR CME-5110: CME-5010 MENCAP 50 10K

1 CME-1600 Redundancy Switch 1 TR-1600 19” Rack-mounted shelf with device mounting hardware 3 SPU24-102 Power supply 3 IEC AC Power Cord 4 BNC-to-BNC cable 2 RJ-12-to-RJ-12 cable 2 CA-TERMINALTerminal Cable 1 CD (includes this manual and the Quick Start reference) 1 Quick Start Sheet

2-1

Digicast Micro Encapsulator (MENCAP) Revision A Installation & Initial Configuration MN/MENCAPEDC.IOM

Figure 2-1. Digicast MENCAP Redundancy (CME-5100 or CME-5110) – Rear View

2.2 Unpacking

The shipping container and packing materials should be retained for possible reshipment. Perform a receiving inspection as follows:

• Inspect the shipping container for damage. If there is damage to the shipping container, notify the carrier.

• Check to determine that all parts, materials and documentation have been shipped

with the IPE.

• Inspect the IPE for possible physical damage.

• Test the IPE for proper operation.

• Contact Comtech EF Data Customer Support if the shipment is:

! Incomplete ! Physically damaged ! Inoperable

2-2


2.3 Installation

2.3.1 Standalone Installation

The MENCAP 50 (CME-5000 or CME-5010) is designed for ease of installation and configuration. Once the unit has been removed from the packing container, please follow these instructions: Step Procedure

1 NOTE

The port labeled REDUN is not utilized with standalone configurations – it is utilized in the MENCAP Redundancy configuration only.

2 Place the MENCAP 50 on a flat surface with free-air flow where the LEDs can be clearly observed with unrestricted access to the rear panel of the unit.

3 Connect the DC power connection to the connection labeled PWR on the back of the unit and tighten the restraining nut to ensure secure operation.

4 Connect an RJ-45 Ethernet cable (patch cord) to the port labeled ETHERNET. This cable should be connected to an Ethernet concentrator (hub) or switch.

5 Connect a terminal cable (supplied) to the port labeled TERM. This cable should be connected to a PC’s serial port (DB-9) to initially configure the MENCAP 50.

6 Connect the AC power cord between a standard wall outlet and the power supply. The blue LED will illuminate.

7

IMPORTANT

It is recommend that the ASI cable NOT be connected until the unit has been completely configured.

Upon startup, the following LEDs will illuminate on the MENCAP 50 front panel: LED Function Label Description Blue POWER LED illuminates if power is properly applied

Red ALARM LED may illuminate since the unit is not yet configured

Green M-ACT LED illuminates if MPE data is present Amber E-ACT LED flashes if there is Ethernet traffic/activity

8

Green E-LINK LED illuminates if Ethernet connection to the Hub/Switch is operational

2-3

Digicast Micro Encapsulator (MENCAP) Revision A Installation & Initial Configuration MN/MENCAPEDC.IOM 2.3.2 Redundancy Installation

The MENCAP 50 Redundancy (CME-5100 or CME-5110) is designed for ease of installation and configuration. Once the unit has been removed from the packing container, please follow these instructions:

Step Procedure

1 Place the MENCAP Redundancy configuration into a rack. This configuration requires a single rack unit (1RU) in a standard 19” rack enclosure.

2 Connect an RJ-45 Ethernet cable (patch cord) to the port labeled ETHERNET on the Primary unit and Secondary unit (left and right, respectively, looking at the front). These cables should connected to an Ethernet concentrator (hub) or switch.

3 Connect a terminal cable (supplied) to the port labeled TERM. This cable should be connected to a PC’s serial port (DB-9) to initially configure the MENCAP 50.

4 Connect the AC power cords between a standard wall outlet and the power supply. The Blue LEDs will illuminate on both MENCAP 50 chassis and the CME-1600 Redundancy Switch chassis.

5

IMPORTANT

It is recommend that the ASI cable NOT be connected until the unit has been completely configured.

Upon startup, the following LEDs will illuminate on the MENCAP 50 front panels: LED Function Label Description Blue POWER LED illuminates if power is properly applied

Red ALARM LED may illuminate since the unit is not yet configured

Green M-ACT LED illuminates if MPE data is present Amber E-ACT LED flashes if there is Ethernet traffic/activity

6

Green E-LINK LED illuminates if Ethernet connection to the Hub/Switch is operational

Concurrently upon startup, the following LEDs will illuminate on the CME-1600 Redundancy Switch front panel:

LED Function Label Description Blue POWER LED illuminates if power is properly applied

Green PRI LED illuminates if PRIMARY unit is enabled (default)

Green AUTO LED flashes if unit is in AUTO configuration (default)

Green SEC LED illuminates if SECONDARY unit is enabled

7

Red ALARM LED should not illuminate

2-4


2.4 Initial Configuration

2.4.1 Standalone Configuration

The initial configuration involves setting up the IP parameters via the terminal cable.

Once the IP parameters have been configured, the terminal cable can be removed and should be stored in a known location, since it may be needed in the future.

To configure the IP parameters: Step Procedure

1 Using a terminal emulator on a PC such as HyperTerminal™ or TeraTerm™, set up the communication port as follows:

• 38,400 BAUD • 8 Data Bits • 1 Stop Bit • No Parity • No Flow Control

2 Press the <ENTER> key on the PC – the MENCAP 50’s menu should be displayed.

3 Press “N” for Network Menu. 4 Press “I” for the IP Address, Enter the IP Address and press <ENTER>. 5 Press “M” for the Subnet Mask. Enter the Subnet Mask and press <ENTER>. 6 Press “G” for the Default Gateway IP Address. Enter the Default Gateway

Address and press <ENTER>.

7 Press “S” to save the parameters.

8 Press “X” to exit to the main menu.

9 Press “E” to configure the egress port.

10 Press “C” to configure the egress clock rate. Enter the egress rate in megabits per second (Mbps) and press <ENTER>.

11 Press “F” to toggle between 188 or 204 byte egress mode.


13 Press “X” to exit the menu.

At this point, the unit has been configured for basic operation and the terminal cable may be removed. The ASI cable may now be safely attached to one of the two (mirrored) output ports. For continued operation the unit may be managed via the Terminal Interface; however, it is recommended to use the Web Interface for ease of management.

2-5

Digicast Micro Encapsulator (MENCAP) Revision A Installation & Initial Configuration MN/MENCAPEDC.IOM 2.4.2 Redundancy Configuration

The initial configuration involves setting up the IP parameters via the terminal cable. The MENCAP Redundancy comes preconfigured – simply configure the IP address for both the Primary and Secondary units.

Once the IP parameters have been configured, the terminal cable can be removed and should be stored in a known location, since it may be needed in the future.

To configure the IP parameters: Step Procedure

1 Using a terminal emulator on a PC such as HyperTerminal™ or TeraTerm™, set up the communication port as follows:

• 38,400 BAUD • 8 Data Bits • 1 Stop Bit • No Parity • No Flow Control

2 Press the <ENTER> key on the PC – the MENCAP 50’s menu should be displayed.

3 Press “N” for Network Menu. 4 Press “I” for the IP Address. Enter the IP Address and press <ENTER>. 5 Press “M” for the Subnet Mask. Enter the Subnet Mask and press <ENTER>. 6 Press “G” for the Default Gateway IP Address. Enter the Default Gateway

Address and press <ENTER>.

7 Press “S” to save the parameters, then press <ENTER> to confirm the changes.


9 Press “Y” to edit the redundancy information.

10 Press “1” to enter the Backup unit IP address. Press <ENTER> when finished.

11 Press “2” to check for the Backup unit MAC address – it should already be there. Press <ENTER> to confirm the selection.

12 Press “M” to set mode “Primary for Left unit Backup for Right unit,” then press <ENTER> to confirm the selection.

13 Press “S” to save the parameters, then press <ENTER> to confirm the changes.


15 Press “E” to configure the egress port.

16 Press “C” to configure the egress clock rate.

17 Enter the egress rate in megabits per second (Mbps) and press <ENTER>.

18 Press “P” to configure PSI parameter only if needed. The default selection is NO.




22 Repeat steps 1 through 14 in this section to configure the Backup (secondary) unit.

2-6


Figure 2-2 shows the LED status displayed on the CME-1600 Redundancy Switch once the unit has been configured for basic operation.

Figure 2-2. LED Status of CME-1600 Redundancy Switch (after configuration)

At this point, the unit has been configured for basic operation and the terminal cable may be removed. The ASI cable may now be safely attached to one of the two (mirrored) output ports. For continued operation the unit may be managed via the Terminal Interface; however, it is recommended to use the Web Interface for ease of management.

Blue POWER Power normally on

Green PRI Primary unit normally on

Green AUTO

Auto Redundancy mode normally on

Green SEC Secondary unit normally off

LEDs

Red ALARM Alarm normally off

2-7


2-8

Notes:

Chapter 3. INTERFACE PINOUTS

3.1 Introduction

The rear panel interface (Figures 3-1 and 3-2) provides all necessary external connections between the MENCAP 50 and other equipment, in both standalone and redundant configurations.

3.2 MENCAP 50 (CME-5000 and CME-5010)

Figure 3-1. MENCAP 50 Connection Interfaces – Rear Panel (Typical)

3.2.1 DC Power

Pin Definition

Center +5VDC Outer Ring GND

3–1

Digicast Micro Encapsulator (MENCAP) Revision A Interface Pinouts MN/MENCAPEDC.IOM

3.2.2 RJ-12 Terminal

Pin Definition 1 GND 2 TXD 3 RXD 4 GND 5 N/C 6 N/C

3.2.3 RJ-12 Redundancy

Pin Definition 1 GND 2 TXD 3 RXD 4 GND 5 N/C 6 N/C

3.2.4 RJ-45 Ethernet

Pin Definition 1 TXD+ 2 TXD- 3 RXD+ 4 N/C 5 N/C 6 RXD- 7 N/C 8 N/C

3.2.5 BNC ASI (Out-A and Out-B)

Pin Definition

Center 8B/10B 270 Mbps Outer Ring GND

Interface connection OUT-A is used for the Standalone and Redundancy – Primary configurations. Use of interface connection OUT-B is reserved only for Redundancy – Secondary configurations. NOTE

3–2


3.3 CME-1600 Redundancy Switch

Figure 3-2. CME-1600 Redundancy Switch Connection Interfaces

a) Rear Panel

c) Side Panel – Primary b) Side Panel – Secondary

3.3.1 DC Power

Pin Definition

Center +5VDC Outer Ring GND

3.3.2 BNC ASI (Typical Out-A and Out-B)

Pin Definition

Center 8B/10B 270 Mbps Outer Ring GND

3.3.3 RJ-12 Primary Redundancy

Pin Definition 1 GND 2 RXD 3 TXD 4 GND 5 N/C 6 N/C

3–3


3.3.4 BNC Primary ASI (Typical In-A and In-B)

Pin Definition Center 8B/10B 270 Mbps

Outer Ring GND

3.3.5 RJ-12 Secondary Redundancy

Pin Definition 1 GND 2 RXD 3 TXD 4 GND 5 N/C 6 N/C

3.3.6 BNC Secondary ASI (Typical In-A and In-B)

Pin Definition Center 8B/10B 270 Mbps

Outer Ring GND

3–4

Chapter 4. DEVICE MANAGEMENT VIA USER INTERFACES

4.1 Introduction

Management of the MENCAP 50 is simple and intuitive. There are a variety of ways to configure and manage the MENCAP 50:

• Web Interface via a LAN-based Desktop Browser • Terminal Interface via direct connection to a PC’s asynchronous serial port • Telnet Interface via a LAN • TFTP for remote terminal upgrades • SNMP Private MIB and MIB II

4.2 Web Interface

The Web Interface, operating under standard HyperText Transport Protocol (HTTP), is used to communicate with and command the MENCAP 50 via a HyperText Markup Language-based Graphical User Interface (GUI). To utilize the Web Interface, a LAN connection must exist between the PC with a browser and the MENCAP 50. Once a valid IP Address, Subnet Mask and Default Gateway have been entered into the MENCAP 50, activate a browser on the desktop. Enter the IP address for the MENCAP 50 into the URL field as shown in Figure 4-1. If the port number has been modified from the Standard 80 via the Terminal Interface, then the port number must be appended with a colon to the IP address.

Figure 4-1. Connecting to the MENCAP 50

A successful connection between the PC and the MENCAP 50 will result in the display of the “splash page” shown in Figure 4-2.

4-1

Digicast Micro Encapsulator (MENCAP) Revision A Device Management via User Interfaces MN/MENCAPEDC.IOM

Figure 4-2. Home (“Splash”) page

4.2.1 Administrative Configuration

Figure 4-3. Administrative Configuration page

4-2


IMPORTANT

Beginning with the Administration Configuration Menu page (Figure 4-3), all pages containing configurable parameters feature a login dialog box at the bottom of the page. Changes to the MENCAP 50 configuration will not be accepted without a valid user name and password.

The MENCAP 50 Administrative Configuration page contains the following configurable parameters: User Name

The MENCAP 50’s User Name is user configurable and is used for connecting to the unit via IP management services. The default user name is comtech.

Password The MENCAP 50’s Password is user configurable and is used for authenticating a user when connecting via IP management services. The default password is comtech. The password is case sensitive and must be entered carefully. When the password is changed, the user will be prompted to enter the password twice to verify it is correct.

System Contact Contact information of the system administrator for support.

System Location The physical location where the unit has been installed.

Enable Telnet

Enables Telnet application on the MENCAP 50.

Enforce QoS Egress BW Rules Enables the bandwidth management feature on the MENCAP 50.

Login Required A user name and password are required to make any changes to the MENCAP 50 configuration.

Update Firmware Allows software/firmware changes to be made. User name and password is required for security.

4-3


4.2.2 Network Configuration

Figure 4-4. Network Configuration page

The MENCAP 50 Network Configuration page has the following configurable parameters: MAC Address The hardware address assigned to the MENCAP 50’s LAN interface. This address may not be assigned, since it is set during the manufacturing process IP Address

The IP Address assigned to the MENCAP 50’s LAN interface. The IP Address is entered in dotted decimal format.

Subnet Mask

The Subnet Mask assigned to the MENCAP 50’s LAN interface. The Subnet Mask is entered in dotted decimal format and is typically 255.255.255.0 for a C-Class mask, 255.255.0.0 for a B-Class mask or 255.0.0.0 for an A-Class mask.

Default Gateway

The Default Gateway assigned to the MENCAP 50’s LAN interface. The Default Gateway is entered in dotted decimal format and must be within the subnet of the IP Address assigned to the LAN interface. The Default Gateway is the address of a local router to which all non-local subnet traffic will be directed.

VLAN ID

If the MENCAP 50 is required to be managed in a VLAN ID environment, the VLAN ID can be set by the terminal or Telnet – the ability to set the MENCAP 50’s Ethernet port’s VLAN ID cannot be done on the Web Interface.

4-4


4.2.3 Egress Configuration

Figure 4-5. Egress Configuration page

The MENCAP 50 Egress Configuration page has the following configurable parameters:

Egress rates The MENCAP 50 supports egress clock rates from 100 Kbps to 85 Mbps (188-Byte mode only) in steps of 1 bps (accuracy better than +/- 1 Kbps). The egress rate may be set up for 204-byte mode, but the egress rate is limited to 67.2 Mbps. The limitation of 204-byte mode is due to the additional 16-bytes for Reed Solomon that is included at the end of the frame, resulting in more overhead in the transport stream.

188-byte/204-byte Framing The MENCAP 50 supports both 188-byte and 204-byte framing mode. When selecting 204-byte framing mode, the 16 bytes of the MPEG-2 packet are padded with zeros (0x00).

4-5


4.2.4 PSI Configuration

Figure 4-6. PSI Configuration page

The MENCAP 50 provides support for MPEG-2 PSI and DVB SI; for MPEG-2, PSI provides the Program Association Table (PAT) and Program Map Table (PMT). The Network Information Table (NIT) is supported per DVB SI specification for DVB-C (cable), DVB-S (satellite), and DVB-T (terrestrial). Since ATSC data is present in the multiplex as unknown, no ATSC tables are supported to ensure audio/video set-top boxes do not inadvertently tune to data services. While no ATSC tables are supported, per se, ATSC data types are supported in the form of IP encapsulation of IP datagrams The PAT resides on PID 0x0000 and the MENCAP 50 allows the user to define the following PID for the PMT:

• The PMT announces the PID assigned to each valid route. • The stream type for a PID assigned to a route will be announced as “DSM-CC”

(stream type 0x08). • Each route will have its own program map PID (defined as PMT base PID + route

number – 1). • In the PAT, each program number will be assigned the corresponding route

number. The NIT is assigned to PID 0x0010.

4-6


The PSI Configuration page has the following configurable parameters: Enable

The “Enable” PSI Boolean allows the user to enable or disable the PSI information. Most multiplexers will require the PSI information to be present to identify the input programs.

Rate

The rate in tenths of a second the PSI tables (PAT/PMT) will be transmitted to the network. For example, 4 is a rate of 400ms.

PMT PID Base The first PID number that will be used to announce the available programs to the network.

Transport Stream ID

The transport stream ID provides the identification of this TS from any other multiplex in the network.

Network ID

The network ID provides a means of identifying the particular physical network over which the tables are being transmitted.

NIT Rate

The rate in seconds that will be used to define the frequency with which the Network Information Table is transmitted.

Types of Tables

This provides the option to select between MPEG-2, DVB and ATSC tables: MPEG-2 – Supports PSI, specifically, PAT and PMT. The ME can be configured to output no tables or at very minimum the MPEG-2 tables known as the Program Specific Information (PSI) tables. This is typically the bear minimum required to connect to a multiplexer. The PSI information prevents PIDs from being identified as “unknown” or “ghost PIDs.” ATSC – The MENCAP 50 does not support ATSC table, but changes the data identifier in the encapsulated Multi-Protocol Encapsulated packet to a 0x3F for ATSC, instead of 0x3E for DVB encapsulated datagrams. DVB – Supports NIT in addition to MPEG-2 DVB tables are identified by the type of NIT announced. This allows for the selection of the NIT based upon network type, namely, satellite (DVB-S), cable (DVB-C), or terrestrial (DVB-T). By clicking on the appropriate link, a list of configurable parameters is displayed for that particular network. By clicking the PSI link, the web page returns to the original ‘PSI’ settings but with the specific network type identified below the other settings.

4-7


The following descriptors are supported in the NIT but not configurable by the user: Network Name (Descriptor tag 0x40)

Character – Specifies character string for the delivery system about which the NIT informs.

Service List (Descriptor tag 0x41) • Service ID – Identifies a service within a Transport Stream.

• Service Type – Specifies the service type according to defined values.

For each of the network options, the required parameters (delivery system descriptors) are configurable by the user in the next three chapter sections:

• Chapter 4.2.4.1 Option DVB-C NIT Submenu

• Chapter 4.2.4.2 Option DVB-S NIT Submenu

• Chapter 4.2.4.3 Option DVB-T NIT Submenu

4.2.4.1 Option DVB-C NIT Submenu

Cable Delivery System (Descriptor tag 0x44)

• Frequency – The frequency of the cable delivery system in use.

• Symbol Rate – Specifies the symbol rate in use.

• Modulation – Specifies the modulation scheme in use.

• FEC Inner – Spervice ID – Identifies a service within a Transport Stream.

• FEC Outer – Defines the Forward Error Correction outer code scheme in use.

Figure 4-7. PSI Configuration page – DVB-C NIT submenu option

4-8


4.2.4.2 Option DVB-S NIT Submenu

Satellite Delivery System (Descriptor tag 0x44) • Frequency – Specifies the frequency of the satellite delivery system in

use.

• Symbol Rate – Specifies the symbol rate in use.

• Orbital Position – Specifies the orbital position in degrees.

• West-East Flag – Specifies if satellite is west or east of the longitudinal meridian.

• Modulation – Specifies the modulation scheme in use.

• Polarization – Specifies whether the signal is linear or circular.

• FEC Inner – Specifies the Forward Error Correction inner code scheme in use.

• West/East – Specifies if satellite is west or east of the longitudinal meridian.

Figure 4-8. PSI Configuration page – DVB-S NIT submenu option

4-9


4.2.4.3 Option DVB-T NIT Submenu

Terrestrial Delivery System (Descriptor tag 0x5A) • Center Frequency – Specifies the center frequency of the channel system

in use.

• Bandwidth – Specifies the channel bandwidth in use.

• Constellation – Specifies the modulation scheme in use.

• Hierarchy Information – Specifies whether transmission is hierarchical and, if so, what the alpha value is.

• Code Rate – Specifies inner FEC scheme. Hierarchical vs non-hierarchical channel coding and modulation is supported.

• Guard Interval – Specifies interval values between 1/32 and 1/4.

• Transmission Mode – Specifies number of carriers in an OFDM frame.

Figure 4-9. PSI Configuration page – DVB-T NIT submenu option

4-10


4.2.5 SMPTE-325M Configuration

Figure 4-10.SMPTE-325M Configuration page

The SMPTE-325M Configuration page defines the flow control protocol to be used between the MENCAP 50 and a multiplexer for opportunistic data broadcast. SMPTE-325M can be implemented over ASI (return channel) or over Ethernet. CEFD has chosen to implement SMPTE-325M over Ethernet, since Ethernet is more prolific and should operate with any manufacturer’s multiplexer. Opportunistic Data Insertion (ODI) places data packets into the output multiplexer to fill any available free bandwidth. The multiplexer requests additional MPEG-2 Transport packets from the MENCAP 50 as buffer becomes available. Enable The “Enable” SMPTE-325M Boolean allows the user to enable or disable the SMPTE 325M option. Port to Listen On The UDP port that will be opened on the MENCAP 50 to listen to SMPTE-325M ODI messages from the multiplexer. PID to Expect The PID (number) returned from the multiplexer encapsulated in an IP packet in the form of a SMPTE-325M ODI packet.

4-11


4.2.6 Route Configuration

Figure 4-11. Route Configuration page

The MENCAP 50’s Route Configuration page supports up to 1,024 Multicast or Unicast routes, grouped in blocks of 16 – or 10,000 Multicast or Unicast routes for the CEFD MENCAP 50 10K (CME-5010). The groups are shown at the bottom of the web page and accessed via hot-links. The user can scroll up or down through the configured routes on the MENCAP 50 using the page window’s scroll bar. Once a route has been added or edited, the Submit button must be pressed to make the change permanent. An advanced link is present on the menu to allow the QoS parameters to be set. The MENCAP 50 has the following configurable route parameters: Promiscuous Mode

The MENCAP 50 now supports a mode of operation where a single promiscuous route may be enabled that allows ALL Unicast and Multicast traffic (non-broadcast) to be routed over a single route. In the event there is a route that covers a received packet, the packet is routed over the defined route and all QoS rules will be applied; but if it does not match a defined route, the packet is routed over the promiscuous route.

4-12


Great care must be exercised when using promiscuous mode, since ALL traffic that is present on the Ethernet segment is routed over this route. All management traffic to and from or between redundant MENCAP 50s is not routed over the promiscuous route.

On The route is enabled when checked.

Name The name assigned to a given route.

IP Address

The IP Address assigned to a given route. Note a Unicast route will fall within the range 0.0.0.0 to 223.255.255.255 (excluding broadcast or reserved IP addresses), and a multicast route will fall within the range of 224.0.0.0 to 239.255.255.255.

Subnet Mask (SM)

The Subnet Mask,(SM), defines the range of IP addresses that will be supported by a particular route. It is represented by a 32-bit string of 1’s (representing the network and subnet network ID) followed by 0’s (representing the host ID). This string when logically ‘ANDED’ with the IP address, defines the network/subnet IP address. The following demonstrates how the subnet mask defines the IP address range – the MENCAP 50 uses Classless Inter-Domain Routing (CIDR) notation for setting the subnet masks:

• 255.255.255.255 is 0 bits (used for an explicit route for a single IP address) • 255.255.255.0 is 24 bits (used for a C-Class Mask) • 255.255.0.0 is 16 bits (used for a B-Class Mask) • 255.0.0.0 is 8 bits (used for an A-Class Mask)

PID

The Program Identifier (PID) assigned to a particular route. PIDs do not have to be unique and may be assigned to one or more routes.

MAC Address

The MAC address is assigned to a given route. For Unicast, this is typically the MAC address the route is assigned to and is determined by the end device (next-hop) to which the data is sent. However, for Multicast, this is derived as previously described.

4-13


4.2.7 Advanced Route Configuration

Figure 4-12. Advanced Route Configuration page

Guaranteed Bandwidth

The guaranteed bandwidth offered to a given route. The route will be guaranteed a minimum of this amount of bandwidth on the MENCAP 50.

Max Bandwidth

The maximum bandwidth allowed for a given route. Any traffic that exceeds the maximum bandwidth will be silently discarded.

Packed

If “Yes” is selected, then Section Packing is enabled for this route. If “No” is selected, then no section packing will take place on this route.

IP Copy

If “Yes” is selected, then IP Copy is enabled for this route. If “No” is selected, then the route is handled as a standard IP route via the assigned IP address, subnet mask, and configured MAC address.

Mode

Mode defines how the route data should be processed. Drop menu selects between normal mode and TCP-to-UDP mode.

4-14


In normal mode, the routes are handled as either Multicast or Unicast routes. In TCP-to-UDP mode, incoming routes are expected to be received as TCP on a known port number and the UDP packets are extracted from the TCP packets and forward as Multicast to the egress port. TCP-to-UDP allows the KenCast server (Fazzt) to use TCP (a connection oriented protocol) to deliver UDP datagrams over a reliable delivery method, resulting in minimum loss of data due to egress overflow. When used in conjunction with SMPTE 325M, this feature allows a multiplexer to provide real-time (or near real-time) feedback to the MENCAP 50, which in turn uses the TCP-to-UDP mechanism to flow control the flow of data. This technique allows error free communication over a data link, while maximizing the available bandwidth.

TCP to UDP Port

The TCP to UDP Port allows the user to configure the MENCAP 50 to listen to a defined (unreserved) port number (>= 1,024), for that route, for a connection request from the server.

VLAN

VLAN support options: NONE – No VLAN traffic will be passed. Only traffic without a VLAN tag will be passed All – All traffic received with VLAN tags will be passed and all non-VLAN traffic will be blocked VLANID – ID must match the VLAN ID field. If the VLANID is set, only traffic on the configured VLAN ID will be passed

VLAN ID

A valid VLAN ID for the desired route. The valid ranges of the VLAN ID are 0 to 4095.

Include PSI

Allows the user to select whether the route is present or not present in the PSI table. The PSI must be enabled for the route to be included in the PSI table.

ZAP

Available only on the terminal or Telnet. This feature is used for customers who need to modify a parameter on every configured route on the MENCAP 50.

4-15


4.2.8 IGMP Configuration

Figure 4-13. IGMP Configuration page

The IGMP Configuration page allows the MENCAP 50 to act as an IGMP client. Some IGMP servers and IP routers will not transmit IP to a network without an active IGMP client on the local network. The MENCAP 50 provides the option to allow joins (and leaves if a route is deleted) if a valid route is present.

IGMP does not function when Multicast Zones are utilized. IGMP will only issue join requests (and leaves) for explicit Multicast routes.

Enable

This turns on/off the IGMP feature. This Boolean is a global setting. When enabled all Multicast routes will have IGMP enabled as is true of the converse.

Version

This allows selection of IGMP version 1 or version 2. Report Period

This specifies the frequency with which multicast group membership is reported to other members of the group.

IMPORTANT

4-16


4.2.9 Redundancy Configuration

Figure 4-14. Redundancy Configuration page

The Redundancy Configuration page is used to configure the MENCAP 50 when part of a 1:1 redundant system. Mode

Specifies the whether redundancy is enabled or disabled and whether the unit is configured to be in primary or backup mode.

Current State

Indicates the redundant status of the MENCAP 50. Other unit’s IP Address

Specifies the other MENCAP 50’s IP address in the redundancy pair Other unit’s MAC Address

Specifies the other MENCAP 50’s MAC address in the redundancy pair.

4-17


4.2.10 Route Statistics

Figure 4-15. Route Statistics reporting page

The Route Statistics page displays the statistics for all configured routes. The user can scroll up or down through the configured routes on the MENCAP 50 using the page window scroll bar. The Clear Stats button allows all statistics to be cleared on the MENCAP 50 at the same time. Aggregate Statistics

Displays the aggregate statistics (combined for all enabled routes) for the entire MENCAP 50.

On

‘Yes’ indicates the route is active. Name

The name assigned to a given route. Received

The number of IP packets received on this route, since the statistics were last cleared.

4-18


Dropped The number of IP packets dropped on this route, since the statistics were last cleared.

PID The PID assigned to the associated route.

Min

The Minimum bandwidth received on this route, since the statistics were last cleared.

Max

The Maximum bandwidth received on this route, since the statistics were last cleared.

Average

The Average bandwidth received on this route.

4.3 Terminal Interface

The Terminal Interface provides the user with a textual configuration dialog for configuring the MENCAP 50. This method of configuration should be used for initial configuration of the unit; i.e., configuring the network parameters for the unit, but not for normal operation. The Web (HTTP) Interface is recommended for operational management. The Terminal Interface allows the entire unit to be configured and managed, but this interface can only be used while a serial connection is present between the MENCAP 50 and a PC. The screens shown in this section are displayed via a Telnet connection. The same menu information is displayed via the serial interface with some specific features only available via this access method – these ‘serial interface only’ features are noted in this section. Detailed information for the menu features is provided in Chapter 4.2 Web Interface. Figure 4-16 shows the hierarchal structure of the Terminal Interface-based menus, and the sections in this chapter which provide figures of these submenu pages. Once the terminal interface is connected, as described in Chapter 2.4 Initial Configuration, press the <ENTER> key . The user should observe the the Main menu, as shown in Figure 4-17.

4-19


Figure 4-16. Terminal Menu Hierarchy

Stats Menu(4.3.4)

Egress Cfg Menu(4.3.5)

Network Cfg Menu(4.3.6)

SMPTE 325 Cfg Menu (4.3.7)

Route Cfg Menu(4.3.8)

Administration Cfg Menu (4.3.3)

Redundancy Cfg Menu (4.3.2)

PSI Cfg Menu(4.3.9)

IGMP Cfg Menu(4.3.10)

DMA Stats Menu(4.3.4.3)

Ethernet Stats Menu(4.3.4.2)

Route Stats Menu(4.3.4.1)

Main Menu (4.3.1)

Advanced Route Cfg Menu (4.3.8.1)

4.3.1 Main Menu

Figure 4-17. Main Menu

4-20


4.3.2 Redundancy Configuration Menu

Figure 4-18. Redundancy Configuration Menu

4.3.3 Administration Menu

Figure 4-19. Administration Menu

4.3.3.1 Port Number Configuration

In addition to the features illustrated, one additional feature is available, for security reasons, via the serial interface only. Modifying the port numbers prevents attacks on “well known” ports by devices known as port scanners. This feature is configuration of the TCP Port number for Telnet and HTTP protocols. Option (M) allows the operator to modify the standard port numbers for Telnet (23) and HTTP (80) to prevent unauthorized access to the device. Care should be taken not to use a reserved standard port number.

4-21


4.3.4 Stats Menu

Figure 4-20. Stats Menu

4.3.4.1 Route Stats Menu

Figure 4-21. Route Stats Menu

4-22


4.3.4.2 Ethernet Stats Menu

Figure 4-22. Ethernet Stats Menu

4.3.4.3 DMA Stats Menu

Figure 4-23. DMA Stats Menu

4-23


4.3.5 Egress Configuration Menu

Figure 4-24. Egress Configuration Menu

4.3.6 Network Configuration Menu

Figure 4-25. Network Configuration Menu

4-24


4.3.7 SMPTE 325M Configuration Menu

Figure 4-26. SMPTE 325M Configuration Menu

4.3.8 Route Configuration Menu

Figure 4-27. Route Configuration Menu

4-25


4.3.8.1 Advanced Route Configuration Menu

Figure 4-28. Advanced Route Configuration Menu

4.3.9 PSI Configuration Menu

Figure 4-29. PSI Configuration Menu

4-26


4.3.10 IGMP Configuration Menu

Figure 4-30. IGMP Configuration Menu

4.4 Telnet Interface

Telnet provides a textual interface over a LAN. Most PCs have the capability to use Telnet. To use Telnet on a Microsoft Windows® product, click , then .

The Run dialog box is shown in Figure 4-31. In the Open: text window, enter “telnet xxx.xxx.xxx.xxx,” where xxx.xxx.xxx.xxx is the IP address of the MENCAP 50. If the port number has been modified from the Standard 23 via the Terminal Interface, then the port number must be appended with a colon to the IP address.

Figure 4-31. Starting Telnet Session The user will be prompted to enter the user name and password to gain access to the telnet interface.

The default username is “CEFD” and the default password is “CEFD”, both of which are case sensitive.

NOTE

Once the menu is started, press <ENTER> and the MENCAP 50 Main Menu will display as shown in Figure 4-32.

4-27


Figure 4-32. Main Menu via Telnet

The user may navigate the menus in the same manner as the Terminal Interface. With specific exceptions as noted in the Terminal Interface section, the menus available via Telnet and Serial interfaces are identical.

4.5 Trivial File Transfer Protocol (TFTP)

The MENCAP 50 supports changes to the resident software and firmware by means of the Trivial File Transfer Protocol (TFTP). This enables changes to be made remotely via the LAN interface. It is recommended to use Solarwinds TFTP server application (available at http://support.solarwinds.net/updates/SelectProgramFree.cfm). To modify the software and/or firmware, use the following procedures: Configure the server as follows:

a) File ! Configuration ! Select the ‘TFTP Root Directory’. Set up the location of the MENCAP 50 files.

b) File ! Configuration ! Select the ‘Security’ tab and make sure ‘Transmit and Receive’ are selected.

c) Save configuration. The server is now configured for the file transfer process.

IMPORTANT

Because the MENCAP 50 stops processing data traffic during the download process, it is recommended that this upgrade procedure be performed during scheduled network down time.

Do NOT remove power from the unit during the download process.

4-28


To modify code via Telnet:

Step Procedure

1 Start up Solarwinds TFTP server – ensure configuration as described previously.

2 Ensure that the code provided by CEFD is located in the TFTP Root directory.

3 Start up Telnet client and initiate a session with the MENCAP 50 as described in the Telnet Interface section

4 Select ‘A’ for Administration 5 Select ‘D’ for Download 6 Enter ‘1’ for Application code or ‘2’ for FPGA code (the user will be

directed to select Application or FPGA code in the download instructions provided by CEFD when new code is provided)

7 Enter the IP address of the TFTP server and wait for the message “Upgrade complete. Press any key to continue”

This code modification process can also be conducted via the Web Interface, under the Administration page, or the Terminal Interface under the Main Menu. Under heavy traffic conditions, the TFTP transfer may take several

minutes. The transfer process reported by Solarwinds may show greater than 100% transferred, but this is a normal condition. Be patient and allow the transfer to take place.

4.6 Simple Network Management Protocol (SNMP)

Simple Network Management Protocol (SNMP) allows an SNMP Manager such as OpenView or Castle Rock to be used to remotely manage the MENCAP 50 in an automated fashion.

The MENCAP 50 supports SNMP versions 1 and 2 (SNMPv1 and SNMPv2). Two types of Management Information Bases (MIBs) are supported: MIB II and private MIB.

MIB II is the default MIB used to gather generic information about the unit, such as system ‘up’ time, packets sent or received on an interface, etc. MIB II is designed for only read access, not write access. To read and write configuration parameters over SNMP requires a private MIB. The MENCAP 50’s private MIB allows parameters to be set that can be set on the Web Interface, terminal, or Telnet.

The elements Object Identifiers (OIDs) of the MENCAP 50’s MIB are listed in the appendix of this manual. CEFD has been assigned an SNMP designator by the IEEE, and will be found in all elements of the IS’s MIB.

The MENCAP 50 supports configurable community strings for added security. As a security precaution, passwords cannot be remotely queried over SNMP.

IMPORTANT

The assigned designator for CEFD (enterprise OID) is 1.3.6.4.1.18723. NOTE

4-29


For SNMP access from a remote network via the public Internet, a VPN connection to the MENCAP 50 will need to be established using third-party VPN client/server access.

The default community string for the public elements is “public” and the private community string is “private.”

Notes:

4-30

Appendix A. SOFTWARE UPGRADE

A.1 Introduction

The MENCAP 50 is enabled to receive an upgrade via Trivial File Transfer Protocol (TFTP) transmission. Comtech EF Data recommends using the Solarwinds TFTP server application (available at http://support.solarwinds.net/updates/SelectProgramFree.cfm) for upgrading the product.

NOTE

The user will be instructed whether to select Application or FPGA code in the download instructions provided by CEFD when new code is provided.

Once the TFTP server is enabled and the new file (Application or FPGA) has been copied to the TFTP server, the procedures outlined in sections A.2 and A.3 may be used to upgrade the unit.

A–1

http://support.solarwinds.net/updates/SelectProgramFree.cfm

Digicast Micro Encapsulator (MENCAP) Revision A Software Upgrade MN/MENCAPEDC.IOM

A.2 Web Interface

Access the Administrative Configuration menu (Figure A-1):

a) In the Update Firmware section, enter the Unit TFTP Server IP Address. b) Select Application or FPGA for the Image Type to be upgraded. c) Enter a valid username and password in the Login Required section (below

the Update Firmware section) then select Update. The software update will begin to download.

IMPORTANT

Do NOT power the unit down during the upgrade process.

d) When the update is complete, the message “Press any key to continue”

will be displayed. e) Once the unit is upgraded, reset the unit by entering a valid username and

password in the first Login Required section, then selecting Reset Unit.

Figure A-1. TFTP Download (via Web)

A–2


A.3 Telnet or Terminal Interface

Access the Administrative Menu (Figure A-2):

a) Select (D) for Download Image. b) At the “Image type” prompt, enter 1 for Application or 2 for FPGA. c) Enter the TFTP IP server address. Once the TFTP IP server address is

entered, the software update will begin to download.

Do NOT power the unit down during the upgrade process.

IMPORTANT

d) When the update is complete, the message “Press any key to continue” will be displayed (Figure A-3).

e) After the unit has been upgraded, reset the unit by selecting (R) for Reset and ‘Y’ to confirm the reset.

Figure A-2. TFTP Upgrade (via Terminal)

A–3


Figure A-3. TFTP Upgrade Complete (via Terminal)

Notes:

A–4

Appendix B. IP ROUTING SUPPORT

B.1 Introduction

Offering state-of-the-art encapsulation based on the DVB Specification for Data Broadcasting (EN 301 192), the MENCAP 50 provides the following configuration features:

• IP Encapsulation per Multi-Protocol Encapsulation (EN 301 192) • Unicast Routing • Multicast Routing • Section Packing and Non-Section Packing • 1,024 Configurable Routes (10,000 configurable routes are available as an

option) • Multicast Zones • IP Copy • 802.1q VLAN

B.2 Route Configuration

Both Unicast and Multicast IP datagrams are encapsulated per the Multi-Protocol Encapsulation specification. Routing of datagrams is accomplished by configuration of the ME Route Table, described in the following section.

B.2.1 Unicast Routing

Unicast routing provides point-to-point delivery of IP datagrams. Routes for Unicast IP packets are configured according to the following:

B-1

Digicast Micro Encapsulator (MENCAP) Revision A IP Routing Support MN/MENCAPEDC.IOM

• IP Addresses, which fall into three classes, namely: A (0.0.0.0 to 127.255.255.255), B (128.0.0.0 to 191.255.255.255) and C (192.0.0.0 to 223.255.255.255).

• Medium Access Control (MAC) Addresses, which identify the destination device (next-hop) to which the packets are sent. The least-significant bit of the first byte of the six-byte MAC address is a ‘0’. For example, 0x00 11 22 33 44 55 is a Unicast address.

Unicast is supported by the MENCAP 50 as it would be in any routed network. A route is created and a subnet mask is assigned to the route. The MENCAP 50 uses Classless Inter-Domain Routing (CIDR) notation in which a ‘slash’ followed by a decimal number is used to represent the number of bits for the mask, e.g. /32 is 255.255.255.255 and /24 is 255.255.255.0. As stated previously, part of the route configuration is a MAC address that is assigned for delivery of the packet when it is encapsulated into MPE. The MAC address typically identifies the remote receiver (physical device); e.g. satellite terminal, DTV terminal, or cable receiver.

B.2.2 Multicast Routing

Multicast routing provides point-to-multipoint delivery of IP datagrams. Routes for multicast IP packets are configured according to the following:

• IP Addresses, which fall into class D (224.0.0.0 to 239.255.255.255) • Medium Access Control (MAC) Addresses, which identify the frames as

multicast. The least-significant bit of the first byte of the six-byte MAC address is a ‘1’. For example, 0x01 00 5E 00 00 01 is a multicast address.

• Broadcast frames are identified by the MAC Address, 0x FF FF FF FF FF FF. Multicast IP addresses are related to multicast MAC addresses as follows:

• The lower 23 bits of the IP address are mapped into the lower 23 bits of the MAC address.

Figure B-1. Multicast Mapping (IP to MAC)

B-2


Several examples of the relationship are:

• Received IP: 239.1.1.10 = MAC: 0x01 00 5E 01 01 0A • Received IP: 224.10.10.10 = MAC: 0x01 00 5E 0A 0A 0A • Received IP: 228.63.10.10 = MAC: 0x01 00 5E 3F 0A 0A

Note that the upper 5 bits of the multicast IP address are ignored in the MAC so that 32 Multicast group IP addresses map to a single MAC address. This implies further filtering is required at the end device.

B.3 802.1Q VLAN Support

802.1Q VLAN support allows the MENCAP to route traffic based on the VLAN tags. The configuration of the VLAN tag is done on the Advanced Routing page on the terminal interface and is also available on the web interface. VLAN tags are supported when LLC_SNAP Ethernet frames are being used. Normal Ethernet frames utilize IEEE 802.3 framing with a maximum frame size of 1,518 bytes; however, LLC_SNAP frames contain four extra bytes (on the frame header) that may be used for VLAN tags, so the Ethernet frame size is up to 1,522 bytes. The VLAN tag allows the MENCAP to route packets based on the presence of a route that matches the VLAN tag. The VLAN tag is 12 bits in length and valid values from 0 to 4095 are accepted.

B.4 Section Packing

Section packing is a technique to provide better utilization of the MPEG-2 Transport Stream (TS) packet structure. When section packing is not used, each TS packet (containing the MPE section) can carry no more than a single section. This often results in wasted payload capacity when the sections are less than 184 bytes. The section packing feature allows more than a single MPE section to be carried by an MPEG-2 TS packet, thereby minimizing wasted payload capacity. In the case of a large MPE section that spans multiple MPEG-2 packets, the ending of an MPE section may

Figure B-2. Section Packing

B-3

occur in the middle of an MPEG-2 packet. In this instance, with section packing, a new MPE section begins immediately after the first MPE section has finished without any ‘fill’ (wasted) bytes having to be inserted before the start of the next MPEG-2 packet.

B.5 1,024 Routes

The MENCAP 50 is capable of providing up to 1,024 unique IP routes. Each IP route can be configured as Unicast or Multicast. Additional routes may be supported by using the Multicast Zones feature described in the next section. Routes can be assigned to PIDs in the range 0x0010 to 0x1FFE (this excludes the reserved PIDs as defined in ISO 13818-1)

B.6 10,000 Routes

The CEFD MENCAP 50-10K (CME-5010) is capable of providing up to 10,000 unique IP routes. Each IP route can be configured as Unicast or Multicast. Additional routes may be supported by using the Multicast Zones feature described in the next section. Routes can be assigned to PIDs in the range 0x0010 to 0x1FFE (this excludes the reserved PIDs as defined in ISO 13818-1). This feature requires a hardware enhancement and is not supported on the standard MENCAP 50 platform.

B.7 Multicast Zones

The Multicast Zones feature allows the user to more efficiently configure the Encapsulator when supporting multicasting. Using the IP subnetting techniques of Unicast routing, Multicast Zones allows a single IP address to be specified on a route and a subnet mask is assigned to the route. The MENCAP 50 uses Classless Inter-Domain Routing (CIDR) notation in which a ‘slash’ followed by a decimal number is used to represent the number of bits for the mask; e.g. /32 is 255.255.255.255 and /24 is 255.255.255.0. The subnet mask defines how many multicast IP addresses are allowed to be mapped to a single route. Care must be taken when using the multicast zone feature since IP traffic present within the multicast zone will be routed over the network. An example of multicast zone is as follows:

• Multicast Route = 239.0.10.1 • Multicast Zone Mask = 255.255.255.252 • Multicast groups mapped to the 239.0.10.1 route:

o 239.0.10.0 o 239.0.10.1 o 239.0.10.2 o 239.0.10.3

B-4


B.8 IP Copy

IP Copy is another technique for more efficiently mapping incoming IP packets to Encapsulator routes by means of a defined rule associated with a given route. Typically, IP Copy is used for Unicast traffic. The rules instruct the MENCAP 50 how to assign the MAC addresses, used in the encapsulation process, based on the incoming IP address of the packets. The rules appear as follows:

• IP Copy Range = 10.10.10.X • Mask = 255.255.255.0

The rule states the last byte of the IP address “X” becomes the last byte of the destined MAC address:

• MAC Address = 0x00 50 C2 25 00 00 – 0x00 50 C2 25 00 FF The IP Copy rules provide automatic MAC address assignment based on the incoming IP address. Therefore, a single route running IP Copy can support multiple remotes. In this example, the rule will support up to 1,024 remotes on a single route. IP Copy Example: Incoming IP Address – 10.10.10.5 assigned MAC Address – 0x00 50 C2 25 00 05

Incoming IP Address – 10.10.10.100 assigned MAC Address – 0x00 50 C2 25 00 64

B.9 Quality of Service (QoS)

Each route defined can be configured to provide a determined bandwidth. Note that all QoS rates are for the MPEG transport stream and are based on MPEG payloads. Therefore, IP data rates may be slightly less due to the transport overhead of the MPEG and MPE. Additionally, running section packing will provide more IP data throughput, but consumes an equal amount of usage over the MPEG transport stream. The bandwidth attributes that may be set are as follows:

• Minimum: The guaranteed amount of bandwidth the MENCAP 50 will provide for this route. The total number of routes with guaranteed bandwidth must always be less than the rate of the egress port.

• Maximum: The maximum amount of bandwidth a route will be allowed to have. Once the traffic for this route exceeds this level, packets will be silently discarded to ensure that the maximum is not exceeded

• No Setting: If neither the Guaranteed nor the Maximum values are set, the route will be allowed to use as much bandwidth as possible and possibly attempt to exceed the egress bandwidth, which will result in lost data. Conversely, if there is not guaranteed bandwidth for the route, another route may utilize all available bandwidth.

B-5


B.10 MPE/IP

Additional menu options have been added for special handling of the encapsulation of data:

• CRC – In normal operation, the MENCAP 50 does not calculate the CRC and sets this field to 0x00000000. Some legacy receivers, may require the CRC to be calculated. When this field is enabled, performance is reduced by as much as 50%. The default should be No.

• Reserved Fields – Setting this field configures the reserved bits for legacy receivers. The default should be No.

• Set Offset – Setting this field configures the reserved bits for legacy receivers. The default should be No.

Notes:

B-6

Appendix C. MENCAP 50 PRIVATE MIB ELEMENTS

C.1 Admin Menu

String OID Access Description dniAdminUserName 1.3.6.1.4.1.18723.2.2.2.0 read-write Admin User Name DniAdminPW 1.3.6.1.4.1.18723.2.2.3.0 read-write Admin Password DniAdminReset 1.3.6.1.4.1.18723.2.2.4.0 read-write Reset Unit: Set to 1 to reset unit dniAdminEnableTelnet 1.3.6.1.4.1.18723.2.2.6.0 read-write Telnet Enabled (Yes/No) dniAdminEnforceEgressQoS 1.3.6.1.4.1.18723.2.2.7.0 read-write Enforce QoS Egress (Yes/No) dniAdminUnitName 1.3.6.1.4.1.18723.2.2.8.0 read-write Unit Name dniAdminOSVersion 1.3.6.1.4.1.18723.2.2.9.0 read-write OS Version dniAdminAppVersion 1.3.6.1.4.1.18723.2.2.10.0 read-write Application Version dniAdminFPGAVersion 1.3.6.1.4.1.18723.2.2.11.0 read-write FPGA Version

C–1

Digicast Micro Encapsulator (MENCAP) Revision A MENCAP 50 Private MIB Elements MN/MENCAPEDC.IOM

C.2 Network Menu

String OID Access Description DniNetworkMAC 1.3.6.1.4.1.18723.2.4.2.0 read-only DniNetworkIP 1.3.6.1.4.1.18723.2.4.3.0 read-write dniNetworkSubnet 1.3.6.1.4.1.18723.2.4.4.0 read-write dniNetworkGateway 1.3.6.1.4.1.18723.2.4.5.0 read-write

C.3 Egress Menu

String OID Access Description dniEgressClockRate 1.3.6.1.4.1.18723.2.3.2.0 read-write Egress Clock Rate in mbps (0.1 - 80.0) dniEgressFraming 1.3.6.1.4.1.18723.2.3.3.0 read-write Framing mode: 188 or 204

C.4 PSI Menu

String OID Access Description dniPSIEnable 1.3.6.1.4.1.18723.2.9.2.0 read-write Enabled or Disabled

dniPSIRate 1.3.6.1.4.1.18723.2.9.3.0 read-write PSI Rate Rate * .1 Second (1-5)

dniPSIPidBase 1.3.6.1.4.1.18723.2.9.4.0 read-write PID Base Hex (0x10 - 0x1FFE)

dniPSItsid 1.3.6.1.4.1.18723.2.9.5.0 read-write Transport Stream ID "1-65 535”

dniPSInetid 1.3.6.1.4.1.18723.2.9.6.0 read-write Network ID "1-65 535”

dniPSInitrate 1.3.6.1.4.1.18723.2.9.7.0 read-write NIT Rate "Seconds (1-65 535)”

dniPSITabletype 1.3.6.1.4.1.18723.2.9.8.0 read-write Table Type MPEG or DVB

dniPSInittype 1.3.6.1.4.1.18723.2.9.9.0 read-write NIT Type "DVB-C DVB-S or DVB-T"

C–2


C.4.1 DVB-C NIT

String OID Access Description

dniPSIDVBCfreq 1.3.6.1.4.1.18723.2.9.100.0 read-write DVB-C Frequency MHz

dniPSIDVBCsymbol 1.3.6.1.4.1.18723.2.9.101.0 read-write DVB-C Symbol Rate MHz

dniPSIDVBCmodulation 1.3.6.1.4.1.18723.2.9.102.0 read-write DVB-C Modulation "16 QAM 32 QAM 64 QAM 128 QAM 256 QAM”

dniPSIDVBCfecinner 1.3.6.1.4.1.18723.2.9.103.0 read-write DVB-C FEC Inner "1/2 2/3 3/4 5/6 7/8 8/9 None”

dniPSIDVBCfecouter 1.3.6.1.4.1.18723.2.9.104.0 read-write DVB-C FEC Outer "None Reed Solomon"

C.4.2 DVB-S NIT


dniPSIDVBSfreq 1.3.6.1.4.1.18723.2.9.200.0 read-write DVB-S Frequency MHz

dniPSIDVBSsymbol 1.3.6.1.4.1.18723.2.9.201.0 read-write DVB-S Symbol Rate MHz

dniPSIDVBSOrbital 1.3.6.1.4.1.18723.2.9.202.0 read-write DVB-S Orbital Position Degrees

dniPSIDVBSmodulation 1.3.6.1.4.1.18723.2.9.203.0 read-write DVB-S Modulation "QPSK 8PSK 16 QAM”

dniPSIDVBSpolarization 1.3.6.1.4.1.18723.2.9.204.0 read-write

DVB-S polarization "linear-horizontal linear-vertical circular-left circular-right"

dniPSIDVBSfecinner 1.3.6.1.4.1.18723.2.9.205.0 read-write DVB-C FEC Inner "1/2 2/3 3/4 5/6 7/8 8/9 None”

dniPSIDVBSwesteast 1.3.6.1.4.1.18723.2.9.206.0 read-write DVB-S West/East East or west

C–3


C.4.3 DVB-T NIT


dniPSIDVBTfreq 1.3.6.1.4.1.18723.2.9.300.0 read-write DVB-T Frequency "0-42 949 672 950”

dniPSIDVBTbandwidth 1.3.6.1.4.1.18723.2.9.301.0 read-write DVB-T Bandwidth "6 7 or 8 MHz”

dniPSIDVBTconstellation 1.3.6.1.4.1.18723.2.9.302.0 read-write DVB-T Constellation "QPSK 16 QAM 64 QAM”

dniPSIDVBThierarchy 1.3.6.1.4.1.18723.2.9.303.0 read-write DVB-T hierarchy "on-hierarchial a=1 a=2 a=4”

DniPSIDVBThp 1.3.6.1.4.1.18723.2.9.304.0 read-write DVB-T Code Rate HP "1/2 2/3 3/4 5/6 7/8)”

DniPSIDVBTlp 1.3.6.1.4.1.18723.2.9.305.0 read-write DVB-T Code Rate LP "1/2 2/3 3/4 5/6 7/8)”

dniPSIDVBTguardinterval 1.3.6.1.4.1.18723.2.9.306.0 read-write DVB-T Guard Interval "1/32 1/16 1/8 1/4”

dniPSIDVBTtransmissionmode 1.3.6.1.4.1.18723.2.9.307.0 read-write DVB-T Transmission Mode "2K 8K”

dniPSIDVBTotherFrequencyFlag 1.3.6.1.4.1.18723.2.9.308.0 read-write DVB-T Other Frequency Flag Yes or No

C.5 SMPTE-325M Menu


dni325MEnable 1.3.6.1.4.1.18723.2.11.2.0 read-write SMPTE 325M Enable or Disable Yes or No

dni325MPort 1.3.6.1.4.1.18723.2.11.3.0 read-write Mux Port Number 1024 - 65535

dni325MPID 1.3.6.1.4.1.18723.2.11.4.0 read-write Mux PID number 0x10 - 0x1FFE

C–4


C.6 Routing Table


RouteIndex

1.3.6.1.4.1.18723.2.5.1.1.1.x Where: x = 1-1024 for route number

read-only Value will be 1-1024

RouteName


read-write Name of Route

ipAddress


read-write IP Address in route

subnetBits


read-write Subnet Bits (8-32)

pidHex


read-write Hex Value for Pid (0x0010 - 0x1FFE)

macAddress


read-write Mac Address for Route

C–5


C.7 Advanced Routing Table


arouteIndex



qosMin


read-write QOS Minimum Bandwidth Setting

qosMax


read-write QOS Maximum Bandwidth Setting

sectionPack


read-write Section Packing Yes or No

ipCopy


read-write IP Copy Yes or No

mode


read-write "0=Normal 1=TCP to UDP"

port


read-write port number (1024 - 65535)

C–6


C.8 IGMP Menu


DniIGMPEnable 1.3.6.1.4.1.18723.2.10.2.0 read-write IGMP Enable or Disable Yes or No

dniIGMPVersion 1.3.6.1.4.1.18723.2.10.3.0 read-write IGMP Version 1 or 2

DniIGMPReport 1.3.6.1.4.1.18723.2.10.4.0 read-write IGMP report Period 10 - 60 seconds

C.9 Redundancy Menu

String OID Access Description dniRedunMode 1.3.6.1.4.1.18723.2.8.2.0 read-write Disabled or Backup or Primary dniRedunState 1.3.6.1.4.1.18723.2.8.3.0 read-only State of Redundancy dniRedunOtherIP 1.3.6.1.4.1.18723.2.8.4.0 read-write Other Units's IP Address dniRedunOtherMac 1.3.6.1.4.1.18723.2.8.5.0 read-write Other Unit's MAC Address

C–7


C.10 Statistics Table


statsIndex



statsName


read-only Name of Route

packetRX


read-only Packets received on route

packetDrop


read-only Packets dropped on route

minBW


read-only Min Bandwidth on route

maxBW


read-only Max Bandwidth on route

avgBW


read-only Average Bandwidth on route

routeEnabled


read-only Route Enabled Yes or No

C–8

Appendix D. TROUBLESHOOTING

This section covers suggestions to assist the user in troubleshooting the MENCAP 50. If the suggestions in this section do not result in correct operation of the unit, please contact Comtech EF Data Customer Support for further assistance. SYMPTOM: MENCAP 50 does not power up

When the MENCAP 50 power is on, the blue PWR LED should be illuminated. If this LED is not illuminated, ensure the power supply is plugged in and tightly connected to the MENCAP 50.

SYMPTOM: Cannot communicate with the MENCAP 50 using a terminal/PC

The user can communicate with the MENCAP 50 using a CEFD-supplied terminal cable and a communications port on a desktop PC or notebook PC.

• Ensure the terminal cable is connected to the PCs communications port and the TERM port on the MENCAP 50.

• The communication program (HyperTerminal or TeraTerminal) should be

configured as 38,400 BAUD rate, 8 Data bits and No Parity and 1 Stop bit commonly referred to as 38,400/8/N/1.

• Flow control should also be disabled.

SYMPTOM: Cannot get E-LINK LED to illuminate on the MENCAP 50

The most common mistake is using an Ethernet Crossover Cable instead of a standard patch cord or straight-through cable. A crossover cable should only be used if connecting the MENCAP 50 directly to a PC. Otherwise, a patch cord to an Ethernet concentrator (Hub) or switch should be used.

SYMPTOM: Cannot ping the MENCAP 50

If the E-LINK LED is illuminated but the user cannot ping the MENCAP 50, the most likely causes are incorrect settings for the IP address or subnet mask.

D–1

Digicast Micro Encapsulator (MENCAP) Revision A Troubleshooting MN/MENCAPEDC.IOM

Ensure the MENCAP 50 and the PC are set with unique IP addresses that are in the same subnet. If the MENCAP 50 and the PC are not in the same subnet, then both the MENCAP 50 and PC must have a valid Default Gateway defined so that non-local traffic will be redirected to this device for routing the IP messages between the two devices.

SYMPTOM: MENCAP 50 will not synchronize with a modem

The MENCAP 50 may be connected directly from an ASI Output port to an ASI Input port on a modem. If the modem will not lock, the most likely cause is the data rate on the MENCAP 50 or modem are not set correctly. Another cause is the formatting of the MPEG packets make sure that both are set to either 188-byte mode (standard) or 204-byte mode. Always ensure the cable type between the MENCAP 50 and the modem is RG59 75Ω cable.

SYMPTOM: MENCAP 50 reports dropped packets

The most likely cause of this problem is the incoming data on a route or all routes exceeds the configured egress bandwidth. To remedy the problem:

• Look at the route statistics for the MENCAP 50 and identify the routes with dropped packets.

• Lower the rate of the incoming data or increase the maximum bandwidth

assigned to the route if QoS is set. SYMPTOM: MENCAP 50 has a RED Alarm displayed

The most likely cause of the Alarm LED is the maximum bandwidth has been exceeded. Please refer to the previous item to troubleshoot this problem.

D–2

METRIC CONVERSIONS

Units of Length

Unit

Centimeter

Inch

Foot Yard Mile

Meter

Kilometer Millimeter

1 centimeter — 0.3937 0.03281 0.01094 6.214 x 10-6 0.01 — —

1 inch 2.540 — 0.08333 0.2778 1.578 x 10-5 0.254 — 25.4

1 foot 30.480 12.0 — 0.3333 1.893 x 10-4 0.3048 — —

1 yard 91.44 36.0 3.0 — 5.679 x 10-4 0.9144 — —

1 meter 100.0 39.37 3.281 1.094 6.214 x 10-4 — — —

1 mile 1.609 x 105 6.336 x 104 5.280 x 103 1.760 x 103 — 1.609 x 103 1.609 —

1 mm — 0.03937 — — — — — —

1 kilometer — — — — 0.621 — — —

Temperature Conversions

Units of Weight

Unit Gram Ounce Avoirdupois

Ounce Troy

Pound Avoirdupois

Pound Troy Kilogram

1 gram — 0.03527 0.03215 0.002205 0.002679 0.001

1 oz. avoir. 28.35 — 0.9115 0.0625 0.07595 0.02835

1 oz. troy 31.10 1.097 — 0.06857 0.08333 0.03110

1 lb. avoir. 453.6 16.0 14.58 — 1.215 0.4536

1 lb. Troy 373.2 13.17 12.0 0.8229 — 0.3732

1 kilogram 1.0 x 103 35.27 32.15 2.205 2.679 —

Unit ° Fahrenheit ° Centigrade

32° Fahrenheit — 0

(water freezes)

212° Fahrenheit — 100

(water boils)

-459.6° Fahrenheit — 273.1

(absolute 0)

Formulas

C = (F - 32) * 0.555

F = (C * 1.8) + 32

2114 WEST 7TH STREET TEMPE ARIZONA 85281 USA 480 • 333 • 2200 PHONE

480 • 333 • 2161 FAX

CME-5000 / CME-5010 CME-5100 / CME-5110 - …€¦ · B.3 802.1Q VLAN Support ... MENCAP products...

Documents

Transcript of CME-5000 / CME-5010 CME-5100 / CME-5110 - …€¦ · B.3 802.1Q VLAN Support ... MENCAP products...