Professional Documents
Culture Documents
PM1VD 000000 000 001 - Rev03
PM1VD 000000 000 001 - Rev03
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
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
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
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.
Contact SpaceBridge for customer support and service at the following office;
Head Office
SpaceBridge
657 Orly Avenue
Dorval, Quebec
H9P 1G1
E-mail: info@spacebridge.com
Printed in Canada
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
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
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.
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
Grounding
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.
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É.
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.
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.
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.
Service
Support provided by SpaceBridge customer service include complete factory
repair for both in warranty and out of warranty equipment.
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 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
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
RLSS1
IPS1 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
J9 RF1
MGMT 1 Eth Eth MGMT 10MHz
J10
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
RX
SPLITTER
10 MHz 1 PPS MOD Ethernet ASI IN
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
RLSS2
IPS2 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
J9 RF1
MGMT 1 Eth Eth MGMT 10MHz
J10
ISP 1 Eth Eth PEP/ PROC RT-TP
ETH2 IF1TP J11
SERV 1 Eth Eth QoS ETH1 IF2TP J12
CUSTOMER ETH 1PPS J13
TRAFFIC RS232 Eth MCD
Alm SW
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*)
RLSS1
IPS1 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
J9 RF1
MGMT 1 Eth Eth MGMT 10MHz
J10
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 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
RLSS2
IPS2 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
J9 RF1
MGMT 1 Eth Eth MGMT 10MHz
J10
ISP 1 Eth Eth PEP/ PROC RT-TP
ETH2 IF1TP J11
SERV 1 Eth Eth QoS ETH1 IF2TP J12
CUSTOMER ETH 1PPS J13
TRAFFIC RS232 Eth MCD
Alm SW
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*)
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
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
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
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
8
1 2 3 4 5 6 7 9 10 11 12 13 14
8
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.
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 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)
Note 1. Actual connectors and locations within can vary, depending on your system
configuration. See your system Interconnect diagram for more details.
Note 1. Actual connectors and locations within can vary, depending on your system
configuration. See your system Interconnect diagram for more details.
RJ-45 TYPE
N TYPE 50 OHM
Note 1. Actual connectors and locations within can vary, depending on your system
configuration. See your system Interconnect diagram for more details.
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.
3.1 General
Grounding
WARNING
ALL INDOOR AND OUTDOOR GROUNDING SYSTEMS ON THE
INSTALLATION SITE MUST MEET THE REQUIREMENTS OF THE
APPLICABLE LOCAL AND NATIONAL STANDARDS.
Note 2. Do not place any objects heavier than 50Kg (110lbs) on the top of
the Hub cabinet.
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!
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
Grounding of Equipment
For grounding of the equipment, refer to Chapter 4.4.1.1, "Installing the Grounding
Cable" on page 56.
Prior to any powering up of the Discovery Hub, Network operators must acquire the
following information so they can properly configure their Discovery Hub.
4.1 Unpacking
Prior to un-crating the units, carefully inspect shipping containers for any damage
that may have occurred during shipment.
Caution
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.
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.
Depending on were you want to install your Discovery Hub, make sure to address
the following:
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.
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.
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:
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.
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.
The Discovery Hub is provided with one of the following power connectors.
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.
1 3 4 6 8
2 5 7 9 10 11 12
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.
Indicator Button or
Item Icon Description
connector
Temperature indicator The indicator blinks amber if the system
experiences a thermal error (for example, a
temperature out of range or fan failure).
Table 5.1 IMS Server Front Panel Controls and Indicators (Continued)
1 2 3 5 6 7 8 9 10 11 12
vFlash media card slot Allows you to connect the optional vFlash
(optional) media card.
2
Indicator Button or
Item Icon Description
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
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 back flashes until one of the
buttons is pressed again.
Table 5.2 IMS Server Rear Panel Controls and Indicators (Continued)
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
Power Button
Power Button
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.
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 root@10.10.40.107 <cr>
• Enter the following command: shutdown - h now <CR>
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.
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.
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.
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
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
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
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
ISP Access Customer Specific
Remote Access Customer Specific
Default IP Address
Unit Function (With mask 255.255.255.0)
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
Default IP Address
Unit Function (With mask 255.255.255.0)
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
ISP Access Customer Specific
Remote Access Customer Specific
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
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
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.
8.1 General
This chapter deals with the basic introduction to the NMS application which is
used to configure and manage your network.
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".
Access to the NMS application is done using your standard browser. Open a ses-
sion and enter the following:
Note: Address(s) shown below are for example only and can vary. Please
refer to your project specific Discovery IP Topology.
10.10.40.125 (IMS # 1)
10.10.40.225 (IMS # 2)
1. Enter the NMS application user ID and password (refer to Figure 8.1).
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.
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).
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.
Useful Tools
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).
The NMS User Interface is divided into various sections as shown in Figure 8.4.
• Tree Pane.
• View Pane
Quick
Drop down Link
Menus
Tree Pane
Refer to the figure below for a brief explanation on how the tree pane functions.
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).
Information
RF Equipment is customer specific
Figure 8.13 Typical NMS Monitoring VSAT M&C Overview Page Example
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.).
• VCC Pools
• PID Ranges
• IP Address Ranges
• RL QoS
• FL QoS
• FL QoS Rules
• FL Routes
• OAM
• Traffic
• Multicast
• SIT Software Versions
9.2.4 RL QoS
9.2.5 FL QoS
9.2.7 FL IP Routes
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
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.
Procedure
Tree Pane
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.
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.
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).
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.
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.
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).
Procedure
Tree Pane
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.
Note: IDU redundancy Specifics only appear if you have checked the IDU
redundancy Enable Box check box.
Figure 9.17 Adding a SIT Example Part 3
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.
..
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)
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.
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
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
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.
• 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
See Note
Note: RL QoS values are customer configurable. See Chapter 9.6.3, “SIT Return
Link QoS” on page 116
See Note
Note: FL QoS values are customer configurable. See Chapter 9.6.4, “Forward
Link Quality of Service Change” on page 121
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.
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.
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.
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.
Field Description
The current CRA traffic bit rate for this SIT Level RL QoS.
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.
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.
Since the SIT is still logged-in, the current values displayed are unchanged.
Note: The nominal Maximum Parameters are applicable for VoIP operation
Figure 9.27 SIT Return Link QoS Change Over Written Example
• Traffic
• OAM
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).
Note: Addresses shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
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.
Note: Addresses) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
The Overwritten values are displayed in bold on the Forward Link Routes page.
Note: Addresses shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
To return to the default Quality of Service, click on the Delete Overwritten QoS
button (refer to Figure 9.30).
Procedure
1. From the tree pane, select SLA. The result will be similar to Figure 9.32.
9.7.2 Service Provider Forward Link Service Level Agreement (SP FL SLA)
Updating or Adding
Procedure
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
9.7.3 Service Group Forward Link Service Level Agreement (SG FL SLA)
Updating or Adding
Procedure
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)
DVB-S2 PID Assignments 2
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)
DVB-S2 PID Assignments 3
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)
DVB-S2 PID Assignments 4
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)
3. Once your setting’s have been entered, click on the ADD button.
9.8.1 Overview
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
1. In the Tree pane, select Frequency Bands (refer to Figure 9.46). The result is
similar to Figure 9.47.
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.
Procedure
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.
Procedure
Procedure
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.
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.
Procedure
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)
Procedure
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.
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.
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
similar to Figure 9.62.
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.
Procedure
Procedure
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.
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
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
• 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
Figure 9.71 and Table 9.14. Apply the desired changes and click on the Update
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.
:
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.
Procedure
Procedure
1. In the Tree pane, under Satellites, select the desired satellite, then select
Frequency bands under the satellite. (refer to Figure 9.76).
Field Description
General Parameters
Name The name that identifies the Superframe.
ID The specific identification number.
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)
Procedure
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).
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
Procedure
1. In the Tree pane, under Satellites, select the desired satellite, then select
Frequency bands under the applicable satellite.
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.
.:
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)
Procedure
.:
Procedure
9.8.5.1.4 Segments
Procedure
1. In the Tree pane, under Satellites, select the desired satellite, then select
Frequency bands under the applicable satellite.
2. Then select:
• The required Frequency band
• The desired Superframe
• 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.
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.
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
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
c. Under Satellites, select the desired satellite, then select Frequency bands
under the applicable satellite.
d. Then select:
• The required Frequency band
• The desired Superframe
Procedure
Procedure
1. In the Tree pane, under Satellites, select the desired satellite, then select
Frequency Bands under the satellite. (refer to Figure 9.97).
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)
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)
Procedure
Procedure
1. In the Tree pane, under Satellites, select the desired satellite, then desired
Frequency bands under the applicable satellite.
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).
Procedure
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).
Step 1
Step 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.
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
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.
Procedure
Step 2
Step 3
Steps 4
Procedure
Note: You can tick the scale to fit check box to fit the results into your
current browsers window size
Note: You can tick the scale to fit check box to fit the results into your
current browsers window size
Procedure
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.
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
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.
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:
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.
The IP Address Ranges page displays the different ranges of IP Address made avail-
able to given Service Providers.
Procedure
Procedure
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
Procedure
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.
Procedure
1. In the Tree pane, under Definitions, select VCC Pools. (refer to Figure 9.125).
2. The result is similar to Figure 9.126.
Procedure
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
Procedure
VSAT Monitoring & Control Main can be broken down into the following sections:
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
Tabs
Stats Area
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.
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.
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).
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.
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.
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).
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
The MAC address of the SIT, which is the primary identifier for a
MAC Address
SIT.
SIT Name The name that identifies the 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.
Procedure
1. In the View Pane, select the OW QoS Tab. (refer to Figure 10.1).
2. The result is similar to Figure 10.3. and Table 10.4
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.
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.
Procedure
1. In the View Pane, select the Statistics Tab. (refer to Figure 10.1).
2. The result is similar to Figure 10.4. and Table 10.5
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.
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)
Procedure
1. In the View Pane, select the ACM Tab. (refer to Figure 10.1).
2. The result is similar to Figure 10.5. and Table 10.6
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.
FL PID Forward Link PID used by the SIT.
MODCOD Used MODCOD used by the SIT.
Efficiency Factor Bandwidth efficiency factor for this SIT.
Procedure
1. In the View Pane, select the WaveSwitch Tab. (refer to Figure 10.1).
2. The result is similar to Figure 10.6. and Table 10.7
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.
WaveSwitch Mode/ Shows whether the SIT is operating in DVB-RCS, ASAT or SCPC
Current Bit Rate along with current bit rate
(kb/s)
Procedure
1. In the View Pane, select the Sit Groups Tab. (refer to Figure 10.1).
2. The result is similar to Figure 10.6. and Table 10.8
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
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:
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.
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:
• 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:
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.5.1 Overview
This feature allows Network operators to review operation events that have occurred.
Procedure
1. In the Tree pane, select Connection Manager Events. (refer to Figure 10.8).
2. The result is similar to Figure 10.9.
You can sort these events simply by selecting any one of the column headings (selected column headings appear in yellow).
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).
2. The result is similar to Figure 10.11.
You can sort these events simply by selecting any one of the column headings (selected column headings appear in yellow).
Procedure
Procedure
1. In the Tree pane, select Equipment Monitoring Events. (refer to Figure 10.14).
2. The result is similar to Figure 10.15.
10.5.6 Command/Results
Procedure
This feature allows Network operators to review System User activity details.
Procedure
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: Any user has the ability to change his own password at will.
Procedure
1. In the Tree pane, either select Service Providers or User Accounts. (refer to
Figure 11.1).
2. The result is similar to Figure 11.2.
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).
2. The result is similar to Figure 11.4.
Procedure
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
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
WARNING
DELETING ANY SERVICE PROVIDER WILL RESULT IN THE DELETION
OF ALL USERS ASSOCIATED TO SAID SERVICE PROVIDER.
Procedure
This feature allows Network operators to enter customer information which may then
be associated with services.
Procedure
Procedure
Procedure
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
Procedure
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
Procedure
12.1 General
The RLSS is the part of a DVB-RCS gateway responsible for the Return Link. it’s
main functions are:
Reserved
LINK
Aux
ETH2 (Traffic)
P0 S1 S3 5V
P1 S0 S2 PG
RESET
CONS
ETH1
(Mgmt)
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.
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.
Note: Default RLSS User ID and password shown. Refer to Table 12.2.
Click OK
• Workspace’s.
• Tree Pane.
• View Pane.
View Pane
Tabs
Page Refresh
Controls
Editable
Field
Apply Field
Change
Drop Down
List
Tree Pane
View Pane
Figure 12.9 RLSS Main Page
Each workspace displays a subset of the RLSS database in the tree pane.
Switch
Controls
Sequence
Object
Link
Individual
Object
• 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.
• 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.
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.
Normal Core
(White background)
Alarmed Core
(Orange Background)
Color Description
White Normal/Information
Light Blue Warning
Yellow Minor Alarm
Orange Major Alarm
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.
Step 3 Step 4
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.
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
• 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.
Note: It is a simple text file. As indicated the first line is optional and
would point to the next file to be used.
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
• File: (rarely used since the offset variation cannot be easily predicted). An
example of the FTE file is given below.
• 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.
Step 2
Step 3
Step 1
Step 4
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)
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.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.
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.
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.
The RLSS configuration is stored in an internal Database (XML format). The data-
base contains the following information:
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.
Procedure:
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
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
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
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
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
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
For remote access to the FLS unit, refer to the table below.
Note: Address(s) shown below are for example only and can vary. Please
refer to your project specific Discovery IP Topology.
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.
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.
Numerous commands in the FLS modulator have additional user ID and password
protection. Examples of this would be Uploading profiles, changing power levels etc.
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.
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.
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.
Procedure:
14.1 General
• 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).
LED Meaning
L2 I/F 0 Activity Flashing yellow to show activity on the port
L3 I/F 1 Activity Flashing yellow to show activity on the port
L3 I/F 2 Activity Flashing yellow to show activity on the port
L3 I/F 3 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
For remote access to the IPS unit, refer to the table below.
Note: Address(s) shown below are for example only and can vary. Please
refer to your project specific Discovery IP Topology.
IP Address
10.10.40.1
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.
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.
Procedure:
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 ONLY BE DONE BY
QUALIFIED PERSONNEL.
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.
1. Network Operators can validate the IDU availability 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.
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:
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.
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.
Connect to the applicable IDU using the “satnetwork” user ID and the procedures
shown in Chapter 15.3, "Accessing IDU’s".
Enabling this feature allows a SIT to transmit Multicast traffic that can be received at
the Hub and by the other SITs.
Note: The Forward Link Multicast must first be created. The previously
defined Multicast programs are used.
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: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Connect to the applicable IDU using the “satnetwork” user ID and the procedures
shown in Chapter 15.3, "Accessing IDU’s".
Note: IDU series 4120, 5120 or 6120 are required for ACM.
1. From the Default Coding Rate drop down box, set it to Auto Rate Setting.
Figure 15.3 IDU Forward Link Default Coding Rate Setting Example
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:
Note: Values shown in these tables will vary depending on the IDU model
you are connected to.
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.
The SITs must have a V at the end of their model name i.e: S4120V
Requirements to consider:
Connect to the applicable IDU using the superuser user ID and the procedures
shown in Chapter 15.3, "Accessing IDU’s".
Note: IDU series 4120V, 5120V or 6120V are required for IPsec operation.
Note: The IPsec Rekey Timeout (Lifetime) should be set to 28,800 sec (8
hours)
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Figure 15.8 IPsec Configuration Network Address Example
Note: IDU series 4120V, 5120V or 6120V are required for IPsec operation.
Note: Address(s) shown are for example only and can vary. Please
refer to your project specific Discovery IP Topology.
See
Note
Note: This particular IDU used in this example capable of IPSec, but
it is not used for this Queue example.
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Figure 15.12 IP Filter #2 Example (for encrypted data)
See
Note
Note: IDU series 4120V, 5120V or 6120V are required for IPsec operation.
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Figure 15.14 IP Filter #3 Example (for VoIP)
See
Note
Note: IDU series 4120V, 5120V or 6120V are required for IPsec operation.
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
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.
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
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 ONLY BE DONE BY
QUALIFIED PERSONNEL.
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.
1. Network Operators can validate the IDU availability 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.
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:
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.
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.
Connect to the applicable IDU using the “superuser” user ID and the procedures
shown in Chapter 16.3, "Accessing IDU’s".
Procedure
Note: The Return Link Multicast must first be created. The previously defined
Multicast programs are used.
Procedure
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: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Procedure
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
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:
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.
The SITs must have a V at the end of their model name i.e: S7400V
Requirements to consider:
Note: IDU series S7000V, S7400V or S7400-MV are required for IPsec
operation.
Procedure
Note: The IPsec Rekey Timeout (Lifetime) should be set to 28,800 sec (8
hours)
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Figure 16.8 IPsec Configuration Network Address Example
Note: IDU series S7000V or S7400V or S7400M-V are required for IPsec
operation.
Procedure
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Procedure
See
Note
Note: The IDU used in this example is capable of IPSec, but it is not
used for this Queue example.
Procedure
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Figure 16.12 IP Filter #2 Example (for encrypted data)
Procedure
See
Note
Note: IDU series S7000V, S7400V or S7400-MV are required for IPsec
operation.
Figure 16.13 Queue #2 Example (for encrypted data)
Procedure
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
Procedure
See
Note
Note: IDU series S7000V, S7400V or S7400-MV are required for IPsec
operation.
Figure 16.15 Queue #3 Example (for VoIP)
Procedure
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
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.
Procedure
Procedure
Note: Address(s) shown are for example only and can vary.
Please refer to your project specific Discovery IP Topology
1 3 4 6 8
2 5 7 9 10 11 12
Indicator Button or
Item connector Icon Description
Indicator Button or
Item Icon Description
connector
Video connector Allows you to connect a VGA display to the
system
3
Table 17.1 QPS Server Front panel Controls and Indicators (Continued)
Indicator Button or
Item Icon Description
connector
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.
Table 17.1 QPS Server Front panel Controls and Indicators (Continued)
1 2 3 5 6 7 8 9 10 11 12
Indicator Button or
Item 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
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 Button or
Item Icon Description
connector
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 back flashes until one of the
buttons is pressed again.
Table 17.2 QPS Server Rear panel Controls and Indicators (Continued)
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
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.
Advisory
The QPS Server contains two users user accounts.
1. The QPS Server Web Page
2. The QPS Console or SSH.
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.
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.
18.1 General
• S5120 IDU
• S6120 IDU
• S7400 IDU
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
Please refer to the applicable Witness Sit Users manual shown in “Reference Docu-
ments” on page 5
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.
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.
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.
WaveSwitch benefits from a modular design, and these blocks are shown in the
following schematic.
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
• 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.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.
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. If you have already logged into the IMS, open Firefox and select the NMS
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
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.
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
19.2.3 NMS
Procedure
1. In the Tree pane, select SCPC (refer to Figure 19.6). The result is similar to
Figure 19.7.
Procedure
WARNING
USERS SHOULD ONLY SELECT SPACEBRIDGE S6040 SCPC
RECEIVER. WAVESWITCH WILL NOT WORK WITH SPACEBRIDGE
AMT-34 / TCC-200.
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
Procedure
Note: Confirm that the SCPC Receiver has connectivity with the IMS by
pinging its IP address.
To add, update or delete frequency bands, refer to Chapter 9.8.2, “Frequency Bands”
on page 139.
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
Information
Multiple Superframes can be defined in the Fix RL Band, as long as the
Frequency band has some room.
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)
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
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
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
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.
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.
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.
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
The example below assumes that this has yet to be set. (refer to Figure 19.20)
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.
Note: Repeat days only appear if you have selected the Repeat check box.
Information
By deleting an ongoing scheduled WaveSwitch event, the SIT will release
the capacity and will go back to Original RCS state.
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)
Procedure
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.
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.
On initial power up of the KVM module, users must enter the following password
to gain access to the unit.
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]
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
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)
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
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
Note 2. The connector shown below is for the mating cable (Male)
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)
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.
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
FLS-1xx ACM
IPS FLS-1xx
Note 1. Layouts shown are for example only. Your actual layout may vary from those shown
PEP IPS
IMS IMS
QoS QPS
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
IMS IMS
QoS QPS
Note 1. Layouts shown are for example only. Your actual layout may vary from those shown
ACM
FLS-1xx Discovery VSAT Hub
IPS ACM
PEP FLS-1xx
IPS
MCD RLSS-100
POWER SUP
QoS IMS
IF SW QPS
ACM IF SW
FLS-1xx ACM
IPS FLS-1xx
PEP IPS
IMS IMS
QoS QPS
ACM
Discovery VSAT Hub SCPC Receiver
Note 1. Layouts shown are for example only. Your actual layout may vary from those shown
ACM FLS-1xx
FLS-1xx IPS
IPS IPsec
PEP GRE
IPsec Router
Router
IMS IMS
QoS QPS
Example # 1 (All options) Example # 1 (All options)
(Legacy) (Current)
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).
1. Type: SU
2. Enter the ROOT password: asnsatnet
Example: In cases where a user forgot to close FIreFox, and a new user log’s into the
system.
1. Type: SU
2. Enter the ROOT password: asnsatnet
3. type: killall firefox
4. Type: Exit
- Time is UTC
Next_SED_File.cfg (optional)
; section key
; Number of entries
13
Note: ISP VLAN addresses shown in this table are used for factory testing
and need to be changed to the customer specific addresses
Table E.2 Sample Addressing scheme for Maximum 4064 SIT’s 172.16-
31.Y.Z
optional
optional
Note 1. Blank panel used where optional items are not ordered
Figure F.1 Discovery 100 Series Next Generation VSAT HUB (8RU)
optional
optional
Note 1. Blank panel used where optional items are not ordered
Figure F.2 Discovery 100 Series Next Generation VSAT HUB (10RU)
optional
optional
optional
Note 1. Blank panel used where optional items are not ordered.
Figure F.3 Discovery 200 Series Next Generation VSAT HUB (10RU)
optional
optional
optional
Note 1. Blank panel used where optional items are not ordered.
Figure F.4 Discovery 300 Series Next Generation VSAT HUB (13RU)
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