iBuilder User Guide

iDX Release 2.0

A component of iVantage NMS

November 01, 2010

iBuilder User Guide

iDX Release 2.0

Copyright 2010 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: UG_iBuilder User Guide iDX 2.0_Rev H_11012010.pdf

Document Part Number: T0000230

ii

iBuilder User Guide

iDX Release 2.0

Contents

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvii
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Contents Of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

The iVantage Network Management System. . . . . . . . . . . . . . . . xxxi

1 iDirect System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Overview of the Network Management System for iBuilder . . . . . . 7
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Gathering the Information You Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 Preparing Equipment in Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4 Components of the Network Management System . . . . . . . . . . . . . . . . . . . . . 9
2.4.1 NMS Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
iBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
iMonitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
iSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.4.2 Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

iBuilder User Guide

iDX Release 2.0

iii

Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

Real-time Data Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

Latency Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

NMS Controller Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

PP Controller Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

Chassis Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

NMS Monitor Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

Consolidation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

Database Backup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

Database Restore Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

2.5 Installing iBuilder, iMonitor, and iSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.5.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5.2 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.6 Launching iBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.6.1 Logging On To Additional Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.6.2 Multiple Users or PCs Accessing the NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.6.3 Accepting Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.7 Pre-defined Components and Components Folders in iBuilder . . . . . . . . . . . 15

2.7.1 Bench Test Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.2 Components Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Folders Containing Critical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components: Remote Antenna Components . . . . . . . . . . . . . . . . . . . . . . . . . .
Components: Hub RFT Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16
16
17
18

Folders Containing Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . .

18

Adding Entries to Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18

Canceling an Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

2.8 Using iBuilders Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.8.1 Clicking on Elements and Folders: What Happens? . . . . . . . . . . . . . . . . . . . . . . . . 21
Right-Clicking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

Double-Clicking vs. Single-Clicking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

2.8.2 Globe Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Using the Docking Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

Expanding the Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22

Collapsing the Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23

Sorting Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23

Sorting the Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23

2.8.3 Network Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.8.4 Using the Interface Toolbars and Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . 27

iv

iBuilder User Guide

iDX Release 2.0

Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27

Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27

Find Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

29

View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

30

Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31

Connection Details on Status Bar Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31

Active Users Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31

Legend Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31

Configuration Changes Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

33

Configuration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

33

Properties View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34

Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34

Collapse Details Hierarchy + Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35

Choose Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36

2.9 Customizing and Creating New Detail Views . . . . . . . . . . . . . . . . . . . . . . . . 36

2.9.1 Customizing Detail Views for Configuration Reporting . . . . . . . . . . . . . . . . . . . . . 36
2.9.2 Creating Additional Filters for Customized Reporting . . . . . . . . . . . . . . . . . . . . . . 40

2.10 Working with Multiple Elements Simultaneously . . . . . . . . . . . . . . . . . . . . 42

2.10.1 Working with Multiple Configurations and Image Files . . . . . . . . . . . . . . . . . . . . 42
2.10.2 Modifying Parameters on Multiple Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Rules for Group Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42

Procedure for Group Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42

2.11 Configuration Status of Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2.11.1 What is a Configuration State? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.11.2 Possible Configuration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.11.3 Configuration State Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.11.4 Viewing Configuration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.11.5 Why Did My Configuration States Change? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.11.6 Configuration States and iMonitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.11.7 Accepting Configuration Changes and Locking the Database . . . . . . . . . . . . . . . . 47

2.12 Understanding the Databases Numbering Convention . . . . . . . . . . . . . . . . 47

2.13 Viewing the Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.14 Configuring Warning Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2.14.1 Setting Global Warning Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.14.2 Customizing Warning Properties for Individual Network Elements . . . . . . . . . . . . . 55
2.14.3 Clearing Customized Warning Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

2.15 Managing NMS Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2.15.1 Importing Your License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

iBuilder User Guide

iDX Release 2.0

2.15.2 License Properties Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

2.15.3 Exporting iBuilder Data for Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.15.4 Permanently Enabling Chassis License Download . . . . . . . . . . . . . . . . . . . . . . . . 62

2.16 In Color versus Shaded Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

3 Defining Hub RFT Components and the Satellite . . . . . . . . . . . . 65

3.1 Preparing the Hub RFT Components Folders . . . . . . . . . . . . . . . . . . . . . . . 65
3.1.1 Adding an Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.1.2 Adding an Up Converter or Down Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.1.3 Adding a High Power Amplifier (HPA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3.2 Adding a Spacecraft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3.3 Adding a Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.4 Adding Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.5 Adding Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.5.1 Adding Downstream Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.5.2 Adding Upstream TDMA Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.5.3 Adding Upstream SCPC Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.5.4 Estimating the IP Data Rate for a DVB-S2 Carrier . . . . . . . . . . . . . . . . . . . . . . . . . 81

4 Defining Network Components . . . . . . . . . . . . . . . . . . . . . . . . 83

4.1 Adding a Teleport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.2 Adding a Backup Teleport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.3 Adding a Hub RFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.4 Adding a Protocol Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.4.1 TRANSEC Protocol Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4.5 Setting Warning Properties for Protocol Processor Blades . . . . . . . . . . . . . . 91

4.6 Adding a Protocol Processor Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.7 Adding a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.7.1 Overriding Automatically-Assigned VLAN Addressing . . . . . . . . . . . . . . . . . . . . . . 95
4.7.2 Special VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.8 Adding a SkyMonitor Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5 Defining Networks, Line Cards, and Inroute Groups . . . . . . . . . 101

5.1 iDirect Line Card and Hub Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.2 Adding a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

vi

iBuilder User Guide

iDX Release 2.0

5.3 Line Card Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

5.4 Adding a Transmit or Transmit and Receive Line Card . . . . . . . . . . . . . . . . 104
5.5 Setting Warning Properties for Line Cards . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6 Adding Receive (Rx) Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.7 Deleting a Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.8 Changing to an Alternate Downstream Carrier . . . . . . . . . . . . . . . . . . . . . 110
5.9 Adding an iSCPC Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.10 Defining a Standby Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.10.1 Overview of Line Card Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Line Card Redundancy in TDMA Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Line Card Redundancy for iSCPC Connections . . . . . . . . . . . . . . . . . . . . . . . . 117
5.10.2 Adding a Standby Line Card to a TDMA Network . . . . . . . . . . . . . . . . . . . . . . . 118
5.10.3 Adding an iSCPC Standby Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.10.4 Managing Line Card Redundancy Relationships . . . . . . . . . . . . . . . . . . . . . . . . 120
Viewing Line Card Redundancy Relationships . . . . . . . . . . . . . . . . . . . . . . . . . 121
Configuring Line Card Redundancy Relationships . . . . . . . . . . . . . . . . . . . . . . 122
Assigning a Warm Standby to an Active Line Card . . . . . . . . . . . . . . . . . . . . . . 123
Assigning a Cold Standby to an Active Line Card . . . . . . . . . . . . . . . . . . . . . . . 124
Removing a Warm Redundancy Relationship . . . . . . . . . . . . . . . . . . . . . . . . . 125
Removing a Cold Redundancy Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5.10.5 Swapping an Active and Standby Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.10.6 Line Card Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

5.11 Adding Inroute Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

5.11.1 Carrier Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.11.2 Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.11.3 Mesh-Enabled Inroute Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.11.4 Adding an Inroute Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

5.12 DVB-S2 Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

5.12.1 System Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.12.2 Configuring DVB-S2 Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.12.3 Adjusting DVB-S2 Parameters for CCM Networks . . . . . . . . . . . . . . . . . . . . . . . 138

6 Configuring Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

6.1 iDirect Remote Satellite Router Models . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
6.3 Adding Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
6.4 Remote Information Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

iBuilder User Guide

iDX Release 2.0

vii

6.4.1 Transmit and Receive Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

6.4.2 Customers and Distributors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

6.5 Remote IP Config Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

6.5.1 VLAN and LAN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Configuring LAN and Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 150
Adding VLANs to a Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
6.5.2 Domain Name System (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6.5.3 Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . 153
6.5.4 RIPv2, Static Routes, Multicast Groups, Port Forwarding and NAT . . . . . . . . . . . . . 154
RIPv2 (Routes Sub-Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Using Static Routes with Multiple Protocol Processor Blades . . . . . . . . . . . . . . . 156
NAT and Port Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Accelerated GRE Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Multicast Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

6.6 Remote Switch Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

6.7 Remote QoS Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
6.7.1 QoS Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
6.7.2 Downstream Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
6.7.3 Rate Shaping and MODCOD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

6.8 Remote Geo Location Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Mobile State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

6.9 Remote VSAT Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Configuring a Remote Transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

6.10 Setting Warning Properties for Remotes . . . . . . . . . . . . . . . . . . . . . . . . 171

6.11 Adding a Remote by Cloning an Existing Remote . . . . . . . . . . . . . . . . . . . 171
6.12 Roaming Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
6.12.1 Adding a Roaming Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
6.12.2 Managing Roaming Remote Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Managing Must be the Same Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Managing Dont Care Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Adding Multiple Roaming Remotes to a Network . . . . . . . . . . . . . . . . . . . . . . . 177
Adding a Roaming Remote to Multiple Network . . . . . . . . . . . . . . . . . . . . . . . 178
6.12.3 Beam Switching for Roaming Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Automatic Beam Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Manual Beam Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Round Robin Beam Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

6.13 Enabling IP Packet Compression Types . . . . . . . . . . . . . . . . . . . . . . . . . 180

viii

iBuilder User Guide

iDX Release 2.0

6.13.1 TCP Payload Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

6.13.2 UDP Header Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
UDP Header Compression Performance Characteristics . . . . . . . . . . . . . . . . . . 182
6.13.3 CRTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
RTP Header Compression Performance Characteristics . . . . . . . . . . . . . . . . . . 183
6.13.4 UDP Payload Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
6.13.5 L2TP Payload Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

7 Configuring Quality of Service for iDirect Networks . . . . . . . . . 185

7.1 Group QoS Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.1.1 QoS Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Change to MIR and CIR Bandwidth Calculation . . . . . . . . . . . . . . . . . . . . . . . . 188
Bandwidth Allocation Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
7.1.2 Group QoS Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Bandwidth Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Bandwidth Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Service Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Application Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Virtual Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
7.1.3 QoS Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Remote Based Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Application Based Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Application Scaled Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Setting the QoS Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
7.1.4 Multicast Bandwidth Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

7.2 Configuring Group QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

7.2.1 The Group QoS User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Group View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Profile View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Profile-Remote View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Remote View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
7.2.2 Estimating Effective MIR and CIR for DVB-S2 Networks . . . . . . . . . . . . . . . . . . . . 202
7.2.3 Effective Cost with Allocation Fairness Relative to CIR . . . . . . . . . . . . . . . . . . . . 207
7.2.4 Allocation Fairness Relative to MODCOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
7.2.5 Adding a Bandwidth Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
7.2.6 Adding a Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
7.2.7 Adding an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
7.2.8 Creating Service Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

iBuilder User Guide

iDX Release 2.0

ix

7.2.9 Configuring Application Properties for Remotes . . . . . . . . . . . . . . . . . . . . . . . . 219

7.2.10 Assigning Service Profiles to Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
7.2.11 Overriding Application Properties on Individual Remotes . . . . . . . . . . . . . . . . . . 224
7.2.12 Configuring Full-Trigger CIR for a Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

7.3 Working with Group Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

7.3.1 Saving Group Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
7.3.2 Copying Group Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
7.3.3 Modifying Group Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
7.3.4 Applying Group Profiles to Networks and Inroute Groups . . . . . . . . . . . . . . . . . . 233

7.4 QoS for iSCPC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

7.5 Application Profiles, iSCPC Profiles and Filter Profiles . . . . . . . . . . . . . . . . 235
Adding a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Copying a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
7.5.1 Adding an Application Profile or iSCPC Profile . . . . . . . . . . . . . . . . . . . . . . . . . 238
7.5.2 Adding a Filter Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
7.5.3 Adding a Rule to a QoS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

7.6 Assigning QoS Profiles to Multiple Remotes . . . . . . . . . . . . . . . . . . . . . . . 246

8 Configuring a Hub Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . 249

8.1 Configuring the Chassis IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
8.1.1 Setting the IP Address for a Chassis with an EDAS Controller Board . . . . . . . . . . . . 250
8.1.2 Setting the IP Address for a Chassis with a MIDAS Controller Board . . . . . . . . . . . . 250

8.2 Chassis Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

8.3 Configuring and Controlling the Hub Chassis . . . . . . . . . . . . . . . . . . . . . . 252
8.4 Configuring a Four-Slot Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
8.5 Sharing a 20 Slot Chassis in a Multi-NMS System . . . . . . . . . . . . . . . . . . . . 260
Sharing the Chassis Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Configuring Chassis Slots for Access by Another NMS . . . . . . . . . . . . . . . . . . . . 262
Duplicating the Chassis Configuration on the Second NMS . . . . . . . . . . . . . . . . 264

8.6 Changing a Chassis IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

8.7 Daisy Chaining Hub Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
8.7.1 Connecting Your Chassis in a Multi-Hub Chain . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-Hub RCM Interface Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-Hub RCM Interface Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-Hub RCM Interface LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

267
268
268
268

8.7.2 Adding a Chassis Group in iBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

8.7.3 Adding a Chassis to a Chassis Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
8.7.4 Changing the Order of the Chassis in a Chassis Group . . . . . . . . . . . . . . . . . . . . . 273

iBuilder User Guide

iDX Release 2.0

9 Controlling Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

9.1 Activating and Deactivating Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
9.2 Moving Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

10 Retrieving and Applying Saved and Active Configurations . . . . 279

10.1 Configuration Options Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
10.2 Hub-side and Remote-side Options Files . . . . . . . . . . . . . . . . . . . . . . . . 280
10.3 Modifying, Deleting, and Viewing Configurations . . . . . . . . . . . . . . . . . . . 281
10.4 Retrieving Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
10.4.1 Retrieving a Single Saved or Active Configuration . . . . . . . . . . . . . . . . . . . . . . 281
10.4.2 Retrieving Multiple Saved or Active Configurations . . . . . . . . . . . . . . . . . . . . . . 283

10.5 Comparing Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

10.6 Applying Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Maintenance Window Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Sequence of Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
10.6.1 Applying Multiple Configurations to Network Elements . . . . . . . . . . . . . . . . . . . 287
Automated Configuration Downloader Options . . . . . . . . . . . . . . . . . . . . . . . . 288
Stopping the Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
10.6.2 Applying a Configuration to a Protocol Processor or Chassis . . . . . . . . . . . . . . . . 289
10.6.3 Applying a Configuration to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
10.6.4 Applying a Configuration to the Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
10.6.5 Applying a TCP or UDP Configuration to a Remote . . . . . . . . . . . . . . . . . . . . . . 291

10.7 Configuration Changes on Roaming Remotes . . . . . . . . . . . . . . . . . . . . . 292

10.7.1 Roaming Options File Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
10.7.2 Pending Changes across Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
10.7.3 Applying Changes to Roaming Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

11 Upgrading Software and Firmware . . . . . . . . . . . . . . . . . . . . 295

11.1 Image Package Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
11.2 Downloading an Image to Remotes and Line Cards Concurrently . . . . . . . . 296
11.2.1 Multicast via UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
11.2.2 Multicast Download Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
11.2.3 Selecting the Download Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Package Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Modems and Hubs Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Download Parameters Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
11.2.4 Downloading an Image to Out of Network Remotes . . . . . . . . . . . . . . . . . . . . . 299

iBuilder User Guide

iDX Release 2.0

xi

11.2.5 Interactions with Other iBuilder Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 299

11.3 Resetting Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

11.4 Downloading an Image or Configuration File via TCP . . . . . . . . . . . . . . . . 301
11.5 Downloading Remotes Using Revision Server . . . . . . . . . . . . . . . . . . . . . 301
11.5.1 How the Revision Server Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
11.5.2 When to Use the Revision Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
11.5.3 Starting the Revision Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
11.5.4 Controlling the Revision Server Real-Time Event Display . . . . . . . . . . . . . . . . . . 306
11.5.5 Monitoring Upgrades Using the Revision Server Status Pane . . . . . . . . . . . . . . . . 309
11.5.6 Cancelling an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

12 Commissioning a Line Card, Private Hub or Mini Hub . . . . . . . 313

12.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
12.2 Add the Line Card in iBuilder and Retrieve the Configuration . . . . . . . . . . 314
12.3 Power on the Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
12.4 Determine the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
12.5 Download the Image Packages and Options File . . . . . . . . . . . . . . . . . . . 317
12.6 Connect the Transmit and Receive Ports . . . . . . . . . . . . . . . . . . . . . . . . 322
12.7 Perform 1 dB Compression Point Test with the Satellite Operator . . . . . . . 322
12.8 Set the Transmit Power for the Outroute . . . . . . . . . . . . . . . . . . . . . . . . 323
12.9 Connect to the LAN and Apply the Line Card Configuration . . . . . . . . . . . 324
12.10 Set the Clear Sky C/N Parameter for a Mesh Outroute . . . . . . . . . . . . . . 325
12.11 Set the UPC Margin for a Mesh Outroute . . . . . . . . . . . . . . . . . . . . . . . 326
12.12 Set the C/N for an Inroute in a Mesh Inroute Group with Existing Carriers

326

12.13 Set the Clear Sky C/N Parameter for an Inroute in a Mesh Inroute Group . 328
12.14 Set the TDMA Nominal C/N Parameter for an Inroute . . . . . . . . . . . . . . . 331

13 Managing User Accounts and User Groups . . . . . . . . . . . . . . . 333

13.1 Conversion of User Accounts During Upgrade Procedure . . . . . . . . . . . . . 333
13.2 NMS User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
13.2.1 Visibility and Access for VNO User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Visibility and Access for Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Visibility and Access for Components Folders . . . . . . . . . . . . . . . . . . . . . . . . . 335
13.2.2 Visibility and Access for CNO User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
13.2.3 Creating and Managing VNO and CNO User Groups . . . . . . . . . . . . . . . . . . . . . . 336

xii

iBuilder User Guide

iDX Release 2.0

Adding or Modifying a VNO or CNO User Group . . . . . . . . . . . . . . . . . . . . . . . . 337

13.2.4 Setting Global Rate Limits for User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
13.2.5 Modifying per Node VNO Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
13.2.6 Changes Made by an HNO During a VNO Session . . . . . . . . . . . . . . . . . . . . . . . . 341
13.2.7 Sharing a Chassis Among Multiple VNO User Groups . . . . . . . . . . . . . . . . . . . . . 342
Configuring VNO Access Rights for a Shared Chassis . . . . . . . . . . . . . . . . . . . . 344
13.2.8 Modifying Group QoS Settings for VNO User Groups . . . . . . . . . . . . . . . . . . . . . 347
Restricting VNO Access to GQoS Tab Only . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Assigning Ownership of Group QoS Nodes to a VNO . . . . . . . . . . . . . . . . . . . . . 348
Setting VNO Permissions for Group QoS Nodes . . . . . . . . . . . . . . . . . . . . . . . . 351
Viewing GQoS Nodes in a VNO Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Setting Application Profile Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

13.3 Adding and Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

13.3.1 Adding a User and Defining User Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
13.3.2 Modifying a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
13.3.3 Adding a User by Cloning a Users Account . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
13.3.4 Viewing a Users Account Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
13.3.5 Deleting an Existing Users Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
13.3.6 Managing Accounts from the Active Users Pane . . . . . . . . . . . . . . . . . . . . . . . . 358

13.4 Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

13.5 User Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
13.5.1 Super User and Guest Level Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
13.5.2 Super User and Guest Privileges for VNOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

13.6 NMS Database Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

14 Adding Mesh Capabilities to a Star Network. . . . . . . . . . . . . . 365

14.1 Prerequisites for Converting an Existing Star Network to Mesh . . . . . . . . . 365
14.2 Recalibrating a Star Outbound Channel for Mesh . . . . . . . . . . . . . . . . . . . 366
14.3 Converting a Star Inbound Channel to Mesh . . . . . . . . . . . . . . . . . . . . . . 367
14.4 Reconfiguring Star Remotes to Carry Mesh Traffic . . . . . . . . . . . . . . . . . . 367

15 Converting an Existing Network to TRANSEC . . . . . . . . . . . . . 371

15.1 TRANSEC Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
15.2 TRANSEC Host Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
15.3 Reconfiguring the Network for TRANSEC . . . . . . . . . . . . . . . . . . . . . . . . 373

iBuilder User Guide

iDX Release 2.0

xiii

16 Converting Between SCPC and DVB-S2 Networks . . . . . . . . . . 377

16.1 Download the New Firmware to the Tx Line Card . . . . . . . . . . . . . . . . . . 378
16.2 Assign the Carrier and Update the Configuration . . . . . . . . . . . . . . . . . . 379

Appendix A Configuring a Distributed NMS Server . . . . . . . . . . . 381

A.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
A.2 Distributed NMS Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
A.3 Logging On to iBuilder and iMonitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
A.4 Setting Up a Distributed NMS Environment . . . . . . . . . . . . . . . . . . . . . . . 383
A.5 Removing the SNMP Proxy Server from Auxiliary NMS Servers . . . . . . . . . . 386
A.6 Regenerating the Options Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
A.7 Granting Read Permissions to NMS 2 and NMS 3 . . . . . . . . . . . . . . . . . . . . 387
A.8 Assigning QoS Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
A.9 Verifying Correct Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
A.10 Running the NAT Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
A.11 Managing a Distributed NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
A.12 dbBackup/dbRestore and the Distributed NMS . . . . . . . . . . . . . . . . . . . . 393

Appendix B Using the iDirect CA Foundry . . . . . . . . . . . . . . . . . 395

B.1 Using the CA Foundry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
B.2 Creating a Certificate Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
B.3 Logging On to a Certificate Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
B.3.1 Connecting to a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
B.3.2 Bringing an Unauthorized Remote into a TRANSEC Network . . . . . . . . . . . . . . . . . 399
B.3.3 Certifying a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
B.3.4 Revoking a Remotes Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

B.4 Updating the Network Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Appendix C Configuring Networks for Automatic Beam Selection . 407

C.1 Adding Beams to the Beam Map File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
C.2 Configuring Remotes for Automatic Beam Selection . . . . . . . . . . . . . . . . . 409
C.2.1 Changing the Minimum Look Angle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

C.3 Remote Custom Keys for Automatic Beam Switching . . . . . . . . . . . . . . . . . 412

C.3.1 Configuring the Network Acquisition Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

xiv

iBuilder User Guide

iDX Release 2.0

C.3.2 Changing the Download Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

C.3.3 Disabling Beam Switching to Zero-Quality Beams . . . . . . . . . . . . . . . . . . . . . . . 415

C.4 Remote Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

C.4.1 latlong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
C.4.2 tlev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
C.4.3 antenna debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
C.4.4 beamselector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Appendix D Remote Locking . . . . . . . . . . . . . . . . . . . . . . . . . . 421

D.1 iDirects Traditional Remote Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
D.1.1 Locking a Remote Using Traditional Remote Locking . . . . . . . . . . . . . . . . . . . . . 421
Configuring the Network Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Setting the Remote Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Checking Remote Locking Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
D.1.2 Unlocking a Remote Using a Valid Password . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
D.1.3 Remote Lock Tampering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
D.1.4 Requesting a Default Remote Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

D.2 Enhanced Remote Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

D.2.1 Soft Locking versus Hard Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
D.2.2 Locking a Remote Using Enhanced Remote Locking . . . . . . . . . . . . . . . . . . . . . . 424
Configuring the Network Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Setting a Soft Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Removing a Soft Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Setting a Hard Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Checking Remote Locking Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
D.2.3 Non-Warranty RMA Required to Remove Locks . . . . . . . . . . . . . . . . . . . . . . . . . 427

Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

iBuilder User Guide

iDX Release 2.0

xv

List of Figures
Figure 1. Example iDirect Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Figure 2. iDirect IP Architecture Multiple VLANs per Remote . . . . . . . . . . . . . . . . . . . . . 3
Figure 3. iDirect IP Architecture VLAN Spanning Remotes . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 4. iDirect IP Architecture Classic IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 5. iDirect IP Architecture TDMA and iSCPC Topologies . . . . . . . . . . . . . . . . . . . . . 6
Figure 6. Desktop Shortcuts for NMS GUI Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 7. Windows Start Menu Entries for NMS GUI Clients . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 8. iBuilder Login Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 9. Using the File Menu to Log On To iBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 10. Error Message for Unavailable Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 11. Accept Changes Button Indicating Configuration Change . . . . . . . . . . . . . . . . . 14
Figure 12. Configuration Changes Pending Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 13. Bench Test Components in Initial NMS Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 14. QoS Subfolders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 15. Filter Profile Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 16. iSCPC Profile Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 17. BUC Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 18. LNB Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 19. Folders Containing Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 20. Example of Entries in Manufacturers Folder . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 21. Dialog Box for Adding a New Manufacturer . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 22. iBuilders Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 23. Expand Tree Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 24. Expanded Tree with Child Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 25. Collapse Tree Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 26. Collapsed Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 27. Sorting Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 28. Sort Preferences Dialog Box: Selecting Sort Order . . . . . . . . . . . . . . . . . . . . . 24
Figure 29. Sort Preferences Dialog Box: Selecting Sort Field . . . . . . . . . . . . . . . . . . . . . . 24
Figure 30. Sort Preferences Dialog Box: Applying the Sort . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 31. Fully-Expanded Network in the iBuilder Network Tree . . . . . . . . . . . . . . . . . . . 26
Figure 32. Fully-Expanded Folder in the iBuilder Network Tree . . . . . . . . . . . . . . . . . . . . 26
Figure 33. iBuilder Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 34. iBuilder Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 35. iBuilder Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 36. Selecting Search Criteria on Find Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 37. Find Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 38. iBuilder View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

xvi

iBuilder User Guide

iDX Release 2.0

Figure 39. iBuilder Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Figure 40. iBuilder Active Users Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 41. iBuilder Legend Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 42. Accept Configuration Changes Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 43. Configuration Changes Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 44. Example of Configuration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 45. Selecting Details from the View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 46. Network Highlighted in Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 47. Result in Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 48. Network Highlighted in Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 49. Result in Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 50. Choose Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 51. Selecting a Details Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 52. Choose Details Dialog Box for Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 53. View Details for Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 54. Adding a Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 55. Custom Report Modify Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 56. Custom Report Delete Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 57. Selecting the Parent Element for Group Editing . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 58. Selecting Multiple Elements for Group Editing . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 59. Configuration States of an iDirect Remote . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 60. New Teleport with System-Generated Number . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 61. Partial List of Activities Displayed in the Activity Log . . . . . . . . . . . . . . . . . . . 49
Figure 62. Activity Log Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 63. Ellipsis Button and Graphical Clock Display . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 64. Opening an Options File from the Activity Log . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 65. Copying Multiple Rows from the Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 66. Modify Global Warning Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 67. Modify Warning Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 68. Warning Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 69. Viewing the iBuilder License Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 70. Enabling Chassis License Download to Chassis Manager . . . . . . . . . . . . . . . . . . 57
Figure 71. Select License Type Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 72. Selecting a License File for Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 73. Accepting Changes Importing a License File . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 74. License Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 75. Selecting Export Data for Licensing on License Toolbar . . . . . . . . . . . . . . . . . . 60
Figure 76. Selecting Data for Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 77. Saving Data for License Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 78. Sample License Request CSV file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

iBuilder User Guide

iDX Release 2.0

xvii

Figure 79. para_cfg.opt with Chassis License Download Enabled . . . . . . . . . . . . . . . . . . . 62

Figure 80. New Antenna Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 81. New Up Converter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 82. New HPA Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 83. New Spacecraft Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 84. Hub Transponder Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 85. New Bandwidth Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 86. New Downstream Carrier Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 87. New Upstream TDMA Carrier Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 88. New Upstream SCPC Carrier Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 89. MODCOD Distribution Calculator for DVB-S2 Carriers . . . . . . . . . . . . . . . . . . . . 81
Figure 90. Calculating Estimated IP Data Rate for a DVB-S2 Network . . . . . . . . . . . . . . . . 82
Figure 91. Teleport Information Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 92. Teleport Geo Location Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 93. Configuring a Backup Teleport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 94. Roaming Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 95. Automated Configuration Downloader Dialog Box . . . . . . . . . . . . . . . . . . . . . . 87
Figure 96. New Hub RFT Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 97. New Protocol Processor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 98. Persistent Multicast Group Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 99. Protocol Processor Blades Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 100. Protocol Processor Blade Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 101. Uplink VLAN Segment in a PP Blade Environment . . . . . . . . . . . . . . . . . . . . . 94
Figure 102. Protocol Processor VLans Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 103. Protocol Processor VLAN Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 104. Overriding Automatically-Assigned VLAN Addressing . . . . . . . . . . . . . . . . . . . 96
Figure 105. New SkyMonitor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 106. RF Port Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 107. Associating a SkyMonitor Port with an iDirect Carrier . . . . . . . . . . . . . . . . . . 99
Figure 108. SkyMonitor Port Configured for Two Carriers and Center Frequency . . . . . . . . . 99
Figure 109. Network Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 110. iBuilder Line Card Type Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 111. New Transmit Line Card Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 112. New Receive Line Card Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 113. Removing a Line Card from an Inroute Group . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 114. Removing a Line Card from the Hub RFT . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 115. Deactivating a Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 116. Setting a Line Card to Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 117. Swapping the Downstream Carriers: Initial Configuration . . . . . . . . . . . . . . . 111
Figure 118. Selecting the New Alternate Downstream Carrier . . . . . . . . . . . . . . . . . . . . 112
Figure 119. Selecting the New Primary Downstream Carrier . . . . . . . . . . . . . . . . . . . . . 112

xviii

iBuilder User Guide

iDX Release 2.0

Figure 120. New iSCPC Line Card Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Figure 121. New Standby Line Card Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 122. New Standby iSCPC Standby Line Card Dialog Box . . . . . . . . . . . . . . . . . . . . 120
Figure 123. Sample Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 124. Manage Line Card Redundancy Dialog Box: By Standby View . . . . . . . . . . . . . 121
Figure 125. Manage Line Card Redundancy Dialog Box: By Active View . . . . . . . . . . . . . . 122
Figure 126. Assigning a Warm Standby Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 127. Assigning a Cold Standby Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 128. Removing a Cold Redundancy Relationship . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 129. Choosing a New Active Line Card During Line Card Swap . . . . . . . . . . . . . . . 127
Figure 130. Line Card Swap Event Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 131. Inroute Group Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 132. New Inroute Group Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 133. Assign Hub to Inroute Group Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 134. Inroute Group Dialog Box with Highlighted Mesh Reference Carrier . . . . . . . . 133
Figure 135. Inroute Group Acquisition/Uplink Control Tab . . . . . . . . . . . . . . . . . . . . . . 134
Figure 136. DVB-S2 Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 137. Remote Information Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 138. Remote Information Tab: Transmit and Receive Parameters . . . . . . . . . . . . . 146
Figure 139. Remote Information Tab: Customer and Distributor Parameters . . . . . . . . . . 147
Figure 140. Add Customers Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 141. Customers Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 142. Entering Customer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 143. Sample VLAN Network Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 144. Remote IP Config Tab: Interface Configuration . . . . . . . . . . . . . . . . . . . . . . 150
Figure 145. Remote IP Config Tab: Adding a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 146. Add New VLAN Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 147. Remote IP Config Tab: DNS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 148. Remote IP Config Tab: DHCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 149. Remote IP Config Sub-Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 150. Remote IP Config Tab: Routes Sub-Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 151. Remote IP Config Tab: Static Routes Sub-Tab . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 152. Add Static Route dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 153. Deactivating a Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 154. Remote IP Config Tab: Port Forwarding Sub-Tab . . . . . . . . . . . . . . . . . . . . . 157
Figure 155. Add Port Forwarding Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 156. Remote IP Config Tab: GRE Tunnels Sub-Tab . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 157. GRE Tunnel Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 158. Remote IP Config Tab: Multicast Group Sub-Tab . . . . . . . . . . . . . . . . . . . . . 159
Figure 159. Persistent Multicast Group Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

iBuilder User Guide

iDX Release 2.0

xix

Figure 160. Remote Switch Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Figure 161. Dedicating a Port to a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 162. Switch Tab with Dedicated VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 163. Reconfiguring a Dedicated Port as a Trunk . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 164. Selecting the Same Switch Setting for All Ports . . . . . . . . . . . . . . . . . . . . . 162
Figure 165. Port Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 166. Remote QoS Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Figure 167. Remote QoS Tab: Downstream Distributor . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 168. Remote QoS Tab: Upstream and Downstream Rate Shaping . . . . . . . . . . . . . 165
Figure 169. Remote Geo Location Tab: Settings for Stationary Remotes . . . . . . . . . . . . . 167
Figure 170. Remote Geo Location Tab: Settings for Mobile Remotes . . . . . . . . . . . . . . . . 167
Figure 171. Remote VSAT Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 172. Remote VSAT Tab with SeaTel ABS Fields . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 173. LNB Dialog Box: Frequency Band and Cross Pol Selection . . . . . . . . . . . . . . . 171
Figure 174. Roaming Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 175. Roaming Properties Update Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 176. iBuilder Details View with Collapsed Hierarchy . . . . . . . . . . . . . . . . . . . . . . 176
Figure 177. Modifying Shared Parameters of Roaming Remotes . . . . . . . . . . . . . . . . . . . 177
Figure 178. Add Multiple Roaming Remotes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 179. Add Roaming Remotes to Networks Dialog Box . . . . . . . . . . . . . . . . . . . . . . 179
Figure 180. Using the Console's beamselector Command . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 181. Selecting Compression Types on the Remote Information Tab . . . . . . . . . . . . 181
Figure 182. Enabling L2TP Payload Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 183. Group QoS Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 184. Remote Based Mode vs. Application Based Mode . . . . . . . . . . . . . . . . . . . . . 194
Figure 185. Selecting the QoS Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Figure 186. Selecting the Group QoS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Figure 187. Group QoS: Group View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 188. Group QoS: Profile View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Figure 189. Group QoS: Profile-Remote View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Figure 190. Group QoS: Remote View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 191. Configured vs. Effective MIR and CIR before Estimation . . . . . . . . . . . . . . . . 203
Figure 192. MODCOD Distribution Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 193. Calculating Estimated Information Rate . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 194. Calculating Information Rate Distribution . . . . . . . . . . . . . . . . . . . . . . . . . 205
Figure 195. Configured vs. Effective MIR and CIR after Estimation . . . . . . . . . . . . . . . . . 206
Figure 196. Effective MIR and CIR in the Group View . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 197. Competing Service Groups without Allocation Fairness Relative to CIR . . . . . . 207
Figure 198. Results of Selecting Allocation Fairness Relative to CIR on Parent . . . . . . . . . 208
Figure 199. Configured vs. Effective Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Figure 200. Selecting Allocation Fairness Relative to MODCOD . . . . . . . . . . . . . . . . . . . 209

xx

iBuilder User Guide

iDX Release 2.0

Figure 201. Bandwidth Group Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Figure 202. New Bandwidth Group in Group QoS Tree . . . . . . . . . . . . . . . . . . . . . . . . . 211
Figure 203. Group QoS Tree with Mesh Bandwidth Group . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 204. Service Group Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 205. New Service Group Inserted Into a Bandwidth Group . . . . . . . . . . . . . . . . . . 214
Figure 206. QoS Application Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 207. Selecting a User Multicast MODCOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Figure 208. New Application Inserted Into a Service Group . . . . . . . . . . . . . . . . . . . . . . 217
Figure 209. QoS Service Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Figure 210. Application Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 211. Multiple Service Profiles Assigned to a Single Remote . . . . . . . . . . . . . . . . . 221
Figure 212. Moving Remotes Between QoS Service Profiles . . . . . . . . . . . . . . . . . . . . . . 223
Figure 213. Dragging Remotes Between QoS Service Profiles . . . . . . . . . . . . . . . . . . . . . 224
Figure 214. Overriding Application Properties on Individual Remotes . . . . . . . . . . . . . . . 225
Figure 215. Determining Virtual Remote Numbers for Remote Applications . . . . . . . . . . . 226
Figure 216. Defining the Full Trigger CIR Custom Key . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 217. Naming a QoS Group Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Figure 218. Viewing Properties of QoS Group Members . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 219. Copying a QoS Group Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Figure 220. Modifying a QoS Group Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Figure 221. Selecting a QoS Group Profile to Apply . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Figure 222. Viewing Properties of QoS Group Members . . . . . . . . . . . . . . . . . . . . . . . . 234
Figure 223. QoS Folders in iBuilder Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 224. Preconfigured iSCPC Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 225. New Profile in iBuilder Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Figure 226. Clone As Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Figure 227. Application Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Figure 228. Add Service Level Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Figure 229. Service Profile Rules Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Figure 230. Filter Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Figure 231. Add Filter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Figure 232. Application Profile Rules Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Figure 233. Selecting and Clearing the Show Protocols Name Check Box . . . . . . . . . . . . . 244
Figure 234. Adding a Rule to a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Figure 235. Assign QoS Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 236. Chassis Dialog Box: New 20-Slot Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 237. Chassis Dialog Box: 20-Slot Chassis with Licensed Slots . . . . . . . . . . . . . . . . 254
Figure 238. Chassis Dialog Box: Selecting Assign Hub . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Figure 239. Assigning a Line Card to a Chassis Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Figure 240. Chassis Dialog Box: Four-Slot Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

iBuilder User Guide

iDX Release 2.0

xxi

Figure 241. Chassis Dialog Box: Four-Slot Chassis with Licensed Slots . . . . . . . . . . . . . . . 257
Figure 242. Turning On/Off the 10 MHz Reference on a Four-Slot Chassis . . . . . . . . . . . . 259
Figure 243. Sharing a Hub Chassis Among Multiple Network Management Systems . . . . . . . 260
Figure 244. Selecting an External Chassis Manager Server . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 245. Determining a Server MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 246. para_cfg.opt with Licensed Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Figure 247. para_cfg.opt Reconfigured to Share Slots 1 and 2 . . . . . . . . . . . . . . . . . . . . 263
Figure 248. Locating the Chassis IP Address in para_cfg.opt . . . . . . . . . . . . . . . . . . . . . 265
Figure 249. Chassis Group Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Figure 250. Multi-Hub RCM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Figure 251. Chassis Group in iBuilder Network Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Figure 252. Chassis Group Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Figure 253. Adding a Chassis to a Chassis Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Figure 254. Chassis With All Jumpers Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Figure 255. Editing or Removing Chassis in a Chassis Group . . . . . . . . . . . . . . . . . . . . . 273
Figure 256. Changing the Order of Chassis in a Chassis Group . . . . . . . . . . . . . . . . . . . . 274
Figure 257. Activating a Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Figure 258. Move Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Figure 259. Changes Pending Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Figure 260. Viewing and Deleting Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Figure 261. Options File Viewed in Notepad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Figure 262. Multiple Configurations Retrieve Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 283
Figure 263. Save As Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Figure 264. Comparing the Active and Latest Configurations . . . . . . . . . . . . . . . . . . . . . 285
Figure 265. Comparing Configurations: Differences Only . . . . . . . . . . . . . . . . . . . . . . . 286
Figure 266. Automated Configuration Downloader . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Figure 267. Viewing the Download Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Figure 268. Global NMS Options Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Figure 269. Multicast Download Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Figure 270. Selecting DVB-S2 or iNFINITI Firmware Package . . . . . . . . . . . . . . . . . . . . . 298
Figure 271. Revision Server Duty Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Figure 272. Revision Server Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Figure 273. Revision Server Realtime Display Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Figure 274. Revision Server: Stop All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Figure 275. Revision Server: Start Highlighted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Figure 276. Revision Server Event Pane with Highlighted Remotes . . . . . . . . . . . . . . . . . 308
Figure 277. Revision Server: Stop Highlighted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Figure 278. Selecting Revision Server Status from the View Menu . . . . . . . . . . . . . . . . . 309
Figure 279. Revision Server Status Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Figure 280. Revision Server Details Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Figure 281. Chassis Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

xxii

iBuilder User Guide

iDX Release 2.0

Figure 282. Tera Terminal Serial Port Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 316
Figure 283. laninfo Command Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Figure 284. iSite Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Figure 285. Creating a New Element in the iSite Tree . . . . . . . . . . . . . . . . . . . . . . . . . 318
Figure 286. iSite Login Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Figure 287. Download Package Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Figure 288. Locating the Hub Packages for Download . . . . . . . . . . . . . . . . . . . . . . . . . 320
Figure 289. Evolution and iNFINITI Line Card Packages . . . . . . . . . . . . . . . . . . . . . . . . . 321
Figure 290. Assigning the Downstream Carrier Power . . . . . . . . . . . . . . . . . . . . . . . . . 324
Figure 291. iMonitor Hub Stats Results Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figure 292. Setting the SCPC LB Clear Sky C/N for a Mesh Outroute . . . . . . . . . . . . . . . . 326
Figure 293. Setting the Hub UPC Margin for a Mesh Outroute . . . . . . . . . . . . . . . . . . . . 326
Figure 294. Inroute Groups Information Tab: Line Cards Section . . . . . . . . . . . . . . . . . . 327
Figure 295. Disabling Remote Uplink Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Figure 296. Remote Probe: Changing the Remote Tx Power . . . . . . . . . . . . . . . . . . . . . 329
Figure 297. Change Remote Tx Power Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Figure 298. Determining the Clear Sky C/N for a Mesh Inroute . . . . . . . . . . . . . . . . . . . 330
Figure 299. Setting the Clear Sky C/N for a Mesh Inroute . . . . . . . . . . . . . . . . . . . . . . . 331
Figure 300. Group Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Figure 301. Group Dialog Box: Modifying a User Group . . . . . . . . . . . . . . . . . . . . . . . . . 337
Figure 302. Setting a VNO Element to Visible with Create Permission . . . . . . . . . . . . . . . 338
Figure 303. Setting a VNO Element to Visible Only . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Figure 304. Setting a VNO Element to Owned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Figure 305. Setting Rate Limits for User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Figure 306. Making an Element Visible to a VNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Figure 307. Setting Element Permissions for a VNO . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 308. VNO Full View: Owned Slots vs. Visible Slots . . . . . . . . . . . . . . . . . . . . . . . 342
Figure 309. HNO and VNO Views of Chassis Modify Screen . . . . . . . . . . . . . . . . . . . . . . 343
Figure 310. Chassis Modify: Attempting to Assign an Occupied Slot . . . . . . . . . . . . . . . . 344
Figure 311. Granting Chassis Rights to a VNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Figure 312. Expanded Chassis in VNO Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Figure 313. Granting Control of Chassis Slots to a VNO . . . . . . . . . . . . . . . . . . . . . . . . . 346
Figure 314. VNO View of Manage Line Card Redundancy Screen . . . . . . . . . . . . . . . . . . . 346
Figure 315. VNO with Network Visibility and GQoS Node Ownership . . . . . . . . . . . . . . . . 347
Figure 316. VNO Network Menu with Owned GQoS Nodes but No Network Access . . . . . . . 347
Figure 317. VNO with Network Write Access and GQoS Node Ownership . . . . . . . . . . . . . 348
Figure 318. VNO Network Menu with Owned GQoS Nodes and Write Access to Network . . . 348
Figure 319. VNO Ownership of Partial Bandwidth Pool . . . . . . . . . . . . . . . . . . . . . . . . . 349
Figure 320. VNO View of Partially-Owned Bandwidth Pool . . . . . . . . . . . . . . . . . . . . . . 349
Figure 321. Request Property Access for GQoS Nodes . . . . . . . . . . . . . . . . . . . . . . . . . 350

iBuilder User Guide

iDX Release 2.0

xxiii

Figure 322. Modify VNO Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Figure 323. A Visible Bandwidth Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Figure 324. An Owned Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Figure 325. VNO View of the Group QoS Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Figure 326. Setting VNO Visibility for an GQoS Application Profile . . . . . . . . . . . . . . . . . 354
Figure 327. User Dialog Box: Adding a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Figure 328. Change Password Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Figure 329. User Dialog Box: Cloning a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Figure 330. Active Users Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Figure 331. Opening the Active Users Pane from the View Menu . . . . . . . . . . . . . . . . . . 359
Figure 332. User Account Options from the Active Users Pane . . . . . . . . . . . . . . . . . . . . 360
Figure 333. Change Password Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Figure 334. Line Card Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Figure 335. Remote Information Tab: Enabling Mesh . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Figure 336. Elements of a TRANSEC Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Figure 337. Enabling TRANSEC for an Existing Network . . . . . . . . . . . . . . . . . . . . . . . . 373
Figure 338. Automated Configuration Downloader Dialog Box . . . . . . . . . . . . . . . . . . . . 374
Figure 339. Selections for Downloading DVB-S2 Line Card Firmware . . . . . . . . . . . . . . . . 378
Figure 340. Assigning a Line Card to a Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Figure 341. Selecting All Remotes for Configuration Download . . . . . . . . . . . . . . . . . . . 379
Figure 342. Sample Distributed NMS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Figure 343. Upstream Application Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Figure 344. Edit Rule Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Figure 345. dbBackup and dbRestore with a Distributed NMS . . . . . . . . . . . . . . . . . . . . 393
Figure 346. Logging On to the NMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Figure 347. Initial CA Foundry Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Figure 348. Exiting the CA Foundry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Figure 349. Creating a New Certificate Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Figure 350. Configuring the New Certificate Authority . . . . . . . . . . . . . . . . . . . . . . . . . 397
Figure 351. Logging On to a Certificate Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Figure 352. CA Foundry Status Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Figure 353. Certificate Authority Connected to a Host . . . . . . . . . . . . . . . . . . . . . . . . . 399
Figure 354. Warning Message when Disabling Authentication . . . . . . . . . . . . . . . . . . . . 400
Figure 355. Flushing a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Figure 356. CA Foundry Issuing a New X.509 Certificate . . . . . . . . . . . . . . . . . . . . . . . . 401
Figure 357. Determining the Derived ID in iBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Figure 358. Determining Certificates Issued by a CA . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Figure 359. Listing of Issued Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Figure 360. Revoking a Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Figure 361. Updating the Chain of Trust . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Figure 362. Logging On to the Root Account of a PP Blade . . . . . . . . . . . . . . . . . . . . . . 405

xxiv

iBuilder User Guide

iDX Release 2.0

Figure 363. Determining the Network ID on a PP Blade . . . . . . . . . . . . . . . . . . . . . . . . 405

Figure 364. Orbit-Marine AL-7104 Reflector Definition . . . . . . . . . . . . . . . . . . . . . . . . . 409
Figure 365. Remote Antenna Settings with General ABS Fields . . . . . . . . . . . . . . . . . . . 410
Figure 366. OpenAMIP, SeaTel and Orbit SBC Antenna Parameters . . . . . . . . . . . . . . . . . 411
Figure 367. Changing a Remotes net_state_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Figure 368. latlong Command Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Figure 369. tlev Command Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Figure 370. antenna debug Command Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Figure 371. beamselector list Command Example . . . . . . . . . . . . . . . . . . . . . . . . 419
Figure 372. beamselector switch Command Example . . . . . . . . . . . . . . . . . . . . . . 420

iBuilder User Guide

iDX Release 2.0

xxv

List of Tables
Table 1. Toolbar Icons and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 2. Configuration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 3. Standby Line Card Model Type Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . 117
Table 4. Example: Calculating Operational SNR Thresholds . . . . . . . . . . . . . . . . . . . . . . 137
Table 5. iDirect Overhead on Upstream Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Table 6. Multi-HUB RCM Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Table 7. RCM Switch Settings for Daisy Chained Chassis . . . . . . . . . . . . . . . . . . . . . . . . 269
Table 8. User Types and Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Table 9. Custom Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Table 10. Net State Timer Custom Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

xxvi

iBuilder User Guide

iDX Release 2.0

About This Guide

Purpose
The iBuilder User Guide provides detailed instructions for configuring your iDirect networks
using the iBuilder client application of the iDirect Network Management System (NMS). For
details on monitoring your iDirect networks, see the iMonitor User Guide.

Intended Audience
The iBuilder User Guide is intended for network operators, network architects, and other
personnel who operate or monitor iDirect networks. It is not intended for end users or field
installers.
Basic knowledge of TCP/IP concepts, satellite communications, and the Windows operating
systems is expected. Prior experience operating an iDirect network, although desirable, is not
required.

Contents Of This Guide

This document contains the following major sections:

The iVantage Network Management System

iDirect System Overview

Overview of the Network Management System for iBuilder

Defining Hub RFT Components and the Satellite

Defining Network Components

Defining Networks, Line Cards, and Inroute Groups

Configuring Remotes

Configuring Quality of Service for iDirect Networks

Configuring a Hub Chassis

Controlling Remotes

Retrieving and Applying Saved and Active Configurations

Upgrading Software and Firmware

Commissioning a Line Card, Private Hub or Mini Hub

iBuilder User Guide

iDX Release 2.0

xxvii

Managing User Accounts and User Groups

Adding Mesh Capabilities to a Star Network

Converting an Existing Network to TRANSEC

Converting Between SCPC and DVB-S2 Networks

Configuring a Distributed NMS Server

Using the iDirect CA Foundry

Configuring Networks for Automatic Beam Selection

Remote Locking

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 youll know how to interpret the
information presented.
Convention Description

xxviii

Example

Blue
Courier
font

Used when the user is required to

enter a command at a command
line prompt or in a console.

Enter the command:

Courier
font

Used when showing resulting

output from a command that was
entered at a command line or on
a console.

crc report all

Bold
Trebuchet
font

Used when referring to text that

appears on the screen on a
windows-type Graphical User
Interface (GUI).

1. If you are adding a remote to an inroute group,

right-click the Inroute Group and select Add
Remote.

Used when specifying names of

commands, menus, folders, tabs,
dialogs, list boxes, and options.

The Remote dialog box has a number of userselectable tabs across the top. The Information
tab is visible when the dialog box opens.

Blue
Trebuchet
font

Used to show all hyperlinked text

within a document.

For instructions on adding an iSCPC line card to the

network tree and selecting a Hub RFT for the line
card, see Adding an iSCPC Line Card on page 108.

Bold italic
Trebuchet
font

Used to emphasize information

for the user, such as in notes.

Note:

Red italic
Trebuchet
font

Used when the user needs to

strictly follow the instructions or
have additional knowledge about
a procedure or action.

cd /etc/snmp/

3100.3235 : DATA CRC [

1]
3100.3502 : DATA CRC [5818]
3100.4382 : DATA CRC [ 20]

Several remote model types can be

configured as iSCPC remotes.

WARNING! The following procedure may

cause a network outage.

iBuilder User Guide

iDX Release 2.0

Related Documents
The following iDirect documents are available at http://tac.idirect.net and may also contain
information relevant to this release. Please consult these documents for information about
installing and using iDirects satellite network software and equipment.

iDX Release Notes

iDX Software Installation Guide or Network Upgrade Procedure Guide

iDX iMonitor User Guide

iDX Technical Reference Guide

iDX Installation and Commissioning Guide for Remote Satellite Routers

iDX Features and Chassis Licensing Guide

iDX Software Installation Checklist/Software Upgrade Survey

iDX Link Budget Analysis Guide

Getting Help
The iDirect Technical Assistance Center (TAC) is available to help you 24 hours a day, 365 days
a year. Software user guides, installation procedures, a 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.
If you are interested in purchasing iDirect products, please contact iDirect Corporate Sales by
telephone or email.
Telephone: (703) 648-8000
Email: SALES@iDirect.net
iDirect strives to produce documentation that is technically accurate, easy to use, and helpful
to our customers. Your feedback is welcomed! Send your comments to techpubs@idirect.net.

iBuilder User Guide

iDX Release 2.0

xxix

xxx

iBuilder User Guide

iDX Release 2.0

The iVantage Network

Management System

iBuilder is a component of the iDirect iVantage Network Management System (NMS). The
iVantage NMS is a complete suite of tools for configuring, monitoring, and controlling your
iDirect satellite network.
The iVantage NMS consists of the following components:

iBuilder enables rapid, intuitive configuration of any iDirect network. It allows you to
easily add components to your network, change your current configuration, and download
configuration and software to network elements. The iBuilder Revision Server provides
automated management of software and firmware upgrades for your remote modems.
The iBuilder Group QoS (GQoS) user interface allows advanced network operators a high
degree of flexibility in creating subnetworks and groups of remotes with various levels of
service tailored to their network requirements. The iBuilder User Guide provides detailed
instructions for using iBuilder to configure and manage your network.

iMonitor provides network operators with detailed information on real-time and

historical performance of the network. Among its many capabilities, iMonitor allows you
to analyze bandwidth usage; view remote status; view network statistics; monitor
performance of networks, sub-networks and individual network elements; and manage
alarms, warnings and network events. Alarms, warnings and statistics can be forwarded as
SNMP traps. All events and performance statistics are automatically archived. Data
displayed on the iMonitor GUI can be exported directly into Excel for further analysis. A
Network Probe allows detailed investigation of network issues. The iMonitor User Guide
provides instructions for using iMonitor.

iSite allows you to monitor and configure iDirect devices in the field. It includes several
features that aid in the remote commissioning process, including assistance for antenna
pointing, antenna look angle calculation, and cross polarization. You can also use iSite to
configure and manage point-to-point SCPC connections between dedicated remotes. An
iSite API is available for custom development.

The Geographic Map is an optional iMonitor feature that displays in real time the exact
geographic location of all remotes within a given network on a world map. Functions
include mobile remote tracking; the ability to zoom, pan in or out, and add or remove
map features from the display; and filtering of remotes filter remotes by active state. The
Geographic Map is described in detail in the iMonitor User Guide.

iBuilder User Guide

iDX Release 2.0

xxxi

xxxii

SkyMonitor allows you to integrate one or more multi-port spectrum analyzers into your
hub installation and then use iMonitor to view your iDirect carriers or other areas of the
spectrum. SkyMonitor can be an invaluable tool for diagnosing performance issues from RF
interference or other carrier-related anomalies. Network Operators can view, analyze,
store and recall the spectral displays of any carrier from anywhere an iMonitor connection
is supported. Configuration of SkyMonitor is described in the iBuilder User Guide. The use
of SkyMonitor for spectrum analysis is described in the iMonitor User Guide.

iToolkit provides a software interface along with engineering services that support
iVantage integration with external systems. For example, you can integrate iVantage with
external web applications or OSS/BSS systems such as billing, provisioning, reporting or
customer access systems. Integrating the power of iVantage with other business tools
allows Network Operators to generate revenue through new service offerings such as
usage-based billing. iToolkit also enables Network Operators to integrate iVantage with
their service ordering and provisioning systems, greatly simplifying the process of adding
new customers and sites. The use of iToolkit is described in the iToolkit Users Guide.

A Virtual Network Operator (VNO) license enables network operators to view and
manage only their own networks and remotes, independent of other operators delivering
services out of the same hub. The VNO package makes it possible to scale investments to
actual business growth, significantly reducing initial capital equipment expenses.
Configuring VNOs is described in the iBuilder User Guide.

A Customer Network Observer (CNO) license grants filtered read-only iMonitor access,
allowing customers real-time and historical views into their own network performance
while maintaining overall network privacy. Configuring CNOs is described in the iBuilder
User Guide.

iBuilder User Guide

iDX Release 2.0

1 iDirect System Overview

As depicted in Figure 1 on p. 2, an iDirect network is a satellite based IP network with a star

topology in which a Time Division Multiplexed (TDM) broadcast downstream channel from a
central hub location is shared by a number of remote nodes. The iDirect Hub equipment
consists of an iDirect Hub Chassis with Universal Line Cards, a Protocol Processor (PP), a
Network Management System (NMS) and the appropriate RF equipment. Each remote node
consists of an iDirect broadband router and the appropriate external VSAT equipment. The
remotes transmit to the hub on one or more shared upstream carriers using DeterministicTDMA (D-TDMA), based on dynamic timeplan slot assignment generated at the Protocol
Processor.
Beginning with iDS Release 7.0, a mesh overlay can be added to the basic star network
topology, allowing traffic to pass directly between remote sites without traversing the hub.
This allows real-time traffic to reach its destination in a single satellite hop, significantly
reducing delay. It also saves the bandwidth required to retransmit mesh traffic from the hub
to the destination remote. For a description of iDirects mesh overlay architecture, see the
chapter titled Mesh Technical Description in the iDirect Technical Reference Guide.
Note:

Mesh is not supported in iDX Release 2.0.

The choice of upstream carriers is determined either at network acquisition time or

dynamically at run-time, based on a network configuration setting. iDirect software has
features and controls that allow the system to be configured to provide QoS and other traffic
engineered solutions to remote users. All network configuration, control, and monitoring
functions are provided via the integrated NMS. The software provides packet-based and
network-based QoS, TCP acceleration (or spoofing), AES link encryption, local DNS cache on
the remote, end-to-end VLAN tagging, dynamic routing protocol support via RIPv2 over the
satellite link, multicast support via IGMPv2 or IGMPv3, and VoIP support via voice optimized
features such as CRTP.
Note:

See the Technical Note titled IP Multicast in iDirect Networks for details on
configuring and using IP Multicast. iDirect Technical Notes can be downloaded
from the iDirect TAC web page.

An iDirect network interfaces to the external world through IP over Ethernet ports on the
remote unit and the Protocol Processor at the hub. The following figures, beginning with
Figure 2 on p. 3, describe the IP level configurations available to a network operator.

iBuilder User Guide

iDX Release 2.0

The iDirect system allows you to mix traditional IP routing based networks with VLAN based
configurations. This capability provides support for customers that have conflicting IP address
ranges in a direct fashion, and to support multiple independent customers at a single remote
site by configuring multiple VLANs directly on the remote.

Figure 1. Example iDirect Network

In addition to end-to-end VLAN, the system supports RIPv2 in an end-to-end manner including
over the satellite link; RIPv2 can be configured on per-network interface.

iBuilder User Guide

iDX Release 2.0

Figure 2. iDirect IP Architecture Multiple VLANs per Remote

iBuilder User Guide

iDX Release 2.0

Figure 3. iDirect IP Architecture VLAN Spanning Remotes

iBuilder User Guide

iDX Release 2.0

Figure 4. iDirect IP Architecture Classic IP Configuration

In addition to the network architectures discussed so far, iDirects iSCPC solution allows you to
configure, control and monitor point-to-point Single Carrier per Channel (SCPC) links. These
links, sometimes referred to trunks or bent pipes, may terminate at your teleport, or
they may be located elsewhere. Each end-point in an iSCPC link sends and receives data
across a dedicated SCPC carrier. As with all SCPC channels, the bandwidth is constant and
available to both sides at all times, regardless of the amount of data presented for
transmission. SCPC links are less efficient in their use of space segment than are TDMA
networks. However, they are very useful for certain applications. Figure 5 shows an iDirect
system containing an iSCPC link as well as a TDMA network, all under the control of the NMS.
Note:

iBuilder User Guide

iDX Release 2.0

iSCPC is not supported in iDX Release 2.0.

Figure 5. iDirect IP Architecture TDMA and iSCPC Topologies

iBuilder User Guide

iDX Release 2.0

Introduction

2 Overview of the
Network Management
System for iBuilder

This chapter presents an overview of the iBuilder network management tool for configuring
your iDirect network. It contains the following sections:

2.1

Introduction on page7

Gathering the Information You Need on page8

Preparing Equipment in Advance on page8

Components of the Network Management System on page9

Installing iBuilder, iMonitor, and iSite on page11

Launching iBuilder on page12

Pre-defined Components and Components Folders in iBuilder on page15

Using iBuilders Interface on page20

Customizing and Creating New Detail Views on page36

Working with Multiple Elements Simultaneously on page42

Configuration Status of Elements on page44

Understanding the Databases Numbering Convention on page47

Viewing the Activity Log on page49

Configuring Warning Properties on page51

Managing NMS Licenses on page56

In Color versus Shaded Icons on page63

Introduction
iDirects Network Management System (the iVantage NMS) is a powerful suite of applications
and servers that provide complete control and visibility to all components of your iDirect
networks. The NMS client/server system architecture consists of three series of components:

iBuilder User Guide

iDX Release 2.0

Gathering the Information You Need

Three NMS applications with Graphical User Interfaces (GUIs) that allow you to configure
and monitor your network

A database that stores the data entered by and displayed to users

A middleware tier that manages access to the database on behalf of user operations

This chapter provides some of the most important information you will need to understand
how iBuilder works and how to use it as effectively as possible. This chapter discusses how to
prepare for installation, what you will see when you first launch iBuilder, how to use the many
powerful tools available in iBuilder, how to create, customize, and print reports, and how to
determine the configuration status of network elements. For a description of all iVantage NMS
components see The iVantage Network Management System on pagexxxi.

2.2

Gathering the Information You Need

You must have the following information readily available when creating a new network.

2.3

Spacecraft and carrier information, such as:

Longitude (Geo location)

Transponder translation frequency

Hub Up/Down local oscillator

LNB stability

Carrier uplink and downlink frequencies

FEC block sizes

FEC blocks per outroute frame

Data rates

Overall IP architecture plan for hub components

Geographic location of the hub

Line Card serial numbers and slot numbers

Number of inroutes

Tx/Rx or Tx-only line cards, depending on downstream/upstream data rates (Refer to the
chapter titled iDirect Modulation Modes and FEC Rates in the iDirect Technical
Reference Guide.)

Frequency hopping (requires that a Reference Clock Module be installed on your hub
chassis) or carrier grooming mode

Remote serial numbers and geographic locations

Preparing Equipment in Advance

Before you begin configuring the network elements, you must have already commissioned
your hub equipment. This involves the following:

The NMS Server must already be installed and its interface defined.

The Protocol Processor blades must already be installed and configured.

The Chassis must already be installed and configured.

iBuilder User Guide

iDX Release 2.0

Components of the Network Management System

2.4

Line Cards must have already been installed in the Chassis with their IP addresses defined
using iSite.

Components of the Network Management System

The NMS consists of several client/server components that work together to provide the
functions and views necessary to control your network. These components are briefly
discussed in the following two sections.

2.4.1 NMS Applications

The iDirect NMS provides three GUI clients, each of which performs specific functions for
networks operators, field installers, and end users.

iBuilder
The iBuilder application provides all configuration and control functions to network
operators. Configuration options consist of creating network elements (e.g. networks, line
cards, remotes) and specifying their operational parameters, such as QoS profiles or IP
addresses. Control options consist of applying the specified configurations to the actual
network elements, retrieving active configurations, resetting elements, and upgrading
element software and firmware.

iMonitor
The iMonitor application provides complete visibility to the real-time status and operational
data of network elements. Status refers to the real-time state of network elements, such as
OK, warning, or alarm. Operational data are captured in a variety of network statistical data
tables and displays, revealing, for example, IP traffic statistics, satellite link quality, and
hardware component operating values.
In addition to real-time visibility, iMonitor allows you to access state and statistics from the
historical archive in order to analyze anomaly conditions and perform trend analyses. Refer to
the iMonitor User Guide for a complete list of real-time and historical data available through
iMonitor.

iSite
The iSite application is used primarily for commissioning new sites and monitoring TDMA
remotes from the local LAN side. It contains functions to help installers calculate antenna
azimuth/elevation, perform antenna pointing, and put up a continuous wave (CW) carrier for
antenna peaking, cross-polarization and 1dB compression tests. It also provides configuration
and real-time state/statistical information for one or more remote units. Instead of
interacting with the NMS middleware, it connects directly to each remote to perform all of its
operations. iSite does not provide access to historical information. See the Installation and
Commissioning Guide for iDirect Satellite Routers for more on commissioning remotes using
iSite.

iBuilder User Guide

iDX Release 2.0

Components of the Network Management System

In addition to its commissioning functions, iSite can be used to configure and monitor remoteto-remote SCPC connections. iSite also allows monitor-only capability to end-users, should
you decide to provide it to them.
Note:

End-users do not need iSite in order to receive or transmit IP data over iDirect
networks.

2.4.2 Server Components

The NMS server processes run on your NMS Linux Server machines. There are a number of NMS
servers processes, each of which performs a specific set of back-end functions.

Configuration Server
The configuration server is the core component of the NMS server family. It manages access to
the configuration database, which contains all the element definitions for your networks and
their operational parameters. Additionally, the configuration server provides most network
control functions (configuration apply, firmware download, resetting, etc.). The other servers
also use this server to determine what the network components are.

Real-time Data Server

The real-time data server collects most of the network statistics produced by your network
elements. These statistics include IP stats for each remote, remote status messages, timeplan
slot assignments, line card statistics, etc. Additionally, the real-time data server provides
these statistics to the GUI clients for real-time and historical display.

Event Server
The event servers primary job is to generate warnings and alarms and send them to iMonitor
for display. Warnings and alarms are collectively known as conditions. The event server also
collects and archives all system events and provides them to iMonitor for display.

Latency Server
The latency server measures round-trip time, or latency, for every active remote in your
networks. These measurements are stored in the archive and provided to iMonitor for display.

NMS Controller Server

The control server manages the PP Controller Server processes running on the NMS server.

PP Controller Servers
The PP Controller processes control the samnc process on each PP blade.

Chassis Manager Server

The chassis manager server controls access to all hub chassis. The CM server only allows
access to chassis slots that have been licensed by iDirect.

10

iBuilder User Guide

iDX Release 2.0

Installing iBuilder, iMonitor, and iSite

NMS Monitor Script

This simple script monitors all other servers and restarts them automatically if they terminate
abnormally. It records a log file of its activities and can be configured to send e-mail to
designated recipients when it restarts any of the other servers.

Consolidation Script
The consolidation process periodically consolidates records in the statistics archive to
preserve disk space on the server machine. Default consolidation parameters are already
entered into your configuration database; they can be tuned to your particular storage
requirements if necessary.

Database Backup Script

This script runs nightly to back up the data in your primary database and copy it to your
backup NMS server. The database backup must be custom-configured for each customer site.

Database Restore Script

This script runs nightly on your backup NMS server. It restores your primary NMS database into
the backup database for NMS failover purposes.

2.5

Installing iBuilder, iMonitor, and iSite

This section provides the system requirements and procedures for installing your Network
Management System components.

2.5.1 System Requirements

The NMS GUI clients are Windows PC-based applications that run under the following versions
of Windows:

Windows 2000 WorkStation, Service Pack 3 or later

Windows XP WorkStation

Vista, Windows NT, Windows 98 and Windows 95 are not supported. iDirect does not support
server-based versions of Windows.

2.5.2 Installation Procedure

A single client installer .exe file, nms_clients_setup.exe, installs all three GUI clients and
associated library files for you. To install the clients, copy the nms_clients_setup.exe file to
the target PC, double-click it, and follow the prompts.
By default, the clients are installed in the directory C:\Program Files\iDIRECT. The installer
automatically places a shortcut to each GUI application on your desktop and adds the
appropriate entries in the Windows Start menu. Click Start All Programs iDirect NMS
Clients <RelNo>, where <RelNo> is your release number. The iBuilder, iMonitor, and iSite
clients are displayed, along with an Uninstall selection.

iBuilder User Guide

iDX Release 2.0

11

Launching iBuilder

Figure 6. Desktop Shortcuts for NMS GUI Clients

Figure 7. Windows Start Menu Entries for NMS GUI Clients

2.6

Launching iBuilder
iBuilder is initially installed with two default accounts: admin and guest. The admin user
has full access privileges to all iBuilder functionality, while the guest account has read-only
access. The passwords for these two accounts are identical to their associated user names.
For information on setting up user accounts, see Managing User Accounts and User Groups
on page333.
iDirect strongly recommends that you modify the admin user password as soon as possible
after the installation. This is especially important if your NMS Server is accessible via the
public Internet.
1. To launch iBuilder, double-click the desktop shortcut or select it from the Windows Start
menu.
2. Enter your user name and password in the Login Information dialog box.

Figure 8. iBuilder Login Information Dialog Box

12

iBuilder User Guide

iDX Release 2.0

Launching iBuilder

3. Click Server and select the IP address or host name of your primary NMS Server machine.
The Server box holds up to three IP addresses. If yours does not exist, enter the IP Address
in the Server box.
4. Click OK to complete the login process.
Note:

The iBuilder version must match the NMS server version in order for you to log
in. (For example, version 8.0.0 of iBuilder may connect only to version 8.0.0 of
the NMS servers.)

The iBuilder application automatically connects to the NMS server processes that are required
to perform the NMSs functions. If this connection is lost for any reason, iBuilder
automatically reconnects to the servers when they become available.

2.6.1 Logging On To Additional Servers

In the event that there are multiple NMS servers in the same teleport or multiple teleports
under the network operators control, you may need to log out of one NMS server and log in to
another one. You can do this without exiting iBuilder. From the Main Menu, select File Log
Off to log out of your current session and File Log On to open the Login Information dialog
box again.

Figure 9. Using the File Menu to Log On To iBuilder

2.6.2 Multiple Users or PCs Accessing the NMS

Multiple users or multiple sessions may run simultaneously on the NMS. For example, the NMS
offers the following capabilities:
1. You may run multiple simultaneous sessions of iBuilder and/or iMonitor on a single PC.
These versions may be connected to different servers or the same server.
2. Multiple PCs may run the same session of iBuilder and/or iMonitor at any given time and
connect to the same server at the same time.

iBuilder User Guide

iDX Release 2.0

13

Launching iBuilder

Note:

Only one iBuilder user may have a Modify Configuration dialog box open at any
given time. If a second user tries to modify a record when someone else already
has a Modify dialog box open, an error message is displayed on the GUI of the
second user, and that user is not allowed to change anything in the database.

Figure 10. Error Message for Unavailable Database

2.6.3 Accepting Changes

When two iBuilder users are connected to the same server, and one of them modifies the
network configuration, the other user cannot modify the configuration until he accepts the
changes, which will automatically refresh his configuration view to reflect the latest changes.
When another user changes the configuration, or when you make a change that affects other
network elements, the Accept Changes button on your toolbar changes color from gray to
red. (For more information, see Table 1 on page 27.)

Figure 11. Accept Changes Button Indicating Configuration Change

If you attempt to modify the network configuration without accepting changes, the following
warning message appears:

Figure 12. Configuration Changes Pending Dialog Box

Before you accept the changes, you may view the other users changes by selecting View
Configuration Changes (see Configuration Changes Pane on page33). To accept the
changes and update your view of iBuilder, click Accept Changes. Any modifications the other
user has made are now displayed in your copy of iBuilder.

14

iBuilder User Guide

iDX Release 2.0

Pre-defined Components and Components Folders in iBuilder

2.7 Pre-defined Components and Components Folders

in iBuilder
iDirect has designed the Network Management System to be as easy to use as possible, and
therefore has added several components and components folder entries to iBuilder to get you
started. These pre-defined components and folders exist in iBuilder when you launch it for
the first time. The elements and folder entries can be re-used as you create new networks.
The NMS configuration database includes a number of pre-defined and re-usable components
and component folders that you can mange using iBuilder, including:

Bench Test Components for I/F Networks

Spacecraft

Transponder

Bandwidth

Upstream/Downstream Carriers

Components Folders Containing Critical Information

Remote Antenna Components

BUCs

LNBs

QoS

Upstream/Downstream Filters

Upstream/Downstream Application Profiles

Upstream/Downstream iSCPC Profiles

Upstream/Downstream Group Profiles

Components Folders Containing Reference Information

Manufacturers

2.7.1 Bench Test Components

The components that exist in the system when it is displayed for the very first time at your
site include Bench Test Components for I/F Networks, that were set up for testing purposes
prior to shipping.

WARNING! Do not modify or clone the Bench Test Spacecraft, Bench Test Inroute, or
Bench Test Outroute for your actual network configuration. These should
only be used for testing purposes. For your network configuration, please
create a new spacecraft and new downstream and upstream carriers.
Bench test components include:
a spacecraft

a transponder

a BUC

an LNB

bandwidth

an upstream and downstream carrier

iBuilder User Guide

iDX Release 2.0

15

Pre-defined Components and Components Folders in iBuilder

Figure 13. Bench Test Components in Initial NMS Tree

2.7.2 Components Folders

Several folders are built into iBuilder for your convenience, some of which have pre-defined
entries, and others of which require you to add the entries yourself. Some of these folders
contain entries that are critical to the configurations of various elements within the system,
whereas other folders contain information that is used only for reference and network recordkeeping. You can add additional entries to either type of folder. For instructions on how to
add entries to folders, see Adding Entries to Folders on page18.

Folders Containing Critical Information

The folders described in this section contain entries that are critical when configuring a given
component. At initial deployment, these folders already contain entries that iDirect has
defined.

QoS
This folder contains a number of subfolders, such as the Upstream and Downstream Filter
Profiles, Upstream and Downstream Application Profiles, and Upstream and Downstream
iSCPC Profiles folders shown in Figure 14. For more information, see Configuring Quality of
Service for iDirect Networks on page185.

Figure 14. QoS Subfolders

16

iBuilder User Guide

iDX Release 2.0

Pre-defined Components and Components Folders in iBuilder

Figure 15. Filter Profile Examples

Figure 16. iSCPC Profile Examples

Components: Remote Antenna Components

This folder contains a number of subfolders, such as the BUC and LNB folders shown below.
The entries listed in the figures below are examples of BUCs and LNBs certified by iDirect for
use on iDirect products. These lists are only partial lists.

Figure 17. BUC Examples

iBuilder User Guide

iDX Release 2.0

Figure 18. LNB Examples

17

Pre-defined Components and Components Folders in iBuilder

Components: Hub RFT Components

For detailed instructions on defining components within the Hub RFT Components folder, see
Preparing the Hub RFT Components Folders on page65.

Folders Containing Reference Information

The information in these folders are for convenience purposes only and are not used to
operate the NMS or any of iDirects equipment. However, entries from these folders can be
selected from drop-down lists on various configuration dialog boxes throughout the system so
that the information is at your fingertips if you need it.
These folders include Manufacturers, Distributors, Operators, Customers and User Groups, as
shown in Figure 19.

Figure 19. Folders Containing Reference Information

An example of entries in the Manufacturers folder is shown in Figure 20.

Figure 20. Example of Entries in Manufacturers Folder

Adding Entries to Folders

You can add entries to any folder, whether it has pre-defined entries in it or not. Selections in
these folders should be added prior to configuring other elements of the system, as the
information in the folders listed above will be requested in various configuration panes
throughout the system. Not having a selection defined in a given folder will result in your not
being able to select that entry when a configuration dialog box requests it. This could add
additional steps to the configuration process because an element may remain Incomplete
until a required component or subcomponent entry is created and selected on a given
elements configuration dialog box.

18

iBuilder User Guide

iDX Release 2.0

Pre-defined Components and Components Folders in iBuilder

You can add additional entries to any folder by right-clicking on the folder and selecting the
Add function for the type of component you want. For example, you can right-click
Manufacturers and select Add Manufacturers.

A dialog box appears allowing you to define a new manufacturer.

Figure 21. Dialog Box for Adding a New Manufacturer

Canceling an Entry
Clicking Cancel in any of the dialog boxes will cancel your current entries.

iBuilder User Guide

iDX Release 2.0

19

Using iBuilders Interface

2.8

Using iBuilders Interface

iBuilders main window is comprised of several toolbars and panes which are described in the
following sections.

Figure 22. iBuilders Main Screen

20

iBuilder User Guide

iDX Release 2.0

Using iBuilders Interface

2.8.1 Clicking on Elements and Folders: What Happens?

Right-Clicking
In general, you must right-click (or use the context-sensitive mouse button) on your mouse to
display any list of options that can be performed on the element you currently have selected.

Double-Clicking vs. Single-Clicking

You can double-click any network element/component in the Tree to automatically display its
properties in read-only mode.
You can single-click a plus (+) or minus (-) sign next to an element in the Tree to expand or
contract the branches to the next level down in the tree for that element or folder. Once an
element has no plus sign or minus sign next to it, you can double-click any element to view
the Properties for that element in read-only mode.
For example, if the Hub RFT Components folder has a plus sign (+) next to it, you can doubleclick it to expand it to see the four folders at the next level: Antenna, Up Converter, Down
Converter, and HPA. You can double-click any folder with a plus sign next to it to expand it to
the next level. However, once the folder is fully expanded and the elements within it are
displayed, if you double-click the actual element, the Properties for that element are
displayed in read-only mode.

2.8.2 Globe Functions

Right-clicking the Globe in the Tree allows you to move dockable panes, sort columns, hide
elements, expand the Tree and Collapse the Tree.

Using the Docking Feature

Docking refers to the ability to move a window pane of the NMS interface to another location
on the screen or to detach it from the screen entirely and place it somewhere else on your
monitor. In iDirects NMS, the dockable panes have double-ridge lines at the top of the pane.

To dock a window pane somewhere else on the NMS interface or on your monitor, follow these
steps:
1. Point to and right-click the double-ridge lines of the pane you want to move and select
Allow Docking.

iBuilder User Guide

iDX Release 2.0

21

Using iBuilders Interface

2. Place the pointer (mouse arrow) on the double-ridge lines and drag the pane wherever
you want it. Depending on where you drag it, the pane may change shape (for example,
from a vertical display to a horizontal display).
3. If you want to move the pane back into its original place or to another location, start by
grabbing the double-ridge lines with your pointer. Then, you can click the Name toolbar
at the top of the pane to move it around, and you can place your pointer at the edges of
the pane to resize the pane.
4. To detach the pane completely, double-click the double-ridge lines. The pane becomes
separately parented and you may move it independently from the main iBuilder window.
This feature is useful if you have two displays on a single PC and want to move this pane
to the second display.

Expanding the Tree

To expand the Tree to view all of the children elements, select Expand Tree. The Tree will
expand to show all of the child elements.

Figure 23. Expand Tree Selection

22

Figure 24. Expanded Tree with Child

Elements

iBuilder User Guide

iDX Release 2.0

Using iBuilders Interface

Collapsing the Tree

To collapse the Tree to view only the top level elements, select Collapse Tree. The Tree will
contract to show only the top level elements

Figure 25. Collapse Tree Selection

Figure 26. Collapsed Tree

Sorting Columns
In any pane with columns, or list controls, you can sort the entries in the pane by the values in
any column by clicking on the column heading. In Figure 27, the Active Users Pane has been
sorted on Group by clicking the column heading.

Figure 27. Sorting Columns

Sorting the Tree

To sort the Tree, follow these steps:
1. Right-click the double-ridge lines above the Tree pane and select Sort Tree. You can also
select Edit Sort Tree.

iBuilder User Guide

iDX Release 2.0

23

Using iBuilders Interface

2. The Sort Preferences dialog box is displayed.

Figure 28. Sort Preferences Dialog Box: Selecting Sort Order

3. Click the Sort items in drop-down list and select either Ascending or Descending.
4. Click the Sort items by drop-down list and select one of the options. Depending on what
you select in this field, your choices in the Apply sort to field will change.

Figure 29. Sort Preferences Dialog Box: Selecting Sort Field

5. If you selected Name, either select or clear the Names are case sensitive check box.

24

iBuilder User Guide

iDX Release 2.0

Using iBuilders Interface

6. In the Apply Sort to field, select the element to which you want to apply the Sort
feature.

Figure 30. Sort Preferences Dialog Box: Applying the Sort

You can apply the sort to any of the following elements:
Remote

Hub

Inroute Group

Spacecraft

QoS Profile

Component

Manufacturer

Operator

Distributor

7. Click OK. The next time you log in, iBuilder will remember and display the last sort
preference you chose.

2.8.3 Network Tree

The Network Tree is the primary navigation tool in iBuilder. It contains all of the elements of
your network, structured hierarchically. Each element in the tree contains a context-sensitive
menu accessible from your mouses context menu button (typically the right mouse button).
By right-clicking a tree element, a submenu of options appears, which you may click to use to
configure or view various types of data and other information used to operate your network.
For example, Teleport or Transponder appear in the submenus of Tree elements. For specific
information on these selections, see the section on that particular option. Use the Contents or
Index of this book to locate this information.
Most elements and entries in the Tree are necessary to operate the network. However, some
folders are provided simply to enable you to add informational entries for reference and

iBuilder User Guide

iDX Release 2.0

25

Using iBuilders Interface

record-keeping. These reference folders include the Manufacturers folder, Operators folder,
Distributors folder, and Customers folder.
A plus sign (+) next to an element or folder in the Tree indicates that additional elements,
folders, or informational entries exist below that level, or branch, of the Tree. Click the plus
sign (+) to expand, or collapse, the element or folder to view the next level of the Tree.

A minus sign (-) next to an element or folder indicates that the element or folder has been
completely expanded and has no other child entries below this level, or branch, in the Tree,
other than the children that are currently visible.
In Figure 31, the NMS Network has been expanded as far as possible. The Network cannot
include children in another network; therefore, its only children are the line cards and the
Inroute Group. The Inroute Group is a parent element that can be expanded by clicking its
plus sign (+) to reveal its children elements (remotes) at the next level of the Tree.

Figure 31. Fully-Expanded Network in the iBuilder Network Tree

In Figure 32, the QoS folder has been expanded as far as possible. The QoS folder cannot
include children in another folder on the same branch of the tree; therefore, its only children
are the Filter, Application, iSCPC and Group Profiles folders. These folders are parents to the
Downstream and Upstream folders that can be expanded by clicking their plus signs (+) to
reveal their children folders or elements below them in the Tree.

Figure 32. Fully-Expanded Folder in the iBuilder Network Tree

26

iBuilder User Guide

iDX Release 2.0

Using iBuilders Interface

2.8.4 Using the Interface Toolbars and Menu Options

Title Bar
The Title bar identifies the name of the application (in this case, iBuilder) and the IP address
of the server to which you are connected.

Figure 33. iBuilder Title Bar

Menu Bar
The Menu bar at the top of the display provides access to log in, log out, quit, and other highlevel functions.

Figure 34. iBuilder Menu Bar

Toolbar
The Toolbar, shown in Figure 35, contains context-sensitive buttons, allowing you to perform
a variety of operations on a currently-selected element without using its context menu. Their
functions are described in Table 1.

Figure 35. iBuilder Toolbar

Table 1. Toolbar Icons and Functions
Toolbar Icon

Function
Allows you to view elements in the Network Tree Menu hierarchy

Displays the Find dialog box

Opens the Modify Configuration dialog box of a highlighted parent element in the
Tree, allowing you to create a new child element for that parent. If the highlighted
element you select before clicking this button has no children elements, this icon will
become unselectable and is displayed in gray.
Allows you to add an element to the Tree. If the element in the Tree that is
highlighted before you click this icon does not have the capability to allow you to add
anything, the icon will become unselectable and be displayed in gray.
Allows you to view the properties of the highlighted element in the Tree in Read-Only
mode

iBuilder User Guide

iDX Release 2.0

27

Using iBuilders Interface

Table 1. Toolbar Icons and Functions (continued)

Toolbar Icon

Function
Allows you to view and edit the highlighted element in the Tree.

Allows you to delete a highlighted element in the Tree. You cannot delete parent
node elements if they have children (sub) elements.

Allows you to compare two configurations

Allows you to apply multiple configurations

Allows you to apply a TCP configuration

Allows you to retrieve the Active Configuration

Allows you to retrieve the Saved Configuration

Allows you to apply a TCP network configuration

Allows you to retrieve the Active Network Configuration

Allows you to retrieve the Saved Network Configuration

Allows you to download firmware images to remote modems and line cards

Allows you to perform a multicast package download

Allows you to accept any changes made to the system by another user. This does not
mean that you approve of or agree with the changes; it simply means that you are
accepting the fact that changes have been made since the time of your last login.
Allows you to view the version number of the NMS as well as system information

28

iBuilder User Guide

iDX Release 2.0

Using iBuilders Interface

Find Toolbar
The Find toolbar provides users the option to search the NMS for a given element and display
the results in either the Network Tree View or the Results Window. This becomes
increasingly important as the network grows larger. You can search by selecting a specific
element name in the first drop-down list (note that only elements you have created will be in
the list); by type of element in the second drop-down list; or by Name, IP address or ID
number in the third drop-down list. Figure 36 illustrates the various options within each
category.

Binoculars

Figure 36. Selecting Search Criteria on Find Toolbar

You can also click the Find button on the toolbar to open a dialog box that gives you the same
options.

Figure 37. Find Dialog Box

To perform a search, follow these steps:
1. Select View Find Toolbar, or click the Find button on the toolbar. Either the Find
toolbar appears to the right of the main toolbar, or the Find dialog box appears in the
Results pane.
2. Click the arrow on each drop-down list and click the criteria you want to use in your
search.
3. To execute the search, you can do one of three things:
Press Enter on the keyboard if you are searching from the Find toolbar.

iBuilder User Guide

iDX Release 2.0

29

Using iBuilders Interface

Click the Binoculars icon to the left of the toolbar if you are searching from the Find
toolbar.

Click Find Next if you are searching from the Find dialog box.

4. In the example below, the user chose to look for a Remote by the Name of X5 9944 and
display it in the Network Tree View.

That remote is highlighted in the Tree when the user clicks the binoculars icon on the
toolbar. (See Figure 36 on page 29.)

View Menu
The View menu on the main menu toolbar allows you to display or hide the following toolbars
and panes. You can also right-click in the main iBuilder window to see the same options as
those in the View menu. If you have clicked an element in the Tree, the Properties option is
available also.

Figure 38. iBuilder View Menu

30

iBuilder User Guide

iDX Release 2.0

Using iBuilders Interface

Status Bar
The Status bar is located at the bottom of the iBuilder window and displays the user name of
the person who is currently logged in and what their server connection status is. On the
toolbar shown in Figure 39, the connection status is Ready.

Figure 39. iBuilder Status Bar

Connection Details on Status Bar Icon

When your mouse hovers over the PC icon next to the user name on the Status bar, the IP
address of the NMS server that you are currently connected to is displayed.

Active Users Pane

The Active Users option and usage is discussed in more detail in Managing Accounts from the
Active Users Pane on page358. However, if you select View Active Users, the pane
displays a list of all defined users, along with their permissions, user groups, and current log
in status.

Figure 40. iBuilder Active Users Pane

Legend Pane
The Legend view displays the Configuration Status icons and their meanings. They are
organized by type of element as shown in Figure 41:

iBuilder User Guide

iDX Release 2.0

31

Using iBuilders Interface

Figure 41. iBuilder Legend Pane

32

iBuilder User Guide

iDX Release 2.0

Using iBuilders Interface

Configuration Changes Pane

If another user changes the database, or if you made a change that results in subsequent
changes that you should be aware of, the Accept Configuration Changes icon on your toolbar
becomes active.

Figure 42. Accept Configuration Changes Icon

If you want to view the changes in iBuilder before you click the icon to accept them, select
Configuration Changes from the View menu to display the Configuration Changes pane. You
can click the arrow to the left of each item to see more detail. Figure 43 shows the changes
that will appear if another user creates a new remote.

Figure 43. Configuration Changes Pane

Note that creating a single remote results in a number of separate objects being created:
antenna, remote, default VLAN, etc. When you click the Accept Configuration Changes Icon,
all entries will be cleared from the Configuration Changes Pane.

Configuration States
Configuration States are identified by both icons and color-coded words on either side of their
corresponding element in the network as shown in Figure 44. (Configuration Status is not the
same as Configuration State. Configuration Status is discussed in detail in Configuration

iBuilder User Guide

iDX Release 2.0

33

Using iBuilders Interface

Status of Elements on page44.) The legend details the meanings of the various icons and
color-coded words. (See Legend Pane on page31.)

Figure 44. Example of Configuration States

Properties View
The Properties view shows the properties of a highlighted element in the Tree, in Read-Only
mode. To view properties via the View menu, click an element in the Tree and select View
Properties, or simply double-click the element.

Details
The NMS is shipped with predefined sets of details that may be viewed for any given element
in the Tree. Different elements have different predefined details. To view the details of a
given elements children who reside at the next level down in the tree, select View
Details.

Figure 45. Selecting Details from the View Menu

The Details view allows you to sort, view and print a number of details, including the realtime states, of all or some of the elements under the parent node you have highlighted in the
Tree. For example, if you click a Network in the Tree, as shown in Figure 46, you can view the
details about that networks children (such as line cards and Inroute Groups) who reside on
the same level of the Tree, as shown in Figure 47. Notice that the remote in the Tree is not

34

iBuilder User Guide

iDX Release 2.0

Using iBuilders Interface

displayed in the Details view. You do not see, however, the details of the Network, itself. If
you want to view the Network details, you must select its parent in the Tree.

Figure 46. Network Highlighted in Tree

Figure 47. Result in Details View

To print a report of all the elements in the Details view, click anywhere in the Details view
and select File Print. You can print a portion of the view by using the Windows Explorer
style functionality to select any elements in the Details view (using the CTRL key and clicking
on individual elements, or using the Shift key to select a group of consecutive elements).
Once the desired elements are highlighted in the Details view, you can print a report of those
elements details by selecting File Print. (To customize the details you want in the report,
see Customizing Detail Views for Configuration Reporting on page36.)

Collapse Details Hierarchy + Details

In the preceding Details section, we learned that the Details option, when used alone,
allows you to view details about the children at the next level down from the parent you
highlight in the Tree but does not allow you to view any sub-elements beneath the children.
For example, if you click a Network in the Tree, you can view the details about that networks
children (such as line cards) who reside on the same level of the Tree, but you cannot view
details about the childrens sub-elements (such as remotes) which reside at the second level
down from the network you highlighted. Notice that the remote is displayed in the Details
view now.

Figure 48. Network Highlighted in Tree

Figure 49. Result in Details View

The Details + Collapse Details Hierarchy view collapses, or flattens, the hierarchy beneath a
highlighted element in the Tree so that you can view the details of all children elements at
every level of the Tree below the parent you selected. For example, if you click a Network in
the Tree, you can view the details about that networks children (such as line cards) who

iBuilder User Guide

iDX Release 2.0

35

Customizing and Creating New Detail Views

reside on the same level of the Tree, and you can view the details about the childrens subelements (such as remotes) which reside at the second level down from the network you
highlighted.
To view the details of all children elements at every level of the Tree below the parent you
selected, select View Details and View Collapse Details Hierarchy.

Choose Details
This option in the View menu allows you to modify the systems predetermined set of details
for any given element so that you can view only the details you need. For a detailed
description on using this feature, see Customizing Detail Views for Configuration Reporting
on page36.

2.9

Customizing and Creating New Detail Views

The NMS allows you to use not only the Details and Collapse Tree buttons to display
predefined details about a given highlighted element and its sub-elements, but it gives you
the ability to customize a Details display with any set of details or to create permanent new
detail views that you can use with any element in the system.

2.9.1 Customizing Detail Views for Configuration Reporting

As mentioned in Details on page34, the NMS is shipped with predefined sets of details that
may be viewed for any given element in the Tree. However, you can customize your Details
views for any element, using the advanced Choose Details feature.
To customize a Details view, follow these steps:
1. Click an element in the Tree for which you want to view details.

36

iBuilder User Guide

iDX Release 2.0

Customizing and Creating New Detail Views

2. Select View Choose Details from the Main Menu. The Choose Details dialog box is
displayed.

Figure 50. Choose Details Dialog Box

iBuilder User Guide

iDX Release 2.0

37

Customizing and Creating New Detail Views

3. Click the Select filter for Details list drop-down list in the Choose Details dialog box.

Figure 51. Selecting a Details Filter

4. Select one of the filters. Each filter offers a different set of details. For example, the
Carrier filter offers a list of all the predefined details that are viewable when you
highlight a carrier in the Tree and select Details from the View menu.
When you select a filter, the detail choices appear in the Choose Details dialog box, as
shown in Figure 52. Figure 52 on page 39 shows the details for Carrier.

38

iBuilder User Guide

iDX Release 2.0

Customizing and Creating New Detail Views

Figure 52. Choose Details Dialog Box for Carrier

5. From the list of available choices, click the details you want to view for the element you
have highlighted in the Tree.
a. Use the Show All button on this dialog box to select all of the details with one click.
b. Use the Move Up and Move Down buttons to arrange the details in the sequence in
which you want them to appear from left to right on the Details pane.

iBuilder User Guide

iDX Release 2.0

39

Customizing and Creating New Detail Views

c. Use the Hide All button to clear checkmarks from detail options you have already
checked.
6. When you are finished customizing the view, click OK to save the list of details for this
filter. The next time you open iBuilder, the last saved list of details for any given filter are
retained.
7. Now that the details in the Carrier view have been altered to include only these five
details, you can select any element in the Tree (the element may be a carrier or any other
element), and select View Details, and only the details you chose for the new Carrier
view will be displayed for that element.
8. In Figure 53, a carrier was selected in the tree. The user selected View Choose Details
Carrier OK. The user also selected View Details for this element. If these options
are selected, the following details on the selected carrier are displayed in the Details
view:

Figure 53. View Details for Carrier

9. If desired, you can now view Details or Details + Show All and print a report.

2.9.2 Creating Additional Filters for Customized Reporting

You can also create your own sets of details for generating and printing reports, using the
Choose Details feature. To create customized Detail or Details + Collapse Tree views, follow
these steps:
1. Select View Choose Details from the Main Menu. The Choose Details dialog box is
displayed. (See Figure 52 on page 39)
2. Select a list of details that you want to display in your Details view by clicking the arrow
in the Select filter for details list drop-down box at the bottom of the dialog box and
choosing a set of details from which to start.
3. Click the Plus (+) button to assign this custom filter a name. The Custom Report dialog
box is displayed. (Figure 54)

Figure 54. Adding a Custom Report

40

iBuilder User Guide

iDX Release 2.0

Customizing and Creating New Detail Views

4. Type a name into the field and click OK. When you add a filter, the buttons at the bottom
of the Choose Details pane change from.

to:
5. To modify the field selection for the filter, make the desired changes to the detail
selections for the filter and click the Modify button shown in Figure 55.

Figure 55. Custom Report Modify Button

6. When the message appears asking if you want to save the filter, enter a name for the
filter and click OK. A new filter is created.

7. To delete a filter, click the X button at the bottom of the Choose Details dialog box. A
message appears to confirm that you want to delete the filter.

Figure 56. Custom Report Delete Button

8. Click OK to delete the filter.
9. If desired, you can now view Details or Details + Collapse Details Hierarchy and print a
report.

iBuilder User Guide

iDX Release 2.0

41

Working with Multiple Elements Simultaneously

2.10 Working with Multiple Elements Simultaneously

The sections below describe how to modify parameters on multiple elements at the same
time and direct you to sections that describe how to work with multiple configurations and
Image files.

2.10.1 Working with Multiple Configurations and Image Files

In chapter 10, Retrieving and Applying Saved and Active Configurations see the following
sections:

Retrieving Configurations on page281

Applying Configuration Changes on page286

In chapter 11, Upgrading Software and Firmware see the following sections:

Multicast via UDP on page296

Downloading an Image to Remotes and Line Cards Concurrently on page296

Downloading an Image to Out of Network Remotes on page299

2.10.2 Modifying Parameters on Multiple Elements

The Group Edit feature allows you to modify parameters on multiple elements simultaneously
as long as the elements are all the same type. For example, you can modify parameters on
any number of Networks, or any number of Remotes, or any number of Receive Line Cards,
etc.

Rules for Group Edit

There are some rules and restrictions regarding the use of group editing:
1. You may select multiple elements only from the Details view. You cannot select multiple
elements from the Tree. Select View Details from the main menu to display the Details
pane.
2. All the elements you select must be of the same type. For example, elements to be
edited in a group must all be remotes or all be line cards, etc. You cannot edit a remote
and a line card in the same Group Edit.
3. You may only modify items in a group that have the same value, or have no value yet
assigned to them. For example, when editing a group of remotes, you may give them all
the same custom key or modify the custom key if they all have the same custom key
value. However, you will probably not be able to change the geographic location, because
this value is generally different on every remote in the group.

Procedure for Group Editing

To perform a Group Edit, follow these steps:
1. Select ViewDetails from the iBuilder Main Menu. The Details pane appears to the right
of the Tree.

42

iBuilder User Guide

iDX Release 2.0

Working with Multiple Elements Simultaneously

2. Select the element in the Tree that is the parent to the elements you want to change.
(For example, Inroute Group is the parent element for remotes.) The elements you want
to change appear in the list of elements in the Details pane.

Figure 57. Selecting the Parent Element for Group Editing

In Figure 57, changes will be made to the remotes in an Inroute Group. Therefore, the
Inroute Group has been selected as the parent element. The child elements (all remotes
in the Inroute Group) are displayed in the Details pane.
Note:

If you want to edit multiple elements that are not under the same parent, you
can select ViewCollapse Detail Hierarchy from the main menu and select your
Teleport in the iBuilder tree. All elements under the Teleport will appear in the
Details view. Click on the Type column in the Details pane to sort elements by
type. Then perform the remaining steps in this procedure.

3. Use the Control (CTRL) key or the Shift key on your keyboard to highlight the elements
you want to change. In the example in Figure 58, changes will be made to three remotes.

Figure 58. Selecting Multiple Elements for Group Editing

4. Right-click the Names of the highlighted elements in the Details pane and select Modify
to open the Configuration dialog box for those elements.
5. Make the changes you want to apply to all of the selected elements, and click OK. The
changes are saved in the database.

iBuilder User Guide

iDX Release 2.0

43

Configuration Status of Elements

2.11 Configuration Status of Elements

Central to the operation of iDirects NMS is the concept of configuration state.
Configuration states represent elements of the network in terms of their condition. This
section describes the concept of configuration state and what it means for both iBuilder and
iMonitor.

2.11.1 What is a Configuration State?

iBuilder divides the configuration process into three steps:
1. Make your changes to the database;
2. Review those changes by selecting Compare Configuration on the element you are
changing (this step is optional but recommended), and if necessary, make any necessary
modifications
3. Once youre satisfied with the changes, make them active in the network by applying
them to the components that you changed via the Apply Configuration or a multicast
download feature
This three-step change process gives the network operator ultimate control over operational
network components, because no change takes place without the operator initiating it.
However, it creates a situation where the NMS database is temporarily out-of-sync with the
actual network. This occurs after the operator has made database modifications, but before
they have been applied to the network.
To help operators easily manage this situation and others like it, iDirect implements the
concept of configuration state. Configuration states show the current configuration status of
key components of the network: Hub Chassis, individual networks, line cards, and remote
modems.
Using a specific modification as an example, we can see how configuration state changes over
time:
1. Remote r_123 is configured, commissioned, and all previous changes have been
applied. Its configuration state is Nominal.
2. User changes the upstream QOS settings for remote r_123.
3. The configuration state for r_123 becomes Changes Pending.
4. User reviews the changes, determines they are correct, and then applies them to the
remote.
5. The configuration state for r_123 returns to Nominal.
Note:

Remote and line card configuration state returns to Nominal immediately

after a new configuration file is applied; iBuilder does not attempt to track
whether or not the modem was reset. Please ensure you reset remote modems
or line cards to activate your changes.

2.11.2 Possible Configuration States

The following table lists all of iBuilders configuration states and the network elements to
which they apply. See also:

44

iBuilder User Guide

iDX Release 2.0

Configuration Status of Elements

Legend Pane on page31

Configuration Changes Pane on page33

Configuration States on page33

Table 2. Configuration States

Configuration
State
Nominal

Network
Element
Network
Chassis

Definition
The element is completely configured, is alive in the network,
and there are no unapplied changes.

Line Card
Remote
Inroute Group
Protocol
Processor
SkyMonitor
Changes
Pending

Network
Chassis
Line Card

The element is completely configured and is alive in the

network. There are changes in the database that have not
been applied.

Remote
Protocol
Processor
Incomplete

Network
Chassis
Line Card

The element is only partially configured; one or more key

components of the configuration are unspecified (e.g. carriers,
IP address, serial number)

Remote
Inroute Group
Protocol
Processor
Never Applied

Network
Chassis

The element is completely configured but the configuration

has never been applied to the element.

Line Card
Remote
Protocol
Processor
Deactivated

Remote
Line Card

The element was at one time active in the network, but it has
been deactivated.

Network

iBuilder User Guide

iDX Release 2.0

45

Configuration Status of Elements

2.11.3 Configuration State Transition

The following diagram illustrates typical state transition for a remote modem in iBuilder from
creation to steady-state.

Figure 59. Configuration States of an iDirect Remote

An explanation of all configuration states for all elements, their meaning, and their
respective icons is available in iBuilder by selecting View Legend from the main menu.

2.11.4 Viewing Configuration States

Configuration states are displayed in iBuilders network Tree. Each network element in the
tree shows its current configuration state with these icons. You can also view the
configuration state as color-coded words next to the corresponding element by selecting View
Configuration Status from iBuilders main menu.
See also Configuration Changes Pane on page33 and Configuration States on page33.

2.11.5 Why Did My Configuration States Change?

Configuration states can change for a variety of reasons, including:

46

You changed configuration. Whenever you change the configuration, the Changes
Pending icon appears beside all affected network elements.

Someone else changed configuration. iBuilder supports multiple simultaneous logins. If

another user changes configuration, your network tree icons will change to reflect the
current configuration state.

Someone changed a modems configuration directly. When a modem comes into the
network, the configuration server uploads the active configuration from the remote and
re-calculates configuration state. If this configuration is different from the latest iBuilder
configuration, you will see the Changes Pending icon for that modem. This can happen if
someone changes a modems configuration from the console or the iSite utility. This
potentially dangerous situation is flagged by the configuration state.

iBuilder User Guide

iDX Release 2.0

Understanding the Databases Numbering Convention

You installed a new version of the Configuration Server. When the configuration server
starts up, it re-generates the configuration files for all networks, hubs, and remotes. The
new server may generate additions, deletions, or changes to the configuration files. If so,
all affected elements will display the Changes Pending icon after the new server starts
up.

2.11.6 Configuration States and iMonitor

Configuration states are shown in iMonitor in the following circumstances:

When a Chassis, Network, Hub, or Remote is Incomplete, iMonitor displays the

Incomplete icon.

When a remote modem is Deactivated or Never Applied, iMonitor shows the

deactivated icon. In this case historical requests may still be made, since a deactivated
remote may have archived data.

When a remote modem is either Nominal or Changes Pending, iMonitors real-time

state icons take over, so you will see either the OK, Warning, or Alarm icon depending on
the real-time status of the modem.

An explanation of the configuration states, their meaning, and their respective icons is
available in iMonitor by selecting View Legend from the main menu.

2.11.7 Accepting Configuration Changes and Locking the

Database
For a discussion on how to accept changes made by others to the database, see Multiple
Users or PCs Accessing the NMS on page13. For the steps to unlock the database in the event
that someone makes changes and forgets to log out, see NMS Database Locking on
page363.

2.12 Understanding the Databases Numbering

Convention
When an element in the Tree is created, a sequenced number is assigned to that element by
the database, and The new component or element appears in the Tree at the bottom of the
list of like-elements on its branch level in the tree. In Figure 60, a user has right-clicked on
the Globe to create a new Teleport. The Modify Configuration dialog box is displayed with
New Teleport #12 in the Name box, and at the bottom of the teleports level in the Tree, a
Teleport is automatically displayed with the same name. When you change the name on the
Modify Configuration dialog box and save it by clicking OK, the name of the teleport in the
Tree will also change.
When you exit iBuilder and log back in, the teleport will move from the bottom of the Tree to
the bottom of the list of teleports. In the example below, we named the new teleport
Dulles. Notice that the teleport names are not sorted alphabetically.
The NMS database assigned a system-generated number to each element when it is created.
The first teleport is assigned the number 1. The second teleport is assigned the number 2,
and so on. The same number assignment takes place with every element created in the tree.
Therefore, the first spacecraft would be named New Spacecraft #1, and so on. This number

iBuilder User Guide

iDX Release 2.0

47

Understanding the Databases Numbering Convention

is always associated with its original element. This is how the database keeps track of the
elements and the configurations and management control associated with it as long as it
exists in the Tree. If an element is deleted, the numbers of the elements created after it do
not change numbers. For example, if you have five teleports and teleport number 3 is
deleted, teleport number 4 does not become teleport number 3. Teleport number 4 remains
teleport 4 forever. If a sixth teleport is created, it becomes teleport number 6, not number 3.

Figure 60. New Teleport with System-Generated Number

48

iBuilder User Guide

iDX Release 2.0

Viewing the Activity Log

2.13 Viewing the Activity Log

iBuilder Users with the Manage Users permission (see page 362) can view the NMS Activity Log
by selecting the View Activity Log option from the View menu. The Activity Log shows the
time and details of iBuilder and iMonitor user activities (such as database modifications, user
logins, etc.) as well as activities such as modem resets and configuration uploads. A partial
list of Activities that can be displayed are show in Figure 61.

Figure 61. Partial List of Activities Displayed in the Activity Log

Follow these steps to view the Activity Log:
1. Select View Activity Log from the iBuilder View Menu to display the Activity Log dialog
box.

The Activity Log dialog box opens. (Figure 62)

iBuilder User Guide

iDX Release 2.0

49

Viewing the Activity Log

Figure 62. Activity Log Dialog Box

2. In the Activity Log dialog box, enter a Start Time and an End Time. The Duration will be
calculated by iBuilder. (You can also use the slider to adjust Duration, which represents
the offset between the Start Time and the End Time. When you adjust the Duration with
the slider, the End Time is automatically updated.)
Note:

If f desired, you can set the times by clicking the ellipsis buttons to the right of
Start Time and End Time to launch the clock display. Click the hour or minute
hand to select it. Then click the clock numbers to move the hand you selected.

Figure 63. Ellipsis Button and Graphical Clock Display

3. In the Activity Name area of the dialog box, select all activities you want to view. (You
can use the Select All and Clear All buttons to select or clear all activities.)
4. Click the Show Log button to display the activities in the List of Activities pane. (You can
also click this button to refresh the display with recent activities if your End Time is set
to a future time.)

50

iBuilder User Guide

iDX Release 2.0

Configuring Warning Properties

5. When viewing Activities, if the Activity Type is applied configuration, then the Details
column will contain a hyperlink to the options file that was applied. You can click the
hyperlink to view the options file in Notepad.

Figure 64. Opening an Options File from the Activity Log

6. As with other multicolumn lists in iMonitor and iBuilder, you can copy and paste multiple
rows from the Activity Log List of Activities into another Windows application such as
Excel for further analysis:
a. Select the data you want to copy. (Click to select a single row. Shift-click to select a
range of rows. Ctrl-click to select multiple, individual rows.)
b. Right-click in the window and select Copy or Copy without headers from the menu to
copy the data.

Figure 65. Copying Multiple Rows from the Activity Log

c. Paste the data into the Windows application.

2.14 Configuring Warning Properties

Warnings that indicate anomalous conditions on your iDirect equipment are generated by the
iDirect network and displayed in iMonitor. You can configure the properties that determine
how individual warnings are generated for the following network elements:

Line cards

Remotes

Protocol processors

iBuilder User Guide

iDX Release 2.0

51

Configuring Warning Properties

There are two categories of warnings:

Limit-based warnings are generated when either the high or low limit defined for the
warning is violated. A warnings range can specify a low limit, a high limit or both.

Boolean warnings have two states: the warning is either off or on. A boolean warning is
generated when the value being monitored by the warning changes from the nominal
state to the anomalous state. For example, if a line card loses the chassis backplane 10
MHz timing signal, then the BackplaneLost10MHz warning is generated for the line card.

You can perform the following operation when configuring warning properties:

Enable or disable a warning.

Set the upper and lower limits that determine when certain warnings are generated.
(Limit-based warnings only.)

Configure a warning to be generated only when a limit is violated, or to be generated

each time a value changes when outside the normal operating range. (Limit-based
warnings only.)

All warning modifications are processed dynamically; you do not need to restart any NMS
processes for the warning changes to take effect. For example, if you disable a warning all
currently active warnings of this type will clear in iMonitor. Similarly if you modify a limit such
that some active warnings now fall in the normal range, those warnings are automatically
cleared.
Note:

When upgrading from a pre-7.0 release, the installation drops your current
warning definitions from the database and recreates them. If you have custom
limits defined in your network, you must redefine them after your upgrade.

You can use iBuilder to modify both global properties of warnings and warning properties for
individual network elements. When you customize a warning for an individual element, the
new setting overrides the global setting. Changes to global warning settings apply only to
those elements that do not have their settings customized on an individual basis.
The behavior of the system with regard to global properties and individual overrides is as
follows:

52

A warning whose properties have not been modified for an individual element uses the
global properties for that warning. In the event that the global properties of the warning
are modified, the new global properties will be used by the element.

A warning whose properties have been modified for an individual element uses the
customized properties for that warning for that element. Changes to the global properties
of the warning have no effect on the warning properties configured for that element; the
element will continue to use the modified properties.

When a warning that has been modified for an individual element is reset for that
element, any properties that were previously modified for the warning take on the
current, global values.

iBuilder User Guide

iDX Release 2.0

Configuring Warning Properties

2.14.1 Setting Global Warning Properties

Global warning properties are configured from iBuilders Edit menu.
To set global warning properties for your line cards, remotes or blades, follow these steps:
1. Click the Edit menu and select Global Warnings for the element type. In this example,
Global Warning for Linecards is selected from the menu.

The Modify Global Warning dialog box appears with all warnings appropriate to the
selected network element type.

Figure 66. Modify Global Warning Dialog Box

2. Select the Warning Type for the warning you want to modify and click the Edit button.

iBuilder User Guide

iDX Release 2.0

53

Configuring Warning Properties

3. Enter the new settings in the Modify Warning dialog box and click OK to save the
changes.

Figure 67. Modify Warning Dialog Box

You can modify the following parameters:

The Limit Value setting determines the high or low limit of the normal range of values for
the network parameter being monitored. When this limit is crossed, a warning is
generated. You can only set the Limit Type for limit-based warnings. This field does not
apply to boolean warnings.

The Send Value Change setting determines whether or not the warning will be generated
each time a value changes while that value is outside normal operating limits. If the
check box is selected, a new warning will be generated each time the abnormal value
changes. If the check box is cleared, a warning will be generated the first time an
abnormal value is detected, but not if the abnormal value changes. You can only set the
Send Value Change property for limit-based warnings. This field does not apply to
boolean warnings.

The Enabled setting enables or disables the warning. If you clear this check box, the
warning will not be generated.

Note:

54

Changes to global warning settings do not affect warnings that have been
customized on the Warning Properties tab. You must reset the customized
warning to return to the global settings. (See Clearing Customized Warning
Properties on page55.)

iBuilder User Guide

iDX Release 2.0

Configuring Warning Properties

2.14.2 Customizing Warning Properties for Individual Network

Elements
To customize warning properties for individual network elements, follow these steps:
1. Right-click the network element in the network tree and select the appropriate Modify
option from the context menu.
2. When the dialog box for the network element appears, click the Warning Properties tab.

Figure 68. Warning Properties Tab

3. Select the Warning Type for the warning you want to reconfigure and click the Edit
button.
4. Follow the procedure beginning with Step 2 in Setting Global Warning Properties on
page53 to reconfigure the warning properties.
Warnings that have been customized are highlighted in bold text on the Warning Properties
tab. In the example, the BackplaneLost10MHz warning has been disabled for this specific line
card.
Note:

Customized warning settings configured on the Warning Properties tab apply

only to the individual element being modified. These settings override the
global settings for the element being reconfigured. (For more details see
Configuring Warning Properties on page51.)

2.14.3 Clearing Customized Warning Properties

When you set warning properties on an elements Warning Properties tab, the customized
settings override the global settings for that element until you clear the customized settings.
To clear the customized settings for a warning and return the warning to the global settings,
follow these steps:
1. Right-click the network element in the network tree and select the appropriate Modify
option from the context menu.

iBuilder User Guide

iDX Release 2.0

55

Managing NMS Licenses

2. When the dialog box for the element appears, click the Warning Properties tab.
3. Select the warning for which you want to clear the customized settings. (Warnings with
customized settings are highlighted in bold text.) Then click the Reset button at the
bottom of the screen. The following dialog box appears:

4. Click OK in the dialog box. Then click OK on the Warning Properties tab. The warning
that you reset will be reconfigured with the global settings.

2.15 Managing NMS Licenses

Beginning with iDX Release 2.0, you must license your chassis slots and certain features to
enable their configuration in iBuilder. In addition to requiring chassis slots to be licensed,
iBuilder requires licenses for the following features:

Evolution X3 Link Encryption

Evolution X5 Link Encryption

Evolution X5 Upstream Spread Spectrum

XLC-11 Upstream Spread Spectrum

XLC-11 Downstream Spread Spectrum

When you license your chassis slots or any of the features listed above, iDirect will send you a
license file. Using the iBuilder License Toolbar, you must then import the license file to enable
the configuration of the chassis or feature on the iBuilder GUI.
This section describes how to import licenses once you have received your license file from
iDirect. It also describes how to generate a file that you can use to request feature licenses
for your existing hardware. For more details on requesting and receiving licenses from iDirect,
see the iDirect Features and Chassis Licensing Guide.
You need to use the iBuilder License Toolbar to perform the procedures in this section. To
display the License Toolbar, select License Toolbar from the iBuilder View menu. The License
Toolbar consists of the two icons show in Figure 69: one for importing license files; the other
for exporting license data.

Figure 69. Viewing the iBuilder License Toolbar

56

iBuilder User Guide

iDX Release 2.0

Managing NMS Licenses

2.15.1 Importing Your License Files

This section describes how to import your feature licenses and chassis licenses.
By default, you cannot import a chassis license file without first connecting to the NMS
Chassis Manager server and enabling the download permission. (See Step 1 below.) However,
you can permanently enable download to the Chassis Manager by following the steps in
Permanently Enabling Chassis License Download on page62. If you permanently enable
download to the Chassis Manager, you do not need to execute Step 1 and Step 7 of the below
procedure when importing a chassis license file.
Follow these steps to import a license file that you received from iDirect:
1. Only perform Step a through Step d if you are importing a chassis license file:
a. Open a terminal window on your PC.
b. Enter the command:
telnet <ip address> 15262
where <ip address> is the IP address of the server running the NMS chassis
manager process.
c. At the Username prompt, log on to the chassis manager admin account. (The default
password is iDirect. You should change this password.)
d. Enter the command:
download on
These steps are illustrated in Figure 70.

Figure 70. Enabling Chassis License Download to Chassis Manager

Note:

iBuilder User Guide

iDX Release 2.0

To permanently enable license download to the Chassis Manager, follow the

procedure in Permanently Enabling Chassis License Download on page62. If
you permanently enable license download, you do not need to execute Step 1
and Step 7 of this procedure when importing a chassis license file.

57

Managing NMS Licenses

2. Click the Import license files button on the iBuilder License Toolbar (Figure 69) to open
the Select License Type dialog box.

Figure 71. Select License Type Dialog Box

3. Select either Feature License or Chassis License and click OK.
4. In the Choose License Files dialog box, navigate to the folder containing the license file
you received from iDirect and select the license file.

Figure 72. Selecting a License File for Import

5. Click the Open button to import the license file.
6. Once the licenses are imported, you will see a message indicating that the licenses have
been successfully downloaded. Click OK.

58

iBuilder User Guide

iDX Release 2.0

Managing NMS Licenses

7. If you imported a chassis license file, you should disable download on the chassis manager
as follows:
a. From the terminal window that you opened in Step 1, enter the following commands:
download off
update
b. Exit the telnet session.
8. Click the Accept Changes icon on the iBuilder main toolbar.

Figure 73. Accepting Changes Importing a License File

2.15.2 License Properties Tabs

Hardware elements that have optional feature licenses have a License Properties tab on
their iBuilder configuration screens. For example, line card and remote configuration screens
have License Properties tab, since features can be licensed for these elements. Once you
have imported a feature license file, the licensed features appear on the License Properties
tab of the licensed hardware.
Note:

Chassis configuration screens do not have a License Properties tab.

Figure 74 shows an example of a License Properties tab for an Evolution X5 remote.

Figure 74. License Properties Tab

Notice that the remote has been licensed for Inbound Spread Spectrum and Link Encryption.
(A Value of 1 indicates that the license has been enabled.) If you have not loaded any licenses
for an element, the License Properties tab is blank.

2.15.3 Exporting iBuilder Data for Licensing

When you request licenses from iDirect, you must include certain information in your request.
To license a feature on your individual hardware elements (such as remotes or line cards),
iDirect requires the following information for each unit:

Hardware Model Type

Serial Number

Derived ID (DID)

iBuilder User Guide

iDX Release 2.0

59

Managing NMS Licenses

Note:

For details on requesting licenses from iDirect, see the iDirect Features and
Chassis Licensing Guide.

If you are requesting licenses for a large number of existing hardware elements, it can be
tedious and error-prone to record the Serial Number and DID of all units. Therefore, iBuilder
provides an automated method to generate a Comma Separated Values (CSV) file of Serial
Numbers, DIDs and Model Types for the elements you want to license.
To export data for feature licenses from iBuilder:
1. Select a parent element in the iBuilder tree that contains all of the hardware units you
want to license.
2. Once you have selected the parent element, click the Export Data for Licensing button
on the iBuilder Licensing Toolbar.

Figure 75. Selecting Export Data for Licensing on License Toolbar

In Figure 75, Network 8 was selected in the iBuilder Tree before clicking the Export Data
for Licensing button. Once you click the Export Data for Licensing button, the Data for
Licensing dialog box appears.

Figure 76. Selecting Data for Licensing

60

iBuilder User Guide

iDX Release 2.0

Managing NMS Licenses

3. In the Data for Licensing, select all units for which you want to request a license. (See
page 56 for a list of features that you can license in this release.)
4. Click the Save to File button to display the Save As dialog box.

Figure 77. Saving Data for License Request

5. Navigate to the folder on your PC where you want to save the CSV file and click the Save
button.
Figure 78 shows an example of a license request CSV file opened in Microsoft Excel. You can
include this information in your license request to iDirect.

Figure 78. Sample License Request CSV file

iBuilder User Guide

iDX Release 2.0

61

Managing NMS Licenses

2.15.4 Permanently Enabling Chassis License Download

By default, you cannot import a chassis license file without first connecting to the NMS
Chassis Manager and enabling the download permission. (This procedure is described in Step 1
of Importing Your License Files on page57.) This security feature guards against accidental
or malicious download of an incorrect chassis license file. However, if desired, you can
permanently enable license download to the Chassis Manager by following these steps:
1. Using a Secure Shell (SSH) client such as PuTTY, log on to the root account of your NMS
server machine that is running the Chassis Manager.
2. Change to the Chassis Manager directory by entering the command:
cd /home/nms/cm
3. Edit the file para_cfg.opt.
4. Add the following line at the beginning of the file:
[DOWNLOAD]
enable = 1
This change to para_cfg.opt is illustrated in Figure 79.

Figure 79. para_cfg.opt with Chassis License Download Enabled

5. Save the file and exit the editor.
6. Enter the command:
telnet <ip address> 15262
where <ip address> is the IP address of the server running the NMS chassis manager
process.
7. At the Username prompt, log on to the chassis manager admin account. (The default
password is iDirect. You should change this password.)
8. Update the Chassis Manager with the new configuration by entering the command:
update
9. Return to the NMS server machine by entering the command:
exit
10. Log off of the NMS server machine.
License download to the Chassis Manager is now permanently enabled, even if the Chassis
Manager server process restarts.

62

iBuilder User Guide

iDX Release 2.0

In Color versus Shaded Icons

2.16 In Color versus Shaded Icons

If an icon next to a component (such as a user, QoS profile, BUC, LNB, Converters, etc.) in the
Tree is in color, it indicates that component is being used somewhere in the network.
Therefore, if you perform any configuration or control functions on that element, it will
affect other elements in the network. If you modify the element, a message is displayed
warning you that if you make changes to this element, any other element in the database that
is using it will be changed also. As long as the icon is in color, you cannot delete the element.
If the icon next to an element in the Tree is unavailable and displayed in gray, you can make
modifications without it affecting other elements in the network.

iBuilder User Guide

iDX Release 2.0

63

In Color versus Shaded Icons

64

iBuilder User Guide

iDX Release 2.0

Preparing the Hub RFT Components Folders

3 Defining Hub RFT

Components and the
Satellite

A spacecraft must exist in the iBuilder Tree before the Hub RFT (Radio Frequency Terminal)
can be defined. However, before you define the spacecraft, you may define the other Hub
RFT sub-components. Steps for configuring the satellite and its Hub RFT sub-components are
contained in the following sections:

3.1

Preparing the Hub RFT Components Folders on page65

Adding a Spacecraft on page69

Adding a Transponder on page70

Adding Bandwidth on page71

Adding Carriers on page72

Preparing the Hub RFT Components Folders

In order to configure the HUB RFT, you must select certain pre-defined subcomponents for
each field in the HUB RFT configuration dialog box. When you expand the HUB RFT folder, you
will see the subcomponent folders listed below. These subcomponents have been previously
configured and contain critical settings used to establish the Hub RFT operational parameters.

Antenna

Up Converter

Down Converter

High Power Amplifier (HPA)

You should add entries to these folders in advance and define the parameters of the
components you add so that the appropriate information is in the drop-down lists on the Hub
RFT configuration dialog box. The procedures in this section explain how to configure these
sub-components.

iBuilder User Guide

iDX Release 2.0

65

Preparing the Hub RFT Components Folders

3.1.1 Adding an Antenna

Follow these steps to add an Antenna to the Hub RFT Components folder.
1. Under the Hub RFT Components folder, right-click the Antenna folder and select Add
Antenna.

The new antenna appears in the Tree with a system-generated generic name, and a dialog
box appears allowing you to define its parameters.

Figure 80. New Antenna Dialog Box

2. If desired, select a Manufacturer from the drop-down list. Items in this list were either
pre-defined or they were added when you populated the folder earlier. See Adding
Entries to Folders on page18.
3. In Manufacturer Part Number, enter a part number or name for the antenna. This field is
used to select the antenna when you configure your HUB RFT.
4. If desired, enter an iDirect Part Number for the antenna. You may enter any information
you like in this field, or leave it blank.
5. Click OK. The new antenna appears in the Tree under the antenna folder.
6. If you have more than one antenna, repeat this procedure and assign the new antenna a
different name.

66

iBuilder User Guide

iDX Release 2.0

Preparing the Hub RFT Components Folders

3.1.2 Adding an Up Converter or Down Converter

Follow the steps in this section to add an Up Converter or Down Converter to the Hub RFT
Components folder.
Note:

Be sure to enter the correct frequency translation values for all of your Up
Converters and Down Converters. The NMS will use these values later to
generate network configurations.

1. Under the Hub RFT Components folder in the Tree, right-click the Up Converter or Down
Converter folder, and select Add Up Converter or Add Down Converter.

The new up converter or down converter appears in the Tree with a system-generated
generic name, and a dialog box appears allowing you to define its parameters. Figure 81
shows an Up Converter being added. The procedure is the same for adding a Down
Converter.

Figure 81. New Up Converter Dialog Box

2. In Manufacturer Part Number, enter a part number or name for the Up Converter. You
may enter any information you like in this field, or leave it blank.
3. You must enter a frequency in MHz in the Frequency Translation field. This information is
provided on the specifications sheet for the Up Converter.
4. You may select a Manufacturer for the Up Converter (optional).

iBuilder User Guide

iDX Release 2.0

67

Preparing the Hub RFT Components Folders

5. Enter an iDirect Part Number for the Up Converter (optional). You may enter any
information you like in this field.
6. You must select ODU Tx DC Power and ODU Tx 10 MHz if you require the iDirect modem
to supply DC power and the 10 MHz clock. These settings are applicable only if you are
operating a small teleport whose BUC and LNB are not built into the antenna.
Note:

Older iDirect chassis and line cards do not provide these capabilities; private
hubs, mini hubs and remote modems have these capabilities built into them.
Four-slot chassis with newer line cards support these functions but require
additional configuration on the four-slot chassis screen. See Configuring a
Four-Slot Chassis on page255 for details.

7. Leave Spectral Inversion at Normal unless you are using C-band. If the local oscillator is
higher in frequency than the one being transmitted or received, then the spectrum must
be inverted.
8. Click OK. The new Up Converter appears in the Tree under the Up Converter folder.
9. If you have more than one Up Converter, repeat this procedure and assign it a different
name.
10. Repeat these steps for all of the Down Converters at your teleport.

3.1.3 Adding a High Power Amplifier (HPA)

Follow the steps in this section to add a High Power Amplifier (HPA) to the Hub RFT
Components folder.
1. Under the Hub RFT Components folder in the Tree, right-click the HPA folder, and select
Add HPA.

The new HPA appears in the Tree with a system-generated generic name, and a dialog box
appears allowing you to define its parameters.

Figure 82. New HPA Dialog Box

68

iBuilder User Guide

iDX Release 2.0

Adding a Spacecraft

2. In Manufacturer Part Number, enter a part number or name for the HPA, or use the
system-generated generic name.
3. You may select a Manufacturer for the HPA (optional).
4. You may enter an iDirect Part Number for the HPA (optional). You may enter any
information you like in this field, or leave it blank.
5. Click OK. The new HPA appears in the Tree under the HPA folder.
6. If you have more than one HPA, complete this procedure again and assign it a different
name.

3.2

Adding a Spacecraft
1. To create a Spacecraft, right-click the Spacecraft folder and select Add Spacecraft.

A new spacecraft appears in the Tree with a system-generated generic name, and a dialog
box appears allowing you to define its parameters.

Figure 83. New Spacecraft Dialog Box

2. Select the name of the Operator (normally the service provider, assuming that your
company is not the provider). Optionally, you can click the Operator drop-down box to
view a list of operators you have entered into the NMS, and select one of them.

iBuilder User Guide

iDX Release 2.0

69

Adding a Transponder

3. In Spacecraft Name, enter a name for the spacecraft.

4. Enter an Operator Reference Name. (Optional)
5. Enter the exact Longitude (between 0 and 180 degrees) of the satellite. This information
can be obtained from your satellite service provider.
6. To the right of the Longitude box, select the Hemisphere: E (East) or W (West).
7. Enter the Orbital Inclination. This is necessary only if the satellite is experiencing
instability or is coming to the end of its life cycle, in which case the satellite provider will
provide you with the orbital inclination.
8. The Minimum Look Angle is applicable to mobile remote antennas. The Minimum Look
Angle configured here is used by all mobile remotes that do not have this setting
overridden on the Remote Geo Location tab. (See Remote Geo Location Tab on
page167.)
9. Maximum Skew represents the maximum angle of skew that a mobile remotes antenna
can tolerate before it stops transmitting. The Maximum Skew configured here is used by
all mobile remotes that do not have this setting overridden on the Remote Geo Location
tab. (See Remote Geo Location Tab on page167.)
10. A satellite with horizontal or vertical polarization may be skewed with respect to its
orbit. In Skew Polarization, enter the amount of skew of the spacecraft in degrees. Valid
values range from -45.0o to +45.0o.
11. Click OK. The spacecraft appears in Tree under the Spacecraft folder.

3.3

Adding a Transponder
A satellite transponder receives the carriers on the uplink frequencies and re-transmits them
on the downlink frequencies. Once you have configured the transponder, you can add
bandwidth regions, which consists of one or more upstream and downstream carriers.
To define a transponder, you must first have a spacecraft defined in the Tree. Follow these
steps to add a transponder:
1. Right-click your Spacecraft and select Add Transponder.

The new transponder appears in the Tree with a system-generated generic name, and a
dialog box appears allowing you to define its basic parameters.

70

iBuilder User Guide

iDX Release 2.0

Adding Bandwidth

Figure 84. Hub Transponder Dialog Box

2. In Operator Reference Name, enter a name for the transponder to identify it in the Tree.
3. You must enter the Translation Frequency. This information can be obtained from your
satellite provider. The frequency, in MHz, is transponder specific. It is that frequency used
to down convert the radio frequency (RF) uplink to the RF downlink for retransmission
from the satellite. This information must be correct for your networks to function
correctly.
4. Enter the information for the remaining fields, which can also be obtained from your
service provider. This information is for reference purposes only.
5. Click OK. A transponder appears in the Tree.

3.4

Adding Bandwidth
A bandwidth region defines a specific portion of the satellites transponder within which you
can define transmit and receive bandwidth carriers. You must define at least one bandwidth

iBuilder User Guide

iDX Release 2.0

71

Adding Carriers

region for each transponder in order to create carriers. To add and define a bandwidth region,
follow these steps:
1. Right-click the transponder and select Add Bandwidth.

The new bandwidth entry appears in the Tree with a system-generated generic name, and
a dialog box appears allowing you to define its basic parameters.

Figure 85. New Bandwidth Dialog Box

2. On the Information tab, in the Operator Reference Name box, enter a name to identify
the bandwidth in the Tree.
3. Enter the Center Frequency, Bandwidth, and Power values, which can be obtained from
your service provider. This information is for reference purposes only.
4. Click OK. A bandwidth entry appears in the Tree.

3.5

Adding Carriers
Each upstream carrier defined becomes available for assignment to a line card once
configured. They are made available for selection for the line card configuration only after
selecting the associated Hub RFT and its assigned spacecraft.

72

iBuilder User Guide

iDX Release 2.0

Adding Carriers

3.5.1 Adding Downstream Carriers

Each Network may have only one active Downstream (Outbound) Carrier. (You can also
configure an Alternate Downstream Carrier to facilitate changing to a new carrier. See
page 106.) The information for creating a carrier should be obtained from your satellite
provider, as it is part of the satellite link budget process.
iDX Release 2.0 supports both SCPC and DVB-S2 downstream carriers. A DVB-S2 capable line
card is required to transmit a DVB-S2 downstream carrier.
In addition to providing the outbound carrier for a network of TDMA remotes, a dedicated
downstream carrier can be used to send data on a point-to-point connection from an iSCPC
line card at the hub to a single iSCPC remote. In that case, the iSCPC remote transmits back
to the hub on an iSCPC upstream carrier. (For details, see Adding Upstream SCPC Carriers
on page79.)
Note:

iSCPC is not supported in iDX Release 2.0.

Note:

When using a downstream SCPC carrier for iSCPC operation, the transmit power
is based on the SCPC line card configuration, not on the downstream carrier
configuration. For further information, please see Adding an iSCPC Line Card
on page113.

To add a downstream carrier, follow these steps:

1. Right-click the bandwidth for your transponder and select Add Downstream Carrier.

iBuilder User Guide

iDX Release 2.0

73

Adding Carriers

The new carrier appears in the iBuilder tree with a system-generated generic name, and a
dialog box appears allowing you to define its basic parameters.

Figure 86. New Downstream Carrier Dialog Box

Figure 86 shows the configuration of a DVB-S2 downstream carrier. The type of
downstream carrier (DVB-S2 or SCPC) is determined by the selection that you make for
Modulation. Selecting ACM indicates that this is a DVB-S2 carrier. Any other modulation
indicates an SCPC carrier.
Note: iDX Release 2.0 does not support CCM. However, you can simulate CCM by
selecting the same Minimum MODCOD and Maximum MODCOD. You must also
adjust your DVB-S2 network parameters as described in Adjusting DVB-S2
Parameters for CCM Networks on page138.
2. Enter a Name for the downstream carrier.
3. Enter the Uplink Center Frequency. This frequency assignment is provided as part of the
satellite link budget process and comes from the satellite provider.
4. The Downlink Center Frequency is automatically calculated when you click in the
Downlink Center Freq box, based on the previous transponder translation frequency.
5. In Power, enter a value for the transmit power. The default is -25 dBm.
6. Carrier Spacing is an optional field that you can use to document the total width of your
carriers. It represents the distance between two adjacent and identical carriers measured

74

iBuilder User Guide

iDX Release 2.0

Adding Carriers

from center to center and normalized by the symbol rate. For more information, see the
chapter titled Carrier Bandwidth Optimization in the iDirect Technical Reference
Guide.
7. Select the Modulation for your carrier. You can select ACM (Adaptive Coding and
Modulation) if you are configuring a DVB-S2 downstream carrier. You can select BPSK,
QPSK or 8PSK if you are configuring an SCPC downstream carrier.
8. If you are configuring a DVB-S2 carrier, the DVB-S2 Range parameters appear on the
screen. To configure these fields:
a. Select both a Minimum M ODCOD and a Maximum MODCOD. This defines the range of
MODCODs used on the downstream carrier.
Note: To simulate CCM select the same Minimum MODCOD and Maximum MODCOD.
You must also adjust your DVB-S2 network parameters as described in
Adjusting DVB-S2 Parameters for CCM Networks on page138.
b. Click the MODCOD Distribution button to estimate the IP Data Rate for your DVB-S2
carrier based on the MODCODs that the remotes in your network are able to receive.
See Estimating the IP Data Rate for a DVB-S2 Carrier on page81 for details.
Note:

In earlier releases, you could configure a single Multicast MODCOD on this

screen. Beginning in iDX Release 2.0, you can configure a different Multicast
MODCOD for each Application. See Adding an Application on page214 for
details.

9. Select the type of Error Correction to be used for this carrier. For DVB-S2 carriers, you
must select LDCP BCH. For information on the available FEC rates and modulation modes,
see the chapter titled iDirect Modulation Modes and FEC Rates in the iDirect Technical
Reference Guide.
10. In the Assigned to Line Card box, select the line card to which this carrier is to be
assigned. If no card is available for selection, you must configure a new card or reconfigure an existing card for use by this carrier.
11. The Carrier Type must be set to Downstream. This will be selected by default.
12. For DVB-S2 downstream carriers, enter the Symbol Rate for your carrier. (You cannot
enter a Transmission Rate or Information Rate for DVB-S2 carriers.) The symbol rate for
DVB-S2 carriers must be between 1000 and 45000 ksym.
For SCPC downstream carriers, enter either a Transmission Rate, Information Rate, or
Symbol Rate. See also the chapter titled iDirect Modulation Modes and FEC Rates in the
iDirect Technical Reference Guide. Entering any of the rate values will cause the
remaining rates and the Occupied Bandwidth to be automatically calculated. Typically,
you will enter a desired transmission rate and the service provider will determine if that
can be accomplished.
Symbol Rate is related to Transmission Rate based on the selected Modulation as
follows:
For BPSK, the Symbol Rate is equal to the Transmission Rate.

For QPSK, the Symbol Rate is half the Transmission Rate.

For 8PSK, the Symbol Rate is one third the Transmission Rate.

iBuilder User Guide

iDX Release 2.0

75

Adding Carriers

For example, if you enter 2800 kbps into the Transmission Rate box, the Symbol Rate
box is automatically calculated to be 2800 ksym for BPSK, 1400 for QPSK, or 933.33 ksym
for 8PSK.
The symbol rate for SCPC carriers must be between 64 and 15000 ksym.
13. In Timeplan Parameters, enter the number of FEC Blocks in each frame. The frame
length is automatically calculated, based on FEC Blocks, FEC rates and transmission data
rate. iDirect recommends that the number of FEC blocks is set such that the frame length
is ~125 ms.
14. Frame Length is automatically calculated based on the data rates, modulation type and
FEC rate selected in previous steps.
15. If you are using the iDirect Spread Spectrum feature, select a Spreading Factor in the
Spreading Parameters area of the dialog box. The following downstream Spreading
Factors can be selected:
No Spreading

COTM SF=2: Spreading factor of 2

COTM SF=4: Spreading factor of 4

COTM SF=8: Spreading factor of 8

Note:

The iDirect Spread Spectrum feature is only supported for BPSK modulation.
You will not be able to select a Spreading Factor unless you have selected BPSK
in the Modulation field. For a complete description of this feature, see the
chapter titled Spread Spectrum in the iDirect Technical Reference Guide.

Note:

A Downstream Spreading Factor of 8 is only available for Evolution hub line

cards transmitting to Evolution Remotes.

16. Click OK. The outbound carrier appears in the Tree.

3.5.2 Adding Upstream TDMA Carriers

The upstream carrier frequency is used to send data from remotes to the hub.
To add an Upstream carrier (Inbound Carrier), follow these steps:
1. Right-click Bandwidth, and select Add Upstream Carrier.

76

iBuilder User Guide

iDX Release 2.0

Adding Carriers

The new carrier appears in the Tree with a system-generated generic name, and a dialog
box appears allowing you to define its basic parameters.

Figure 87. New Upstream TDMA Carrier Dialog Box

2. Enter a Name for the upstream TDMA carrier.
3. Enter the Uplink Center Frequency. This frequency assignment is provided as part of the
satellite link budget process and comes from the satellite provider.
4. The Downlink Center Frequency will automatically be calculated when you click the
Downlink Center Freq box, based on the previous transponder translation frequency.
5. Carrier Spacing is an optional field you can use to document the total width of your
carriers. It represents the distance between two adjacent and identical carriers measured
from center to center and normalized by the symbol rate. For more information, please
see the chapter titled Carrier Bandwidth Optimization in the iDirect Technical
Reference Guide.
6. Select the Modulation for your carrier: BPSK, QPSK or 8PSK.
7. In the Error Correction drop-down list, select the type of forward error correction (FEC).
See also the chapter titled iDirect Modulation Modes and FEC Rates in the iDirect
Technical Reference Guide.
Note:

iBuilder User Guide

iDX Release 2.0

Only Evolution line cards can receive 8PSK Modulation with .793 Error
Correction. iNFINITI line cards cannot receive 8PSK / .793 FEC.

77

Adding Carriers

8. When building a new carrier, the Assigned to Line Card box is not available. The field is
populated automatically after the satellite is assigned to this Hub RFT and this carrier is
assigned under the hub line card configuration.
9. Select a Carrier Type. If you plan to use this carrier in a mesh-enabled Inroute Group,
select Star-Mesh. Otherwise, select Star.
Note:

You must select Star for your upstream Carrier Type in iDX Release 2.0. Mesh is
not supported in this release.

10. Enter either a Transmission Rate, Information Rate, or Symbol Rate. See also the
chapter titled iDirect Modulation Modes and FEC Rates in the iDirect Technical
Reference Guide. Entering any of the rate values will cause the remaining two rates to be
automatically calculated.
Symbol Rate is related to Transmission Rate based on the selected Modulation as
follows:
For BPSK, the Symbol Rate is equal to the Transmission Rate.

For QPSK, the Symbol Rate is half the Transmission Rate.

For 8PSK, the Symbol Rate is one third the Transmission Rate.

For example, if you enter 2800 kbps into the Transmission Rate box, the Symbol Rate
box is automatically calculated to be 2800 ksym for BPSK, 1400 for QPSK, or 933.33 ksym
for 8PSK.
If you selected a Carrier Type of Star, the Symbol Rate must be between 64 and 7500
ksym. If you selected Star-Mesh, the Symbol Rate must be between 128 ksym/s and 2.048
Msym/s.
Typically, all carriers that you plan to use in the same Inroute Group must have the same
Symbol Rate, Error Correction and Modulation. However, you may configure different
Symbol Rates for Star and Star-Mesh carriers in an Inroute Group. The following
restrictions apply:
All star-only carriers in the Inroute Group must have the same symbol rate.

All star-mesh carriers in the Inroute Group must have the same symbol rate.

The star carrier symbol rate must be a 2n multiple of the mesh carrier symbol rate,
where n is an integer.

Note:

When creating a carrier for an inroute group with existing carriers, right-click
the existing carrier in the iBuilder tree and select Clone Scaled Carrier from the
menu. In the dialog box, select the desired Multiplication Factor for the
Information Rate of the new carrier.

11. In the Timeplan Parameters section:

a. The Acquisition Aperture Length is the size of the acquisition window in the Time
Plan. It is automatically calculated as a percentage of bandwidth.

78

iBuilder User Guide

iDX Release 2.0

Adding Carriers

b. Guard Band is the time between bursts on the TDMA upstream carrier. This parameter
is typically set to eight symbols.
c. Frame Length and Traffic Slots for an upstream carrier are determined when the
carrier is assigned to a line card in a network with a downstream carrier already
assigned. Frame Length is the size of the Time Plan frame in msec. Each frame is
composed of or divided into many time slots, based on data rate, FEC, etc. Each time
slot is a slice of time allotted to a remote to send its data traffic.
12. If you are using the iDirect Spread Spectrum feature, select a Spreading Factor in the
Spreading Parameters area of the dialog box. The following upstream Spreading Factors
can be selected:
No Spreading

COTM SF=1: This spreading factor is applicable to fast moving mobile applications
only. As with a spreading factor of 1, there is no spreading. However, the size of the
carrier unique word is increased, allowing mobile remotes to remain in the network
when they might otherwise drop out. This advantage comes at the cost of a slightly
lower information rate.

COTM SF=2: Spreading factor of 2

COTM SF=4: Spreading factor of 4

COTM SF=8: Spreading factor of 8

COTM SF=16: Spreading factor of 16

Note:

The iDirect Spread Spectrum feature is only supported for BPSK modulation.
You will not be able to select a Spreading Factor unless you have selected BPSK
in the Modulation field. For a complete description of this feature, see the
chapter titled Spread Spectrum in the iDirect Technical Reference Guide.

Note:

Upstream Spreading Factors of 8 and 16 are only available for Evolution

Remotes transmitting to Evolution hub line cards.

13. Click OK to save your settings.

3.5.3 Adding Upstream SCPC Carriers

An Upstream SCPC carrier frequency is used to send data on a point-to-point connection
between an iSCPC remote and the hub. An iSCPC line card or 5000/7000 iNFINITI series
remote modem receives the SCPC upstream carrier at the hub. In the downstream direction,
the iSCPC remote receives the SCPC carrier transmitted by the iSCPC line card, completing
the point-to-point connection.
Note:

iBuilder User Guide

iDX Release 2.0

iSCPC is not supported in iDX Release 2.0.

79

Adding Carriers

To add an Upstream SCPC carrier, follow these steps:

1. Right-click on the bandwidth for your transponder and select Add Upstream SCPC
Carrier.

The new carrier appears in the Tree with a system-generated generic name, and a dialog
box appears allowing you to define its basic parameters.

Figure 88. New Upstream SCPC Carrier Dialog Box

2. Enter a Name for the upstream SCPC carrier.
3. The Carrier Type must be set to SCPC. This will be selected by default.
4. The remaining configuration of an upstream SCPC carrier is similar to that of a
downstream carrier. Follow the instructions beginning with Step 3 of Adding Downstream
Carriers on page73 to complete the carrier definition.

80

iBuilder User Guide

iDX Release 2.0

Adding Carriers

Note:

When using an upstream SCPC carrier for iSCPC operation, the transmit power
is based on the SCPC line card configuration, not on the upstream carrier
configuration. For further information, please see Adding an iSCPC Line Card
on page113.

3.5.4 Estimating the IP Data Rate for a DVB-S2 Carrier

When you configure a DVB-S2 carrier with ACM, only the symbol rate and occupied bandwidth
are known. The IP Data Rate depends on the combination of MODCODs being received by the
remotes in the network at any time.
iBuilder includes a MODCOD Distribution Calculator that allows you to estimate the IP Data
Rate for your carrier. You can access this calculator by clicking the MODCOD Distribution
button on the DVB-S2 Downstream Carrier dialog box.
To use the MODCOD Distribution Calculator for your DVB-S2 carrier:
1. Click the MODCOD Distribution button on the DVB-S2 Downstream Carrier dialog box to
display the calculator. (See Figure 86 on p. 74.)

Figure 89. MODCOD Distribution Calculator for DVB-S2 Carriers

Figure 89 shows an instance of the MODCOD Distribution Calculator. The range of the
MODCOD column is limited to the DVB-S2 Range defined for the carrier assigned to this
network. The Total row shows the totals for the columns.
2. Double-click the cells to enter either the percentages of traffic or the IP Data Rates that
you estimate will be transmitted on the different MODCODs for remotes under this node.
If you change the percentages in the Distribution column, the IP Data Rate for each
MODCOD is automatically recalculated and the total is displayed in the Total row. If you
change bit rates in the IP Data Rate column, percentages in the Distribution column are
automatically recalculated and the new total percentage is displayed in the Total row.

iBuilder User Guide

iDX Release 2.0

81

Adding Carriers

Figure 90 shows the results of changing the percentages in the Distribution column.

Figure 90. Calculating Estimated IP Data Rate for a DVB-S2 Network

In the example in Figure 90, the network operator estimates that 20% of the remotes
typically receive 16APSK-4/5, 20% receive 16APSK-5/6, and the remaining 60% receive
16APSK-8/9 (the best MODCOD defined for the carrier). Based on this input, the calculator
determines the estimated IP Data Rate for the carrier to be 3190 kbps.
3. Click OK to save your changes.
A variation of the MODCOD Distribution Calculator can be used to calculate the effective MIR
and CIR for Group QoS nodes. See Estimating Effective MIR and CIR for DVB-S2 Networks on
page202 for details.

82

iBuilder User Guide

iDX Release 2.0

Adding a Teleport

4 Defining Network
Components

The Teleport is the highest component in the Tree hierarchy and represents the facility where
the antenna and, typically, the rest of the Hub equipment is housed. After adding a Teleport,
you can add a Protocol Processor (PP), Blades, Hub RFT, and Chassis to the Tree. This chapter
discusses how to configure all of these components, with the exception of the chassis.
Because the chassis requires a different type of configuration process, it is discussed in
another chapter. See Configuring a Hub Chassis on page249.
This chapter contains the following sections:

4.1

Adding a Teleport on page83

Adding a Backup Teleport on page85

Adding a Hub RFT on page88

Adding a Protocol Processor on page88

Adding a Protocol Processor Blade on page92

Setting Warning Properties for Protocol Processor Blades on page91

Adding a VLAN on page94

Adding a SkyMonitor Spectrum Analyzer on page96

Adding a Teleport
1. To add a Teleport, right-click the iDirect Globe at the top of the Tree and select Add
teleport.

iBuilder User Guide

iDX Release 2.0

83

Adding a Teleport

The new teleport appears in the Tree with a system-generated generic name, and a dialog
box appears allowing you to define its basic parameters.

Figure 91. Teleport Information Tab

2. On the Information tab, enter a name and a phone number for your Teleport facility.
3. Click the Geo Location tab.

Figure 92. Teleport Geo Location Tab

The Geo Location identifies precisely where the Uplink facility (the Hub RFT) is
geographically located on the Earth. The teleport transmits the uplink signal to the
satellite and receives the downlink signal from the satellite.
Note: The Geo Location information must be accurately configured for your
remotes to function correctly in an iDirect network.
4. Enter the exact Latitude and Longitude of your teleport facility. This information can be
obtained from your service provider or can be determined with a GPS device. Be sure to
select the correct hemisphere for each. Latitude represents North and South; longitude
represents East and West.
5. Click OK to save your settings. The Teleport appears in the Tree.

84

iBuilder User Guide

iDX Release 2.0

Adding a Backup Teleport

4.2

Adding a Backup Teleport

As part of the iDirect Geographic Redundancy feature, iBuilder allows you to create a fullyredundant backup teleport which can assume the role of your primary teleport in the event
that the primary teleport becomes unavailable.
Note:

To configure Geographic Redundancy you must have a Global NMS licence, and
you must configure your remotes as roaming remotes. See the iDirect Technical
Reference Guide for a description of this feature. See Roaming Remotes on
page172 for details on configuring your remotes as roaming remotes.

The procedure for configuring your backup teleport assumes that your primary teleport is
already operational and that your backup teleport has been installed. Generally, the iBuilder
configuration of the backup components should be identical to the configuration of the
primary teleport. During operation, any configuration changes that you make at the primary
teleport should also be made at the backup teleport. This can be accomplished using the NMS
database backup and restore utility described in the iDirect Technical Note NMS Redundancy
and Failover for your release.
Note:

If you are using the same outbound carrier for your primary and backup
teleports, the teleport operator must disable the backup transmitter while the
primary teleport is operational. In the event of failure of the primary site, the
teleport operator must enable the backup transmitter for the backup teleport
to become operational.

Using iBuilder at the primary teleport, follow these steps to configure your backup teleport
hub equipment and to add your existing remotes to the backup teleports networks. The
procedure assumes that your primary teleport and the networks it controls are already
configured in iBuilder and operational.
1. Add the backup teleport to your network by following the steps in the section Adding a
Teleport on page83. Then configure all the components of the backup teleport,
including:
The Hub RFT (See Adding a Hub RFT on page88)

The Protocol Processor (See Adding a Protocol Processor on page88)

Protocol Processor Blades (See Adding a Protocol Processor Blade on page92)

Networks (See Adding a Network on page102)

Line Cards (See Adding a Transmit or Transmit and Receive Line Card on page104)

Inroute Groups (See Adding Inroute Groups on page129)

2. Right-click the backup teleport in the network tree and select Modify Item.

iBuilder User Guide

iDX Release 2.0

85

Adding a Backup Teleport

3. In the Backup NMS area of the Teleport dialog box, select Enabled (Figure 93).

Figure 93. Configuring a Backup Teleport

4. Enter the IP address (or addresses) of the NMS server(s) at your backup teleport.
5. Click OK to save your changes.)
Note:

A distributed NMS requires up to three IP addresses for the NMS servers. If you
do not have a distributed NMS at the backup site, all three IP addresses should
be identical.

6. Add each of your remotes to the backup teleport as follows:

a. Right-click the remote in the network tree and select Add to Networks from the
menu to display the Roaming dialog box.

Figure 94. Roaming Dialog Box

b. In the Roaming dialog box, select the remotes Network under the backup teleport.
c. Click OK to save your changes.
7. At this point, all remotes will have changes pending. Apply the changes for each network
as follows:

86

iBuilder User Guide

iDX Release 2.0

Adding a Backup Teleport

a. Right-click the network in the tree and select Apply Configuration Multiple.

b. In the Automated Configuration Downloader dialog box, select all remotes and line
cards.

Figure 95. Automated Configuration Downloader Dialog Box

c. Click the Start button.
8. Right-click the protocol processor and select Apply Configuration from the menu.
9. Click Yes in the confirmation dialog box to update the protocol processor and blades.

iBuilder User Guide

iDX Release 2.0

87

Adding a Hub RFT

4.3

Adding a Hub RFT

Before you define the Hub RFT, you should define the elements in the Hub RFT Components
folders. See Defining Hub RFT Components and the Satellite on page65.
1. To create a Hub RFT, right-click your Teleport and select Add Hub RFT.

The new Hub RFT appears in the Tree with a system-generated generic name, and a dialog
box appears allowing you to define its basic parameters.

Figure 96. New Hub RFT Dialog Box

2. Enter a name for the Hub RFT, and then select the subcomponents for the Hub RFT from
each of the drop-down list boxes.
3. Select the Satellite to which this Hub RFT is assigned.
4. Click OK. The Hub RFT appears in the Tree with its new name.

4.4

Adding a Protocol Processor

After adding the Hub RFT, create the Protocol Processor. Networks can be expanded by adding
additional processing elements, referred to as Blades, to the Protocol Processor. The Protocol
Processor architecture provides both scalability and automatic failover. If a blade fails, its
load is automatically distributed across the remaining blades; the previous manual switchover
process is obsolete.

WARNING! iDirect strongly recommends changing the default password of your protocol
processor as soon as possible.

88

iBuilder User Guide

iDX Release 2.0

Adding a Protocol Processor

4.4.1 TRANSEC Protocol Processors

Transmission Security (TRANSEC) prevents an adversary from exploiting information available
in a communications channel without necessarily having defeated the encryption inherent in
the channel. Even if a wireless transmissions encryption is not compromised, by using basic
signal processing techniques taken from wireless transmission acoustics, information such as
timing and traffic volumes can be determined. This information could provide someone
monitoring the network a variety of information on unit activity.
iDirect achieves full TRANSEC compliance by presenting to an adversary eavesdropping on the
RF link a constant wall of fixed-size, strongly-encrypted (AES, 256 bit Key) traffic segments,
the frequency of which does not vary in response to network utilization. For a detailed
technical description of iDirects TRANSEC feature, see the iDirect Technical Reference
Guide.
Note:

iDirect TRANSEC is a licensed feature. If you plan to deploy this feature, please
contact the iDirect Technical Assistance Center (TAC). If you are not licensed to
use the TRANSEC feature, you will not be able to add a TRANSEC protocol
processor in iBuilder.

To configure a TRANSEC network in iBuilder, you must first create one or more TRANSEC
protocol processors. All network elements that you subsequently create under a TRANSEC
protocol processor will be part of your TRANSEC-compliant network.
TRANSEC networks require TRANSEC-capable remote and line card model types. For a list of
compatible model types, see TRANSEC Hardware Requirements on page371.
All hosts in an iDirect TRANSEC network must have X.509 certificates issued by the iDirect
Certificate Authority (CA) Foundry. Hosts include NMS servers, protocol processor blades,
TRANSEC line cards, and TRANSEC remotes. You should issue your certificates before creating
your TRANSEC network. For details on the certification process, see Using the iDirect CA
Foundry on page395.
Follow these steps to add a protocol processor:
1. To create a Protocol Processor (PP), right-click the Teleport, and select Add Protocol
Processor. (If you are adding a TRANSEC protocol processor, you can select either Add
Protocol Processor or Add TRANSEC Protocol Processor.)

iBuilder User Guide

iDX Release 2.0

89

Adding a Protocol Processor

The new Protocol Processor appears in the Tree with a system-generated generic name,
and a dialog box appears allowing you to define its basic parameters.

Figure 97. New Protocol Processor Dialog Box

2. On the Information tab, enter a Name for your Protocol Processor (PP).
3. Enter your User Password and the Admin Password. The default passwords are shown in
Figure 97. Make sure you record any changed password in case you forget it. You will not
be able to log in with the default passwords once they are changed.
4. In Download Monitor Credentials, enter any value greater than one and less than four
billion. (This number is used for multicast firmware image download and can be
duplicated across multiple PPs It is critical for communications between the NMS and
network elements.)
5. In Upstream Gateway, enter the IP address of your upstream router. This should be the
address of the router interface connected to the upstream LAN segment.
6. Click Enabled RIPv2 if you want the Protocol Processor to advertise remote routes to your
upstream router using the protocol RIPv2. This setting affects your default VLAN only.

90

iBuilder User Guide

iDX Release 2.0

Setting Warning Properties for Protocol Processor Blades

7. Select the Upstream and Tunnel Interfaces. The tunnel is the LAN segment between the
Protocol Processor and the line cards.
8. Select TRANSEC Enabled if you are adding a protocol processor for a new TRANSEC
network. (If you selected Add TRANSEC Protocol Processor from the iBuilder tree,
TRANSEC Enabled will already be selected.)
Note:

You can also select TRANSEC Enabled to convert a non-TRANSEC network to a

TRANSEC network. However, before you select this option for an existing
network, you must ensure that all preliminary steps have been taken. Follow
the procedure in Converting an Existing Network to TRANSEC on page371 to
convert an existing network to TRANSEC.

Note:

TRANSEC Enabled will not appear in the dialog box if you are not licensed for
TRANSEC. If you plan to deploy this feature, please contact the iDirect
Technical Assistance Center (TAC).

9. A persistent multicast group is a multicast group that includes all remotes communicating
with this protocol processor. A remote will be a member of this group even if it has not
been acquired into the network.
To add a persistent multicast group, click Add in the Multicast Groups section of the
Information tab to open the Persistent Multicast Group dialog box.

Figure 98. Persistent Multicast Group Dialog Box

10. Enter the Vlan Id and the IP Address of the multicast group you want to add.
Note:

4.5

For more information, see the Technical Note titled IP Multicast in iDirect
Networks.

Setting Warning Properties for Protocol Processor

Blades
You can use iBuilder to modify both global properties of protocol processor blade warnings
and warning properties for all blades of individual protocol processors. To change the global
warning properties, select Global Warnings for Blades from the Edit menu. To change
warning properties for individual protocol processors, click the Warning Properties tab for
the protocol processor you want to modify.

iBuilder User Guide

iDX Release 2.0

91

Adding a Protocol Processor Blade

Note:

When you override global blade warnings on the Protocol Processor Warning
Properties tab, the new settings are applied to all blades of that protocol
processor. You cannot override the settings for the individual blades of a
protocol processor.

For details on configuring warning properties for line cards, remotes and protocol processors,
please see Configuring Warning Properties on page51.

4.6

Adding a Protocol Processor Blade

The Protocol Processor level of the tree represents a set of one or more blades. If a blade
fails, its load is automatically distributed across the remaining blades; the previous manual
switchover process is obsolete.
To add a Blade to a Protocol Processor, follow these steps:
1. You can use either the Blades tab of the Protocol Processor or the Tree context menu to
add a Blade. Both methods are shown here.
a. Right-click the Protocol Processor in the Tree and select Modify Item to open the
Protocol Processor dialog box.
b. Select the Blades tab.

Figure 99. Protocol Processor Blades Tab

c. Click the Add button to open the Protocol Processor Blade Dialog Box (Figure 100 on
page 93).
2. Alternatively, right-click the Protocol Processor in the Tree and select Add Blade.

92

iBuilder User Guide

iDX Release 2.0

Adding a Protocol Processor Blade

In either case, the Protocol Process Blade dialog box appears allowing you to define its
parameters.

Figure 100. Protocol Processor Blade Dialog Box

3. Enter a Name for the blade.
4. Enter the Upstream Interface information for the default VLAN. (iBuilder will
automatically assign the Upstream Interface information for other existing VLANs.)
5. Enter the Tunnel Interface information for the default VLAN.

iBuilder User Guide

iDX Release 2.0

93

Adding a VLAN

4.7

Adding a VLAN
Due to the distributed architecture of the Protocol Processor, all blades in a blade set
combine to form a single, logical, upstream interface. However, each blade must have a
distinct IP address for each VLAN. This is illustrated for a single VLAN in Figure 101.

End-to-End VLAN

Network
PP Blade 1

Upstream
VLAN
Segment
VLAN-Aware
Switch or
Router

PP Blade 2
SAT
Link

Remote

PP Blade 3

Remote
VLAN
Segment

PP Blade 4

Figure 101. Uplink VLAN Segment in a PP Blade Environment

For more information on VLANs, see VLAN and LAN Information on page149.
To add a VLAN:
1. Right-click the Protocol Processor in the Tree and select Modify Item.

2. Select the VLANs tab in the Protocol Processor dialog box.

Figure 102. Protocol Processor VLans Tab

94

iBuilder User Guide

iDX Release 2.0

Adding a VLAN

3. Click Add to display the VLAN dialog box.

Figure 103. Protocol Processor VLAN Dialog Box

4. Enter a VLAN ID. Valid VLAN IDs range from 2 to 4094.
5. Enter a VLAN Name.
6. Select Enable RIPv2 to advertise remote routes to your upstream router using the
protocol RIPv2.
7. In the Address Start field, specify the Upstream Interface IP Address to be used by the
first blade. iBuilder automatically enters the remaining IP addresses. (You can override
the automatic addressing by following the procedure in the next section.)
8. Click OK. A new Upstream VLAN Interface is now defined.

4.7.1 Overriding Automatically-Assigned VLAN Addressing

After you have created a VLAN, you can modify the automatically-assigned addresses as
follows:
1. On the VLANs tab (Figure 102 on page 94), select the row containing the ID and Name of
the interface you want to modify and click Edit to view the VLAN dialog box (Figure 103).
2. To change the automatically-assigned Upstream Interface addressing:
a. Select the Override Addresses check box.
b. Enter the IP addressing information as desired.

iBuilder User Guide

iDX Release 2.0

95

Adding a SkyMonitor Spectrum Analyzer

This is illustrated in Figure 104.

Figure 104. Overriding Automatically-Assigned VLAN Addressing

If a new blade is subsequently added for scalability, all VLAN end addresses will be
automatically updated to give the new blade the appropriate upstream interfaces, and the
VLANs will be added to the new blade.

4.7.2 Special VLAN Configuration

VLAN support requires one special configuration task, which must be done at the Linux level
on the Protocol Processor. To support VLAN, the upstream Ethernet port (eth0) of the Protocol
Processor must be configured with an MTU of 1504. This is done by typing MTU = 1504
(without quotation marks) in the file /etc/sysconfig/network-scripts/ifcfgeth0. Once this is done, save the file. After saving the file, the network services must be
restarted with the following command: service network restart.
Note:

If a line like this is already present for eth0, but contains a different value (e.g.
1500), then edit the line to the above value. The MTU value can also be
checked by typing ifconfig at the prompt to display the MTU size.

WARNING! Do not change the default MTU (1500) on the tunnel interface (eth1).

4.8

Adding a SkyMonitor Spectrum Analyzer

SkyMonitor is an iDirect digital spectrum analyzer that is fully integrated with the NMS. You
can use a SkyMonitor unit to view your iDirect inbound and outbound carriers, or to view other
carriers present at your hub. Each SkyMonitor unit has eight RF ports, each of which can be

96

iBuilder User Guide

iDX Release 2.0

Adding a SkyMonitor Spectrum Analyzer

configured in iBuilder to monitor one or more L-band carriers or a specific area of the
spectrum.
Using standard Ethernet connectors, you can connect one or more SkyMonitor spectrum
analyzers to any network reachable from your NMS. However, iDirect recommends a direct
connection on your upstream LAN. In addition, a single iDirect Global NMS can connect to
multiple SkyMonitor units at multiple hub locations. Each unit can operate using either an
internal reference clock or an external 10 MHz reference signal. For details on SkyMonitor
installation, see the iDirect SkyMonitor 1880 Spectrum Analyzer Installation and Safety
Manual.
Note:

SkyMonitor is a licensed feature. If you plan to add SkyMonitor units to your

networks, please contact the iDirect Technical Assistance Center (TAC).

From iBuilder, you can associate a SkyMonitor port with the Tx or Rx carrier of a line card, or
you can manually configure the center frequency, span and resolution bandwidth (RBW) to be
displayed for that port. Once you have configured your SkyMonitor units, you can view your
carriers in iMonitor. See the iMonitor User Guide for details on viewing your carriers.
Once your SkyMonitor unit has been installed on the hub LAN, follow these steps to configure
it in iBuilder:
1. Right-click your teleport in the network tree and select Add Sky Monitor.

The New SkyMonitor dialog box appears.

Figure 105. New SkyMonitor Dialog Box

2. Enter a Name for the SkyMonitor unit.

iBuilder User Guide

iDX Release 2.0

97

Adding a SkyMonitor Spectrum Analyzer

3. Enter an IP Address for the SkyMonitor unit.

4. Enter a Serial Number for the SkyMonitor unit.
Note:

The serial number of each of your SkyMonitor units is included in your

SkyMonitor license. The NMS software verifies that the serial numbers in the
license match the serial numbers configured in iBuilder. Therefore you must
enter the correct value for the Serial Number for the SkyMonitor feature to
work.

5. Select an RF Port and click the Modify button (Figure 105) to display the RF Port dialog
box.

Figure 106. RF Port Dialog Box

6. Enter a Name for the RF Port.
Note:

In iMonitor, you can view your carriers by selecting either the assigned line
card carrier or the SkyMonitor unit in the network tree. When you view a
carrier by right-clicking its line card, the Center Frequency and Span are
automatically calculated based on the carrier configuration. When you view
bandwidth by right-clicking the SkyMonitor icon, the center frequency, span
and RBW from this configuration screen are used. Therefore, you can configure
both iDirect carriers and a Center Frequency, Span and RWB for the same RF
port.

7. If desired, enter the Center Frequency, Span and RBW that you want to use when
monitoring this port.
These fields may be left at zero if you are assigning one or more iDirect carriers to this RF
Port. These fields are required if you are monitoring bandwidth that is not associated with
a line card.

98

iBuilder User Guide

iDX Release 2.0

Adding a SkyMonitor Spectrum Analyzer

8. You can use the Available Line Card drop-down menu to associate the port with one or
more iDirect carriers. Tx-only and Rx-only line cards have one entry in the list of available
line cards. Tx/Rx line cards have two entries in the list: one for the transmit carrier and
one for the receive carrier.
Select each line card / carrier that you want to monitor on this RF Port. Then click the
Add button to add that line card as an Assigned Line Card for this port.

Figure 107. Associating a SkyMonitor Port with an iDirect Carrier

9. If you want to remove a line card from this port, select the line card in the Assigned Line
Card area and click Remove.
10. Click OK to return to the main SkyMonitor dialog box.
11. Once you have configured your RF Ports, click OK in the main SkyMonitor dialog box to
save the SkyMonitor configuration.
Figure 108 shows the SkyMonitor dialog box after configuring RF Port 4 to monitor two iDirect
carriers and also configuring a Center Frequency and Span for the port itself.

Figure 108. SkyMonitor Port Configured for Two Carriers and Center Frequency

iBuilder User Guide

iDX Release 2.0

99

Adding a SkyMonitor Spectrum Analyzer

Using Figure 108 as an example, when you launch SkyMonitor from the iMonitor tree it will
automatically tune RF port 4 as follows:

100

If you launch SkyMonitor by right-clicking line card M1D1-41401, SkyMonitor will

automatically tune port 4 to Center Frequency 1520000 kHz. (This is the center
frequency configured for the carrier named Down 1520. iBuilder automatically appends
the carrier name to the line card name in the dialog box.)

If you launch SkyMonitor by right-clicking line card M1D1-41402, SkyMonitor will

automatically tune port 4 to Center Frequency 1510000 kHz, which is the center
frequency of carrier Down 1510.

If you launch SkyMonitor from the SkyMonitor unit in the iMonitor tree, SkyMonitor will
automatically tune port 4 to Center Frequency 1222000 kHz, which is the center
frequency configured for the SkyMonitor port.

iBuilder User Guide

iDX Release 2.0

5 Defining Networks, Line

Cards, and Inroute
Groups

This chapter explains how to add an iDirect Network and its sub-elements to the iBuilder tree.
The network sub-elements include the line cards or 10000 series satellite hub, the inroute
groups, and the remotes. Before you add a Network, you must have already added a Protocol
Processor.
This chapter contains the following sections:

iDirect Line Card and Hub Models on page102

Adding a Network on page102

Line Card Types on page104

Adding a Transmit or Transmit and Receive Line Card on page104

Setting Warning Properties for Line Cards on page107

Adding Receive (Rx) Line Cards on page107

Deleting a Line Card on page109

Changing to an Alternate Downstream Carrier on page110

Adding an iSCPC Line Card on page113

Defining a Standby Line Card on page115

Adding Inroute Groups on page129

DVB-S2 Network Parameters on page135

Note:

iBuilder User Guide

iDX Release 2.0

Beginning with iDX Release 2.0, a line card must be assigned to a hub chassis
before it can become operational. Until a line card is assigned to a hub chassis,
the line card will be in the incomplete state in the iBuilder Tree and you will be
unable to apply changes to the line card. See Configuring a Hub Chassis on
page249 for details on assigning a line card to a chassis.

101

iDirect Line Card and Hub Models

5.1

iDirect Line Card and Hub Models

iDX Release 2.0 supports TDMA inbound and iDirect SCPC (iNFINITI) outbound carriers as well
as DVB-S2 outbound carriers. This section specifies the hub line cards available in this release
to transmit and receive those carriers.
Note:

iNFINITI line cards can only be used to transmit SCPC outbound carriers. They
cannot be used to transmit DVB-S2.

You can use any of the following line card model types in this release.

5.2

Evolution eM1D1 line card (DVB-S2 and SCPC modes)

Evolution XLC-11 line card (DVB-S2 and SCPC modes)

Evolution XLC-10 line card (Tx-only)

Evolution XLC-M line card (Rx-only, Multi-channel. One channel only in iDX 2.0.)

iNFINITI M1D1 line card (Transmit/Receive)

iNFINITI M0D1 line card (Receive-only)

iNFINITI M0D1-NB line card (Narrow band, Receive-only)

iNFINITI M1D1-T line card (TRANSEC)

iNFINITI M1D1-TSS line card (TRANSEC and Spread Spectrum)

iNFINITI 10000 series Private Hub

iNFINITI 10000 series Mini Hub

Adding a Network
To create the network, follow these steps:
1. Right-click the Protocol Processor and select Add Network.

102

iBuilder User Guide

iDX Release 2.0

Adding a Network

The new network appears in the Tree with a system-generated name, and a dialog box
appears allowing you to define its parameters.

Figure 109. Network Dialog Box

2. Enter a Name for the Network.
3. Select the IF Network check box only if you are creating an L-Band/Bench Test network.
This is critical for IF networks. It has the effect of setting all geographic locations to zero
for FSO calculations.
4. Once you have added remotes to your network, in the Remotes section of the screen, you
can activate or deactivate any remote in your network, regardless of inroute group by
selecting or clearing the appropriate check box.
Note:

iBuilder User Guide

iDX Release 2.0

You must deactivate a network before you can delete it. When a network is
activated, a check mark is shown next to the Activate Network selection in the
iBuilder tree context menu. To deactivate a network, right-click the network in
the tree and select Activate Network to remove the check mark. After applying
all resulting changes, you will be able to Delete the network.

103

Line Card Types

5.3

Line Card Types

You must select a Line Card Type when you add a line card to your iDirect network in iBuilder.
The Line Card Type that you select in iBuilder affects your choice of Model Type. (For
example, if you select Transmit Line Card as the Line Card Type, you cannot select M0D1 as
the Model Type since an M0D1 is a receive-only line card. See iDirect Line Card and Hub
Models on page102 for a description of the available line card Model Types.)
The Line Card Types that you can select in iBuilder are shown in Figure 110.

Figure 110. iBuilder Line Card Type Selections

The various Line Card Types as they appear in iBuilder are defined as follows:

5.4

Transmit Line Card: Transmit-only line card. The line card can transmit an outbound
carrier, but cannot receive an inbound carrier.

Receive Line Card: Receive-only line card. The line card can receive an inbound carrier,
but cannot transmit an outbound carrier.

Transmit and Receive Line Card: The line card can transmit an outbound carrier and
receive an inbound carrier. (This selection also applies to Private Hubs and Mini Hubs.)

Standby Line Card: The line card acts as a standby (spare) line card for one or more
active line cards in a chassis or chassis group.

Solo Transmit and Receive Line Card: A Transmit and Receive Line Card that is the only
active hub line card in a network. You cannot add additional Receive Line Cards to the
network if you select this option. A Solo line card can co-exist with other Solo line cards
or with one other Tx or Tx/Rx line card in a single Chassis Timing Group.

Adding a Transmit or Transmit and Receive Line

Card
Only one line card in each network may have transmit capabilities. You should have already
created a carrier. If you have not, the line card will have an Incomplete status until a carrier
is created and assigned to it and it is assigned to a hub chassis.
To add a transmit or transmit and receive line card, follow these steps:
1. Right-click Network and select Add Transmit Line Card.

104

iBuilder User Guide

iDX Release 2.0

Adding a Transmit or Transmit and Receive Line Card

The new line card appears in the Tree with a system-generated generic name, and a
dialog box appears allowing you to define its basic parameters.

Figure 111. New Transmit Line Card Dialog Box

2. Enter a Name for the line card.
3. Select a Model Type. The model type you select must match the installed line card or
10000 series hub. If you are configuring a Mesh Enabled line card, you must select either
PrivateHub, M1D1, eM1D1, M1D1-T as the Model Type. (See iDirect Line Card and Hub
Models on page102 for a list of line card model types available in this release.)
4. Enter a Serial Number. A system-generated DID is displayed in the Derived ID box.
Serial numbers are not sufficient to uniquely identify remotes and line cards. Serial
numbers are guaranteed to be unique within a particular model type, but could repeat
from one model type to another. Therefore a unique Derived ID (DID) is automatically
generated to avoid problems that would be caused by duplicate serial numbers. The DID is
a 32-bit integer formed by joining a model type code with a units serial number. Each
remote and line card has a unique DID value.
In the NMS, the DID is typically formatted as <Model Type Name>.<Serial Number>, for
example, 5150.1492. Occasionally you may see the raw DID, however, especially when

iBuilder User Guide

iDX Release 2.0

105

Adding a Transmit or Transmit and Receive Line Card

viewing server log files or console output. You may select the raw DID as a column to view
in iBuilders Details View to determine the raw DID of a modem.

WARNING! You must correctly specify both the serial number and the model type for a
line card or hub to function properly. If you configure an M1D1 card as an
M0D1 card, for example, the line card will not operate in a network.
5. Select the Line Card Type from the drop-down box. See Line Card Types on page104
for options.
6. Select the Hub RFT that is associated with this network. This allows you to select the
appropriate carriers in Step 11.
7. Under LAN / MGMT IP Address, enter the IP Address, Subnet Mask, and Gateway used by
the NMS to communicate with the line card.
8. Under GIG0 IP Address:
a. Enter the IP address for downstream data from the protocol processor to the network.
b. Use the drop-down menu to set the Speed of your GIG0 port to 100 Mbps or 1000
Mbps.
Note:

Your switch and chassis must support the selected port speed. (Older iDirect
chassis do not support 1000 Mbps.) Also, you must specifically configure the
port speed on your switch to be the same as the port speed selected for the line
card. Do not set the switch to auto-negotiate.

Note:

The GIG0 port is only used in DVB-S2 networks.

9. If you are adding a mesh-enabled line card:

a. Select Mesh Enabled to make the mesh-related parameters available for
configuration.
b. When you commission a transmit line card, you must specify the following Uplink
Control Parameters if it will be used in a mesh network:
SCPC LB Clear Sky C/N is the C/N of the loopback SCPC carrier as measured by
the line card modem under clear sky conditions. This value is typically set during
hub commissioning.

Hub UPC Margin is the maximum amount of uplink power control available at the
hub through an external device. If the teleport performs power control, enter the
margin configured for the UPC unit. Otherwise, set this parameter to zero.

For more information on setting these parameters, see Set the Clear Sky C/N Parameter
for a Mesh Outroute on page325 and Set the UPC Margin for a Mesh Outroute on
page326.
10. By default, the User Password is set to iDirect and the Admin Password is set to
P@55w0rd!. You should specify alternate, secure passwords.
11. Select the Transmit Carrier associated with this line card. If this is a transmit/receive
line card, also select the Receive Carrier.
12. If desired, you can select an Alternate Downstream Carrier in the Alternate Transmit
Properties area of the dialog box.

106

iBuilder User Guide

iDX Release 2.0

Setting Warning Properties for Line Cards

An alternate downstream carrier is configured in order to facilitate moving a network to a

new downstream carrier while minimizing the chance of stranding remotes in the process.
See Changing to an Alternate Downstream Carrier on page110 for the procedure to
move your network from the current transmit carrier to the alternate downstream carrier.
Note:

You cannot select an alternate downstream carrier for your transmit line card
if your NMS server is licensed for the Global NMS feature.

13. The line card appears in the Tree under the Network.
Note:

5.5

For details on deleting a line card, see Deleting a Line Card on page109.

Setting Warning Properties for Line Cards

You can use iBuilder to modify both global properties of line card warnings and warning
properties for individual line cards. To change global warning properties for line cards, select
Global Warnings for Linecards from the Edit menu. To change warning properties for
individual line cards, click the Warning Properties tab for the line card you want to modify.
For details on configuring warning properties for line cards, remotes and protocol processor
blades, please see Configuring Warning Properties on page51.

5.6

Adding Receive (Rx) Line Cards

Configure the desired number of receive-only line cards for this network, configuring only one
per inroute, for up to 20 inroutes. You may have as many as 19 receive-only line cards per
chassis. (If you have defined a Tx/Rx line card, then that line card can also receive an
inroute. See Adding a Transmit or Transmit and Receive Line Card on page104.) Before
adding the line card, you must have defined a unique upstream carrier for the inroute.
To add a receive line card, follow these steps:
1. Right-click Network and select Add Receive Line Card.

iBuilder User Guide

iDX Release 2.0

107

Adding Receive (Rx) Line Cards

The new line card appears in the Tree with a system-generated generic name, and a
dialog box appears allowing you to define its basic parameters.

Figure 112. New Receive Line Card Dialog Box

2. Enter a Name for the line card.
3. Select the Model Type of the line card. (See the introduction of this chapter for a list of
available line card model types.)
4. Enter a Serial Number. A Derived ID (DID) is automatically generated.
5. Under LAN /MGMT IP Address, enter the IP Address, Subnet Mask, and Gateway used by
the NMS to communicate with the line card.
6. Enter the GIG0 IP Address if applicable to this model type.
7. By default, the User Password is set to iDirect and the admin password is set to
P@55w0rd!. You may specify alternate passwords.
8. In Receive Properties, select the Carrier associated with this line card.
9. The receive line card appears in the Tree under the Network.
Note:

108

Since a receive line card requires no special configuration to be used for mesh,
you cannot select Enabled for Mesh when adding a receive line card for a mesh
inroute group. Any receive line card becomes mesh-enabled by virtue of
adding it to a mesh-enabled inroute group. See Adding Inroute Groups on
page129.

iBuilder User Guide

iDX Release 2.0

Deleting a Line Card

5.7

Deleting a Line Card

Follow the procedure in this section to delete a line card from iBuilder. This procedure applies
to both active line cards and failed line cards.
1. Right-click the inroute group of the line card you want to delete and select ModifyItem
to display the Inroute Group dialog box.
2. If you are deleting a Tx or Tx/Rx Line Card, remove all Rx line cards from the inroute
group. If you are deleting an Rx-only line card, remove only this line card from the inroute
group.
To remove a line card from an inroute group:
a. Select the line card in the Line Cards area of the dialog box.
b. Click Remove. (Figure 113)

Figure 113. Removing a Line Card from an Inroute Group

3. Click OK to save the changes to the inroute group.
4. If this is a Tx or Tx/Rx line card:
a. Right-click the line card and select ModifyConfiguration to display the Line Card
dialog box.
b. In the Hub RFT field of the dialog box, select None.

Figure 114. Removing a Line Card from the Hub RFT

c. Click OK to save the changes to the line card. The line card will automatically be
placed in the deactivation pending state.
5. If this is an Rx-only line card, right-click the line card and select Activate Line Card to
remove the check mark (Figure 115). This puts the Rx line card in the deactivation
pending state.

Figure 115. Deactivating a Line Card

iBuilder User Guide

iDX Release 2.0

109

Changing to an Alternate Downstream Carrier

6. Right-click the line card and select Apply ConfigurationReliable (TCP) to deactivate
the line card.
Note:

You may not be able to apply the changes if your line card has failed. In that
case, you must ensure that the failed line card is powered off or disconnected.
If the line card is configured in a chassis, you can power off the slot from
iBuilder. (See Configuring and Controlling the Hub Chassis on page252.) For
standalone line cards or private hubs, you should physically disconnect or
power off the line card.

WARNING! A failed transmit line card may continue to transmit if not deactivated or
powered off.
7. If you were not able to deactivate the line card, you will not be able to delete it from
iBuilder unless you first set it to standby. To set the line card to standby:
a. Right-click the line card and select ModifyConfiguration to display the Line Card
dialog box.
b. In the Line Card Type field of the dialog box, select Standby.

Figure 116. Setting a Line Card to Standby

Note: Some Model Types (e.g. Private Hub) cannot be changed to Standby. If
Standby is not available for your Model Type, select a Model Type that
supports the Standby role and then change the Line Card Type to Standby.
c. Click OK to save the line card changes.
8. Right-click the line card in the iBuilder tree and select Delete.

9. Click OK in the confirmation dialog box to delete the line card.

5.8

Changing to an Alternate Downstream Carrier

Follow the steps in this section to change your primary downstream carrier to the alternate
downstream carrier configured for your transmit line card. This procedure assumes that:

110

You have already configured your alternate downstream carrier on the Tx Line Card dialog
box. (See step Step 12 of Adding a Transmit or Transmit and Receive Line Card on
page104.)

You have ensured that all remotes in your network have received their options files
containing the alternate downstream carrier definition.

You are ready to move your network to the new downstream carrier.

iBuilder User Guide

iDX Release 2.0

Changing to an Alternate Downstream Carrier

See the chapter titled Alternate Downstream Carrier in the iDirect Technical Reference
Guide for a description of this feature.

WARNING! Remotes that have not been downloaded with the alternate downstream
carrier definition will be stranded. Site visits may be required to recover
those remotes.
When a remote rejoins a network configured with an alternate downstream carrier, it first
tries to acquire the last carrier it was receiving. When you follow the procedure in this
section, the old primary carrier is brought down and the new primary carrier begins
transmitting, forcing all remotes to lose lock and then try to rejoin the network. The remotes
first try to acquire the old active carrier before timing out and acquiring the new active
carrier. By default this timeout is set to five minutes (300 seconds). If you want to shorten this
timeout, define the following remote-side custom key on the Remote Custom tab for each
remote before executing the procedure.
[BEAMS]
net_state_timeout = <timeout>
where <timeout> is the number of seconds that the remote tries to acquire the primary
carrier before switching to the alternate carrier.
The example in this section shows how to swap the current active carrier (DVB-S2 Down
1250) with the alternate carrier (DVB-S2 Down 1230). This initial configuration is shown in
Figure 117. (If you want to move to the alternate carrier, but do not want to select a new
alternate carrier, select None in Step 2 of the procedure.)

Figure 117. Swapping the Downstream Carriers: Initial Configuration

Follow these steps to move your network to the alternate downstream carrier:
1. Right-click your transmit line card in the iBuilder Tree and select ModifyConfiguration.

iBuilder User Guide

iDX Release 2.0

111

Changing to an Alternate Downstream Carrier

2. In the Carrier Name field of the Alternate Transmit Properties section of the Line Card
dialog box, select the carrier that is currently defined as the active downstream carrier.

Figure 118. Selecting the New Alternate Downstream Carrier

3. In Carrier Name field of the Transmit Properties section of the Line Card dialog box,
select the carrier that was configured as the alternate downstream carrier as the new
primary downstream carrier.

Figure 119. Selecting the New Primary Downstream Carrier

4. Click OK to save your changes. The iBuilder Tree will show changes pending on your
transmit line card, receive line cards, and remotes (hub-side and remote-side).
5. Apply the changes to your transmit and receive line cards. Also apply the hub-side
changes to your remotes.
Note:

To avoid applying the remote-side changes twice, wait until the remotes have
re-acquired the network on the new carrier before applying the remote-side
changes.

At this point, the remotes will lose the original primary carrier. Since they were last
locked to that carrier, they will attempt to re-acquire on the same carrier. After the
remotes timeout, they will search for their alternate carrier which is the new active
carrier. At that point, the remotes will rejoin the network.
6. Once the remotes have rejoined the network on the new active carrier, apply the remoteside changes.
Note:

112

Any remotes that were not in the network at the time of the carrier change will
acquire the new carrier when they re-acquire the network since that carrier is
still defined as their alternate carrier.

iBuilder User Guide

iDX Release 2.0

Adding an iSCPC Line Card

5.9

Adding an iSCPC Line Card

An iSCPC line card is the hub equipment that transmits and receives the SCPC carriers used in
a point-to-point connection with an iSCPC remote. You can configure the following iDirect
Model Types as iSCPC line cards:

iSCPC M1D1 Line Card

iNFINITI M1D1-TSS Line Card (Spread Spectrum)

iNFINITI 5100 and 5150

iNFINITI 5300 and 5350

iNFINITI 7300 and 7350

iNFINITI 8350

Evolution e8350

Note:

iSCPC is not supported in iDX Release 2.0.

For the most part, iSCPC line cards, iSCPC remotes, and other iDirect remotes share a
common set of parameters and are defined using similar dialog boxes. This section only
discusses how to add an iSCPC line card to the network tree and select a hub RFT. The
instructions for defining parameters common to iSCPC line cards and remotes are contained in
chapter 6, Configuring Remotes on page141.
As with TDMA networks, you must configure a Hub RFT record for the hub end point of an
iSCPC link, and a set of VSAT components for the remote end point. You may use traditional
VSAT components in your Hub RFT, such as iDirect-supported BUCs and LNBs, by defining these
components in the HubRFT Components folder in iBuilders network tree. You may also use
an existing Hub RFT definition in iBuilder.
To add an iSCPC line card, follow these steps:
1. Right-click your Teleport and select Add iSCPC Line Card.

iBuilder User Guide

iDX Release 2.0

113

Adding an iSCPC Line Card

The new line card appears in the Tree with a system-generated generic name, and a
dialog box appears allowing you to define its basic parameters.

Figure 120. New iSCPC Line Card Dialog Box

2. Enter a Name for the line card.
3. Select the Model Type of the line card or remote you are using to terminate your SCPC
connection at the hub.
4. Enter a Serial Number. A system-generated DID is displayed in the DID box.
5. Select the Hub RFT that is associated with your iSCPC line card.
6. At this point, the procedure for configuring the iSCPC line card is similar to the procedure
for configuring a remote. To complete the configuration of the line card, follow the
instructions in chapter 6, Configuring Remotes beginning with the section titled
Remote Information Tab on page143. Special considerations related to iSCPC line cards
are noted in those instructions.

114

iBuilder User Guide

iDX Release 2.0

Defining a Standby Line Card

5.10 Defining a Standby Line Card

When standby line cards are configured in your network, the NMS can automatically detect
the failure of an operational line card and swap that card for a standby line card if one is
available. However, you are not required to configure any standby line cards. If a line card
fails and there is no standby backing it up, the NMS server will not attempt to initiate a
failover.

5.10.1 Overview of Line Card Redundancy

In earlier releases, you could only configure a single standby line card to back up all active
line cards in your TDMA networks. In addition, iSCPC line card redundancy was not supported.
Line card redundancy has now been enhanced to add the following capabilities:

You can define multiple standby line cards per TDMA network.

You can define standby line cards to back up your iSCPC line cards.

You can manage the configuration of the relationships of your standby line cards to your
active line cards.

Line card redundancy is defined by the relationship between a standby and an active line
card. An active line card is any line card configured to be active in your network under normal
operating conditions when no line card failures have occurred. An active line card can be any
of the following:

A Tx (or Tx/Rx) line card configured to transmit the SCPC or DVB-S2 outbound carrier in a
TDMA network to the remote modems. (A Tx/Rx line card also receives a TDMA inroute
transmitted by the remotes in the network. Both Tx and Tx/Rx line cards are referred to
as Tx line cards in this section.)

An Rx-only line card configured to receive an inbound TDMA carrier transmitted by the
remote modems in a TDMA network. (An Rx-only line card does not transmit an outbound
carrier. Rx-only line cards are referred to as Rx line cards in this section.)

An iSCPC line card configured to transmit and receive the SCPC carriers in a point to point
connection with an iSCPC remote.

A standby line card is a line card that does not become operational until it is enabled by the
NMS to take over for an active line card. Line card switching can be automatic or manual,
depending on the configuration of the standby line card.
In the iDirect system, there are two types of relationships between standby and active line
cards:

A warm standby is a line card that has been pre-configured with the same software and
configuration as an active line card. Because the configuration is pre-loaded, a line card
acting as a warm standby for an active line card provides the fastest recovery time
available. However, a line card can serve as a warm standby for only one active line card.

A cold standby is not pre-loaded with the same configuration as the active line card. Since
the configuration must be downloaded from the NMS server to the line card before the
standby can become operational, a line card acting as a cold standby for an active line
card takes significantly longer to take over for a failed active line card. However, a line
card can serve as a cold standby for multiple active line cards.

iBuilder User Guide

iDX Release 2.0

115

Defining a Standby Line Card

Automatic failover occurs when the NMS fails to receive the expected heartbeat message
from the active line card. The following prerequisite conditions must be met in order for the
failover operation to proceed:
1. A standby line card must be configured in iBuilder for the network to back up the failed
line card.
2. The standby line card must be in the OK state (and accessible from the NMS) as
determined by the NMS event server.
3. Both line cards must be in the same chassis and the chassis must be accessible to the NMS
through the TCP interface.
4. A standby line card must be a warm standby for at least one active line card. (There is no
requirement to establish any cold relationships.)
If the standby line card itself has failed, both the above warning and the failed alarm will be
active in iMonitor.
Note:

When configuring a line card to backup a transmit line card, connect the Tx IFL
cable only after the standby line card configuration has been downloaded.
Once you have configured the line card, ensure that the cable is connected.

Line Card Redundancy in TDMA Networks

Default redundancy relationships are no longer established automatically when you configure
standby line cards for your TDMA networks. Therefore, once you have configured a standby
line card, you must explicitly configure the warm and cold redundancy relationships for that
line card on the chassis. (See Managing Line Card Redundancy Relationships on page120 for
details.)
When you configure a standby line card in a TDMA network, you can limit the types of
redundancy relationships that an operator can configure for the line card using the Allow
Failover For field of the Standby Line Card dialog box. The following selections are available:

116

None: The standby line card does not back up any active line cards. The line card cannot
be swapped (automatically or manually) for a failed line card until another selection is
made. The line cards configuration will be labeled incomplete in the iBuilder tree.

All: The standby line card can be configured to act as a warm standby for one line card
and as a cold standby for any remaining line cards. (Typically the standby line card is
configured as a warm standby for the Tx line card and as a cold standby for Rx line cards.
This favors the most critical line card. In a multi-inroute, frequency-hopping network, the
failure of a receive-only line card results in diminished upstream bandwidth only; remotes
will automatically load-balance across the remaining receive line card(s) without
dropping out of the network. However, if the transmit line card fails, the entire network
will be out of service.)

Tx Only: The standby line card can be configured to act only as a standby for the Tx (or
Tx/Rx) line card.

Rx Only: The standby line card can be configured to act as a warm standby for one Rx (or
Tx/Rx) line card and as a cold standby for all remaining Rx line cards.

iBuilder User Guide

iDX Release 2.0

Defining a Standby Line Card

In general, a standby line card can only back up line cards of the same model type. Table 3
shows the line card model types that can act as standby for each active line card model type.
Table 3. Standby Line Card Model Type Compatibility
Active Line Card
Model Type

Required Standby Line Card

Model Type

M1D1

M1D1

M1D1-T

M1D1-T

M1D1-TSS

M1D1-TSS

eM1D1

eM1D1

XLC-11

XLC-11

XLC-10

XLC-10

XLC-M

XLC-M

M0D1

M0D1, M1D1

M0D1-NB

M0D1-NB, M1D1

Line Card Redundancy for iSCPC Connections

You can configure standby iSCPC line cards to back up one or more active iSCPC line cards. As
with all standby line cards, an iSCPC standby can only act as the warm standby for a single
active line card.
Note:

iSCPC is not supported in iDX Release 2.0.

Standby iSCPC line cards do not back up any active iSCPC line cards by default. You must use
iBuilder to explicitly define the redundancy relationships among active and standby iSCPC line
cards. See Managing Line Card Redundancy Relationships on page120 for details on
configuring the relationships between your active and standby line cards.

iBuilder User Guide

iDX Release 2.0

117

Defining a Standby Line Card

5.10.2 Adding a Standby Line Card to a TDMA Network

Follow the procedure in this section to add a standby line card to a TDMA network:
1. Right-click your Network and select Add Standby Line Card to display the Line Card
dialog box.

The new line card appears in the Tree with a system-generated generic name, and a
dialog box appears allowing you to define its basic parameters.

Figure 121. New Standby Line Card Dialog Box

2. Enter a Name, Model Type, Serial Number, and LAN IP Address for the new line card.
3. For DVB-S2 line cards, configure the GIG0 IP Address.
4. Make sure that Standby is selected for Line Card Type.

118

iBuilder User Guide

iDX Release 2.0

Defining a Standby Line Card

5. Select the desired option in the Allow Failover For drop-down list. Four selections are
available in the menu:

Select None to disable failover. You cannot configure redundancy relationships for
this standby line card if None is selected. Changing a standby line cards selection to
None deletes any existing redundancy relationships.

Select All to allow the standby line card to be configured to backup all transmit and
receive line cards.

Select Tx Only to allow the standby line card to be configured to backup only your
transmit (or Tx/Rx) line card.

Select Rx Only to allow the standby line card to be configured to backup only your
receive line cards. (This includes Tx/Rx line cards.)

6. Click OK to save the standby line card configuration.

7. Once you have defined your standby line card, follow the procedures in the section
Managing Line Card Redundancy Relationships on page120 to set up the line cards
redundancy relationships.

5.10.3 Adding an iSCPC Standby Line Card

Note:

iSCPC is not supported in iDX Release 2.0.

To add an iSCPC standby line card, follow these steps:

1. Right-click your Teleport and select Add iSCPC Standby Line Card.

iBuilder User Guide

iDX Release 2.0

119

Defining a Standby Line Card

The new line card appears in the Tree with a system-generated name, and a dialog box
appears allowing you to define its basic parameters.

Figure 122. New Standby iSCPC Standby Line Card Dialog Box
2. In the dialog box, enter a Name for the new Line Card.
3. Select the correct Model Type for the iSCPC line card. You must select M1D1-iSCPC.
Note:

The NMS must power down the chassis slot of the failed line card during the
failover procedure to ensure that the line card is no longer transmitting.
Therefore, only M1D1-iSCPC line cards configured in a chassis can be used in
redundancy relationships, even though some remote model types can be
configured as iSCPC line cards.

4. Enter the remaining configuration settings for the iSCPC standby line card and click OK to
save your changes.
5. Once you have defined your standby line card, follow the procedures in the section
Managing Line Card Redundancy Relationships on page120 to set up the line cards
redundancy relationships.

5.10.4 Managing Line Card Redundancy Relationships

Before you can configure or modify the redundancy relationships among your active and
standby line cards, all line cards must be assigned to a chassis. A chassis with line cards
assigned is shown in Figure 123. For details on configuring a chassis, see Configuring a Hub
Chassis on page249.

120

iBuilder User Guide

iDX Release 2.0

Defining a Standby Line Card

Figure 123. Sample Chassis Configuration

Viewing Line Card Redundancy Relationships

Once the line cards have been added to the chassis, follow these steps to view the
redundancy relationships:
1. Right-click your chassis and select ModifyManage Line Card Redundancy to display the
Manage line card redundancy dialog box.

The default view (By Standby) of the Manage line card redundancy dialog box is shown in
Figure 124.

Figure 124. Manage Line Card Redundancy Dialog Box: By Standby View

iBuilder User Guide

iDX Release 2.0

121

Defining a Standby Line Card

This dialog box has two views. The default view (By Standby, shown in Figure 124) lists each
standby line cards on the left. On the right of each standby, the dialog box lists each active
line card backed up by the standby line card, and the standby line cards relationship (warm
or cold) to the active line card. The second view (By Active, shown in Figure 125) lists the
active line cards on the left and each of its standby line cards on the right.

Figure 125. Manage Line Card Redundancy Dialog Box: By Active View
To switch between views, right-click anywhere in the dialog box and select the View you want
from the menu.

The dialog box is divided into virtual backplanes, organized by the assignments of the line
cards to the chassis. In the example below, all the standby line cards are in virtual backplane
1 because the jumper between slots 4 and 5 is enabled, providing connectivity between the
first two groups in the physical chassis. (See Figure 123 on page121.) The dialog box also
shows the physical slot numbers and the redundancy relationships of all line cards in the
chassis.

Configuring Line Card Redundancy Relationships

You can perform the following operations to configure the redundancy relationships among
your active and standby line cards:

122

Assign a standby line card as a warm standby

Assign a standby line card as a cold standby

Dissociate a standby line card from all redundancy relationships

Dissociate an active line card from a single cold standby relationship

iBuilder User Guide

iDX Release 2.0

Defining a Standby Line Card

You can reconfigure your line card redundancy relationships from either View in the Manage
Line Card Redundancy dialog box by right-clicking on an active or standby line card and
selecting the desired option from the context menu. The following sections explain how to
configure these relationships.
Note:

A standby line card must be assigned as a warm standby for an active line card
before it can become a cold standby for any additional line cards.

Assigning a Warm Standby to an Active Line Card

Follow these steps to establish a warm redundancy relationship between an active line card
and a standby line card:
1. In the Manage Line Card Redundancy dialog box, right-click a standby line card and
select Assign as warm, or right-click an active line card and select Assign a warm
standby.

2. If there are any valid line cards available, a dialog box appears with a list of all valid
selections. (If you right-clicked a standby line card, available active line cards are listed.
If you right-clicked an active line card, available standby line cards are listed. Both views
are shown in Figure 126.)

Figure 126. Assigning a Warm Standby Line Card

3. Select a line card from the list and click OK. iBuilder saves the configuration immediately.

iBuilder User Guide

iDX Release 2.0

123

Defining a Standby Line Card

4. Apply the changes to the standby line card by right-clicking the line card in the iBuilder
tree menu and select Apply Configuration.

Assigning a Cold Standby to an Active Line Card

Follow these steps to establish a cold redundancy relationship between an active line and a
standby line card:
1. In the Manage Line Card Redundancy dialog box, right-click a standby line card and
select Assign as cold, or right-click an active line card and select Assign a cold standby.

2. If there are any valid line cards available, a dialog box appears with a a list of all valid
selections. (If you right-clicked a standby line card, available active line cards are listed.
If you right-clicked an active line card, available standby line cards are listed. Both views
are shown in Figure 127.)

Figure 127. Assigning a Cold Standby Line Card

124

iBuilder User Guide

iDX Release 2.0

Defining a Standby Line Card

3. Select a line card from the list and click OK. iBuilder saves the configuration immediately.
Note:

You do not need to apply the changes to the cold standby line card. A cold
standby is automatically downloaded when a failover occurs.

Removing a Warm Redundancy Relationship

Follow these steps to remove a warm redundancy relationship between an active line card
and a standby line card:
1. In the Manage Line Card Redundancy dialog box, right-click a standby line card.
2. Select Dissociate all from the menu. This will clear all of the standby line cards
redundancy relationships.

Note:

The only way to destroy a warm relationship is to dissociate all relationships

from a standby line card. Therefore, once you remove a warm relationship, you
must recreate any cold relationships associated with that standby line card.

Removing a Cold Redundancy Relationship

Follow these steps to remove a cold redundancy relationship between an active line card and
a standby line card:
1. In the Manage Line Card Redundancy dialog box, right-click an active line card and
select Dissociate from standby from the menu.

2. In the Dissociate cold standby dialog box, select all standby line cards that you no longer
want to serve as cold standbys for the active line card. Then click OK. The standby line

iBuilder User Guide

iDX Release 2.0

125

Defining a Standby Line Card

card will not be selected to take over for the active line card in the event that the active
line card fails.

Figure 128. Removing a Cold Redundancy Relationship

5.10.5 Swapping an Active and Standby Line Card

Follow these steps to manually swap an active line card with a standby line card. Use the
same command to perform a manual failover to replace a failed active line card with a
standby line card. When you swap an operational line card with a standby line card, the line
cards swap roles and both slots remain powered on. However, if the original line card has
failed or if a problem occurs during the swap, the NMS will power off the slot of the failed line
card.
Note:

In order to perform a manual swap, the standby line card must have a
redundancy relationship with the active line card.

1. Right-click the active line card and select Swap Line Card from the menu.

126

iBuilder User Guide

iDX Release 2.0

Defining a Standby Line Card

2. In the dialog box, select the standby line card that you want to be the new active line
card.

Figure 129. Choosing a New Active Line Card During Line Card Swap
3. Click OK to swap the line cards.
Figure Figure 130 shows the events you will see in iMonitor if the line cards are successfully
swapped.

Figure 130. Line Card Swap Event Sequence

iBuilder User Guide

iDX Release 2.0

127

Defining a Standby Line Card

5.10.6 Line Card Failover

Automatic failover occurs when the NMS fails to receive the expected heartbeat message
from the active line card. If this happens, the NMS changes the state of the active card to
failed and then attempts to perform a series of actions to switch the active and standby line
cards. Note that this series of actions will only succeed if the active line card has experienced
a temporary loss of communication with the NMS long enough to trigger the failover, but short
enough to allow the NMS to re-establish communication with the failed line card during the
course of these actions. Otherwise, the standby line card will take over for the failed active
line card, and the failed line card will be disabled.
Note:

For line cards with an active GIG0 port, the NMS expects a heartbeat message
from both line card LAN ports.

The NMS performs the following actions to attempt to switch a failed active line card and a
standby line card:
1. The NMS monitors the standby line card to ensure that the standby remains operational.
2. The NMS establishes a TCP connection to the failed line card and reconfigures it to be a
standby line card.
3. The NMS establishes a TCP connection to the original standby line card and reconfigures it
to be the new active line card.
4. The NMS re-establishes all redundancy relationships for the new standby line card,
mirroring the redundancy configuration of the old standby as it existed before the
failover.
If all of the steps above are successful, you will see the same sequence of events in iMonitor
that you see when you manually swap line cards. See Figure 130 on page127.
In many cases, the NMS will be unable to configure the failed line card to be the new standby
line card. If the NMS cannot connect to the failed line card, it will power off the chassis slot
of that line card. It will then re-configure the original standby to be the new active line card
to recover the network. At that point, the system will be operational, but the failed line card
will be in an interim state requiring recovery. You should call the iDirect TAC to assist you in
diagnosing the reason for the failure and to guide you through the recovery process.
If the line card experienced a hard failure or internal component failure, you will be
instructed to remove the failed card from the chassis and return it to iDirect for repair. Some
failures, such as those listed below, may be repaired on-site.

Switch port failure

LAN cable failure

FPGA image load failure or runtime flash corruption

WARNING! Do not power on the chassis slot of a failed line card unless the I/F Tx and Rx
cables are disconnected and you have recovered from the line card failure
condition.

128

iBuilder User Guide

iDX Release 2.0

Adding Inroute Groups

5.11 Adding Inroute Groups

Inroute Groups are groups of receive line cards, or Inroutes. If you have used a
transmit/receive line card, you may add this card to the Inroute Group also. However,
transmit-only line cards may not be included. The purpose for bundling several receive line
cards together into Inroute Groups is to allow for load balancing among the individual line
cards. You must have created Inroute Groups in order to add remotes to the network.
The relationship between carriers, line cards, and inroute groups is shown in Figure 131.
There are specific rules regarding the assignment of line cards to inroute groups.
1. You cannot assign a line card to an inroute group unless its assigned carrier is identical in
data rate and FEC block size to the other line card(s) in that inroute group.
2. You cannot assign a line card to an inroute group if it is already assigned to another
inroute group. In this case, if rule 1 is true, you can un-assign the line card from its
current inroute group and re-assign it to the desired inroute group.
3. You may not change a line cards carrier assignment if the line card is assigned to an
inroute group. However, you may modify the characteristics of the current carrier (see
rule 4).
4. If you modify either the FEC block size or data rate of a carrier that belongs to a line card
in an inroute group, iBuilder will automatically change all other carriers that belong to
the other line cards in that inroute group. It will prompt you first and allow you to cancel
the modify operation.
To assign a line card to an inroute group, modify the Inroute Group and click Add. iBuilder will
only show you line cards that are valid to be assigned to that inroute group. If you dont see
line cards you expect to see, review the rules above.
Network

Inroute Group 1

Tx/Rx -- or -- Rx
Hub Line Card

Inroute Group n
Inroute Group n

Remotes
Remotes
Remotes
Remotes

Inroute Carrier
(in Spacecraft folder in tree)

Figure 131. Inroute Group Relationships

iBuilder User Guide

iDX Release 2.0

129

Adding Inroute Groups

5.11.1 Carrier Grooming

Carrier Grooming mode is an option in which remotes dynamically acquire into the inroute
with the fewest number of remotes (assuming multiple inroutes in the group). Once acquired
into an inroute, the remote will remain in that inroute until it passes through acquisition
again. iMonitors Inroute Distribution screen provides an ACQ Bounce function that forces a
remote to re-acquire without resetting. An RCM is required for Carrier Grooming.

5.11.2 Frequency Hopping

Users may also select Frequency Hopping mode when defining inroute groups. Frequency
Hopping requires that you upgrade your Hub Chassis with redundant Reference Clock Modules
(RCMs). Frequency Hopping mode provides true run-time load balancing across all the inroutes
within an inroute group. In Frequency Hopping mode, remotes will dynamically load-balance
across all inroutes in the group based on inroute demand. The Protocol Processor analyzes
upstream demand from all remotes and automatically allocates timeplan slot assignments to
achieve an equal balance of remote demand across all the inroutes. Remotes will hop from
one inroute to another either on a frame boundary or within the same frame depending on the
nature of the demand.
Both Carrier Grooming and Frequency Hopping provide an added level of inroute redundancy
as well as improved performance. When line cards are added to or removed from a network,
remotes respond dynamically, either by reacquiring into another inroute when a line card is
removed or fails, or by moving to a newly added inroute.

5.11.3 Mesh-Enabled Inroute Groups

A mesh-enabled Inroute Group contains inroutes that are received both by the hub and by
mesh-enabled remotes. This allows direct remote-to-remote communications for real-time
traffic, eliminating the double satellite hop and extra bandwidth required for star traffic. To
indicate that an inroute group will be used by mesh remotes, you must select Enabled for the
group in the Mesh area on the Information tab of the Inroute Group dialog box. Because all
remotes in a mesh Inroute Group receive their home inroute, you must be careful to correctly
set the values on the Acquisition and Uplink Control Parameters tab. For general details on
iDirects mesh implementation, see the chapter titled Mesh Technical Description in the
iDirect Technical Reference Guide.

130

Note:

Beginning with iDS Release 7.0, acquisition and uplink control parameters are
configured at the Inroute Group level rather than the network level. See
Adding Inroute Groups on page129.

Note:

You can add the following remote models to a mesh inroute group: iNFINITI
5300/5350; iNFINITI 7300/7350; iNFINITI 8350; Evolution e8350; iConnex-100;
iConnex-700; and iConnex-e800.

iBuilder User Guide

iDX Release 2.0

Adding Inroute Groups

5.11.4 Adding an Inroute Group

1. Right-click Network and select Add Inroute Group.

The new inroute group appears in the Tree with a system-generated generic name, and a
dialog box appears allowing you to define the basic parameters.

Figure 132. New Inroute Group Dialog Box

iBuilder User Guide

iDX Release 2.0

131

Adding Inroute Groups

2. Enter a Name for the Inroute Group.

3. Carrier Grooming and Frequency Hopping are selected by default. See Carrier
Grooming on page130 and Frequency Hopping on page130 for more information.
Note:

Beginning with iDS Release 8.0, Free Slot Allocation is always on and is no
longer configurable on the Inroute Group Information tab. For information
about Free Slot Allocation, see the chapter titled QoS Implementation
Principles in the iDirect Technical Reference Guide.

4. In the Mesh area of the dialog box:

a. Select Enabled if you are adding a mesh inroute group.
b. Select UDP Payload Compression if you want to enable payload compression for UDP
packets for all remotes in your mesh inroute group.
c. Select CRTP if you want to enable CRTP for RTP packets for all remotes in your mesh
inroute group.
d. Select VLAN if you want to enable VLAN support for all remotes in this mesh inroute
groups. You cannot add VLANs to your mesh remotes unless VLAN is selected for the
Inroute Group.
e. Select UDP Header Compression if you want to enable header compression for UDP
packets for all remotes in your mesh inroute group.
Note: If Mesh is Enabled, the mesh settings configured for the inroute group apply
to all remotes in that group, overriding any individual remote settings that
may have been configured. For a discussion of the various compression
types, see Enabling IP Packet Compression Types on page180.
Note: When you enable mesh for your inroute group, a new QoS Bandwidth Group is
automatically created in the Group QoS tab with a default mesh QoS
Application for unreliable traffic. You can modify the default mesh
Application and add additional Applications to the mesh Bandwidth Group.
All traffic matching Applications in that group will be sent over the mesh
network overlay. Since mesh does not support TCP acceleration (or
spoofing), any TCP traffic sent over mesh will not be accelerated.

132

iBuilder User Guide

iDX Release 2.0

Adding Inroute Groups

5. Click Add to add line cards (with the same Information Rate, FEC Rate, and Modulation)
to this Inroute Group.The Assign Hub To Inroute Group Dialog Box opens.

Figure 133. Assign Hub to Inroute Group Dialog Box

Note:

All line cards in an Inroute Group must have the same parameters. The only
exception is an Inroute Group with a mix of Star and Star-Mesh carriers. See
page 78 for details.

6. In the Assign Hub To Inroute Group dialog box, select the line cards that you wish to add.
Click OK. You are returned to the Inroute Group dialog box.
7. The Inroutes area of the Information tab displays information about the carrier of the line
card selected in the Line Cards list. Many of these parameters are shared by all carriers in
the Inroute Group. These settings are configured on the Uplink and Downlink Carrier
dialog boxes, described in Adding Upstream TDMA Carriers on page76.

Figure 134. Inroute Group Dialog Box with Highlighted Mesh Reference Carrier

iBuilder User Guide

iDX Release 2.0

133

Adding Inroute Groups

For a mesh-enabled inroute group, the carrier highlighted in blue is the reference carrier.
(See Figure 134.) The reference carrier is always one of the star carriers, which typically
have a higher Symbol Rate than the star-mesh carriers. The Symbol Rate Factor shows
the ratio between the symbol rates of the star and star-mesh carriers. For further
information, see page78.
Any modifications to Shared Carrier Parameters must be made to the reference carrier.
Parameters of other carriers will be adjusted automatically.
Note:

You can add a maximum of eight carriers to a mesh-enabled inroute group.

8. Click the Acquisition/Uplink Control tab.

Figure 135. Inroute Group Acquisition/Uplink Control Tab

9. Specify the Uplink Control Parameters. Two of the parameters, TDMA Nominal C/N and
TDMA Clear-Sky C/N, are specified per inroute by first selecting the Line Card for that
inroute and then entering the values. The remaining parameters are common for the
entire inroute group.
Frequency Range is a read-only field showing the total range of the frequency band
swept during acquisition, one half on either side of the target frequency. This value
reflects the stability entered in the hub down converter (LNB) configuration.

134

iBuilder User Guide

iDX Release 2.0

DVB-S2 Network Parameters

Frequency Interval is the read-only step size for the sweep across the Frequency
Range.

The Fine Adjust and Coarse Adjust parameters define the ranges and increments
used when applying uplink power control adjustments to the upstream carriers for
this inroute group.

Note: You can click and drag the Power Adjust sliders to vary the C/N ranges and
automatically update the Fine Adjust and Course Adjust settings.

TDMA Nominal C/N is the target C/N value of the upstream TDMA carrier as measured by
the Line Card modem. TDMA Nominal C/N should be set during hub commissioning.
For a mesh inroute, TDMA Nominal C/N is used as a backup reference in the event of a
failure of the SCPC loopback, allowing the network to continue to operate as a star
network from the perspective of uplink power control.
TDMA Nominal C/N is determined based on the link budget analysis for your network,
which takes into consideration the modulation and FEC rate. The fine adjustment is
typically set to +/-1 dB.
For networks that migrate from iDS Release 6.0, this value will be set to:
(Fine Adjust Upper C/N Fine Adjust Lower C/N) / 2
TDMA Clear Sky C/N applies to mesh inroutes only. It is the C/N of the upstream
TDMA carrier as measured by the Line Card modem under clear sky conditions. This
value is typically set during commissioning. (For details, see Set the Clear Sky C/N
Parameter for an Inroute in a Mesh Inroute Group on page328.)

10. Click OK and the Inroute Group appears in the Tree under the Network.
Note:

You can click and drag the Power Adjust sliders to vary the C/N ranges and
automatically update the Fine Adjust and Course Adjust settings.

Note:

The Group QoS tab is discussed in Chapter 7, Configuring Quality of Service

for iDirect Networks.

5.12 DVB-S2 Network Parameters

iBuilder allows you to configure the network-level parameters that control how a DVB-S2
network behaves when ACM is enabled for your downstream carrier.
These parameters affect the following two areas of ACM operation:

The thresholds which determine a remotes current MODCOD based on its reported Signalto-Noise Ratio (SNR)

The behavior of the system during remote fade conditions

You can modify the following DVB-S2 parameters:

Steady State Margin (Default: 0.5 dB): The margin added to the SNR thresholds measured
at hardware qualification to arrive at the operational SNR threshold during steady state
operation.

Fast Fade Margin (Default: 1 dB): The additional margin added to the SNR thresholds
measured at hardware qualification to arrive at the operational threshold during a fast
fade condition. During a fade, this margin is added to the Steady State Margin.

iBuilder User Guide

iDX Release 2.0

135

DVB-S2 Network Parameters

Fast Fade Threshold (Default: 0.5 dB): The drop in receive signal strength between two
consecutive SNR measurements by a remote that causes the remote to enter a fast fade
state. If, during steady state operation, a remote reports an SNR drop that is greater than
or equal to the Fast Fade Threshold, then the hub considers the remote to be in the fast
fade state.

Fade Slope Threshold (Default: 0.3 dB per second): The rate of drop in receive signal
strength by a remote that causes the remote to enter a fast fade state. If, during
steady state operation, a remotes SNR drops at a rate that is greater than or equal to the
Fade Slope Threshold, then the hub considers the remote to be in a fast fade state.

Note:

These parameters apply to all remotes in an ACM network. You cannot modify
these settings for individual remotes.

5.12.1 System Operation

During steady state conditions, DVB-S2 remotes report their current SNR measurements to the
hub every five seconds. The hub monitors the SNR measurements of each remote. Using the
network settings for the Fast Fade Threshold and the Fade Slope Threshold, the hub
determines whether or not a remote has entered the fast fade state. If either the Fast Fade
Threshold or the Fade Slope Threshold is exceeded, the remote is placed in the fast fade
state. When in the fast fade state, the remote reports its current SNR to the hub every
second. Once the remote has stabilized and is no longer exceeding either of the above
thresholds, the hub returns the remote to the steady state condition. This typically takes a
few seconds due to processing time and transmission delay.
During hardware qualification of a DVB-S2 remote model type, SNR thresholds are determined
for each MODCOD that the remote can receive. Each threshold represents the minimum SNR
at which the remote can reliably receive the MODCOD. These thresholds are published in the
Technical Reference Guide and in the Link Budget Analysis Guide.
In an operational network, the system adds margin to these SNR thresholds to ensure that the
remote can receive the outbound carrier with Quasi Error Free (QEF) performance. During
steady state operation, the Steady State Margin is added to the threshold. Additional margin,
Fast Fade Margin, is added during fast fade conditions at the remote.
In addition to the margin added to the SNR threshold during operation, the system must also
take into account the variance, or margin of error, associated with the remotes SNR
measurement. To account for this margin of error, an additional 0.2 dB is added to the SNR
threshold. This margin of error cannot be changed.
As an example, consider an Evolution e8350 Satellite Router receiving a DVB-S2 outbound
carrier with a current MODCOD of 16PSK 3/4. This MODCOD has an SNR threshold of 10.8 dB,
determined at hardware qualification. Table 4 shows the operational SNR threshold below
which the hub changes the outbound frames transmitted to the remote to a lower MODCOD.
The table assumes the default settings for the Steady State Margin and Fast Fade Margin are
in effect.

136

iBuilder User Guide

iDX Release 2.0

DVB-S2 Network Parameters

Table 4. Example: Calculating Operational SNR Thresholds

Steady State
Conditions
SNR Threshold (From LBA)
Steady State Margin
Fast Fade Margin
Margin of Error
Operational SNR Threshold

Fast Fade
Conditions

10.8 dB

10.8 dB

0.5 dB

0.5 dB

N/A

1.0 dB

0.2 dB

0.2 dB

11.5 dB

12.5 dB

Adding margin to increase the SNR threshold causes the system to behave more conservatively
by dropping to a lower MODCOD at a higher SNR threshold. For more information, see the LInk
Budget Analysis Guide and the Technical Reference Guide for this release.

5.12.2 Configuring DVB-S2 Network Parameters

You can configure the DVB-S2 parameters at the network level of the iBuilder Tree.

CAUTION: Adjusting these parameters can adversely affect the performance of your
ACM network. You should consult with iDirect before changing these settings in an
operational network.
To modify the DVB-S2 parameters for a network:
1. Right-click your Network in the iBuilder tree and select ModifyDVB-S2 from the menu.

iBuilder User Guide

iDX Release 2.0

137

DVB-S2 Network Parameters

2. In the DVB-S2 Configuration dialog box, edit any settings you want to change.

Figure 136. DVB-S2 Configuration Dialog Box

The Steady State Margin and Fast Fade Margin must be greater than or equal to zero.
The Fast Fade Threshold and Fade Slope Threshold must be greater than zero.
Note:

You can click Set to Default to return your network to the default settings.

3. Click OK to save the new settings

4. Right-click your DVB-S2 network in the iBuilder Tree and select Apply Configuration
Network to send the changes to the protocol processor.

5.12.3 Adjusting DVB-S2 Parameters for CCM Networks

The iDirect system simulates CCM on the DVB-S2 outbound carrier by setting the Minimum
MODCOD and Maximum MODCOD to the same value. (For details on configuring your DVB-S2
carrier, see Adding Downstream Carriers on page73.) If your DVB-S2 carrier is configured
for CCM, adjust the DVB-S2 network parameters as follows:

Set the Steady State Margin to 0.

Set the Fast Fade Margin to 0.

Set the Fast Fade Threshold to a large number (for example, 3 dB).

Set the Fade Slope Threshold to a large number (for example, 3 dB).

These parameters are defined in DVB-S2 Network Parameters on page135. The procedure
for configuring these parameters is documented in Configuring DVB-S2 Network Parameters
on page137.
In addition to adjusting the DVB-S2 network parameters, add the following custom keys:
On the Custom Tab of each remote in the CCM network, enter the following Remote-Side
custom key:
[DVBS2]
override_acm_mon = 1

138

iBuilder User Guide

iDX Release 2.0

DVB-S2 Network Parameters

On the Custom Tab of the Tx Line Card transmitting the CCM carrier, enter the following
custom keys:
[DVBS2]
fill_frame_enable = 1
fill_frame_modcod = n
where n is the MODCOD index of the MODCOD selected for your DVB-S2 CCM carrier.
Note:

iBuilder User Guide

iDX Release 2.0

MODCOD indexes are documented in the Link Budget Analysis Guide for your
release.

139

DVB-S2 Network Parameters

140

iBuilder User Guide

iDX Release 2.0

iDirect Remote Satellite Router Models

6 Configuring Remotes

The most important components of your network are the remotes. This chapter discusses the
various aspects of their functionality; provides instructions on how to create and configure
them; and provides details about their parameters. It contains the following sections:

6.1

iDirect Remote Satellite Router Models on page141

Before You Start on page142

Adding Remotes on page142

Setting Warning Properties for Remotes on page171

Adding a Remote by Cloning an Existing Remote on page171

Roaming Remotes on page172

Enabling IP Packet Compression Types on page180

iDirect Remote Satellite Router Models

iDX Release 2.0 supports the following remote satellite router model types:

Evolution e8350 (DVB-S2 and SCPC modes)

Evolution X5 (DVB-S2 and SCPC modes)

Evolution X3 (DVB-S2 outbound only)

iConnex e800, iConnex e850mp (DVB-S2 and SCPC modes)

iNFINITI 8350

iNFINITI 7300, 7350

iNFINITI 5300, 5350

iNFINITI 5100, 5150

iNFINITI 3100, 3125, 3100-NB (Narrow Band)

iConnex-700, iConnex 300, iConnex 100

Note:

iBuilder User Guide

iDX Release 2.0

NetModem II and NetModem II Plus Remote Satellite Routers are not supported
in iDX Release 2.0.

141

Before You Start

6.2

Before You Start

Configuring remotes is a complex procedure. Before you start, you must know the IP
addressing scheme of your network, the specifications of all outdoor components, and the
geographic location and hemisphere of your satellite. You must also have performed the
following functions before configuring a remote:
Configured the network in which the remote will reside

6.3

Configured all of that networks parent elements

Configured one or more Inroute Groups within the network where the remotes will
reside

Adding Remotes
All iDirect remotes that transmit on an upstream TDMA carrier must be associated with an
Inroute Group. This allows all remotes assigned to an inroute group to share all carriers (line
cards) currently being serviced by the inroute group. You will probably have a multitude of
remotes associated with a given Inroute Group.
An iSCPC remote is used to establish point-to-point communications with an iSCPC line card.
Only one line card and one remote participate in any iSCPC connection. Therefore, an iSCPC
remote is not a member of an inroute group. Instead, an iSCPC remote is associated with its
peer line card. Before you can add an iSCPC remote, you must first add the iSCPC line card as
described in Adding an iSCPC Line Card on page113.
Note:

iSCPC is not supported in iDX Release 2.0.

To add and configure remotes, follow these steps:

1. If you are adding a remote to an inroute group, right-click the Inroute Group and select
Add Remote.

If you are adding an iSCPC remote, right-click the peer iSCPC line card and select Add
iSCPC Remote from the menu.

142

iBuilder User Guide

iDX Release 2.0

Remote Information Tab

6.4

Remote Information Tab

The new remote appears in the Tree with a system-generated generic name, and a dialog box
appears allowing you to define this remotes configuration parameters. The Remote dialog
box has a number of user-selectable tabs across the top. The Information tab (Figure 137) is
visible when the dialog box opens.
Note:

Many of the steps described in the remaining sections for configuring remotes
also apply to configuring iSCPC line cards. For instructions on adding an iSCPC
line card to the network tree and selecting a Hub RFT for the line card, see
Adding an iSCPC Line Card on page113.

Figure 137. Remote Information Tab

iBuilder User Guide

iDX Release 2.0

143

Remote Information Tab

Note:

If you are configuring a remote with an eight-port switch, a Switch tab also
appears on the Remote dialog box. See Remote Switch Tab on page159 for
details.

2. On the Remote Information tab, enter a Name for this remote.

3. Select the Model Type of the remote from the drop-down list. The model type you select
must match the actual hardware model.
4. Enter the Serial Number of the remote.
5. A system-generated Derived ID (DID) automatically appears.
Serial numbers are not sufficient to uniquely identify remotes and line cards. Serial
numbers are guaranteed to be unique within a particular model type, but could be
duplicated from one model type to another. To avoid potential duplicates and the
problems they would cause, iDirect uses the concept of a Derived ID, or DID. The DID is a
32-bit integer formed by joining a model type code with a units serial number. Each
remote and line card will have a unique DID value.
In the NMS, the DID is typically formatted as <Model Type Name>.<Serial Number>, for
example 5150.1492. Occasionally you may see the raw DID, however, especially when
viewing server log files or console output. You may also select the raw DID as a column to
view in iBuilders Details View.
6. The name of the remotes Inroute Group automatically appears in the Inroute Group box.
7. By default, the User Password is set to iDirect and the Admin Password is set to
P@55w0rd!. You may specify alternate passwords. The User Password provides users with
access to basic commands and the Admin password provides administrator-level access to
all commands. For security reasons, network operators should change the User and Admin
passwords from the defaults.
8. Select Active to make the Protocol Processor aware of the remote site in the network
once you apply changes at the network level. If the remote is Active, the remote is
available for access to the network.
Network operators can define the remote parameters before actually activating the
remote when it is commissioned. This option also allows you to deactivate remotes, which
removes them from the Protocol Processors current network configuration, but leaves the
configured parameters intact.
9. Select MUSiC Box, Disable Tx PWM, Disable Authentication, or Link Encryption.
a. Select MUSiC Box if this site will use a Multi User Summing Chassis at the remote site.
The iDirect MUSiC Box allows a common antenna/electronics platform to be shared
across multiple remotes that are at the same physical location. Selecting MUSiC Box
overwrites VSAT ODU settings that turn on the DC/10 MHz timing; instead, the MUSiC
Box provides the DC/10 MHz timing.
b. Select Disable Tx PWM to disable the Transmit Pulse Width Modulation on the remote
and enable console pointing mode. (With this box selected, installers dont have to
remove the transmit cable during pointing.)
c. Select Disable Authentication if you are certifying a previously-uncertified remote in
a TRANSEC network. For details, see Bringing an Unauthorized Remote into a
TRANSEC Network on page399.

144

iBuilder User Guide

iDX Release 2.0

Remote Information Tab

d. Select Link Encryption to encrypt the connection between the remote and the
protocol processor blade. You can only select Link Encryption if it is supported on
your remote model type.
10. Select Sleep in and enter a value for seconds if you want to enable Sleep Mode on the
remote. If Sleep Mode is enabled, the remote will conserve power by disabling the 10 MHz
reference for the BUC after the specified number of seconds have elapsed with no
remote upstream data transmissions. A remote will automatically wake from Sleep Mode
when packets arrive for transmission on the upstream carrier, provided that Trigger
Wakeup is selected for the service level associated with the packets. (See Adding an
Application Profile or iSCPC Profile on page238 for details.)
Note:

The Sleep Mode feature requires iDX Release 2.0.1. Earlier versions of iDX
Release 2.0 do not support Sleep Mode.

Note:

If you enable Sleep Mode, edit the QoS Service Levels that apply to the remote
to ensure that Trigger Wakeup is only enabled for those Service Levels that
match customer traffic. If Trigger Wakeup is enabled for management
traffic, the constant flow of management traffic will prevent the remote from
entering Sleep Mode.

11. In the Compression area of the dialog box, select any IP compression types you want to
enable for this remote. For details on the different types of compression available, see
Enabling IP Packet Compression Types on page180.
Note:

UDP Header Compression, UDP Payload Compression and CRTP cannot be

selected for individual mesh remotes in mesh-enabled inroute groups. Instead,
all mesh remotes in the inroute group use the settings for these parameters
that are configured for that inroute group. For details on configuring mesh
parameters for inroute groups, see Adding Inroute Groups on page129.

12. If this remote will be commissioned to send and receive mesh traffic on the inbound
carriers, enter the following parameters in the Mesh section of the dialog box:
a. Select Enabled.
b. Select a Home Inroute for this remote. Although a mesh remote can frequency hop
when transmitting to other mesh remotes, a mesh remote receives all mesh
communications on its home inroute. If you select None, the remote configuration
state will change to incomplete.
c. Enter a value for SCPC Clear Sky C/N. SCPC Clear Sky C/N is the C/N of the
downstream SCPC carrier as measured by the remote modem under clear sky
conditions. This value is typically set during remote commissioning.
d. Enter a value for TDMA Loopback Clear Sky C/N. This represents the C/N of the
loopback TDMA carrier as measured by the remote modem under clear sky conditions.
This value is typically set during remote commissioning.
See the section on Adjusting Power Settings and Configuring UCP Parameters of the
Installation and Commissioning Guide for iDirect Satellite Routers for details on setting
these parameters.
Note:

iBuilder User Guide

iDX Release 2.0

Only the following remote model types can be enabled for mesh: iNFINITI
5300/5350; iNFINITI 7300/7350; iNFINITI 8350, Evolution e8350; iConnex100/700/e800.

145

Remote Information Tab

Note:

The Timeplan Properties section of the Remote Info Tab is for future use.

6.4.1 Transmit and Receive Properties

This section discusses the transmit and receive parameters on the Information tab.

Figure 138. Remote Information Tab: Transmit and Receive Parameters

1. In the Information tabs Transmit Properties and Receive Properties panes, the Details
buttons allow you to view the details about the carriers
Note:

If you configuring an iSCPC remote or line card, you can only select the transmit
and receive carriers when defining the line card. iBuilder will automatically
assign the transmit carrier of the line card to be the receive carrier of the
remote. iBuilder will also assign the receive carrier of the line card to be the
transmit carrier of the remote. If you have not yet defined your iSCPC carriers,
see Adding Carriers on page72.

Note:

iSCPC is not supported in iDX Release 2.0.

2. In Transmit Properties, the L-Band Frequency is calculated and displayed for you once
the BUC is assigned on the VSAT tab. See Remote VSAT Tab on page169.
3. Enter the Initial Power level in dBm, based on the commissioning results. The default is
-25 dBm.
4. In Max Power, enter the maximum Tx power level in dBm as determined during remote
commissioning. The default is 0 dBm.
5. In the Receive Properties pane, you cannot select the Carrier Name, although you can
view the details regarding it.This is the downstream SCPC carrier for the network.
6. If you select Lock to Inroute, the remote will only transmit on the carrier that you select
in the Carrier Name field. This will prevent the remote from switching to any other
inbound carriers in the inroute group.
7. If desired, record the 1dB Compression Point determined at remote commissioning. This
field is informational only.
Note:

146

The L-Band Frequency is calculated for you once the LNB is assigned on the
VSAT tab. See Remote VSAT Tab on page169.

iBuilder User Guide

iDX Release 2.0

Remote Information Tab

6.4.2 Customers and Distributors

This section discusses the Customer and Distributor parameters on the Remote Information
tab (Figure 139).

Figure 139. Remote Information Tab: Customer and Distributor Parameters

Configuring customers or distributors is completely optional. The following procedure adds a
customer. However, the procedure for adding customers and distributors is the same.
1. To add a Customer or a Distributor associated with the remote, click the button to the
right of the Name box. The Add Customers or Add Distributors dialog box appears.

Figure 140. Add Customers Dialog Box

If any customers or distributors have already been added to the NMS database, the names
appear in the list.
2. To the right of the dialog box, you can click Add to add another customer or distributor.

iBuilder User Guide

iDX Release 2.0

147

Remote Information Tab

3. The Customers (or Distributors) dialog box appears.

Figure 141. Customers Dialog Box

4. Enter the Customers or Distributors Name and Phone Number.
5. Click OK. You are returned to the Customers (or Distributors) dialog box.
6. If desired, add additional Customers (or Distributors).
7. Click OK to return to the Remote Information tab.
8. The new customer or distributor appears in the boxes, as shown in Figure 142.

Figure 142. Entering Customer Parameters

9. For customers, you can enter a Commission Date, Contract Number, and additional
information in the Site Notes box.
10. If you click OK, the dialog box will close, but your changes will be saved. Instead, click
the IP tab to continue configuring the remote.

148

iBuilder User Guide

iDX Release 2.0

Remote IP Config Tab

6.5

Remote IP Config Tab

The IP Config tab consists of several individual panes and sub-tabs, each of which is displayed
and discussed in the following sections. iBuilder provides a wide range of IP configurations for
remotes accessible from the IP Config tab. All configurable IP parameters and all VLANs are
collected onto a single major tab for quick reference.

6.5.1 VLAN and LAN Information

iDirect Software supports end-to-end VLAN tagging. To implement this feature, the router or
switch that is upstream from the Protocol Processor must support IEEE 802.1Q (VLAN) tagging.
When multiple VLANs are present on the remote, a similar switch that is downstream from the
remote is also required.
A detailed, two-VLAN, multiple-remote example is shown in Figure 143. Management traffic
between the NMS and remote must be untagged and each remote must have a unique
Management IP address. Networks may contain a mixture of remote VLAN and traditional IPbased remotes. Each remote must be configured to work in either traditional IP or VLAN
mode.

Figure 143. Sample VLAN Network Layout

The iDirect VLAN capability allows customers to use their existing IP addressing schemes.
Since all routing options (RIPv2 and static routing) are configurable per VLAN interface, the
end-to-end VLAN feature allows each end customer to have their own routing architecture
independent of other customers sharing the same physical network components.
You must either enable or disable VLAN support for all remotes in a mesh inroute group. This
is accomplished by selecting or clearing a check box on the Inroute Group Information tab.
(See page132 for details.) If VLAN is selected, packets sent on both user-defined VLANs and
on the default VLAN are tagged. Remotes in the inroute group on the same user-defined VLAN
can communicate over that VLAN. All mesh remotes in the mesh inroute group can
communicate over the default VLAN.

iBuilder User Guide

iDX Release 2.0

149

Remote IP Config Tab

There are two check boxes for configuration of the Routing Information Protocol (RIPv2) on
the remote: one for the LAN interface (eth0) and one for the for satellite interface (sat0).
(The sat0 interface is called the management interface when referring to the default VLAN.)
You can enable or disable RIPv2 independently on the two interfaces. Depending on the RIPv2
options selected, the remote behaves as follows:

When RIPv2 is not enabled on either interface, RIP is completely disabled on the remote.
It does not send or receive any RIP updates.

When RIPv2 is enabled on the LAN interface, the remote sends and receives RIP updates
over the LAN, updating its own IP routing table when new routing information is received.

When RIPv2 is enabled on the satellite (or management) interface, the remote sends and
receives RIP updates over the satellite, updating its IP own routing table when new
routing information is received.

The remote does not relay RIP messages to other routers. Instead, it generates RIP messages
based on its own IP routing table.

Configuring LAN and Management Interfaces

This section discusses only the portion of the IP tab shown in Figure 144. You must select the
Interface sub-tab to configure the LAN and Management Interfaces for your VLANs.

Figure 144. Remote IP Config Tab: Interface Configuration

The IP information for a remote is configurable per VLAN. Once you have selected a VLAN on
the left side of the dialog box, you can configure its IP addressing information on the
Interface sub-tab.
1. The LAN Interface IP address represents the remotes IP address on the selected VLAN.
a. Enter the IP Address and Subnet Mask.
b. Select Tag Packets if you want to tag packets with the VLAN ID according to the IEEE
802.1Q VLAN Tagging specification.
Note:

150

Unless VLAN tagging is enabled, you will not be able to connect to the Ethernet
side of the default LAN from a hub PC. Ensure that Tag Packets is selected if
you require this capability.

iBuilder User Guide

iDX Release 2.0

Remote IP Config Tab

Note:

You can only add VLANs to remotes in a mesh inroute group if VLAN support is
enabled on the Inroute Group Information tab. VLAN tagging for mesh remotes
with VLAN enabled is always on. Therefore, you cannot modify the Tag Packets
check box if the remote is enabled for mesh on the remote Information tab. See
page132 for details on enabling or disabling VLAN support for mesh remotes.

c. If you are configuring an iConnex 100, 700 or e800, you can select Port A or Port B as
your LAN port.
Note:

If you change the LAN port selection for an iConnex e800 from Port B to Port A,
you must reset the remote before the change will take effect. Right-click the
remote in the iBuilder tree and select Reset Remote to perform this operation.

2. The remotes Management Interface (Sat) IP address represents the remotes virtual
interface on the default VLAN. The NMS always communicates with the remotes using this
address. This address should not conflict with the LAN Interface addresses.
a. Selecting Same as LAN sets the Management Interface IP address to the LAN Interface
IP address. (The Gateway is always set to 0 and cannot be changed.) This option is not
available on the iNFINITI Series 3000, 5000, or 7000 remotes.
Note:

When you select a VLAN other than the default VLAN, the interface names
change. LAN Interface changes to ETH0 Interface. Management Interface
changes to SAT0 Interface

Adding VLANs to a Remote

This section only discusses adding the VLAN configuration to Remotes. You must first define
the VLAN Upstream Interface on the VLANs tab of the Protocol Processor. See Adding a
VLAN on page94 for details.
Additional VLANs can be added and removed from a remote using the appropriate buttons
located in the VLAN area of the IP Config tab. The default VLAN is VLAN 1 (native VLAN) and
is based on the LAN Interface address.
To add a VLAN to a remote:
1. Click the Add button at the bottom of the VLAN area of the IP Config tab.

Figure 145. Remote IP Config Tab: Adding a VLAN

iBuilder User Guide

iDX Release 2.0

151

Remote IP Config Tab

Note:

For remotes in mesh-enabled inroute groups, you must select VLAN on the
Inroute Group information tab before you can add VLANs to the remotes. See
Adding Inroute Groups on page129.

The Add New VLAN dialog box appears.

Figure 146. Add New VLAN Dialog Box

2. In the Add New VLAN dialog box:
a. Select a VLAN Id
b. Enter a VLAN Name
c. Click OK.
Once a VLAN is added to the remote, it appears in the VLAN list, and the LAN and
Management Interfaces change to ETH0 and SAT0 Interface for the VLAN.
3. If you click the Remove button (see Figure 145), a warning message is displayed, asking
you to confirm the deletion. VLAN 1 is the default VLAN; you cannot remove it.
The VLAN ID is also considered in QoS Profiles. See chapter 7, Configuring Quality of Service
for iDirect Networks section Adding an Application Profile or iSCPC Profile on page238.

6.5.2 Domain Name System (DNS)

This section discusses only the DNS portion of the remote IP Config tab.

Figure 147. Remote IP Config Tab: DNS Configuration

1. You must select Enable Cache to configure the DNS settings.
2. If you want to configure DNS, you must specify both primary and secondary IP addresses.
Assigning DNS names is optional.

152

iBuilder User Guide

iDX Release 2.0

Remote IP Config Tab

3. The Cache Size, Forward Queue Size and Forward Timeout shown are default values.
Modifications may be made to these settings if desired.

6.5.3 Dynamic Host Configuration Protocol (DHCP)

This section discusses only the portion of the remote IP Config tab shown in Figure 148.

Figure 148. Remote IP Config Tab: DHCP Configuration

DHCP, including DHCP relay, is configurable on a per VLAN basis. In iBuilder, DHCP is disabled
by default.
To use an existing or separate DHCP server at your hub location:
1. Select Relay.
2. Enter the IP Address of your DHCP Server.
To enable the remote to act as the DHCP server:
1. Select Server to enable DHCP configuration entries.
2. Enter the Lease Duration or the amount of time before the address must be renewed.
3. Enter the Primary and Secondary DNS server addresses, and the Default Gateway.
4. Click the Add button to enter Client Address Ranges, which are the ranges of assignable
addresses. Multiple unique ranges may be assigned as desired.
5. To edit a Client Address Range:
a. Click the range in the table to highlight the range you want to change.
b. Select Edit.
c. Modify the range and click OK to save your changes.
6. To delete a Client Address Range:
a. Select a range in the table and click the Remove button, a warning message is
displayed, asking you to confirm the deletion.
b. Click OK to delete the range.

iBuilder User Guide

iDX Release 2.0

153

Remote IP Config Tab

6.5.4 RIPv2, Static Routes, Multicast Groups, Port Forwarding

and NAT
This section discusses the following sub-tabs of the IP Config Tab:

Routes, for configuring RIPv2 on the ETH0 and SAT0 interfaces

Static Routes, for configuring IP addressing for your static routes

Port Forwarding, for configuring port forwarding and NAT

GRE Tunnels, for setting up GRE tunnels within the iDirect system

Multicast Groups, for configuring a remote as a member of a persistent Multicast Group

Figure 149. Remote IP Config Sub-Tabs

RIPv2 (Routes Sub-Tab)

Click the Routes sub-tab to configure RIPv2 per VLAN for the LAN and/or Management
interface.

Figure 150. Remote IP Config Tab: Routes Sub-Tab

To configure RIPv2:
1. Select a VLAN in the left pane of the dialog box.
2. Select Enable RIPv2 for the LAN interface and/or Management interface to enable RIPv2
over the satellite link for the selected VLAN.

154

iBuilder User Guide

iDX Release 2.0

Remote IP Config Tab

Static Routes
Click the Static Routes sub-tab to add, edit, or remove static routes. The default route across
the sat 0 interface is added automatically when you create a new remote. Do not delete this
route unless your remote routing scheme requires it.
To add a Static Route:
1. click the Add button.

Figure 151. Remote IP Config Tab: Static Routes Sub-Tab

The Add Static Route dialog box appears.

Figure 152. Add Static Route dialog Box

2. Enter an IP Address and Subnet Mask.
3. Enter the IP address of the Gateway.
4. Select the Interface.
5. Click OK to add the Static Route.

iBuilder User Guide

iDX Release 2.0

155

Remote IP Config Tab

Using Static Routes with Multiple Protocol Processor Blades

You may use static routes between an upstream router and a multiple-blade Protocol
Processor; this removes the need for RIPv2 on the upstream LAN. In order to ensure correct
routes, you must clamp remotes to one specific blade using a custom key. You must also add
all static routes to your upstream router.

WARNING! When you clamp a remote to a specific blade, it will not re-acquire if that
blade fails. The remote will remain out-of-network until the blade is back up,
or the specific blade assignment is changed or removed using iBuilder.
Use the following procedure to clamp a remote to a specific blade:
1. Bring up the remotes Modify Dialog in iBuilder
2. Click on the Custom Key tab
3. Add the following entry to the Hub-Side section:
[BLADE]
id = <blade ID>
4. Click OK to close the dialog.
5. Apply the modified hub-side configuration.
6. Right-click the remote and deactivate it by clearing the Activate Remote check mark.

Figure 153. Deactivating a Remote

7. Apply the hub-side changes to the remote.
8. Right-click the remote again and select Activate Remote to return it to the network. The
check mark should re-appear.
9. Re-apply the hub-side changes to the remote.
To determine a blades ID, select ViewDetails from iBuilders main menu bar, and click on
the PP record in the network tree view.
Use the following procedure to turn RIPv2 off for a Protocol Processor:
1. Bring up the Protocol Processors Modify Dialog in iBuilder.
2. Clear the box labeled RIP Enabled
3. Click OK to close the dialog and apply the modified configuration.

156

iBuilder User Guide

iDX Release 2.0

Remote IP Config Tab

NAT and Port Forwarding

Click the Port Forwarding sub-tab to configure NAT and Port Forwarding on a per-VLAN basis.
NAT enables you to make the Management Interface public and the LAN interface private on
the remote, providing a way to have multiple private addresses represented by one public
address.

Figure 154. Remote IP Config Tab: Port Forwarding Sub-Tab

Port forwarding allows you to specify that IP packets with certain port numbers are forwarded
to private IP addresses behind the remote. For example, if you wanted to run a web server on
a PC with a private IP address, you could specify http as the port start and port end, with TCP
as the protocol, and then add the PCs IP address in the IP address field.
1. Select a VLAN in the left pane of the dialog box.
2. Select the Enable NAT (Network Address Translation) check box. Then click Add to open
the Add Port Forwarding dialog box.

Figure 155. Add Port Forwarding Dialog Box

3. Select a Port Range Start and Port Range End for port forwarding.

iBuilder User Guide

iDX Release 2.0

157

Remote IP Config Tab

4. Select a Protocol and specify an IP address.

5. Click OK to save your changes.

Accelerated GRE Tunnels

Click the GRE Tunnels sub-tab to configure your system to send GRE-tunneled data with TCP
acceleration across an iDirect network.

Figure 156. Remote IP Config Tab: GRE Tunnels Sub-Tab

Follow these steps to define a GRE Tunnel:
1. Click Add to open the GRE Tunnel dialog box.

Figure 157. GRE Tunnel Dialog Box

2. Specify the Hub Gateway and Remote Gateway endpoints for the tunnel.
3. Click OK to save your changes.
Note:

158

This procedure only sets up the GRE tunnel within the iDirect system. You must
still establish the actual GRE endpoints on both sides of the link for a GRE
tunnel to work. GRE endpoints must be configured upstream from the Protocol
Processor and downstream from the remote.

iBuilder User Guide

iDX Release 2.0

Remote Switch Tab

Multicast Groups
Click the Multicast Group sub-tab to add, edit, or remove a persistent Multicast Group. To
configure the remote to be a member of a persistent Multicast Group, follow these steps:
1. Click the Add button.

Figure 158. Remote IP Config Tab: Multicast Group Sub-Tab

The Persistent Multicast Group dialog box appears.

Figure 159. Persistent Multicast Group Dialog Box

2. Select the Interface: eth0 or sat0.
3. Enter an IP Address of the multicast group.
4. Click OK.
Note:

6.6

For more information, see the Technical Note titled IP Multicast in iDirect
Networks.

Remote Switch Tab

Using the Switch tab, you can associate each of the eight RJ45 Lan B Ethernet ports located
on the back panel of some iDirect remote modems with a specific VLAN. For a VLAN to appear
on the Switch tab, it must first be added to the remote on the Remote Information tab. (See
Adding VLANs to a Remote on page151). Note that the Switch tab is only displayed for
remote Model Types with an eight port switch.

iBuilder User Guide

iDX Release 2.0

159

Remote Switch Tab

By default, all VLAN ports are defined as trunks. When a port is defined as a trunk, all traffic
on any VLAN (including both user-defined VLANs and the default VLAN) can pass through the
port. All user-defined VLAN frames on trunk ports are tagged to explicitly identify the VLAN.
Default VLAN traffic passing through a trunk port is not tagged.
As an alternative to allowing a port to act as a trunk, you can define a port to be dedicated to
a single, specific VLAN. You can dedicate a port to any user-defined VLAN or to the default
VLAN. When a port is dedicated to a VLAN, only traffic for that VLAN passes through the port.
There is no VLAN tagging on a port dedicated to a single VLAN, regardless of whether the port
is dedicated to the default VLAN or to a user-defined VLAN.
The Switch tab allows you to perform the following operations:

Dedicate a port to a specific VLAN

Configure a port as a trunk (allow traffic on all VLANs to pass through the trunk)

Specify the port speed and mode (full duplex or half duplex)

Copy the table of switch settings to an external application such as a spreadsheet

To configure the eight port switch follow these steps:

1. Click the Switch tab to view the current assignment of VLANs to ports.

Figure 160. Remote Switch Tab

The Switch tab contains two panes: the Port View (on the left), and the VLAN View (on
the right). Only VLANs that have already been added to this remote appear in the display.
By default, all ports are defined as trunks. Trunk ports display the word Yes in the All
VLANs row of the VLAN View. Trunk ports also display All VLANs to the right of the port in
the Port View. This default configuration is illustrated in Figure 160.
2. You can use either the Port View or the VLAN View to dedicate a port to a single VLAN.
Both methods are described here:
To use the Port View to dedicate a port to a single VLAN:
a. In the Port View, right-click the port that you want to configure and select Assign
VLAN from the menu to display the dialog box.
Note: You can also select the port and click the Assign VLAN button at the bottom
of the screen.
b. In the dialog box, select the VLAN ID of the VLAN you want to assign to the port. (The
VLAN Name will be displayed automatically when you select the VLAN ID.

160

iBuilder User Guide

iDX Release 2.0

Remote Switch Tab

c. Click OK.
To use VLAN View to dedicate a port to a single VLAN:
a. In the VLAN View, right-click in the table cell representing the port of the VLAN you
want to configure.
b. Choose Select from the menu.
Both methods of dedicating a port to a VLAN are illustrated in Figure 161.

Figure 161. Dedicating a Port to a VLAN

In the VLAN View, the word Yes will be displayed for the VLAN in the column for the
selected port, and the Port View will display the new selection.

Figure 162. Switch Tab with Dedicated VLAN

Note:

You can double-click in any empty cell in the VLAN view to select that cell.
Double-clicking in an empty cell will select that cell, causing the word Yes to be
displayed. The cell that was previously selected will be cleared.

3. To reconfigure a dedicated port to be a trunk, do one of the following

In the Port View, right-click the port and select All VLANs from the menu.

Or, in the VLAN View, right-click in the column of the port in the All VLANs row and
select All VLANs from the menu.

Both methods are illustrated in Figure 163.

iBuilder User Guide

iDX Release 2.0

161

Remote Switch Tab

Figure 163. Reconfiguring a Dedicated Port as a Trunk

4. To select the same setting for all ports:
a. Right-click your choice in the VLAN column of the VLAN View
b. Select All from the menu.
The word Yes appears in all columns of the selected row. In Figure 164, Select All was
used to dedicate all ports to the default VLAN.

Figure 164. Selecting the Same Switch Setting for All Ports
5. By default, the port speed and port mode are automatically negotiated. Follow these
steps if you want to disable auto-negotiation and select a port speed and port mode:
a. In the Port View, right-click the port you want to configure and select Properties
from the menu to display the Properties dialog box.

Figure 165. Port Properties Dialog Box

162

iBuilder User Guide

iDX Release 2.0

Remote Switch Tab

b. In the Properties dialog box, select Off for Auto Negotiation.

c. Select a Speed for the port: 10 Mbps or 100 Mbps.
d. Select a Mode for the port: Full Duplex or Half Duplex.

WARNING! The port settings must match the attached equipment. Mismatches in either
port speed or port mode will result in packet loss.
6. To copy a row (or all rows) from the VLAN View so that you can paste the information into
a separate application such as a spreadsheet, follow these steps:
a. In the VLAN column, click the VLAN name (or click All VLANs) in the first column of
the row you want to select. This will highlight the name in the VLAN column. (Or press
Ctrl + A to select all rows in the table.)
b. Right-click on any of the selected entries in the first column; then select Copy or
Copy without headers from the menu.

c. You can now paste the row or rows you copied into your target application.

iBuilder User Guide

iDX Release 2.0

163

Remote QoS Tab

6.7

Remote QoS Tab

The following sections describe how to configure Quality of Service (QoS) on iDirects
remotes.

6.7.1 QoS Profiles

You can assign both upstream and downstream Filter Profiles and Service Profiles to any
remote. Simply select the desired profile from the four drop-down lists at the top of the QoS
tab. When you click Details, iBuilder automatically displays a read-only summary of that
profile for quick reference. For more information on assigning QoS Profiles, see Configuring
Quality of Service for iDirect Networks on page185. For an in-depth discussion on how QoS is
implemented in iDirects system, see the chapter titled QoS Implementation Principles in
the iDirect Technical Reference Guide.
The Remote QoS tab is shown in Figure 166.

Figure 166. Remote QoS Tab

164

iBuilder User Guide

iDX Release 2.0

Remote QoS Tab

6.7.2 Downstream Distributor

This section discusses only the parameters of the QoS tab shown in Figure 167. If enabled, the
downstream distributor is responsible for segmenting outbound packets for transmission. For
more information about packet segmentation, see the chapter titled QoS Implementation
Principles in the iDirect Technical Reference Guide.

Figure 167. Remote QoS Tab: Downstream Distributor

Note:

Beginning with iDS Release 8.2, the upstream segment size is automatically
calculated by the system. You can no longer configure the upstream segment
size in iBuilder.

Downstream packet segmentation defaults to disabled (unchecked). To enable it:

1. Select Enable under Downstream Distributor.
2. Enter a downstream Segment Size.

6.7.3 Rate Shaping and MODCOD Configuration

This section discusses only the parameters of the QoS tab shown in Figure 168.

Figure 168. Remote QoS Tab: Upstream and Downstream Rate Shaping
Follow the steps in this section to set the rate shaping and MODCOD parameters for an
individual remote. For the downstream carrier, you can set the Maximum Information Rate,
Committed Information Rate, and Enhanced Information Rate (EIR) for the remote. You can

iBuilder User Guide

iDX Release 2.0

165

Remote QoS Tab

also set the Nominal MODCOD and Maximum MODCOD. (EIR and MODCOD settings are for
DVB-S2 ACM networks only.)
For the upstream carrier, you can set the Maximum Information Rate, Committed
Information Rate and Minimum Information Rate for the remote. For definitions of these
parameters, see QoS Properties on page186.
Note:

Dormant Minimum Information Rate is for future use. These fields cannot be
configured in this release.

The EIR and MODCOD sections of the dialog box apply only to remotes receiving a DVB-S2
outbound carrier with ACM enabled. Note the following:

EIR is enabled for CIR allocations within the range defined by the Nominal MODCOD and
the EIR Minimum MODCOD defined of the remote.

Allocation of physical bandwidth is held constant at the remotes Nominal MODCOD when
the current MODCOD of the remote is below the EIR Minimum MODCOD.

CIR and MIR allocations to the remote are capped at the remotes Nominal MODCOD. A
remote may operate above its Nominal MODCOD, but CIR and MIR allocations are not
increased.

Note:

You can only configure upstream and downstream Committed Information Rate
(CIR) and downstream EIR from the Remote QoS tab if the corresponding QoS
mode is set to Remote Based. See QoS Modes on page193 for more
information.

Note:

You cannot configure EIR on the Remote QoS tab unless EIR has been enabled
for remotes in this Service Group. The minimum possible EIR MODCOD for the
remote is also determined by the Service Group configuration. See Adding a
Service Group on page212 for more information.

For each information rate parameter you want to configure in the Rate Shaping sections of
the QoS tab:
1. Select Enable.
2. Enter a value for the rate.
3. To configure EIR on the DVB-S2 outbound carrier for your physical remote, select a
Minimum MODCOD in the EIR section of the dialog box.
Note:

Dormant Minimal Information Rate is for future use.

For DVB-S2 ACM networks, in the MODCOD section of the QoS tab:
1. Select a Nominal MODCOD for this remote. The Nominal MODCOD is the Reference
Operating Point for this remote. A remote may operate above its Nominal MODCOD, but it
will not be granted additional CIR or MIR.
2. Select a Maximum MODCOD for this remote. A remote never operates above its Maximum
MODCOD. By default, the Maximum MODCOD of a remote is the Maximum MODCOD of
the DVB-S2 carrier of the network. The Maximum MODCOD cannot be less than the
Nominal MODCOD.
Note:

166

You should not select 16APSK as the Maximum MODCOD unless your remote is
using an internal PLL LNB.

iBuilder User Guide

iDX Release 2.0

Remote Geo Location Tab

6.8

Remote Geo Location Tab

If you are commissioning a stationary remote, use the Geo Location tab to specify the
geographic location of the installation site. Geo location can be determined by using a GPS.

Figure 169. Remote Geo Location Tab: Settings for Stationary Remotes
If you are commissioning a mobile remote, use the Geo Location tab to specify the remotes
mobile settings.

Figure 170. Remote Geo Location Tab: Settings for Mobile Remotes
Follow these steps if you are commissioning a mobile remote:
1. Select Mobile.
2. Select the correct type of GPS Input for your mobile remote.
The GPS Input selected determines the baud rate of the serial console interface to the
remote. If required, you can change the Baud Rate and other serial interface parameters
if you select Serial or NMEA. See the following section on Mobile State for a discussion
of the various GPS input selections and their associated serial port baud rates.
3. Selecting Handshake Signaling provides an input and output signal to the stabilizing
antenna through the serial console port. (See the following section on Mobile State.)
4. Selecting Mobile Security prevents the remotes latitude and longitude location from
being sent over the air to the NMS. If this is selected, it is not possible to determine the
remotes location from the hub. (See the following section on Mobile State.)

iBuilder User Guide

iDX Release 2.0

167

Remote Geo Location Tab

5. You can change the Minimum Look Angle configured for this remotes antenna by
selecting Override and entering a new angle. If you select Inherit from Satellite, the
value configured for the satellite is used for this remote. (See Adding a Spacecraft on
page69.)
6. You can change the Maximum Skew configured for this remotes antenna by selecting
Override and entering a new angle. This value represents the maximum angle of skew
that the antenna can tolerate before it stops transmitting. If you select Inherit from
Satellite, the value configured for the satellite is used for this remote. (See Adding a
Spacecraft on page69.)

Mobile State
When the remote is configured as Mobile, it looks for GPS string on the serial console port to
provide its latitude and longitude information in the form of an NMEA string. It uses this
information to compute the FSD and acquire into the network.
Once a remote has been acquired into the network, the remote automatically sends its
latitude and longitude to the hub every 30 seconds. However, when Mobile Security is
selected, the remote will not send its current geographic location to the hub. Since the
remote requires this information to communicate with the hub, mobile remote users must
determine it and communicate it to the remote, enabling the remote to compute the FSD.
In the absence of a GPS receiver interface to the modem, you can supply the latitude and
longitude information manually through the serial console interface. You can also provide the
geographic location information for the hub through the iSite GUI. (The hub geographic
location is always sent as a broadcast message from the hub.)
The baud rate of a serial connection to a mobile remote depends on the GPS Input selected in
the Mobile area of the Geo Location tab. The baud rates and typical usage of these selections
are discussed here:

Manual (9600 baud): Select Manual when the port is not connected to a GPS receiver and
you want to manually set the latitude and longitude from the remote console. Selecting
Manual will cause the modem to save the latitude and longitude to flash memory. If you
select either of the other options, this information will not be saved to flash and will be
lost in the event that the remote resets.

Serial or NMEA (4800 baud): Select Serial or NMEA when the port is connected to a GPS
receiver. The 4800 baud rate is a requirement of the NMEA protocol used by GPS to
communicate with the remote.

Antenna (9600 baud): Select Antenna when using the iDirect Automatic Beam Selection
feature. If you select this option, the port must be connected to one of the mobile
antennas supported by iDirect. For more on this feature, see Configuring Networks for
Automatic Beam Selection on page407.

Note:

The serial console interface is set to 9600 baud for non-mobile remotes.

Handshake signaling requires a stabilizing antenna and requires customers to build their own
electrical interface (converter) to communicate with the antenna. When Handshake
Signalling is enabled at the NMS, the mobile remote provides an input and output signal to the
stabilizing antenna through the serial console port. The output signal, or lock signal, indicates
the frame lock status of the receiver on the remote. The input signal TxMute is used to mute
the transmitter until the antenna pointing is completed.

168

iBuilder User Guide

iDX Release 2.0

Remote VSAT Tab

The remote sends an RS-232 active signal on the console port DTR output (pin 2) while the
modem is trying to acquire the downstream carrier. Once the remote achieves TDM frame
lock, the DTR signal becomes inactive. This signal is intended to indicate to the auto-point
antenna equipment when to switch from coarse-tune to fine-tune mode.
The DSR input on the console port (pin 7) can be used as a mute function and will allow the
auto-point antenna equipment to delay acquisition transmit until the antenna has finished
pointing. Without this function, the modem may transmit as soon as it detects TDM frame
lock, before the antenna is properly pointed and polarized. Sending an RS-232 active level to
the DSR input enables the mute function.

6.9

Remote VSAT Tab

The remote VSAT tab (Figure 171) contains two sets of inter-related VSAT tabs. The top
contains tabs and drop-down list boxes for selecting the previously defined IFL, BUC,
Reflector Mount, Reflector, and LNB. The tabs on the bottom display configuration details for
the currently selected subcomponent. Switching between tabs enables users to review the
configuration of selected subcomponents on one screen. To add these subcomponents entries
to the NMS database, see Adding Entries to Folders on page18.

Figure 171. Remote VSAT Tab

iBuilder User Guide

iDX Release 2.0

169

Remote VSAT Tab

Note:

Beginning with iDX Release 1.0, iDirect supports the XR3, XR3E, DR5 and DR7
Transceivers from ASCSignal. Each Transceiver is represented in the iBuilder
tree as both a BUC and an LNB. To select a Transceiver for your remote, you
must select the same Transceiver from both the BUC and LNB drop-down lists on
the VSAT tab. For information on changing the LNB settings for a Transceiver,
see Configuring a Remote Transceiver on page171.

Enter the following information on the VSAT tab:

1. In the Remote Antenna area, select a BUC from the BUC drop-down box. (If you are using
a Transceiver, select the Transceiver for both the BUC and LNB.)
2. Select the LNB you are using for this remote from the LNB drop-down box.
3. Selecting an IFL, Reflector Mount, and/or Reflector is optional.
4. The Approximate Cable Length should be set during the commissioning process. You can
record it here for reference.
5. The tabs on the lower half of the dialog box display the details of the components that
you have selected. Click OK to save your settings. The new remote appears in the Tree
under the Inroute Group to which you assigned it.
Note:

If you are using the iDirect Automatic Beam Selection feature, you must select a
Reflector that is configured with a controllable antenna. When you do this, a
number of additional fields will appear on the right-hand side of the Remote
Antenna area of the VSAT tab. (See Figure 172 for one example.) For details on
configuring these fields, see Configuring Networks for Automatic Beam
Selection on page407.

Figure 172. Remote VSAT Tab with SeaTel ABS Fields

170

iBuilder User Guide

iDX Release 2.0

Setting Warning Properties for Remotes

Configuring a Remote Transceiver

The XR3, XR3E, DR5 and DR7 Transceivers from ASCSignal appear in the iBuilder tree under
the Remote Antenna Components folders for both the BUC and LNB as shown below.

You can configure the LNB frequency band and cross pol selection for Transceivers from the
LNB folder of the iBuilder tree:
1. Right-click the Transceiver in the LNB folder and select ModifyItem to open the LNB
dialog box.

The Frequency Band and Cross Pol Selection fields at the bottom of the dialog box apply
to Transceivers only.

Figure 173. LNB Dialog Box: Frequency Band and Cross Pol Selection
2. Frequency Band is the LNB band selection. Select Low Band for 10.70 to 11.70 GHz with
Rx 22 KHz tone off. Select High Band for 11.70 to 12.20 GHz with Rx 22 KHz tone on.
3. Cross Pol Selection is only valid for the DRU15F16X and DRU17F16X. Select X-Pol Mode
(19V) for cross-polarization with LNB voltage of 19VDC. Select Co-Pol Mode (14V) for copolarization with LNB voltage of 14VDC.

6.10 Setting Warning Properties for Remotes

You can use iBuilder to modify both global properties of remote warnings and warning
properties for individual remotes. To change global warning properties for remotes, select
Global Warnings for Remotes from the Edit menu. To change warning properties for
individual remotes, click the Warning Properties tab for the remote you want to modify.
For details on configuring warning properties for line cards, remotes and protocol processor
blades, please see Configuring Warning Properties on page51.

6.11 Adding a Remote by Cloning an Existing Remote

You can either add a new remote by using the procedures in Adding Remotes on page142 or
you can clone an existing remote to create another remote with a new name but the same

iBuilder User Guide

iDX Release 2.0

171

Roaming Remotes

definition. The cloning feature is a quick and easy way to create several remotes with minor
differences, without having to configure each one from a blank configuration screen.
To clone an existing remote, follow the procedure below:
1. Right-click a Remote and select Clone. In the example below, the remote named Darwin
01 Rev C is being cloned. A new remote named Copy of Darwin 01 Rev C appears in the
Tree and the remote configuration dialog box is displayed.

2. Enter a new Name for the remote.

3. Modify any fields you want to change for the new remote.
4. Click OK to save your changes.

6.12 Roaming Remotes

Beginning with iDS Release 7.0, you can define mobile remotes that roam from network to
network around the globe. Roaming remotes are not constrained to a single location or
limited to any geographic region. Instead, by using the capabilities provided by the iDirect
Global NMS feature, you can configure your remote terminals to have true global IP access
Note:

Global NMS is a licensed feature. If you plan to define and track roaming
remotes in your network, please contact the iDirect Technical Assistance
Center (TAC).

The Global NMS feature allows remotes to move among networks on various transponders and
satellites, controlled from various hubs. To accomplish this, you must define the remote in all
of the networks in which it will be visible. For more information of the Global NMS feature,
see the chapter titled Global NMS Architecture in the iDirect Technical Reference Guide.
The set of parameters that defines a roaming remote falls into three categories:

Parameters that must be the same in all networks: DID, passwords, and remote name.
iBuilder will not allow you to define these parameters inconsistently across networks for
the same remote.

Parameters that must be different in each network. These consist mostly of internal
database IDs and references that are automatically established by iBuilder when the
remote is defined in multiple networks.

Parameters that may be the same or different from network to network. These dont
care parameters include everything not in the lists above. Examples are IP configuration,
QoS settings, initial transmit power values.

Once you define a roaming remote and add it to multiple networks, the dont care
parameters will be identical in all networks. At that time, you can modify these parameters in
the different networks as desired. (See Managing Dont Care Parameters on page175).

172

iBuilder User Guide

iDX Release 2.0

Roaming Remotes

Note:

Evolution e8350, iConnex e800/e800mp and Evolution X5 remotes can roam

between DVB-S2 networks and SCPC networks.

6.12.1 Adding a Roaming Remote

To define a roaming remote, first create the remote in one of the target networks using the
procedure in Adding Remotes on page142. Define this remote in the normal way for that
network, including setting IP parameters and features, VSAT components, rate limits, and
other settings.
Once you have added the remote to one network, follow these steps to add it to the
remaining networks:
1. Right-click the Remote in the Tree and select Add to Networks in the Roaming section of
the remote menu.

The Roaming dialog box opens.

Figure 174. Roaming Dialog Box

iBuilder User Guide

iDX Release 2.0

173

Roaming Remotes

2. Select the appropriate check boxes to add the remote to one or more additional
networks.
3. Click OK to save your changes and close the dialog box. iBuilder automatically adds the
remote to the selected networks, copying the dont care configuration items to the
new networks. You are free to modify the remotes configuration in the other networks as
desired.
Note:

When adding roaming remotes to networks, only networks in which the remote
is not currently configured are displayed in the dialog box.

6.12.2 Managing Roaming Remote Configuration

There are two primary ways to manage a roaming remotes configuration across all of its
network instances. Each is described in the sections that follow.
The Revision Server is completely compatible with roaming remotes. You may upgrade a
network even if a roaming remote is in another network. As long as IP connectivity is available
from the NMS to the remote, the remote will receive the download package (image and
options file), write it to flash memory, and reset. For details, see Downloading Remotes
Using Revision Server on page301.

Managing Must be the Same Parameters

You can modify the parameters that must be the same across all network instances of a
roaming remote by selecting Update Properties in the Tree for that remote. When you
change a parameter in one network using the remotes Update Properties dialog box, iBuilder
makes the same change to that remote in all of its networks.
Use the following procedure to change roaming remote parameters that must be the same in
all networks:
1. Right-click the Remote in the Tree and select Update Properties in the Roaming section
of the remote menu.

174

iBuilder User Guide

iDX Release 2.0

Roaming Remotes

2. Update the values in the Roaming Properties Update dialog box as desired.

Figure 175. Roaming Properties Update Dialog Box

3. Click OK to save your changes and close the dialog box. iBuilder updates the remote in all
of its networks.

Managing Dont Care Parameters

You can change the value for a dont care parameter on a roaming remote in a single
network by following the usual procedure: right-click the remote in the Tree for the desired
network and selecting Modify. This allows you to modify the remotes parameters in one
network while leaving them unchanged in the others.
However, it is likely that many of a roaming remotes dont care parameters will be the
same from network to network. In those instances, iDirect recommends that you use iBuilders
Group Edit feature to modify the remote. Since this method allows you to modify shared
parameters on all instances of the remote at the same time, it is both easier and less errorprone than making the changes one by one. For a general discussion of this feature, see
Working with Multiple Elements Simultaneously on page42.
Follow these steps to modify multiple instances of the same remote:
1. Select View Details from the iBuilder main menu to display the Details pane. The
Details pane is displayed to the right of the Tree.
2. Select the top-level node in the Network Tree view.

iBuilder User Guide

iDX Release 2.0

175

Roaming Remotes

3. Select View Collapse Details Hierarchy from the iBuilder main menu. This option
removes the hierarchical structure of the network elements and components so they can
all be shown in a single window.

Figure 176. iBuilder Details View with Collapsed Hierarchy

4. In the Details View, select the Type column header to sort by element type. This will
group together all remotes, regardless of their networks.
5. If desired, select the Name column header to further sort by element name. This will
group together all instances of a roaming remote, since the remote has the same name in
all networks.

176

iBuilder User Guide

iDX Release 2.0

Roaming Remotes

6. Select all desired instances of the Roaming Remote in the Details pane. Then right-click
the selected group and choose Modify from the menu. You may now modify any of the
remotes parameters that are shared across all network instances.

Figure 177. Modifying Shared Parameters of Roaming Remotes

Adding Multiple Roaming Remotes to a Network

You can add multiple roaming remotes to a network in one operation by following these steps:
1. Right-click the network in the iBuilder tree and select Add Multiple Roaming Remotes
from the menu.

iBuilder User Guide

iDX Release 2.0

177

Roaming Remotes

2. The Add Multiple Roaming Remotes dialog box appears with a list of available remotes.

Figure 178. Add Multiple Roaming Remotes Dialog Box

Remotes that already exist in more than one other network may be listed multiple times.
Select the remotes you want to add to the network. When you select a remote instance
from the list, other instances may be invalidated. Invalid selections appear in red and an
explanation is displayed in the Comment column.
3. Click OK to add the selected remotes to the network.

Adding a Roaming Remote to Multiple Network

You can add an existing roaming remote to multiple networks in one operation by following
these steps:
1. Right-click the remote in the iBuilder tree and select Add to Networks from the menu.

178

iBuilder User Guide

iDX Release 2.0

Roaming Remotes

The Add Roaming Remotes to Networks dialog box appears with a list of available
network / inroute group combinations.

Figure 179. Add Roaming Remotes to Networks Dialog Box

2. Select the network / inroute groups to which you want to add the remote.
Note: You can only select one inroute group in any network for the remote. Invalid
selections appear in red and an explanation is displayed in the Comment
column.
3. Click OK to add the remote to the selected network.

6.12.3 Beam Switching for Roaming Remotes

The decision of which network a particular roaming remote joins is made by the remote.
There are currently three beam selection methods supported by iDirect.

Automatic Beam Selection

Automatic beam selection is the most powerful and flexible way for remotes to roam from
network to network. It requires an auto-pointing antenna at the remote site, and a map
server process on the NMS.
The map server contains footprint information for all beams on all satellites in the global
network. It parcels out pieces of the map to remotes based on their current geographic
location. Depending on signal quality and location, the remote will either remain in the
current network or automatically switch to a higher-quality network.
For a technical description of the Automatic Beam Selection feature, see the iDirect
Technical Reference Guide. For details on configuring your network for Automatic Beam
Selection, see Configuring Networks for Automatic Beam Selection on page407.

iBuilder User Guide

iDX Release 2.0

179

Enabling IP Packet Compression Types

Manual Beam Selection

Users at a remote terminal can command the remote to join a particular network using the
beamselector command, available from the remotes console. The following figure shows the
command format and the output of the list option.
[RMT:2036] admin@telnet:10.0.150.7;1084
> beamselector
control
Beam selector control command
list
list known beams
mapsize
print or change the map size request params
params
stats | params | debug
switch
switch to new beam
[RMT:2036] admin@telnet:10.0.150.7;1084
> beamselector list
3 is currently selected
3 = Beam_603_340000_GA
2 = Beam_906_64000_GB
1 = Beam_605_174000_GA

Figure 180. Using the Console's beamselector Command

Round Robin Beam Selection

In the absence of both a map server and a beamselector command from the console, remotes
default to a round-robin selection algorithm. Using this method, a remote attempts to join
each network in turn until the remote has acquired a beam. Beams that cannot be acquired
are marked as unusable. The remote will not re-try an unusable beam until all other beams
have been tried. The order in which the remote tries each network is based on the perceived
quality of the networks downstream carrier, as determined by the remotes geographic
location relative to the satellite longitude.

6.13 Enabling IP Packet Compression Types

Four types of IP packet compression are supported in iDirect:

TCP payload compression

UDP header compression

UDP payload compression

CRTP (RTP header compression)

In addition, iDirect supports Layer 2 Tunneling Protocol (L2TP) payload compression using
custom keys. For details, see L2TP Payload Compression on page183.
The following sections discuss these compression type.
Note:

180

For remotes in a mesh inroute group, you must enable and disable the various
compression types at the inroute group level. The inroute group compression
settings override individual remote settings. See Adding Inroute Groups on
page129 for details.

iBuilder User Guide

iDX Release 2.0

Enabling IP Packet Compression Types

You can enable the first four compression types per remote on the remotes Information tab
by following these steps:
1. Right-click the Remote and select Modify Item.

2. In the Compression area of the Information Tab, select each compression type that you
want to enable for the remote.

Figure 181. Selecting Compression Types on the Remote Information Tab

3. Click OK to save your changes.

iBuilder User Guide

iDX Release 2.0

181

Enabling IP Packet Compression Types

6.13.1 TCP Payload Compression

You can enable TCP payload compression on your iNFINITI 5000 and 7000 series remotes to
increase the available bandwidth for TCP streams during periods of channel congestion. When
enabled, the TCP streams are compressed on both the downstream and upstream channels
simultaneously. By default, TCP payload compression is turned off.
TCP payload compression is activated only during times of congestion. If no congestion is
present, data passes through the compression layer unchanged. The compression ratio varies
depending on the amount of congestion and the nature of the TCP payload data.
Even during channel congestion, compression is not enabled under all circumstances. If a
remotes CPU utilization is above 50 percent, TCP payload compression is automatically
disabled for all sessions. If CPU utilization is below 50 percent, a maximum of five TCP
sessions are compressed. If the number of sessions exceeds five, the additional sessions are
not compressed.
Note:

TCP payload compression is available on the following remote model types:

iNFINITI 5000/7000 series; iNFINITI 8300; Evolution e8350; Evolution X5; and
iConnex 700/e800/e850mp remotes.

6.13.2 UDP Header Compression

UDP header compression is performed on per-packet basis using zlib. Unlike TCP Payload
compression, it is not stream-based. UDP header compression is available for all iDirect
remote model types.
iDirect UDP header compression follows the specification in RFC 2508, Compressing
IP/UDP/RTP Headers for Low-Speed Serial Links. This RFC defines both CRTP (header
compression for RTP packets) and UDP header compression (for other UDP packets). When you
enable UDP header compression in iBuilder, only non-RTP headers are compressed for UDP
packets. If you want header compression to be applied to RTP packets, you must enable CRTP.
(See CRTP on page182.)
The iDirect UDP header compression implementation is a simplex-based compression scheme
with the periodic retransmission of full headers to restore the compression state in the event
of error.

UDP Header Compression Performance Characteristics

You can expect the following performance characteristics for UDP header compression in
iDirect networks:

The 28-byte header is typically reduced 8 bytes.

The average compressed header size is 9.25 bytes.

The reduction in header size is approximately 67 percent.

6.13.3 CRTP
Compression of RTP packet headers (CRTP) is performed on per-packet basis using zlib. Unlike
TCP Payload compression, it is not stream-based. CRTP is available for all iDirect remote
model types.

182

iBuilder User Guide

iDX Release 2.0

Enabling IP Packet Compression Types

iDirects implementation of the CRTP algorithm follows the specification in RFC 2508,
Compressing IP/UDP/RTP Headers for Low-Speed Serial Links. This RFC defines both CRTP
(header compression for RTP packets) and UDP header compression (for other UDP packets).
When you enable CRTP in iBuilder, only RTP packet headers are compressed. If you want
header compression to be applied to other UDP packets, you must enable UDP header
compression. (See UDP Header Compression on page182.)
The iDirect CRTP implementation is a simplex-based compression scheme with the periodic
retransmission of full headers to restore the compression state in the event of error. Correct
functionality of the CRTP implementation has been field-proven in multiple releases.

RTP Header Compression Performance Characteristics

You can expect the following performance characteristics for RTP header compression in
iDirect networks:

The 40-byte header is typically reduced to 10 bytes.

The average header size is 11.875 bytes.

The reduction in header size is approximately 70 percent.

6.13.4 UDP Payload Compression

iDirects UDP payload compression algorithm is similar to the algorithm used by iDirect for
TCP payload compression. (See Section6.13.1 TCP Payload Compression for details.)
However, the implementation differs in the following significant areas:

UDP payload compression is packet-based rather than session-based.

The UDP payload compression algorithm always attempts to compress UDP packets prior
to transmission. Unlike TCP payload compression, it does not make dynamic decisions
based on congestion, system load, etc.

UDP payload compression is designed specifically for the GSM backhaul market. It is unlikely
that enabling UDP payload compression will have any noticeable benefit for standard voice
traffic, since this type of traffic normally cannot be compressed. iDirect does not recommend
enabling this compression feature for typical VoIP traffic; it will not increase channel capacity
and it will put unnecessary strain on the remotes processor.

6.13.5 L2TP Payload Compression

Layer 2 Tunneling Protocol (L2TP) is a tunneling protocol used to support applications such as
Abis over IP and Virtual Private Networks (VPNs). By default, L2TP payload compression is
disabled. You can enable L2TP payload compression for your remote as follows:
1. Right-click the remote in the iBuilder Tree and select ModifyItem.
2. Click the Custom tab.
3. Configure the following custom key in both the Hub-side Configuration area and the
Remote-side Configuration area of the Custom tab:
[L2TP]
passthru = 0

iBuilder User Guide

iDX Release 2.0

183

Enabling IP Packet Compression Types

This is illustrated in Figure 182.

Figure 182. Enabling L2TP Payload Compression

4. Click OK to save your changes.
5. Right-click the Remote and select Apply ConfigurationReliable Both (TCP) to apply the
changes.
You can disable L2TP payload compression by returning the passthru settings to the default
state:
[L2TP]
passthru = 1

184

iBuilder User Guide

iDX Release 2.0

7 Configuring Quality of
Service for iDirect
Networks

Quality of Service (QoS) refers to the classification and prioritization of IP traffic in order to
optimize the delivery of packets as they flow through your iDirect network. Attributes of a
connection that affect QoS include throughput, latency, jitter and packet loss, among others.
When available bandwidth is greater than demanded bandwidth, all bandwidth needs are met
and there is no requirement for a QoS algorithm designed to optimize network performance.
When demand exceeds bandwidth, however, the algorithm that divides the available
bandwidth to best accommodate the current demand becomes very important. Whether the
bandwidth is distributed equally or unequally, the distribution of available bandwidth in the
face of contention is subject to some sort of business model.
Group QoS (GQoS), introduced in iDS Release 8.0, enhances the power and flexibility of
iDirects QoS feature for TDMA networks. It allows advanced network operators a high degree
of flexibility in creating subnetworks and groups of remotes with various levels of service
tailored to the characteristics of the user applications being supported.
Because QoS and Group QoS are complex in nature, iDirect has designed a scheme that allows
the average operator to continue to maintain the QoS configurations much as before, while
offering the flexibility for advanced users to customize the Group QoS configuration to meet
the requirements of more complex QoS models. To accomplish this, a new permission called
GQoS Planning can now be set for iBuilder users. By creating NMS users with this
permission, you can restrict Group QoS configuration changes to designated operators. Users
without this permission can view Group QoS settings, but they cannot change them. (See
chapter 13, Managing User Accounts and User Groups for details on defining users.)
Note:

iBuilder User Guide

iDX Release 2.0

Group QoS is only applicable to TDMA networks. QoS configuration for iSCPC
connections works much the same as it did in earlier releases. See QoS for
iSCPC Connections on page235 for details.

185

Group QoS Description

This chapter contains the following major sections:

7.1

Group QoS Description on page186

Configuring Group QoS on page197

Working with Group Profiles on page228

QoS for iSCPC Connections on page235

Application Profiles, iSCPC Profiles and Filter Profiles on page235

Assigning QoS Profiles to Multiple Remotes on page246

Group QoS Description

Group QoS is built on the Group QoS tree: a hierarchical construct within which containership
and inheritance rules allow the iterative application of basic allocation methods across groups
and subgroups. QoS properties configured at each level of the Group QoS tree determine how
bandwidth is distributed when demand exceeds availability.
Group QoS enables the construction of very sophisticated and complex allocation models. It
allows network operators to create network subgroups with various levels of service on the
same outbound carrier or inroute group. It allows bandwidth to be subdivided among
customers or service providers, while also allowing oversubscription of one groups configured
capacity when bandwidth belonging to another group is available.
QoS properties and the Group QoS tree are described in detail in the next sections.

7.1.1 QoS Properties

Each node in the Group QoS tree has properties related to bandwidth allocation and
bandwidth requests. These properties are separately configured for each node in the tree.
How these properties are configured determines how available bandwidth is distributed
among groups of competing nodes in the tree. (Details of the tree structure are contained in
Group QoS Hierarchy on page190.)
The Group QoS configuration properties that can be defined using iBuilder are described here.

186

Priority: Priority defines the order in which bandwidth is exclusively allocated among
competing nodes. You can select five priorities: Multicast (the highest priority, reserved
for outbound multicast traffic), followed by P1 through P4. All higher-priority bandwidth
is allocated before any lower-priority bandwidth is allocated. Note that cost-based traffic
and best-effort traffic have lower priorities than traffic with priorities Multicast through
P4.

Cost: Cost is a QoS attribute used to apportion bandwidth among competing nodes at the
same priority when demand exceeds availability. When bandwidth is limited, the relative
costs of all competing nodes with the same priority are used to distribute the remaining
bandwidth. For example (ignoring CIR discussed below), a node configured with a cost of
.5 will receive twice as much bandwidth as a node configured with a cost of 1.

Cost-Based: Cost-based traffic receives bandwidth allocation only after all priority
(Multicast through P4) traffic allocations have been made among competing nodes. As
with other priorities, if demand exceeds availability for cost-based traffic, the relative
costs of all competing nodes are used to apportion the remaining bandwidth.

iBuilder User Guide

iDX Release 2.0

Group QoS Description

Best Effort: Best-effort traffic is allocated bandwidth only after all priority traffic and all
cost-based allocations have been made among competing nodes. In other words, no
bandwidth is granted for best-effort traffic until all other demand has been met.

Maximum Information Rate (MIR): MIR specifies the maximum amount of bandwidth that
will be allocated to a node, regardless of demand generated by the node. A node with MIR
set will never be granted more bandwidth than the configured MIR bit rate.

Note:

The QoS bandwidth allocation algorithm does not strictly enforce MIR for
inroute traffic. Therefore, it is possible that a node may receive more
bandwidth than the configured maximum if free bandwidth is available.
However, this does not affect bandwidth allocations for competing nodes. Note
that MIR is strictly enforced for outbound traffic.

Committed Information Rate (CIR): CIR specifies an amount of bandwidth that is allocated
to a node before additional (non-CIR) bandwidth is allocated to that node for traffic with
the same priority. At any priority level, all competing nodes are first granted their CIR
bandwidth to the extent possible. If CIR demand is met, additional demand exists, and
additional bandwidth is available, then the remaining (non-CIR) demand is met to the
extent possible.

Sticky CIR: In general, CIR is redistributed each time bandwidth is requested in

accordance with the CIR levels configured for all competing nodes. Thus the amount of
CIR granted to a node may vary from one frame to the next during congestion, depending
on competing demand.
Rather than allocating new CIR based solely on current requests, Sticky CIR favors nodes
with previous CIR allocations as long as those nodes continue to request bandwidth. This
can reduce the allocation of CIR bandwidth to competing nodes. Sticky CIR is useful for
VoIP applications.

Full-Trigger CIR: If you configure Full-Trigger CIR for a remote application, the remote
will be granted all of its configured CIR bandwidth whenever any CIR bandwidth is
requested. For example, if the remote is configured with 500 kbps of CIR but current
traffic requires only 10 kbps of bandwidth, the remote will be granted the full 500 kbps of
bandwidth even though it only requested 10 kbps.

Note:

Unlike the other QoS properties described here, Full-Trigger CIR can only be
configured with a remote custom key. See Configuring Full-Trigger CIR for a
Remote on page226 for details.

Allocation Fairness Relative to CIR: If you select this option then, during contention for
bandwidth, bandwidth allocation is proportional to the configured CIR. This favors QoS
nodes with higher CIR settings, since those nodes are granted a larger portion of the
available bandwidth. If this option is not selected, bandwidth is allocated equally to
competing nodes until available bandwidth is exhausted. If selected, this option applies
to both CIR and best-effort bandwidth allocation. (See Allocation Fairness Relative to
MODCOD on page208 for more details.)

Enhanced Information Rate (EIR): EIR only applies to networks that use DVB-S2 with
Adaptive Coding and Modulation (ACM). ACM adjusts the modulation and coding (MODCOD)
of the outbound channel on a frame-by-frame basis depending on the current receive
capabilities of the individual remotes in the network.
EIR is enabled only within the range of MODCODs from the Nominal MODCOD configured
for a remote down to the EIR Minimum MODCOD configured for a remote application. (See

iBuilder User Guide

iDX Release 2.0

187

Group QoS Description

page226.) Within this range, the system attempts to sustain the bandwidth allocations
required for the remote to meet its configured QoS information rates (CIR and MIR) even
as the encoding of the remotes downstream data drops to lower MODCODs. This is
accomplished by increasing the bandwidth allocated to the remote application in order to
compensate for the additional bits required for error correction at the lower MODCODs.
When the remotes current MODCOD is below the EIR minimum MODCOD, the system
ignores the current MODCOD status of the remote when allocating bandwidth. Instead,
physical bandwidth is allocated to the remote application as if it were receiving the
outbound carrier at the Remotes Nominal MODCOD. Therefore, below the minimum
MODCOD, the system does not attempt to meet the CIR or MIR settings and the remotes
information rate will decrease based on the satellite bandwidth required at the remotes
nominal MODCOD. For more information on EIR, see the DVB-S2 chapter of the iDirect
Technical Reference Guide.

Allocation Fairness Relative to MODCOD: This property only applies to networks that use
DVB-S2 with Adaptive Coding and Modulation (ACM). If you select this option, bandwidth
allocation is based on information rate rather than raw satellite bandwidth. This favors
remotes at lower MODCODs, since their satellite bandwidth allocations must increase to
achieve the same information rate as remotes at higher MODCODs. If this option is not
selected, satellite bandwidth is allocated without regard to MODCOD. This favors remotes
at higher MODCODs, since the higher the MODCOD, the greater the information rate for
the same amount of bandwidth.

Change to MIR and CIR Bandwidth Calculation

Prior to iDX Release 2.0, upstream MIR and CIR settings for Group QoS nodes were based on
Information Rate, while upstream MIR and CIR settings for physical remotes (as specified on
the Remote QoS tab) were based on IP Data Rate. Information Rate includes iDirect overhead,
which can be significant on the upstream, depending on the FEC rate of the carrier. On the
other hand, IP Data Rate does not include iDirect overhead. Therefore, upstream MIR and CIR
values configured for Group QoS were not equivalent to upstream MIR and CIR values
configured for physical remotes.
Beginning with iDX Release 2.0, all upstream CIR and MIR throughout the system are based on
IP Data Rate. Therefore, if you upgraded from a pre-2.0 release, the upstream Group QoS CIR
and MIR values configured for your inroute groups may represent more satellite bandwidth
than they did in your earlier release.
Table 5 shows the relationship between the pre-2.0 and 2.0 (or later) upstream MIR or CIR
configurations. For example, for FEC Rate .793, a configured CIR of 1000 kbps in a pre-2.0
release is equal to a configured CIR configuration of 902.455 kbps in Release 2.0 or later.
Table 5. iDirect Overhead on Upstream Carriers
FEC Rate

188

Pre- 2.0
MIR or CIR

Equivalent 2.0
iDirect
MIR or CIR
Overhead

TPC-441/1024 (.431)

1000 kbps

676.457 kbps

32.35%

TPC-546/1024 (.533)

1000 kbps

718.280 kbps

28.17%

TPC-676/1024 (.66)

1000 kbps

752.046 kbps

24.80%

TPC-3249/4096 (.793)

1000 kbps

902.455 kbps

09.75%

iBuilder User Guide

iDX Release 2.0

Group QoS Description

Bandwidth Allocation Algorithm

The basic algorithm for allocating bandwidth among competing nodes is:
While bandwidth is available:
For each priority level competing for bandwidth:
If CIR demand exists:
Allocate bandwidth for CIR demand.
If non-CIR demand exists:
Allocate bandwidth for non-CIR demand.
Thus, any higher-priority traffic has the potential to starve lower-priority traffic, and CIR
configurations only affect how bandwidth is allocated among requests at the same priority.
Due to the risk of starvation of lower-priority traffic, iDirect recommends that you configure
MIR for higher-priority Applications when unequal priorities are competing for bandwidth.
Priorities are considered in the following order by the algorithm as long as bandwidth is
available:

Multicast (Available only to Group QoS nodes in the Network Multicast Bandwidth Group)

P1 through P4

Cost-based

Best-effort

For more details on iDirects QoS implementation, see the chapter titled QoS
Implementation Principles in the iDirect Technical Reference Guide.

iBuilder User Guide

iDX Release 2.0

189

Group QoS Description

7.1.2 Group QoS Hierarchy

The Group QoS tree is an organization of nodes into groups and subgroups for the purpose of
allocating bandwidth to each node based on the properties and rules that you configure for
your networks bandwidth.
Figure 183 shows the Group QoS tree. The elements shown in the diagram are defined later in
this section.
Bandwidth
Pool

Bandwidth
Group 1

Service
Group 1
Applications
Default
Profile

Remote 1

Bandwidth
Group 2

Service
Group 2
Applications
Default
Profile

Special
Profile

Remote 2

Service
Group 3
Applications
Default
Profile

Remote 3

Service
Group 1
Applications
Default
Profile

Remote A

Service
Group n
Applications
Special
Profile

Default
Profile

Remote B

Figure 183. Group QoS Hierarchy

A node is a basic element in the Group QoS tree and can either be a terminating element or a
container for other nodes. Beginning at the highest (root) node in the Group QoS tree,
available bandwidth is allocated by that node to all subnodes based on operator-defined QoS
properties and the current demand as indicated by the subnodes.
Only terminating (leaf) nodes generate demand. As demand moves up the tree in the form of
bandwidth requests, each higher-level (parent) node aggregates demand from its subnodes
before passing it up in the form of its own request. All demand reaches the root in a single
request representing the total demand of all leaf nodes.
Bandwidth allocation begins at the root node and flows down the tree. Each node subdivides
its own allocation among its subnodes based only on the Group QoS properties of the
subnodes. Therefore each node competes for bandwidth only within its own node group (i.e.
the set of subnodes that share a parent node). Each remote prioritizes the use of its allocated
bandwidth according to QoS properties configured for the different types of applications that
generated the demand in the first place. (See QoS Properties on page186.)
The properties configured for a parent node supersede those of its subnodes when those
properties conflict. For example, the total maximum bandwidth granted to all nodes in a node
group will never exceed the maximum bandwidth configured for the parent node, regardless
of the configuration of its subnodes.

190

iBuilder User Guide

iDX Release 2.0

Group QoS Description

Note:

For flexibility, the NMS does not attempt to enforce limits on subnodes based
on the properties of the parent node. For example, the total CIR configured for
a node group may exceed the CIR configured for the parent node. If CIR is
oversubscribed in this way, it is possible that all nodes will not receive their
full CIR allocations during times of heavy traffic.

Bandwidth Pool
A Bandwidth Pool represents the root of a Group QoS tree. Therefore, all other groups in the
tree are contained in the Bandwidth Pool. In iDirect, a Bandwidth Pool can be either an
Outroute or an Inroute Group.

Bandwidth Group
A Bandwidth Pool can be divided into multiple Bandwidth Groups. By defining Bandwidth
Groups, a network operator can subdivide an Outroute or Inroute Group into multiple QoS
groups, each with its own QoS properties.
A Network Operator might use multiple Bandwidth Groups to divide a Bandwidth Pool among
different Service Providers or Virtual Network Operators (VNOs). In addition, a separate
Bandwidth Group is automatically created to handle all mesh traffic transmitted over a meshenabled Inroute Group. Bandwidth Groups can be configured with CIR and MIR to enforce the
desired division of the total bandwidth among the Bandwidth Groups.
Note:

The bandwidth allocation algorithm cannot guarantee that MIR configured at

the Bandwidth Group and Service Group levels will be met.

Service Group
Just as a Bandwidth Pool can be divided into multiple Bandwidth Groups, a Bandwidth Group
can be subdivided into multiple Service Groups, each with its own QoS properties. Service
Groups, along with the Applications they contain, are used to define Service Profiles that are
then assigned to remotes.
A Service Group might be used solely to partition the bandwidth of a Bandwidth Group among
sub-groups; or it might be used to differentiate groups by class of service. For example, an
operator or a VNO might further divide a Bandwidth Group into Service Groups and assign
each Service Group to a different customer, using CIR and MIR to enforce the desired division
of the total bandwidth among the Service Groups. Or a Service Provider might create Service
Groups to offer multiple levels of service, using a combination of Priority, Cost and CIR/MIR to
create tiered service.

Application
A Service Group contains two or more Applications. (An NMS Application and a Default
Application are required for every Service Group except those configured for mesh traffic.)
Like Bandwidth Groups, each Application is configured with QoS properties. In addition, an
Application is associated with one or more Upstream or Downstream Application Profiles,
containing Service Levels and Rules for that Application. Upstream Application Profiles are
assigned to Inroute Groups to manage Inroute traffic. Downstream Application Profiles are
assigned to Outroutes to manage Outroute traffic.

iBuilder User Guide

iDX Release 2.0

191

Group QoS Description

Service Profile
Like Service Groups, a Service Profile contains two or more Applications, each of which
consists of the Service Levels and Rules specified by their respective Application Profiles. You
can view a Service Profile as the implementation of a Service Group. In other words, a Service
Group provides a template from which you can create your Service Profiles.
Service Profiles are assigned directly to Remotes. When you assign a Service Profile to a
remote, the Applications contained in the Service Profile are applied to the remote as Virtual
Remotes.
When you create a new Service Group, you automatically create a default Service Profile for
the new group containing the NMS and Default Applications. (These two Applications are part
of every Service Group and Service Profile.) When you add Applications to Service Groups,
those Applications are added to the list of Applications that you can select for the Service
Profiles based on that Service Group. (See Creating Service Profiles on page217 for further
details.)

Application Profile
Application Profiles are fundamental building blocks of Group QoS. They define the
Applications that are used by Service Profiles. In addition to being configured with QoS
properties that determine packet scheduling, Application Profiles contain one or more rules
that determine which packets match the type of traffic defined by the Application Profile.
Rules specify boolean operations that are performed on individual fields in IP packet headers
to determine whether or not packets match Applications using the Application Profile.
An Application Profile is typically used to categorize packets for a specific traffic type, such
as NMS traffic, Voice over IP (VoIP) traffic, etc. The Default Application Profile is used to
handle any traffic not explicitly defined by the other Application Profiles in a Service Profile.

Virtual Remote
When you assign a Service Profile to a remote, you are configuring the remote with the
complete set of the Applications specified in the Service Profile. Each individual Application
running on a remote is called a Virtual Remote. The physical remote makes independent
requests for bandwidth for each of its Virtual Remotes in accordance with the properties
assigned to that Application.

192

iBuilder User Guide

iDX Release 2.0

Group QoS Description

7.1.3 QoS Modes

When configuring QoS for your outbound channels and inroute groups, you can select one of
three QoS modes:

Remote Based

Application Based

Application Scaled

By selecting a QoS mode for your Networks and Inroute Groups in iBuilder, you can affect
upstream and downstream GQoS behavior, respectively. The behavior of each mode is
described here.

Remote Based Mode

Selecting Remote Based as the QoS mode provides pre-GQoS compatibility. It allows you to
configure all upstream and/or downstream rate shaping parameters on the QoS tab for each
remote. These parameters include Maximum Information Rate (MIR), Committed Information
Rate (CIR), Minimum Information Rate (MIN), and Enhanced Information Rate (EIR).
When you upgrade to a release that supports QoS modes, the upgrade procedure sets the QoS
mode for all existing outroutes and inroute groups to Remote Based. Once you have upgraded,
you have the option to configure some or all of your networks and inroute groups to use Group
QoS by selecting another QoS mode. If you choose to continue operation in the Remote Based
mode, then you can continue to configure upstream and downstream CIR on the Remote QoS
tab.
If you are operating in Remote Based QoS mode, you will define your QoS settings much like
you did in pre-8.0 releases. In other QoS modes, you define multiple Applications per remote.
These Applications run on the physical remote as Virtual Remotes. Each Virtual Remote is
responsible for bandwidth allocation for its own application.
However, in Remote Based mode, remotes do not run multiple QoS Applications. Since the
concept of Virtual Remotes is not applicable in this mode, you cannot define individual
request and allocation properties for Applications. Although Group QoS can be configured for
inroute groups and networks in Remote Based mode, all Group QoS Applications are merged
into a single Application in the remote-side and hub-side remote options files. Therefore,
Application properties such as MIR, CIR and Priority defined for new QoS Applications are not
used in Remote Based mode.

iBuilder User Guide

iDX Release 2.0

193

Group QoS Description

This is illustrated by Figure 184.

Figure 184. Remote Based Mode vs. Application Based Mode

When Remote Based QoS Mode is selected (top image), no properties are shown for the two
Applications (NMS and Default). When Application Based is selected, the GQoS Application
Properties appear and can be configured by the operator. This is true because Remote Based
Mode collapses all Applications into a single Application that is executed on the physical
remote. If you want to change properties such as Priority or Cost for Remote Based traffic,
you can configure these parameters per Service Level.
As in pre-8.0 releases, you define the QoS behavior of a remote in Remote Based mode by
creating Service Levels in QoS profiles. Service Levels contain Rules and matching criteria that
are compared in order to IP packets until a match is found. Once a packet matches a Rule, no
further comparisons are made.
Remote Based QoS differs from pre-8.0 QoS in that, rather than each remote being assigned a
single Traffic Profile, each remote is assigned a Service Profile derived from multiple
Application Profiles, each with its own list of Service Levels. (Application Profiles are similar
to pre-8.0 Traffic Profiles.) This means that the order in which Service Levels are applied to IP
traffic is determined by the order of the Applications in the Service Profile. If the packet does
not match any Service Levels in the first Application, it is compared to those in the second
Application, and so on, until a match is found. Therefore, it is very important that you add
new Applications to your Service Profiles so that the correct overall order of the Service
Levels is maintained across all Applications.
When you upgrade from a pre-8.0 release, Traffic Profiles currently assigned to remotes are
converted to Application Profiles. Those new Application Profiles are automatically included
in new Service Profiles, and the Service Profiles are assigned to those remotes that were using
the equivalent Traffic Profiles. (Traffic profiles not assigned to remotes are removed from the
QoS folders.) After the upgrade, you can assign these Service Profiles to remotes on the
Remote QoS tab, the same way you assigned Traffic Profiles to remotes prior to GQoS.

194

iBuilder User Guide

iDX Release 2.0

Group QoS Description

However, if you require a new Application Profile to be used by some of the remotes in your
network, you will need to create a new Service Profile that uses the new Application Profile,
and then assign the Service Profile to the Remotes. You must use the Group QoS feature to
create Service Profiles from Application Profiles. See the Creating Service Profiles on
page217 for details.

Application Based Mode

Selecting Application Based as the QoS mode for a network or inroute group fully enables the
GQoS feature. Although MIR and MIN configured on the Remote QoS tab will be maintained,
CIR will not. You can configure CIR at a number of levels in the GQoS hierarchy. If you require
different CIR settings for individual remotes, you must override the general GQoS CIR
configuration on your Virtual Remotes. Configuring your Group QoS settings is discussed in
detail in the remainder of this chapter.

Application Scaled Mode

Application Scaled mode is intended for complex GQoS configurations that result in a large
number of Virtual Remotes executing on a single physical remote. For example, in networks in
which remotes provide service to multiple customers with different QoS requirements, the
large number of Virtual Remotes executing on each physical remote may degrade network
performance. In such cases, Application Scaled mode may be preferable to Application Based
mode.
Application Scaled mode is identical to Application Based mode with one exception.
Application Based mode results in a minimum of two Virtual Remotes for every physical
remote: NMS and Default. Each additional Virtual Remote increases the processing load on the
protocol processor and the remote during bandwidth allocation.
Application Scaled mode merges the NMS and Default Virtual Remotes into a single Virtual
Remote to improve performance. This merging is performed in the hub-side and remote-side
options files; not on the GUI. Therefore, even though these two Virtual Remotes are combined
on the protocol processor and on the remote, this is not visible on the iBuilder GUI. Both the
NMS and Default Applications (and Virtual Remotes) still appear on the GQoS screens.
Note:

Although iBuilder still allows you to configure the NMS and Default Applications
in Application Scaled mode, the Default Application properties override the
NMS Application properties for any conflicting settings. Therefore, changing
the properties of the NMS Application to be different from those in the Default
Application has no effect in this mode, and can be misleading.

Setting the QoS Mode

In iBuilder, you can select the QoS mode for an Inroute Group or Outroute as follows:
1. Right-click the Inroute Group or Network in the iBuilder tree and select ModifyItem.
2. Click the Group QoS tab.

iBuilder User Guide

iDX Release 2.0

195

Group QoS Description

3. Select the desired QoS Mode.

Figure 185. Selecting the QoS Mode

4. Click OK to save your changes.
Selecting the QoS Mode for an Inroute Group is illustrated in Figure 185. The Network Group
QoS tab has an identical QoS Mode setting that applies to the Networks Outroute. The default
QoS Mode is Remote Based.

7.1.4 Multicast Bandwidth Group

Beginning with iDX Release 2.0, a new default Bandwidth Group named Multicast is
automatically created for every network. This Bandwidth Group can be used to manage both
the NMS and user multicast traffic on the outbound carrier. The Multicast Bandwidth Group
has the following characteristics:

There is only one Multicast Bandwidth Group per Network. Therefore you cannot clone
the Multicast Bandwidth Group, insert additional multicast Bandwidth Groups, or delete
the Multicast Bandwidth Group.

The Multicast Bandwidth Group must contain one and only one Service Group. Therefore
you cannot clone the default Service Group, delete the default Service Group or insert
additional Service Groups under the Multicast Bandwidth Group.

Like other Bandwidth Groups, the Multicast Bandwidth Group contains two Applications
by default: NMS and Default. The NMS application is used for outbound multicast NMS
traffic.

By default, the Multicast Bandwidth Group, its Service Group, and all multicast
Applications are assigned Multicast priority, the highest priority setting. This setting is
only available for the Multicast Bandwidth Group, its Service Group, and multicast
Applications.

You cannot disable MIR for the Multicast Bandwidth Group. The minimum value that you
can set for Multicast MIR is 128 kbps.

If you are configuring a DVB-S2 ACM network, you can select a different Multicast
MODCOD for each Application. By default, NMS multicast traffic is sent on the Minimum
MODCOD of the DVB-S2 carrier. See Adding an Application on page214 for details.

You can create new multicast Application Profiles and add new Applications for user multicast
traffic the same way that you add applications to other Bandwidth Groups. See Configuring
Group QoS on page197 for details.

196

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

7.2

Configuring Group QoS

This section explains how to use iBuilder to configure Group QoS settings for your Networks
and Inroute Groups. You can define Group QoS parameters in three places in iBuilder:

On the Network Group QoS tab, you can define Group QoS settings for an Outroute and
assign Group QoS Service Profiles to the remotes using that Outroute.

On the Inroute Group QoS tab, you can define Group QoS settings for an Inroute Group and
assign Group QoS Service Profiles to the remotes using that Inroute Group.

In the Group Profile Upstream and Downstream folders of the iBuilder tree, you can
create Group QoS profiles that you can later assign to your Networks and Inroute Groups
from the Group QoS tab.

When you create a new Network or Inroute Group in the iBuilder tree, the default
downstream or upstream group profile is used to automatically configure the default QoS
settings for the new bandwidth pool.
The default Group QoS configuration for a Network contains:

Two default Bandwidth Groups, one named Multicast and one named Bandwidth

The default Group QoS configuration for an Inroute Group contains:

A single Bandwidth Group named Bandwidth

Each default Bandwidth Group contains a single default Service Group named Service Group
Each default Service Group contains two default Applications:
An Application named NMS to manage bandwidth for NMS traffic

An Application named Default to manage all other bandwidth

The default Bandwidth Group for an Inroute Group is applied to star traffic only. If you create
a mesh-enabled Inroute Group, a second Bandwidth Group named Mesh Bandwidth is also
created to handle packets sent on the mesh overlay. By default, the Mesh Bandwidth Group
contains a single Service Group with a single Application called Mesh. The default Mesh
Application matches unreliable (UDP) traffic sent between mesh remotes.
You can modify the default Mesh Application and add additional Applications to the Mesh
Bandwidth Group. All traffic matching Applications in that group will be sent over the mesh
network. Since mesh does not support TCP acceleration (or spoofing), any TCP traffic sent
over mesh will not be accelerated.
Note:

Mesh is not supported in iDX Release 2.0.

The procedures in this section assume that you have already opened the Group QoS tab for
your Network or Inroute Group. Many of the same operations are also available when
configuring upstream or downstream Group Profiles. (See Working with Group Profiles on
page228 for details on Group QoS profiles.)

iBuilder User Guide

iDX Release 2.0

197

Configuring Group QoS

To open the Group QoS tab:

1. Depending on the Bandwidth Pool you want to configure, right-click your Network or
Inroute Group in the iBuilder Tree and select ModifyItem.

2. When the dialog box appears, click the Group QoS tab.

7.2.1 The Group QoS User Interface

The Group QoS user interface allows you to configure and view all Group QoS settings for
Bandwidth Groups, Service Groups and Applications. It also allows you to configure Service
Profiles and assign them to your remotes. The Group QoS User Interface has four views,
described in the following sections:

Group View

Profile View

Profile-Remote View

Remote View

To select any of the Group QoS views, right-click anywhere in the main area of the Group QoS
tab and select the view you want to display.

Figure 186. Selecting the Group QoS View

198

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

Note:

Profiles is not an Application. Rather, double-clicking the Profiles folder

provides a convenient way to switch from the Group QoS Group View to the
Profile View. See Configuring Group QoS on page197 for details on the
different Group QoS views.

Group View
The Group View (Figure 187) shows the Group QoS Hierarchy (Bandwidth Groups, Service
Groups, and Applications) and the properties associated with each group in the tree. The
Group View illustrated in the following figure shows an Inroute Group with a single Bandwidth
Group divided into two Service Groups.

Figure 187. Group QoS: Group View

Some characteristics of the illustrated Bandwidth Group are:

A Maximum Information Rate (MIR) of 5 Mbps, with 3 Mbps dedicated to SG 1 and 2 Mbps
dedicated to SG 2.

Since SG 1 has an MIR that is higher than its Committed Information Rate (CIR), SG 1 can
be granted bandwidth over its CIR limit if all of SG 2s CIR demand is met and additional
bandwidth is available.

Since SG 2 has an MIR equal to its CIR, SG 2 will never be granted more that its configured
CIR, even if additional bandwidth is available. (This may not always be the case for
upstream traffic. See the definition of CIR in QoS Properties on page186.)

For each Service Group, bandwidth is allocated in the following priority order:
Bandwidth requested by the NMS Application is given the highest priority (P1).
Bandwidth will be allocated for all NMS traffic before bandwidth is given to any other
Application.

iBuilder User Guide

iDX Release 2.0

Bandwidth requested by the VoIP Application is given the next priority (P2). Only after
all NMS traffic demand is met will VoIP bandwidth be allocated.

199

Configuring Group QoS

Bandwidth requested by the TCP Application is given the next priority (Cost Based).
No TCP bandwidth will be allocated until all NMS and VoIP traffic demand is met.
When competing for CIR or non-CIR TCP bandwidth, a higher proportion of bandwidth
will be granted to SG 1 than SG 2 due to the lower cost configured for TCP on SG 1.

All remaining traffic is specified by the Default Application which is given a priority of
Best Effort. If bandwidth is available for the Service Group after all other traffic
demand has been satisfied, then Default demand will be met to the extent possible.

For detailed information on all QoS properties see QoS Properties on page186. For
information on how QoS properties are applied in the Group QoS hierarchy see Group QoS
Hierarchy on page190.

Profile View
The Profile View (Figure 188) shows all Service Profiles defined for each Bandwidth Group,
and all Applications defined for each Service Profile. It also shows the properties of each
Application and how those properties are currently assigned to remotes.

Figure 188. Group QoS: Profile View

200

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

Profile-Remote View
The Profile-Remote View (Figure 189) shows all Service Profiles defined in a Bandwidth Group,
all remotes that use each Service Profile, and all Applications assigned to each remote. It also
displays all Service Levels configured for each Application.

Figure 189. Group QoS: Profile-Remote View

iBuilder User Guide

iDX Release 2.0

201

Configuring Group QoS

Remote View
The Remote View (Figure 190) shows all remotes in a Bandwidth Pool, and all Applications,
QoS properties, and Service Levels assigned to each remote. The Remote View groups the QoS
configuration by remote, allowing you to better understand how QoS processing will be
applied on any remote.

Figure 190. Group QoS: Remote View

7.2.2 Estimating Effective MIR and CIR for DVB-S2 Networks

When you configure a DVB-S2 carrier with ACM, only the symbol rate and occupied bandwidth
are known. The information rate depends on the combination of MODCODs being received by
the remotes in the network at any time. Therefore, when you configure CIR or MIR for a Group
QoS node, you are configuring the MIR or CIR based on the best MODCOD configured for the
DVB-S2 carrier. The true MIR or CIR limits for the GQoS node do not equal the configured CIR
or MIR unless all remotes or Virtual Remotes under the node are receiving the best MODCOD of
the carrier. Since even under ideal conditions, remote information rates are limited to their
Nominal (or Clear Sky) MODCOD, it is unlikely that the configured MIR or CIR is ever achieved
in an operational ACM network.
iBuilder includes a MODCOD Distribution Calculator that allows you to estimate the effective
IP Data Rate for your carrier or the effective MIR and CIR for individual GQoS nodes. You can
access this calculator by clicking the MODCOD Distribution button on the configuration dialog
box for Bandwidth Groups, Service Groups or Applications. (The calculator can also be
accessed from the downstream carrier dialog box, allowing you to estimate the effective IP
Data Rate for the entire carrier.)

202

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

A variation of the MODCOD Distribution Calculator can be used to estimate the IP Data Rate
for a DVB-S2 carrier with ACM. See Estimating the IP Data Rate for a DVB-S2 Carrier on
page81 for details.
The following example illustrates how to estimate the effective MIR and CIR for a Group QoS
node. Figure 191 shows the portion of a GQoS node dialog box that displays the Configured
and Effective MIR and CIR for that node.

Figure 191. Configured vs. Effective MIR and CIR before Estimation
Notice in Figure 191 that initially the Configured MIR and CIR are equal to the Effective CIR
and MIR. By default, the calculator for the node assumes that all remotes receive the best
MODCOD of the assigned carrier.
1. Click the MODCOD Distribution button (Figure 191) to display the calculator (Figure 192).

Figure 192. MODCOD Distribution Calculator

iBuilder User Guide

iDX Release 2.0

203

Configuring Group QoS

Figure 192 shows an instance of the MODCOD Distribution Calculator. The range of the
MODCOD column is limited to the DVB-S2 Range defined for the carrier assigned to this
network. The Total row shows the totals for the columns. The Network Best row shows
the configured MIR and CIR for the node.
2. Double-click the cells to enter either the percentages of traffic or the data rates that you
estimate will be transmitted on the different MODCODs for remotes under this node.
If you change the percentages in the MIR Distribution and CIR Distribution columns, the
Estimated MIR and Estimated CIR are automatically recalculated and the totals are
displayed in the Total row. If you change information rates in the Estimated MIR and
Estimated CIR columns, percentages in the MIR Distribution and CIR Distribution
columns are automatically recalculated and the new configuration totals are displayed in
the Network Best row.
Figure 193 shows the results of changing the percentages in the MIR Distribution and CIR
Distribution columns.

Figure 193. Calculating Estimated Information Rate

In the example in Figure 193, the satellite operator estimates that 20% of the remotes
typically receive 8PSK3/4, 20% receive 8PSK-5/6, and the remaining 60% receive 8PSK-8/9
(the best MODCOD defined for the carrier). The calculator maintains the configured
information rates at 512 kbps and 128 kbps while adjusting the effective information
rates to account for the traffic on the lower MODCODs.

204

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

Figure 194 shows the results of entering the Estimated MIR and Estimated CIR in kbps,
splitting the information rates evenly between the two best MODCODs.

Figure 194. Calculating Information Rate Distribution

Notice in Figure 194 that the distribution percentages and the Network Best information
rates have been automatically adjusted to account for the variation in bandwidth
required by the different MODCODs to transmit the same information rate.
3. Click OK to save your changes.

iBuilder User Guide

iDX Release 2.0

205

Configuring Group QoS

Figure 195 shows the results of the following the steps in the example.

Figure 195. Configured vs. Effective MIR and CIR after Estimation
In the top image in Figure 195, the totals for the Effective MIR and Effective CIR that were
recalculated by changing the percentages in the MIR Distribution and CIR Distribution
columns (Figure 193) have been updated in the dialog box. In the bottom image in Figure 195,
the totals for the Configured MIR and Configured CIR that were recalculated by changing the
Estimated MIR and Estimated CIR columns (Figure 194) have been updated in the dialog box.
The estimated MIR and CIR, not configured MIR and CIR, are displayed in the Group QoS Group
View. This is illustrated in the MIR and CIR columns for Bandwidth Group 2 in Figure 196. This
is the result of saving the configuration in the top image of Figure 195.

Figure 196. Effective MIR and CIR in the Group View

206

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

Although effective MIR and CIR are only estimations based on the inputs to the MODCOD
Distribution Calculator, you can use iMonitor to monitor your DVB-S2 performance and refine
these estimations over time to more accurately reflect your actual network performance. See
the iMonitor User Guide for details on monitoring your DVB-S2 networks.

7.2.3 Effective Cost with Allocation Fairness Relative to CIR

As described on page 187, selecting Allocation Fairness Relative to CIR causes CIR bandwidth
allocations to subnodes to be proportional to the configured CIR. This lowers the effective
Cost of bandwidth allocation to competing subnodes with higher CIR. Therefore, if this
property is selected on a parent Group QoS node, peer subnodes at the same priority level
with different CIR configurations display different Effective Costs.
Allocation Fairness Relative to CIR can be defined at the Bandwidth Pool and Bandwidth
Group levels of the Group QoS tree. In Remote Based QoS Mode, it can also be defined at the
Service Group level of the Group QoS tree. In Application Based QoS Mode, it can also be
defined at the Application level of the Group QoS tree.
If selected, Allocation Fairness Relative to CIR applies to both CIR allocation and to besteffort bandwidth allocation. If additional bandwidth is available after all CIR requests have
been satisfied for competing nodes, the additional (best-effort) bandwidth distribution is also
proportional to the configured CIR. If a node has no CIR configured, the cost of its best-effort
bandwidth is identical to the cost calculated for the peer node with the lowest configured
CIR.
Figure 197 shows the Group View with two competing cost-based Service Groups in BWG 1:
Service Group 1 and Service Group 2.

Figure 197. Competing Service Groups without Allocation Fairness Relative to CIR
Note:

The Allocation Fairness Relative to Bandwidth CIR check box in the Group View
(Figure 197) applies to competing Bandwidth Groups in this Bandwidth Pool.

Notice in Figure 197 that Service Group 1 has been granted 256 kbps of CIR while Service
Group 2 has been granted 128 kbps of CIR. Allocation Fairness Relative to CIR has not yet
been enabled for BWG 1. Therefore bandwidth allocation is not affected by the proportion of
CIR configured for each node and the Bandwidth % column and the Cost column are identical
for the two Service Groups.

iBuilder User Guide

iDX Release 2.0

207

Configuring Group QoS

Figure 198 shows the effect of selecting Allocation Fairness Relative to CIR for BWG 1.

Figure 198. Results of Selecting Allocation Fairness Relative to CIR on Parent

Since bandwidth allocation is now proportional to the configured CIRs for the two nodes, the
Bandwidth % for Service Group 1 (256 kbps of CIR) is now twice that of Service Group 2 (128
kbps of CIR). Also notice that the Cost column shows that the Service Group 1 bandwidth
allocation cost is half the cost of Service Group 2.
The difference between the Configured Cost and Effective Cost is displayed on the dialog
box of the competing subnodes. Figure 199 shows the Configured and Effective Costs for
Service Group 1 used in this example.

Figure 199. Configured vs. Effective Cost

For definitions of Cost and Allocation Fairness Relative to CIR, see QoS Properties on
page186.

7.2.4 Allocation Fairness Relative to MODCOD

As described on page 188, Allocation Fairness Relative to MODCOD only applies to networks
that use DVB-S2 with Adaptive Coding and Modulation (ACM). If you select this option,
bandwidth allocation is based on information rate rather than on raw satellite bandwidth.
Therefore, remotes with lower nominal MODCODs receive more satellite bandwidth than

208

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

remotes with higher nominal MODCODs to achieve the same information rate. If the option is
not selected, satellite bandwidth is divided among competing remotes without regard to the
nominal MODCODs of the remotes. (See page 166 for instructions on setting a remotes
nominal MODCOD.)
In Remote Based QoS Mode, Allocation Fairness Relative to MODCOD can only be defined at
the Service Group level of the Group QoS tree. In Application Based QoS Mode, Allocation
Fairness Relative to MODCOD can only be defined at the Application level of the Group QoS
tree.
Note:

Allocation Fairness Relative to MODCOD may be a useful option to maintain CIR

allocations for VoIP applications at the expense of other Applications in a
Service Group.

Figure 199 shows Allocation Fairness Relative to MODCOD selected for an Application.

Figure 200. Selecting Allocation Fairness Relative to MODCOD

Unlike Allocation Fairness Relative to CIR, selecting Allocation Fairness Relative to
MODCOD does not change the effective cost on the Group QoS GUI. However, the system
calculates a hidden cost and uses that hidden cost during bandwidth allocation to apportion
the bandwidth. Allocation fairness relative to MODCOD applies both to CIR bandwidth
allocation and to best-effort bandwidth allocation.
For a definition of Allocation Fairness Relative to MODCOD, see QoS Properties on page186.
For details on configuring Group QoS Service Groups, see Adding a Service Group on
page212. For details on configuring Group QoS Applications, see Adding an Application on
page214.

7.2.5 Adding a Bandwidth Group

Each Bandwidth Pool (Network or Inroute Group) can contain multiple Bandwidth Groups. This
section explains how to configure Bandwidth Groups for your individual Bandwidth Pools.

iBuilder User Guide

iDX Release 2.0

209

Configuring Group QoS

To add a new Bandwidth Group:

1. In the Group View of the Group QoS tab, right-click an existing Bandwidth Group and
select Insert. (You can also select Modify to modify the Bandwidth Group or Clone to
insert a copy of the Bandwidth Group.)

2. In the Bandwidth Group dialog box, enter a Name for the new Bandwidth Group.

Figure 201. Bandwidth Group Dialog Box

210

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

Note:

Group QoS nodes are divided into Allocation Properties and Request Properties.
(For example, see Figure 201.) Allocation Properties of Group QoS nodes
influence the behavior of the node on which they are configured when that node
is allocating bandwidth to its subnodes. Request Properties of Group QoS nodes
determine how the configured node requests its bandwidth.

3. Enter the properties you want to configure for the Bandwidth Group and click OK. (For
details on all Group QoS properties, see QoS Properties on page186.)
4. If you are configuring Group QoS for a DVB-S2 network and you have defined CIR or MIR,
you can click the MODCOD Distribution button to estimate the effective rates for your
network. See Estimating Effective MIR and CIR for DVB-S2 Networks on page202 for
details. Configured and effective cost are discussed in Effective Cost with Allocation
Fairness Relative to CIR on page207.
Figure 202 shows a new Bandwidth Group inserted into the Group QoS tree for a Bandwidth
Pool.

Figure 202. New Bandwidth Group in Group QoS Tree

A new Bandwidth Group automatically includes a single Service Group containing two
Applications. Properties are assigned to these subgroups based on the configuration of the
default upstream or downstream Group Profile. (See Working with Group Profiles on
page228 for a discussion of Group Profiles.)

iBuilder User Guide

iDX Release 2.0

211

Configuring Group QoS

Note:

When you create a mesh-enabled Inroute Group, a Mesh Bandwidth Group is

added by default. The Mesh Bandwidth Group is used for remote-to-remote
mesh traffic only. This is illustrated in Figure 203.

Figure 203. Group QoS Tree with Mesh Bandwidth Group

Note:

Mesh is not supported in iDX Release 2.0.

7.2.6 Adding a Service Group

Each Bandwidth Group can contain multiple Service Groups. This section explains how to
configure Service Groups under your individual Bandwidth Groups.
1. In the Group View of the Group QoS tab, right-click an existing Service Group and select
Insert. (You can also select Modify to modify the Service Group or Clone to insert a copy
of the Service Group.)

212

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

2. In the Service Group dialog box, enter a Name for the new Service Group.

Figure 204. Service Group Dialog Box

3. Enter the properties you want to configure for the Service Group and click OK. (For
details on all Group QoS properties, see QoS Properties on page186.)
4. If you are configuring Group QoS for a DVB-S2 network and you have defined CIR or MIR,
you can click the MODCOD Distribution button to estimate the Effective rates for your
network. See Estimating Effective MIR and CIR for DVB-S2 Networks on page202 for
details. Configured and Effective cost are discussed in Effective Cost with Allocation
Fairness Relative to CIR on page207. Allocation Fairness Relative to MODCOD is
discussed on page 208.
5. For Service Groups, Enable EIR for Remotes in Group applies only to DVB-S2 networks in
Remote Based QoS mode. Select this option to allow EIR to be configured for physical
remotes on the Remote QoS tab. (See Remote QoS Tab on page164.)

iBuilder User Guide

iDX Release 2.0

213

Configuring Group QoS

Note:

Selecting Enable EIR for Remotes in Group allows a network administrator with
Group QoS permissions to allow or disallow the configuration of EIR for
physical remotes per Service Group in a DVB-S2 network. It also allows the
administrator to limit the value that can be set for the EIR Minimum MODCOD
on the physical remotes.

6. If you selected Enable EIR for Remotes in Group, you should also select a Minimum
MODCOD Allowed for the remotes in this Service Group. The selected MODCOD is the
minimum MODCOD that can be configured for the physical remote on the Remote QoS tab.
Figure 205 shows a new Service Group inserted into a Bandwidth Group in the Group QoS tree.

Figure 205. New Service Group Inserted Into a Bandwidth Group

A new Service Group automatically contains two Applications, NMS and Default. The
properties of these Applications are assigned based on the configuration of the default
upstream or downstream Group Profile. (See Working with Group Profiles on page228 for a
discussion of Group Profiles.)

7.2.7 Adding an Application

Each Service Group can contain any number of Applications. This section explains how to
configure Applications under your individual Service Groups.

214

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

1. In the Group View of the Group QoS tab, right-click an existing Application and select
Insert. (You can also select Modify to modify the Application or Clone to insert a copy of
the Application.)

2. In the QoS Application dialog box, enter a Name for the new Application.

Figure 206. QoS Application Dialog Box

iBuilder User Guide

iDX Release 2.0

215

Configuring Group QoS

3. Enter the properties you want to configure for the Application in the Request Properties
and Allocation Properties areas of the dialog box. These properties determine how
bandwidth is allocated for all remotes you configure to use this Application. (For details
on all Group QoS properties, see QoS Properties on page186.)
4. If you are configuring Group QoS for a DVB-S2 network and you have defined CIR or MIR,
you can click the MODCOD Distribution button to estimate the Effective rates for your
network. See Estimating Effective MIR and CIR for DVB-S2 Networks on page202 for
details. Configured and Effective cost are discussed in Effective Cost with Allocation
Fairness Relative to CIR on page207. Allocation Fairness Relative to MODCOD is
discussed on page 208.
5. Enable EIR for Remotes in Application applies only to DVB-S2 networks in Application
Based (or Application Scaled) QoS mode. Select this option to configure EIR for Virtual
Remotes using this Application.
6. If you selected Enable EIR for Remotes in Application, you should also select a Minimum
MODCOD Allowed. The selected MODCOD is the minimum MODCOD that can be configured
for remotes using this Application.
7. If you are configuring a Multicast Application for a DVB-S2 network, the Allocation
Properties display the Multicast MODCOD (Figure 207) rather than an EIR Minimum
MODCOD. Select a Multicast MODCOD for your Multicast Application.

Figure 207. Selecting a User Multicast MODCOD

8. In the Applications Profiles area of the dialog box, select each Application Profile you
want to include in this Application. Each Application is specified by one or more
Application Profiles configured in the Application Profiles folder. (See section Adding an
Application Profile or iSCPC Profile on page238 for details.)
Note: You can use the arrow buttons
to change the order of the Application
Profiles within an Application. First, select an Application Profile; then click
the buttons to move the Application up or down in the list.
Note: The order of Application Profiles within your Applications is important for
two reasons. First, once a rule in an Application Profile matches a packet, no
further classification of the packet is performed. Second, placing highvolume Application Profiles higher in the list will reduce the amount of
processing time used to check seldom-matched rules.
9. Click OK when you have finished defining the Application.

216

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

Figure 208 shows a new Application for TCP inserted into the Group QoS tree for a Bandwidth
Pool.

Figure 208. New Application Inserted Into a Service Group

7.2.8 Creating Service Profiles

Like a Service Group, a Service Profile contains one or more Applications. Each Application
consists of Service Levels and Rules specified by one or more Application Profiles. (See
Adding an Application Profile or iSCPC Profile on page238 for details on creating and
editing Application Profiles.)
When you create a new Service Group, you automatically create a default Service Profile for
the new group containing the NMS and Default Applications. These two Applications are based
on the Upstream or Downstream NMS and the Default Application Profiles. You can modify the
NMS and Default Application Profiles, but you cannot delete them.
The only Applications available to a Service Profile are those assigned to the corresponding
Service Group in the Group View, as described in Adding an Application on page214.
However, adding an Application to a Service Group does not automatically select that
Application as part of any Service Profiles configured from that Service Group. You must
select the Applications manually. The following procedure shows how to configure your
Service Profiles.
1. Right-click anywhere on the Group QoS tab and select Profile View from the menu.

iBuilder User Guide

iDX Release 2.0

217

Configuring Group QoS

2. Right-click the Service Profile and select Modify to display the QoS Service Profile dialog
box. You can also Clone or Modify existing Service Profiles, or Insert new Service Profiles
into the Group QoS tree.

3. In the QoS Service Profile dialog box, select each Application you want to add to the
Service Profile. If the Application contains more than one Application Profile, you can
individually select which Application Profiles you want to include.

Figure 209. QoS Service Profile Dialog Box

4. Click OK to save the Service Profile and return to the Group QoS tab.

218

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

7.2.9 Configuring Application Properties for Remotes

Once you have added an Application to your Service Profile, you can configure how the
Application is applied on the individual remotes that use that Service Profile. When you added
the Application in the Group View (see Adding an Application on page214), you were
configuring how bandwidth is allocated for all remotes using that Application. However, when
you configure the properties of an Application in a Service Profile, you are configuring the
individual properties of each Virtual Remote configured to use the Service Profile.
For example, you might define an MIR of 1000 kbps for an Application in the Group View to
limit the amount of bandwidth distributed for that Application to all remotes in a Service
Group. You might then define an MIR of 100 kbps for the Application in a Service Profile to
limit each remote using that Service Profile to 100 kbps for that Application.
Follow these steps to configure the QoS properties assigned to Virtual Remotes:
1. Right-click anywhere on the Group QoS tab and select Profile View from the menu.

2. Under the Service Profile you want to change, right-click an Application and select
Modify from the menu.

iBuilder User Guide

iDX Release 2.0

219

Configuring Group QoS

3. In the Request Properties area of the dialog box, modify the properties you want to
change.

Figure 210. Application Properties Dialog Box

4. In the Allocation Properties, the EIR section of the dialog box applies only to DVB-S2
outbound carriers with ACM enabled. EIR is only enabled within the range defined by the
carriers Maximum MODCOD and the Minimum MODCOD entered here. (See page187 for
the definition of EIR. See page75 for details on configuring the MODCOD range of your
DVB-S2 carriers.)
5. Select Apply to All if you want to apply these settings to all Virtual Remotes using this
Application. This will remove any overrides that were previously configured for individual
Virtual Remotes. If you do not select Apply to All, previously-defined overrides will be
retained. (See Overriding Application Properties on Individual Remotes on page224.)
6. Click OK to save your changes.

7.2.10 Assigning Service Profiles to Remotes

Once you have created a Service Profile for a Network or an Inroute Group, you can then
assign the Service Profile to selected remotes in that Bandwidth Pool. By assigning different
Service Profiles to separate groups of remotes in a single Bandwidth Pool, you can control how
bandwidth is requested by and allocated for the remote groups.
Typically, you will only assign one Service Profile per remote. However, under rare
circumstances, you may want to assign more than one Service Profile to a single remote. You

220

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

can only assign multiple Service Profiles to a single remote if those Service Profiles are in
different Service Groups within the same Bandwidth Group or in different Bandwidth Groups.
You cannot configure a remote with more than one NMS or Default Application. If you choose
to assign multiple Service Profiles to a single remote, the NMS and Default Applications of the
new Service Profile will be applied to the remote in place of the NMS and Default Applications
that were previously applied. When you remove a Service Profile from a remote which had
multiple profiles assigned, then if the NMS and Default Applications were applied from that
profile, the remote will be re-assigned the NMS and Default Applications of the first Service
Profile in the Group QoS Profile View that is still assigned to the remote. Applications other
than NMS and Default should be unique across all Service Profiles assigned to a remote. If not,
only one of the identical Applications will be selected, overriding the duplicate Application.
Normally, an operator assigns Service Profiles to individual remotes on the Remote QoS tab.
(See Remote QoS Tab on page164 for details.) Service Profiles assigned to a Remote are
displayed in bold in the Upstream QoS and Downstream QoS sections of that tab. Figure 211
shows two Service Profiles (SP 1 and SP 2) assigned to a single remote for an Inroute Group.

Figure 211. Multiple Service Profiles Assigned to a Single Remote

Note:

When multiple Service Profiles are assigned to a Remote, you can unassign a
Service Profile on the Remote QoS tab by holding down the Ctrl key and clicking
the Service Profile.

The remainder of this section describes how to assign Service Profiles to remotes from the
Group QoS Profile-Remote View. This method can be used by a Group QoS administrator as an
alternative to assigning Service Profiles to individual remotes on the Remote QoS tab.

iBuilder User Guide

iDX Release 2.0

221

Configuring Group QoS

To assign a Service Profile to a Remote:

1. Right-click anywhere in the Group QoS tab of a Network or Inroute Group and select
Profile-Remote View from the menu.

2. Right-click anywhere in the Profile-Remote View and select Expand Tree to view the
current Service Profile assignments.

222

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

3. Right-click the Service Profile you want to assign and select Assign/Unassign Remote.

4. In the QoS Service Profile dialog box (Figure 212), use the arrow keys
to move remotes between the Available Remotes pane and the Assigned Remotes pane.
(Use Ctrl-click or Shift-click to select multiple remotes. The single-headed arrows move
all selected remotes between panes. The double-headed arrows move all remotes
between panes.)

Figure 212. Moving Remotes Between QoS Service Profiles

5. Click OK to save the Service Profile assignments.
Note:

iBuilder User Guide

iDX Release 2.0

After you assign a remote to a new service profile, its previous service profile
is still assigned as well. You can follow steps similar to those above to unassign
the remotes previously-assigned profile.

223

Configuring Group QoS

Note:

You can also change the Service Profile assignments of remotes by selecting
remotes in the Profile-Remote View and dragging the remotes between Service
Profiles. Figure 213 shows remote 7350-1272 being dragged from SG 1 to SG 2.

Figure 213. Dragging Remotes Between QoS Service Profiles

7.2.11 Overriding Application Properties on Individual Remotes

Normally, when you assign a Service Profile to a remote, the remote is assigned the properties
of the Applications that you configured for the Applications in the Service Profile. (See
Configuring Application Properties for Remotes on page219.) However, you can override
these Application properties for individual Virtual Remotes in the Group QoS Profile View.
Follow these steps to override the QoS properties assigned to Virtual Remotes:
1. Right-click anywhere on the Group QoS tab and select Profile View from the menu.

224

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

2. Under the Service Profile you want to change, right-click a Virtual Remote and select
Modify from the menu.

3. In the Request Properties area of the Properties dialog box, modify the properties you
want to change.

Figure 214. Overriding Application Properties on Individual Remotes

iBuilder User Guide

iDX Release 2.0

225

Configuring Group QoS

4. In the Allocation Properties area of the dialog box, you can override the EIR Minimum
MODCOD setting on the outbound for a remote receiving a DVB-S2 outbound. See
Configuring Application Properties for Remotes on page219 for details.
5. Click OK to save your changes to the Virtual Remote.

7.2.12 Configuring Full-Trigger CIR for a Remote

You can enable Full-Trigger CIR for any upstream application running on a remote (i.e., for
any Virtual Remote configured on the Group QoS tab of your Inroute Group). You cannot
enable Full-Trigger CIR on the downstream. If Full-Trigger CIR is enabled for a Virtual Remote,
the remote will be granted all of its configured CIR bandwidth whenever any CIR bandwidth is
granted to the Virtual Remote, regardless of the amount requested.
Full-Trigger CIR can only be enabled by configuring a hub-side custom key on the remote
Custom tab. Follow these steps to enable Full-Trigger CIR for a Virtual Remote:
1. Determine the Virtual Remote number by right-clicking anywhere on the Group QoS tab of
your Inroute Group and selecting Profile-Remote View from the menu.
2. Right-click anywhere in the Profile-Remote View and select Expand Tree to view all
remotes and their Applications.
3. Scroll down to the remote in the Service Profile that you want to configure, and examine
the Application column in the Profile-Remote View. Each Application listed for a remote
represents a Virtual Remote. Virtual Remote numbers are assigned according to the order
of the Applications.
In Figure 215, for Remote 5150_4748, NMS is Virtual Remote 1, UDP APP is Virtual Remote
2, and Default is Virtual Remote 3. Note the Virtual Remote number for the Application
that you want to configure for Full-Trigger CIR.

Figure 215. Determining Virtual Remote Numbers for Remote Applications

226

iBuilder User Guide

iDX Release 2.0

Configuring Group QoS

4. Right-click the remote in the iBuilder tree and select ModifyItem.

5. In the Modify Configuration Object dialog box, click the Custom Tab. Then add a custom
key to the Hub-Side Configuration pane in the following format:
[UPSTREAM_VR_#]
full_cir_trigger = 1
where # is the Virtual Remote number determined in Step 3. Figure 216 shows the custom
key required to enable Full-Trigger CIR for UDP App based on the Virtual Remote numbers
calculated in that step.

Figure 216. Defining the Full Trigger CIR Custom Key

6. Click OK to save your changes. Then right-click the remote in the iBuilder Tree and select
Apply ConfigurationReliable Hub-Side (TCP) to send the new configuration to the
protocol processor.

iBuilder User Guide

iDX Release 2.0

227

Working with Group Profiles

7.3

Working with Group Profiles

Group Profiles allow you to apply the identical Group QoS configuration to multiple Networks
or Inroute Groups. They also enable you to work offline to develop Group QoS configurations
before assigning them to your Bandwidth Pools. A Group Profile contains the entire Group QoS
tree associated with a Bandwidth Pool.
Using Group Profiles, you can:

Save the Group QoS configuration of an existing Bandwidth Pool to an Upstream or

Downstream Group Profile.

Create copies of Group Profiles to use as templates for similar profiles

Modify Group Profiles

Replace the Group QoS configuration of any Bandwidth Pool with a Group Profile

The following sections explain how to create, modify, copy, and apply your Group Profiles.
There are two default Group Profiles: the Default Downstream Profile and the Default
Upstream Profile. When you add a Network to the iBuilder tree, iBuilder automatically assigns
the Default Downstream Profile to the new Network. When you add an Inroute Group to the
iBuilder tree, iBuilder automatically assigns the Default Upstream Profile to the new Inroute
Group. The contents of the default Group Profiles are described in Configuring Group QoS
on page197. You can modify the default Group Profiles, but you cannot delete them.

7.3.1 Saving Group Profiles

Follow these steps to save the Group QoS configuration of an Inroute Group or Network to an
Upstream or Downstream Group Profile. The entire Group QoS tree associated with the
selected Bandwidth Pool will be saved to a Group Profile.
1. Right-click anywhere on the Group QoS tab and select Group View from the menu.

228

iBuilder User Guide

iDX Release 2.0

Working with Group Profiles

2. Right-click anywhere in the Group View and select Save to Profile to display the QoS
Group Profile dialog box.

3. In the QoS Group Profile dialog box, enter a name for your new Group Profile.

Figure 217. Naming a QoS Group Profile

4. You can view the properties of the various group members before saving the Group
Profile. To see the properties of a Bandwidth Group, Service Group or Application, select

iBuilder User Guide

iDX Release 2.0

229

Working with Group Profiles

the folder in the Group Hierarchy pane. The properties of that group member will appear
in the Group Members pane.

Figure 218. Viewing Properties of QoS Group Members

5. To save the Group Profile, click OK in the QoS Group Profile dialog box. Then click OK in
main screen of the Group QoS tab.
Inroute Group QoS profiles are saved in the QoSGroup ProfilesUpstream folder of the
iBuilder tree. Network Group QoS profiles are saved in the QoSGroup
ProfilesDownstream folder of the iBuilder tree.

230

iBuilder User Guide

iDX Release 2.0

Working with Group Profiles

7.3.2 Copying Group Profiles

You can use the Clone operation to create a copy of an Upstream or Downstream Group
Profile. You cannot copy Group Profiles between the Upstream and Downstream folders. You
can only create copies of Group Profiles within the original folder.
To create a copy of a Group Profile:
1. Right-click the Group Profile in the iBuilder tree and select Clone from the menu. The
new profile is automatically created in the current folder (Upstream or Downstream) and
the Modify Configuration dialog box appears.

2. In the Modify Configuration Object dialog box, enter a Profile Name for the new Group
Profile.

Figure 219. Copying a QoS Group Profile

3. If desired, you can make changes to the Group Profile before you save it. See Configuring
Group QoS on page197 for details on modifying the Group QoS configuration.
Note:

iBuilder User Guide

iDX Release 2.0

Only the Group View and Profile View are available when working with Group
Profiles. The Profile-Remote View and Remote View, which appear on the Group
QoS tab, are not applicable to Group Profiles.

231

Working with Group Profiles

7.3.3 Modifying Group Profiles

To modify a Group Profile:
1. Right-click the Group Profile in the iBuilder tree and select ModifyItem to display the
Modify Configuration Object dialog box.

2. In the Modify Configuration Object dialog box, make the desired changes to the Group
QoS configuration. See Configuring Group QoS on page197 for details on modifying the
Group QoS configuration.

Figure 220. Modifying a QoS Group Profile

3. When finished, click OK to save the changes to your Group Profile.
Note:

232

Only the Group View and Profile View are available when working with Group
Profiles. The Profile-Remote View and Remote View, which appear on the Group
QoS tab, are not applicable to Group Profiles.

iBuilder User Guide

iDX Release 2.0

Working with Group Profiles

7.3.4 Applying Group Profiles to Networks and Inroute Groups

You can replace the Group QoS configuration for a Bandwidth Pool by re-creating the Group
QoS tree for that Bandwidth Pool from a Group Profile. When you replace the Group QoS tree,
remotes that are part of the Bandwidth Pool are automatically reconfigured as follows:

All remotes in the Network or Inroute Group are assigned to the first Bandwidth Group in
the new Group QoS tree.

All Remotes in the Network or Inroute are reconfigured to use the new Default Service
Profile of the first Service Group of the first Bandwidth Group.

Once you have replaced the Group QoS configuration, you can re-assign the remotes in the
Bandwidth Pool to Service Profiles by following the steps in Assigning Service Profiles to
Remotes on page220.
To replace the Group QoS configuration for a Network or Inroute Group with the configuration
specified in a Group Profile, follow these steps:
1. Right-click the Network or Inroute Group in the iBuilder tree and select ModifyItem.
2. Click the Group QoS tab.
3. Right-click anywhere on the Group QoS tab and select Group View from the menu.

4. Right-click anywhere in the Group View and select Create From Profile to display the
QoS Group Profile dialog box.

iBuilder User Guide

iDX Release 2.0

233

Working with Group Profiles

5. In the QoS Group Profile dialog box, select the Group Profile you want to use for this
Bandwidth Pool. (Only Upstream Group Profiles can be selected for Inroute Groups. Only
Downstream Group Profiles can be selected for Networks.)

Figure 221. Selecting a QoS Group Profile to Apply

6. You can view the properties of the various group members before applying the Group
Profile to the Bandwidth Pool. To see the properties of a Bandwidth Group, Service Group
or Application, select the folder in the Group Hierarchy pane. The properties of that
group member will appear in the Group Members pane.

Figure 222. Viewing Properties of QoS Group Members

234

iBuilder User Guide

iDX Release 2.0

QoS for iSCPC Connections

7. When finished, click OK in the dialog box. Then click Yes in the confirmation dialog box to
replace the Group QoS configuration.
8. Follow the steps in Assigning Service Profiles to Remotes on page220 to assign your
remotes to Service Profiles based on the Service Groups of the new configuration.
9. When finished, click OK at the bottom of the Group QoS tab to save your changes.

7.4

QoS for iSCPC Connections

Group QoS is not applicable to iSCPC connections; it is only applicable to TDMA networks.
Therefore, you do not assign Application Profiles and Service Profiles to your iSCPC line cards
and remotes. Instead, you assign iSCPC Profiles, which are similar to Application Profiles,
directly to these elements. Filter Profiles can be assigned to both TDMA remotes and iSCPC
line cards and remotes. Application Profiles, iSCPC Profiles and Filter Profiles are described in
detail in the following sections.
Note:

iSCPC is not supported in iDX Release 2.0.

The QoS tabs of both iSCPC line cards and iSCPC remotes are divided into Transmit and
Receive settings. The Transmit settings represent the QoS settings applied to packets
transmitted by the modem being configured. The Receive settings represent the QoS settings
applied to packets transmitted by the peer modem.
All QoS settings for both ends of an iSCPC connection are configured on the QoS tab of the
iSCPC Line Card. The settings on the iSCPC Remote QoS tab mirror the line card assignments.
The Transmit QoS iSCPC Profile configured on the Line Card is assigned as the Receive QoS
iSCPC Profile of the Remote, and the Receive QoS iSCPC Profile configured on the Line Card
is assigned as the Transmit QoS iSCPC Profile of the Remote. Therefore, you can assign
iSCPC Profiles on the iSCPC line card QoS tab, but you cannot change their assignments on the
iSCPC Remote QoS tab. For details on configuring iSCPC line cards, see Adding an iSCPC Line
Card on page113.

7.5

Application Profiles, iSCPC Profiles and Filter

Profiles
Both Application Profiles and iSCPC Profiles consist of groups of Service Levels, collected
together and given the name of your choice. Each Service Level can be configured with QoS
properties and a set of rules. They determine how packets are filtered and prioritized.
Although they are defined in a similar way, Application Profiles and iSCPC Profiles are used
differently in TDMA networks and iSCPC connections.

For TDMA networks, Application Profiles define the Group QoS Applications that you add
to your Service Profiles. You then assign the Service Profile to your TDMA remotes using
the Group QoS tab for your Bandwidth Pools. (See Configuring Group QoS on page197
for details.)

iSCPC Profiles are assigned directly to iSCPC line cards on the QoS tab. The Line Card
assignments of iSCPC Profiles are mirrored on the iSCPC remote. (See QoS for iSCPC
Connections on page235 for details.)

iBuilder User Guide

iDX Release 2.0

235

Application Profiles, iSCPC Profiles and Filter Profiles

Although configured identically, it is important to note that Application Profiles are only used
for Group QoS. iSCPC Profiles are used only by iSCPC line cards and remotes and are not
associated with Group QoS.
Filter Profiles encapsulate a single filter definition. A Filter Profile contains a group of rules,
but no Service Levels. Filter Profiles can be assigned to both TDMA remotes and iSCPC line
cards. As with iSCPC Profiles, Filter Profiles assigned to an iSCPC Line Card are mirrored on
the peer remote. Filter Profiles are applied to packets before any other QoS processing.
Application Profiles, iSCPC Profiles and Filter Profiles are stored in separate folders in
iBuilders Network Tree. They are not associated with a teleport; instead they are
independent of any network hierarchy, similar to spacecraft and antenna components. Group
QoS Application Profiles are stored in the Application Profiles folder. iSCPC Profiles are stored
in the iSCPC Profiles folder.

Figure 223. QoS Folders in iBuilder Tree

iBuilder contains a number of pre-configured iSCPC Profiles to help you define various
categories of IP traffic. You can modify these pre-configured profiles to meet your needs;
copy them to use as templates for new profiles; or create your own profiles. A typical list of
iSCPC Profiles in the iBuilder tree is shown in Figure 224.

Figure 224. Preconfigured iSCPC Folders

Preconfigured Application Profiles (Default Downstream or Upstream, NMS and Default Mesh
Upstream) are automatically added to your Networks or Inroute Groups when created. The
Default Mesh Upstream Profile applies only to mesh-enabled Inroute Groups.

236

iBuilder User Guide

iDX Release 2.0

Application Profiles, iSCPC Profiles and Filter Profiles

Adding a Profile
To add a new profile, right-click the Upstream or Downstream folder under Filter Profiles,
Application Profiles, or iSCPC Profiles and select the Add option. The title of the Add option
will differ depending on what type of profile you are adding: Upstream or Downstream.

A Modify Configuration dialog box opens to allow you to configure the profile you are adding.
Details are discussed in Adding an Application Profile or iSCPC Profile on page238 and
Adding a Filter Profile on page242.
Once a Profile is configured and saved, it appears in the iBuilder Tree within its respective
folder. Figure 225 shows Group QoS Downstream Application Profiles in the iBuilder tree.

Figure 225. New Profile in iBuilder Tree

Note:

When a profile is being used, the icon in the iBuilder Tree is colored red and the
name appears in bold typeface.

Copying a Profile
You can copy a profile by right-clicking it and selecting Clone or Clone As from the menu. If
you select Clone, a copy of the selected profile is created in the same folder. You can then
edit the new profile to make changes.

iBuilder User Guide

iDX Release 2.0

237

Application Profiles, iSCPC Profiles and Filter Profiles

If you select Clone As, the Clone As dialog box appears. The Clone As dialog box allows you
select a Direction for the copy of your profile. By selecting a Direction, you can copy a
Downstream profile to the Upstream folder, or an Upstream Profile to the Downstream folder.

Figure 226. Clone As Dialog Box

Note:

Clone As is not available for Group QoS Profiles. You cannot copy Group
Profiles between the Upstream and Downstream folders.

7.5.1 Adding an Application Profile or iSCPC Profile

For TDMA networks, Application Profiles define the individual Applications that you include in
your Service Groups and Service Profiles. Upstream Application Profiles are used on Inroute
Groups. Downstream Application Profiles are used on Outroutes.
For iSCPC connections, iSCPC Profiles are assigned directly to iSCPC Line Cards on the QoS
tab. (See QoS for iSCPC Connections on page235).
To add either an Application Profile or an iSCPC Profile, follow these steps:
1. In the iBuilder Tree, right-click the Downstream or Upstream folder under
QoSApplication Profiles or QoSiSCPC Profiles.
2. Select Add Downstream Profile or Add Upstream Profile from the menu.

You can also modify or copy an existing profile by right-clicking the profile and selecting
ModifyItem, Clone or Clone As from the menu. Clone creates a copy in the current

238

iBuilder User Guide

iDX Release 2.0

Application Profiles, iSCPC Profiles and Filter Profiles

folder. Clone As allows you to copy profiles between the Downstream and Upstream
folders.

3. After you have selected the operation you want from the menu, a dialog box opens.
(Figure 227 shows an Upstream Application Profile with multiple Service Levels. New
Application Profiles will be empty.)

Figure 227. Application Profile Dialog Box

Each Application Profile or iSCPC Profile contains one or more Service Levels. Each Service
Level can have multiple Rules. When you select a Service Level in the Service Levels
pane, all Rules associated with that Service Level are displayed in the Rules pane.

iBuilder User Guide

iDX Release 2.0

239

Application Profiles, iSCPC Profiles and Filter Profiles

4. You can Add, Edit or Delete Service Levels by selecting the Service Level and clicking the
appropriate button. Figure 228 shows the Add Service Level dialog box. The Edit Service
Level dialog box is identical.

Figure 228. Add Service Level Dialog Box

5. Enter a Level Name for the Service Level.
6. Choose Reliable or Unreliable. If the Service Level is intended to match TCP traffic, you
should choose Reliable. For all other traffic, you should choose Unreliable.
7. Spoofing (sometimes called TCP Acceleration) applies to star TCP (Reliable) traffic
only. It does not apply to mesh or unreliable traffic. Select Spoofing to enable it for TCP
traffic between the hub and remotes.
8. By default, TDMA slots used by an application are grouped together in the frame for
transmission. If you select Reduce Jitter, the system will attempt to distribute the slots
as evenly as possible across the frame. Reduce Jitter should be selected for VoIP
applications. However, since it can decrease throughput, it should not be selected for
applications that are not jitter-sensitive.
9. Select or clear Drop Oldest First.
10. If Trigger Wakeup is selected, remotes will automatically exit Sleep Mode to transmit
incoming LAN packets on the upstream carrier if the packets match the Service Level

240

iBuilder User Guide

iDX Release 2.0

Application Profiles, iSCPC Profiles and Filter Profiles

definition. Trigger Wakeup applies only to upstream profiles, and affects only remotes
that have Sleep Mode enabled. (See Adding Remotes on page142.)
Note:

The Sleep Mode feature requires iDX Release 2.0.1. Earlier versions of iDX
Release 2.0 do not support Sleep Mode.

Note:

If a remote in Sleep Mode receives traffic for transmission on the upstream,

and Trigger Wakeup is not selected for the traffics Service Level, then the
packets will be dropped and the remote will remain in Sleep Mode. A remote
will only wake from Sleep Mode if Trigger Wakeup is enabled for the traffic, or
if Sleep Mode is manually disabled for the remote on the remote Information
tab.

11. Select the method of Optimization for traffic matching this Service Level. Selecting
Maximum Efficiency instructs the software to allocate bandwidth as efficiently as
possible. Selecting Minimum Latency instructs the software not to hold onto partially
filled TDMA bursts but to release them immediately. For more details, see the chapter
titled QoS Implementation Principles in the iDirect Technical Reference Guide.

WARNING! Selecting Minimum Latency can result in an increased number of unused bytes
per burst, significantly decreasing the upstream throughput for remotes with
this setting. Do not select Minimum Latency unless you are certain that your
application requires it.
12. Select the method of Scheduling to be used for this Service Level: Priority Queue, CostBased, or Best Effort. If you select Priority Queue, then select the priority level from the
menu. If you select Cost-Based, then enter a cost value. For details on each scheduling
method, see the discussion of packet scheduling in the chapter titled QoS
Implementation Principles in the iDirect Technical Reference Guide.
13. Enter the Queue Depth.
14. Choose the Type of Service Marking you want.
15. Click OK to save this Service Level.
16. You can use the Add, Edit and Delete Buttons in the Rules Pane to configure Rules for
your Service Profile. The steps for configuring Rules are covered in Adding a Rule to a
QoS Profile on page244.

Figure 229. Service Profile Rules Pane

iBuilder User Guide

iDX Release 2.0

241

Application Profiles, iSCPC Profiles and Filter Profiles

7.5.2 Adding a Filter Profile

You can define both Upstream and Downstream Filter Profiles. Like Application and iSCPC
Profiles, Filter Profiles can contain one or more rules that are used to classify transmit traffic.
Unlike Application and iSCPC Profiles, there are no Service Levels associated with Filter
Profiles.
You can configure any remote with an Upstream Filter Profile, a Downstream Filter Profile, or
both. The rules configured for the assigned profile(s) are applied to any packets offered for
transmission before any other QoS processing is performed.
Each filter profile can be configured with one or more rules. For a packet to be further
classified, it must match at least one of that filter profiles rules. A rule is made up of one or
more comparisons between IP header fields and a known constant value specified by the user.
The system compares each rule in the order specified, and classifies the packet according to
the first rule that matches.
Follow these steps to add a Filter Profile:
1. Right-click the Filter Profiles folder under QoSUpstream or QoSDownstream in the
iBuilder tree. Then select the Add Filter option from the menu to display the Filter
Profile dialog box (Figure 230).

Figure 230. Filter Profile Dialog Box

242

iBuilder User Guide

iDX Release 2.0

Application Profiles, iSCPC Profiles and Filter Profiles

2. In the Filter Profile dialog box, click the Add button in the Rules pane to display the Add
Filter dialog box.

Figure 231. Add Filter Dialog Box

3. Follow the steps in Adding a Rule to a QoS Profile on page244 to configure a rule for
this Filter Profile.
4. When you have finished adding Rules, click OK in the Filter Profile dialog box to save the
Filter Profile.

iBuilder User Guide

iDX Release 2.0

243

Application Profiles, iSCPC Profiles and Filter Profiles

7.5.3 Adding a Rule to a QoS Profile

Each Application, iSCPC or Filter Profile has one or more rules. A rule consists of one or more
clauses defining comparisons between IP header fields and the values specified by the user.
The system compares each rule in the order specified, and classifies the packet according to
the first rule that matches.
You configure rules in the Add Filter dialog box described later in this section. The Add Filter
dialog box is displayed by clicking the Add button in the Rules pane of the profile dialog box.
The Rules pane from an Application Profile dialog box is shown in Figure 232.

Figure 232. Application Profile Rules Pane

In the profile dialog box, the Rules pane displays all Rules configured for the Service Level
selected in the Service Level pane, along with the name of the selected Service Level. In the
Filter Profile dialog box, the Rules pane displays all Rules configured for the Filter Profile.
(See Adding an Application Profile or iSCPC Profile on page238 and Adding a Filter Profile
on page242 for more details.)
When you select or clear the Show Protocol Names check box at the bottom of the dialog
box, the Rules pane toggles the displayed Rules between IP protocol names and numbers.
Figure 233 shows the result of selecting the check box (top) and of clearing the check box
(bottom) in the profile dialog box. Application, iSCPC and Filter Profile dialog boxes all
provide the same capability.

Figure 233. Selecting and Clearing the Show Protocols Name Check Box

244

iBuilder User Guide

iDX Release 2.0

Application Profiles, iSCPC Profiles and Filter Profiles

Follow these steps to add a new rule for your Application, iSCPC or Filter Profile:
1. Click the Add button in the Rules pane to display the Add Rule dialog box.

Figure 234. Adding a Rule to a Profile

Note:

When specifying rules, all comparisons specified (as indicated by the check
boxes on the left-hand side of the dialog box) must match for the rule to match
a packet.

2. Select the check boxes at the left to enable an IP header field for comparison by the
filter. Then define the values and operators for each comparison to be made as follows:
Source IP and Destination IP address and Subnet Masks: You can configure a Source
and/or Destination IP address, each with a Subnet Mask. The IP header field may be
equal to (=) or not equal to (<>) the value entered. The subnet mask is first applied
to the IP address in the packet, and then compared to the address specified in the
filter. This way, Source and Destination Ranges of subnet masks may be made to
match the rule.

iBuilder User Guide

iDX Release 2.0

245

Assigning QoS Profiles to Multiple Remotes

Source and Destination Port Ranges: You can configure Source and Destination Port
Ranges and select the desired protocols in the From and To drop down lists. Each
protocol may be equal to (=) or not equal to (<>) the value entered. Select Same as
Source to configure the Destination Port Range to be identical to the Source Port
Range.

VLAN Ranges: You can configure VLAN Ranges to be equal to (=) or not equal to (<>)
the value entered.

Protocol: You can select a Protocol which may be equal to (=) or not equal to (<>)
the value entered.

DSCP, TOS, Precedence: If you select DiffServ DSCP you cannot select TOS or
Precedence. If you select TOS or Precedence you cannot select DSCP.

3. Click OK to save the filter.

7.6

Assigning QoS Profiles to Multiple Remotes

You can assign Filter Profiles or Service Profiles to multiple remotes simultaneously at the
Teleport, Network and Inroute Group levels of the iBuilder tree. However, this function is not
available for iSCPC remotes or line cards. Follow these steps:
1. Right-click the element in the Tree and select Assign Profiles. The Assign QoS Profile
dialog box opens.

The Assign QoS Profile dialog box shows all Remotes under the selected element and
their current profile assignments.

Figure 235. Assign QoS Profile Dialog Box

2. To assign a different profile to a remote or a group of remotes, select the rows of all
remotes you want to change, and right-click in the column of the profile you want to re-

246

iBuilder User Guide

iDX Release 2.0

Assigning QoS Profiles to Multiple Remotes

assign. (Use Shift-click and Ctrl-click to select a range of remotes or multiple, individual
remotes.) Then select Assign Profile from the menu.

3. Select the profile you want to assign from the drop-down list.

Note:

iBuilder User Guide

iDX Release 2.0

When multiple Service Profiles are assigned to a remote, you can unassign a
Service Profile on the Remote QoS tab by holding down the Ctrl key and clicking
the Service Profile you want to unassign. See Assigning Service Profiles to
Remotes on page220 for details.

247

Assigning QoS Profiles to Multiple Remotes

248

iBuilder User Guide

iDX Release 2.0

Configuring the Chassis IP Address

8 Configuring a Hub
Chassis

This chapter includes the following sections:

8.1

Configuring the Chassis IP Address on page249

Chassis Licenses on page252

Configuring and Controlling the Hub Chassis on page252

Configuring a Four-Slot Chassis on page255

Sharing a 20 Slot Chassis in a Multi-NMS System on page260

Changing a Chassis IP Address on page265

Daisy Chaining Hub Chassis on page266

Configuring the Chassis IP Address

The interface between the Hub Chassis and the NMS is encapsulated in an IP-addressable
controller board. By communicating with the chassis controller board, the NMS server can
monitor the status of the chassis power supplies and fans, power on and off the chassis slots,
and change chassis SOF jumper settings.
There are two types of controller boards:

The EDAS board, designed and manufactured by Intelligent Instruments, Inc.

The newer iDirect MIDAS board

The steps for configuring the IP address of the chassis differ depending on the type of
controller board installed on your chassis. To set the IP address for your chassis, follow the
procedure in this section that applies to your type of chassis controller board.
Note:

iBuilder User Guide

iDX Release 2.0

If you do not know if your chassis has an EDAS or MIDAS controller board,
attempt to follow Step 1 through Step 6 in Setting the IP Address for a Chassis
with a MIDAS Controller Board on page250. If you have an EDAS controller
board, you will not be able to log on to the board using the MIDAS procedure.

249

Configuring the Chassis IP Address

Note:

If you are changing the IP address of a chassis and you have already configured
the chassis in iBuilder, you must update the Chassis Manager Server with the
new IP address. See Changing a Chassis IP Address on page265 for details.

8.1.1 Setting the IP Address for a Chassis with an EDAS

Controller Board
To configure the IP address of a chassis with an EDAS board, you must have the EDAS
SYSCHECK utility installed on your PC. The EDAS SYSCHECK utility is available on the iDirect
TAC website.
Follow these steps to configure the IP address of a hub chassis with an EDAS board:
1. Ensure that the EDAS SYSCHECK program is installed on your PC.
2. Ensure that the hub chassis is powered on.
3. Ensure that you have a standard null modem serial cable.
4. Connect the serial cable from the serial port of your PC to the M&C Config Port on the
four slot chassis control module or the 20 slot chassis rear panel.
5. From the Start menu on your PC, run EDAS SYSCHECK.
6. In the EDAS SYSCHECK window, select the Program tab.
7. Select the correct COM port.
8. Click the Attach to EDAS button. This connects your PC to the EDAS board and displays
the current IP settings of the EDAS board.
9. Select the Configuration tab.
10. Set the appropriate IP address, subnet mask and default gateway values. The default
gateway should be your upstream router.
11. Re-select the Program tab.
12. Write each IP address value to the board by clicking the appropriate buttons.

WARNING! Do not click the Write Ethernet Address Button. The Ethernet Address field
should never be modified.
13. Reset the EDAS board either by powering the hub chassis off and on, or by resetting only
the EDAS board.
Note:

To reset the EDAS board without powering down a 20 slot chassis, remove the
EDAS board cover and disconnect and reconnect the power connector to the
board itself. To reset the EDAS board without powering down a four slot
chassis, press the EDAS Reset button on the chassis control module.

8.1.2 Setting the IP Address for a Chassis with a MIDAS

Controller Board
Follow these steps to configure the IP address of a hub chassis with a MIDAS board:
1. Ensure that the hub chassis is powered on.

250

iBuilder User Guide

iDX Release 2.0

Configuring the Chassis IP Address

2. Ensure that you have a standard null modem serial cable.

3. Connect the serial cable from the serial port of your PC to the M&C Config Port on the
four slot chassis control module or the 20 slot chassis rear panel.
4. Configure a serial terminal program (such as Tera Term under Windows or Minicom under
Linux) to match the serial settings on the MIDAS control module. The default settings are:
Baud rate: 57600

Data bits: 8

Parity: None

Stop bits: 1

Flow Control: None

5. Press Enter in the terminal program to display the MIDAS login: prompt.
6. At the MIDAS login: prompt, type the MIDAS administrative login name and press Enter.
(The default administrative login name is admin.)
7. At the Password > prompt, type the administrative password and press Enter. (The
default administrative password is admin.)
8. If you want to display the current IP settings, enter the command:
show ip config
9. At the admin > command line prompt, enter the command:
set ip <n.n.n.n>
where <n.n.n.n> is the desired IP address. For example, to set the IP address to
172.17.2.50, you would enter the command set ip 172.17.2.50.
10. Enter the command:
set mask <n.n.n.n>
where <n.n.n.n> is the desired subnet mask. For example, to set the subnet mask to
255.255.255.0, you would enter the command set mask 255.255.255.0.
11. Enter the command:
set gateway <n.n.n.n>
where <n.n.n.n> is the desired gateway IP address. The default gateway should be your
upstream router. For example, to set the gateway IP address to 172.17.2.1, you would
enter the command set gateway 172.17.2.1.
12. Enter the command:
reboot
Your new IP settings will take effect on completion of the reboot.
13. To verify your IP settings, you can log on again and enter the following command:
show ip config

iBuilder User Guide

iDX Release 2.0

251

Chassis Licenses

8.2

Chassis Licenses
Beginning with iDX Release 2.0, your chassis slots must be licensed before you can configure
your chassis in iBuilder. If you have received your license file from iDirect but you have not
yet imported the licenses, follow the procedure in Importing Your License Files on page57
before configuring your chassis.
Note:

Beginning with iDX Release 2.0, a hub line card must be assigned to a licensed
chassis slot before it can be activated. Until a line card is assigned to slot, the
line card will be in the incomplete state in the iBuilder tree.

For information on licensing your chassis, see the iDirect Features and Chassis Licensing
Guide available on the TAC web page.

8.3

Configuring and Controlling the Hub Chassis

The Hub Chassis includes the line cards, power supplies, and fans. There are three types of
chassis: 20-slot chassis, iSCPC 20-slot chassis, and four-slot chassis. Follow these steps to
create a 20-slot Chassis or an iSCPC chassis in iBuilder. Four-slot chassis configuration is
discussed in Configuring a Four-Slot Chassis on page255. If you are adding a 1 IF, 20-slot
iSCPC chassis to the iBuilder Network Tree be sure to clear the RCM Installed check box and to
select all jumpers between virtual backplanes.
1. Right-click the Teleport in the iBuilder Tree and select Add 20-Slot Chassis from the
menu.

252

iBuilder User Guide

iDX Release 2.0

Configuring and Controlling the Hub Chassis

The Chassis dialog box appears, containing one row for each slot and jumper. Rows are
arranged from top to bottom to mirror the chassis slots from left to right

Figure 236. Chassis Dialog Box: New 20-Slot Chassis

2. If you have not yet loaded the license file containing your chassis licenses, follow the
procedure in Importing Your License Files on page57.
3. Enter a Name for the new chassis.
4. Enter the six-digit Serial Number of your chassis and click the Validate SN button. The
Serial Number that you enter must match a chassis serial number in your chassis license
file.

iBuilder User Guide

iDX Release 2.0

253

Configuring and Controlling the Hub Chassis

Once iBuilder has validated the chassis serial number, the read-only IP Address of the
chassis is displayed and all licensed slots and jumpers change from Off - Not Licensed to
Off - Licensed.

Figure 237. Chassis Dialog Box: 20-Slot Chassis with Licensed Slots
Note:

The IP Address displayed in the Chassis Dialog Box must match the IP Address
that you configured for your chassis. See Configuring the Chassis IP Address
on page249.

5. If the chassis contains an RCM, select RCM Installed. Do not select RCM Installed if you
are adding an iSCPC chassis.
6. To turn power on for specific slots, or to set jumpers, click the check boxes in the State
column. You should power on all slots in which you have installed line cards. After each
group of four slot rows, you will see a jumper row. Do not select the jumper boxes unless
your network spans virtual backplanes. If you are adding an iSCPC chassis, select all
jumpers.
Note:

If you are creating a Chassis Group of daisy-chained chassis, all jumpers will be
automatically selected and cannot be disabled. All line cards in a Chassis Group
are in a single network with one virtual backplane. See Daisy Chaining Hub
Chassis on page266.

7. To associate a configured line card with a specific slot, right-click the slot and select
Assign Hub from the menu.

Figure 238. Chassis Dialog Box: Selecting Assign Hub

Note: You can also select Free to indicate that no modems are installed in that
slot. The associations you make must reflect the actual physical layout of
your chassis; iBuilder cannot map logical associations to physical line card
locations.

254

iBuilder User Guide

iDX Release 2.0

Configuring a Four-Slot Chassis

8. When you select Assign Hub, a drop-down list appears in the row, listing all of the line
cards that can be assigned to that slot. Select the line card installed in that slot.

Figure 239. Assigning a Line Card to a Chassis Slot

9. Click OK. When you save your changes, iBuilder displays Changes Pending for the
Chassis in the network Tree.
10. To make your changes active, right-click the Chassis and select Apply Configuration.
iBuilder uses the following rules when making line card assignments:

If no line cards have been associated with slots, the drop-down choice list will contain all
the line cards you currently have defined.

After you make the first association, the following rules apply:
That line card no longer appears in any drop-down list.

Only line cards from the same network appear in drop-down lists for other slots in the
same virtual backplane. If you have unassigned Solo line cards, they also appear.

Drop down lists for other virtual backplanes will not contain any line cards from the
network already assigned.

If you have two networks in adjacent virtual backplanes, iBuilder will not let you set the
jumper between those two backplanes.

To assign line cards from a single network across a jumper, you must first set that jumper.

If you have a large network that spans a jumper, iBuilder will not let you clear the jumper.

All chassis slots are powered on by default when the chassis is powered on. For this reason,
the configuration database is the sole keeper of slot power and jumper settings. When the
configuration server starts up, or after a reconnection to the chassis, it automatically applies
the chassis settings stored in the database, thus restoring the desired chassis state.
Note:

8.4

If you are using Spread Spectrum, you must install your M1D1-TSS line cards
with one empty slot to the right. For example, if you want to install the line
card in slot 4, slot 5 must be empty. You cannot install a M1D1-TSS line card in
slot 20.

Configuring a Four-Slot Chassis

An iDirect four-slot chassis can be used as an alternative to a 20-slot chassis when fewer line
cards are required. As discussed in the previous section, a 20-slot chassis contains from one to
five independent groups of four slots per group. By enabling or disabling software jumpers
between groups, you can configure virtual backplanes to allow single networks to span
multiple groups of line cards.

iBuilder User Guide

iDX Release 2.0

255

Configuring a Four-Slot Chassis

The same concept applies to four-slot chassis. However, a four-slot chassis has a jumper
between each pair of slots, effectively allowing up to four groups with one slot per group.
Therefore you can allocate the four slots to virtual backplanes in any combination you choose.
A four-slot chassis actually has five slots. However, slot 5 cannot contain an active line card in
your network. In the current release, slot 5 is available only for testing. You can configure,
download and activate transmit and receive line cards in slot 5, but because the output is
attenuated, you can only use the slot for configuration and testing.
Note:

Although there is a jumper between slots 4 and 5, you cannot enable or disable
that jumper. In a stand-alone four-slot chassis, that jumper is always disabled,
isolating slot 5, which is available only for configuration and testing.
For Daisy Chained chassis, all jumpers are always enabled. In that case, slot 5
is not available for any purpose and is disabled by the NMS software.

Follow these steps to create a four-slot chassis in iBuilder:

1. Right-click your Teleport in the iBuilder Tree and select Add 4 Slot Chassis from the
menu.

256

iBuilder User Guide

iDX Release 2.0

Configuring a Four-Slot Chassis

The Chassis dialog box appears, containing one row for each slot and jumper. Rows are
arranged from top to bottom to mirror the chassis slots.

Figure 240. Chassis Dialog Box: Four-Slot Chassis

2. Enter a Name for the new chassis.
3. Enter the six-digit Serial Number of your chassis and click the Validate SN button. The
Serial Number that you enter must match a chassis serial number in your chassis license
file.
Once iBuilder has validated the chassis serial number, the read-only IP Address of the
chassis is displayed and all licensed slots and jumpers change from Off - Not Licensed to
Off - Licensed.

Figure 241. Chassis Dialog Box: Four-Slot Chassis with Licensed Slots

iBuilder User Guide

iDX Release 2.0

257

Configuring a Four-Slot Chassis

Note:

The IP Address displayed in the Chassis Dialog Box must match the IP Address
that you configured for your chassis. See Configuring the Chassis IP Address
on page249.

4. If the chassis contains an RCM, select RCM Installed.

5. The Chassis Information area of the dialog box (see Figure 240) displays status
information about the IF Module (IFM) and Outdoor Power Modules (OPM) received from
the chassis.
6. You can configure the following options for your OPMs:
a. Select BUC Voltage On to enable BUC voltage. These settings should be the same for
OPM A and OPM B.
b. Select LNB Voltage On to enable LNB voltage. These settings should be the same for
OPM A and OPM B.
Note:A four-slot chassis with four RF ports can only supply DC voltage to a BUC
or LNB on RF port 1. It cannot supply voltage on RF port 2, 3 or 4.
c. Select 22 KHz Tone On to enable the 22 KHz tone option. The 22 KHz tone capability
is for use with DiSEqC-compatible Universal LNBs. Note that if you select this option
for one OPM, it will not be selectable for the other.
d. If you have selected LNB Voltage ON, select one of the OPM-AB LNB Voltage options:
Select Low to enable low LNB voltage (+14VDC at 500 mA)

Select High to enable high LNB voltage (+19VDC at 500 mA). Typically, High is
selected. This is the default, standard setting.

7. The procedure to power on the slots, assign the line cards and set jumpers 1 through 3 is
identical to the procedure for a 20-slot chassis. Jumper 4 is controlled by the software.
See Configuring and Controlling the Hub Chassis on page252 for details on assigning
line cards to slots and setting the jumpers.
Note: If you are using Spread Spectrum, a four-slot chassis must have an empty slot
above each M1D1-TSS line card. For example, if you want to install an M1D1TSS line card in slot 2, slot 1 must be empty. You cannot install an M1D1-TSS
line card in slot 1.
8. You can configure Line cards in a four slot chassis to supply the 10 MHz clock to the Up
Converter, the Down Converter, or both. Note the following:
You must select ODU Tx 10 MHz on the Up Converter screen or ODU Rx 10 MHz on the
Down Converter screen for these selections to appear in the menu. See Adding an Up
Converter or Down Converter on page67 for details.

Only one line card per Up Converter or Down Converter can be selected for this
function. The Up Converter and Down Converter associated with each line card in
this chassis are shown in the Hub Assignment column.

This feature is available on the following line card model types: M1D1 (Tx and Rx);
eM1D1 (Tx and Rx); XLC-11 (Tx and Rx); XLC-10 (Tx only); and XLC-M (Rx only).

Only newer M1D1 line cards have this capability. If you configure an M1D1 line card to
supply the 10 MHz reference and the line card cannot perform that function, an alarm
will be raised in iMonitor when the changes are applied to the line card.

To turn on or off the 10 MHz reference from a line card, right-click in the Tx-10 MHz
column (for the Up Converter) or Rx-10 MHz column (for the Down Converter) in the slot

258

iBuilder User Guide

iDX Release 2.0

Configuring a Four-Slot Chassis

containing the line card. Then select 10 MHz On/Off from the menu. The 10 MHz setting
will toggle between off and on.

Figure 242. Turning On/Off the 10 MHz Reference on a Four-Slot Chassis

WARNING! If you have multiple iDirect networks sharing the same Up Converter or Down
Converter and you have configured one of the Tx (or Tx/Rx) line cards to
supply the 10 MHz clock, then failure of that line card will cause all networks
sharing the Up/Down Converter to fail. Under these circumstances, iDirect
strongly recommends that you install a Standby Line Card to back up the line
card supplying the 10 MHz clock. See Defining a Standby Line Card on
page115 for details.
9. Click OK to save your changes. Then apply the changes to your chassis and line cards.
Elements requiring update will show changes pending in the iBuilder tree.
Note:

iBuilder User Guide

iDX Release 2.0

If you are changing the 10 MHz clock source from one line card to another,
apply the line card changes to the original clock source to turn off the 10 MHz
before applying the line card changes to the new clock source.

259

Sharing a 20 Slot Chassis in a Multi-NMS System

8.5

Sharing a 20 Slot Chassis in a Multi-NMS System

In some system configurations, you may need to share a chassis with multiple Network
Management Systems. For example, a hub operator may want to allow a customer with his
own NMS to configure or control specific slots in a hub chassis. This section explains how to
configure multiple Network Management Systems to share a hub chassis.
Note:

You can only share a 20 slot chassis among multiple Network Management
Systems. You cannot share a four slot chassis.

When multiple Network Management Systems share one or more chassis, a single NMS Chassis
Manager Server (CM Server) controls all access to the chassis. All NMS configuration servers
that share the chassis share the single CM Server.
The CM server only allows access to chassis slots that have been licensed by iDirect. An HNO
can share licensed slots with additional NMS configuration servers by including the MAC
addresses of the configuration server machines in a CM server configuration file named
para_cfg.opt.
Figure 243 on p. 260 shows an example of an HNO NMS sharing a 20 slot chassis with VNO1 NMS
and VNO2 NMS.

Figure 243. Sharing a Hub Chassis Among Multiple Network Management Systems
To share the chassis, the HNO first determines where to run the common Chassis Manager
Server and configures the HNO NMS accordingly. (For details on how to distribute the NMS
server processes across multiple server machines, see Configuring a Distributed NMS Server
on page381.) The HNO must also obtain a chassis license from iDirect and use iBuilder to
import the license file. (See Importing Your License Files on page57.)

260

iBuilder User Guide

iDX Release 2.0

Sharing a 20 Slot Chassis in a Multi-NMS System

Once the chassis is licensed, the HNO modifies the configuration file para_cfg.opt on the
Chassis Manager Server to allow the VNO NMS configuration servers to access specific chassis
slots. This is accomplished by adding the MAC address of the VNOs NMS configuration server
machine for each slot that the VNO is allowed to access.
An excerpt from para_cfg.opt is shown in the upper left of Figure 243. In the figure, VNO 1
can access slots 1 through 4 of the chassis with IP address 172.20.136.6, while VNO 2 can
access slot 5 through 8 of the chassis with IP address 172.20.136.6.
Note:

All Network Management Systems sharing a chassis must have IP connectivity to

the machine on which the Chassis Manager Server is running.

The following three subsections show how to:

1. Configure a VNO NMS (NMS 2) to point to an HNO NMS (NMS 1)
2. Configure NMS 1 to share chassis slots with NMS 2
3. Duplicate NMS 1s chassis configuration on NMS 2 to allow the VNO to manage its slots
The example assumes that the HNO NMS (NMS 1) has already been installed (including the
Chassis Manager) and that you now want to configure the VNO NMS (NMS 2) to share the
existing Chassis Manager Server. Although the example only shares the chassis with one
additional NMS, you can follow the same steps to configure additional NMSs to use slots in the
same chassis.

Sharing the Chassis Manager Server

To share the Chassis Manager Server of NMS 1 with NMS 2:
1. Log on to the root account of the NMS 2 server machine.
2. Stop the NMS services on the server by entering the following command:
service idirect_nms stop
3. Run the script attach_extern_cm2nms.pl by entering the following command:
/home/nms/utils/db_maint/attach_extern_cm2nms.pl -db=nms
-xip=<ip address>
where <ip address> is the IP address of the external CM server machine. Sample
output is shown in Figure 244.

Figure 244. Selecting an External Chassis Manager Server

iBuilder User Guide

iDX Release 2.0

261

Sharing a 20 Slot Chassis in a Multi-NMS System

4. Enter the following command to restart the NMS services:

service idirect_nms start
5. Enter the following command to verify that all server processes are running.
service idirect_nms status
6. The MAC address of this NMSs configuration server machine is required to configure the
HNOs Chassis Manager to share the chassis. To determine the MAC address, log on to the
NMS 2 configuration server machine and enter the following command:
ifconfig
In the example in Figure 245, the MAC address is the Hwadd on the first line of the
ifconfig command output.

Figure 245. Determining a Server MAC Address

Configuring Chassis Slots for Access by Another NMS

Now that you have configured your Chassis Manager Server for sharing, follow these steps to
allow a second NMS to access specific slots in a chassis. This example configures and licenses
the chassis in the database of NMS 1 and then assigns two slots for use by NMS 2.
1. If you have not already done so, using iBuilder on NMS 1, configure your chassis and
validate the chassis Serial Number. (See Configuring a Hub Chassis on page249.)
2. Log on to the root account of the NMS server machine that is running the shared Chassis
Manager Server.
3. Change to the Chassis Manager directory by entering the command:
cd /home/nms/cm
4. Edit the file para_cfg.opt.
Each licensed chassis that is managed by this Chassis Manager Server is configured in
para_cfg.opt. Figure 246 shows an example of a 20 slot chassis as configured in
para_cfg.opt.

262

iBuilder User Guide

iDX Release 2.0

Sharing a 20 Slot Chassis in a Multi-NMS System

Figure 246. para_cfg.opt with Licensed Chassis

The 20 slot chassis in Figure 246 has Serial Number 700100 and IP address 192.168.76.16.
The rows for each slot contain the MAC addresses of the NMS configuration server
machines that can access the chassis. Zeros in a slot MAC address mean that the slot can
only be accessed by the licensed NMS.
5. For each slot you want to share with NMS 2, replace the zero MAC address with the MAC
address of the machine running NMS 2s configuration server.
In Figure 247, slots 1 and 2 of the chassis with serial number 700100 have been
reconfigured for sharing with a configuration server machine whose MAC address is
00:14:5E:17:A8:AC.

Figure 247. para_cfg.opt Reconfigured to Share Slots 1 and 2

iBuilder User Guide

iDX Release 2.0

263

Sharing a 20 Slot Chassis in a Multi-NMS System

Note:

You can enter more than one MAC address per slot. Separate each address with
a semicolon. For example: slot_1 = 00:11:25:A9:38:1E;00:21:52:C3:22:22
means that two additional configuration servers can access slot 1 of this
chassis.

6. Once you have added the MAC address for each slot you want to share, save the file and
exit the editor.
7. Enter the command:
telnet <ip address> 15262
where <ip address> is the IP address of the server running the NMS chassis manager
process.
8. At the Username prompt, log on to the chassis manager admin account. (The default
password is iDirect. You should change this password.)
9. Update the Chassis Manager with the new configuration by entering the command:
update
10. Return to the NMS server machine by entering the command:
exit
11. Log off of the NMS server machine.

Duplicating the Chassis Configuration on the Second NMS

Now that you have configured the Chassis Manager Server to share your chassis, you must
duplicate the chassis in the database of the NMS that is sharing the chassis. In this example,
NMS 2 is sharing a chassis that was originally licensed and configured on NMS 1. Therefore, you
would follow these steps on NMS 2:
1. Log on to iBuilder on NMS 2.
2. Add the chassis in iBuilder and validate the Serial Number. (See Configuring a Hub
Chassis on page249 for details.)
Make sure the Serial Number and any other common chassis parameters (such as RCM
Installed) are identical to the configuration on NMS 1.
3. Save the chassis in iBuilder.
4. Right-click the chassis in the iBuilder Tree and apply the chassis configuration.
You can now configure line cards on NMS 2 and assign those line cards to the slots you
configured for access from NMS 2s configuration server MAC address.
Note:

264

You can control which operations a VNO user on NMS 2 can perform on the
chassis by setting VNO access rights on the chassis and slots in NMS 2s
database. For more information see Sharing a Chassis Among Multiple VNO
User Groups on page342.

iBuilder User Guide

iDX Release 2.0

Changing a Chassis IP Address

8.6

Changing a Chassis IP Address

When you request a chassis license from iDirect, you must include the IP address of your
chassis in the request. The IP address that you included in the license request is loaded into
the para_cfg.opt file of the NMS Chassis Manager Server when you import your chassis license
file. If you change the chassis IP address after you have loaded your chassis license, you must
update the Chassis Manager Server with the new IP address.
Follow this procedure to change the IP address of a chassis:
1. Perform the steps in Configuring the Chassis IP Address on page249 to connect to the
chassis controller board and change the IP address of the chassis.
2. Log on to the root account of the NMS server machine that is running the Chassis Manager
Server.
3. Change to the Chassis Manager directory by entering the command:
cd /home/nms/cm
4. Edit the file para_cfg.opt.
5. In para_cfg.opt, scroll down until you find the Serial Number and IP address of the chassis
that you want to change. Search for the section beginning [CHASSIS_IP_<nnnnnn>],
where <nnnnnn> is the chassis Serial Number. The IP address is located on the next line.

Figure 248. Locating the Chassis IP Address in para_cfg.opt

Figure 248 contains an excerpt from para_cfg.opt. In the figure, the chassis with Serial
Number 700100 has an IP address of 192.168.76.16.
6. Change the IP address of the chassis to the new IP address.
7. Save the file and exit the editor.
8. Enter the command:
telnet <ip address> 15262
where <ip address> is the IP address of the server running the NMS chassis manager
process.
9. At the Username prompt, log on to the chassis manager admin account. (The default
password is iDirect. You should change this password.)

iBuilder User Guide

iDX Release 2.0

265

Daisy Chaining Hub Chassis

10. Update the Chassis Manager Server with the new IP address by entering the command:
update
11. Return to the NMS server machine by entering the command:
exit
12. Log off of the NMS server machine.
Note:

8.7

The chassis IP address configured in para_cfg.opt takes precedence over the IP

address in the chassis license file. Therefore, if you reload the original chassis
license file, you do not need to re-edit para_cfg.opt.

Daisy Chaining Hub Chassis

In some cases, more line cards may be required in a single Network than are available in one
chassis. In order to create Networks containing additional line cards, iDirect allows you to
physically link your chassis in a Daisy Chain and then use iBuilder to configure a single
network spanning multiple chassis. A Daisy Chain can include 20-slot chassis, four-slot chassis,
or both.
To use the Daisy Chain feature, you must install two multi-hub Reference Clock Modules
(RCMs) on each chassis. These RCMs are then connected in a ring and the RCM switches set to
provide inter-communication among the chassis.
Once the physical setup is complete, you create a Chassis Group under your Teleport in the
iBuilder tree. You then add the chained chassis to the group and configure the line cards
within each chassis. All line cards in the chained chassis can then be used in the same iDirect
network. Chassis and line card configuration has not changed from previous iDirect releases.
Note the following restrictions when connecting your chassis and configuring a Chassis Group:

All daisy-chained chassis must have two multi-hub RCMs installed.

Your transmit line card must be in the first (Master) chassis of the Chassis Group.

A standby line card in a slave chassis can only back up Rx-only line cards. It cannot back
up the Tx line card. A standby line card in the master chassis can back up any active line
card.

In iBuilder, you cannot add an existing chassis to a Chassis Group. You must first create
the group; then add each chassis to the group.

All daisy-chained chassis must be within 10 dB of each other. (The power range for an
iDirect chassis is from -5 dB to -65 dB.)

Note:

Although iBuilder does not limit the number of chassis that you can add to a
Chassis Group, iDirect has only certified, and therefore only supports, two
chassis per group.

The following sections explain how to physically connect a daisy chain of chassis and how to
configure them as a Chassis Group in iBuilder.

266

iBuilder User Guide

iDX Release 2.0

Daisy Chaining Hub Chassis

8.7.1 Connecting Your Chassis in a Multi-Hub Chain

This section explains how to connect your daisy-chained hub chassis and how to set the RCM
switches to allow the individual chassis to operate in the same network. It assumes that all
chassis in the group are configured with two multi-hub RCMs.
A Chassis Group (or multiple hub network) has two or more chassis connected in two rings by
connecting the RCM input and output connectors as shown in Figure 249.

Figure 249. Chassis Group Interconnection

iBuilder User Guide

iDX Release 2.0

267

Daisy Chaining Hub Chassis

The interface to the multi-hub RCM is shown in Figure 250. The INPUT and OUTPUT
connectors are used to form the rings shown in Figure 249.

Figure 250. Multi-Hub RCM Interface

The components of the multi-hub RCM interface are defined in the following sections.

Multi-Hub RCM Interface Connectors

The INPUT and OUTPUT connectors shown in Figure 250 are nine-pin Micro-D connectors that
mate with a MOLEX 83421 or equivalent.
As depicted in Figure 249, the INPUT connector receives input signals from the RCM output of
the previous hub chassis in the chain; while the OUPUT connector transmits output signals to
the RCM input of the next hub chassis in the chain. These signals are used to coordinate
operation of the linked chassis.

Multi-Hub RCM Interface Switches

The multi-hub RCM interface shown in Figure 250 has the following switches:

INT/EXT: Determines whether or not an external 10 MHz reference clock is expected

MULTI/SINGLE: Set in a accordance with the type of network (single-hub or multi-hub)

SLAVE/MASTER: Determines the operational role of the chassis in the Chassis Group

Multi-Hub RCM Interface LEDs

The multi-hub RCM interface in Figure 250 has the following LEDs:

268

REF CLK: Status of the external reference clock, if present

FLL: Condition of the FLL when used

ON/STDBY: Indicates if the RCM is Master or Slave

FAIL: Indicates a failure condition other than the failure of the reference clock

iBuilder User Guide

iDX Release 2.0

Daisy Chaining Hub Chassis

The status indicated by the color of each LED is specified in Table 6.

Table 6. Multi-HUB RCM Status Indicators
LED

OFF

GREEN

YELLOW

RED

REF CLK

10 MHz not used

10 MHz signal
present

N/A

10 MHz signal missing

FLL

FLL not running

FLL locked

FLL tracking

N/A

ON/STBY

N/A

RCM is Master

RCM is Slave

N/A

FAIL

No failures detected

N/A

N/A

Failure condition present

To set up your chassis to work in a multi-hub configuration, follow these steps:

1. Connect the chassis as shown in Figure 249.
Note: At this time, iDirect only supports two chassis in a multi-hub configuration.
2. The first chassis in the Chassis Group is the Master chassis. Other chassis are Slave chassis.
The Master chassis must hold your Tx line card and any standby line cards that back up
the Tx line card. On each chassis in the multi-hub configuration, set the RCM switches for
both RCMS as shown in Table 7.
Table 7. RCM Switch Settings for Daisy Chained Chassis
INT/EXT

MUTLI/SINGLE

SLAVE/MASTER

Master Chassis

EXT if external clock; INT otherwise

MULTI

MASTER

Slave Chassis

EXT if external clock; INT otherwise

MULTI

SLAVE

iBuilder User Guide

iDX Release 2.0

269

Daisy Chaining Hub Chassis

8.7.2 Adding a Chassis Group in iBuilder

A Chassis Group consists of an ordered list of daisy chained chassis. When you add a chassis
to the group, it is automatically configured as the last chassis in the group. If desired, you can
then use iBuilder to modify the order of the chassis in the Chassis Group.
The Chassis Group adds a new level to the iBuilder tree for networks using the Daisy Chain
feature, as illustrated in Figure 251.

Figure 251. Chassis Group in iBuilder Network Tree

As in previous releases, when you configure an individual chassis in iBuilder, you enable or
disable the software jumpers that connect or segregate the chassis partitions. However, when
you add a chassis to a Chassis Group, all jumpers in the chassis are automatically enabled and
cannot be disabled. Therefore, all slots in all chassis in a Chassis Group are, by design,
dedicated to a single virtual backplane. (See Configuring and Controlling the Hub Chassis on
page252.)
To add a Chassis Group to the iBuilder tree:
1. Right-click your Teleport in the iBuilder tree and select Add Chassis Group from the
menu.

270

iBuilder User Guide

iDX Release 2.0

Daisy Chaining Hub Chassis

2. In the Chassis Group dialog box, enter a Name for the new group.

Figure 252. Chassis Group Dialog Box

3. Click OK to save the Chassis Group in the iBuilder tree.

8.7.3 Adding a Chassis to a Chassis Group

To add a chassis to a Chassis Group:
1. Do either of the following:
From the Chassis Group dialog box of the group to which you want to add the chassis,
click Add 20 Slot Chassis or Add 4 Slot Chassis, or

iBuilder User Guide

iDX Release 2.0

Right-click the Chassis Group in the iBuilder tree and select Add 20 Slot Chassis or
Add 4 Slot Chassis from the menu.

271

Daisy Chaining Hub Chassis

Both methods are illustrated in Figure 253.

Figure 253. Adding a Chassis to a Chassis Group

2. In the Chassis dialog box, add your line cards to the chassis Slots to reflect your network
configuration.

Figure 254. Chassis With All Jumpers Enabled

Note: When you add a chassis to a Chassis Group, all jumpers in the chassis are
automatically enabled and cannot be disabled. Therefore, all slots in all
chassis in a Chassis Group are dedicated to a single virtual backplane.

272

iBuilder User Guide

iDX Release 2.0

Daisy Chaining Hub Chassis

3. Click OK in the Chassis dialog box when you are finished configuring the chassis. If you
added the chassis from the Chassis Group dialog box, you will be returned to that dialog
box. Click OK in the Chassis Group dialog box to save the modified configuration.

Figure 255. Editing or Removing Chassis in a Chassis Group

Note:

You can use the Edit and Remove buttons in the Chassis Group dialog box to
modify the configuration of a chassis, or to delete a chassis from the group.
First select the chassis in the Daisy Chained Chassis area of the dialog box;
then click the button for the function you want.

8.7.4 Changing the Order of the Chassis in a Chassis Group

By default, Chassis are ordered in a Chassis Group according to the order in which they are
added to the group. However, you can use iBuilder to change the order of the chassis within a
group.
Note:

Your transmit line card and any standby line cards that back up the transmit
line card must be in the first chassis. Subsequent chassis can only contain
receive-only line cards or standby line cards for receive-only line cards.

To change the order of the Chassis within a Chassis Group:

1. Right-click the Chassis Group in the iBuilder tree and select ModifyItem from the menu.

iBuilder User Guide

iDX Release 2.0

273

Daisy Chaining Hub Chassis

2. Select a chassis in the Daisy Chained Chassis area of the Chassis Group dialog box.

Figure 256. Changing the Order of Chassis in a Chassis Group

3. Use the arrow buttons at the top of the dialog box to move the chassis up or down in the
list.
4. Click OK to save your changes.

274

iBuilder User Guide

iDX Release 2.0

Activating and Deactivating Remotes

9 Controlling Remotes

This chapter discusses the following topics:

9.1

Activating and Deactivating Remotes on page275

Moving Remotes on page277

Activating and Deactivating Remotes

Remotes may be activated and deactivated by selecting the remote you want to activate,
right-clicking on it, and selecting Activate Remote.
1. Select a deactivated remote, right-click, and then select Activate Remote.

Figure 257. Activating a Remote

The term Activation Pending appears in red text to the right of the remote you are
activating. The term Changes Pending appears in red text to the right of its
corresponding network. For other states, see Step 4 on page 276.

iBuilder User Guide

iDX Release 2.0

275

Activating and Deactivating Remotes

2. Select the network in which the remote resides, right-click the network, and then select
Apply Configuration.

3. Click Yes to confirm the action.

4. Click OK to acknowledge that the configuration has been downloaded successfully.

If the remote has been acquired into the network, the term Nominal appears in blue text
to the right of both the remote and the network. If it has not been commissioned and
acquired into the network for the first time, the term Never Applied appears to the right
of the remote.
5. To deactivate an active remote, select an activated remote, right-click it, and select
Activate Remote. The check mark will be removed and the remote will become inactive.

276

iBuilder User Guide

iDX Release 2.0

Moving Remotes

9.2

Moving Remotes
In iBuilder you can easily move remotes from one Inroute Group or Network to another.
1. Right-click the remote to be moved, and select Move.

2. In the Move dialog box, highlight the destination Inroute Group and click OK.

Figure 258. Move Dialog Box

The remote now appears under the selected Inroute Group in the Tree.
Note:

iBuilder User Guide

iDX Release 2.0

Since iNFINITI remotes cannot receive DVB-S2 outbound carriers, you cannot
move an iNFINITI remote into a DVB-S2 network. Similarly, since Evolution X3
remotes can only receive DVB-S2 outbound carriers, you cannot move an
Evolution X3 remote into an SCPC network.

277

Moving Remotes

278

iBuilder User Guide

iDX Release 2.0

Configuration Options Files

10 Retrieving and Applying

Saved and Active
Configurations

Once you have configured your network elements, you may add more elements which will
need to be configured, or you may simply modify the configuration of one or more elements in
your network. This chapter explains how to manage updates to your iBuilder configuration. It
includes the following sections:

Configuration Options Files on page279

Hub-side and Remote-side Options Files on page280

Modifying, Deleting, and Viewing Configurations on page281

Retrieving Configurations on page281

Comparing Configuration Changes on page284

Applying Configuration Changes on page286

Configuration Changes on Roaming Remotes on page292

10.1 Configuration Options Files

You can retrieve current configurations and save them on your PC as Options files. You can
also download (or apply) the Options files to other elements of the same type or to elements
that will be affected by a modified elements new configuration. In addition, you can
compare an elements Saved configuration its Active configuration.
Network elements such as remotes and Protocol Processors have both Active and Saved
configurations. The Saved configuration is the configuration that is stored in the NMS
database. The Active configuration is resident on the network element itself. When you
modify the configuration of an element, the Saved configuration is updated. When you Apply
the changes, the Saved configuration is sent to the element and loaded as the Active
configuration.

iBuilder User Guide

iDX Release 2.0

279

Hub-side and Remote-side Options Files

The iDirect NMS system knows which elements are dependent upon one another, so that if you
download an Options file to one element that affects the configuration of other elements in
the network, the system will automatically update those elements as well.
You can retrieve the configurations of the following elements:

Protocol Processors (Active and Saved configurations)

Networks (Active and Saved configurations)

Chassis (Saved configuration only)

Line Cards (Saved configuration only)

Remotes (Active and Saved configurations)

Note:

If a VNO user retrieves an options file, only elements owned by or visible to

that VNO are included.

10.2 Hub-side and Remote-side Options Files

Each remote has two separate Options files, each with Saved and Active versions. One remote
Options file, called the remote-side Options file, is sent to the remote. The other remote
Options file, called the hub-side Options file, is sent to the Protocol Processor to configure
the remote on the PP. When you modify a remote using iBuilder, the changes may affect the
remote-side Options file, the hub-side Options file, or both.
You can perform the following control operations on both types of remote Options files from
the remote level of the Network Tree:

Apply configuration changes

Retrieve the active and saved configurations

Compare the active configuration to the saved configuration

Separate versions of the Changes Pending icon indicate which of the remote Options files
has been affected by a change. There are three icon variations: remote-side only, hub-side
only, and both. The hub-side icon is referred to as PP-Side in Figure 259.

Figure 259. Changes Pending Icons

The following sections describe how to modify, retrieve, compare, and apply configurations
on remotes as well as on other network elements.
Note:

280

Beginning in iDX Release 2.0, the Dynamic Function Options Exchange (DFOE)
protocol allows some remote-side configuration changes to be dynamically
applied. All remote hub-side options groups beginning with 'RMT_' are sent
from the Protocol Processor to the remote using the DFOE protocol. For these
options, you are no longer required to apply remote-side changes to the remote
and you will no longer see remote-side changes pending in iBuilder.

iBuilder User Guide

iDX Release 2.0

Modifying, Deleting, and Viewing Configurations

10.3 Modifying, Deleting, and Viewing Configurations

You can modify your network configuration by right-clicking on the element in the Tree that
you want to modify and selecting Modify from the menu. In cases where you can also modify
the VNO properties for an element, select Modify Item to modify the elements
configuration; select Modify VNO to modify the VNO properties. Similarly, you can delete
or view the configuration of an element by selecting either Delete, View Properties, View
Properties Item, or View Properties VNO.
Note:

You must deactivate a remote before you can delete it. When a remote is
activated, a check mark is shown next to the Activate Remote selection in the
network tree for the remote. To deactivate a remote, right click the remote in
the Network Tree and select Activate Remote to remove the check mark.

The Network Tree menu selections for viewing and deleting a remote are shown in Figure 260.
Notice that you cannot select Delete until a remote is deactivated.

Figure 260. Viewing and Deleting Remotes

10.4 Retrieving Configurations

When you make modifications to any element, iBuilder saves the modified configuration at
the NMS in the Saved Options file. To retrieve this latest version of the Options file and apply
it to one or more elements, you must use the Retrieve Saved Configuration function.
An Active Configuration is the configuration that is currently running on the element. By
retrieving it, you are creating an Options file with that current configuration and saving it on
your PC as an .opt file. You can then downloaded, or apply, this Options file to one or more
elements of the same type. For example, if you retrieve and save the current configuration of
a particular remote, you can then apply that configuration to one or more other remotes.

10.4.1 Retrieving a Single Saved or Active Configuration

To retrieve a saved or active configuration, follow these steps:
1. Right-click the element whose configuration you want to retrieve, select Retrieve, and
then select Active Configuration or Saved Configuration.

iBuilder User Guide

iDX Release 2.0

281

Retrieving Configurations

Note:

In the case of remotes, the menu allows you to select either the hub-side or the
remote-side configuration for retrieval. The example shows Saved
Configurations being selected. However, the procedure for both are the same.

2. Navigate to the folder on your PC in which you want to save the options file and click
Save.
3. The options file opens in Notepad allowing you to review the configuration parameters.

Figure 261. Options File Viewed in Notepad

282

iBuilder User Guide

iDX Release 2.0

Retrieving Configurations

10.4.2 Retrieving Multiple Saved or Active Configurations

You can simultaneously retrieve multiple saved or active configurations for remotes or hubs as
follows:
1. Right-click the Network element and select Retrieve Multiple. Then select either Active
Configurations or Saved Configurations.

This example shows Saved Configurations being selected. The procedure for retrieving
multiple Active Configurations is identical.
2. In the Multiple Configurations Retrieve dialog box, select the remotes and/or the hubs
for which you want to retrieve the configurations.

Figure 262. Multiple Configurations Retrieve Dialog Box

iBuilder User Guide

iDX Release 2.0

283

Comparing Configuration Changes

3. Click OK to open the Save As dialog box.

Figure 263. Save As Dialog Box

4. In the Save As dialog box, navigate to the location on your PC where you want to save the
configuration files.
5. Click Save.
iBuilder retrieves the selected configurations and copies them to the designated location.
Both the remote-side and hub-side options files will be retrieved and saved for all selected
remotes.

10.5 Comparing Configuration Changes

When you perform a Retrieve command, iBuilder automatically opens the Options file so you
can view the configuration. In addition, if you have made changes to an element, you can
compare the Latest configuration in iBuilder with the Active configuration currently
applied to that element. Once you are satisfied with the results, apply the configuration using
one of the methods in Applying Configuration Changes on page286.
You can compare configurations for Protocol Processors, Chassis, Networks, Line Cards, and
Remotes using the following method. This example compares the active configuration that
was last applied to a remote with the remotes latest configuration as stored in the NMS
database. Notice that the operator has configured a MUSiC Box for this remote, but has not
yet applied the changes.

284

iBuilder User Guide

iDX Release 2.0

Comparing Configuration Changes

To compare the active configuration of an element with its latest configuration, follow this
procedure:
1. Right-click the element in the Tree and select Compare Configurations. In the case of a
remote, select Remote-Side or Hub-Side.

2. To view all configuration parameters in the dialog box, clear the Show differences only
check box. Note that differences are shown in red.

Figure 264. Comparing the Active and Latest Configurations

iBuilder User Guide

iDX Release 2.0

285

Applying Configuration Changes

3. To view only the parameters that are different, select the Show differences only check
box.

Figure 265. Comparing Configurations: Differences Only

10.6 Applying Configuration Changes

You can apply the latest configuration changes to multiple elements at the same time, which
greatly improves the management of your networks, especially as they grow. Whether you
want to download configurations to one or multiple Networks, Line Cards, or Remotes, you
can do so via the Automated Configuration Downloader dialog box, accessed from the
Network element in the Tree. You can also use the TCP Download feature to download
Options files to multiple remotes and line cards. The TCP Download feature allows you to
download Image files also. For information about this feature, see chapter 11, Upgrading
Software and Firmware.

Maintenance Window Consideration

Be aware, however, that downloading configurations or images to multiple elements can take
a long time to complete and uses a lot of bandwidth. Therefore, you probably should establish
a maintenance window in which to make a large number of multiple changes.

Sequence of Download
When applying configurations to multiple elements, iBuilder treats each group of elements as
a batch, processing the batches in upstream order. Therefore, remotes are downloaded first,
followed by hub lines cards, and finally the network itself.
All elements of a batch must complete its download successfully before iBuilder will proceed
to the next batch. For example, if any remote in a given batch fails during the download
process, iBuilder will stop at the end of the remote batch and wait for your next command. It
will not download to any line cards or to the network. However, all elements within a single
batch are processed simultaneously, so a single remote failure will not stop the other remotes
from being downloaded. Also, if the reset button is selected on the dialog box, iBuilder
immediately sends a reset command to any remote that downloads successfully. If this
behavior is not desired, make sure you check the Dont reset button (you can always select
Reset only at a later time).

286

iBuilder User Guide

iDX Release 2.0

Applying Configuration Changes

10.6.1 Applying Multiple Configurations to Network Elements

To download configurations to one or several of these elements, follow these steps:
1. Right-click your Network and select Apply Configuration Multiple. This launches the
Automated Configuration Downloader.

Figure 266. Automated Configuration Downloader

iBuilder User Guide

iDX Release 2.0

287

Applying Configuration Changes

2. Select the options particular to your download. (These options are explained in the next
section.)
3. Click Start. The Status column shows that the configuration is downloading.

Figure 267. Viewing the Download Status

Automated Configuration Downloader Options

The Automated Configuration Downloader is divided into three main sections:

Remotes

Line Cards

Network

Beside each entry is a check box that you can select to include that item in the download.
When you first launch the Automated Configuration Downloader, all Remotes that currently
have changes pending are automatically preselected. If a box is not checked, the
configuration will not be downloaded to the corresponding element.
In the Remotes pane are three additional options.
1. The Target options let you choose to download the remote-side options file, the hub-side
options file, or both.
2. The Protocol options let you choose between reliable (TCP) and push (UDP) delivery
methods. If all the modems in your list are currently acquired into the network, iDirect
recommends using the reliable delivery method.
3. The Reset options allow you to choose a reset action after the download completes. The
three choices are: Reset on success, Reset only, or Dont reset.
Reset on success automatically resets the modems after a successful download.

Reset only resets the modems without a download being performed. This option is
useful if you previously selected Dont reset, but now you want to reset the
downloaded modems.

Dont Reset does not reset the modem.

Stopping the Download

The stop command attempts to halt processing at the next appropriate step after its current
operation. iBuilder will not stop download operations that are currently in progress, but when
the current operation is finished, iBuilder will not continue to the next chosen step.
For example, assume you have selected a given remote and clicked the Reset on Success
button. If you click Stop in the middle of the download, the reset command will not be sent.
However, the current download will finish; iBuilder makes no attempt to halt a download in
the middle or to back out a downloaded configuration.

288

iBuilder User Guide

iDX Release 2.0

Applying Configuration Changes

10.6.2 Applying a Configuration to a Protocol Processor or

Chassis
To apply configuration changes to a Protocol Processor or a Chassis, follow these steps. The
example shows the configuration being applied to the protocol processor, but the procedure is
the same for both.
1. Right-click the Protocol Processor or Chassis and select Apply Configuration.

2. When the message appears asking you to confirm the download, click Yes.

3. When the message appears indicating that the configuration has been downloaded
successfully, click OK.

iBuilder User Guide

iDX Release 2.0

289

Applying Configuration Changes

10.6.3 Applying a Configuration to the Network

To apply the configuration at the Network level, follow these steps:
1. Right-click the Network and select Apply Configuration.
2. When the message appears asking you to confirm the download, click Yes.

3. Wait while the configuration is applied.

After the configuration is applied to the Network, the status of the network changes from
Changes Pending to Nominal.

10.6.4 Applying a Configuration to the Line Card

1. Right-click the Line Card and select Apply Configuration.
2. When the message appears prompting you to confirm the download, click Yes.

When the download is complete and successful, a message appears, allowing you the
option of resetting the unit now or waiting and resetting it later.

290

iBuilder User Guide

iDX Release 2.0

Applying Configuration Changes

3. Click Reset Now or Reset Later, depending upon your needs.

If you reset the remote now, a message appears, confirming that the unit was reset
successfully.

4. Click OK.

10.6.5 Applying a TCP or UDP Configuration to a Remote

When applying remote configurations, you may choose remote-side, hub-side, or both sides.
When you select both sides, iBuilder enforces the correct apply order: remote, then hub.
1. Right-click the remote whose configuration you want to be changed.
2. Select Apply Configuration, and then select Reliable Hub-Side (TCP), Reliable RemoteSide (TCP), Reliable (Both), or Push Remote-Side with Reset (UDP). It is recommended
that you use TCP if possible.

iBuilder User Guide

iDX Release 2.0

291

Configuration Changes on Roaming Remotes

3. When the message appears asking you to confirm the download, click Yes.

When the download is complete and successful, a dialog box appears, giving you the
option of resetting the remote now or waiting and resetting it later.

4. Click Reset Now or Reset Later, depending upon your needs.

If you reset the remote now, a message appears, confirming that the remote was reset
successfully.

5. Click OK. The remotes status will return to nominal.

10.7 Configuration Changes on Roaming Remotes

The NMS maintains two options files for each non-roaming remote. One file resides on the
Protocol Processor and the other resides on the remote itself. Together, these two files
represent the configuration for a remote terminal in a single network. Roaming remotes
require a different set of options files. This section describes the options files associated with
roaming remotes and the implications of applying configuration changes to remotes that are
configured in multiple networks.

10.7.1 Roaming Options File Generation

Figure 268 illustrates the options files generated by the NMS for both non-roaming and
roaming remotes. Roaming remote options files are built as an extension to the normal two
file structure.

292

iBuilder User Guide

iDX Release 2.0

Configuration Changes on Roaming Remotes

One Remote (global instance ), Multiple Networks

One Remote, One Network

Remote
Definition in
a Network

PP Options
File

Remote
Definition in
Network 1

Remote
Options File

Remote
Definition in
Network 2

Remote
Definition in
Network 3

PP Options
File Network 1

PP Options
File Network 2

Remote
Options File
Network 1
Network 2
Network 3

PP Options
File Network 3

Figure 268. Global NMS Options Files

As with non-roaming remotes, the NMS sends a single options file to each roaming remote.
However, the NMS puts all the necessary parameters for each of the member networks into a
single remote options file.
The structure of the options file sent to the protocol processor has not changed. However, the
NMS generates a separate PP options file for each network a roaming remote belongs to.

10.7.2 Pending Changes across Networks

With a single remote options file now containing elements from multiple networks, a roaming
remotes configuration can now change for one, many, or all networks the remote is a
member of. This leads to some differences when the NMS compares its own configuration files
to those resident on the Protocol Processor or the remote.
For changes to a single network affecting only the Protocol Processor options files for a
roaming remote:

Only that specific network instance will show the Changes Pending icon

Only comparisons performed on that network instance will show the differences

For changes that affect multiple networks, or changes to any remote consolidated options
file:

Each network instance will show the Changes Pending icon

Comparison operations from any of these networks will show the differences.

iBuilder User Guide

iDX Release 2.0

293

Configuration Changes on Roaming Remotes

10.7.3 Applying Changes to Roaming Remotes

When you modify a roaming remote in one network, you can apply the changes to the remote
regardless of which network it is in. You do not need to wait until the remote is acquired into
the network with the pending changes.
As long as the NMS can route packets to the remote terminal, it will update the remote when
you apply the changes. However, the remote must be acquired into some network.
For example, if a remote is a member of Networks 1, 2 and 3, and is currently in Network 1,
you can make changes that affect Network 2 and apply them immediately.

294

iBuilder User Guide

iDX Release 2.0

Image Package Versions

11 Upgrading Software and

Firmware

An image package is a file that contains firmware images for a particular release and
hardware platform. The packages contain FPGA (Field Programmable Gated Array) Images.
You can download images to remotes or line cards via the Multicast Download feature,
Download Image feature, or TCP Multicast feature. The TCP Multicast feature allows you to
download both Option and Image files to remotes and line cards.
To upgrade from one version to another, you should schedule a maintenance window with your
customers. The time required for an upgrade varies based on the number of remotes you have
deployed. The upgrade process is described in the Network Upgrade Procedure for your
release. That document is specific to each release.
This chapter includes:

Image Package Versions on page295

Downloading an Image to Remotes and Line Cards Concurrently on page296

Resetting Remotes on page300

Downloading an Image or Configuration File via TCP on page301

Downloading Remotes Using Revision Server on page301

11.1 Image Package Versions

The iDirect NMS GUIs, NMS Servers, Protocol Processor, embedded software and firmware are
all released with the same version number. The NMS GUIs and NMS servers must match in
version number or you are not allowed to log on. A mixed installation (one where not all
components have the same version) is not guaranteed to function properly.
A number of packages are installed on the NMS server during the upgrade. See the Network
Upgrade Procedure for your release for details.

iBuilder User Guide

iDX Release 2.0

295

Downloading an Image to Remotes and Line Cards Concurrently

11.2 Downloading an Image to Remotes and Line Cards

Concurrently
The Multicast Download feature allows you to download images to multiple remotes or
multiple line cards in any given network. However, images can only be downloaded to a single
network at a time. The Multicast Download feature uses UDP, which is explained below.
Note:

Your upstream router must have multicast enabled before you can multicast
images to your line cards.

11.2.1 Multicast via UDP

The Multicast Download operation is driven by the NMS Configuration Server, which spawns a
stand-alone command that resides on the NMS server machine. The protocol for packet
transmission exists entirely between the modems and the standalone command; the Protocol
Processor isnt involved in any way, except to transmit multicast packets on the downstream
(and ACKs/NACKs on the upstream).
The multicast address used for package downloads is statically configured in all iDirect
equipment. Therefore, IGMP is not required by iDirect modems to process these update
messages. However, IGMP messages are advertised in case there is third party equipment that
needs to be dynamically updated.
A multicast download operation consists of two phases: the data transmission phase and the
flash phase. During the data transmission phase, the package is broken into multicast IP
packets, each of which is given a sequence number. All recipients reassemble the individual
packets, in order, into the original image package. If a recipient misses a packet, it will send
a NACK back to the sender, at which point the sender re-winds to the missed packet and
begins re-sending. A remote will only NACK once; if it doesnt receive the missing packet it
gives up and sends a final NACK when it receives the last packet.
When reassembly is complete, the flash phase begins. Each individual component of the
package is extracted and written to the modems flash memory. After flashing is complete,
the modem resets automatically if the reset option was checked in iBuilder.
We refer to the protocol used for transmission as semi-reliable. It is reliable in that
recipients will NACK missing packets, but only semi-reliable in that packets are not re-sent
forever. Also, the recipients only NACK missing packets; a single ACK is sent when all packets
have been received, but no ACKs are sent during packet transmission.

296

iBuilder User Guide

iDX Release 2.0

Downloading an Image to Remotes and Line Cards Concurrently

11.2.2 Multicast Download Procedure

Follow these steps to perform a multicast download:
1. Right-click the Network and select Package DownloadMulticast. The Multicast
Download dialog box is displayed.

Figure 269. Multicast Download Dialog Box

2. Select the download parameters. (See Section11.2.3 Selecting the Download
Parameters for details.)
3. Click Start.

11.2.3 Selecting the Download Parameters

In the Multicast Download dialog box (Figure 269), you can select an image to download to
multiple remotes or multiple line cards, but the images for remotes and line cards are
different files, and the two files cannot be downloaded to the remotes and line cards at the
same time. You must download the images to all of the remotes and then perform the
procedure again to download the appropriate images to all of the line cards. You can deselect
any remote or line card that you do not want to receive the new image.

iBuilder User Guide

iDX Release 2.0

297

Downloading an Image to Remotes and Line Cards Concurrently

The dialog box is divided into the following sections.

Package Section
The upper-left section of the dialog box contains a drop-down list of all available image
packages (see Image Package Versions on page295). Select your Hardware, Role, Mode,
and Version to determine the Selected Package. When you select a particular package, the
contents of the package are displayed in the Contents box below the drop-down list. Confirm
that the control application version is correct; it is in the last row of the list.
The eM1D1 Line Card, the Evolution e8350 remote, and the iConnex e800/e800mp remotes
are all capable of supporting either an SCPC outbound carrier or a DVB-S2 outbound carrier.
The firmware for these two modes is contained in two separate packages. Therefore, when
you select Remote Role for Evolution Remote or Hub Role for Evolution Line Card, you can
select one of two modes: DVB-S2 or iNFINITI (SCPC). (See Figure 269.) This determines which
package is downloaded to the hardware.

Figure 270. Selecting DVB-S2 or iNFINITI Firmware Package

WARNING! In cases where the hardware supports both DVB-S2 and SCPC, iDirect strongly
recommends that you download both packages. If you change a remotes
configuration (options file) to receive a different carrier type but the remote
does not have the corresponding firmware package installed, the remote will
be stranded. A site visit will be required to recover the remote.

Modems and Hubs Sections

iBuilder does not allow you to download an image package to an element that is not
compatible. When you select an image package for a given element (for example, an iNFINITI
8350 remote or an M1D1 line card), only the elements that are compatible with that package
are displayed in the list of remotes or hubs in their respective boxes on the right side of the
dialog box. For example, if you select the package for e8350 remotes, only e8350 remotes are
displayed in the Remotes box. Likewise, if you select the package for Receive line cards, only
Receive line cards are displayed in the Hubs box. This is a safety feature that prevents you
from sending a mismatched image package to the remotes and hubs. If you do not want to
download the image package to a given remote or line card, clear the check box next to it.

Download Parameters Section

The lower-left corner of the dialog box contains run-time parameters that change the
behavior of the multicast. iBuilder automatically chooses an appropriate Download Rate for
your network; setting this rate higher is not recommended as it may cause the download to
fail.

298

iBuilder User Guide

iDX Release 2.0

Downloading an Image to Remotes and Line Cards Concurrently

The Credentials and Group Address fields are primarily for reference purposes, and should
be left unchanged. The Reset check box, if selected, tells each remote to reset after the
package has been processed.
When you have made your selections, click Start to begin the download. The Progress bar at
the bottom of the dialog box will indicate the status of your download. The results of the
download to each remote (or line card) recipient are displayed next to that recipients name
in the appropriate pane. Depending on the status of the download, you will see either
Download Complete or Download Incomplete. If you receive the latter message, this
doesnt necessarily mean the download failed; it simply means the sending application didnt
receive an ACK (acknowledgement) from that recipient. This behavior is explained in the next
sections.

11.2.4 Downloading an Image to Out of Network Remotes

You can download an image to remotes that are out of network. As long as the remote is
locked on the downstream carrier, it will receive the packets, reassemble the package, and
flash its contents. Make sure you set the reset flag if you multicast images to out-of-network
remotes.
Since the remotes are out-of-network and unable to send the final acknowledgement, the
iBuilder dialog box will display the Download Incomplete message after sending all packets.
If the remote is encrypted and out-of-network, you cannot perform a multicast download to
it. This is because the required key exchange cant take place. The workaround in this
situation is to temporarily turn encryption off, send the package, and turn it back on after the
image has been downloaded.

11.2.5 Interactions with Other iBuilder Operations

The sequence of events during a multicast download is as follows:
1. The image package is broken into separate IP multicast packets.
2. Each packet is sent in order to the recipients.
3. When all packets have been received, each recipient sends an acknowledgement to the
sender
4. The contents of the package are extracted and written to flash memory (a defragment
operation is performed automatically if necessary).
5. If the reset option was checked in iBuilder, each recipient resets.
After step 3, iBuilder and the NMS are out of the loop. iBuilder declares the download
complete, and the user is free to move on to other tasks; however, the recipients are not
finished they will take up to a minute to flash the package contents. For this reason, it is
wise to view recipient multicast activity in iMonitor, and wait until step 5 is complete before
continuing with other tasks in iBuilder. Recipients send events into the NMS indicating the
progress of the multicast operation, and these events can be viewed in an iMonitor events
pane if the recipients are in-network.
For example, consider the following sequence of events:
1. You send a package to a group of remotes.

iBuilder User Guide

iDX Release 2.0

299

Resetting Remotes

2. When iBuilder declares the operation complete, you immediately send an options file to a
particular remote.
Because options files are also stored in flash memory, and the remote may still be flashing
package contents, the options file apply will block until the package flash is complete.
iBuilder, meanwhile, is waiting for a response to the options apply, and will probably time out
waiting for that response. The apply will work, but not until after iBuilder gives up waiting for
a response. iDirect recommends you wait until all multicast activity is complete before
performing additional tasks in iBuilder.

11.3 Resetting Remotes

Modifications must be applied to all of the affected remotes in the network by resetting
them.
1. Right-click the remote, select Reset RemoteReliable (TCP).

2. Click Yes to confirm the reset.

A message appears confirming that the reset command has been issued. The success of
the reset is confirmed with a dialog box.
3. Click OK to acknowledge the confirmation.

300

iBuilder User Guide

iDX Release 2.0

Downloading an Image or Configuration File via TCP

11.4 Downloading an Image or Configuration File via

TCP
You can download an Image or Options file via the TCP protocol by using the TCP Download
feature. However, images and options files can only be downloaded to a single network at a
time.
Follow these steps to download an Image or Options file via the TCP protocol:
1. Right-click your Network and select Package Download TCP.

The TCP Package Download dialog box is displayed.You work with the TCP Package
Download dialog box the same way you do with the Multicast Download dialog box. Follow
the directions in Selecting the Download Parameters on page297.
2. Select the appropriate options in the lower left portion of the TCP Download dialog box.
3. Click Start.

11.5 Downloading Remotes Using Revision Server

Prior to iDS Release 7.0, it was the responsibility of the network operator to ensure that all
remotes were successfully upgraded to the current version of their image files. The network
operator had to monitor the network to determine if any remotes failed to receive the initial
image upgrade. If so, the operator had to manually resend the image package until all
remotes were up-to-date.
Using iDirects Revision Server, you can configure the NMS to automatically upgrade remote
sites that have not yet received the latest download. Once you select a set of remotes to
upgrade, the Revision Server packages the current images and options files together. (This
includes the Board Support package.) It then periodically transmits the latest package to the
selected remotes, stopping only after all remotes in the list have successfully received their
upgrades.

iBuilder User Guide

iDX Release 2.0

301

Downloading Remotes Using Revision Server

You can also use the Revision Server to send only options files, without reloading the images.
This allows you to change the configuration of one or more remotes and ensure that the
changes will be applied without further operator intervention.
The Revision Server has the following characteristics:

The Revision Server can download multiple networks simultaneously.

By default, the Revision Server uses up to 10 percent of the downstream bandwidth when
it is active. (However, you can modify the download rate when you launch an upgrade.)

Once you start the Revision Server, it immediately begins to upgrade all the selected
remotes. If one or more remotes fail to receive the package during an upgrade cycle, the
revision server will automatically begin a new cycle to retransmit the package to those
remotes. (The time remaining before the next cycle is displayed on the Revision Server
dialog box.) Once all remotes in the list are upgraded, the revision server stops.

You can command the Revision Server to stop upgrading one or more networks while the
upgrade is in progress.

VNO users can use the Revision Server to download remotes as long as the VNO has the
necessary permissions or ownership of the appropriate network elements. Only remotes
that the VNO is allowed to download are displayed on the Revision Server GUI.

11.5.1 How the Revision Server Works

In order to decide which remotes require updates, the Revision Server determines the
versions of software and configuration (options file) currently loaded on each remote. It then
compares the versions on the remote to the latest versions for that remote as stored at the
NMS. Based on this comparison, the NMS assigns each remote a status of UpRev or DownRev.
An UpRev remote is up-to-date; i.e., it is loaded with an options file version and a software
version that match the versions configured at the NMS. A DownRev remote is a remote with
an options file version and/or software version that do not match the versions configured at
the NMS.
Under normal operation, the Revision Server sits in an idle state waiting for commands from
iBuilder. When commanded to perform an upgrade and/or options file application, it operates
in a specific duty cycle until its assigned tasks are complete or until it is commanded to
stop by an iBuilder user.
The Revision Servers duty cycle is shown in Figure 271 on p. 303. As the figure shows, the
Revision Server performs the following tasks for each cycle:
1. Compiles a list of DownRev remotes.
2. Creates a single package file containing the appropriate images (if upgrading) and options
files for all down-rev remotes.
3. Multicasts the package to the remotes using 10% of the downstream channel capacity.
4. Waits a calculated amount of time for the multicast to complete and for remotes to
receive the package and process it. (When a remote gets a complete package, it picks out
the images (if upgrading) and its own options file, writes the file(s) to flash, and resets.)
5. Returns to step 1. When the list of down-rev remotes reaches zero, the revision server
returns to the inactive state.

302

iBuilder User Guide

iDX Release 2.0

Downloading Remotes Using Revision Server

Figure 271. Revision Server Duty Cycle

iBuilder User Guide

iDX Release 2.0

303

Downloading Remotes Using Revision Server

11.5.2 When to Use the Revision Server

The Revision Server is useful both during network upgrades (when remotes require new image
packages) and during normal operations when applying configuration changes to your
network.
There are two ways you can use the Revision Server to automate remote upgrades:
1. Follow the manual upgrade procedure for all of your iDirect equipment, including
remotes. Then launch the Revision Server to upgrade any sites that were unreachable at
the time of the initial upgrade.
2. Upgrade your hub equipment, including line cards and protocol processors, manually.
Then launch the Revision Server to upgrade all remote sites.
When you make changes to your remotes configuration parameters, you can use the Revision
Server to automatically apply those changes by sending the updated options files to the
remotes as they become available in the network.
Note:

The Revision Server will upgrade or downgrade your remotes to the iDirect
version that is currently running on your NMS Server. Therefore you should
upgrade the NMS servers, followed by your Protocol Processors, before starting
a Revision Server upgrade.

Note:

You can use the Revision Server to upgrade to the new release provided you are
upgrading from iDS Release 5.05 or later.

11.5.3 Starting the Revision Server

To start the Revision Server, follow these steps:
1. Right-click your network in the Tree and select Package Download Revision Server
from the menu.

304

iBuilder User Guide

iDX Release 2.0

Downloading Remotes Using Revision Server

The Revision Server dialog box appears (Figure 272), including a list of all the remotes in
the network. Remotes with a status of DownRev have a different package version from
that of the NMS server. UpRev remotes are current.

Figure 272. Revision Server Dialog Box

2. In the Remotes section of the dialog box, select all remotes you want to upgrade by
clicking the check boxes. You can also click any of the following buttons to select remotes
for download:
The Select All button selects all remotes in the network.

The Select Down Rev button selects only remotes with a status of DownRev.

The Select Active button selects only remotes that are currently acquired into the
network.

The Changes Pending button selects all remotes with remote-side configuration
changes that have not yet been applied.

The Clear All button clears the check boxes for all remotes in the network.

iBuilder User Guide

iDX Release 2.0

305

Downloading Remotes Using Revision Server

3. You can change the Download Rate specified in the Download Parameters section if
desired. By default, the download rate is calculated to be 10 percent of the downstream
information rate.
4. Select Options Files Only if you only want to send options files to the remotes. No image
files will be sent.
Note:

The status of UpRev or DownRev is determined solely by the version string of

the image package. Therefore, remotes with an up-to-date package for which
the remote-side options files have not been applied will have a status of UpRev.

5. Click Start Upgrade to begin the upgrade process.

6. Once you have started the upgrade, you can observe the following real-time status in the
Revision Server dialog box:
The Next Cycle counter will begin to count down, indicating the time remaining
before the Revision Server will restart the upgrade process for any remotes that are
not updated during this cycle.

In the Remotes section of the dialog box, the status will change from DownRev to
UpRev when a remote has successfully received its upgrade.

Status messages will be displayed in the Messages section of the dialog box, logging
the progress of the upgrade.

Real-time events are displayed in the event pane at the bottom of the dialog box.

11.5.4 Controlling the Revision Server Real-Time Event Display

By default, all real-time events for up to five hundred remotes are displayed in the event
pane at the bottom of the Revision Server dialog box. If more than five hundred remotes are
being upgraded, only events for the first five hundred remotes are displayed.
This default behavior has two drawbacks during downloads of large networks:

The large number of events may make it difficult for you to monitor them on the display.

You can only see events for the first five hundred remotes.

To address these limitations, the Revision Server GUI allows you to change the Realtime
Display settings for the remotes being downloaded. By doing this, you can configure the set of
remotes for which events are displayed in the event pane. You can access these settings by
selecting remotes in the Remotes area of the dialog box and then choosing the option you
want from the Realtime Display menu.

Figure 273. Revision Server Realtime Display Menu

The Realtime Display options that you can select are shown in Figure 273. They include:

306

Start Highlighted: Starts the event display for the highlighted remotes

iBuilder User Guide

iDX Release 2.0

Downloading Remotes Using Revision Server

Stop Highlighted: Stops the event display for the highlighted remotes

Start All: Starts the event display for all remotes

Stop All: Stops the event display for all remotes

Clear RT Display: Clears all events from the event pane at the bottom of the Revision
Server display

The following example shows how to stop viewing events from all remotes and begin viewing
events only from selected remotes. The procedure assumes you have selected all remotes for
download and are currently receiving events for all remotes.
1. Right-click in the Remotes area of the Revision Server dialog box and select Stop All from
the menu to stop events from all remotes.

Figure 274. Revision Server: Stop All

2. Highlight the remotes for which you want to view events. (Use Shift + click to highlight a
range of remotes. Use Ctrl + click to select multiple, individual remotes.)
3. Right-click any of the highlighted remotes in the Remotes area of the Revision Server
dialog box and select Start Highlighted from the menu.

Figure 275. Revision Server: Start Highlighted

iBuilder User Guide

iDX Release 2.0

307

Downloading Remotes Using Revision Server

Only events from the highlighted remotes are added to the event pane at the bottom of the
Revision Server dialog box.

Figure 276. Revision Server Event Pane with Highlighted Remotes

4. To begin viewing events from all remotes again, right-click in the Remotes area of the
Revision Server dialog box and select Start All from the menu.
As an alternative to Stop All followed by Start Highlighted, you can select all remotes you do
not want to monitor. Again, assuming you have selected all remotes for download and are
currently receiving events for all remotes:
1. Highlight the remotes for which you do not want to view events.
2. Right-click any of the highlighted remotes in the Remotes area of the Revision Server
dialog box and select Stop Highlighted from the menu.

Figure 277. Revision Server: Stop Highlighted

Events from the selected remotes are no longer added to the event pane at the bottom of the
Revision Server dialog box.

308

iBuilder User Guide

iDX Release 2.0

Downloading Remotes Using Revision Server

11.5.5 Monitoring Upgrades Using the Revision Server Status

Pane
The Revision Server Status pane displays the status of all current upgrades, as well as the
status of completed upgrades. To display the Revision Server Status pane, follow these steps:
1. Select Revserver Status from the View menu.

Figure 278. Selecting Revision Server Status from the View Menu
The Revision Server Status pane will appear in place of the Network Tree, showing the
status of all upgrades that are in progress. Note that two tabs appear at the bottom of the
pane allowing you toggle between the Network Tree (iBuilder Tree View tab) and the
Revision Server Status pane (Revision Server tab) as shown in Figure 279.

iBuilder User Guide

iDX Release 2.0

309

Downloading Remotes Using Revision Server

Figure 279. Revision Server Status Pane

2. If you want to see the status of completed upgrades as well as current upgrades, select
Show historical information.

310

iBuilder User Guide

iDX Release 2.0

Downloading Remotes Using Revision Server

3. Click Details for any upgrade to see more information about that upgrade. This includes
the upgrade Status of each remote in the upgrade list.

Figure 280. Revision Server Details Display

11.5.6 Cancelling an Upgrade

You can cancel a Revision Server upgrade at any time as follows:
1. Right-click your network in the Tree and select Package Download Revision Server to
launch the Revision Server dialog box.
2. Click the Stop Upgrade button to cancel the upgrade.

iBuilder User Guide

iDX Release 2.0

311

Downloading Remotes Using Revision Server

312

iBuilder User Guide

iDX Release 2.0

Before You Begin

12 Commissioning a Line
Card, Private Hub or
Mini Hub

This section provides instructions for commissioning iDirect line cards, private hubs, and mini
hubs to transmit SCPC outroutes. It discusses the following topics:

Powering on the equipment

Determining the IP address

Downloading the initial image package and options file

Performing the 1 dB compression test when necessary

Setting the transmit power for the SCPC carrier

Setting UPC parameters for mesh outroutes

In addition, the steps are provided for setting the clear sky C/N parameter for a mesh inroute.
This procedure must be performed at the hub during commissioning of the first mesh remote
that will transmit on each inroute.
Note:

Unless otherwise indicated, the term line card as used here refers to iDirect
Private and Mini Satellite Hubs as well as iDirect Line Cards.

12.1 Before You Begin

Before you execute this procedure, the following tasks should have already been performed
at the hub:

The physical teleport installation must be complete.

The hub antenna should have been pointed and cross polarization test performed.

The NMS client and server software should be running.

Using iBuilder, you should have already:

iBuilder User Guide

iDX Release 2.0

313

Add the Line Card in iBuilder and Retrieve the Configuration

Defined your hub equipment, satellite transponder bandwidth, and the upstream
carrier to be transmitted by this line card. (See Defining Hub RFT Components and
the Satellite on page65)

Added your hub components to the iBuilder Network Tree. (See Defining Network
Components on page83)

Added your network to the iBuilder Network Tree. (See Defining Networks, Line
Cards, and Inroute Groups on page101)

Note:

If you are adding a new line card, the Tx Out, Rx In and Lan A ports should not
be connected at this time. Do not connect these cables until instructed to do so
by this procedure.

12.2 Add the Line Card in iBuilder and Retrieve the

Configuration
Use iBuilder to add the line card to the Network Tree and configure the line card parameters
in the options file.
1. In iBuilder, right-click your network in the Tree and follow the procedure in Adding a
Transmit or Transmit and Receive Line Card on page104 to configure the line card.
2. Right-click your network in the Network Tree and select Apply Network Configuration
from the menu.
Note:

Do not apply the line card configuration at this time.

3. Right-click the line card in the Tree and select Retrieve Saved Configuration.

4. In the Save As dialog box, navigate to the folder on your PC in which you want to save
the options file. Then click the Save button to save the file to your PC.
5. After you save the options file, it will be displayed in Notepad as a text file. If desired,
review the configuration in Notepad; then close the Notepad window.

314

iBuilder User Guide

iDX Release 2.0

Power on the Line Card

12.3 Power on the Line Card

Follow these steps to power on the line card or private hub.
1. If you are commissioning a private or mini hub, plug in the AC power cord.
2. If you are commissioning a line card:
a. Insert the line card into the slot in the chassis you plan to use.
b. In iBuilder, right-click the chassis in the Network Tree and select Modify Item. The
Chassis dialog box will appear.

Figure 281. Chassis Dialog Box

c. Select the check box for the slot that contains the new line card. This will toggle the
setting from Off to On.
3. Wait two minutes.
4. Right-click the Chassis in the iBuilder tree and select Apply Configuration to power on
the slot

12.4 Determine the IP Address

Follow these steps to determine the IP Address and subnet mask of your line card.
Note:

The default IP Address of iNFINITI line cards is 192.168.0.1, with a subnet mask
of 255.255.255.0. If you already know the IP address, you can skip this section.

1. Connect a console cable from the COM1 port on your client PC to the console port on the
line card.
2. Using a terminal emulator program such as Tera Terminal or HyperTerminal, connect to
the line card with the following settings:
9600 bps

8 bits

No parity

1 stop bit

iBuilder User Guide

iDX Release 2.0

315

Determine the IP Address

This is illustrated in Figure 282 using Tera Terminal.

Figure 282. Tera Terminal Serial Port Setup Dialog Box

3. Log on as:
Username: root
Password: <password>
Either iDirect or P@55w0rd! is the default password for the root account.
4. At the Linux prompt, type
telnet 0
The Telnet login screen will appear.
5. Log in to the Telnet session as:
Username: admin
Password: <password>
Either iDirect or P@55w0rd! is the default password for the admin account.
6. At the Telnet prompt, type the following command to determine the IP Address and
subnet mask of the line card:
laninfo

316

iBuilder User Guide

iDX Release 2.0

Download the Image Packages and Options File

The output of the laninfo command is shown in Figure 283.

Figure 283. laninfo Command Output

7. Note the IP address and subnet mask. You will need this information when downloading
the image packages and options file.

12.5 Download the Image Packages and Options File

When installing a new line card or private hub, you can use iSite to download the image
packages containing the software and firmware before establishing connectivity with the
NMS. (For information on downloading images from iBuilder, see Upgrading Software and
Firmware on page295.)
These steps assume that you are still connected to the console port of the line card and that
you have not yet connected your line card to the LAN.
1. Configure the IP address and subnet mask on your PC to be an IP address in the same
subnet as the IP address of the line card.
Note:

The default IP Address of iNFINITI and Evolution line cards is 192.168.0.1, with
a subnet mask of 255.255.255.0.

2. Connect a cross-over Ethernet cable between the LAN port of the line card and your PC or
laptop.

iBuilder User Guide

iDX Release 2.0

317

Download the Image Packages and Options File

3. Launch iSite. The main iSite screen will appear.

Figure 284. iSite Main Screen

4. Right-click the globe in the Network Tree and select New. An Unknown element appears
in the Tree.

Figure 285. Creating a New Element in the iSite Tree

318

iBuilder User Guide

iDX Release 2.0

Download the Image Packages and Options File

5. Right-click the new element and select Login to display the Login dialog box.

Figure 286. iSite Login Dialog Box

6. Enter the IP Address of the line card and a password. (iDirect is the default password.)
7. Select Admin in the Login as section and click OK. The line card will appear in the
Network Tree, replacing the unknown element.

8. In the Network Tree, right-click the line card and select Download Package to display
the Download Package dialog box.

iBuilder User Guide

iDX Release 2.0

319

Download the Image Packages and Options File

Figure 287. Download Package Dialog Box

9. In the Download Package dialog box:
a. Click the Open button to display the Open dialog box.
b. Navigate to the folder on the client PC that contains your iDirect image packages.

Figure 288. Locating the Hub Packages for Download

320

iBuilder User Guide

iDX Release 2.0

Download the Image Packages and Options File

c. Double-click the folder for your line card model (Evolution or iNFINITI) to open it.
This folder contains the packages that you need to download to your line card.

Figure 289. Evolution and iNFINITI Line Card Packages

Note: You must download all packages to your line card, beginning with the Board
Support Package (BSP), followed by the hub package(s).
Note: For Evolution line cards, the evo_d_hub package is used for DVB-S2
networks. The evo_l_hub package is used for SCPC networks. iDirect
recommends that you download both packages to your Evolution line card. If
you switch between SCPC and DVB-S2 and both packages are not present, the
line card will not function correctly.
d. Select the Linux Board Support Package (BSP).
e. Click the Open button to return to the Package Download dialog box.
f.

In the Download Package dialog box, select:

Dont check versions

Download images only

Dont reset

g. Click the Start button to download the package.

h. Repeat Step a through Step g, but this time download the hub package(s) for your line
card model rather than the BSP. For Evolution line cards download both the
evo_d_hub package (DVB-S2) and the evo_l_hub package (SCPC).
10. After you have downloaded all packages, right-click the line card in the Network Tree and
select Download Option From Disk to display the Open dialog box.
11. Navigate to the folder containing the options file that you saved from iBuilder when
executing step 4 of section 12.2 on page314. Then select the options file.
12. Click the Open button.
13. Click Yes to download the options file to the line card.

iBuilder User Guide

iDX Release 2.0

321

Connect the Transmit and Receive Ports

14. Right-click the line card in the Network Tree and select Reset from the menu.
At this point the new configuration (including the new IP address of line card) will be applied
and you will lose connectivity to the line card. Do not disconnect the console cable.

12.6 Connect the Transmit and Receive Ports

Follow these steps to connect the transmit and receive ports of your line card or private /
mini hub to the network.

WARNING! Connecting the transmit port of your line card will result in the transmission
of a carrier on the satellite. This step should only be performed while on line
with the satellite provider.
If you are adding a Tx-only line card:
1. Connect the Tx coax patch cable to the line cards Tx Out port.
2. Connect the Tx coax patch cable to the corresponding Tx patch panel port above the line
card slot.
If you are adding a Tx/Rx line card or a Tx line card that is configured for mesh:
1. Connect the Tx coax patch cable to the line cards Tx Out port.
2. Connect the Tx coax patch cable to the corresponding Tx patch panel port above the line
card slot.
3. Connect the Rx coax patch cable to the line cards Rx In port.
4. Connect the Rx coax patch cable to the corresponding Rx patch panel port below the line
card slot.
If you are adding an Rx-only line card:
1. Connect the Rx coax patch cable to the line cards Rx In port.
2. Connect the Rx coax patch cable to the corresponding Rx patch panel port below the line
card slot.
If you are adding a private hub or mini hub:
1. Power off the private hub or mini hub.
2. Connect the Rx cable to the Rx In port on the back panel.
3. Connect the Tx cable to the Tx Out port on the back panel.
1. Power on the private hub or mini hub.

12.7 Perform 1 dB Compression Point Test with the

Satellite Operator
This step determines the maximum transmit power level at which line card or private hub
operates before starting to saturate the BUC. This test should not be necessary if your
teleport is using an SSPA or a BUC with more than five watts of power. However, if you are

322

iBuilder User Guide

iDX Release 2.0

Set the Transmit Power for the Outroute

using a BUC with five watts of power or less, this test should be performed to ensure that you
do not overdrive the BUC.
The 1 dB Compression Point test is performed at the direction of the satellite operator using a
CW carrier. The satellite operator should inform you of the transmit frequency for the test.
To perform the test, follow these steps:
1. If you do not have a console connection to the line card, establish one now by following
the steps in section 12.4 on page315. (Note that the IP address that you configured for
your line card should now be loaded on the line card. You may need to reconfigure the IP
address of your PC to match the new subnet.)
2. Set the transmit frequency of the line card by entering the command:
tx freq <fx>
where fx represents the L band frequency in MHz.
3. Set the initial transmit power of the line card by entering the command:
tx power <pwr>
where pwr represents the power setting in dBm. Typically you should begin with a low
value such as -25 dBm to minimize the chance of interfering with other carriers.
4. Turn on a CW signal by entering the command:
tx cw on
At this point the satellite operator should see your signal.
5. While the satellite operator is observing your CW carrier, increase the transmit power in 1
dBm increments until a 1 dBm change in power no longer results in a corresponding 1 dBm
change in signal strength as measured by the satellite operator. The last point at which
the CW changes by 1 dB is the 1 dB compression point. This is maximum Tx power.
6. Disable the CW signal by entering the command:
tx cw off

12.8 Set the Transmit Power for the Outroute

Work with the satellite operator to determine the contracted power at the satellite.
Note:

The tx pn commands in these steps are used to transmit a modulated carrier at

the configured data rate, FEC rate, and modulation. The satellite operator my
request you to transmit a CW carrier rather than a modulated carrier. In that
case, replace the tx pn commands with tx cw on and tx cw off. Note, however,
that iDirect recommends using a modulated carrier to set the transmit power.

Note:

Whenever tx pn or tx cw commands are used, you must reset the line card to
restore normal operation. Be sure to follow the instructions in the next section
to reset your line card after applying the configuration.

1. If you do not have a console connection to the line card, establish one now by following
the steps in section 12.4 on page315.
2. Configure the line card to transmit at the frequency indicated by the satellite operator by
entering the command:

iBuilder User Guide

iDX Release 2.0

323

Connect to the LAN and Apply the Line Card Configuration

tx freq <fx>
where fx represents the L band frequency in MHz.
3. Configure the line card to transmit a signal with pseudo-random data by entering the
command:
tx pn on
4. Working with the satellite operator, adjust the transmit power to achieve the contracted
power at the satellite. To change the tx power to a new value, type:
tx power <pwr>
where pwr represents the power setting in dBm.
5. Disable the PN carrier by entering the command:
tx pn off
6. Open iBuilder and select the line card in the Network Tree. Then select Modify
Assigned Downstream Carrier from the context menu.
7. In the Downstream Carrier dialog box, enter the value for Power determined in step 4.

Figure 290. Assigning the Downstream Carrier Power

Note:

For an iSCPC downstream, the transmit power is configured in the Transmit

Properties section of the iSCPC line card modify dialog box. Click the iSCPC line
card in the network tree and select ModifyItem to display that screen.

8. Exit the console window by entering the command:

exit
9. You can disconnect the console cable at this time.

12.9 Connect to the LAN and Apply the Line Card

Configuration
Connect your line card to the LAN and apply the updated configuration.
1. Connect the Ethernet to the LAN A port on the line card or private / mini hub.

324

iBuilder User Guide

iDX Release 2.0

Set the Clear Sky C/N Parameter for a Mesh Outroute

2. In iBuilder, right-click the line card in the network tree and select Apply
Configuration from the menu. Select the option to Reset your line card.

12.10 Set the Clear Sky C/N Parameter for a Mesh

Outroute
If you are configuring a mesh outroute, you must use iMonitor to determine the value of the
SCPC loopback clear sky C/N. You will then use iBuilder to configure that value for the
outroute.
Note:

You must determine the clear sky C/N value under clear sky conditions at the
hub.

WARNING! Following this procedure while the hub is in a rain fade will adversely affect
the performance of uplink power control. This can cause your remote
modems to overdrive the power on the satellite.
Follow these steps to determine and set the outroute SCPC LB Clear Sky C/N parameter in
iBuilder:
1. In iMonitor, right-click the line card in the network tree and select Line Card Stats. Then
click OK in the Select Items dialog box. (The line card should already be selected in the
Line Cards area of the dialog box.)
2. In the Hub Stats Results pane, determine the value for SCPC LB C/N [dB].

Figure 291. iMonitor Hub Stats Results Pane

3. In iBuilder, right-click the line card in the network tree and select Modify
Configuration.
4. In the Line Card dialog box, enter the value for SCPC LB Clear Sky C/N determined in
step 2.

iBuilder User Guide

iDX Release 2.0

325

Set the UPC Margin for a Mesh Outroute

Figure 292. Setting the SCPC LB Clear Sky C/N for a Mesh Outroute

12.11 Set the UPC Margin for a Mesh Outroute

Determine from the hub operator the amount of margin, in dB, that is built into the teleports
UPC system. iDirect uses this value in its power control algorithm. Once you have determined
the margin, follow these steps to enter that value into iBuilder as the Hub UPC Margin for
your mesh outroute:
1. In iBuilder, right-click the line card in the network tree and select Modify
Configuration.
2. In the Line Card dialog box, enter the Hub UPC Margin.

Figure 293. Setting the Hub UPC Margin for a Mesh Outroute

12.12 Set the C/N for an Inroute in a Mesh Inroute

Group with Existing Carriers
When you set the clear sky C/N for a mesh inroute, that inroute must be the only inroute in its
inroute group. If you are commissioning a new inroute in a mesh inroute group that already
contains one or more carriers, then you should create a temporary inroute group containing
only the new carrier and use that temporary inroute group to determine the clear sky C/N
setting. You can then use the clear sky C/N value determined in the temporary inroute group
to configure the new carrier in the your mesh inroute group.
Note:

The C/N calibration procedure should be applied to each inroute in a mesh

inroute group, regardless of whether it is a star carrier or star-mesh carrier.

If you are setting the clear sky C/N for the first inroute in a mesh inroute group, you do not to
follow the procedure in this section. Instead, follow the procedure in Set the Clear Sky C/N
Parameter for an Inroute in a Mesh Inroute Group on page328.
Follow the steps in this section to create a temporary inroute group and set the clear sky C/N
value for your new inroute. You can do this either during the commissioning of the first
remote that will use this inroute, or you can use a spare remote to determine the correct
setting.
1. If you have not done so, add the new upstream carrier to your network bandwidth in the
iBuilder tree. (See Adding Upstream TDMA Carriers on page76.)
Note:

326

The creation of additional carriers for a mesh inroute group is facilitated by

cloning the existing mesh carrier. (Right-click the existing carrier in the
iBuilder tree and select Clone Scaled Carrier). The correct symbol rate is
enforced by the NMS based on the ratio selected. Symbol rate constraints for
carriers in the same mesh inroute group are discussed on page78.

iBuilder User Guide

iDX Release 2.0

Set the C/N for an Inroute in a Mesh Inroute Group with Existing Carriers

2. Add a mesh-enabled line card to your iBuilder network and assign the new inbound carrier
to the line card. (See Adding a Transmit or Transmit and Receive Line Card on
page104.)
3. Add a temporary mesh-enabled inroute group to your iBuilder network. Click the Add
button at the bottom of the Inroute Group Information tab to add the new line
card/carrier to the temporary inroute group. (See Adding Inroute Groups on page129).
4. Add the remote you are using to determine the clear sky C/N to the temporary inroute
group. This can be a test remote, a spare remote, or a remote being commissioned for the
mesh network.
Note:

If you are using an existing remote, you can move it into the temporary inroute
group by right-clicking the remote in the iBuilder tree and selecting Move from
the menu. You must activate the remote in the new inroute group after you
move it.

5. Execute Step 1 through Step 10 in Set the Clear Sky C/N Parameter for an Inroute in a
Mesh Inroute Group on page328 to determine the clear sky C/N value for the new
inroute. Record the C/N value determined for the inroute. This will be the setting you
enter when you add the new inroute to the existing mesh inroute group.
6. In the Line Cards section of the Information tab of the temporary inroute group, select
the line card/carrier at the bottom of the dialog box and click the Remove button to
remove the carrier from the inroute group.

Figure 294. Inroute Groups Information Tab: Line Cards Section

7. In the Line Cards section of the Information tab of the existing mesh inroute group, click
the Add button. Then add the new line card/carrier to the permanent mesh inroute
group.
8. Execute Step 12 through Step 20 in Set the Clear Sky C/N Parameter for an Inroute in a
Mesh Inroute Group on page328. Set the clear sky C/N for the new inroute to the value
determined in Step 5. Be sure to delete the custom key from the remote you used to
commission the carrier.
9. Complete the commissioning procedure by setting the TDMA Nominal C/N for the new
inroute. (See Set the TDMA Nominal C/N Parameter for an Inroute on page331.)

iBuilder User Guide

iDX Release 2.0

327

Set the Clear Sky C/N Parameter for an Inroute in a Mesh Inroute Group

12.13 Set the Clear Sky C/N Parameter for an Inroute

in a Mesh Inroute Group
You must set the clear sky C/N parameter for each inroute in a mesh-enabled inroute group
before you set the initial transmit power of the first remote commissioned on the inroute. You
should configure this setting for both star-mesh and star carriers. To accurately determine the
value for clear sky C/N, you must first configure a custom key to disable uplink power control.
Once clear sky C/N is entered, you must delete the custom key to re-enable uplink power
control.
Note:

If you are adding a new carrier to a mesh inroute group that contains one or
more existing carriers, you must create a temporary inroute group to
determine the correct clear sky C/N setting. Please follow the procedure in Set
the C/N for an Inroute in a Mesh Inroute Group with Existing Carriers on
page326.

For instructions on remote commissioning, including mesh remotes, see the Installation and
Commissioning Guide for iDirect Satellite Routers.
Follow the steps in this section to correctly set the clear sky C/N for the inroute.
Note:

This procedure only applies before or during the commissioning of the first
mesh remote on a mesh inroute. It should be performed before setting the
initial transmit power of that remote in ibuilder.

1. In iBuilder, right-click the remote in the network tree and select Modify Item.
2. Select the Custom tab in the Modify Remote dialog box.
3. Configure the following custom key under Hub-side Configuration:
[REMOTE_DEFINITION]
ucp_power_disable = 1

Figure 295. Disabling Remote Uplink Power Control

4. Right-click the remote in the network tree and apply the hub-side configuration.
5. In iMonitor, right-click the remote in the network tree and select Probe from the menu.

328

iBuilder User Guide

iDX Release 2.0

Set the Clear Sky C/N Parameter for an Inroute in a Mesh Inroute Group

6. In the Remote Power area of the screen, click the Change button.

Figure 296. Remote Probe: Changing the Remote Tx Power

7. Working with the satellite operator, adjust the transmit power of the remote until the
contracted Tx Power on the satellite is reached for the TDMA carrier. Adjust the power by
entering a power setting in New Tx Power and clicking the Set button.

Figure 297. Change Remote Tx Power Dialog Box

8. In iMonitor, right-click the mesh remote in the network tree and select Control Panel
from the menu.
9. Select the UCP Info tab.

iBuilder User Guide

iDX Release 2.0

329

Set the Clear Sky C/N Parameter for an Inroute in a Mesh Inroute Group

10. Record the average value displayed in the column Up C/N [db].

Figure 298. Determining the Clear Sky C/N for a Mesh Inroute
11. If you are determining the C/N value in a temporary inroute group, return to Step 6 on
page327.
12. In iBuilder, right-click the inroute group in the network tree and select Modify Item
from the menu.
13. Select the Acquisition/Uplink Control tab.
14. At the bottom of the dialog box, select the Line Card that receives the mesh inroute.

330

iBuilder User Guide

iDX Release 2.0

Set the TDMA Nominal C/N Parameter for an Inroute

15. In TDMA Clear Sky C/N, enter the value recorded for Up C/N [dB] from iMonitor.

Figure 299. Setting the Clear Sky C/N for a Mesh Inroute
16. Click OK to save changes. Then apply the configuration to the line card.
17. In iBuilder, right-click the remote in the network tree and select Modify Item.
18. Select the Custom tab in the Modify Remote dialog box.
19. Delete the following custom key:
[REMOTE_DEFINITION]
ucp_power_disable = 1
20. Right-click the remote in the network tree and apply the hub-side configuration by
selecting Apply Configuration Reliable Hub-Side (TCP) from the menu.

12.14 Set the TDMA Nominal C/N Parameter for an

Inroute
Whenever you add an inroute, you should set the TDMA Nominal C/N parameter on the
Acquisition/Uplink Control tab for that inroute according to the TDMA carrier modulation
type. The value for TDMA Nominal C/N is determined based on the link budget analysis for
your network, which takes into consideration the modulation and FEC rate of the carrier.
For details on setting this parameter in iBuilder, see Adding an Inroute Group on page131.

iBuilder User Guide

iDX Release 2.0

331

Set the TDMA Nominal C/N Parameter for an Inroute

332

iBuilder User Guide

iDX Release 2.0

Conversion of User Accounts During Upgrade Procedure

13 Managing User Accounts

and User Groups

Prior to iDS Release 7.0, all user accounts were independent of one another. Beginning with
Release 7.0, all users belong to one of a variable number of User Groups. Visibility of network
elements and access rights to those elements are now defined at the user group level rather
than for each user account. This chapter explains how to create and manage user groups and
user accounts, and how to define the permissions and access rights associated with each. It
discusses the following topics:

Conversion of User Accounts During Upgrade Procedure on page333

NMS User Groups on page334

Adding and Managing User Accounts on page355

Changing Passwords on page360

User Privileges on page361

NMS Database Locking on page363

13.1 Conversion of User Accounts During Upgrade

Procedure
If you are upgrading from a pre-7.0 release, the database conversion process, which runs
automatically when you upgrade your NMS server, performs the following actions on existing
user accounts:

All non-VNO accounts are put into the System group automatically.

For each VNO account, the upgrade creates a new user group and adds the user account
to it.

Account permissions are maintained, but all VNO visibility settings are turned off. You
must use iBuilder to re-establish appropriate visibility for each user group.

WARNING! As soon as possible after you upgrade from a pre-7.0 release, you must redefine the visibility settings for each VNO user group. VNO users will be
unable to use the system until you have done this.

iBuilder User Guide

iDX Release 2.0

333

NMS User Groups

13.2 NMS User Groups

There are three types of NMS User Groups:

The System User Group

VNO (Virtual Network Operator) User Groups

CNO (Customer Network Observer) User Groups

The System User Group provides specific permissions and access rights above all other groups.
Members of the system group are the Host Network Operators (HNOs), system administrators,
NOC managers, and other super users of the system.
All database items are visible to users in the system group, including all network elements
created by VNO users. Individual permissions of system users may vary from account to
account.
VNO users may create and manage their own QoS profiles, filter profiles, antenna
components, or any other network components, subject to permissions established at the
group level by the HNO.
VNO User Groups restrict visibility and access rights of group members based on the
permissions granted to the group. Creating and managing VNO User Groups is discussed in
detail later in this chapter.
CNO User Groups can be created to allow customers to monitor groups of network elements
without the ability to add new elements or modify the network in any way. CNO users are
restricted to iMonitor read-only access to the network elements that are visible to their CNO
User Group. They cannot log into iBuilder.
Note:

VNO and CNO User Groups are licensed features. If you plan to define VNO or
CNO User Groups in your network, please contact your iDirect Account Manager.

Note:

The term HNO Administrator is used in the following sections to refer to a

System Group User with permissions to create and modify VNO User Groups.

13.2.1 Visibility and Access for VNO User Groups

iBuilder distinguishes between network elements (such as inroute groups and remotes) and
component folders (such as QoS and Filter folders) when applying rules for visibility and
access within a VNO User Group. Each is discussed separately in the following sections.

Visibility and Access for Network Elements

When setting network element visibility and access rights for VNO groups, it is important to
keep the following principles in mind:

334

Visibility propagates up the tree, but not down the tree. For example if you make a
remote Visible to a User Group, members of the group will see that remotes parentage
all the way to the up to the teleport element. However, if you set visibility at the teleport
level, group members will see only the teleport when they log in; they will not see any
elements underneath it.

Visibility has three different levels of access rights. When you give visibility of an
element to a User Group, for example an inroute group, you have the following additional
access rights you can grant or revoke:

iBuilder User Guide

iDX Release 2.0

NMS User Groups

Create access allows users to create new elements underneath this node. For
example, you can allow a user to create new remotes in an inroute group.

Write access allows users to modify the contents of the element itself. For example,
a user with Write access to an inroute group could modify the inroute group to turn
off frequency hopping.

Control access gives users the right to perform control operations on child elements
of the specified node. For example, users with Control access for an inroute group can
perform all control operations on remotes in that inroute group.

Ownership is different from Visibility. When you set a node as Owned by a VNO group,
you are dedicating that node and all of its children to this VNO group exclusively (except
for system users, of course). No other VNO groups are able to see or interact with this
group in any way. Visibility to network elements, however, can be shared across multiple
VNOs.

VNOs cannot see each other; System users see all. When a VNO creates a network
element, only the members of that group and the System User Group are able to see the
element. When the system group creates or owns a network element, no VNOs can see
this element unless they are granted visibility to it.

User Groups are highly configurable. The implementation of VNO User Groups is quite
flexible; you can configure groups in a number of ways. However, unless you are careful
when configuring your user groups, this flexibility can result in unwanted results. It is
possible to give VNO User Groups various combinations of write and visibility access that
may create confusion in practice.
For example, giving a VNO Write access to an inroute group, without granting Control
access at the Network level, could result in a condition from which the VNO user is unable
to recover. In this example, a VNO user could modify the inroute group so that it sets the
Network to the Changes Pending state, yet be unable to apply the changes.

Visibility and Access for Components Folders

Visibility and access rights are handled differently for components folders than they are for
elements of the Network Tree. The following options exist when setting up VNO group
visibility and access to components folders in the Tree:

Users see the contents of folders. In general, users in a VNO group can see the contents
of all component folders. However, they cannot change them or add new components.

Users can add elements to some folders. VNO users can add Remote Antenna
Components, Operators, Distributors and Customers. Folder elements added by a VNO
user are owned by the VNO.

QoS Profile folders are special. By default, VNO users cannot add or modify QoS filters
or QoS profiles. However, selecting the Create property on a QoS profile folder allows the
customer to create new entries in that folder.

The rules for QoS visibility and control are:

All VNO users see profiles created in the System User Group.

Profiles created by VNO members are visible only to members of that VNO User Group and
the System User Group.

iBuilder User Guide

iDX Release 2.0

335

NMS User Groups

13.2.2 Visibility and Access for CNO User Groups

CNO User Groups have the following characteristics:

CNO users can log in to iMonitor only. They cannot log in to iBuilder.

Within iMonitor, CNO users can view all network elements that have been made Visible to
their CNO User Group. The rules of visibility propagation in the network tree that apply to
VNOs also apply to CNOs. (See Visibility and Access for Network Elements on page334).

CNO users have no access rights other than the ability to view visible elements.
Specifically, Create, Write and Control access cannot be granted to CNO users.

CNO users cannot execute iMonitor Probe functions that modify or control remote
modems. However, they can use all Probe read-only functions.

CNO users cannot select the Connect command from the iMonitor GUI.

13.2.3 Creating and Managing VNO and CNO User Groups

You can manage User Groups and their users from iBuilders Network Tree View. When you add
or modify a User Group, the Group dialog box is displayed (Figure 300).

Figure 300. Group Dialog Box

336

iBuilder User Guide

iDX Release 2.0

NMS User Groups

The Information tab contains a Full View of the network tree in the left pane and the User
Group View in the right pane. Notice that the visibility and ownership properties of the Tree
elements in the User Group View are color coded according to the key at the bottom of the
window.

Adding or Modifying a VNO or CNO User Group

To add or modify a new User Group:
1. To add a User Group, right-click the User Group folder in the Tree and select either Add
VNO User Group or Add CNO User Group. To modify an existing User Group, right-click
the User Groups name in the Tree and select Modify. Both alternatives are shown below.

2. In the Group dialog box, enter a Group Name for the User Group. If desired, you can also
change the Group Type and add a Description of the group.

Figure 301. Group Dialog Box: Modifying a User Group

3. On the Information tab of the dialog box, right-click on elements in the Full View to set
their visibility and permissions for the User Group.
The menu displays a check mark next to all access rights selected for this element. The
User Group View shows you which elements this groups users will have access to, and
what their access rights will be. Figure 302, Figure 303, and Figure 304 show examples of
VNO User groups with various settings.

iBuilder User Guide

iDX Release 2.0

337

NMS User Groups

Figure 302. Setting a VNO Element to Visible with Create Permission

Figure 303. Setting a VNO Element to Visible Only

338

iBuilder User Guide

iDX Release 2.0

NMS User Groups

Figure 304. Setting a VNO Element to Owned

Note:

If you are configuring a CNO User Group, you can only select Visible from the
context menu. Other permissions in the list apply to VNO User Groups only.

13.2.4 Setting Global Rate Limits for User Groups

You can use the Properties tab of the Group dialog box to limit the maximum upstream and
downstream information rates for a User Group. When either or both of these fields is greater
than zero, a rate limit above the specified value cannot be configured for any remote under
the groups control.
1. In the Group dialog box, select the Properties tab.

Figure 305. Setting Rate Limits for User Groups

2. To limit the downstream information rate, select the MaxDownstreamKbps check box and
enter the rate limit in kbps.

iBuilder User Guide

iDX Release 2.0

339

NMS User Groups

3. To limit the upstream information rate, select the MaxUpstreamKbps check box and
enter the rate limit in kbps.
In Figure 305, remotes created or controlled by members of the User Group are restricted to a
maximum of 256 kbps on the downstream and a maximum of 32 kbps on the upstream.

13.2.5 Modifying per Node VNO Properties

In addition to changing a VNO User Groups properties directly, you can also modify multiple
VNO access rights for a particular element in the Network Tree. To view or change all VNO
properties for an Inroute Group, for example:
1. Right-click the inroute group and select ModifyVNO.

2. To make the element visible to a VNO, select the check box next to the VNO name. (You
can also do this by selecting from the context menu as described in the next step.)

Figure 306. Making an Element Visible to a VNO

In Figure 306, the inroute group is visible to three different VNO groups. VNO1 and VNO3
can only view the Inroute Group. VNO2 can perform control operations such as applying
configuration changes.

340

iBuilder User Guide

iDX Release 2.0

NMS User Groups

3. To modify a VNOs permissions for the selected element, right-click on the VNO name and
select the desired permissions from the menu.

Figure 307. Setting Element Permissions for a VNO

13.2.6 Changes Made by an HNO During a VNO Session

If a VNO user is already logged on to iBuilder when an HNO administrator changes permissions
for the VNO User Group, a pop-up window is displayed to the VNO user with the following
message:

Clicking OK causes iBuilder to log out and then log back on to the VNO user session,
committing the configuration changes executed from the HNOs administrative session.

iBuilder User Guide

iDX Release 2.0

341

NMS User Groups

13.2.7 Sharing a Chassis Among Multiple VNO User Groups

Beginning with iDX Release 2.0, an HNO can assign VNOs access rights or ownership for
individual slots in a 20-slot or a four-slot chassis. This allows an HNO to share a single chassis
among multiple VNOs. It allows the VNOs to perform configuration and control operations on
some chassis slots while disallowing access to other slots.
Figure 308 shows two possible configurations of a chassis in the Full View of the Modify VNO
configuration screen. On the left, the first eight slots of a 20 slot chassis have been divided
between VNO 1 and VNO 2. VNO 1 owns slots 1 through 4. VNO 2 owns slots 5 through 8. On
the right, VNO 1 has been granted visibility to slots 1, 2 and 3 in a four-slot chassis, but no
visibility to slots 4 and 5.

Figure 308. VNO Full View: Owned Slots vs. Visible Slots
If a VNO has write access to a chassis, then a VNO operator can modify the chassis. The
operations that each VNO can perform on the chassis slots depend on the VNOs access rights
to those slots.

If the VNO owns a chassis slot, a VNO operator can power on and off the slot and assign a
line card to the slot.

If the VNO owns all slots in two adjacent timing groups, a VNO operator can enable the
jumper between the timing groups. (This is subject to additional backplane checks.)
Ownership of all slots in both timing groups is required to set these jumpers.

If the VNO has both write access and control access to a chassis slot, a VNO operator can
assign line cards to the slot and power on or off the slot.

If the VNO has only write access to a chassis slot, a VNO operator can assign line cards to
the slot. However the VNO operator cannot power on or off the slot.

If the VNO has only control access to a chassis slot, a VNO operator can power on or off
the slot. However the VNO operator cannot assign line cards to slot.

Note:

A VNO must own a network and its line cards in order to manage line card
redundancy.

If two VNOs have write access to the same chassis, VNO users in both VNO user groups can
modify the chassis in iBuilder. However, on the chassis modify screen, each VNO sees only the
slot assignments of its own line cards or to line cards set to Visible for the VNO. A VNO
operator cannot see the line card assignments for line cards owned by another VNO.

342

iBuilder User Guide

iDX Release 2.0

NMS User Groups

Figure 309 shows two versions of the same Chassis Modify screen.

Figure 309. HNO and VNO Views of Chassis Modify Screen

iBuilder User Guide

iDX Release 2.0

343

NMS User Groups

In Figure 309, VNO 1 owns the line cards in slots 1 and 2 and VNO 2 owns the line cards in slots
9 and 10. The top image in Figure 309 shows what the HNO sees when right-clicking the
chassis in the iBuilder Tree and selecting ModifyItem. Both VNO 1s line cards and VNO 2s
line cards are displayed to the HNO.
The bottom image in Figure 309 shows the same screen when a VNO 1 user is logged on to
iBuilder. Notice that VNO 1 cannot see the slot assignments for slots 9 and 10, since those line
cards are owned by VNO 2.
If a VNO owns a chassis slot, then iBuilder does not allow any other VNO to assign line cards to
that slot. Therefore, no conflicts can arise. However, if two VNOs have write access to the
same slot, the slot may be occupied by a line card owned by one VNO that cannot be seen by
the second VNO. In that case, if the second VNO attempts to assign a line card to the occupied
slot, iBuilder does not allow the assignment and displays an error message. Figure 310 show
the result when a VNO attempts to assign slot 1 when the slot is already occupied.

Figure 310. Chassis Modify: Attempting to Assign an Occupied Slot

Configuring VNO Access Rights for a Shared Chassis

The following procedure illustrates how an HNO might configure a chassis to be shared by two
VNOs. In this example, the HNO grants each VNO write and control access to the chassis and
control access to specific slots within the chassis. This allows each VNO to perform
redundancy operations on their own line cards and to power on and off the slots containing
their line cards. Since the HNO does not grant the VNOs write access to the timing groups, the
VNOs cannot change their slot assignments.
For details on configuring a chassis see Configuring a Hub Chassis on page249. For details
on line card redundancy management see Managing Line Card Redundancy Relationships on
page120.
Note:

344

This example assumes that the VNOs have been granted ownership of their
respective networks and line cards. The VNOs must own these elements to
manage their line card redundancy.

iBuilder User Guide

iDX Release 2.0

NMS User Groups

1. Log on to iBuilder as an HNO administrator.

2. Under the User Groups folder in the iBuilder Tree, right-click the first VNO user group and
select Modify.

3. In the Full View section of the Modify Configuration screen for the VNO, expand the tree
to expose the chassis you want the VNOs to share.
4. Right-click the chassis and grant Visibility and Write and Control access to the VNO.

Figure 311. Granting Chassis Rights to a VNO

Note:

Control access allows the VNO to apply configuration changes to the chassis.
For example, if the VNO enables or disables the power to a slot, the VNO can
then download the changes to the chassis.

5. Expand the chassis in the Full View to display the chassis slots.

Figure 312. Expanded Chassis in VNO Tree

iBuilder User Guide

iDX Release 2.0

345

NMS User Groups

6. Right-click each Slot that you want the VNO to use and grant Visibility and Control to the
VNO.

Figure 313. Granting Control of Chassis Slots to a VNO

7. Click OK to save the changes.
8. Repeat these steps for the other VNO, granting chassis and slot access as desired.
Once the VNOs are configured according to this example, a VNO user can right-click the
shared chassis in the iBuilder Tree and select Modify. On the Chassis Modify screen:

The VNO user can toggle on and off the power for line cards owned by the VNO, since
Control access has been granted for the slots. (See Figure 313.)

The VNO user cannot change the slot assignments for line cards owned by the VNO, since
Write access has not been granted for the timing groups.

The VNO user cannot view or modify the slot assignments for line cards owned by other
VNOs.

Because the VNOs in the example have ownership of their networks and line cards, a VNO user
can establish line card redundancy relationships and swap active and standby line cards, but
only for those line cards owned by the VNO. Figure 314 shows the Manage Line Card
Redundancy screen when logged on as VNO 1. VNO 2s line cards are not displayed to the VNO
1 user.

Figure 314. VNO View of Manage Line Card Redundancy Screen

Note:

346

If you are sharing a chassis among multiple Network Management Systems,

please see Sharing a 20 Slot Chassis in a Multi-NMS System on page260.

iBuilder User Guide

iDX Release 2.0

NMS User Groups

13.2.8 Modifying Group QoS Settings for VNO User Groups

Host Network Operators (HNOs) can selectively turn on or off different levels of Group QoS
(GQoS) configuration privileges for Virtual Network Operators (VNOs). Under a network or
inroute group, an HNO can set VNO permissions for the Bandwidth Pool, Bandwidth Groups
and Service Groups. An HNO can assign ownership or visibility to a VNO User Group for these
GQoS nodes. However, visible GQoS nodes cannot be assigned Create, Write or Control access.

Restricting VNO Access to GQoS Tab Only

If a VNO owns a GQoS node, the VNO can modify that node from the Group QoS tab of the
network or inroute group dialog box. However, unless the VNO also has write permission or
ownership for the network or inroute group itself, the VNO cannot modify parameters on
other tabs of the network or inroute group element.
For example, Figure 315 shows a VNO configured with Visibility to VNO 1 Network but no
additional permissions for the network. The VNO owns the Bandwidth Pool for the network,
including all Bandwidth Groups and Service Groups.

Figure 315. VNO with Network Visibility and GQoS Node Ownership
Note:

Visibility is indicated by green text. Ownership is indicated by magenta text.

When ownership is assigned to a node, visibility is automatically granted to all
higher nodes in the tree necessary to reach the owned node.

As shown in Figure 316, when a VNO user right-clicks the network, the user can only select
ModifyGroup QoS but cannot select ModifyItem.

Figure 316. VNO Network Menu with Owned GQoS Nodes but No Network Access

iBuilder User Guide

iDX Release 2.0

347

NMS User Groups

When the VNO User selects ModifyGroup QoS, the network dialog box is displayed with all
tabs. However, the user can only modify owned GQoS nodes on the Group QoS tab. The VNO
user cannot change anything on the Information tab or the Custom tab.
However, if the VNO has Write access to or Ownership of the network or inroute group, then a
VNO user can change any settings on the network or inroute group as well as on its owned
GQoS nodes. For example, Figure 317 shows the VNO from Figure 315 re-configured to add
Write and Control access to the network.

Figure 317. VNO with Network Write Access and GQoS Node Ownership
Because the VNO has been granted Write access to VNO 1 Network, a VNO user can select
both ModifyGroup QoS and ModifyItem from the network menu. This is illustrated in
Figure 318.

Figure 318. VNO Network Menu with Owned GQoS Nodes and Write Access to Network
When the VNO user selects ModifyItem for the network, the user can change the
configuration on the Information and Custom tabs as well as the configuration of its owned
GQoS nodes on the Group QoS tab.

Assigning Ownership of Group QoS Nodes to a VNO

By selectively assigning ownership of GQoS nodes to a VNO, the HNO can delegate the GQoS
configuration privileges for the branches under that node to the VNO. If a VNO owns a GQoS

348

iBuilder User Guide

iDX Release 2.0

NMS User Groups

Node, then VNO users can modify the node and create new subnodes. VNO users cannot
modify any parts of the bandwidth tree which are not owned by the VNO.
For example, Figure 319 shows a VNO with Ownership of Bandwidth Group 1 (and all its
subnodes) but no ownership of or visibility to Bandwidth Group 2.

Figure 319. VNO Ownership of Partial Bandwidth Pool

When a VNO user modifies the Group QoS settings for VNO Network, the VNO user has access
to all nodes in Bandwidth Group 1 but cannot see or modify Bandwidth Group 2. This is
illustrated in Figure 320.

Figure 320. VNO View of Partially-Owned Bandwidth Pool

Notice in Figure 320 that the VNO user cannot see Bandwidth Group 2, since the VNO has not
been granted any permissions for that Bandwidth Group. However the VNO can see (and
modify) Bandwidth Group 1, since it is owned by the VNO.
Some properties of Group QoS nodes (called Request Properties) affect how the parent node
allocates bandwidth among its subnodes. When a VNO is granted ownership of a Group QoS
node, the VNO can only modify the Request Properties of the node if the VNO has the right to
modify the parent node. If the VNO could modify the Request Properties of a node without

iBuilder User Guide

iDX Release 2.0

349

NMS User Groups

having permission to modify the parent node, then the VNO could change settings such as the
MIR and CIR granted to the owned node by the parent node, potentially at the expense of
competing nodes. Therefore, the ability to change the Request Properties of a Group QoS
node is dependent on permissions set for the parent.
An example is illustrated in Figure 321.

Figure 321. Request Property Access for GQoS Nodes

On the left side of Figure 321, the VNO owns Bandwidth Group 1 but does not have ownership
of the networks Bandwidth Pool. Therefore, the VNO cannot modify the Request Properties
of Bandwidth Group 1. On the right side of Figure 321, the VNO owns Bandwidth Group 1 and
its parent node, the networks Bandwidth Pool. Therefore, the VNO can modify the Request
Properties of Bandwidth Group 1.

350

iBuilder User Guide

iDX Release 2.0

NMS User Groups

Setting VNO Permissions for Group QoS Nodes

This section describes how to assign a VNO ownership or visibility to nodes and subnodes of a
Group QoS bandwidth pool.
To assign the VNO permissions to a GQoS node such as a Bandwidth Pool, Bandwidth Group or
Service Group to a VNO:
1. In an iBuilder HNO administrative session, right-click the VNO User Group and select
Modify to open the VNO Modify dialog box (Figure 322).

Figure 322. Modify VNO Dialog Box

iBuilder User Guide

iDX Release 2.0

351

NMS User Groups

2. Expand the Full View tree to expose the node or nodes you want to assign to the VNO.
Group QoS nodes are displayed in folders under Networks and Inroute Groups. The toplevel folder for the Group QoS Nodes is always labeled Bandwidth Pool.
3. Grant the desired access by right-clicking the GQoS Node and selecting the desired
options. You can either select Owned or Visible for a GQoS node. However, if you select
Visible, you cannot select any additional access rights.
Figure 323 shows a Visible Bandwidth Group (Bandwidth Group 1). VNO users can view
the Bandwidth Group 1 settings but cannot change them. VNO users in this VNO cannot
see Bandwidth Group 2.

Figure 323. A Visible Bandwidth Group

In Figure 324, the VNO owns Service Group 2 under Bandwidth Group 1. Therefore,
Bandwidth Group 1 (and higher nodes) are automatically set to visible for the VNO. VNO
operators in this VNO cannot see Service Group 1.

Figure 324. An Owned Service Group

Note:

An HNO cannot assign Create, Write or Control access to a VNO for a Visible
Group QoS node. For a VNO user to modify or control a Group QoS node, the
VNO must own the Group QoS node.

4. Click OK to save the changes to the VNO User Group configuration.

Viewing GQoS Nodes in a VNO Session

By logging on as a VNO user, the HNO can verify that the VNO permissions have been set
correctly. Using the example from the previous section as shown in Figure 324, the VNO should

352

iBuilder User Guide

iDX Release 2.0

NMS User Groups

be able to create subnodes (such as GQoS Applications) under Service Group 2 in Bandwidth
Group 1. However, the VNO should have no visibility to Service Group 1 in Bandwidth Group
1.
Figure 325 shows the Group QoS tab for the network when logged on as a VNO user.

Figure 325. VNO View of the Group QoS Tree

Notice in Figure 325 that the VNO user can Modify Service Group 2 or Add Applications to it.
However, since the VNO does not own Bandwidth Group 1, the VNO user cannot Insert
additional Service Groups into Bandwidth Group 1 or Delete Service Group 2 from
Bandwidth Group 1. Notice also, that the VNO user cannot see Service Group 1 in Bandwidth
Group 1 (see Figure 324), since the VNO was not granted visibility to that Service Group 1.
Note:

Before VNO users can add new Applications to a Service Group, the Application
must first be created and then made Visible to the VNO User Group by the HNO
administrator. This is discussed in the next section.

Setting Application Profile Visibility

This section describes how an HNO administrator can selectively make Group QoS Application
Profiles available to VNO User Groups. Once an Application Profile is visible to a VNO, the VNO
can add the Application to its Service Groups.
Note:

iBuilder User Guide

iDX Release 2.0

See Adding an Application Profile or iSCPC Profile on page238 for details on

creating GQoS Application Profiles.

353

NMS User Groups

To make an Application Profile visible to a VNO User Group:

1. From an HNO administrative session, right-click the Application Profile and select
Modify>VNO to view the Resource VNO Property screen (Figure 326).

Figure 326. Setting VNO Visibility for an GQoS Application Profile

2. In the Visible to VNO Group area, Select the VNO User Groups you want to be able to
access the profile.
3. Click OK to assign visibility for this Application Profile to the VNO. Only selected VNOs can
see and assign the profile.

354

iBuilder User Guide

iDX Release 2.0

Adding and Managing User Accounts

13.3 Adding and Managing User Accounts

You can create and manage User Accounts from iBuilders Network tree. Depending on your
permission level within the NMS, you can perform the following actions:

Add new user

Clone an existing user and change the name and some of the properties

Delete a user

Modify a users account

View a users current properties

The next few sections explain these operations in detail.

13.3.1 Adding a User and Defining User Privileges

To add a new user to a User Group, follow the procedure below.
1. Right-click the User Group in the Network Tree and select Add User.

2. When you select Add User, the User dialog box appears.

Figure 327. User Dialog Box: Adding a User

iBuilder User Guide

iDX Release 2.0

355

Adding and Managing User Accounts

3. Enter a user name and click Change Password.

Figure 328. Change Password Dialog Box

4. Enter and confirm a password for this user.
5. If you click either the Super User or Guest check box, the permissions allowed for the
user level you selected appear with check marks next to them on the User dialog box, but
they are not selectable. These permissions may vary in accordance with the type of User
Group.
6. If you clear both of the main User Level boxes (Super User and Guest), the individual
permissions detailed in Table 9, Custom Privileges on page 362 become selectable. Click
the boxes next to the customized functions that you want to assign to the user.
7. Click OK to save the settings for the user account. The new user will appear in the
Network Tree under the User Group you selected.

13.3.2 Modifying a User

To modify a user account:
1. Right-click the User Name in the Network Tree and select Modify Item.

2. When the User dialog box appears, change the settings as desired. (For details, see
Adding a User and Defining User Privileges on page355.)
3. Click OK to save the changes.

356

iBuilder User Guide

iDX Release 2.0

Adding and Managing User Accounts

13.3.3 Adding a User by Cloning a Users Account

To clone a user in the same User Group:
1. Right-click the User Name in the Network Tree and select Clone.

2. A new user appears in the Tree and the User dialog box is displayed with settings identical
to the cloned user.

Figure 329. User Dialog Box: Cloning a User

3. Modify the Name and Password.
4. If desired, change the permissions.
5. Click OK to save the changes.
For a detailed description of user permissions, see User Privileges on page361.

iBuilder User Guide

iDX Release 2.0

357

Adding and Managing User Accounts

13.3.4 Viewing a Users Account Properties

To view a users account properties:
1. Right-click the User Name in the Network Tree.
2. Select View Properties Item.

3. View the properties of the user account.

4. Click the Close button at the top of the dialog box to exit the pane.

13.3.5 Deleting an Existing Users Account

To delete a user from a User Group:
1. Right-click the User Name in the Network Tree and select Delete.

2. Click Yes to confirm the deletion.

13.3.6 Managing Accounts from the Active Users Pane

In addition to managing users accounts from the Network Tree, you can perform some of the
same operations from the Active Users pane. In addition, the Active Users pane allows you to
view the list of operators currently logged on to iBuilder and iMonitor.
The Active Users pane is a standard Microsoft Windows dockable display that you can
attach to any part of iBuilders main window; detach into its own window; or hide altogether.
When you first open the pane, it will appear on the right side of the NMS window. The last
setting you select is saved between iBuilder sessions.
The Active Users pane(Figure 330) has four columns. The columns display the Name,
Permissions, Group (User Group) and Logged On status for all users defined in the system.

358

iBuilder User Guide

iDX Release 2.0

Adding and Managing User Accounts

The Logged On column indicates the logon session count for that user under both iBuilder and
iMonitor. This pane is updated in real time as values change.

Figure 330. Active Users Pane

To open the Active Users pane, Select View View Active Users from the main menu.

Figure 331. Opening the Active Users Pane from the View Menu
Depending on your permission level within the NMS, you can perform the following actions:

Delete a user

Modify a users account

View a users current properties

iBuilder User Guide

iDX Release 2.0

359

Changing Passwords

To perform any of these actions:

1. Right-click on any user in the Active Users pane. A list of the user management options
available from this pane is displayed.

Figure 332. User Account Options from the Active Users Pane
2. Select the desired operation from the menu.
3. For details, see the section indicated below for your menu selection:
Delete: Deleting an Existing Users Account on page358

Modify: Modifying a User on page356

View Properties: Viewing a Users Account Properties on page358

13.4 Changing Passwords

You can change your own password, regardless of what authorization level you are assigned.
Super Users and users with the Manage Users permission can see and change all user
passwords.
To change your password:
1. Select File Change Password from the Main Menu to open the Change Password dialog
box.

Figure 333. Change Password Dialog Box

2. Enter your current password in Old Password.
3. Enter your New Password before the change is processed.
4. Re-enter the new password in Confirm New Password.
5. Click OK.
Note:

360

For security reasons, it is important to change the passwords for the default
user names as soon as possible.

iBuilder User Guide

iDX Release 2.0

User Privileges

Note:

Changes to user accounts take place immediately, i.e. you do not have to
apply changes for users. However, new settings for a specific user will not
take effect until the next login under that account. If the user is logged in while
you make changes, the old settings remain in effect for the remainder of that
session.

13.5 User Privileges

The NMS allows users to be assigned a predetermined set of privileges or a custom-defined set
of privileges. There are two standard user levels: Super User and Guest. Both the standard
user levels and the custom-defined user level are described in detail in this chapter.
Initially, the Super User in the System group is the only user who can set up accounts. User
Groups and users can be added or deleted, and user privileges can be added or removed at
any time. For System and VNO users, a users privilege level is the same for both iMonitor and
iBuilder. For example, a user cannot be a Guest in iBuilder and a Super User in iMonitor. CNO
users have access to iMonitor only.
The NMS is shipped with a Super User and a Guest account already set up in the System User
Group. The Super User can then set up additional user groups and users and assign them to
have any of the following user levels:

Super User

Guest

Individually-defined User

If the Super User sets up a user as one of the standard user levels, the NMS system
automatically generates a predetermined set of privileges for that user level. (See Table 8.)
If the Super User sets up a user as a custom-defined user, the Super User can assign that user
any number of privileges from a list provided in the system. (See Table 9.)
Table 8. User Types and Access Privileges
Account Type

Access
Level

User Name
Password

Access Privileges

Pre-Programmed
by iDirect

Super User

admin
admin

Access to the NMS database and all of its

components within this user group, including the
ability to configure, modify, and delete anything in
the database owned by the group, including users
and their privileges. For System Super Users, ability
to perform these operations on other User Groups
as well.

Pre-Programmed
by iDirect

Guest

guest
guest

Read-only access to the NMS database and all of its

components within this user group. System Guests
can read all User Group information.

iBuilder User Guide

iDX Release 2.0

361

User Privileges

Table 8. User Types and Access Privileges (continued)

Access
Level

Account Type
Custom
Defined by
Super User

Custom
Defined

User Name
Password
Defined by
Super User or
else the VNO
Super User
must have
Manage Users
privilege

Access Privileges
See Table 9, Custom Privileges.

Table 9 lists the various privileges that can be granted or revoked for a custom-defined user.
Table 9. Custom Privileges
Privilege Name

362

NMS
Application

Description

Database Read

The most basic privilege; allows retrieval of stored configuration

information. This is the only privilege Guest users are granted.
You cannot grant or revoke this privilege from iBuilder.

iBuilder,
iMonitor

Change Database

Allows modification of configuration information.

iBuilder

Download
Firmware

Allows download of firmware to line cards and remote modems.

iBuilder

Apply
Configuration

Allows application of configuration changes to networks, hub

lines cards, and remote modems.

iBuilder

Reset Modem

Allows remote and line card resets.

iBuilder,
iMonitor

Manage Users

Allows modification of user names and passwords.

iBuilder

Edit Permissions

Allows modification of user permission settings.

iBuilder

Upload
Configuration

Allows retrieval of a remote modems or line cards active

configuration.

iBuilder

Basic Probe

Allows retrieval of real-time statistics in the Probe tab.

iMonitor

Advanced Probe

Allows all Probe functions (reset, connect, change tx power,

etc.).

iMonitor

Customize
Configuration

Allows access to the Custom tab in the Remote Modify Dialog

Box.

iBuilder

Password in Clear
Text

Controls whether or not an NMS user can see remote and protocol
processor passwords in clear text.

iBuilder

Monitor Longterm
Statistics

Allows monitoring of long term statistics in iMonitor.

iMonitor

GQoS Planning

Allows modifications to the Group QoS configuration for

Networks, Inroute Groups and Group Profiles.

iBuilder

iBuilder User Guide

iDX Release 2.0

NMS Database Locking

13.5.1 Super User and Guest Level Privileges

The two basic privilege levels are Super User (all privileges) and Guest (read-only).

The Super User access level gives the user complete access to all features of the NMS, in
both iBuilder and iMonitor, that are available to the User Group in which the Super User is
defined.

Guest access level provides read-only access to all parts of the network in iBuilder with
no ability to change data or download images. Guest access provides most functions in
iMonitor, with the following exceptions:
Guest-level users cannot connect to remote modems.

Guest-level users cannot exercise functions on the Probe tab of iMonitors remote
control panel.

13.5.2 Super User and Guest Privileges for VNOs

A user defined in a VNO as a Super User is able to see and operate on only those network(s)
that the Super User specifies, with the following additional restrictions. VNO Super Users can
add, modify or delete all remotes within their visible nodes. Generally, they are provided with
full remote management capability on these nodes.
1. They cannot create or modify any network components in the network tree
(Spacecraft/Carriers, remote/hub antenna components, QoS Profiles).
2. They cannot create or modify Hub RFT or Hub Chassis records.
3. They cannot perform any operations on the Teleport or Protocol Processor entries in the
network tree.
4. From the network level in the tree, they cannot perform multicast downloads, delete
networks, or create new line cards.
5. They can modify the network record, but only to activate/deactivate remotes.
6. They cannot see or modify acquisition or uplink control parameters.
7. From the hub level in the tree, they cannot perform image downloads, nor can they
create or delete line cards.
A user defined in a VNO as Guest has read-only permissions to the nodes visible to a Super
User in that the VNO.

13.6 NMS Database Locking

The NMS configuration server guarantees the integrity of your configuration parameters by
locking the database when a modification takes place, and releasing the lock when the
modification is complete. Prior to iDS Release 7.0, there was one global lock shared by all
users. The lock became active whenever any iBuilder user launched a Modify dialog box for
any network object. During this time no other users could launch any Modify panes.
Beginning with release 7.0, there is one lock for each User Group. Members of different User
Groups can modify the database at the same time. Within a User Group, there is still a single
lock. The System User Group, however, is granted a global lock; if a user from the System

iBuilder User Guide

iDX Release 2.0

363

NMS Database Locking

group is modifying a record, no other users, regardless of group membership, can modify the
database.
If a user launches a Modify pane and forgets to close it, thereby preventing other users in the
same User Group from modifying records, you can use the following procedure to free the
lock for other users:
1. Log into the NMS server as root.
2. Enter the command:
telnet 0 14123
3. Log onto the console with user name admin and password iDirect.
4. Enter the command:
clients -v
5. Locate the line of the user who has the lock. The line will look something like this:
type: iBuilder V $Name: iNFINITI-80 $, IP: 10.0.19.108:1513, login:
crb, server_time: Thu Jul 29 17:54:16 2004
The IP address of the lock-holder is shown in the error message pop-up when you try to
modify an object.
6. The section that begins IP contains the information you need to break the lock.
7. Enter the command:
kill <ip address>:<port number>
where <ip address> is the host address, and <port number> is the actual port number. In
the example above, you would enter kill 10.0.19.108:1513.
8. This command will break the users lock and other users will now be able to modify
network objects.

364

iBuilder User Guide

iDX Release 2.0

Prerequisites for Converting an Existing Star Network to Mesh

14 Adding Mesh Capabilities

to a Star Network

Converting a star network to support mesh traffic will require changes to your existing inroute
groups, inroutes and remotes. This chapter documents the prerequisites and procedures for a
successful conversion from a network that supports star traffic only to one that can also carry
mesh traffic. It discusses the following topics:

Prerequisites for Converting an Existing Star Network to Mesh on page365

Recalibrating a Star Outbound Channel for Mesh on page366

Converting a Star Inbound Channel to Mesh on page367

Reconfiguring Star Remotes to Carry Mesh Traffic on page367

Note:

Mesh is not supported in iDX Release 2.0.

14.1 Prerequisites for Converting an Existing Star

Network to Mesh
Prior to converting an existing star network to carry mesh traffic, the following actions should
be taken:

Perform a new Link Budget Analysis (LBA) to ensure that the equipment is correctly sized
to support mesh. This is discussed in detail in the chapter titled Mesh Technical
Description in the iDirect Technical Reference Guide.

Verify that the satellite transponder configuration for the hub and each remote is able to
support the mesh architecture. All hubs and remotes must lie in the same geographic
footprint so that they are able to receive their own loopback transmissions to the
satellite. This requirement precludes the use of the majority of spot beam and all crossstrap hemi-beam transponders for mesh networks.

Verify that all of the following mesh hardware requirements are met:
A Private Hub supporting mesh must use an externally referenced PLL LNB

An M1D1, eM1D1 or M1D1-T line card must be used to transmit the mesh outroute.

An M1D1, eM1D1 or M0D1 line card must be used to receive the mesh inroute. (This
line card can be the same M1D1 line card used for the mesh outroute.)

iBuilder User Guide

iDX Release 2.0

365

Recalibrating a Star Outbound Channel for Mesh

All mesh remotes must be equipped with PLL LNBs.

Each remote BUC and antenna must be properly sized to close link budget for a given
data rate.

A mesh remote must be an iNFINITI 5300/5350; iNFINITI 7300/7350; iNFINITI 8350;

Evolution e8350; iConnex-100; iConnex-700; iConnex-e800.

For a detailed discussion of these prerequisites, see the chapter titled Mesh Technical
Description in the iDirect Technical Reference Guide.

14.2 Recalibrating a Star Outbound Channel for Mesh

If you plan to use an existing M1D1 (or M1D1-T) transmit line card to support mesh remotes,
you must recalibrate the line card to determine the clear sky C/N values, and reconfigure the
line card in iBuilder. Follow these steps to recalibrate a star outroute to support mesh
remotes:
1. Right-click the M1D1/M1D1-T line card in the iBuilders tree and select
ModifyConfiguration from the menu.
2. When the Line Card dialog box appears, select the Mesh Enabled check box in the Mesh
area of the screen.

Figure 334. Line Card Dialog Box

3. Configure the Uplink Power Control (UPC) parameters for the mesh outroute:
a. Follow the steps in section 12.10 on page325 to determine and set the SCPC LB Clear
Sky C/N parameter for the mesh outroute.
b. Follow the steps in section 12.11 on page326 to determine and set the Hub UPC
margin for the mesh outroute.

366

iBuilder User Guide

iDX Release 2.0

Converting a Star Inbound Channel to Mesh

14.3 Converting a Star Inbound Channel to Mesh

You can configure either an M1D1/M1D1-T line card or an M0D1 line to receive a mesh inroute.
The same M1D1 line card that transmits the mesh outroute can also receive the mesh inroute.
Whether you are converting an existing inroute to mesh or adding a new mesh inroute, you
must calibrate the inbound carrier and set the Clear Sky C/N parameters for the mesh
inroutes. This must be performed during the commissioning of each inroute.
For details on how to calibrate the inbound channel to support mesh, see section 12.13 on
page328.
Note:

Subsequent mesh inbound channels can be calibrated and added to the network
without affecting existing outbound or inbound channels.

Note:

Beginning with iDS Release 8.2, you can add multiple inroutes to a meshenabled inroute group. These inroutes can consist of a mix of star-mesh and
star carriers. See Adding Upstream TDMA Carriers on page76 for details.

14.4 Reconfiguring Star Remotes to Carry Mesh Traffic

This section describes the steps necessary to reconfigure an existing star remote to carry
mesh traffic. Once the remote has been reconfigured for mesh, it will be able to send and
receive single-hop traffic to and from other remotes in the mesh inroute group.
Reconfiguring a star remote for mesh involves the following steps:

Enabling the remote for mesh in iBuilder

Recommissioning the initial transmit power of the remote to be clear sky C/N plus 1 dB
and entering the new value in iBuilder. (This can be achieved without personnel at the
remote site.)

Determining the outbound and inbound Clear Sky C/N parameters for the remote and
entering them in iBuilder

Enabling Mesh for a remote in iBuilder automatically configures the second demodulator on
the remote to receive the mesh inroute. When you apply the new configuration, inroute
parameters such as the carrier frequency, symbol rate, and FEC rate are sent to the remote.
The UPC algorithm adjusts the transmit power of all remotes to operate within a common C/N
range at the hub. A remote with a C/N significantly higher or lower than this range will not
acquire into the network.
Note:

iBuilder User Guide

iDX Release 2.0

Incorrect commissioning of a remote may prevent the remote from acquiring

into the network.

367

Reconfiguring Star Remotes to Carry Mesh Traffic

Follow these steps to configure an existing remote to carry mesh traffic:

1. Right-click the remote in the network tree and select ModifyItem to display the Remote
Modify dialog box.

Figure 335. Remote Information Tab: Enabling Mesh

2. In the Mesh section of the screen, select Enabled.
3. Select a Home Inroute for this remote. Although a mesh remote can frequency hop when
transmitting to other mesh remotes, a mesh remote receives all mesh communications on
its home inroute. If you select None, the remote configuration state will change to
incomplete.
4. To determine and set the new initial power for the remote follow the steps in the section
Set the Initial Tx Power for a Remote of the Installation and Commissioning Guide for
iDirect Satellite Routers.
5. To set the Clear Sky C/N parameters for the remote, follow the steps in the section Set
the Clear Sky C/N Parameters for a Mesh Remote of the Installation and Commissioning
Guide for iDirect Satellite Routers.

368

iBuilder User Guide

iDX Release 2.0

Reconfiguring Star Remotes to Carry Mesh Traffic

Note:

Once recommissioned for mesh, a remote will typically have a higher initial
transmit power setting than it had in the star network.

Note:

A similar procedure should be followed when moving a remote from a mesh

network to a star network, i.e. the initial Tx power should be adjusted to
accommodate the star requirements.

iBuilder User Guide

iDX Release 2.0

369

Reconfiguring Star Remotes to Carry Mesh Traffic

370

iBuilder User Guide

iDX Release 2.0

TRANSEC Hardware Requirements

15 Converting an Existing
Network to TRANSEC

Transmission Security (TRANSEC) prevents an adversary from exploiting information available

in a communications channel without necessarily having defeated the encryption inherent in
the channel. Even if a wireless transmissions encryption is not compromised, by using basic
signal processing techniques taken from wireless transmission acoustics, information such as
timing and traffic volumes can be determined. This information could provide someone
monitoring the network a variety of information on unit activity.
iDirect achieves full TRANSEC compliance by presenting to an adversary eavesdropping on the
RF link a constant wall of fixed-size, strongly-encrypted (AES, 256 bit Key) traffic segments,
the frequency of which does not vary in response to network utilization. For a detailed
technical description of iDirects TRANSEC feature, see the iDirect Technical Reference
Guide.
This chapter explains how to convert an existing iDirect network to use the TRANSEC feature.
Before you can do this, all hardware in your network must be TRANSEC-compatible, and you
must be licensed by iDirect to use the TRANSEC feature. If you are not licensed to use
TRANSEC, please contact the iDirect Technical Assistance Center (TAC).
This chapter contains the following major sections:

TRANSEC Hardware Requirements on page371

TRANSEC Host Certification on page372

Reconfiguring the Network for TRANSEC on page373

Note:

TRANSEC is not supported on DVB-S2 outbound carriers.

15.1 TRANSEC Hardware Requirements

All line cards and remote model types under a TRANSEC protocol processor must be TRANSECcompatible. If you attempt to convert a protocol processor to TRANSEC which has nonTRANSEC elements in its sub-tree, iBuilder will disallow the conversion and generate an error
message. Therefore you must ensure that all installed model types support TRANSEC and
correctly configured in iBuilder.

iBuilder User Guide

iDX Release 2.0

371

TRANSEC Host Certification

Only the following iDirect model types support TRANSEC:

M1D1-T, M1D1-TSS, eM1D1 line cards

iNFINITI 7350, 8350 remotes

Evolution e8350 remotes

iConnex-100, iConnex-700, iConnex-e800 remotes

15.2 TRANSEC Host Certification

All hosts in an iDirect TRANSEC network must have X.509 certificates issued by the iDirect
Certificate Authority (CA) Foundry. Hosts include NMS servers, protocol processor blades,
TRANSEC line cards, and TRANSEC remotes. Since uncertified remotes will not be allowed to
join the network, you should issue your certificates before converting your network to
TRANSEC.
Follow this procedure to issue X.509 certificates to your TRANSEC hosts:
1. Follow the procedure in Using the CA Foundry on page395 to log on to your NMS server
and execute the CA Foundry.
2. If you have not created your Certificate Authority (CA), do so by following the procedure
in Creating a Certificate Authority on page397.
3. Follow the procedure in Logging On to a Certificate Authority on page398 to log on to
your CA.
4. Following the procedure in Certifying a Host on page401, connect to each host in your
network and issue an X.509 certificate to the host from your CA. Issue certificates in the
following order:
a. Issue a certificate to each NMS server.
b. Issue a certificate to each protocol processor blade in the sub-tree of the protocol
processor.
c. Issue a certificate to each remote in the sub-tree of the protocol processor.
Figure 336 illustrates a single TRANSEC sub-tree in the iBuilder network tree with one blade,
two line cards and three remotes. All of those network elements, plus the NMS servers, should
be certified before you convert to TRANSEC.

Figure 336. Elements of a TRANSEC Network

372

iBuilder User Guide

iDX Release 2.0

Reconfiguring the Network for TRANSEC

Note:

Although it is more convenient to certify your remotes before TRANSEC is

enabled, there may be times when you are required to certify a non-TRANSEC
remote over the air in an existing TRANSEC network. For details on how to
accomplish this, see Bringing an Unauthorized Remote into a TRANSEC
Network on page399.

15.3 Reconfiguring the Network for TRANSEC

Once you have ensured that all hardware is TRANSEC-compatible, and you have issued
certificates to all X.509 hosts, follow these steps to convert your network to TRANSEC:
1. Right-click the protocol processor in the network tree and select ModifyItem.

The Protocol Processor dialog box opens with the Information tab selected.

Figure 337. Enabling TRANSEC for an Existing Network

2. Select TRANSEC Enabled.
3. Click OK to save the change. This will cause all elements under the protocol processor to
display pending changes in the iBuilder tree.

iBuilder User Guide

iDX Release 2.0

373

Reconfiguring the Network for TRANSEC

4. Right-click the Protocol Processor in the Network Tree and select ApplyConfiguration.

5. In the confirmation dialog box, click Yes to confirm the change.

6. For each network under the TRANSEC protocol processor, right-click the network icon and
select Apply ConfigurationMultiple to display the Automated Configuration
Downloader dialog box.

Figure 338. Automated Configuration Downloader Dialog Box

7. In the Automated Configuration Downloader dialog box, select the following options:
a. In the Remotes area of the dialog box:

374

Select all remotes.

Under Target, select Both.

Under Protocol, select Reliable (TCP).

Under Reset, select Reset on Success.

iBuilder User Guide

iDX Release 2.0

Reconfiguring the Network for TRANSEC

b. In the Line Cards area of the dialog box:

Select all line cards with Status of Changes Pending.

Under Protocol, select Reliable (TCP).

Under Reset, select Reset on Success.

c. In the Network area of the dialog box, select your network.

8. Click the Start button to apply the changes to your network.
9. Monitor the download to ensure that all changes are applied successfully.
10. Repeat Step 6 through Step 9 for any remaining networks under your TRANSEC protocol
processor.
Once all changes have been downloaded, the conversion to TRANSEC is complete.

iBuilder User Guide

iDX Release 2.0

375

Reconfiguring the Network for TRANSEC

376

iBuilder User Guide

iDX Release 2.0

16 Converting Between
SCPC and DVB-S2
Networks

Some iDirect hardware can support either an SCPC or a DVB-S2 outbound carrier. An eM1D1 or
XLC-11 line card can transmit either carrier type. Evolution e8350, Evolution X5, and iConnex
e800/e850mp remotes can receive either carrier type. This chapter describes how to convert
an existing iDirect network from SCPC to DVB-S2 or from DVB-S2 to SCPC when your hardware
supports it.
Note:

Before converting between SCPC and DVB-S2, verify that your link budget meets
the requirements of the new outbound carrier configuration.

Beginning in iDX Release 2.0, a single package contains the firmware to allow remotes to
receive both SCPC and DVB-S2 carriers. Therefore, you are no longer required to re-load the
remote firmware to convert your network to a different type of outbound carrier.
However, a line card must execute different firmware depending on the type of outbound
carrier configured for the network. For a line card to operate in an SCPC or DVB-S2 network,
it must have the correct firmware package for that carrier type installed.
For example, an XLC-11, eM1D1 or XLC-M line card executing iDX Release 2.0 requires the
evo_d_hub package to operate in a DVB-S2 network. The same line card requires the
evo_l_hub package to transmit operate in an SCPC network.
The line cards that support SCPC and DVB-S2 are able to store both packages simultaneously.
Downloading one package does not overwrite the other package. Once the modem has both
packages, you can switch between SCPC and DVB-S2 without reloading firmware.
Follow the procedure in this chapter to convert a network from SCPC to DVB-S2 or to convert
a network from DVB-S2 to SCPC. The procedure consists of the following main steps:

Download the new firmware to the line card that will transmit the new carrier.

Define the new carrier and assign it to the transmit line card.

Apply the configuration changes to the remotes in the network.

Apply the configuration changes to the network.

iBuilder User Guide

iDX Release 2.0

377

Download the New Firmware to the Tx Line Card

16.1 Download the New Firmware to the Tx Line Card

You must ensure that the eM1D1 or XLC-11 transmit line card in your network is loaded with
the correct firmware package for the new carrier type. If you are not certain that your Tx line
card has both packages, follow the steps in this section to download the new package. If you
have a standby line card backing up your transmit line card, download the new firmware to
that line card as well.
1. Right-click your network in the iBuilder tree and select Package DownloadTCP.
2. In the Package section of the TCP Download dialog box, make the following selections:
Hardware: EvolutionLinecard

Role: Hub

Mode: Select DVB-S2 if you are converting to DVB-S2. Select iNFINITI if you are
converting to SCPC.

Figure 339 shows the appropriate selections for converting your Evolution line card from
SCPC to DVB-S2.

Figure 339. Selections for Downloading DVB-S2 Line Card Firmware

3. Verify that the Selected Package is correct: evo_d_hub for DVB-S2; evo_l_hub for SCPC.
4. In the Line Cards section of the TCP Download dialog box, verify that all line cards you
want to download are selected.
5. In the Options section of the TCP Download dialog box, under Reset, select Reset on
Success.
6. Click the Start button to begin the download.
7. When the download is complete and the line card has reset, verify that the remotes reacquire the existing network and become operational before continuing. At this point
your network should be operating as it did prior to starting this procedure.
Your line card now has both packages and your network is ready for conversion. Perform the
remaining steps to switch the network to the new carrier type.

378

iBuilder User Guide

iDX Release 2.0

Assign the Carrier and Update the Configuration

16.2 Assign the Carrier and Update the Configuration

1. If you have not already done so, follow the steps in Adding Downstream Carriers on
page73 to configure your Tx (or Tx/Rx) carrier for the new carrier type.
Note:

You can also convert your existing carrier to the new carrier type by modifying
the appropriate fields in the Downstream Carrier dialog box.

2. Once the carrier parameters are configured, in the Assigned to Line Card field of the
Downstream Carrier dialog box, select your Tx line card.

Figure 340. Assigning a Line Card to a Carrier

3. Click OK to save your changes.
4. Right-click your network and select Apply ConfigurationMultiple.
5. In the Automated Configuration Downloader dialog box, select All remotes in your
network.

Figure 341. Selecting All Remotes for Configuration Download

6. For Target, select Both.
7. For Protocol, select Reliable (TCP).
8. For Reset, select Reset on Success.
9. Click the Start button to apply the configuration to your remotes.
Note:

At this point the remotes will lose the network as they update their
configuration for the new carrier type.

10. Once the remotes have been updated, right-click your network and select Apply
ConfigurationNetwork to complete the conversion.

11. Once the line card begins transmitting the new outbound carrier, verify that the remotes
acquire the new carrier and the network becomes operational.

iBuilder User Guide

iDX Release 2.0

379

Assign the Carrier and Update the Configuration

380

iBuilder User Guide

iDX Release 2.0

Appendix A Configuring a
Distributed NMS Server
You can distribute your NMS server processes across multiple NMS server machines. The
primary benefits of machine distribution are improved server performance and better
utilization of disk space.
iDirect recommends a distributed NMS server configuration once the number of remotes being
controlled by a single NMS exceeds approximately 800.

A.1

Prerequisites
Before you begin the configuration process, ensure that you have the following in place:

Four NMS servers, each installed with the same version of NMS software; three of these
servers are used for running various services and the fourth is used as a backup server. If
you already have a single Primary NMS server and a single Backup NMS server in place, you
will need to add two more NMS servers with the same version of software the current
Primary NMS is running.

Note:

A.2

For information on setting up a Backup NMS server for you DNMS, see the
iDirect Technical Note NMS Redundancy and Failover for your release.

IP addresses for all additional NMS servers must be on the same subnet as the Primary and
Backup servers. These servers are on the upstream side.

If the NMS servers have private IP addresses and you need to access these servers (for
running iBuilder and iMonitor) externally, then you have the following options: configure a
VPN system to allow access to the servers, or NAT the private addresses to the public
addresses and run the iDirect provided script on every client PC that will run iBuilder and
iMonitor clients. See Running the NAT Script on page390 for the script.

Distributed NMS Server Architecture

The distributed NMS architecture allows you to match your NMS server processes to server
machines however you want. For example: you can run all server processes on a single
platform (the current default); you can assign each server process to its own machine; or you
can assign groups of processes to individual machines.
Server configuration is performed one time using a special script distributed with the
nms_servers installation package. Once configured, the distribution of server processes
across machines will remain unchanged unless you reconfigure it. This is true even if you
upgrade your system.

iBuilder User Guide

iDX Release 2.0

381

Logging On to iBuilder and iMonitor

The only supported distribution scheme is shown in the figure below.

Figure 342. Sample Distributed NMS Configuration

This configuration has the following process distribution:

A.3

NMS Server 1 (Primary) runs the configuration server (cfgsvr), the chassis manager server
(cmsrv) and the Protocol Processor controller process.

NMS Server 2 (Auxiliary) runs only the Statistics server (nrdsvr).

NMS Server 3 (Auxiliary) runs the Event server (evtsvr) and the Latency Server (latsvr).
The latsvr is not shown in this diagram.

Logging On to iBuilder and iMonitor

From the iBuilder or iMonitor users perspective, a distributed NMS server functions identically
to a single NMS server. In either case, users provide a user name, password, and the IP address
or Host Name of the NMS configuration server when logging in. The configuration server stores
the location of all other NMS servers and provides this information to the iBuilder or iMonitor
client. Using this information, the client automatically establishes connections to the server
processes on the correct machines.

382

iBuilder User Guide

iDX Release 2.0

Setting Up a Distributed NMS Environment

A.4

Setting Up a Distributed NMS Environment

You may set up or modify a Distributed NMS environment at any time while your network
remains operational. However, you will be required to stop your NMS server processes briefly
and restart them on the new machine(s) for the new configuration to take effect.
Note:

There is a slight probability that problems will occur if the database server
process should exit during the reconfiguration. You can avoid this possibility by
stopping your NMS processes prior to setting up the new configuration. In that
case, the NMS outage will be slightly longer.

To configure a distributed NMS, you will run the script NMS-configuration-client.pl. This
script resides on the primary NMS server. When executed, it queries the local subnet,
determining the IP addresses of all NMS server machines and the current assignment of NMS
processes to server machines. The script then asks you to specify the new distribution and
updates the assignments before exiting. You then restart the NMS processes.
To configure a distributed NMS and retain historical data, begin with Step 1. To configure a
distributed NMS and not retain historical data, begin with Step 9.
1. Verify that all four servers are configured with correct IP addresses, there is IP
connectivity between all the of the servers, and that iDirect NMS software is installed on
each server such that NMS server 1, 2, and 3 are installed as primary and NMS server 4 is
installed as backup.
2. Log on to NMS 2 as root.
3. Stop the NMS processes on the server by entering the following command:
service idirect_nms stop
4. Repeat Step 2 and Step 3 on NMS 3.
5. Log on to the NMS 1 as root.
6. Change your directory as follows:
cd /var/lib/mysql/nrd_archive
7. To copy the database from NMS 1 to NMS 2, enter the following command:
scp * root@x.x.x.x:/var/lib/mysql/nrd_archive/
Where x.x.x.x represents the IP address of NMS 2.
8. Repeat Step 7 and replace x.x.x.x with the IP address of NMS 3.
9. Start the NMS configuration on NMS 2 and NMS 3 by entering the following command on
each machine:
service idirect_nms start nms_config
The following steps must be done during a maintenance window as network downtime will
occur.
10. Logon to NMS 1 as root.
11. Stop the NMS services by entering the following command:
service idirect_nms stop

iBuilder User Guide

iDX Release 2.0

383

Setting Up a Distributed NMS Environment

12. Run the conversion script by entering the following command:

/home/nms/utils/db_maint/NMS-configuration-client.pl
The conversion script prompts you to select which services are to run on which servers. At a
minimum, the nrdsvr runs on NMS 2; the evtsvr and the latsvr run on NMS 3. The nmssvr,
nms_config, nms_monitor, cmsvr, cntrl, revsvr, and snmpsvr run on NMS 1.
Enter the number of the respective NMS when prompted. Sample output is shown below.
Note:

If this NMS shares the Chassis Manager Server of another NMS, you should enter
a 0 when prompted for the CM Server to skip that IP address. The procedure to
point your configuration server to an external CM Server is described in
Sharing the Chassis Manager Server on page261.

root@x3550 ~
# /home/nms/utils/db_maint/NMS-configuration-client.pl
NMS Config Client >>> Looking for NMS installations with bcast
255.255.255.255, please wait...
===========================================================
List of existing NMS configurations
===========================================================
From NMS.ServerConfiguration on computer with 192.168.76.82 :
127.0.0.1
nms_cfg_server_ip
127.0.0.1
nms_cm_server_ip
127.0.0.1
nms_ctl_server_ip
127.0.0.1
nms_evt_server_ip
127.0.0.1
nms_lat_server_ip
127.0.0.1
nms_nrd_server_ip
127.0.0.1
nms_oss_server_ip
From NMS.ServerConfiguration on computer with 192.168.76.80 :
127.0.0.1
nms_cfg_server_ip
127.0.0.1
nms_cm_server_ip
127.0.0.1
nms_ctl_server_ip
127.0.0.1
nms_evt_server_ip
127.0.0.1
nms_lat_server_ip
127.0.0.1
nms_nrd_server_ip
127.0.0.1
nms_oss_server_ip
From NMS.ServerConfiguration on computer with 192.168.76.65 :
127.0.0.1
nms_cfg_server_ip
127.0.0.1
nms_cm_server_ip
127.0.0.1
nms_ctl_server_ip
127.0.0.1
nms_evt_server_ip
127.0.0.1
nms_lat_server_ip
127.0.0.1
nms_nrd_server_ip
127.0.0.1
nms_oss_server_ip
From NMS.ServerConfiguration on computer with 192.168.76.67 :
127.0.0.1
nms_cfg_server_ip
127.0.0.1
nms_cm_server_ip
127.0.0.1
nms_ctl_server_ip

384

iBuilder User Guide

iDX Release 2.0

Setting Up a Distributed NMS Environment

127.0.0.1
127.0.0.1
127.0.0.1
127.0.0.1

nms_evt_server_ip
nms_lat_server_ip
nms_nrd_server_ip
nms_oss_server_ip

===========================================================
List of IPs, where NMS installation was presented:
===========================================================
192.168.76.82
(1)
192.168.76.80
(2)
192.168.76.65
(3)
192.168.76.67
(4)
NMS Config Client >>> Please enter index for MySql server
(use number in parentheses above)
1
NMS Config Client >>> Server MySql assigned to IP address
192.168.76.82
NMS Config Client >>> Please enter index for CFG server
(use number in parentheses above)
1
NMS Config Client >>> Server CFG assigned to IP address
192.168.76.82
NMS Config Client >>> Please enter index for CTL server
(use number in parentheses above)
1
NMS Config Client >>> Server CTL assigned to IP address
192.168.76.82
NMS Config Client >>> Please enter index for EVT server
(use number in parentheses above)
3
NMS Config Client >>> Server EVT assigned to IP address
192.168.76.65
NMS Config Client >>> Please enter index for NRD server
(use number in parentheses above)
2
NMS Config Client >>> Server NRD assigned to IP address
192.168.76.80
NMS Config Client >>> Please enter index for LAT server
(use number in parentheses above)
3
NMS Config Client >>> Server LAT assigned to IP address
192.168.76.65
NMS Config Client >>> Please enter index for OSS server
(use number in parentheses above)
3

iBuilder User Guide

iDX Release 2.0

385

Removing the SNMP Proxy Server from Auxiliary NMS Servers

NMS Config Client >>> Server OSS assigned to IP address

192.168.76.65
NMS Config Client >>> Please enter index for SKY server
(use number in parentheses above)
2
NMS Config Client >>> Server SKY assigned to IP address
192.168.76.80
NMS Config Client >>> Please enter index for CM server
(use number in parentheses above)
1
NMS Config Client >>> Server CM assigned to IP address 192.168.76.82
NMS Config Client >>> storing to NMS table ServerConfiguration
NMS Config Client >>> Done
13. Start all services on NMS 1 by entering the following command:
service idirect_nms start
14. Log on to NMS 2 and repeat Step 13.
15. Log on to NMS 3 and repeat Step 13.

A.5

Removing the SNMP Proxy Server from Auxiliary

NMS Servers
Before you continue, you must remove the SNMP proxy service from NMS 2 and NMS 3. To
remove the snmpproxy from NMS 2 and NMS 3, perform the following:
1. Log into NMS 2 as root.
2. Enter the following command:
rpm --erase nms_snmpproxy
The snmpproxy service is erased from the server.
3. Verify that the snmpproxy service is no longer running by entering the following
command:
service idirect_nms status
A list of all of the services that are running on the logged in machine displays.
4. Repeat these steps for NMS 3.
The SNMP proxy service is removed from the servers.

A.6

Regenerating the Options Files

Now that you have removed the SNMP proxy from the servers, you are ready to regenerate the
options files. The steps to do this follow:
1. Log on to NMS 1 as root.
2. Enter the following command:

386

iBuilder User Guide

iDX Release 2.0

Granting Read Permissions to NMS 2 and NMS 3

telnet 0 14123
3. Enter the Username and Password when prompted as follows:
Username: admin
Password: iDirect
4. Enter the following commands:
cfg status recalc netmodem.*
cfg status recalc rmtdef.*
cfg status recalc netdef.*
cfg status recalc ppglobal.*
Note:

Once these commands have been entered successfully, all the devices (remote,
HLC, network, PP) will display Changes Pending in iBuilder.

5. Launch iBuilder and apply the changes in the following order: all remotes, all Hub Line
Cards, network, and Protocol Processor.

WARNING! Downtime will be incurred while devices reboot.

A.7

Granting Read Permissions to NMS 2 and NMS 3

Now that you have regenerated the options files, you are ready to grant read permissions to
NMS 2 and NMS 3. Follow these steps to change the permissions:
1. Log on to NMS 1 and enter the following command:
mysql --exec=GRANT ALL ON *.* TO root@x.x.x.x
Where x.x.x.x represents the IP address of NMS 2.
2. Enter the following commands to flush the register:
mysql --exec=FLUSH PRIVILEGES
3. Repeat these steps and replace x.x.x.x with the IP address of NMS 3.
4. Restart the Event and NRD servers to force a reconnection to the config server using the
new permissions.
To verify that the new permissions have been correctly configured, perform the following step
on both NMS 2 and NMS 3:
1. Enter the following command from the command line prompt:
mysql --host=x.x.x.x
Where x.x.x.x represents the IP address of NMS 1.
If this command immediately connects you to the mysql prompt on NMS 1, then the new
permissions have been correctly configured on the server from which you are connecting.

iBuilder User Guide

iDX Release 2.0

387

Assigning QoS Profiles

A.8

Assigning QoS Profiles

Once you have set up your distributed NMS, you must redirect your IP packets for remote NMS
traffic to the correct NMS servers by modifying the NMS Service Levels in your Upstream and
Downstream Application Profiles.
For the NMS Upstream Application Profile, modify the Service Levels as follows:

Assign the destination IP address for NMS_TCP to NMS 1

Assign the destination IP address for NMS_UDP to NMS 2

Assign the destination IP address for NMS_ICMP to NMS 3

For the NMS Downstream Application Profile, modify the Service Levels as follows:

Assign the source IP address for NMS_TCP to NMS 1

Assign the source IP address for NMS_ICMP to NMS 3

For each of the above Service Levels, (the Upstream Application Profile is shown in this
example) follow these steps to reassign the destination IP address of the upstream traffic:
1. In the iBuilder tree, right-click the NMS Upstream Application Profile folder and select
Modify Item to open the Upstream Application Profile dialog box.

Figure 343. Upstream Application Dialog Box

2. In the Service Level area of the dialog box, select the appropriate Service Level for the
IP packet type you want to modify. (NMS_UDP, NMS_TCP or NMS_ICMP).
3. In the Rules area of the dialog box, select the Rule for that traffic.

388

iBuilder User Guide

iDX Release 2.0

Verifying Correct Operation

4. Click the Edit button to open the Edit Rule dialog box.

Figure 344. Edit Rule Dialog Box

5. Change the Destination IP address and Subnet Mask to match the NMS servers IP address
for this type of traffic. (TCP traffic must be routed to config server, UDP traffic to nrd
server, and ICMP traffic to both evt server and lat server.)
6. There will be Changes Pending on all remotes. Apply the changes.

A.9

Verifying Correct Operation

Now that you have completed the configuration steps, the cfgsvr, nrdsvr, evtsvr, cmsvr and
latsvr should all be running on the appropriate servers. To ensure proper operation, you must
verify that no service is running on more than one server. Enter the following command on
each server and verify that the correct services are running:
ps -ef | grep svr | grep -vi mysql | grep -vi logger
A list of running services displays.
If a service is running on a server that it should not be, use the following command to kill the
service:
killall service
where service represents the name of the service
For example, if the evtsvr process is running on NMS 1, enter the following command to kill
the process:
killall evtsvr
Verify that your servers are configured to run dbBackup and dbRestore. For configuration
procedures, refer to the iDirect NMS Redundancy technical note, which is available for
download on the TAC web page located at http://tac.idirect.net.

iBuilder User Guide

iDX Release 2.0

389

Running the NAT Script

A.10 Running the NAT Script

The iDirect NAT script translates private IP addresses to public IP address so that you can run
iBuilder and iMonitor from an external source. This section describes how to run the script for
iBuilder and iMonitor.
The steps for running the script for iBuilder are as follows:
1. On your PC or laptop, open Note Pad.
2. Copy the following lines into Note Pad:
@ECHO OFF
SET ENV_NRD_NMSAPI_IPADDR=x.x.x.x
Where x.x.x.x represents the IP address of NMS 2.
SET ENV_EVT_NMSAPI_IPADDR=x.x.x.x
Where x.x.x.x represents the IP address of NMS 3
SET ENV_LAT_NMSAPI_IPADDR=x.x.x.x
Where x.x.x.x represents the IP address of NMS 3
ibuilder.exe
3. Rename the Note Pad file to ibuilder.bat.
4. Save the file to the same directory where iBuilder is located.
The steps for running the script for iMonitor are as follows:
1. On your PC or laptop, open Note Pad.
2. Copy the following lines into Note Pad:
@ECHO OFF
SET ENV_NRD_NMSAPI_IPADDR=x.x.x.x
Where x.x.x.x represents the IP address of NMS 2
SET ENV_EVT_NMSAPI_IPADDR=x.x.x.x
Where x.x.x.x represents the IP address of NMS 3
SET ENV_LAT_NMSAPI_IPADDR=x.x.x.x
Where x.x.x.x represents the IP address of NMS 3
imonitor.exe
3. Rename the Note Pad file to iMonitor.bat.
4. Save the file to the same directory where iMonitor is located.

390

iBuilder User Guide

iDX Release 2.0

Managing a Distributed NMS

A.11 Managing a Distributed NMS

Run all scripts to mange a Distributed NMS from the directory: /home/nms/utils/db_maint.
To verify the DNMS server configuration, including the server IP addresses, enter the following
mysql command on the primary NMS server. Sample output is show after the command.
# mysql -e"select * from ServerConfiguration" nms | grep MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS

allow_ad_hoc
1
allow_fips
0
use_remote_active_flag 0
default_password
iDirect
default_su_password
P@55w0rd!
nms_server_ip
manage_tunnel_information
1
calculate_ppglobal_status
1
default_ppglobal_status Nominal
manage_remote_location 0
manage_remote_antenna
0
hub_sat_is_eth 1
manage_teleport_location
0
outroute_hub_has_rx_carrier
1
inroute_hub_has_tx_carrier
1
nms_cfg_server_ip
172.16.137.9
nms_nrd_server_ip
172.16.137.13
nms_evt_server_ip
172.16.137.14
nms_lat_server_ip
172.16.137.14
nms_ctl_server_ip
172.16.137.9
nms_cm_server_ip
172.16.137.9
nms_oss_server_ip
192.168.76.80
nms_sky_server_ip
172.16.137.9

The various forms of the NMS-configuration-client.pl command are shown here. It is unlikely
that you will need to use any command arguments when configuring your distributed NMS.
# ./NMS-configuration-client.pl h
NMS-configuration-client.pl [-cd=NAME] [-ad=NAME]
[-udp=UDPPORT] [-bcast=BCASTADDRESS]
-cd
:
-ad
:
-udp :
-bcast:
-vvv :
-qos :
-h
:

Change config database from [nms]

Change archive database from [nrd_archive]
Change default UDP port [70123]
Change default bcast address[255.255.255.255]
verbose mode level equals number or v(s)
reload service level QoS rules -- do not use it
print help

The NMS-domain-commands.pl command stops, starts or restarts the NMS server processes
on all NMS machines. You can run the command on any of the server machines.
The various command forms are:
# ./NMS-domain-commands.pl -h

iBuilder User Guide

iDX Release 2.0

391

Managing a Distributed NMS

Usage:
NMS-domain-commands.pl [-udp=UDPPORT] [-exec="<command> <server
name> <server name> ..."
-udp
: Change default UDP port [70123]
<command> is <start | stop | restart | reload | status >
<server name> is <nmssvr | evtsvr | nrdsvr | latsvr | cntrlsvr |
snmpsvr | nms_monitor>
For example, the following two commands show the status of NMS server processes. The first
example shows the status of all processes. The second example shows the status of the
nms_monitor process.
./NMS-domain-commands.pl -exec="status"
./NMS-domain-commands.pl -exec="status nms_monitor"
The following commands start, stop and restart server processes. The first example starts all
processes. The second example stops all processes. The third example starts the evtsvr
process. The final example restarts the latsvr process.
./NMS-domain-commands.pl -exec="start"
./NMS-domain-commands.pl -exec="stop"
./NMS-domain-commands.pl -exec="start evtsvr"
./NMS-domain-commands.pl -exec="restart latsvr"
An example of the output for NMS-domain-commands.pl script is presented below:
# ./NMS-domain-commands.pl -exec="status"
ip = 172.16.137.13, servers: nrdsvr nms_monitor
ip = 172.16.137.9, servers: nmssvr revsvr snmpsvr mapsvr nms_monitor
cntrlsvr
ip = 172.16.137.14, servers: evtsvr nms_monitor latsvr
+++++++++++++++++++++++++++++++++++++++++++++++++
Using configuration from MySQL NMS.ServerConfiguration table on
computer 127.0.0.1:
>>>>> 172.16.137.13:
nms_config (pid 28903) is running...
nrdsvr (pid 30734) is running...
cmsvr (pid 6373) is running...
nms_monitor (pid 30755) is running...
>>>>> 172.16.137.14:
nms_config (pid 6346) is running...
evtsvr (pid 18493) is running...
latsvr (pid 6917) is running...
nms_monitor (pid 6931) is running...
>>>>> 172.16.137.9:
nms_config (pid 2118) is running...
nmssvr is stopped
revsvr is stopped
snmpsvr is stopped
cntrlsvr is stopped
nms_monitor is stopped

392

iBuilder User Guide

iDX Release 2.0

dbBackup/dbRestore and the Distributed NMS

A.12 dbBackup/dbRestore and the Distributed NMS

The dbBackup and dbRestore scripts are completely compatible with the new distributed
NMS. You may choose to have one-for-one or one-for-n redundancy for your NMS servers.
One-for-n redundancy means that one physical machine will back up all of your active servers,
If you choose this form of redundancy, you must modify the dbBackup.ini file on each NMS
server to ensure that the separate databases are copied to separate locations on the backup
machine.
Figure 345 shows three servers, each copying its database to a single backup NMS. If NMS 1
fails, you will not need to run dbRestore prior to switchover since the configuration data will
have already been sent to the backup NMS. If NMS 2 or NMS 3 fails, you will need to run
dbRestore prior to the switchover if you want to preserve and add to the archive data in the
failed servers database.

Figure 345. dbBackup and dbRestore with a Distributed NMS

iBuilder User Guide

iDX Release 2.0

393

dbBackup/dbRestore and the Distributed NMS

394

iBuilder User Guide

iDX Release 2.0

Using the CA Foundry

Appendix B Using the

iDirect CA Foundry

All hosts in an iDirect TRANSEC network must have X.509 public key certificates. Hosts include
NMS servers, protocol processor blades, TRANSEC line cards, and TRANSEC remotes.
Certificates are required to join an authenticated network. They serve to prevent man-in-themiddle attacks and unauthorized admission to the network. You must use the iDirect
Certificate Authority (CA) utility (called the CA Foundry) to issue the certificates for your
TRANSEC network. For more information on the iDirect TRANSEC feature, see the iDirect
Technical Reference Guide.
This appendix contains the procedures required to issue and manage the X.509 certificates in
an iDirect TRANSEC network. It contains the following major sections:

B.1

Using the CA Foundry on page395

Creating a Certificate Authority on page397

Logging On to a Certificate Authority on page398

Connecting to a Host on page398

Bringing an Unauthorized Remote into a TRANSEC Network on page399

Certifying a Host on page401

Revoking a Remotes Certificate on page402

Updating the Network Keys on page404

Using the CA Foundry

This section explains how to start the iDirect CA Foundry and how to use its operator
interface. The CA Foundry is copied to your NMS server during the release installation or
upgrade procedure. Subsequent sections in this appendix explain the details of the specific CA
Foundry commands that you will need to certify your TRANSEC network.

iBuilder User Guide

iDX Release 2.0

395

Using the CA Foundry

Start the CA Foundry as follows:

1. Using a Secure Shell (SSH) client such as PuTTY, log on to the root account of your NMS
server.

Figure 346. Logging On to the NMS Server

2. At the command line prompt, enter the ca command to display the initial CA Foundry
menu shown in Figure 347. Once you have created a CA and logged on to it, more menu
choices will become available.

Figure 347. Initial CA Foundry Menu

3. Navigate in the CA Foundry as follows:
For all menus (and sub-menus), use the arrow keys to change menu selections. The
current selection is displayed with a blue background.

Press Enter to select any menu item.

If you want to terminate a command without completing it, press the F5 key. This will
return control to the menu at the top of the window.

To exit the CA Foundry and return to the Linux command prompt, select Exit from the
menu, or press the F5 key when the top-level menu is active.

Figure 348. Exiting the CA Foundry

For details on specific CA Foundry operations, see the remaining sections in this appendix.

396

iBuilder User Guide

iDX Release 2.0

Creating a Certificate Authority

B.2

Creating a Certificate Authority

You should create a single (root) Certificate Authority (CA) to certify all hosts in your TRANSEC
network. iDirect does not support a hierarchical chain of trust for CAs.
Follow these steps to create a new CA:
1. Start the CA Foundry according to the procedure in Using the CA Foundry on page395.
2. Using the arrow keys, select New CA from the top-level menu and press Enter.

Figure 349. Creating a New Certificate Authority

3. When prompted, enter the information for your new CA. A CA name and password are
required. The remaining entries are optional.

Figure 350. Configuring the New Certificate Authority

4. When asked whether or not you want to generate a signing request for this CA, type n.
(Chain-of-trust certification is not supported in iDirect.)
5. Press any key to continue. You will be automatically logged on to the new CA.

iBuilder User Guide

iDX Release 2.0

397

Logging On to a Certificate Authority

B.3

Logging On to a Certificate Authority

Follow these steps to log on to a CA:
1. Start the CA Foundry according to the procedure in Using the CA Foundry on page395.
2. Using the arrow keys, select Open CA from the top-level menu and press Enter to display
a menu of available CAs.

Figure 351. Logging On to a Certificate Authority

3. Select the CA you want to open and press Enter.
4. Enter the CAs password at the prompt.
You are now logged on to the CA. When you are logged on to a CA, a status bar is displayed at
the bottom of the window. The status bar displays the name of the CA you are logged on to,
the CA that signed this CAs certificate, and, if you are connected to a host, the IP address of
the host.

Figure 352. CA Foundry Status Line

Note:

Since chain-of-trust certification is not supported by iDirect, the CA certificate

should be displayed as Self-signed.

B.3.1 Connecting to a Host

Your CA must be connected to a host before you can perform any host operations. If desired,
you can first connect to the host by selecting Connect to Host from the CA Foundrys Host
Operations menu and, once connected, select the specific host operation you want to
execute. Alternatively, you can simply select the host operation from the menu without
connecting first. If you are not connected to a host, the CA Foundry will prompt you for the
required host information and establish the connection before executing the operation.
Note:

You will not be able to connect to an uncertified remote over the air unless you
first disable authentication for the remote. See Bringing an Unauthorized
Remote into a TRANSEC Network on page399 for details.

Follow these steps to connect to a host:

1. Start the CA Foundry and log on to a CA according to the procedure on page398.
2. Use the arrow keys to select Host Operation from the top-level menu and press Enter.

398

iBuilder User Guide

iDX Release 2.0

Logging On to a Certificate Authority

3. Select Connect to Host from the Host Operation menu and press Enter.
4. When prompted, enter the following host information:
a. Enter the IP address of the host to which you want to connect.
b. Accept the default port number by pressing Return.
c. Enter the password for the admin account of the host.
Figure 353 shows an example of a successful attempt to connect to a host from a CA.

Figure 353. Certificate Authority Connected to a Host

B.3.2 Bringing an Unauthorized Remote into a TRANSEC

Network
In general, it is best to certify your TRANSEC remotes over a direct LAN connection at your
hub before commissioning them in your TRANSEC network. If you are converting an existing
network to TRANSEC, you should certify the existing remotes over the air before you enable
TRANSEC for the network to avoid the necessity of connecting to unauthorized hosts over the
TRANSEC link.
However, there may be times when you are required to issue a certificates to uncertified
remotes over the air in an existing TRANSEC network. Therefore, iDirect provides a way for
you to allow an uncertified remote to join a TRANSEC network by temporarily disabling
authentication for the remote. When authentication is disabled for a remote, the TRANSEC
protocol processor allows that remote to enter the TRANSEC network without checking its
X.509 certificate. Once you have disabled authentication for the remote and the remote joins
the network, you can then certify the remote using the CA Foundry. Once the remote is
certified, you should immediately re-enable acquisition authorization for the remote.

WARNING! Remotes with authentication disabled can join a TRANSEC network without a
valid X.509 certificate. You should only disable authentication when
absolutely necessary.
The procedure in this section describes how to disable authentication for a TRANSEC remote.
Once you have disabled authentication and the remote joins the network, you can use the CA
Foundry to connect to your remote and issue the X.509 certificate.

iBuilder User Guide

iDX Release 2.0

399

Logging On to a Certificate Authority

Follow these steps to disable authentication for a specific remote:

1. In iBuilder, right-click the remote in the network tree and select ModifyItem to display
the Information tab of the remote configuration dialog box.
2. Select the Disable Authentication check box.
3. When the warning message appears, click Yes to confirm the change.

Figure 354. Warning Message when Disabling Authentication

4. Click OK to save the change.
5. Right-click the remote in the network tree and select Apply ConfigurationReliable
Both (TCP) to download the configuration change.

6. Using the CA Foundry, connect to the remote and issue the X.509 certificate. (See
Certifying a Host on page401 for details.)
7. Once the remote has its certificate:
a. Return to the remote configuration dialog box, clear the Disable Authentication
check box, and click OK.
b. Perform Step 5 again to send the apply the configuration change.

400

iBuilder User Guide

iDX Release 2.0

Logging On to a Certificate Authority

B.3.3 Certifying a Host

All hosts in an iDirect TRANSEC network must have X.509 public key certificates. Hosts include
the following network elements:

NMS servers

Protocol processor blades

TRANSEC line cards

TRANSEC remotes

You can use the procedure in this section to certify a new host or to update the certificate on
an existing host. Your NMS server must have IP connectivity to the host to issue a certificate.
Follow these steps to issue a certificate to a host.
1. Start the CA Foundry and log on to a CA according to the procedure on page398.
2. Use the arrow keys to select Host Operation from the top-level menu and press Enter.
3. Select Flush Host from the menu and press Enter.

Figure 355. Flushing a Host

Note:

Select Flush Host rather than Generate Host Key and Cert. The Flush Host
command performs all operations required to certify the host.

4. When prompted, enter the following host information:

a. Enter the IP address of the host you want to certify.
b. Accept the default port number by pressing Return.
c. Enter the password of the admin account of the host you want to certify.
The CA Foundry will issue a new X.509 certificate to the host, signed by your CA. Sample
output is shown in Figure 356.

Figure 356. CA Foundry Issuing a New X.509 Certificate

iBuilder User Guide

iDX Release 2.0

401

Logging On to a Certificate Authority

B.3.4 Revoking a Remotes Certificate

The procedure in this section describes how to revoke a remotes X.509 certificate and force
the remote to exit the TRANSEC network. Updating the keys twice at the end of the
procedure forces the remote to leave the network, since certificates are validated after each
key update.
Follow these steps to revoke a remotes X.509 certificate:
1. Using iBuilder, right-click the remote in the Network Tree and select View
PropertiesItem.
2. Note the number in Derived ID field of the remote Information tab.

Figure 357. Determining the Derived ID in iBuilder

3. Start the CA Foundry and log on to a CA according to the procedure on page398.
4. Use the arrow keys to select Maintenance from the top-level menu and press Enter.
5. Select Show Issued Certs from the Maintenance menu and press Enter.

Figure 358. Determining Certificates Issued by a CA

6. In the Subject field of the command output, note the highest CA serial number that
matches the DID determined in Step 1. (In the case that the CA has multiple certificates
for a single remote, the one with the highest serial number is the certificate currently in
use.)

402

iBuilder User Guide

iDX Release 2.0

Logging On to a Certificate Authority

Figure 359. Listing of Issued Certificates

7. Select Revoke Certificate from the Maintenance menu and press Enter.
8. At the prompt, enter the serial number of the certificate to be revoked as determined in
Step 6 and press Enter. Sample output is shown in Figure 360.

Figure 360. Revoking a Certificate

9. For each Protocol Process Blade in the remotes network:
a. Select Update Chain of Trust from the Host Operation menu and press Enter.
Respond to the prompts as follows:

iBuilder User Guide

iDX Release 2.0

Enter the IP address of the blade.

Accept the default port number by pressing Return.

For host password, enter the password of the blades admin account.

403

Updating the Network Keys

Sample results of this command are shown in Figure 361.

Figure 361. Updating the Chain of Trust

The updated blades will no longer allow the remote to enter the TRANSEC network. If you
want to ensure that the remote leaves the network immediately, you should force two
updates to the TRANSEC network keys. The procedure for updating the keys is documented in
the next section.

B.4

Updating the Network Keys

This section describes the procedure for forcing an update of the encryption keys used by your
TRANSEC network. Although keys are updated on a regular basis, you may want to force key
updates after you have revoked a remotes X.509 certificate in order to force the remote to
leave the network immediately. Because of the specifics of iDirects key management
protocol, you must update the keys twice to ensure that a remote that has had its certificate
revoked no longer has a valid key. For details on the TRANSEC key management protocol, see
the iDirect Technical Reference Guide.
Follow these steps to update the network keys in a TRANSEC network:
1. Check each protocol processor blade in the remotes network until you find the blade
responsible for key distribution as follows:
a. Using iMonitor, right-click the blade in the Network Tree and select Connect.

b. Log on to the root account of the blade.

c. At the command line, enter the following command:
telnet 0 13255

404

iBuilder User Guide

iDX Release 2.0

Updating the Network Keys

d. At the prompt, log on to the admin account.

Figure 362. Logging On to the Root Account of a PP Blade

e. From the command line, enter the following command, including the semi-colon.
sarmt;
f.

Enter the command:

net * status
If this blade is responsible for key distribution, the command output of this command
will indicate that multicast is supported.

Figure 363. Determining the Network ID on a PP Blade

g. Note the Network ID indicated in the net * status command. (The Network ID in
Figure 363 is 1.)
2. On the blade that supports multicast:
a. Enter the following commands to enable security commands and update the network
keys:
csp enable
key_ctrl net <net id> update
where <net id> is the network ID determined in the previous step.
b. Repeat the key_ctrl command to ensure that no unauthorized hosts have a valid
key.

iBuilder User Guide

iDX Release 2.0

405

Updating the Network Keys

406

iBuilder User Guide

iDX Release 2.0

Adding Beams to the Beam Map File

Appendix C Configuring
Networks for Automatic
Beam Selection

Beginning with iDS Release 7.0, iDirect remotes are no longer restricted to a single network.
Customers can define remotes that roam from network to network around the globe. These
roaming remotes are not constrained to a single location or limited to any geographic region.
Instead, by using the capabilities provided by the iDirect Global NMS feature, remote
terminals have true global IP access.
The decision of which network a particular remote joins is made by the remote. When joining
a new network, the remote must re-point its antenna to receive a new beam and tune to a
new outroute. Selection of the new beam can be performed manually (using remote modem
console commands) or automatically. This appendix documents the procedure you should
follow to enable the Automatic Beam Selection (ABS) feature for your mobile remotes in a
maritime environment. A technical description of this feature, including all prerequisites for
implementing ABS in your network, is contained in the iDirect Technical Reference Guide.
This appendix contains the following major sections:

C.1

Adding Beams to the Beam Map File on page407

Configuring Remotes for Automatic Beam Selection on page409

Remote Custom Keys for Automatic Beam Switching on page412

Remote Console Commands on page416

Adding Beams to the Beam Map File

To determine the best beam for the current remote location, the modem relies on a beam
map file that is downloaded from the NMS to the remote and stored on the modem. iDirect
provides a utility that converts the beam information supplied by your satellite provider into a
beam map file that can be used by the iDirect system. Adding a new beam requires a new
conveyance beam map file from your satellite provider that includes all beams. For a detailed
discussion of this topic, see the iDirect Technical Reference Guide.

iBuilder User Guide

iDX Release 2.0

407

Adding Beams to the Beam Map File

You must execute the procedure in this section during the initial set up of the ABS feature for
your network. Re-execute the procedure any time you need to add a new beam to your beam
map file.
Note:

When you add a new beam, the beam name used in the conveyance beam map
file must exactly match the name of the network configured for that beam in
iBuilder. For example, if a beam name in the conveyance file is Beam_10, then
the name configured in the iBuilder tree for the corresponding network must
also be Beam_10.

The satellite provider delivers conveyance beam map files to the customer in a pre-defined
format. This format is defined in a specification document agreed upon between the beam
provider and iDirect. iDirect provides each ABS customer with a software utility that converts
the conveyance beam map files into a format that is usable by the NMS. Once the conversion
is complete and the NMS map server is restarted, the new beam becomes available for the
map server to send to remotes using ABS.
Follow these steps to convert a conveyance beam map file from your satellite provider into
the map server format and make it available for use in your networks.
1. Log on to the map server machine as root.
2. Change to the map server directory:
# cd /etc/idirect/map
3. Copy the conveyance beam map file into the /etc/idirect/map directory using an
appropriate form of file transfer such as CD-ROM or WinSCP.
4. Copy the conveyance beam map file to the file name curr.in with the following
command:
# cp <conveyance file name> curr.in
where <conveyance file name> is the name of the conveyance beam map file.
5. Run the newmap conversion utility by entering the following command at the command
line prompt:
# newmap
6. Wait until the conversion is complete.
7. Start the map server by entering the following command:
# service idirect_nms restart mapsvr

408

iBuilder User Guide

iDX Release 2.0

Configuring Remotes for Automatic Beam Selection

C.2

Configuring Remotes for Automatic Beam

Selection
In order to use iDirects Automatic Beam Selection (ABS) feature, you must install and
configure your remotes to use one of the supported antennas. The following antennas are
supported:

Orbit-Marine AL-7104

Schlumberger Spacetrack 4000

SeaTel DAC-97 (Also supports the DAC-03, DAC-2200, and DAC-2202)

In addition to the antennas listed above, iDirect supports the OpenAMIP protocol as defined in
the document titled Open Antenna Modem Interface Protocol (AMIP) Specification. This
section explains how to configure your ABS networks for any of the supported antennas or for
use with OpenAMIP.
When you configure your remote in iBuilder, you must select an Antenna Reflector on the
Remote VSAT tab. The selected reflector must be configured to use a supported Antenna
Controller. Reflectors for all supported controllable antennas are pre-defined in the iBuilder
database. You can also create your own controllable antenna reflector by checking
Controllable in the Reflector dialog box and, and then selecting the Controller Type that is
compatible with your antenna.
Figure 364 shows an antenna reflector definition for a SeaTel DAC antenna. Notice in the
figure that Controllable is selected, along with the SeaTel DAC Controller Type, indicating
that the antenna can be controlled by the modem and uses one of the SeaTel DAC controller
variants.

Figure 364. Orbit-Marine AL-7104 Reflector Definition

Note:

The Elevation and Gain parameters are not used in this release.

Follow these steps to configure your remote for Automatic Beam Selection:
1. In iBuilder, right-click the remote and select ModifyItem.

iBuilder User Guide

iDX Release 2.0

409

Configuring Remotes for Automatic Beam Selection

2. When the remotes Modify Configuration dialog box is displayed, click the VSAT tab.

Figure 365. Remote Antenna Settings with General ABS Fields

3. In the Remote Antenna section of the dialog box, enter the antenna components for your
antenna. (For a description of the fields in the left-hand column of Figure 365, see
Remote VSAT Tab on page169.) To enable ABS for this remote, you must select a
Reflector that uses one of the following Controller Types: Orbit SBC, Schlumberger,
Spacetrack 400, SeaTel DAC or OpenAMIP. The following such reflectors are predefined in
the iBuilder tree:
Spacetrack 4000 for Schlumberger Spacetrack 4000

DAC-97 (used for any supported SeaTel DAC antenna controller: DAC-97 DAC-03, DAC2200, or DAC-2202)

AL-7104 for the Orbit-Marine AL-7104

OpenAMIP. (An open antenna controller protocol developed by iDirect.)

When you select one of these reflectors on the Remote VSAT tab, the ABS configuration
fields appear on the right of the Remote Antenna section of the screen. The second and
third columns of Figure 365 show the fields that apply to all ABS antennas. Additional
fields appear on the bottom right of the screen when you select the DAC-97, Al-7104 or
OpenAMIP. Those additional fields are discussed later in this section.
Note:

You will not see the ABS-specific fields on the right-hand side of this screen
until you have selected a controllable Reflector.

4. Enter the IP address (Antenna Address) and port number (Antenna Port) of the antenna
on the remote LAN. This addressing is required for the remote modem to communicate
with the antenna controller.
5. In Hunt Frequency, enter the L-Band hunt frequency to be programmed into the antenna
controller. This frequency may be different for different instances of your roaming
remote, depending on the beam in which that remote instance is defined.
Note:

Noise Reference Frequency is currently not used.

6. In Rx Polarization, select the polarization of the remotes receive carrier.

7. In Tx Polarization, select the polarization of the remotes transmit carrier.

410

iBuilder User Guide

iDX Release 2.0

Configuring Remotes for Automatic Beam Selection

8. Enter a value for Connect Timeout. This is the number of seconds the remote modem
waits to reconnect to the antenna controller if the connection is lost. The default timeout
is 30 seconds.
Note:

Init Tx Power Offset is not supported in this release.

Figure 366 shows the additional fields that appear on the VSAT tab if you select OpenAMIP,
DAC-97 or AL-7104 as your antenna.

Figure 366. OpenAMIP, SeaTel and Orbit SBC Antenna Parameters

9. If you select a reflector configured to use the OpenAMIP controller type, the OpenAMIP
parameters shown on the left of Figure 366 appear on the VSAT tab. To configure these
parameters:
a. In Tx Frequency, enter the center frequency of your transmit carrier.
b. In Tx Bandwidth, enter the width of you transmit carrier.
c. In Hunt Bandwidth, enter the width of the Hunt Frequency.
d. In Tx Local Oscillator, enter the frequency of your transmit local oscillator. This
should match the Frequency Translation field configured for the remotes BUC.
e. In Rx Local Oscillator, enter the frequency of your receive local oscillator. This should
match the Frequency Translation field configured for the remotes LNB.
10. The SeaTel DAC controller type should be used for any of the four SeaTel antenna
controllers supported by the ABS feature. If you select a reflector configured to use the
SeaTel DAC controller type (such as DAC-97), the SeaTel parameters shown in the center
of Figure 366 appear on the VSAT tab. To configure these parameters:
a. Select the LNB Voltage. This is the nominal voltage being supplied by external
equipment to the LNB. You can select either 13V or 18V. The default value is 18V.
b. Select 22 KHz Tone to tell the antenna controller to enable the 22 KHz tone to the
LNB.
c. DAC 97 distinguishes a SeaTel DAC-97 from the other supported SeaTel DAC variants
(DAC-03, DAC-2200, or DAC-2202). Select this check box only if using a DAC 97
antenna controller.
d. Enter the NID. This is the Network ID of the DVB carrier specified by the Hunt
Frequency and Hunt Polarity.
e. Enter a value for DVB_FEC. This is the FEC rate of the DVB carrier specified by the
Hunt Frequency and Hunt Polarity.
11. If you select a reflector configured to use the Orbit SBC controller type (such as AL-7104),
the Orbit SBC parameters shown on the right of Figure 366 appear on the VSAT tab. To
configure these parameters:

iBuilder User Guide

iDX Release 2.0

411

Remote Custom Keys for Automatic Beam Switching

a. Select the LNB Voltage. This is the nominal voltage being supplied by external
equipment to the LNB. You can select either 13V or 18V. The default value is 18V.
b. Select 22 KHz Tone to tell the antenna controller to enable the 22 KHz tone to the
LNB.

C.2.1 Changing the Minimum Look Angle

You are no longer required to define a custom key to change the minimum look angle for a
mobile remote. Instead, you can change the default minimum look angle used for all remote
antennas associated with a satellite on the Spacecraft dialog box. You can override this
setting for specific remotes on the Remote Geo Location Tab. See Adding a Spacecraft on
page69 and Remote Geo Location Tab on page167 for details.
If, for previous releases of the ABS feature, you have defined the remote-side min_look_angle
custom key for any remotes in your network, you should delete each custom key and override
the setting on the Remote Geo Location tab instead. This will prevent the custom key from
inadvertently overwriting your intended setting if you change the minimum look angle on the
Geo Location tab in the future.

C.3

Remote Custom Keys for Automatic Beam

Switching
There are a number of custom keys that you can define to control the behavior of your
remotes during Automatic Beam Switching. All the custom keys discussed here must be
configured in the Remote-side Configuration area of the remote Custom tab.

WARNING! Custom keys in the [BEAMS] group must be applied to the remote in each of
the remotes networks. If these changes are applied to some, but not all,
remote instances, all the beam information on the remote will be lost and
the remote will no longer be operational. See Configuring the Network
Acquisition Timers on page414 and Changing the Download Timeout on
page414.
The general steps for configuring the custom keys defined in this section are:
1. In iBuilder, right-click the remote and select ModifyItem.
2. Click the Custom tab.
3. In the Remote-side Configuration section of the screen, configure the custom key. (See
the subsections below for definitions.)
4. Click OK to save your changes.

412

iBuilder User Guide

iDX Release 2.0

Remote Custom Keys for Automatic Beam Switching

5. For each of the remotes networks, right-click the remote in the iBuilder tree and select
Apply ConfigurationReliable Remote-Side (TCP).

The example in this figure changes the remotes net_state_timeout (discussed below) to six
minutes. The same general steps can be used to define any of the custom keys described in
the remainder of this section.

Figure 367. Changing a Remotes net_state_timeout

iBuilder User Guide

iDX Release 2.0

413

Remote Custom Keys for Automatic Beam Switching

C.3.1 Configuring the Network Acquisition Timers

The following custom keys determine how a remote behaves when it attempts, but fails, to
join a network:
Table 10. Net State Timer Custom Keys
Custom Key Name

Default Value

Meaning

net_state_timeout

300 seconds
(5 minutes)

Time the remote waits between attempts to switch

if the remote fails to join the new network.

net_state_timeout_increment

300 seconds
(5 minutes)

Time added to current value for net_state_timeout

each time the remote fails to join the network.

net_state_timeout_max

3600 seconds
(60 minutes)

The highest value net_state_timeout is allowed to

reach when increments are added.

These timers work together as follows:

After the first failure, the remote waits net_state_timeout before it again attempts to
join the network.

After each subsequent failure, the remote adds net_state_timeout_increment to the

current value of net_state_timeout, successively increasing the wait time before each
new attempt.

If net_state_timeout reaches net_state_timeout_max, the remote will not further

increase net_state_timeout.

Once the remote successfully joins a network, the remote resets net_state_timeout to its
configured value.

To configure a net_state timer, enter a remote-side custom key of the form:

[BEAMS]
<custom key> = <timeout>
where <custom key> is one of the custom key names in Table 10 and <timeout> is the
value of the timer, in seconds.

WARNING! You must apply these custom keys to all instances of the remote.

C.3.2 Changing the Download Timeout

The remote-side custom key download_timeout determines how long a remote will wait to
switch beams if an image download is in progress. The remote will not attempt to switch
unless one of the following conditions is true:

The image download completes, or

The download_timeout expires

The default value for download_timeout is 900 seconds (15 minutes).

414

iBuilder User Guide

iDX Release 2.0

Remote Custom Keys for Automatic Beam Switching

To change the download timeout, enter a remote-side custom key of the form:
[BEAMS]
download_timeout = <timeout>
where <timeout> is the value of the download timeout, in seconds.

WARNING! You must apply these custom keys to all instances of the remote.

C.3.3 Disabling Beam Switching to Zero-Quality Beams

By default, a remote modem always attempts to join any beam included in the beam map file
if that beam is determined to be the best choice available. This includes beams with a quality
value of zero for the remotes current location.
Beginning with iDX Release 2.0.1, you can configure your remotes so that they never attempt
to join a beam if the quality of the beam at the current location is zero. To configure a
remote to never attempt to join beams with a quality value of zero, enter a remote-side
custom key of the form:
[BEAMS]
beam_unuse_zero = <value>
where a <value> of 0 means use zero-quality beams and a <value> of 1means do not use
zero-quality beams.

WARNING! You must apply this custom keys to all instances of the remote.

iBuilder User Guide

iDX Release 2.0

415

Remote Console Commands

C.4

Remote Console Commands

The four remote console commands described in this section can be used to observe ABS
operation on individual remotes. Two of the commands (tlev and latlong) are applicable
to all iDirect remote modems. The remaining two commands (beamselector and
antenna debug) are specific to the ABS feature.

C.4.1 latlong
The latlong command displays the current latitude and longitude of the remote. It also
displays the word muted if the current satellite is below the configured minimum look angle.
The precision of the values returned by the latlong command is greater than or equal to the
precision of the values returned to the remote by the antenna controller. (By contrast, the
precision sent to the NMS is in hundredths of a degree to maintain backward compatibility
with the location event format.) The latlong command is convenient when you do not want
to wait for the next location event, since the location event interval is set to five minutes by
default.
Syntax:
latlong
Example:
Figure 368 shows an example of the latlong command.

Figure 368. latlong Command Example

C.4.2 tlev
The tlev command sets or reads the system's global trace level.
Although there are seven trace levels, level 4 is the highest level that can be used effectively
under normal operations. At level 4, the various ABS state machines trace all state
transitions. Each time an event occurs, the name of the state machine, the current state, and
the name of the event are displayed on the screen. This provides the analyst with a clear view
of the sequence of events occurring in the software.
Syntax:

416

tlev

Reads the trace level

tlev 0

Sets the trace level to normal, tracing critical events only.

iBuilder User Guide

iDX Release 2.0

Remote Console Commands

tlev 4

Sets the trace level to the highest trace level that is practical during normal
operations

tlev 7

Sets the trace level too high to be usable during normal operations

Example:
Figure 369 shows an example of the tlev command. The command in the example sets the
trace level to 4.

Figure 369. tlev Command Example

C.4.3 antenna debug

The antenna debug command sets the trace level for the antenna client subsystem,
including the state machines. There are four different sets of traces, each with seven
different levels. In practice, except for rare debugging situations in the lab, antenna debug
should be used to either enable or disable all antenna traces.
Among other things, the antenna tracing displays all commands to the antenna and all
responses received from the antenna. These commands and responses can be understood by
reading the antenna controller documentation.
Note:

The antenna debug command works for all types of antennas supported by
ABS. However, the tracing for each antenna type differs dramatically because
the controller interface for each antenna type is unique.

Syntax:
antenna debug 7 7 7 7

Enables all antenna traces

antenna debug 0 0 0 0

Disables all antenna traces

Spaces are required between digits when setting the trace level.

iBuilder User Guide

iDX Release 2.0

417

Remote Console Commands

Example:
Figure 370 shows the trace output after the antenna debug command has been issued to
enable all antenna tracing.

Figure 370. antenna debug Command Example

C.4.4 beamselector
Depending on the command line argument, the beamselector command can be used either
to list the set of beams available to the remote or to switch the remote from its current beam
to a new beam.
When using the list argument, the command displays the beam number and the beam name
for each beam in the current set of beams available in the options file. It also indicates which
beam is currently selected and which, if any, of these available beams are unknown to the
map server that provided the current map. A beam that is in the options file but unknown to
the current map server is listed as not in map.
Note:

Not in map indicates that the modem does not have a map from a map server
that knows about the beam. In other words, the name of the beam in the
options file does not match the name of any beam in the map being sent to the
modem by the map server.

When using the switch argument, the beamselector command allows the operator to
initiate a beam switch. For example, the command beamselector switch 5 commands
the modem to switch from its current beam to beam 5. Once the command is issued, the
remote will reset and attempt to use the new beam. The beam numbers may be determined
by issuing a beamselector list command.
This form of the command will not permit you to switch to a beam unless that beam is both in
the map and in the current options file. If you are sure you want to switch to a beam that is
unknown or that is not in the map, you must use the -f (or force) option.

418

iBuilder User Guide

iDX Release 2.0

Remote Console Commands

Syntax:
beamselector list Displays all beams available to this remote as defined in the
remote options file.
beamselector switch <beam number> Switches the remote to the beam indicated
by beam number.
beamselector switch <beam number> -f Forces the remote to switch to the beam
indicated by beam number, even if that beam is not in the map.

WARNING! Executing the beamselector switch command is a service-affecting

operation.
beamselector lock <beam number> This command is used during commissioning to
prevent the modem from attempting to switch beams every net_state_timeout
when not locked. (See Configuring the Network Acquisition Timers on page414.)
The modem must be restarted after commissioning to return to normal operation.
Example:
Figure 371 shows the results of the beamselector list command. The remote has four
beams configured in its options file. Beam 2 is the current beam.
Note:

The beam names displayed by this command are identical to the beam names in
the conveyance beam map file supplied by the satellite provider, as well as to
the corresponding network names configured in iBuilder.

Figure 371. beamselector list Command Example

iBuilder User Guide

iDX Release 2.0

419

Remote Console Commands

Figure 372 shows the results of the beamselector switch command.

Figure 372. beamselector switch Command Example

420

iBuilder User Guide

iDX Release 2.0

iDirects Traditional Remote Locking

Appendix D Remote
Locking

The remote lock feature allows individual remotes to be locked to a particular network. Once
a remote is locked with a key, it only functions in a network with the same key.
There are two types of Remote Locking supported in iDirect networks:

D.1

iDirects Traditional Remote Locking is supported for iNFINITI remotes and Evolution e8350
remotes. It is described in iDirects Traditional Remote Locking on page421.

Enhanced Remote Locking is only supported for Evolution X3 remotes. It is described in

Enhanced Remote Locking on page424.

iDirects Traditional Remote Locking

iDirects Traditional Remote Locking is supported for iNFINITI remotes and Evolution e8350
remotes. Once a remote is locked with a key, it only functions in a network with the same key.

D.1.1 Locking a Remote Using Traditional Remote Locking

You must perform the following steps to lock a remote to a network.
1. Populate the network key at the network level in iBuilder, and apply the changes.
2. Open a console session to each remote that needs to be locked, and use the rmtlock
command to lock the remote to the network.
3. Enter the rmtlock command with the status argument to verify the status of the
remote lock.
The steps for performing these operations are detailed in the following sections.

iBuilder User Guide

iDX Release 2.0

421

iDirects Traditional Remote Locking

Configuring the Network Key

You must create a custom key to configure the network key used to lock the remotes to that
network. The network key is from 1 to 64 alphanumeric characters and is configured at the
network level in iBuilder.
The custom key is defined as follows:
[NETWORK_DEFINITION]
net_key = <Network Key>
Where <Network Key> is the Network Key.
Once you have configured the custom key in iBuilder, apply the changes to your network.
Note:

In order to implement remote locking on a network, a Network Key must first be

generated by the network operator and then propagated to each remote in the
network by applying the changes to the network.

During operation, if the remote receives a Network Key message containing a Network Key
that is different than the one set on the remote, the remote immediately stops sending
upstream messages. If the remote cannot join the network, the following message is
displayed:
This Remote CANNOT operate in this NETWORK

Setting the Remote Lock

The rmtlock console command is used to lock a remote to the network. A password is
required to prevent unauthorized modification of the key. This command also lets you unlock
the remote when the correct password is provided.
Enter the following command to lock the remote to the network key with a password:
rmtlock lock <network key> <password>
Where: <network key> is the network key you defined for your network.
<password> is the password you assign the remote.
Passwords must be 8 to 12 characters in length and conform to password security
recommendations.
When the rmtlock command is used to change the network key and password, it must match
the previously-set password. You must unlock the remote before moving the remote from one
network to another network.

Checking Remote Locking Status

You can check the status of the locking state on the remote by entering the rmtlock
command with the status argument:
rmtlock status
Examples of output from the rmtlock status command:
engaged

The Remote is locked to the network.

not engaged The Remote is not locked to the network.

422

iBuilder User Guide

iDX Release 2.0

iDirects Traditional Remote Locking

D.1.2 Unlocking a Remote Using a Valid Password

The following command unlocks the remote (using a valid password):
rmtlock unlock <password>
Where: <password> is the valid password previously assigned to the remote.
The Network Key resets to the wildcard, allowing access to any network.

WARNING! Since the NMS does not store the password, it is the network operators
responsibility to maintain the list of passwords for your networks.

WARNING! If a password is lost, you must contact the iDirect TAC for assistance. The
TAC will validate the ownership of the unit in question before the default
password is given to the requestor.

D.1.3 Remote Lock Tampering

Attempts to defeat the remote lock without the password will cause the remote to stop
functioning. If the remote has been tampered with in an attempt to bypass the lock, you must
return the remote to iDirect using standard RMA procedures.

D.1.4 Requesting a Default Remote Password

If you lose your password and need to reset it for a specific remote, the following procedure
must be followed in order to receive a new default password from the TAC.
1. You must submit a list of authorized personnel from within your organization that are
allowed to request and receive default password information.
2. You must sends a default remote password request in writing to the TAC (via email) that
includes:
a. Serial number of the remote
b. Type of remote
c. DID of the remote (as seen in iBuilder)
3. TAC verifies the ownership of the specific remote(s), which may require additional
information from the Network Operator.
4. Once ownership is verified, TAC creates and emails the default password for each specific
remote to the requestor.
Note:

iBuilder User Guide

iDX Release 2.0

The above procedure requires iDirect internal verification and management

approval. It may take several business days to complete.

423

Enhanced Remote Locking

D.2

Enhanced Remote Locking

Enhanced Remote Locking is only supported for Evolution X3 remotes.
Enhanced remote locking strengthens iDirects Traditional Remote Locking with the use of
symmetric key generation. A unique and secure Locking Key is generated for each remote,
using a combination of the Network Key and a randomly generated Confirmation Word for
each remote. Enhanced remote locking also adds a hardening option to persistently save
the Locking Key on the remote.
Remote locking is similar to locking a cell phone to a cellular network. It is performed at the
operators own risk. Non-Warranty RMA charges of $250 (plus all shipping) apply to all remotes
returned to iDirect for the purpose of removing a network lock. Please refer to Non-Warranty
RMA Required to Remove Locks on page427.

D.2.1 Soft Locking versus Hard Locking

Enhanced Remote Locking includes the choice of two levels of remote locking using the
rmtlock console command:

Soft Locks: You can use the rmtlock engage command to set a Soft Lock on a remote.
When the command is first entered, a randomly-generated Confirmation Word is
displayed to the operator on the remote console. After re-entering the command with the
Confirmation Word to confirm the lock, the Soft Lock is set on the remote. A remote
locked with a Soft Lock can be unlocked. You can remove the Soft Lock by re-entering the
rmtlock command with the disengage option and providing the same Confirmation
Word.

Hard Locks: Once a remote is soft locked to a network, you can use the rmtlock
command to irrevocably burn the remotes Locking Key into the remote hardware using
the same Confirmation Word that was generated for the Soft Lock. After a Hard Lock has
been burned into the remote, only a Non-Warranty RMA hardware replacement can
remove the Hard Lock. Please refer to warning notes in Setting a Hard Lock on
page426.

Note:

You must first Soft Lock a remote to a network before you can Hard Lock that
remote.

D.2.2 Locking a Remote Using Enhanced Remote Locking

You must perform the following steps to lock remotes to a network.
1. Populate the Network Key at the Network level in iBuilder, and apply the changes.
2. Open a console session to each remote that needs to be locked, and use the rmtlock
command at the remote console to configure a Soft Lock on the remote.
3. Enter the rmtlock command with the status argument to verify the status of the lock.
4. If you want to hard lock the remote, use the rmtlock command at the remote console to
configure the Hard Lock.
5. Enter the rmtlock command with the status argument to verify the status of the lock.
The procedures for performing these operations are detailed in the following sections.

424

iBuilder User Guide

iDX Release 2.0

Enhanced Remote Locking

Configuring the Network Key

You must create a custom key to configure the Network Key used to lock the remotes to the
network. The network key is from 1 to 64 alphanumeric characters and is configured on the
Custom Tab of your network in iBuilder.
The custom key is defined as follows:
[NETWORK_DEFINITION]
net_key = <Network Key>
Where <Network Key> is the Network Key.
Once you have configured the custom key in iBuilder, apply the changes to your network.
Note:

In order to implement remote locking on a network, a Network Key must first be

generated by the network operator and then propagated to each remote in the
network by applying the changes to the network.

During operation, if a locked remote receives a Network Key message containing a Network
Key that is different than the one set on the remote, the remote immediately stops sending
upstream messages. If the remote cannot join the network, the following message is
displayed:
This Remote CANNOT operate in this network!

Setting a Soft Lock

To set a Soft Lock on a remote:
1. Enter the rmtlock command with the engage argument:
rmtlock engage <netkey>
Where <netkey> is the Network Key of the network to which the remote will be locked.
The following warning message is displayed, which includes the Confirmation Word:
The confirmation word is: DIFEWdsf
Please type:
rmtlock engage <netkey> <confirmation word>
to confirm.
WARNING: Remote lock will be engaged. Make sure the network key
is correct. Keep the confirmation word safe. If the remote has to
be disengaged, the confirmation word will be needed. If you lose
the confirmation word, you will not be able to disengage the
lock. In order to unlock the unit will have to be returned to
iDirect under Non-Warranty Repair.
You have 60 seconds to confirm it.
Note:

As a convenience, you can enter the rmtlock verify command to display the
Network Key configured for the remote.

2. Record the Confirmation Word. The Confirmation Word is required to remove the Soft
Lock or to set a Hard Lock on the remote.

iBuilder User Guide

iDX Release 2.0

425

Enhanced Remote Locking

3. Within 60 seconds of performing Step 1, confirm the Soft Lock by re-entering the
rmtlock command followed by the Confirmation Word:
rmtlock engage <netkey> <confirmation word>

Removing a Soft Lock

To remove a Soft Lock on a remote, enter the rmtlock command with the disengage
argument followed by the Confirmation Word that was generated when the Soft Lock was set
on the remote:
rmtlock disengage <confirmation_word>
After executing this command, the remote is no longer locked to the network.

Setting a Hard Lock

You must set a Soft Lock on a remote before you can set a Hard Lock on that remote. The
Confirmation Word generated when you set the Soft Lock is required to set the Hard Lock. The
Network Key is not required to set the Hard Lock. When you set the Hard Lock, the remote
will be permanently locked to the network. You cannot remove the Hard Lock from the
remote.
To set a Hard Lock on a remote:
1. Enter the rmtlock command with the burn argument:
rmtlock burn
The following warning message is displayed:
Please type:
rmtlock burn <confirmation word>
to confirm.
WARNING: Remote lock will be burned into the hardware. This lock
cannot be changed or removed once burned. In order to unlock the
unit will have to be returned to iDirect under Non-Warranty
Repair.
You have 60 seconds to confirm it.

WARNING! The following command will permanently lock the remote to the Network.
Only a hardware replacement can reverse this lock.
2. Within 60 seconds of performing Step 1, repeat the rmtlock burn command with the
Confirmation Word appended. This is the Confirmation Word that was generated when you
set the Soft Lock on this remote.
rmtlock burn <confirmation_word>

WARNING! If the Locking Key is burned into the remote hardware using the Hard Lock
option, the remote can only function in a network with the Network Key
associated with the Hard Lock. From this point forward, the lock is
permanent and the Locking Key can only be removed with a Non-Warranty
RMA hardware replacement.

426

iBuilder User Guide

iDX Release 2.0

Enhanced Remote Locking

Checking Remote Locking Status

You can check the status of the locking state on the remote by entering the rmtlock
command with the status argument:
rmtlock status
This command displays the current locking state of the remote as one of the following:
engaged
not engaged
permanently engaged

D.2.3 Non-Warranty RMA Required to Remove Locks

Losing the Confirmation Word for a Soft Lock or removing a Hard Lock on a remote requires
the remote modem to be returned to iDirect under Non-Warranty Repair.

You must know the Confirmation Word to remove a Soft Lock. If you lose the Confirmation
Word, you will not be able to disengage the Soft Lock. In order to unlock the remote, you
must return it to iDirect for a Non-Warranty RMA hardware replacement.

You cannot change or remove a Hard Lock on a remote. In order to unlock the remote, you
must return it to iDirect for a Non-Warranty RMA hardware replacement.

WARNING! RMA charges of $250 (plus all shipping) will apply to all remotes returned to
iDirect for the purpose of removing a network lock.

iBuilder User Guide

iDX Release 2.0

427

Enhanced Remote Locking

428

iBuilder User Guide

iDX Release 2.0

Glossary of Terms
Acquisition

A process whereby the satellite modem locks onto the proper satellite carrier.

ACU

Antenna control unit.

ADC

Analog-to-Digital Converter. A device that converts analog signals to a digital

representation.

Analog

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

the wave form of the electromagnetic current. An analog signal is responsive to
changes in light, sound, heat and pressure. See also digital.

Antenna

Device for transmitting and receiving radio waves. Depending on their use and
operating frequency, the form on an antenna can change from a single piece of wire to
a dish-shaped device.

Antenna Alignment
(pointing)

The process of optimizing the orientation of a satellite antenna's main direction of

sensitivity towards the satellite to maximize the received signal level and to minimize
the chance of receiving unwanted interference from other satellite systems.

Aperture

A cross sectional area of the antenna which is exposed to the satellite signal.

Apogee

Point in an elliptical satellite orbit that is farthest from the surface of the earth.

Asynchronous

A communications strategy that uses start and stop bits to indicate the beginning and
end of a character, rather than using constant timing to transmit a series of characters.
Asynchronous methods are especially efficient when traffic comes in bursts (and not
regularly paced). Modems and terminals are asynchronous communications devices.

Attenuation

Weakening, usually measured in decibels, of a signal (loss) that occurs as it travels

through a device or transmission medium (e.g. radio waves through the atmosphere).

Attitude Control

The orientation of the satellite in relationship to the earth and the sun.

Azimuth

The horizontal co-ordinate used to align the antenna to the satellite. See also
Elevation.

Bandwidth

The amount of data a cable can carry; measured in bits per second (bps) for digital
signals, or in hertz (Hz) for analog signals. A voice transmission by telephone requires a
bandwidth of about 3000 cycles per channel (3KHz). A TV channel occupies a bandwidth
of 6 million cycles per second (6 MHz) in terrestrial systems. In satellite based systems
a larger bandwidth of 17.5 to 72 MHz is used to spread or dither the television signal
in order to prevent interference.

Baud

The number of times an electrical signal can be switched from one state to another
within a second.

Bit Error Rate

(BER)

The ratio of the number of information bits received in error to the total number of bits
received, averaged over a period of time. It is used as an overall measure of the quality
of a received digital bit stream.

Bit Rate

The number of bits transmitted within a second (bps) in a digital communication.

Broadcast

Sending a single message to all the nodes of a network.

C band

Band of frequencies used for satellite and terrestrial communications. Most

communications satellites use a range from 4 to 6 gigahertz (billion cycles per second).
Requires larger ground antennas, usually twelve feet in diameter, for television
reception.

iBuilder User Guide

iDX Release 2.0

429

Capacity

A proportion of the satellites bandwidth which is used to establish one or more

communication channel.

Carrier

The basic radio, television, or telephony transmit signal. The carrier in an analog
signal.

Carrier Frequency

The rate at which the carrier signal repeats, measured in cycles per second (Hertz).
This is the main frequency on which a voice, data, or video signal is sent. Microwave
and satellite communications transmitters operate between 1 to 14 GHz.

Channel

A band of radio frequencies assigned for a particular purpose, usually for the
establishment of one complete communication link, or a path for an electrical signal.
Television signals require a 6 MHz frequency band to carry all the necessary picture
detail. Channel frequencies are specified by governmental agencies.

CIR

See Committed Information Rate.

Coaxial Cable

A transmission line in which the inner conductor is completely surrounded by an outer

conductor, so that the inner and outer conductor are coaxially separated. The line has a
wide bandwidth capacity which can carry several television channels and hundreds of
voice channels.

Collocated
(satellites)

Two or more satellites occupying approximately the same geostationary orbital

position. To a small receiving antenna the satellites appear to be exactly at the same
place. The satellites are kept several kilometers apart in space to avoid collision.

Committed
Information Rate
(CIR)

The guaranteed network bandwidth availability.

Common Carrier

An organization which operates communications circuits. Common carriers include the

telephone companies as well as the owners of the communications satellites.

Communications
Satellite

A satellite in Earth orbit which receives signals from an Earth station and retransmits
the signal to other Earth stations.

COMSAT

Communication Satellite Corporation, the U.S. signatory for INTELSAT.

Continuous Wave
(CW)

Signal consisting of a single frequency especially used in testing satellite modems and
antennas.

Decibel (Db)

The standard unit used to express the ratio of two power levels. It is used in
communications to express either a gain or loss in power between the input and output
devices.

Decoder

A television set-top device that converts an electronically scrambled television picture

into a viewable signal.

Delay

The time it takes for a signal to go from the sending station through the satellite to the
receiving station (around one-quarter of a second).

Demodulator

A satellite receiver circuit which extracts or demodulates the desired signals from
the received carrier.

Digital

Representation of information as bits of data for transmission. Digital communications

technology permits higher transmission speeds and a lower error rate than analog
technology. As an analog signal is received and amplified at each repeater station, any
noise is also amplified. A digital signal, however, is detected and regenerated (not
amplified), and any noise is lost unless it corresponds to a value that the regenerator
interprets as digital signal.

Dish

Slang for parabolic antenna.

Downlink

The part of the satellite communications link that involves signal retransmission from
the satellite and reception on the ground. See also Uplink.

430

iBuilder User Guide

iDX Release 2.0

Downstream
Carrier

Downstream carrier (synonymous to outbound carrier) is the carrier from the Hub to
the remote modem, via the satellite.

Duplex

Two-way communications. The telephone line is full duplex in that both directions of
communication occur at the same time. Walkie-talkie communications is half-duplex
only one party may transmit at a time.

Earth Station

A combination of devices (antenna, receivers) used to receive a signal transmitted by

one or more satellites.

Elevation

The upward tilt (vertical coordinate) of a satellite antenna measured in degrees,

required to align the antenna with the communications satellite. See also Azimuth.

Elliptical Orbit

Orbits in which the satellite path describes an ellipse, with the Earth located at one
focus.

Encoder

A device used to electronically alter a signal so that it can only be understood on a

receiver equipped with a special decoder.

Equatorial Orbit

An orbit with a plane parallel to the Earths equator.

FEC

Forward Error Correction is an error correction method that adds redundant bits to a
bit stream, so that the receiver can detect and correct errors in transmission.

FEC Block

The basic FEC unit is a FEC block.

Feed

1) The transmission of video content from a distribution center.

2)The feed system of an antenna.

Focal Length

Distance from the center feed to the center of the dish.

Footprint

The geographic area over which a satellite antenna receives or directs its signals.

Free Slots

Slots left in the dynamic sub-frame after all stream, guaranteed (CIR) and preemptive
bandwidth requests are satisfied. Free slots are allocated to all VSATs (up or down),
except the master, in a round-robin fashion.

Frequency

The number of times that an alternating current goes through its complete cycle in one
second of time. One cycle per second is also referred to as one hertz.

Frequency
Coordination

A process designed to eliminate frequency interference between different satellite

systems or between terrestrial microwave systems and satellites.

Full duplex

Transmission that occurs in both directions simultaneously over the communications

media (e.g. telephone).

Geostationary
satellite

An satellite orbiting Earth at such speed that it appears to remain stationary with
respect to the earths surface. See also Clarke Orbit.

Geosynchronous
satellite

A satellite orbiting Earth at Earths rotational speed and at the same direction. A
satellite in geosynchronous orbit is known as a geosynchronous or geostationary
satellite. The orbit is synchronous because the satellite makes a revolution in about
24 hours. The satellites are about 35,800 kilometers (22,350 miles) above Earth, and
they appear to be stationary over a location.

Ground Segment

All the Earth stations that are operating within a particular satellite system or network.

Ground Station

A radio station, on or near the surface of the Earth, designed to transmit or receive
to/from a spacecraft.

Guaranteed
Bandwidth

The capability for transmitting continuously and reliably at a specified transmission

speed. The guarantee makes it possible to send time-dependent data (such as voice,
video, or multimedia) over the line.

Guaranteed Slots

Slots configured per VSAT and made available to that VSAT upon its request. When the
queue is depleted, these slots are taken away by the master and distributed to other
requesting VISNs as preemptive slots.

iBuilder User Guide

iDX Release 2.0

431

Guard Band
(guardband)

A thin frequency band used to separate bands (channels) in order to prevent

interference and signal leakage.

Guard Channel

Unused frequency space between carriers that prevents adjacent carriers from
interfering each other.

Half Duplex

A communications form in which transmissions can go in only one direction at a time.

With half-duplex operation, the entire bandwidth can be used for the transmission. In
contrast, full-duplex operation must split the bandwidth between the two directions.

High Band

The upper part of the Ku band downlink frequency range, from 11.7 GHz to 12.75 GHz.

HPA

High Power Amplifier. Earth station equipment that amplifies the transmit RF signal and
boosts it to a power level that is suitable for transmission over an earth-space link.

Hub RFT

Hub Radio Frequency Terminal - Equipment that includes the antenna, U/C (up
Converter), D/C (Down Converter) HPA, and LNA, which provides the up and down
conversion of signals in a satellite-based network.

IF

Intermediate Frequency. The frequency range 70 to140 MHz used for the distribution of
satellite signals from the LNB at the dish to the users satellite receiver. It is always
used in direct-to-home systems and is the most suitable for distribution of digital
signals in communal systems IF systems.

Inbound Carrier

See Upstream Carrier.

Inclination

The angle between the orbital plane of a satellite and the equatorial plane of the
Earth.

Indoor Unit (IDU)

The satellite modem and indoor devices (in contrast to outdoor units, ODU).

Information Rate

The user data rate including IP headers plus iDirect overhead. The downstream
overhead is approximately 2.75% of the information rate.

INTELSAT

International Telecommunications Satellite Organization. Agency that operates a

network of satellites for international transmissions.

Interfacility Link
(IFL)

The cable that connects the indoor unit with the outdoor unit.

Intermediate
Frequency (IF)

Generally, 70 MHz or 140 MHz.

Ka band

The frequency range from 18 GHz to 31 GHz.

Ku Band

Frequency range from 10.9 GHz to 17 GHz, increasingly used by communications

satellites. Requires smaller ground antennas, usually four feet (1.2 meter) in diameter.

L-Band

The frequency range from 0.5 GHz to 1.5 GHz.

LNA

Low Noise Amplifier The preamplifier between the antenna and the earth station
receiver. For maximum effectiveness, it should be located as near the antenna as
possible, and is usually attached directly to the antenna receive port.

LNB

Low Noise Block Converter is the converter on the down link that takes the Ku, Ka, or CBand signal from the satellite and converts it to a lower frequency (L-band) signal that
can be fed through the IFL cable to the modem.

Low Earth Orbit

(LEO) satellite

Satellites that are not stationary from a fixed point on earth and have the lowest orbit
of all communication satellites. Most handset-to-satellite systems are based on LEO
satellites using L-Band.

Low Noise
Amplifier (LNA)

The preamplifier between the antenna and the Earth station receiver. For maximum
effectiveness, it must be located as near the antenna as possible, and is usually
attached directly to the antenna receive port.

432

iBuilder User Guide

iDX Release 2.0

Margin

The amount of signal in dB by which the satellite system exceeds the minimum levels
required for operation.

Multiplexing

Techniques that allows a number of simultaneous transmissions to travel over a single

circuit.

ODU

Outdoor unit, such as an antenna dish.

Outbound Carrier

See Downstream Carrier.

Passband

The range of frequencies handled by a satellite translator or transponder.

Perigee

The point in a satellites orbit where it is closest to Earth.

Polarization

Design technique used to increase the capacity of the satellite transmission channels by
reusing the satellite transponder frequencies.

QPSK (Quadrature
Phase Shift Keying)

Digital modulation scheme used in transmission communications to allow increased

sending capacity.

Rain Outage

Loss of signal at Ku or Ka Band frequencies due to absorption and increased sky noise
temperature caused by heavy rainfall.

Satellite

A sophisticated electronic communications relay station orbiting 22,237 miles above

the equator moving in a fixed orbit at the same speed and direction of the Earth (about
7,000 m.p.h. east to west).

Satellite
Communications

The use of geostationary orbiting communication satellites to relay transmission from

one Earth station to another or to several Earth stations. It takes only three satellites to
cover the whole Earth.

Satellite Pass

Segment of orbit during which the satellite passes nearby and in the range of a
particular ground station.

Shared hub

Satellite communications operations center that is shared among several separate

network users; often used for VSAT operations.

Single-ChannelPer-Carrier (SCPC)

A method used to transmit a large number of signals over a single satellite transponder.

SNR

Signal to Noise Ratio - In analog and digital communications, signal-to-noise ratio, (S/N
or SNR), is a measure of signal strength relative to background noise. The ratio is
usually measured in decibels (dB).

Spillover

Satellite signal that falls on locations outside the beam patterns defined edge of
coverage.

Subcarrier

In satellite television transmission, the video picture is transmitted over the main
carrier. The corresponding audio is sent via an FM subcarrier. Some satellite
transponders carry as many as four special audio or data subcarriers.

Symbol Rate

Symbol Rate refers to the number of symbols that are transmitted in one second. From
the symbol rate, you can calculate the bandwidth (total number of bits per second) by
multiplying the bits per symbol times the symbol rate.

TDM (Time Division

Multiplexing)

A type of multiplexing where two or more channels of information are transmitted over
the same link by allocating a different time interval (slot or slice) for the
transmission of each channel. (i.e. the channels take turns to use the link.)

TDMA (Time
Division Multiple
Access)

A communications technique that uses a common channel (multipoint or broadcast) for

communications among multiple users by allocating unique time slots to different
users.

Transmission
Control Protocol

A protocol developed for the internet to get data from one network device to another;
TCP uses a retransmission strategy to ensure that data will not be lost in transmission.

(TCP)

iBuilder User Guide

iDX Release 2.0

433

Transmission Rate

Includes all over-the-air data. This includes the user data (information rate), iDirect
overhead, and FEC encoding bits.

Transponder

A device in a communications satellite that receives signals from the earth, translates
and amplifies them on another frequency, and then retransmits them.

UHF

Ultra High Frequency. Band in the 500-900 MHz range, including TV channels 14 through
83.

Uplink

The Earth station used to transmit signals to a satellite and the stream of signals going
up to the satellite.

Upstream

Upstream carrier (synonymous to inbound carrier) is the carrier from the remote
modem to the Hub, via the satellite.

Carrier
VHF

Very High Frequency, Refers to electromagnetic waves between approximately 54 MHz

and 300 MHz.

VSAT

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

434

iBuilder User Guide

iDX Release 2.0

Index

adding 92
BUC 169 to 170
button
accept changes 14
right mouse 25

A
ABS
see Automatic Beam Selection
accelerated GRE tunnels 158
acquisition aperture length 78
activating
remotes 275
active users pane 358
activity log 49 to 51
copying data from 51
list of selectable activities 49
viewing 49
antenna 65
antenna, adding 66
applying changes to roaming remotes 294
applying configurations 286
Automatic Beam Selection 407 to 420
adding beams to a network 407
antenna reflector definition 409
changing the minimum look angle 412
configuring a remote for 409
configuring hunt frequency 410
determining beam numbers 419
forcing a beam switch 418
IP address of antenna 410
remote console commands 416
setting download timeout 414
setting network acquisition timers 414
supported antennas 409
Automatic Beam Switching
see Automatic Beam Selection

B
bandwidth
adding 71
beam selection
see beam switching for mobile remotes; Automatic
Beam Selection
beam switching for roaming remotes 179
before you start
information needed 8
preparing equipment 8
blades

iBuilder User Guide

iDX Release 2.0

C
CA Foundry 395 to 405
connecting to a host 398
creating a CA 397
creating a certificate authority 397
executing 62, 396
issuing host certificates 401
logging on to a CA 398
navigating in 396
revoking host certificates 402
carrier
acquisition aperture length 78
adding downstream carrier 73
adding upstream 79
adding upstream carrier 76
defining an alternate downstream carrier 106
information rate 78
large block 78
small block 78
switching to an alternate downstream carrier 110
symbol rate 78
transmission rate 78
uplink/downlink center frequency 74, 77
carrier grooming 130
certificate authority, creating 397
chassis
adding the initial hub chassis 249
assigning line cards to slots 255
configuring an iSCPC chassis 252
configuring and controlling 252
daisy chaining
see also chassis group
described 266
limit on number of chassis 266
physical connection of 267
RCM interface 268
restrictions 266
EDAS vs MIDAS controller boards 249
four-slot chassis
configuring 255
enabling 10 MHz clock on a tx line card 258
enabling 22 KHz tone 258
enabling BUC voltage 258
enabling LNB voltage 258
limitation on DC voltage supplied by 4-IF chassis
258

435

LNB voltages supplied by chassis 258

selecting high or low LNB voltage 258
use of jumper between slots 4 and 5 256
use of slot 5 256
installing 8
permanently enabling chassis license downloads 62
rules for assigning line cards to slots 255
setting the IP address 249
sharing slots on more than one NMS 260
validating a chassis license 253
chassis group
see also chassis, daisy chaining
configuring 270
default jumper settings 272
ordering chassis within 273
choose details
feature 36
view 36
cloning
remotes 171
user accounts 357
CNO User Groups
adding and modifying 337
visibility and access 336
commissioning line cards
See hub commissioning 313
comparing configurations 284
compression
CRTP performance characteristics 183
enabling compression types on remotes 180
L2TP payload compression 183
RTP header compression performance characteristics 183
TCP payload compression 182
UDP header compression 182
UDP header compression performance characteristics 182
UDP payload compression 183
UDP payload compression compared to TCP payload
compression 183
configuration changes 33
accepting 47
configuration state 44
changing 46
configurations
changes on roaming remotes 292
comparing 284
deleting 281
downloading
canceling 288
chassis 289
line card 290

436

network 290
protocol processor 289
using revision server 301
modifying 281
saving
TCP vs. UDP 291
status 44
uploading last modified vs. existing 281
uploading multiple modified vs. existing 283
viewing 281
context menu button 25
converters
adding 67
CRTP 182
CRTP performance characteristics 183
customers
adding 147 to 148
listing on remotes 147

D
daisy chaining
see chassis, daisy chaining
database locking 363
deactivating
remote 275
details
choosing 36
choosing details feature 36
creating sets of 36
view 34
DHCP 153
distributors
adding 147 to 148
listing on remotes 147
DNS 152
down converter 65
adding 67
downloading
concurrently to remotes and hub 296
images
TCP 301
interactions 299
multicast 296
multiple images 297
out of network remotes 299
using revision server 301
downloading configurations 286
canceling 288
chassis 289
line card 290

iBuilder User Guide

iDX Release 2.0

network 290
protocol processor 289
DVB-S2
adjusting CCM network parameters 138
configuring network parameters 137
converting to DVB-S2 from SCPC 377
estimating Effective CIR and MIR for ACM outbound
202
estimating IP data rate for ACM outbound 81
fast fade algorithm 136
line card model types supported 102
network-level parameters defined 135
selecting a MODCOD range for ACM 75

E
elements 15

F
FEC blocks 76
find toolbar 29
Firmware
downloading to remotes and line cards 297
DVB-S2 vs. SCPC for Evolution hardware 298
Evolution line card package names 378
folders 15
adding entries 18
BUCs 15
customers 16
distributors 15 to 16
empty 16
Hub RFT components 16
LNBs 15
manufacturers 15
operators 16
QoS profiles 15
remote antenna components 15
top level of 18
four-slot chassis
see chassis, four-slot chassis
free slot allocation 132
frequency hopping 130
frequency translation 67

G
geo location
remotes 167
globe
sorting

iBuilder User Guide

iDX Release 2.0

globe
hide element 21
tree 21
globe, iDirect 15
GRE tunnels 158
group profiles
available views 232
Group QoS
see also QoS
allocation properties vs. request properties 211
application profiles vs. iSCPC profiles 236
bandwidth allocation algorithm 189
bandwidth allocation fairness relative to CIR 187
bandwidth allocation fairness relative to MODCOD
188
changing properties on individual remotes 224
changing the order of application profiles within
applications 216
configuring a remotes maximum MODCOD 166
configuring a remotes nominal MODCOD 166
configuring bandwidth allocation fairness relative
to MODCOD 208
configuring group QoS settings for VNO user groups
347
default and NMS applications for remotes with multiple service profiles 221
default applications in service profiles 217
effective cost with allocation fairness relative to
CIR 207
enabling EIR for remotes in group for application
based mode 214
enabling EIR for remotes in group for remote based
mode 213
enforcement of MIR on inroute 187
Enhanced Information Rate (EIR) described 187
estimating Effective CIR and MIR for DVB-S2 ACM
outbound 202
group view applications vs. service profile view applications 219
group view example 199
multicast bandwidth group 196
order of application profiles in applications 216
oversubscription of subnodes 191
preconfigured application profiles 236
QoS properties defined 186
relationship between information rate and IP data
rate 188
selecting a multicast MODCOD 216
tree structure 190
unassigning service profiles to remotes with multiple profiles 221
use of mesh bandwidth pool 191, 197
views 198
guest user 363

437

H
high power amplifier See HPA
HPA 65
adding 68
hub commissioning 313 to 331
1 dB compression test 322
downloading line cards using iSite 317
setting C/N for mesh inroute 328
setting C/N for mesh outroute 325
setting IP address on line card 315
setting tx power on line card 323
setting UPC margin for mesh outroute 326
Hub RFT
adding 88
Hub RFT Components 65
hubs
assigning inroute groups 133

I
iBuilder
description 9
installing 11
images 295
downloading 296
interactions 299
out of network 299
TCP 301
downloading multiple units 297
UDP multicast 296
iMonitor
description 9
information rate 78
inroute groups
adding 129
assigning to hubs 133
description 129
enabling CRTP for mesh remotes 132
enabling for mesh 132
enabling UDP header compression for mesh remotes
132
enabling UDP payload compression for mesh remotes 132
maximum carriers per mesh inroute group 134
mesh-enabled, described 130
uplink control parameters 134
installation
NMS applications 11
interface
using NMS GUI 20

438

IP configuration on remotes 149 to 158

iSCPC
adding an iSCPC chassis 252
adding upstream SCPC carriers 79
carrier assignment to remotes 146
downstream carriers 73
iSCPC line cards 113
iSCPC remotes 142
overview 5
iSite 9
using to download a line card 317
iVantage NMS components xxxi

L
LAN
interface 150
remotes 149 to 152
large block 78
latitude
teleport 84
legend 31
licenses
exporting data for feature license requests 59
importing license files 57
license properties tab 59
license toolbar 56
list of features licensed in iBuilder 56
permanently enabling chassis license downloads 62
sharing chassis slot licenses on more than one NMS
260
validating a chassis license 253
line cards
adding
receive 107
standby 115
transmit 104
transmit/receive 104
adding a TDMA standby 118
adding an iSCPC standby 119
commissioning See hub commissioning
configuring for mesh 106
downloading using iSite 317
enabling 10 MHz clock from the four-slot chassis
screen 258
failure recovery 128
free slot allocation 132
iSCPC line cards 113
managing redundancy relationships 120
NMS failover algorithm 128
performing manual switchover or failover 126
prerequisites for automatic failover 116

iBuilder User Guide

iDX Release 2.0

rules for assignment to chassis slots 255

selectable line card types in iBuilder 104
setting tx power 323
solo Tx/Rx line card described 104
supported model types 102
TRANSEC-compatible model types 372
types of redundancy relationships 115
LNB 169 to 170
locking
database 363
logging in 12
passwords 12
to other servers 13
longitude
spacecraft 70
teleport 84

M
main toolbar 29
management interface 151
mesh
adding a mesh inroute group 132
adding a mesh line card 106
configuring a home inroute for a remote 145
configuring remotes for mesh 145
converting a network from star to mesh 365 to 369
converting a star inroute to mesh 367
enabling CRTP per inroute group 132
enabling UDP header compression for mesh inroute
groups 132
enabling UDP payload compression for mesh inroute
groups 132
hardware requirements 365
maximum carriers per mesh inroute group 134
mesh-enabled inroute groups described 130
prerequisites for converting from star to mesh 365
recalibrating a star outroute for mesh 366
reconfiguring a star remote for mesh 367
remote model types supported 130
setting inroute C/N 328
setting outroute C/N 325
setting outroute UPC margin 326
transponder configuration requirements 365
uplink control parameters on mesh inroute groups
134
uplink control parameters on mesh line cards 106
uplink control parameters on mesh remotes 145
VLAN support on mesh remotes 149
mobile remotes
See remotes: mobile remotes 168
modifying

iBuilder User Guide

iDX Release 2.0

accepting changes 14

N
NAT 154
network tree, See tree
networks
adding 102
deactivating 103
free card slot allocation 132
inroute groups
adding 129
assigning to hubs 133
description 129
line cards
adding receive 107
adding transmit 104
adding transmit/receive 104
NMS
applications 9
distributed NMS server 381
iVantage NMS components xxxi
main components 7
multiple users accessing 13
servers used 10
setting up a distributed environment 383

O
ODU Tx 10 MHz 68
ODU Tx DC power 68
options files 279
hub-side and remote-side 280
orbital inclination 70

P
packet segmentation
setting a downstream segment size 165
panes
active users 31, 358
choose details 36
configuration changes 33
details 34
legend 31
network tree, See tree
See also dialog boxes
passwords 12, 360
profiles
assigning QoS profiles to multiple remotes 246
properties

439

viewing element 34
protocol processor
adding 88
blades 92
installing 8
TRANSEC support for 89

Q
QoS
see also Group QoS
assigning profiles to multiple remotes 246
bandwidth allocation fairness relative to CIR 187
bandwidth allocation fairness relative to MODCOD
188
configuring a remotes maximum MODCOD 166
configuring a remotes nominal MODCOD 166
configuring CIR for a physical remote 166
configuring EIR for a physical remote 166
configuring MIR for a physical remote 166
custom key for full-trigger CIR 227
Enhanced Information Rate (EIR) described 187
filter profiles vs. traffic profiles 236
full-trigger CIR 187
iSCPC connections vs. tdma networks 235
normal CIR vs. sticky CIR vs. full-trigger CIR 187
preconfigured iSCPC profiles 236
QoS properties defined 186
remote QoS Tab 164
sticky CIR 187
use of application profiles in TDMA networks 235

R
receive line card
adding 107
receive properties
remotes 146
remote locking
configuring enhanced remote locking 424
configuring traditional remote locking 421
model types supported for enhanced remote locking
424
model types supported for traditional remote locking 421
requesting a new password 423
types of remote locking 421
remotes 141
activating 275 to 276
adding 142 to 194
antenna 170
applying configurations 291

440

BUC 169 to 170

cloning 171
configuring
actions to perform beforehand 142
data to know beforehand 142
configuring for mesh 145
configuring RIPv2 on 150
customers 147 to 148
deactivating 275 to 276
deactivating before deleting 281
DHCP 153
distributors 147 to 148
DNS 152
downloading
using revision server 301
downloading configurations
out of network 299
enabling link encryption 145
geo location 167
information tab 143 to 148
IP configuration 149 to 158
iSCPC remotes 142
LAN 149 to 152
LAN "same as" option 151
LAN interface 150
listing customers 147
listing distributors 147
LNB 169 to 170
locking to an inroute 146
management interface 151
mobile remotes
automatic beam switching for 179
configuring the default minimum look angle for
remote antennas 70
GPS Input settings defined 168
handshake signalling 168
overriding the maximum skew for a remote antenna 168
overriding the minimum look angle for a remote
antenna 168
security setting 168
setting geo location parameters 167
model type 144
moving 277
multicast groups 159
MUSiC 144
NAT 154
passwords 144
port forwarding 157
receive properties 146
carrier name 146
reconfiguring for mesh 367
remote antenna 170
resetting 300
roaming remotes 172 to 180

iBuilder User Guide

iDX Release 2.0

adding multiple remotes to a network 177

adding remotes to multiple networks 178
applying changes 294
beam switching for 179
configuration changes 292
managing configuration of 174
options files for 292
pending changes across networks 293
serial number 144
serial number, system-generated 144
sleep mode
enabling 145
triggering wakeup 240
static routes 154
supported model types 141
switch tab 159 to 163
copying data to a spreadsheet 163
dedicating a port to a VLAN 160
default settings 160
setting a port as a trunk 161
setting the port speed and port mode 162
TRANSEC-compatible model types 372
transmit properties 146
power 146
power, max 146
uplink control parameters on 145
VLAN 149 to 152
VSAT 169
requirements
system 11
resetting 300
retrieving configurations
modified vs. existing 283
multiple 283
single
last modified vs. existing 281
revision server 301 to 311
cancelling an upgrade 311
controlling real-time events 306
duty cycle explained 302
real-time display options 306
starting 304
status pane 309
using to download remotes 301
when to use 304
right mouse button 25
right-click
menu options 30
RIP, see RIPv2
RIPv2 150, 154, 156
roaming remotes, see remotes: roaming remotes
RTP header compression performance characteristics

iBuilder User Guide

iDX Release 2.0

183

S
saving configurations
TCP vs. UDP 291
servers 10
SkyMonitor
assigning a carrier or center frequency 98
configuring in iBuilder 97
configuring RF ports 98
described 96
removing a line card from a port 99
selecting carriers for Tx/Rx line cards 99
sleep mode
enabling on remotes 145
triggering wakeup on remotes 240
slot allocation
free 132
small block 78
spacecraft 69 to 70
adding 69
longitude 70
spectral inversion 68
spread spectrum
empty slot requirement for line card 255, 258
modulation type supported 76
selecting a downstream spreading factor 76
selecting an upstream spreading factor 79
static routes 154
status
elements 44
status bar 31
super user 363
switch, eight-port: see remote: switch tab
symbol rate 75, 78
symbol rate vs. transmission rate 78
symbol rates for star and star-mesh carriers in the
same inroute group 78
system requirements 11

T
TCP payload compression 182
TCP vs. UDP download 288
teleport 83 to 86
adding 83
adding a backup 85
latitude 84

441

longitude 84
toolbars
choose details 36
configuration changes 33
details 34
find 29
icons 29
legend 31
license toolbar 56
main 29
main menu 30
status bar 31
view menu 30
transceiver
selecting frequency band and cross pol mode 171
selecting on the remote VSAT tab 170
supported models 170
TRANSEC
CA Foundry, See CA Foundry
certifying an unauthorized remote 399
certifying hosts before converting to TRANSEC 372
converting a network to TRANSEC 371 to 375
description 371
determining the key distribution blade 405
enabling on protocol processor 89
example of a TRANSEC sub-tree 372
line card and remote model types supported 372
protocol processor described 89
updating network keys 404
translation frequency 71
transmission rate 75, 78
transmit line card
adding 104
transmit properties
remotes 146
transmit/receive line card
adding 104
transponder
adding 70
tree
description 25
elements 15
folders 15
tree view, See tree
treebar, See tree

U
UDP payload compression 183
up converter 65
adding 67

442

upgrade assistant
See revision server
uplink control parameters
configuring for inroute groups 134
configuring on mesh line cards 106
uplink/downlink center frequency 74, 77
User Groups
CNO user groups 336
NMS user groups 334
VNO user groups 336
users
active users pane 358
adding user accounts 355
changing passwords 360
cloning user accounts 357
conversion during upgrade 333
deleting user accounts 358
guest 363
levels of 361
locking others out 363
managing 361
modifying user accounts 355 to 356
multiple 13
permissions 361
privileges
defined 361
predetermined 361 to 362
super user 363
types 361
viewing user accounts 358
VNO guest 363
VNO super user 363

V
VLAN
adding 94
default vs. upstream 150
enabling for mesh inroute groups 132
on eight-port switch: see remote: switch tab
on mesh remotes 149
remotes 149 to 152
upstream interface 94
VNO guest, see users: VNO guest
VNO super user, see users: VNO super user
VNO User Groups
adding and modifying 337
configuring group QoS settings 347
creating and managing 336
modifying visibility and access 340
setting rate limits 339
visibility and access 334

iBuilder User Guide

iDX Release 2.0

VSAT 169

W
warning properties 51 to 56
categories of warnings 52
clearing customized properties 55
configurable properties 52
customizing for specific network elements 55
distinguishing customized warnings 55
global vs. customized 52
of line cards 107
of protocol processors 91
of remotes 171
setting global properties for network elements 53
windows, See panes
See also dialog boxes

X
X.509 certificates
issuing to hosts 401
revoking from hosts 402

iBuilder User Guide

iDX Release 2.0

443