Overview of Changes to Previous Edition..............................................................................................................viii
About this Manual ...................................................................................................................................................viii
Conventions and References....................................................................................................................................ix
Reporting Comments or Suggestions Concerning this Manual...............................................................................ix
EMC Compliance........................................................................................................................................................ x
EN55022 Compliance............................................................................................................................................... x
Federal Communications Commission (FCC).......................................................................................................... x
European Low Voltage Directive..............................................................................................................................xi
Limitations of Warranty..........................................................................................................................................xii
Exclusive Remedies................................................................................................................................................ xii
1.3.3Data Mapping and DVB Mapping......................................................................................................1–6
1.3.4Quality of Service ............................................................................................................................... 1–6
B.6.2Installing Data Access Objects (DAO)................................................................................................B-8
B.6.3Installing the CCU Application........................................................................................................... B-9
B.6.4Getting Started .................................................................................................................................. B-10
B.6.5Uninstalling the CCU Application....................................................................................................B-11
B.7Configuring the CCU.................................................................................................................. B-12
B.7.1Specifying CCU Server Properties.................................................................................................... B-12
B.7.2Adding a CCU Server ....................................................................................................................... B-15
B.7.3Deleting a CCU Server...................................................................................................................... B-15
B.8Configuring the CCU to the RADIUS Authentication Server ................................................B-16
B.9Configuring the CCU to the RADIUS Billi ng Server .............................................................. B-19
B.10Configuring the CCU to the Proxy Server................................................................................ B-22
B.11Configuring the CCU to the DTMX5000Gateway................................................................... B-24
B.12Operating the CCU..................................................................................................................... B-26
B.12.1Monitoring the Events Log ............................................................................................................... B-26
B.12.2The CCU Logfile Mechanism........................................................................................................... B-27
B.13Client Parameters Sent from the RADIUS............................................................................... B-30
Figure 1-1. The DTMX5000................................................................................................................................ 1–1
Figure C-1. System Diagram...............................................................................................................................C–5
This manual provides installation and oper at ion info rmation for the Comtech EFData
DTMX5000 IP Gateway. This is a technical document intended for earth station
engineers, technicians, and operators responsible for the operation and maintenance of
the DTMX5000 IP Gateway.
viiiRev. 1
DTMX5000 IP GatewayPreface
Conventions and References
Cautions and Warnings
CAUTION indicates a hazardous situation that, if not avoided, may result in
minor or moderate injury. CAUTION may also be used to indicate other
CAUTION
unsafe practices or risks of property damage.
WARNING indicates a potentially hazardous situation that, if not avoided,
could result in death or serious injury.
WARNING
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 English to Metric
conversions.
Recommended Standard Designations
Recommended Standard (RS) Designations have been superseded by the new designation
of the Electronic Industries Association (EIA). References to the old designations are
shown only when depicting actual text displayed on the screen of the unit (RS-232, RS485, etc.). All other references in the manual will be shown with the EIA designations
(EIA-232, EIA-485, etc.) only.
Trademarks
Other product names mentioned in this manual may be trademarks or registered
trademarks of their respective companies and are hereby acknowledged.
Reporting Comments or Suggestions Concerning this Manual
Comments and suggestions regarding the content and design of this manual will be
appreciated. To submit comments, please contact the Comtech EFData Customer Support
Department.
Rev. 1ix
PrefaceDTMX5000 IP Gateway
EMC Compliance
EN55022 Compliance
This equipment meets EN55022.
This is a Class A product. In a domestic environment, it may cause radio interference in
which the user may be required to take adequate measures.
Federal Communications Commission (FCC)
Note:
All cables shall be shielded.
This equipment has been tested and found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC rules. These limits are designed to provided
reasonable protection against harmful interference when the equipment is operated in a
commercial environment.
This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, may cause harmful
interference to radio communications. Operation of this equipment in a residential area is
likely to cause harmful interference in which case the user will be required to correct the
interference at his own expense.
xRev. 1
DTMX5000 IP GatewayPreface
European Low Voltage Directive
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
!
International Symbols:
ACHTUNG: Zweipolige bzw. Neutralleiter-Sicherung
Alternating Current.
Fuse.
Safety Ground.
Chassis Ground.
Note:
For additional symbols, refer to “Cautions and Warnings” listed earlier in this
preface.
Rev. 1xi
PrefaceDTMX5000 IP Gateway
Warranty Policy
This Comtech EFData product is warranted against defects in material and workmanship
for a period of one year from the date of shipment. During the warranty period, Comtech
EFData will, at its option, repair or replace products that prove to be defective.
For equipment under warranty, the customer is responsible for freight to Comtech
EFData and all related custom, taxes, tariffs, insurance, etc. Comtech EFData is
responsible for the freight charges
the customer. Comtech EFData will return the equipment by the same method (i.e., Air,
Express, Surface) as the equipment was sent to Comtech EFData.
only
for return of the equipment from the factory to
Limitations of Warranty
The foregoing warranty shall not apply to defects resulting from improper installation or
maintenance, abuse, unauthorized modification, or operation outside of environmental
specifications for the product, or, for damages that occur due to improper repack ag ing of
equipment for return to Comtech EFData.
No other warranty is expressed or implied. Comtech EFData specifically disclaims the
implied warranties of merchantability and fitness for particular purpose.
Exclusive Remedies
The remedies provided herein are the buyer's sole and exclusive remedies. Comtech
EFData shall not be liable for any direct, indirect, special, incidental, or consequential
damages, whether based on contract, tort, or any other legal theory.
Disclaimer
Comtech EFData has reviewed this manual thoroughly in order that it will be an easy-touse guide to your equipment. All statements, technical information, and
recommendations in this manual and in any guides or related documents are believed
reliable, but the accuracy and completeness thereof are not guaranteed or warranted, and
they are not intended to be, nor should they be understood to be, representations or
warranties concerning the products described. Further, Comtech EFData reserves the
right to make changes in the specifications of the products described in this manual at any
time without notice and without obligation to notify any person of such changes.
If you have any questions regarding your equipment or the information in this manual,
please contact the Comtech EFData Customer Support Department.
xiiRev. 1
This chapter provides a general description of the DTMX5000 IP Gateway, herein after
referred to as, “the DTMX5000” or “Gateway.”
1.1 Introduction
The DTMX5000 IP Gateway (Figure 1-1) provides a high-speed connection between a
network and a satellite or cable DVB channel. The DTMX5000 is compliant with DVB
MPE standard EN 301.192. (See Appendix A.)
Chapter 1.
INTRODUCTION
1
Figure 1-1. The DTMX5000
Rev. 11–1
IntroductionDTMX5000 IP Gateway
1.2 Description
On the input-side, the DTMX5000 connects to two 10/100 BaseT Local Area Networks
(LANs). To ensure security and support high availability, the DTMX5000 has two
separate 10/100 BaseT Network Interface Cards (NICs).
Transportation NIC
Data from this NIC can only be forwarded to the
DVB channel. This NIC can be connected to an
unsecured network (such as the Internet).
Control and Management NIC
Connected to a secured network.
The DTMX5000 links to a DVB modulator for the Single Channel per Carrier (SCPC)
transmissions, or to a DVB Multiplexer (Mux), connected to a QPSK modulator in the
case of Multiple Channels per Carrier (MCPC) transmissions. The DTMX5000
environment is shown in Figure 1-2.
1–2Rev. 1
DTMX5000 IP GatewayIntroduction
DVB Channel
CATC/Satellite
SUBSCRIBER
SUBSCRIBERS
DVB MUX
(Optional)
RADIUS
Billing
RADIUS
Authentication
Video
Audio
Stream
Informatio n
Server
Server
PSTN Modem to localISP
Router
LAN
Transportation
Gateway
C&M LAN
Line
Auxiliary Transport
Stream Input
Proxy Server
Central
Configuration
NMS
Firewall
INTERNET
Figure 1-2. DTMX5000 Environment
Rev. 11–3
IntroductionDTMX5000 IP Gateway
1.2.1 Proxy Servers
At data request, the requested packet is routed to the proxy server. The proxy server acts
as an intermediary between the final destination and the subscriber. The proxy server
retrieves the data from its cache or the Internet, and returns the requested data to the
subscriber via the DTMX5000.
1.2.2 Central Configuration Unit
The Central Configuration Unit (CCU) can control the DTMX5000. The CCU is an
application running on a Windows NT station at the hub. This application monitors
subscriber’s activities, selects the proxy server for each session, maintains the routing
table on the proxy table server, and interacts with external billing and authentication
systems. (See Appendix B.)
As the subscriber logs On, the CCU notifies the DTMX5000 of the subscriber’s:
• Quality of Server (QoS)
• Group Identification (ID)
• Encryption Parameters
When the subscriber logs Off, the CCU updates the DTMX5000 and collects the
accounting information accumulated by the DTMX5000 for the subscriber. The CCU
connects to the Control and Management (C&M) LAN.
• If the C&M LAN is protected by a Firewall, the appropriate actions must be
taken to ensure connection between the CCU and the server (RIP2 messages
from the CCU should be able to reach the proxy server) and between the CCU
and the clients.
• For additional information, refer to the CCU User’s Manual.
1.2.3 Network Management System
The DTMX5000 is an SNMP V2 client and can be fully controlled by any ANMP-based
NMS application. The MIB parameters include the unit’s configuration, statistic and
diagnostic information. By editing and viewing these parameters, the service provider can
configure and control the DTMX5000.
The NMS also enables the service provider to view and monitor realtime performance
statistics, for example: Client information, memory usage, and packet information. The
statistics can then be evaluated to enhance the QoS offered to subscribers.
1–4Rev. 1
DTMX5000 IP GatewayIntroduction
1.3 DTMX5000 Features
The units’s many configuration options enable service providers to tailor the operation of
the DTMX5000 to suit their specific circumstances, to improve operational performance
and to offer subscribers a high quality, versatile level of service.
DTMX5000 feature include the following:
• IP Multicast, enabling the same message to be sent to many subscribers
simultaneously.
• IGMP client, enabling easy interfacing with standard routers.
• Data mapping mode for IP datagrams, piping, streaming or multiprotocol
encapsulation (SI-DAT 360).
• Compliance with the DVB MPE standard, according to EN 301.192.
• DVB mapping options, enabling the unit to operate as a fully DVB compatible
system, usable with SCPC and MCPC applications.
• Datagram flushing to maintain TCP/IP performance through DVB multiplexers
with internal buffers.
• QoS prioritizing, to enable the service provider to optimize output bandwidth
allocation according to subscribers profiles while guaranteeing minimum bit-rate
requirements.
• Packet encryption for the privacy of DTMX5000 subscribers.
• Support for up to 8192 PID in the output Transport Stream.
• Dual input NICs, one for transportation and the other for control and
management that ensures security and supports high availability.
• Passwords to enable remote NMS access.
• Remote downloads of new versions of the unit’s software and firmware.
• Auxiliary transport Stream (TS) input to combine with the TS generated by the
DTMX5000.
• On-the-Fly configuration, most DTMX5000 parameters can be configured
without stopping the service.
• Support for both static and dynamic users, using the CCU.
• Support for user groups.
The values for these and other options can be set from the local terminal connected to the
DTMX5000 and, with some restrictions, also from a remote NMS.
Rev. 11–5
IntroductionDTMX5000 IP Gateway
1.3.1 IP Multicast
The DTMX5000 receives TCP/IP datagram addressed to subscribers and maps them onto
a DVB compatible MPEG2 transport stream. The DTMX5000 is capable of mapping two
types of datagrams.
Unicast Packets
Multicasts Packets
Each unicast packet is addresses to one individual user.
Multicast packet are add r essed are addressed to a group of users, and are
simultaneously sent to all members of the group. These packets are usually for
the distribution of files, or for streaming audio or video. It is possible to disable
Multicast broadcasting if, example: this type of transmission is being handled by
a separate DTMX5000. It is also possible to enable multicasting for predefined
channels only.
1.3.2 IGMP Client
The DTMX5000 acts as an IGMP client (RFP 1122). For each registered multicast
channel that it forwards, the unit generates an IGMP request and replies to IGMP queries.
The IGMP protocol is managed on the Transportation NIC only.
1.3.3 Data Mapping and DVB Mapping
Data mapping specifies how IP datagrams are mapped onto the output transport stream.
There are three mapping modes.
• Piping
• Streaming
• Multiprotocol Encapsulation
Data piping and data streaming are proprietary mapping, data piping without encryption
and data streaming with encryption. Multiprotocol encapsulation is used for compatibility
with other DVB based systems.
1.3.4 Quality of Service
Quality of Service (QoS) Management is a feature that determines the amount of
bandwidth each subscriber is allocated. Th is feature can eithe r be enabled or disa ble d.
• When QoS is enabled, subscribers receive their bandwidth share according to the
level of service specified in their individual subscription fees.
• When QoS is disabled, the DTMX5000 will provide best effort service, resulting
in the available bandwidth being equally divided among the various subscribers.
1–6Rev. 1
DTMX5000 IP GatewayIntroduction
The DTMX5000 contains two QoS parameters for each user:
• Committed Information Rate
• Maximum Rate
The committed information rate is the maximum the DTMX5000 will allocate to that
individual subscriber. The maximum rate specifics how the overall rate divides among all
subscribers. If at a certain time free bandwidth is available; the subscribers may or may
not receive more than their maximum rate, depending on the specified QoS mode.
1.3.5 On-the-Fly Configuration
Most of the configuration and maintenance parameters of the DTMX5000 can be
configured without disturbing the flow of data. For example: using the NMS, the user can
set a new CIR for a subscriber, without stopping the flow of data to the subscriber.
1.3.6 Packet Encryption
To provide privacy, the data addressed to individual subscribers is encrypted with the
DES algorithm, implementing the CBC mode.
For additional encryption inform ation , refer to F IPS-4 6-2 and FIPS-81 .
1.3.7 Dual Input NIC
To ensure security and support high availability, the DTMX5000 has two input 10/100
BaseT NICs:
Transportation NIC
Control and Manageme nt
Note:
The DTMX5000 supports full functionality even with only one input NIC. In this
case, the C&M input NIC acts as C&M and Transportation.
This NIC does not enable access to the C&M of the
DTMX5000. This NIC can be co nnected to the unsecured
network, such as the Internet. The DTMX5000 design prevents
hackers from gaining acces s to the unit from the transp ortation
NIC.
The Control and Management NIC of the DTMX5000 is via
the Telnet, SNMP, and FTP. This NIC is connected to a
secured C&M network. The C&M NIC can also act as an
additional transportation NIC, enabling the sending of the IP
datagrams from the C&M network to the DVB channel.
Along with security, the two input NICs enable the support the high availability
topologies. High availability will be supported in the next DTMX5000 version.
Rev. 11–7
IntroductionDTMX5000 IP Gateway
1.3.8 Accounting
The CCU informs the DTMX5000 each time a subscriber logs On or Off the system. The
unit creates an account of the packets that each indiv idua l subsc rib ers dow nlo ads, and the
Billing Server later transfers this information for use.
The DTMX5000 also enables full access to the accounting information via the NMS.
This enables an external system to retrieve the information.
1.3.9 Auxiliary Transport Stream Input
If enabled, the Auxiliary Transport Stream (Aux TS) input is compiled with the internal
TS generated by the DTMX5000. The Aux IS input has precedence over the TS
generated by the DTMX5000.
The TS generated by the DTMX5000 can be compiled with the Aux TS input in two
ways:
1. The TS packets generated by the DTMX5000 will be transmitted only when there
is free bandwidth in the output TS of the unit. It is up to the system architecture
to ensure that such free bandwidth is available.
2. The TS packets generated by the DTMX5000 will be transmitted on free
bandwidth, instead of DVB null packets in the Aux TS input.
1.3.10 Downloading Software
To enable new software versions of the DTMX5000 application and firmware to be
downloaded, the NMS system can initiate a TFTP download process from any TFTP
server. The DTMX5000 also supports FTP services.
1.3.10.1 Default Application Fallback
TFTP or FTP may be used to remotely download new software/firmware versions to the
DTMX5000.
In the event that an invalid file is downloaded, the DTMX5000 will lock-up trying to run
the invalid code. To correct this problem, a fixed default software application is provided
on the DTMX5000’s local hard drive. This default application enables the user to
perform the download again.
Note:
The Default application is set by the manufacturer and can not be altered.
Attaching a VGA display, rebooting the DTMX5000, and pressing <D> when prompted
can access this file.
1–8Rev. 1
DTMX5000 IP GatewayIntroduction
1.4 DTMX5000 Configuration
The DTMX5000 must be connected to a local serial terminal in order to enable definition
of the unit’s essential configuration parameters.
The DTMX5000 also can be accessed and configured remotely using the unit’s NMS. In
addition, the unit supports remote configuration via a Telnet terminal.
1.4.1 DTMX5000 Application
The operation of the DTMX5000 is determined by a software application, which is
loaded automatically on Startup. A new release of this application can be downloaded to
the DTMX5000 from a remote station. A new software release also can be downloaded
using FTP.
1.4.2 Local Configuration
The unit’s default operational behavior is determined by a configuration file (
which resides on the unit’s internal hard drive. This file is persistent and is loaded by
default into memory when the DTMX5000 is started up.
CFG.INI
The
in the form of a <DUMB> terminal or PC.
file can be accessed and edited directly from a locally connected terminal,
1.4.3 VGA Display
An optional VGA display can be connected to the DTMX5000, for viewing startup and
operational messages.
1.4.4 Remote Configuration
The DTMX5000 also can be controlled and configured remotely from a Telnet terminal.
Setting the relevant parameters via the local terminal can enable Telnet services.
1.4.5 Firmware
The DTMX5000 contains a Field Programmable Gate Array (FPGA) which performs
most of the mapping of IP datagrams onto the MPEG2 transport stream. The
configuration of this FPGA is downloaded by the DTMX5000 application each time the
DTMX5000 restarts.
CFG.INI
),
Rev. 11–9
IntroductionDTMX5000 IP Gateway
This page is intentionally left blank.
1–10Rev. 1
This section provides important information concerning the installation of the
DTMX5000.
2.1 Overview
Note:
For security reasons, the unit’s vital parameters can only be configured through a
direct serial connection to a local terminal. The remaining parameters can be configured
either via the local terminal or remotely via a Telnet terminal.
An optional VGA display also can be connected to the DTMX5000 using a 15-pin cable
for viewing, boot, and operational messages.
Chapter 2.
INSTALLATION
2
Never install the unit where it may be exposed to rain or moisture. Water in
the unit may damage components and create a shock hazard.
CAUTION
Never remove the cover. This multiplexer has very sophisticated circuitry
that should only be serviced by a fully trained technician.
Removal of the cover might:
Void the warranty
••••
Allow ESD damage to components
••••
Create a shock hazard
••••
Rev. 12–1
InstallationDTMX5000 IP Gateway
2.2 Connect and Configure
Perform the following procedures to connect the local terminal to the DTMX5000 and
establish a communications link.
Note:
Either a PC or a <DUMB> terminal, (a terminal processing no programming
capabilities) can be used as a monitor. A PC may run a terminal emulation application,
such as HyperTerminal, which is supplied as an accessory with Win95. The PC must
have the following minimum requirements:
• Windows OS, with 16 Mbit/s of RAM
• EIA-232 Serial cable
• HyperTerminal application
To connect the local terminal to the DTMX5000, proceed as follows:
1. Attach one end of a EIA-232 serial cable to the back of the DTMX5000’s COM1
connector.
2. Connect the other end of the EIA-232 serial cable to the COM1 or COM2
connector of the PC.
Configure the local term inal as foll ow s:
Note:
To enable a communication link between the terminal and the DTMX5000, it is
necessary to configure the local te rm inal. Th is conf ig urat ion can be perfo rmed with the
standard Windows HyperTerminal application.
The local terminal must be configured to the following parameters:
• Baud rate:9600 bit/s
• Data bits:8
• Parity:None
• Stop bit:1
• Flow Control: Xon/Xoff
2–2Rev. 1
DTMX5000 IP GatewayInstallation
To configure the local termina l to the required p aram eters, proceed to the Start Menu bar
and as follows:
1. Select the Program option to display the Programs menu.
2. Select the Accessories option to display the Accessories menu.
3. Select the HyperTerminal program group. The HyperTerminal program group
window opens.
4. Double-click the Hypertrm.exe
. The Connection Description Windows
opens.
5. Enter a name and choose an icon for the connection.
Rev. 12–3
InstallationDTMX5000 IP Gateway
6. Click OK. The window closes and the Phone Number window opens.
7. In the Connect using field, scroll down the dropdown list and select either
COM 1 or COM 2, depending where the local terminal is connected. Click OK.
The Phone Number window closes and the COM Properties window opens.
2–4Rev. 1
DTMX5000 IP GatewayInstallation
8. In the Port Setting tab, enter the setting exactly as shown.
9. Click OK. The COM Properties window closes and is replaced with the
HyperTerminal window.
Rev. 12–5
InstallationDTMX5000 IP Gateway
2.3 Starting the DTMX5000
Note:
The DTMX5000 can be started once the local terminal has been connected and
configured. The optional VGA display can be connected at this time.
To start up the DTMX5000 and local terminal, proceed as follows:
Note:
Ensure the local terminal is connected and configured.
1. Double-click the icon defined for the local te rminal’s DTMX5000 connection.
The HyperTerminal window opens.
2. Power-up the DTMX5000 and the local terminal. Observe the following:
DTMX5000
VGA Display (Optional)
The booter, which is a software program, loads the application program,
and the DTMX5000’s parameters file (CFG.INI), from disk to memory.
The application program controls all the DTMX5000’s functionality.
Then an FPGA programmable ch i p is loaded. This chip is responsible for
the low level bit manipulation which creates the output transport stream.
A confirmation message is displayed, stating that the booter has loaded
the application program.
3. Observe the following screen, when the connection between the DTMX5000 and
the local terminal is established. The local terminal and the DTMX5000 are now
connected
4. Press <Ctrl>R to refresh the terminal display.
2–6Rev. 1
Loading...
+ 150 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.