PM1VD 000000 000 001 - Rev03

Discovery
Series
Product Manual
PM-1VD-000000-000
Revision
03
006
SpaceBridge
Change History
Rev Corrections
001 Draft
Major re-write:
002 • Upgrade to NMS 5
• Upgrade to 7000 series IDU’s
003 • Rebranded
PM-1VD-000000-000 Discovery Product Manual Revision 3

Change History
4 Discovery Product Manual Revision

NMS Configuration
This manual contains the information that describes the installation, operation and
maintenance procedures for the Discovery Series.
The Standards and Safety Section contains the guidance and precaution instruc-
tions necessary to prevent accidents from occurring when working with the units.
Reference Documents
For more information, please refer to the following documents
Item Document Number Title

[A1] PM16A-400009-000 R800 Users Guide
[A2] PM851615 S5120 / S6120 IDU Terminal User manual.
[A3] PM16A-007xxxx-000 S7400 IDU Terminal Users Manual
[A4] Assorted IPsec Server. Please refer to the applicable IPsec
Server manufactures web site.
[A5] PM851682 VSAT Terminal S5220 MESH
[A6] PM851636 VSAT Terminal S6520 A-SAT
[A7] PM851674 VSAT Terminal S5420/S6420
[A8] PM16A-007xxxx-xxx VSAT Terminal (7000 series based)
Document Information
This manual and all the documents listed above cover the complete Discovery Series
product range.
Typing Conventions
Option Description
text item of interest
Select Select the applicable item

Advisory
The detailed use of the software applications covered in this manual apply
to the Discovery Hub series of products. These software applications do
contain additional functions that are outside of the scope of Discovery
series Hubs, and Network Operators are advised that should they wish to
use commands not covered in this manual, they should first seek advice
from SpaceBridge’s customer support center before proceeding.
SpaceBridge is not be responsible for unauthorized use.
Proprietary
Copyright Notice
Copyright © by SpaceBridge. All rights reserved. This manual may not be reproduced
or disclosed in whole or in part by any means without the written consent of SpaceBri-
dge. In recognition of its continued commitment to product improvement SpaceBridge
reserves the right to change the information contained herein without notice.
Customer Support and Service
Contact SpaceBridge for customer support and service at the following office;
Head Office
SpaceBridge
657 Orly Avenue
Dorval, Quebec
H9P 1G1
Tel: (514) 420 0045
E-mail: [email protected]
Please visit our web site at: www.spacebridge.com
Printed in Canada

Table Of Contents
Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
NMS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Document Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Typing Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Proprietary .......................................................7
Chapter 1 Safety Information and Standards . . . . . . . . . . . . . . . . . . . . . . . . . 29
Informational Warnings or Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Handling Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
FCC Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Warranty and Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Extended Warranty Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 2 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.1 System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.2 System OverView. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.3 System Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.4 Discovery Block Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5 Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5.1 1 RU Interface Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5.2 2 RU Interface Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.3 Flight Case Interface Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5.4 Gigabit Ethernet Ports Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Chapter 3 Site Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.1.1 Basic Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.1.2 Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.1.3 Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 4 Discovery Hub Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.1 Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.2 General Warnings and Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.3 Visual Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.4 Installing Your Discovery Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.4.1 Connecting to Your Discovery Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.4.1.1 Installing the Grounding Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Table Of Contents
4.4.1.2 Installing a Local Keyboard/Mouse and Monitor (Optional) . . . . . . . . . . . . . .58

4.4.1.3 Connecting the RF Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
4.4.1.4 Ethernet Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
4.4.1.5 Power Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Chapter 5 IMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
5.2 IMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
5.2.1 IMS Server Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
5.2.2 IMS Server (Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Chapter 6 Start-up and Shut-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

6.1 Switching ON your Discovery Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
6.2 Switching OFF your Discovery Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
6.2.1 Closing the QPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
6.2.2 Closing the IMS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Chapter 7 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

7.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
7.2 User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
7.3 Accessing the Discovery Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
7.3.1 Access Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
7.3.1.1 Direct Access Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
7.3.1.2 Remote Access Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
7.3.2 Access Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
7.3.2.1 Direct Access Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
7.3.2.2 Remote Access Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
7.3.3 Logging in to the IMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
7.3.3.1 Adjusting Discovery Hub’s Remote Access List . . . . . . . . . . . . . . . . . . . . . . .77
Chapter 8 Introduction to the NMS Application . . . . . . . . . . . . . . . . . . . . . . .79

8.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
8.2 Accessing the NMS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
8.2.1 Direct Access to NMS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
8.2.2 Access to NMS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
8.3 Starting the NMS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
8.3.1 Information Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
8.3.2 Navigation Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
8.4 Navigating the NMS User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
8.4.1 Tree Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
8.4.2 Navigation Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Chapter 9 NMS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

9.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
9.2 Pre-Configured Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
9.2.1 VCC Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Table Of Contents
9.2.2 PID Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

9.2.3 IP Address Ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9.2.4 RL QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9.2.5 FL QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
9.2.6 FL QoS Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
9.2.7 FL IP Routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.2.8 SIT Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.3 System Setup Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
9.4 Managing your SIT Group(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
9.4.1 Adding a SIT Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.4.2 Deleting a SIT Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
9.5 Managing your SIT’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
9.5.1 Adding SIT’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
9.5.2 Modifying SIT’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
9.5.3 Adding SIT Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
9.5.4 Traffic Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
9.6 Defining and Changing the QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
9.6.1 Defining Default Quality of Service (QoS) Profiles . . . . . . . . . . . . . . . . . . . . . . 112
9.6.2 Sit Group QoS Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
9.6.3 SIT Return Link QoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
9.6.3.1 SIT Return Link Quality of Service Change (Dynamic) . . . . . . . . . . . . . . . . 117
9.6.3.2 SIT Return Link Quality of Service Change (Overwritten). . . . . . . . . . . . . . 119
9.6.4 Forward Link Quality of Service Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
9.6.5 Viewing your Service Level Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
9.7 Forward and Return Link Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.7.1 General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.7.2 Service Provider Forward Link Service Level Agreement (SP FL SLA)
Updating or Adding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.7.3 Service Group Forward Link Service Level Agreement (SG FL SLA) Up-
dating or Adding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.7.4 Multicast IDU Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.8 Frequency Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
9.8.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
9.8.2 Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.8.2.1 Frequency Band (Updating or Adding) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
9.8.2.2 Deleting a Frequency Band. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
9.8.3 Viewing Frequency Band Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
9.8.3.1 Frequency Guard (Updating or Adding) . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
9.8.3.2 Deleting a Frequency Guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
9.8.4 Forward Link Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
9.8.4.1 FL MODCOD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
9.8.4.1.1 MODCOD (Updating or Adding) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
9.8.4.1.2 Deleting a MODCOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
9.8.4.2 FL Transport Stream Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Table Of Contents
9.8.4.3 PID Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

9.8.4.3.1 Deleting SP PID Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
9.8.5 Return Link Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
9.8.5.1 Superframe (DVB-RCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
9.8.5.1.1 RL Superframes (Updating or Adding) . . . . . . . . . . . . . . . . . . . . . . . . . .169
9.8.5.1.2 Deleting a Superframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
9.8.5.1.3 Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
9.8.5.1.4 Segments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
9.8.5.2 Continuous Carrier Set (DVB-S2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
9.8.5.2.1 RL Continuous Carrier Set (Updating or Adding) . . . . . . . . . . . . . . . . . .189
9.8.5.2.2 Deleting a Continuous Carrier Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
9.8.6 Frequency Plan Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
9.8.6.1 Generic Frequency Plan Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
9.8.6.2 Forward Link Frequency Plan Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . .196
9.8.6.3 Return Link Frequency Plan Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
9.9 Satellites Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
9.10 Service Level Agreement View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
9.11 RLSS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
9.11.1 Adding or Updating the RLSS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .208
9.12 Miscellaneous VSAT Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
9.12.1 Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
9.12.1.1 IP Address Ranges (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
9.12.1.1.1 Adding or Updating IP Address Ranges . . . . . . . . . . . . . . . . . . . . . . . .211
9.12.1.1.2 Deleting an IP Address Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
9.12.1.2 Configure Network Ranges Virtual Channel Connection Ranges. . . . . . . .214
9.12.1.2.1 Adding or Updating Virtual Channel Connection Ranges . . . . . . . . . . .215
9.12.1.2.2 Deleting a Virtual Channel Connection Range . . . . . . . . . . . . . . . . . . .218
Chapter 10 NMS Monitoring & Control (M & C) . . . . . . . . . . . . . . . . . . . . . . . .219

10.1 Hub Equipment M & C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
10.2 RF Equipment M & C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
10.3 VSAT M & C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
10.3.1 VSAT M&C Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
10.3.1.1 VSAT M&C Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
10.3.1.2 VSAT M&C (Operations Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
10.3.1.3 VSAT M&C (Configuration Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
10.3.1.4 VSAT M&C (OW QoS Tab). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226
10.3.1.5 VSAT M&C (Statistics Tab). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
10.3.1.6 VSAT M&C (ACM Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230
10.3.1.7 VSAT M&C (WaveSwitch Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232
10.3.2 SIT Groups M&C Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
10.3.3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
10.3.3.1 Layer 2 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236

Table Of Contents
10.3.3.2 Layer 3 SCS Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

10.3.3.3 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
10.4 Network Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
10.5 System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
10.5.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
10.5.2 Connection Manager Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
10.5.3 Operations Connection Manager Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
10.5.4 WaveSwitch Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
10.5.5 Equipment Monitoring Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
10.5.6 Command/Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
10.5.7 User Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Chapter 11 NMS Account Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

11.1 Account Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
11.1.1 Account Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
11.1.1.1 Account Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
11.1.1.2 User Management Service Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
11.1.1.2.1 Adding or Updating Service Providers . . . . . . . . . . . . . . . . . . . . . . . . . 256
11.1.1.2.2 Deleting a Service Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
11.1.1.3 Account Management Customer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
11.1.1.3.1 Adding or Updating Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
11.1.1.3.2 Deleting a customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
11.1.1.4 Account Management User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
11.1.1.4.1 Adding or Updating User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
11.1.1.4.2 Deleting a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Chapter 12 RLSS Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

12.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
12.2 RLSS Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
12.3 RLSS User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
12.4 RLSS Management Interface (RMI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
12.4.1 RLSS Main Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
12.4.1.1 RMI Workspace’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
12.4.1.2 Tree Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
12.4.1.2.1 Tree Pane - General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
12.4.1.2.2 Tree Pane - Navigation Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
12.4.1.3 View Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
12.5 RLSS Status Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
12.5.1 RLSS Monitoring from RMI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
12.5.2 RLSS Alarms/Notifications and Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . 287
12.5.2.1 Active Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
12.5.2.2 Notification Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
12.5.2.3 RLSS Traffic Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
12.6 Updating RLSS License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Table Of Contents
12.7 SED and FTE Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289

12.7.1 Satellite Ephemeris Data (SED) Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
12.7.2 Frequency Translation Error (FTE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291
12.8 Terminal Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293
12.9 Other RMI Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296
12.9.1 Forward Link Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296
12.9.2 Return Link Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298
12.9.3 Frame Definitions Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299
12.10 RLSS Configuration Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300
12.11 Shutting Down the RLSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300
Chapter 13 FLS Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301

13.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301
13.2 FLS Front Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305
13.3 FLS Rear Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306
13.3.1 FLS-100 Rear Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306
13.3.2 FLS-100A Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307
13.3.3 FLS-150 Rear Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308
13.3.4 FLS-150A Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309
13.4 FLS IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310
13.5 FLS User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310
13.6 Additional FLS Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311
13.7 FLS Configuration Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311
13.7.1 FLS Modem Configuration Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311
13.7.2 FLS IPE Configuration Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311
13.7.3 FLS ACM Configuration Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312
13.8 Shutting Down the FLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312
Chapter 14 IPS Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313

14.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313
14.2 IPS Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313
14.3 IPS Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314
14.4 IPS IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315
14.5 IPS User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315
14.6 IPS Configuration Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316
14.7 Shutting Down the IPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316
Chapter 15 IDU (Legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317

15.1 IDU User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317
15.2 Adding IDU’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317
15.3 Accessing IDU’s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
15.3.1 Confirming your IDU’s Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
15.3.2 Connecting to the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
15.4 Using S4xxx, S5xxx or S6xxx Model IDU’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
15.4.1 Multicast Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
15.4.1.1 Forward Link Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318

Table Of Contents
15.4.1.2 Return Link Multicast. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

15.4.2 ACM Configuration -SIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
15.4.2.1 Setting the IDU for ACM Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
15.4.2.2 Setting the IDU’s ACM MODCODs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
15.4.3 IPsec Configuration in IDU’s (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
15.4.3.1 IPsec Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
15.4.3.2 IP Filters and Queues Configuration Example . . . . . . . . . . . . . . . . . . . . . 329
15.4.3.2.1 IP Filter #1 Example (for OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
15.4.3.2.2 Queue #1 Example (for OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
15.4.3.2.3 IP Filter #2 Example (for encrypted data) . . . . . . . . . . . . . . . . . . . . . . 332
15.4.3.2.4 Queue #2 Example (for encrypted data) . . . . . . . . . . . . . . . . . . . . . . . 333
15.4.3.2.5 IP Filter #3 Example (for VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
15.4.3.2.6 Queue #3 Example (for VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
15.4.3.3 IPsec Pre-Shared Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
15.4.3.4 MIB Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
15.4.3.5 MIB Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Chapter 16 IDU (Current) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

16.1 IDU User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
16.2 Adding IDU’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
16.3 Accessing IDU’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
16.3.1 Confirming your IDU’s Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
16.3.2 Connecting to the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
16.4 Using S7xxx Model IDU’s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
16.4.1 Multicast Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
16.4.1.1 Forward Link Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
16.4.1.2 Return Link Multicast. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
16.4.2 ACM Configuration -SIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
16.4.2.1 Setting the IDU for ACM Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
16.4.2.2 Setting the IDU’s ACM MODCODs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
16.4.3 IPsec Configuration in IDU’s (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
16.4.3.1 IPsec Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
16.4.3.2 IP Filters and Queues Configuration Example . . . . . . . . . . . . . . . . . . . . . 348
16.4.3.2.1 IP Filter #1 Example (for OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
16.4.3.2.2 Queue #1 Example (for OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
16.4.3.2.3 IP Filter #2 Example (for encrypted data) . . . . . . . . . . . . . . . . . . . . . . 351
16.4.3.2.4 Queue #2 Example (for encrypted data) . . . . . . . . . . . . . . . . . . . . . . . 352
16.4.3.2.5 IP Filter #3 Example (for VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
16.4.3.2.6 Queue #3 Example (for VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
16.4.3.3 IPsec Pre-Shared Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
16.4.3.4 MIB Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
16.4.3.5 MIB Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Table Of Contents
Chapter 17 QPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359

17.1 QPS Server Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359
17.2 QPS Server Rear Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361
17.3 QPS IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363
17.4 QPS User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364
17.5 Accessing the QPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364
17.6 QPS Server Configuration Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365
17.7 Shutting Down the QPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365
Chapter 18 Witness Sit (Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367

18.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367
18.2 Witness Sit IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367
18.3 Witness Sit User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367
Chapter 19 WaveSwitch (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369

19.1 WaveSwitch Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369
19.1.1 WaveSwitch Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369
19.1.2 WaveSwitch Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370
19.1.3 Gradual Bandwidth Adjustment – Threshold margins . . . . . . . . . . . . . . . . . . .372
19.1.4 WaveSwitch Benefit highlights: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
19.2 WaveSwitch Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
19.2.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
19.2.1.1 Assumptions:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
19.2.1.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373
19.2.2 SCPC Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374
19.2.3 NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377
19.2.3.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377
19.2.3.1.1 SCPC Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377
19.2.3.1.2 Example SCPC Receiver Configuration . . . . . . . . . . . . . . . . . . . . . . . .381
19.2.3.2 Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .382
19.2.3.2.1 Example of a Fixed Frequency Band. . . . . . . . . . . . . . . . . . . . . . . . . . .382
19.2.3.2.2 Example of a Variable Frequency Band. . . . . . . . . . . . . . . . . . . . . . . . .383
19.2.3.3 Superframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385
19.2.3.3.1 Fixed RCS Superframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385
19.2.3.3.2 Example of a Fixed RCS Superframe . . . . . . . . . . . . . . . . . . . . . . . . . .385
19.2.3.3.3 Variable RCS Superframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .387
19.2.3.3.4 Example of a Variable RCS Superframe . . . . . . . . . . . . . . . . . . . . . . . .387
19.2.3.4 Frequency Band Components Showing the entire Satellite span (RL
& FL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388
19.2.3.5 VSAT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390
19.2.3.5.1 Example of a VSAT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390
19.2.4 SIT’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .391
19.2.4.1 MIB Configuration of the WaveSwitch SIT . . . . . . . . . . . . . . . . . . . . . . . . .391
19.2.4.1.1 MIB Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .391

Table Of Contents
19.2.4.1.2 MIB Access Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

19.2.4.2 WaveSwitch Configuration Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
19.2.4.3 Application based trigger – Filter/Queue Configuration. . . . . . . . . . . . . . . 396
19.2.5 Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
19.2.5.1 Manual Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
19.2.5.2 Manual Switchback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
19.2.6 Scheduled WaveSwitch Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
19.2.6.1 Scheduled WaveSwitch Events (Adding) . . . . . . . . . . . . . . . . . . . . . . . . . 400
19.2.6.2 Scheduled WaveSwitch Events (Deleting) . . . . . . . . . . . . . . . . . . . . . . . . 401
19.3 WaveSwitch Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
19.3.1 WaveSwitch SIT Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
19.3.2 WaveSwitch Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
19.3.3 Checking Successful Changeover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Chapter 20 KVM (Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

20.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
20.2 KVM Power Up Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Appendix A Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Appendix B Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
B.1 Power & Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
B.2 Connector Pin Outs and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
B.2.1 RF Port Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
B.2.2 RJ-45 Ethernet Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
B.3 Hub Versions& Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Appendix C Useful Linux Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

C.1 ROOT Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
C.2 Terminate Running Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Appendix D RLSS Input Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

D.1 Satellite Ephemeris Data (SED) File Format (sample) . . . . . . . . . . . . . . . . . . . . . 425
Appendix E SIT IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

E.1 Router VLANS & IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Appendix F Available Hub Hardware Configurations . . . . . . . . . . . . . . . . . . . 429

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Table Of Contents
This page intentionally left blank

List Of Figures
Figure 2.1 Non Redundant Discovery HUB System Architecture . . . . . . . . . . . . . . . . . . . 37
Figure 2.2 Redundant Discovery HUB System Architecture (FLS-100*) . . . . . . . . . . . . . . 38
Figure 2.3 Redundant Discovery HUB System Architecture (FLS-150*) . . . . . . . . . . . . . . 39
Figure 2.4 FLS-100 Bock Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 2.5 FLS-100A Bock Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 2.6 FLS-150 Bock Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 2.7 FLS-150A Bock Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 2.8 Discovery Series 1RU Interface Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 2.9 Discovery Series 2RU Interface Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 2.10 Discovery Series 2RU RJ-45 Sub Panel Examples . . . . . . . . . . . . . . . . . . . . 46
Figure 2.11 Discovery Series 2RU N-type Sub Panel Examples . . . . . . . . . . . . . . . . . . . . 47
Figure 2.12 Discovery Series 2RU BNC Sub Panel Examples . . . . . . . . . . . . . . . . . . . . . 48
Figure 2.13 Discovery Series F-type Sub Panel Examples . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 2.14 Discovery Series Flight Case Sub Panel Examples . . . . . . . . . . . . . . . . . . . . 49
Figure 3.1 Clearance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 4.1 Typical Internal Grounding Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 4.2 Optional Keyboard, Mouse and Monitor Connections Example . . . . . . . . . . . . 58
Figure 5.1 IMS Server Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 5.2 IMS Server (Current) Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 6.1 Typical IMS-100 Power Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 6.2 Typical QPS Power Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 8.1 Default NMS Application Login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 8.2 NMS Application Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 8.3 NMS Information Bar Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 8.4 Typical NMS Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 8.5 Typical NMS Tree Pane Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 8.6 Typical NMS Home Page Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 8.7 Typical NMS Wizard Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 8.8 Typical NMS HUB Configuration HUB Equipment Overview Page Example . . 86
Figure 8.9 Typical NMS VSAT Configuration Overview Page Example. . . . . . . . . . . . . . . 87
Figure 8.10 Typical NMS Configuration Bandwidth Management Air Interface
Overview Page Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 8.11 Typical NMS Monitoring Hub Equipment M&C Overview Page Example . . . . 88
Figure 8.12 Typical NMS Monitoring RF Equipment M&C Overview Page Example . . . . 88
Figure 8.13 Typical NMS Monitoring VSAT M&C Overview Page Example . . . . . . . . . . . 89
Figure 8.14 Typical NMS Monitoring Network Performance Overview Page Example . . . 89
Figure 8.15 Typical NMS Monitoring System Events Overview Page Example. . . . . . . . . 90
Figure 8.16 Typical NMS Account Management Overview Page Example . . . . . . . . . . . . 90
Figure 9.1 Definitions VCC Pool Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 9.2 Definitions PID Ranges Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 9.3 Definitions IP Address Ranges Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 9.4 Definitions RL QoS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 9.5 Definitions FL QoS Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 9.6 Definitions FL QoS Rules Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 9.7 Definitions FL Routes Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 9.8 Definitions Sit SW Versions Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 9.9 SIT Group View Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

List Of Figures
Figure 9.10 Adding A SIT Group Part 1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Figure 9.11 Adding A SIT Group Part 2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 9.12 Adding A SIT Group Part 3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 9.13 Deleting A SIT Group Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 9.14 SIT Group View Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 9.15 Adding A SIT Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 9.16 Adding a SIT Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 9.19 Modifying a SIT Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 9.20 Modifying a SIT Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 9.21 Viewing Current Defined RL or FL QoS Example. . . . . . . . . . . . . . . . . . . . . 113
Figure 9.22 SIT Return Link QoS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 9.23 SIT Forward Link QoS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 9.24 SIT Group QoS Modify Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 9.25 SIT RL QoS Modify Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 9.26 SIT Return Link QoS Change Not Over Written Example . . . . . . . . . . . . . . 118
Figure 9.27 SIT Return Link QoS Change Over Written Example. . . . . . . . . . . . . . . . . . 120
Figure 9.28 Modifying an Forward Link QoS Example Part 1 . . . . . . . . . . . . . . . . . . . . . 121
Figure 9.29 Modifying an Forward Link QoS Example Part 2 . . . . . . . . . . . . . . . . . . . . . 122
Figure 9.30 Forward Link QoS OverWritten Example Part 4 . . . . . . . . . . . . . . . . . . . . . . 123
Figure 9.31 Forward Link QoS OverWritten Example Part 5 . . . . . . . . . . . . . . . . . . . . . . 123
Figure 9.32 SLA View Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 9.33 Updating a SP FL SLA Examples Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 9.34 Updating a SP FL SLA Examples Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 9.35 Adding a SP FL SLA Examples Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 9.36 Adding a SP FL SLA Examples Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 9.37 Updating a SG FL SLA Examples Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 9.41 Adding a SG FL SLA Examples Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 9.45 Air Interface View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 9.46 Frequency Bands And Components Page Example Part 1 . . . . . . . . . . . . . 139
Figure 9.47 Frequency Bands And Components Page Example Part 2 . . . . . . . . . . . . . 139
Figure 9.48 Frequency Band Updating Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . 141
Figure 9.49 Frequency Band Updating Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 9.50 Frequency Band Adding Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 9.51 Frequency Band Adding Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 9.52 Frequency Band Deleting Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 9.53 Frequency Band Components Page Example . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 9.54 Frequency Guard Updating Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 9.55 Frequency Guard Updating Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 9.56 Frequency Guard Adding Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 9.57 Frequency Guard Adding Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 9.58 Frequency Guard Deleting Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 9.59 Setting MODCODs Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 9.60 Setting MODCODs Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

List Of Figures
Figure 9.61 Updating MODCODs Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Figure 9.62 Updating MODCODs Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 9.63 Adding MODCODs Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 9.64 Adding MODCODs Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 9.65 Delete a MODCOD Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 9.66 Transport Stream Updating Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 9.67 Transport Stream Adding Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 9.68 Transport Stream Adding/Updating Example Part 2 . . . . . . . . . . . . . . . . . . . 157
Figure 9.69 Transport Stream Adding/Updating Example Part 3 . . . . . . . . . . . . . . . . . . . 158
Figure 9.70 PID Ranges Updating Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 9.71 PID Ranges Updating (RL) Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 9.72 PID Ranges Updating (FL) Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 9.73 PID Ranges Adding Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 9.74 PID Ranges Adding Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 9.75 Deleting PID Ranges Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 9.76 RL Super Frame Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 9.77 RL Super Frame Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Figure 9.78 RL Super Frame Updating Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 9.79 RL Super Frame Updating Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 9.80 Adding Super Frame Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 9.81 Adding Super Frame Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 9.82 Deleting Superframes Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 9.83 Area Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 9.84 Area Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 9.85 Area Updating Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Figure 9.86 Area Updating Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 9.87 Area Adding Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 9.88 Area Adding Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 9.89 Deleting Area Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 9.90 Segments Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 9.91 Segment Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 9.92 Segments Updating Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 9.93 Segments Updating Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 9.94 Segments Adding Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 9.95 Segments Adding Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 9.96 Deleting Segments Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Figure 9.97 RL Continuous Carrier Set Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 9.98 RL Continuous Carrier Set Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . 188
Figure 9.99 Updating Continuous Carrier Set Example Part 1 . . . . . . . . . . . . . . . . . . . . 190
Figure 9.100 Updating Continuous Carrier Set Example Part 2 . . . . . . . . . . . . . . . . . . . 191
Figure 9.101 Adding Continuous Carrier Set Example Part 1 . . . . . . . . . . . . . . . . . . . . . 192
Figure 9.102 Adding Continuous Carrier Set Example Part 2 . . . . . . . . . . . . . . . . . . . . . 193
Figure 9.103 Deleting Continuous Carrier Set Example . . . . . . . . . . . . . . . . . . . . . . . . . 194
Figure 9.104 Frequency Plan Activation Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 9.105 Frequency Plan Activation Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . 196
Figure 9.106 FL Frequency Plan Activation Example (Steps 1 to 2) . . . . . . . . . . . . . . . . 197
Figure 9.107 FL Frequency Plan Activation Example (Steps 3 to 9) . . . . . . . . . . . . . . . . 198
Figure 9.108 RL Frequency Plan Activation Example (Steps 2 to 3) . . . . . . . . . . . . . . . . 200
Figure 9.109 RL Frequency Plan Activation Example (Step 4) . . . . . . . . . . . . . . . . . . . . 201
Figure 9.110 Satellite General Overview Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 9.111 Satellite General Overview Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . 202

List Of Figures
Figure 9.112 Satellite Detailed Frequency Band Components Overview Example Part
1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 9.113 Satellite Detailed Frequency Band Components Overview Example Part
2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 9.114 Service Level Agreement View Example Part 1 . . . . . . . . . . . . . . . . . . . . . 205
Figure 9.115 Service Level Agreement View Example Part 2 . . . . . . . . . . . . . . . . . . . . . 206
Figure 9.116 RLSS Configuration Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Figure 9.117 RLSS Configuration Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Figure 9.118 IP Address Ranges Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Figure 9.119 IP Address Ranges Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Figure 9.120 IP Address Range Updating Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . 211
Figure 9.121 IP Address Range Updating Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . 211
Figure 9.122 IP Address Range Adding Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 9.123 IP Address Range Adding Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 9.124 Deleting IP Address Range Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 9.125 VCC Pools Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 9.126 VCC Pools Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 9.127 VCC Range Updating Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 9.128 VCC Range Updating Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Figure 9.129 VCC range Adding Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Figure 9.130 VCC Range Adding Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Figure 9.131 VCC Range Delete Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Figure 10.1 VSAT M&C Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 10.2 VSAT M&C (Configuration Tab) Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 10.3 VSAT M&C (OW QoS Tab) Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 10.4 VSAT M&C (Statistics Tab) Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Figure 10.5 VSAT M&C (ACM Tab) Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Figure 10.6 VSAT M&C (WaveSwitch Tab) Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Figure 10.7 SIT Groups M&C Tab Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 10.8 Connection Manager Events Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . 239
Figure 10.9 Connection Manager Events Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . 240
Figure 10.10 Connection Manager Alarms Example Part 1 . . . . . . . . . . . . . . . . . . . . . . 241
Figure 10.11 Connection Manager Alarms Example Part 2. . . . . . . . . . . . . . . . . . . . . . . 242
Figure 10.12 WaveSwitch Events Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Figure 10.13 WaveSwitch Events Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Figure 10.14 Equipment Monitoring Events Example Part 1 . . . . . . . . . . . . . . . . . . . . . . 245
Figure 10.15 Equipment Monitoring Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 10.16 Command/Results Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Figure 10.17 Command Results Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Figure 10.18 User Activity Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Figure 10.19 User Activity Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Figure 11.1 Account Management Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Figure 11.2 Account Management Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 11.3 Service Providers Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Figure 11.4 Service Providers Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Figure 11.5 Updating Service Provider Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . 256
Figure 11.6 Updating Service Provider Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . 257
Figure 11.7 Adding a Service Provider Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . 258
Figure 11.8 Adding a Service Provider Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . 259
Figure 11.9 Deleting a Service Provider Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Figure 11.10 Customer Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

List Of Figures
Figure 11.11 Customer Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Figure 11.12 Updating Customers Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Figure 11.13 Updating Customer Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Figure 11.14 Adding Customer Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 11.15 Adding Customer Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 11.16 Delete a Customer Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Figure 11.17 User Account Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Figure 11.18 User Accounts Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Figure 11.19 Updating User Account Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 11.20 Updating User Accounts Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Figure 11.21 Adding User Account Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Figure 11.22 Adding User Account Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Figure 11.23 Deleting User Account Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Figure 12.1 RLSS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Figure 12.2 RLSS-100 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Figure 12.3 RLSS-100 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Figure 12.4 RLSS-200 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Figure 12.5 RLSS-200 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Figure 12.6 RLSS Access via WEB Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Figure 12.7 RLSS Login Security Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Figure 12.8 RLSS Initial Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Figure 12.9 RLSS Main Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Figure 12.10 RMI Tree Pane Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Figure 12.11 Multiple View Pane Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Figure 12.12 Table View Pane Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Figure 12.13 Global Object Table View Pane Example . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Figure 12.14 Physical Resource Space Information Examples . . . . . . . . . . . . . . . . . . . . 286
Figure 12.15 RLSS Active Notifications Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Figure 12.16 RLSS Alarm Log Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Figure 12.17 Traffic Monitoring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Figure 12.18 Configuring Traffic Statistics Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Figure 12.19 Updating RLSS Licence File Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Figure 12.20 SED Using File Mode Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Figure 12.21 SED File Format Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Figure 12.22 FTE Update using Operator Mode Example. . . . . . . . . . . . . . . . . . . . . . . . 292
Figure 12.23 FTE File Format Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Figure 12.24 Terminals Workspace Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Figure 12.25 Enabling the Monitoring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Figure 12.26 Terminal Real Time Monitoring Example . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Figure 12.27 Forward Link Workspace View Example (CCM configuration) . . . . . . . . . . 296
Figure 12.28 Forward Link Workspace View Example (ACM configuration) . . . . . . . . . . 297
Figure 12.29 Return Link Workspace View Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Figure 12.30 Frame Definitions Workspace View Example . . . . . . . . . . . . . . . . . . . . . . . 299
Figure 13.1 FLS-100 Bock Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Figure 13.2 FLS-100A Bock Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Figure 13.3 FLS-150 Bock Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Figure 13.4 FLS-150A Bock Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Figure 13.5 FLS Front Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Figure 13.6 FLS-100 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Figure 13.7 FLS-100A Rear Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Figure 13.8 FLS-150 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

List Of Figures
Figure 13.9 FLS-150A Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Figure 13.10 Typical FLS Modulator Security Window . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Figure 14.1 IPS-100 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Figure 14.2 IPS-100 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Figure 15.1 Forward Link Multicast IDU Settings Example . . . . . . . . . . . . . . . . . . . . . . . 319
Figure 15.2 Return Link Multicast IDU Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Figure 15.3 IDU Forward Link Default Coding Rate Setting Example . . . . . . . . . . . . . . . 321
Figure 15.4 Create an ACM MODCOD Threshold Entry Example . . . . . . . . . . . . . . . . . 323
Figure 15.5 Setting the ACM MODCOD Threshold Entry # 1 Values Example . . . . . . . . 324
Figure 15.6 ACM Configuration Entry #2 Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figure 15.7 IPsec Configuration Peer Address Example . . . . . . . . . . . . . . . . . . . . . . . . 327
Figure 15.8 IPsec Configuration Network Address Example. . . . . . . . . . . . . . . . . . . . . . 328
Figure 15.9 IP Filters and Queues Configuration Example . . . . . . . . . . . . . . . . . . . . . . . 329
Figure 15.10 IP Filter #1 Example (for OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Figure 15.11 Queue #1 Example (for OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Figure 15.12 IP Filter #2 Example (for encrypted data) . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Figure 15.13 Queue #2 Example (for encrypted data) . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Figure 15.14 IP Filter #3 Example (for VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Figure 15.15 Queue #3 Example (for VoIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Figure 15.16 IMS FTP Server Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Figure 15.17 Downloading IPsec Key.dat Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Figure 15.18 MIB Traps Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Figure 15.19 MIB Policy Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Figure 16.1 Forward Link Multicast IDU Settings Example . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 16.2 Return Link Multicast IDU Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Figure 16.3 IDU Forward Link Default Coding Rate Setting Example . . . . . . . . . . . . . . . 343
Figure 16.4 Create an ACM MODCOD Threshold Entry Example . . . . . . . . . . . . . . . . . 344
Figure 16.5 Setting the ACM MODCOD Threshold Entry # 1 Values Example . . . . . . . . 344
Figure 16.6 ACM Configuration Entry #2 Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Figure 16.7 IPsec Configuration Peer Address Example . . . . . . . . . . . . . . . . . . . . . . . . 347
Figure 16.8 IPsec Configuration Network Address Example. . . . . . . . . . . . . . . . . . . . . . 347
Figure 16.9 IP Filters and Queues Configuration Example . . . . . . . . . . . . . . . . . . . . . . . 348
Figure 16.10 IP Filter #1 Example (for OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Figure 16.11 Queue #1 Example (for OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Figure 16.12 IP Filter #2 Example (for encrypted data) . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Figure 16.13 Queue #2 Example (for encrypted data) . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Figure 16.14 IP Filter #3 Example (for VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Figure 16.15 Queue #3 Example (for VoIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Figure 16.16 IMS FTP Server Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Figure 16.17 Downloading IPsec Key.dat Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Figure 16.18 MIB Traps Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Figure 16.19 MIB Policy Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Figure 17.1 QPS Server Front Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Figure 17.2 QPS Server Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Figure 19.1 WaveSwitch Modular Design Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Figure 19.2 VSAT M&C Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Figure 19.3 SCPC Receiver Configuration Example Part 1 . . . . . . . . . . . . . . . . . . . . . . 374
Figure 19.4 SCPC Receiver Configuration Example Part 2 (MIB Access Policy) . . . . . . 375
Figure 19.5 SCPC Receiver Configuration Example Part 2 (MIB Trap) . . . . . . . . . . . . . 376
Figure 19.6 SCPC Receiver Page Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Figure 19.7 SCPC Receiver Page Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

List Of Figures
Figure 19.8 SCPC Receiver Updating Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Figure 19.9 SCPC Receiver Updating Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Figure 19.10 SCPC Receiver Adding Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Figure 19.11 SCPC Receiver Adding Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Figure 19.12 SCPC Receiver Deleting Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Figure 19.13 Fixed Frequency Band Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Figure 19.14 Variable Frequency Band Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Figure 19.15 Fixed RCS Superframes Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Figure 19.16 Variable RCS Superframes Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Figure 19.17 Frequency Band Components Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Figure 19.18 WaveSwitch MIB Trap Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Figure 19.19 WaveSwitch MIB Access Policy Examples. . . . . . . . . . . . . . . . . . . . . . . . . 394
Figure 19.20 WaveSwitch Triggers Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Figure 19.21 Application Based Trigger Filter/Queue Example . . . . . . . . . . . . . . . . . . . . 397
Figure 19.22 Manual Switch Over Access Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . 398
Figure 19.23 Manual Switch Over Access Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . 399
Figure 19.24 Manual Switch Over Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Figure 19.25 Schedule Events Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Figure 19.26 Add Schedule Events Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Figure 19.27 Delete Schedule Events Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Figure 19.28 Delete Schedule Events Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Figure 19.29 WaveSwitch Monitoring Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Figure 19.30 WaveSwitch Monitoring Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Figure 19.31 WaveSwitch Events Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 19.32 WaveSwitch Events Example Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Figure 19.33 WaveSwitch State Example Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Figure 19.34 WaveSwitch State Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Figure 20.1 KVM Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Figure B.1 RJ-45 (10/100/1000T) Ethernet Connector Rear View. . . . . . . . . . . . . . . . . . 417
Figure B.2 Discovery Typical Rack Layouts Examples (No redundancy) . . . . . . . . . . . . 420
Figure B.3 Discovery Typical Rack Layouts Examples (With redundancy) . . . . . . . . . . . 421
Figure B.4 Discovery Typical Rack Layouts Examples (With redundancy) . . . . . . . . . . . 422
Figure F.1 Discovery 100 Series Next Generation VSAT HUB (8RU) . . . . . . . . . . . . . . . 429
Figure F.2 Discovery 100 Series Next Generation VSAT HUB (10RU) . . . . . . . . . . . . . . 430

List Of Figures

List Of Tables
Table 2.1 System Details Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 2.2 Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Table 3.1 System Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 4.1 Installation Tool Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 4.2 AC Power Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 5.1 IMS Server Front Panel Controls and Indicators . . . . . . . . . . . . . . . . . . . . . . . 62
Table 5.2 IMS Server Rear Panel Controls and Indicators . . . . . . . . . . . . . . . . . . . . . . . . 64
Table 6.1 Hub Power Up Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 6.2 Hub Power Down Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 7.1 IMS User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 7.2 Typical Non Redundant Discovery Hub (PEP/ACM/QoS) Factory Default
IP Addresses Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Table 7.3 Typical Non Redundant Discovery Hub (PEP/ACM/QoS/IPsec) Factory
Default IP Addresses Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 7.4 Typical Redundant Discovery Hub (PEP/ACM/QoS/IPsec) Factory Default
IP Address Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 7.5 user Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 7.6 IMS Server IP Address Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 8.1 NMS IP Address(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 8.2 NMS User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Table 8.3 Navigation Bar Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 9.1 System Setup Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Table 9.2 SIT Groups View Page Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 9.3 SIT Group Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Table 9.4 SIT Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 9.5 SIT Level RL QoS Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Table 9.6 Service Provider Forward Link SLA Page Fields . . . . . . . . . . . . . . . . . . . . . . 127
Table 9.7 Service Group Forward Link SLA Page Fields . . . . . . . . . . . . . . . . . . . . . . . . 136
Table 9.8 Frequency Bands And Components Page Fields . . . . . . . . . . . . . . . . . . . . . . 140
Table 9.9 Frequency Band Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Table 9.10 Frequency Band Components Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . 147
Table 9.11 Frequency Guard Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Table 9.12 MODCOD Page fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Table 9.13 Transport Stream Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Table 9.14 SP PID Ranges Page Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Table 9.15 Adding a PID Range page fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Table 9.16 RL Superframes Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 9.17 Area Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Table 9.18 Segment Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Table 9.19 RL Continuous Carrier Set Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Table 9.20 RLSS Profile Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Table 9.21 IP Address Range Page Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Table 9.22 VCC Range Page fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Table 10.1 VSAT M&C Summary Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Table 10.2 VSAT M&C (Operations) Page Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Table 10.3 VSAT M&C (Configuration Tab) Page Fields . . . . . . . . . . . . . . . . . . . . . . . . 224
Table 10.4 VSAT M&C (OW QoS Tab) Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

List Of Tables
Table 10.5 VSAT M&C (Statistics Tab) Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

Table 10.6 VSAT M&C (ACM Tab) Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230
Table 10.7 VSAT M&C (WaveSwitch Tab) Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . .232
Table 10.8 VSAT M&C (SIT Groups M&C Tab) Page Fields . . . . . . . . . . . . . . . . . . . . . .234
Table 11.1 Service Provider Information fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
Table 11.2 Default Service Provider User Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
Table 11.3 User Account Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271
Table 12.1 RLSS Front Panel LED’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Table 12.2 RLSS User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Table 12.3 Alarm Status Color Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
Table 13.1 FLS Model Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301
Table 13.2 FLSS Front Panel LED’s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305
Table 13.3 FLS-100 Rear Panel Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306
Table 13.4 FLS-100A Rear Panel Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307
Table 13.5 FLS-150 Rear Panel Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308
Table 13.6 FLS-150A Rear Panel Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309
Table 13.7 FLS IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310
Table 13.8 FLS User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310
Table 14.1 IPS Front Panel LED’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313
Table 14.2 IPS Rear Panel Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314
Table 14.3 IPS IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315
Table 14.4 IPS User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315
Table 15.1 IDU User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317
Table 15.2 MIB Trap Destination OID’s Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337
Table 16.1 IDU User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339
Table 16.2 MIB Trap Destination OID’s Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356
Table 17.1 QPS Server Front panel Controls and Indicators . . . . . . . . . . . . . . . . . . . . . .359
Table 17.2 QPS Server Rear panel Controls and Indicators . . . . . . . . . . . . . . . . . . . . . .362
Table 17.3 Remote Access QPS IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363
Table 17.4 Qos User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364
Table 18.1 Remote Access Witness Sit IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367
Table 19.1 SCPC Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379
Table 20.1 KVM Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .412
Table B.1 Power & Environmental Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .415
Table B.2 RX RF Port Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .416
Table B.3 TX RF Port Electrical Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .416
Table B.4 RJ-45 (10/100/1000T) Ethernet Connector Pin Allocation . . . . . . . . . . . . . . . .417
Table B.5 Ethernet Ports Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .417
Table B.6 Discovery Hub Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .418
Table E.1 Router VLANs & IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427
Table E.2 Sample Addressing scheme for Maximum 4064 SIT’s 172.16-31.Y.Z . . . . . . .427

Chapter 1 Safety Information and Standards
Informational Warnings or Cautions

This manual contains a several types of safety warnings which are used when poten-
tial injury or damage can occur.
WARNING
USERS SHOULD TAKE NOTE OF THE CONTENTS OF THESE
ADVISORIES ACCOMPANYING THIS ICON WHERE IMMINENT
DANGERS AND/OR DAMAGE TO EQUIPMENT MAY OCCUR. THE
USER IS ASKED TO STOP ANY RELATED OPERATION.
AVERTISSEMENT
LES UTILISATEURS DOIVENT PRENDRE NOTE DU CONTENU DE CES
AVIS ACCOMPAGNANT CETTE ICÔNE LORSQUE DANGERS
IMMINENTS ET / OU DES DÉGÂTS MATÉRIELS PEUVENT SE
PRODUIRE. L'UTILISATEUR EST INVITÉ À CESSER TOUTE
OPÉRATION CONNEXE.
Caution
Users should take note of the contents of these advisories accompanying
this icon concerning potential hazards of injury and/or damage to
equipment. Only factory authorized service personnel should perform this
task.
Attention
Les utilisateurs doivent prendre note du contenu de ces avis accompagnant
cette icône concernant les dangers potentiels de blessures et / ou
endommager l'équipement. Seul le personnel de service autorisés par
l'usine doivent effectuer cette tâche.
Caution
Radio frequency fields at this site may exceed the FCC rules for safe human
exposure. Users should take note of the contents of these advisories
accompanying this icon concerning potential hazards of injury and/or
damage to equipment. Only factory authorized service personnel should
perform this task.

Safety Information and Standards
Attention
Champs de fréquence radio sur ce site peuvent dépasser les règles de la
FCC pour l'exposition humaine sécuritaire. Les utilisateurs doivent prendre
note du contenu de ces avis accompagnant cette icône concernant les
dangers potentiels de blessures et / ou endommager l'équipement. Seul le
personnel de service autorisés par l'usine doivent effectuer cette tâche.
Information
Users should take note of the contents of these advisories accompanying
this icon as useful information and general tips.
Information
Les utilisateurs doivent prendre note du contenu de ces avis accompagnant
cette icône que des informations utiles et des conseils généraux.
Handling Procedures
Caution
Observe precautions for handling electrostatic sensitive devices.
Attention
Respectez les précautions pour la manipulation de dispositifs sensibles aux
décharges électrostatiques.

Safety Precautions
• Access to the Discovery Series system shall be restricted to qualified service

personnel.
• The use of the warning symbol means the equipment is subject to restrictions of
use in certain countries, please check national regulations.
• The unit cannot be serviced (installed, un-installed or repaired) by operators, only
by qualified service personnel.
• Observe the safety warnings and take all precautions listed in this manual.
• When maintaining the Discovery Series system, follow the replacement
procedures in this manual and use the correct tools, preferably the recommended
tools, for tightening of nuts, etc.
• Do not use any components (screws, nuts, etc.) other than those delivered
together with the Discovery Series equipment or recommended by SpaceBridge
Inc.
• Although the radiated output power is low (less than 1.0 Watt), it is wise to take
some personal safety precautions when working near the RF output:
Grounding
All equipment shall be grounded before the power cable is connected.
WARNING
ALL INDOOR AND OUTDOOR GROUNDING SYSTEMS ON THE
INSTALLATION SITE MUST MEET THE REQUIREMENTS OF THE
APPLICABLE LOCAL AND NATIONAL STANDARDS.

FCC Warning
This equipment generates, uses and can radiate radio frequency energy, and, if
not installed in accordance with the instructions contained herein, may cause interfer-
ence to radio communications.
Operation of this equipment in a residential area may cause interference. In this

case, the user is required to take whatever measures are necessary to correct the
interference at the user’s expense.
If radio frequency interference is encountered after the installation of this equip-

ment, information on recommended corrective measures can be obtained from the
SpaceBridge.
WARNING (UL/CSA)
ONLY QUALIFIED TECHNICIANS SHOULD HAVE ACCESS TO THIS
UNIT.
1. TO ENSURE ADEQUATE COOLING OF THE EQUIPMENT, A 5CM
UNOBSTRUCTED SPACE MUST BE PROVIDED AROUND ALL
SIDES OF THE UNIT AND 30CM ON FRONT AND BACK OF THE
UNIT.
2. THE AC POWER SOCKET SHALL BE INSTALLED NEAR THE BASE
BAND RACK AND SHALL BE EASILY ACCESSIBLE.
3. REMOVE POWER PLUG FROM THE POWER SOCKET BEFORE
PERFORMING ANY SERVICE WORK ON THE UNIT.
AVERTISSEMENT
SEULEMENT DES SPÉCIALISTES QUALIFIÉS DEVRAIENT AVOIR
ACCÈS À CET APPAREIL.
1. A FIN DE NE PAS NUIRE AU PROCESSUS DE REFROIDISSEMENT,
IL EST NÉCESSAIRE DE LAISSER UN ESPACE D’ENVIRON 5 CM
DE CHAQUE CÔTÉ DE L’APPAREIL.
2. PLACEZ L’APPAREIL PRÈS D’UNE PRISE DE COURANT
FACILEMENT ACCESSIBLE.
3. DÉBRANCHEZ L’APPAREIL AVANT D’EFFECTUER DES TRAVAUX
DE SERVICE SUR L'UNITÉ.

Warranty and Service
SpaceBridge warrants to the purchaser that the products and any repaired prod-
ucts (repairs) will be free from defects in material and workmanship for a period of one
year from the date of shipment to the purchaser.
SpaceBridge’ obligation under this warranty is limited to replacing or repairing, at

SpaceBridge’s option, products or repairs found by SpaceBridge to be defective within
the warranty period. All such replacements and repairs shall be performed at facilities
designated by SpaceBridge and shall be performed only after the customer has
received a Return Material Authorization (RMA) number from SpaceBridge and has
returned the product to SpaceBridge, shipping and insurance prepaid by the pur-
chaser.
The returned product must be accompanied by the customer's name, address and
telephone number, the model and serial number of the product, a statement of the
purchase date and a detailed description of the problem. Products and repairs
returned by purchaser shall be repaired by SpaceBridge using new or refurbished
parts and shall be returned to the purchaser by SpaceBridge, shipping prepaid by
SpaceBridge.
This warranty shall immediately become null and void if, in SpaceBridge’ sole
judgment, the product has been subject to unauthorized modification, misuse, abuse,
neglect, accident, improper installation or application, alteration or neglect in use,
storage, transportation or handling, or if the serial number and/or other product mark-
ings have been removed, defaced or altered.
SpaceBridge may, at its discretion, perform out-of-warranty repairs at SpaceBri-

dge facilities in exchange of customary charges, or offer a written agreement extend-
ing the terms of this warranty at a price stated in such agreement. All repairs
performed out of warranty or pursuant to an extended warranty agreement shall be
subject to all of the applicable limitations and procedures of this agreement.
The above warranties are in lieu of all other warranties, expressed, implied, or
statutory or arising by custom of trade usage, including any warranty of merchantabil-
ity of fitness for any unique, special or express purpose, and of all other obligations of
liabilities whether in contract, tort or otherwise including, without limitation, liability for
damages (whether general or special, direct or indirect, consequential, incidental,
exemplary) or any claim for the loss of profits or business or for damage to goodwill.

Extended Warranty Options
Please contact SpaceBridge customer service or your reseller for information on

optional extended warranties.
Service
Support provided by SpaceBridge customer service include complete factory
repair for both in warranty and out of warranty equipment.
Contact your local SpaceBridge distributor or reseller. Refer to Customer Support

and Service in “Proprietary” on page 7.
A customer service engineer will answer warranty related questions, discuss your
specific equipment problems, and when necessary, give you shipping instructions for
returning the equipment to SpaceBridge for repair.
To return any equipment for service or repair, you must obtain an RMA number
from SpaceBridge customer service.
The following information is required:
• Customer name, address, telephone number.

• Model number.
• Serial number.
• Detailed description of problem.
All customer-returned equipment must be shipped to SpaceBridge freight prepaid,

in the original carton or equivalent. SpaceBridge is not responsible for damage in tran-
sit.

Chapter 2 Description
2.1 System Features
• Maximum Flexibility: Economically Scalable.

• DVB-RCS MF-TDMA inbound (Return Link)
• DVB-S2 CCM or optional VCM/ACM to optimize the outbound (Forward Link or
FL) bandwidth.
• Optimized for IP and multi-media content.
• Open standard design (DVB-RCS).
• Acceleration using Performance Enhancement Proxy (PEP)
• Quality of Service (QoS)
• VoIP support
• Unique and powerful multi-carrier demodulation technology.
• World-class scheduling efficiency, maximizing bandwidth utilization.
• Always-on.
• User-friendly Network Management System.
• Mesh Overlay (peer-to-peer) capability (option).
• WaveSwitch dual waveform operation for the Return Link (option)

Description
2.2 System OverView
The RLS is a modular hub sub-system which can be integrated with new or
installed IP/DVB broadcast platforms and IP switch/routing equipment to provide two-
way satellite broadband access services. It is designed to receive inbound (Return
Link or RL) traffic, handle inbound (Return Link or RL) and outbound (Forward Link or
FL) signalling, schedule and control networks of satellite interactive terminals (SIT)
,available from multiple suppliers.
The FLS is the outbound (Forward Link or FL) equivalent of the RLS. The FLS
takes IP traffic and using Multi-Protocol Encapsulation (MPE) transforms the data into
an MPEG2 format for transmission on the outbound (Forward Link or FL) using its
embedded DVB-S/S2 modulator.
Information
Users should take note that due to the shear number of overall system
design options, we have chosen to show the Discovery hub system rack
examples as pencil sketches. Your actual design may not be shown in this
manual, so please refer to your actual system supplied documentation
packages. For some examples, please refer to Appendix B.3, “Hub
Versions& Physical Specifications” on page 418.
Information
Users should take note that the information in Figure 2.1 thru Figure 2.3
are simplistic examples. Please refer to your customer specific system
configuration

Description
RLSS
IPS J12 Rear I/O
1 PPS GPS 1PPS
10MHz 1PPS
J13
1PPS
Optional J11 ASI IN J7
10MHz 10MHz
ASI OUT J9
ASC ASI OUT J8
RL Traffic J6
J6 MIF J7
Router Timing RF2
J8 L-BAND
J9 RF1
MGMT 1 Eth Eth MGMT 10MHz
J10 RX IN
CUSTOMER ISP 1 Eth Eth PEP/ PROC RT-TP
TRAFFIC
ETH2 IF1TP J11
SERV 1 Eth Eth QoS ETH1 IF2TP J12
ETH 1PPS J13
RS232 Eth MCD
Alm SW
10 MHz 1 PPS MOD Ethernet ASI IN

IN
OUT ACM FL Traffic
ASI IN
IMS Console ASI IN
Ethernet
Server ALARM (IPE)
L-BAND
TO LNB
M&C (MODEM) Refer to either: L-BAND
RX OUT
CONSOLE (IPE) Figure 2.4 "FLS-100 Bock Diagrams"
Figure 2.6 "FLS-150 Bock Diagrams" L-BAND
TX OUT
Figure 2.1 Non Redundant Discovery HUB System Architecture

Description
RLSS1
IPS1 J12 Rear I/O
1 PPS GPS 1PPS
10MHz 1PPS
J13
1PPS
10MHz 10MHz
ASI OUT J9
ASC ASI OUT J8
RL Traffic J6
J6 MIF J7
Router Timing RF2
J8
J9 RF1
J10
TRAFFIC
ETH2 IF1TP J11
ETH 1PPS J13
RS232 Eth MCD
Alm SW
RX
SPLITTER
IN
OUT ACM FL Traffic
ASI IN
IMS1 Console
FLS 1 ASI IN L-BAND
Ethernet
Server ALARM (IPE) RX-IN
L-BAND
TO LNB
M&C (MODEM) Refer to either: RX OUT
L-BAND

Figure 2.5 "FLS-100A Bock Diagrams" L-BAND
TX OUT
RLSS2
IPS2 J12 Rear I/O
1 PPS GPS 1PPS
10MHz 1PPS
J13
1PPS
10MHz 10MHz
ASI OUT J9
ASC ASI OUT J8
RL Traffic J6
J6 MIF J7
Router Timing RF2
J8
J9 RF1
J10
ISP 1 Eth Eth PEP/ PROC RT-TP
ETH2 IF1TP J11
CUSTOMER ETH 1PPS J13
TRAFFIC RS232 Eth MCD
Alm SW

IN
OUT
ACM FL Traffic
ASI IN
IMS2 Console ASI IN
IF
Ethernet FLS 2
Server ALARM (IPE)
Switch
L-BAND
TO LNB
M&C (MODEM) Refer to either: RX OUT
L-BAND
L-BAND
Figure 2.5 "FLS-100A Bock Diagrams" L-BAND TX OUT
TX OUT
Note: In redundant systems only, IPS unit can be replaced by independent GPS unit
and an independent router unit. (models may vary).
Figure 2.2 Redundant Discovery HUB System Architecture (FLS-100*)

Description
RLSS1
IPS1 J12 Rear I/O
1 PPS GPS 1PPS
10MHz 1PPS
J13
1PPS
10MHz 10MHz
ASI OUT J9
ASC ASI OUT J8
RL Traffic J6
J6 MIF J7
Router Timing RF2
J8
J9 RF1
J10
TRAFFIC
ETH2 IF1TP J11
ETH 1PPS J13
RS232 Eth MCD
Alm SW L-BAND
RX-IN
RX
RX SW
Splitter
10 MHz 1 PPS MOD Ethernet ASI IN COMB
IN
OUT ACM FL Traffic
ASI IN
IMS1 Console
FLS 1 ASI IN
Ethernet
Server ALARM (IPE)
RX OUT L-BAND
M&C (MODEM) Refer to either: TO LNB L-BAND

TX OUT
RLSS2
IPS2 J12 Rear I/O
1 PPS GPS 1PPS
10MHz 1PPS
J13
1PPS
10MHz 10MHz
ASI OUT J9
ASC ASI OUT J8
RL Traffic J6
J6 MIF J7
Router Timing RF2
J8
J9 RF1
J10
ISP 1 Eth Eth PEP/ PROC RT-TP
ETH2 IF1TP J11
CUSTOMER ETH 1PPS J13
TRAFFIC RS232 Eth MCD
Alm SW

IN
OUT
ACM FL Traffic
ASI IN
IMS2 Console ASI IN
IF
Ethernet FLS 2
Server ALARM (IPE)
Switch
L-BAND
RX OUT
M&C (MODEM) Refer to either: TO LNB
L-BAND L-BAND
CONSOLE (IPE) Figure 2.6 "FLS-150 Bock Diagrams" TX OUT
TX OUT
Note: In redundant systems only, IPS unit can be replaced by independent GPS unit
and an independent router unit. (models may vary).
Figure 2.3 Redundant Discovery HUB System Architecture (FLS-150*)

Description
Ethernet /4 Console 10MHz 1PPS
Tx Out
IPE MOD
L-Band
ALARM
Ethernet
ASI In 1 ASI
M&C
ASI In 2 RS232
ASI M&C
OUT
RS422
ASI no connect
In 3
no connect
ASI
In 4
FLS-100
IN 1 OUT 1
Console
KEY:
External Unit ACM
Ethernet
Figure 2.4 FLS-100 Bock Diagrams
Tx Out
IPE MOD
L-Band
ALARM
Ethernet
ASI In 1 ASI
M&C
ASI In 2 RS232
ASI M&C
OUT
RS422
ASI no connect
ASI
In 3
no connect
ASI
In 4
IN 1 OUT 1
Console
ACM
Ethernet
FLS-100A
Figure 2.5 FLS-100A Bock Diagrams

Description
Ethernet /4 Console 10MHz
Rx out
SPLITTER LIM (L-Band)
To LNB
(L-Band)
1PPS
Tx Out
IPE MOD
L-Band
ALARM
Ethernet
ASI In 1 ASI
M&C
ASI In 2 RS232
ASI M&C
OUT
RS422
no connect
ASI
In 3
ASI
In 4
FLS-150
IN 1 OUT 1
Console
ACM
Ethernet
KEY:
External Unit

Description
Rx out
To LNB
(L-Band)
1PPS
Tx Out
IPE MOD
L-Band
ALARM
Ethernet
ASI In 1 ASI
M&C
ASI In 2 RS232
ASI M&C
OUT
RS422
no connect
ASI ASI
In 3
no connect
ASI
In 4
IN 1 OUT 1
Console
ACM
Ethernet
FLS-150A

Description
2.3 System Details
Air Interface—outbound (Forward Link or FL)

Modulation DVB-S: CCM/VCM/ACM, IP over MPEG, QPSK (DVB-S), QPSK, 8PSK, 16APSK,
32APSK
Information Rates Up to 135 Mbps (1Msps to 45Msps)
Coding RS/Convolutional or LDPC on the outbound (Forward Link or FL)
Air Interface—inbound (Return Link or RL)
Modulation DVB-RCS, IP over ATM or MPEG, Multiple Access Method MF-TDMA. QPSK, 8PSK
Max Burst Info rates 128 kbps—8 Mbps
Coding Turbo Convolutional on the inbound (Return Link or RL)
MAC Layer—inbound (Return Link or RL)
Protocol CF-DAMA (Combined Free & Demand-Assigned Multiple Access)
QoS Multiple priority queues
Capacity Requesting Constant Rate Assignment (CRA), Volume Based Dynamic Capacity (VBDC), Rate
Based Dynamic Capacity (RBDC), Free Capacity Assignment (FCA)
Bandwidth on Demand 0-8 Mbps updated every 26.5 ms, framed in 1, or 2 ATM or 1 MPEG packet, with
(Return Link) in-band and out-of-band capacity requesting mechanisms
Network IP over Ethernet (10/100/1000BaseT)
NMS NMS100, web interface control, remote SIT management, VNO, 3rd Party
Equipment—Standard SNMP interfaces available
Tx & Rx Frequency Independent (can use any combination of C, Ku, Ka, X, etc.)
(TX 950-1450 MHz) Can interface with any frequency at L-band IF frequency
(Rx 950-1450 MHz)
Features
Fade Countermeasure ClearSky™
Network Architecture DVB-RCS, Star
Scalability Scalable forward & return link capacities + number of supported remotes
Multicast From hub or from behind remote
Options
Redundancy Hot swaps Redundant
Mesh Mesh overlay
Higher Layer Protocol IPSec/VPN, VLAN, VCM/ACM, TCP/HTTP Acceleration & Data Compression,
Options Virtual Telephony™
Table 2.1 System Details Summary

Description
2.4 Discovery Block Diagrams
Please refer to your supplied customer interface document.
2.5 Interface Overview
2.5.1 1 RU Interface Examples
8
1 2 3 4 5 6 7 9 10 11 12 13 14
8
Figure 2.8 Discovery Series 1RU Interface Examples
Item Designation Connector Function

1 Rx 1 N type 50 Ohm Female Return Link 1 Input
2 Rx 2 N type 50 Ohm Female Return Link 2 Input (Optional)
3 Rx 3 N type 50 Ohm Female Return Link 3 Input (Optional)
4 Monitor 9 Pin Dsub Female VGA monitor port (Optional)
5 MGMT RJ-45 receptacle Management
6 SERV RJ-45 receptacle Local Server
7 TUN RJ-45 receptacle Tunnel
8 ISP RJ-45 receptacle Remote Access
9 E1 RJ-45 receptacle VOIP
10 1PPS In BNC Female 50 Ohm 1PPS input
11 10MHz In BNC Female 50 Ohm 10MHz input
12 Tx 1 N type 50 Ohm Female Forward Link 1 Output
13 Tx 2 N type 50 Ohm Female Forward Link 2 Output (Optional)
14 Tx 3 N type 50 Ohm Female Forward Link 3 Output (Optional)
Table 2.2 Connector Summary

Description
2.5.2 2 RU Interface Examples
Note: Actual connectors and locations within can

vary, depending on your system configuration.
See your system Interconnect diagram for more
details.
Figure 2.9 Discovery Series 2RU Interface Example

Description
See note 2 1
Note 1. Actual connectors and locations within can vary, depending on your system
configuration. See your system Interconnect diagram for more details.
Note 2. In Redundant system, there may be more than one RJ-45 sub panel, hence each
sub-panel will be numbered.
Figure 2.10 Discovery Series 2RU RJ-45 Sub Panel Examples

Description
Note 2. In Redundant system, there may be more than one N-type sub panel, hence each
sub-panel will be numbered.
Note 3. If your system supports multiple satellites, there may be more than one pair of Tx
and Rx connectors (these pairs will be labeled as such. i.e: C-band, KU-band etc)
Figure 2.11 Discovery Series 2RU N-type Sub Panel Examples

Description
Figure 2.12 Discovery Series 2RU BNC Sub Panel Examples
Figure 2.13 Discovery Series F-type Sub Panel Examples

Description
2.5.3 Flight Case Interface Examples
RJ-45 TYPE
N TYPE 50 OHM
Figure 2.14 Discovery Series Flight Case Sub Panel Examples

Description
2.5.4 Gigabit Ethernet Ports Overview
MGMT This port (10.10.40.125/24) is used for local management. The NMS
server can be accessed from a local PC connected to the management
port.
SERV This port (192.168.2.1/24) is used to add local content, if required. Local
content can take the form of a file server and/or a Web server. This can
also be used to check the system health for end-to end traffic with the
remote SITs.
ISP This port is connected to the customer’s Internet Service Provider in order
to provide Internet access for the Remote SITs. It also allows for SpaceBri-
dge to remotely access the Hub for customer service purposes.
GRE Generic Routing Encapsulation interface
E1 VoIP interface to the telephone network
HPA Interfaces to the RF subsystem
XCEIVER Interfaces to the RF subsystem

Chapter 3 Site Requirements
3.1 General
3.1.1 Basic Safety Requirements
• Access to Discovery Hub products shall be restricted to service personnel.

• Observe the safety warnings and take all precautions listed in this manual.
• Follow the installation procedures in this manual and use the correct tools,
preferably the recommended tools, for tightening of nuts, etc.
• Do not use any components (screws, nuts, etc.) other than those delivered
together with the Discovery Hub equipment or recommended by SpaceBridge
Inc.
Grounding
All equipment shall be grounded before the power cable is connected.
WARNING
ALL INDOOR AND OUTDOOR GROUNDING SYSTEMS ON THE
INSTALLATION SITE MUST MEET THE REQUIREMENTS OF THE
APPLICABLE LOCAL AND NATIONAL STANDARDS.

Site Requirements
3.1.2 Space Requirements
Note 1. Dimensions will vary depending on Hub options. Refer to appendix

B for all applicable dimensions.
Note 2. Do not place any objects heavier than 50Kg (110lbs) on the top of
the Hub cabinet.
Note 3. For proper system operation it is recommended to allow

approximately 150mm (6 inch) air clearance on all sides.
Figure 3.1 Clearance Requirements

Site Requirements
3.1.3 Power Requirements
Power Supply
The Voltage supply should be provided through a two wire power distribution with
a nominal voltage of Auto sensing 100/250 VAC, 50/60 Hz(100 to 250VAC). A third
wire is required to provide earth grounding.
WARNING
THE SUPPLY VOLTAGE MUST NOT GO BELOW 100 VAC OR EXCEED
250 VAC. THIS IS THE MAXIMUM VOLTAGE TOLERANCE OF THE
DISCOVERY HUB!
Internal Protection Circuits
The Discovery Hub is equipped with a power distribution unit which contains a
built in 20 amp circuit breaker. In addition, each of the units in the Discovery Hub has
it’s own applicably rated fuse.
Power Consumption
The maximum power consumption is indicated in Table B.1 on page 415.
Grounding of Equipment
For grounding of the equipment, refer to Chapter 4.4.1.1, "Installing the Grounding
Cable" on page 56.

Site Requirements
3.2 System Requirements
Prior to any powering up of the Discovery Hub, Network operators must acquire the
following information so they can properly configure their Discovery Hub.
Requirement Reason Details

Location of Hub Must convert GPS location or Longitude/ The Hub position must be entered in the
Latitude into X/Y/Z values. RLSS configuration.
The Windows program “XYZWin” can be used
to convert from Lat-Long-El to XYZ and from
XYZ to Lat-Long-El.
Refer to the following web site to download
the program:
http://www.ngs.noaa.gov/PC_PROD/
XYZWIN/
Satellite Location Needs to be provided by the Hub to the This information is supplied by the satellite
SIT, as part of the FL signalling. provider.
It contains the predicted satellite position for
a given period of time. Each X, Y and Z
coordinate is associated with a specific time
stamp.
Refer to Appendix D, “RLSS Input Format” on
page 425.
Frequency Plan The frequency plan information is Forward Link:
required in order to configure the Hub for Uplink/downlink center frequencies, DVB-S or
satellite operation. DVB-S2, CCM or ACM, symbol rate,
modulation, coding rate, roll-off. If ACM, the
desired MODCODs to be used.
Return Link:
Uplink/downlink center frequencies, bit rate,
modulation, coding rate, payload type and
number of carriers
Satellite Transponder:
Satellite and transponder being used and
conversion factor between the Uplink and
downlink
RF Equipment:
Hub Uplink and Downlink Conversion factors
SIT Ip Determine the IP addressing scheme for As a guide, a proposed IDU addressing
Addressing the IDU’s. scheme is given in Appendix E, “SIT IP
Addressing” on page 427
External IP To allow the SITs to access the Internet The configuration of the router portion of the
addresses and to allow remote access to IPS-100 needs to be updated to assign the
SpaceBridge for customer support appropriate IP addresses for the default
(optional). gateway, Internet access and SpaceBridge
remote access (optional).
Table 3.1 System Installation Requirements

Chapter 4 Discovery Hub Installation
4.1 Unpacking
Prior to un-crating the units, carefully inspect shipping containers for any damage
that may have occurred during shipment.
4.2 General Warnings and Tools Required
Caution
Observe precautions for handling electrostatic sensitive devices.
WARNING
INSTALLATION, MAINTENANCE, OR REMOVAL OF ANY PART OF
THE INDOOR EQUIPMENT MUST BE PERFORMED ACCORDING TO
MANUFACTURER’S RECOMMENDATIONS BY QUALIFIED
PERSONNEL.
WARNING
WHEN REMOVING YOUR DISCOVERY HUB FROM ITS SHIPPING
CRATE, CARE SHOULD BE TAKEN AND AT LEAST 2 PERSONNEL
ARE REQUIRED TO LIFT THE UNIT AS IT IS QUITE HEAVY.
Applicable tools for disassembling the shipping crate Varies
Table 4.1 Installation Tool Requirements

Discovery Hub Installation
4.3 Visual Inspection
Carefully un-crate the unit and inspect it for any visible damage. If any damage is
found, please contact your SpaceBridge sales office. If required, refer to “Head Office”
on page 7.
4.4 Installing Your Discovery Hub
Depending on were you want to install your Discovery Hub, make sure to address
the following:
• Respect the clearance requirements mentioned in Chapter 3.1.2, "Space

Requirements" on page 52.
• The selected installation location is capable of supporting the Discovery Hub
rack weight.
• All RF and Ethernet cabling interconnections are in close proximity of the
Discovery Hub.
• To insure reliable system operation, Network Operators should provide a fail-
safe power source with adequate backup run time. See Appendix B.1, “Power
& Environmental Specifications” on page 415.
4.4.1 Connecting to Your Discovery Hub
WARNING
IT IS STRONGLY SUGGESTED TO FOLLOW BEST PRACTICES OF
COMPLETING ALL THE REQUIRED CABLING BEFORE POWERING UP
THE SYSTEM FOR THE FIRST TIME.
FOLLOW IN ORDER, THE STEPS OUTLINE IN Chapter 4.4.1,
"Connecting to Your Discovery Hub" AND INSTALL THE CABLES
THAT ARE APPLICABLE TO YOUR SPECIFIC SYSTEM’S
REQUIREMENTS.
4.4.1.1 Installing the Grounding Cable
To avoid equipment damage, be sure to ground the system before connecting any
other cables.
Cable Procedure
1. If the unit does not have external grounding lug proceed as follows, otherwise go to
Step 2.

• Remove rear panel and connect a ground cable to the grounding bar, that
meets the requirements of the applicable national standards. (Refer to
Figure 4.1).
• Replace the rear panel.
2. If you completed step 1, proceed to step 3 otherwise for those units have an
external groundling lug, connect a ground cable that meets the requirements of the
applicable national standards to the grounding lug,
3. Ground cabling completed.
Figure 4.1 Typical Internal Grounding Bar

4.4.1.2 Installing a Local Keyboard/Mouse and Monitor (Optional)
If the Network Operators wishes to install a local Keyboard, mouse and monitor
(assuming they do not have the KVM option on their Discovery Hub), proceed as fol-
lows:
1. Remove rear panel.

2. Connect your keyboard, mouse and monitor as shown in Figure 4.2 "Optional
Keyboard, Mouse and Monitor Connections Example".
3. Replace the rear panel.
Keyboard Mouse Video

(Purple) (Green) Monitor
Figure 4.2 Optional Keyboard, Mouse and Monitor Connections Example

4.4.1.3 Connecting the RF Cables
Connect the RF cables to the applicable RX(#) or TX(#) connectors on the rear
interface panel of the Discovery Hub. RF port specifications can be found in Appendix
B.2.1, “RF Port Connectors” on page 416.
Note 1. RX(#) implies Return Link (#) where # varies between 1 and 3.
Note 2. TX(#) implies Forward Link (#) where # varies between 1 and 3.
4.4.1.4 Ethernet Cabling
Connect the ethernet cables to the applicable MGMT, SERV or ISP connectors on
the rear interface panel of the Discovery Hub. Ethernet port specifications can be
found in Chapter 2.5.4, "Gigabit Ethernet Ports Overview" on page 50.
MGMT This port (10.10.40.125/24) is used for local management. The NMS
server can be accessed from a local PC connected to the management
port.
SERV This port (192.168.2.1/24) is used to add local content, if required. Local
content can take the form of a file server and/or a Web server. This can
also be used to check the system health for end-to end traffic with the
remote SITs.
ISP This port is connected to the customer’s Internet Service Provider in order
to provide Internet access for the Remote SITs. It also allows for SpaceBri-
dge to remotely access the Hub for customer service purposes.

4.4.1.5 Power Cable
The Discovery Hub is provided with one of the following power connectors.
Type Country Appearance
Nema-15P North America
Continental-euro-cee7_7 Continental europe
Table 4.2 AC Power Connectors

Chapter 5 IMS Server
5.1 General
The IMS server is the main controller for the Discovery Hub. It comes pre-config-
ured with a Linux operating system and all required tools for proper operation of your
Discovery Hub. It’s main purpose is to run the Network Management Software (NMS).
For details on the NMS application, refer to Chapter 8, “Introduction to the NMS Appli-
cation” on page 79.
5.2 IMS Server
5.2.1 IMS Server Front Panel
1 3 4 6 8
2 5 7 9 10 11 12
Figure 5.1 IMS Server Front Panel

IMS Server
Indicator Button or
Item Icon Description
connector
Power-on indicator, power The power-on indicator lights when the
button system power is on. The power button
1 controls the power supply output to the
system.
NMI Button Used to troubleshoot software and device

driver errors when running certain operating
systems. This button can be pressed using
the end of a paper clip.
2
Use this button only if directed to do so by
qualified support personnel or if the
information is provided in the operating
system documentation.
Video connector Allows you to connect a VGA display to the
system
3
Health indicator If the system is on, and in good health, the

indicator lights solid blue.
4
The indicator blinks amber if the system is on
or in standby, and any error exists (for
example, a failed fan or hard drive).
Hard-drive indicator The indicator blinks green to indicate hard-
drive activity.
5
Electrical indicator The indicator blinks amber if the system

experiences an electrical error (for example,
voltage out of range, or a failed power supply
or voltage regulator).
6
See the System Event Log or system
messages for the specific issue. Re-seat the
power supply by removing and reinstalling it.
If the problem persists, see Getting help.
Table 5.1 IMS Server Front Panel Controls and Indicators

IMS Server
Indicator Button or
connector
Temperature indicator The indicator blinks amber if the system
experiences a thermal error (for example, a
temperature out of range or fan failure).
Ensure that none of the following conditions

exist:
7
• A cooling fan is removed or has failed.
• System cover, cooling shroud, EMI filler
panel, memory-module blank, or back-
filler bracket is removed.
• Ambient temperature is too high.
• External airflow is obstructed.
System status indicator Lights blue during normal system operation.
Lights amber when the system needs
attention due to a problem.
8 • See the System Event Log or system

messages for the specific issue.
• Invalid memory configurations can cause
the system to halt at startup without any
video output.
System identification The identification buttons on the front and
button back panels can be used to locate a particular
system within a rack. When one of these
buttons is pressed, the system status
indicator on the front and the back of the
system flashes until one of the buttons is
pressed again.
Press to toggle the system ID on and off.

9
If the system stops responding during POST,
press and hold the system ID button for more
than five seconds to enter BIOS progress
mode.
To reset iDRAC (if not disabled in the iDRAC

Settings option) press and hold the button for
more than 15 seconds.
USB connectors (2) Allow you to connect USB devices to the
system. The ports are USB 2.0-compliant.
10
System service tag A slide-out label panel that allows you to

record system information such as Service
11
Tag, NIC, MAC address, and so on as per your
need.
Optical drive One slim SATA DVD-ROM drive or DVD+/-RW
12
drive.
Table 5.1 IMS Server Front Panel Controls and Indicators (Continued)

IMS Server
5.2.2 IMS Server (Rear Panel
1 2 3 5 6 7 8 9 10 11 12
Figure 5.2 IMS Server (Current) Rear Panel
Item Indicator Button or Icon Description

connector
iDRAC7 Enterprise port Dedicated management port for the iDRAC7
(optional) Enterprise card.
1
vFlash media card slot Allows you to connect the optional vFlash
(optional) media card.
2
Serial connector Allows you to connect a serial device to the

system.
3
PCIe expansion card slot Two integrated 10/100/1000 Mbps NIC

4
connectors.
5 system.
eSATA Allows you to connect additional storage

devices.
6

7
Table 5.2 IMS Server Rear Panel Controls and Indicators

IMS Server
Indicator Button or
connector
Ethernet connectors (2) Two integrated 10/100/1000 Mbps NIC
connectors.
8
System status indicator Indicates the status of the system. Lights blue
during normal system operation. Lights
9
amber when the system needs attention due
to a problem
indicator on the back flashes until one of the
buttons is pressed again.

10
mode.

11 Power supply 250 W AC power supply.
12 Retention clip Secures the power cable.
Table 5.2 IMS Server Rear Panel Controls and Indicators (Continued)

IMS Server

Chapter 6 Start-up and Shut-down
6.1 Switching ON your Discovery Hub
Caution
Both the IMS and the optional QPS are factory configured so that they
return to last known power state.
i.e. if they were operational and a power failure occurs (assuming no
redundant power source is available), they will automatically reboot upon
power return (i.e. NMS and optional QPS applications will resume on power
up).
Original factory shipping for both the IMS and the optional QPS are
powered down state.
1. Connect the hub’s power cable to the AC outlet.
2. Follow the steps as shown in the table below.
Step # 1a
Unit Power Up Procedure
(Where applicable)
Sub
Step Requirement
NSU (Optional) 1A
GPS (Optional) 1B
NSU (Optional) 1C
FLS unit 1D
RLSS 1E
IPS unit 1F • Auto start when hub is powered
ACM (Optional) 1G
IPsec Server (Optional) 1H
Witness SIT (Optional) 1J •
RLSS 1K •
IMS Server 1L • Press the Power button on the IMS Server. Refer to
Figure 6.1.
QPS Server 1N • Press the Power button on the QPS (Current
option). Refer to Figure 6.2
Table 6.1 Hub Power Up Sequence

a.Make sure to follow the power up sub step sequence as indicated.

Start-up and Shut-down
Power Button
Note: For more details see Figure 5.1
Figure 6.1 Typical IMS-100 Power Button
Power Button
Note: For more details see Figure 5.1
Figure 6.2 Typical QPS Power Button

6.2 Switching OFF your Discovery Hub
WARNING
NETWORK OPERATORS ARE ADVISED TO MAKE SURE THAT THEY
HAVE SAVED ANY CHANGES TO THE SYSTEM CONFIGURATION
BEFORE SHUTTING DOWN THE SYSTEM. FAILURE TO DO THIS WILL
RESULT IN THE LOSS OF ANY OF THE POSSIBLE CHANGES THAT
MAY HAVE BEEN DONE TO THE SYSTEM CONFIGURATION.
Step # 1a Step #2b

Unit Backup Procedure Shutdown Procedure Step #3
(Where applicable)
Sub Requirement Sub Requirement
Step Step
NSU (Optional) 1A • N/A 2A • N/A Only do this
GPS (Optional) 1B • N/A 2B • N/A after you have
competed the
NSU (Optional) 1C • N/A 2C • N/A applicable items
Witness SIT (Optional) 1D • N/A 2D • N/A in Steps 1 & 2
shown oh the
FLS unit 1E • Coming in a 2E • N/A
left.
future release
RLSS 1F • Coming in a 2F • N/A Turn off the
future release power to or
IPS unit 1G • Coming in a 2G • N/A disconnect the
future release HUB from it’s
power source.
ACM (Optional) 1H • Coming in a 2H • N/A
future release
QPS Server 1N • Coming in a 2N • Chapter 6.2.1,
future release on page 70
IMS Server 1P • Coming in a 2P • Chapter 6.2.2,
future release on page 70
Table 6.2 Hub Power Down Sequence

a.Make sure to follow the BACKUP sub step sequence as indicated.
b.Make sure to follow the SHUTDOWN sub step sequence as indicated.

6.2.1 Closing the QPS Server
Procedure:
1. Access the Discovery Hub. See Chapter 7.3, “Accessing the Discovery Hub” on
page 72.
2. Open a ssh session to the QPS server, using GNOME terminal.
• ssh [email protected] <cr>
• Enter the following command: shutdown - h now <CR>
6.2.2 Closing the IMS Server
Procedure:
1. Access the Discovery Hub. See Chapter 7.3, “Accessing the Discovery Hub” on
page 72.
2. From the IMS desktop, select the Shutdown from the applicable Linux “system”
menu.
3. From the resulting screen, select Shutdown or wait the default 60 seconds.
Note: Depending on the user account you used to access the IMS server,
you may be prompted to enter the root password.

Chapter 7 Initial Configuration
7.1 General
This chapter deals with the basic commissioning procedures that are required to
bring a Discovery Hub on line. Note that these procedures will vary depending on
each client’s unique system network and each site’s specific requirements.
The procedures described in this chapter are Network Manager System (alter-
nately know as NMS), unless otherwise indicated.
7.2 User Accounts
There are several User accounts on the Discovery Hub.
Account Name Default Password

Unit (See note 1) (See note 1) Used for
IMS Root asnsatnet Access to the IMS Server master

account. See Caution below.
rcs_gwy advwireless Access to the IMS Server general use
account.
Table 7.1 IMS User Accounts

Note: The user names and passwords are case sensitive and should be
entered as shown.
Caution
Use of the root account name on the IMS Server should be restricted to
qualified personnel only. Improper use in this account can cause system
instability and or failure.

Initial Configuration
7.3 Accessing the Discovery Hub
7.3.1 Access Methods
7.3.1.1 Direct Access Method
Direct access to the Discovery Hub is done using either:
• The KVM system (optional).

• A user supplied keyboard, video monitor and mouse.
7.3.1.2 Remote Access Method
Remote access to the Discovery Hub requires the following:
1. An ethernet connection defined as follows:

• via your network,
• via a local PC such as a laptop with a cross over ethernet cable or over
your ethernet network,
2. The Discovery Hub is factory default configured as follows:
Caution
The Discovery Hub product line is typically configured as per customer
requirements, therefore SpaceBridge’s reserves the right to change default
IP addresses and topology of the equipment within the Discovery Hub.
SpaceBridge provides the typical factory defaults shown below for reference
only. For actual addresses, users should refer to their Discovery Hub’s IP
Topology.
Default IP Address
Unit Function
(With mask 255.255.255.0)
IMS Server Management 10.10.40.125
NMS Management 10.10.40.125
RLSS System 10.10.40.80
Return Link Unit (RLU) RLC Processor 10.10.40.150
TRF Gigabit Interface 192.168.255.151
MCDv2 (#1 to #5) 10.10.40.11 to 15
Table 7.2 Typical Non Redundant Discovery Hub (PEP/ACM/QoS) Factory

Default IP Addresses Example

Default IP Address
Unit Function
(With mask 255.255.255.0)
FLS (Modulator section) Management 10.10.40.131
FLS (IPE section) Management Traffic 192.168.254.111
ACM (optional) Management 10.10.40.145
NTP Server 10.10.40.1
QPS Server Management 10.10.40.107
Terrestrial 192.168.253.107
Satellite 192.168.254.107
Switched Rack PDU Management 10.10.40.31
IPS Management (eth1) 10.10.40.1
NAT Dynamic (eth2) 192.168.9.xxx
Server (VLAN) (eth3) 192.168.2.1
PEP (eth0, port 4) 192.168.253.1
Traffic - Return/Forward Links 192.168.254.1
(eth0, ports 1, 2 & 3)
ISP Access Customer Specific
Remote Access Customer Specific
Table 7.2 Typical Non Redundant Discovery Hub (PEP/ACM/QoS) Factory

Default IP Addresses Example (Continued)
Default IP Address
Unit Function (With mask 255.255.255.0)
IMS Server Management 10.10.40.125
NMS Management 10.10.40.121
RLSS System 10.10.40.80
Return Link Unit (RLU) RLC Processor 10.10.40.150
TRF Gigabit Interface 192.168.255.151
MCDv2 (#1 to #5) 10.10.40.11 to 15
FLS (Modulator section) Management 10.10.40.131
FLS (IPE section) Management Traffic 192.168.254.111
ACM (optional) Management 10.10.40.145
NTP Server 10.10.40.1
QPS Server Management 10.10.40.107
Terrestrial 192.168.253.107
Satellite 192.168.254.107
Switched Rack PDU Management 10.10.40.31
Table 7.3 Typical Non Redundant Discovery Hub (PEP/ACM/QoS/IPsec)

Factory Default IP Addresses Example

Default IP Address
Unit Function
(With mask 255.255.255.0)
IPS VLANnms (503)--eth1 10.10.40.1
VLANisp(501)--eth2) 192.168.9.xxx
VLANserv (505)--eth3 192.168.2.1
VLANrlss (504)--eth2 192.168.255.1
VLANtrf (502)--eth2 192.168.253.1
VLANflss (500)--eth2 192.168.254.1
VLANclr (506)--eth2 192.168.250.1
Table 7.3 Typical Non Redundant Discovery Hub (PEP/ACM/QoS/IPsec)

Factory Default IP Addresses Example (Continued)
Default IP Address
Virtual Chain 1 Chain 2
IMS Server Management
10.10.40.20 10.10.40.125 10.10.40.225
NMS Management
RLSS System 10.10.40.80 -- --
Return Link Unit (RLU) RLC Processor or OAM
-- 10.10.40.150 10.10.40.250
Processor
TRF Processor -- 10.10.40.151 10.10.40.251
SIG Processor -- 10.10.40.152 10.10.40.252
TRF Gigabit Interface -- 192.168.255.151 192.168.255.251
MCDv2 (#1 to #5) -- 10.10.40.11 to 15 10.10.40.21 to 25
FLS (Modulator section) Management -- 10.10.40.131 10.10.40.231
FLS (IPE section) Management Traffic 192.168.254.11 192.168.254.111 192.168.254.211
ACM (optional) Management -- 10.10.40.145 10.10.40.245
NTP Server 10.10.40.1 10.10.40.2 10.10.40.3
QPS Server Management 10.10.40.17 10.10.40.107 10.10.40.207
Terrestrial 192.168.253.17 192.168.253.107 192.168.253.207
Satellite 192.168.254.17 192.168.254.107 192.168.254.207
Switched Rack PDU Management -- 10.10.40.31 10.10.40.41
Table 7.4 Typical Redundant Discovery Hub (PEP/ACM/QoS/IPsec) Factory

Default IP Address Example

Default IP Address
Virtual Chain 1 Chain 2
IPS VLANnms (503)--eth1 10.10.40.1 10.10.40.2 10.10.40.3
VLANisp(501)--eth2) 192.168.9.xxx 192.168.9.xxx 192.168.9.xxx
VLANserv (505)--eth3 192.168.2.1 192.168.2.2 192.168.2.3
VLANrlss (504)--eth2 192.168.255.1 192.168.255.2 192.168.255.3
VLANtrf (502)--eth2 192.168.253.1 192.168.253.2 192.168.253.3
VLANflss (500)--eth2 192.168.254.1 192.168.254.2 192.168.254.3
VLANclr (506)--eth2 192.168.250.1 192.168.250.2 192.168.250.3
IF Switch Management 10.10.40.51
RF Sub System Management 10.10.40.56 to 59
Ethernet Switch Management 10.10.40.153 10.10.40.253
Table 7.4 Typical Redundant Discovery Hub (PEP/ACM/QoS/IPsec) Factory

Default IP Address Example (Continued)
3. Network Operators have a choice of how to connect.to the IMS server desktop
• via direct connection of Keyboard-Video-Mouse.
• via Remote Access using a program such as TightVNC Viewer.
4. Regardless of how you access the Hub, Table 7.5 lists the possible user
interface(s) for each unit. For User ID and Passwords, refer to the applicable
chapter.
Unit Details
IMS Server • Linux GNOME Desktop Environment (GDE)
NMS • Web (https)
RLSS • Web
FLS (Modulator section) • Web and Telnet
FLS (IPE section) • Telnet
IPS • Telnet
QPS Server • Web access from IMS: admin / satnet
• SSH & Console: root /satnet
ACM (optional) • Telnet
Table 7.5 user Interfaces

7.3.2 Access Procedures
7.3.2.1 Direct Access Procedures
Proceed to Chapter 7.3.3, "Logging in to the IMS Server" on page 76.
7.3.2.2 Remote Access Procedures
Note 1. Due to the endless possibilities of which computer video monitor is

used by the client to access the system, the IMS Server VNC client
has been pre programmed with several screen resolutions. Refer to
the table below.
Note 2. Address(s) shown below are for example only and can vary. Please
refer to your project specific Discovery IP Topology.
IP Address Screen Resolution
10.10.40.125:1 1280x1024
10.10.40.125:2 1440x900
10.10.40.125:3 1600x1200
10.10.40.125:4 1024x768
10.10.40.125:5 1600x900
Table 7.6 IMS Server IP Address Options

1. Open a VNC session.
2. Select the IP address from the table above.
7.3.3 Logging in to the IMS Server
1. Select your preferred method of access (“Direct Access Method” on page 72 or

“Remote Access Method” on page 72).
2. Enter the desired user name and password. See Table 7.1, “IMS User Accounts”
on page 71.

7.3.3.1 Adjusting Discovery Hub’s Remote Access List
Network Operators will have to modify Discovery’s default access list in order to
connect the Discovery Hub to their network.
Access lists are configured on the Router using a Command Line Interface (CLI)
whose syntax is Cisco like. For security reasons, it is required to restrict Remote
Access to the Hub, especially to the Management LAN. The default configuration
contains only the required minimum Remote Access IP addresses, including the
SpaceBridge address used for customer support. For more information on how to
modify access lists, please refer to reference document “[A1]” on page 5.


Chapter 8 Introduction to the NMS Application
8.1 General
This chapter deals with the basic introduction to the NMS application which is
used to configure and manage your network.
8.2 Accessing the NMS Application
Access to the NMS application varies as per your connection method.
8.2.1 Direct Access to NMS Application
Direct access to the Discovery Hub is done via the optional KVM or user supplied
keyboard, video monitor and mouse. The NMS is accessed using a Web Browser
application (Firefox is pre configured to bring you to the NMS application). Proceed to
Chapter 8.3, "Starting the NMS Application".
8.2.2 Access to NMS Application
Access to the NMS application is done using your standard browser. Open a ses-
sion and enter the following:
HTTPS// (address of your NMS, See table below)
Note: Address(s) shown below are for example only and can vary. Please
Hub Type IP Address

Non Redundant 10.10.40.125
Redundant 10.10.40.20
(Virtual address of MASTER IMS)
10.10.40.125 (IMS # 1)
10.10.40.225 (IMS # 2)
Table 8.1 NMS IP Address(s)
8.3 Starting the NMS Application
On first time use, Network Operators will be prompted to login,.
1. Enter the NMS application user ID and password (refer to Figure 8.1).

Introduction to the NMS Application

Unit Used for
(See note 1) (See note 1)
NMS NO admin1 no_admin1 Access to the NMS application. See
note 2.
NO op1 no_op1 Users in this category can create,
modify and delete SIT resources as
well as send commands to SITs
belonging to any Service Provider.
NO viewer no_viewer1 Users have read-only access to the
entire database
Table 8.2 NMS User Accounts

Note 1. The user names and passwords are case sensitive and should be
entered as shown.
Note 2. The user-name given above is the Network Operator (NO), which
has complete control over the configuration of the system. Other
users with more restricted privileges can also be created.
Figure 8.1 Default NMS Application Login Page
The entry page is shown in Figure 8.2 "NMS Application Home Page". Navigation
given in this chapter uses the top navigation bar, unless otherwise indicated.

Caution
Once completely logged into the NMS system the use of the back or
forward buttons in the browser is not recommended (Hint: https).
Information bar Navigation bar
Figure 8.2 NMS Application Home Page
The primary function of the NMS application is to configure and manage your Sat-
ellite Interactive Terminals (SITs) by automatically configuring the various elements of
the HUB. It could also be used to execute frequency plan changes.
Where applicable, tool tips exist to provide Network Operators with more details
about the applicable item. Tool tips are displayed by the use of blue dashed lines
under an item.

8.3.1 Information Bar
Useful Tools
Current selected menu List of recent alarms Help Log out
Currently user’s name
Figure 8.3 NMS Information Bar Details
8.3.2 Navigation Bar
The navigation bar, displayed at the top of the page, provides access to the differ-
ent feature categories found in NMS: clicking on each item in the menu will make sub-
menu items appear. Clicking the sub-menu items will either navigate to the appropri-
ate application page, or open a second sub-menu with additional items (indicated by
an arrow).

8.4 Navigating the NMS User Interface
The NMS User Interface is divided into various sections as shown in Figure 8.4.
• Tree Pane.
• View Pane
View Pane TABs Navigation Bar
Quick
Drop down Link
Menus
Tree Pane
Action Buttons View

Pane
Figure 8.4 Typical NMS Application Example

8.4.1 Tree Pane
Refer to the figure below for a brief explanation on how the tree pane functions.
Click the circle to expand/collapse the tree branch
If the bar appears under the

item, selecting it will bring you
that items web page
Selecting the small down arrow

will make a sub menu appear,
that will vary, depending on
the item underlined, but an
example of a sub menu could
be:
- Add
- Delete
Figure 8.5 Typical NMS Tree Pane Example

8.4.2 Navigation Bar
The navigation bar, displayed at the top of the page, provides access to the differ-
ent feature categories found in NMS: clicking on each item in the menu will make sub-
menu items appear. Clicking the sub-menu items will either navigate to the appropri-
ate application page, or open a second sub-menu with additional items (indicated by
an arrow).
Navigation Bar Pick Sub Options Example, See

Home Figure 8.6
Wizards Network Operator VNO Wizard Figure 8.7
Configuration Hub Configuration Figure 8.8
VSAT Configuration Figure 8.9
Bandwidth Configuration Figure 8.10
Monitoring Hub Equipment M&C Figure 8.11
RF Equipment M&C Figure 8.12
VSAT M&C Figure 8.13
Network Performance Figure 8.14
System Events Figure 8.15
Account Management Figure 8.16
Table 8.3 Navigation Bar Options
Figure 8.6 Typical NMS Home Page Example

Coming in a future release
Figure 8.7 Typical NMS Wizard Example
Figure 8.8 Typical NMS HUB Configuration HUB

Equipment Overview Page Example

Figure 8.9 Typical NMS VSAT Configuration Overview Page Example
Figure 8.10 Typical NMS Configuration Bandwidth

Management Air Interface Overview Page Example

Figure 8.11 Typical NMS Monitoring Hub Equipment M&C

Overview Page Example
Information
RF Equipment is customer specific
Figure 8.12 Typical NMS Monitoring RF Equipment M&C


Figure 8.13 Typical NMS Monitoring VSAT M&C Overview Page Example
Figure 8.14 Typical NMS Monitoring Network Performance


Figure 8.15 Typical NMS Monitoring System Events

Figure 8.16 Typical NMS Account Management


Chapter 9 NMS Configuration
9.1 General
This chapter deals with the steps needed to configure and/ or manage your net-
work. Your Discovery Hub is delivered pre-configured and operational, with factory
default parameters unless different ones were specified by the customer prior to fac-
tory Integration and Test. Therefore, the bulk of any configuration changes and/or
additions are typically related to SIT Management and to a much lesser extent to Fre-
quency Planning and/or bandwidth changes whenever necessary.
The procedures described in this chapter are therefore based on a number of fac-
tory configured items (e.g., FL & RL SLAs, SIT Group, Service Provider, etc.).
In order to better understand some of the pre-configured items, a brief summary of

each will be presented below.
9.2 Pre-Configured Definitions
• VCC Pools
• PID Ranges
• IP Address Ranges
• RL QoS
• FL QoS
• FL QoS Rules
• FL Routes
• OAM
• Traffic
• Multicast
• SIT Software Versions

NMS Configuration
9.2.1 VCC Pools
Figure 9.1 Definitions VCC Pool Example
9.2.2 PID Ranges
Figure 9.2 Definitions PID Ranges Example

NMS Configuration
9.2.3 IP Address Ranges
Figure 9.3 Definitions IP Address Ranges Example
9.2.4 RL QoS
Figure 9.4 Definitions RL QoS Example

NMS Configuration
9.2.5 FL QoS
Figure 9.5 Definitions FL QoS Example
9.2.6 FL QoS Rules
Figure 9.6 Definitions FL QoS Rules Example

NMS Configuration
9.2.7 FL IP Routes
Figure 9.7 Definitions FL Routes Example
9.2.8 SIT Software Versions
Figure 9.8 Definitions Sit SW Versions Example

NMS Configuration
9.3 System Setup Summary
Function See
SIT Groups Chapter 9.4, on page 96
• Adding Chapter 9.4.1, on page 98
• Deleting Chapter 9.4.2, on page 102
Managing your SITs (IDU’s) Chapter 9.5, on page 103
• Adding Chapter 9.5.1, on page 104
• Modifying Chapter 9.5.2, on page 110
• Traffic Queues Chapter 9.5.4, on page 112
QoS related Chapter 9.6, on page 112
• Defining Default QoS Chapter 9.6.1, on page 112
• Changing Sit Group QoS Chapter 9.6.2, on page 114
• Changing Return Link QoS Chapter 9.6.3, on page 116
• Forward Ling QOS Change Chapter 9.6.4, on page 121
Forward and Return Link Multicast Chapter 9.7, on page 125
Frequency Planning Chapter 9.8, on page 138
• Adding or updating Frequency Bands Chapter 9.8.2, on page 139
• Adding or changing Frequency Components Chapter 9.8.3, on page 146
Forward Link Configurations Chapter 9.8.4, on page 151
Return Link Configurations Chapter 9.8.5, on page 166
• Superframes Chapter 9.8.5.1, on page 166
• Areas Chapter 9.8.5.1.3, on page 174
• Segments Chapter 9.8.5.1.4, on page 180
Frequency Plan Activation Chapter 9.8.6, on page 195
Table 9.1 System Setup Summary
WARNING
NETWORK OPERATORS MUST HAVE THEIR SYSTEM
REQUIREMENTS PRIOR TO ATTEMPTING TO DO ANY CHANGES TO
THEIR DISCOVERY HUB. REFER TO Chapter 3.2, “System
Requirements” on page 54.
9.4 Managing your SIT Group(s)

A SIT Group is the link between the Forward and Return Link Service Level Agree-
ment (SLA)
• Types of SIT Groups

• SIT two-way traffic
• SIT Group linked to Forward Link (FL) & Return Link (RL) Service
Level Agreements
• Multicast
• SIT Group linked to a Forward Link Service Level Agreement only
• For Traffic and SCS.

NMS Configuration
To view your SIT groups, access is as follows:
Procedure
Navigation Bar: Configuration → VSAT Configuration
Tree Pane
Figure 9.9 SIT Group View Example
Field Description
Sit Group The name that identifies the SIT Group.
The Forward Link QoS’s that are assigned as default for the
members of this SIT group; the first name in the cell refers to
the QoS profile assigned to the OAM route and the second to
FL QoS
the traffic route(s).
Note: If this cell is empty, then the SIT group was not
assigned any default Forward Link QoS.
The Return Link QoS that is assigned as default for the
members of this SIT group; The first name in the cell refers to
the login QoS profile, and the second name the maximum that
RL QoS
can be reached with CCP.
Note: If this cell is empty, then the SIT group was not
assigned a default Return Link QoS.
FL SLA The Forward Link Service Level Agreement for the SIT Group.
RL SLA The Return Link Service Level Agreement for the SIT Group.
Table 9.2 SIT Groups View Page Fields

NMS Configuration
9.4.1 Adding a SIT Group
Procedure
1. To add a new SIT Group, in the Tree pane, select triangle to the right of VSAT
Terminal Groups, and right click on the Add Sit Group button (refer to
Figure 9.10). The results will be similar to Figure 9.11, Figure 9.12 and Table 9.3.
Figure 9.10 Adding A SIT Group Part 1 Example

NMS Configuration

NMS Configuration
Field Description
Service Provider
Service Provider Select the appropriate Service Provider using the pull-down menu.
Basic Parameters
SIT Group Name The name that identifies the SIT Group.
The name of the Customer or entity that this SIT Group represents.
Customer
Note: This is an informative field only and is not required.
Multicast Check box selected to create a SIT Group for FL Multicast traffic only.
Check box must be selected if the Group contains SIT(s) that operate in
SCPC Group
SCPC instead of RCS.
SNMP Communities
The SIT MIB community name that allows for reading the MIB.
Read Community
Name
The factory default is Public
The SIT MIB community name that allows for writing to the MIB.
Write Community
Name
The factory default is Private
SCS Parameters
Uplink Power Determines whether or not Uplink Power Control is enabled.
Control Enabled
The target Energy per bit per noise power spectral density (Signal to Noise
Target Eb/No
ration per bit).
Table 9.3 SIT Group Page Fields

NMS Configuration
Field Description
Population Id The population ID.
Port Automatically assigned by the NMS. Can be overwritten, if required,
and should be left unchanged
Data Rate
Block Size
Retry Count
This field is automatically populated by the NMS. It is used by the SCS to
Group Number send multicast commands to SITs using the address
(Multicast)
239.255.255.<group_number>.
Default S/W Software version currently used. This can also be left empty.
Version
VoIP Capabilities
CCP Enabled The CCP protocol is enabled for the SITs of that SIT group.
Maximum The maximum number of CCP calls per SIT.
Number of CCP
Calls (per SIT)
QoS Profiles
SIT Maximum FL This is the maximum FL bit rate per SIT in that SIT group. By default, this
Rate (kbits/s) field is populated with the maximum bit rate of the SG FL SLA.
The Default Forward Link QoS profile assigned to OAM routes for this SIT
Group.
FL OAM QoS
Note: This is the default for SITs in this SIT group, but can be overwritten
in each FL Route profile.
The Default Forward Link QoS profile assigned to Traffic routes for this SIT
Group.
FL Traffic QoS
Note: This is the default for SITs in this SIT group, but can be overwritten
in each FL Route profile
Maximum FL The default Forward Link QoS profile assigned to packets matching a ToS
Rate per specified in a FL Traffic route.
Application TOS
The initial Return Link QoS profile assigned to SITs at logon.
Login RL QoS Note: This is the default for SITs in this Group, but can be overwritten in
each SIT’s Profile
Max CCP RL QoS The maximum RL QoS available to SITs in this group.
RL Traffic Queue RL Traffic Queue Filter (limited to IP source IP & mask)
Filter
SLAs
Note: Link the group to a Forward Link Service Level Agreement for Multicast and to a Forward Link
& Return Link Service Level Agreement for normal Unicast traffic.
The Forward Link Service Level Agreement that this SIT Group subscribes
FL SLA
to.
The Return Link Service Level Agreement that this SIT Group subscribes
RL SLA
to.
Table 9.3 SIT Group Page Fields (Continued)

To return to the SIT Groups page, click the < Close > button.

NMS Configuration
9.4.2 Deleting a SIT Group
Procedure
1. To remove SIT Groups, select the desired group from the tree pane, right click on
the right triangle and click the Delete Group button.
Figure 9.13 Deleting A SIT Group Example

NMS Configuration
9.5 Managing your SIT’s
This feature allows you to manually add a new SIT for NMS to manage, or modify
the attributes of a SIT already in the system.
Note: When adding a SIT, the NMS checks that the number of SIT profiles
that are linked to the SIT group is smaller than the maximum of
allowed SITs for the SP and the NMS license.
Caution
As part of a security feature, network operators are advised that in addition
to using their network IP topology, SITS must be processed as follows:
1. Add the known IDU IP address’s and it’s associated MAC address into
the NMS.
2. Have the IDU installers program the same IDU with all the required
parameters and if the NMS does not recognize it, the NMS will deny
access to this SIT, effectively locking it out of the network (i.e.: no TX
ability).
Managing your SIT’s can be done by selecting:
Procedure
Tree Pane
Figure 9.14 SIT Group View Example 2

NMS Configuration
9.5.1 Adding SIT’s
Procedure
1. To add a new SIT, select the desired SIT Group in the Tree pane (refer to
Figure 9.14)
2. Then select triangle to the right of the desired SIT Group and right click on the Add
SIT button (refer to Figure 9.15). The results will be similar to Figure 9.16,
Figure 9.17 and Table 9.4.
The addition of a SIT results in the following actions being performed by the NMS.
• IPE
• Traffic and OAM routes are added to the IPE
• Return Link Sub-System
• The SIT is added to the appropriate Terminal Group
• Forward Link Quality of Service (if the optional FL QoS is provided)
• Shaping entries are added for the Traffic and Operation and Maintenance
(OAM) routes
This added SIT can now access the Network and its status can be observed. For
details, refer to Chapter 10.3, “VSAT M & C” on page 219.
Right Click on
the Triangle.
Figure 9.15 Adding A SIT Example Part 1

NMS Configuration
Figure 9.16 Adding a SIT Example Part 2

NMS Configuration
Note: IDU redundancy Specifics only appear if you have checked the IDU
redundancy Enable Box check box.

NMS Configuration
Note: WaveSwitch Specifics only appear if you have checked the

Waveswitch Enable Box check box
You can modify the SIT Profile as required and click the Add or Update button,
depending on the requirements, to commit your changes. The SIT Profile fields are
described in Table 9.4 below.

NMS Configuration
..
Field Description
Service Provider
Service Provider Displays the current Service provider
Basic Configuration
SIT Group The SIT Group to which this SIT belongs.
Name The name that identifies the SIT.
MAC-Address The SIT's MAC Address, which is its unique identifier. The MAC address is
(00:00:00:00:00:00) a 6 byte value; its format is: xx:xx:xx:xx:xx:xx
Customer The customer serviced by the SIT. (information only)
Ethernet IP The IP Address and Mask for the SIT's Ethernet-side (LAN). The IP part is
Address/Mask specified in decimal while the network mask is in the CIDR format.
(decimal/CIDR Note: The Ethernet IP Address must be unique and within the range of
mask) SP IP Addresses Range with Traffic usage type.
The IP Address for the SIT's satellite side.
OAM IP Address Note: The OAM IP Address must be unique and within range of SP IP
(decimal)
Addresses Range with OAM usage type.
Flight Protocol PEP Determines whether or not the SIT uses Flight Protocol Performance
Enabled Enhancement Proxy acceleration.
Pull-down menu with the following choices:
• DVB-RCS-MF-TDMA (default)
RL Type
• SCPC-DVB-S2
• SCPC-Turbo Code
PEP Enabled Check enabled or disabled
PEP Compression Check enabled or disabled
Enabled
Mesh Receive If the SIT is capable of MESH operation, apply a check mark.
Enabled
Indicate if the SIT will automatically be pinged by the NMS. If not in
Automatic Ping Traffic Ready or OAM Ready, the success or failure of a ping is used to
Enabled
determine if the SIT is in a Sleep state.
SIT Model
Model The SIT’s model. Select from the list.
Commissioning
X Coordinate (m) The X, Y or Z coordinate used in commissioning the SIT (sent by SCS).
Y Coordinate (m) See note a
Z Coordinate (m)
Control
Note: These parameters are only effective for the next login of the SIT.
Deny Service When checked denies service and prevents the SIT from logging on.
• Prompts the RLSS to send a Tx Disable MAC command and bring the
SIT into “Transmit Disable” state.
TX Disabled
• When checked prevents the SIT from logging on by putting the SIT
in “HOLD state.”
Max Tx Rate For information only. Can be left blank.
(ksymb/s)
Table 9.4 SIT Page Fields

NMS Configuration
Field Description
SCS Parameters
The software version selected should be the current one used in the
S/W version system. It also determines which software version will be downloaded
using the Satellite Interactive Terminal Command System (SCS).
IDU Redundancy
IDU Redundancy Apply a check mark if the SIT provided is redundant. A new panel will
Enable then appear allowing the configuration of the redundancy parameters.
View
Note: These parameters are not supported in this version of NMS
Segment ID of the RLSS in which the SIT is logged or “Unknown”
Segment
otherwise.
The low level RL SLA that the SIT is currently using (e.g. Main, rain fade,
Low Level SLA Name
etc.)
State The current State of the SIT.
RLSS ID The ID of the RLSS that manages the SIT.
The software revision currently running on the SIT, as decoded from the
Current S/W Version
SIT capability field transferred to the CM.
WaveSwitch Enabled
WaveSwitch Apply a check mark if the SIT is WaveSwitch capable. A new panel will
Enabled then appear allowing the configuration of the WaveSwitch parameters.
Table 9.4 SIT Page Fields (Continued)

a.To convert your SIT GPS location into X,Y, Z coordinates, you can use the supplied Xyz-
Win tool. From the linux desktop, open the file browser and navigate to c:\Utils folder and
select the XyZWin.exe tool.

NMS Configuration
9.5.2 Modifying SIT’s
Procedure
1. To modify a SIT, select the desired SIT in the Tree pane (refer to Figure 9.14). The
results will be similar to Figure 9.19 and Figure 9.20.
2. Adjust the parameters as required and then click on the Update button.
Note: Addresses shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Figure 9.19 Modifying a SIT Example Part 1

NMS Configuration
Figure 9.20 Modifying a SIT Example Part 2

NMS Configuration
9.5.3 Adding SIT Collection
Information
This section is under development and will be available in a future release.
It’s intent is to allow to easily add a group of SITs with similar configuration
in the NMS database without having to configure each SIT individually
9.5.4 Traffic Queues
Traffic Queues are automatically added when Network Operators adds a SIT.
Refer to Chapter 9.5.1, “Adding SIT’s” on page 104.
The VCC and PID used for the Queues are selected from the range that was pre-
viously defined (refer to Chapter 9.12.1, “Ranges” on page 209.
9.6 Defining and Changing the QoS
9.6.1 Defining Default Quality of Service (QoS) Profiles
• A SIT takes its Quality of Service from the SIT Group it belongs to, unless the
Quality of Service is overwritten.
• The Return Link and Forward Link Quality of Service are selected using pull-
down menus in the SIT Group
• The currently defined QoS can be viewed as follows:
Procedure
1. Under Definitions in the Tree pane, select RL QoS or FL QoS (refer to

Figure 9.21).
2. The results would be similar to Figure 9.22 or Figure 9.23.

NMS Configuration
Figure 9.21 Viewing Current Defined RL or FL QoS Example
See Note
Note: RL QoS values are customer configurable. See Chapter 9.6.3, “SIT Return
Link QoS” on page 116
Figure 9.22 SIT Return Link QoS Example

NMS Configuration
See Note
Note: FL QoS values are customer configurable. See Chapter 9.6.4, “Forward
Link Quality of Service Change” on page 121
Figure 9.23 SIT Forward Link QoS Example
9.6.2 Sit Group QoS Change
Notice
Change to the Quality of Service profile used in a SIT Group will be applied
when the SIT is logging in. Therefore, where required, the SITs already
logged-in, needs to re-log in order to adopt the modified Quality of Service.
Alternately, the current RL QoS can be dynamically changed without re-
logging as described in Chapter 9.6.3, “SIT Return Link QoS” on page 116.
Procedure
From the tree pane, select the desired SIT group. (refer to Figure 9.9). The result
will be similar to Figure 9.24.
• Scroll to the QoS Profiles section and select the desired QoS you want to change.
• From it’s pull down menu, select the desired value.
• To implement the change, click on the Update button at the bottom of the page.

NMS Configuration
Figure 9.24 SIT Group QoS Modify Example

NMS Configuration
9.6.3 SIT Return Link QoS
The Return Link Quality of Service page of a given SIT can be accessed as follows:
Procedure:
1. From the tree pane, select the desired SIT group and then the desired SIT. (refer to
Figure 9.9).
2. In the View pane, scroll to the bottom and in the Operations button, click on the SIT
RL Qos button, The result will be similar to Figure 9.25.
Figure 9.25 SIT RL QoS Modify Example

NMS Configuration
Two types of changes can be made:
• Dynamic: Applied to the logged-in SIT.

• Overwritten: Permanent change applied at the next SIT log-in.
If no overwritten RL QoS profile has been defined for the given SIT, then the
Name field gives the name of the default RL QoS profile defined for the SIT Group
and the other fields give the properties of the default RL QoS profile define for the SIT
Group. Once the Add or Update button (depending on the requirement) is clicked,
the NMS highlights the differences between the default QoS profile (for the SIT
Group) and the overwritten profile.
9.6.3.1 SIT Return Link Quality of Service Change (Dynamic)
The Dynamic QoS change is applied to the logged-in IDU in the current section of
the page and is only effective when the Set Current button is clicked. When the SIT
re-logs, it takes back the original SIT Group Quality of Service. See the NOTICE on
page 114. Refer to Figure 9.26 and Table 9.5.

NMS Configuration
Figure 9.26 SIT Return Link QoS Change Not

Over Written Example
Upon clicking the Set Current button, the NMS:
• Configures the new parameters in the RLSS

• Configures the new parameters in the SIT
• Expects an SNMP trap from the RLSS acknowledging the changes. If the
NMS does not receive the confirmation from the RLSS, the values in the
Current section are automatically reverted to the previous values and a CM
event is generated.

NMS Configuration
Field Description
The current CRA traffic bit rate for this SIT Level RL QoS.
Constant Rate Assignments (CRA) is DVB-RCS specific terminology for

constant capacity on the Return Link that does not need to be
Constant Traffic (CRA) kbit/s
requested.
Because of its constant nature and the fact that it does not need to be
requested, it is especially suited for applications that require constant
throughput, low delays and low jitter.
The current maximum RBDC traffic bit rate for this SIT Level RL QoS.
Rate-Based Dynamic Assignments (RBDC) is DVB-RCS specific

terminology for variable capacity on the Return Link that needs to be
requested as a rate.
Max Persistent Traffic (RBDC) It is called persistent traffic because the RBDC capacity does not need
kbit/s to be requested at the scheduling time interval. Without updates, the
capacity is granted at the same rate for up to one second. Because of
its relatively constant nature, it is especially suited for applications that
require relatively constant throughput.
Because the overbooking can be controlled, it can accommodate

applications that require moderately low delays and low jitter.
The current maximum VBDC traffic bit rate for the SIT Level RL QoS.
Volume-Based Dynamic Assignments (VBDC) is DVB-RCS specific

terminology for variable capacity on the Return Link that needs to be
requested as a quantity (volume).
Max Best-effort Traffic
(VBDC) kbit/s It is called best-effort traffic because the VBDC traffic is granted as a
lower priority than persistent (RBDC) and constant (CRA) traffic.
Because of its burst like nature, it is especially suited for applications

that require intermittently high throughput but are robust to jitter and
delays.
When checked, allows this SIT Level RL QoS to receive left-over Return
Left-Over Capacity (FCA) Link throughput capacity (available to SITs without having to signal a
request for it).
Table 9.5 SIT Level RL QoS Page Fields
9.6.3.2 SIT Return Link Quality of Service Change (Overwritten)
The Overwritten QoS change is a permanent change applied at the next SIT log-
in. See the NOTICE on page 114. Refer to Figure 9.27 and Table 9.5.
Setting this change is done as follows:
• In the Nominal Login section of the page, enter your changes.

• Click on the Add Overwritten Qos button to implement.
Since the SIT is still logged-in, the current values displayed are unchanged.

NMS Configuration
• The Tool tip indicates the Default Quality of Service value.

• Click on the Delete Overwritten QoS button to remove the Overwritten
Quality of Service.
Note: The nominal Maximum Parameters are applicable for VoIP operation
Figure 9.27 SIT Return Link QoS Change Over Written Example

NMS Configuration
9.6.4 Forward Link Quality of Service Change
Two mandatory Forward Link routes exists for each SIT.
• Traffic
• OAM
Additional routes can also be created, as required.
Procedure:
1. From the tree pane, select the desired SIT group and then the desired SIT, then
select FL Routes. (refer to Figure 9.28).
Figure 9.28 Modifying an Forward Link QoS Example Part 1

NMS Configuration
Select the desired QoS Route
Figure 9.29 Modifying an Forward Link QoS Example Part 2
To determine the default Forward Link Quality of Service value, simply locate the
entry field where the value’s background color has changed to green and placing the
cursor on the tool tip indicates the default Forward Link Quality of Service value.

NMS Configuration
Note: Addresses) shown are for example only and can vary.
Figure 9.30 Forward Link QoS OverWritten Example Part 4
The Overwritten values are displayed in bold on the Forward Link Routes page.
Figure 9.31 Forward Link QoS OverWritten Example Part 5

NMS Configuration
To return to the default Quality of Service, click on the Delete Overwritten QoS
button (refer to Figure 9.30).
9.6.5 Viewing your Service Level Agreement
To view your Service Level Agreements access is as follows:
Procedure
Navigation Bar: Configuration → Bandwidth Management
1. From the tree pane, select SLA. The result will be similar to Figure 9.32.
Figure 9.32 SLA View Examples

NMS Configuration
9.7 Forward and Return Link Multicast
9.7.1 General Overview
• Multicast traffic is transmitted from the Gateway to the SITs

• SITs are able to join only the Multicast programs signaled in the Multicast Mapping
Table (MMT) send over the FL
• FL Multicast must be enabled in the IDU
• In an ACM system, Multicast is using the Most Protected MODCOD (MPM)
9.7.2 Service Provider Forward Link Service Level Agreement (SP FL SLA)
Updating or Adding
Procedure
Navigation Bar: Configuration → BandWidth Management
1. To update any SP FL SLA, in the Tree pane,

a. Under SLA expand the Forward Link
b. Select the desired SP FL SLA under the applicable Forward Link. (refer to
Figure 9.33). The results will be similar to Figure 9.34 and Table 9.6. Apply the
desired changes and click on the Update button.
2. To add a SP FL SLA, in the Tree pane,
a. Under SLA, expand the Forward Link
b. Select triangle to the right of the SP FL SLA in the Tree pane and left click on
the Add SP SLA button (refer to Figure 9.35). The results will be similar to
Figure 9.36 and Table 9.6. Apply the desired changes and click on the Add
button.
Figure 9.33 Updating a SP FL SLA Examples Part 1

NMS Configuration
Figure 9.34 Updating a SP FL SLA Examples Part 2

NMS Configuration
Field Description
General Parameters
Service Provider Select the Service Provider associated with this SP FL SLA
Name Enter a meaningful name for the for this SP FL SLA
MAC Properties
Transport Stream ID Using the pull-down menu, select the applicable Transport Stream ID
Using the pull-down menu, select the Service Category as CBR, VBR or
Service Category
UBR.
Minimum Guaranteed Applicable for CBR only
Capacity (kbit/s)
Maximum Capacity (kbit/s) Applicable for VBR and UBR
Table 9.6 Service Provider Forward Link SLA Page Fields
Figure 9.35 Adding a SP FL SLA Examples Part 1

NMS Configuration
Figure 9.36 Adding a SP FL SLA Examples Part 2

NMS Configuration
9.7.3 Service Group Forward Link Service Level Agreement (SG FL SLA)
Updating or Adding
Procedure
1. To update any SG FL SLA, in the Tree pane,

a. Under SLA expand the Forward Link
b. Select the desired SP SG FL SLA under the applicable Forward Link. (refer to
2. To add a SG FL SLA, in the Tree pane,
a. Under SLA, expand the Forward Link
b. Select triangle to the right of the desired SP FL SLA in the Tree pane and left
click on the Add SP SG SLA button (refer to Figure 9.41). The results will be
similar to Figure 9.42 and Table 9.7. Apply the desired changes and click on the
Add button.
Figure 9.37 Updating a SG FL SLA Examples Part 1

NMS Configuration

NMS Configuration

NMS Configuration

NMS Configuration
Figure 9.41 Adding a SG FL SLA Examples Part 1
Note: You must select the applicable Service Provider FL SLA

NMS Configuration

NMS Configuration

NMS Configuration
Field Description
General Information
Service Provider Select the SP FL SLA to which this SG FL SLA is linked to.
SP FL SLA
SIT Group FL SLA Name Enter a meaningful name for this SG FL SLA
MAC Properties
This is the Multicast PID that will be used by the NMS to send
Multicast PID
commands to the SITs.
Traffic Shaping
Service Category Using the pull-down menu select CBR, VBR or UBR
Minimum Guaranteed Applicable for CBR Service Category
Capacity (kbits/s)
Maximum Capacity (kbits/s) Applicable for VBR and UBR Service Category
Access control
Oversubscribing Factor for Example:
Minimum Guaranteed Cap The parameter is set to a value (example 10).
Then if the operator defines SIT’s and assigns more than 10 times of
Oversubscribing Factor for
Maximum Cap the available capacity to them, NMS will raise a popup alarm to warn
the operator not to Over Oversubscribe, regardless if the SIT’s are
offline or Online (NMS counts all the capacity assigned to SIT’s
Overbooking factor for regardless of their status). The minimum is the Guaranteed capacity
Maximum Cap. (CRA), the maximum is supposed to be shared Capacity (RBCD and
VBDC).
DVB-S2 PID Assignments 1
PID MODCOD Select the PID associated with this MODCOD using the pull-down
(disable if left blank) menu.
Preferred MODCOD/PID Apply a check mark only for the Most Protected MODCOD (MPM)
Table 9.7 Service Group Forward Link SLA Page Fields
3. Once your setting’s have been entered, click on the ADD button.

NMS Configuration
9.7.4 Multicast IDU Settings
Depending on your IDU model, please refer to
• Legacy IDU’s: Chapter 15.4.1, “Multicast Settings” on page 318.

• Current IDU’s: Chapter 16.4.1, “Multicast Settings” on page 341

NMS Configuration
9.8 Frequency Planning
9.8.1 Overview
Overall view of the Air Interface can obtained by selecting:
Navigation Bar: Configuration → BandWidth Management (refer to Figure 9.45)
Figure 9.45 Air Interface View

NMS Configuration
9.8.2 Frequency Bands
Start and end frequencies are entered with Satellite translation offset can be
defined for both Return Link and Forward Link beams or separately as shown below.
Procedure
The frequency bands are accessed as follows:
1. In the Tree pane, select Frequency Bands (refer to Figure 9.46). The result is
similar to Figure 9.47.
Figure 9.46 Frequency Bands And Components Page

Example Part 1
Figure 9.47 Frequency Bands And Components Page

Example Part 2

NMS Configuration
This page lists each Frequency Band Component with the parameters listed in
Table 9.8. The frequency band components can be displayed in either Uplink fre-
quency or Downlink frequency.
When Uplink is selected from the Frequency Display Choice drop down list, the
frequency bands are displayed without satellite translation applied. When Downlink is
selected, the frequency bands are displayed with the satellite translation frequency
subtracted.
Field Description
Frequency Band The name of the Frequency Band.
The Frequency Band’s lowest frequency edge.
Start Frequency (Hz) The carrier center frequency will be determined from the
specified start frequency.
The Frequency Band’s highest Frequency edge. The end
End Frequency (Hz)
frequency is only used for display purposes.
RL Beam The Return Link to which the Frequency Band is associated.
FL Beam The Forward Link to which the Frequency Band is associated.
Table 9.8 Frequency Bands And Components Page Fields
9.8.2.1 Frequency Band (Updating or Adding)
Procedure
1. To update any Frequency Band, in the Tree pane;

a. Under Satellites, select the applicable satellite.
b. Select the desired frequency band under the applicable satellite (refer to
c. Select Satellites→ Frequency Bands and then select the desired frequency
band in the view pane. The results will be similar to Figure 9.49 and Table 9.9.
Apply the desired changes and click on the Update button.
2. To add a new Frequency Band, in the Tree pane
a. Under Satellites, select the applicable satellite
a. Select triangle to the right of Frequency Band in the Tree pane and left click on
the Add Frequency Band button (refer to Figure 9.50). The results will be
similar to Figure 9.51 and Table 9.9. Apply the desired changes and click on the
Add button.

NMS Configuration
Figure 9.48 Frequency Band Updating Example Part 1

NMS Configuration
Figure 9.49 Frequency Band Updating Example Part 2

NMS Configuration
The lower part of the page presents a graphical outline of the Frequency Band as
it is currently configured, displaying the Transport Streams, Superframes and Fre-
quency Guards, when applicable.
Field Description
Configuration Parameters
Name The name that identifies the frequency band.
Uplink: The frequency bands are displayed without any satellite
translation applied.
Frequency Display
Choice
Downlink: The frequency bands are displayed with the satellite
translation frequency subtracted.
Uplink Start The lower frequency edge for the Frequency Band.
Frequency (Hz)
Uplink End The higher frequency edge for the Frequency Band.
Frequency (Hz)
Frequency Span Displays the width of the Frequency Band which is automatically
(Hz) calculated by the NMS.
Satellite translation The frequency translation offset of the satellite
Offset
WaveSwitch
Enable WaveSwitch Apply a check mark if this Frequency Band will be used for a SIT that
for this RL Band can switch from MF-TDMA RCS to DVB-S2 SCPC transmission.
When checked, the generated SCPC carrier in this frequency band will
SCPC are with Pilots
have pilot ON
SPSC Use Short When checked, the generated SCPC carrier in this frequency band will
Frames use Short Frames
Satellite and RL/FL Beams
Satellite The satellite to which this Frequency Band is associated.
RL Beam The Return Link beam to which the Frequency Band is associated.
FL Beam The Forward Link beam to which the Frequency Band is associated.
Table 9.9 Frequency Band Fields

NMS Configuration
Figure 9.50 Frequency Band Adding Example Part 1
Figure 9.51 Frequency Band Adding Example Part 2

NMS Configuration
9.8.2.2 Deleting a Frequency Band
Procedure
1. In the Tree pane, under Satellites, select the applicable satellite.

2. Select the desired Frequency Band under the applicable satellite.
3. Select the triangle to the right of the Frequency Band and right click on the Delete
Frequency Band button (refer to Figure 9.52).
Figure 9.52 Frequency Band Deleting Example

NMS Configuration
9.8.3 Viewing Frequency Band Components
Procedure
1. In the Tree pane, select Frequency Bands.

2. In the view pane, select the Frequency Band Components Tab. The result is
Figure 9.53 Frequency Band Components Page Example
The page lists each Frequency Band Component with the parameters listed in
Table 9.10. A filter based on Frequency Band can be applied to the Components dis-
played; This is done by selecting the desired Frequency Band from the Frequency
Band drop down list at the top of the page.
The frequency band components can be displayed in either Uplink frequency or

Downlink frequency. When Uplink is selected from the Frequency Display Choice
drop down list, the frequency bands are displayed without satellite translation applied.
When Downlink is selected, the frequency bands are displayed with the satellite trans-
lation frequency subtracted.

NMS Configuration
Selecting All displays all Components, regardless of Frequency Band or Frequency

Display Choice.
Field Description
Sequence Number The sequence number associated with the component.
Frequency Band The name given to the component.
Component
Type The type of component.
Occupied Bandwidth (Hz) The width of the frequency component.
Center Frequency (Hz) The center frequency for the component.
Frequency Band The Frequency Band to which this component is associated.
Indicates that a committed frequency band component change is
Config Commit Pending
pending.
Table 9.10 Frequency Band Components Page Fields

This page provides the tools and links necessary to build and configure a Fre-
quency Band. It is possible to manually create or associate components to the Fre-
quency Band:
• Transport streams: Existing Transport Streams can be associated to the

Frequency Band using the Assign Transport Stream button; alternatively, new
ones can be added using the Assign Transport Stream button, then Add
Transport Stream button. The result would bring you to Chapter 9.8.4.2, “FL
Transport Stream Configuration” on page 155.
• Superframes: Existing Superframes can be associated to the Frequency Band
using the Assign Superframe button; alternatively, new ones can be added using
the Assign Superframe button, then the Add Superframe button. The result
would bring you to Chapter 9.8.5.1, “Superframe (DVB-RCS)” on page 166.
• Frequency Guard: Existing Frequency Guard components can be edited using
the Update Frequency Guard button (see Chapter 9.8.3.1, “Frequency Guard
(Updating or Adding)” on page 148).
• Frequency Plan Activation: Provides access to the Frequency Plan Activation
page (see Chapter 9.8.6, “Frequency Plan Activation” on page 195).
Throughout the process of configuring components in a Frequency Band, it is pos-

sible to change their relative positions with respect to one another; this is done by
selecting a component and clicking either the Move Up or Move Down buttons to
shift it one position up or down.

NMS Configuration
9.8.3.1 Frequency Guard (Updating or Adding)
Procedure
1. To update any Frequency Guard, in the Tree pane,

a. Under Satellites, select the applicable satellite,
b. Select the desired frequency band under the applicable satellite, then the
desired Frequency Guard (refer to Figure 9.54). The results will be similar to
Figure 9.55 and Table 9.11. Apply the desired changes and click on the Update
button.
2. To add a Frequency Guard, in the Tree pane,
b. Select the desired frequency band under the applicable satellite.
c. Select triangle to the right of the desired Frequency band in the Tree pane and
left click on the Add Frequency Guard button (refer to Figure 9.56). The results
will be similar to Figure 9.57 and Table 9.11. Apply the desired changes and
click on the Add button.
Figure 9.54 Frequency Guard Updating Example Part 1

NMS Configuration
Figure 9.55 Frequency Guard Updating Example Part 2
Field Description
The name of the Frequency Band to which this Frequency
Frequency Band
Guard is associated.
Name The name of this Frequency Guard.
The sequence number for the Frequency Guard, representing
Sequence Number
its position in the Frequency Band.
Occupied Bandwidth The width of the Frequency Guard.
(Hz)
Center Frequency The center frequency for the Frequency Guard.
(Hz)
Table 9.11 Frequency Guard Page Fields
Figure 9.56 Frequency Guard Adding Example Part 1

NMS Configuration
Figure 9.57 Frequency Guard Adding Example Part 2
9.8.3.2 Deleting a Frequency Guard
Procedure
1. In the Tree pane, under Satellites, select the applicable satellite.

2. Select the desired frequency band under the applicable satellite.
3. Select the triangle to the right of the desired frequency guard and right click on the
Delete Frequency Guard button (refer to Figure 9.58).
Figure 9.58 Frequency Guard Deleting Example

NMS Configuration
9.8.4 Forward Link Configuration
For ACM operation, MODCOD’s must be created first, otherwise refer directly to
Chapter 9.8.4.2, "FL Transport Stream Configuration" on page 155.
9.8.4.1 FL MODCOD
Procedure
1. In the Tree pane, under Definitions, select MODCODs (refer to.Figure 9.59). The
results will be similar to Figure 9.60.
Figure 9.59 Setting MODCODs Example Part 1
Figure 9.60 Setting MODCODs Example Part 2

NMS Configuration
The page lists each MODCOD with the parameters listed in Table 9.12...
Field Description
Name Name of the MODCOD.
MODCOD The MODCOD (modulation coding) of this MODCOD.
This is the currently used CNI threshold setting and is for information
CNI Threshold
only.
CNI Threshold This is the currently used CNI threshold margin setting and is for
margin information only.
Short Frame For ACM, the default value is short frame.
With Pilots For ACM, the default value is with pilots.
Table 9.12 MODCOD Page fields
9.8.4.1.1 MODCOD (Updating or Adding)
Procedure
1. To update any MODCOD, in the Tree pane, under Definitions, select MODCODs.
a. Select from the list in the Tree pane (refer to Figure 9.61). The results will be
2. To add a new MODCOD, select triangle to the right of MODCODs in the Tree pane
and left click on the Add MODCOD button (refer to Figure 9.63). The results will be
similar to Figure 9.64. Apply the desired changes and click on the Add button.
Figure 9.61 Updating MODCODs Example Part 1

NMS Configuration
Figure 9.62 Updating MODCODs Example Part 2
• If updating, refer to Table 9.12, “MODCOD Page fields” on page 152.
Figure 9.63 Adding MODCODs Example Part 1

NMS Configuration
Figure 9.64 Adding MODCODs Example Part 2
9.8.4.1.2 Deleting a MODCOD
Procedure
1. In the Tree pane, under Definitions, select MODCODs

2. To delete any MODCOD, simply pick it from the list and select the triangle to the
right of MODCODs in the Tree pane and left click on the Delete MODCOD button
(refer to Figure 9.65).
Figure 9.65 Delete a MODCOD Example

NMS Configuration
9.8.4.2 FL Transport Stream Configuration
Procedure
1. To update any transport stream, in the tree pane, either

a. Select Satellites, then select the applicable satellite.
b. Select the desired frequency band under the applicable satellite (refer to
Figure 9.66). The results will be similar to Figure 9.68, Figure 9.69 and
Table 9.13. Apply the desired changes and click on the Update button.
2. To add a new transport stream, in the Tree pane
a. Select Satellites and then select the applicable satellite.
b. Select the applicable Forward Link, and then select triangle to the right of said
Forward Link, and right click on the Add Transport Stream button (refer to
Figure 9.67). The results will be similar to Figure 9.68, Figure 9.69 and
Table 9.13. Apply the desired changes and click on the Add button.
Figure 9.66 Transport Stream Updating Example Part 1

NMS Configuration
Figure 9.67 Transport Stream Adding Example Part 1
• If the FL is operating in CCM, the appropriate selection will be made when

configuring the FL Transport Stream. In this case, the DVB-S2 mode is
selected as CCM and then a single Modulation Scheme and Coding Rate are
selected for this TS. The other parameters described for ACM are still
applicable.

NMS Configuration
Figure 9.68 Transport Stream Adding/Updating Example Part 2

NMS Configuration
Figure 9.69 Transport Stream Adding/Updating Example Part 3
You can modify the Transports Streams as required and click the Update button to
commit your changes. The Transport Stream fields are described in the table below.).
Field Description
Equipment Assignment
Modulator Modulator associated with this transport stream.
IP DVB Encapsulator IPE associated with this transport stream.
MODCOD Adaptation Unit ACM Unit associated with this transport stream.
Transport Stream and Network ID
Transport Stream The numerical identifier for the Transport stream.
Interactive Network ID The interactive Network identifier.
Modulation Standard
DVB-S2 Determines whether or not this is a DVB-S2 Stream.
DVB-S2 Mode Indicates if the DVB-S2 transport stream is in CCM, VCM or ACM
Note: If CCM, then the following two mode.
check boxes are present:
• Short Frame
• With Pilots
Bit Rates
Rate Calculation Source Unit used to perform automatic calculation (bit rate or symbol rate).
IP Bit Rate (kbit/s) The bit rate at the input of the IP DVB Encapsulator.
IPE (Mux) Output Bit Rate The bit rate at the output of the IPE. This bit rate is the sum of the IP
(bit/s) bit rate and of the signaling bit rate from the RLSS.
Table 9.13 Transport Stream Page Fields

NMS Configuration
Field Description
Transport Stream Bit Rate This is the bit rate corresponding to the specified symbol rate. For
(kbit/s) ACM it is the Least Protected MODCOD (LPM).
RF Characteristics
Roll-Off Factor The roll-off factor.
The symbol rate. If the Rate Calculation Source was previously
Symbol Rate (symb/s) selected as Symbol Rate, a value can be entered here. Otherwise it is
calculated and greyed out.
The reference MODCOD is used in the system as the denominator
when calculating the efficiency factors of the MODCOD’s. The
efficiency factor of a MODCOD is calculated as the ratio of its bit rate
Reference MODCOD over the bit rate of the reference MODCOD.
ACM only:
The Reference MODCOD shall be the Least Protected MODCOD
(LPM).
MODCOD Provides access to MODCOD configuration for ACM only.
Note: If CCM, the following two items
are present:
• Modulation Scheme
• Coding rate
Frequency Band The name of the frequency band.
This is the transport stream frequency from the Gateway to the
Uplink Center Frequency (Hz)
Satellite.
Downlink Center Frequency This is the transport stream frequency from the Satellite to the
(Hz) Gateway.
Occupied Bandwidth (Hz) The width of the Transport Stream.
This is the Gateway frequency up conversion offset. This value is
Up conversion Offset (Hz) subtracted from the Uplink center frequency to calculate the
modulator center frequency.
Polarization The polarization of the transport stream (horizontal or vertical).
Auto Calibration Delay (PCR The automatically calculated calibration delay for this transport
ticks) stream.
Overwritten Calibration Delay If set, this value overwrites the automatic calibration delay.
(PCR ticks)
Services
RCS Map Service ID IDs of the specified services.
Forward Link Signaling Service ID of the Forward Link Signaling Service.
ID
IP/DVB Data Service ID ID of the IP/DVB Data Service.
Tables PIDs
Network Information Table PID of the Network Information Table (NIT).
(NIT) PID
RCS Map Table (RMT) PID The PCR inserter bit rate.
Composition Tables (SCT, FCT, PID of the Composition tables (SCT, FCT, TCT, SPT).
TCT, SPT) PID
Terminal Tables (CMT, TBTP) PID of the Terminal Tables (CMT, TBTP).
PID
Table 9.13 Transport Stream Page Fields (Continued)

NMS Configuration
Field Description
Terminal Information Message PID of the Terminal Information Message (TIM).
(TIM) PID
Program Clock Reference (PCR) PID of the Program Clock Reference (PCR).
PID
PCR Repetition Rate Rate of the PCR Repetition.
Multicast Map Table (MMT) PID PID of the Multicast Map Table (MMT).
Transmission Mode Support PID of the Transmission Mode Support Table (TMST) for ACM only.
Table (TMST) PID
Mesh Flow Receive Parameters PID of the Mesh Flow Receive Parameters Table (MFRxPT).
Table (MFRxPT) PID
Mesh Receive Definition Table PID of the Mesh Receive Definition Table (MRSDT).
(MRSDT) PID
Table 9.13 Transport Stream Page Fields (Continued)

NMS Configuration
9.8.4.3 PID Range
• For the Return Link (RL) a PID range must be specified since the payload can be
defined as MPEG.
• For the Forward Link (FL), in the case of ACM, a PID range must be specified for
each MODCOD being used for this Transport Stream (TS).
Procedure
1. In the Tree pane, under Definitions, select PID Ranges (refer to Figure 9.70)
2. To update any PID Range, simply pick it from the list. The results will be similar to
button.
3. To add a new PID Range, select triangle to the right of PID Ranges in the Tree
pane and left click on the Add PID Range button (refer to Figure 9.73). The results
will be similar to Figure 9.74 and Table 9.15.
Figure 9.70 PID Ranges Updating Example Part 1

NMS Configuration
Figure 9.71 PID Ranges Updating (RL) Example
Figure 9.72 PID Ranges Updating (FL) Example

NMS Configuration
Figure 9.73 PID Ranges Adding Example Part 1
Figure 9.74 PID Ranges Adding Example Part 2
The following parameters are displayed for each SP PID Range

NMS Configuration
:
Field Description
Service Provider
Service Provider
PID Range Properties
PID Start The first PID assignable for users of the PID Range.
PID End The last PID assignable for users of the PID Range.
PID Range Type The type of PID Range, select Forward Link.
Transport Stream The Transport Stream this PID Range will be used on.
Usage Type The intended usage type for this PID Range. Select indiscriminate.
Table 9.14 SP PID Ranges Page Fields

.
The fields in Table 9.14 and those listed here will appear
Field Description
MODCOD Name (for The Modulation and Coding name for this PID Range.
DVB-S2 ACM
systems)
Table 9.15 Adding a PID Range page fields
9.8.4.3.1 Deleting SP PID Ranges
Procedure
1. In the Tree pane, under Definitions, select PID Ranges

2. Select the desired range from the tree pane, right click on the right triangle and
click the Delete button (refer to Figure 9.75).

NMS Configuration
Figure 9.75 Deleting PID Ranges Example

NMS Configuration
9.8.5 Return Link Configuration
The Return Link configuration can be either:
• Superframe (DVB-RCS) which consists of

• Areas
• Segments
• Continuous Carrier Set (DVB-S2)
9.8.5.1 Superframe (DVB-RCS)
• Defines the burst payload (ATM1, ATM2 or MPEG)

• Number of carriers/rate using a pull-down menu
• Linked to an Operational Multi-Carrier Demodulator (MCD) and frequency band
• Down Conversion = sat. offset + Hub Low Noise Block Conversion
Superframes are accessed as follows:
Procedure
1. In the Tree pane, under Satellites, select the desired satellite, then select
Frequency bands under the satellite. (refer to Figure 9.76).
Figure 9.76 RL Super Frame Example Part 1

NMS Configuration
Figure 9.77 RL Super Frame Example Part 2
This page lists each Superframe with the following parameters:
Field Description
General Parameters
Name The name that identifies the Superframe.
ID The specific identification number.
Table 9.16 RL Superframes Page Fields

NMS Configuration
Field Description
The burst type for the Carrier Set.
Possible values are:
• ATM1
Burst Type
• ATM2
• IP (Reserved for future use)
• MPEG
The coding type for the Carrier Set.
Possible values are:
Coding Type
• Turbo (default)
• Concatenated (Legacy)
The spacing between carriers.
Carrier Spacing Select 1.2 or 1.25 from the pull-down menu.
1.5 is for legacy.
DVB RCS Parameters
Frame Type The type of frame for the Carrier Set.
RLSS Name Select the RLSS name using the pull-down menu
Using the pull-down menu select the MCD that will be used to
receive the RL bursts. In the case of a redundant configuration,
make sure to select the MCD belonging to the Operational
MCD Return Link Unit (RLU). To check the RLU state, open the
Physical Resource workspace of the RLSS Management Interface
(RMI) as described in Chapter 12.4, “RLSS Management
Interface (RMI)” on page 278.
When adding a Carrier Set, and this box;
• Is checked: The NMS automatically creates the Area,
Segment, Low Level RL SLA and SP RL SLA and assigns
default IDs.
• Is not checked: The user needs to create the Area and
Create Simple RL & SLA Segment and has the choice of IDs. In this case, when
creating the segment, the check box Create SP RL SLA will
be present and must be selected.
Note: The Service Provider must also be selected using the pull-
down menu.
• Depending on the Frequency Band configuration described
earlier, the choices may be General or Fix RCS if the
WaveSwitch Orientation Frequency does not support WaveSwitch.
• If the frequency band was configured to support
WaveSwitch, it automatically defaults to Var RCS/SCPC
RF Characteristics
Symbol Rate The Symbol rate (information only)
Frequency Band The Frequency Band to which this Superframe is associated.
Uplink Center Frequency The uplink center frequency for the Superframe. (information
(Hz) only)
Occupied Bandwidth (Hz) The width of the Superframe. (information only)
Down Conversion Enter the Down-Conversion factor.
(Satellite +LNB in Hz)
Table 9.16 RL Superframes Page Fields (Continued)

NMS Configuration
9.8.5.1.1 RL Superframes (Updating or Adding)
Procedure
Note: A new Superframe is applied immediately to the RLSS and thus a

frequency plan activation is not required.
1. To update any Superframe, in the Tree pane,

a. Under Satellites, select the desired satellite
desired superframe (refer to Figure 9.78). The results will be similar to
button.
2. To add a Superframe, in the Tree pane,
left click on the Add Superframe button (refer to Figure 9.80). The results will
be similar to Figure 9.81 and Table 9.16. Apply the desired changes and click
on the Add button.
Figure 9.78 RL Super Frame Updating Example Part 1

NMS Configuration
Figure 9.79 RL Super Frame Updating Example Part 2

NMS Configuration
Figure 9.80 Adding Super Frame Example Part 1

NMS Configuration
Figure 9.81 Adding Super Frame Example Part 2

NMS Configuration
9.8.5.1.2 Deleting a Superframe
Procedure
1. In the Tree pane, under Satellites, select the desired satellite, then desired
Frequency bands under the applicable satellite.
2. Select the desired superframe from the tree pane,
3. Select the triangle to the right of the Superframe and right click on the Delete
Superframe button (refer to Figure 9.82).
Figure 9.82 Deleting Superframes Example

NMS Configuration
9.8.5.1.3 Areas
• Must contain the required overhead slots to permit SIT login. Scheduling tool for
Return Link Sub-System.
• Linked to a Frequency Band Superframe and Transport Stream
Areas are accessed as follows:
Procedure
2. Then select:
• The required Frequency band
• The desired Superframe
• The desired Area (refer to Figure 9.83). The result is similar to Figure 9.84 and
Table 9.17.
Figure 9.83 Area Example Part 1

NMS Configuration
Figure 9.84 Area Example Part 2
.:
Field Description
General Information
Name The name that identifies the Area.
ID The numerical identifier for the Area.
Assignment
The Frequency Band to which the Area is
Frequency Band
associated.
Carrier Set ID The Superframe to which the Area belongs.
The Transport Stream associated with the
Transport Stream Id
Area.
Scheduling Parameters
Available Capacity / Max Capacity / The capacity parameters based on the
Granularity (kbit/s) Superframe associated with the Area.
Size (kbit/s) The size of the Area.
FCA value (kbit/s) The FCA bandwidth for the Area.
The starting carrier number
Start Carrier Number
(Set to 0 by default)
The number of carriers in the Area.
Number of carriers
(Automatically set and for information only)
Table 9.17 Area Page Fields

NMS Configuration
9.8.5.1.3.1 Area’s (Updating or Adding)
Procedure
1. To update any Area, in the Tree pane,

b. Then select:
• The desired Area of said Superframe. (refer to Figure 9.85).
c. The results will be similar to Figure 9.86 and Table 9.17. Apply the desired
changes and click on the Update button.
2. To add any Area, in the Tree pane,
b. Then select:
• Select the triangle to the right of the desired Superframe in the Tree pane
and left click on the Add Area button (refer to Figure 9.87). The results will
be similar to Figure 9.88 and Table 9.17. Apply the desired changes and
click on the Add button.
Figure 9.85 Area Updating Example Part 1

NMS Configuration
Figure 9.86 Area Updating Example Part 2
.:
Figure 9.87 Area Adding Example Part 1

NMS Configuration
Figure 9.88 Area Adding Example Part 2

NMS Configuration
9.8.5.1.3.2 Deleting an Area
Procedure
1. To delete any AREA, in the Tree pane,

b. Then select:
• The desired Area of said Superframe.
• Right click on the right triangle and click the Delete button.(refer to
Figure 9.89)
Figure 9.89 Deleting Area Example

NMS Configuration
9.8.5.1.4 Segments
• One or more segments can be defined for each area.

• Used for capacity assignment purposes
Segments are accessed as follows:
Procedure
2. Then select:
• The desired Area for said Superframe.
• The desired Segment for said Area. (refer to Figure 9.90). The result is similar
to Figure 9.91 and Table 9.18.
Figure 9.90 Segments Example Part 1

NMS Configuration
Figure 9.91 Segment Example Part 2
Field Description
General Information
Area The Area associated with the Segment.
Name The name that identifies the Segment.
Placing the cursor on the dotted line under
Segment ID the “Segment ID” shows the IDs already
used.
Persistent Traffic (RBDC) Time-out The RBDC time-out for the Segment.
Capacities
The maximum capacity that can be carried by
Maximum Capacity (kbit/s)
the segment (for information only)
Information field giving the available capacity
that is left after assigning the Segment
Maximum Available Capacity in Area Guaranteed Capacity.
(kbit/s) If the entered Guaranteed Capacity is equal to
the Maximum Capacity, then this value will be
0.
Table 9.18 Segment Page Fields

NMS Configuration
Field Description
Information field giving the slot size
depending of the selected payload for the
Granularity (slot size) (kbit/s)
Superframe, i.e., 16 kbit/s for ATM1, 32 kbit/s
for ATM2 and 56.7547 kbit/s for MPEG
Guaranteed Capacity (kbit/s) The segment’s guaranteed capacity.
The segment RBDC traffic.
It is recommended to enter the Guaranteed
Persistent Traffic (RBDC) (kbit/s) Capacity value.
Note: If a single segment is configured, then
enter Maximum Capacity value.
The left over capacity associated with the
segment.
Left-over Capacity (FCA) (kbit/s)
It is recommended to enter the Guaranteed
Capacity value.
Burstable Determines if the Segment is burstable.
RFCM Thresholds
The threshold at which to upgrade to a higher
Increase Protection Mode Threshold RFCM protection mode.
(dB) Only applicable for Return Link Rain Fade
Counter Measure (RFCM).
The threshold at which to downgrade to a
Decrease Protection Mode Threshold lower RFCM protection mode.
(dB)
Note: Only applicable to RFCM
Table 9.18 Segment Page Fields (Continued)
9.8.5.1.4.1 Segments (Updating or Adding)
Caution
If the Create Simple RL & SLA was not checked when creating the
Superframe, a check box labeled Create SP RL SLA will be present
Note: It must be selected and also the appropriate Service Provider (SP)
must be selected before clicking on the Add button
Procedure
1. To update any Segment, in the Tree pane,
c. Under Satellites, select the desired satellite, then select Frequency bands
under the applicable satellite.
d. Then select:

NMS Configuration
• The desired Area for said Superframe.

• The desired Segment for said Area. (refer to Figure 9.92). The result is
similar to Figure 9.93 and Table 9.18.
2. To add any Segment, in the Tree pane,
b. Then select:
• The desired Area for said superframe
• Select the triangle to the right of the desired Area in the Tree pane and left
click on the Add Segment button (refer to Figure 9.94). The results will be
similar to Figure 9.95 and Table 9.18. Apply the desired changes and click
on the Add button.
Figure 9.92 Segments Updating Example Part 1

NMS Configuration
Figure 9.93 Segments Updating Example Part 2
Figure 9.94 Segments Adding Example Part 1

NMS Configuration
Figure 9.95 Segments Adding Example Part 2

NMS Configuration
9.8.5.1.4.2 Deleting a Segment
Procedure
1. To delete any Segment, in the Tree pane,

b. Then select:
• The desired Area for said superframe
• The desired Segment of said Area
• Right click on the right triangle and click the Delete button.(refer to
Figure 9.96)
Figure 9.96 Deleting Segments Example

NMS Configuration
9.8.5.2 Continuous Carrier Set (DVB-S2)
Continuous Carrier Set are accessed as follows:
Procedure
Frequency Bands under the satellite. (refer to Figure 9.97).
Figure 9.97 RL Continuous Carrier Set Example Part 1

NMS Configuration
Figure 9.98 RL Continuous Carrier Set Example Part 2
This page lists each Continuous Carrier Set with the following parameters:
Field Description
General Parameters
Name The name that identifies the Continuos Carrier
ID The specific identification number. (for information only)
Encapsulation MPEG (for information only)
Coding Type LDPC (for information only)
Carrier Spacing The spacing between carriers. (for information only)
Table 9.19 RL Continuous Carrier Set Page Fields

NMS Configuration
Field Description
SCPC Parameters
SCPC Receiver Name Select applicable SCPC receiver from the list
Options are;
• QPSK
Modulation Scheme • 8PSK
• 16APSK
• 32APSK
With Pilot Select if Pilot is required
Short Frame Select if short frame is required
Rx PID’s (Separated by “,”) Enter desired RX PID numbers
Carrier Rate (kbps) Enter desired bit rate
Coding Rate Select desired Coding rate.
RF Characteristics
Symbol Rate The Symbol rate. (for information only)
The Frequency Band to which this Continuos carrier is
Frequency Band
associated.
Uplink Center Frequency The uplink center frequency for the Continuos carrier (for
(Hz) information only)
Occupied Bandwidth (Hz) The width of the Continuos carrier (for information only)
Down Conversion (Satellite The value to subtract from Frequency Plan reception frequency.
+LNB in Hz)
Table 9.19 RL Continuous Carrier Set Page Fields (Continued)
9.8.5.2.1 RL Continuous Carrier Set (Updating or Adding)
Procedure
1. To update any Continuous Carrier Set, in the Tree pane,

a. Under Satellites, select the desired satellite
desired Continuous Carrier Set (refer to Figure 9.99). The results will be similar
to Figure 9.100 and Table 9.19. Apply the desired changes and click on the
Update button.
2. To add a Continuous Carrier Set, in the Tree pane,
left click on the Add Continuous Carrier Set button (refer to Figure 9.101). The
results will be similar to Figure 9.101 and Table 9.19. Apply the desired changes
and click on the Add button.

NMS Configuration
Figure 9.99 Updating Continuous Carrier Set Example Part 1

NMS Configuration
Figure 9.100 Updating Continuous Carrier Set Example Part 2

NMS Configuration
Figure 9.101 Adding Continuous Carrier Set Example Part 1

NMS Configuration
Figure 9.102 Adding Continuous Carrier Set Example Part 2

NMS Configuration
9.8.5.2.2 Deleting a Continuous Carrier Set
Procedure
1. In the Tree pane, under Satellites, select the desired satellite, then desired
2. Select the desired Continuous Carrier Set from the tree pane,
3. Select the triangle to the right of the Continuous Carrier Set and right click on the
Delete Superframe button (refer to Figure 9.103).
Figure 9.103 Deleting Continuous Carrier Set

NMS Configuration
9.8.6 Frequency Plan Activation
9.8.6.1 Generic Frequency Plan Activation
Frequency plan activation is accessed as follows:
Procedure
1. In the Tree pane, select Frequency Bands (refer to Figure 9.104)

2. In the view pane, select the Frequency Band Components Tab.
3. The result is similar to Figure 9.105
Figure 9.104 Frequency Plan Activation Example Part 1

NMS Configuration
Figure 9.105 Frequency Plan Activation Example Part 2
9.8.6.2 Forward Link Frequency Plan Activation
The following steps must be completed:
1. Select the Frequency band component that has been modified. In this example,
select General. (refer to Figure 9.106).
2. The frequency band outline is then displayed at the bottom of the page. Click on
the Frequency Plan Activation button (refer to Figure 9.106).

NMS Configuration
Step 1
Step 2
Figure 9.106 FL Frequency Plan Activation Example (Steps 1 to 2)
3. From the Frequency Plan Activation page, enter a duration for the SCS command
to be sent to the SITs affected by the change and then click on the Start button
(refer to Figure 9.107). The SCS will configure the alternate TS parameters in each
of the SITs affected by the modified frequency plan.This allows the SCS to repeat
the same message for the period selected, ensuring that all SITs concerned are
properly configured since Multicast is used in this case.
4. Once the countdown is over or terminated by the operator, the SCS commands
on alternate TS parameters information box will turn green.

NMS Configuration
5. All the SITs concerned by the change are commanded to reboot and will therefore
log off. Before proceeding to the next step, wait for all the SITs to reconnect to the
network using the current FL parameters.
6. The Commit button will now be enabled. The operator must now press the
Commit button to activate all the configuration changes in the Gateway
equipment.The SITs will again be commanded to reboot. Make sure that the
command results at the bottom of the page are all successful.
7. Wait for the SITs to log back in using the new FL parameters. This may take a
while, since the SITs will initially try the last successful FL parameters before
switching to the new FL parameters.
8. Once the SITs have logged back in using the new FL parameters, the final step is
to configure the SITs Prime TS parameters. The operator has to enter a duration
for which the SCS commands are sent and press the Start button. The SCS will
configure the Primary Transport Stream acquisition parameters in each of the SIT
affected by the modified frequency plan.
9. Once the countdown is expired or terminated by the operator, the box SCS
commands on prime TS parameters changes to green color.
10. The new Frequency Plan has now been activated on the FL.
Step 10
Steps 4 Step 6 Step 3 & 8
Figure 9.107 FL Frequency Plan Activation Example (Steps 3 to 9)

NMS Configuration
9.8.6.3 Return Link Frequency Plan Activation
Any change made to an existing Return Link (RL) configuration (e.g., center fre-
quency, frame type, number of carriers, etc.) needs to be implemented by performing
a frequency plan activation.
The Return Link frequency plan activation is accessed as follows:
Procedure
1. Follow procedure as outlined in Chapter 9.8.6.1, “Generic Frequency Plan

Activation” on page 195
2. Select the Frequency band component that has been modified. In this case, select
Frequency band Variable. (refer to Figure 9.108).
3. The frequency band outline is then displayed at the bottom of the page. It should
be noted that the outline shows the new RL parameters that will be pushed to the
RLSS when the activation will be completed. Click on the Frequency Plan
Activation button (refer to Figure 9.108).
4. Click on the Commit button. (refer to Figure 9.109).
5. The NMS then pushes the changes to the RLSS. This operation can take several
minutes, depending on the complexity of the changes.After this point, the
parameters shown on the RLSS Management Interface (RMI) Return Link
workspace are the same as those in the NMS database.

NMS Configuration
Step 2
Step 3
Figure 9.108 RL Frequency Plan Activation Example (Steps 2 to 3)

NMS Configuration
Steps 4
Figure 9.109 RL Frequency Plan Activation Example (Step 4)
9.9 Satellites Overview
Procedure
1. In the Tree pane, select Satellites

2. For a general Satellite overview:
• Select the applicable Satellite (see Figure 9.110). The result is similar to
Figure 9.111.
3. For a specific satellite frequency band overview on a specific satellite.
• Select the applicable Satellite’s Frequency band (see Figure 9.112). The
result is similar to Figure 9.113.

NMS Configuration
Figure 9.110 Satellite General Overview Example Part 1
Note: You can tick the scale to fit check box to fit the results into your
current browsers window size
Figure 9.111 Satellite General Overview Example Part 2

NMS Configuration
Figure 9.112 Satellite Detailed Frequency Band

Components Overview Example Part 1

NMS Configuration
Note: You can tick the scale to fit check box to fit the results into your
current browsers window size
Figure 9.113 Satellite Detailed Frequency Band

Components Overview Example Part 2

NMS Configuration
9.10 Service Level Agreement View
Procedure
1. In the tree pane, select SLA. (refer to Figure 9.114).

2. The results will be similar to Figure 9.108.
The SLA View shows the SLA configurations of two separate Service Providers
(SP) and their linkage of the various SIT Groups to the Forward and Return Links.
Figure 9.114 Service Level Agreement View Example Part 1

NMS Configuration
Figure 9.115 Service Level Agreement View Example Part 2

NMS Configuration
9.11 RLSS Configuration
NMS needs to access the Gateway’s RLSS configuration in order to provide accu-
rate Return Link management services. To provide this, Network Operators create an
RLSS Configuration.
Note: When the Hubs are delivered to the customer, the RLSS configuration
is already created and should not require any modifications. This
section is for information only.
Procedure
Navigation Bar: Configuration → Hub Configuration
1. In the Tree pane, under Equipment Configuration, select Baseband

2. Then expand RLS and select RLSS. (refer to Figure 9.116).
3. The result is similar to Figure 9.117.
Figure 9.116 RLSS Configuration Example Part 1

NMS Configuration
Figure 9.117 RLSS Configuration Example Part 2
9.11.1 Adding or Updating the RLSS Configuration
If an RLSS configuration does not exist, the Add button will be enabled, indicating
that an initial profile must be created. If the Add button is disabled, then an RLSS pro-
file has already been created. In this case, the page displays the current RLSS config-
uration and only the Update operation is possible.
Network Operators can modify the RLSS profile and then click either the Add or
Update button, depending on the requirement. The RLSS profile fields are described
in Table 9.20.
Note: Certain fields will only appear on the page depending on the current
selection in the RLSS Version field.
Field Description
Name The name of the RLSS.
Supported RLSS versions are 1.5.x and 2.x.
RLSS Major Version
Note: RLSS version 1.5x is legacy only.
RLSS Specific The current version of the RLSS.
Version
Primary IP Address The primary IP Address of the RLSS.
Password of the FTP server used to save the RLSS configuration.
RLSS FTP Server
Password NOTE: Contact SpaceBridge Customer service before changing the default
password as this will affect the operation of the Hub.
Automatic Determines whether or not this RLSS should be automatically updated when
Configuration changes affecting its configuration are modified in the NMS.
Table 9.20 RLSS Profile Page Fields

NMS Configuration
9.12 Miscellaneous VSAT Definitions
9.12.1 Ranges
Ranges are a tool that Network Operators can use to further compartmentalize
Service Providers by restricting them to specified ranges of values for the following
parameters:
• IP addresses (see “IP Address Ranges (Optional)” on page 209).

• PIDs (see “PID Range” on page 161).
• VCCs (see “Configure Network Ranges Virtual Channel Connection Ranges”
on page 214).
Information
For CCM, PIDs are assigned when creating the SG FL SLA. One PID for SCS
and one PID for traffic.Signalling PIDs are described when creating the FL
TS.
9.12.1.1 IP Address Ranges (Optional)
IP address ranges allow for the partitioning of a domain of IP addresses into

smaller, typically non-overlapping ranges for use by different Service Providers. Ser-
vice Providers may be restricted to use a particular range of IP Addresses when
assigning them to SITs. Multiple IP ranges can be assigned to a given Service Pro-
vider, and the ranges can be classified according to usage.
The IP Address Ranges page displays the different ranges of IP Address made avail-
able to given Service Providers.
To access the page, proceed as follows:
Procedure
1. In the Tree pane, under Definitions, select IP Address Ranges. (refer to

Figure 9.118).

NMS Configuration
Figure 9.118 IP Address Ranges Example Part 1
Figure 9.119 IP Address Ranges Example Part 2

NMS Configuration
9.12.1.1.1 Adding or Updating IP Address Ranges
Procedure
1. In the Tree pane, under Definitions select IP Address Ranges.

2. To update any IP address range, simply pick it from the list (refer to Figure 9.120).
The results will be similar to Figure 9.121 and Table 9.21. Apply the desired
changes and click on the Update button.
3. To add an IP address range, select triangle to the right of the IP address range in
the Tree pane and left click on the Add IP Address button (refer to Figure 9.122).
The results will be similar to Figure 9.123 and Table 9.21. Apply the desired
changes and click on the Add button.
Figure 9.120 IP Address Range Updating Example Part 1
Figure 9.121 IP Address Range Updating Example Part 2

NMS Configuration
Field Description
Service Provider
Service Provider Select the Service Provider to which the IP range applies.
Parameters
Numerical identifier assigned automatically by the NMS and
IP Address Range ID
used to name this IP Address range.
The first IP Address assignable for the Service Provider using
IP Address Range this range, entered as a numerical IP address:
Start
xxx.xxx.xxx.xxx
The mask determines the valid assignable IP addresses,
limited at the lower-end by the Range Start (as described in
IP Mask the IP Address Range Start field).
The format for the IP Mask field is that of a numerical IP
Address.
Usage type The intended usage type for this IP Address Range.
Transport Stream Select the Transport Stream using the pull-down menu
Table 9.21 IP Address Range Page Fields
Figure 9.122 IP Address Range Adding Example Part 1

NMS Configuration
Figure 9.123 IP Address Range Adding Example Part 2
9.12.1.1.2 Deleting an IP Address Range
Procedure
1. In the Tree pane, under Definitions, select IP Address Ranges.

2. Then select the desired IP Address range. and right click on the right triangle and
click the Delete button. (refer to Figure 9.89)
Figure 9.124 Deleting IP Address Range Example

NMS Configuration
9.12.1.2 Configure Network Ranges Virtual Channel Connection Ranges
A virtual connection (VC) defines a logical networking path between two endpoints
in an ATM network and through which the 53 byte ATM cells travel. In other words,
VCCs are logical circuits uniquely identified for each link of the network. The Payload
part of an ATM cell contains the user data while its header includes an 8-bit Virtual
Path Identifier (VPI) and a 16-bit Virtual Channel Identifier (VCI).
One type of Virtual Connection used to switch ATM traffic is the Virtual Channel
Connection (VCC). The VCC is formed by joining a series of Virtual Channels and
uses the combined VPI and VCI values to move traffic from one link to another.
SP VCC Ranges allow for the separation of VCCs for use by different Service Pro-
viders based on assigned ranges of VPIs and VCIs. Multiple VCC Ranges can be
assigned to a given Service Provider.
To access the page, proceed as follows:
Procedure
1. In the Tree pane, under Definitions, select VCC Pools. (refer to Figure 9.125).
Figure 9.125 VCC Pools Example Part 1

NMS Configuration
Figure 9.126 VCC Pools Example Part 2
9.12.1.2.1 Adding or Updating Virtual Channel Connection Ranges
Procedure
1. In the Tree pane, under Definitions, select VCC Pools

2. To update any VCC Range, simply pick it from the list (refer to Figure 9.127). The
and click on the Update button.
3. To add a VCC Range, select triangle to the right of the VCC Pool in the Tree pane
and left click on the Add VCC Pool button (refer to Figure 9.129). The results will
be similar to Figure 9.130 and Table 9.22. Apply the desired changes and click on
the Add button.
Figure 9.127 VCC Range Updating Example Part 1

NMS Configuration
Figure 9.128 VCC Range Updating Example Part 2
Field Description
Service Provider
Service Select the Service Provider to which the VCC Pool applies.
Provider
Configuration Parameters
VPI Start The first available VPI value in this VCC Range.
VPI End The last available VPI value in this VCC Range.
VCI Start The first available VCI value in this VCC Range.
VCI End The last available VCI value in this VCC Range.
Usage Type Select Indiscriminate
Table 9.22 VCC Range Page fields

NMS Configuration
Figure 9.129 VCC range Adding Example Part 1
Figure 9.130 VCC Range Adding Example Part 2

NMS Configuration
9.12.1.2.2 Deleting a Virtual Channel Connection Range
Procedure
1. In the Tree pane, under Definitions, select VCC Pools

2. Then select the desired VCC Range and right click on the right triangle and click
the Delete button. (refer to Figure 9.131)
Figure 9.131 VCC Range Delete Example

NMS Monitoring & Control (M & C)
Chapter 10 NMS Monitoring & Control (M & C)
10.1 Hub Equipment M & C
10.2 RF Equipment M & C
10.3 VSAT M & C
VSAT Monitoring & Control Main can be broken down into the following sections:
• VSAT M&C Tab

• Operations Tab
• Configuration Tab
• Overwrite (OW) QoS Tab
• Statistics Tab
• ACM Tab (Optional)
• WaveSwitch Tab (Optional)
• SIT Groups M&C Tab
Note 1. The ACM tab is only present if the Hub is equipped for the optional
ACM operation.
Note 2. The WaveSwitch Tab is only present if the Hub is equipped for the
optional WaveSwitch operation.
Procedure
Navigation Bar: Monitoring → VSAT M&C

Tabs
Stats Area
Figure 10.1 VSAT M&C Example

The commands are covered in Chapter 10.3.3, “Commands” on page 236
10.3.1 VSAT M&C Tab
10.3.1.1 VSAT M&C Overview
Network Operators can observe and control SIT activity on the system using the
VSAT M&C page.
Procedure
1. In the view pane, select the VSAT M&C Tab. The result is similar to Figure 10.1.
The SITs displayed in the on this page can be filtered using the four list-boxes at
the top of the page: SITs can therefore be filtered according to the following four crite-
ria:
• Service Provider
• SIT Group
• SIT Name
• SIT State (e.g. Traffic Ready)
The results can display a few SITs at a time, but a scroll bar is available to access
up to 50 SITs per display; if the number of SITs to display exceeds 50, they will be split
into pages and a button labelled Next will appear at the bottom of the page, allowing
navigation between pages of SITs.
For convenience, an overview of the principal status information on SITs is pre-

sented, above the results, in a box named Stats. It shows a summary of number of
SITs in given states, as explained in the table below.
Field Description
Active The number of Active SITs.
Total The total number of SITs configured on the system.
Logging In The number of SITs currently logging in to the system.
The total number of SITs that are in OAM Ready state (independent
OAM Rdy
of the SIT State filtering selected).
The total number of SITs that are in Traffic Ready state
Trf Rdy
(independent of the SIT State filtering selected).
Disabled The number of SITs currently disabled.
Table 10.1 VSAT M&C Summary Fields

Unknown The number of SITs in an unknown state.

Sleep The number of SITs in the sleep state.
Table 10.1 VSAT M&C Summary Fields (Continued)

Also, the NMS presents an overview of the principal status information on filtered
SITs in a box named Filtered Stats. The filtered SITs are the subset from the whole
SIT population once the filters have been applied.
Various commands can be issued to SITs, using the buttons at the bottom of the page
(see Chapter 10.3.3, “Commands” on page 236).
10.3.1.2 VSAT M&C (Operations Tab)
The Operations view (see Figure 10.1) in the VSAT M&C page is accessible by
clicking on the Operations tab. It presents information relevant to SIT Operations; of
special interest is the fact that the State of each SIT is shown using a color code
(described in Table 10.2) for easier identification.
Field Description
The MAC address of the SIT, which is the primary identifier for a
MAC Address
SIT.
SIT Name The name that identifies the SIT.
The state of the SIT as of last page refresh. The states are color
coded to make them easy to identify at a glance. Possible states
are:
• Unknown (blue): SIT is not logged in; nothing else can be
determined from this state.
• Entry Request (Forest green): The SIT has requested to join
the network and is in the process of synchronizing the Return
Link (CSC, ACQ, SYNC).
• OAM Ready (Green): The SIT failed to acknowledge MIB
configuration; Return Link is synchronized but the normal
SNMP exchanges with the SIT did not complete successfully.
State • Traffic Ready (BOLD Forest green): The SIT has requested to
transmit traffic and maintains its Return Link synchronization;
either the normal SNMP exchanges between the SIT and the
CM have completed successfully or the SIT has been
configured to bypass the SNMP exchanges (manual traffic
VCC).
• Sleep: The SIT is not currently synchronized into the network
but the last ping attempted to that SIT OAM IP address
succeeded.
• Hold (yellow)
• TX Disabled (yellow)
• Deny Service (yellow)
The CRA traffic bit rate for the monitored SIT, based on the SIT’s
CRA (kbit/s)
QoS.
Table 10.2 VSAT M&C (Operations) Page Fields

The RBDC traffic bit rate for the monitored SIT, based on the SIT’s
RBDC max (kbit/s)
QoS.
The VBDC traffic bit rate for the monitored SIT, based on the SIT’s
VBDC max (kbit/s)
QoS.
The Return Link Signal to Noise ratio, as defined by:
RL Es/No (db)
Energy per symbol / Noise power spectral density.
Protection Level The current Protection level for the SIT (clear sky, rain fade 1-3).
The resulting time from the last ping command sent to the SIT.
Ping Time (ms) Only applies to Return Link Rain Fade Countermeasure (RFCM). If
not used, it displays Clear Sky.
Table 10.2 VSAT M&C (Operations) Page Fields (Continued)

Note 1. The Entry Request and OAM ready states are transient states. A
SIT remaining in one of these states for a prolonged period of time
may be experiencing problems.
Note 2. If the SIT stays in the Entry Request phase, it may be experiencing
problems with Return Link synchronization, MAC layer message
reception (between the SIT and the RLSS), SNMP communication
between the CM and the RLSS, or problems with software.
Note 3. If the SIT remains in the OAM ready state, it may simply mean that
the SIT has in fact no traffic to transmit, but it may also be indicative
of SNMP communication problems (between the SIT and the CM).

10.3.1.3 VSAT M&C (Configuration Tab)
Procedure
1. In the View Pane, select the Configuration Tab. (refer to Figure 10.1).
2. The result is similar to Figure 10.2. and Table 10.3
Field Description
MAC Address
SIT.
Ethernet Subnet The subnet for the SIT.
PEP Enabled Reflects whether or not the SIT is PEP enabled.
PEP Compression Reflects whether or not the SIT is using PEP Compression
Mesh Receive Reflects whether the SIT is enabled for Mesh operation.
Enabled
Software Version Reflect the software version running on the SIT.
Reflects whether the SIT is in a state where it requires a reboot
Reboot Required
(after a software download).
SIT Group The SIT Group to which the SIT belongs.
Table 10.3 VSAT M&C (Configuration Tab) Page Fields

Figure 10.2 VSAT M&C (Configuration Tab) Example

10.3.1.4 VSAT M&C (OW QoS Tab)
Procedure
1. In the View Pane, select the OW QoS Tab. (refer to Figure 10.1).
Field Description
MAC Address
SIT.
Yes indicates that the QoS is overwritten and therefore different
OW FL QoS
than the one specified for the SIT Group.
Yes indicates that the QoS is overwritten and therefore different
OW RL QoS
than the one specified for the SIT Group.
By default one OAM and one Traffic are created when a SIT is
IP Routes
added. Additional routes can be created.
By default one OAM is created when adding a SIT. Additional
Queues
Queues may be created depending on application, e.g, VoIP, MESH.
Table 10.4 VSAT M&C (OW QoS Tab) Page Fields

Figure 10.3 VSAT M&C (OW QoS Tab) Example

10.3.1.5 VSAT M&C (Statistics Tab)
Procedure
1. In the View Pane, select the Statistics Tab. (refer to Figure 10.1).
Field Description
MAC Address
SIT.
Bytes RL/FL Provides the RL/FL totals bytes transferred by the SIT for the
Yesterday (kB) previous day
Bytes RL/FL Provides the RL/FL totals bytes transferred by the SIT since 00h00
Today (kB) of the current day up to the current time
Current Bitrate Provides current RL/FL traffic in kbps.
RL/FL (kbps)
Table 10.5 VSAT M&C (Statistics Tab) Page Fields

Figure 10.4 VSAT M&C (Statistics Tab) Example

10.3.1.6 VSAT M&C (ACM Tab)
Procedure
1. In the View Pane, select the ACM Tab. (refer to Figure 10.1).
Field Description
MAC Address
SIT.
FL PID Forward Link PID used by the SIT.
MODCOD Used MODCOD used by the SIT.
Efficiency Factor Bandwidth efficiency factor for this SIT.
Table 10.6 VSAT M&C (ACM Tab) Page Fields

Figure 10.5 VSAT M&C (ACM Tab) Example

10.3.1.7 VSAT M&C (WaveSwitch Tab)
Procedure
1. In the View Pane, select the WaveSwitch Tab. (refer to Figure 10.1).
Field Description
MAC Address
SIT.
WaveSwitch Mode/ Shows whether the SIT is operating in DVB-RCS, ASAT or SCPC
Current Bit Rate along with current bit rate
(kb/s)
Table 10.7 VSAT M&C (WaveSwitch Tab) Page Fields

Figure 10.6 VSAT M&C (WaveSwitch Tab) Example

10.3.2 SIT Groups M&C Tab
Procedure
1. In the View Pane, select the Sit Groups Tab. (refer to Figure 10.1).
Field Description
SIT Group The SIT Group name.
Nbr. Configured SITs The number of SITs configured in the SIT Group.
The number of SITs of the SIT Group that are currently
Nbr. SITs Logged in
logged in.
Multicast group Whether the SIT Group is Multicast or not.
SIT Software Version The SIT software versions elected for this group.
Geo Redundancy State The current Geographic Redundancy state of the SIT Group.
Table 10.8 VSAT M&C (SIT Groups M&C Tab) Page Fields

Figure 10.7 SIT Groups M&C Tab Example

10.3.3 Commands
Both the VSAT M&C and SIT Groups M&C pages allow operators to control the
SITs through a set of commands. There are several types of mechanisms available to
send commands to SITs, mainly distinguished by the data transmission method:
10.3.3.1 Layer 2 Commands
Individual SITs can be issued a command by selecting the checkbox beside its
MAC Address and clicking the appropriate button for the command:
To Summarize:
• Wake Up: Sends a wake up command to the selected SIT; this does not
command the SIT to log in.
• Log off: Sends a log off command to the selected SIT.
• Enter HOLD: Shuts down the SIT transmission which can only be re-enabled by
the NMS using the Leave HOLD command
• Leave HOLD: Enable the SIT transmission following the Enter HOLD command
• Allow: Permits the selected SIT to logon to the network, presumably after a Deny
command has previously been issued.
• Deny: Prevents the selected SIT from logging in to the network. When a SIT is
denied network access, any services configured for it become inactive. Services
can still be configured for a SIT that has been denied network access, but they will
not become active until the SIT is allowed entry into the network.
Note: After sending a command to a SIT, verify that its state is consistent with
the expected result of the command. For example, if you send a Logoff
command to a SIT in the Traffic Ready state, its state should change to
Unknown.
• SIT Reboot: Sends an SNMP reboot command to the selected SIT.

10.3.3.2 Layer 3 SCS Commands
The Layer 3 SCS commands are used to set various SIT parameters and also to
send commands to the SITs (e.g., Tx enable/disable, Software Update, Reboot, etc.).
In general:
Layer 3 SCS can send commands to:
• VSAT M&C
• Individual SIT (using Unicast)
• SIT GROUPS:
• All SITs belonging to a SIT Group (using Multicast)
• The SCS Multicast address for a given SIT Group is
239.255.255.<Group_number>
• The SCS PID is the one of the SG-Forward Link-Service Level Agreement to
which the SIT Group is linked
• The SCS multicast route is automatically added to the IPE
• Each SIT requires the following information in order to be able to receive SCS
multicast commands.
• SCS Group Number
• SCS Port Number
• SCS PID
To Summarize:
• Enable TX: Enables Transmission on the SIT.

• Disable TX: Disables Transmission on the SIT
• Acquire Return Link: Commands the SIT to acquire the Return Link.
• Acquire Forward Link: Forces the re-acquisition of the Forward Link
(configuration “A” on the IDU web page).
• Acquire 2nd Forward Link: Forces the re-acquisition of the second Forward Link
(configuration “B” on the IDU web page).
• Software Update: Permits upgrading the SIT software (software specified for the
SIT Group).
• Reboot from Alternate Image: Reboots the SIT and instructs them to restart
using their alternate software image (software B).
• Send SCS Parameters: Is used to set SIT parameters and is present on the
pages where the command can be sent. The SIT will then reboot. The default port
number (1500) which needs to be configured on the IDU as well.
• SCS Logoff: Forces the SIT to logoff from the network.
• Reboot: Restarts the SIT.

10.3.3.3 Operational Commands
These commands are sent using SNMP commands to selected SITs using the
OAM IP address. In this case, the SCS messages are Unicast.
Multicast SCS messages are sent when using the commands located on the SIT
Group Monitoring / Control page. In this case messages are sent to the all SITs
belonging to a Group using multicast.
• SIT RL QoS: Access the SIT RL QoS page of the selected SIT where the QoS
can be changed (refer to Chapter 9.6.3, “SIT Return Link QoS” on page 116).
• SIT OAM Ping: Pings the SIT (once, and only in Traffic Ready state) using SCS;
reports the value in the Ping Time column of the table, The page needs to be
refreshed to see the results.
• SIT Events: Navigates to the Connection Manager Events page (see Chapter
10.5.2, “Connection Manager Events” on page 239) filtering the displayed result
according to the selected SIT.
• SIT Alarms: Navigates to the Connection Manager Alarms page (see Chapter
10.5.3, “Operations Connection Manager Alarms” on page 241) filtering the
displayed result according to the selected SIT.
• WaveSwitch Events: Displays WaveSwitch related events. Shortcut to the page
“Monitoring --> SIT Events --> WaveSwitch Events

10.4 Network Performance
10.5 System Events
10.5.1 Overview
• Connection Manager Events

• Connection Manager Alarms
• WaveSwitch Events
• Equipment Monitoring Events
• Commands/Results
• User Activity
10.5.2 Connection Manager Events
This feature allows Network operators to review operation events that have occurred.
Procedure
Navigation Bar: Monitoring→ System Events
1. In the Tree pane, select Connection Manager Events. (refer to Figure 10.8).
Figure 10.8 Connection Manager Events Example Part 1

Figure 10.9 Connection Manager Events Example Part 2
You can sort these events simply by selecting any one of the column headings (selected column headings appear in yellow).

10.5.3 Operations Connection Manager Alarms
This feature allows Network operators to review operation alarms that have occurred.
Procedure
1. In the Tree pane, select Connection Manager Alarms. (refer to Figure 10.10).
Figure 10.10 Connection Manager Alarms Example Part 1

Figure 10.11 Connection Manager Alarms Example Part 2
You can sort these events simply by selecting any one of the column headings (selected column headings appear in yellow).

10.5.4 WaveSwitch Events
Procedure
1. In the Tree pane, select WaveSwitch Events. (refer to Figure 10.12).

Figure 10.12 WaveSwitch Events Example Part 1


10.5.5 Equipment Monitoring Events
Procedure
1. In the Tree pane, select Equipment Monitoring Events. (refer to Figure 10.14).
Figure 10.14 Equipment Monitoring Events Example Part 1

Figure 10.15 Equipment Monitoring Example Part 2

10.5.6 Command/Results
The Commands/Results page enables operators to monitor the result of certain

equipment configuration commands, such as the configuration of an IP/DVB Encap-
sulator with updated SP FL SLA information.
Procedure
1. In the Tree pane, select Command/Results. (refer to Figure 10.16).

Figure 10.16 Command/Results Example Part 1

Figure 10.17 Command Results Example Part 2

10.5.7 User Activity
This feature allows Network operators to review System User activity details.
Procedure
1. In the Tree pane, select User Activity (refer to Figure 10.18).

Figure 10.18 User Activity Example Part 1

Figure 10.19 User Activity Example Part 2

Chapter 11 NMS Account Management
11.1 Account Management
11.1.1 Account Categories
NMS security scheme provides for two user classes, Network Operators (NO) and
Service Providers (SP), each sub-divided into user categories with different access
rights depending on the tasks they must perform and the responsibilities they have.
• Network Operator: This is the meta-user that has access to the entire database,
including the data for all Service Providers. The Network Operator class is divided
into the following categories of users: This is the owner of the system; this user
class manages the NMS application and supports the Service Providers.
• Administrator: The system Super-user. Users in this category can
perform any valid operation on the database, i.e. create, update and delete
any entity (SLAs, SITs, IP/DVB Encapsulators, etc.) in the database. They
can also create and delete Service Providers and user accounts of any
type as well as change the password for any operator account. They can
also use special features, such as RLSS configuration import.
• Operator: Users in this category can create, modify and delete SIT
resources as well as send commands to SITs belonging to any Service
Provider.
• Viewer: These users have read-only access to the entire database.
Note: At installation time, NMS is configured with three pre-defined user

accounts: NO Administrator, NO Operator and NO Viewer, with default
usernames and passwords; these accounts can be customized as
desired.
• Service Provider: This is the user class representing an organization that is

offering the services to end-users. The Service Provider class is divided into the
following categories of users:
• Administrator: Users in this category can perform any valid operation on data
belonging to the given Service Provider, i.e. they can create, update and
delete any entity (SIT Groups, QoS’s, etc.) in their own section of the
database. They can also change the username of user accounts belonging to
the given Service Provider.
• Operator: Users in this category can create, modify and delete SIT resources
as well as send commands to SITs that belong to this Service Provider.
• Viewer: These users have read-only access to the database for the given
Service Provider.
Note: Any user has the ability to change his own password at will.

NMS Account Management
11.1.1.1 Account Management Overview
To access this feature, proceed as follows:
Procedure
Navigation Bar: Account Management
1. In the Tree pane, either select Service Providers or User Accounts. (refer to
Figure 11.1).
Figure 11.1 Account Management Example Part 1

Figure 11.2 Account Management Example Part 2

11.1.1.2 User Management Service Providers
This feature allows Network operators to manage the Service Provider details.
All services configured in the NMS are linked to a Service Provider. Each Service
Provider has three default users, one for each category (see Chapter 11.1.1, “Account
Categories” on page 251): Administrator, Operator and Viewer, with distinct user-
names and passwords.
Procedure
1. In the Tree pane, either select Service Providers (refer to Figure 11.3).
Figure 11.3 Service Providers Example Part 1

Figure 11.4 Service Providers Example Part 2

11.1.1.2.1 Adding or Updating Service Providers
Procedure
1. In the Tree pane, select Service Providers.

2. To update any service provider, simply pick it from the list (refer to Figure 11.5).
The results will be similar to Figure 11.6 and Table 11.1. Apply the desired changes
3. To add a service provider select triangle to the right of the Service Providers in the
Tree pane and left click on the Add Service Provider button (refer to Figure 11.7).
The results will be similar to Figure 11.8 and Table 11.1.
When creating a new Service Provider profile, three default users linked to the
new Service Provider are automatically created: Administrator, Operator and Viewer.
If you require additional users, they can be added to the Service Provider profile at
any time (see Chapter 11.1.1.4, “Account Management User Accounts” on page 267).
The Network Administrator needs to define a user name and a password for each
Service Provider profile using the fields described in Table 11.2. Enter the fields as
required and click the Add button
Figure 11.5 Updating Service Provider Example Part 1

Figure 11.6 Updating Service Provider Example Part 2
Information
If you want to Update the default Users assigned to a service provider, you
have to edit them in user accounts. See Chapter 11.1.1.4, “Account
Management User Accounts” on page 267

Field Description
Service Provider Information
The name of the Service Provider.
Name
Note: This field cannot be modified once the
Service Provider has been created.
The full name of the main contact person for
Contact Name
this Service Provider profile.
The primary phone number where the contact
Phone Number
person can be reached.
Max Number Of The maximum number of SITs that this
Configured Service Provider profile is allowed to configure
Terminals into the system
Table 11.1 Service Provider Information fields
Default Service Provider Users

Administrator Login The login name for the default user with administrative access to the
Name database.
Password The password for the Administrator user profile.
Operator Login Name The login name for the default user having only access to the SIT data
for the Service Provider.
Password The password for the Operator user profile.
Viewer Login Name The login name for the default user having only read-only access to the
Service Provider’s database.
Password The password for the Viewer user profile.
Table 11.2 Default Service Provider User Fields
Figure 11.7 Adding a Service Provider Example Part 1

Figure 11.8 Adding a Service Provider Example Part 2

11.1.1.2.2 Deleting a Service Provider
WARNING
DELETING ANY SERVICE PROVIDER WILL RESULT IN THE DELETION
OF ALL USERS ASSOCIATED TO SAID SERVICE PROVIDER.
Procedure

2. Then select the desired Service Provider. and right click on the right triangle and
click the Delete button. (refer to Figure 11.9)
Figure 11.9 Deleting a Service Provider Example

11.1.1.3 Account Management Customer
This feature allows Network operators to enter customer information which may then
be associated with services.
Procedure

2. Then select the desired the desired Service Provider.
3. Then select the desired Customer (refer to Figure 11.10).
Figure 11.10 Customer Example Part 1

Figure 11.11 Customer Example Part 2

11.1.1.3.1 Adding or Updating Customers
Procedure

2. To update any customer simply pick it from the list (refer to Figure 11.12). The
results will be similar to Figure 11.13. Apply the desired changes and click on the
Update button.
3. To add a customer, select triangle to the right of the desired Service provider in the
Tree pane and left click on the Add Customer button (refer to Figure 11.14). The
results will be similar to Figure 11.15. Apply the desired changes and click on the
Add button.
Figure 11.12 Updating Customers Example Part 1

Figure 11.13 Updating Customer Example Part 2

Figure 11.14 Adding Customer Example Part 1
Figure 11.15 Adding Customer Example Part 2

11.1.1.3.2 Deleting a customer
Procedure

2. Then select the desired customer. and right click on the right triangle and click the
Delete button. (refer to Figure 11.16)
Figure 11.16 Delete a Customer Example

11.1.1.4 Account Management User Accounts
This feature allows Network operators to manage the System users details.
Information
1. Only Network Operator Administrators can create or delete user
accounts.
2. In addition to the account authentication process, NMS has an added
security feature in the form of an Access Control List (ACL). The ACL,
which is maintained on a per-user basis, can restrict the hosts from
which users can connect to NMS to only certain IP Addresses. This
means that, if the ACL is configured for a given user, this user will not
be allowed to login to NMS unless his host IP address has been allowed
by adding it to the ACL. Leaving the ACL list blank removes this security
feature.
Procedure
1. In the Tree pane, select User Accounts. (refer to Figure 11.17).

Figure 11.17 User Account Example Part 1

Figure 11.18 User Accounts Example Part 2

11.1.1.4.1 Adding or Updating User Accounts
Procedure
1. In the Tree pane, select User Accounts

2. To update any User account, simply pick it from the list (refer to Figure 11.19). The
3. To add a User account, select triangle to the right of the User Accounts in the Tree
pane and left click on the Add User button (refer to Figure 11.21). The results will
be similar to Figure 11.22 and Table 11.3. Apply the desired changes and click on
the Add button.
Figure 11.19 Updating User Account Example Part 1

Figure 11.20 Updating User Accounts Example Part 2

Field Description
User Account Details
Service Provider Select the SP to which this account belongs
Login The Username assigned to the user account.
When changing the password for an existing user account, you must
provide the current password as a security measure.
Old Password
Note: This parameter is not required for creating a user profile; the
field is grayed-out.
New Password Enter the desired password for the user.
Re-enter the password you typed in the New Password field to
validate it: the password you type in the Verify New Password field
Verify New Password
must match the New Password field for the operation to be
accepted.
The user type associated to this user account. This field is editable
when adding a new user, otherwise it will be grayed-out.
User Type
Note: The Network Operator type is only available if no Service
Provider was associated with the new user account.
Primary Client IP First ACL address from which the user can connect to the NMS
Address
Secondary Client IP Second ACL address from which the user can connect to the NMS
Address
Third Client IP Third ACL address from which the user can connect to the NMS
Address
Table 11.3 User Account Page Fields
Figure 11.21 Adding User Account Example Part 1

Figure 11.22 Adding User Account Example Part 2

11.1.1.4.2 Deleting a User Account
Procedure
1. In the Tree pane, select User Account

2. Then select the desired user account and right click on the right triangle and click
the Delete button. (refer to Figure 11.23)
Figure 11.23 Deleting User Account Example


Chapter 12 RLSS Unit
12.1 General
The RLSS is the part of a DVB-RCS gateway responsible for the Return Link. it’s
main functions are:
• Receives Return Link communications from SITs and forwards it to an IP

network.
• Handle SIT logon / SIT synchronization.
• Allocates Return Link capacity.
• Uses the Forward Link to send signaling and control information to SITs.
The RLSS can be subdivided into these functional cores.
• OA&M – Operation, Administration and Maintenance.

• Signalling Core – Controller/scheduler and Receiver signalling functionality.
• Demodulator Core.
• Traffic Core.
A user interface is provided by either HTTP and/or SNMP.
12.2 RLSS Front Panel
Board LED Meaning

PMC P0 (Red) EPLD Programmed
P1 (Red) EPLD Programmed
S0 (Amber) Alarm Status: OFF=OK, ON= Active
Fault
S1 (Amber) Flashing: 10MHz and 1PPS OK
S2 (Green) ON: TS Mode active
S3 (Green) ON: Timing Mode active
5 V (Red) 5V
PG (Red) FPGA Configuration Status
Table 12.1 RLSS Front Panel LED’s

RLSS Unit
Board LED Meaning

MCD 2 MIF (Green) Must be ON
LED 1 (Amber) Must be ON
LED 5 (Green) Must be ON
LED 6 Must be OFF
PWR5 (Green) Must be ON
PWR15 (Green) Must be ON
Table 12.1 RLSS Front Panel LED’s (Continued)
Reserved
LINK
Aux
ETH2 (Traffic)
P0 S1 S3 5V
P1 S0 S2 PG
RESET
CONS
ETH1
(Mgmt)
Figure 12.1 RLSS Modules

RLSS Unit
Figure 12.2 RLSS-100 Front Panel
Figure 12.3 RLSS-100 Rear Panel
Figure 12.4 RLSS-200 Front Panel
Figure 12.5 RLSS-200 Rear Panel

RLSS Unit
12.3 RLSS User Accounts
Caution
Network Operators are advised that the user name and password provided
below are for information only. It is recommended that all modifications to
the system should be done via Chapter 9 "NMS Configuration" when ever
possible.
In the event that you must access this unit via the user ID and password
shown below, it should be done by qualified personnel only.

(See note 1) (See note 1) Used for
hub_user hub All Privileges

sit_user sit Satellite Ephemeris (SED)/Frequency
Translation Error (FTE) updates and
system monitoring
demo 12345 Read only
Table 12.2 RLSS User Accounts

entered as shown.
12.4 RLSS Management Interface (RMI)
The RLSS management interface (RMI) can be accessed from any PC with IP
access to the RLSS. JAVA must be installed.
1. Network Operators can access the RLSS via the IMS server’s pre configured web
browser.
a. If you have not already logged into the IMS, refer to Chapter 7.3.3, “Logging in
to the IMS Server” on page 76.
2. If you have already logged into the IMS, open Firefox and select the RLSS
bookmark and log in to the RLSS application.
3. You will be prompted for a user ID and Password.

RLSS Unit
Password is: hub
Note: Default RLSS User ID and password shown. Refer to Table 12.2.
Figure 12.6 RLSS Access via WEB Browser
You will then an security advisory. This is normal. Click on OK.
Click OK
Figure 12.7 RLSS Login Security Prompts

RLSS Unit
Figure 12.8 RLSS Initial Page

RLSS Unit
12.4.1 RLSS Main Page
The RLSS main page can be broken down as follows:
• Workspace’s.
• Tree Pane.
• View Pane.
View Pane
Tabs
Page Refresh
Controls
Open Work Read Only

Space Field
Editable
Field
Apply Field
Change
Drop Down
List
Tree Pane
View Pane
Figure 12.9 RLSS Main Page
12.4.1.1 RMI Workspace’s
Each RMI workspace provides access to a related group of RLSS management

features.
• RLSS Physical Resources.

• Forward Link Resources.
• Return Link Resources.
• Satellite Resources.
• Terminals.
• Frame Definitions.
Each workspace displays a subset of the RLSS database in the tree pane.

RLSS Unit
12.4.1.2 Tree Pane
12.4.1.2.1 Tree Pane - General
• Provides a view of a subset of the RLSS database according to the active

workspace.
• Basic objects in the database, such as cores, are grouped into higher-level
database elements, such as units.
• The hierarchical tree view gives easy visual access to the organization of
basic objects and higher-level elements.
Switch
Controls
Sequence
Object
Link
Individual
Object
Figure 12.10 RMI Tree Pane Examples
12.4.1.2.2 Tree Pane - Navigation Tips
• Single mouse click on switch controls will expand or collapse the tree view.
• Objects can be viewed or modified once selected with a single mouse click.
• Information related to a selected object is displayed in the view pane.
• Links to elements located elsewhere in the RLSS database hierarchy are
indicated with the shortcut arrow at the bottom left of the icon.

RLSS Unit
12.4.1.3 View Panes
• Enables the operator to view or modify the database object selected in the
tree pane.
• Properties of objects in the view pane are displayed in color-coded fields.
• Gray fields are view-only.
• White fields can be edited, either by selecting from a drop-down list or
typing directly in the field. Click Apply to execute the changes to the
RLSS.
• The status bar at the bottom of the page shows the results of these
changes.
• Some database objects have multiple view panes associated with them.
• To access another view pane, click on a view pane tab.
• Table Views
• Selecting a sequence header presents a table view of all the associated
parameters.
• Clicking on any entry in the table links to the properties of the selection.
• Sort the view by selecting on any column.
• Columns can be re-ordered as desired.
• Global Object Table Views
• To view all objects of a specific type.
• Select a Object Sequence.
• Toggle the LOCAL selector to GLOBAL to view all Objects in the table
view.
• Terminal example.

RLSS Unit
Figure 12.11 Multiple View Pane Example

RLSS Unit
Figure 12.12 Table View Pane Example
Figure 12.13 Global Object Table View Pane Example

RLSS Unit
12.5 RLSS Status Monitoring
12.5.1 RLSS Monitoring from RMI
The Primary view of RLSS status is available via the Physical Resource Work-
space. Core status alarms are indicated by a highlighted background and a white
background indicates Normal Status.
The Core state is indicated by text next to the associated object.
Normal Core
(White background)
Alarmed Core
(Orange Background)
Figure 12.14 Physical Resource Space Information Examples
Color Description
White Normal/Information
Light Blue Warning
Yellow Minor Alarm
Orange Major Alarm
Table 12.3 Alarm Status Color Coding

RLSS Unit
12.5.2 RLSS Alarms/Notifications and Monitoring
12.5.2.1 Active Notifications
Figure 12.15 RLSS Active Notifications Example
12.5.2.2 Notification Logs
Figure 12.16 RLSS Alarm Log Example

RLSS Unit
12.5.2.3 RLSS Traffic Monitoring
The RLSS provides information related to the raw traffic received from the MCD
as well as data related to the IP dekagrams being forwarded to the IPSS. The raw
ATM, raw MPEG, and IP datagram statistics are available to the operator on separate
view panes.
Monitoring Traffic Statistics Procedure
Refer to Figure 12.17.
1. Open the Physical Resources workspace.

2. Expand external communications sequence.
3. Expand traffic statistics.
4. Select the traffic core from the operational RLU to monitor.
5. In the view pane select ATM/MPEG/IP depending on the RLSS configuration.
Step 1 Step 2 Step 5
Step 3 Step 4
Figure 12.17 Traffic Monitoring Example
The operator can change the statistics refresh interval (default is 5 seconds) and a
new update interval can be configured by entering an appropriate value in the refresh
interval field.
The statistics can be reset the statistics by selecting Reset from the Control drop-
down list. Refer to Figure 12.18.

RLSS Unit
Figure 12.18 Configuring Traffic Statistics Example
12.6 Updating RLSS License File
The RLSS Capability licensing file can be updated on-line to ensure seamless opera-
tion as the additional capabilities are enabled. The user hub_user has sufficient rights
to perform the following procedure.
Procedure
1. In C:/Rlss/Management, rename the previous license.cfg to license_date.cfg

2. Copy the new license file supplied from SpaceBridge into the same directory
3. On the Administration node and Main tab of the Physical workspace, fill the
filename field with license.cfg and then click on the submit button (pencil icon)
4. To apply the new license file to the RLSS, click on the Read License Control
submit button.
Figure 12.19 Updating RLSS Licence File Example
12.7 SED and FTE Updates

RLSS Unit
12.7.1 Satellite Ephemeris Data (SED) Update
Satellite Ephemeris Data is accessible through the RMI Satellite workspace. It

provides the position of the satellite, expressed in x, y and z coordinates and corre-
sponding timestamp. SED data is sent to the SIT over the FL signalling and is used by
the SIT to position its CSC burst in the correct Time Slot. SED must be kept current,
otherwise new SITs may not be able to login because of inaccurate timing
The following SED modes are available:
• File: The file can contain up to 1440 entries (x, y, z and UTC) in an RLSS
predefined format.
• Buffer: Buffer Mode is automatically entered if the SED file no longer contains
data points for the current date. In buffer mode, SED values come from the
RLSS buffer. This buffer contains the last 24 hours of valid SED values used
by the RLSS.
• Operator: The SED values used are those that are manually entered by the
operator.
Figure 12.20 SED Using File Mode Example

RLSS Unit
Note: It is a simple text file. As indicated the first line is optional and
would point to the next file to be used.
Figure 12.21 SED File Format Example
12.7.2 Frequency Translation Error (FTE)
Frequency Translation Error (FTE) is accessible through the RMI Satellite work-
space. FTE values are used by the Receive Chain to adjust the carrier frequency off-
set to compensate for the introduced frequency error. It is used to ensure that the RL
frequency error is:
≤ ± 1% of RL symbol rate
The following modes are available:
• File: (rarely used since the offset variation cannot be easily predicted). An
example of the FTE file is given below.

RLSS Unit
• Buffer: Buffer Mode is automatically entered if the FTE file no longer contains
data points for the current date. In buffer mode, FTE values come from the
RLSS buffer. This buffer contains the last 24 hours of valid FTE values used
by the RLS.
• Operator: The SED values used are those that are manually entered by the
operator.
Figure 12.22 FTE Update using Operator Mode Example
Figure 12.23 FTE File Format Example

RLSS Unit
12.8 Terminal Monitoring
The Terminals workspace is automatically configured by the NMS. This work-

space is therefore only used to monitor SIT signalling messages in real time for up to
five SITs at a time. The RMI displays these signalling messages and other information
about monitored SITs. Refer to Figure 12.24.
Figure 12.24 Terminals Workspace Example
To enable monitoring of a given Terminal, proceed as follows:
1. First select the Terminal on left pane.

2. Then the Monitoring tab on the right pane.
3. Using the Monitored pull-down menu, select YES and click on the pencil on the
right-hand side. Refer to Figure 12.25.
4. Select the SIT Activity tab at the bottom of the right pane. The real time Return
Link messages from the selected Terminal will be displayed. Refer to Figure 12.26.

RLSS Unit
Step 2
Step 3
Step 1
Step 4
Figure 12.25 Enabling the Monitoring Example
Figure 12.26 Terminal Real Time Monitoring Example

RLSS Unit
The Monitoring facility displays the following Return Link bursts: CSC, ACQ and
SYNC. The first two are only present during the initial acquisition of the Terminal while
the SYNC is transmitted every 0.848 seconds (i.e., every 32 frames) as long as the
Terminal remains logged-on. The following information is provided for the received
burst:
• MAC Address
• Frame number
• Area ID
• Slot number
• Type of burst received (CSC, ACQ or SYNC)
• Burst position in NCR Ticks
• Frequency offset from nominal one in Hz
• Relative Received Power in%
• Es/No in dB
• Request Type and Request Value
• M&C Message
• MODCOD Requested by the Terminal (ACM only)
• Forward Link CNI reported by the Terminal (ACM only)

RLSS Unit
12.9 Other RMI Workspaces
The Physical Resources, Terminals and Satellite workspaces were described in

the previous sections. This section covers the Forward and Return Link workspaces
that are automatically configured by the NMS and the Frame Definition workspace
which is reserved for SpaceBridge usage only. These workspaces shall be used for
information only.
12.9.1 Forward Link Workspace
The Forward Link workspace contains the Forward Link logical resources, Trans-
port Streams, Services, RCS Map Table (RMT), Multicast mapping Table (MMT) and
Network Information Table (NIT).
The RLSS generates all the Forward Link signalling information required by the
Terminals and the IPE is therefore only used to encapsulate the IP traffic and multi-
plex it with the signalling from the RLSS. Refer to Figure 12.27.
Figure 12.27 Forward Link Workspace View

Example (CCM configuration)

RLSS Unit
Figure 12.28 shows the Forward Link workspace for an ACM configuration con-
taining four MODCODs. Also notice the additional streams (TMST) that is used to sig-
nal to the Terminals which MODCODs are supported by the Hub.
Figure 12.28 Forward Link Workspace View

Example (ACM configuration)

RLSS Unit
12.9.2 Return Link Workspace
The Return Link workspace contains Return Link logical resources, Frames,
Areas and Segments. Figure 12.29 shows an example of Return Link workspace con-
taining two Superframes.
Figure 12.29 Return Link Workspace View Example

RLSS Unit
12.9.3 Frame Definitions Workspace
The Frame Definitions workspace is reserved for SpaceBridge usage and it con-
tains information about Frame Types, Carrier Types and Time Slot types supported by
the RLSS.
Figure 12.30 Frame Definitions Workspace View Example

RLSS Unit
12.10 RLSS Configuration Backup
The RLSS configuration is stored in an internal Database (XML format). The data-
base contains the following information:
• Hardware, logical and physical resources

• All operational parameters
• Notification log
Advisory
SpaceBridge suggests as part of best practices, before doing any upgrading,
that Network Operators should have backup copies of their current system
software (s), operational profile(s) and configuration setup(s). This will
insure that should any system issues arise, the Network Operators can
always revert their system back to a known compatible state.
12.11 Shutting Down the RLSS
Procedure:
1. Refer to RLSS Configuration Backup/Restore Procedures (Coming in a future

release)
2. Unplug the unit.

Chapter 13 FLS Unit
13.1 General
Sub Modules
FLS Model Part Number See
IPE Modulator ACM LIM
FLS-100 16A-500001-100 Figure 13.1 Incl Incl N/A N/A
FLS-100A 16A-500001-300 Figure 13.2 Incl Incl Incl N/A
FLS-150 16A-500001-150 Figure 13.3 Incl Incl N/A Incl
FLS-150A 16A-500001-350 Figure 13.4 Incl Incl Incl Incl
Table 13.1 FLS Model Overview
Tx Out
IPE MOD
L-Band
ALARM
Ethernet
ASI In 1 ASI
M&C
ASI In 2 RS232
ASI M&C
OUT
RS422
ASI no connect
In 3
no connect
ASI
In 4
FLS-100
IN 1 OUT 1
Console
ACM
Ethernet
KEY:
External Unit

FLS Unit
Tx Out
IPE MOD
L-Band
ALARM
Ethernet
ASI In 1 ASI
M&C
ASI In 2 RS232
ASI M&C
OUT
RS422
ASI no connect
ASI
In 3
no connect
ASI
In 4
IN 1 OUT 1
Console
ACM
Ethernet
FLS-100A

FLS Unit
Rx out
To LNB
(L-Band)
1PPS
Tx Out
IPE MOD
L-Band
ALARM
Ethernet
ASI In 1 ASI
M&C
ASI In 2 RS232
ASI M&C
OUT
RS422
no connect
ASI
In 3
ASI
In 4
FLS-150
IN 1 OUT 1
Console
ACM
Ethernet
KEY:
External Unit

FLS Unit
Rx out
To LNB
(L-Band)
1PPS
Tx Out
IPE MOD
L-Band
ALARM
Ethernet
ASI In 1 ASI
M&C
ASI In 2 RS232
ASI M&C
OUT
RS422
no connect
ASI ASI
In 3
no connect
ASI
In 4
IN 1 OUT 1
Console
ACM
Ethernet
FLS-150A

FLS Unit
13.2 FLS Front Panel
LED Meaning
ASI In 1 Green when ASI signal is present
ASI In 2 Green when ASI signal is present
IPE Alarm Red if not Ethernet cable connected
Transmit Alarm Currently not used
Timing Alarm Ref if 10MHz/ 1PPS signal not present
TX 10MHz Ref Currently not used
Transmit On Green when modulator output is enabled
Table 13.2 FLSS Front Panel LED’s
Figure 13.5 FLS Front Panels

FLS Unit
13.3 FLS Rear Panels
13.3.1 FLS-100 Rear Panel
Row Connector Function

Top ASI Out ASI Output (used in ACM systems)
Top ASI In 1 IPE ASI Input 1
Top Console IPE Serial Port
Top 10/100/1000 Base T Ethernet port 1 -4 for IPE
Top Rx Out (L-Band) Not used
Top 10 MHz In 10 MHz Input
Top TO LNB Not Used
Top Tx Out Tx Out (L-Band) Modulator Output
Top 100-220 VAC Input Power
Bottom 10/100 B-T Modulator Management Ethernet port
Bottom M&C EIA-232 Modulator serial port
Bottom 1 PPS In 1 PPS Input
Bottom ASI In 3 Not Used
Bottom ASI In 4 ASI Input 4 (used with External ACM systems)
Bottom M&C EIA-422 Not used
Bottom M&C Alarm FLS-100 Summary Alarm
Bottom Chassis Ground Chassis Ground
Table 13.3 FLS-100 Rear Panel Connectors
Note: Connector information is from left to right as per Table 13.3

Figure 13.6 FLS-100 Rear Panel

FLS Unit
13.3.2 FLS-100A Rear Panel

Top IPS ASI In 1 IPE ASI Input 1
Top IPE ASI In 2 IPE ASI Input 2
Top TO LNB Not Used
Top 10/100 Base T Ethernet port for ACM
Top Console ACM Serial Port
Top Tx Out (L-Band) Modulator Output
Bottom M&C Alarm FLS-100A Summary Alarm
Table 13.4 FLS-100A Rear Panel Connectors

Figure 13.7 FLS-100A Rear Panel

FLS Unit
13.3.3 FLS-150 Rear Panel

Top ASI Out ASI Output (used in ACM systems)
Top Tx Out Tx Out (L-Band) Modulator Output
Bottom ASI In 4 ASI Input 4 (used with External ACM systems)
Bottom M&C Alarm FLS-150 Summary Alarm
Table 13.5 FLS-150 Rear Panel Connectors
Figure 13.8 FLS-150 Rear Panel

FLS Unit
13.3.4 FLS-150A Rear Panel

Top IPS ASI In 1 IPE ASI Input 1
Top IPE ASI In 2 IPE ASI Input 2
Top Rx Out (L-Band) Return Link output connected to the RLSS
Top TO LNB Return Link input connected to the LNB
Top 10/100 Base T Ethernet port for ACM
Top Console ACM Serial Port
Top Tx Out (L-Band) Modulator Output
Bottom M&C Alarm FLS-150A Summary Alarm
Table 13.6 FLS-150A Rear Panel Connectors
Figure 13.9 FLS-150A Rear Panel

FLS Unit
13.4 FLS IP Addressing
For remote access to the FLS unit, refer to the table below.
Unit IP Address Applies to

FLS (Modulator section) 10.10.40.131 All versions of FLS
FLS (IPE section) 192.168.254.111 All versions of FLS
FLS (ACM section) 10.10.40.145 FLS-100A & FLS-150A only
Table 13.7 FLS IP Address
13.5 FLS User Accounts
WARNING
NETWORK OPERATORS ARE ADVISED THAT THE USER NAME AND
PASSWORD PROVIDED BELOW ARE FOR INFORMATION ONLY. IT IS
RECOMMENDED THAT ALL MODIFICATIONS TO THE SYSTEM
SHOULD BE DONE VIA Chapter 9 "NMS Configuration" WHEN EVER
POSSIBLE.
IN THE EVENT THAT YOU MUST ACCESS THIS UNIT VIA THE USER ID
AND PASSWORD SHOWN BELOW, IT SHOULD BE DONE BY
QUALIFIED PERSONNEL ONLY.
Used for Account Name Default Password Applies to

Modulator section root adminop All versions of FLS
See note 2 See note 2
IPE section satnet satnet All versions of FLS
ACM section satnet satnet FLS-100A & FLS-150A only
Table 13.8 FLS User Accounts

entered as shown.
Note 2. Network Operators can access the Modulator via the IMS server’s
pre configured web browser.
• If you have not already logged into the IMS, refer to Chapter
7.3.3, “Logging in to the IMS Server” on page 76
• If you have already logged into the IMS, open Firefox and
select the Modulator bookmark.

FLS Unit
13.6 Additional FLS Security
Numerous commands in the FLS modulator have additional user ID and password
protection. Examples of this would be Uploading profiles, changing power levels etc.
Default User ID: sbt75

Default password: sbt75
Figure 13.10 Typical FLS Modulator Security Window
13.7 FLS Configuration Backup
13.7.1 FLS Modem Configuration Backup
Advisory
13.7.2 FLS IPE Configuration Backup
Advisory

FLS Unit
13.7.3 FLS ACM Configuration Backup
Advisory
13.8 Shutting Down the FLS
Procedure:
1. Refer to “FLS (Modulator) Configuration Backup/Restore Procedures” (Coming in

a future release)
2. Refer to “FLS (IPE) Configuration Backup/Restore Procedures” (Coming in a
future release)
3. Unplug the unit.

Chapter 14 IPS Unit
14.1 General
The IPS-100 has three main functions:
• Layer 3 Router.
• Provide 10 MHz / 1 PPS to various components of the Discovery (FLS-100,
Rear I/O and MIF).
• Act as NTP server for the RLSS and FLS-100 (modulator).
14.2 IPS Front Panel
LED Meaning
L2 I/F 0 Activity Flashing yellow to show activity on the port
10MHz/1PPS Lock Green when10 Mhz and 1 PPS signals present
Minor Alarm Yellow to indicate high temperature
Major Alarm Red to indicate very high temperature
Table 14.1 IPS Front Panel LED’s
Figure 14.1 IPS-100 Front Panel

IPS Unit
14.3 IPS Rear Panel

Top 10 MHz Out 1 10 MHz output
Top 1 PPS Out 1 1 PPS output
Top 1 PPS Input 1 PPS Input
Top RS-232 Console Serial port
Top GigE I/F 2 Ethernet port 2
Top 10 MHz In 10 MHz input
Bottom GigE switched ports 1-4 Ethernet ports 0
Bottom Alarm I/F Not Used
Bottom GigE I/F 3 Ethernet port 3
Table 14.2 IPS Rear Panel Connectors
Figure 14.2 IPS-100 Rear Panel

IPS Unit
14.4 IPS IP Addressing
For remote access to the IPS unit, refer to the table below.
IP Address
10.10.40.1
Table 14.3 IPS IP Address
14.5 IPS User Accounts
WARNING
POSSIBLE.

satnet satnet
Table 14.4 IPS User Accounts

Note: The user names and passwords are case sensitive and should be
entered as shown.

IPS Unit
14.6 IPS Configuration Backup
Advisory
14.7 Shutting Down the IPS
Procedure:
1. Refer to “IPS Configuration Backup/Restore Procedures” (Coming in a future

release)
2. Unplug the unit.

Chapter 15 IDU (Legacy)
15.1 IDU User Accounts
WARNING
POSSIBLE.
AND PASSWORD SHOWN BELOW, IT SHOULD ONLY BE DONE BY
QUALIFIED PERSONNEL.
IDU Series S4xxx, S5xxx, S6xxx

superuser su001pwd
installer ins001pwd
satnetwork sat001pwd
Table 15.1 IDU User Accounts

entered as shown.
15.2 Adding IDU’s

To add IDU’s to your network, network operators should proceed as follows:
1. See the Warning in Chapter 15.1, “IDU User Accounts” on page 317.
2. Add your IDU to the network using NMS. See Chapter 9.5, “Managing your SIT’s”
on page 103.
Note: Make sure that the MAC address is properly entered in NMS.
3. Have the installer complete the IDU installation as required.

IDU (Legacy)
15.3 Accessing IDU’s
In order to access any IDU, the following must be known:
• The IDU must be logged in and in a ready state.

• The IDU’s OAM IP address.
15.3.1 Confirming your IDU’s Availability
1. Network Operators can validate the IDU availability via the IMS server’s pre
configured web browser.
b. If you have already logged into the IMS, open Firefox and select the NMS
bookmark and log in to the NMS application. Refer to Chapter 8.3, "Starting the
NMS Application" on page 79.
2. Validate the IDU availability from the NMS by selecting:
Navigation Bar: Operations → Sit Monitoring and Control
3. In the resulting workspace, the IDU’s will be displayed along with their “State”.
Make sure the IDU you wish to get access to is showing up as “Traffic Ready” in
the State column.
4. Click on the Mac Address of the desired IDU. From the resulting page, note down
the OAM IP address shown in the work space area.
15.3.2 Connecting to the IDU
Using the OAM IP address from above, open a web browser window and connect to
the IDU using the applicable user ID and password as shown in Table 15.1 above.
15.4 Using S4xxx, S5xxx or S6xxx Model IDU’s
15.4.1 Multicast Settings
Connect to the applicable IDU using the “satnetwork” user ID and the procedures
shown in Chapter 15.3, "Accessing IDU’s".
15.4.1.1 Forward Link Multicast
Enabling this feature allows a SIT to transmit Multicast traffic that can be received at
the Hub and by the other SITs.

IDU (Legacy)
To set the Forward Links multicast, proceed as follows:
Satnetworks menu page links panel: Satellite Forward Link
Refer to Figure 15.1 and do the following:
1. Scroll down until you see the Forward Link Settings.

2. From the Forward Link Enable Multicast Enable Flag drop down box, set it to
enabled.
3. Click on the Save Forward Link Configuration button.
Figure 15.1 Forward Link Multicast IDU Settings Example
15.4.1.2 Return Link Multicast
Note: The Forward Link Multicast must first be created. The previously
defined Multicast programs are used.
To set the Return Links multicast, proceed as follows:
Satnetworks menu page links panel: Satellite Return Link
1. Scroll down until you see the Return Link Multicast Source Support settings.
2. From the RL Multicast Source Enable Flag drop down box, set it to enabled.

IDU (Legacy)
3. Set the IP address and mask and click on the Save Return Link Configuration
button.
Note: The IDU cannot receive the Multicast program it transmits
Note: Address(s) shown are for example only and can vary.
Figure 15.2 Return Link Multicast IDU Settings
15.4.2 ACM Configuration -SIT
Connect to the applicable IDU using the “satnetwork” user ID and the procedures
Note: IDU series 4120, 5120 or 6120 are required for ACM.
To set the ACM configuration for your IDU, proceed as follows:
Satnetworks menu page links panel: Satellite Forward Link Setting
15.4.2.1 Setting the IDU for ACM Operation
Referring to Figure 15.3, proceed as follows:
1. From the Default Coding Rate drop down box, set it to Auto Rate Setting.

IDU (Legacy)
Figure 15.3 IDU Forward Link Default Coding Rate Setting Example

IDU (Legacy)
15.4.2.2 Setting the IDU’s ACM MODCODs
At the bottom of the same page, enter the threshold values corresponding to each
modulation/coding rate that you have. It is recommended to enter 3 or 4 entries into
the threshold table.
For example:
1. Referring to Figure 15.4, then

a. To Add a new entry, click on the Create a New MODCOD CNI Threshold
Table Entry button.
b. To view any table entry, click and select via the ACM CNI Threshold Table
Selection Entry pick box.

IDU (Legacy)
Figure 15.4 Create an ACM MODCOD Threshold Entry Example
2. Click on the resulting Return to previous page button.

3. Refresh your browser window (typically Ctrl + R).
4. Select the desired ACM MODCOD from the ACM MODCOD drop down box. This
examples assumes MODCOD=1/2.
5. Enter the ACM CNI Threshold value (refer to the table at the bottom of the screen
for suggested minimum values. In this example, the value was 0.6 dB)
6. Set the ACM MODCOD CNI Threshold status to Active.
7. Click on the Save the ACM MODCOD CNI Threshold Table Entry button.

IDU (Legacy)
Note: Values shown in these tables will vary depending on the IDU model
you are connected to.
Figure 15.5 Setting the ACM MODCOD Threshold Entry # 1

Values Example

IDU (Legacy)
8. Repeat the process as required by either:

• Adding in additional Threshold table entries by clicking on the Create a
New MODCOD CNI Threshold Table Entry button and following steps 2
thru 7 above while referring to Figure 15.6.
• Deleting the currently selected entry by clicking on the Delete this ACM
MODCOD CNI Threshold Table Entry button.
Figure 15.6 ACM Configuration Entry #2 Menu
Once done the IDU ACM configuration steps, please confirm that you are consistent
with the MODCODS that you have defined in Chapter 9.7.2, "Service Provider For-
ward Link Service Level Agreement (SP FL SLA) Updating or Adding" on page 125.

IDU (Legacy)
15.4.3 IPsec Configuration in IDU’s (Optional)
The SITs must have a V at the end of their model name i.e: S4120V
Note: The “V” implies that the encryption chip is present
Requirements to consider:
• To create your IPsec Configuration you need to define;

• IPsec Server
• IP Address
• IPsec Re-key Time-out (in sec)
• Dead Peer Detection (DPD)
• Timer for inactivity from remote peer
• Timer between DPD retransmissions
• Number of DPD retransmissions
• Pre-Shared Key download via the Key.dat file
• Pre-configured ISAKMP Policy (Main Mode)
• Encryption: 3DES, AES 256
• Hashing: MD5 (one way hashing algorithm that produces a 128-bit hash)
• Authentication: Pre-Shared Key (PSK) for the remote peer
• Diffie-Hellman Group 1, Group 2 (method to establish a shared key over
an insecure medium)
• Default lifetime to 24 hours
• Pre-configured IPsec Policy (Quick Mode)
• ESP Tunnel mode
• Default Lifetime to 8 hours (28800 sec)
• IP Filters
• Define the subnets in the tunnels
• Mapped to a Queue
• Queue
• Encrypted or not, if encrypted, mapped to a pre-defined IPsec Server

IDU (Legacy)
15.4.3.1 IPsec Server Configuration
Connect to the applicable IDU using the superuser user ID and the procedures
Note: IDU series 4120V, 5120V or 6120V are required for IPsec operation.
To set the IPsec configuration for your IDU, proceed as follows:
Superuser menu page links panel: IPsec Configuration
1. Enter the IP address of the IPsec peer server.
Note: The IPsec Rekey Timeout (Lifetime) should be set to 28,800 sec (8
hours)
Figure 15.7 IPsec Configuration Peer Address Example

IDU (Legacy)
2. Enter the Network Configuration for IPsec
Superuser menu page links panel: Network Configuration
Figure 15.8 IPsec Configuration Network Address Example

IDU (Legacy)
15.4.3.2 IP Filters and Queues Configuration Example
Figure 15.9 IP Filters and Queues Configuration Example

IDU (Legacy)
15.4.3.2.1 IP Filter #1 Example (for OAM)
Superuser menu page links panel: Queue Management
Note: Address(s) shown are for example only and can vary. Please
Figure 15.10 IP Filter #1 Example (for OAM)

IDU (Legacy)
15.4.3.2.2 Queue #1 Example (for OAM)
Scroll to the bottom of the screen
See
Note
Note: This particular IDU used in this example capable of IPSec, but
it is not used for this Queue example.
Figure 15.11 Queue #1 Example (for OAM)

IDU (Legacy)
15.4.3.2.3 IP Filter #2 Example (for encrypted data)
Figure 15.12 IP Filter #2 Example (for encrypted data)

IDU (Legacy)
15.4.3.2.4 Queue #2 Example (for encrypted data)
See
Note
Figure 15.13 Queue #2 Example (for encrypted data)

IDU (Legacy)
15.4.3.2.5 IP Filter #3 Example (for VoIP)
Figure 15.14 IP Filter #3 Example (for VoIP)

IDU (Legacy)
15.4.3.2.6 Queue #3 Example (for VoIP)
See
Note
Figure 15.15 Queue #3 Example (for VoIP)

IDU (Legacy)
15.4.3.3 IPsec Pre-Shared Key
1. Set the configuration of IMS FTP Server as shown in Figure 15.16.
Superuser menu page links panel: File Management
Figure 15.16 IMS FTP Server Example
2. Scroll down the page and press the Download Key.dat button to download the
key.dat file
3. Reboot the SIT (default Key = “AAAAAAAAAAAAAAAA”) using the Reboot IDU
button. Refer to Figure 15.17.
Figure 15.17 Downloading IPsec Key.dat Example

IDU (Legacy)
15.4.3.4 MIB Objects
Satnetwork menu page links panel: MIB Trap
Note: There are 11 Entries listed (based on a VoIP example)
Figure 15.18 MIB Traps Example
MIB Entry Entry Object ID Status

1 PrimaryCM 1.3.6.1.4.1.2696.2.1.1.3.4.1 Active
Table 15.2 MIB Trap Destination OID’s Example

IDU (Legacy)
15.4.3.5 MIB Policies
Satnetwork menu page links panel: MIB Access Policy
If a non-redundant NMS then 10.10.40.125
Figure 15.19 MIB Policy Example

Chapter 16 IDU (Current)
16.1 IDU User Accounts
WARNING
POSSIBLE.
AND PASSWORD SHOWN BELOW, IT SHOULD ONLY BE DONE BY
QUALIFIED PERSONNEL.
IDU Series VR7xxx

superuser su001pwd
Table 16.1 IDU User Accounts

entered as shown.
16.2 Adding IDU’s

To add IDU’s to your network, network operators should proceed as follows:
1. See the Warning in Chapter 16.1, “IDU User Accounts” on page 339.
2. Add your IDU to the network using NMS. See Chapter 9.5, “Managing your SIT’s”
on page 103.
Note: Make sure that the MAC address is properly entered in NMS.
3. Have the installer complete the IDU installation as required.

IDU (Current)
16.3 Accessing IDU’s
In order to access any IDU, the following must be known:
• The IDU must be logged in and in a ready state.

• The IDU’s OAM IP address.
16.3.1 Confirming your IDU’s Availability
1. Network Operators can validate the IDU availability via the IMS server’s pre
configured web browser.
bookmark and log in to the NMS application. Refer to Chapter 8.3, "Starting the
NMS Application" on page 79.
2. Validate the IDU availability from the NMS by selecting:
Navigation Bar: Operations → Sit Monitoring and Control
3. In the resulting workspace, the IDU’s will be displayed along with their “State”.
Make sure the IDU you wish to get access to is showing up as “Traffic Ready” in
the State column.
4. Click on the Mac Address of the desired IDU. From the resulting page, note down
the OAM IP address shown in the work space area.
16.3.2 Connecting to the IDU
Using the OAM IP address from above, open a web browser window and connect to
the IDU using the applicable user ID and password as shown in Table 16.1 above.

IDU (Current)
16.4 Using S7xxx Model IDU’s
16.4.1 Multicast Settings
Connect to the applicable IDU using the “superuser” user ID and the procedures
16.4.1.1 Forward Link Multicast
Enabling this feature allows a SIT to receive Multicast traffic.
To set the Forward Link multicast:
Procedure
Navigation Bar: Configuration → Satellite Forward Link
1. Scroll down until you see the Forward Link settings.

2. From the Forward Link Enable Multicast Enable Flag drop down box, set it to
enabled.
3. Click on the Save Forward Link Configuration button.
Figure 16.1 Forward Link Multicast IDU Settings Example

IDU (Current)
16.4.1.2 Return Link Multicast
Note: The Return Link Multicast must first be created. The previously defined
Multicast programs are used.
To set the Return Link multicast, multicast:
Procedure
Navigation Bar: Configuration → Satellite Return Link
1. Scroll down until you see the Return Link Multicast Source Support settings.
2. From the RL Multicast Source Enable Flag drop down box, set it to enabled.
3. Set the IP address and mask and click on the Save Return Link Configuration
button.
Note: The IDU cannot receive the Multicast program it transmits
Figure 16.2 Return Link Multicast IDU Settings

IDU (Current)
16.4.2 ACM Configuration -SIT
To set the ACM configuration for your IDU:
Procedure
Navigation Bar: Configuration → Satellite Forward Link
16.4.2.1 Setting the IDU for ACM Operation
Referring to Figure 16.3, proceed as follows:
1. From the Default Coding Rate drop down box, set it to Auto Rate Setting.
Figure 16.3 IDU Forward Link Default Coding Rate Setting Example
16.4.2.2 Setting the IDU’s ACM MODCODs
At the bottom of the same page, enter the threshold values corresponding to each
modulation/coding rate that you have. It is recommended to enter 3 or 4 entries into
the threshold table.
For example:
1. Referring to Figure 16.4, then

a. To Add a new entry, click on the Create a New MODCOD CNI Threshold
Table Entry button.
b. To view any table entry, click and select via the ACM CNI Threshold Table
Selection Entry pick box.

IDU (Current)
To Add, click here
To View, select here
Figure 16.4 Create an ACM MODCOD Threshold Entry Example
2. Click on the resulting Return to previous page button.

3. Refresh your browser window (typically Ctrl + R).
4. Select the desired ACM MODCOD from the ACM MODCOD drop down box. This
examples assumes MODCOD=1/2.
5. Enter the ACM CNI Threshold value (refer to the table at the bottom of the screen
for suggested minimum values. In this example, the value was 0.6 dB)
6. Set the ACM MODCOD CNI Threshold status to Active.
7. Click on the Save the ACM MODCOD CNI Threshold Table Entry button.
Figure 16.5 Setting the ACM MODCOD Threshold Entry # 1

Values Example

IDU (Current)
8. Repeat the process as required by either:

• Adding in additional Threshold table entries by clicking on the Create a
New MODCOD CNI Threshold Table Entry button and following steps 2
thru 7 above while referring to Figure 16.6.
• Deleting the currently selected entry by clicking on the Delete this ACM
MODCOD CNI Threshold Table Entry button.
Figure 16.6 ACM Configuration Entry #2 Menu
Once done the IDU ACM configuration steps, please confirm that you are consis-
tent with the MODCODS that you have defined in Chapter 9.7.2, "Service Provider
Forward Link Service Level Agreement (SP FL SLA) Updating or Adding" on
page 125.
16.4.3 IPsec Configuration in IDU’s (Optional)
The SITs must have a V at the end of their model name i.e: S7400V
Note: The “V” implies that the encryption chip is present
Requirements to consider:
• To create your IPsec Configuration you need to define;

• IPsec Server
• IP Address
• IPsec Re-key Timeout (in sec)
• Dead Peer Detection (DPD)
• Timer for inactivity from remote peer

IDU (Current)
• Timer between DPD retransmissions

• Number of DPD retransmissions
• Pre-Shared Key download via the Key.dat file
• Pre-configured ISAKMP Policy (Main Mode)
• Authentication: Pre-Shared Key (PSK) for the remote peer
• Diffie-Hellman Group 1, Group 2 (method to establish a shared key over
an insecure medium)
• Default lifetime to 24 hours
• Pre-configured IPsec Policy (Quick Mode)
• ESP Tunnel mode
• Default Lifetime to 8 hours (28800 sec)
• IP Filters
• Define the subnets in the tunnels
• Mapped to a Queue
• Queue
• Encrypted or not, if encrypted, mapped to a pre-defined IPsec Server
16.4.3.1 IPsec Server Configuration
Note: IDU series S7000V, S7400V or S7400-MV are required for IPsec
operation.
To set the IPsec configuration for your IDU:
Procedure
Navigation Bar: Configuration→ IPsec
1. Enter the IP address of the IPsec peer server.
Note: The IPsec Rekey Timeout (Lifetime) should be set to 28,800 sec (8
hours)

IDU (Current)
Figure 16.7 IPsec Configuration Peer Address Example
2. Enter the Network Configuration for IPsec
Navigation Bar: Configuration → Network
Figure 16.8 IPsec Configuration Network Address Example

IDU (Current)
16.4.3.2 IP Filters and Queues Configuration Example
Note: IDU series S7000V or S7400V or S7400M-V are required for IPsec
operation.
Figure 16.9 IP Filters and Queues Configuration Example

IDU (Current)
16.4.3.2.1 IP Filter #1 Example (for OAM)
Procedure
Navigation Bar: Configuration → Queue
Figure 16.10 IP Filter #1 Example (for OAM)

IDU (Current)
16.4.3.2.2 Queue #1 Example (for OAM)
Procedure
See
Note
Note: The IDU used in this example is capable of IPSec, but it is not
used for this Queue example.
Figure 16.11 Queue #1 Example (for OAM)

IDU (Current)
16.4.3.2.3 IP Filter #2 Example (for encrypted data)
Procedure
Figure 16.12 IP Filter #2 Example (for encrypted data)

IDU (Current)
16.4.3.2.4 Queue #2 Example (for encrypted data)
Procedure
See
Note
operation.
Figure 16.13 Queue #2 Example (for encrypted data)

IDU (Current)
16.4.3.2.5 IP Filter #3 Example (for VoIP)
Procedure
Figure 16.14 IP Filter #3 Example (for VoIP)

IDU (Current)
16.4.3.2.6 Queue #3 Example (for VoIP)
Procedure
See
Note
operation.
Figure 16.15 Queue #3 Example (for VoIP)

IDU (Current)
16.4.3.3 IPsec Pre-Shared Key
1. Set the configuration of IMS FTP Server as shown in Figure 16.16.
Procedure
Navigation Bar: Management → File Transfer
Figure 16.16 IMS FTP Server Example
2. Scroll down the page and press the Download Key.dat button to download the
key.dat file
3. Reboot the SIT (default Key = “AAAAAAAAAAAAAAAA”) using the Reboot IDU
button. Refer to Figure 16.17.
Figure 16.17 Downloading IPsec Key.dat Example

IDU (Current)
16.4.3.4 MIB Objects
Procedure
Navigation Bar: Configuration → MIB Trap
Note: There are 11 Entries listed (based on a VoIP example)
Figure 16.18 MIB Traps Example
MIB Entry Type Object ID

1 VoIP / CCP 1.3.6.1.4.1.2696.2.1.1.3.4.1
2 VoIP / CCP 1.3.6.1.4.1.2696.2.1.1.3.4.2
3 VoIP / CCP 1.3.6.1.4.1.2696.2.1.1.4.2.1
4 VoIP / CCP 1.3.6.1.4.1.2696.2.1.1.4.2.2
5 VoIP / CCP 1.3.6.1.4.1.2696.2.1.1.4.2.3
6 VoIP / CCP 1.3.6.1.4.1.2696.2.1.1.4.2.4
7 VoIP / CCP 1.3.6.1.4.1.2696.2.1.1.4.2.5
8 VoIP / CCP 1.3.6.1.4.1.2696.2.1.1.3.4.3
9 VoIP / CCP 1.3.6.1.4.1.3937.1.1.1.5.1.2
10 VoIP / CCP 1.3.6.1.4.1.3937.1.1.1.5.1.3
11 VoIP / CCP 1.3.6.1.4.1.3937.1.1.1.5.1.4
Table 16.2 MIB Trap Destination OID’s Example

IDU (Current)
MIB Entry Type Object ID

12 A-SAT Terminal Requesting an 1.3.6.1.4.1.3937.1.2.6.1.2.1.2.7
ACM MODCOD Change
13 A-SAT Terminal Requesting 1.3.6.1.4.1.3937.1.1.1.6.8
Increase or Decrease of BW
Table 16.2 MIB Trap Destination OID’s Example (Continued)
16.4.3.5 MIB Policies
Procedure
Navigation Bar: Configuration → MIB Access Policy
If a non-redundant NMS then 10.10.40.125
Figure 16.19 MIB Policy Example

IDU (Current)

Chapter 17 QPS Server
17.1 QPS Server Front Panel
1 3 4 6 8
2 5 7 9 10 11 12
Figure 17.1 QPS Server Front Panel
Indicator Button or
Item connector Icon Description
Power-on indicator, power The power-on indicator lights when the

button system power is on. The power button
1 controls the power supply output to the
system.
NMI Button Used to troubleshoot software and device

driver errors when running certain operating
systems. This button can be pressed using
the end of a paper clip.
2
Use this button only if directed to do so by
qualified support personnel or if the
information is provided in the operating
system documentation.
Table 17.1 QPS Server Front panel Controls and Indicators

QPS Server
Indicator Button or
connector
system
3
Health indicator If the system is on, and in good health, the

indicator lights solid blue.
4
The indicator blinks amber if the system is on
or in standby, and any error exists (for
example, a failed fan or hard drive).
Hard-drive indicator The indicator blinks green to indicate hard-
drive activity.
5
Electrical indicator The indicator blinks amber if the system

experiences an electrical error (for example,
voltage out of range, or a failed power supply
or voltage regulator).
6
See the System Event Log or system
messages for the specific issue. Re-seat the
power supply by removing and reinstalling it.
If the problem persists, see Getting help.
Temperature indicator The indicator blinks amber if the system
experiences a thermal error (for example, a
temperature out of range or fan failure).
Ensure that none of the following conditions

exist:
7
• A cooling fan is removed or has failed.
• System cover, cooling shroud, EMI filler
panel, memory-module blank, or back-
filler bracket is removed.
• Ambient temperature is too high.
• External airflow is obstructed.
System status indicator Lights blue during normal system operation.
Lights amber when the system needs
attention due to a problem.
8 • See the System Event Log or system

messages for the specific issue.
• Invalid memory configurations can cause
the system to halt at startup without any
video output.
Table 17.1 QPS Server Front panel Controls and Indicators (Continued)

QPS Server
Indicator Button or
connector
indicator on the front and the back of the
system flashes until one of the buttons is
pressed again.

9
mode.

10
System service tag A slide-out label panel that allows you to

record system information such as Service
11
Tag, NIC, MAC address, and so on as per your
need.
Optical drive One slim SATA DVD-ROM drive or DVD+/-RW
12
drive.
Table 17.1 QPS Server Front panel Controls and Indicators (Continued)
17.2 QPS Server Rear Panel
1 2 3 5 6 7 8 9 10 11 12
Figure 17.2 QPS Server Rear Panel

QPS Server
Indicator Button or
connector
iDRAC7 Enterprise port Dedicated management port for the iDRAC7
(optional) Enterprise card.
1
vFlash media card slot Allows you to connect the optional vFlash
(optional) media card.
2
Serial connector Allows you to connect a serial device to the

system.
3
PCIe expansion card slot Two integrated 10/100/1000 Mbps NIC

4
connectors.
5 system.
eSATA Allows you to connect additional storage

devices.
6

7
Ethernet connectors (2) Two integrated 10/100/1000 Mbps NIC

connectors.
8
System status indicator Indicates the status of the system. Lights blue
during normal system operation. Lights
9
amber when the system needs attention due
to a problem
Table 17.2 QPS Server Rear panel Controls and Indicators

QPS Server
Indicator Button or
connector
indicator on the back flashes until one of the
buttons is pressed again.

10
mode.

11 Power supply 250 W AC power supply.
12 Retention clip Secures the power cable.
Table 17.2 QPS Server Rear panel Controls and Indicators (Continued)
17.3 QPS IP Addressing
For remote access to the QPS unit, refer to the table below.
Note: Address(s) shown are for example only and can vary. Please refer to
your project specific Discovery IP Topology.
IP Address
10.10.40.107
Table 17.3 Remote Access QPS IP Address

QPS Server
17.4 QPS User Accounts
WARNING
POSSIBLE.
Advisory
The QPS Server contains two users user accounts.
1. The QPS Server Web Page
2. The QPS Console or SSH.

Item
QPS Server Web Page admin satnet
QPS console or SSH root satnet
Table 17.4 Qos User Accounts

entered as shown.
17.5 Accessing the QPS Server
1. Network Operators can access the QPS via a remote desktop session on the IMS
server.
a. If you have not already logged into the IMS, refer to Chapter 7.3.3, "Logging in
to the IMS Server" on page 76.
b. Select the QPS shortcut in Firefox.
c. Enter the user ID and password and click OK button.

QPS Server
17.6 QPS Server Configuration Backup
The QPS Server configuration is supplied from the NMS.
Advisory
17.7 Shutting Down the QPS Server
Refer to Chapter 6.2.1, “Closing the QPS Server” on page 70.

QPS Server

Chapter 18 Witness Sit (Option)
18.1 General
Typically, the witness sit can be any of the following:
• S5120 IDU
• S6120 IDU
• S7400 IDU
18.2 Witness Sit IP Addressing

For remote access to the Witness Sit unit, refer to the table below.
Note: Address(s) shown are for example only and can vary. Please refer to
your project specific Discovery IP Topology.
IP Address
10.10.40.31
Table 18.1 Remote Access Witness Sit IP Address
18.3 Witness Sit User Accounts
Please refer to the applicable Witness Sit Users manual shown in “Reference Docu-
ments” on page 5

Witness Sit (Option)

WaveSwitch (Optional)
Chapter 19 WaveSwitch (Optional)
Information
Users should take note that your HUB must contain at least quantity one
SCPC receiver. If your HUB does not contain any, please contact
SpaceBridge customer service for information on obtaining applicable
hardware (SCPC receivers, cabling, etc) and HUB configuration procedures.
19.1 WaveSwitch Overview
19.1.1 WaveSwitch Concept
Due to the fact that satellite segments are extremely expensive, and also the link
quality over satellite depends on various factors, two vectors have always been the
main concerns and targets for satellite service providers and users.
First, getting the most possible throughput of the satellite bandwidth, second, hav-
ing stable link in order not to degrade traffic quality.
WaveSwitch is the solution to answer this requirement by developing the following

algorithms and mechanisms:
• Dynamic traffic-aware waveform selection and switch over.

• Interactive reuse of the same frequency span over satellite for all waveforms and
carriers and avoid reserving frequency bands.
• Deploying more elaborated SLAs over what described in DVB-RCS standard.
This is achieved by hiring following techniques:
• ASCPC (Dynamic SCPC on the MF-TDMA carrier), it helps to switch the

guaranteed bitrate on the fly.
• Switch over between RCS, ASCPC and SCPC dynamically and stepwise.
• Bandwidth request based on total traffic volume.
• Bandwidth request based on specific application(s) traffic amount.
• Bandwidth Assignment according to hourly/daily/weekly schedule.
• Using a shared pool of frequency for all 3 waveforms (RCS/ASCPC/SCPC)
• Priority in ASCPC and SCPC waveforms.
• Central mechanism to decide about waveform selection.
• Central mechanism to manage the shared bandwidth pool.

19.1.2 WaveSwitch Solution
WaveSwitch is a mechanism to handle variation of bandwidth needs, in order to

achieve an interactive and efficient bandwidth assignment as well as serving clients
based on their real time request and priority.
The major aim is assigning traffic-aware CIR Capacity on return link to SITs, when
they require more bandwidth than their current/usual RCS capacity, with the best pos-
sible quality and cost by choosing the most appropriate waveform, Priority consider-
ation and bandwidth pool consideration (congestion management).
This extra bandwidth assignment is done in two levels; first level is for smaller
requests, which is handled just by assigning fixed slots of MF-TDMA carrier to the SIT,
this waveform is called ASCPC. The second level is true SCPC based on DVB-S2
standard.it is considered for larger amounts of traffic requests.
To make the system capable of assigning bandwidth intelligently, the Priority con-
cept is introduced, so with prioritizing SITs and assigning bandwidth based on that pri-
oritization, the operator can utilize the available bandwidth to the maximum, and the
intelligent management system can handle congestion in the shared pool.
This bandwidth assignment can be performed manually or it can be decided intel-

ligently by the system. The intelligent bandwidth assignment is done by the use of trig-
gers like input traffic, type of traffic (Application), schedule etc.
WaveSwitch benefits from a modular design, and these blocks are shown in the
following schematic.

Figure 19.1 WaveSwitch Modular Design Schematic

19.1.3 Gradual Bandwidth Adjustment – Threshold margins
Regardless of waveform selection, the assigned bitrate can increase or decrease

repeatedly based on the SIT or application request. This flexibility to change bitrates
will not result in frequent peaks and instability. Therefore there are some complex
mechanisms used, that are designed to prevent jitters, peaks and unwanted rate
changes, but are easy to use.
All these margins and parameters are configurable to fit different types of net-
works and requirements, please refer to Chapter 19.2, “WaveSwitch Configuration”
on page 372
19.1.4 WaveSwitch Benefit highlights:
• Unlike single waveform platforms, WaveSwitch combines the three waveforms for
maximum adaptation to dynamic application requirements.
• Because the waveform is selected according to traffic density and traffic type
awareness, the overall efficiency is considerably improved.
• WaveSwitch dynamically allocates Bandwidth from a single shared Bandwidth
pool for the highest efficiency.
19.2 WaveSwitch Configuration
19.2.1 General
19.2.1.1 Assumptions:
• Your Discovery Hub is fully operational, with DVB-S2 Forward Link (CCM or ACM)
and DVB-RCS Return Link.
• The WaveSwitch SIT is properly configured to successfully acquire the FL and RL.
The state of the WaveSwitch SIT should be Traffic Ready as reported on the
VSAT M&C page. This ensures that routing is correctly configured and that the
NMS can configure this WaveSwitch SIT.
Information
DVB-RCS only and WaveSwitch SIT(s) can co-exist on the same Hub

19.2.1.2 Example
1. Below is an example of VSAT M&C showing DVB-RCS only and WaveSwitch SITs
in DVB-RCS Return Link mode.
to the IMS Server” on page 76
bookmark.
c. If you have not already logged into the NMS, refer to Chapter 8.3, “Starting the
NMS Application” on page 79
2. Access SIT monitoring from the NMS by:
Procedure
Navigation Bar: Monitoring→ VSAT M&C
Figure 19.2 VSAT M&C Example

19.2.2 SCPC Receiver
SCPC Receiver configuration specific for WaveSwitch Operation
To ensure that the SCPC Receiver can be configured by the NMS, ensure that the
Gateway for the default destination is the appropriate VLAN (refer to the customer
specific configuration)
Procedure
1. Login into the SCPC Receiver and select the Routing Management menu.
2. Confirm that the SCPC Receiver has connectivity with the IMS by pinging its IP
address and opening its Web page from the IMS.
Figure 19.3 SCPC Receiver Configuration Example Part 1
3. MIB Access Policy and MIB trap also need to be configured as shown in

OAM IP
address of
transmitting
SIT is
automatically
configured by
the NMS
Figure 19.4 SCPC Receiver Configuration Example

Part 2 (MIB Access Policy)

Figure 19.5 SCPC Receiver Configuration Example

Part 2 (MIB Trap)

19.2.3 NMS
19.2.3.1 System Configuration
19.2.3.1.1 SCPC Receiver
Procedure
Navigation Bar: Configuration→ Hub Configuration
1. In the Tree pane, select SCPC (refer to Figure 19.6). The result is similar to
Figure 19.7.
Figure 19.6 SCPC Receiver Page Example Part 1
Figure 19.7 SCPC Receiver Page Example Part 2

19.2.3.1.1.1 SCPC Receiver (Updating or Adding)
Procedure
Navigation Bar: Configuration→ Hub Configuration
1. To update any SCPC receiver, in the Tree pane;

a. Expand Baseband
b. Then expand RLS
c. Then expand and select the desired SCPC receiver (refer to Figure 19.8). The
result is similar to Figure 19.9. Apply the desired changes and click on the
Update button.
2. To add a new SCPC receiver, in the Tree pane;
a. Expand Baseband
b. Then expand RLS
a. Select triangle to the right of SCPC in the Tree pane and left click on the Add
SCPC button (refer to Figure 19.10). The results will be similar to Figure 19.11
and Table 19.1. Apply the desired changes and click on the Add button.
WARNING
USERS SHOULD ONLY SELECT SPACEBRIDGE S6040 SCPC
RECEIVER. WAVESWITCH WILL NOT WORK WITH SPACEBRIDGE
AMT-34 / TCC-200.
Figure 19.8 SCPC Receiver Updating Example Part 1

Figure 19.9 SCPC Receiver Updating Example Part 2
Field Description
General Parameters
Name The name that identifies the SCPC Receiver
SCPC Receiver Type Select the SCPC receiver form the pull down list.
Management IP Enter the IP address for the first receiver.
Address (carrier 1) Note: There are two receivers in each physical SCPC receiver
Management IP Enter the IP address for the second receiver.
Address (carrier 2) Note: There are two receivers in each physical SCPC receiver
Automatic Apply a check mark for the NMS to automatically configure the SCPC
Configuration
SNMP Parameters
SNMP Port Enter SNMP Port number
Get Community Enter the GET Community name (default is “public”)
Name
Set Community Enter the SET Community name (default is “private”)
Name
Table 19.1 SCPC Fields

Figure 19.10 SCPC Receiver Adding Example Part 1
Figure 19.11 SCPC Receiver Adding Example Part 2

19.2.3.1.1.2 Deleting an SCPC Receiver
Procedure
1. To delete an SCPC receiver, in the Tree pane;

a. Expand Baseband
b. Then expand RLS
c. Then expand SCPC
a. Select triangle to the right of the desired SCPC receiver in the Tree pane and
left click on the Delete SCPC button (refer to Figure 19.12).
Figure 19.12 SCPC Receiver Deleting Example
19.2.3.1.2 Example SCPC Receiver Configuration
Below is an example of SCPC Receiver configuration.
Enter the following information:
a. Name: Enter a name for this receiver

b. SCPC Receiver Type: SpaceBridge S6040
c. Management IP Addresses: S6040 has two demodulators, with separate IP
address for each demodulator.
d. Automatic Configuration: Check the check box for the demodulators to be
automatically configured by the NMS.
e. SNMP Parameters: Set as shown to allow the NMS to configure the
demodulators.
Note: Confirm that the SCPC Receiver has connectivity with the IMS by
pinging its IP address.

19.2.3.2 Frequency Bands
• FL frequency band remains untouched.

• Two RL Frequency bands must be created, Fix band and Variable band.
• Fix band hosts all the RCS Superframes which stays untouched and are not
eliminated by WaveSwitch mechanism. The Superframes in the Fix band also
hosts the SITs belonging to the eliminated RCS Superframes
• The Variable Band hosts all the RCS Superframes which could be eliminated
by WaveSwitch mechanism in case the some bandwidth is required. It also
hosts the automatically created SCPC carriers.
To add, update or delete frequency bands, refer to Chapter 9.8.2, “Frequency Bands”
on page 139.
19.2.3.2.1 Example of a Fixed Frequency Band.
1. Name: Provide a name for this fixed Frequency Band

2. Frequency Display Choice: Uplink
3. Uplink Start Frequency: Start of the band in Uplink Frequency
4. Uplink End Frequency: End of the band in Uplink Frequency
5. Satellite Translation Offset: The Frequency translation imposed by the satellite
6. Enable WaveSwitch for this band: Leave Unchecked
7. SCPC are with Pilots: Leave Unchecked
8. SCPC use Short Frames: Leave Unchecked
9. Satellite: Choose the Satellite name from the list (In case of Multi-satellite
operation)
10. RL Beam: RL on Sat said satellite.
11. FL Beam: Leave empty

Figure 19.13 Fixed Frequency Band Example
19.2.3.2.2 Example of a Variable Frequency Band.
1. Name: Provide a name for this variable Frequency Band

2. Frequency Display Choice: Uplink
3. Uplink Start Frequency: Start of the band in Uplink Frequency
4. Uplink End Frequency: End of the band in Uplink Frequency
5. Satellite Translation Offset: The Frequency translation imposed by the satellite
6. Enable WaveSwitch for this band: Checked
7. SCPC are with Pilots: Checked if Pilot is desired.
8. SCPC Use Short Frames: Unchecked if normal -frame is desired, Checked if short
frame is desired.
9. Satellite: Choose the Satellite name from the list (In case of Multi-satellite
operation)
10. RL Beam: RL on Sat said satellite.
11. FL Beam: Leave empty

Figure 19.14 Variable Frequency Band Example
Information
General RL band can coexist with Fix and Variable Bands. No operation from
WaveSwitch is performed on General band so there is no interference.

19.2.3.3 Superframes
19.2.3.3.1 Fixed RCS Superframes
One or multiple Superframes can be defined in the Fix RL band.
To add, update or delete superframes, refer to Chapter 9.8.5.1, “Superframe (DVB-

RCS)” on page 166.
19.2.3.3.2 Example of a Fixed RCS Superframe
1. Name: Enter a name for this superframe

2. ID: Choose a unique ID number for the Superframe
3. Burst Type: Different encapsulation methods are available, Select ATM1, ATM2 or
MPEG
4. Coding Type: Turbo
5. Carrier Spacing: Choose between 1.5, 1.25 and 1.2
6. Frame Type: Select the desired Carrier set
7. RLSS Name: Select the desired RLSS
8. MCD: In the case of Multiple MCDs, choose the desired MCD that belongs to the
Operational RLU if the RLSS is redundant.
9. Creating Simple RL & SLA: Checked
• To configure RL and SLA manually, please refer to
• Chapter 9.8.5, “Return Link Configuration” on page 166
• Chapter 9.7.3, “Service Group Forward Link Service Level Agreement (SG
FL SLA) Updating or Adding” on page 129
10. WaveSwitch Orientation: Fixed RCS
11. Service Provider: You must select the desired Service Provider.
12. Transport stream ID: You must select the desired Transport stream.
13. Frequency Band: Leave it as is (Fix RL Band)
14. Down Conversion: Insert the overall down conversion (Satellite translation + Down
conversion in Hz)

Figure 19.15 Fixed RCS Superframes Example
Information
Multiple Superframes can be defined in the Fix RL Band, as long as the
Frequency band has some room.

19.2.3.3.3 Variable RCS Superframes
• One or multiple Superframes can be defined in the Variable RL band.

• For better efficiency, it is recommended to define only one carrier in the Variable
Superframe.
• To add, update or delete superframes, refer to Chapter 9.8.5.1, “Superframe
(DVB-RCS)” on page 166.
19.2.3.3.4 Example of a Variable RCS Superframe
1. Name: Enter a name for this superframe

2. ID: Choose a unique ID number for the Superframe
3. Burst Type: Different encapsulation methods are available, Select ATM1, ATM2 or
MPEG
4. Coding Type: Turbo
5. Carrier Spacing: Choose between 1.5, 1.25 and 1.2
6. Frame Type: Select the desired Carrier set
7. RLSS Name: Select the desired RLSS
8. MCD: In the case of Multiple MCDs, choose the desired MCD that belongs to the
Operational RLU if the RLSS is redundant.
9. Creating Simple RL & SLA: Checked
• To configure RL and SLA manually, please refer to
• Chapter 9.8.5, “Return Link Configuration” on page 166
• Chapter 9.7.3, “Service Group Forward Link Service Level Agreement (SG
FL SLA) Updating or Adding” on page 129
10. WaveSwitch Orientation: Grayed out (Var RCS/SCPC)
11. Service Provider: You must select the desired Service Provider.
12. Transport stream ID: You must select the desired Transport stream.
13. Frequency Band: Leave it as is (Variable RL Band)
14. Down Conversion: Insert the overall down conversion (Satellite translation + Down
conversion in Hz)

Figure 19.16 Variable RCS Superframes Example
Information
Multiple Superframes can be defined in the Variable RL Band, as long as the
Frequency band has some room. Some free capacity can be reserved at the
end of the frequency band as well.
19.2.3.4 Frequency Band Components Showing the entire Satellite span (RL
& FL)
To view frequency band components, refer to Chapter 9.8.3, “Viewing Frequency

Band Components” on page 146.

Figure 19.17 Frequency Band Components Example

Information
Regarding Group definition there is no difference between WaveSwitch and
Regular Superframes. Therefore, a regular group can be linked to the SP RL
SLAs belonging to Fix or Variable Superframes. Refer to Chapter 9.7.3,
“Service Group Forward Link Service Level Agreement (SG FL SLA)
Updating or Adding” on page 129
19.2.3.5 VSAT Configuration
There is a separate section in the SIT configuration page for WaveSwitch, the rest of
the configuration is identical to a regular SIT.
It is assumed that the SIT has already been added to the NMS.
To define a SIT, please refer to Chapter 9.5, “Managing your SIT’s” on page 103
19.2.3.5.1 Example of a VSAT Configuration
Procedure
1. WaveSwitch Enabled: The compatible SIT Model must be selected first in order to
be able to enable the WaveSwitch configuration. and By checking the box,
WaveSwitch is enabled for the SIT
2. ASCPC Enabled: If Checked, ASCPC is enabled for the SIT. It means that NMS
could assign extra capacity by ASCPC waveform to the SIT.
3. SCPC Enabled: If Checked, SCPC is enabled for the SIT. It means that NMS could
assign extra capacity by SCPC waveform to the SIT.
4. ASCPC/SCPC Threshold: This number is the Maximum amount that can be
assigned to the SIT by ASCPC Waveform. This number must be equal or lesser
than the carrier size. The default Value is the carrier size.
5. Max Bit Rate: This number is the Maximum amount that can be assigned to the
SIT by any waveform (ASCPC or SCPC).
6. Logon CRA: Informational, shows the original RCS CRA capacity that SIT carrier
when enters the network.
7. SIT Max Power: Informational, shows the Maximum possible transmission power
of the SIT before saturating the BUC
8. Priority: Defines SIT Priority. The priority functions in ASCPC and SCPC.
• Priority 1 = High, 2 = Normal, 3 = Low

9. Current Bit Rate: Informational, Demonstrates the present bitrate of the SIT,
regardless of the waveform. The bit rate could have been provided by RCS,
ASCPC or SCPC.
19.2.4 SIT’s
19.2.4.1 MIB Configuration of the WaveSwitch SIT
For details on how to access your SIT please refer to the applicable IDU user’s man-
ual. For assistance, see reference document “Reference Documents” on page 5.
19.2.4.1.1 MIB Traps
For correct WaveSwitch functionality regarding Volume and Application based

triggers, two MIB Traps have to be configured.
The example below assumes that these traps have yet to be set. (refer to
Figure 19.18)
1. Login into the SIT and select the MIB Trap menu.
2. In the MIB TRAP FLAGS section, confirm that
• the General Trap Flag is set to Enabled
• the Reboot Status Trap Flag: leave as is
• If required, click on the Save MIB Traps Flags button
a. Click on the Create a new Trap Table Entry button, then click on Return To
Previous Page button and refresh the page.
b. Select the new Entry and enter the following Information:
• Trap Destination Entity: PrimaryCM
• Trap Destination Object ID: 1.3.6.1.4.1.3937.1.2.6.1.2.1.2.7
• Hint: SIT requesting Forward Link ACM MODCOD change while
transmitting in SCPC
• Trap Destination Status: Active
c. Click on the Save this MIB Trap Table Entry button to complete the
configuration
d. Again, click on the Create a new Trap Table Entry button, then click on Return
To Previous Page button and refresh the page.
e. Select the new Entry and enter the following Information:
• Trap Destination Entity: PrimaryCM
• Trap Destination Object ID: 1.3.6.1.4.1.3937.1.1.1.6.8
• Hint: SIT requesting increase or decrease of bandwidth
• Trap Destination Status: Active

f. Click on the Save this MIB Trap Table Entry button to complete the
configuration.
Figure 19.18 WaveSwitch MIB Trap Examples

19.2.4.1.2 MIB Access Policy
The example below assumes that this policy have yet to be set. (refer to Figure 19.19)
1. Login into the SIT and select the MIB Access Policy menu.
2. In the MIB ACCESS POLICY section, confirm that
• MIB ACCESS POLICY Usage Flag is set to Disabled
• Hint: This makes the MIB Private Enterprise Number irrelevant
3. Under the ACCESS POLICY TABLE section, one Entry needs to be created. The
Access Policy – IP Address is the address of the NMS.
The other parameters are shown in Figure 19.19. The Access Policy – Management
Entity Name must be the same as the Trap Destination – Entity configured for the MIB
Trap
Information
The ACCESS VIEW RIGHTS TABLE section is not used.

See Note 2
Note 1. Address(s) shown above are for example only and can
vary. Please refer to your project specific Discovery IP
Topology.
Note 2. in the case of a redundant IMS, the Virtual IP address

must be used.
Figure 19.19 WaveSwitch MIB Access Policy Examples

19.2.4.2 WaveSwitch Configuration Page
The example below assumes that this has yet to be set. (refer to Figure 19.20)
1. Login into the SIT and select the WaveSwitch Triggers menu.
Definition of Parameters
a. WaveSwitch: Enabled (By disabling, Volume and Application triggers stop

working)
b. WaveSwitch Triggers: Select Volume or Application Trigger (If Application
Trigger is selected, the configuration of the next section must be followed after).
c. Extra Bandwidth Assignment: By defining some extra bandwidth assignment,
each time that the SIT requests for specific amount of bitrate, the assigned
bitrate will be the actual rate plus this amount. This gives some margin to the
SIT. It can be set to 0 if it is not desired, the maximum amount is equal to the
RCS carrier size.
d. Request Upper limit: To avoid multiple switch over, operator can define a margin
for switching to higher bitrate. This margin can be defined between 100% to
200% of the current rate. For example if the current rate is 1 Mbps, and the
upper limit margin is set to 150%, SIT will not switch over unless it requires
more than 1.5 Mbps.
e. Request Lower limit: To avoid multiple switch over, operator can define a margin
for switching to lower bitrate. This margin can be defined between 0% to 100%
of the current rate. For example if the current rate is 1 Mbps, and the Lower limit
margin is set to 50%, SIT will not switch over unless it requires less than 0.5
Mbps.
f. Average Incoming Data Rate Interval: The operator can decide to make the
average based on the input rate or application rate between 1 second to 1800
seconds. Therefore, if the immediate switch over is required, WaveSwitch can
react and assign bandwidth every second. However, for some bursts or not
stable traffic patterns, the traffic can be monitored and averaged for maximum
half an hour and then the decision is made.
g. WaveSwitch Triggers No Response Timeout: The range is 1 to 120 seconds,
the default value is 3. If by any reason the WaveSwitch request by SIT is not
answered, the SIT stops sending a new request for X seconds, which X is the
value of this field.
h. WaveSwitch Switch over Sleep Time: Operator can configure some sleep time
(be-tween 0 to 1800 seconds) to the WaveSwitch mechanism to avoid frequent
switch overs. Therefore, after the switch over SIT will not request for any new
rate until the sleep time is finished.
i. Max ASAT bit rate: This value is the Maximum bitrate that SIT is allowed to
request for.
In order to save the configuration, click on Save WaveSwitch Triggers Configura-

tion button

Figure 19.20 WaveSwitch Triggers Example
19.2.4.3 Application based trigger – Filter/Queue Configuration
The example below assumes that this has yet to be set. (refer to Figure 19.20)
1. Login into the SIT and select the Queue menu.

2. Create a Filter pattern with desired classification parameters. To do so please refer
to the SIT’s User manual.
3. Application Trigger: Enabled.
4. Filter Pattern Status: Active
5. Click on Save This Filter Pattern Table Entry button
Example: In Figure 19.21, the traffic is from source IP 192.168.100.250. If it is Voice

over IP, (VoIP protocol with DSCP 0xb8) is filtered and measured by “Application Trig-
ger” mechanism. Eventually the WaveSwitch Bandwidth Assignment is performed if
this stream needs some extra capacity.

Note: More than one Filter pattern can be selected for Application Base
WaveSwitch. Therefore, the SIT requests for the total amount of traffic
from all the selected filter pattern streams.
Figure 19.21 Application Based Trigger Filter/Queue Example

19.2.5 Manual Switch
19.2.5.1 Manual Switchover
The Manual WaveSwitch bandwidth assignment is accessible in two ways
1. Via the tree pane:

• Expand VSAT Terminal Groups
• Then expand the applicable Service Provider Name
• Then expand the applicable Group Name
• Then to the right of the desired SIT name, right click on the triangle and select
WaveSwitch Controls
Figure 19.22 Manual Switch Over Access Example Part 1

• Expand VSAT Terminal Groups
• Then expand the applicable Service Provider Name
• Then expand the applicable Group Name

• Then select the applicable SIT Name

• In the view pane, scroll to the bottom and select the Operations menu button
Figure 19.23 Manual Switch Over Access Example Part 2
a. Stay On Manual Trigger tab

b. Insert the desired Bit Rate
c. Click on Assign Bit Rate button
Figure 19.24 Manual Switch Over Example

19.2.5.2 Manual Switchback
1. Access the WaveSwitch controls as described in Chapter 19.2.4, “SIT’s” on

page 391
2. Click on the Switch to RCS button. (refer to Figure 19.24)
19.2.6 Scheduled WaveSwitch Events
19.2.6.1 Scheduled WaveSwitch Events (Adding)
The Scheduled WaveSwitch bandwidth assignment is accessible in two ways
1. Access the WaveSwitch controls as described in Chapter 19.2.4, “SIT’s” on

page 391
2. Select the Schedule tab (refer to Figure 19.25
3. Click on the ADD event button. (refer to Figure 19.25)
Figure 19.25 Schedule Events Example
4. Enter the following information: (refer to Figure 19.26)

a. Repeat check box:
• for a one time event, leave unchecked

• for a repeat event, check the check box

• Select days that event is repeating in. If Every day is selected, the
event repeats every day
b. Data Rate: Insert desired Data Rate
c. Start Date and Time: Set the start date and time of the event
d. End Date and Time: Set the end date and time of the event
Note: Repeat days only appear if you have selected the Repeat check box.
Figure 19.26 Add Schedule Events Example
19.2.6.2 Scheduled WaveSwitch Events (Deleting)
The Manual WaveSwitch bandwidth assignment is accessible in two ways

• Select WaveSwitch Scheduled Events (refer to Figure 19.27)

• Select the desired Event

• Click on Delete Event button (refer to Figure 19.28)
Figure 19.27 Delete Schedule Events Example Part 1

Figure 19.28 Delete Schedule Events Example Part 2
Information
By deleting an ongoing scheduled WaveSwitch event, the SIT will release
the capacity and will go back to Original RCS state.

19.3 WaveSwitch Monitoring
19.3.1 WaveSwitch SIT Status
Procedure
1. In the tree pane, click on VSAT Terminal Groups (refer to Figure 19.29)
2. In the view pane, click on the WaveSwitch Tab (refer to Figure 19.30)
Figure 19.29 WaveSwitch Monitoring Example Part 1

Figure 19.30 WaveSwitch Monitoring Example Part 2

19.3.2 WaveSwitch Events
Procedure
1. In the tree pane, click on WaveSwitch Events (refer to Figure 19.31)

2. In the view pane, click on the WaveSwitch Tab (refer to Figure 19.32)


19.3.3 Checking Successful Changeover
Procedure
1. In the tree pane, click on VSAT Terminal Groups (refer to Figure 19.29)
2. In the view pane; (refer to Figure 19.33)
• The WaveSwitch SIT State should be:
• Traffic Ready In case NMS uses ASCPC to assign extra Bitrate,
• SCPC Traffic Ready in case NMS uses SCPC to assign it.
• In case the SCPC waveform is used by NMS
• The assigned SCPC receiver channel should be Locked and
configured according to the requested parameters.
• To see which waveform is used, please refer to Chapter 19.3.1,
“WaveSwitch SIT Status” on page 404. To see which SCPC receiver
channel is assigned, please refer to Chapter 19.3.2, “WaveSwitch
Events” on page 406 (WaveSwitch events/SCPC Info)
• At the IMS, ping the OAM IP address of the WaveSwitch SIT
• Check end-to-end connectivity:
• At the WaveSwitch SIT Host PC, ping the IP address of the Gateway Host
• Perform an FTP Transfer between the WaveSwitch SIT Host and the
Gateway Host equipped with an FTP server.

Figure 19.33 WaveSwitch State Example Part 1

Figure 19.34 WaveSwitch State Example Part 2

Chapter 20 KVM (Option)
20.1 General
Our KVM option (1RU) allows network operators to have direct access to the Discov-
ery hub without the need of any additional laptop computers.
Figure 20.1 KVM Unit
20.2 KVM Power Up Access
On initial power up of the KVM module, users must enter the following password
to gain access to the unit.
KVM Password: 00000000 (i.e: eight zeros)

KVM (Option)
Hardware
Key Lock No
Audio No
Display Size 17in
Panel Type Active Matrix TFT LCD
KVM Ports 1
PC Interface USB
PC Video Type VGA
Performance
Brightness 250 cd/m²
Contrast Ratio 1000:1
Pixel Pitch Support 0.264 x 0.264 mm
Response Time 5ms
Viewing Angle 170° (H), 160° (V)
IP Control No
Maximum Analog Resolutions 1280x1024 @ 60Hz
Aspect Ratio Standard (4:3)
Color Depth 24-bit, 16.7M colors (Truecolor)
MTBF 60,000 Hours
Environmental
Operating Temperature 0 ~ 50 °C / 32 ~ 122 °F
Storage Temperature -20 ~ 60 °C / -4 ~ 140 °F
Humidity 90% RH
Packaging Information
Shipping (Package) Weight 39.6 lb. [17.9 kg]
Table 20.1 KVM Details

Appendix A Glossary
A
AC
Alternating Current
C
CSA
Canadian Standards Association
F
FCC
Federal Communications Commission
H
HTTP
Hypertext Transfer Protocol
U
UL
Underwriters Laboratories
V
VAC
Volts AC

414 Discovery Product Manual RevisionProduct Manual
Technical Specifications
Appendix B Technical Specifications
B.1 Power & Environmental Specifications
Environmental Specifications Discovery HUB [P/N]

Dimensions Height: Varies (depends on which options are selected)
Width: 533.4mm (21") (internally, standard 19” inch rack mount)
Depth: varies as per options selected
• 609.6mm (24 inch) approx (not including door if so equipped)
• 801.1mm (31.5 inch) approx (not including door if so equipped)
Clearance Height:
Requirements • Depends on which options are selected
• Add minimum of 150mm (6 inch)
• Possibility of top mounted ventilation exhaust fans (varies as per options selected)
Width: Add minimum of 150mm (6 inch)
Depth: varies as per options selected
• If no rear door equipped, then Add minimum of 150mm (6 inch)
• If rear door equipped, then Add minimum of 635mm (25 inch)
Power AC: Auto sensing 100/250 VAC, 50/60 Hz
Power Cord: 6 ft. with NEMA 5-15P connector
Connector varies depending on country
Typical Power Dissipation: 500 watts
Environmental Operating Temperature: 0°C to 35°C (32°F to 95°F)
Storage Temperature: -25°C to 85°C (-13°F to 185°F)
Relative Humidity:
• Operating: up to 90% non-condensing, operating; up to 95% non-condensing
• Non-Operating: 5-100%
Altitude:
• Operating: Up to 10,000 ft. (3,045 m)
• Non-Operating: -120 to 40,000 ft. (12,180 m) during transit
Shock, Non-Operational: Withstand 2.3 G’s sinusoidal shock, any axis, with 20.0 millisecond
duration
Weight:
• Varies as per options selected (shipping crate extra)
Table B.1 Power & Environmental Specifications

B.2 Connector Pin Outs and Specifications
B.2.1 RF Port Connectors
Specification
Parameter
(see Note)
Connector N type, female
Impedance 50 ohms
Frequency Range 950-1450MHz
Input Power Range -45 dBm +/- 20 dB
Total Power for all Carriers -21 dBm (-108 dBm/Hz)
Signal DVB-RCS
Return Loss > 16 dB
Table B.2 RX RF Port Electrical Specifications

Note: The RX n ports are connected to the LNA/LNB output(s) and all the RX
ports are identical.
Specification
Parameter (See note)
Connector N type, female
Impedance 50 ohms
Frequency Range 950-1450MHz
Output Power Range 0 to -40 dBm
Signal DVB-S, DVB-S2
Return Loss > 12 dB
Table B.3 TX RF Port Electrical Specifications

Note: The TX n ports are connected to the SSPA/HPA input(s) and all the TX
ports are identical.

B.2.2 RJ-45 Ethernet Connector
Note 1. The connectors on the unit are Female.
Note 2. The connector shown below is for the mating cable (Male)
Figure B.1 RJ-45 (10/100/1000T) Ethernet Connector Rear View
Pin Number Function

1 RX_D1+
2 RX_D1-
3 TX_D2+
4 BI_D3+
5 BI_D3-
6 TX_D2-
7 BI_D4+
8 BI_D4-
Table B.4 RJ-45 (10/100/1000T) Ethernet Connector Pin Allocation
Parameter Specification
Connector RJ-45 receptacle
Cabling Un shielded Twisted Pair (UTP), category 5
Electrical 10BASE-T, 100BASE-T or 1000BASE-T with
auto-negotiation
IP Datagram Encapsulation IEEE 802.2/802.3 RFC 1042
Network Layer IP v4 (RFC 791)
Table B.5 Ethernet Ports Electrical Specifications

B.3 Hub Versions& Physical Specifications
Information
• For actual Part numbers, please contact your SpaceBridge sales office
• For RLSS, you need one MCD card per Forward Link.
• Basic Hub’s height start at 5RU. Actual height may vary depending on number of
Forward Links and options chosen.
• Other options are possible. For details, contact your SpaceBridge sales office.
- implies not applicable S implies standard

Keying:  implies required A As required
O implies option
Units Power
Options
Qty of Forward Links
Basic Modules Optional Modules
SCPC Receiver
Example #
Cable Brush
Witness Sit
Min
RLSS-100
RLSS-200
RLSS-400
FLS-100A
FLS-150A
IF Switch
VoIP GW
Mode
FLS-100
FLS-150
Router
# Notes
IPsec
ULPC
KVM
ACM
GRE
QPS
GPS
QoS
IMS
PEP
Redundancy
IPS
RU
110V
220V
1 1 1 1 1 1 1 2 4 8 1 1 1 1 1 1 1 1 1 2 1 1 1 1
1 1 CCM 5      - O O O O O A O O O O O O O S O O 1,2,3,4
2 1 ACM 6   - -     O O O O O A O O O O O O O S O O 1,3,4
3 1 ACM 5  - -     - O O O O O A O O O O O O O S O O 1,3,4
4 2 CCM 7      - O O O O O A O O O O O O O S O O 1,2,3,4,5
5 2 ACM 8   - -     O O O O O A O O O O O O O S O O 1,3,4
6 2 ACM 7  - -     - O O O O O A O O O O O O O S O O 1,3,4
Table B.6 Discovery Hub Versions

Note 1. For RLSS Units

• RLSS-100 contains quantity 1 Processor card and quantity 1
MCD card
MCD card with space for 2 additional MCD cards.
MCD card with space for 6 additional MCD cards.
• In RLSS-400, you can alternately have 3 processor cards and
up to 5 MCD cards
• RLSS model can vary, depending on number of FL required.
Note 2. For FLS units, in CCM systems, it could be either:

• FLS-100 or FLS-150
• FLS-100A or FLS-150A and bypass the internal ACM
• If FLS-100A or FLS-150A, this allows users switching to ACM if
they show wish.
Note 3. For FLS units, in ACM systems,

• When using FLS-100 or FLS-150, you require the external
ACM unit.
• For FLS units, in ACM systems, when using FLS-100A or FLS-
150A, the ACM feature is included internally, hence you do not
need the external ACM unit.
Note 4. With respect to QoS, QPS or PEP units,

• QoS is now considered a legacy product. It has been replaced
by the QPS unit.
• PEP is now considered a legacy product. It has been replaced
by the QPS unit.
Note 5. When increasing to 2 or more Forward Links, then

• FLS-100 or FLS-100A or FLS-150 or FLS-150A (1 per FL) and
consider notes on FLS above.
• ACM (1 per FL) and consider notes on FLS above.
• PEP (1 per FL) consider notes on QoS & PEP units above.
• QoS (1/ FL), consider notes on QoS & PEP units above.
• QPS-100 (1/ FL), consider notes on QoS & PEP units above.
Note 6. For SCPC Functionality option.

• You require qty 1 SCPC capable receiver in the HUB per
remote SCPC SIT. See Chapter 19, "WaveSwitch
(Optional)" on page 369

Discovery VSAT Hub
ACM Discovery VSAT Hub
FLS-1xx ACM
IPS FLS-1xx
Note 1. Layouts shown are for example only. Your actual layout may vary from those shown
PEP IPS
MCD RLSS-100 MCD RLSS-100

POWER SUP POWER SUP
PROC PROC
IMS IMS
QoS QPS
Note 2. RLSS model can vary, depending on number of FL required.

Example # 1 (no options) Example # 1 (no options)
(Legacy) (Current)
Discovery VSAT Hub
SCPC Receiver
KVM
Discovery VSAT Hub ULPC
KVM WITNESS SIT
WITNESS SIT GPS
ACM ACM
FLS-1xx FLS-1xx
IPS IPS
PEP IPsec
IPsec GRE
Router Router

POWER SUP POWER SUP
PROC PROC
IMS IMS
QoS QPS
Example # 1 (All options) Example # 1 (All options)

(Legacy) (Current)
Figure B.2 Discovery Typical Rack Layouts Examples

(No redundancy)

Discovery VSAT Hub
ACM
FLS-1xx Discovery VSAT Hub
IPS ACM
PEP FLS-1xx
IPS
MCD RLSS-100
POWER SUP

PROC MCD RLSS-100
POWER SUP
IMS PROC
QoS IMS
IF SW QPS
ACM IF SW
FLS-1xx ACM
IPS FLS-1xx
PEP IPS

POWER SUP POWER SUP
PROC PROC
IMS IMS
QoS QPS
Example # 1 (no options) Example # 1 (no options)

(Legacy) (Current)

(With redundancy)

Discovery VSAT Hub
ACM
Discovery VSAT Hub SCPC Receiver
ACM FLS-1xx
FLS-1xx IPS
IPS IPsec
PEP GRE
IPsec Router
Router

MCD RLSS-100
POWER SUP
MCD RLSS-100 PROC
POWER SUP
PROC
IMS
IMS QPS
QoS KVM
KVM UPLC
WITNESS SIT WITNESS SIT
IF SW IF SW
ACM ACM
FLS-1xx FLS-1xx
IPS IPS
PEP IPsec
IPsec GRE
Router Router

POWER SUP POWER SUP
PROC PROC
IMS IMS
QoS QPS
Example # 1 (All options) Example # 1 (All options)
(Legacy) (Current)

(With redundancy)

Useful Linux Tips
Appendix C Useful Linux Tips
C.1 ROOT Access
Advisory
Be advised that ROOT access is required in certain instances. SpaceBridge
strongly recommends that ROOT access be done by qualified personnel
and that they exit ROOT access as soon as they have completed their
applicable task(s).
From a Gnome terminal window, proceed as follows:
1. Type: SU
2. Enter the ROOT password: asnsatnet
C.2 Terminate Running Processes
Example: In cases where a user forgot to close FIreFox, and a new user log’s into the
system.
From a Gnome terminal window, proceed as follows:
1. Type: SU
2. Enter the ROOT password: asnsatnet
3. type: killall firefox
4. Type: Exit

Useful Linux Tips

RLSS Input Format
Appendix D RLSS Input Format
D.1 Satellite Ephemeris Data (SED) File Format (sample)
Note: Text file that can contain up to 1440 entries
where - X, Y, Z Coordinates are in meters
- Time is UTC
Next_SED_File.cfg (optional)
; section key
SATELLITE UPDATES REPORT
; Number of entries
13
; X_Axis Y_Axis Z_Axis Time_UTC
-15181626 -39337947 -13047 2005:03:17:00:00:00:000
-15181690 -39337989 -13146 2005:03:17:00:05:00:000
-15181756 -39338029 -13238 2005:03:17:00:10:00:000
-15181825 -39338069 -13324 2005:03:17:00:15:00:000
-15181895 -39338107 -13404 2005:03:17:00:20:00:000
-15181967 -39338142 -13478 2005:03:17:00:25:00:000
-15182040 -39338175 -13547 2005:03:17:00:30:00:000
-15182115 -39338205 -13609 2005:03:17:00:35:00:000
-15182192 -39338233 -13666 2005:03:17:00:40:00:000
-15182270 -39338259 -13716 2005:03:17:00:45:00:000
-15182349 -39338283 -13761 2005:03:17:00:50:00:000
-15182430 -39338304 -13800 2005:03:17:00:55:00:000
-15182511 -39338323 -13833 2005:03:17:01:00:00:000

RLSS Input Format

SIT IP Addressing
Appendix E SIT IP Addressing
E.1 Router VLANS & IP Addressing
Note: ISP VLAN addresses shown in this table are used for factory testing
and need to be changed to the customer specific addresses
VLAN Name (ID) Virtual Chain 1 Chain 2

NMS (503) 10.10.40.1 10.10.40.2 10.10.40.3
ISP (501) – Note 1 192.168.5.111 192.168.5.112/114 192.168.5.113/115
Serv (505) 192.168.2.1 192.168.2.2 192.168.2.3
RLSS (504) 192.168.255.1 192.168.255.2 192.168.255.3
TRF (502) 192.168.253.1 192.168.253.2 192.168.253.3
FLSS (500) 192.168.254.1 192.168.254.2 192.168.254.3
Table E.1 Router VLANs & IP Addressing
Description Format Value

Y 8 Bits Identifies the SIT (1-254)
maximum of 254 SIT’s per network
(16 networks: i.e 16 to 31)
Z 8 Bits 2 to 254:
Defines the Hosts behind the SIT
i.e.: 256 – 2(IP) – 1 (SIT) = 253
for a maximum of 253 hosts
1: Identifies the SIT on the Ethernet
LAN
SIT Ethernet IP Address 172.16.Y.Z to 172.31.Y.Z Example: 172.16.50.1/24
Ethernet LAN: Network Z=0 Example: 172.16.50.0/24
Ethernet LAN: Directed Broadcast Z = 255 Example: 172.16.50.255/24
Ethernet LAN: Hosts Z = 2-254 Example: 172.16.50.2/24 to
172.16.50.254/24
SIT Satellite OAM IP Address 10.1.16.Y to 10.1.31.Y Example: 10.1.16.50/32
SIT Satellite Traffic IP Address (IPsec) 10.1.16.Y to 10.1.31.Y Example: 10.2.16.50/32
Table E.2 Sample Addressing scheme for Maximum 4064 SIT’s 172.16-
31.Y.Z

SIT IP Addressing

Available Hub Hardware Configurations
Appendix F Available Hub Hardware Configurations
optional
optional
Note 1. Blank panel used where optional items are not ordered
Note 2. The positions of the units in the rack may vary.
Figure F.1 Discovery 100 Series Next Generation VSAT HUB (8RU)

optional
optional
Note 1. Blank panel used where optional items are not ordered

optional
optional
optional
Note 1. Blank panel used where optional items are not ordered.
Note 2. Possibility of 8RU if some options not present.

optional
optional
optional
Note 1. Blank panel used where optional items are not ordered.
Note 2. Possibility of 8RU if some options not present.

Index
C
Connectors
Pin Allocation
Ethernet 417
CRA 222
H
Hub Installation
General Warnings and Tools
Required 55
M
MAC Address 222, 224, 226, 228, 230,
232
P
Proprietary 7
R
RBDC 223
Reference Documents 5
S
Safety
Grounding 31
Handling Procedures 30
Information Warnings & Cautions 29
Precautions 31
Standards
FCC 32
Safety Information and Standards 29
Signal 223
SIT
State 222, 223
Site Requirements 51
Basic Safety 51
Grounding 51
IDU Requirements
Power 53
Space 52
State
see State, under SIT
System Description
Overview 35
V
VBDC 223
W
Warranty
Extended Warranty Options 34
Warranty and Service 33

Index

006

PM1VD 000000 000 001 - Rev03

Uploaded by

Copyright:

Available Formats

PM1VD 000000 000 001 - Rev03

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PM1VD 000000 000 001 - Rev03

Uploaded by

Copyright:

Available Formats

Discovery

PM-1VD-000000-000 Discovery Product Manual Revision 3

4 Discovery Product Manual Revision

For more information, please refer to the following documents

Item Document Number Title

PM-1VD-000000-000 Discovery Product Manual Revision 5

Customer Support and Service

Tel: (514) 420 0045

Please visit our web site at: www.spacebridge.com

PM-1VD-000000-000 Discovery Product Manual Revision 7

Chapter 3 Site Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 4 Discovery Hub Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

PM-1VD-000000-000 Discovery Product Manual Revision 9

4.4.1.2 Installing a Local Keyboard/Mouse and Monitor (Optional) . . . . . . . . . . . . . .58

Chapter 5 IMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Chapter 6 Start-up and Shut-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Chapter 7 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Chapter 8 Introduction to the NMS Application . . . . . . . . . . . . . . . . . . . . . . .79

Chapter 9 NMS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

10 Discovery Product Manual Revision

9.2.2 PID Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

PM-1VD-000000-000 Discovery Product Manual Revision 11

9.8.4.3 PID Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

Chapter 10 NMS Monitoring & Control (M & C) . . . . . . . . . . . . . . . . . . . . . . . .219

12 Discovery Product Manual Revision

10.3.3.2 Layer 3 SCS Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Chapter 11 NMS Account Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Chapter 12 RLSS Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

PM-1VD-000000-000 Discovery Product Manual Revision 13

12.7 SED and FTE Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289

Chapter 13 FLS Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301

Chapter 14 IPS Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313

Chapter 15 IDU (Legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317

14 Discovery Product Manual Revision

15.4.1.2 Return Link Multicast. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Chapter 16 IDU (Current) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

PM-1VD-000000-000 Discovery Product Manual Revision 15

Chapter 17 QPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359

Chapter 18 Witness Sit (Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367

Chapter 19 WaveSwitch (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369

16 Discovery Product Manual Revision

19.2.4.1.2 MIB Access Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

Chapter 20 KVM (Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Appendix A Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Appendix C Useful Linux Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Appendix D RLSS Input Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Appendix E SIT IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Appendix F Available Hub Hardware Configurations . . . . . . . . . . . . . . . . . . . 429

PM-1VD-000000-000 Discovery Product Manual Revision 17

This page intentionally left blank

18 Discovery Product Manual Revision

PM-1VD-000000-000 Discovery Product Manual Revision 19

Figure 9.10 Adding A SIT Group Part 1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

20 Discovery Product Manual Revision

Figure 9.61 Updating MODCODs Example Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

PM-1VD-000000-000 Discovery Product Manual Revision 21

22 Discovery Product Manual Revision

Figure 11.11 Customer Example Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

PM-1VD-000000-000 Discovery Product Manual Revision 23