INST BHI8x10x InstStd Guide 080109 Rev1

Instructor/Student Guide
Broadband Hub Installation (BHI) Course

iDS Release 8.x and
iDX Release 1.0.x
August 1, 2009
Copyright © 2009 VT iDirect, Inc. All rights reserved. Reproduction in whole or in part without permission is
prohibited. Information contained herein is subject to change without notice. The specifications and information
regarding the products in this document are subject to change without notice. All statements, information, and
recommendations in this document are believed to be accurate, but are presented without warranty of any kind,
express, or implied. Users must take full responsibility for their application of any products. Trademarks, brand
names and products mentioned in this document are the property of their respective owners. All such references
are used strictly in an editorial fashion with no intent to convey any affiliation with the name or the product's
rightful owner.
Document Name: INST_BHI8x10x_InstStdGuide_080109_Rev1.pdf
Document Part Number: GE0000049
ii BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

Contents
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Introduction to Course . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Prerequisite Learner Skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Learner Outcomes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Course Goals and Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Course Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Contacts, Questions and Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Module 1: Introduction to Broadband Hub Installation

1.1 Overview of iDirect’s Broadband Satellite Technology . . . . . . . . . . . . . . . . . . . 8
1.2 Spread Spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3 Mesh Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.3.1 Mesh-enabled Remote Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.3.2 Mesh Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.3.3 NMS Control of Mesh Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.3.4 Monitoring Mesh Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.4 TRANSEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.4.1 TRANSEC Key Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.4.2 TRANSEC Remote Admission Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.5 iSCPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.5.1 iSCPC IP Addressing Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1.5.2 iSCPC Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1.6 DVB-S2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.6.1 DVB-S2 Key Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1.6.2 DVB-S2 in iDirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x iii
1.6.3 Configuring and Monitoring DVB-S2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Module 2: Introduction to System Installation

2.1 iDirect Hub Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
2.1.1 20-Slot Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.1.2 Reference Clock Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2.1.3 Chassis Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
2.1.4 EDAS Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
2.1.5 Hub Chassis Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
2.1.6 Chassis Slot Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Module 3: Hub Installation Paperwork, Processes and Procedures

3.1 Customer Familiarization Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.1.1 Downloading the Training Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.1.2 Providing iBuilder Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1.3 Providing iMonitor Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1.4 Providing iSite Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Module 4: The As-Built Document Preparation

4.1 Introduction and Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.2 Completing the As-Built Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.2.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.2.2 Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
iv BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

List of Figures
Figure 1. Example of Link Budget Analysis Results . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 2. Example of an IP Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 3. Example of a Packing Slip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 4. Example of a Network Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 99
BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x v

vi BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x
List of Tables
Table 1. Course Modules and Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 2. BHI Course Daily Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Table 3. MODCOD Indexes for Multicast Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x vii
viii BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x
Acknowledgements
This training manual is the culmination of hard work by several individuals and groups within
the iDirect family. As the Senior Course Developer I am grateful for the many employees and
departments who have written material, provided important feedback, encouragement, and a
thorough review of this document before the final copy is distributed to our valuable
customer contingency.
For the development and production of this training manual itself I feel a deep sense of
gratitude:
• to Trish Jenkins for her tireless devotion to researching, writing and compiling all the
information from multiple sources included in this training manual. It is easy to gather
information, but to inject a sense of order and clarity to the random ideas, opinions and
thoughts of many individuals and groups was a monumental task she completed with the
forethought and tenacity needed to deliver an outstanding product. Thanks for rising up
to the challenge to produce a product of brilliance under any and all circumstances and
conditions.
• to Eric Rosales, the TAC, and all the other individuals for providing feedback, information,
insight, correction and technical guidance which enable this labor of love to be
completed in record time.
All of you deserve more than the simple “Thank You” that I have included here. You all have
my gratitude for making Broadband Hub Installation an outstanding training manual.
Bruce M. Minor
Senior Course Developer
BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x ix

x BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x
Introduction to Course
Overview
The iDirect BHI course is intended for those personnel who are responsible for the installation
and configuration of iDirect satellite communications products and networks. The course
provides the learner with the skills necessary to install and configure a typical iDirect satellite
network. The learner’s main focus will center solely on the processes and procedures
associated with the hub installation guide that includes the many steps necessary to
successfully install and configure an iDirect Broadband hub.
Learners will also learn how to perform the iDirect Acceptance Test Plan, a set of test
procedures which are used to certify correct hub component installation. In addition, they will
also learn how to successfully complete the iDirect Hub As-Built document which includes all of
the hub component configuration information.
The iDirect training course includes sections on Network operations and acquisition with
emphasis on network troubleshooting and remote installation and acquisition. Expanding on
basic theory, the course will provide an in depth understanding of the iDirect hardware and
software platform up to, and including iDX 1.0.x. The student will complete a number of hands
on exercises using the iDirect platform to reinforce the structured course material.
Presented in a clear and technical manner, the entire course provides a combination of
lecture, demonstrations, and practical exercises that will give the learner a comprehensive
overview of hub installation from the iDirect perspective.
Learners are evaluated during the course of instruction to ensure that they have attained a
level of understanding and proficiency that will enable them to install all iDirect and third-
party equipment associated with hub installation, as well as to diagnose problems as they
occur.
Course Outline:
• Introduction to Broadband Hub Installation
– DVB-S2 and Other Important Features
• Introduction to System Installation
• Hub Installation Paperwork, Processes, and Procedures
• Lab:
– Configuration of the Hub Equipment
BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 1

– Acceptance Test Plan
• As-Built Document Preparation
• Review
• Q&A with iDirect Subject Matter Experts (Only for Herndon training sessions)
• Course Critique and Certificate Presentation
Note: Training provided is based on the particular version utilized or

requested by the organization if conducted on site. All BHI
training in Herndon will be conducted according to the latest
software versions and hardware equipment.
Handouts will be provided as required to supplement existing course material and provide
additional up-to-date detail on currently released software and hardware components. All
learners will receive, in addition to the Instructor/Student Guide, a BHI Student Workbook
which contains all applicable exercises/labs for the course.
Prerequisite Learner Skills

Each learner attending an iDirect Broadband Hub Installation course must have successfully
completed the basic Installation, Operation and Maintenance course. A working knowledge and
familiarity with iDirect equipment is required in addition to an intermediate to advance
understanding of satellite communications and Internet Protocol theory. A fundamental
understanding of VSAT technology and normal eye hand coordination for parts assembly is also
required. In addition, basic software installation is also required since each learner will be
required to install the iVantage suite of applications on their laptop.
Learner Outcomes
1. Each learner upon completion of this course will be able to install the applicable
applications from the iVantage suite.
2. Each learner upon completion of this course will be able to load image packages, BSP
packages, and options files using iSite to the Hub Line Card and the Remote.
3. Each learner upon completion of this course will be able to perform basic routine
maintenance on their iDirect network utilizing principles acquired during the lecture and
hands-on portions of this course.
4. Each learner upon completion of this course will be able to perform basic troubleshooting
of an iDirect network and identify escalation protocol to solve more complex issues.
5. Each learner upon completion of this course will understand how to access information by
utilizing the TAC web page.
6. Each learner upon completion of this course will be able to satisfactorily perform a
complete install of hub equipment.
7. Each learner upon completion of this course will be able to successfully load the required
software on the Protocol Processor and the NMS.
2 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

8. Each learner upon completion of this course will be able to successfully complete all
associated paperwork required for delivery to the Program Manager: i.e. As-Built
Document and Acceptance Test Plan.
9. Each learner will understand all requirements necessary to initiate and prepare for an
iDirect hub installation. (Work-orders, Packing List, Link Budgets)
Course Goals and Objectives

This course is comprised of four learning modules, described in Table 1, and a comprehensive
workbook.
Table 1. Course Modules and Goals
Module Title Goal

Module 1, Introduction to Broadband Through lecture, presentation and visual displays each learner will
Hub Installation understand, identify, and explain in detail each of the critical items,
hardware equipment, software, and paperwork involved in a complete
iDirect hub installation, as well as understand, explain and demonstrate
the important features which make up the DVB-S2 theory of operation.
Module 2, Introduction to System Through lecture, presentation and visual display each learner will fully
Installation understand how to properly rack mount the iDirect hub equipment. The
learner will also walk through a Hub Line Card installation exercise.
Module 3, Hub Installation Through lecture, presentation and visual display each learner will fully
Paperwork, Processes and understand which items are required before going to the site, what to
Procedures expect when you first arrive to the install location, and how to verify
the preinstallation checklist.
Module 4, The As-Built Document Through lecture, presentation and visual display each learner will be
Preparation able to understand, explain and demonstrate how to properly prepare
an As-Built document for program manager review and verification.
In addition, learners will perform the following hands-on lab exercises:

Configuration of the NMS Servers
1. Configure the NMS Server
2. Set the Date and Time on the Servers
3. Install the NMS Software License File
4. Change the Linux Password
5. Configure the Protocol Processor Blade
6. Configure the EDAS/Control Module IP Address
7. Install the NMS Client Software
8. Configure the Switch IP address and EDAS Port
9. Configure the IP Address of Each Hub Line Card

10. Commission the Hub Carrier
The Acceptance Test Plan
11. RCM Failover Testing
12. Hub Chassis Backplane Testing
13. Hub Line Card Failover Testing
14. Protocol Processor Failover Testing
15. Hub Power Failure Simulation Testing
16. Connectivity Testing
17. Performance and Throughput Testing
18. ACM Verification
Instructions for these lab exercises are contained in the BHI Student Workbook.
Course Administration
1. Welcome
2. Instructor Introduction
3. Points of contact
4. Training Hours and Attendance
5. Break and Lunch
6. Restroom
7. Attire and Professional Decorum
8. Rules concerning electronic devices (Cell phones, pagers, and other devices)
9. Faxes, UPS, Fed-Ex
10. Accommodations
11. Site Emergency Procedures
12. Course Introduction
13. Learner Skills and Knowledge Review
14. Course Goals and Objectives
15. Course Daily Activities: see Table 2 on page 5
16. Course Materials (Learner Manuals, Workbooks, etc.)
17. Lab Safety
18. Final Examination
19. Learner Introductions

Table 2. BHI Course Daily Activities
Day One Day Two Day Three Day Four Day Five
0830 – 0920 Administrative Module 2, Lab Exercise: Lab Exercise: Module 4, The
and Module 1, Introduction to Configuration of The Acceptance As-Built
Introduction to System the Hub Test Plan Document
Broadband Hub Installation and Equipment Preparation
Installation Lab
0930 – 1020 Module 1, Module 2, Lab Exercise: Lab Exercise: The Module 4, The
Introduction to Introduction to Configuration of Acceptance Test As-Built
Broadband Hub System the Hub Plan Document
Installation Installation and Equipment/Review Preparation
Lab
1030 – 1120 Module 1, Module 3, Hub Lab Exercise: Lab Exercise: The Module 4, The As-
Introduction to Installation Configuration of Acceptance Test Built Document
Broadband Hub Paperwork, the Hub Plan Preparation
Installation Processes and Equipment/Review
Procedures
1130 – 1150 Review/Q & A Review/Q & A Review/Q & A Review/Q & A Review/Q & A
1150 – 1250 Lunch Lunch Lunch Lunch Lunch
1300 – 1350 Module 1, Module 3, Hub Lab Exercise: Lab Exercise: The Final Exam
Introduction to Installation Configuration of Acceptance Test (optional)
Broadband Hub Paperwork, the Hub Plan/Review
Installation Processes and Equipment/Review
Procedures
1400 – 1450 Module 1, Lab Exercise: Lab Exercise: Lab Exercise: The Final Exam and
Introduction to Configuration of Configuration of Acceptance Test Exam Review
Broadband Hub the Hub the Hub Plan/Review (optional)
Installation Equipment Equipment/Review
1500 – 1550 Module 1, Lab Exercise: Lab Exercise: Lab Exercise: The Certificate
Introduction to Configuration of Configuration of Acceptance Test Presentation and
Broadband Hub the Hub the Hub Plan/Review Surveys
Installation Equipment Equipment/Review
1600 – 1630 Review/Q & A Review/Q & A Review/Q & A Review/Q & A Dismissal
1630 – 1700

Contacts, Questions and Answers
Patsey Rios – Registration/Training Program Coordinator
• email: prios@idirect.net
• phone: 703-648-8240
Bruce Minor – Course Content
• email: bminor@idirect.net
• phone: 703-648-8169

Module 1: Introduction to
Broadband Hub
Installation
Goal: Through lecture, presentation and visual display, each learner will understand, identify,
and explain in detail each of the critical items, hardware equipment, software, and paperwork
involved in a complete iDirect hub installation, as well as understand, explain and demonstrate
the important features which make up the DVB-S2 theory of operation.
Objectives:
1. The learner will be able to identify each hardware component of the basic iDirect
network.
2. The learner will be able to name each software application associated with the basic
iDirect network and explain its purpose within the network.
3. The learner will be able to identify and explain the critical features of any iDS/iDX
network hardware.
4. The learner will be able to understand the differences between the iDirect Legacy and
DVB-S2, iNFINITI and Evolution series of products.
5. The learner will understand how each feature is utilized in an iDirect iDS/iDX network.

Introduction to Broadband Hub Installation
1.1 Overview of iDirect’s Broadband Satellite

Technology
The above slide shows the overall topology of the basic iDirect network. The hub end of the
basic iDirect network houses the NMS and this is where you will perform the task of
communicating or working with the iDirect software suite. This is also the focal point of this
training. The software applications you should be most concerned with, within this basic
topology, are iBuilder, iMonitor and iSite. However, the software installation for the Protocol
Processor and the NMS is just as important
Your utilization of each of these applications/software in conjunction with the equipment you
install will, to some degree, determine the successfulness of your installation.
As a review, the Downstream direction, according to iDirect, contains the traffic from the hub
to the remotes with a broadcast transmission to all remotes. Of course that would mean that
the Upstream direction is the transmission from the remotes to the hubs. This is the TDMA
frame structure.

Overview of iDirect’s Broadband Satellite Technology
iSite is the software used to communicate with the remotes locally. You can read different
fields using iSite as well as download the BSP, image package, and the options files. Again, the
applications iBuilder, iMonitor, and iSite work together to form a powerful suite of tools.

The hub equipment and the software work in conjunction to provide a stable, secure and
functional system in iDX 1.0.x which supports DVB-S2 outbound carriers and TDMA inbound
carriers. iDirect offers three different hub chassis models:
• Series 15000 5IF 20 slot chassis
• Series 12000 4-slot chassis
• Series 12200 Industrial 4-slot
The Series 15000 5IF 20 slot chassis can support multiple bands, transponders, and satellites
as well as Star, Mesh, and SCPC topologies.
The Series 12000 Universal 4-slot chassis is a compact, 19-inch rack-mountable chassis that
provides 1 IF or 4 IF satcom interfaces. It supports TDMA star, Mesh, and SCPC topologies.
The Series12200 Universal Hub (Industrial 4-slot) chassis is a cost-effective, compact, and
durable solution for military, comms-on-the-pause, first responders, disaster recovery, or other
field operations, who will benefit from the flexibility, efficiency, and reliability of an iDirect
hub solution. The hub consists of 4+1 slots and up to 4 IF interfaces, enabling multiple in- and
outbound networks on four satellites.

One of the most important items to remember is that the 5IF chassis cannot provide 10MHz and
DC voltage from the chassis. The 4 Slot Hub can provide DC voltage when the Optional Power
Module (OPM) is installed. The OPM comes in two models: 24V and 48V. The 4-slot huh can
provide the 10 MHz reference with the correct linecard installed in slot one (iNFINITI M1D1).
The M1D1 linecard must have a sticker indicating that it has the 10MHz option.
If you would like to view the complete list of differences between the 5IF hub and the 4 Slot
Hub, you may consult the hardware user’s guides which are provided on the Technical
Assistance Center’s web page.
The Evolution XLC-10 line card is capable of supporting DVB-S2 with Adaptive Coding and
Modulation (ACM) on the outbound (or downstream), as well as iNFINITI TDM outbound carriers
(in future releases). The line card fits in any new or existing universal hub chassis and supports
data rates up to 156 Mbps.
The XLC-10 supports a single DVB-S2 modulator producing a DVB-S2 outbound carrier through
an L-band interface. The XLC-10 also works in conjunction with existing iNFINITI line cards such
as the M0D1 or M1D1 used in receive-only mode.

A variety of iNFINITI hub line cards are offered, depending on your network’s needs. They fit
in any new or existing universal hub chassis, making network expansion easy. These line cards
(depending on the model) can reach IP data rates of up to 20 Mbps on the outbound and up to
10 Mbps on the inbound, based on TDM/deterministic MF-TDMA. It is ideally suited for
broadband applications such as Internet and VPN access, along with real-time VoIP and
videoconferencing.

The iDirect 12100 series™ Universal 4-Slot Hub is the highest performance remote networking
solution available today, offering tremendous flexibility, security, and network capacity.
Developed to meet the most demanding user requirements, 12100 series Universal 4-Slot Hubs
are ideal for military, network carriers, or high end enterprise customers requiring reliable,
fast, secure, and encrypted data communications.
• Scalability — Supports multiple networks with varying requirements for frequencies,
topologies, or bandwidth; interfaces with multiple satellites; grows as customer needs
expand
• Flexibility — Supports TDM/ D-TDMA Star, Mesh, SCPC, and Hybrid networks; supports
thousands of sites with multiple sub-networks from a single hub; “One-box” solution
includes satellite modem, IP router, TCP optimization, QoS, encryption
• Efficiency — Superior bandwidth management; deterministic TDMA allows 98% payload
efficiency; Fast Frequency Hopping (MF-TDMA) combined with rapid bandwidth allocation;
TPC encoding ensures 10-9 BER, providing fiber-like reliability to BER sensitive TCP/IP;
Spread Spectrum technology allows use of very efficient, ultra-small antennas; advanced
QoS and IP routing capabilities

The rear panel consists of two redundant fans, a Fan Status Module (FSM), two Reference Clock
Modules (RCMs), two redundant power supplies, a one-port or optional four-port IF Module
(IFM), and two optional Outdoor unit Power Modules (OPMs). A view of the rear panel with 1-
IFM is shown.

The iDirect SkyMonitor 1880 Spectrum Analyzer is a fully integrated, always-connected, high
performance spectrum analyzer for easy and complete monitoring and troubleshooting of
iDirect network carriers.
SkyMonitor is the industry’s first fully-integrated spectrum analyzer of multiple carriers,
providing instant access to real-time spectral data of inbound and outbound carriers.
Network operators can dramatically reduce the time and cost required to diagnose
performance issues from RF interference or other carrier-related anomalies.
• Fast and accurate spectrum measurements — SkyMonitor’s state-of-the-art digital
technology and Fast Fourier Transformation (FFT) provides the capability to quickly and
accurately measure of all iDirect carriers and monitor peak power, spurious signals, carrier
spacing, and rogue carriers.

• Easy-to-use integrated solution — The rack-mounted SkyMonitor is fully integrated with

iDirect’s award-winning iVantage NMS providing local or remote access. With full
integration into a single, familiar GUI interface, SkyMonitor enables network operators to
eliminate the need for lengthy training and set-up. Through iVantage, the operator can
easily drill down on any hub line card to monitor the real-time spectrum of its transmit or
receive carriers. Stored configurations auto-tune to the correct frequency for instant
analysis.
• Powerful and intuitive analysis tools — SkyMonitor is a cost effective solution that bridges
the gap between typical Layer 2 and above network analysis and Layer 1 RF spectrum and
power analysis in a single GUI. When used in conjunction with iVantage’s standard features,
SkyMonitor allows for simultaneous analysis of RF and IP layers resulting in improved
troubleshooting capabilities.

With the capability to retrieve and view stored displays and compare real-time traces with
historical data, SkyMonitor enables network operators to perform powerful analysis even with
minimal detailed knowledge of standard spectrum analyzers or RF measuring
Note: The figure above shows an actual iDirect carrier being monitored by a
SkyMonitor spectrum analyzer.

The keypad on the right allows you to temporarily change the RF port settings, capture data,
recall captures, and save screen images. These functions are discussed in detail later in this
section. You can select a new SkyMonitor port by clicking a port number in the RF Port section
of the keypad. (If you launched SkyMonitor from a line card, the RF port configured for the
carrier is automatically selected.)
• Click the Start button to begin monitoring your preconfigured carrier or RF port.
• Click the Stop button if you want to stop monitoring the bandwidth and clear the display.

Spread Spectrum
1.2 Spread Spectrum
Spread Spectrum (SS) is a transmission technique in which a pseudo-noise (PN) code is

employed as a modulation waveform to “spread” the signal energy over a bandwidth much
greater than the signal information bandwidth. The signal is “despread” at the receiver by
using a synchronized replica of the pseudo-noise code. By spreading the signal information over
greater bandwidth, less transmit power is required. The purpose of Spread Spectrum is to
minimize adjacent satellite interference.
The initial application was in the development of military guidance and communication
systems. By the end WW II, SS for jamming resistance was already a familiar concept. During
subsequent years, SS investigation was motivated primarily by the desire to achieve highly
jam-resistant communication systems.
Spread Spectrum requires transmission bandwidth much greater than the minimum bandwidth
required to transmit the information (data).
In an iDirect network, SS requires a M1D1-TSS hub line card and remote model 8350. The M1D1-
TSS HLC occupies two slots on chassis. It has a daughter board.

Spreading takes place when the input data x(t) multiplied by the PN data g(t), which results in
the transmit wide transmission bandwidth y(t). This signal is fed to the modulator (DSS).
Y(t) = x(t).g(t) ÅÆ Y(W) = X(W) * G(W)
Despreading takes place at the receiver side by correlating the received signal Y(W) with PN
G(W) to get the X(W).
Y(W) * G(W) Æ X(W)
Spread Spectrum (SS) transmission is supported in both TDMA and legacy SCPC configurations.
Spread spectrum is not available on DVB-S2 Downstream carriers. SS mode is employed in
iDirect networks to minimize adjacent satellite interference (ASI). ASI can occur in
applications such as Comms-On-The-Move (COTM) because the small antenna (typically
submeter) used on mobile vehicles has small aperture size, large beam width, and high
pointing error which can combine to cause ASI. Enabling SS reduces the spectral density of the
transmission so that it is low enough to avoid interfering with adjacent satellites.
Conversely, when receiving through a COTM antenna, SS improves carrier performance in cases
of ASI (channel/interference).

Spread Spectrum
The iDirect SS is an extension of BPSK modulation in both Upstream and Downstream. The
signal is spread over wider bandwidth according to a Spreading Factor (SF) that you select.
You can select a Downstream Spreading Factor of 1, 2, 4 or 8. You can select an Upstream
Spreading Factor of 1, 2, 4, 8 or 16.
Note: A Downstream Spreading Factor of 8 is only available for Evolution Hub Line
Cards transmitting to Evolution Remotes. Upstream Spreading Factors of 8 and
16 are only available for Evolution Remotes transmitting to Evolution Hub Line
Cards.
Spread Spectrum Rates:
• Downstream carrier
– Minimum rate for all Spreading factors is 64 Ksps
– SF =1, 15000 ksps
– SF = 2, 7500 Ksps
– SF = 4, 3750 Ksps
• Upstream carrier

– Minimum rate for all Spreading factor is 64 Ksps

– SF =1, 7500 ksps
– SF = 2, 3750 Ksps
– SF = 4, 937.5 Ksps

Mesh Networks
1.3 Mesh Networks
iDirect’s Mesh offering provides a full-mesh solution implemented as a mesh overlay network
superimposed on an iDirect star network. The mesh overlay provides direct connectivity
between remote terminals with a single trip over the satellite, thereby halving the latency and
reducing satellite bandwidth requirements. As with other iDirect features, mesh is being
implemented in a phased manner. The first phase was delivered in IDS Release 7.0. Phase II of
mesh is available beginning with Release 8.2.
iDS Release 8.2 introduces the second phase of iDirect Mesh. Mesh Phase II adds the following
enhancements to the Mesh feature:
• The ability to configure multiple mesh inroutes per inroute group
• The ability to configure separate data rates for star and mesh inroutes
• Support for TRANSEC over mesh
In the Mesh Phase I release (7.0, 7.1 or 8.0), you are limited to a single inroute per mesh
inroute group. In addition, TRANSEC over mesh was not supported in Mesh Phase I.

in a typical star network, the one-way transmission delay from user A to user B over a
geosynchronous satellite averages 550 ms. The extended length of the delay is due to the
“double-hop” transmission path: remote A to the satellite; the satellite to the hub; the hub
back to the satellite; and the satellite to remote B. This transmission delay, added to the voice
processing and routing delays in each terminal, results in an unacceptable quality of service for
voice. In addition, the remote-to-remote transmission requires twice as much satellite
bandwidth as a single-hop call.
A more cost-effective use of satellite bandwidth and improved quality of service for real-time
traffic can be achieved by providing remote-to-remote connections over a single satellite hop,
as provided in mesh networks.
One advantage of the iDirect Mesh implementation is that mesh remote terminals continue to
be part of the star network. This allows the monitor and control functions and the timing
reference for the mesh network to be provided by the existing hub equipment over the SCPC
downstream carrier.
In an iDirect Mesh network, the hub broadcasts to all remotes on the star outbound channel.
This broadcast transmits user traffic as well as the control and timing information for the
entire network of inbound mesh and star channels. The mesh remotes transmit user data on
mesh TDMA inbound channels, which other mesh remotes are configured to receive.
Note: The following remote model types are supported over iDirect Mesh: iNFINITI
5300/5350; iNFINITI 7300/7350; iNFINITI 8350; Evolution e8350; iConnex-100;
iConnex-700; and iConnex e800.
Each mesh remote is configured with a “home” mesh inroute. A mesh remote receives its home
inroute using the second demodulator on the Indoor Unit (IDU). All mesh transmissions to the
remote must be sent on the home inroute of the destination remote. Therefore, any peer
remote sending single-hop data must frequency hop to the peer’s home inroute before
transmitting.
Note: iDirect Mesh is logically a full-mesh network topology. All remotes can
communicate directly with each other (and the hub) in a single-hop. This is
accomplished by allowing the remote to receive both the outbound channel from
the hub and its home TDMA mesh inbound channel. This is sometimes referred to
as a star/mesh configuration. When referring to the iDirect product portfolio,
“star/mesh” and “mesh” are synonymous.
1.3.1 Mesh-enabled Remote Restrictions

Mesh-enabled remotes must belong to the same Inroute Group (IG)
• Mesh Inroute Group is limited to a single Upstream carrier
• Frequency Hopping is not supported
• Link Encryption (AES) of mesh traffic is not supported
Mesh-enabled remotes do support full QoS for all traffic
• Standard Mesh traffic is UDP, or Real-time data
• Normal, accelerated TCP traffic must pass through the hub

Mesh Networks
Upstream SAR is always enabled

• SAR Segment size set to the same value
• iDirect recommends default segment size be used
Common parameters shared across all mesh IG remotes
• TCP Acceleration mode
• UDP Header & UDP Payload Compression
• If Mesh enabled, @ IG, then ALL remotes use common parameters
Support for Single-Hop TCP traffic exists
• Requires TCP Acceleration to be disabled for all mesh IG remotes
• All TCP traffic performance will be affected, star or mesh
1.3.2 Mesh Hardware Support and Requirements

Only 5300, 7300, & 8300 iNFINITI remotes can be used for mesh
• ODU must be sized properly for mesh Upstream carrier
• Phase Locked Loop (PLL) LNBs required for all mesh capable & configured remotes
• PLL LNBs not required for typical, traditional star networks
Only iNFINITI line cards and Private Hubs support mesh
• M1D1 HLC must transmit Mesh Downstream carrier
• Hub must monitor its own SCPC loopback carrier
– Precludes the use of regional or spot beam coverage
– Same satellite/transponder must be used (Upstream & Downstream)
– Private Hub must use externally referenced PLL LNB for the hub ODU
Mesh remotes & mesh hub listen to loopback on its uplink carrier
• Values recorded (iBuilder) for all clear-sky (C/N) commissioning results
• Loopback values (used to manage Uplink Control Process, or UCP)
• Over-the-air values for Upstream also important; collected & recorded
1.3.3 NMS Control of Mesh Networks

iBuilder provides all needed tools for managing mesh networks, including some changes
specifically for mesh.
• All mesh restrictions checked automatically, preventing errors
• Mesh can be turned On or Off at different levels
– Turning it On/Off for any remote affects only that remote
– Turning it On/Off at Mesh TX HLC or Inroute Group affects all mesh IG remotes
• Acquisition/Uplink control parameters now set at each the Inroute Group for configured
remotes
• Power adjustment control range is now relative to nominal Carrier-to-Noise ratio, not
absolute C/N as before

• Specify the fixed nominal value, with fine & course adjustment ranges now set relative to
this nominal value
1.3.4 Monitoring Mesh Networks

iMonitor provides all needed tools for monitoring mesh networks with some new additions for
mesh.
• Downstream SCPC loopback carrier is closely monitored
– Timing (SCPC Symbol offset)
– Frequency (SCPC frequency offset)
– Power (SCPC SNR cal)
• Upstream TDMA loopback carrier is also monitored closely and performance reported
• Additional line card Stats included for mesh
– SCPC frame lock status – lock status of SCPC loopback
– SCPC lost lock count – number of times mesh line card lost lock on SCPC loopback since
last stats message
iMonitor provides other valuable stats specifically for monitoring mesh configured remotes:
• Remote Status messages contain additional mesh detail
– SCPC C/N – Downstream C/N at remote site
– TDMA Loopback C/N – Upstream C/N on loopback at remote
– TDMA Offsets – Symbol & Frequency
– Currently used for debug only; adjustments made thru the hub UCP
– Tx/Rx Data bytes – Reliable (TCP) & Unreliable (UDP) counted
– Tx/Rx Control bytes – Also monitors overhead traffic, in bytes
iMonitor provides mesh traffic statistics:
• Mesh Traffic Graph displays mesh traffic statistics
– Data collected is the same as on the SAT Traffic Graph
– Data combined for all remotes or displayed by individual remote
• Criteria for viewing stats on mesh-enabled remotes
Remote-to-remote traffic uses the TDMA Upstream carrier:
• On SAT Traffic Graph, Upstream includes mesh traffic
• On Mesh Traffic Graph, non-mesh traffic is not included
• Each byte in mesh displayed here is actually counted twice; once for the sender, once for
the receiver
• Mesh traffic never shows up on the IP Stats Graph
• IP Stats represent traffic upstream from the PP
iMonitor provides a remote-to-remote mesh Probe
• Probe Mesh allows examination of a pair of mesh remotes for:
– The number of attempts to transmit to peer remote
– The number of bursts successfully transmitted to the peer

Mesh Networks
– The number of bursts received from the peer

– The number of bursts received, but dropped by the peer
• Right click a mesh remote, select Probe Mesh to select pair
• Probe Mesh is primarily for debug support
• Adds to processing time on remotes
• Adds additional debug info, consuming additional bandwidth
Long-Term Bandwidth Usage Report for Mesh networks available
• Allows fast, flexible bandwidth usage detail
• A percentage of max. mesh capacity is calculated

1.4 TRANSEC
TRANSEC is based on AES 256 bit encryption. There are certain hardware requirements in order
to utilize TRANSEC in the iDirect system.
Above you will see these hardware requirements. TRANSEC creates a continuous pattern of
encrypted data at layer 2, meaning all packets other than the management and control
information being sent to and from the remotes, are encrypted as seen in the diagram above.
• Packets extracted from the data queue are always encrypted
• Packets sent from the bypass queue are always unencrypted
• Burst Time Plan or BTP, messages can be sent in either mode
• BTP sent in the clear is only used for initial admission control
• Traffic sent in the clear bypasses the next two blocks and precedes to physical framing and
FEC
iDirect achieves full TRANSEC compliance by presenting to an adversary who may be
eavesdropping on the RF link a constant “wall” of fixed-size, strongly encrypted (such as

TRANSEC
Advanced Encryption Standard (AES) and 256 bit key Cipher Block Chaining (CBC) Mode) traffic
segments, which do not vary in frequency in response to network utilization.
Other than network messages that control the admission of a remote terminal into the
network, all portions of all packets are encrypted, and their original size is hidden. The
content and size of all user traffic (Layer 3 and above), as well as network link layer (Layer 2)
traffic is completely indeterminate from an adversary’s perspective. Further, no higher layer
information is revealed by monitoring the physical layer (Layer 1) signal.
The solution includes a remote-to-hub and a hub-to-remote authentication protocol based on
standard X.509 certificates designed to prevent man-in-the-middle attacks. This
authentication mechanism prevents an adversary’s remote from joining an iDirect TRANSEC
secured network. In a similar manner, it prevents an adversary from coercing a TRANSEC
remote into joining the adversary’s network. While these types of attacks are extremely
difficult to achieve even on a non-TRANSEC iDirect network, the mechanisms put in place for
the TRANSEC feature render them completely impossible.
All Hub Line Cards and remote model types associated with a Protocol Processor must be
TRANSEC compatible. The only iDirect hardware that operate in TRANSEC mode are the M1D1-
T and M1D1-TSS; the iNFINITI 7350 and 8350 remotes; and the iConnex 700 remotes. Therefore
these are the only iDirect products that are capable of operating in a FIPS 140-2 Level 1
compliant mode.
For more information, see the chapter “Converting an Existing Network to TRANSEC” of the
iBuilder User Guide.
Note: TRANSEC is not supported on DVB-S2 outbound carriers.

The Initialization Vector (IV) provides a method of encryption known as Cipher Block Chaining.
Past encryption methods allowed encryption of the same plain text with the same key results
in the same ciphertext which resulted in a considerable threat to security. In other words, if
the same text information was being encrypted, then the protocol would use the same cypher
block and cypher key in order to encrypt the same type of information. The IV solves this
problem by providing a random block of bits which allow stream or block ciphers to be
transmitted in any of several different modes of streaming. These random bits of information
can be transmitted with a unique stream of information but using the same encryption key
without having to go through a re-keying process.

TRANSEC
1.4.1 TRANSEC Key Management
TRANSEC Key Management - All hosts must have X.509 public key certificates. The iDirect CA
Foundry issues the certificates to all NMS, protocol processors, TRANSEC hub line cards, and
TRANSEC remotes. All PP blades must be equipped Soekris 1201 or 1401 encryption card for key
management. The key distribution protocol, key rolling, and host keying protocol are based on
standard techniques within X.509 based PKI.
This protocol describes how hosts are originally provided an X.509 certificate from a
Certificate Authority. iDirect provides a Certificate Authority Foundry module with its TRANSEC
hub. Host key generation is done on the host in all cases.

Key Distribution Protocol – Used to validate and establish a chain of trust based on the
contents. iDirect TRANSEC utilizes standard X.509 certificates. After completion of sequence a
key update message is provided in an unsolicited fashion. The data structure is utilized to
complete key update (key roll).

TRANSEC
Key Rolling and Key Ring

• Current, Next, Fallow
• Two bit ID field (in Encryption Header)
• Key update consists of generating a new key
• Key roll mechanism allows for multiple keys in place
• By default iDirect TRANSEC solution rolls any symmetric key every 2 hours but it is user
configurable

1.4.2 TRANSEC Remote Admission Protocol

Remotes acquire into the network over the clear channel. Specifically, a protocol processor
blade is designated to be in charge of controlling remote admission into the network.
1. The system will conceptually generate two time plans, one of which is the normal time
plan utilized to indicate to remotes which slots in which inroutes they may burst on. This
time plan is always encrypted. The second time plan is not encrypted and indicates the
owner of the acquisition slot (i.e., who may acquire) and also who may burst on selected
slots unencrypted. The union of the two time plans covers all slots in all inroutes.
2. The time plans are forwarded and broadcast to all remotes in the normal method.
3. The remote designated in the acquisition slot acquires in the normal fashion.
4. Once the physical layer acquisition occurs, the remote must follow the key distribution
protocol outline above before it is trusted by the network, and for it to trust the network
it is a part of. This step must be carried out in the clear. Therefore remotes in this state

TRANSEC
will request bandwidth normally and will be granted unencrypted TDMA slots as described
in step 1.
5. Once authentication is complete, the key update message must also complete in the
clear. The actual symmetric keys are encrypted using the remote’s public key information
obtained in the exchanged certificate.
6. Once the symmetric key is exchanged the remote enters the network as a trusted entity,
and begins normal (completely encrypted) operation.

Here we get a look at the TRANSEC Upstream operation. BTP’s are forwarded to all remotes in
the normal method first. The remote designated in the acquisition slot acquires in the normal
fashion. Once the physical layer acquisition occurs the remote must follow the key distribution
protocol before it is trusted. This is carried out in the clear.
Once the authentication is complete, the key update message must also be completed in the
clear. The symmetric keys are encrypted using the remote’s public key information obtained in
the exchange certificate. Once the symmetric key is exchanged, the remote enters the
network as a trusted entity and begins normal (completely encrypted) operation.
• Packets extracted from the Data Queue are always encrypted
• Packets exacted from the Clear Queue are always sent unencrypted
• The overwhelming majority of traffic will be extracted from the Data Queue
Traffic sent in the clear bypasses the Encryption Engine and proceeds to the FEC engine for
transmission.

TRANSEC
The Encryption Header consists of five 32 bit words with four fields. The fields are:
• Code. This field indicates if the frame is encrypted or not. The Code field is one byte in
length.
• Seq. This field is a sequence number that increments with each segment. The Seq field is
two bytes in length.
• Rsvd. This field is 1 byte and is reserved for future use.
• Initialization Vector (IV). IV is utilized by the encryption/decryption algorithm and
contains random data. The IV field is 16 bytes in length.


TRANSEC
X.509 certificates are an optional feature that provide an infrastructure to prevent various
types of attacks on a network, such as man-in-the-middle attacks, or someone simply setting
up a fake nodes and joining the network.
Customers can setup a hierarchical set of Certificate Authorities using iDirect Software
distributed with our NMS to create and manage a PKI system. In order to configure a host with
a set of certificates needed to join an authenticated network, it must be present at the
customer’s hub. Once it has been keyed, it can be shipped to location. Updates to the set of
trusted roots and revocation lists can be sent over the air.
1. Issue the Certificates created by iDirect CA Foundry to all the hosts on the network in this
order:
• NMS Servers (not required but best practice)
• Protocol Processor Blades
• All Hub line cards
• All remotes
2. Reconfigure the network as TRANSEC network.
3. Bring up unauthorized remotes into TRANSEC network.

1.5 iSCPC
iDirect SCPC operates in a point-to-point topology. Designed for applications that need to
provide IP connectivity between two geographic diverse locations. These point-to-point
applications typically aren’t able to take advantage of a star network topology that shares
bandwidth, or they need to provide a direct connection between two nodes with a single hop
over the satellite.
The iDirect system has features and controls that allow it to be easily configured to deliver
application QoS and other traffic?engineered solutions to the users. The iDirect system also
provides TCP and Web acceleration that supports line rate TCP throughputs in BOTH directions,
even to only one TCP session in the network.
The iDirect system is highly accessible and reliable, even with smaller antennas (when
compared to competitive solutions). The features that have enhanced the iDirect solution
include TCP/IP optimization over satellite (TCP and HTTP Acceleration, local DNS caching),
QoS and Prioritization of traffic, traffic engineering flexibility options, DHCP/NAT, network
configuration and management features, and centralized control features.

iSCPC
The SCPC point-to-point minimum rate should not be less than 64 ksps.
Information rates up to 18Mbps/11.5 Msps for iNFINITI modem are supported.
• Asymmetric/Symmetric data rates for TX & RX
• Hubless Architecture – VSAT to VSAT, or VSAT to Teleport
The Modems are designed to operate with both high quality phase-locked LNBs and DRO LNBs.
The stability of the LNB affects the performance of the satellite link in three ways:
• Phase Noise: lower data rate links can be impaired by the phase noise of the LNB
• Frequency Stability: The LO frequency of a DRO LNB will drift with time and temperature
changes which can cause modem sync loss events for lower data rates.
• Receive Acquisition Range: The frequency stability of the LNB will introduce an unknown
frequency offset into the satellite link and forces the receiver to sweep a frequency range
to acquire the carrier. If the frequency stability is wider than the occupied bandwidth, the
modem may erroneously lock onto another carrier.
1.5.1 iSCPC IP Addressing Scheme

Follow these guidelines when configuring the IP addressing information for each remote:
• Eth0 of remote A cannot be within the same network as the Eth0 of remote B.
• Sat0 of remote A must be within the same network as the Sat0 of remote B.
• Sat0 must not be within either of the networks used on either Eth0.
• RIP on Eth0 must be enabled in both remotes or static routes must be in place to direct
traffic outside of the remote’s LAN. If a PC is connected directly to the remote, you may
disable the RIP and no static route as well
For example:
Remote A:
Eth0 192.168.1.1/24
Sat0 10.0.0.1/24
Remote B:
Eth0 192.168.2.1/24 and
Sat0 10.0.0.2 /24
1.5.2 iSCPC Static Routes

To configure a Static Route with RIPv2 disabled:
1. Select the IP Configuration tab.
2. In the ETH0 Interface section, enter the Eth0 addressing for the remote.
3. In the SAT0 Interface section, enter the Sat0 addressing for the remote.
4. Open the Add Static Route or Edit Static Route dialog box for the remote by clicking the
Add or Edit button in the Static Routes section of the dialog box.

5. In the IP Address text box, enter the range of addresses that you want to forward to the
peer remote over the satellite.
6. Enter the Subnet Mask.
7. In Gateway, enter the peer remote’s Sat0 interface.
8. In Interface, select Sat0.
You do not need to configure a Cost for the route. Since there is only one static route,
Cost has no meaning in iSCPC.
9. Click OK.

DVB-S2
1.6 DVB-S2
iDX Release 1.0.x is the first iDirect release that supports DVB-S2 on the downstream carriers.
DVB-S2 is the second-generation modulation and coding standard for satellite broadband
transmissions. DVB-S2 uses the industry’s latest forward error coding technology, Low-Density
Parity Check Codes (LDPC), to achieve a significant increase in performance over the original
DVB standard. It supports multiple modulation schemes, including QPSK, 8PSK and 16APSK.
In release iDX 1.0.x, iDirect Evolution hardware supports DVB-S2 networks only. iDirect iNFINITI
line cards are required for the TDMA upstream carrier. Not all iDirect Hub Line Cards and
remote Satellite Routers are supported in iDX Release 1.0.x. Supported line card model types
include:
• Evolution XlC-10 (transmit DVB-S2 only)
• iNFINITI M1D1 (receive TDMA)
• iNFINITI (receive TDMA)
iDX Release 1.0.x supports only the Evolution X3 satellite router model.

1.6.1 DVB-S2 Key Concepts
A BBFRAME (Baseband Frame) is the basic unit of the DVB-S2 protocol. Two frame sizes are
supported: short and long. Each frame type is defined in the DVB-S2 standard in terms of the
number of coded bits: short frames contain 16200 coded bits; long frames contain 64800 coded
bits.
MODCOD refers to the combinations of Modulation Types and Error Coding schemes supported
by the DVB-S2 standard. The higher the modulation the greater the number of bits per symbol
(or bits per Hz). The modulation types specified by the standard are:
• QPSK (2 bits/Hz)
• 8PSK (3 bits/Hz)
• 16PSK (4 bits/Hz)
Coding refers to the error-correction coding schemes available. Low-Density Parity Coding
(LDPC) and Bose-Chaudhuri-Hocquenghem (BCH) codes are used in DVB-S2. Effective rates are
1/4 through 9/10. The 9/10 coding rates are not supported for short BBFRAMEs.

DVB-S2
DVB-S2 outbound carriers now utilize the following MODCOD combinations:

Downstream DVB-S2: QPSK
MODCOD DVB-S2: 8PSK
(DVB-S2)
DVB-S2: 16APSK
D-TDMA inbound carriers support the following MODCODs:

Upstream TDMA BPSK/SS .431 .533 .66
MODCODS BPSK .431 .533 .66 .793
TPC
QPSK .533 .66 .793
8PSK .66 (and .793 Evolution only)

As we mentioned earlier, MODCOD stands for modulation and coding. Here are the 28
modulation/coding schemes which can be configured within our DVB-S2 networks.
Note that the 9/10 coding rates are not supporting for SHORT frames.
Note: CCM with long frames is not currently supported in iDX 1.0.x.

DVB-S2
Each modulation can transmit a certain amount of bits per symbol. The lower the MODCOD, the
less bits/hz efficiency. The higher the MODCOD, the more bits/hz efficiency.

DVB-S2 defines three methods of applying coding to a data stream:

• CCM (Constant Coding and Modulation) specifies that every BBFRAME is transmitted at the
same MODCOD. Effectively, the iDirect legacy system is a CCM system.
Note: In iDX 1.0, CCM is mimicked using ACM set to a single MODCOD. True CCM will be
supported in a later release.
• ACM (Adaptive Coding and Modulation) specifies that every BBFRAME can be transmitted on
a different MODCOD. Remotes receiving an ACM carrier cannot anticipate the MODCOD of
the next BBFRAME. A DVB-S2 demodulator must be designed to handle dynamic MODCOD
variation.
• VCM (Variable Coding and Modulation) specifies that MODCODs are assigned according to
service type. As in ACM mode, the resulting Downstream contains BBFRAMEs transmitted at
different MODCODs. (iDirect does not support VCM on the Downstream.)

DVB-S2
The above slide contains examples of what BBFRAMES being transmitted may look like
depending on what modulation and coding is being used.


DVB-S2
A DVB-S2 downstream can be configured as CCM (future) or ACM. If you configure the
downstream as ACM, it is not constrained to operate at a fixed modulation and coding. Instead,
the modulation and coding of the downstream varies within a configurable range of MODCODs.
Symbol rate remains fixed — Variation in throughput is realized through DVB-S2 support, and
the variation of MODCODs that ACM performance allows for.
As with legacy iDirect networks, multiple Protocol Processors may be required to support high
traffic to multiple remotes.
Throughput of DVB-S2 system much higher — Maximum possible throughput (calculated at 45
Msps and highest MODCOD 16 APSK 8/9) yields a throughput rate of approximately 155 Mbps.
No changes have been made to PP to handle these higher throughput rates. Similar to existing
networks, multiple PPs might be required to support high traffic to multiple remotes.
Hardware and software features in the XLC-10 will allow it to support the maximum possible
throughput.
ACM mode means that remotes operating in better signal conditions can receive data on a
higher MODCOD. DVB-S2 remotes (the X3) are capable of realizing greater throughput for

allocated Downstream bandwidth by means of the improved modulation and schemes

available. However, the raw throughput to the user-side LAN has not changed.

DVB-S2
iDirect DVB-S2 networks support ACM on the downstream carrier with all modulations up to
16APSK. An iDirect DVB-S2 network uses short DVB-S2 BBFRAMES for ACM. Future releases will
support long DVB-S2 BBFRAMES for CCM. iDirect does not support VCM on the downstream
carrier.
The iDirect TDMA upstream carrier does not use DVB-S2. It is unchanged from previous iDirect
releases.

1.6.2 DVB-S2 in iDirect
iDX Release 1.0 supports the following DVB-S2 hardware:

• Evolution XLC-10 Tx line card
• Evolution X3 remote satellite routers
Note: In iDX 1.0.x, iBuilder allows you to select e8350 remotes; however, these remotes
are not supported in iDX 1.0.x.
The Evolution XLC-10 line card is a Tx-only line card. It can transmit a DVB-S2 downstream
carrier. An Evolution X3 remote satellite router can receive a DVB-S2 downstream carrier while
transmitting on the TDMA upstream carrier.

DVB-S2
ACM mode allows remotes operating in better signal conditions to receive data on higher
MODCODs. This is accomplished by varying the MODCODs of data targeted to specific remotes
to match their current receive capabilities.
Not all data is sent to a remote at its best MODCOD. Important system information (such as
timeplan messages), as well as broadcast traffic, is transmitted at the minimum MODCOD
configured for the outbound carrier. This allows all remotes in the network, even those
operating at the worst MODCOD, to reliably receive this information.
The Protocol Processor determines the maximum MODCOD for all data sent to the DVB-S2 line
card for transmission over the outbound carrier. However, the line card does not necessarily
respect these MODCOD assignments. In the interest of downstream efficiency, some data
scheduled for a high MODCOD may be transmitted at a lower one as an alternative to inserting
padding bytes into a BBFRAME. When assembling a BBFRAME for transmission, the line card
first packs all available data for the chosen MODCOD into the frame. If there is space left in the
BBFRAME, and no data left for transmission at that MODCOD, the line card attempts to pack
the remainder of the frame with data for higher MODCODs. This takes advantage of the fact
that a remote can demodulate any MODCOD in the range between the carrier’s minimum
MODCOD and the remote’s current maximum MODCOD.

The maximum MODCOD of a remote is based on the latest Signal-to-Noise Ratio (SNR)
reported by the remote to the Protocol Processor. Here we show the SNR thresholds per
MODCOD for the Evolution X3 remote. These values are determined during hardware
qualification. The graph shows how spectral efficiency increases as the MODCOD changes.

DVB-S2
iDirect uses DVB-S2 “Generic Streams” for encapsulation of downstream data between the
DVB-S2 line cards and remotes. Although the DVB-S2 standard includes the provision for
generic streams, it is silent on how to encapsulate data in this mode. iDirect uses the
proprietary LEGS (Lightweight Encapsulation for Generic Streams) protocol for this purpose.
LEGS maximizes the efficiency of data packing into BBFRAMES on the downstream. For
example, if a timeplan only takes up 80% of a BBFRAME, the LEGS protocol allows the line card
to include a portion of another packet that is ready for transmission in the same frame. This
results in maximum use of the downstream bandwidth.

The hub adjusts the MODCODs of the transmissions to the remotes by means of the feedback
loop shown here. Each remote continually measures its downstream SNR and reports the
current value to the Protocol Processor. When the Protocol Processor assigns data to an
individual remote, it uses the last reported SNR value to determine the highest MODCOD on
which that remote can receive data without exceeding a specified BER. The Protocol Processor
includes this information when sending outbound data to the line card. The line card then
adjusts the MODCOD of the BBFRAMES to the targeted remotes accordingly.
Note: The line card may adjust the MODCOD of the BBFRAMEs downward for reasons of
downstream packing efficiency.
There is constant throttling feedback coming from the Tx card to the PP Blade to prevent
overrun. This is called the back-off mechanism.

DVB-S2
In the legacy system, even with fixed modulation/coding on downstream, throughput can vary
up to 1% due to bit-stuffing on downstream. QoS is already designed to accept input telling it
that the downstream maximum bps is varying. This information is gathered from a feedback
mechanism from the linecard: the linecard reports (on a 100 ms basis) its queue fullness to the
PP. If the queue exceeds a certain level, the PP will backoff the data that it assigns to the
linecard.
In DVB-S2 mode, this mechanism is exaggerated. Throughput rate on the downstream can vary
now between the (theoretical limits) of {every remote on the minimum MODCOD} to {every
remote on the maximum MODCOD}.
For example, with a MODCOD {min; max} = {QPSK3/5; 8PSK 8/9}, if all packets transmitted at
the best case of 8PSK8/9, it will perform 123% better than if all packets were being
transmitted at QPSK3/5.
In practice, the downstream throughput will lie somewhere in between, since it is unlikely that
all remotes in the network will experience the same conditions at the same time.

iDirect QoS for DVB-S2 downstream carriers is basically identical to QoS for legacy downstream
carriers. However, with DVBS2 in ACM Mode, the same amount of user data (in bits per second)
occupies more or less downstream bandwidth, depending on the MODCOD at which it is
transmitted. This is true because user data transmitted at a higher MODCOD requires less
bandwidth than it does at a lower MODCOD.
When configuring QoS in iBuilder, you can define a Maximum Information Rate (MIR) and/or a
Committed Information Rate (CIR) at various levels of the QoS tree. As noted above, the
occupied bandwidth for these information rates varies per MODCOD. If, when allocating
downstream bandwidth for a remote, the system always attempted to meet these rates
regardless of MODCOD, then a remote in a deep rain fade may be granted a disproportionate
share of bandwidth at the expense of other remotes in the network. On the other hand, if CIR
and MIR settings were only honored at the best MODCOD of the carrier, then only remotes
operating under ideal conditions would ever be granted their configured rates.
To address these issues, iDX 1.0.x introduces the concept of “Enhanced Information Rate”
(EIR). EIR only applies to networks that use DVB-S2 with Adaptive Coding and Modulation
(ACM). EIR can be enabled for a physical remote or for individual applications executing on a

DVB-S2
physical remote (known as a Virtual Remotes.) To enable EIR in iBuilder, the Network Operator
selects an EIR Minimum MODCOD for the remote or Virtual Remote.
EIR is only enabled in the range of MODCODs from the best MODCOD defined for the DVB-S2
carrier down to the EIR Minimum MODCOD selected for the remote. Within this range, the
system always attempts to allocate requested bandwidth in accordance with the MIR and CIR
settings, regardless of the current MODCOD at which the remote is operating. Since higher
MODCODs contain more information bits per second, as the remote’s MODCOD increases, so
does the capacity of the outbound channel to carry additional information.
As signal conditions worsen, and the MODCOD assigned to the remote drops, the system
attempts to maintain CIR and MIR only down to the configured EIR Minimum MODCOD. If the
remote drops below this EIR Minimum MODCOD, it is allocated bandwidth based on the carrier’s
best MODCOD with the rate scaled to the MODCOD actually assigned to the remote. The net
result is that the remote receives the CIR as long as the current MODCOD of the remote does
not fall below the EIR Minimum MODCOD. Below the minimum MODCOD, the information rate
achieved by the remote falls below the configured settings.
This slide illustrates the relationship between total bandwidth and information rate as the
MODCOD changes with EIR enabled. Here, 16APSK 8/9 is the best MODCOD; QPSK 3/5 is the
Minimum EIR MODCOD configured for the remote. As the MODCOD drops, the bandwidth
required to maintain the configured CIR increases until the EIR Minimum MODCOD is reached.
As soon as the MODCOD of the remote falls below the EIR Minimum MODCOD, the total
allocated bandwidth immediately drops to the level required to meet the CIR at the networks
best MODCOD, causing the steep reduction in the information rate at the lower MODCOD.
When the system allocates bandwidth, it first considers CIR demand. Once all CIR demand is
satisfied, bandwidth is allocated for non-CIR demand. This algorithm affects EIR as follows:
• The system maintains the configured CIR down to the EIR Minimum MODCOD only if enough
bandwidth is available during CIR allocation to satisfy all CIR demand. If bandwidth is not
available to satisfy all CIR demand, allocation is scaled to the network’s best MODCOD.
• If there is enough bandwidth to satisfy CIR demand, MIR is satisfied down to the EIR
Minimum MODCOD as long as there is enough bandwidth to satisfy all demand in excess of
CIR demand. Otherwise, allocation in excess of CIR demand is scaled to the network’s best
MODCOD.
• Below the EIR Minimum MODCOD, CIR and MIR are scaled to the network’s best MODCOD.
• If EIR is not enabled, CIR and MIR are scaled to the network’s best MODCOD.
Note: In remote-based QoS mode, EIR is not in effect when capping a physical remote’s
downstream bandwidth at the Maximum Information Rate (MIR) configured on the
iBuilder Remote QoS tab. Therefore, if you configure MIR for your physical
remote, and the remote is operating at a MODCOD below the best MODCOD of the
carrier, the remote will not be granted its full MIR.

This table shows the scaling factors that can be used to calculate the information rate at
different MODCODs when the allocated bandwidth is held constant at the network’s best
MODCOD.
The following formula can be used to determine the information rate at which data is sent
when that data is scaled to the network’s best MODCOD:
IRa = IRn x Sb / Sa
where:
• IRa is the actual information rate at which the data is sent
• IRn is the nominal information rate (for example, the configured CIR)
• Sb is the scaling factor for the network’s best MODCOD
• Sa is the scaling factor for the MODCOD at which the data is sent

DVB-S2
For example, assume that a remote is configured with a CIR of 1024 kbps in a network with a
best MODCOD of 16ASPK 8/9. If EIR is not in effect, and data is being sent to the remote at
MODCOD QPSK 8/9, then the resulting information rate is:
IRa = IRn x Sb / Sa
IRa = 1024 kbps x 1.2382 / 2.4605 = 515 kbps

XLC-10 has an additional Ethernet port:1000bT/100bT.

Tx FPGA has an embedded core on which runs software dedicated to processing and formatting
downstream data. The application running on FPGA is called “Raven.”
Statistics/configuration is still handled by the Falcon application (running on the existing
processor).
Raven:
• receives and processes tunnel packets from the Protocol Processor (from one or more
blades)
• parses tunnel packets for constituent acm_packets
• untransmitted acm_packets are stored according to their maximum_modcod
• next BBFRAME transmit opportunity, a decision is made as to what MODCOD on which to
next transmit data
• handles LEGS encapsulation

DVB-S2
Similar to XLC-10, software running on the NIOSII processor in the FPGA processes data prior to
its being passed up to Falcon.
“Griffin” is the new application running on the X3 FPGA. Griffin:
• handles NCR processing and programming of the NCR clock
• filters out data not destined to the remote
• flags errors if critical system information (timeplans, timeplan start messages) is found to
be missing
• handles LEGS de-encapsulation. Falcon has no knowledge of this.
• processes the entire downstream, and only passes on to Falcon what is destined for it
Falcon continues to process timeplans, program bursts on return link (inroute). Falcon
continues to be responsible for reporting to NMS.
However, Falcon is now responsible for SNR measurements and reporting to Protocol Processor.
If the difference between the previous and current SNR is larger than a programmable
threshold (see page 70) the remote will deem itself to be in a fast fade condition, and report
more frequently back to the PP. The intent here is to ensure that there is not an extended

period where the Protocol Processor is assigning data to the remote on a MODCOD higher than
it is capable of receiving.

DVB-S2
1.6.3 Configuring and Monitoring DVB-S2
The iBuilder GUI allows you to configure a various parameters that affect the operation of your
DVB-S2 networks. For details on configuring DVB-S2, see the iBuilder User Guide.
Downstream Carrier Definition: When you add an ACM DVB-S2 downstream carrier, you must
specify a range of MODCODs over which the carrier will operate. Error correction for the
carrier is fixed to LDPC and BCH. In addition, you cannot select an information rate or
transmission rate for a DVB-S2 carrier as an alternative to the symbol rate, since these rates
will vary dynamically with changing MODCODs.
Multicast MODCOD: In iDX Release 1.0.1, DVB-S2 downstream multicast data is always
transmitted at the lowest MODCOD configured for an ACM carrier. Beginning with iDX Release
1.0.2, you can use iBuilder to configure a different MODCOD for your multicast user traffic by
entering a network-level custom key. Once the custom key is defined, all outbound multicast
user traffic is sent at the new MODCOD.

To configure the multicast MODCOD for the outbound carrier in your ACM network, create the
following custom key at the Network level of the iBuilder tree:
[MULTICAST]
modcod_index = Multicast MODCOD
where Multicast MODCOD is the index of the MODCOD to be used for multicast data. Once you
have created the custom key, apply the changes to your ACM network. Table 3 shows the
MODCOD index numbers used for configuring the multicast MODCOD.
Note: The index numbers for this custom key are one less than the standard DVB-S2
MODCOD numbers. Be sure to use the index numbers shown in Table 2 when
changing the multicast MODCOD.
Table 3. MODCOD Indexes for Multicast Data
Index Modulation Code

0 QPSK 1/4
1 1/3
2 2/5
3 1/2
4 3/5
5 2/3
6 3/4
7 4/5
8 5/6
9 8/9
11 8PSK 3/5
12 2/3
13 3/4
14 5/6
15 8/9
17 16APSK 2/3
18 3/4
19 4/5
20 5/6
21 8/9

DVB-S2
DVB-S2 Line Card Definition: When you add a DVB-S2 line card, you must configure a second
IP port (called the GIG0 port) in addition to the management IP port. All data to be transmitted
on the DVB-S2 downstream carrier is sent to this port.

DVB-S2 Network-Level Parameters: iBuilder allows you to configure the network-level

parameters that control how a DVB-S2 network behaves when ACM is enabled for your
downstream carrier. These parameters affect the behavior of the system during remote fade
conditions.

DVB-S2
iMonitor allows you to monitor the several characteristics of your DVB-S2 outbound carriers.
ACM Gain represents the increase in performance achieved on a DVB-S2 outbound carrier when
the MODCOD used to transmit data is higher than the minimum MODCOD configured for the
carrier. ACM Gain can be monitored at the Network, Inroute Group, Remote and Tx Line card
levels of the iMonitor tree.

You can examine how the downstream data is distributed across the range of MODCODs
configured for an ACM carrier. MODCOD distribution can be monitored at the Network, Remote
and Tx Line Card levels of the iMonitor tree.

DVB-S2
In an ACM network, each DVB-S2 remote periodically reports its current Signal-to-Noise Ratio
(SNR) to the Protocol Processor. Based on the remote’s last-reported SNR, the Protocol
Processor determines the maximum MODCOD at which the remote can receive data. Remote
SNR can be monitored at the Network, Inroute Group, and Remote levels of the iMonitor tree.

A DVB-S2 line card keeps detailed statistics for traffic that is sent from the Protocol Processor
to the line card and then transmitted by the line card on the DVB-S2 outbound carrier. DVB-S2
hub line card debug statistics can be monitored at the Tx Line Card level of the iMonitor tree.
For details, see the iMonitor User Guide.

Module 2: Introduction to
System Installation
Goal: Through lecture, presentation and visual display each learner will fully understand how
to properly rack mount the iDirect hub equipment. The learner will also walk through a Hub
Line Card installation exercise.
Objectives:
1. The learner will be able to describe the overall chassis configuration associated with an
iDirect network.
2. The learner will be to identify the specifications for an iDirect chassis, RCM, EDAS Board.
a. The learner will be able to identify the types of chassis.
3. The learner will be able to properly configure a chassis.
4. The learner will be able to explain chassis design considerations as they apply to their
specific network as well as a standard iDirect network.

Introduction to System Installation
2.1 iDirect Hub Configuration
Although the slide above is a representation of a “typical” hub configuration, there truly is
nothing typical about the configuration or the configuration process. As you can see, the NMS
servers are only physically connected to the Upstream switch via the eth0 port. Some
individuals like to refer to the NMS server as the “brains” of the iDirect configuration.
The Protocol Processors are connected to both the Upstream switch and the tunnel switch. PP
eth0 is connected to the Upstream switch and eth1 is connected to the tunnel switch. For this
reason, the Protocol Processor is sometimes referred to as the “heart” of the iDirect
configuration.
The Upstream router is physically connected to both the Upstream and tunnel switches and the
chassis EDAS card is connected to the Upstream switch. Each individual Hub Line Card is
connected to the tunnel switch as well.
What do you think would happen to your network if you lost the NMS server? The Protocol
Processor? Can you explain the resulting effect it would have on your particular network?

2.1.1 20-Slot Chassis
The rear of the chassis has 5 IF ports which physically support 4 slots per group. We will explain
this further and in more detail later in the training manual. The chassis reference clock
modules (RCMs) are also found in the rear of the chassis.
The front view image of the chassis shows the chassis door closed. This chassis door is shipped
with all iDirect hubs and should remain closed during normal operations. This is a special EMI
door which will assist in shielding EMI signals to and from the Hub Line Cards.
Note: Make sure you check the packing materials thoroughly. Many customers have
accidently discarded the chassis door only to discover while attending this course
that the chassis was shipped to them with the chassis front door.
iDirect also supports the 4-slot and industrial 4-slot chassis.

2.1.2 Reference Clock Module
The Reference Clock Modules (RCMs) provide timing and synchronization of your iDirect
network. This is very important. The RCM modules can be configured for internal or an
external station clock connection. The RCM modules are fully redundant and hot swappable.
One RCM module is active at any given time while the other is in standby mode.
The RCMs are installed in dedicated slots, RCM A and RCM B, on the rear panel of the chassis.

2.1.3 Chassis Accessories
This image above shows some of the items which are normally shipped with the 5IF chassis.
Notice we only ship two power supplies. Our chassis supports two redundant power supplies
and three fans as well as the EMI door.
Hub accessories include:
• RCMs
• DB9F-DB9F, Null-Modem Cable
• Spare Coax/LAN Jumpers Set
• Static Wrist Strap
• 1 Seven-foot CAT5 Cable
• Rack Mounting Hardware

2.1.4 EDAS Board
Also located in the rear of the chassis behind a metal faceplate is the EDAS card. Consider the
EDAS card the NIC (Network Interface Card) of the 5IF chassis. The EDAS card is physically
connected to the Upstream switch and holds the IP, Subnet mask, and gateway configurations.
You will have to use the EDAS Syscheck 3.0 software application to configure these IP
parameters.
The EDAS system is:
• Third-party vendor supplied hardware and software
• Configured using vendor provided software
• EDAS Syscheck 3.0 is contained in the iDS NMS Clients zipped file
• 10 Mbps, half-duplex, fixed mode only (no auto-negotiation)
• Requires null-modem, DB9 female to DB9 female cable (found in Chassis Accessories Kit) for
typical PC serial/COM port connection to chassis config port

The actual EDAS board shown above can be seen because the metal faceplate has been
removed. Above the actual EDAS board are the physical ethernet connection which is
connected to the Upstream switch, and the config port which you use to configure the IP
address information using the SYSCHECK 3.0 software, which is shown to the left.
To configure the EDAS board:
1. Connect null modem, DB9F to DB9F cable (provided) between PC/laptop COM port and
config. port on rear of chassis (1IF or 5IF).
2. Open EDAS configuration software (EDAS SYSCHECK 3.0 – Configuration Tab).
3. Enter assigned IP, Subnet Mask, and Default Gateway (the Default Gateway is ALWAYS the
Upstream interface on the Upstream router for the chassis).
4. Power cycle the board upon completion to reinitialize EDAS with new IP configuration
detail.
5. Switch to Program Tab.
6. Select correct COM port.

7. Click Attach to EDAS button. The EDAS picture and Current Configuration detail appears.
8. Select Write IP Address, Write Subnet Mask and Write Gateway Address to update the
changes.

The slide above shows the EDAS Syscheck 3.0 GUI which you use to configure and write the IP
address, subnet mask, and gateway address information to the EDAS board. You know you have
successfully connected and are communicating with the EDAS board when the picture of the
EDAS board shows to the right.
Do not configure the ethernet address of the EDAS! This is the board’s MAC hardware address
and this should not be changed.

2.1.5 Hub Chassis Design Considerations
There are many important considerations to be aware of when operating the iDirect 5IF 20 Slot
chassis!
All Hub Line Cards and remotes alike operate strictly on L-band frequency and the iDirect
equipment relies on external equipment to convert these signals to the desired Ku, Ka, C, and
X bands. Careful considerations should be exercised when you are installing the Hub Line Cards
due to future expansion of your networks and the possibility of needing additional Hub Line
Cards installed for your network.
The hub line card does not have the capability of compensating its Tx power for rain fade.
Instead, it relies on the UPC provided by the teleport. Chassis power requirements are also
listed below for a fully populated chassis which includes Hub Line Cards, EDAS board, RCM
modules, fans, and power supplies.
Hub Chassis design considerations are summarized here:
• Designed for an enterprise class teleport RFT Chain
– Can be utilized with VSAT Hub if external DC/10 MHz reference implemented

– Chassis and all HLCs cannot provide DC power or 10 MHz reference for BUC/LNB
• L-Band input/output only
– External L-Band to 70 or 140 Mhz interfaces available, may be required per teleport
• Hub Line Card (HLC) carrier loopback requirements
– HLC does not have to “see” itself for commissioning or monitoring star networks
– M1D1 does use loopback C/N measurements to maintain Mesh network topologies (not
supported in iDX 1.0.x)
– Precludes the use of regional or spot/focused beam transponders
• Initial HLC layout should consider future expansion of any network
– Allocate sufficient slots (allows for future reconfiguration if necessary)
– HLC auto-failover requires spare to be in same network/timing group
• Teleport must allow for signal processing losses through chassis
– 1IF (legacy option) losses are 19 dB, both Tx and Rx path (20:1 splitter/combiner)
– 5IF losses are better, 7 dB for both Tx and Rx path (4:1 splitter/combiner)
• Utilizes teleport external Uplink Power Control (UPC) to compensate for hub-related rain
fade (no iDS UPC available for hub carrier)
– Chassis requires ~600 to 650 watts of power (fully populated chassis)
– 20 watts per HLC (20 x 20 = 400 watts)
– 200–250 watts for power supplies, fan modules, EDAS, etc.

2.1.6 Chassis Slot Groups
The default slot layout of the 5IF Hub Line Cards is shown above. You will notice that for each
Group you have 4 Hub Line Cards separated by a jumper. A total of 20 Hub Line Cards can be
installed on the chassis. Each group of 4 cards will physically transmit and receive on one IF
pair in the rear of the chassis.
A summary of chassis default slot groups is below:
• Can support up to 5 Multi-Upstream networks per chassis easily, without additional
configuration (5IF)
• Each group uses common (network, frame synchronization) timing on the backplane
• Groups can be combined to increase multi-Upstream capacity by enabling the software
configurable jumper
• A single (solo) Downstream-Upstream network can take any slot since it does not interact
with backplane timing
• Rear panel TX/RX port pairings are fixed as shown, and cannot be reconfigured regardless
of final network configuration

Here is an example of multiple networks installed onto the same 5IF chassis.
Notice network number 1 has a total of 11 Hub Line Cards all in one network. These 11 Hub
Line Cards can be combined onto the same timing group by removing the jumpers via software
configuration in iBuilder. This particular network has one transmit and 11 receive carriers with
one standby Hub Line Card installed. The solo card found in slot 12 is its own network and it is
not receiving timing information from any other network in the chassis.
Network 3 (represented in red) has one transmit and 3 receive carriers with a standby Hub Line
Card installed. Network 4 has one transmit and 3 receive carriers installed and there is another
solo line card installed in slot 20. Slot 20 is its own network and does not receive timing from
any of the other slot groups.
The standby line cards are only standby cards for the networks where they are currently
installed.
To summarize:
• Slot Groups 1, 2, and 3 are jumpered on the backplane to share timing (requires software
configuration only)

• Network 1 has one Downstream and 11 Upstream carriers (or some spares, for example, 10
Upstream and one Standby HLC)
• Network 2 has one Downstream and 1 Upstream (does not use timing on the backplane –
Solo HLC)
• Network 3 has one Downstream and 3 Upstream (one Standby HLC)
• Network 4 has one Downstream and 3 Upstream (no spares configured; no auto redundancy
on this network)
• Network 5 has one Downstream and 1 Upstream (does not use timing on the backplane –
also solo HLC)
• Each network can have its own characteristics (Frame length, oversubscription, etc.)
• Standby Cards MUST adhere to established criteria for successful auto fail-over capability

Benefits of having a distributed NMS environment include more server processing power and
memory utilization as well as hard drive space. Busy processes can now resides on different
NMS servers as to not hinder other processes associated with a single NMS.
A single NMS server can supports upwards of 800 remotes depending on the traffic being
generated. Once you reach these levels of supported remotes, you should consider a
Distributed NMS architecture.

This slide explains how database backup and redundancy works in a Distributed NMS
environment. You don’t necessarily need a backup server for each NMS server in a Distributed
NMS. However, you do need to run dbRestore to restore the database content before swapping
out servers, if one of the servers fail.
• Same scripts remain compatible with new NMS
• Choose a one-for one or one-for-n database redundancy
• If one-for-n, ensure backups are handled properly in the script file

Don’t forget to bring a loopback kit just in case the customer’s space segment is unavailable!


Module 3: Hub
Installation Paperwork,
Processes and
Procedures
Goal: Through lecture, presentation and visual display each learner will fully understand which
items are required before going to the site, what to expect when you first arrive to the install
location, and how to verify the preinstallation checklist.
Objectives:
1. Each learner will be able to thoroughly explain all paperwork, processes and procedures
required pre-installation of the iDirect hub.
required during the installation of the iDirect hub.
required post-installation of the iDirect hub.
4. Each learner will be able to complete all paperwork required efficiently for return to the
Program Manager.

Hub Installation Paperwork, Processes and Procedures
Installing a hub for anyone is a very important and detailed task. Whether you are an iDirect
engineer, or one of our PSPs, it is important to keep in mind when installing a hub: “It’s not
over with until the hub is functioning and all the paperwork is completed and in the hands of
the iDirect Program Manager (PM).”
Although it is not listed on the slide, a Work Order must be generated by iDirect before any
iDirect hub can be installed. You, the installer, will probably never see the Work Order, but just
remember that there are many things that go into creating and generating one. Things we
want you to remember are:
• It is generated by iDirect
• It is sent to our PSPs and CHiPs from iDirect
• If the installation is not perform by an authorized PSP or CHiP/iDirect then the equipment
is not under warranty.
Things to remember to bring:
• Hub Readiness Checklist— The Hub Readiness Checklist lists everything that should be
onsite before you start the installation procedure.

• iDirect Network Planning Tool (iNPT) — The Network Planning Tool (iNPT) is intended to
provide the network designer a simplified and easy process of planning a network based on
voice and data application requirements. The tool provides a very simple way to use
sharing or overbooking ratios for both data application requirements. iNPT is designed to
calculate bandwidth requirements in both the upstream and downstream directions based
primarily on IP data rates requirements and assumptions.
As most customers’ requirements are based on IP throughputs and bandwidth
requirements, the Planning Tool uses IP data rates only for bandwidth requirements
calculations and outputs the amount of satellite bandwidth needed t o support the
requirements.
Proper network planning will involve an iterative process of determining the data rates
for the upstream and downstream carriers. The iterative process can be attributed to link
budget calculation and fine-tuning of carriers based on data requirements and
calculations.
You may view more information regarding the Network Planning Tool on the TAC web page
(http://tac.idirect.net). To find out more about the Link budget calculation see the Link
Budget Analysis Guide located on the TAC web page. See Figure 1 for an example of a Link
Budget Analysis.
• Frequency Assignment and IP Address Scheme (Plan) — See Figure 2 for an example of an
IP Plan.
• Packing List — This is the Inventory Inspection that you should conduct. For example,
based on the results of your Work Order, I should have two chassis, six PPs, 2 NMS, 20
Linecards, etc. Make sure you have everything that you require to perform a proper
installation according to the customer’s needs. See Figure 3 for an example of an iDirect
packing slip.
• Block Diagram — This is for the engineer who is needs specific directions that depend on
customer requirements. Figure 4 shows an example of a network block diagram.

SES NEW SKIES LINK BUDGET ANALYSIS
Prepared by: anna Date: 23-Jun-09
Customer Name: <insert prospect name>

Project Name: <insert project name>
Scenario name: Intersat Africa idirect Tanzania spot C NSS703 23Jun2009
© 2007 SES NEW SKIES Spacecraft: 703

Common Link Budget Tool - v 3.2.3 Orbital location: 57 ° E longitude
All Rights Reserved
Transponder information Resource usage summary
Transponder ID: 136/136 Required bandwidth: 0.50 MHz
Start frequency (U/D): 6302.0/4077.0 MHz Equivalent EIRP: 16.3 dBW
Bandwidth: 36.0 MHz EIRP margin: 1.0 dB
Saturated EIRP: 38.4 dBW Total
Saturated flux density: -85.4 dBW/m² Number of carriers: 2
G/T: 2.7 dB/K EIRP: 15.4 dBW
OBO used for PEB: 3.5 dB PEB of carriers: 0.40 MHz
Operational mode: Multi carrier Allocated bandwidth: 0.462 MHz
Inclined orbit: 0.0 degrees Bandwidth margin: 0.038 MHz
Calculation type: Clear Sky + Worse of Up & Downlink Fades ALC mode, OBO: No, 0.0 dB
Analysis target: Transponder Resource
Earth stations
Tx earth station ID: Tanzania HUB Tanzania remote
Antenna diameter: m 2.40 2.40
Latitude: deg. N -8.00 -8.00
Longitude: deg. E 37.25 37.25
Antenna elevation angle: degrees 65.1 65.1
Uplink aspect correction: dB 1.7 1.7
Receive earth station ID: Tanzania remote Tanzania HUB
Antenna diameter: m 2.40 2.40
Latitude: deg. N -8.00 -8.00
Longitude: deg. E 37.25 37.25
Antenna elevation angle: degrees 65.1 65.1
Rx E/S G/T clear sky: dB/K 17.9 17.9
Downlink aspect correction: dB 0.6 0.6
CARRIER
C:Tanzania C:Tanzania
Carrier ID: HUB>Tanzania remote remote>Tanzania HUB
Part of topology: Duplex Duplex
Information rate: Mbps 0.256 0.256
Overhead rate: kbps 0.0 0.0
FEC inner coding: 0.793 0.660
RS outer coding (if used): n/a n/a
Coding type: Turbo Coding Turbo Coding
Modulation scheme: QPSK QPSK
Allocated bandwidth: MHz 0.210 0.252
Noise bandwidth: MHz 0.161 0.194
Desired threshold Eb/No: dB 4.6 5.4
BANDWIDTH REQUIREMENTS
Calculated PEB, one carrier: MHz 0.182 0.219
Required BW, one carrier: MHz 0.21 0.25
Number of carriers (multiplier): 1 1
Total BW per carrier type: MHz 0.30 0.30
LINK BUDGET Clear sky Clear sky

E/S transmit EIRP/carrier: dBW 51.1 51.9
Uplink rain margin, if used: dB 1.4 1.4
Target uplink availability: % 99.98 99.98
Availability calculated for: Annual Annual
C/N uplink (thermal): dB 28.7 28.7
C/I uplink (interference prior to ASI): dB 30.0 30.0
Carrier input back-off: dB 27.7 26.9
Carrier downlink EIRP at BC: dBW 11.9 12.7
Downlink rain margin, if used: dB 0.5 0.5
Target downlink availability: % 100.00 100.00
C/N downlink (thermal): dB 9.6 9.6
C/I downlink (interference prior to ASI)dB 18.7 18.7
C/(N+I) total prior ASI: dB 9.0 9.0
C/I adjacent spacecraft interference: dB 14.1 14.1
C/(N+I) total: dB 7.9 7.9
Eb/No total, clear sky: dB 5.9 6.7
MARGINS
Implementation margin: dB 0.0 0.0
Required threshold C/(N+I): dB 6.6 6.6
Threshold margin: dB 1.3 1.3

Margins shown for: Clear Sky Clear Sky
Link availability: % 99.978 99.978
Uplink power density

On-axis power spectral density: dBW/Hz -43.1 -43.1
Margin to ITU limit (3 deg.): dB 10.12 10.12
Downlink power density
BC power spectral density: dBW/Hz -40.15 -40.14
Margin to ITU limit: dB 14.31 14.31
Earth Station HPA: Tanzania HUB Tanzania remote

Total number of carriers: 1 1
Total EIRP required: dBW 51.1 51.9
Peak antenna gain: dBi 42.2 42.2
UPC: dB n/a n/a
Post HPA losses and margin: dB 0.0 0.0
HPA type: SSPA SSPA
Required backoff: dB 1.0 0.5
Required HPA size: Watts 9.9 10.6
Recommended HPA size: Watts 10.0 20.0
136_136 Intersat Africa idirect Tanzania spot C NSS703 23Jun2009 Page 1 of 1
Figure 1. Example of Link Budget Analysis Results

IP Plan - iDirect Sat

3/12/2009
Hub IP Plan - iDirect-Sat
Upstream LAN 10.154.117.0/28 255.255.255.240
Usable IP Addresses 10.154.117.1 - 10.154.117.14
Device IP Address U/S Switch Port #

Upstream Router Interface 10.154.117.1 1
(Hub EDAS Module) 10.154.117.2 2
Primary NMS Server (eth0) 10.154.117.3 3
Secondary NMS Server (eth0) 10.154.117.4 4
PP Server Blade 1 (eth0) 10.154.117.5 5
Not used 10.154.117.7 - 10.154.117.12
Co-Located Utility PC (if used) 10.154.117.13 13
Cisco Switch Management IP 10.154.117.14 N/A
Tunnel LAN 10.154.117.16/28 255.255.255.240

Usable IP Addresses 10.154.117.17 - 10.154.117.30
Tunnel Switch GIG0 Address

Device IP Address Port # fuw XLC-10
Tunnel Router Interface 10.154.117.17 1
Hub Line Card #1 10.154.117.20 11 10.154.117.25

Hub Line Card #2 10.154.117.21 12 10.154.117.26
Hub Line Card #3 10.154.117.22 13 10.154.117.27
Hub Line Card #4 10.154.117.23 14 10.154.117.28
Hub Line Card #5 10.154.117.24 15 10.154.117.29
Cisco Switch Management 10.154.117.30 N/A
Figure 2. Example of an IP Plan

IDIRECT OPERATIONS Packing Slip Report Date: 29-MAY-2009 14:59

Draft 11495 Page: 1 of 5
Ship from Ship to Bill to
IDIRECT OPERATIONS AA SAT PROFESSIONAL AA SAT PROFESSIONAL
44991 FALCON PLACE PIRITA TEE 20 PIRITA TEE 20
BAY 180 TALLINN 10127, Estonia TALLINN 10127, Estonia
STERLING, VA 20166, United States
Phone: 1 (703) 648-8000
Attn Attn
Tax Name 54-1736959 Tax Number
Delivery Name 605090 Pick up Date 21-MAY-09
FOB Shipping Point Ship Method BEST WAY
Freight Terms Prepay & Add without Insurance conversion Way Bill
Reason of Transport Service Contract
Order
Order Type PO Number Item Number Description
Number
606567 FOREIGN ORDER 21 K0000033-0002 KIT,HUB,MODEL 12102 W/ 4 IF IFM,ROHS
Order Line Qty Qty Cumulative Secondary Secondary Secondary
UOM
Number Requested Shipped Qty Qty Requested Qty Shipped Cumulative Qty
1.1 EA 1 1 0 0 0
Shipping Instructions NEW ORDER SHIP BEST WAY AIR CONTACT KARMO POOM +372 6014570, KARMO@AASAT.EU
Packing Instructions
From Serial Number To Serial Number
000046 000046
Order
Number
606567 FOREIGN ORDER 21 9131-0105-0250 RG6 RoHS IFL CABLE KIT 250 FT
UOM
2.1 EA 1 1 0 0 0
Order
Number
606567 FOREIGN ORDER 21 4100-0012-0001 8 PORT KVM SWITCH FOR IBM MODEL
UOM
3.1 EA 1 1 0 0 0
Figure 3. Example of a Packing Slip

RF Diagram – PAK Datacom

AC Power
Codan Redundant 16W Ku-band 110-265 VAC
Codan
Codan BUCs
6580 BUC Gain = 73dB Nom.
6916-W/S-48/IF
16W Ku-band P/S Atten. = 12 dB Max.
INT RF Out = 42dBm Max.
10MHz IFL Cable per Codan L-Band
IF Transceiver 6700/6900 +48VDC
series USER GUIDE (pg. 33)
BUC
0dBm
38.0°E
1
± 2dBm
A
1:2 Divider
-16dBm
L-band (950 – 1450 MHz) N Connector
Tx
F Connector SMA N IFL L-band + 10MHz Tx IF
Connector WR-75 Flexible
BUC
Connector In Waveguide
2
i -1 dBm to -43 dBm +48VDC
N (per carrier)
C Paksat 1
F O
2800 MHz LO
I Codan
D 6580
N A P/S
I N Ku-band Transmit
CODAN
T 6586 AC Power
(14.0 – 14.5 GHz)
to Feed
110-265 VAC
I 6 Redundant
Controller
5
5 RF Configuration
5 (reference Codan
- 0 drawing #03-01166 for
I cabling connections) 3.8M Patriot
TX380-AZ
F I Gain Tx 53.5 dBi
Gain Rx 51.8 dBi
F AC Power 15VDC @9W supplied by
H U 115/230 6586 Controller to each
u VAC LNB
Ku-band Receive
+3 dBm to -57 dBm LNBs - NJR2637E (10.95 – 11.70 GHz)
b (composite) External Reference from Feed
LNB
2
SMA (10.95 – 11.70 GHz)
F Connector
F Connector Connector TRF
N Connector
Rx
IFL L-band + 10MHz Rx IF
H L-band (950 – 1700 MHz) IFL Out
LNB
1
AC Power
AC Power 115/230
90-265 VAC VAC
Indoors Outdoors
RF Diagram Codan Redundant 16W Ku-band
Figure 4. Example of a Network Block Diagram

1. Install iDirect Hub Components according to rack elevation.

It would be in your best interest to always configure the Protocol Processor and the NMS
AFTER you have installed the equipment in the rack location. This is what we refer to as
installing iDirect hub components according to rack elevation. Also be sure to cable up
everything. It never hurts to check twice! Set up the IP addresses on all of your servers
and build network in the database.
2. Commission the Hub.
3. Commission a Remote.
4. Fill in the Commissioning and Configuration Checklist.
5. Perform Acceptance Test Plan (ATP).
3.1 Customer Familiarization Training

After the installation is complete, it is important that the customer have a basic understanding
of the iDS or iDX software that supports their hub. This includes the installer downloading the
training guides for iBuilder, iMonitor and iSite.
3.1.1 Downloading the Training Guides

To download these guides, perform the following:
1. Browse to http://tac.idirect.net.
2. Login by using your user name and password.
3. Click on Software Releases.
4. The software upload page displays.
5. Scroll down to Installation Best Practices.
6. Click on each guide to download it to your PC or laptop.

7. Click on the Training Acceptance form to download the form to your PC or laptop.
8. Train the customer through demonstration as described in the following sections.
9. Once complete, make sure you receive sign-off from the customer.
When the training is complete and you have customer sign-off, return the signed form to the
iDirect Implementation Group via email at implementation@idirect.net.
3.1.2 Providing iBuilder Training

It is important that the customer knows how to properly commission remotes, set initial power,
and set max power. Show the customer how to do this by demonstrating how to use iBuilder to
add and configure the following components:
• Hub site (Teleport) hardware
• Remote site (VSAT) hardware
• Upstream carriers
• Downstream carriers
• Hub Line Cards
• New Netmodems
• Existing Netmodems
3.1.3 Providing iMonitor Training

Demonstrate how to use iMonitor to view the following:
• Acquisition of a Netmodem into the network
• Statistics analysis for potential RF-related or IP-related issues
• QoS Configuration, per remote
• Rate Shaping
• Hub Line Card RF and IP statistics
• Netmodem RF and IP statistics
• Real-time network RF and IP statistics
• Historical network RF and IP statistics
3.1.4 Providing iSite Training

Demonstrate how to use iSite to install, commission, and monitor remote sites. Specifically,
demonstrate the following tasks:
• Upgrade remotes to new software releases
• Perform antenna pointing
• Perform cross-polarization alignment
• Perform “1 dB Compression Point Test”
• Change and set transmit power levels
We will discuss how to use the As-Built template in Module 4 of this class.
Open your BHI Student Workbook and begin the exercises.
Module 4: The As-Built
Document Preparation
Goal: Through lecture, presentation and visual display each learner will be able to understand,
explain and demonstrate how to properly prepare an As-Built document for program manager
review and verification.
Objectives:
1. Understand the purpose of the As-Built documentation.
2. Identify the important sections within an As-Built document.
3. Create an As-Built document using data/information supplied by the instructor.
The As-Built Document Preparation
4.1 Introduction and Overview
The hub installation “As-Built” document provides information about your hub installation site
and documents how the hub equipment is installed. You should definitely keep this information
on-hand for future reference.
The following information is included in the Hub Installation “As-Built”:
• Installation Site Information, which contains information about the hub installation site.
• Problems and Resolutions, which lists any problems encountered during installation and
how they were resolved.
• Network Diagram, which provides a diagram that illustrates how the network is installed.
• Infrastructure Network Diagram, which provides a diagram that illustrates the IP address
scheme that is applied to the network.
• Frequency Plan Diagram, which provides a diagram that illustrates end-to-end links.
• Component Information, which describes the hub components that are installed.
• Cable Run List Definitions, which describes how each component is connected.
• Equipment Rack Elevation, which illustrates where each component is mounted in the
equipment rack.
• Supplemental Information, which provides key points of contact, digital photographs of the
installation, and any other information that is not previously covered.
4.2 Completing the As-Built Template

A completed As-Built document is required by iDirect so that any issues pertaining to an
installation can be identified and rectified quickly. This section describes how to complete the
Hub Installation “As-Built” template, and it is written for the installer responsible for the hub
installation.
4.2.1 Before You Begin

The Hub Installation “As-Built” template contains interactive diagrams that you are required to
complete. You must have MS Visio installed on your PC before you can use some of the features
of the template.
There are three ways in which you provide Information:
• Editing. Information shown in the interactive diagrams which you are required to edit is in
bold blue font. To change the information, double-click the diagram (MS Visio opens) and
type the new information over the blue text. When you are finished editing, simply click
outside MS Visio to close the diagram and return to the As-Built template.
• Fields. There are fields that you are required to complete. Click the gray box and type the
requested information.
• Commands. You are required to log on to certain pieces of equipment and enter commands
to retrieve data. Commands that you type are shown in blue courier font.
The template is fully editable; you can provide additional information about the installation
that is not directly covered in the previous sections by typing the data into the appropriate
section or in the Installation Photographs & Additional Information section at the end of the
template. Include diagrams or photographs in addition to those that are requested.
4.2.2 Instructions
To complete the Hub Installation “As-Built” template, use this document as a guide to
completing each section and perform the following steps:
1. Installation Site Information. Complete this section by using data that is specific to the
customer site.
2. Problems and Resolutions. Using Table X on page XX, describe any problems you
encountered and how you resolved them.
3. Network Diagram. Using the interactive MS Visio diagram found in Figure X on page XX,
click on the blue text and modify the network block diagram. Add or delete blocks as
required.
4. Infrastructure Network Diagram. Using the interactive MS Visio diagram found in Figure X
on page X, label the diagram with the IP addresses as applied to the network.
5. Frequency Plan Diagram. Perform the following:
a. Using the interactive MS Visio diagram found in Figure X on page X, click on the blue
text and type over the information requested.
b. Using Table X on page X, complete the outbound carrier information.
c. Using Table X on page X, complete the inbound carrier information for each inbound
carrier.
6. Component Information. Using Table X on page X, specify the company name and enter
the IP address and password (if applicable) for each component that is installed.
a. Hub RF Components. Enter the transmit equipment, receive equipment, antenna and
RF link information.
b. Remote Components. Enter the transmit equipment, receive equipment, antenna and
RF link information.
c. Upstream Switch Configuration. Logon to the upstream switch as root, and enter the
following command:
Enable show run
Paste the running configuration into the Upstream Switch Configuration section.
d. Tunnel Switch Configuration. Logon to the tunnel switch as root, and enter the
following command:
Enable show run
Paste the running configuration into the Tunnel Switch Configuration section.
7. Cable Run List Definitions. Using Table X on page XX, specify the company name and enter
the cable IDs and destination for each cable switch port number, as they apply to both
upstream LAN and tunnel LAN switch connections. Sample data is shown in the Upstream
LAN Destination column. Clear this information and enter your specific data. Complete
the Destination column for both the Upstream and Tunnel LAN switches. If the optional
iDirect SkyMonitor 1880 Spectrum Analyzer is installed, complete the cable run lists in
Table XX on page XX and the interconnect diagram in Figure X on page XX.
8. Equipment Rack Elevation. Using the diagram shown in Figure X, modify the rack
elevation to reflect the equipment mounted in the rack.
9. Supplemental Information. Using Table X on page XX, enter the key points of contact.
10. Installation Photographs & Additional Information. You are required to photograph the
completed installation, and return the photographs to iDirect. Include digital photographs
that clearly show the following:
• Equipment rack front view
• Equipment rack rear view
• Hub Line Cards with serial number labels applied
• Cables with appropriate labels applied
• Neatly routed and tied cables within the rack
• Other pertinent details
When you have completed the As-Built template, return it with digital photographs to iDirect
by email to: implementation@idirect.net.
The section contains information about the hub installation site:

Site information is provided as follows:
• Customer Name:
• Teleport Name:
• Teleport Location:
• Installer Name and Title:
• Date Commissioned:
• Date of this Report:
• iDirect Software Version:
• iDirect Hub Chassis Model:
• Hub Room Number:
• Hub Rack Number:
The local ISP is connected (if applicable) as follows:
Multiple hub chassis are or are not installed. The hub chassis are or are not linked together in a
daisy chain configuration.
iDirect SkyMonitor 1880 Spectrum Analyzer is or is not installed.
If SkyMonitor is installed, the IP address and logon information is as follows:
• IP Address: User Name: Password:
The upstream switch and tunnel switch port connections to your switch/router are as follows:
• Upstream Port Number: Upstream Port Speed:
• Tunnel Switch Number: Tunnel Switch Speed:
Remote monitoring and control for iDirect access is or is not available.
If access is available, the IP address and logon information is as follows:
• IP Address: User Name: Password:
If access is not available, the reason is explained here:
In this table, list any problems encountered and how they were resolved.
The Network Block Diagram illustrates the interconnection of network elements.
The Infrastructure Network Diagram illustrates the IP addresses as they apply to your network.
The Frequency Plan Diagram illustrates the IF/RF components of your network. List the details
in the tables assocaited with this diagram.
This table lists the IP addresses and passwords (if applicable) for hub components that are
installed.
This section describes the Hub RF components installed.

Transmit Equipment Information
The following information describes your up-converter:
• Manufacturer:
• Model:
• RF Link (Ku-Band or C-Band):
• IF Band (70 MHz or 140 MHz):
• LO Frequency (MHz):
Center Frequency (MHz):
Receive Equipment Information
The following information describes your down-converter:
• Manufacturer:
• Model:
• RF Link (Ku-Band or C-Band):

• IF Band (70 MHz or 140 MHz):
• Center Frequency (MHz):
Antenna Information
The following information describes your antenna:
• Diameter (m):
• Manufacturer:
• Model:
• Feed (linear or circular):
RF Link Information
The following information describes your RF link:
• Total Up Converter: LO Frequency (MHz):
• The system is or is not fully redundant with automatic failover.
• Spectral inversion is or is not required.
This section describes the Remote Components installed.

Transmit Equipment Information
The following information describes your BUC:
• Manufacturer:
• Model:
• Transmit Polarization:
Receive Equipment Information
The following information describes your LNB:
• Manufacturer:
• Model:
• Receive Polarization:
Antenna Information
The following information describes your antenna:
• Diameter (m):
• Manufacturer:
• Model:
• Feed (linear or circular):
RF Link Information
The following information describes your RF link:
• RF Link: (Ku-Band or C-Band):
• iDirect Satellite Router Model:
UPSTREAM SWITCH CONFIGURATION
This section contains the upstream switch configuration at the time of installation.
TUNNEL SWITCH CONFIGURATION
This section contains the tunnel switch configuration at the time of installation.
Use this table to list the cable information.
On the Equipment Rack Elevation diagram, illustrate where each hub component is mounted in
the equipment rack.
In this section, list the points of contact for the installation and include photographs of the
installation as well as any additional information not previously covered.
Glossary
Acquisition A process whereby the satellite modem locks onto the proper satellite carrier.
ACU Antenna control unit.
ADC Analog-to-Digital Converter. A device that converts analog signals to a digital

representation.
Analog Method of signal transmission in which information is relayed by continuously altering

the wave form of the electromagnetic current. An analog signal is responsive to
changes in light, sound, heat and pressure. See also digital.
Antenna Device for transmitting and receiving radio waves. Depending on their use and
operating frequency, the form on an antenna can change from a single piece of wire
to a dish-shaped device.
Antenna Alignment The process of optimizing the orientation of a satellite antenna's main direction of
(pointing) sensitivity towards the satellite to maximize the received signal level and to
minimize the chance of receiving unwanted interference from other satellite
systems.
Aperture A cross sectional area of the antenna which is exposed to the satellite signal.
Apogee Point in an elliptical satellite orbit that is farthest from the surface of the earth.
Asynchronous A communications strategy that uses start and stop bits to indicate the beginning and
end of a character, rather than using constant timing to transmit a series of
characters. Asynchronous methods are especially efficient when traffic comes in
bursts (and not regularly paced). Modems and terminals are asynchronous
communications devices.
Attenuation Weakening, usually measured in decibels, of a signal (loss) that occurs as it travels
through a device or transmission medium (e.g. radio waves through the atmosphere).
Attitude Control The orientation of the satellite in relationship to the earth and the sun.
Azimuth The horizontal co-ordinate used to align the antenna to the satellite. See also
Elevation.
Bandwidth The amount of data a cable can carry; measured in bits per second (bps) for digital
signals, or in hertz (Hz) for analog signals. A voice transmission by telephone requires
a bandwidth of about 3000 cycles per channel (3KHz). A TV channel occupies a
bandwidth of 6 million cycles per second (6 MHz) in terrestrial systems. In satellite
based systems a larger bandwidth of 17.5 to 72 MHz is used to spread or “dither” the
television signal in order to prevent interference.
Baud The number of times an electrical signal can be switched from one state to another
within a second.
Bit Error Rate The ratio of the number of information bits received in error to the total number of
(BER) bits received, averaged over a period of time. It is used as an overall measure of the
quality of a received digital bit stream.
Bit Rate The number of bits transmitted within a second (bps) in a digital communication.
Broadcast Sending a single message to all the nodes of a network.
C band Band of frequencies used for satellite and terrestrial communications. Most
communications satellites use a range from 4 to 6 gigahertz (billion cycles per
second). Requires larger ground antennas, usually twelve feet in diameter, for
television reception.
Capacity A proportion of the satellite’s bandwidth which is used to establish one or more
communication channel.
Carrier The basic radio, television, or telephony transmit signal. The carrier in an analog
signal.
Carrier Frequency The rate at which the carrier signal repeats, measured in cycles per second (Hertz).
This is the main frequency on which a voice, data, or video signal is sent. Microwave
and satellite communications transmitters operate between 1 to 14 GHz.
Channel A band of radio frequencies assigned for a particular purpose, usually for the
establishment of one complete communication link, or a path for an electrical signal.
Television signals require a 6 MHz frequency band to carry all the necessary picture
detail. Channel frequencies are specified by governmental agencies.
CIR See Committed Information Rate.
Circular Occurs when the two orthogonal components of a waveform are exactly 90 degrees
Polarization out of phase. Both components have the same amplitude. When one component is at
Zero (reference) the other component is either at maximum or minimum amplitude.
Coaxial Cable A transmission line in which the inner conductor is completely surrounded by an outer
conductor, so that the inner and outer conductor are coaxially separated. The line
has a wide bandwidth capacity which can carry several television channels and
hundreds of voice channels.
Collocated Two or more satellites occupying approximately the same geostationary orbital
(satellites) position. To a small receiving antenna the satellites appear to be exactly at the same
place. The satellites are kept several kilometers apart in space to avoid collision.
Committed The guaranteed network bandwidth availability.

Information Rate
(CIR)
Common Carrier An organization which operates communications circuits. Common carriers include
the telephone companies as well as the owners of the communications satellites.
Communications A satellite in Earth orbit which receives signals from an Earth station and retransmits
Satellite the signal to other Earth stations.
COMSAT Communication Satellite Corporation, the U.S. signatory for INTELSAT.
Continuous Wave Signal consisting of a single frequency especially used in testing satellite modems and
(CW) antennas.
Decibel (Db) The standard unit used to express the ratio of two power levels. It is used in
communications to express either a gain or loss in power between the input and
output devices.
Decoder A television set-top device that converts an electronically scrambled television

picture into a viewable signal.
Delay The time it takes for a signal to go from the sending station through the satellite to
the receiving station (around one-quarter of a second).
Demodulator A satellite receiver circuit which extracts or “demodulates” the desired signals from
the received carrier.
Deterministic- A technique used to prevent collisions of remotes transmitting simultaneously in

TDMA (D-TDMA) which synchronized burst time plan provides the network timing.
Digital Representation of information as bits of data for transmission. Digital

communications technology permits higher transmission speeds and a lower error
rate than analog technology. As an analog signal is received and amplified at each
repeater station, any noise is also amplified. A digital signal, however, is detected
and regenerated (not amplified), and any noise is lost unless it corresponds to a value
that the regenerator interprets as digital signal.
Dish Slang for parabolic antenna.
Downlink The part of the satellite communications link that involves signal retransmission from
the satellite and reception on the ground. See also Uplink.
Downstream Downstream carrier (synonymous to outbound carrier) is the carrier from the Hub to
Carrier the remote modem, via the satellite.
Duplex Two-way communications. The telephone line is full duplex in that both directions of
communication occur at the same time. Walkie-talkie communications is half-
duplex– only one party may transmit at a time.
Earth Station A combination of devices (antenna, receivers) used to receive a signal transmitted by
one or more satellites.
Elevation The upward tilt (vertical coordinate) of a satellite antenna measured in degrees,
required to align the antenna with the communications satellite. See also Azimuth.
Elliptical Orbit Orbits in which the satellite path describes an ellipse, with the Earth located at one
focus.
Encoder A device used to electronically alter a signal so that it can only be understood on a
receiver equipped with a special decoder.
Equatorial Orbit An orbit with a plane parallel to the Earth’s equator.
FEC Forward Error Correction is an error correction method that adds redundant bits to a
bit stream, so that the receiver can detect and correct errors in transmission.
FEC Block The basic FEC unit is a FEC block.
Feed 1) The transmission of video content from a distribution center.
2)The feed system of an antenna.
Focal Length Distance from the center feed to the center of the dish.
Footprint The geographic area over which a satellite antenna receives or directs its signals.
Free Slots Slots left in the dynamic sub-frame after all stream, guaranteed (CIR) and
preemptive bandwidth requests are satisfied. Free slots are allocated to all VSATs (up
or down), except the master, in a round-robin fashion.
Frequency The number of times that an alternating current goes through its complete cycle in
one second of time. One cycle per second is also referred to as one hertz.
Frequency A process designed to eliminate frequency interference between different satellite
Coordination systems or between terrestrial microwave systems and satellites.
Full duplex Transmission that occurs in both directions simultaneously over the communications
media (e.g. telephone).
Geostationary An satellite orbiting Earth at such speed that it appears to remain stationary with
satellite respect to the earth’s surface. See also Clarke Orbit.
Geosynchronous A satellite orbiting Earth at Earth’s rotational speed and at the same direction. A
satellite satellite in geosynchronous orbit is known as a geosynchronous or geostationary
satellite. The orbit is “synchronous” because the satellite makes a revolution in
about 24 hours. The satellites are about 35,800 kilometers (22,350 miles) above
Earth, and they appear to be stationary over a location.
Ground Segment All the Earth stations that are operating within a particular satellite system or
network.
Ground Station A radio station, on or near the surface of the Earth, designed to transmit or receive
to/from a spacecraft.
Guaranteed The capability for transmitting continuously and reliably at a specified transmission
Bandwidth speed. The guarantee makes it possible to send time-dependent data (such as voice,
video, or multimedia) over the line.
Guaranteed Slots Slots configured per VSAT and made available to that VSAT upon its request. When
the queue is depleted, these slots are taken away by the master and distributed to
other requesting VISNs as preemptive slots.
Guard Band A thin frequency band used to separate bands (channels) in order to prevent
(guardband) interference and signal leakage.
Guard Channel Unused frequency space between carriers that prevents adjacent carriers from
interfering each other.
Half Duplex A communications form in which transmissions can go in only one direction at a time.
With half-duplex operation, the entire bandwidth can be used for the transmission.
In contrast, full-duplex operation must split the bandwidth between the two
directions.
High Band The upper part of the Ku band downlink frequency range, from 11.7 GHz to 12.75
GHz.
HPA High Power Amplifier. Earth station equipment that amplifies the transmit RF signal
and boosts it to a power level that is suitable for transmission over an earth-space
link.
Hub RFT Hub Radio Frequency Terminal - Equipment that includes the antenna, U/C (up
Converter), D/C (Down Converter) HPA, and LNA, which provides the up and down
conversion of signals in a satellite-based network.
IF Intermediate Frequency. The frequency range 70 to140 MHz used for the distribution
of satellite signals from the LNB at the dish to the user’s satellite receiver. It is
always used in direct-to-home systems and is the most suitable for distribution of
digital signals in communal systems – IF systems.
Inbound Carrier See Upstream Carrier.
Inclination The angle between the orbital plane of a satellite and the equatorial plane of the
Earth.
Indoor Unit (IDU) The satellite modem and indoor devices (in contrast to outdoor units, ODU).
Information Rate The user data rate including IP headers plus iDirect overhead. The Downstream
overhead is approximately 2.75% of the information rate.
INTELSAT International Telecommunications Satellite Organization. Agency that operates a

network of satellites for international transmissions.
Interfacility Link The cable that connects the indoor unit with the outdoor unit.
(IFL)
Intermediate Generally, 70 MHz or 140 MHz.

Frequency (IF)
Ka band The frequency range from 18 GHz to 31 GHz.
Ku Band Frequency range from 10.9 GHz to 17 GHz, increasingly used by communications
satellites. Requires smaller ground antennas, usually four feet (1.2 meter) in
diameter.
L-Band The frequency range from 0.5 GHz to 1.5 GHz.
Linear Occurs when the two vector components of a waveform are in phase. The two
Polarization components can have different amplitudes.
LNA Low Noise Amplifier – The preamplifier between the antenna and the earth station
receiver. For maximum effectiveness, it should be located as near the antenna as
possible, and is usually attached directly to the antenna receive port.
LNB Low Noise Block Converter is the converter on the down link that takes the Ku, Ka,
or C-Band signal from the satellite and converts it to a lower frequency (L-band)
signal that can be fed through the IFL cable to the modem.
Low Earth Orbit Satellites that are not stationary from a fixed point on earth and have the lowest
(LEO) satellite orbit of all communication satellites. Most handset-to-satellite systems are based on
LEO satellites using L-Band.
Low Noise The preamplifier between the antenna and the Earth station receiver. For maximum
Amplifier (LNA) effectiveness, it must be located as near the antenna as possible, and is usually
attached directly to the antenna receive port.
Margin The amount of signal in dB by which the satellite system exceeds the minimum levels
required for operation.
Multiplexing Techniques that allows a number of simultaneous transmissions to travel over a single
circuit.
ODU Outdoor unit, such as an antenna dish.
Outbound Carrier See Downstream Carrier.
Passband The range of frequencies handled by a satellite translator or transponder.
Perigee The point in a satellite’s orbit where it is closest to Earth.
Polarization Design technique used to increase the capacity of the satellite transmission channels
by reusing the satellite transponder frequencies.
QPSK (Quadrature Digital modulation scheme used in transmission communications to allow increased
Phase Shift Keying) sending capacity.
Rain Outage Loss of signal at Ku or Ka Band frequencies due to absorption and increased sky noise
temperature caused by heavy rainfall.
RMA Return Material Authorization. Issued by iDirect’s TAC for equipment that must be
returned for repair or replacement.
Satellite A sophisticated electronic communications relay station orbiting 22,237 miles above
the equator moving in a fixed orbit at the same speed and direction of the Earth
(about 7,000 m.p.h. east to west).
Satellite The use of geostationary orbiting communication satellites to relay transmission from
Communications one Earth station to another or to several Earth stations. It takes only three satellites
to cover the whole Earth.
Satellite Pass Segment of orbit during which the satellite “passes” nearby and in the range of a
particular ground station.
Shared hub Satellite communications operations center that is shared among several separate
network users; often used for VSAT operations.
Single-Channel- A method used to transmit a large number of signals over a single satellite
Per-Carrier (SCPC) transponder. User data is transmitted to the satellite continuously on a single
satellite carrier and can be received by a single location (point-to-point link) or
multiple locations (SCPC - TDMA link).
SNR Signal to Noise Ratio - In analog and digital communications, signal-to-noise ratio,
(S/N or SNR), is a measure of signal strength relative to background noise. The ratio
is usually measured in decibels (dB).
Spillover Satellite signal that falls on locations outside the beam pattern’s defined edge of
coverage.
Subcarrier In satellite television transmission, the video picture is transmitted over the main
carrier. The corresponding audio is sent via an FM subcarrier. Some satellite
transponders carry as many as four special audio or data subcarriers.
Symbol Rate Symbol Rate refers to the number of symbols that are transmitted in one second.
From the symbol rate, you can calculate the bandwidth (total number of bits per
second) by multiplying the bits per symbol times the symbol rate.
TAC Technical Assistance Center. iDirect’s customer service and technical support
center, available 24/7/365 at http://tac.idirect.net or 703-648-8151.
TDM (Time A type of multiplexing where two or more channels of information are transmitted
Division over the same link by allocating a different time interval (“slot” or “slice”) for the
Multiplexing) transmission of each channel. (i.e. the channels take turns to use the link.)
TDMA (Time A communications technique that uses a common channel (multipoint or broadcast)
Division Multiple for communications among multiple users by allocating unique time slots to different
Access) users.
Transmission A protocol developed for the internet to get data from one network device to
Control Protocol another; TCP uses a retransmission strategy to ensure that data will not be lost in
(TCP) transmission.
Transmission Rate Includes all over-the-air data. This includes the user data (information rate), iDirect
overhead, and FEC encoding bits.
Transponder A device in a communications satellite that receives signals from the earth,
translates and amplifies them on another frequency, and then retransmits them.
Turbo Product A Forward Error Correction (FEC) method in which small blocks (128 bytes—1 kb) or
(Block) Code (TPC) large blocks (512 bytes—4 kb) are used.
UHF Ultra High Frequency. Band in the 500-900 MHz range, including TV channels 14
through 83.
Uplink The Earth station used to transmit signals to a satellite and the stream of signals
going up to the satellite.
Upstream Carrier Upstream carrier (synonymous to inbound carrier) is the carrier from the remote
modem to the Hub, via the satellite.
VHF Very High Frequency, Refers to electromagnetic waves between approximately 54

MHz and 300 MHz.
VSAT Very Small Aperture Terminal. Means of transmission of video, voice, and data to a
satellite. Used in business applications.

INST BHI8x10x InstStd Guide 080109 Rev1

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

INST BHI8x10x InstStd Guide 080109 Rev1

Hochgeladen von

Copyright:

Verfügbare Formate

Instructor/Student Guide

Broadband Hub Installation (BHI) Course

Document Name: INST_BHI8x10x_InstStdGuide_080109_Rev1.pdf

Document Part Number: GE0000049

ii BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

Module 1: Introduction to Broadband Hub Installation

Module 2: Introduction to System Installation

Module 3: Hub Installation Paperwork, Processes and Procedures

Module 4: The As-Built Document Preparation

iv BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x v

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x ix

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 1

Note: Training provided is based on the particular version utilized or

Prerequisite Learner Skills

2 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

Course Goals and Objectives

Table 1. Course Modules and Goals

Module Title Goal

In addition, learners will perform the following hands-on lab exercises:

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 3

4 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 5

6 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 7

1.1 Overview of iDirect’s Broadband Satellite

8 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 9

10 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 11

12 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 13

14 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 15

• Easy-to-use integrated solution — The rack-mounted SkyMonitor is fully integrated with

16 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 17

18 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

1.2 Spread Spectrum

Spread Spectrum (SS) is a transmission technique in which a pseudo-noise (PN) code is

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 19

20 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 21

– Minimum rate for all Spreading factor is 64 Ksps

22 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

1.3 Mesh Networks

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 23

1.3.1 Mesh-enabled Remote Restrictions

24 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

Upstream SAR is always enabled

1.3.2 Mesh Hardware Support and Requirements

1.3.3 NMS Control of Mesh Networks

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 25

1.3.4 Monitoring Mesh Networks

26 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

– The number of bursts received from the peer

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 27

28 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 29

30 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

1.4.1 TRANSEC Key Management

BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x 31

32 BHI Course Instructor/Student Guide, iDS 8.x and iDX 1.0.x

Key Rolling and Key Ring