Copyright 2015, 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.
A Family of iDirect Companies
iDirect Government, created in 2007, is a wholly owned subsidiary of iDirect and was formed to better
serve the U.S. government and defense communities.
iDirect Government
Company web site: http://www.idirectgov.com ~ Main Phone: 703.648.8118
TAC Contact Information: Phone: 703.648.8111 ~ Email: tac@idirectgov.com ~ Web site:
http://tac.idirectgov.com
iDirect Asia Pte Ltd was established in Singapore during 2008 to enhance iDirects value-add and
responsiveness to customers in the Asia Pacific region.
iDirect Asia Pte Ltd
Company web site: http://www.stengg.com ~ Main Phone: 65.6521.7888
TAC Contact Information: Phone: 703.648.8151 ~ Email: tac@idirect.net ~ Web site: tac.idirect.net
ii
Revision History
The following table shows all revisions for this document. To determine if this is the latest
revision, check the TAC Web site at http://tac.idirect.net.
Revision
Date Released
07/31/2014
02/11/2015
04/27/2015
iii
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables
xvii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Contents Of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
IP Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 2
2.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2
Required Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3
2.4
NMS Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4.2
Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
iv
Contents
2.5
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5.2
Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6
Launching iBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6.1
2.6.2
2.6.3
Accepting Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.7
2.7.2
Components Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8
2.8.2
2.8.3
2.8.4
2.8.5
Sorting Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.8.6
2.8.7
2.8.8
2.9
2.9.2
2.10
Contents
2.12
2.13
2.14
2.15
Chapter 3
3.1
Adding an Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.1.2
3.1.3
3.2
Adding a Spacecraft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.3
Adding a Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.4
Adding Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.5
Adding Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.5.1
3.5.2
3.5.3
3.5.4
Chapter 4
. . . . . . . . . . . . . . . . . . . . . . . . 85
4.1
Adding a Teleport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.2
4.3
4.4
Protocol Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.4.1
vi
Contents
4.4.2
4.5
4.6
4.7
Adding a VLAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.7.1
4.7.2
4.8
Chapter 5
103
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.8.2
5.8.3
5.8.4
5.8.5
5.9
5.10
vii
Contents
Chapter 6
Configuring Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
6.1
6.2
6.3
6.3.2
6.4
6.4.2
6.4.3
6.4.4
RIPv2, Static Routes, Multicast Groups, Port Forwarding and NAT. . . . . . . 156
6.5
6.6
6.6.2
6.6.3
6.6.4
6.6.5
6.7
6.8
6.9
6.10
6.11
6.12
viii
Contents
Chapter 7
7.1
7.2
7.3
7.4
7.1.2
7.1.3
7.1.4
7.2.2
7.2.3
7.2.4
7.2.5
7.2.6
7.2.7
7.2.8
7.2.9
7.3.2
7.3.3
7.3.4
7.4.2
7.4.3
7.4.4
7.4.5
Chapter 8
8.1
201
. . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Setting the IP Address for a Chassis with an EDAS Controller Board . . . . . . 286
ix
Contents
8.1.2
Setting the IP Address for a Chassis with a MIDAS Controller Board . . . . . . 286
8.2
8.3
8.4
8.5
8.5.2
8.5.3
8.5.4
8.6
Chapter 9
Controlling Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
303
9.1
9.2
Moving Remotes Between Networks, Inroute Groups, and Line Cards . . . . . . . . 305
Chapter 10
309
10.1
10.2
10.3
10.4
10.6
Contents
Chapter 11
. . . . . . . . . . . . . . . . . . . . 325
11.1
11.2
11.4
11.5
Chapter 12
. . . . . . . . . . . . . . . . . . . . . . 341
12.1
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
12.2
Add the Line Card in iBuilder and Retrieve the Configuration . . . . . . . . . . . . . 342
12.3
12.4
12.5
12.6
12.7
12.8
12.9
Connect to the LAN and Apply the Line Card Configuration . . . . . . . . . . . . . . 352
Chapter 13
. . . . . . . . . . . . . . 353
13.1
13.2
xi
Contents
13.6
Chapter 14
xii
. . . . . . . . . . . . . . . . . . . . . . . . 393
14.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
14.2
Contents
14.3
Chapter 15
. . . . . . . . . . . . . . . . . . . . 407
15.1
15.2
15.3
15.4
15.5
415
A.1
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
A.2
A.3
A.4
A.5
A.6
A.7
A.8
A.9
A.10
A.11
xiii
Contents
Appendix B
B.1
B.2
B.3
B.4
B.5
B.6
B.7
439
C.1
C.2
C.3
C.4
C.5
C.6
D.3
449
xiv
429
D.2.2
D.2.3
D.2.4
D.2.5
D.3.2
D.3.3
D.3.4
D.3.5
Contents
Appendix E
E.1
E.2
E.3
E.4
461
E.1.2
E.1.3
E.2.2
E.2.3
E.3.2
E.3.3
E.3.4
E.3.5
E.3.6
E.3.7
latlong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
E.4.2
tlev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
E.4.3
E.4.4
E.4.5
beamselector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
E.4.6
E.4.7
E.4.8
Appendix F
481
F.1
F.2
F.3
F.4
xv
Contents
F.5
F.6
F.7
FEC Blocks per Frame for Spread Spectrum SCPC Return Channels . . . . . . . . . 485
F.8
F.9
G.2
G.2.2
G.2.3
G.2.4
G.2.5
G.2.6
Glossary of Terms
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
487
501
Figures
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
Figure 11.
Figure 12.
QoS Subfolders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 13.
Figure 14.
Figure 15.
BUC Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 16.
LNB Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 17.
Figure 18.
Figure 19.
Figure 20.
Figure 21.
Figure 22.
Figure 23.
Figure 24.
Collapsed Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 25.
Sorting Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 26.
Figure 27.
Figure 28.
Figure 29.
Figure 30.
Figure 31.
Figure 32.
iBuilder Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 33.
Figure 34.
Figure 35.
Figure 36.
Figure 37.
Figure 38.
xvii
Figures
Figure 39.
Figure 40.
Figure 41.
Figure 42.
Figure 43.
Figure 44.
Figure 45.
Figure 46.
Figure 47.
Figure 48.
Figure 49.
Figure 50.
Figure 51.
Figure 52.
Figure 53.
Figure 54.
Figure 55.
Figure 56.
Figure 57.
Figure 58.
Figure 59.
Figure 60.
Figure 61.
Figure 62.
Figure 63.
Figure 64.
Figure 65.
Figure 66.
Figure 67.
Figure 68.
Figure 69.
Figure 70.
Figure 71.
Figure 72.
Figure 73.
Figure 74.
Figure 75.
Figure 76.
Figure 77.
Figure 78.
Figure 79.
xviii
Figures
Figure 80.
Figure 81.
Figure 82.
Figure 83.
Figure 84.
Figure 85.
Figure 86.
Figure 87.
Figure 88.
Figure 89.
Figure 90.
Figure 91.
Figure 92.
Figure 93.
Figure 94.
Figure 95.
. . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 96.
Figure 97.
Figure 98.
Figure 99.
Figure 100.
Figure 101.
Figure 102.
Figure 103.
Figure 104.
Figure 105.
Figure 106.
Figure 107.
Figure 108.
Figure 109.
Figure 110.
Figure 111.
Figure 112.
Figure 113.
Figure 114.
Figure 115.
Figure 116.
Figure 117.
Figure 118.
Figure 119.
Figure 120.
xix
Figures
xx
Figure 121.
Figure 122.
Figure 123.
Figure 124.
Figure 125.
Figure 126.
Figure 127.
Figure 128.
Figure 129.
Figure 130.
Figure 131.
Choosing a New Active Line Card During Line Card Swap . . . . . . . . . . . . . . . . . 128
Figure 132.
Figure 133.
Figure 134.
Figure 135.
Figure 136.
Figure 137.
Figure 138.
Figure 139.
Figure 140.
Figure 141.
Figure 142.
Figure 143.
Remote Information Tab: Transmit and Receive Parameters for TDMA Remote . . 147
Figure 144.
Remote Information Tab: Transmit and Receive Parameters for SCPC Remote. . . 148
Figure 145.
Figure 146.
Figure 147.
Figure 148.
Figure 149.
Figure 150.
Figure 151.
Figure 152.
Figure 153.
Figure 154.
Figure 155.
Figure 156.
Figure 157.
Figure 158.
Figure 159.
Figure 160.
Figure 161.
Figures
Figure 162.
Figure 163.
Figure 164.
Figure 165.
Figure 166.
Figure 167.
Figure 168.
Figure 169.
Figure 170.
Figure 171.
Figure 172.
Figure 173.
Figure 174.
Figure 175.
Figure 176.
Figure 177.
Figure 178.
Figure 179.
Figure 180.
Figure 181.
Figure 182.
Figure 183.
Figure 184.
Figure 185.
Figure 186.
Figure 187.
Figure 188.
Figure 189.
Figure 190.
Figure 191.
Figure 192.
Figure 193.
Figure 194.
Figure 195.
Figure 196.
Figure 197.
. . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 198.
Figure 199.
Figure 200.
Figure 201.
Figure 202.
xxi
Figures
Figure 203.
Figure 204.
Figure 205.
Figure 206.
Figure 207.
Figure 208.
Figure 209.
Figure 210.
Figure 211.
Figure 212.
Figure 213.
Figure 214.
Figure 215.
Figure 216.
Figure 217.
Figure 218.
Figure 219.
Figure 220.
Figure 221.
Figure 222.
Figure 223.
Figure 224.
Figure 225.
Figure 226.
Figure 227.
Figure 228.
Figure 229.
Figure 230.
Figure 231.
Figure 232.
Figure 233.
Figure 234.
Figure 235.
Figure 236.
Figure 237.
Figure 238.
Figure 239.
Figure 240.
Figure 241.
Figure 242.
Figure 243.
xxii
Figures
Figure 244.
Figure 245.
Inserting a Multicast Service Profile into the Multicast Service Group . . . . . . . . 252
Figure 246.
Figure 247.
Figure 248.
Figure 249.
Figure 250.
Figure 251.
Figure 252.
Figure 253.
Figure 254.
Figure 255.
Figure 256.
Figure 257.
Figure 258.
Figure 259.
Figure 260.
Figure 261.
Figure 262.
Figure 263.
Figure 264.
Figure 265.
Figure 266.
Figure 267.
Figure 268.
Figure 269.
Figure 270.
Figure 271.
Figure 272.
Figure 273.
Figure 274.
Figure 275.
Figure 276.
Figure 277.
Figure 278.
Selecting and Clearing the Show Protocols Name Check Box . . . . . . . . . . . . . . 281
Figure 279.
Figure 280.
Figure 281.
Figure 282.
Figure 283.
Figure 284.
xxiii
Figures
Figure 285.
Figure 286.
Figure 287.
Figure 288.
Figure 289.
Figure 290.
Figure 291.
Figure 292.
Figure 293.
Figure 294.
Figure 295.
Figure 296.
Figure 297.
Figure 298.
Figure 299.
Figure 300.
Figure 301.
Figure 302.
Figure 303.
Figure 304.
Figure 305.
Figure 306.
Figure 307.
Figure 308.
Figure 309.
Figure 310.
Figure 311.
Figure 312.
Figure 313.
Figure 314.
Figure 315.
Figure 316.
Figure 317.
Figure 318.
Figure 319.
Figure 320.
Figure 321.
Figure 322.
Figure 323.
Figure 324.
Figure 325.
xxiv
Figures
Figure 326.
Figure 327.
Figure 328.
Figure 329.
Figure 330.
Figure 331.
Figure 332.
Figure 333.
Figure 334.
Figure 335.
Figure 336.
Figure 337.
Figure 338.
Figure 339.
Figure 340.
Figure 341.
Figure 342.
VNO Full View: SCPC Return Channels Shared by two VNOs . . . . . . . . . . . . . . . 368
Figure 343.
Figure 344.
Line Card Dialog Box: VNO User Selecting Configure Carriers . . . . . . . . . . . . . . 370
Figure 345.
Figure 346.
VNO Network Menu with Owned GQoS Nodes but No Network Access . . . . . . . . . 372
Figure 347.
VNO with Network Write Access and GQoS Node Ownership . . . . . . . . . . . . . . . 372
Figure 348.
VNO Network Menu with Owned GQoS Nodes and Write Access to Network . . . . . 373
Figure 349.
Figure 350.
Figure 351.
Figure 352.
Figure 353.
Figure 354.
Figure 355.
Figure 356.
Figure 357.
Figure 358.
Enabling the Create Permission on a QoS Folder for a VNO User Group. . . . . . . . 380
Figure 359.
Figure 360.
Figure 361.
Figure 362.
Figure 363.
Figure 364.
Opening the Active Users Pane from the View Menu . . . . . . . . . . . . . . . . . . . . 386
Figure 365.
Figure 366.
xxv
Figures
Figure 367.
Figure 368.
Figure 369.
Figure 370.
Selecting the Payload Block Size for Adaptive and Static Carriers . . . . . . . . . . . 396
Figure 371.
Figure 372.
Figure 373.
Figure 374.
Figure 375.
Figure 376.
Figure 377.
Figure 378.
Figure 379.
Figure 380.
Figure 381.
Figure 382.
Figure 383.
Figure 384.
Figure 385.
Figure 386.
Figure 387.
Figure 388.
Figure 389.
Figure 390.
Figure 391.
Figure 392.
Figure 393.
Figure 394.
Figure 395.
Figure 396.
Figure 397.
Figure 398.
Figure 399.
Figure 400.
Figure 401.
Figure 402.
Figure 403.
Figure 404.
Figure 405.
Figure 406.
Figure 407.
xxvi
Figures
Figure 408.
Viewing the ACC Key Data Structure on the Protocol Processor. . . . . . . . . . . . . 444
Figure 409.
Figure 410.
Figure 411.
Figure 412.
Figure 413.
Figure 414.
Figure 415.
Figure 416.
Figure 417.
Figure 418.
Figure 419.
Figure 420.
Figure 421.
Figure 422.
Figure 423.
Figure 424.
Figure 425.
Figure 426.
Figure 427.
Figure 428.
Figure 429.
Figure 430.
Figure 431.
Figure 432.
Figure 433.
Figure 434.
Figure 435.
Figure 436.
Figure 437.
Figure 438.
Figure 439.
Figure 440.
Figure 441.
Figure 442.
Remote Geo Location Tab: Selecting Avionics for COTM Type. . . . . . . . . . . . . . 482
Figure 443.
Figure 444.
xxvii
Tables
Table 1.
Table 2.
Configuration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 3.
Table 4.
Table 5.
Availability of Remote QoS Parameters by Service Group Type and Mode . . . . . . . 172
Table 6.
Table 7.
Table 8.
Table 9.
Table 10.
Table 11.
Table 12.
xxviii
Purpose
The iBuilder User Guide provides detailed instructions for configuring iDirect networks using
the iBuilder client application of the iDirect Network Management System (NMS). For details
on monitoring 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.
Configuring Remotes
Controlling Remotes
xxix
Document Conventions
Remote Locking
Document Conventions
This section illustrates and describes the conventions used throughout this document.
Convention Description
Example
Terminal
Output
Screen
Reference
Command
cd /etc/snmp/
The Remote dialog box has a number of userselectable tabs across the top. The Information
tab is visible when the dialog box opens.
For instructions on adding a line card to the
network tree, see Adding a Line Card on
page 108.
xxx
Getting Help
Getting Help
The iDirect Technical Assistance Center (TAC) and the iDirect Government Technologies
Technical Assistance Center (iGT TAC) are available to provide assistance 24 hours a day, 365
days a year. Software user guides, installation procedures, FAQs, and other documents that
support iDirect products are available for download.
E-mail: tac@idirect.net
For sales or product purchasing information contact iDirect Corporate Sales at:
E-mail: sales@idirect.net
E-mail: tac@idirectgt.com
iDirect and iGT produce documentation that is technically accurate, easy to use, and helpful
to our customers. Please assist us in improving this document by providing feedback. Send
comments to:
iDirect: techpubs@idirect.net
iGT: techpubs@idirectgt.com
xxxi
Related Documents
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.
xxxii
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.
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. An iSite API is available
for custom development. Remotes that support the iSite client do not support Web iSite.
Web iSite is the Web-based version of iSite available for the latest generation of iDirect
remote modems, including the Evolution X1, X7 and e150. Web iSite can be used with any
supported Web browser; therefore, no client software is required. Remotes that support
Web iSite do not support the iSite GUI client discussed above.
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.
xxxiii
xxxiv
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.
This chapter presents a high-level overview of iDirect Networks. It provides a sample iDirect
network and describes the network architectures supported by iDirect.
System Overview
An iDirect network is a satellite 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 sites. Each remote transmits to the hub either on a shared DeterministicTDMA (D-TDMA) upstream channel with dynamic timeplan slot assignments or on a dedicated
SCPC return channel.
iDirect supports both traditional OSI Layer 3 TCP/IP networks and Layer 2 over Satellite (L2oS)
networks that transport Ethernet frames over the satellite link. The L2oS feature, which was
added in iDX Release 3.3.1, is described in the Layer 2 over Satellite chapter of the
Technical Reference Guide.
The iDirect Hub equipment consists of one or more iDirect Hub Chassis with Universal Line
Cards, one or more Protocol Processors (PP), a Network Management System (NMS) and the
appropriate RF equipment. Each remote site consists of an iDirect broadband satellite router
and the appropriate external VSAT equipment.
TDMA upstream carriers are configured in groups called Inroute Groups. Multiple Inroute
Groups can be associated with one downstream carrier. Any remote configured to transmit to
the hub on a TDMA upstream carrier is part of an Inroute Group. The specific TDMA upstream
carrier on which the remote transmits at any given time is determined dynamically during
operation. A remote that transmits on a dedicated SCPC return channel is not associated with
an Inroute Group. Instead, the dedicated SCPC upstream carrier is directly assigned to the
remote and to the hub line card that receives the carrier.
Before iDX Release 3.2, all TDMA upstream carriers in an Inroute Group were required to have
the same symbol rate, modulation, and error coding. With the introduction of Adaptive TDMA
in iDX Release 3.2, the symbol rate and MODCOD of the carriers in an Inroute Group may vary
from carrier to carrier. Remotes in an Inroute Group move from carrier to carrier in real time
based on network conditions. Furthermore, with Adaptive TDMA, the individual carrier
MODCODs can adjust over time to optimize network performance for changing network
conditions. Adaptive TDMA allows for significantly less fade margin in the network design and
optimal use of upstream bandwidth during operation.
System Overview
Figure 1 shows an example of an iDirect network. The network consists of one downstream
carrier; two Inroute Groups providing the TDMA return channels for a total of 1200 remotes;
and three remotes transmitting dedicated SCPC return channels to the hub.
Packet-based and network-based QoS, including Layer 2 and Layer 3 packet classification
Multicast support
Layer 3 TCP/IP networks also support a long list of IP features, including DNS, DHCP, RIPv2,
IGMP, GRE tunneling, and cRTP. Layer 2 Ethernet-based networks provide Layer 3 protocol
transparency and simplified operation for applications such as Virtual Private Networks. For a
IP Network Architecture
complete list of available features in all iDirect releases, see the iDirect Software Feature
Matrix available on the TAC Web site.
IP Network Architecture
The examples in this section apply to traditional iDirect TCP/IP networks which transport IPV4
traffic over the satellite link. Layer 2 networks, which transport Ethernet frames over
satellite, are discussed in the Technical Reference Guide. Since Layer 3 protocols are
transparent to a Layer 2 network, a Layer 2 network can support Layer 3 protocols (such as
IPv6 and BGP) that are not supported in an iDirect TCP/IP network.
An iDirect network interfaces to the external world through IP over Ethernet ports on the
Remote Satellite Routers and the Protocol Processor servers at the hub. The examples in
Figure 2 on page 4, Figure 3 on page 5, and Figure 4 on page 6 illustrate the IP level
configurations available to a network operator for Layer 3 networks.
The iDirect system allows a mix of networks that use traditional IP routing and VLAN based
configurations. This provides support for customers with conflicting IP address ranges. It also
allows multiple independent customers at individual remote sites by configuring multiple
VLANs on the same remote.
IP Network Architecture
IP Network Architecture
IP Network Architecture
2 Overview of the
Network Management
System for iBuilder
This chapter presents an overview of the iBuilder network management tool for configuring
iDirect networks. It contains the following sections:
2.1
Introduction on page 7
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 iDirect networks.
The NMS client/server system architecture consists of three series of components:
Three NMS applications with Graphical User Interfaces (GUIs) for configuring and
monitoring iDirect networks
A middleware tier that manages access to the database on behalf of user operations
This chapter provides information required to understand how iBuilder works and how to use
it as effectively as possible. This chapter discusses how to prepare for installation; how to use
the tools available in iBuilder; how to create, customize, and print reports; and how to
Required Information
determine the configuration status of network elements. For a description of all iVantage NMS
components see The iVantage Network Management System on page xxxiii.
2.2
Required Information
Have the following information readily available when creating a new network.
2.3
LNB stability
Data rates
2.4
Line cards are installed in the chassis with their IP addresses defined using iSite.
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 can retrieve historical statistics from the archive
database 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.
NOTE: End-users do not need iSite in order to receive or transmit data over
iDirect networks.
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 network element definitions 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.
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 the
networks. These measurements are stored in the archive and provided to iMonitor for display.
PP Controller Servers
The PP Controller processes control the samnc process on each PP blade.
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 the configuration database; they can be tuned to particular storage
requirements if necessary.
10
databases on a per-transaction basis. This provides near real-time backups of NMS data. For
details, see the Technical Reference Guide.
2.5
Windows XP
Windows 7
No additional operating systems are supported. iDirect does not support server-based versions
of Windows.
NOTE: The iDirect clients may not operate correctly below screen resolution 1280
X 1024.
11
Launching iBuilder
The iDirect clients may not operate correctly in the 32-bit version of Windows 7. If an iDirect
client experiences problems, configure it to run in Windows XP Service Pack 3 compatibility
mode as follows:
1. Right click the .exe file and select Properties.
2. Click the Compatibility tab.
3. Select Run this program in compatibility mode for: Windows XP (Service Pack 3).
4. Click OK.
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; 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
page 361.
iDirect strongly recommends changing the admin user password as soon as possible after the
installation. This is especially important if the NMS Server is accessible over the public
Internet.
1. To launch iBuilder, double-click the desktop shortcut or select it from the Windows Start
menu.
2. Enter the user name and password in the Login Information dialog box.
12
Launching iBuilder
The iBuilder application automatically connects to the NMS server processes that are required
to perform NMS functions. If this connection is lost, iBuilder automatically reconnects to the
servers when they become available.
Multiple simultaneous sessions of iBuilder and/or iMonitor can run on a single PC. These
versions may be connected to different servers or the same server.
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.
Multiple iBuilder users can modify the configuration data base at the same time.
13
Launching iBuilder
element at the same time and each user saves the configuration, then the last user to save
the configuration will overwrite the other users changes. This loss of data will only occur if
the same element is being modified by the two users simultaneously.
To ensure that an iBuilder user knows when another user has modified the configuration, turn
on the accept changes functionality per iBuilder user as follows:
1. Click the Edit menu and select Preferences.
2. Clear Automatically accept configuration changes (Figure 8).
14
2.7
15
CAUTION: Do not modify or clone the Bench Test Spacecraft, Bench Test Inroute,
or Bench Test Outroute for a real network configuration. These should only be
used for testing purposes. Instead, create a new spacecraft and new carriers.
2.7.2
Pre-configured components in the QoS folder include Upstream and Downstream Filter
Profiles. For more information, see Configuring Quality of Service for iDirect Networks on
page 201.
HubRFt Components
16
parameters. For more information, see Chapter 3, Defining Hub RFT Components and the
Satellite on page 63.
2.7.4
Pre-configured components in the Manufacturers folder include items that are selectable from
drop-down lists on various configuration dialog boxes within iBuilder. Figure 16 shows an
example of typical item in the Manufacturers folder.
17
2.8
18
Single-click a plus (+) or minus (-) sign next to an element in the iBuilder Tree to expand
or contract the branches to the next level for that element or folder.
Double-click any folder with a plus sign next to it to expand it to the next level.
2. Click and hold the double-ridge lines at the top of the pane and drag the pane to a new
position. Depending on its new position, the pane may change shape. The shape of the
new position will be outlined in iBuilder.
3. Release the mouse pointer to re-dock or detach the pane.
4. To detach a pane completely, double-click the double-ridge lines.
5. To move a detached pane, either click and drag, or right-click in the border at the top of
the pane and select Move.
6. To resize the pane, place the mouse pointer at the edges of the pane.
19
20
21
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. The choices in the
Apply sort to field change depending on the selection in the Sort items by field.
5. When sorting by Name, select or clear the Names are case sensitive check box.
6. In the Apply Sort to field, select the element to sort on. Figure 24 shows the available
sort selections.
Figure 24. Sort Preferences Dialog Box: Selecting the Sort Field
7. Click OK to sort the iBuilder Tree.
NOTE: iBuilder remembers the selected sort preference after logging out and
logging on again.
22
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 25, 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.
23
Canceling an Entry
Click Cancel in any of the dialog boxes to discard the current changes without saving.
However, cancelling the configuration when the element is first added may result in an
unwanted new element in the iBuilder tree with a default name. To delete the element, rightclick the element in the tree and select Delete.
24
Menu Bar
The Menu bar at the top of the display provides access to log in, log out, quit, and other highlevel functions.
Toolbar
The Toolbar, shown in Figure 30, contains context-sensitive buttons used for a variety of
operations on a currently-selected element without using its context menu. Their functions
are described in Table 1.
Function
Displays or hides the iBuilder Tree Menu hierarchy
Opens the modify dialog box to view and edit the selected element in the tree.
Deletes the selected element in the tree. This function is not available if the selected
element has one or more child elements.
25
Function
Applies multiple configurations
Accepts any changes made to the system by another user. This feature is off by default.
For more information see Accepting Changes on page 13.
Searching iBuilder
The Find toolbar provides the option to search the NMS for matching elements and display the
results in either the Network Tree View or the Results Window. This becomes increasingly
important as the network grows larger.
To search using the Find toolbar:
1. Select ViewFind Toolbar from the main menu.
26
2. Enter a string in the first box or click the drop-down arrow to select from earlier search
strings.
3. Select an element type in the second drop-down list.
4. Select a search type in the third drop-down list.
5. Select the screen area to search in the last drop-down list.
6. Click the Binoculars icon to begin the search.
The search in Figure 31 finds remotes in the iBuilder Tree with X1 in the name.
27
View Menu
The View menu on the main menu toolbar displays or hides the toolbars and panes shown in
Figure 33. The same menu is available by right-clicking in the main iBuilder pane. If an
element is selected in the tree, the Properties option is also available.
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 34, the connection status is Ready.
28
Legend Pane
The Legend pane displays the Configuration Status icons and their meanings. They are
organized by type of element as shown in Figure 36:
29
30
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 39. (Configuration Status is not the
same as Configuration State. Configuration Status is discussed in detail in Configuration
Status of Elements on page 39.) The legend details the meanings of the various icons and
color-coded words. (See Legend Pane on page 29.
31
Properties View
The Properties view shows the properties of a selected 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 element in the
tree. Different elements have different predefined details. Use the Details view to sort, view
and print a number of details of all or some of the elements under the parent node selected in
the tree.
To view the details of an elements children that reside at the next level down in the tree:
1. Select ViewDetails.
32
Details view since it is not on the same level as the line cards and inroute group. Also, the
details of the Network itself are not displayed.
To print a report of all the elements in the Details view, select FilePrint from the main
menu. To print a subset of the elements in the Details view, use CTRL-click or the Shift key to
select the elements to print. Once the elements are selected in the Details view, select
FilePrint. (To customize the details, see Customizing Details Views for Configuration
Reporting on page 34.)
2.9
33
34
35
6. When finished customizing the view, click OK to save the list of details for this filter. The
saved list of details for the filter are retained by iBuilder.
7. In Figure 47, a carrier was selected in the tree. The user selected View Choose Details
and Show All for the carrier filter to display all carrier filter parameters.
to:
36
5. To modify the field selection for the filter, make changes to the detail selections for the
filter and click the Modify button shown in Figure 49.
7. To delete a filter, click the X button at the bottom of the Choose Details dialog box.
37
38
In Figure 51, 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: To edit multiple elements that are not under the same parent, select
ViewgCollapse Detail Hierarchy from the main menu and select the 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 Control (CTRL) + click or Shift + click to select the elements to change. In the
example in Figure 52, changes will be made to three remotes.
39
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. Be sure to reset remote modems or
line cards to activate all changes.
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
40
Network
Element
Network
Chassis
Line Card
Definition
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
Remote
Inroute Group
Protocol
Processor
Never Applied
Network
Chassis
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
41
42
You changed configuration. Whenever you change the configuration, the Changes
Pending icon is displayed beside all affected network elements.
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, iBuilder will display 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.
To view an explanation of the configuration states, their meanings, and their respective icons,
select ViewLegend from the iMonitor main menu.
43
44
45
46
Line cards
Remotes
Protocol processors
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.
Set the upper and lower limits that determine when certain warnings are generated.
(Limit-based warnings only.)
All warning modifications are processed dynamically. The NMS processes do not need to be
restarted for the warning changes to take effect. For example, when a warning is disabled in
iBuilder, iMonitor automatically clears all currently active warnings of that type. Similarly if a
47
limit is changed 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 current
warning definitions from the database and recreates them. Custom limits must be
redefined after the upgrade.
iBuilder allows modification of both global warning properties and warning properties of
individual network elements. The customized warning settings for an individual element
override the settings of the global warning. 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:
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.
48
The Modify Global Warning dialog box opens with all warnings appropriate to the
selected network element type.
49
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. Limit Type can only be changed 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. Send Value Change
property can only be changed for limit-based warnings. This field does not apply to
boolean warnings.
The Enabled setting enables or disables the warning. If this check box is cleared, the
warning will not be generated.
NOTE: Changes to global warning settings do not affect warnings that have been
customized on the Warning Properties tab. Reset the customized warning to
return to the global settings. (See Clearing Customized Warning Properties on
page 51.)
50
2. When the dialog box for the network element opens, click the Warning Properties tab.
51
4. Click the Reset button at the bottom of the screen. The following dialog box opens:
5. Click OK in the dialog box. Then click OK on the Warning Properties tab. The warning
will be reconfigured with the global settings.
52
Licensing chassis slots or any of the features listed above requires a license file from iDirect.
Use the iBuilder License Toolbar to import the license file to enable the configuration of the
chassis or feature on the iBuilder GUI.
This section describes how to import licenses after receiving a license file from iDirect. It also
describes how to generate a file that can be used to request feature licenses for existing
hardware. For more details on requesting and receiving licenses from iDirect, see the iDirect
Features and Chassis Licensing Guide.
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 64: one for importing license files; the other for
exporting license data.
53
54
55
7. When importing a chassis license file, disable download on the chassis manager as
follows:
a. From the terminal window opened in Step 1, enter the following commands:
download off
update
b. Exit the telnet session.
8. If auto-accept changes is off, click the Accept Changes icon on the iBuilder main toolbar.
(See Accepting Changes on page 13 for details on turning off and on the feature for
automatically accepting changes.)
56
Serial Number
Derived ID (DID)
NOTE: For details on requesting licenses from iDirect, see the iDirect Features
and Chassis Licensing Guide.
iBuilder provides an automated method to generate a Comma Separated Values (CSV) file of
Serial Numbers, DIDs and Model Types for the elements to be licensed. This can be useful
when requesting licenses for a large number of existing hardware elements.
To export data for feature licenses from iBuilder:
1. Select a parent element in the iBuilder Tree that contains all of the hardware units to
license.
2. Click the Export Data for Licensing button on the iBuilder Licensing Toolbar.
57
58
59
60
61
62
3.1
Antenna
Upconverter
Downconverter
Add entries to these folders and define the parameters of the components in advance 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.
63
The new antenna appears in the iBuilder Tree with a system-generated name, and the
Antenna dialog box opens to the Information tab.
64
1. Under the Hub RFT Components folder in the iBuilder Tree, right-click the Upconverter
or Downconverter folder, and select Add Upconverter or Add Downconverter.
The new upconverter or downconverter appears in the iBuilder Tree with a systemgenerated name, and the appropriate dialog box opens to the Information tab. Figure 76
shows an upconverter being added. The procedure is the same for adding a
downconverter.
65
6. Select ODU Tx DC Power and ODU Tx 10 MHz to tell the iDirect modem to supply DC
power and the 10 MHz clock. These settings are applicable when 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;
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 page 291 for
details.
7. Leave Spectral Inversion at Normal unless 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 upconverter appears in the iBuilder Tree under the Upconverter
folder.
9. To add additional upconverters, repeat this procedure, assigning each upconverter a
different name.
10. Repeat these steps for all of the downconverters at the teleport.
The new HPA appears in the iBuilder Tree with a system-generated name, and the HPA
dialog box opens to the Information tab.
66
Adding a Spacecraft
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 iBuilder Tree with a system-generated name, and the
Spacecraft dialog box opens to the Information tab.
67
Adding a Transponder
3.3
Adding a Transponder
A satellite transponder receives the carriers on the uplink frequencies and re-transmits them
on the downlink frequencies. Each transponder is configured under a spacecraft in iBuilder.
Bandwidth regions are then defined for each transponder. Upstream and downstream carriers
are then added to the bandwidth regions. This hierarchy is illustrated in Figure 79.
68
Adding a Transponder
The new transponder appears in the iBuilder Tree with a system-generated name, and the
Transponder dialog box (Figure 80) opens to the Information tab.
69
Adding Bandwidth
4. Enter the information for the remaining fields, which can also be obtained from the
service provider. This information is for reference purposes only.
5. Click OK. The new transponder is added to the iBuilder Tree under the Spacecraft.
3.4
Adding Bandwidth
A bandwidth region defines a specific portion of the satellites transponder within which
transmit and receive carriers are defined. At least one bandwidth region is required 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 iBuilder Tree with a system-generated name, and
the Bandwidth dialog box opens to the Information tab.
70
Adding Carriers
3.5
Adding Carriers
This section describes how to add both downstream and upstream carriers in iBuilder.
The new carrier appears in the iBuilder Tree with a system-generated name, and the
Downstream Carrier dialog box opens to the Information tab.
71
Adding Carriers
72
Adding Carriers
a. Select both a Minimum M ODCOD and a Maximum MODCOD. This defines the range of
MODCODs used on the downstream carrier.
NOTE: iDX Release 3.3 does not support CCM. To simulate CCM, select the same
Minimum MODCOD and Maximum MODCOD. If simulating CCM, adjust the DVB-S2
network parameters as described in Adjusting DVB-S2 Parameters for CCM
Networks on page 138.
b. Click the MODCOD Distribution button to estimate the Information Rate for the DVBS2 carrier based on the MODCODs that the remotes in this network are able to
receive. See Estimating the Information Rate for a DVB-S2 Carrier on page 81 for
details.
9. For Error Correction, LDCP BCH is automatically selected for all DVB-S2 carriers. For
information on the available FEC rates and modulation modes, see the iDirect Link Budget
Analysis Guide for this release.
10. In the Assigned to Line Card field, select a transmit line card for this carrier. If no line
card is available for selection, configure a new card or re-configure an existing card for
use by this carrier.
11. Enter the Symbol Rate for the DVB-S2 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.
12. In Timeplan Parameters:
a. FEC Blocks per Frame is not applicable to DVB-S2 carriers.
b. Frame Length is automatically set to 125 ms.
13. Spreading Parameters cannot be selected. Spread Spectrum is not supported on DVB-S2
downstream carriers.
14. Click OK. The outbound carrier appears in the iBuilder Tree.
The new carrier appears in the iBuilder Tree with a system-generated name, and the
Upstream Carrier- TDMA dialog box opens to the Information tab.
73
Adding Carriers
74
Adding Carriers
8. If Adaptive is selected in Modulation, the Payload Size field appears in place of the Error
Correction field (Figure 84). Select a Payload Size for the Adaptive carrier.
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.
NOTE: Evolution X1 and e150 remotes are not allowed to transmit on TDMA
upstream carriers larger than 4 Msps.
11. In the Timeplan Parameters section:
a. Frame Length is determined when the carrier is assigned to a line card in a network
with a downstream carrier. Frame Length is the size of the upstream frame in
milliseconds.
b. Select Enable Superburst to allow remotes to use the Superburst waveform to
acquire the network on this upstream carrier. (Use of Superburst is limited to
upstream carriers received by multichannel line cards or by receive-only eM1D1 line
cards.)
NOTE: See the chapter titled Remote Acquisition in the iDirect Technical
Reference Guide for details on Acquisition Slots and Superburst.
75
Adding Carriers
12. If using the iDirect Spread Spectrum feature with BPSK modulation, select a Spreading
Factor in the Spreading Parameters area of the dialog box. The following upstream
Spreading Factors can be selected:
No Spreading
3.5.2.1
iDX Release 3.3.2.1 introduces the ability to disable acquisition slots on specific carriers
which may be useful when larger carriers are set up using inclined orbit satellite bandwidth. It
accomplishes this through the use of a custom key that causes the Protocol Processor to
disable acquisition on the selected carrier.
NOTE: The Acquisition Aperture is still present; however, it is not used for TDMA
acquisition slots on the selected carrier.
To disable the use of acquisition slots on specific carriers (e.g., high symrate or low symrate
carriers), create a network-level custom key in iBuilder as follows:
1. Right-click the network in the iBuilder Tree and select ModifyItem.
2. Click the Custom tab.
3. Enter the following Custom Key:
[INROUTE_x]
76
//x = Inroute id
Adding Carriers
acq_disable=1
4. Click OK to save the changes.
5. Right-click the network in the iBuilder Tree and select Apply ConfigurationNetwork to
download the changes.
The new carrier appears in the iBuilder Tree with a system-generated name, and the
Upstream Carrier - SCPC dialog box opens to the Information tab.
NOTE: As shown in Figure 86, an SCPC upstream carrier is distinguished from a
TDMA upstream carrier by the S in the carrier icon in the iBuilder Tree.
77
Adding Carriers
78
Adding Carriers
NOTE: Additional Guard Band is required for SCPC return channels being
transmitted by some mobile remotes. See Guard Band for SCPC Return Channels
on page 494.
6. Select the Modulation for the carrier: BPSK, QPSK or 8PSK.
7. Select the type of Error Correction to be used for this carrier. Only 2D 16-State Coding is
supported for SCPC upstream carriers.
NOTE: For information on the available FEC rates and modulation modes, see the
iDirect Link Budget Analysis Guide for this release.
8. Enter either the Transmission Rate, Information Rate, or Symbol Rate. Entering any of
these values will cause the remaining rates and the Occupied Bandwidth to be
automatically calculated.
NOTE: Not all configurable Symbol Rates and Modulations are supported for some
mobile applications. See Minimum Symbol Rates for Mobile Remotes on page 491.
9. In Frame Parameters, the Frame Length and the number of FEC Blocks per Frame are
automatically calculated based on the selected Error Correction.
10. To use the iDirect Spread Spectrum feature, select a Spreading Factor in the Spreading
Parameters area of the dialog box. The following SCPC upstream Spreading Factors can
be selected:
No Spreading
NOTE: The iDirect Spread Spectrum feature is only supported for BPSK
modulation. A Spreading Factor can only be selected if BPSK is selected in the
Modulation field. For more information, see the chapter titled Spread Spectrum
in the iDirect Technical Reference Guide.
NOTE: Spread Spectrum is not supported for upstream carriers received by XLC-M
or eM0DM line cards.
11. In the Uplink Control Parameters area of the dialog box (Figure 87 on page 78), specify
the Operating Margin and the three Power Adjust parameters. The Uplink Control
Parameters are defined as follows:
79
Adding Carriers
To calculate the Operating Margin, subtract the C/N Threshold from the Clear Sky
C/N provided by the Link Budget Analysis (LBA) for the network. The system adds the
Operating Margin to the C/N Threshold to arrive at the Nominal C/N for the carrier.
The Nominal C/N is the target C/N value of the SCPC upstream carrier as measured by
the hub line card. (This target C/N is represented by the dashed vertical line in the
green area of the graphical display in Figure 87.)
The value entered for Below Nominal determines how far below the Nominal C/N the
receive signal can drop before the system increases the remotes transmit power in
order to bring the C/N back into the operational range. (This is represented by the
green area to the left of the target C/N in the graphical display in Figure 87.)
The value entered for Above Nominal determines how far above the Nominal C/N the
receive signal can rise before the system decreases the remotes transmit power in
order to bring the C/N back into the operational range. (This is represented by the
green area to the right of the target C/N in the graphical display in Figure 87.)
The Max Power Adjustment is the maximum change that the system will make to the
remotes transmit power in a single adjustment. (This is represented by the two red
areas at the left and right ends of the graphical display in Figure 87.) If the change
required to reach the target C/N is less than or equal to the Max Power Adjustment,
then the system will adjust by that amount in a single step. If a larger change is
required, the system will make multiple adjustments to arrive at the target C/N.
NOTE: Click and drag the Power Adjust sliders to vary the C/N ranges and
automatically update the Power Adjust settings.
80
Adding Carriers
81
Adding Carriers
82
4 Defining Network
Components
The Teleport is the highest component in the iBuilder Tree hierarchy and represents the
facility where the antenna and, typically, the rest of the Hub equipment is housed. After
adding a Teleport, add a Protocol Processor (PP), Blades, Hub RFT, and Chassis to the iBuilder
Tree. This chapter discusses how to configure all of these elements except the chassis. Chassis
configuration is discussed in Configuring a Hub Chassis on page 285.
This chapter contains the following sections:
4.1
Adding a Teleport
1. To add a Teleport, right-click the iDirect Globe at the top of the iBuilder Tree and select
Add Teleport.
The new teleport appears in the iBuilder Tree with a system-generated name, and the
Teleport dialog box opens to the Information tab.
83
4.2
84
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 this release.
NOTE: When using the same outbound carrier for both the 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 the backup teleport
hub equipment and to add existing remotes to the backup teleports networks. The procedure
assumes that the primary teleport and the networks it controls are already configured in
iBuilder and operational.
1. Add the backup teleport by following the steps in the section Adding a Teleport on
page 83. Then configure all the components of the backup teleport, including:
The Hub RFT (See Adding a Hub RFT on page 87)
Protocol Processor Blades (See Adding a Protocol Processor Blade on page 92)
Line Cards (See Adding a Transmit or Transmit and Receive Line Card on page 105)
2. Right-click the backup teleport in the iBuilder Tree and select ModifyItem.
3. In the Backup NMS area of the Teleport dialog box, select Enabled (Figure 92).
85
NOTE: A distributed NMS requires up to three IP addresses for the NMS servers.
Unless there is a distributed NMS at the backup site, all three IP addresses should
be identical.
6. Add each remote to the backup teleport as follows:
a. Right-click the remote in the iBuilder Tree and select Add to Networks from the
menu to display the Roaming dialog box.
b. In the Automated Configuration Downloader dialog box, select all remotes and line
cards.
86
4.3
The new Hub RFT appears in the iBuilder Tree with a system-generated name, and the
Hub RFT dialog box opens to the Information tab.
87
Protocol Processors
4.4
Protocol Processors
After adding the Hub RFT, create the Protocol Processor. The Protocol Processor configuration
defines general parameters that apply to the Protocol Processor server machines, which are
called blades. Protocol Processor blades are the hub servers responsible for processing,
routing and managing the upstream and downstream traffic. Add the Protocol Processor in
iBuilder before configuring the blades.
Networks can be expanded by adding multiple blades to the Protocol Processor. This
architecture provides both scalability and automatic failover. If a blade fails, its load is
automatically distributed across the remaining blades.
88
Protocol Processors
technical description of iDirects TRANSEC feature, see the iDirect Technical Reference
Guide.
NOTE: A license is required for all Protocol Processor blades and line cards that
use the TRANSEC feature. All blades must be licensed for TRANSEC in order to add
a TRANSEC protocol processor in iBuilder. For complete details on requesting and
installing iDirect licenses, see the iDirect Features and Chassis Licensing Guide.
To configure a TRANSEC network in iBuilder, first create one or more TRANSEC protocol
processors. All network elements that are subsequently created under a TRANSEC protocol
processor are part of the 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 page 416.
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, TRANSEC remotes, and GKD Servers. Issue X.509 certificates before
creating the TRANSEC network. For details on the certification process, see Using the iDirect
CA Foundry on page 437.
The new Protocol Processor appears in the iBuilder Tree with a system-generated name,
and the Protocol Processor dialog box opens to the Information tab.
89
Protocol Processors
90
Protocol Processors
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 Protocol Processors. It is critical for communications between
the NMS and network elements.)
5. In Upstream Gateway, enter the IP address of the upstream router. This is the address of
the router interface connected to the upstream LAN segment.
6. Click Enabled RIPv2 to configure the Protocol Processor to advertise remote routes to the
upstream router using the RIPv2 protocol. This setting affects the default VLAN only.
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 to add a protocol processor for a new TRANSEC network.
(Selecting Add TRANSEC Protocol Processor from the iBuilder Tree automatically enables
this field.)
NOTE: Before selecting this option for an existing network, ensure that all
preliminary steps have been taken. Follow the procedure in Converting a Network
to TRANSEC on page 415 to convert an existing network to TRANSEC.
NOTE: TRANSEC Enabled only appears in the dialog box if a TRANSEC license is
installed on the Protocol Processor. Before deploying this feature, contact the
iDirect Technical Assistance Center (TAC).
9. Select L2oS Enabled to configure Layer 2 networks under this Protocol Processor. If this
field is selected, only Layer 2, Ethernet-based networks containing Evolution X1 and/or
Evolution X7 remotes can be configured under this Protocol Processor.
NOTE: The L2oS feature requires iDX Release 3.3.1 or later.
10. Select Forward SNAP LLC Frames Enabled to allow Logical Link Control (LLC) frames to
be transported over the satellite link in Layer 2 networks.
11. A persistent multicast group is a multicast group that includes all remotes communicating
with this protocol processor. The protocol processor always forwards upstream multicast
traffic for a persistent multicast group. (This is not supported in L2oS networks.)
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.
91
12. Enter the Vlan Id and the IP Address of the multicast group.
NOTE: For more information, see the Technical Note titled IP Multicast in
iDirect Networks.
13. Under SI Table, enter a Multicast IP Address for system messages that are broadcast by
the Protocol Processor to the remotes. Select a multicast IP address that meets the
following conditions:
The selected IP address must not conflict with any multicast IP addresses being used
by the networks.
4.5
The tunnel switch must not filter out the selected multicast IP address.
If there are multiple Protocol Processors that are not isolated on the LAN, then a
different Multicast IP Address must be configured for each Protocol Processor.
4.6
92
In either case, the Protocol Process Blade dialog box opens (Figure 99).
93
Adding a VLAN
4.7
Adding a VLAN
This section explains how to configure VLANs for Layer 3 IPv4 networks. This information does
not apply to Layer 2 over Satellite (L2oS) networks. L2oS configuration is discussed in
Configuring L2oS Hub Parameters on page 98 and in Remote L2oS Tab on page 183.
94
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 100.
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
95
Adding a VLAN
NOTE: The VLANs tab is not displayed if L2oS is enabled for this protocol
processor.
3. Click Add to display the VLAN dialog box.
96
Adding a VLAN
97
4.8
98
b. If the Default Mode is VPWSEPC, enter the MAC address to which the hub sends all
upstream Ethernet packets for all SVNs, unless an Optional Override applies. The
default for this field is 00:00:5E:00:52:13.
Optional Overrides can be configured to modify the Default Mode parameters for specific
fields of specific SVNs. In the absence of an Optional Override for an SVN, the default service
mode settings are used.
To add an Optional Override for an SVN:
1. Click the Add button in the Optional Overrides section of the L2oS tab to open the SVN
dialog box (Figure 105).
99
100
5.1
101
Adding a Network
5.2
Adding a Network
To create the network, follow these steps:
1. Right-click the Protocol Processor and select Add Network. The new network is added to
the iBuilder Tree with a system-generated name, and the Network dialog box opens to
the Information tab.
102
Adding a Network
4. Inhibit Tx (When beam quality = 0) is only applicable when using the Automatic Beam
Selection feature for roaming remotes.
When this option is selected, remotes will not attempt to join this network when the
beam quality at the current location is zero. If a remote has already joined this network
and the beam quality becomes zero, the remote will stop transmitting and look for
another network to join. If another network with positive beam quality is available, then
the remote will join that network. (See Configuring Networks for Automatic Beam
Selection on page 469 for more information.)
NOTE: If you enable Inhibit Tx (When beam quality = 0) and the beam maps have
been designed to avoid unnecessary beam switching, it is possible that a remote
may mute its transmitter when you do not expect it. For questions, please contact
the TAC before enabling this feature.
5. To enable encryption for Multicast Fast Path streams, select Multicast Encryption.
NOTE: Link Encryption licenses are required for protocol processors and some
remote model types to use this feature. See the chapter on Multicast Fast Path
in the iDirect Technical Reference Guide for details.
6. To add a persistent Multicast Group to the network:
a. In the Multicast Groups section of the dialog box, click the Add button to display the
Persistent Multicast Group dialog box (Figure 107).
103
5.3
104
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.
Standby Line Card: The line card acts as a standby (spare) line card for one or more
active line cards in a chassis.
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.
5.4
The new line card is added to the iBuilder Tree with a system-generated name, and the
Line Card dialog box opens to the Information tab.
105
106
NOTE: Beginning with iDX Release 3.0, you cannot modify a line cards Model
Type, Receive Mode, Serial Number, or Line Card Type once a Receive Carrier is
assigned to the line card. You must unassign the carrier to change these fields. To
unassign a receive carrier from a line card, first remove the carrier from its
inroute group or line card (in SCPC return mode) and then select None in the
Carrier Name field.
12. If configuring an Alternate Downstream Carrier for this network, select that carrier in the
Alternate Transmit Properties area of the dialog box.
Configuring an alternate downstream carrier facilitates 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 page 115 for the procedure to move a
network from the current transmit carrier to the alternate downstream carrier.
NOTE: An alternate downstream carrier cannot be selected if the NMS server is
licensed for the Global NMS feature.
13. Click OK to save the line card configuration. The line card is added to the iBuilder Tree
under the Network.
NOTE: For details on deleting a line card, see Deleting a Line Card on page 113.
5.5
An eM0DM Multichannel Line Card can receive as many as eight upstream carriers.
An XLC-M Multichannel Line Card can receive as many as eight upstream carriers or as
many as 16 narrowband TDMA upstream carriers (up to 128 ksym/s).
In addition, there are two types of upstream carriers that can be received by a receive-only
line card:
The combination of the number and type of upstream carriers that a line card is capable of
receiving results in five possible receive modes for a receive-only line card:
107
The receive modes that can be selected in iBuilder for a receive-only line card depend on the
line card model type and licensing. The following restrictions apply to the receive mode
selection:
Only Evolution XLC-M and eM0DM line cards can receive multiple upstream carriers.
All upstream carriers received by an Evolution XLC-M or eM0DM line card must be the
same carrier type. You cannot configure a multichannel line card to receive both SCPC
and TDMA carriers at the same time.
All TDMA upstream carriers received by a multichannel line card must be in the same
inroute group.
All TDMA upstream carriers received by a multichannel line card must be on the same
transponder.
All TDMA upstream carriers received by a multichannel line card must be configured for
the same type of acquisition bursts. Superbursts and traditional acquisition bursts cannot
be received simultaneously by the same line card. See Adding TDMA Upstream Carriers on
page 73 for details on selecting the carrier acquisition type.
A multichannel line card cannot receive more than eight carriers with Superburst
acquisition enabled. Since Superburst and traditional acquisition bursts cannot be
received simultaneously by the same line card, an Evolution XLC-M line card receiving
more than eight narrowband carriers must use traditional acquisition.
For a single channel line card to receive an Adaptive TDMA upstream carrier, the receive
mode must be set to Single Channel TDMA (Adaptive).
A line card in Single Channel TDMA Receive Mode is not capable of processing more than
600 traffic slots per TDMA frame. Therefore, a TDMA carrier with more than 600 traffic
slots per frame should never be assigned to any line card configured for Single Channel
TDMA Receive Mode. This restriction only applies to Single Channel TDMA Receive Mode. It
does not apply to Single Channel TDMA (Adaptive) Receive Mode. Traffic slots per frame
are displayed in iBuilder on the Inroute Group Composition Dialog Box as shown in
Figure 136 on page 133.
Only Evolution XLC-M, eM0DM, and eM1D1 line cards can receive SCPC upstream carriers.
An Evolution eM1D1 line card receiving an SCPC upstream carrier must be configured as a
receive-only line card. It cannot be used as a Tx/Rx line card.
Licenses are required to use Evolution XLC-M and eM0DM line cards in TDMA and SCPC
Multiple Channel modes for more than one channel. (See the iDirect Features and Chassis
Licensing Guide for details.)
If an XLC-M line card has a narrowband multichannel license, individual upstream TDMA
carriers assigned to the line card cannot exceed 128 ksym/s.
NOTE: Beginning with iDX Release 3.0, you cannot modify a line cards Model
Type, Receive Mode, Serial Number, or Line Card Type if a Receive Carrier is
assigned to the Line Card.
108
The new line card is added to the iBuilder Tree with a system-generated name, and the
Line Card dialog box opens to the Information tab.
109
6. Under LAN / MGMT IP Address, enter the IP Address, Subnet Mask, and Gateway used by
the NMS to communicate with the line card.
7. Enter the GIG0 IP Address.
8. The User Password and Admin Password are set to the default passwords that appear on
the screen. Specify alternate, secure passwords.
9. In Receive Properties, if you selected Single Channel TDMA mode or Single Channel
SCPC mode, select the Carrier associated with this line card.
NOTE: To enable Single Channel SCPC mode for an XLC-M line card, choose
Multiple Channel SCPC mode for Receive Properties, and select the Carrier
associated with the line card.
NOTE: Beginning with iDX Release 3.0, you cannot modify a line cards Model
Type, Receive Mode, Serial Number, or Line Card Type once a Receive Carrier is
assigned to the Line Card. You must unassign the carrier to change these fields. To
unassign a receive carrier from a line card, first remove the carrier from its
inroute group or SCPC line card and then select None in the Carrier Name field.
10. To add your carriers in Multiple Channel TDMA mode or Multiple Channel SCPC mode,
follow the procedure in the next section, <Hyperlink>Adding Multiple Receive Carriers to
a Line Card.
11. Once you have added your carrier or carriers, click OK to save the line card configuration.
The receive line card is added to the iBuilder Tree under the Network.
110
111
5. Select Show carriers associated with other line cards to see TDMA and SCPC upstream
carriers in this line cards frequency band that are assigned to other line cards. Carriers
assigned to other line cards appear as vertical orange bars in the graph (Figure 113).
Figure 114. Associating an SCPC Return Channel with a VNO User Group
The carrier is now assigned to one of the SCPC channels owned by the selected VNO
user group. The carrier automatically becomes visible to the VNO user group.
NOTE: Only VNO user groups that own channels on this SCPC line card appear in
the drop-down menu. For details on assigning SCPC return channels to VNO user
groups, see Configuring VNO Access Rights for SCPC Return Channels on page 376.
8. Click OK to save the carrier selections.
112
5.6
113
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 117). This puts the Rx line card in the deactivation
pending state.
114
5.7
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
page 105.)
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.
See the chapter titled Alternate Downstream Carrier in the iDirect Technical Reference
Guide for a description of this feature.
CAUTION: 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). To shorten this timeout,
define the following remote-side custom key on the Remote Custom tab for each remote
before executing the procedure.
[BEAMS_LOCAL]
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). Figure 119 shows this initial
configuration. (To move to the alternate carrier without selecting a new alternate carrier,
select None in Step 2 of the procedure.)
115
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.
116
5.8
A Tx (or Tx/Rx) line card configured to transmit the outbound carrier in an iDirect
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 one or more inbound TDMA carrier or one or
more inbound SCPC carriers transmitted by the remote modems in a 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.)
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.
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. A standby line card backing up a Tx or Tx/Rx line card must be in the same chassis as the
failed line card.
4. A standby line card backing up an Rx-only line card must be in the same chassis as the
failed line card.
117
5. The chassis must be accessible to the NMS through the TCP interface.
6. 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.)
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.
Default redundancy relationships are not established automatically when you configure
standby line cards for your 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 page 120 for
details.)
When you configure a standby line card in a 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:
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.
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
118
eM1D1
eM1D1
eM0DM
eM0DM
XLC-11
XLC-11
XLC-10
XLC-10
XLC-M
XLC-M
119
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.)
120
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
This dialog box has two views. The default view (By Standby, shown in Figure 124) lists each
standby line card 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 their 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 a View from the
menu.
121
The dialog box is divided into virtual backplanes, organized by the assignments of the line
cards to the chassis. The dialog box also shows the physical slot numbers and the redundancy
relationships of all line cards in the chassis.
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.
2. If there are any valid line cards available, a dialog box opens with a list of all valid
selections. Right-clicking a standby line card shows a list of available active line cards.
Right-clicking an active line card shows a list of available standby line cards. Figure 126
shows both views.
122
2. If there are any valid line cards available, a dialog box opens with a a list of all valid
selections. Right-clicking a standby line card shows a list of available active line cards.
123
Right-clicking an active line card shows a list of available standby line cards. Figure 127
shows both views.
124
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
card will not be selected to take over for the active line card in the event that the active
line card fails.
125
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.
126
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 page 126.
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 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.
5.9
127
Inroute Groups
For details on configuring warning properties for line cards, remotes and protocol processor
blades, please see Configuring Warning Properties on page 47.
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)
128
Inroute Groups
that remote under current conditions. If no slots are available, slots may be assigned on a
less-optimal carrier, provided the remotes bursts can be received at the hub on that carrier.
NOTE: Beginning in iDX Release 3.2, Carrier Grooming can no longer be selected
for an inroute group.
The specific rules regarding the assignment of TDMA upstream carriers to inroute groups are:
All carriers in an inroute group must have the same payload block size.
A line cards carrier assignment cannot be changed if the carrier is assigned to an inroute
group. However, some of the carriers parameters can be modified.
Beginning with iDX Release 3.2, a TDMA upstream carrier can be configured as either Static or
Adaptive. Multiple Inroute Group Compositions (IGCs) can be created per inroute group to
optimize the carrier definitions for different network conditions. (For details, see the chapter
titled Adaptive TDMA in the iDirect Technical Reference Guide.)
The specific rules regarding the use of Adaptive and Static carriers and the configuration of
IGCs are:
Both Static and Adaptive carriers can be included in the same inroute group.
To configure multiple IGCs for an inroute group, at least one carrier must be Adaptive.
A different MODCOD can be selected for each Adaptive carrier in each IGC.
The center frequency and symbol rate of an Adaptive carrier is the same for all IGCs.
129
Inroute Groups
The new inroute group is added to the iBuilder Tree with a system-generated name, and
the Inroute Group dialog box opens to the Information tab.
130
Inroute Groups
b. The Guard Interval is the guard time in NCR ticks needed to account for symbol
timing uncertainty when the remotes transmit TDMA bursts. NCR ticks are used
internally by the system for network timing. The Guard Interval is translated into
microseconds on the screen. (See Figure 132.)
5. Shared Carrier Parameters are the same for all carriers in the inroute group. These
parameters are defined as follows:
a. Payload Size is a read-only field that shows the payload block size configured for the
carriers. Only carriers with the same payload size can be added to the inroute group.
b. Frame Length is a read-only field that shows the frame length of the upstream
carriers in the inroute group.
6. Adaptive Parameters determine how IGCs are selected for this inroute group. Adaptive
Parameters only need to be configured for inroute groups with multiple IGCs. For
additional information, see the chapter titled Adaptive TDMA in the Technical
Reference Guide.
a. Before selecting an IGC, the algorithm predicts the percentage of remotes currently
in the network that would drop out if that IGC were selected. If the predicted
percentage of remotes that would drop out exceeds the Allowed Dropout Factor,
that IGC will not be selected unless that IGC is the default IGC.
b. The Default IGC is the IGC that is selected if the Allowed Dropout Factor is exceeded
for all IGCs defined for the inroute group.
c. The Update Interval is the frequency (in seconds) with which the IGC selection
algorithm executes to select the optimal IGC for the current network conditions. The
algorithm may run more frequently if required by network performance. The default
is 60 seconds.
d. Under Selection Algorithm, check Enable Fixed IGC and select a specific IGC to lock
this inroute group to that IGC. When a fixed IGC is selected, other IGCs are not used.
7. In the Line Cards section of the Information Tab, click Add to open the Assign Hub To
Inroute Group dialog box.
131
Inroute Groups
8. In the Assign Hub To Inroute Group dialog box, select the upstream carrier to be added
to this inroute group.
NOTE: All TDMA upstream carriers assigned to a multichannel line card must be in
the same inroute group.
9. Click OK to return to the Information tab of the inroute group.
10. Repeat Step 7 through Step 9 to add additional upstream carriers to the inroute group.
11. To add a new IGC, follow the procedure in the next section, <Hyperlink>Configuring
Inroute Group Compositions.
12. To configure the acquisition and uplink control parameters for the inroute group, follow
the procedure in Configuring Uplink Control Parameters on page 134.
13. Click OK to save the inroute group configuration.
NOTE: The Group QoS tab of the Inroute Group is discussed in Chapter 7,
Configuring Quality of Service for iDirect Networks.
132
Inroute Groups
3. Click Edit IGC and select the new IGC to open the Inroute Group Composition dialog box.
Payload is the read-only payload block size in bytes for all upstream carriers in the
inroute group. It must be the same for all carriers in the inroute group. For Static
upstream carriers, this value is defined in the Error Correction field of the upstream
carrier dialog box. For Adaptive upstream carriers, this value is defined in the Payload
Size field of the upstream carrier dialog box. (See Adding TDMA Upstream Carriers on
page 73.)
133
Inroute Groups
Each row in the Inroute Group Composition dialog box represents a single upstream carrier
assigned to this Inroute Group. All carrier-specific parameters are read-only except for the
MODCOD. For Adaptive carriers, a different MODCOD can be selected for each IGC. Changing
the carrier MODCOD automatically updates the Information Rate, C/N0, and number of
Traffic Slots.
The carrier-specific parameters are defined as follows:
ID is a system-generated identifier for the carrier that is consistent across all IGCs.
Hub is the name of the receive line card to which the upstream carrier is assigned.
Type is the carrier type (Static or Adaptive) determined by the Modulation selected for
this upstream carrier in the upstream carrier dialog box. If Adaptive is selected for the
carrier Modulation, the Type is Adaptive. If a specific Modulation (such as BPSK) is
selected for this carrier, the Type is Static.
Freq Uplink/Downlink shows both the Uplink Center Frequency and Downlink Center
Frequency in MHz configured for the carrier.
For Adaptive carriers, select the carriers MODCOD for this IGC by clicking in the
MODCOD cell and selecting a MODCOD from the drop-down list.
Spreading Factor is the Spread Spectrum Spreading Factor selected for BPSK carriers. All
Spread Spectrum carriers are Static.
C/N0 is the C/N threshold of the carrier as specified in the Link Budget Analysis Guide
adjusted for the Symbol Rate of the carrier and includes the M1 and M2 margins
configured for the inroute group. (See the next section for details.)
Traffic Slots is the number of traffic slots per TDMA frame for this carrier.
134
Inroute Groups
the chapters titled Remote Acquisition, Uplink Control Process, and Adaptive TDMA in
the Technical Reference Guide.
To configure the uplink control parameters for the inroute group:
1. If the Information tab for the inroute group is not already open, right-click the inroute
group in the iBuilder Tree and select ModifyItem.
2. In the Inroute Group dialog box, click the Uplink Control tab.
The Hysteresis Margin (M2) is added to the Fade Slope Margin when determining
whether or not a remote should switch to an upstream carrier with a different
MODCOD and/or symbol rate. This margin prevents unnecessarily frequent switching
between carriers.
The Acquisition Margin (M3) is used to determine the initial nominal upstream carrier
for the remote based on the C/N of the acquisition burst. For more information, see
the section titled Acquisition in the Uplink Control Process chapter of the
Technical Reference Guide.
135
The thresholds which determine a remotes current MODCOD based on its reported Signalto-Noise Ratio (SNR)
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.
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.
136
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.
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.
137
2. In the DVB-S2 Configuration dialog box, edit any settings you want to change.
138
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 page 136. The procedure for
configuring these parameters is documented in Configuring DVB-S2 Network Parameters on
page 137.
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
On the Custom Tab of the transmit 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: MODCOD indexes are documented in the Link Budget Analysis Guide for
this release.
139
140
6 Configuring Remotes
Remote satellite routers provide IP or Ethernet connectivity between each remote LAN and
the hub. This chapter contains detailed procedures for configuring remotes to operate in
iDirect networks. The chapter contains the following sections:
6.1
Evolution e8350
Evolution X7
Evolution X5
Evolution X3
141
Adding Remotes
6.2
Adding Remotes
The following information is required to add a remote in iBuilder: the IP addressing scheme of
the network; the specifications of all outdoor components; the configuration parameters to
be assigned to the remote; and the geographic location and hemisphere of the satellite.
The procedure for adding a remote assumes that the following elements have already been
configured in iBuilder:
One or more Inroute Groups within the network (TDMA remotes only)
Any iDirect remote that transmits to the hub on a TDMA upstream carrier must be assigned to
an inroute group. All remotes in the inroute group share the upstream carriers assigned to the
inroute group. The protocol processor assigns TDMA frame slots to individual remotes in real
time based on the each remotes current bandwidth demand.
An SCPC remote transmits a dedicated SCPC return channel to a receive line card at the hub.
An SCPC remote is not a member of an inroute group. Instead, an SCPC remote is assigned to
its receive line card. For a line card to receive an SCPC upstream carrier, the line card must
be configured in single channel or multiple channel SCPC mode. See Adding Receive-Only (RxOnly) Line Cards on page 107 for details.
NOTE: Only Evolution e8350, Evolution X5 and Evolution X3 remotes can transmit
SCPC upstream carriers.
To add and configure remotes, follow these steps:
1. To add a remote to an inroute group, right-click the Inroute Group and select Add
Remote.
To add an SCPC remote, right-click the receive line card and select Add SCPC Remote
from the menu.
142
6.3
143
3. Select the Model Type of the remote from the drop-down list. The selected model type
must match the actual hardware model.
4. Enter the Serial Number of the remote.
5. A system-generated Derived ID (DID) is automatically generated.
NOTE: Serial numbers are not sufficient to uniquely identify remotes and line
cards. Serial numbers are unique within a particular model type, but can repeat
from one model type to another. Therefore a unique Derived ID (DID) is
automatically generated to avoid potential problems caused by duplicate serial
numbers.
6. For TDMA remotes, the name of the remotes Inroute Group is automatically displayed in
the Inroute Group field. This field is not applicable to SCPC remotes.
7. Enter a new User Password and Admin Password. The User Password provides access to
basic remote console commands. The Admin password provides administrator-level access
to all remote console commands. iDirect recommends changing these default passwords.
8. Select Active to make the Protocol Processor aware of this remote site once the remote
has been commissioned. A remote must be Active to join the network.
NOTE: To deactivate an active remote, clear the Active check box. A deactivated
remote is removed from the Protocol Processors current network configuration
while preserving the configuration in iBuilder.
9. Select MUSiC Box, Disable Tx PWM, Disable Authentication, and/or Link Encryption.
a. Select MUSiC Box if this remote site uses a Multi User Summing Chassis. The iDirect
MUSiC Box allows a common antenna/electronics platform to be shared across
multiple remotes 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 are not required
to remove the transmit cable during antenna pointing.)
c. Select Disable Authentication to certify a previously-uncertified remote in a
TRANSEC network. For details, see Bringing an Unauthorized Remote into a TRANSEC
Network on page 441.
d. Select Link Encryption to encrypt the connection between the remote and the
protocol processor blade. Link Encryption can only be selected if it is supported for
this remote model type.
NOTE: Link Encryption is a licensed feature. A license file must be loaded on each
protocol processor blade that supports Link Encryption. For information on
obtaining these licenses, please contact the iDirect Technical Assistance Center
(TAC).
10. To enable Sleep Mode on the remote, select Sleep in and enter a value in seconds. If
Sleep Mode is enabled, the remote conserves 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 automatically wakes from Sleep Mode when packets arrive
for transmission on the upstream carrier, provided that Trigger Wakeup is selected for
144
the service level associated with the packets. (See Adding an Application Profile on
page 275 for details.)
NOTE: For Sleep Mode to work, the 10 MHz reference must be enabled for the
BUC assigned to the remote on the Remote VSAT Tab. The 10 MHz reference is
enabled by selecting ODU Tx 10 MHz in the BUC configuration dialog box.
NOTE: When enabling Sleep Mode, also 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. See page 278 for details.
11. In the Compression area of the dialog box, select any IP compression types to be used by
this remote. For details on the different types of compression available, see Enabling IP
Packet Compression Types on page 195.
NOTE: The compression options are not available in Layer 2 networks. For
information on configuring L2oS header compression, see Remote L2oS Tab on
page 183.
Figure 141. Remote Information Tab: Transmit and Receive Parameters for TDMA Remote
1. Under Transmit Properties for a TDMA remote:
a. Enter the Symbol Rate, MODCOD, TDMA Initial Power, Spreading Factor and Payload
size of this remotes Reference Carrier. For more information, see the chapter titled
Adaptive TDMA in the Technical Reference Guide.
145
NOTE: See the Installation and Commissioning Guide for Remote Satellite
Routers for details on determining the Reference Carrier Initial Power.
b. In TDMA Max Power, enter the maximum TDMA transmit power level in dBm as
determined during remote commissioning. The default is 0 dBm. This field is not
applicable if the remote is transmitting an SCPC upstream carrier.
c. If desired, record the 1dB Compression Point determined at remote commissioning.
This field is informational only.
Figure 142 shows the Transmit Properties of an SCPC remote.
Figure 142. Remote Information Tab: Transmit and Receive Parameters for SCPC Remote
2. To configure the Transmit Properties of an SCPC remote:
a. For Carrier Name, select the remotes SCPC upstream carrier.
b. If desired, record the 1dB Compression Point determined at remote commissioning.
This field is informational only
c. Click Edit SCPC Initial Power to open the SCPC Initial Power dialog box (Figure 143).
146
d. Enter the Initial Power and Max Power for the SCPC upstream carrier selected on the
Remote Information tab by double-clicking the cells and entering the values in dBm.
e. If this remote may transmit on other SCPC upstream carriers in the future, you can
also configure the initial power and maximum power for those carriers at this time.
f.
d. You can enable Rx Only Multicast without enabling Rx Only. If Rx Only Multicast is
Enabled, the remote will receive multicast traffic even when no upstream return
channel is available. This allows remotes that are temporarily unable to transmit to
continue to receive multicast traffic.
e. If Rx Only Multicast is enabled, enter a Timeout in seconds or accept the default.
The timeout determines how often the multicast configuration data is sent to the
remote on the outbound carrier.
147
148
6.4
149
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.
NOTE: An Evolution X1 or e150 remote must use static routing to a single
gateway. RIPv2 is not supported on these model types.
150
151
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.
152
Forward Timeout - Expiration time (in ms) for elements in the forward queue
DNS Operation
The DNS component functions as follows:
1. Clients on the remote network issue DNS queries to the DNS component.
2. The DNS searches its cache for a matching response.
3. If a matching response is found, the DNS replies with the cached response.
4. If a matching response is not found, the DNS performs the following:
a. Appends the query along with a timestamp to the forward queue.
b. Sends the query to its primary DNS server.
5. If a response is received within the time specified by the Forward Timeout parameter
the DNS performs the following:
a. Adds the response to its cache.
b. Forwards the response to the client.
c. Deletes the query from the forward queue.
153
6. If a response is not received within the time specified by the Forward Timeout
parameter, the DNS performs the following:
a. Forwards the query to the secondary name server.
b. Resets the timestamp associated with the forwarded query.
7. If a response is received within the time specified by the Forward Timeout parameter,
the DNS performs the items listed in Step 5 above.
8. If a response is not received within the time specified by the Forward Timeout
parameter, the DNS deletes the query from the forward queue.
154
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.
GRE Tunnels, for setting up GRE tunnels within the iDirect system
155
2. Select Enable RIPv2 for the ETH0 (LAN) interface and/or SAT0 (Management) interface
to enable RIPv2 over the satellite link for the selected VLAN.
NOTE: RIPv2 cannot be enabled on Evolution X1 or e150 remotes.
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.
156
157
5. Right-click the remote in the iBuilder tree and select Apply ConfigurationReliable
Hub-Side.
6. Right-click the remote and clear the Activate Remote check mark to deactivate it.
158
private IP address, specify http as the port start and port end; TCP as the protocol; and 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.
159
160
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.
6.5
161
tab. (See Adding VLANs to a Remote on page 151). In Layer 2 networks, VLAN IDs can be
created in the VLAN Assignment dialog box of the X7 Switch tab. The Switch tab is only
displayed for remote Model Types with an eight port switch.
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.
A port can also be dedicated to a single user-defined VLAN or to the default VLAN. A port
dedicated to a single VLAN is referred to as an Access Port. 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.
On Evolution X7 remotes only, multiple, specific VLANs can be assigned to a port. This is
called VLAN pruning. When an X7 LAN port is dedicated to mulitple VLANs, traffic on any of
the assigned VLANs passes through the port. Other traffic is discarded.
The Switch tab allows you to perform the following operations:
Configure a port as a trunk (allow traffic on all VLANs to pass through the port)
Specify the port speed and mode (full duplex or half duplex)
162
163
In the VLAN View, right-click in the column of the port in the All VLANs row and
select All VLANs from the menu.
Figure 169. Selecting the Same Switch Setting for All Ports
5. By default, the port speed and port mode are automatically negotiated. Follow these
steps to disable auto-negotiation and select a port speed and port mode:
a. In the Port View, right-click the port and select Properties from the menu to open
the Properties dialog box.
164
165
6.6
166
167
Figure 174. Remote QoS Tab: QoS Profile Select Dialog Box
2. To assign a Remote Profile:
a. In the QoS Group pane, select a Remote Service Group in the Service Group column.
b. In the Remote Profile pane, select a Remote Profile.
3. To assign an Application Service Profile, select a non-multicast Service Profile in the QoS
Group pane.
4. To assign a downstream Multicast Service Profile, select a Service Profile under the
Multicast Service Group. See Configuring Remotes for Multicast Fast Path on page 249 for
more information.
168
5. Click OK. The new assignments are displayed on the Remote QoS tab.
In rare cases, when using Application Service Groups, you may want to assign multiple
Downstream or Upstream Service Profiles to a single remote. If you select more than one
Service Profile, the last Service Profile that you select in the QoS Profile Select Dialog Box is
designated as the Primary Service Profile. The NMS and Default Applications from the Primary
Service Profile are used by the system. The NMS and Default Applications from other selected
Service Profiles are not used. For more information see Assigning Service Profiles to Remotes
on page 243.
NOTE: Unlike Service Profiles, only one Downstream and one Upstream Remote
Profile can be assigned to a Remote.
Figure 175 shows two Service Profiles assigned to a single remote in an Application Service
Group. Service Profile 1 is the Primary Service Profile. The Primary Service Profile is always
displayed in bold typeface on the GUI.
169
Figure 177. Remote QoS Tab: Upstream and Downstream Rate Shaping
170
Your ability to configure the Downstream and Upstream Rate Shaping parameters, as well as
Allocation Fairness Relative to CIR, depends on the type of Service Group selected in the
Service Group field (Figure 172) and the QoS Mode selected on the QoS tab of your Network
and Inroute Group. Since QoS Mode only applies to Application Service Groups, the selection
among the following three options determines which parameters you can configure here:
Application Service Groups in Application Based (or Application Scaled) QoS Mode.
For a detailed explanation of Service Group types and QoS Modes, see Configuring Quality of
Service for iDirect Networks on page 201.
Table 5 on page 171 shows which QoS parameters you can select on the Remote QoS tab
depending on which of the three options listed above is configured for the remotes Network
(Downstream) or Inroute Group (Upstream). As noted in the table, you cannot configure EIR
on the Remote QoS tab unless it has been enabled for remotes in this remotes Service Group
on the QoS tab of your DVB-S2 network.
NOTE: Upstream Rate Shaping parameters such as CIR and MIR are not applicable
to SCPC remotes at the remote level of the QoS tree, since all of the upstream
bandwidth is dedicated to the physical remote. However, you can select or clear
Allocation Fairness Relative to CIR to influence how bandwidth is distributed
among the Applications running on the remote.
Table 5. Availability of Remote QoS Parameters by Service Group Type and Mode
QoS Service Group Type Applicable Parameters:
and Mode
Downstream
Applicable Parameters:
Upstream
Priority
Priority
Cost
Cost
* DVB-S2 Networks only. EIR must be enabled for the Service Group on the Network QoS tab
to select this option.
171
NOTE: For definitions of Priority, Cost, MIR, CIR, MIN, EIR, and Allocation Fairness
Relative to CIR, see QoS Properties on page 202.
If the Idle and Dormant States feature is enabled, the remote can be in one of three states:
Active, Idle or Dormant. Figure 178 shows the fields on the Remote QoS tab used to configure
this feature. The configuration of the remotes Minimum Information Rate fields determine
the system behavior in the Active State. The configuration of the Idle and Dormant States
fields determine the system behavior in the other two states.
172
173
b. In Timeout, enter the number of seconds that the remote should remain in the
previous state with no upstream user traffic before entering this state.
NOTE: By default, only upstream user traffic triggers a state change from Idle
State or Dormant State to Active State. Upstream NMS traffic does not trigger a
state change by default. However, you can change these default settings by
selecting or clearing the Trigger State Change field in your upstream Service
Levels. See Adding an Application Profile on page 275 for details.
174
EIR is enabled for CIR allocations within the range defined by the Nominal MODCOD and
the EIR Minimum MODCOD defined for 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 CIR and downstream EIR
on the Remote QoS tab when using Remote Service Groups or when the QoS mode
for the Network is set to Remote Based. See QoS Modes on page 212 for more
information about QoS Modes.
NOTE: You cannot configure EIR on the Remote QoS tab unless EIR has been
enabled for remotes in this Service Group. This applies to both Remote Service
Groups and Application Service Groups in Remote Based Mode. The minimum
possible EIR MODCOD for the remote is also determined by the Service Group
configuration. See Adding a Service Group on page 234 for more information.
175
176
6.7
Figure 182. Remote Geo Location Tab: Settings for Stationary Remotes
When commissioning a mobile remote, use the Geo Location tab to specify the remotes
mobile settings.
Figure 183. Remote Geo Location Tab: Settings for Mobile Remotes
177
The GPS Input selected determines the baud rate of the serial console interface to the
remote. For Serial or NMEA, change the Baud Rate and other serial interface parameters
as required.
3. Select Handshake Signaling to provide an input and output signal to the stabilizing
antenna through the serial console port.
4. Select Mobile Security to prevent the remotes latitude and longitude location from being
transmitted to the NMS over the satellite link. With Mobile Security selected, it is not
possible to determine the remotes location from the hub.
5. If required, change the Minimum Look Angle configured for this remotes antenna by
selecting Override and entering a new angle. Select Inherit from Satellite to use the
value configured for the satellite. (See Adding a Spacecraft on page 67.)
6. If required, 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. Select Inherit from Satellite
to use the value configured for the satellite. (See Adding a Spacecraft on page 67.)
7. If required, change the Skew Margin configured for this remotes antenna by selecting
Override and entering a value in degrees. Skew Margin is used to optimize the use of
upstream carriers for mobile remotes using non-circular polarization in Adaptive systems.
Select Inherit from Satellite to use the value configured for the satellite. (See Adding a
Spacecraft on page 67.)
8. Select a COTM type: Maritime, Vehicular, or Avionics. This selection should be consistent
with the Maximum Speed configured for the remotes inroute group.
NOTE: A high-speed COTM license is required for mobile remotes that exceed 150
mph. Avionics does not appear in the drop-down menu unless this feature licence
has been imported into iBuilder for this remote. See Managing NMS Licenses on
page 53.
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:
178
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 page 469.
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.
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.8
179
NOTE: The Tx Key Line area of the Remote Antenna section of the VSAT Tab
(Figure 184) only appears when configuring Evolution e850mp or e150 remotes.
NOTE: Beginning with iDX Release 3.1, iDirect brand BUCs and LNBs are
preconfigured in the Components folder of the iBuilder Tree.
180
181
To select the LNB frequency band and cross polarization for these Transceivers from the LNB
folder of the iBuilder Tree:
1. Right-click the Transceiver in the LNB folder and select ModifyItem.
2. In the LNB dialog box, select the correct ODU Rx DC Power and 22 kHz Tone settings for
the transceiver as follows:
a. For a DRU15F16X or DRU17F16X, select 18V for ODU Rx DC Power for crosspolarization. Select 13V for ODU Rx DC Power for co-polarization.
182
6.9
183
184
185
186
Roaming Remotes
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 page 189).
187
Roaming Remotes
188
Roaming Remotes
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 Upgrading Remotes Using
Revision Server on page 339.
2. Update the values in the Roaming Properties Update dialog box as desired.
189
Roaming Remotes
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 page 37.
The procedure beginning on page 191 explains how to modify multiple instances of the same
remote using the iBuilder Details pane. Although you can use this method to modify any or all
instances of a remote, beginning with iDX Release 2.1, a more convenient method exists to
modify all instances of the remote.
To modify all instances of the same remote:
1. Right-click the Remote in the iBuilder Tree and select Modify All Instances in the
Roaming section of the menu.
2. In the Modify Configuration Object dialog box (Figure 193), change the remote
parameters that you want to modify.
190
Roaming Remotes
191
Roaming Remotes
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.
6. Select all desired instances of the Roaming Remote in the Details pane.
7. Place the mouse pointer over the remote names in the highlighted group.
8. Right-click and select Modify from the menu.
9. Modify the remotes shared parameters as required. Only parameters that are common to
all network instances can be changed.
192
Roaming Remotes
The Add Multiple Roaming Remotes dialog box opens with a list of available remotes.
NOTE: Remotes that already exist in more than one other network may be listed
multiple times.
2. Select the remotes you want to add to the network.
NOTE: 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.
193
Roaming Remotes
The Add Roaming Remotes to Networks dialog box opens with a list of available network
/ inroute group combinations.
194
[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
In addition, iDirect supports Layer 2 Tunneling Protocol (L2TP) payload compression using
custom keys. For details, see L2TP Payload Compression on page 198.
NOTE: These compression options are not available in Layer 2 networks. For
information on configuring L2oS header compression, see Remote L2oS Tab on
page 183.
The following sections discuss these compression types.
195
Follow these steps to enable the first four compression types per remote on the remote
Information tab:
1. Right-click the Remote and select ModifyItem.
2. In the Compression area of the Information Tab, select each compression type that you
want to enable for the remote.
196
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: Evolution e8350; Evolution X5; Evolution X7; and iConnex e800/e850mp
remotes.
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.
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. To apply header
compression to other UDP packets, enable UDP header compression. (See UDP Header
Compression on page 197.)
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.
197
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.
198
199
200
7 Configuring Quality of
Service for iDirect
Networks
Quality of Service (QoS) refers to the classification and prioritization of traffic in order to
optimize the delivery of packets as they flow through an 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 maintain the QoS configurations, while offering the flexibility for
advanced users to customize the Group QoS configuration to meet the requirements of more
complex QoS models. Creating NMS users with the GQoS Planning permission restricts Group
QoS configuration changes to designated operators. Users without this permission can view
Group QoS settings, but they cannot change them. (See <Hyperlink>chapter 13,
<Hyperlink>Managing User Accounts and User Groups for details on defining users.)
This chapter contains the following major sections:
7.1
201
Priority: Priority defines the order in which bandwidth is exclusively allocated among
competing nodes. There are 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.
Best Effort: Best-effort traffic is allocated bandwidth only after all priority and costbased traffic 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.
202
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.
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 page 262 for details.
Note:
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 CIR
on page 228 for more details.)
NOTE: The above definition assumes that equal cost has been configured for
bandwidth on all competing nodes. Unequal cost will affect the proportions of
bandwidth allocated to each node regardless of whether or not Allocation Fairness
is selected.
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
page 249.) 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
203
nominal MODCOD. For more information on EIR, see the DVB-S2 chapter of the iDirect
Technical Reference Guide.
Allocation Fairness Relative to Nominal 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 scaled to information rate at the Nominal MODCODs of the
remotes. This favors remotes configured with lower nominal MODCODs, since their
satellite bandwidth allocations must increase to achieve the same information rate as
remotes with higher MODCODs. If neither this option nor Allocation Fairness Relative to
Operating MODCOD is selected, satellite bandwidth is allocated without regard to
MODCOD. This favors remotes with higher MODCODs, since the higher the MODCOD, the
greater the information rate for the same amount of bandwidth.
Allocation Fairness Relative to Operating 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 scaled to information rate at the operating MODCODs of the
remotes. This favors remotes currently operating at lower MODCODs, since their satellite
bandwidth allocations must increase to achieve the same information rate as remotes
operating at higher MODCODs. If neither this option nor Allocation Fairness Relative to
Nominal MODCOD is selected, satellite bandwidth is allocated without regard to MODCOD.
This favors remotes with higher MODCODs, since the higher the MODCOD, the greater the
information rate for the same amount of bandwidth.
204
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%
NOTE: Unlike TDMA upstream MIR and CIR, downstream MIR and CIR are not based
on IP Data Rate. Downstream MIR and CIR are based on Information Rate.
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.
205
Bandwidth
Pool
Bandwidth
Group 1
Application
Service
Group 1
Application 1
Remote 1
Application
Service
Group 2
Application 2
Remote 2
Bandwidth
Group 2
Application
Service
Group n
Remote
Service
Group 1
Remote
Service
Group n
Application 3
Remote 3
Remote A
Remote B
Application 4
Application 6
Application 7
Application 10
Application 11
Application 14
206
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). 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.
Beginning with iDX Release 2.1, there are two types of Service Groups, Application Service
Groups and Remote Service Groups. There are no restrictions on the types of Service Groups
contained in a Bandwidth Group. A Bandwidth Group may contain only Application Service
Groups, only Remote Service Groups, or both types of Service Groups.
Application Service Groups are identical to the Service Groups that existed in pre-iDX 2.1
iDirect releases that support Group QoS. An Application Service Group contains multiple
Applications. Remotes assigned to an Application Service Group share the bandwidth assigned
to the various Applications in the group.
Remote Service Groups are supported beginning with iDX Release 2.1. When using Remote
Service Groups, a remote becomes a container node for its Applications. Each remote is
configured with its own QoS properties such as MIR and CIR and independently allocates that
bandwidth to its Applications. Remote Service Groups allow you to configure bandwidth for
individual remotes and then assign multiple Applications to the remotes. The bandwidth
allocated to the Applications under a remote is taken from bandwidth granted to the
individual remote; it is not shared with other remotes as it is with Application Service Groups.
Note that this structure allows remotes to retain their QoS configuration when moving
207
between networks. See Moving Remotes Between Networks, Inroute Groups, and Line Cards
on page 305 for more information.
Figure 203 illustrates the difference between Application Service Groups and Remote Service
Groups.
Application
Service
Group
Application 1
Application 2
Remote 2
Remote 1
Remote
Service
Group
Application 3
Remote 3
Remote 1
Remote 2
Remote 3
Application 4
Application 6
Application 7
Application 10
Application 11
Application 14
Application 14
Application 15
Application 16
Application
Applications consist of the Service Levels and Rules defined to handle the various types of
traffic in your networks. Applications are defined by Application Profiles and are either
assigned to Application Service Groups or to Remotes in Remote Service Groups.
Like Bandwidth Groups and Service 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.
208
Upstream Application Profiles are associated with Inroute Groups to manage Inroute traffic.
Downstream Application Profiles are associated with Outroutes to manage Outroute traffic.
An Application Service Group contains two or more Applications. (An NMS Application and a
Default Application are required for every Application Service Group.) A Remote Service
Group does not contain Applications. Instead, a Remote Service Group contains remotes and
the remotes are assigned Applications.
Service Profile
Service Profiles are only used to define Applications for Application Service Groups. They are
not used to define Applications used directly by remotes in Remote Service Groups.
Like an Application Service Group, 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 an Application Service
Group. In other words, an Application Service Group provides a template from which you can
create your Service Profiles.
Service Profiles are assigned directly to Remotes that use Application Service Groups. 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 Application 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 Application Service Group and Service Profile.) When you add
Applications to Application 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 page 239 for further details.)
Remote Profile
Remote Profiles are used to define Applications for remotes in Remote Service Groups or
remotes that transmit a dedicated SCPC upstream carrier. Remote Profiles are not used to
define Applications used by Application Service Groups.
A Remote Profile contains one or more Applications. Each Application in a Remote Profile is
built from one or more Application Profiles. Application Profiles contain the Service Levels
and Rules defined to handle the various types of traffic in your networks.
A Remote Profile is either an Upstream Remote Profile (built from Upstream Application
Profiles) or a Downstream Remote Profile (built from Downstream Application Profiles). When
you assign a Remote to a Remote Service Group for your Network or Inroute Group, you can
select the Remote Profile to be used by the remote.
An SCPC upstream carrier is dedicated to a single remote. Therefore, a remote that transmits
an SCPC upstream carrier is not part of any upstream Service Group. You assign the Upstream
Remote Profile directly to the remote on the Remote QoS tab. (See Group QoS and SCPC
Remotes on page 211 for further details.)
Application Profile
Application Profiles are fundamental building blocks of Group QoS. They define the
Applications that are used by Service Profiles and Remote Profiles. In addition to being
209
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 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 or a Remote Profile to a remote, you are configuring the
remote with the complete set of the Applications specified in the 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.
NOTE: The concept of Virtual Remote does not apply to Multicast Applications.
Application
Service
Group
Configured in the
GQoS Group View
Application 1
Added in the GQoS
Group View from
Application Profiles
Application
Profiles
Application 2
Configured in the
Application Profiles Folder
Application n
Service Profile
Remote 1
Remote 2
Remote 3
210
Figure 204 shows the Application Service Group subtree of the Group QoS hierarchy.
Applications are configured from Application Profiles and then added to the Group QoS
Application Service Group. These Applications are then used to create a Service Profile which
is assigned to remotes. The Applications in the Service Profile are implemented on the
remotes as Virtual Remotes.
Remote
Service
Group
Configured in the
GQoS Group View
Remote 1
Remote 2
Remote
Profile 1
Remote
Profile 2
Application 1
Application a
Application 2
Application b
Application n
Application m
Like remotes that transmit TDMA upstream carriers, remotes that transmit SCPC upstream
carriers (called SCPC remotes) are part of an iDirect network and receive the shared outroute
associated with that network. Therefore, SCPC remotes are part of the networks outroute
Bandwidth Pool just like any other remote in the network. There is no difference in how
downstream Group QoS is configured and applied to a TDMA remote or an SCPC remote.
However, because each SCPC remote transmits its own dedicated upstream carrier, SCPC
remotes are not part any inroute group and therefore are not associated with an inroute
groups Bandwidth Pool. Since the upstream bandwidth is not shared with other remotes, an
SCPC remote is not part of a Service Group. Instead the entire upstream QoS tree for an SCPC
211
remote consists of the Remote, its Remote Profile, and the Applications associated with the
remote profile. This is illustrated in Figure 206.
SCPC
Remote
(Upstream)
Remote
Profile
Application a
Application b
Application n
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.
NOTE: QoS Modes only apply to Application Service Groups. Selecting a QoS mode
has no effect on Remote Service Groups. When using only Remote Service Groups,
it is not necessary to select a QoS mode for your Inroute Group or Network.
212
213
executed on the physical remote. To change properties such as Priority or Cost for Remote
Based traffic, 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 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 a
packet 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. If you choose to upgrade to Application Service Groups,
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.
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
page 239 for details.
214
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.
215
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 Application Service Group.
It cannot contain any Remote Service Groups. You cannot clone or delete the default
Application Service Group in the Multicast Bandwidth Group. You cannot insert additional
Service Groups under the Multicast Bandwidth Group.
Like other Application Service Groups, the Application Service Group in 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 Application Service Group, and the NMS
Application 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.
When 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. To prevent user multicast traffic from accidentally consuming too much
downstream bandwidth, the Multicast MODCOD of the Default Application is set to the
Maximum MODCOD of the DVB-S2 carrier. See Adding Applications to Application Service
Groups on page 236 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 page 216 for details.
NOTE: Beginning with iDX Release 3.0, you can enable Multicast Fast Path when
configuring your user multicast Applications. When Multicast Fast Path is enabled,
downstream multicast packets received by a remote are forwarded directly to the
Ethernet by the remote firmware. This bypasses software processing on the
remote resulting in improved throughput. For details on configuring Multicast Fast
Path Applications and assigning them to your remotes see Configuring Remotes
for Multicast Fast Path on page 249.
7.2
216
On the Network Group QoS tab, you can define Group QoS settings for an Outroute and
assign Group QoS Service Profiles and Remote 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 and Remote 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.
On the Remote QoS tab, you can define QoS properties for remotes using Remote Service
Groups or Application Service Groups in Remote Based QoS mode.
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 Multicast Bandwidth Group contains a single default Application Service Group
named Application Service Group.
All non-Multicast default Bandwidth Groups contain two default Service Groups:
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
page 264 for details on Group QoS profiles.)
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 opens, click the Group QoS tab.
217
and assign them to remotes that use Application Service Groups. It also allows you to assign
Remote Profiles to remotes that use Remote Service Groups.
The Group QoS User Interface has five views, described in the following sections:
Group 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.
218
Group View
The Group View shows the Group QoS Hierarchy (Bandwidth Groups, Service Groups,
Applications and Remotes) and the properties associated with each group in the tree. The
Group View illustrated in Figure 210 shows an Inroute Group with a single Bandwidth Group
divided into one Application Service Group (Appl SG 1) and one Remote Service Group (Rmt
SG 1).
A Maximum Information Rate (MIR) of 5 Mbps, with 3 Mbps configured for Appl SG 1 and 2
Mbps configured for Rmt SG 1.
Since Appl SG 1 has an MIR that is higher than its Committed Information Rate (CIR), Appl
SG 1 can be granted bandwidth over its CIR limit if all of Rmt SG 1s CIR demand is met
and additional bandwidth is available.
Since Rmt SG 1 has an MIR equal to its CIR, Rmt SG 1 will never be granted more than 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 page 202.)
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.
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.
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.
219
For Rmt SG 1, all remote priorities and cost are equal. Therefore, bandwidth will be
distributed evenly to these remotes. Each remote has a CIR of 32 kbps and will never
receive more than its MIR of 128 kbps.
NOTE: In Figure 210, only three of five remotes in Rmt SG 1 are displayed in this
view because Maximum Remotes Displayed is set to 3. You can adjust the
maximum number of remotes displayed for each Remote Service Group by
changing the setting for Maximum Remotes Displayed and clicking the Set button.
For detailed information on all QoS properties see QoS Properties on page 202. For
information on how QoS properties are applied in the Group QoS hierarchy see Group QoS
Hierarchy on page 205.
220
NOTE: The Select Group drop down menu at the top of the Service Profile View,
the Remote Profile View, and the Service Profile - Remote View, allows you to
filter on the entire Bandwidth Pool, a specific Bandwidth Group, or a specific
Service Group for display in the main window.
221
222
Remote View
The Remote View (Figure 214) shows all remotes in a Bandwidth Pool, and all Applications and
Service Levels assigned to each remote. The Remote View includes remotes in Application
Service Groups and remotes in Remote Service Groups. The Remote View groups the QoS
configuration by remote, allowing you to better understand how QoS processing will be
applied on any remote.
223
Figure 215. Configured vs. Effective MIR and CIR before Estimation
Notice in Figure 215 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 215) to display the calculator (Figure 216).
224
225
226
Notice in Figure 218 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.
Figure 219 shows the results of the following the steps in the example.
Figure 219. Configured vs. Effective MIR and CIR after Estimation
In the top image in Figure 219, 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 217) have been updated in the dialog box. In the bottom image in Figure 219,
the totals for the Configured MIR and Configured CIR that were recalculated by changing the
Estimated MIR and Estimated CIR columns (Figure 218) 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 220. This
is the result of saving the configuration in the top image of Figure 219.
227
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.
Figure 221. Competing Service Groups without Allocation Fairness Relative to CIR
NOTE: The Allocation Fairness Relative to Bandwidth CIR check box in the Group
View (Figure 221) applies to competing Bandwidth Groups in this Bandwidth Pool.
Notice in Figure 221 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
228
CIR configured for each node and the Bandwidth % column and the Cost column are identical
for the two Service Groups.
Figure 222 shows the effect of selecting Allocation Fairness Relative to CIR for BWG 1.
229
The QoS properties Allocation Fairness Relative to Nominal MODCOD and Allocation
Fairness Relative to Operating MODCOD are defined on page 204. These properties apply
only to downstream bandwidth allocated in DVB-S2 networks. These properties cannot be
configured for Inroute Groups.
For simplicity, this section assumes that configured costs and CIRs are equal when comparing
these two properties.
230
A remote does not always receive the outbound carrier at its nominal MODCOD. When
Allocation Fairness Relative to Nominal MODCOD is enabled, the effective cost of bandwidth
is fixed based on the configured nominal MODCOD. Therefore, at a given symbol rate, the
remotes information rate changes when the operating MODCOD of the remote changes. For
example, if a remote is operating below its nominal MODCOD, the remotes information rate
is reduced relative to other remotes since the remote requires more bits for error correction
than at its nominal MODCOD.
Note that when Allocation Fairness Relative to Nominal MODCOD is enabled, the MODCOD
that a mobile remote receives may vary due to differences in beam quality at various
locations in the beam footprint. This can cause the information rate received by the remote
to vary even in clear sky conditions as the remote moves across the beam. This variation in
information rate can be avoided by selecting Allocation Fairness Relative to Operating
MODCOD.
231
232
2. In the Bandwidth Group dialog box, enter a Name for the new Bandwidth Group.
233
2. In the Service Group dialog box, enter a Name for the new Service Group.
234
235
be configured for physical remotes on the Remote QoS tab. (See Remote QoS Tab on
page 166.)
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, also select the 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 229 shows a new Application Service Group inserted into a Bandwidth Group in the
Group QoS tree.
Figure 229. New Application Service Group Inserted Into a Bandwidth Group
A new Application 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 page 264 for a
discussion of Group Profiles.)
236
2. In the QoS Application dialog box, enter a Name for the new Application.
237
3. You can only select Multicast Fast Path when configuring a downstream Multicast
Application.
NOTE: Selecting Multicast Fast Path improves performance by forwarding
multicast packets received by a remote directly from firmware to the ethernet,
bypassing remote software processing. See Configuring Remotes for Multicast
Fast Path on page 249 for details.
4. 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 page 202.)
5. When configuring Group QoS for a DVB-S2 network with CIR or MIR defined, click the
MODCOD Distribution button to estimate the Effective rates for the network. See
Estimating Effective MIR and CIR for DVB-S2 Networks on page 224 for details.
Configured and Effective cost are discussed in Allocation Fairness Relative to CIR on
page 228. Allocation Fairness Relative to Nominal MODCOD and Allocation Fairness
Relative to Operating MODCOD are discussed on page 230.
6. 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.
7. If you selected Enable EIR for Remotes in Application, also select the Minimum MODCOD
Allowed. The selected MODCOD is the minimum MODCOD that can be configured for
remotes using this Application.
8. When configuring a Multicast Application for a DVB-S2 network, the Allocation Properties
display the Multicast MODCOD (Figure 231) rather than an EIR Minimum MODCOD. Select
a Multicast MODCOD for your Multicast Application.
238
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 high-volume
Application Profiles higher in the list will reduce the amount of processing time
used to check seldom-matched rules.
10. Click OK when you have finished defining the Application.
Figure 232 shows a new Application for TCP inserted into an Application Service Group in the
Group QoS tree.
239
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.
240
241
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 Service Profile View from the
menu.
2. Under the Service Profile you want to change, right-click an Application and select
Modify from the menu.
3. In the Request Properties area of the dialog box, modify the properties you want to
change.
242
243
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 page 166 for details.) Service Profiles assigned to a Remote are
displayed in the Upstream QoS and Downstream QoS sections of that tab. Figure 235 shows
two Service Profiles (SP 1 and SP 2) assigned to a single remote for an Inroute Group. (The
Service Profile shown in boldcalled the Primary Service Profilecontains the NMS and
Default Applications applied to this remote.)
244
2. Right-click anywhere in the Service Profile-Remote View and select Expand Tree to view
the current Service Profile assignments.
3. Right-click the Service Profile you want to assign and select Assign/Unassign Remote.
245
4. In the Remote Select dialog box (Figure 236), select the remote or remotes you want to
assign. Use Ctrl-click or Shift-click to select multiple remotes.)
246
NOTE: You can also change the Service Profile assignments of remotes by
selecting remotes in the Service Profile-Remote View and dragging the remotes
between Service Profiles. Figure 237 shows remote e8350 32132 being dragged
from Appl Service Group 1/SP 1 to Appl Service Group 2/SP 2.
247
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.
248
249
Figure 240. QoS Application Dialog Box: Selecting Multicast Fast Path
250
Figure 241. Selecting a Fast Path Application Profile for a Multicast Application
7. Click OK to add the Multicast Fast Path Application to the Multicast Bandwidth Group and
return to the Group View.
8. In the Group View, double-click the Profiles folder for the Multicast Service Group to open
the Service Profile View for the Multicast Application Service Group.
251
9. If the Service Profile View is empty (Figure 243, left image), right-click anywhere in the
main window and select Insert from the menu. If there are existing Multicast Service
Profiles (Figure 243, right image), right-click an existing Service Profile and click Insert.
Figure 243. Inserting a Multicast Service Profile into the Multicast Service Group
10. In the QoS Service Profile dialog box:
a. Enter a Name for the Service Profile.
b. Select the Multicast Fast Path Application that you configured in the previous steps.
Figure 244. Selecting a Fast Path Application for a Multicast Service Profile
11. Click OK to return to the Service Profile View.
12. Right click anywhere in the Service Profile View and select Service Profile Remote View
from the menu.
13. In the Service Profile Remote View, right-click your Multicast Service Profile and select
Assign/Unassign Remote.
252
253
groups to a network. For a complete description of multicast support in iDirect, see the
Technical Note titled IP Multicast in iDirect Networks.
NOTE: A remote will always forward Multicast Fast Path packets to the local LAN,
even if a persistent multicast group is not configured for the eth0 interface of the
remote. However, you should configure a persistent multicast group for your
Network to ensure that the protocol processor forwards the multicast packets to
the transmit line card for transmission on the downstream carrier.
Remote Profiles
A Remote Profile contains one or more Applications. Each Application in a Remote Profile is
built from one or more Application Profiles. Application Profiles contain the Service Levels
and Rules defined to handle the various types of traffic in your networks. (See Adding an
Application Profile on page 275 for details on creating and editing Application Profiles.)
Remote Profiles are created in the QoS folder of the iBuilder Tree under the Remote Profiles
folder. Two subfolders named Downstream and Upstream contain the Remote Profiles that
you can assign for your Networks and Inroute Groups, respectively. Figure 246 shows an
example of the Remote Profiles folder in the iBuilder Tree.
254
Remote Profiles are configured in the Upstream and Downstream Remote Profile dialog boxes.
An example of the Upstream Remote Profile dialog box is shown in Figure 247.
255
The Used By pane of the dialog box shows all remotes assigned to this Remote Profile. For
upstream profiles such as the one in figure Figure 247, the Inroute Group for each remote is
displayed in the second column. For downstream profiles, the Network containing each
remote is displayed in the second column.
You can perform the following operations on your Remote Profile:
Each Application in the Remote Profile must contain at least one Application Profile.
The NMS Application Profile must be included in one Application within the Remote
Profile.
The same Application Profile cannot be included more than once in a Remote Profile.
The last Application Profile in the last Application of a Remote Profile must be the Default
Application Profile.
256
A new Remote Profile automatically contains a single Application built from the NMS and
Default Application Profiles.
2. Enter a Profile Name for your Remote Profile.
3. To add a new Application or Modify an existing Application:
a. Right-click an Application and select Add Application or Modify from the menu.
257
c. In the Request Properties area of the Application dialog box, modify any QoS
properties you want to change for this Application. (For details on all Group QoS
properties, see QoS Properties on page 202.)
d. EIR applies only to Downstream Applications in DVB-S2 networks. Select Enable EIR to
configure EIR for this Application.
e. If you selected Enable EIR, also select the Minimum MODCOD Allowed. The selected
MODCOD is the minimum EIR MODCOD for this Application.
f.
NOTE: You can drag Applications to rearrange their order within a Remote Profile.
b. In the Choose Application Profile dialog box, select the Application Profile you want
to add to the Application.
258
Figure 253. Assigning a Remote Service Group on the Remote QoS Tab
This remainder of this section describes how to assign Remotes to Remote Service Groups
from the Group QoS Remote Profile 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.
To assign Remotes to a Remote Service Group:
1. Right-click anywhere in the Group QoS tab of a Network or Inroute Group and select
Remote Profile View from the menu.
259
2. Right-click anywhere in the Remote Profile View and select Expand Tree to view the
current Remote Service Group assignments.
3. Right-click the Service Profile you want to assign and select Assign/Unassign Remote.
4. In the Remote Select dialog box (Figure 254), select the remote or remotes you want to
assign. Use Ctrl-click or Shift-click to select multiple remotes.
260
261
262
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 258 shows the custom
key required to enable Full-Trigger CIR for Virtual Remote 2 on the remote being
configured.
263
7.3
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
264
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
page 216. You can modify the default Group Profiles, but you cannot delete them.
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.
265
266
267
2. In the Modify Configuration Object dialog box, enter a Profile Name for the new Group
Profile.
268
NOTE: Only the Group View and Service Profile View are available when working
with Group Profiles. The Service Profile-Remote View, Remote Profile View, and
Remote View, which appear on the Group QoS tab, are not applicable to Group
Profiles.
2. In the Modify Configuration Object dialog box, make the desired changes to the Group
QoS configuration. See Configuring Group QoS on page 216 for details on modifying the
Group QoS configuration.
269
If the new Group QoS tree created from the Group Profile contains at least one
Application Service Group, then:
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. This includes remotes
that were previously assigned to Remote Service Groups.
If the new Group QoS tree created from the Group Profile contains only Remote Service
Groups, then all remotes will be unassigned in the new Group QoS tree.
Once you have replaced the Group QoS configuration, if you are using Application Service
Groups, you can assign different Service Profiles to your remotes by following the steps in
Assigning Service Profiles to Remotes on page 243.
If you are using Remote Service Groups, you must assign the remotes to Remote Service
Groups in the new tree and re-select their Remote Profiles. See Assigning Remotes to Remote
Service Groups on page 259.
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.
270
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.)
271
7.4
272
Application Profiles define the Group QoS Applications that you add to your Service Profiles or
Remote Profiles. You then assign the Service Profile or Remote Profile to your remotes using
the Group QoS tab for your Bandwidth Pools or the QoS tab for your remotes. (See Configuring
Group QoS on page 216 for details.)
Filter Profiles encapsulate a single filter definition. A Filter Profile contains a group of rules,
but no Service Levels. Filter Profiles are assigned on the Remote QoS tab.
Application Profiles, Remote Profiles and Filter Profiles are stored in separate folders in the
iBuilder Tree. They are not associated with a teleport; instead they are independent of any
network hierarchy, similar to spacecraft and antenna components. Figure 266 shows the
folders that store these profiles.
273
A Modify Configuration dialog box opens to allow you to configure the profile you are adding.
Details are discussed in Adding an Application Profile on page 275 and Adding a Filter Profile
on page 279. Adding Remote Profiles is discussed in Adding a Remote Profile on page 256.
Once a Profile is configured and saved, it is added to the iBuilder Tree within its respective
folder. Figure 268 shows Group QoS Downstream Application Profiles in the iBuilder Tree.
274
If you select Clone As, the Clone As dialog box opens. 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.
You can also modify or copy an existing profile by right-clicking the profile and selecting Modify
Clone As allows you to copy profiles between the Downstream and Upstream folders.
Item, Clone or Clone As from the menu. Clone creates a copy in the current folder.
2. After you have selected the operation you want from the menu, a dialog box opens.
(Figure 270 shows an Upstream Application Profile with multiple Service Levels. New
Application Profiles will be empty.)
275
276
277
applications. However, since it can decrease throughput, it should not be selected for
applications that are not jitter-sensitive.
8. Select or clear Drop Oldest First.
9. Select Trigger Wakeup to cause remotes to automatically exit Sleep Mode to transmit
incoming LAN packets on the upstream carrier if the packets match the Service Level
definition. Trigger Wakeup applies only to upstream profiles, and affects only remotes
that have Sleep Mode enabled. (See Adding Remotes on page 142.)
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.
10. Select Trigger State Change to cause remotes to automatically change from the Idle
State or Dormant State to the Active State when incoming packets for transmission on the
upstream carrier match the Service Level definition. (See Configuring Minimum
Information Rate and Idle and Dormant States on page 172.)
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.
CAUTION: 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. 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 an
Application Profile or Filter Profile on page 280.
278
279
280
Figure 276. Selecting and Clearing the Show Protocols Name Check Box
Follow these steps to add a new rule for an Application or Filter Profile.
NOTE: Classifiers marked L2oS only in the descriptions below are used to classify
Ethernet frames in Layer 2 networks. These classifiers are not applicable to Layer
3 IPv4 networks. Other classifiers can be used in both Layer 2 and Layer 3
networks.
1. Click the Add button in the Rules pane to display the Add Rule dialog box.
281
282
Source IPv6 and Destination IPv6 address and Subnet Masks (L2oS only): To enter an
IPv6 IP address:
Source and Destination Port Ranges: Enter port range and mask. Select Same as
Source to configure the Destination Port Range to be identical to the Source Port
Range.
SVN ID (L2oS only): This field refers to the SVN ID of the Ethernet frame. One or twopart SVN IDs are allowed. Two-part SV IDs are used for QinQ tagging.
SVN PCP (L2oS only): This field refers to the PCP (Priority Code Point) field of the SDT
in an Ethernet frame.
DSCP, TOS, Precedence: If you select DSCP you cannot select TOS or Precedence. If
you select TOS or Precedence you cannot select DSCP.
Protocol: The protocol of the packet can equal to (=) or not equal to (<>) the selected
protocol.
Ethernet Type (L2oS only): This field refers to the outer-most Ethertype of the
Ethernet frame.
Effective Ethernet Type (L2oS only): This field refers to the inner-most Ethertype
contained in the Ethernet frame.
VLAN PCP (L2oS only): This field refers to the PCP field of the VLAN tag after the SDT
headers are removed.
VID Ranges: VID Ranges can be equal to (=) or not equal to (<>) the value entered.
283
284
8 Configuring a Hub
Chassis
This chapter includes the following sections:
Note:
8.1
The steps for configuring the IP address of the chassis differ depending on the type of
controller board installed on the chassis. To set the IP address for the chassis, follow the
procedure in this section that applies to your type of chassis controller board.
NOTE: If you do not know if the 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 page 286. If you have an EDAS controller board,
you will not be able to log on to the board using the MIDAS procedure.
NOTE: When changing the IP address of a chassis already configured in iBuilder,
you must update the Chassis Manager Server with the new IP address. See
Changing a Chassis IP Address on page 300 for details.
285
286
Chassis Licenses
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
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. 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 IP address. For example, to set the IP address to 172.17.2.50,
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 subnet mask. For example, to set the subnet mask to
255.255.255.0, 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 gateway IP address. The default gateway should be your
upstream router. For example, to set the gateway IP address to 172.17.2.1, enter the
command set gateway 172.17.2.1.
12. Enter the command:
reboot
The new IP settings will take effect on completion of the reboot.
13. To verify the IP settings, log on again and enter the following command:
show ip config
8.2
Chassis Licenses
Beginning with iDX Release 2.0, chassis slots must be licensed before the chassis can be
configured in iBuilder. If you have received a license file from iDirect but have not yet
287
imported the licenses, follow the procedure in Importing License Files on page 54 before
configuring the 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 the chassis, see the iDirect Features and Chassis Licensing Guide
available on the TAC web page.
8.3
The Chassis dialog box opens, containing one row for each slot and jumper. Rows are
arranged from top to bottom to mirror the chassis slots from left to right.
288
2. If the chassis license has not been imported into iBuilder, follow the procedure in
Importing License Files on page 54.
3. Enter a Name for the new chassis.
4. Enter the six-digit Serial Number of the chassis and click the Validate SN button. The
Serial Number entered must match a chassis serial number in the 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 280. Chassis Dialog Box: 20-Slot Chassis with Licensed Slots
NOTE: The IP Address displayed in the Chassis Dialog Box must match the IP
Address configured for the chassis. See Configuring the Chassis IP Address on
page 285.
5. If the chassis contains an RCM, select RCM Installed.
6. To turn power on for specific slots, or to set jumpers, click the check boxes in the State
column. Power on all slots in which line cards are installed. A jumper row follows each
group of four slot rows. Do not select a jumper check boxes unless the network spans the
adjacent virtual backplanes.
7. To associate a configured line card with a specific slot, right-click the slot and select
Assign Hub from the menu.
289
NOTE: Select Free to indicate that no modems are installed in that slot. These
associations must reflect the actual physical layout of the chassis; iBuilder cannot
map logical associations to physical line card locations.
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.
If no line cards have been associated with slots, the drop-down list displays all the line
cards currently defined in the network.
Only line cards from the same network appear in drop-down lists for other slots in the
same virtual backplane. Unassigned Solo line cards also appear in the list.
Drop down lists for other virtual backplanes do not contain any line cards from the
network already assigned.
If there are two networks in adjacent virtual backplanes, iBuilder will not allow the
jumper between those two backplanes to be set.
To assign line cards from a single network across a jumper, you must first set that jumper.
For 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.
290
8.4
The Chassis dialog box opens, containing one row for each slot and jumper. Rows are
arranged from top to bottom to mirror the chassis slots.
291
Figure 284. Chassis Dialog Box: Four-Slot Chassis with Licensed Slots
292
NOTE: The IP Address displayed in the Chassis Dialog Box must match the IP
Address configured for the chassis. See Configuring the Chassis IP Address on
page 285.
4. If the chassis contains a Reference Clock Module (RCM), select RCM Installed.
5. The Chassis Information area of the dialog box (see Figure 283) displays status
information about the IF Module (IFM) and Outdoor Power Modules (OPM) received from
the chassis.
6. The OPMs have the following configurable options:
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. If this option is selected for one
OPM, it cannot be selected 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 page 288 for details on assigning line
cards to slots and setting the jumpers.
8. You can configure line cards in a four slot chassis to supply the 10 MHz clock to the
upconverter, the downconverter, or both. Note the following:
You must select ODU Tx 10 MHz on the upconverter screen or ODU Rx 10 MHz on the
downconverter screen for these selections to appear in the menu. See Adding an
Upconverter or Downconverter on page 64 for details.
Only one line card per upconverter or downconverter can be selected for this
function. The upconverter and downconverter 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: eM1D1 (Tx and Rx);
XLC-11 (Tx and Rx); XLC-10 (Tx only); and XLC-M (Rx only).
To turn on or off the 10 MHz reference from a line card, right-click in the Tx-10 MHz
column (for the upconverter) or Rx-10 MHz column (for the downconverter) in the slot
containing the line card. Then select 10 MHz On/Off from the menu. The 10 MHz setting
will toggle between off and on.
293
294
8.5
Figure 286. Sharing a Hub Chassis Among Multiple Network Management Systems
295
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 page 423.) The HNO must also obtain a chassis license from iDirect and use iBuilder to
import the license file. (See Importing License Files on page 54.)
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 286. 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 Network Management
Servers to use slots in the same chassis.
296
297
298
299
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: 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
page 371.
8.6
300
301
302
9 Controlling Remotes
9.1
Moving Remotes Between Networks, Inroute Groups, and Line Cards on page 305
303
If the remote has been acquired into the network, the term Nominal is displayed 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 is displayed 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.
304
9.2
305
2. On the left side of the Move Remote dialog box, select the new Inroute Group for this
remote. The new Inroute Group can be in the same Network or in a different Network.
3. When moving the remote to a new network, in the Network QoS Tree section of the
dialog box, select either a Remote Service Group in the Service Group column or a
Service Profile from an Application Service Group in the Service Profile column.
4. In the Inroute Group QoS Tree section of the dialog box, select either a Remote Service
Group in the Service Group column or a Service Profile from an Application Service Group
in the Service Profile column.
5. If you selected a Remote Service Group for the new Network and/or Inroute Group, you
can also select new Remote Profiles in the Downstream and Upstream Remote Profile
sections of the dialog box.
NOTE: When moving a remote from one Remote Service Group to another, the
Remote Profile that was assigned to the remote in the original Service Group will
still be assigned in the new Service Group unless you select a new Remote Profile.
NOTE: An NMS Operator must have Group QoS permissions to select a new Remote
Profile while moving a remote. If you do not have Group QoS permissions, you will
not see the Remote Profile sections of the dialog box.
6. Click OK to move the remote. The remote is added to the iBuilder Tree under the new
Inroute Group.
You can also move remotes between Inroute Groups and Line Cards in SCPC Receive Mode, or
between two Line Cards in SCPC Receive Mode. This example shows how to move a remote
from an Inroute Group to a receive-only line card in SCPC Receive Mode.
1. Right-click the remote to be moved, and select Move from the menu.
306
Figure 293. Moving a Remote from an Inroute Group to an SCPC Line Card
2. On the left side of the Move Remote dialog box, select the Line Card that will receive the
remotes SCPC upstream carrier.
3. When moving the remote to a new network, in the Network QoS Tree section of the
dialog box, select either a Remote Service Group in the Service Group column or a
Service Profile from an Application Service Group in the Service Profile column.
4. The SCPC Channel List section of the dialog box displays all available SCPC upstream
carriers assigned to the selected line card. Select the Channel ID of the SCPC upstream
carrier that you want to assign to this remote.
5. In the Upstream Remote Profiles section of the dialog box, select a Remote Profile.
NOTE: An NMS Operator must have Group QoS permissions to select a new Remote
Profile while moving a remote. If you do not have Group QoS permissions, you will
not see the Remote Profile sections of the dialog box.
307
6. You can change the remotes Initial Power and Max Power by entering values in the fields
at the bottom of the dialog box. If these values have been pre-configured for the remote,
then the pre-configured values are displayed on the screen.
NOTE: The remote cannot become operational until the Initial Power and Max
Power are configured for the upstream carrier.
7. Click OK to move the remote. The remote is added to the iBuilder Tree under the receive
Line Card.
308
309
NOTE: If a VNO user retrieves an options file, only elements owned by or visible
to that VNO are included.
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 294.
310
Retrieving Configurations
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
iBuilder Tree for the remote. To deactivate a remote, right click the remote in the
iBuilder Tree and select Activate Remote to remove the check mark.
Figure 295 shows the iBuilder Tree menu selections for viewing and deleting a remote. Notice
that you cannot select Delete until a remote is deactivated.
NOTE: In the case of remotes, the menu allows selection of either the hub-side or
the remote-side configuration for retrieval.
311
Retrieving Configurations
2. Navigate to the PC folder in which to save the options file and click Save.
3. The options file opens in Notepad allowing you to review the configuration parameters.
312
Retrieving Configurations
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.
313
314
2. To view all configuration parameters in the dialog box, clear the Show differences only
check box. Note that differences are shown in red.
315
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).
316
317
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.
318
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.
319
After the configuration is applied to the Network, the status of the network changes from
Changes Pending to Nominal.
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.
320
4. Click OK.
3. When the message appears asking you to confirm the download, click Yes.
321
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.
322
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
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:
Comparison operations from any of these networks will show the differences.
323
324
325
326
327
Package Section
Figure 305 shows the package section.
Selected Package - Shows the most recently selected package for the selected
hardware.
Package area - Shows the packages available for the hardware selected at the Hardware
drop-down list.
Modems Section
Figure 306 shows the Modems section.
NOTE: iBuilder does not allow you to download an image package to an
incompatible element. When you select a specific hardware element, only the
elements that correspond to that hardware type appear in the Remotes or Hubs
panes in the Modems section. For example, if you select the package for
Evolution X1 KA remotes, only X1 KA remotes appear in the Remotes pane. If you
select the package for Evolution line cards, only line cards appear in the Hubs
pane.
If you do not want to download the image package to a given remote or line card,
clear the check box next to it.
328
Remotes Section
The Remotes section contains the following elements:
Select/Deselect - Use this pull-down list with the All pull-down list (directly below)
for additive and subtractive remote selection.
All - Use this pull-down list with the Select/Deselect pull-down list (directly above)
for additive and subtractive remote selection.
Nominal
Changes Pending
Deactivated
RT WARNING
RT ALARM
329
Flash started
Flash complete
Rebooting OS
REMOTE HELLO
ALARM
Deactivated
WARNING
OK
Hubs Section
The Hubs section contains the following elements:
Select/Deselect - Use this pull-down list with the All pull-down list (directly below)
for additive and subtractive line card selection.
All - Use this pull-down list with the Select/Deselect pull-down list (directly above)
for additive and subtractive line card selection.
Nominal
Changes Pending
Deactivated
RT WARNING
RT ALARM
330
Flash started
Flash complete
Rebooting OS
REMOTE HELLO
R/T State
ALARM
Deactivated
WARNING
OK
Reset check box - If selected, tells each remote to reset after the package has been
processed.
331
The Progress bar at the bottom of the dialog box indicates the status of the download.
Depending on the status of the download, you will see either Download Complete or
Download Incomplete. If you receive the latter message, this does not necessarily mean the
download failed; it simply means the sending application did not receive an ACK
(acknowledgement) from that destination device. This behavior is explained in the next
sections.
NOTE: For Multicast Download, remote option files are bundled together with the
remote package.
NOTE: At the Progress bar, download movement displays as 0 to 100% per group
of 150 remotes. Below the Progress bar, you will see an indication of which group
is being downloaded (e.g., 3 of 8). Each group has a separate Board Support
Package (BSP) and remote package.
332
Group Reset
Use the Reset check box in the Download Parameters Section on page 331.
Individual Reset
Reset a remote as follows:
1. Right-click the remote, select Reset RemoteReliable (TCP).
2. When a message appears asking if you are sure, 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.
333
334
Selection
Targets
Options
Selection Section
Figure 309 shows the Selection section.
Selected Package - Shows the most recently selected package for the selected
hardware.
Package area - Shows the packages available for the hardware selected at the Hardware
drop-down list.
335
Targets Section
Note: iBuilder does not allow you to download an image package to an
incompatible element. When you select a specific hardware element, only the
elements that correspond to that hardware type appear in the Remotes or Line
Cards panes in the Target section. For example, if you select the package for
e8350 remotes, only e8350 remotes appear in the Remotes pane.
If you do not want to download the image package to a given remote or line card,
clear the check box next to it.
Figure 310 shows the Targets section.
Remotes Section
The Remotes section contains the following elements:
Select/Deselect - Use this pull-down list with the All pull-down list (directly below)
for additive and subtractive remote selection.
All - Use this pull-down list with the Select/Deselect pull-down list (directly above)
for additive and subtractive remote selection.
336
Nominal
Changes Pending
Deactivated
RT WARNING
RT ALARM
Flash started
Flash complete
Resetting...
Reset
Rebooting OS
REMOTE HELLO
R/T State
ALARM
Deactivated
WARNING
OK
Select/Deselect - Use this pull-down list with the All pull-down list (directly below)
for additive and subtractive remote selection.
All - Use this pull-down list with the Select/Deselect pull-down list (directly above)
for additive and subtractive remote selection.
Nominal
Changes Pending
Deactivated
RT WARNING
RT ALARM
337
Flash started
Flash complete
Resetting...
Reset
Rebooting OS
REMOTE HELLO
ALARM
Deactivated
WARNING
OK
Options Section
The Options section provides the options shown in Figure 311.
338
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.
339
340
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.
Upgrade your hub equipment, including line cards and protocol processors, manually.
Then launch the Revision Server to upgrade all remote sites.
When changing remote 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.
The Revision Server dialog box opens (Figure 313), 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.
341
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.
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.
342
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.
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.
Start Highlighted: Starts the event display for the highlighted remotes
Stop Highlighted: Stops the event display for the highlighted 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.
343
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.
344
Figure 318. Selecting Revision Server Status from the View Menu
The Revision Server Status pane will appear in place of the iBuilder 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 iBuilder Tree (iBuilder Tree View tab) and the
Revision Server Status pane (Revision Server tab) as shown in Figure 319.
345
346
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.
347
348
12 Commissioning a Hub
Line Card
This section provides instructions for commissioning iDirect line cards. It discusses the
following topics:
12.1 Prerequisites
Before executing this procedure, the following tasks must have been performed at the hub:
The hub antenna is pointed and the cross polarization test performed.
The NMS client and server software are installed and running.
All hub components in the iBuilder Tree. (See Defining Network Components on
page 83.)
The iBuilder network in which this line card will operate. (See Defining Networks,
Line Cards, and Inroute Groups on page 101)
NOTE: If 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.
349
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 is displayed in Notepad as a text file. You can review the
configuration before closing the Notepad window.
350
2. In iBuilder, right-click the chassis in the iBuilder Tree and select Modify Item to open
the Chassis dialog box.
8 bits
No parity
351
1 stop bit
352
7. Note the IP address and subnet mask. You will need this information when downloading
the image packages and options file.
353
354
5. Right-click the new element and select Login to display the Login dialog box.
8. In the iSite Tree, right-click the line card and select Download Package to display the
Download Package dialog box.
355
356
f.
Dont reset
g. Repeat Step a through Step f, but this time download the hub package(s) for your line
card model rather than the BSP.
10. After you have downloaded both packages, right-click the line card in the iSite 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 page 350. Then select the options file.
12. Click the Open button.
13. Click Yes to download the options file to the line card.
14. Right-click the line card in the iSite Tree and select Reset from the menu.
At this point the new line card configuration (including the new IP address) has been applied
and you will lose connectivity to the line card. Do not disconnect the console cable.
357
358
Set the Transmit Power for the Outroute with the Satellite Operator
12.9 Set the Transmit Power for the Outroute with the
Satellite Operator
Set the transmit power for the outroute as follows:
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 page 351.
2. Configure the line card to transmit at the frequency indicated by the satellite operator by
entering the command:
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 iBuilder 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.
359
360
Modifying Group QoS Settings for VNO User Groups on page 379
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.
CAUTION: As soon as possible after you upgrade from a pre-7.0 release, you must
re-define the visibility settings for each VNO user group. VNO users will be unable
to use the system until you have done this.
361
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. Before defining VNO or
CNO User Groups, 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.
362
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:
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.
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. For more information, see Setting VNO
Permissions for QoS Profiles on page 386.
All VNO users see profiles created in the System User Group.
363
Profiles created by VNO members are visible only to members of that VNO User Group and
the System User Group.
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 iBuilder Tree that apply to
VNOs also apply to CNOs. (See Visibility and Access for Network Elements on page 362).
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.
364
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.
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.
365
366
367
3. To limit the upstream information rate, select the MaxUpstreamKbps check box and
enter the rate limit in kbps.
In Figure 335, 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.
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.)
368
In Figure 336, the inroute group is visible to three different VNO groups. VNO1 and VNO2
can only view the Inroute Group. VNO3 can perform control operations such as applying
configuration changes.
3. To modify a VNOs permissions for the selected element, right-click on the VNO name and
select the desired permissions from the menu.
369
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.
370
Figure 339. 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.
371
Figure 340 shows two versions of the same Chassis Modify screen.
372
In Figure 340, 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 340 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 340 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 341 show
the result when a VNO attempts to assign slot 1 when the slot is already occupied.
373
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.
374
6. Right-click each Slot that you want the VNO to use and grant Visibility and Control to the
VNO.
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 344.)
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 345 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.
375
Figure 346. VNO Full View: SCPC Return Channels Shared by two VNOs
When one or more SCPC return channels are owned by a VNO, the line card is automatically
Visible to the VNO. The VNO can add remotes to the SCPC line card or move remotes between
SCPC line cards and inroute groups.
A VNO can own an SCPC return channel even when the channel has not been assigned an
upstream carrier or a remote. This allows VNO users to assign upstream carriers and remotes
to the VNOs SCPC return channels without the assistance of the HNO.
NOTE: The HNO must make an SCPC upstream carrier Visible to the VNO before
the VNO can assign that carrier to an SCPC return channel or to a remote. A VNO
cannot own an upstream carrier.
NOTE: When the HNO assigns an SCPC return channel to a VNO user group, and
that channel is already associated with an SCPC upstream carrier, then the carrier
is automatically visible to the VNO user group. Furthermore, if the upstream
carrier is also assigned to a remote, then the VNO automatically owns the remote.
376
As an HNO, you can assign ownership of SCPC upstream channels to a VNO as follows:
1. Right-click the VNO user group in the iBuilder Tree and select Modify from the menu.
2. In the Full View, expand the line card to view the channels. Channels are numbered from
zero to seven.
3. Right-click the channels you want to assign to the VNO and select Owned (Figure 347).
The line card will automatically become Visible to the VNO, with Create permission.
Move remotes from the SCPC line card to another SCPC line card with owned channels
Move remotes between SCPC line cards and inroute groups that have the correct
permissions set
See Moving Remotes Between Networks, Inroute Groups, and Line Cards on page 305 for
details on moving remotes.
As a VNO user, if your VNO owns individual return channels on an SCPC multichannel line card,
then you can modify the SCPC carrier assignments as follows:
1. Right-click the line card in the iBuilder Tree and select Modify Carriers from the menu.
377
2. In the Line Card dialog box, click the Configure Carriers button to open the Select
Carrier dialog box (Figure 348).
Figure 348. Line Card Dialog Box: VNO User Selecting Configure Carriers
When opened by a VNO user, the Select Carrier dialog box shows the SCPC upstream
carriers currently assigned to the line card and any additional carriers that the VNO user
can assign. Only carriers that are visible to the VNO are displayed.
3. To assign a new carrier to the line card, select the check box of the carrier. The User
Group is automatically updated with your VNO user group name.
NOTE: A VNO user cannot select more SCPC upstream carriers than the number of
SCPC return channels owned by the VNO.
4. To remove a carrier from the line card, clear the check box of the carrier. The User Group
is automatically cleared.
NOTE: A VNO user cannot change the line card center frequency.
5. Click OK in the Select Carrier dialog box to save the new carrier assignments.
6. Click OK in the Line Card dialog box to save the changes.
378
Figure 349. 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 350, when a VNO user right-clicks the network, the user can only select
ModifyGroup QoS but cannot select ModifyItem.
379
Figure 350. VNO Network Menu with Owned GQoS Nodes but No Network Access
When the VNO User selects ModifyGroup QoS, the network dialog box is displayed with all
tabs. However, the user can only modify owned QoS 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 351 shows the VNO from Figure 349 re-configured to add
Write and Control access to the network.
Figure 351. 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 352.
380
Figure 352. 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.
381
382
383
2. In the Group dialog box (Figure 356), 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 top-level folder for the Group QoS Nodes is always
labeled Bandwidth Pool.
384
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.
385
386
Make individual QoS Profiles available to a VNO User Group or hide individual QoS Profiles
from a VNO User Group. (See Managing VNO Visibility to QoS Profiles on page 387.)
Change QoS folder permissions to allow VNO Users to create their own Upstream or
Downstream profiles. (See Allowing VNO Users to Create QoS Profiles on page 388.)
Change permissions on individual Filter Profiles to allow VNO Users to modify those
profiles. See (Allowing VNO Write Access to Individual Filter Profiles on page 388.)
For details on configuring the various types of QoS Profiles, see Configuring Group QoS on
page 216.
387
NOTE: You can also right-click the QoS profile in the iBuilder Tree and select
ModifyVNO from the menu to easily make a profile visible to multiple VNOs at
the same time. See Modifying per Node VNO Properties on page 368 for more
information.
Figure 362. Enabling the Create Permission on a QoS Folder for a VNO User Group
In Figure 362, the image on the left shows the VNO permissions set for the Upstream Remote
Profile folder by the HNO; the image on the right shows the VNO Users right-click menu for
the same folder. As illustrated on the right of Figure 362, VNO users can now add their own
Upstream Remote Profiles. Any QoS profile created by a VNO User is owned by that VNO User
Group.
388
2. Expand the tree in the Full View pane to view the profile you want to modify in the
Downstream or Upstream folder under the Filter Profiles folder.
3. Right-click the Profile in the Full View and select Write from the menu.
Clone an existing user and change the name and some of the properties
Delete a user
389
1. Right-click the User Group in the iBuilder Tree and select Add User.
2. When you select Add User, the User dialog box opens.
390
6. If you clear both of the main User Level boxes (Super User and Guest), the individual
permissions detailed in Table 8, Custom Privileges on page 396 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 is added to the iBuilder
Tree under the User Group you selected.
2. When the User dialog box opens, change the settings as desired. (For details, see Adding
a User and Defining User Privileges on page 389.)
3. Click OK to save the changes.
391
2. A new user is added to the iBuilder Tree and the User dialog box is displayed with settings
identical to the cloned user.
392
393
To open the Active Users pane, Select View View Active Users from the main menu.
Figure 368. 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
Figure 369. 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 page 393
394
Changing Passwords
Super User
395
User Privileges
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 7.)
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 8.)
Table 7. User Types and Access Privileges
Access
Level
Account Type
User Name
Password
Access Privileges
Pre-Programmed
by iDirect
Super User
admin
admin
Pre-Programmed
by iDirect
Guest
guest
guest
Custom
Defined by
Super User
Custom
Defined
Defined by
Super User or
else the VNO
Super User
must have
Manage Users
privilege
Table 8 lists the various privileges that can be granted or revoked for a custom-defined user.
Table 8. Custom Privileges
Privilege Name
396
NMS
Application
Description
Database Read
iBuilder,
iMonitor
Change Database
iBuilder
Download
Firmware
iBuilder
Apply
Configuration
iBuilder
Reset Modem
iBuilder,
iMonitor
Manage Users
iBuilder
User Privileges
Description
NMS
Application
Edit Permissions
iBuilder
Upload
Configuration
iBuilder
Basic Probe
iMonitor
Advanced Probe
iMonitor
Customize
Configuration
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
iMonitor
GQoS Planning
iBuilder
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.
397
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.
Figure 371. Message Displayed if Another User Has Modified the Configuration
398
CAUTION: You will only be notified of configuration changes if you have disabled
the feature to automatically accept configuration changes discussed in Accepting
Changes on page 13.
If you choose to save changes after being alerted that another user has modified the
configuration, then the changes made by the first user may be lost if you are both modifying
the same element. For example, if you and another user are modifying the same remote,
when the other user clicks OK to save the configuration, the modifications will not be
reflected in your remote modify window. Therefore, when you save the remote configuration,
the fields changed by the first user will be overwritten with their pervious values. To ensure
that you are not overwriting another users changes, you can cancel your changes and re-open
the dialog box.
NOTE: If you attempt to save configuration changes to a network element that
has been deleted, iBuilder will not be able to save your changes. You will see an
error message stating that iBuilder failed to save the configuration.
399
400
14 Converting to Adaptive
TDMA
This chapter explains how to convert an Inroute Group containing a uniform set of Static
TDMA upstream carriers to Adaptive TDMA.
This chapter contains the following major sections:
14.1 Overview
Prior to iDX Release 3.2, an iDirect Inroute Group consisted of a set of uniform TDMA upstream
carriers. All carriers were required to have the same modulation and coding (MODCOD) and
symbol rate.
Beginning with iDX Release 3.2, iDirect supports Adaptive TDMA. Adaptive TDMA allows
Inroute Groups to contain upstream carriers with different MODCODs and symbol rates.
Adaptive TDMA also supports multiple Inroute Group Compositions (IGCs) that vary the
MODCODs of individual Adaptive carriers to adjust to changing network conditions.
After upgrading from an earlier release to a release that supports Adaptive TDMA, all TDMA
upstream carriers in each Inroute Group are set to Static and the carrier definitions from the
previous release are not changed. This chapter explains how to convert an Inroute Group
containing all Static carriers with the same MODCOD and symbol rate to an Inroute Group
containing both Adaptive and Static carriers and multiple IGCs.
This chapter assumes that iDirects network planning tools have been used to fully define all
aspects of the Adaptive Inroute Group. Before converting an Inroute Group, read the chapter
titled Adaptive TDMA in the Technical Reference Guide and Adding an Inroute Group on
page 129.
401
All Shared Carrier Parameters and Adaptive Parameters of the Inroute Group
Line card model types, receive modes, and licensing must be correct for all receive
line cards that will receive Adaptive carriers.
Line card model types and receive modes must be compatible with SuperBurst for line
cards that will receive carriers with SuperBurst acquisition enabled.
14.3.1 Assumptions
This procedure assumes that:
402
The new Inroute Group configuration has been completely specified using iDirects
network planning tools.
The total occupied bandwidth of the Inroute Group has not changed.
All line cards are installed, operational and capable of receiving the specified carriers.
The reference carrier parameters, maximum power and initial power are set correctly for
remotes in the Inroute Group.
Carrier Constraints limit the minimum symbol rate of the remotes upstream carrier and
the maximum C/N at which the remotes bursts are allowed to be received. A remote will
not be assigned TDMA slots on upstream carriers that violate either of these constraints.
Maximum Link Impairment affects how a fading remote affects the Inroute Group
Composition selection algorithm.
NOTE: For more information, see Adaptive Parameters on page 174.
Configure the adaptive parameters for an individual remote in the Adaptive Parameters area
of the Remote QoS tab as follows:
1. If a Maximum Link Impairment is specified by the network design for the remote:
a. Select Enable.
b. Enter the Maximum Link Impairment in dB.
2. Configure any Carrier Constraints specified by the network design:
a. Enter the Minimum Symbol Rate for carriers on which the remote can transmit.
b. Enter the Maximum C/N for the remote.
403
4. Right-click the remote in the iBuilder tree and apply the hub-side changes.
Figure 374. Selecting the Payload Block Size for Adaptive and Static Carriers
3. In the Timeplan Parameters area, select Enable Superburst to use Superburst
acquisition on the carrier. Clear the Enable Superburst check box to use traditional
acquisition bursts on the carrier.
404
NOTE: Only Multichannel Line Cards and Receive-Only eM1D1 Line Cards can
receive Superbursts. Do not enable Superburst unless the receive line card to
which this carrier will be assigned supports it. For more information, see the
Remote Acquisition chapter of the Technical Reference Guide.
NOTE: All upstream carriers received by a multichannel line card must be
configured for the same type of acquisition. Superbursts and traditional
acquisition bursts cannot be received simultaneously by the same line card.
Multichannel line cards that receive more than eight carriers cannot use
Superburst.
405
406
Figure 380. Assigning the New Upstream Carrier to the Inroute Group
407
408
409
410
411
Power is set too high, the remote may cause interference on upstream carriers during
operation. If either condition is observed, re-execute the procedure for determining the
correct TDMA Maximum Power and update the configuration in iBuilder.
The procedure for determining the TDMA Maximum Power is contained in the iDirect Satellite
Router Installation and Commissioning Guide. That procedure uses iSite or Web iSite and
assumes that the installer is present at the remote site. However, the iMonitor Probe can also
be used to execute the same general procedure since it provides similar capabilities for
transmitting a test carrier and adjusting the remote transmit power. Steps for using the
iMonitor Probe are contained in the iMonitor User Guide.
Figure 387 shows the section of the iMonitor Probe used to command the remote to transmit a
test carrier.
Figure 387. Checking and Modifying the Remote TDMA Maximum Power
412
Use the Inroute Group Composition Usage display to look for discrepancies between actual
and expected usage of the IGCs configured for the inroute group. Verify that the usage
percentages correspond approximately to the predictions from the network design.
The Inroute Group Composition Usage display also shows a time line graph of IGC usage.
The selected IGC should correspond to network conditions as predicted by the network
design. Adaptive Parameters for the Inroute Group can be adjusted in iBuilder to change
the behavior of the IGC selection algorithm.
Assuming there is sufficient demand, use the Timeplan display to verify that slots are
being allocated efficiently on most or all carriers. Keep in mind that fade conditions and
constraints on individual remotes can affect bandwidth allocation.
In addition to total capacity versus allocated slots, the Timeplan display shows a time line
graph of IGC usage. This shows how the capacity and slot allocations change when a new
IGC is selected.
Use the Upstream C/N0 and Thresholds display to verify that the individual remotes
operate near the thresholds of the various carriers in the different IGCs. The Upstream
C/N0 and Thresholds display also shows the remotes current nominal carrier. This should
correspond to the predictions from the network design for the current conditions. For
example, if in clear sky conditions the remotes nominal carrier does not match the
design, the remotes TDMA Maximum Power may be set too low or incorrect constraints
may be configured for the remote.
For further details, see the iMonitor User Guide, iBuilder User Guide, and Technical
Reference Guide.
413
414
15 Converting a 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 wireless transmission 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 converting to TRANSEC, all hardware in the network must be TRANSEC-compatible. In
addition, all TRANSEC line cards and Protocol Processor blades must be licensed by iDirect to
use the TRANSEC feature. If your blades are not licensed to use TRANSEC, contact the iDirect
Technical Assistance Center (TAC).
This chapter contains the following major sections:
415
416
417
2. Ensure that Superburst acquisition is not enabled for any TDMA upstream carriers.
Superburst is not supported in TRANSEC networks.
3. Right-click the Protocol Processor in the iBuilder Tree and select ModifyItem.
The Protocol Processor dialog box opens with the Information tab selected.
418
419
Follow these steps to remove the secure data from the TRANSEC remote and to re-configure
the remote for the non-TRANSEC network:
1. Open a console session to the remote modem and log on to the root account of the
remote.
420
421
422
Appendix A Configuring a
Distributed NMS Server
The NMS server processes can be distributed across multiple NMS server machines. The
primary benefits of machine distribution are improved server performance and better use 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
The prerequisites for setting up a Distributed NMS are:
Four NMS servers, each installed with the same version of NMS software. Three of these
servers run various services and the fourth is a backup server. Existing systems with a
single Primary NMS server and a single Backup NMS server require two additional NMS
servers installed with the same version of software as the current Primary NMS.
NOTE: For information on setting up a Backup NMS server, see the iDirect
Technical Note NMS Redundancy and Failover.
A.2
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. IP connectivity between all
servers is required.
The MySQL database passwords must be identical on all NMS server machines of a
Distributed NMS. If the MySQL database passwords on the existing NMS server have been
changed from the default passwords, use the dbPasswd command to configure the same
passwords on the remaining servers.
For NMS servers with private IP addresses that require external access for running iBuilder
and iMonitor, there are two 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 page 432 for the script.
423
configured, the distribution of server processes across machines remains unchanged unless
reconfigured. This is true even when upgrading to a new release.
The standard distribution scheme is shown in Figure 391.
NMS Server 1 (Primary) runs the configuration server (nmssvr) and MySql, the chassis
manager server (cmsrv), and the Protocol Processor controller process.
NMS Server 3 (Auxiliary) runs the Event server (evtsvr) and the Latency Server (latsvr).
The latsvr is not shown in Figure 391.
NOTE: Not all distributed configurations are supported. For non-standard
configurations, contact the TAC.
A.3
424
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.
A.4
The setup script now requires a data input file containing the IP addresses of all NMS
servers that will comprise the DNMS. In earlier releases, the setup script learned these IP
addresses by sending a broadcast query on the local subnet.
X.509 certificates must be installed on all DNMS servers for the servers to communicate
during the setup procedure.
The service idirect_nms_config must be running on all servers in order to run the setup
script. This service is also required when running scripts to manage the DNMS. This service
supports the following commands:
service
service
service
service
idirect_nms_config
idirect_nms_config
idirect_nms_config
idirect_nms_config
status
start
stop
restart
425
g. On NMS 2, enter the following commands to move the NRD database files to the
correct directory and delete the temporary directory.
cd /var/lib/mysql/nrd_archive
rm -rf *.*
cd
mv /var/tmpdb/* /var/lib/mysql/nrd_archive/
chown -R mysql:mysql /var/lib/mysql/nrd_archive
rmdir /var/tmpdb/
8. Repeat all actions in Step 7 on NMS 3.
9. Log on to NMS 1 as root.
10. Execute the following commands to create the X.509 certificate:
cd /home/nms/utils/db_maint/
mkdir certs
cd certs
openssl req -x509 -nodes -newkey rsa:2048 -out cacert.pem
-outform PEM -days 1825 -keyout privkey.pem
11. Answer the prompts, or press Enter to accept the defaults.
426
427
428
A.5
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.
CAUTION: Downtime will be incurred while devices reboot.
A.6
429
5. Restart the iDirect NMS services on each server sequentially, starting on NMS 1, by
entering the following command:
service idirect_nms restart
A.7
For the NMS Downstream Application Profile, modify the Service Levels as follows:
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.
430
3. In the Rules area of the dialog box, select the Rule for that traffic.
4. Click the Edit button to open the Edit Rule dialog box.
A.8
431
A.9
432
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
433
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
MISCELLANEOUS
hub_sat_is_eth 1
manage_teleport_location
0
outroute_hub_has_rx_carrier
1
inroute_hub_has_tx_carrier
1
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
The various forms of the NMS-configuration-client.pl command are shown here. Typically, no
command arguments are required to configure a 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
:
The NMS-domain-commands.pl command stops, starts or restarts the NMS server processes
on all NMS machines. The command cab be executed on any of the server machines.
The various command forms are displayed by entering the -h option:
./NMS-domain-commands.pl -h
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"
434
435
436
B.1
437
NOTE: Beginning with iDX Release 2.1, SSH can no longer be used to log on
directly to the root account of an NMS server or Protocol Processor blade. Instead,
use SSH to log on to another account such as the idirect account. Then enter su from the command line to log on as root.
Figure 394. 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 395. Once you have created a CA and logged on to it, more menu
choices will become available.
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.
438
B.2
439
B.3
B.4
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
440
connecting first. If not connected to a host, the CA Foundry will prompt for the required host
information and establish the connection before executing the operation.
NOTE: When certifying a new remote in a TRANSEC network, please see Bringing
an Unauthorized Remote into a TRANSEC Network on page 441. The remote must
have authentication disabled and it must be configured with the current Network
Acquisition Key before it can acquire the TRANSEC network.
Follow these steps to connect to a host:
1. Start the CA Foundry and log on to a CA according to the procedure on page 440.
2. Use the arrow keys to select Host Operation from the top-level menu and press Enter.
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. Unless you are connecting to a GKD Server, accept the default port number by
pressing Return. To connect to a GKD Server, enter port number 45010.
c. Enter the admin password of the host.
Figure 401 shows an example of a successful attempt to connect to a host from a CA.
B.5
The remote options file with the remotes configuration for the TRANSEC network must be
transferred to on-site personnel for local download to the remote via iSite.
441
After the options file is loaded, the current Network Acquisition Keys must be configured
on remote before the remote can acquire the TRANSEC network. This requires access to
the remote console.
Once the remote options file (with authentication disabled) and the ACC Keys are present on
the remote, the remote will be able to acquire the TRANSEC network. At that point, you can
use the CA Foundry to connect to your remote over the air and issue the X.509 certificate.
Follow these steps to certify the remote in your TRANSEC network. This procedure assumes
that the remote has been configured in the TRANSEC network in iBuilder and that
Authentication has not yet been disabled on the GUI.
1. In iBuilder, right-click the remote in the iBuilder 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.
442
Certifying a Host
10. Use the CA Foundry to connect to the remote over the air and issue the X.509 certificate.
(See Certifying a Host on page 443 for details.)
11. Once the remote has its certificate, return to the remote configuration dialog box, clear
the Disable Authentication check box, and click OK.
12. Right-click the remote in the iBuilder Tree and select Apply ConfigurationReliable
Both (TCP) to download the configuration change.
B.6
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
TRANSEC remotes
GKD Servers
NOTE: After you issue a certificate to a Protocol Processor blade or a GKD server,
you must restart the iDirect service before it will take effect. After issuing the
certificate, log on to the root account of the blade or GKD server and enter the
command service idirect_hpb restart (blade) or service
idirect_gkd restart (GKD).
NOTE: Before certifying an auxiliary NMS server for a distributed NMS, log on to
the root account of the server and enter the command service idirect_nms
start nmssvr to start the nmssvr process. Once the auxiliary server has been
certified, stop the nmssvr process with the command service idirect_nms
stop nmssvr.
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 page 440.
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.
443
B.7
444
1. Using iBuilder, right-click the remote in the iBuilder Tree and select View
PropertiesItem.
2. Note the number in Derived ID field of the remote Information tab.
445
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 408.
For host password, enter the password of the blades admin account.
446
Appendix C Managing
TRANSEC Keys
This appendix contains procedures for managing TRANSEC keys. It includes the following
major sections:
C.1
When a remote in a TRANSEC network has missed two consecutive ACC Key updates
The current ACC Key must be determined at the hub and transferred to the remote modem.
The ACC Key is protected by a user-generated passphrase entered by the hub operator
when retrieving the key. The passphrase is required to update the key on the remote.
Transmitting the key and passphrase to the remote is done outside of the iDirect system. This
can be accomplished verbally (over a secure phone line) or through secure file transfer.
Before the key can be entered on the remote, you must retrieve the current key from the
Protocol Processor blade responsible for key distribution. To determine the current ACC key:
1. Follow the steps in Identifying the Blade that Distributes TRANSEC Keys on page 455 to
determine the Protocol Processor blade responsible for transmitting the ACC Keys to this
remotes network.
2. Log on to the idirect account of the blade identified in Step 1.
447
448
6. At this point, you will be prompted for each of the three segments (lines) of the
encrypted key and the passphrase from Step 6 on page 448. Respond to each prompt
with the requested information. You can type uppercase Q to quit at any time.
7. When asked if you want to continue, enter:
Yes
You should see a message stating that the Network Acquisition Key has been updated. At
this point, if the TRANSEC network is up and the remote is certified, the remote should
acquire the outbound carrier.
8. Once the remote acquires the network, to check the status of the remote, enter the
remotestate command. Sample output is shown below.
remotestate
TX Power:
-26.000000 dbm
TX Freq:
1115.000000 Mhz
FSD:
0
Assigned IGroup: 1
Assigned HDLC:
0xd
Assigned UID:
0x40 - 0x4e, 0x4f
TXer State:
ON
RXer Lock:
LOCKED
Modem State:
In Network
Link Layer State: In Data Transfer
Transec: Up
NOTE: Step 8 assumes the remote already has its X.509 certificate for the
TRANSEC network. If not, the hub operator can now disable authentication for the
remote on the iBuilder Remote Information tab to allow the remote to join the
network the first time. Once it has acquired the network, the hub operator can
issue the certificate to the remote over the satellite link and then re-enable
authentication on the remote. See Bringing an Unauthorized Remote into a
TRANSEC Network on page 441 for details.
C.2
449
C.3
C.4
450
For details on the TRANSEC key management protocol, see the iDirect Technical Reference
Guide.
CAUTION: Use great caution when updating the ACC Keys. Any remote that misses
two consecutive ACC Key updates will be stranded. A site visit is required to reconfigure the ACC keys on the remote.
NOTE: Even if a valid ACC Key is present on a de-certified remote, the remote
cannot send or receive traffic if you have performed two DCC Key updates.
When using Local Mode (ACC Keys generated by the Protocol Processor blades), you must
execute the ACC Key update from the blade that is generating your ACC Keys. If you have one
or more GKDs configured for your TRANSEC network, you must execute the ACC Key update
from the Master GKD. (For more information, see Global Key Distribution on page 457.)
Follow these steps to update the ACC Keys in a TRANSEC network:
1. If using Local Mode:
a. Follow the steps in Identifying the Blade that Distributes TRANSEC Keys on page 455
to determine the Protocol Processor blade responsible for key distribution.
b. Log on to the idirect account of the blade.
c. At the command line, enter the following command:
telnet localhost 13255
d. At the prompt, log on to the admin account.
2. If you have one or more GKDs configured for your TRANSEC network:
a. Log on to the root account of the Master GKD Server.
b. At the command line, enter the command:
telnet 0 46002
c. At the Username prompt, log on to the admin account. (The default password is
iDirect.)
3. On the GKD or the Protocol Processor blade responsible for generating the ACC Keys,
enter the following command to enable security commands:
csp enable
4. If this is a GKD Server, verify that this is the Master GKD by entering the command:
kd status
5. To update ACC Keys, enter the command:
kd keyroll update confirm
NOTE: The ACC Key update may take several minutes to complete. Therefore,
wait at least an hour before executing the kd keyroll update command a
second time.
451
6. To ensure that no unauthorized hosts have a valid ACC Key, wait at least one hour and
repeat Step 5.
CAUTION: Any remote that misses two consecutive ACC Key updates will be
stranded. A site visit is required to re-configure the ACC keys on the remote.
C.5
Figure 412. Viewing the ACC Key Data Structure on the Protocol Processor
452
5. Note the number of the active key. (The active key is Key 0 in Figure 412.)
NOTE: If you have one or more GKDs configured for your network, it is possible
that the ACC Keys have been updated on the Master GKD but have not yet been
accepted by the Protocol Processor blade. You can enter the kd keyroll show
command on the Master GKD to ensure that the active key on the GKD matches
the active key on the Protocol Processor blade.
6. From the root account of the NMS server, enter the following command to open a secure
connection the remote.
ssh <ip address>
where <ip address> is the IP address of the remote.
7. When prompted, enter the remotes admin password.
8. Enter the following telnet command and log on with Username admin and the remotes
admin password:
telnet localhost
Step 6 through Step 8 are illustrated in Figure 413.
453
Figure 414. Viewing the Key Roll Data Structure on a Remote Modem
11. Compare the ACC Key output of the key_mgr command on the Protocol Processor (Step 4)
with the ACC Key output of the remote keyroll_mgr key command. The active key
numbers should be the same. In the example in Figure 415, the remote has successfully
received the latest ACC Keys. Therefore the number of the active key on the Protocol
Processor (on the left) is identical to the number of the active key on the remote (on the
right).
454
C.6
455
the Protocol Processor ID is 2. if the Protocol Processor ID were 11, you would telnet to
port number 15011.
3. At the Username prompt, log on to the admin account of the Protocol Processor.
4. From the command line, enter the following command to determine the Tunnel Interface
IP Addresses of all blades responsible for multicast for this Protocol Processor:
blades query multicast
Sample output of this command is shown in Figure 418. In the figure, the Tunnel Interface
IP Address (eth1) of the multicast blade for Network ID 9 is 192.168.77.230.
456
D.1
In Local Mode, ACC Key management is not redundant across Protocol Processor blades.
Therefore, if the blade generating the ACC Keys for a TRANSEC network fails, the new
blade responsible for ACC Key generation for that network is not guaranteed to be
synchronized with the remotes. If the ACC Keys are not synchronized between the blade
and the remotes, remotes that are not in the network when the keys change cannot reacquire until the new keys have been manually configured on the remote. This requires
local access to those remotes.
457
Configuring GKDs for TRANSEC networks ensures that the ACC Keys are synchronized
across all blades that send the ACC Keys to the remotes. If a blade fails or the Protocol
Processor software restarts, the ACC keys do not change and local reconfiguration of
remotes that are out-of-network when the keys change is not required. In addition, GKD
redundancy prevents the keys from being regenerated if a GKD Server fails.
D.2
Remotes that use iDirects Automatic Beam Selection (ABS) feature must be able to move
from network to network as they travel across the globe. If an ABS remote in one network
attempted to acquire a new network with different ACC Keys, acquisition would fail.
Therefore, ACC Keys must be the same on any network that the remote is allowed to join.
Synchronizing the ACC Keys across TRANSEC networks using GKD Servers allows ABS
systems to meet this requirement.
Backup GKD
KeyDistributor
KeyDistributor
KeySync
KeySync
Master GKD
KeyDistributor
KeySync
PP Blade
PP Blade
KeySync
KeySync
PP Blade
PP Blade
KeySync
KeySync
458
In any established network of GKDs, there is only one Master GKD. The Master GKD is
responsible for generating the ACC Keys for all Protocol Processors that have that GKD
configured under it in iBuilder. All other GKDs (called Backup GKDs) are responsible for
synchronizing their keys with the Master GKD.
Each GKD is configured with a unique priority. The highest-priority GKD is the configured
Master GKD. If the configured Master GKD fails, the highest-priority Backup GKD becomes the
promoted Master GKD. When the configured Master GKD recovers, it resumes the function
of key generation and the promoted Master returns to the Backup role. Similarly, if a backup
GKD loses connectivity to the Master GKD and promotes itself to Master, it returns to Backup
status when connectivity to the configured Master GKD is restored.
A Protocol Processor blade responsible for distributing or using keys generated by a GKD
Server attempts to synchronize its keys with the Master GKD. However, if the blade cannot
communicate with the Master GKD, it may synchronize with a Backup GKD. If the blade cannot
communicate with any GKD, new keys are not generated for the network.
NOTE: In order to minimize the possibility that TRANSEC remotes do not have a
valid ACC Key, a Protocol Processor blade that has received a new ACC Key from a
GKD will not accept the next ACC Key for one hour. This one hour wait is not
enforced if key updates are performed manually using the kd keyroll update
confirm command. (See Updating the ACC Keys on page 450.)
The following sections explain how to install and run one or more GKDs.
459
460
The GKD_NODE definitions give the IP address and port number for all GKD Servers in the
GKD network as configured in iBuilder. In this case there are three GKD Servers. These
GKD_NODE definitions must be included in the GKD options file of each GKD.
All priorities in the GKD options file must match the priorities configured for the GKD in
iBuilder. Priorities must be unique. No two GKD Nodes in an options file can have the same
priority.
All GKD_NODE numbers must match the priorities configured in iBuilder. For example,
GKD_NODE_20 must have priority = 20.
The GKD_LOCAL_CFG definition at the end of the options file identifies this GKD. Since
GKD_LOCAL_CFG priority is 30 in the example, this is the options file for the GKD running
on 192.168.77.32. The options file for GKD_NODE_20 would be identical to this options
file except that the final line defining the GKD_LOCAL_CFG would be priority = 20.
Since it has the highest priority, GKD_NODE_30 is the Configured Master for this group of
GKDs. In other words, if all three GKDs are operational and connected, GKD_NODE_30 will
always assume the role of Master GKD.
TRANSEC GKD options files are backward-compatible with pre-iDX 3.2 iDirect releases
that supported Global Key Distribution of ACC keys. It is not necessary to change existing
GKD options files when upgrading to iDX Release 3.2 or later.
461
Figure 423. Protocol Processor Options File with GKD Node Definitions
4. Delete everything from the options file except the GKD_NODE definitions.
5. Add the following to the end of the options file:
[GKD_LOCAL_CFG]
priority = <This Nodes Priority>
462
where <This Nodes Priority> is the priority of the GKD that will use this options
file.
6. Select FileSave As and save the file in the folder of your choice with the name of your
choice.
7. Using WinSCP (or any other method) transfer the file to the idirect account of the GKD
Server machine.
8. Log on to the root account of the GKD Server identified by GKD_LOCAL_CFG.
9. Move the GKD options file to /etc/idirect/gkd/gkd_opts.opt. For example:
mv /home/idirect/gkd_opts_30.opt /etc/idirect/gkd/gkd_opts.opt
NOTE: Each GKD options file must be named gkd_opts.opt and must be present
in the directory /etc/idirect/gkd on the GKD Server.
To create the options files for the other two GKDs in the example, make two additional copies
of this options file and change the GKD_LOCAL_CFG definitions to match the priorities of the
other two GKDs.
463
D.3
464
The procedure in this section explains how to change the password to be the same as the
Admin Password configured for any Protocol Processor in iBuilder. To set a password that is
different from the Protocol Processors password, change the Admin Password in iBuilder and
save the configuration; follow the procedure below; then return the password in iBuilder to
the original setting.
The Admin Password is configured in iBuilder on the Information tab of the Protocol
Processor as shown in Figure 425.
465
[GKD_LOCAL_CFG]
priority = 20
[SECURITY]
admin_password =
$idi3$//kdd/$0bwUdQy2daA/d95g6/DC4KkVJ40091r0sdVSi0dqFy6lbSBO9zOiYA
qY8GtVYiCf08BricTpbNeF6C45UrNf03
5. Follow the procedure on page 463 to copy the GKD options file into the correct directory
on the GKD Server.
6. Restart the GKD service by entering the following command from the root account of the
GKD Server:
service idirect_gkd restart
7. Follow the procedure in Logging On to the GKD Console on page 464 to verify that the
password change was successful.
The Current State of this Key Distributor. (Master, Backup, Promoted Master, etc.)
The number of clients (GKDs and blades) receiving keys from this GKD.
Figure 427 shows an example of the kd status command executed on both a Master
GKD (on the left) and on a Backup GKD (on the right).
466
The Node ID of this GKD. (The Node ID equals the priority of the GKD.)
If the Key Synchronizer is connected, the IP Address of the GKD supplying the keys.
Figure 428 shows an example of the ks status command executed on both a Master
GKD (on the left) and on a Backup GKD (on the right).
467
468
Appendix E 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 procedures for configuring
the Automatic Beam Selection (ABS) feature for mobile remotes. A technical description of
this feature is contained in the iDirect Technical Reference Guide.
NOTE: Evolution X1 and e150 remotes do not support Automatic Beam Selection.
This appendix contains the following major sections:
469
E.1
470
For most parameters in map.conf, the default settings are identical and can be left
unchanged for standard installations. However, note the following differences in Figure 432:
If ABS was already in use before upgrading to this release, map.conf should already exist on
the NMS server machine. When setting up ABS for the first time, use the template file
(/etc/idirect/map/map.conf.template) on the map server machine to create map.conf. Copy
the template file to map.conf and edit the file to comply with the format if necessary.
471
idirect_map
idirect_map
idirect_map
idirect_map
start
restart
stop
status
472
E.2
Orbit-Marine AL-7104
This section explains how to configure ABS networks for use with OpenAMIP or any of the
supported antennas.
473
Follow these steps to modify one of the pre-configured ABS antenna definitions:
1. In iBuilder, right-click the reflector in the Remote Antenna ComponentsReflector
folder and select ModifyItem to open the Reflector dialog box (Figure 433).
2. Enter the Size of the Reflector in meters.
3. Enter the Offset Angle in degrees.
4. Select Controllable.
5. Select the Controller Type for the antenna.
6. On the right-hand side of the dialog box (Figure 433) you can define multiple Elevation /
Gain pairs, each of which represents the variation in antenna gain for a specific satellite
elevation. You can enter as many as 91 values, one for each degree between zero and 90,
inclusive.
During beam acquisition, iDirect uses these data points to interpolate the gain variation
for the elevation at the remotes current location. This gain variation is used in the
calculation of initial transmit power. (See the iDirect Technical Reference Guide for
details on how the initial transmit power is calculated.)
NOTE: Elevation / Gain pairs are only applicable to flat plate antennas with
multiple plates. For all other antenna types, leave this area blank. To configure
an applicable antenna, contact the antenna manufacturer for the correct data.
NOTE: When entering Elevation / Gain pairs, values must be added for both 0o
and 90o. If these two values are not included, some gain variations will be
undefined.
To add an Elevation / Gain pair:
a. Click the Add button to open the Gain dialog box.
474
7. When using OpenAMIP, you can also define Skew Angle / Gain pairs (Figure 433). Skew
angle gain affects the maximum emitted power spectral density.
Skew Angle / Gain pairs are configured in the same manner as Elevation / Gain pairs. (See
Step 6 on page 474.) The skew angle range is from zero to 90 degrees. As the configured
skew angle increases, the configured gain must decrease in value.
NOTE: Skew Angle / Gain pairs are only applicable to flat plate antennas using
the OpenAMIP antenna controller protocol.
8. When finished configuring the Reflector, click OK to save the changes.
DAC-97. (Used for any supported SeaTel DAC antenna controller: DAC-97 DAC-03,
DAC-2200, or DAC-2202)
475
476
2. The Hunt Frequency is the L-Band hunt frequency programmed into the antenna
controller. This frequency may be different for different instances of the roaming remote,
depending on the beam in which that remote instance is defined.
For Hunt Frequency, select Inherit From Downstream Carrier to automatically inherit
the remotes L-Band receive frequency for each instance of the remote. Select Override
to enter a different value in MHz.
NOTE: Noise Reference Frequency is currently not used.
3. In Rx Polarization, select the polarization of the remotes receive carrier.
4. In Tx Polarization, select the polarization of the remotes transmit carrier.
5. 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.
6. Enter the Init Tx Power Offset determined at commissioning for this remote.
The Init Tx Power Offset is used to adjust the transmit power of the remote during beam
acquisition based the EIRP budgeted for the link at the current location as received from
the beam map. The console command used to determine this value during commissioning
is described on page 487. For information on how this value is used during operation, see
the iDirect Technical Reference Guide.
Figure 438 shows the additional fields that appear on the VSAT tab for antennas configured to
use OpenAMIP, DAC-97 and AL-7104, respectively.
477
8. 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 438 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-S2 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.
9. 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 438 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.
E.3
478
NOTE: Custom keys in the [BEAMS_LOCAL] group only apply to the remote
instances on which they are defined. For a custom key in the [BEAMS_LOCAL]
group to apply to all instances of a remote, the custom key must be added to the
remote in each of the remotes networks. See Configuring the Network
Acquisition Timers on page 480 and Changing the Download Timeout on page 480.
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.
5. Right-click the remote in the remotes current network 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.
479
Default Value
Meaning
net_state_timeout
300 seconds
(5 minutes)
net_state_timeout_increment
300 seconds
(5 minutes)
net_state_timeout_max
3600 seconds
(60 minutes)
After the first failure, the remote waits net_state_timeout before it again attempts to
join the network.
Once the remote successfully joins a network, the remote resets net_state_timeout to its
configured value.
480
To change the download timeout, enter a remote-side custom key of the form:
[BEAMS_LOCAL]
download_timeout = <timeout>
where <timeout> is the value of the download timeout, in seconds.
NOTE: Custom keys in the [BEAMS_LOCAL] group only apply to the remote
instances on which they are defined.
481
482
[MAPSERVER_0]
hostname = <Ip Address>
port = <port number>
where <Ip Address> and <port number> are the local IP address and port number of the
local map server process.
CAUTION: You must apply this custom key to all instances of the remote.
For information on configuring and using a local map server, contact the iDirect TAC at (703)
648-8151.
E.4
E.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 440 shows an example of the latlong command.
483
E.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:
tlev
tlev 0
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 441 shows an example of the tlev command. The command in the example sets the
trace level to 4.
484
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
antenna debug 0 0 0 0
Spaces are required between digits when setting the trace level.
Example:
Figure 442 shows the trace output after the antenna debug command has been issued to
enable all antenna tracing.
beam debug 0
485
E.4.5 beamselector
Depending on the command line argument, the beamselector command can be used for any
of the following purposes:
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.
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.
CAUTION: Executing the beamselector switch command is a service-affecting
operation.
beamselector lock <beam number> 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 page 480.) The modem
must be restarted after commissioning to return to normal operation.
486
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.
487
map debug 0
488
F.1
Figure 445. Setting the Maximum Speed for Remotes in an Inroute Group
489
COTM Type
F.2
COTM Type
Applicable to: High-speed TDMA and SCPC remotes
Beginning in iDX Release 3.2, you can select the type of mobile remote on the Remote Geo
Location tab. The remote-side custom key mobile_remote_type required in earlier
releases is no longer needed.
For high-speed mobile remotes, select Avionics as the COTM Type on the Remote Geo
Location tab. This configures the remote for high-speed mobility.
Figure 446. Remote Geo Location Tab: Selecting Avionics for COTM Type
For more information, see Remote Geo Location Tab on page 177.
NOTE: A high-speed COTM license is required for mobile remotes that exceed 150
mph. Avionics does not appear in the drop-down menu unless this feature licence
has been imported into iBuilder for this remote. See Managing NMS Licenses on
page 53.
NOTE: The COTM Type should be consistent with the Maximum Speed configured
for the remotes inroute group.
F.3
490
F.4
For high-speed remotes experiencing frequent fades due to temporary blockage, iDirect
recommends changing this parameter to 60 seconds. To accomplish this, configure the
following custom key in the Remote-side Configuration area of the Remote Custom tab:
[OOB]
inroute_map_ttl_sec = 60
F.5
491
F.6
Maritime
30
128
256
128
256
Vehicular
150
10
256
512
256
512
Airplane
700
17
400
800
512
1024
X Band
Ku Band Ka Band
15
19000
26000
42000
63000
75
21000
29000
47000
73000
220
26000
36000
59000
98000
700
48000
64000
108000
200000
NOTE: Table 11 assumes Hub LNB stability of 1 ppm or better and an elevation
angle of 10o.
To determine the inroute ID of an SCPC return channel in iMonitor:
1. Right-click the line card in the iMonitor tree and select Line Card Stats.
2. Click OK in the Select Line Cards dialog box.
3. In the HLC Traffic Graph window, select the SCPC channel of interest.
4. Click the second tab to view the tabular data and find the Inroute ID column.
The Inroute ID for the selected channel in Figure 447 is 62.
492
FEC Blocks per Frame for Spread Spectrum SCPC Return Channels
F.7
493
4. In the iBuilder Tree, right-click the Network in which this carrier is used and select
ModifyItem.
5. In the Network dialog box, click the Custom tab.
6. Add the following custom key:
[INROUTE_id]
fec_blocks_per_frame = n
where id is the inroute ID of the SCPC return channel determined in Step 3 and n is:
floor (FEC Blocks per Frame / 4)
For example, if the number of FEC Blocks per Frame determined in Step 2 is 10, set
fec_blocks_per_frame to 2.
NOTE: Do not set fec_blocks_per_frame to a value that is less than 1.
7. Click OK to save your changes.
8. Right-click your network in the iBuilder Tree and apply the configuration to your network.
F.8
X Band
Ku Band Ka Band
Vehicular
120
21
29
47
73
Train
350
26
36
59
98
1280
48
64
108
200
Airplane
F.9
Maximum
Speed (Km/h)
494
Appendix G Remote
Locking
The remote lock feature allows individual remotes to be locked to a particular network. Once
a remote is locked with a Network Key, it only functions in a network with the same key.
Remote Locking is supported on Evolution X3, Evolution X1, and Evolution e150 remotes. The
procedure for locking these remotes differs based on remote model type.
This appendix describes remote locking for Evolution X3 remotes. Remote locking for
Evolution X1 and Evolution e150 remotes is described in the Web iSite User Guide.
The remote locking feature uses symmetric key generation when locking the remotes. A
unique and secure Locking Key is generated for each remote, using a combination of the
Network Key and a randomly generated Confirmation Word. Remote locking uses a
hardening option to permanently 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 (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 X3 Locks on page 498.
Soft Locks: The rmtlock engage command sets a Soft Lock on a remote. When the
command is first entered, a randomly-generated Confirmation Word is displayed on the
remote console. Re-entering the command with the Confirmation Word to confirm the
lock sets the Soft Lock on the remote. A remote locked with a Soft Lock can be unlocked.
A Soft Lock is removed 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, entering the rmtlock
command irrevocably burns 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 page 497.
NOTE: You must first Soft Lock an X3 remote to a network before you can Hard
Lock that remote.
495
496
497
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>
CAUTION: 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.
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.
CAUTION: RMA and shipping charges apply to all remotes returned to iDirect for
the purpose of removing a network lock.
498
Glossary of Terms
Acquisition
A process whereby the satellite modem locks onto the proper satellite carrier.
ACU
ADC
Analog
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)
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
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 (3 kHz). 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.
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
Broadcast
499
C band
Capacity
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
Coaxial Cable
Collocated
(satellites)
Committed
Information Rate
(CIR)
Common Carrier
Communications
Satellite
A satellite in Earth orbit which receives signals from an Earth station and retransmits
the signal to other Earth stations.
COMSAT
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
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
500
Dish
Downlink
The part of the satellite communications link that involves signal retransmission from
the satellite and reception on the ground. See also Uplink.
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
Elevation
Elliptical Orbit
Orbits in which the satellite path describes an ellipse, with the Earth located at one
focus.
Encoder
Equatorial Orbit
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
Feed
Focal Length
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
Full duplex
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.
501
Guaranteed
Bandwidth
Guaranteed Slots
Slots configured per VSAT and made available to that VSAT upon its request. When the
queue is depleted, these slots are taken away by the master and distributed to other
requesting VISNs as preemptive slots.
Guard Band
(guardband)
Guard Channel
Unused frequency space between carriers that prevents adjacent carriers from
interfering each other.
Half Duplex
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
(upconverter), D/C (downconverter) 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
Inclination
The angle between the orbital plane of a satellite and the equatorial plane of the
Earth.
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
Interfacility Link
(IFL)
The cable that connects the indoor unit with the outdoor unit.
Intermediate
Frequency (IF)
Ka band
Ku Band
L-Band
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.
502
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.
Margin
The amount of signal in dB by which the satellite system exceeds the minimum levels
required for operation.
Multiplexing
ODU
Outbound Carrier
Passband
Perigee
Polarization
Design technique used to increase the capacity of the satellite transmission channels by
reusing the satellite transponder frequencies.
QPSK (Quadrature
Phase Shift Keying)
Rain Outage
Loss of signal at Ku or Ka Band frequencies due to absorption and increased sky noise
temperature caused by heavy rainfall.
Satellite
Satellite
Communications
Satellite Pass
Segment of orbit during which the satellite passes nearby and in the range of a
particular ground station.
Shared hub
Single-ChannelPer-Carrier (SCPC)
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.
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.)
503
TDMA (Time
Division Multiple
Access)
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)
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
VSAT
Very Small Aperture Terminal. Means of transmission of video, voice, and data to a
satellite. Used in business applications.
504
505
506
507
508
Index
A
ABS
see Automatic Beam Selection
accelerated GRE tunnels 160
accepting changes
automatically accepting changes 13
enabling accept changes button 13
acquisition aperture 132
activating
remotes 303
active users pane 385
activity log 47 50
copying data from 49
list of selectable activities 47
viewing 48
adaptive TDMA
acquisition margin (M3) 137
adaptive parameters of inroute group 133
adding adaptive carriers to an inroute group 396
configuring adaptive parameters per remote 175
configuring uplink control parameters 137
converting an inroute group to adaptive TDMA 394
converting to adaptive TDMA 393
enabling superburst 77
fade slope margin (M1) 137
goal of frequency hopping in adaptive TDMA 130
hysteresis margin (M2) 137
inroute group composition
allowed dropout factor for IGC selection 133
carrier-specific IGC parameters 136
configuring IGCs 134
default IGC 133
enabling a fixed IGC 133
selecting a carriers MODCOD for an IGC 136
update frequency for IGC selection 133
measurement spacing 137
prerequisites for converting to adaptive TDMA 394
selecting adaptive modulation 77
selecting carrier payload size 77
static vs. adaptive TDMA carriers 131
updating an inroute group composition 397
verifying network operation after conversion 403
antenna 65
antenna, adding 65
applying changes to roaming remotes 324
applying configurations 316
Automatic Beam Selection 461 480
adding beams to a network 463
adding elevation / gain pairs for flat plate
antennas 466
adding skew angle / gain pairs for flat plate antennas using OpenAMIP 467
antenna reflector definition 465
changing the GPS interval 474
changing the minimum look angle 470
changing the usable beam timeout 473
configuring a local mapserver IP address 474
configuring a remote for 467
configuring hunt frequency 469
configuring the initial tx power offset 469
determining a remotes initial tx power offset 479
determining beam numbers 479
disabling or enabling the rx-only feature 474
forcing a beam switch 478
IP address of antenna 468
muting the remote transmitter when mapless 473
reading the tx power from the beam map 479
remote console commands 475
setting download timeout 472
setting network acquisition timers 472
setting OpenAMIP parameters 469
setting Orbit SBC parameters 470
setting SeaTel DAC parameters 470
setting up the configuration file 462
starting the map server 464
supported antennas 465
Automatic Beam Switching
see Automatic Beam Selection
B
bandwidth
adding 72
beam selection
see beam switching for mobile remotes; Automatic
Beam Selection
beam selection for roaming remotes 195
before you start
information needed 8
preparing equipment 8
509
Index
blades
adding 94
BUC
adding to a remote 182
button
accept changes 14
right mouse 25
C
CA Foundry 429 444
connecting to a host 432
creating a CA 431
creating a certificate authority 431
executing 63, 430
issuing host certificates 435
logging on to a CA 432
navigating in 430
revoking host certificates 436
carrier
acquisition aperture 132
adding downstream carriers 73
adding SCPC upstream carriers 78
adding TDMA upstream carriers 75
assigning upstream carriers to inroute groups 134
defining an alternate downstream carrier 109
guard interval 133
information rate 77
large block 77
rules for assigning TDMA carriers to inroute
groups 131
small block 77
switching to an alternate downstream carrier 117
symbol rate 77
transmission rate 77
uplink/downlink center frequency 74, 76, 80
certificate authority, creating 431
chassis
adding the initial hub chassis 285
assigning line cards to slots 290
configuring and controlling 288
EDAS vs. MIDAS controller boards 285
four-slot chassis
configuring 291
enabling 10 MHz clock on a tx line card 293
enabling 22 kHz tone 293
enabling BUC voltage 293
enabling LNB voltage 293
limitation on DC voltage supplied by 4-IF
510
chassis 293
LNB voltages supplied by chassis 293
selecting high or low LNB voltage 293
use of slot 5 291
installing 8
permanently enabling chassis license downloads 63
rules for assigning line cards to slots 290
setting the IP address 285
sharing slots on more than one NMS 295
validating a chassis license 289
chassis groups
not supported in this release 285
choose details
feature 37
cloning
remotes 187
user accounts 383
CNO User Groups
adding and modifying 357
visibility and access 356
commissioning line cards
See hub commissioning 341
comparing configurations 314
components
bench test 16
folders 16
QoS folders 16
remote antenna components 17
compression
CRTP performance characteristics 199
enabling compression types on remotes 196
L2TP payload compression 199
RTP header compression performance
characteristics 199
TCP payload compression 197
UDP header compression 198
UDP header compression performance
characteristics 198
UDP payload compression 199
UDP payload compression compared to TCP payload
compression 199
configuration changes 34
configuration state 42
changing 45
Index
downloading
concurrently to remotes and hub 326
images
TCP 330
interactions 329
multicast 326
multiple images 326
out of network remotes 328
using revision server 331
downloading configurations 316
canceling 318
chassis 319
line card 320
network 319
protocol processor 319
DVB-S2
adjusting CCM network parameters 140
configuring a remotes maximum MODCOD 177
configuring a remotes nominal MODCOD 177
configuring network parameters 139
estimating effective CIR and MIR for ACM
outbound 224
estimating information rate for ACM outbound 83
fast fade algorithm 138
line card model types supported 103
network-level parameters defined 138
selecting a MODCOD range for ACM 75
E
elements 15
D
daisy chaining of chassis
not supported in this release 285
database, simultaneous changes 390
deactivating
remote 303
details
choosing 37
choosing details feature 37
creating sets of 37
view 35
DHCP 155
distributors
adding 150
listing on remotes 149
DNS 154
downconverter 65
adding 66
F
find toolbar 29
Firmware
downloading to remotes and line cards 326
folders 15
adding entries 19
BUCs 15
component 16
customers 16
distributors 15 16
empty 16
Hub RFT components 16
LNBs 15
manufacturers 15
operators 16
QoS profiles 15
reference information 18
remote antenna components 15
511
Index
four-slot chassis
see chassis, four-slot chassis
frequency hopping 130
frequency translation 67
G
geo location
remotes 178
GKD
bringing a GKD online for the first time 456
changing a GKDs password 456
configuring in iBuilder 452
defined 449
determining the clients of a GKD 459
determining the time of the next key update 460
installing 451
installing a GKD options file on a server 455
kd status and ks status commands 458
logging on 456
starting a GKD 455
GRE tunnels 160
Group Edit
procedure for group edits 41
rules and restrictions on group edits 41
Group QoS
see also QoS
allocation fairness relative to nominal or operating
MODCOD 230
allocation properties vs. request properties 233
allowing VNO users modify filter profiles 380
allowing VNO users to create QoS profiles 380
application scaled QoS mode vs. application based
QoS mode 214
application service groups vs. remote service
groups 207, 210
assigning ownership of QoS nodes to VNO user
groups 373
assigning remotes to remote service groups in remote profile view 259
bandwidth allocation algorithm 205
bandwidth allocation fairness relative to CIR 203
bandwidth allocation fairness relative to Nominal
MODCOD 204
bandwidth allocation fairness relative to Operating
MODCOD 204
bandwidth allocation for SCPC return channels 212
best-effort traffic defined 202
changing properties on individual remotes 247
changing the order of application profiles within
512
applications 238
Committed Information Rate defined 202
configuring a remotes maximum MODCOD 177
configuring a remotes nominal MODCOD 177
configuring bandwidth allocation fairness relative
to nominal MODCOD 230
configuring bandwidth allocation fairness relative
to operating MODCOD 231
configuring group QoS settings for VNO user
groups 371
cost defined 202
cost-based traffic defined 202
default and NMS applications for remotes with multiple service profiles 244
default applications in service profiles 239
effective cost with allocation fairness relative to
CIR 228
enabling EIR for remotes in group for remote based
mode or remote service groups 235
Enhanced Information Rate (EIR) described 203
estimating effective CIR and MIR for DVB-S2 ACM
outbound 224
for SCPC remotes 211
full-trigger CIR defined 203
group view applications vs. service profile view
applications 241
group view example 219
Maximum Information Rate defined 202
multicast bandwidth group 215
operations on remote profiles 256
preconfigured application profiles 273
priority defined 202
QoS properties defined 202
relationship between information rate and IP data
rate 204
remote profiles described 254
selecting a multicast MODCOD 238
setting VNO permissions for QoS profiles 378
Sticky CIR defined 203
tree structure 205
views 218
visibility of QoS profiles for VNO users 379
VNO configuration of request properties on owned
QoS node 375
guard interval for TDMA carriers 133
guest user 389
H
high power amplifier See HPA
HPA 65
adding 68
Index
I
iBuilder
description 9
installing 11
iDirect network architecture example 2
Idle and Dormant States
configuring 173
triggering state changes 175, 278
images 325
downloading 326
interactions 329
out of network 328
TCP 330
downloading multiple units 326
UDP multicast 326
iMonitor
description 9
information rate 77
inroute group compositions 134
inroute groups
adaptive parameters defined 133
adding 130
assigning upstream carriers 134
configuring the maximum speed of remotes 132
description 130
frequency hopping 130
setting acquisition aperture for carriers 132
setting the guard interval for TDMA carriers 133
shared TDMA carrier parameters 133
static vs. adaptive carriers 131
installation
NMS applications 11
interface
using NMS GUI 21
IP configuration on remotes 151 161
iSite 9
using to download a line card 345
L
LAN
interface 153
remotes 151 154
large block 77
latitude
teleport 86
Layer 2 Over Satellite (L2oS)
adding a VLAN ID to the X7 switch 164
adding SVNs to a remote 185
classifying IPv6 packets in Layer 2 networks 282
configuring a remote local ID for an SVN 186
configuring L2oS header compression 186
configuring L2oS hub parameters 100
configuring the hub VLAN or QinQ Ethertypes 100
configuring the MAC address of the upstream switch
for VPWSEPC 101
configuring the remote L2oS parameters 184
configuring the remote SDT parameters 185
configuring the remote VLAN or QinQ
Ethertypes 185
enabling networks for L2oS 93
overriding the default service mode settings at the
hub 101
selecting the hub SDT mode 100
selecting the L2oS operating mode 100
legend 32
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 63
sharing chassis slot licenses on more than one
NMS 295
validating a chassis license 289
line cards
adding
receive 109
standby 119
transmit 107
transmit/receive 107
adding a TDMA standby line card 121
adding receive carriers to a multichannel line
card 112
commissioning See hub commissioning
downloading using iSite 345
enabling 10 MHz clock from the four-slot chassis
513
Index
screen 293
failure recovery 128
managing redundancy relationships 122
multichannel line card operational frequency
band 113
NMS failover algorithm 129
performing manual switchover or failover 127
prerequisites for automatic failover 119
receive carrier types 109
receive mode restrictions 110
receive modes 109
receive-mode licenses required 110
receive-only line card types 109
rules for assignment to chassis slots 290
selectable line card types in iBuilder 106
selecting carriers for multichannel line cards 113
setting tx power 351
solo Tx/Rx line card described 106
supported model types 103
TRANSEC-compatible model types 408
types of redundancy relationships 119
LNB
adding to a remote 182
logging in 12
passwords 12
to other servers 13
longitude
spacecraft 70
teleport 86
M
main toolbar 29
management interface 153
mobile remotes
See remotes: mobile remotes 179
setting the maximum speed for an inroute
group 481
modifying
accepting changes 13
multicast fast path
configuring 249
defined 216
enabling encryption 105
selecting for a GQoS application 238
514
N
NAT 156
network architecture example 2
network tree, See tree
networks
adding 104
deactivating 106
inroute groups
adding 130
assigning upstream carriers 134
description 130
line cards
adding receive 109
adding transmit 107
adding transmit/receive 107
NMS
applications 8
distributed NMS server 415
iVantage NMS components xxxiii
main components 7
multiple users accessing 13
servers used 9
setting up a distributed environment 417
O
ODU Tx 10 MHz 68
ODU Tx DC power 68
options files 309
hub-side and remote-side 310
orbital inclination 70
P
packet segmentation
setting a downstream segment size 177
panes
active users 32, 385
choose details 37
configuration changes 34
details 35
legend 32
network tree, See tree
See also dialog boxes
passwords 12, 387
properties
viewing element 35
Index
protocol processor
adding 90
blades 94
installing 8
TRANSEC support for 90
Q
QoS
Committed Information Rate defined 202
cost-based traffic defined 202
Maximum Information Rate defined 202
see also Group QoS
assigning a filter profile to a remote 168
assigning a remote profile to a remote 168
assigning a service profile to a remote 168
assigning multiple service profiles to a remote 170
bandwidth allocation fairness relative to CIR 203
bandwidth allocation fairness relative to Nominal
MODCOD 204
bandwidth allocation fairness relative to Operating
MODCOD 204
best-effort traffic defined 202
configuring a remotes maximum MODCOD 177
configuring a remotes nominal MODCOD 177
configuring EIR for a physical remote 176
configuring Idle and Dormant States 173
configuring Minimum Information Rate 173
cost defined 202
custom key for full-trigger CIR 263
Enhanced Information Rate (EIR) described 203
for SCPC remotes 211
full-trigger CIR defined 203
normal CIR vs. sticky CIR vs. full-trigger CIR 202
preconfigured profiles 273
priority defined 202
QoS properties defined 202
remote parameters by service group type and QoS
mode 172
remote QoS Tab 167
sticky CIR defined 203
R
receive line card
adding 109
receive properties
remotes 147
515
Index
remote antennas 70
configuring the default skew margin 70
configuring the skew polarization 70
GPS Input settings defined 179
handshake signalling 180
high-speed COTM configuration 481
inroute map stale timeout for high-speed TDMA
remotes 483
LFO correction angle for SCPC mobile
remotes 486
minimum symbol rates for mobile remotes 483
overriding the maximum skew for a remote
antenna 179
overriding the minimum look angle for a remote
antenna 179
overriding the skew margin for a remote
antenna 179
security setting 179
selecting the COTM type 179
spread spectrum blocks per frame for high-speed
SCPC remotes 485
TDMA upstream acquisition range for high-speed
remotes 482
upstream acquisition range for SCPC return
channels 484
model type 146
moving between inroute groups and line cards 306
moving between networks, inroute groups and line
516
cards 305
multicast groups 162
MUSiC Box 146
NAT 156
passwords 146
port forwarding 159
receive properties 147
receive-only
configuring for 149
rx-only multicast 149
remote antenna 182
resetting 329
roaming remotes 188 196
adding multiple remotes to a network 193
adding remotes to multiple networks 194
applying changes 324
beam selection for 195
configuration changes 322
managing configuration of 189
modifying all instances 191
modifying multiple instances 192
options files for 322
pending changes across networks 323
selecting a BUC 182
selecting an LNB 182
serial number 146
serial number, system-generated 146
sleep mode
enabling 146
triggering wakeup 278
static routes 156
supported model types 143
switch tab 162 166
copying data to a spreadsheet 166
dedicating a port to a VLAN 163
default settings 163
setting a port as a trunk 165
setting the port speed and port mode 165
TRANSEC-compatible model types 408
transmit properties 147
reference carrier parameters 147
SCPC initial power 148
SCPC max power 149
TDMA max power 148
VLAN 151 154
VSAT 180
requirements
system 11
resetting 329
retrieving configurations
modified vs. existing 312
multiple 312
single
last modified vs. existing 311
Index
S
saving configurations
TCP vs. UDP 321
SCPC upstream carriers, configuring uplink control
parameters 81
servers 9
sleep mode
enabling on remotes 146
triggering wakeup on remotes 278
small block 77
spacecraft 69 70
adding 69
longitude 70
spectral inversion 68
spread spectrum
selecting a TDMA upstream spreading factor 78
selecting an SCPC upstream spreading factor 81
static routes 156
status
elements 42
status bar 31
super user 389
switch, eight-port: see remote: switch tab
symbol rate 77
symbol rate vs. transmission rate 77
system requirements 11
T
TCP payload compression 197
TCP vs. UDP download 318
teleport 85 88
adding 85
adding a backup 86
latitude 86
longitude 86
toolbars
configuration changes 34
details 35
find 29
icons 29
legend 32
license toolbar 56
main 29
main menu 30
status bar 31
view menu 30
transceiver
selecting frequency band and cross pol mode 183
selecting on the remote VSAT tab 182
supported models 182
TRANSEC
bringing a GKD online for the first time 456
CA Foundry, See CA Foundry
certifying an unauthorized remote 433
certifying hosts before converting to TRANSEC 408
changing a GKDs password 456
changing DCC key update frequency 442
changing the ACC key update frequency 459
comparing hub and remote ACC keys 444
configuring ACC keys on a remote 439
configuring GKDs in iBuilder 452
converting a network to TRANSEC 407
converting remotes to non-TRANSEC 412
description 407
determining the clients of a GKD 459
determining the network ID 447
determining the time of the next ACC key
517
Index
update 460
enabling on protocol processor 91
example of a TRANSEC sub-tree 409
finding the blade that distributes keys 447
GKD defined 449
GKD kd status and ks status commands 458
GKD options file example 453
installing a GKD 451
installing a GKD options file on a server 455
key distribution requirements for ABS 450
line card and remote model types supported 408
local mode for ACC key distribution 449
logging on to a GKD 456
protocol processor described 90
starting a GKD 455
updating ACC keys 442
updating DCC keys 441
translation frequency 71
transmission rate 77
Transmit Key Line, enabling on e850mp 182
transmit line card
adding 107
transmit properties
remotes 147
transmit/receive line card
adding 107
transponder
adding 70
tree
elements 15
elements and folders 25
folders 15
tree view, See tree
treebar, See tree
U
UDP payload compression 199
up converter 65
upconverter
adding 66
upgrade assistant
See revision server
uplink control parameters
acquisition margin (M3) 137
configuring adaptive UCP parameters 137
configuring for SCPC upstream carriers 81
fade slope margin (M1) 137
hysteresis margin (M2) 137
measurement spacing 137
518
V
VLAN
adding 96
default vs. upstream 153
on eight-port switch: see remote: switch tab
remotes 151 154
upstream interface 96
VNO guest, see users: VNO guest
VNO super user, see users: VNO super user
VNO User Groups
access rights for SCPC return channels 368
adding and modifying 357
allowing VNO users modify filter profiles 380
allowing VNO users to create QoS profiles 380
assigning ownership of QoS nodes 373
assigning ownership of SCPC return channels 369
configuration of request properties on owned QoS
node 375
configuring group QoS settings 371
creating and managing 356
modifying visibility and access 360
setting permissions for QoS profiles 378
setting rate limits 359
sharing a chassis among multiple VNO user
Index
groups 363
visibility and access 354
visibility of QoS profiles 379
VNO operations on line cards in SCPC return
mode 369
VSAT 180
X
X.509 certificates
issuing to hosts 435
revoking from hosts 436
warning properties 50 55
categories of warnings 50
clearing customized properties 54
configurable properties 50
customizing for specific network elements 53
distinguishing customized warnings 54
global vs. customized 51
of line cards 129
of protocol processors 94
of remotes 187
setting global properties for network elements 51
519
Index
520
iDirect
13861 Sunrise Valley Drive, Suite 300
Herndon, VA 20171-6126
+1 703.648.8000
+1 866.345.0983
www.idirect.net
Advancing a Connected World