Introduction to System Installation

iDS v6.0
Chapter 4, IOM Basic Training
March 2006 1
 Copyright Notice

iDirect Technologies Technical Training Manual

Copyright © 2002; 2004 - 2006, iDirect, Inc. All rights reserved. This training
material may not be reproduced, in part or in whole, without the permission of
iDirect, Inc.
All other brands or product names are trademarks or registered trademarks of
their respective holders.
Printed in the USA.
No part of this work covered by copyright may be reproduced in any form.
Reproduction, adaptation, or translation without prior written permission is
prohibited, except as allowed under the copyright laws.
This publication is provided by iDirect Technologies as-is without warranty of any
kind, either express or implied, including, but not limited to, the implied warranties
or conditions of merchantability or fitness for a particular purpose. iDirect
Technologies shall not be liable for any errors or omissions which may occur in
this publication, nor for incidental or consequential damages of any kind resulting
from the furnishing, performance, or use of this publication.
Information published here is current or planned as of the date of publication of
this document. Because we are improving and adding features to our products
continuously, the information in this document is subject to change without notice.

2
 Training Objectives
Introduction to iDirect System Installation
Introduction to Network Components
Network Design Considerations
Installation & Initial Setup of Network
Components
Typical Configuration/Variations
Rack Elevation/Physical Installation
Interface Requirements
Cabling (LAN Cat 5; RF Coaxial)
Hub Software Provided
¾ Red Hat Enterprise Linux, v3, Update 3
¾ NMS & PP Specific Software Packages
o Server/Client Components
o Manual Parameters Entry LAN Switch
Critical Items Parameters Protocol Processor
NMS Server
Preparation for Building a Network
from Scratch
Tools Required/Recommended iDirect Hub
Chassis
Hand Tools & Test Equipment w/Universal Line
Cards

3
 Typical Remote Site Configuration

Antenna Reflector
(w/mount)

iDirect Remote VSAT Solution

TM
Ethernet/VLAN
iNFINITI Capable Switch Users

L-Band IFL
(Inter-Facility Link 10/100 Mbps LAN
Coaxial Cable Ethernet

PCs

VoIP
Benefits Phones Remote LAN
$ Simple Configuration
$ No Power At Antenna
$ VSAT Antenna for High Bandwidth
and Reliability
$ Centrally Managed
$ Enhanced TCP Performance

4
 Remote Site Design Considerations
Antenna
Defined by Upstream Carrier (Link Budget) NOT individual site bandwidth
Cost typically a secondary consideration

BUC
Up to a 5W BUC can be Powered by the NetModem itself
High Power Amplifier (HPA) add-ons require external power provisioning
• NetModem powers 1st stage BUC (1-2watt)
• External AC must be present at roof/antenna location
LNB
Dielectric Resonance Oscillator (DRO) LNB, (less expensive)
Phase Lock Loop (PLL) LNB, Required when Downstream </= 512 kbps)
LNB ‘Stability’ value determines acquisition sweep range

Coaxial Cable Length

Will affect Link Budgets
May affect power to BUC (DC loop resistance)

Current remote site IP Transmit Limits

1.4 Mbps of IP Data (Info) Rate w/small (1k)-block (0.66) FEC
4.2 Mbps of IP Data (Info) Rate w/large (4k)-block (0.793) FEC

NetModem is limited to ~500 concurrent Active TCP Sessions

cRTP sessions count towards this.
5
 Upstream Design Considerations
Upstream should be based on data requirements (Link Budget)
Size may also be limited by remote ODU size and location
Two FEC Options currently available
0.660 FEC
• Provides for more time-slots
• Allocates less BW per time slot
• More Burst-able Bandwidth available
0.793 FEC
• Used when number of sites are less
• Allocates more BW per time slot
• Less Burst-able Bandwidth available
Upstream supports Dynamic/Static and “Sticky” CIR
“Scheduled Dedicated Timeslot”
How often a remote is given its dedicated time-slot (every frame,
every-other frame, third frame, etc. up to a max 2 second interval)
Allows for more efficient use of available time slots on the Upstream
Releases more time slots for use as Burst-able Bandwidth (free slots)
Should only be used on networks that can tolerate the demand delay
Each Upstream requires a Hub Line Card for carrier processing

6
 Typical Hub Configuration
‘Upstream’
Network Traffic or Router Maintenance & Control (M&C)
‘Upstream’ LAN Segment (CFE) or ‘Tunnel’ LAN Segment

NMS Server
& Spare Regional
Teleport

Internet
Backbone
‘Core’ or Hub RFT
‘Edge’ Protocol Chassis
Router Processor
(Controller)

NMS GUI
(Configuration
& Monitoring) Protocol
Processor
Blades (1+n)
iDirect Hub Components

7
 iDirect Mini/Private Hub
Solution for Enterprises and Smaller Organizations
Supports Non-Teleport Class RFT equipment (BUC/LNB)
Can provide DC power
Can provide 10 MHz reference
Only One Downstream & One Upstream Capability
Mini Hub vs. Private Hub - Number of Servers
(Private Hub includes Backups) ‘Upstream’
Router (CFE)

NMS
‘Core’ or ‘Edge’ Server
Router
Internet
Backbone

Protocol
Processor
(Controller)
Private
Hub
NMS GUI
(Configuration Protocol
& Monitoring) Processor
(Blade)
iDirect ‘Mini’
Mini’ Hub

8
 Downstream Design Considerations
SCPC Carrier using Packet Division Multiplexing actually (vs. Time
Division Multiplexing)
Based on data traffic requirements (plus required overheard)
May be limited by remote ODU size & geographic location
Size of Downstream will define whether to use DRO or PLL LNBs
9.1 Mbps of IP Data (Info) Rate on the Downstream (NMII, II+)
TM
18.2 Mbps - IP Data (Info) Rate on Downstream with iNFINITI HLC
The Downstream supports a configurable Dynamic CIR
One Frame Length only per network
Set Frame Length based on applications (set for Downstream carrier)
Downstream carrier provides network frame synchronization (timing)
TM
New FEC Rates supported (iDS v6.x), iNFINITI HLC ONLY
0.431 Option
0.533 Option
0.879 Option
TM
Existing 0.793 FEC option supported, II+ & iNFINITI HLC
Existing 0.495 FEC option supported, II+ HLC Only

9
 20 Slot Chassis Options
iDirect Hub Chassis
Accommodates Up To 20 Line Cards
NMS Support for Multiple Chassis
Location of Reference Clock Modules 1-IF Rear Ports

iDirect Allows for Hub Enablement of

an Existing Teleport 5-IF Rear Ports

Solution is Comprised of a Required

Set of Hardware, Software, and
Installation Services
Optional Products and Services are
Available to Enhance Hub
Enablement
Network Operator Must have Existing
Satellite Bandwidth Front View

5IF Option Allows Easy Access to

Multiple Satellites and/or
Transponders Simultaneously
RCMs Installed

10
 Reference Clock Module (RCM)
Installed in Dedicated Slots, RCM A & B
on the Rear Panel of Chassis
Required Hardware for iDS v6.0 &
Greater
Required Hardware for iDS v5.0 when
Implementing Run-Time Frequency
Hopping Feature (vs. Carrier Grooming)
Provides Stable Timing Reference
¾ Internal 10 MHz Reference (via Oven-
ized Crystal Controlled Oscillator)
¾ Station Clock External Reference – Locks
Frequency Locked Loop (FLL) of Internal
Reference if Selected

Fully Redundant w/Auto Switchover if

Online Module Fails
Hot Swappable

11
 Hub Chassis Considerations
Designed for an enterprise class teleport RFT Chain
Can be utilized with ‘VSAT’ Hub if external DC/10 MHz reference implemented
Chassis, all hub boards 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
Cost of L-to-70 Mhz similar to L-to-C or L-to-Ku Band Converters

Hub does not have to ‘see’ itself for commissioning or monitoring

Initial Hub Line Card layout should consider future expansion of any network
Allocate sufficient slots (allows for future reconfiguration of Network/Timing Groups
if/when necessary)
HLC Auto-Failover requires spare to be in same Network/Timing Group

Teleport must allow for signal processing losses through chassis

1IF losses are 19 db, both Tx and Rx path (20:1 splitter/combiner)
5IF losses are better, 7db 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.

12
 Chassis – Default Slot Groups

Slot 10

Slot 11

Slot 20
Slot 15

Slot 17

Slot 19
Slot 14

Slot 18
Slot 12

Slot 13

Slot 16
Slot 6
Slot 1

Slot 2

Slot 4

Slot 7

Slot 8

Slot 9
Slot 3

Slot 5
Jumpers (4 per chassis)
between slot groups

Slot Group 1 Slot Group 2 Slot Group 3 Slot Group 4 Slot Group 5 (Re-
(Re-Configurable)

TX/RX Port A TX/RX Port B TX/RX Port C TX/RX Port D TX/RX Port E (Hard Wired – ‘Fixed’
Fixed’ Configuration)

• Up to 5 Multi-
Multi-Upstream networks per chassis easily, without additional configuration
configuration (5IF)
• Each Group uses common (network, frame synchronization) timing on on the backplane
• Groups can be combined to increase multi-
multi-Upstream capacity by selecting the software configurable jumper
• A Single (Solo) Downstream-
Downstream-Upstream network can take any slot since it does not interact with
with backplane timing
• Rear panel TX/RX port parings fixed as shown, & cannot be reconfigured
reconfigured regardless of final ‘Network’
Network’ configuration

13
 Slot Group Variations - Example

Network 1 Network 2 Network 3

Slot 17

Slot 19
Slot 20
Slot 16
Slot 12
Slot 13
Slot 14

Slot 15

Slot 18
Slot 10
Slot 11
Slot 5
Slot 6
Slot 7

Slot 8
Slot 1
Slot 2
Slot 3
Slot 4

Slot 9
TX

TX
TX
TX

TX
TX
Downstream

TX
(Outroute)

STANDBY

SOLO
SOLO
STANDBY
Network 4
Upstream
(Inroute)

RX
RX
RX
RX
RX

RX

RX
RX
RX
Network 5
RX
RX
RX

RX

RX
RX
RX
RX
RX
RX

RX

Slot Group 1 Slot Group 2 Slot Group 3 Slot Group 4 Slot Group 5
“A” Ports “B” Ports “C” Ports “D” Ports “”E
“”E” Ports

Network 1 Network 2 Network 3 Network 4 Network 5

• Slot Groups 1, 2, and 3 are jumpered on the Backplane to share timing (requires software configuration
configuration only)
• Network 1 has one Downstream and 11 Upstream carriers (or some spares
spares ex, 10 Upstream & 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;
configured; no auto redundancy 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,
oversubscription, etc.)
• Standby Cards MUST adhere to established criteria for successful auto fail-
fail-over capability 14
 20 Slot Chassis Accessories

Hub Physical Installation (2 units)

Hub Chassis, 1IF or 5IF

Install Empty Chassis Without
Accessories Initially (No Fans, Power
Supplies, or HLCs); Weighs Less
Install With or Without Support Shelf
Next Install Accessories, Ensuring
All are Properly ‘Seated’ in
Associated Chassis Locations *
Configure EDAS Board With Assigned IP,
Subnet Mask and Gateway (Upstream
Router, eth0 Interface)

Hub Accessories

* Install Fans and Power Supplies, according to the 1. RCMs (not shown here)
instructions contained in the iDirect Hub Chassis 2. DB9F-DB9F, Null-Modem Cable
Installation Guide, p/n 8100-0003-0001 (1IF) and/or 3. Spare Coax/LAN Jumpers Set
8100-0003-0002 (5IF) 4. Static Wrist Strap
5. 1 - Seven Foot CAT5 Cable
6. Rack Mounting Hardware

15
 Hub Chassis EDAS* Board
Installed Behind ‘Fan Alarm’ Panel (During Assembly)/Rear of Chassis
Third Party Vendor Supplied Hardware & Software
Configured Using Vendor Provided Software (EDAS SYSCHECK 3.0 is
Contained in iDS Clients Module)
Allows Assignment of IP Address to Chassis Hardware
10 Mbps, Half-Duplex, Fixed Mode Only (No Auto-Negotiation)
Requires Null-Modem, DB9 Female to DB9 Female Cable for Typical
Chassis to PC Com Port Connection

* EDAS = Ethernet Data

Acquisition System

16
 Hub Universal Line Cards
Universal Line Cards are Flexible
Based on iDirect’s NetModem II+ or iNFINITITM Technology
Can Share Remote Units at Ratios Allowing Different Service Levels
Network Operator has Control of Sharing
Each Universal Line Card is Configurable via Local & Remote Access
Initial Release of iNFINITITM HLC as Direct Replacement for II+ HLC
Automatic/Manual Redundancy Supported on Both
¾ Spares must adhere to rules for correct substitution
¾ Limitations imposed at ‘Network’ boundaries

II+ HLC
iNFINITITM HLC

17
 Line Card – Design Considerations
Each Hub Line Card (NMII+) has a Modulator and De-Modulator
Each Carrier requires dedicated line card (always with II+ HLC)
TM
Initially, iNFINITI HLC becomes the direct replacement for II+ HLC
Hardware variations supported
No Modulator, 1 Demodulator only (M0D1, supported iDS v6.0)
No Modulator, dual Demod option (M0D2, for future mesh, multiple
Upstream carrier support)
5.750 Msps of Aggregate Bandwidth per line card (NMII+)
Downstream & Upstream combined
TM
11.5 Msps of Aggregate Bandwidth per line card (iNFINITI )
Downstream & Upstream combined
5,500-12,500 packets-per-second supported (Depends on Config)
TM
iNFINITI HLC now supports BPSK Modulation (iDS v6.0. )
A Hub Line Card with Downstream may also support one Upstream
II+ HLC and iNFINITI M1D1, M0D1 capable
Aggregate Bandwidth will define if a line-card can support both
Spare, or ‘Standby’ configured Hub Line Cards should be in the same
“Timing Group” for ease of failover (Manual or Auto Redundancy)

18
 II + Hub Line Card Installation
Hub Physical Installation Hold down screw
(top & bottom)
Modulator

II+ Hub Line Card (HLC)

Static Sensitive & Should be Installed According 950-1700 MHz
Transmit Out Port
to the Procedure Described in the iDirect Hub
Chassis Installation Guide, p/n 8100-0003-0001
(1IF) and/or 8100-0003-0002 (5IF) Status LEDs

Ensure Chassis/Slot is Powered Off (Physically)

Install HLC According to Referenced Procedure 10/100, Full/Duplex
Auto-Neg LAN Port
Making Certain HLC is Seated Properly
Tighten (2) HLC Hold Down Screws Console Port
Connect LAN Patch Cable Between LAN Port
RX Monitor Port
on Card & Chassis LAN Port Immediately Below
Slot
Connect Coax Patch Cable Between the TX Out 950-1700 MHz
Receive In Port Demodulator
and TX Combiner Port Immediately Above Slot
Board Pull Handle
Connect Coax Patch Cable Between the RX In (top & bottom)
and RX Splitter Port Immediately Below Slot
Connect Power and Power Up Chassis
CAUTION! Do NOT Connect TX Out Patch Cable Until Ready to Commission Outbound
Carrier. Doing So May Result in Inadvertent Transmission on Unassigned Frequency!

19
 iNFINITI Hub Line Card Installation
Hub Physical Installation Board Pull Handle
Hold down screw (top & bottom)
iNFINITI Hub Line Card (HLC) (top & bottom)

950-1700 MHz Power LED

Procedure identical to that of the II+ Transmit Out Port
Modulator (M1)
HLC as discussed on the previous page.
TX LED
Ensure Chassis/Slot is Powered Off 950-1700 MHz
RX Monitor Port
Install HLC According to Procedure
Making Certain HLC is Seated Properly Demodulator (D1)
950-1700 MHz
Tighten (2) HLC Hold Down Screws Receive In Port Status LED

Connect LAN Patch Cable Between LAN

Port ‘A’ on Card & Chassis LAN Port ‘A’ Console Port
Immediately Below Slot in Card Cavity
LAN ‘A’
Connect Coax Patch Cable Between the LAN ‘B’
(future)
TX Out and TX Combiner Port
Immediately Above Slot
(Both LAN ports
Connect Coax Patch Cable Between the are 10/100 Mbps,
RX In and RX Splitter Port Immediately Full or Half
Duplex, Set to
Below Slot Auto-Negotiate)

Connect Power and Power Up Chassis

iNFINITITM HLC
CAUTION! Do NOT Connect TX Out Patch Cable Until Ready
to Commission Outbound Carrier. Doing So May Result in
Inadvertent Transmission on an Unassigned Frequency!
20
 Hub Line Card Pre-Configuration
Hub Line Card (HLC) Preparation DB-9 to RJ-45 adapter Pin-Out
HLC Must Be Configured (IP-wise) to Accept Data DB-9 to RJ-45 Adapter Pin-Out
from the NMS Server RJ-45 Color Code DB-9
1 Blue 8
¾ Connect DB9 Female Adapter With Cat 5 Cable to 2 Orange 6
RJ45 ‘Console’ Port & Open HyperTerm Session 3 Black 2
4 Red N.C.
(9600, 8, none, 1, no flow control) 5 Green 5
¾ Secure Login Required; HLC Should Display Console 6 Yellow 3
7 Brown 4
Port prompt 8 White/Gray 9
¾ Type laninfo and ‘Enter’ to Confirm Current Address
¾ To Re-IP HLC, Retype laninfo Command Again Using
the Following Format:
laninfo <IP> <SUBNET> <GATEWAY>
Reset (for change to take effect)
¾ Gateway Should ALWAYS THE Hub Upstream Router
Tunnel Interface Address
¾ After Reboot, HLC Should Now Display New Address
When laninfo Command Re-entered; ‘Ping-able’
¾ HLC is Now Ready to Receive Valid Options File from
NMS/iBuilder
¾ Remember to Confirm Correct Hub Application & Image Console
Files are Loaded, or Update as Required Port

DO NOT RESET UNLESS AND UNTIL OPTIONS FILE

AND IMAGES ARE KNOWN TO BE COMPATIBLE!
21
 NetModem II/II+ Software Images

Boot Loader Control Process Application

•Hardware Boot Instructions •CpApp_V6.0.0.s19

Field Programmable Gate Array (FPGA) Images

•FpgaDqt_2plus-V106.bin
•FpgaRx1Tdma_2plus-V400.bin
•FpgaRx2Tdma_2plus-V315.bin Always – ENSURE IMAGE &
•FpgaTxScpc_2plus-V416.bin
•LutRxScpc_2plus-V002.s19
OPTIONS COMPATABILITY!!!

Loader (Image Set)(*.ldr) Options File (*.opt)

•Hub_ImageSet_2plus.ldr •H7994.opt

22
 iNFINITI Software & Images
iDS Software Images & Options
File Typically Loaded Using the
Current Version of iSite

Board DID Specific Configuration Detail

Options
File

Software Loading Order

FPGA Field Programmable Gate Array
Image Files (Binary ~ x.bin)
Image ‘Package’
iDirect Proprietary Application
iDirect (‘Falcon’ login required)

Falcon Process
telnet 0

Customized Linux (v2.4.24) Base

Operating System
Embedded Operating System (root login required)

23
 Protocol Processor Considerations
One Protocol Processor (PP) can support Multiple Networks
New/Additional PPs can be added to PP Blade Set, (aka Blade Stack)
Protocol Processor Controller – Process running on the NMS Server
• Manages a group of Protocol Processor Blades
• Determines remote distribution process
Each individual PP server is physically added as a Blade in the Blade Set
Allows for Automatic Redundancy & Protocol Processor Failover
Up to 20,000 Concurrent Active TCP Sessions Per Protocol Processor
PP Blade operates in excess of 18,000 packets-per-second
Each Blade limited to easily supporting up to 250 remotes
Remotes added remain assigned to a particular Protocol Processor Blade
• No Dynamic/Operational load balancing performed initially, iDS v6.0
• Remotes dynamically assigned/reassigned during startup and
acquisition, or as a result of a detected fail over condition only
Networks ‘share’ PP Blades as part of hardware array
Encryption Solution Needs Add-On Card if encryption required
TM
AES encryption supported (for Select iNFINITI Remotes)
3DES encryption supported (NM II+ platform only)
24
 Protocol Processor Processes
Protocol Processor Controller
Determines type & number of
processes for each Blade
1 pp_controller process per Blade Set
Managed by the NMS server
Controls process redistribution in the
event of Blade failure
PP Stand-Alone (sa) Processes
Monitor & Control process (samnc)
One samnc process runs on each Blade
Starts & stops other Blade processes
Communicates with the PP Controller
Manages a unified console for all other
sa processes running on a Blade
samnc console port fixed - 13255
Dynamic bandwidth allocation (sada)
Manages dynamic bandwidth allocation
for all upstream channels
Only one sada process per Blade Set
Bandwidth allocation manager (sana)
Manages the bandwidth allocation for
all downstream channels
Only one sana process per Blade Set
Remote protocol stack manager
(sarmt)
Number of sarmt processes varies;
depends upon number of
remotes/Blades
Manages TCP Acceleration, LL, PAD,
SAR, etc.
Router process (sarouter)
Performs all packet routing, upstream
and downstream
One sarouter process per sarmt
process
PP Monitor process (hpb_monitor)*
Monitors and restarts samnc process if
it terminates abnormally
*hpb = high powered box
25
 PP Blade Process Architecture
NMS Server PP Blade 1
PP Controller Process
sarmt Runs on NMS
sanmc Spawn and
Control manages samnc
NMS 1 per Blade Set
Control Server
Process Initial Blade spawns
M&C sada
1 - sada
sarouter sana
1 - sana
Blade also spawns
Monitor and Control sarmt process
(M & C) PP Blade 2 sarouter process
Each successive Blade
sanmc Spawn and
spawns it’s own:
M&C Control sarmt process
sarmt sarouter process
pp_controller Process
Additional sarmt &
sarouter processes
as required
sarouter

26
 Protocol Processor Blade

True ‘Heart’ of the iDirect Hub

IBM xSeries 335/336 Slim Line
Server
1 GB RAM & 3.2 GHz Processor
2 Physical 36.4/146 GB Hard Drives
ServeRAID Controller, Level 1
Red Hat Enterprise Linux
iDirect Proprietary iDS Software
Dual NIC’d, Both Ports Enabled

Command Line Operator Interface (Linux OS); xWindows GUI Available

Performs TCP acceleration functions within network
Monitors network traffic and IP connections
Provides 3DES/AES Encryption, When Optioned w/Add-on HiFn Board
27
 Network Management System (NMS)
– Server Design Considerations
One NMS Per Teleport (today)
Generally, no limit on
Number of Networks
Number of VSATs
Number of Hub Chassis

Supports Star/TDMA networks today

Hard Disk capacity may become the limiting factor
Built-in archival feature available that may alleviate this
Default number of database back-up copies configurable

Latest hardware configuration available for upgrades where needed

Larger, 146 GB HD vs. 36.4 GB
1 GB RAM vs. 512 MB; additional 1 GB RAM optional
Dual Processor @ 3.2 GHz vs. Single Processor @ 2.8 GHz

Manual redundancy only, today

Needs IP connectivity to remotes and all hub components
SNMP Proxy is MONITOR Only

28
 Hub Servers/NMS
IBM xSeries 336 Slim Line Server (Series 335 server still supported)
Physical Hardware Configuration Nearly Identical to Protocol Processor
¾ 2 GB RAM, 2 - 3.2 GHz Processors, and Larger 146 GB Hard Drives
Dual NIC’d; However ENET1/eth0 Port Enabled, ENET2/eth1 Port Disabled

Network Management System

Allows Monitoring of Network Connectivity
Maintains Database of Customer Activity
Allows for Report Generation
Generates Network Conditions (Alarms)
Manages Hub & NetModems on Network
Windows Based GUI for Operator Ease
of Access and Control

29
 LAN Switch
Cisco 2950 Series EI 48 port Switch

48 Port Capability

10/100 Mbps, Auto Negotiate Full or Half Duplex

Virtual LANs (VLAN) 802.1Q Capable

Stackable; 19 Inch Rack Mountable

2 Switches Included; 1 for each Subnet (Upstream & Tunnel)

30
 Upstream Router
Typically Provided by Hub/Teleport Facility
Should Be Cisco 2600/2800 Series Compatible Technology
Requires Minimum 1 Physical, 2 Virtual 10/100 Mbps Interface
Ports for iDirect Hub Components (for eth0 & eth1 subnets)
Access Beyond iDirect Hub Requires Additional Interface
2 Physical Interfaces Preferred Whenever Possible
Becomes Hub/Network Gateway for Major Components (Servers,
Chassis, HLC, etc.)

31
 Pre-Loaded NMS/PP Server Software

iDirect - iDS Software Version

Inventory Released Version Pre-Loaded
Ready for iDirect Software Upgrade

Software Upgrades Available via

iDirect Technical Assistance Center
(TAC) Web Page (Controlled Login)

Red Hat Enterprise Linux

(RHEL) Operating System
Time Zone Set for UTC/GMT;
Clocks Synchronized
Ready for iDirect NetModem
Software Load
Configured for Operation Without
Keyboard, Monitor & Mouse

32
 NMS GUI Software Configuration
PC System Requirements
Windows NT, Windows 2000 or XP
Windows 2000 Needs Service Pack 3
Windows 98/95 are Not Supported
NMS Client – Load Software
Unzip the File
Run NMS Clients Setup.exe to Install
NMS Clients (GUI)
¾ Loads Software in Known Location: -
C:\Program Files\iDirect\NMS\Clients
¾ Creates Desktop Icons for Clients
Uncompress EDAS.zip File (Needed for
Chassis Configuration)
¾ Produces Two Files; EDASchk.exe &
MSCOMM32.OCX
¾ Create Shortcut for EDASchk.exe, if
Desired
¾ Copy MSCOMM32.OCX to
C:\WINNT\system32 Folder

33
Remote Site Installation Software

PC System Requirements
Windows NT, Windows 2000 or XP
¾ XP with SP2 requires registry edit for
reliable ‘Auto-Discovery’
¾ Modifies IGMP Version v3 to v2
Windows 2000 Needs SP 3
Windows 98/95 are Not Supported

NMS iSite Client & Remote

Application and Image Files – Load
Software
Unzip Files
iSite is a Subset of NMS Clients for
Remote NetModem Interface
¾ Primarily for Field/Installer Use or
Auxiliary PC/Laptop
Create Shortcut/Desktop Icons for
iSite as Desired

34
 iBuilder Critical Item Entries - Hub
iBuilder Entries Required for Proper Hub Configuration
Detail Needed for NMS Calculated Parameters
Satellite Longitude in Degrees/Minutes/Seconds or Decimal, East/West
Teleport - GEO Location (Latitude/Longitude + Correct Hemisphere)
Transponder - Local Oscillator L/O, or Translation Frequency
Link Budget Detail
¾ Transmit/Receive Frequencies
¾ Information Rate/Allocated Bandwidth
¾ Forward Error Correction Required (FEC);
• Outroute/Outbound/Downstream Carrier (TDM/SCPC) Turbo
Product Code (TPC)
ƒ 0.793 or 0.495 for NMII/II+
TM
ƒ 0.533, 0.431, or 0.879 for iNFINITI HLCs
• Inroute/Inbound/Upstream Carrier (TDMA) Turbo Product
Code (TPC) 0.660 (1k block) or 0.793 (4k block) Only
Up/Down Converter
¾ Local Oscillator (L/O) or Translation Frequency
• If BUC Fixed L/O
• If L-Band to 70/140 MHz, L/O=U/C (D/C) CF – (L-Band CF)
• Is Spectral Inversion Required
• Down Converter Stability
IP Addresses Assigned for Upstream & Tunnel Subnets

35
 iBuilder Critical Item Entries-Remote
iBuilder Entries Required for Proper Remote Configuration (Generic)
Detail Needed (Minimum Required) for
NMS Calculated Parameters
Remote Site Coordinates
¾ GEO Location (Latitude/Longitude +
Hemisphere)
VSAT Components
¾ Block Up Converter (BUC)
• Local Oscillator (L/O) or Translation
Frequency
• BUC Fixed L/O
• Spectral Inversion
• DC Power
• 10 MHz Reference
¾ Low Noise Block (LNB) Down Converter
• Local Oscillator (L/O) or Translation
Frequency
• LNB Fixed L/O
• Spectral Inversion
• DC Power
• 10 MHz Reference
• LNB Stability
¾ IP Addresses Assigned for LAN Interfaces

36
 Tools Required/Recommended
Hand tools
Common Tool Box Items Required
¾ # 2 Phillips Screwdriver
¾ 6 inch Crescent Wrench (or 5/16 Open End)
¾ Coaxial Cable Stripper (Prep Tool – RG6 or RG11)
¾ Coaxial Connector Hex Crimp Tool (RG6 or RG11)
0.384 inch crimp
¾ Anti-Static Wrist Strap

Test Equipment
Spectrum Analyzer, 0-2GHz typical (L-Band)
Specialty Tools
Laptop PC
¾ PCMCIA Compatible NIC to Support 10/100 Base T
¾ Windows 2000 (or XP) Professional
¾ 133MHz or Higher Pentium Compatible CPU
¾ 64 MB RAM (Minimum)
¾ Recommended 2 GB Hard Drive w/650 MB Free

Crossover CAT 5 LAN Cable (LAN Port)

Normal CAT 5 LAN Cable w/DB9 to RJ45
Adapter (Console Port)
37
Introduction to System
Installation
iDS v6.0
*** Thank You ***
38