WKBK Bhi 8xand10x 080109 Rev1

Student Workbook
for iDirect Broadband Hub Installer

Training
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: WKBK_BHI_8xand10x_080109_Rev1.pdf
Document Part Number: GE0000048
ii BHI Course Student Workbook

Revision History
The following table shows all revisions for this document. Refer to this information to verify
that you have the latest version.
Revision Date Released Reason for Change(s) Who Updated?
A August 1, 2009 First release of this document. TJenkins
BHI Course Student Workbook iii

iv
Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Content Summary
Hub Configuration Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
IP Addressing Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Acceptance Test Procedure Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Exercise 1. Configure the NMS Servers

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Exercise 2. Set the Date and Time on the Servers

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Exercise 3. Install the NMS Software License File

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
BHI Course Student Workbook v

Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Exercise 4. Change the Linux Passwords

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Exercise 5. Configure the Protocol Processor Blades

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Exercise 6. Configure the EDAS / Control Module IP Address

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Exercise 7. Install the NMS Client Software

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Exercise 8. Configure the Switch IP Address and EDAS Port

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
vi BHI Course Student Workbook

Configuring the Network in iBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Exercise 9. Configure the IP Address of Each Line Card

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Exercise 10. Commission the Hub Carrier

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Commissioning a Remote in a Star Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuring NMS Redundancy Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Exercise 11. RCM Failover Test

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Exercise 12. Hub Chassis Backplane Test

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
20-Slot Hub Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Slot-group Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4-slot Hub Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
BHI Course Student Workbook vii

Exercise 13. Hub Line Card Failover Test
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Exercise 14. Protocol Processor Blade Failover Test

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Exercise 15. Hub Power Failure Simulation Test

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Exercise 16. Connectivity Test

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Exercise 17. Performance and Throughput Test

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
viii BHI Course Student Workbook

Performance Test Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Test 1: Evolution DVB-S2 Downstream Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Test 2: iNFINITI Downstream Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Test 3: iNFINITI and Evolution DVB-S2 Upstream Performance . . . . . . . . . . . . . . . . . . . . . 67
Test 4: Internet Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Exercise 18. ACM Verification

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Appendix A. Configuration and Commissioning Checklist . . . . . . . . 75
Appendix B. iDX 1.0.x Software Installation Process . . . . . . . . . . . 77

Perform Preinstallation Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Procedure 1 Download the NMS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Install iDX 1.x on Your NMS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Procedure 1 Uninstall Existing NMS Server Software on the Primary NMS Server 78
Procedure 2 Remove any Existing NMS Database . . . . . . . . . . . . . . . . . . . . . . 79
Procedure 3 Install the New NMS Server Software on the Primary NMS Server . . 80
Procedure 4 Install the New NMS Server Software on the Backup NMS Server . . 82
Install iDX 1.x on the Protocol Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Procedure 1 Download the PP Software to the Protocol Processor Blades . . . . . 83
Procedure 2 Install iDX 1.x on the Protocol Processor Blades . . . . . . . . . . . . . 84
Install iDX 1.x Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Procedure 1 Install the NMS Client Software (iBuilder/iMonitor) . . . . . . . . . . . 85
Procedure 2 Configure Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Install iDX 1.x on the Hub Line Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Procedure 1 Download the Cumulative Update . . . . . . . . . . . . . . . . . . . . . . . 86
Procedure 2 Download Software Packages to Line Cards . . . . . . . . . . . . . . . . 89
Procedure 3 Apply the Configuration Options File . . . . . . . . . . . . . . . . . . . . . 90
Install iDX 1.x on the Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Procedure 1 Download the Cumulative Update . . . . . . . . . . . . . . . . . . . . . . . 92
Procedure 2 Download Software Packages to Remotes . . . . . . . . . . . . . . . . . . 94
Procedure 3 Apply the Configuration Options File . . . . . . . . . . . . . . . . . . . . . 96
BHI Course Student Workbook ix

x BHI Course Student Workbook
About This Guide
Purpose
The purpose of this document is to provide students with the instructions for
completing the hands-on exercises required for this course.
Document Conventions
This section illustrates and describes the conventions used throughout the
manual. Take a look now, before you begin using this manual, so that you’ll
know how to interpret the information presented.
Convention Description Example

Blue Used when the user is [SWITCH_PORT_n]
Courier required to enter a vid = vlan_id
Bold command at a command
line prompt or in a console)
Courier Used when showing Output similar to the following sample appears:
font resulting output from a [SECURITY]
command that was entered password =
at a command line or on a
$idi2$/bFMhf$5H8mYAaP1sTZ0m1Ny/dYyLaS40/
console.
admin_password =
$idi2$146rgm$.KtDb4OH5CEBxzH6Ds2xM.ehHCH
os_password =
$1$UTKh0V$cc/UfNThFmBI7sT.zYptQ0
BHI Course Student Workbook xi

Convention Description Example
Bold Used when the user is 1. If you are adding a remote to an inroute group,
Trebuchet required to type right-click the Inroute Group and select Add Remote.
font information or values into a
field within a windows-type
The Remote dialog box has a number of user-
interface software.
selectable tabs across the top. The Information Tab is
visible when the dialog opens.
Used when specifying
names of commands,
menus, folders, tabs,
dialogs, list boxes, and
options.
Blue Used to show all For instructions on adding an iSCPC line card to the
Trebuchet hyperlinked text within a network tree and selecting a Hub RFT for the line card,
italc document. see “Adding an iSCPC Line Card” on page 108.
Bold italic Used to emphasize Note: Several remote model types can be
Trebuchet information for the user, configured as iSCPC remotes.
font such as in notes.
Red italic Used when the user needs

Trebuchet to STRICTLY follow the
font instructions or have WARNING! The following procedure may cause
(or see additional knowledge about a network outage.
table a procedure or action.
below)
Symbol Warning type Definition
CAUTION: When you see this alert

CAUTION symbol and the CAUTION heading,
strictly follow the warning instructions
to avoid personal injury, equipment
damage, or loss of data.
WARNING! Electric shock hazard: When

WARNING you see this symbol and the WARNING
heading, strictly follow the warning
instructions to avoid electric shock
injury.
xii BHI Course Student Workbook

Related Documents
The following iDirect documents are available at http://tac.idirect.net and
may also contain information relevant to this release. Please refer to these
documents as needed.
Note: As you determine which documents may be helpful to you, be sure to
refer to the document that pertains to the iDX/iDS release you are
installing or have installed on your iDirect network.
• iDXiDS Release Notes

• iDX/iDS Software Installation Guide/Network Upgrade Procedure Guide
• iDX/iDS iBuilder User Guide
• iDX/iDS iMonitor User Guide
• iDX/iDS Technical Reference Guide
• iDXiDS Software Installation Checklist/Software Upgrade Survey
• iDX/iDS Satellite Router Installation & Commissioning Guide
• iDX/iDS Link Budget Analysis Guide
• iDX/iDS iDirect Hub Readiness Checklist
• iDX/iDS iDirect Teleport Design Considerations
• iDX/iDS iDirect Hub Installation Guide
• iDX/iDS Remote Installation & Commissioning Guide
• iDX/iDS iDX Satellite Router Installation & Commissioning Guide
• iDX/iDS iDirect Hub Installation As-Built Template
• iDX/iDS iDirect Acceptance Test Plan
Getting Help
The iDirect Technical Assistance Center (TAC) is available to help you
24x7x365. iDS Software user’s guides, installation procedures, an FAQ page,
and other documentation that supports our products are available on the TAC
webpage. Please access our TAC webpage at: http://tac.idirect.net.
If you are unable to find the answers or information that you need, you can
contact the TAC at (703) 648-8151.
BHI Course Student Workbook xiii

xiv BHI Course Student Workbook
Content Summary
Content Summary
This section summarizes all Broadband Hub Installer (BHI) practical exercises
(PEs).
Practical exercises relating to the information presented for each topic will be
conducted as soon as possible and in some cases during the covered subject. If
the practical exercise for a particular topic should be performed later, at a
more appropriate time to support or assist with the explanation or a later
topic, the practical exercise may be inserted where needed.
All practical exercises supporting the lectures and demonstrations must be
completed by the end of the class week in order for the student to
successfully complete the hands-on.
The practical exercises for the topics are documented below. Each practical
exercise is listed with its description. Additionally, the order of practical
exercises is subject to alteration, as stated previously, to accommodate any
last minute changes in presentation of the material. Every attempt will be
made to follow the order of the Practical Exercises as presented in this
document.
Completion of all instructor-provided practical exercises, along with all
required written exercises, is mandatory for successful completion of this
course.
Hub Configuration Exercises

After you have physically installed your equipment, you are ready to configure
the hub equipment for your network environment. Exercises 1 through 10 in
this workbook must be completed in the order shown to correctly configure
your hub equipment. A configuration and commissioning checklist follows the
configuration procedures.
The practical exercises for configuring hub equipment are summarized below:
Title Description
Exercise 1, Configure the NMS Servers This exercise defines the commands you can use to
configure the NMS servers
Exercise 2, Set the Date and Time on the This exercise shows you how to set the date and time
Servers on the NMS servers.
Exercise 3, Install the NMS Software This exercise shows you how to install the required
License File license file.
BHI Course Student Workbook xv

Content Summary
Title Description
Exercise 4, Change the Linux Passwords This exercise shows you how to change the Linux
password on the NMS servers.
Exercise 5, Configure the Protocol This exercise shows you how to configure the Protocol
Processor Blades Processor Blades on your network.
Exercise 6, Configure the EDAS / Control This exercise provides the steps to configure the EDAS
Module IP Address Board or Control Module (CM) IP address.
Exercise 7, Install the NMS Client This procedure shows you how to install the NMS
Software client software on a customer PC. The NMS client
software includes iBuilder, iMonitor, and iSite.
Exercise 8, Configure the Switch IP This exercise shows you how to assign an IP address to
Address and EDAS Port the Cisco switch.
Exercise 9, Configure the IP Address of This exercise shows you how to configure the IP
Each Line Card address of each hub line card.
Exercise 10, Commission the Hub Carrier This exercise shows you how to commission the hub
carrier.
Appendix A, Configuration and Use the Configuration and Commissioning Checklist to
Commissioning Checklist verify that the hub installation is complete.
IP Addressing Scheme
For example purposes, the tables in this section provide a sample network
addressing scheme. Using the sample networking addressing scheme as a
guide, apply the customer-provided IP addressing plan.
The sample network uses the following address ranges:

Upstream Network = 192.168.1.0 / 24 (255.255.255.0), usable IP address space =
192.168.1.1 through 192.168.1.254
Tunnel Network = 192.168.2.0 / 24 (255.255.255.0), usable IP address space =
192.168.2.1 through 192.168.2.254
Apply the network addresses as defined in Table 1 and Table 2.
xvi BHI Course Student Workbook

Content Summary
Table 1. Upstream Network
Device IP Address Switch Port Number

Upstream Router Interface 192.168.1.1 1
Hub EDAS Module 192.168.1.2 2
Primary NMS Server (eth0) 192.168.1.3 3
Secondary NMS Server (eth0) 192.168.1.4 4
PP Blade 1 Server (eth0) 192.168.1.5 5
Co-Located Utility PC (If used) 192.168.1.8 8
iDirect SkyMonitor 1880 Spectrum 192.168.1.9 9
Analyzer (if installed)
Cisco Switch Management (Upstream 192.168.1.200 N/A
LAN)
Table 2. Tunnel Network

Tunnel Router Interface 192.168.2.1 17
Hub Line Card – Slot 1 192.168.2.11 21
BHI Course Student Workbook xvii

Content Summary
Table 2. Tunnel Network (continued)

Cisco Switch Management (Tunnel LAN) 192.168.2.200 N/A
Note: Additional IP addresses and switch ports may be required if installing

XLC line cards.
Acceptance Test Procedure Exercises

Acceptance testing is performed after the installation of the hub equipment is
complete to verify that the installation was performed correctly and to
confirm that the network is operational.
Exercises 11 through 18 contain the Acceptance Test Procedures required to
verify a hub installation.
Title Description
Exercise 11, RCM Failover Test This procedure verifies that the standby Reference
Clock Module (RCM) takes over for the online RCM in
the event of catastrophic failure. The test passes
when the takeover occurs without any downtime on
the network.
Exercise 12, Hub Chassis Backplane Test This test procedure verifies that the hub chassis
backplane is operational.
Exercise 13, Hub Line Card Failover Test This procedure verifies that the redundant Hub Line
Card (HLC) takes over for the primary line card in the
event of catastrophic failure.
Exercise 14, Protocol Processor Blade This procedure verifies that the Protocol Processor
Failover Test Blade 2 takes over for Protocol Processor Blade 1 in
the event of catastrophic failure.
Exercise 15, Hub Power Failure This test simulates a power failure at the hub
Simulation Test equipment and verifies that the system restarts
properly when power restores.
xviii BHI Course Student Workbook

Content Summary
Title Description
Exercise 16, Connectivity Test This procedure verifies that all critical network
components are connected. The test passes if the
results are within the expected range.
Exercise 17, Performance and This procedure measures UDP traffic flow in the
Throughput Test Upstream and Downstream channels and it verifies
that the Internet and customer intranet are
accessible.
Exercise 18, ACM Verification This procedure verifies and demonstrates that
Adaptive Code Modulation (ACM) functions properly
on an Evolution DVB downstream carrier when there is
a change in IF power levels. This test is not required
for iNFINITI networks.
Appendix B, iDX 1.0.x Software Contains the procedures for uninstalling legacy
Installation Process software and installing the 1.0.x iDX software.
BHI Course Student Workbook xix

Content Summary
xx BHI Course Student Workbook

Configure the NMS Servers
Exercise 1. Configure the NMS Servers

Purpose
This exercise defines the commands you can use to configure the NMS servers.
Goal
To successfully configure the NMS servers to allow IP connectivity.
Objective
Follow the steps provided to correctly configure the ifcfg-eth0 and the
network files with the required configuration information.
Steps
Configure the IP address of the eth0 interface of the first NMS server by
performing the following:
1. Logon to the NMS server as root.
The # prompt displays.
2. Enter the password:
iDirect
3. Change directories by entering the following command:

cd /etc/sysconfig/network-scripts
4. Using the vi editor, open the ifcfg-eth0 file for editing by entering the
following command:
vi ifcfg-eth0
5. Change the command lines in the ifcfg-eth0 file as shown in Table 1 (do not
change any other values, and retain all other lines within this file).
BHI Course Student Workbook 1

Note: Command lines are case-sensitive.
Table 1. ifcfg-eth0 File Entries
Command Description
DEVICE eth0
BOOTPROTO none
ONBOOT yes
IPADDR upstream IP address of the NMS Server
NETMASK subnet mask of the NMS Server
GATEWAY IP address of the upstream router
interface
MTU 1500
An example of a correctly configured network-script file for eth0 is shown in

Figure 1.
Figure 1. ifcfg-eth0 Results Display
WARNING! Do not delete any lines from the existing file. Doing so may have an adverse
effect on network performance.
6. Record the hardware address (HWADDR) as displayed in the Network

Scripts ifcfg-eth0 Results Display in Figure 1 on page 2.
2 BHI Course Student Workbook

7. Contact the TAC and request a software license file to be generated.

8. Return to the cd /etc/sysconfig directory by entering the following
command:
cd /etc/sysconfig
9. Using the vi editor, open the network file for editing by entering the
following command:
vi network
The network file displays (Figure 2).
Figure 2. Network File Display
10.Change the command lines in the network-scripts file as shown in Table 2

(do not change any other values, and retain all other lines within this file).
Table 2. Network File Commands
Command Description
NETWORKING yes
HOSTNAME Company_Name_NMS_Primary
GATEWAYDEV eth0
11.To save the file and exit, press Esc and enter:
:wq!

12.Perform Step 6 through Step 11 on each NMS server. Set the value for the
HOSTNAME command line to reflect the name of each component.
13.Change directories by entering the following command:
cd /etc/
14.Using the vi editor, open the hosts file for editing by entering the following
command:
vi hosts
localhost.localdomain localhost displays in the /etc Window.

15.Add the following lines to the hosts file, as applicable to the IP
addressing scheme being implemented. The two lines for 127.0.0.1 must
be present. Enter the following command lines:
127.0.0.1 COMPANY_NMS_PRIMARY localhost.localdomain localhost
192.168.1.3 COMPANY_NMS_PRIMARY
The local host displays (Figure 3).
Figure 3. Etc/Hosts File Display
16.To save the file and exit, press the Esc key and enter:
:wq!
17.Repeat this procedure for each NMS Server.

Set the Date and Time on the Servers
Exercise 2. Set the Date and Time on the

Servers
Purpose
This exercise shows you how to set the date and time on the NMS servers.
Goal
To successfully configure the date and time on the NMS and Protocol Processor
servers.
Objective
Follow the steps provided to correctly input the Linux commands in order to
configure the date and time on the servers.
Steps
1. Display the time zone configuration by entering the following command:
timeconfig
The Configure Time Zones Window displays.

2. Ask the customer what time zone they want to use.
3. Using the Tab key to toggle between elements, select the required time
zone in the pull-down menu.
4. Select OK.
5. Set the date by entering:
date MMDDhhmmyyyy
Where:
MMDDhhmmyyyy = the month, day, hour, minute, and year.
6. Start the hardware clock by entering the following command:
hwclock -w
7. Restart network services by entering:

Set the Date and Time on the Servers
reboot
8. Verify that the server reboots and the time is set correctly.
9. Repeat this procedure for each server.

Install the NMS Software License File
Exercise 3. Install the NMS Software

License File
Purpose
This exercise shows you how to install the required license file.
Goal
To successfully transfer the iDirect-provided license file to the correct
directory location on the NMS server.
Objective
Follow the steps provided to transfer the license file to the correct directory
on the NMS server.
Steps
You are required to load a NMS software license file. The software can not run
if the license file is not present.
1. Contact the iDirect TAC to acquire a software license file. You must
provide the hardware address (HWADDR) that you recorded while
performing Step 6 on page 2.
The TAC will verify which file you are authorized to install. The TAC will
then generate the license file and send it to you via email. Copy the file to
your desktop.
2. Provide the hardware address to the TAC.
The TAC will email the license file to you.
3. Access your email to retrieve the license file.
4. Using WinSCP, copy the license file to the root directory by left-clicking the
file and dragging it from your laptop to the NMS server.
5. Change to the root directory by entering the following command:
cd /root

Install the NMS Software License File
6. Move and rename the license file to the /home/nms/cfg directory by

entering the following command:
mv xxx.lic /home/nms/cfg/nmssvr_e.lic
Where,
xxx.lic = the name of the license file.
7. Repeat this procedure for the Backup NMS server.

Change the Linux Passwords
Exercise 4. Change the Linux Passwords

Purpose
This exercise shows you how to change the Linux password on the servers.
Goal
To successfully change the login password on the NMS and Protocol Processor
servers.
Objective
Follow the steps provided to change the login password information for the
NMS and Protocol Processor servers.
Steps
To change the password, perform the following:
1. Logon to the Primary NMS server as root.
iDirect
Note:You can use P@55w0rd! if iDirect does not work.

3. At the console prompt, enter the command:
passwd
4. Using a combination of letters, numbers, and special characters (for

enhanced security), enter a new password and confirm it is entered as you
intended.
5. Repeat this procedure for the backup NMS server and each Protocol
Processor Blade.

Change the Linux Passwords

Configure the Protocol Processor Blades
Exercise 5. Configure the Protocol

Processor Blades
Purpose
This exercise shows you how to configure the Protocol Processor Blades on
your network.
Goal
To successfully log on to the Protocol Processor Blade servers and reconfigure
the Ethernet interface information.
Objective
Follow the steps provided to reconfigure the Protocol Processor ifcfg-eth0 and
ifcfg-eth1 interfaces with all of the required information.
Steps
To configure the PP Blades, perform the following:
1. Logon to the Protocol Processor Blade as root.
iDirect
3. Change to the directory where the network-scripts file is located by

entering:
cd /etc/sysconfig/network-scripts/
4. Using the vi editor, open the ifcg-eth0 file by entering:

vi ifcfg-eth0

The ifcg-eth0 file displays (Figure 4).
Figure 4. ifcfg-eth0 File Display
5. Change the command lines in the ifcfg-eth0 file as shown in Table 3 (do
not change any other values, and retain all other lines within this file).
Table 3. Protocol Processor ifcfg-eth0 File Entries
Command Description
DEVICE eth0
BOOTPROTO none
ONBOOT yes
IPADDR upstream IP address of the Protocol
Processor Blade
NETMASK subnet mask of the Protocol Processor
Blade
GATEWAY IP address of the upstream router
interface
MTU 1504
6. To save the file and exit, press the Esc key and enter:
:wq!
7. Using the vi editor, open the ifcfg-eth1 file for editing by entering the
following command:

vi ifcfg-eth1
The ifcfg-eth1 file displays (Figure 5).
Figure 5. Network Scripts ifcfg-eth1 File Display
8. Change the command lines in the ifcfg-eth0 file as shown in Table 4 (do
not change any other values, and retain all other lines within this file).
Table 4. Protocol Processor ifcfgeth1 File Entries
Command Description
DEVICE eth1
BOOTPROTO none
ONBOOT yes
IPADDR tunnel IP address of the Protocol
Processor Blade
NETMASK subnet mask of the Protocol Processor
Blade
MTU 1500
9. To save the file and exit, press the Esc key and enter:
:wq!
10.Restart the network services by entering:

service network restart

11.Verify that the network services successfully restart by viewing the

network processes on the Protocol Processor.
12.Return to the sysconfig directory by entering:
cd /etc/sysconfig
13.Enter the command:

vi network
The network file displays (Figure 6).
Figure 6. Network File Display
14.Change the command lines in the network-scripts file as shown in Table 5

(do not change any other values, and retain all other lines within this file).
Table 5. Protocol Processor Host File Commands
Command Description
NETWORKING yes
HOSTNAME Company Name_PP_1_Blade_1
GATEWAYDEV eth0
15.To save the file and exit, press the Esc key and enter:
:wq!

16.Display the time zone configuration by entering the following command:

timeconfig
The Configure Time Zones Window displays.

17.Ask the customer what time zone they want to use.
18.Using the Tab key to toggle between elements, select the required time
zone in the pull-down menu.
19.Select OK.
20.Set the date by entering:
date MMDDhhmmyyyy
Where:
MMDDhhmmyyyy = the month, day, hour, minute, and year.
21.Start the hardware clock by entering the following command:
hwclock -w
22.Restart network services by entering:

reboot
23.Verify that the server reboots and the time is set correctly.
24.Repeat this procedure for each server.


Configure the EDAS / Control Module IP Address
Exercise 6. Configure the EDAS / Control

Module IP Address
Purpose
This exercise provides the steps to configure the EDAS Board or Control
Module (CM) IP address.
Goal
To successfully log onto the EDASmodule and reconfigure the IP address
information.
If you are installing an iDirect Series 15000 Universal 5-IF/20-Slot Hub, you
must configure the IP address for the EDAS card (Figure 7).
Figure 7. iDirect Series 15000 Universal 5-IF/20-Slot Hub EDAS Board

If you are installing an iDirect Series 12000 Universal 4-Slot Hub, you must
configure the IP address for the Control Module (CM) (Figure 8).
Figure 8. iDirect Series 12000 Universal 4-Slot Hub Control Module
If you are installing an iDirect Series 10000 Private or Mini Hub, there is no
EDAS Board or CM to be configured.
This procedure is the same for both the EDAS Board and the CM.
Objective
Follow the steps provided to log onto the EDAS module using the provided
EDAS syscheck 3.0 software and reconfigure the IP address, subnet mask, and
gateway information.
Steps
To assign the IP address, perform the following:
1. If you have not already loaded EDAS SYSCHECK on your laptop, browse to
the Software Releases section of the TAC web page and unzip the NMS
Clients to download and extract the EDAS.zip file.
Two files are created: EDASchk.exe and MSCOMM32.ocx.
2. Copy MSCOMM32.ocx to the c:\WINNT\SYSTEM 32 folder.
3. Connect a null modem, D-B9 female to DB-9 female cable (provided)
between your laptop serial port and the RS-232 port on the EDAS board.
4. Using your laptop, open EDAS SYSCHECK 3.0.
The EDAS SYSCHECK Window displays default settings on first use,
otherwise last entries made are displayed.
5. Select the Configuration Tab.

The EDAS SYSCHECK Window displays (Figure 9).
Figure 9. EDAS SYSCHECK Window
6. In the IP Address field, type the assigned IP address of the EDAS or CM.
7. In the Subnet Mask field, the type the network subnet mask.
8. In the Gateway Address field, type the default gateway address.
WARNING! Do not change or write anything in the Ethernet Address field.
9. Power cycle the hub chassis to re-initialize the EDAS or CM configuration.

10.Using EDAS SYSCHECK 3.0, select the Program Tab.

The and EDAS picture and EDAS SYSCHECK Window displays (Figure 10).
Figure 10. EDAS SYSCHECK Program Tab
11.In the COM Port field, select the serial port to which your laptop is
connected.
12.Click Attach to EDAS.
13.Click Write IP Address.
The Current Configuration details update.
14.Click Write Subnet Mask.
15.Click Write Gateway Address.
WARNING! Do NOT click the Write Ethernet Address field. Doing so renders the EDAS
board unusable. Do not run any tests on the Test Tab. They are not supported.
16.Remove AC power from the hub chassis.

17.Wait 15 seconds, and apply AC power to the hub chassis.

18.If you are configuring more than one hub chassis, repeat Step 4 through
Step 17 for each hub chassis. It is imperative that you do these steps in the
order shown. Failure to do so results in the MAC address of the EDAS board
being overwritten with the MAC address of the first EDAS board, and you
will not be able to access it.


Install the NMS Client Software
Exercise 7. Install the NMS Client

Software
Purpose
This procedure shows you how to install the NMS client software on a
customer PC. The NMS client software includes iBuilder, iMonitor, and iSite.
Goal
To successfully install the NMS client software on your PC.
Objective
Follow the steps provided to install the provided NMS client software onto
your PC. You will need to verify that iBuilder, iMonitor, and iSite work on your
PC.
Steps
WARNING! You are required to load a license file before loading the NMS Client
Software. The client software cannot run if the license file is not present.
Contact the iDirect TAC to acquire a software license file. You will need to
provide the hardware address (HWADDR) that you recorded while performing
Step 6 on page 2.
To install the client software, perform the following:
1. Using a customer provided PC that is connected to the upstream network,
browse to the Software Releases section of the TAC web page and
download the NMS Clients.
The files are saved at c:\Program Files\iDirect\NMS\Clients. NMS icons are
created on the desktop.
2. Unzip the files to extract the NMS Client software (iBuilder, iMonitor, and
iSite).
3. Open iBuilder and login using the following username, password, and IP
address information:

Install the NMS Client Software
Username: admin
Password: admin
Server IP: IP address
Where:
IP address = the NMS Server IP address. If you are using a distributed NMS,
enter the IP address of the server that is running the configuration server
process (nmssvr).
WARNING! iDirect strongly recommends that you change the default passwords before
proceeding.

Configure the Switch IP Address and EDAS Port
Exercise 8. Configure the Switch IP

Address and EDAS Port
Purpose
This exercise shows you how to assign an IP address to the Cisco switch.
Goal
To successfully log onto the iDirect Upstream Switch and reconfigure the port
to which the EDAS module will be connected.
Objective
Follow the steps provided to log onto the Upstream Switch and reconfigure
the port used for EDAS communications for 10Mbps, Half Duplex.
Steps
To assign the IP address, perform the following:
1. Log on to the switch.
2. At the > prompt, enter privileged EXEC mode by entering the following
command:
enable

3. At the # prompt, change to global configuration mode by entering the
following command:
config terminal
The by default, no password is configured. Press the Enter key when

prompted for a password.
4. Enter the following commands in the order shown:
interface vlan 1
ip address ip address subnet mask
Where:

Configure the Switch IP Address and EDAS Port
ip address = the IP address of the switch

subnet mask = the subnet mask of the network
no shutdown
exit
exit
copy running-config startup-config
5. Display the port configurations by entering the following command:

show interface
6. Verify that the switch ports are configured for the default setting of auto-
negotiate and full duplex mode.
7. Verify that the EDAS switch port is configured for the default setting of 10
Mbps and half duplex by entering the following commands for the EDAS
port:
speed 10
duplex half
Note:Perform Step 8 if you are using only one switch. If you are using
more than one switch, skip Step 8 and proceed to Step 9.
8. Connect to each Cisco 48-port switch and configure the Management IP
address using the instructions in the Cisco switch instruction manual.
Switch should be configured with two separate VLANs, based on the IP
addressing which will be implemented.
9. Change the default password to one that the customer wants to use by
entering the following command:
enable password password
Where:
password = the password that the customer wants to use.
Configuring the Network in iBuilder

Before you can continue with the configuration, you must use iBuilder to
configure the network. Refer to the Network Management System User Guide
for detailed instructions.
After the network is configured, proceed to “Exercise 9. Configure the IP
Address of Each Line Card”.

Configure the IP Address of Each Line Card
Exercise 9. Configure the IP Address of

Each Line Card
Purpose
This exercise shows you how to configure the IP address of each hub line card.
Goal
To successfully log onto the iDirect hub line card and change the IP address
information.
Objective
Follow the steps provided to log onto the iDirect hub line card in order to
change the IP address, subnet mask and gateway information.
Steps
To assign the IP addresses, perform the following:
1. Using the Cisco cable and RJ-45 to DB-9 adapter provided with the hub
equipment, connect your laptop serial port to the HLC LAN A port.
2. Using your laptop, open a HyperTerminal session to each HLC and log in as
root.
The connection parameters are 9600 baud, 8 data bits, 1 stop bit, no
parity, and no flow control.
iDirect
4. Enter the following commands to configure the HLC IP address and subnet
mask as a host on the tunnel-side LAN:
ifconfig ixp0 ip address netmask subnet mask
Where:
ip address = the IP address of the E1 interface and
subnet mask = the subnet mask for this network.

Configure the IP Address of Each Line Card
5. Enter the following command to configure the tunnel-side gateway on the

HLC:
route add default gw gateway address
Where:
gateway address = the IP address of the tunnel upstream router.
Note:The gateway address must reflect the IP address of the tunnel side
upstream router.
For example:
ifconfig ixp0 192.168.2.21 netmask 255.255.255.0
route add default gw 192.168.2.1

Commission the Hub Carrier
Exercise 10. Commission the Hub Carrier

Purpose
This exercise shows you how to commission the hub carrier.
Goal
To successfully telnet into the iDitect hub line card and commission and Hub
Carrier.
Objective
Follow the steps provided to telnet into the iDirect hub line card in order to
enter the commands required to commission a hub carrier. You will be
adjusting the hub line cards transmit power as well as bringing up a CW
(carrier wave) and PN (pseudorandom noise carrier).
Steps
To commission the hub carrier, perform the following:
1. Enter the data rate, transmit frequency, and translation frequencies for
the upconverter and satellite transponder in iBuilder according to the
transmission plan.
2. Disconnect the transmit cable on the front of the line card.
3. Establish a telnet session between your laptop and the line card.
4. Using iBuilder, apply the options file and reset the line card.
5. Set transmit power to -35 dBm by entering the following command:
tx power -35
6. Contact the satellite owner/operator and request permission to transmit.

7. When directed by the satellite owner/operator to transmit a pure
continuous wave (CW), reconnect the transmit cable and enter the
following command:
tx cw on

Commission the Hub Carrier
8. Using the tx power command as shown in Step 5, adjust the initial

transmit power as directed by the satellite owner/operator.
9. When directed to transmit a modulated carrier by the satellite controller,
enter the following command:
tx pn on
10.Using the tx power command as shown in Step 5, adjust final transmit

power as directed by the satellite controller.
11.Using iBuilder, enter the downstream carrier transmit power level.
12.Using iBuilder, apply the options file to the line card.
13.Reset the line card.
14.Verify with the satellite provider that the transmit level is nominal.
Commissioning a Remote in a Star Network

If you have not already downloaded the Installation and Commissioning
Guide, browse to the Software Releases section of the TAC web page. Scroll
down to the Reference Documents section for the release that you are
installing. Download the guide by clicking the Installation and Commissioning
Guide link.
Follow the procedures in the guide to commission a remote carrier in a star
network.
Configuring NMS Redundancy Failover

Refer to the NMS Redundancy and Failover Procedures for configuration
instructions. You can download the procedure from the TAC web page located
at http://tac.idirect.net under the Technical Notes section of Network
Operator Documentation.

RCM Failover Test
Exercise 11. RCM Failover Test

Purpose
This procedure verifies that the standby Reference Clock Module (RCM) takes
over for the online RCM in the event of catastrophic failure. The test passes
when the takeover occurs without any downtime on the network.
Goal
To verify that the offline RCM card takes over with no disturbance on the
network.
Objective
To perform all the steps without errors.
Steps
Perform the following:
1. Verify that there is at least one active remote in the network.
2. Using iMonitor, view the frequency offset of the remote.
3. Physically remove the online RCM from the Hub Chassis.
The backup RCM takes over. The STATUS LEDs on the backup RCM are as
follows:
– REF CLK: Off
– FLL: Off
– ON/STBY: Changes from amber to green
– FAIL: Off
4. Using iMonitor, verify that the remote does not drop out of the network
and that the Frequency Offset does not change by more than ±1 kHz.
5. Place the RCM back into the Hub Chassis.
6. Record the test results in Table 6 on page 32.

RCM Failover Test
Results
Table 6. RCM Failover Test Results
Subject Test
Test User Guide Reference Expected Results Pass/Fail
Components
RCM forced Online and Backup NMS iMonitor User’s Guide Backup RCM takes over
failover RCMs without any remote
downtime
Frequency Online and Backup NMS iMonitor User’s Guide Remote Frequency offset
offset RCMs < ±1 kHz

Hub Chassis Backplane Test
Exercise 12. Hub Chassis Backplane Test

Purpose
This test procedure verifies that the hub chassis backplane is operational.
• If you are testing an iDirect Series 15000 Universal Satellite Hub (20-Slot),
perform the 20-Slot Hub Test on page 35.
• If you are testing an iDirect Series 12000 Universal 4-Slot Hub, perform the
4-Slot Hub Test on page 36.
This test is not required for the iDirect Series 10000 Private or Mini Satellite
Hub.
• For a 15000 Series 20-Slot Hub, the test passes when the transmit and
receive levels on each Hub Chassis Slot Group are within ± 0.5 dB of each
other.
• For a 12000 Series 4-Slot Hub using a 1-IFM, the test passes when the
transmit and receive levels between Ports 1, 2, 3, and 4 are within ± 1.0 dB
of each other.
• For a 4-Slot Hub using a 4-IFM, the test passes when the transmit and
receive levels between Port 1 is within 3 dB of Ports 2, 3, and 4.
For reference purposes, a view of the iDirect Series 15000 Universal Satellite
Hub is shown in Figure 11.

Figure 11. iDirect Series 15000 Universal 4-Slot Hub Front Panel
Goal
To successfully verify that the hub chassis backplane is operational by testing
the transmit and recieve power levels in each slot group.
Objective
To perform all the steps without errors.
Steps
For reference purposes, a view of the Hub Chassis rear panel is shown in
Figure 12.

Figure 12. Hub Chassis Rear Panel
20-Slot Hub Test

The Series 15000 Universal Satellite 20-Slot Hub has five slot-timing groups,
which are labeled “A” through “E” on the rear panel. Each slot-timing group
consists of four hub line card slots as follows:
• Slot Group A is includes slots 1-4
• Slot Group B is includes slots 5-8
• Slot Group C is includes slots 9-12
• Slot Group D is includes slots 13-16
• Slot Group E is includes slots 17-20

Slot-group Testing
Referring to Figure 11 and Figure 12, perform the following:
1. Install a Hub Line Card (HLC) in the first slot of Slot Group A.
2. Connect a 2-foot long coax test cable from the TX Out port of the HLC to
corresponding port of the hub chassis TX Patch Panel.
3. Connect a 2-foot long coax test cable from the RX In port of the HLC to the
corresponding port of the hub chassis RX Patch Panel.
4. Connect the teleport transmit IFL to the Hub Chassis “Group A” TX port on
the hub chassis rear panel.
5. Connect the teleport receive IFL to the Hub Chassis “Group A” RX port on
the hub chassis rear panel.
6. Logon to iBuilder.
7. Using iBuilder, apply power to the slot.
8. Using a spectrum analyzer and iBuilder, verify that “Group A” has nearly
equal transmit and receive power levels.
9. Using iBuilder, power down the slot.
10.Move the HLC from the first slot to the last slot in the slot-timing group.
11.Record the test results in Table 7 on page 37.
12.Repeat Step 1 through Step 11 for Slot-Groups B through E. Remember to
move the transmit and receive IFL cables to each corresponding interface
and move the coax test cables to the IF transmit and receive port that
correspond with the first slot in the slot-timing group.
4-slot Hub Test

To test the Series 12000 Universal 4-Slot Hub chassis backplane, while making
sure to terminate unused ports as you step through the tests, perform the
following:
1. Perform the Slot-Group Test.
2. Move the HLC into each slot and repeat the test.

Results
Table 7. Hub Chassis Backplane Test Results
Subject Test
Components
Measure Transmit Hub Chassis “Group A” iDirect iBuilder User Equal transmit and
and Receive Guide receive levels Slot
Levels Group A
Hub Chassis “Group B” iDirect iBuilder User Equal transmit and
Guide receive levels Slot
Group B
Hub Chassis “Group C” iDirect iBuilder User Equal transmit and
Group C
Hub Chassis “Group D” iDirect iBuilder User Equal transmit and
Group D
Hub Chassis “Group E” iDirect iBuilder User Equal transmit and
Group E


Hub Line Card Failover Test
Exercise 13. Hub Line Card Failover Test

Purpose
This procedure verifies that the redundant Hub Line Card (HLC) takes over for
the primary line card in the event of catastrophic failure. The test passes
when the takeover occurs and connectivity to the remote end is restored. The
amount of time it takes a remote to rejoin the network varies, depending on
your network implementation.
Goal
To configure and perform HLC failover.
Objective
To perform all of the steps without errors.
Steps
To test Hub Line Card failover, perform the following:
1. Disconnect the Ethernet cable (RJ-45) from the 10/100 LAN port on the
HLC.
2. Disconnect the transmit IF cable from the Tx Out port on the HLC.
3. Through iMonitor, verify that the redundant HLC takes over and remotes
rejoin the network.
4. Record the results in Table 8 on page 40.
5. Reconnect all cables.
6. Using iBuilder, restore the HLC.

Hub Line Card Failover Test
Results
Table 8. Hub Line Card Failover Test Results
Subject Test
Components
HLC Forced Online and Backup HLCs NMS iMonitor User’s Guide Backup HLC takes over and
Failover remotes rejoin the network

Protocol Processor Blade Failover Test
Exercise 14. Protocol Processor Blade

Failover Test
Purpose
This procedure verifies that the Protocol Processor Blade 2 takes over for
Protocol Processor Blade 1 in the event of catastrophic failure. The test passes
when the takeover occurs and remotes rejoin the network. The amount of
time it takes a remote to rejoin the network varies (can be up to 10 minutes),
depending on your network implementation.
Goal
To configure and perform Protocol Processor blade failover.
Objective
Steps
Note: A brief outage occurs when you perform this procedure.
To test Protocol Processor Blade failover, perform the following:
1. Login to the Primary NMS as follows:
a. At the login prompt, type root and press Enter.
b. At the password prompt, type iDirect and press Enter.
2. Start a continuous ping to one of the remotes on the primary Protocol
Processor Blade.
3. Remove AC power from the primary Protocol Processor Blade.
A brief network outage occurs as the backup Protocol Processor takes over.
4. Observe the ping session. During the network outage, ping results are not
returned. Ping results are returned when the backup Protocol Processor
Blade has taken over and the network recovers from the outage. A sample
ping session during this sequence of events is shown in Figure 13.

Figure 13. Sample Protocol Processor Ping Test
5. Apply AC power to the primary Protocol Processor Blade.

6. Record the test results in Table 9 on page 43.
After the failover test is complete, you must balance the Protocol
Processor Blades. To do this, perform the following:
7. Logon to iMonitor by using the following user name and password:
user name: admin
password: admin
8. Right-click on the Protocol Processor Controller, then select Telnet.
The Telnet window displays.
9. Login as follows:
a. At the login prompt, type root and press Enter.
b. At the password prompt, type iDirect and press Enter.
10.Enter the following command: blades rebalance.

Within a few minutes, the Protocol Processor Blades rebalance and the
remotes join the network.
11.Enter exit to close the Telnet session.
Note: For detailed information about Protocol Processor redundancy and load
balancing, refer to the latest iDS Release Features document accessible
on the TAC web page.
Results
Table 9. Protocol Processor Failover Test Results
Subject Test User Guide

Test Expected Results Pass/Fail
Components Reference
Protocol Processor Primary and Backup iMonitor User Guide Backup Protocol Processor
Blade forced Protocol Processor Blade(s) iBuilder User takes over and remotes
failover Guide rejoin the network within
seven minutes.


Hub Power Failure Simulation Test
Exercise 15. Hub Power Failure

Simulation Test
Purpose
This test simulates a power failure at the hub equipment and verifies that the
system restarts properly when power restores.
Goal
To verify system restart when a power failure occurs.
Objective
Steps
1. Logon to the Primary NMS as root.
2. Stop all running processes by entering: service idirect_nms stop as
shown in Figure 14.

Figure 14. Stopping NMS Services
3. Shut down the NMS by entering: shutdown –h 0.

4. Repeat for the Backup NMS.
5. Logon to Protocol Processor Blade 1 as root.
6. Stop all running processes by entering: service idirect_hpb stop as
shown in Figure 15.

Figure 15. Stopping Protocol Processor Services
7. Shut down the Protocol Processor blade by entering: shutdown –h 0.

8. Repeat for all other Protocol Processor Blades.
9. Remove AC power from the Hub Chassis, NMS servers, Protocol Processor
Blades, and switches.
10.After 60 seconds, apply power to each hub component.
11.Logon to the Primary NMS as root.
12.Verify that services are running by entering: service idirect_nms
status as shown in Figure 16.

Figure 16. NMS Services Status
13.Logon to the Backup NMS as root.

14.Verify that services are not running by entering: service idirect_nms
status.
15.Logon to the Protocol Processor Blade 1 as root.
16.Verify that services are running by entering: service idirect_hpb
status as shown in Figure 17.

Figure 17. Protocol Processor Services Status
17.Logon to the Protocol Processor Blade 2 as root.

18.Verify that services are running by entering: service idirect_hpb
status.
19.Login to iMonitor.
20.Verify that the network recovers by observing remotes are in the network
and are operating. Enter your results in Table 10 on page 50.

Results
Table 10. Hub Power Failure Simulation Testing
Subject Test
Components
Simulated Hub Chassis iMonitor User Guide Hub Chassis recovers after
Power simulated power outage.
Failure

Connectivity Test
Exercise 16. Connectivity Test

Purpose
This procedure verifies that all critical network components are connected.
The test passes if the results are within the expected range.
Goal
To verify and troubleshoot that connectivity is within the expected range.
Objective
Steps
To complete this test, perform the following:
1. On your laptop or PC, click the start button and select Run.
2. Type cmd in the Open field and click OK.
A command line prompt displays.
3. Type: ping n.n.n.n
Where n.n.n.n = the IP address of the target device.
A sample is shown in Figure 18.

Connectivity Test
Figure 18. Sample Connectivity Ping Test with Results
Four lines display the IP address from which you are pinging, the number of
bytes, and the response time (in ms) that it took the ping to return.
Below these four lines are ping statistics for the IP address you pinged, the
number of packets sent (which is typically four), and the number received.
Ping the Upstream router, Internet/Intranet, and NMS.
4. Logon to the NMS as root.
5. Enter the following command: ping n.n.n.n
Where n.n.n.n = the IP address of the target device.
Ping the Upstream Router, Tunnel Switch, HLC, and EDAS Board.
6. Record the ping results in the Measured Results column in Table 11 on
page 53.

Connectivity Test
Results
Table 11. Connectivity Statistics
Expected Measured
Server Command Connection Points Pass/Fail
Results Results
1. ping Remote PC J Upstream Router 600-1500 ms
2. ping Remote PC J Internet/Intranet 600-1500 ms
3. ping Remote PC J NMS Server 600-1500 ms
4. ping NMS server J Upstream Router < 10 ms
5. ping NMS server J Tunnel Switch < 10 ms
6. ping NMS Server J HLC < 10 ms
7. ping NMS Server J EDAS Board < 10 ms

Connectivity Test

Performance and Throughput Test
Exercise 17. Performance and

Throughput Test
Purpose
This procedure measures UDP traffic flow in the Upstream and Downstream
channels and it verifies that the Internet and customer intranet are
accessible. Perform each test on one remote only, and verify that no other
remotes are in use during the test. Best results are achieved when the tests
are performed under clear sky conditions at the hub and at the remote. The
test passes when the measured results meet or exceed the expected results.
The minimum expected results are based on a configuration that does not use
encryption or VLANs. A packet size of 1500 bytes is assumed.
The performance test procedures that follow require you to change upstream
and downstream carrier parameters. Be sure to coordinate with the satellite
operator/owner when making changes.
Goal
To verify that throughput is equal to or above the acceptance value.
Objective
Steps
Performance Test Procedures
This section outlines four tests that you perform to test network measurement
and performance. iPerf and a web browser are required to perform these
tests.
The four tests to perform that test your network for measurement and
performance include:
• Test 1: Evolution DVB-S2 Downstream Performance

• Test 2: iNFINITI Downstream Performance

• Test 3: iNFINITI and Evolution DVB-S2 Upstream Performance
• Test 4: Internet Connectivity
The procedures that follow use a number of iPerf commands. Table 12
provides the command options and syntax with a description of each variable.
Note: All commands used in these test procedure are case sensitive.
Table 12. iperf Commands
Command Line Option Description
Client and Server Options

-f, --format [bkmaBKMA]. A letter specifying the format to print bandwidth numbers.
Supported formats are:
'b' = bits/sec 'B' = Bytes/sec
'k' = Kbits/sec 'K' = KBytes/sec
'm' = Mbits/sec 'M' = MBytes/sec
'g' = Gbits/sec 'G' = GBytes/sec
'a' = adaptive bits/sec 'A' = adaptive Bytes/sec
The adaptive formats choose between kilo and mega. Fields other
than bandwidth always print bytes, but otherwise follow the
requested format
NOTE: Kilo = 1024, Mega = 1024^2 and Giga = 1024^3 when referring
to bytes. Commonly in networking, Kilo = 1000, Mega = 1000^2, and
Giga = 1000^3 so we use this when referring to bits.
-i, --interval # Sets the interval time in seconds between periodic bandwidth,
jitter, and loss reports. If non-zero, a report is made every interval
seconds of the bandwidth since the last report. If zero, no periodic
reports are printed. Default is zero.
-l, --len #[KM] The length of buffers to read or write. Iperf works by writing an
array of len bytes a number of times. Default is 8 KB for TCP, 1470
bytes for UDP. Note for UDP, this is the datagram size and needs to
be lowered when using IPv6 addressing to 1450 or less to avoid
fragmentation. See also the -n and -t options.
-m, --print_mss Print the reported TCP MSS size (via the TCP_MAXSEG option) and
the observed read sizes which often correlate with the MSS. The
MSS is usually the MTU - 40 bytes for the TCP/IP header. Often a
slightly smaller MSS is reported because of extra header space from
IP options. The interface type corresponding to the MTU is also
printed (Ethernet or FDDI, for example). This option is not
implemented on many operating systems, but the read sizes may
still indicate the MSS.

Table 12. iperf Commands (continued)

-p, --port # The server port for the server to listen on and the client to connect
to. This should be the same in both client and server. Default is
5001, the same as TCP.
-u, --udp Use UDP rather than TCP. See also the -b option.
-w, --window #[KM] Sets the socket buffer sizes to the specified value. For TCP, this sets
the TCP window size. For UDP it is the buffer size in which
datagrams are received, and so limits the largest receivable
datagram size.
-B, --bind host Bind to host, one of this machine's addresses. For the client this
sets the outbound interface. For a server this sets the incoming
interface. This is only useful on multi-homed hosts, which have
multiple network interfaces.
For Iperf in UDP server mode, this is also used to bind and join to a
multicast group. Use addresses in the range 224.0.0.0 to
239.255.255.255 for multicast. See also the -T option.
-C, --compatibility Compatibility mode allows for use with older version of iperf. This
mode is not required for interoperability but it is highly
recommended. In some cases when using representative streaming
you could cause a server to crash or cause undesired connection
attempts.
-M, --mss #[KM} Attempt to set the TCP maximum segment size (MSS) via the
TCP_MAXSEG option. The MSS is usually the MTU - 40 bytes for the
TCP/IP header. For Ethernet, the MSS is 1460 bytes (1500 byte
MTU). This option is not implemented on many operating systems.
-N, --nodelay Set the TCP no delay option, disabling Nagle's algorithm. Normally
this is only disabled for interactive applications like telnet.
-V (from v1.6 or higher) Bind to an IPv6 address
Server side: $ iperf -s -V
Client side: $ iperf -c <Server IPv6 Address> -V
Note: On version 1.6.3 and later a specific IPv6 Address does not
need to be bound with the -B option, previous 1.6 versions do. Also
on most operating systems using this option will also respond to
IPv4 clients using IPv4 mapped addresses.
Server Specific Options

-s, --server Run Iperf in server mode
-D (from v1.2 or higher) Run the server as a daemon (Unix platforms)
On Win32 platforms where services are available, Iperf will start
running as a service.
-R (only for Windows, from Remove the Iperf service (if the service is running).
v1.2 or higher)
-o (only for Windows, from Redirect output to given file.
v1.2 or higher)


-c, --client host f Iperf is in server mode, then specifying a host with -c limits the
connections that Iperf accepts to the host specified. Does not work
well for UDP.
-P, --parallel # The number of connections to handle by the server before closing.
Default is 0 (which means to accept connections forever).
Client Specific Options

-b, --bandwidth #[KM] The UDP bandwidth to send in bits/sec. This implies the -u option.
Default is 1 Mbit/sec.
-c, --client host Run Iperf in client mode, connecting to an Iperf server running on
host.
-d, --dualtest Runs Iperf in dual testing mode. This will cause the server to
connect back to the client on the port specified in the -L option (or
defaults to the port the client connected to the server on). This is
done immediately therefore running the tests simultaneously. If you
want an alternating test use -r.
-n, --num #[KM] The number of buffers to transmit. Normally, Iperf sends for 10
seconds. The -n option overrides this and sends an array of len
bytes num times, no matter how long that takes. See also the -l and
-t options.
-r, --tradeoff Run Iperf in tradeoff testing mode. This will cause the server to
connect back to the client on the port specified in the -L option (or
defaults to the port the client connected to the server on). This is
done following the client connection termination, therefore
running the tests alternating. If you want an simultaneous test use -
d.
-t, --time # The duration of time in seconds to transmit. Iperf normally works
by repeatedly sending an array of len bytes for time seconds.
Default is 10 seconds. See also the -l and -n options.
-L, --listenport # This specifies the port that the server will connect back to the
client on. It defaults to the port used to connect to the server from
the client.
-P, --parallel # The number of simultaneous connections to make to the server.
Default is 1. Requires thread support on both the client and server.
-S, --tos # The Type of Service for outgoing packets. (Many routers ignore the
TOS field.) You may specify the value in hex with a '0x' prefix, in
octal with a '0' prefix, or in decimal. For example, '0x10' hex = '020'
octal = '16' decimal. The TOS numbers specified in RFC 1349 are:
IPTOS_LOWDELAY minimize delay 0x10
IPTOS_THROUGHPUT maximize throughput 0x08
IPTOS_RELIABILITY maximize reliability 0x04
IPTOS_LOWCOST minimize cost 0x02


-T, --ttl # The Time-To-Live for outgoing multicast packets. This is essentially
the number of router hops to go through, and is also used for
scoping. Default is 1, link-local.
-F (from v1.2 or higher) Use a representative stream to measure bandwidth, e.g. :-
$ iperf -c <server address> -F <file-name>
-I (from v1.2 or higher) Same as -F, input from stdin.
Miscellaneous Options
-h, --help Print out a summary of commands and quit.
-v, --version Print version information and quit. Prints 'pthreads' if compiled with
POSIX threads, 'win32 threads' if compiled with Microsoft Win32
threads, or 'single threaded' if compiled without threads.
-v, --version Print version information and quit. Prints 'pthreads' if compiled with
POSIX threads, 'win32 threads' if compiled with Microsoft Win32
threads, or 'single threaded' if compiled without threads.
Test 1: Evolution DVB-S2 Downstream Performance

This test measures throughput performance on Evolution DVB-S2 Downstream
carriers. You are required to calculate the expected Information Rate for this
test. You must refer to the Link Budget Analysis Guide when performing the
calculation.
To calculate the expected Information Rate, perform the following:
1. Using iBuilder, configure the downstream carrier for 10 Msps symbol rate,
ACM modulation, and 16APSK-8/9 for the Maximum MODCOD and Multicast
MODCOD (refer to the section on Adding Downstream Carriers of the
iBuilder User Guide for configuration instructions).
2. Using iMonitor, right click on the remote in the iMonitor Tree View and
select DVB-S2 Stats then SNR Graph, as shown in Figure 19.

Figure 19. Selecting the SNR Graph
3. In the SNR Graph window, select the List Data Tab as shown in Figure 20.

Figure 20. SNR List Data Tab
4. Referring to the Downstream Spectral Efficiency and Modem Performance

Limit table in the Link Budget Analysis Guide, find the MODCOD value in
the Payload Type column that you recorded in Step 4.
5. Record the MODCOD value for two indexes below the current MODCOD in
use.
For example, if the current MODCOD in use is Index 20, record the MODCOD
for Index 18.
6. Using iBuilder, reconfigure the carrier Modulation, Minimum MODCOD,
Maximum MODCOD, and Multicast MODCOD for the MODCOD value that you
recorded in Step 5.
This “locks” the MODCOD to a defined value and ensures that Adaptive
Code Modulation (ACM) does not change the MODCOD during the
throughput test.

7. Using the Spectral Efficiency (bps/Hz) column of the Downstream Spectral

Efficiency and Modem Performance Limit table in the Link Budget Analysis
Guide, record the Spectral Efficiency value for the MODCOD that you
identified in Step 5.
8. Perform the following calculation to determine the Expected Information
Rate as follows:
Expectied Info Rate = Symbol Rate x 1.2 x Spectral Efficiency
For example, 10 Msps (Symbol Rate from Step 1), multiplied by 1.2
(minimum carrier spacing), multiplied by 2.08 (Spectral Efficiency from
Step 8), equals an Expected Information Rate of 24.96 Mbps. This is the
maximum throughput that can be achieved for this carrier and MODCOD.
9. Record the Expected Information Rate in Table 13 on page 72.
Now that you have established the expected symbol rate, you are ready to
test downstream performance. Perform the following:
1. Prepare a laptop or PC to connect to the remote by changing its IP address
to an address that is on the same subnet as the remote. Set the default
gateway on the laptop or PC to the IP address of the remote.
2. Connect the laptop or PC to LAN B on the remote.
3. Enter the following command:
iperf –s –u
4. Open Putty and establish a SSH connection to the NMS Server.
6. In the NMS server Putty command window, enter the following command:
iperf –c <ipaddress> -u –b B –t 60 –i 1
Where:
ipaddress = IP address of the PC or laptop
B = bandwidth K/M (for example, enter 5M for 5 Mbps or 256K for 256
Kbps)
Enter a bandwidth value that is higher than the carrier information rate
(for example, if the carrier is configured for 128 Kbps, use 256K as the
bandwidth value).
Verify that iPerf traffic is flowing as shown in the example in Figure 21.

Figure 21. Observing iPerf Traffic Flow
7. Using iMonitor, select the remote in the network tree and click the SAT
Traffic tab. Display the UDP traffic graph by performing the following:
a. Click the IP Traffic tab.
b. Right-click the grey area under the Restart button.
A list of options displays.
c. Select Show Legend.
The traffic legend displays at the bottom of the Downstream and Upstream
panels.
A sample throughput graph is shown in Figure 22.

Figure 22. Sample Throughout Graph
8. Record the measured information rate and throughout percentage in Table

13 on page 72.
Test 2: iNFINITI Downstream Performance

This test measures throughput performance on an iNFINITI Downstream
carrier. To test downstream performance, perform the following:
1. Using iBuilder, configure the downstream carrier for 256 Kbps and QPSK
.793 FEC (refer to the section on Adding Upstream TDMA Carriers of the
iBuilder User Guide for configuration instructions).

4. Using the laptop or PC connected to the remote, enter the following

command:
iperf –s -u
iperf –c ipaddress -u –b B –t 60 –i 10
Where:
ipaddress = IP address of the laptop or PC
B = bandwidth K/M (for example, enter 5M for 5Mbps or 256K for 256Kbps)
Enter a bandwidth value that is higher than the carrier information rate
bandwidth value).
Verify that iPerf traffic is flowing as shown in the example in Figure 23 on
page 66.
8. Repeat Steps 1 through 9 of this procedure for each of the following
downstream carrier configurations:
– 512 Kbps – 15 Mbps, QPSK .793 FEC
– Greater than 15 Mbps, QPSK .793 FEC

9. Using iMonitor, select the remote in the network tree and click the SAT
Traffic tab. Display the UDP traffic graph by performing the following:
panels.
A sample throughput graph is shown in Figure 24.

Figure 24. Sample Throughput Graph
10.Record the configured information rate, measured information rate, and

throughput percentage in Table 13 on page 72.
Test 3: iNFINITI and Evolution DVB-S2 Upstream Performance

This test measures throughput performance on the iNFINITI and Evolution
DVB-S2 Upstream carriers. To test upstream performance, perform the
following:
1. Using iBuilder, configure the upstream carrier for 128 kbps and QPSK .66
FEC (refer to the section on Adding Upstream TDMA Carriers of the iBuilder
User Guide for configuration instructions).
iperf –s –u


7. On the laptop or PC connected to the remote, enter the following
command:
iperf –c <ipaddress> -u –b B –t 60 –i 1
Where:
ipaddress = IP address of the NMS server
B = bandwidth K/M (for example, enter 5M for 5Mbps or 256K for 256Kbps)
Enter a bandwidth values that is higher than the carrier information rate
bandwidth value).
Verify that iPerf traffic is flowing as shown in the example in Figure 25.

8. Using iMonitor, select the remote in the network tree and click the IP
Traffic tab. Verify that the UDP traffic graph displays by performing the
following:
panels.
A sample throughput graph is shown in Figure 26 on page 70.
9. Repeat Steps 1 through 9 of this procedure for each of the following
upstream carrier configurations:
– 256 to 1.4 Mbps, QPSK .66 FEC
– 256 to 4.5 Kbps, QPSK .793 FEC

Figure 26. Sample Throughput Graph
10.Record the configured information rate, measured information rate, and

throughout percentage in Table 13 on page 72.
11.Repeat Step1 through Step 9 of this procedure for each of the following
upstream carrier configurations:
• 512 Kbps, QPSK .66 FEC
• 512 Kbps, QPSK .793 FEC
This completes iNFINITI and Evolution DVB-S2 Upstream Performance.
Test 4: Internet Connectivity

To test internet connectivity, use an Internet browser to reach well-known
web sites and load files or HTML pages. These sites may be very busy, which
can highly affect the results of the performance test. Perform the following:
1. Log on to the NMS server as root.

2. Configure the NMS server as a web server by entering the following

command:
service httpd start
3. Browse to the NMS server and download files of different sizes (from 1 KB
to 500 MB) simultaneously.
4. Record the results in Table 13 on page 72.

Results
Table 13. Throughput and Performance Tests Results
Tool/Software Minimum Expected Results for

Test Measured Results Pass/Fail
Package Configured Information Rate
TEST 1 iPerf installed on a 3 Mbps and Greater 90% Expected Information Rate:
Evolution client PC and the ___________Msps
DVB-S2 Hub server Measured Information
Downstream Rate: ___________Mbps
Throughput: ______ %
TEST 2 Client PC running Less than 512 Kbps May be Configured Information Rate:
iNFINITI iPerf installed and (QPSK .793 FEC) affected by ___________Kbps
SCPC the Hub server network Measured Information
Downstream traffic Rate: ___________Kbps
overhead
512 Kbps – 15 Mbps 90% Configured Information Rate:
(QPSK .793 FEC) ___________Kbps
Measured Information
Rate: ___________Kbps
Greater than 15 Mbps Limited by Configured Information Rate:
(QPSK .793 FEC) iDirect ___________Kbps
Remote Measured Information
capability Rate: ___________Kbps
TEST 3 iPerf installed on a Less than 256 Kbps May be Configured Information Rate:
iNFINITI client PC and the (QPSK .66 FEC) affected by ___________Kbps
Upstream Hub server network Measured Information
traffic Rate: ___________Kbps
overhead
256 Kbps to 1.4 Mbps 70% Configured Information Rate:
(QPSK .66 FEC) ___________Kbps
Rate: ___________Kbps
256 Kbps to 4.5 Mbps 70% Configured Information Rate:
(QPSK .793 FEC) ___________Kbps
Rate: ___________Kbps
TEST 4 Internet Explorer Web pages load successfully.
Internet running on a client
Browsing PC and the NMS
web server

ACM Verification
Exercise 18. ACM Verification

Purpose
This procedure verifies and demonstrates that Adaptive Code Modulation
(ACM) functions properly on an Evolution DVB downstream carrier when there
is a change in IF power levels. This test is not required for iNFINITI networks.
Goal
To verify ACM function in the network.
Objective
Steps
To verify correct operation, perform the following:
1. Using iMonitor, record the current MODCOD value.
2. Using iBuilder, reduce the hub transmit power by 3 dB.
3. Using iMonitor, verify that the MODCOD value changes.
4. Using iBuilder, reduce the hub transmit power by 3 dB again.
5. Using iMonitor, verify that the MODCOD value changes.
6. Using iBuilder, return the hub transmit power to the original value by
increasing power by 6 dB.
7. Verify that the MODCOD changes to the original value recorded in Step 1.
This completes ACM verification. Record the test results in Table 14 on
page 74.

ACM Verification
Results
Table 14. ACM Verification
Subject Test User Guide

Test Expected Results Pass/Fail
Components Reference
ACM Hub Chassis and iMonitor User’s Guide ACM changes power levels
Demonstration Remote iBuilder User Guide during simulated fade.

Appendix A. Configuration
and Commissioning
Checklist
Complete the Equipment Configuration and Commissioning Checklist to verify that the physical
installation is complete. Check off each item in Table 15.
Table 15. Equipment Configuration and Commissioning Checklist
Item to Verify Yes No N/A

1. Install license file on NMS servers.
2. Assign IP address to the EDAS (M&C) board in hub chassis.
(null modem cable required).
3. Assign IP address to each line card provided.
4. Edit IP address, gateway and host name of primary NMS
(Eth0).
5. Edit IP address, gateway and host name of NMS Backup
(Eth0).
6. Edit IP address, gateway and host name of PP Blades
(Eth0 and Eth1); also verify MTU=1504 for Eth0
configuration.
7. Verify that SETUP for all Linux servers has proper
SERVICES on BOOT.
8. Program proper daily backup configuration between the
primary and backup NMS servers.
9. Has the on-site staff configured primary and secondary IP
addresses on router for Upstream and Tunnel?
10. Restart all equipment (following proper procedures).

Table 15. Equipment Configuration and Commissioning Checklist (continued)
Item to Verify Yes No N/A

11. Can the NMS Primary PING all of the IP addresses on both
Upstream and Tunnel networks? If not, debug until yes.
12. Configure Network (in NMS) via iBuilder (refer to NMS
configuration procedure).
13. Write configurations to Protocol Processor and hub line
cards (using iBuilder).
14. Upgrade all hub line cards to current release.
15. Load options file to hub line cards.
16. Set date and time on PP and NMS to the time zone that
the customer requires.
17. Check hub line card receive composite power.
18. Commission carrier with satellite provider (refer to the
Remote Commissioning Guide).
19. Set power level for downstream carrier (using iBuilder).
20. Commission VSAT.
21. Configure IP address, user name, and password for the
switch.
22. Perform Acceptance Test Procedure
23. System passed ATP (debug until yes)
24. Complete all entries in As-Built template.
25. Test remote access for TAC Support with the iDirect TAC.
26. Hand off to customer and iDirect TAC.
27. Return the ATP signature form and Hub Familiarization
Training Signature Form to iDirect as soon as possible.
28. Return the As-Built with required photographs to iDirect
within 5 days of leaving the site. Please refer to the Hub
Installation “As-Built” guide for a list of required
photographs.

Perform Preinstallation Activities
Appendix B. iDX 1.0.x

Software Installation
Process
Perform Preinstallation Activities

Before you begin these procedures, download and review the relevant Release Notes. In the
Release Notes, note any special installation instructions that need to be performed before
and during the installation process. The required procedure is:
• Procedure 1, Download the NMS Software
WARNING: If you encounter any problems during the procedure, do

not continue the installation. Contact iDirect’s Technical
Assistance Center (TAC) at (703) 648-8151 immediately for
assistance.
Procedure 1. Download the NMS Software

Before starting the installation process, you need to download the NMS software from the TAC
web page.
1. Create a temporary folder on each computer’s Desktop on which you want to install the
client software.
2. Using your iDirect login name and password, log on to the iDirect Technical Assistance
Center web site, located at: http://tac.idirect.net/.
3. Click Software Releases.
4. Scroll down to the release you are installing (either iDX 1.0.x or iDX 1.1).
5. Click the links to download each of the required files. These include:
• NMS clients for iDX 1.x

Install iDX 1.x on Your NMS Servers
• Protocol Processor for iDX 1.x

• NMS Servers for iDX 1.x
• Patches may also be part of the version to which you are upgrading. Ensure that you
also download any related patch software for that version. This is typically shown as a
link under the section for that software release. Keep in mind that patches include
files that are in addition to the standard files required for download, and may not
contain full software.

To install iDX 1.x on your NMS servers, the following procedures are required:
• Procedure 2, Uninstall Existing NMS Server Software on the Primary NMS Server
• Procedure 3, Remove any Existing NMS Database
• Procedure 4, Install the New NMS Server Software on the Primary NMS Server
• Procedure 5, Install the New NMS Server Software on the Backup NMS Server
Procedure 2. Uninstall Existing NMS Server Software on the

Primary NMS Server
iDirect-supplied IBM eServers are typically shipped with a pre-installed version of iDS 7.x. The
iDX 1.x systems will be completely new networks eliminating the need for an upgrade.
Therefore, it is critical to remove the pre-installed version of iDirect software.
1. Open the temporary folder that you created on the desktop of your PC in Download the
NMS Software on page 5 and locate the NMS Server software file nms_servers-9_x.tar.gz
Note: The actual release number varies. Substitute the actual release number
for “9-x.”
2. Open a WinSCP session between your PC/Laptop and the Primary NMS Server and transfer
the file nms_servers-9_x.tar.gz to the /root directory of the Primary NMS Server.
3. Open a PuTTY session and log on to the Primary NMS Server.
4. On the Primary NMS Server, verify that you are in the /root directory by typing pwd at the
command prompt. If /root is displayed at the prompt, then you are in the correct place.
5. Enter the following command at the shell prompt:
tar -zxvf nms_servers-9_x.tar.gz
This command creates a subdirectory named NetModem-9x/install in the /root directory,
placing the decompressed output of the tar file into that subdirectory.
You are now ready to uninstall the current NMS Server software and install the new NMS
Server software.
Before carrying out the uninstall of the previous version of the NMS Server software, you
must determine the version of NMS software installed on your server.

6. On the Primary NMS server, determine the version of NetModem software that was pre-
installed by entering the following command:
rpm –q nms_servers
The following sample output displays:
nms_servers-7_0_0-1
The version is the three numbers connected by underscores.
7. From the /root directory, go to the current version of NMS Software directory by entering
the following command:
cd NetModem-<current version>/install
8. Uninstall the current NMS Server software by entering the following command:
./install_nms_servers.sh –u
Procedure 3. Remove any Existing NMS Database

iDirect-supplied IBM eServers are typically shipped with a pre-installed version of iDS 7.x. The
iDX 1.x systems will be completely new networks eliminating the need for an upgrade.
Therefore, it is critical to remove any database that might have been created with the pre-
installed version of iDirect software.
1. Log on to the Primary (On-line) NMS server using SSH (PuTTY).
2. Stop the NMS server process by entering:
service idirect_nms stop
3. Change to the MySQL directory by entering:
cd /var/lib/mysql/
4. Check the existing directories by entering:
ls -al
total 20604
drwxr-xr-x 6 mysql root 4096 Jun 3 16:37 .
drwxr-xr-x 29 root root 4096 Jun 8 2007 ..
-rw-rw---- 1 mysql mysql 25088 Jun 8 2007
ib_arch_log_0000000000
-rw-rw---- 1 mysql mysql 10485760 Jun 1 04:20 ibdata1
-rw-rw---- 1 mysql mysql 5242880 Jun 2 01:50 ib_logfile0
-rw-rw---- 1 mysql mysql 5242880 Jun 8 2007 ib_logfile1
drwx--x--x 2 mysql root 4096 Jun 8 2007 mysql
srwxrwxrwx 1 mysql mysql 0 Jun 2 01:50 mysql.sock
drwx------ 2 mysql mysql 8192 Jun 3 16:38 nms
-rw-rw---- 1 mysql mysql 4 Jun 2 01:50 NMS1.pid
-rw-rw---- 1 mysql mysql 4 Dec 5 2007 NMS1.pid
drwx------ 2 mysql mysql 24576 Jun 5 00:00 nrd_archive

drwxr-xr-x 2 mysql root 4096 Jun 8 2007 test

5. Remove the NMS directory by entering:
rm -rf nms
6. Remove the nrd_archive database by entering:
rm -rf nrd_archive
7. Flush the databases by entering:
mysqladmin flush-tables
8. Confirm the NMS and nrd_archive databases have been deleted by entering:
ls -al
drwxr-xr-x 6 mysql root 4096 Jun 3 16:37

drwxr-xr-x 29 root root 4096 Jun 8 2007
-rw-rw---- 1 mysql mysql 25088 Jun 8 2007
ib_arch_log_0000000000
-rw-rw---- 1 mysql mysql 10485760 Jun 1 04:20 ibdata1
-rw-rw---- 1 mysql mysql 5242880 Jun 2 01:50 ib_logfile0
-rw-rw---- 1 mysql mysql 5242880 Jun 8 2007 ib_logfile1
drwx--x--x 2 mysql root 4096 Jun 8 2007 mysql
srwxrwxrwx 1 mysql mysql 0 Jun 2 01:50 mysql.sock
-rw-rw---- 1 mysql mysql 4 Jun 2 01:50 NMS1.pid
-rw-rw---- 1 mysql mysql 4 Dec 5 2007 NMS1.pid
drwxr-xr-x 2 mysql root 4096 Jun 8 2007 test
Notice that the nrd_archive is deleted.
9. Go to /etc/idirect and remove the old PP controllers by entering:
rm -rf pp*
10. Go to the /home directory and delete the NMS directory by entering:
rm -rf nms
Procedure 4. Install the New NMS Server Software on the

Primary NMS Server
This procedure explains how to install the NMS server software on the NMS server.
1. From the /root directory of the NMS Server, go to the directory containing the latest
version of NMS software by entering the following commands:
cd
cd NetModem-9_x/install
2. Install the latest version of NMS Server software on your NMS Server by entering the
following command:
./install_nms_servers.sh

The script prompts you to specify which type of NMS Server you are setting up, Backup or
Primary.
Note: A Primary server starts the NMS services automatically when the operating
system is restarted. A backup server does not automatically start the NMS
services when the operating system is restarted.
3. Type 1 at the prompt to select Primary, and then press Enter to keep the current NMS as
the Primary NMS.
The script installs the NMS server software. Follow any instructions that are displayed
once the installation is complete.
4. Transfer the license file you obtained earlier from TAC to both the Primary and the Backup
NMS servers after you have installed the software on both. Name the file nmssvr_e.lic
and placed it in the /home/nms/cfg directory.
5. Turn on the specific individual services by entering the following command:
service idirect_nms start
6. Verify that the NMS servers are running by entering the following command.
service idirect_nms status
The following sample output displays.
nms_config (pid 20111) is running...
nmssvr (pid 20363) is running...
nrdsvr (pid 20363) is running...
evrsvr (pid 20363) is running...
revsvr (pid 20391) is running...
latsvr (pid 20405) is running...
osssvr is stopped
snmpsvr (pid 20610) is running...
nms_monitor is stopped
cntrlsvr is stopped
The services cntrlsvr and nms_monitor must be running.
7. Close the WinSCP and PuTTY sessions to your NMS Server.

Procedure 5. Install the New NMS Server Software on the

Backup NMS Server
This procedure explains how to install the NMS Server software on the Backup NMS.
1. Using PuTTY, log on to the root user account on the Backup NMS Server and repeat steps 1
through 8 of “Download the NMS Software” on page 77.
2. Repeat Procedure 3, Remove any Existing NMS Database on page 79 on the Backup NMS
server.
3. Repeat step 1 through 3 of Procedure 4, Install the New NMS Server Software on the
Primary NMS Server, but do so on the Backup NMS server.
4. Type 2 at the prompt to select Backup, and then press Enter to keep the current NMS as
the Backup NMS.
5. Check to see that the backup NMS servers are not running by entering:
service idirect_nms status
All services should indicate that they are not running. The following sample output
displays:
# service idirect_nms status
nms_config is stopped
nmssvr is stopped
revsvr is stopped
snmpsvr is stopped
cntrlsvr is stopped
evtsvr is stopped
latsvr is stopped
nrdsvr is stopped
nms_monitor is stopped
Continue to the next chapter for instructions on installing software on the Protocol Processor
Blades.

Install iDX 1.x on the Protocol Processor
6. In addition, download the following documents to assist you in your installation process:
• iDX 1.x iMonitor User Guide
• iDX 1.x iBuilder User Guide
• iDX 1.x Release Notes

To successfully install the iDX software on your Protocol Processor Blades, the following
procedures are required:
• Procedure 6, Download the PP Software to the Protocol Processor Blades
• Procedure 7, Install iDX 1.x on the Protocol Processor Blades
Procedure 6. Download the PP Software to the Protocol

Processor Blades
In this procedure, you transfer the downloaded Protocol Processor server software to the
Protocol Processor Blade(s). You are not be installing the software at this point.
1. Open a WinSCP session between your PC/Laptop and any one of the Protocol Processor
Blades, and then transfer the file protocol_processor-9_x.tar.gz to the /root directory of
the Protocol Processor Server.
Note: The actual release number will vary. Substitute the actual release number
for “9-x.”
2. On your PC/Laptop open a PuTTY session and log on to the Protocol Processor Blade.
3. Verify that you are in the root directory of the Protocol Processor Blade by entering the
command pwd at the command prompt. If the response /root is displayed, then you are
in the correct directory.
4. Enter the following command at the shell prompt:
tar -zxvf protocol_processor-9_x.tar.gz
This command creates a subdirectory named Netmodem-9x/install in the /root directory,
placing the decompressed output of the tar file into that subdirectory.
5. Repeat steps 1 through 4 for every Protocol Processor Blade in your network before
continuing to the next procedure.

Procedure 7. Install iDX 1.x on the Protocol Processor Blades

Use this procedure to install the iDX software on your Protocol Processor Blades.
1. On your PC/Laptop, open a PuTTY session and log on to any Protocol Processor Blade.
2. Verify that you are in the /root directory of the Protocol Processor Blade by entering the
command pwd at the command prompt. If the response /root is displayed, then you are
in the correct directory.
3. Services must be stopped to allow the software installation. Enter the following command
at the shell prompt:
service idirect_hpb stop
4. Determine the version of software that was pre-installed by entering the following:
rpm –q protocol_processor
5. The following sample output displays:
protocol_processor-7_0_1
The version is the three numbers connected by underscores. In this example, it is 7.0.1.
6. From the /root directory, go to the current version of Protocol Processor software
directory by entering the following command:
cd NetModem-<current version>/install
7. Uninstall the current version of Protocol Processor Server software by entering the
following command:
./install_pp.sh –u
8. Go the the /etc/idirect/ directory and enter the following commands:
rm *
rm -rf *
9. From the /root directory of the Protocol Processor Server, go to the latest version of
Protocol Processor software directory by entering the following command:
cd NetModem-<9.x version>/install
Remember, this directory was created in step 4 of “Download the NMS Software” on
page 77.
10. Install the latest version of Protocol Processor Server software on your server by entering
the following command:
./install_pp.sh
11. After the install script finishes and you are returned to the shell prompt, services must be
started again on the Protocol Processor Blade. Restart services by entering the following
command:
service idirect_hpb start
iDX 1.x is now installed on this Protocol Processor Blade. Repeat steps 1 through 11 for
each Protocol Processor Blade in the network.

Install iDX 1.x Client Software
Install iDX 1.x Client Software

This chapter includes the procedures for successfully installing the NMS client software on
your PC or laptop:
• Procedure 8, Install the NMS Client Software (iBuilder/iMonitor)
• Procedure 9, Configure Your Network
Procedure 8. Install the NMS Client Software (iBuilder/iMonitor)

Before you install the NMS client software, ensure that the PC or laptop has the following:
• Windows 2000 or XP; refer to the system requirements at the beginning of this document
• Approximately 50 megabytes of free disk space
• At least 512 MB of RAM.
WARNING! If you ran nms_clients_setup.exe to install a previous

version of the iDirect NMS GUIs, you must remove the current
clients before installing the new ones. Use the Windows
Add/Remove Programs option available in your Windows Control
Panel to remove the old clients, and then run the setup program
to install the new clients.
Note: If you want to run multiple versions of iDirect NMS clients on the same PC, copy
the installation directory of the current version (iDirect under Program Files)
to a different location and uninstall it from the Control Panel. Now you can
install a new version and still use the old one.
1. On the PC/Laptop, log on as administrator.
2. Using Unzip, WinZip, or PKZIP, uncompress the previously downloaded nms_clients-9x.zip
to a location on your PC/Laptop where you can easily locate it later.
3. To install the NMS client software, double-click the nms_clients_setup.exe icon
contained in the NMS Clients folder.
When the setup program has finished, you have entries for iBuilder, iMonitor, and iSite in
your WindowsJStartJPrograms menu under iDirect. Additionally, a directory named
iDIRECT NMS Clients 9.x is created on your desktop with the proper shortcuts.
4. Double-check the new NMS connectivity by pinging the primary NMS.
5. Open the new version of iBuilder and connect to the upgraded NMS. Make sure the
database that you see is the correct one.
You are now ready to build and configure the network components. For instructions, refer to
the iDX 1.x iBuilder User Guide.
Procedure 9. Configure Your Network

At this point, you build your iDirect network with iBuilder using the iDX 1.x iBuilder User
Guide as reference. Your network consists of the following components:

Install iDX 1.x on the Hub Line Cards
• Hub RFT components and satellite (antenna, HPA, transponder, spacecraft, upstream
carrier, downstream carrier, etc.)
• Network components (teleport, Hub RFT, Protocol Processor, Protocol Processor Blades)
• The Network itself, transmit and receive line cards, inroute groups, and remotes.
Note: DO NOT modify or clone the Bench Test spacecraft, Bench Test Inroute, or Bench
Test Outroute for your actual network configurations. These are only for
testing purposes. For your network configuration, create new spacecraft,
downstream, and upstream carriers.
Once these items have been defined in iBuilder, the last two parts of the installation process
involve installing certain iDX software configuration packages on the hub line cards and the
remotes. You use iBuilder to accomplish this, as described in the following chapters.

This chapter contains the following procedures required to successfully install the appropriate
iDX software on your hub line cards:
• Procedure 10, Download the Cumulative Update
• Procedure 11, Download Software Packages to Line Cards
• Procedure 12, Apply the Configuration Options File
Refer to the iDX 1.x Release Notes appropriate to the release that you are installing for
information about which hub line card models are supported in that release.
Table 16 lists the cumulative update files and the hub packages by type of hub line card.
Table 16. Hub Line Card Updates and Packages
Type of Hub Line Card Cumulative Update Hub Package

iNFINITI cumulative_update-9.0.x hub-9.0.x
Evolution evo_bsp-9.0.x evo_d_hub-9.0.x
Note: In these instructions, “9.0.x” refers to the latest release of the iDX software.
Please substitute the latest release number (for example, 9.0.0.9, or 9.1.0) for
“9.0.x” throughout this document.
Note: If you have more than one type of hub line card, perform these procedures once
for each line card type, selecting the appropriate update or package each time.
Procedure 10. Download the Cumulative Update

When installing the iDX software on your iNFINITI and/or Evolution Hub Line Cards, you must
first load the cumulative update file listed in Table 16 before loading the hub software
package.


1. Launch iBuilder and log on with an administrator-level user ID and Password.
2. In iBuilder, in the Tree View, right-click the Network icon, and then select Package
Download J TCP (Figure 27).
Figure 27. Selecting Package DownloadJTCP
The TCP Download window displays (Figure 28).

Figure 28. TCP Download Window— Selecting Cumulative Updates for Hub Line Cards
3. In the Options pane of the TCP Download dialog (Figure 28), select the appropriate
Hardware: either Evolution Line Card or iNFINITI.
4. For Role, select Any if it is not already selected.
5. For Mode, leave the default selected.
6. For Version, select 9.0.x BSP Update.
7. For Image Version Check, select Don’t check versions,
8. For Configurations, select Download images only.
9. For Reset, select Don’t reset.
10. Click Start to download the cumulative package.
When the download is complete, continue to the next procedure.

Procedure 11. Download Software Packages to Line Cards

Perform the steps in this procedure to select appropriate hub software packages and
download them to your hub line cards.
DownloadJTCP.
Figure 29. TCP Download Window - Selecting Hub Package
2. In the Options area of the TCP Download dialog box (Figure 29), select the appropriate
Hardware: either Evolution Linecard or iNFINITI.
3. For Role, select Hub.
4. For Mode, select DVB-S2 for an Evolution Linecard or Legacy for an iNFINITI linecard.
5. For Version, make sure 9.0.x is selected.
6. For Image Version Check, select Don’t check versions.
8. For Reset, select Don’t Reset.
9. Click Start to download the software packages to the line cards.
Monitor the download by observing the Status column in the Line Cards section. When a
line card has been downloaded successfully, the Status changes to Done.

10. When the download is complete, wait three minutes for the line cards to completely store
the package into Flash memory.
11. Repeat these steps for each type of hub line card.
Procedure 12. Apply the Configuration Options File

After completing the software install, use this procedure to apply the configuration to all of
the active line cards in your network.
Note: You must use the Apply ConfigurationsJMultiple option with Push (UDP) to
apply the options files to all of the line cards.
1. In iBuilder, in the Tree View, right-click the Network icon, and then select Apply
ConfigurationsJMultiple.
The Automated Configuration Downloader window displays your remotes, hub line
cards, and the network (Figure 30).
Figure 30. Apply Configurations to Hub Line Cards
2. In the Line Cards pane, select all line cards.

3. For Protocol, select Push (UDP).
4. For Reset, select Reset on Success.
5. Verify that the remotes and network are NOT selected. You do NOT send options files to
these components at this time.
6. Click Start to send the appropriate option files to all of the hub line cards and reset them.

Install iDX 1.x on the Remotes
7. When the multiple configuration download to all of your active line cards is complete,
close the Automated Configuration Downloader window.
8. Repeat Procedures 1, 2 and 3 for each network that you are installing.
This completes the hub line card install portion of your software installation. Proceed to the
next chapter to install iDX 1.x on the remotes.

This chapter contains the following required procedures to successfully install the appropriate
iDX software on your remotes:
• Procedure 13, Download the Cumulative Update
• Procedure 14, Download Software Packages to Remotes
• Procedure 15, Apply the Configuration Options File
Refer to the iDX 1.x Release Notes appropriate to the release you are installing for
information about which remote modem models are supported in that release.
Table 17 lists the cumulative update files and remote software package files by type of
remote.
Table 17. Remote Cumulative Update and Software Packages
Type of Remote Cumulative Update Remote Package

Evolution X3 cumulative_update-9.0.x evo_x3_rmt-9.0.x
Evolution e8350, e850 evo_bsp-9.0.x evo_d_rmt-9.0.x
iNFINITI cumulative_update-9.0.x remote-9.0.x
Note: In these instructions, “9.0.x” refers to the latest release of the iDX software.
Substitute the latest release number (for example, 9.0.0.9, or 9.1.0) for
“9.0.x” throughout this document.
Note: If you have more than one type of remote, perform these procedures once for
each remote type, selecting the appropriate update or package each time.

WARNING! The multicast download feature can only be run on

one network at a time. It may be necessary to repeat
downloading packages to remotes in case a remote does not
acknowledge.
WARNING! If you use the Multicast Download option, DO NOT

ADJUST THE DOWNLOAD RATE; iBuilder automatically sets the
download rate to the appropriate value for your downstream
data rate.
Procedure 13. Download the Cumulative Update

When installing the iDX software on your remotes, you must first load the cumulative update
package listed in Table 17 before loading the remote packages.
1. Launch iBuilder and log on as administrator.
Download J TCP (Figure 31).
Figure 31. Selecting Package DownloadJTCP

Figure 32. TCP Download Window—Selecting Cumulative Updates for Remotes
3. In the Options area, select the appropriate Hardware.

4. For Role, select Remote if it is not already selected.
6. For Version, select 9.0.x BSP Update.
7. For Image Version Check, select Don’t check versions.
9. For Reset, select Don’t reset.
10. Click the Start button to download the cumulative package.
11. When the download is complete, wait three minutes for the remotes to completely store
the package into Flash memory.
12. Repeat this procedure for the other types of remotes in your network (if any), until you
have downloaded the packages to them all.

Procedure 14. Download Software Packages to Remotes

Perform the steps in this procedure to select appropriate remote software packages and
download them to your remotes.
1. In iBuilder, in the Tree View, right-click on the Network icon, and select Package
DownloadJMulticast (Figure 33).
Figure 33. Selecting Package DownloadJMulticast
The Multicast Download window displays (Figure 34).

Figure 34. Multicast Download Window—Selecting Remote Package
2. In the Package area, select the appropriate Hardware.

3. For Role, select Remote.
5. For Version, make sure 9.0.x is selected.
6. Under Download Parameters, make sure Reset is NOT selected.
WARNING! When using the Multicast Download option, DO NOT

ADJUST THE DOWNLOAD RATE. iBuilder has automatically set this
to the appropriate value for your downstream data rate.
WARNING! DO NOT reset the remotes at this time!
In the Modems area of the Multicast Download window, notice that active remotes are
already selected.
7. Click Start to begin multicasting to the remotes.

Progress displays in the Progress bar (lower left corner) and is indicated to the right of
each active remote by the word Done in the Status column.
have downloaded the images to them all.
9. When the software download to all of your active remotes is complete, close the
Multicast Download dialog box.
Procedure 15. Apply the Configuration Options File

After completing the software install, use this procedure to apply the configuration to all of
the active remotes in your network.
1. In the Tree View, right-click the Network icon, and then select Apply Configurations J
Multiple (Figure 35).
Figure 35. Selecting Apply ConfigurationJMultiple
The Automated Configuration Downloader dialog displays your remotes, hub line cards,
and the network (Figure 36). In the Remotes area, iBuilder automatically selects the
affected remotes.

Figure 36. Apply Configurations to Remote(s)
2. For Target, select Remote-side Only.

3. For Protocol, select Push (UDP).
4. For Reset, select Reset on Success.
5. Clear any selected check boxes in the Line Cards and Network areas.
6. Click Start to send the appropriate option files to all of the remotes.
Download progress is indicated to the right of each active remote in Status column.
have applied the configuration options to them all.
8. When the multiple configuration download to all of your active remotes is complete, close
the Automated Configuration Downloader dialog box.
9. Repeat Procedures 1, 2, and 3 for each network that you are installing.
This completes the remote install portion of your iDX software installation.


WKBK Bhi 8xand10x 080109 Rev1

Hochgeladen von

Dokumentinformationen

Originaltitel

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

WKBK Bhi 8xand10x 080109 Rev1

Hochgeladen von

Copyright:

Verfügbare Formate

Student Workbook

for iDirect Broadband Hub Installer

Document Name: WKBK_BHI_8xand10x_080109_Rev1.pdf

Document Part Number: GE0000048

ii BHI Course Student Workbook

Revision Date Released Reason for Change(s) Who Updated?

A August 1, 2009 First release of this document. TJenkins

BHI Course Student Workbook iii

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Exercise 1. Configure the NMS Servers

Exercise 2. Set the Date and Time on the Servers

Exercise 3. Install the NMS Software License File

BHI Course Student Workbook v

Exercise 4. Change the Linux Passwords

Exercise 5. Configure the Protocol Processor Blades

Exercise 6. Configure the EDAS / Control Module IP Address

Exercise 7. Install the NMS Client Software

Exercise 8. Configure the Switch IP Address and EDAS Port

vi BHI Course Student Workbook

Exercise 9. Configure the IP Address of Each Line Card

Exercise 10. Commission the Hub Carrier

Exercise 11. RCM Failover Test

Exercise 12. Hub Chassis Backplane Test

BHI Course Student Workbook vii

Exercise 14. Protocol Processor Blade Failover Test

Exercise 15. Hub Power Failure Simulation Test

Exercise 16. Connectivity Test

Exercise 17. Performance and Throughput Test

viii BHI Course Student Workbook

Exercise 18. ACM Verification

Appendix A. Configuration and Commissioning Checklist . . . . . . . . 75

Appendix B. iDX 1.0.x Software Installation Process . . . . . . . . . . . 77

BHI Course Student Workbook ix

Convention Description Example

BHI Course Student Workbook xi

Red italic Used when the user needs

Symbol Warning type Definition

CAUTION: When you see this alert

WARNING! Electric shock hazard: When

xii BHI Course Student Workbook

• iDXiDS Release Notes

BHI Course Student Workbook xiii

Hub Configuration Exercises

BHI Course Student Workbook xv

The sample network uses the following address ranges:

Apply the network addresses as defined in Table 1 and Table 2.

xvi BHI Course Student Workbook

Table 1. Upstream Network

Device IP Address Switch Port Number

Table 2. Tunnel Network

Device IP Address Switch Port Number

BHI Course Student Workbook xvii

Table 2. Tunnel Network (continued)

Device IP Address Switch Port Number

Note: Additional IP addresses and switch ports may be required if installing

Acceptance Test Procedure Exercises

xviii BHI Course Student Workbook

BHI Course Student Workbook xix

xx BHI Course Student Workbook

Exercise 1. Configure the NMS Servers

3. Change directories by entering the following command:

BHI Course Student Workbook 1

Note: Command lines are case-sensitive.