NMS User Guide NO P08

NetManager User Guide
Network Operator’s Manual
Document Number: 850176

Revision: P08
850176 P08
Document Number: 850176
Revision: P08
Date: 27 August 2010
Proprietary Notice: Copyright © 2010 Advantech Satellite Networks, Inc. All

rights reserved.
The information contained herein is proprietary to Advan-
tech Satellite Networks or third party proprietary information
which Advantech Satellite Networks is obligated to protect
and shall not be disclosed in whole or in part without the
prior written permission of Advantech Satellite Networks Inc.
27 August 2010 Advantech Satellite Networks Proprietary Page II

850176 P08
Table of Contents
List of Tables XI
List of Figures XV
Chapter 1. Introduction 1
1.1 Role of the NetManager Application 2
1.1.1 Overview 2
1.1.2 Features 2
1.2 NetManager Architecture 3
1.2.1 Context 3
1.2.2 Architecture 3
1.3 Operational Model 4
1.3.1 Bandwidth Assignment: SLAs 4
1.3.2 Bandwidth Usage 5
1.3.3 Resources Overview 6
1.4 Air Interfaces 8
1.4.1 DVB-RCS 8
1.4.2 Mesh Overlay 9
1.4.3 SCPC 10
Chapter 2. Overview of the NetManager Interface 11

2.1 Accessing the NetManager Application 12
2.1.1 Log in to NetManager 12
2.1.2 Access Control List 14
2.1.3 NetManager Entrance Page 14
2.2 Navigating the NetManager User Interface 15
2.2.1 Navigation Bar 16
2.2.2 Filter Drop-Down List 25
2.2.3 Workspace 26
2.2.4 Buttons 30
2.2.5 Refresh Bar 31
2.2.6 Tooltips 32
2.2.7 Expert Mode 35
27 August 2010 Advantech Satellite Networks Proprietary Page III

850176 P08
2.2.8 Quick Access Links 36

2.3 Adding, Updating and Deleting Records 37
2.3.1 Adding Records to the Database 38
2.3.2 Updating Records in the Database 38
2.3.3 Deleting Records from the Database 40
2.4 Interactive View Pages 41
2.5 Getting Help with the NetManager 43
Chapter 3. NetManager Configuration Management 45

3.1 Accessing the NetManager Database 46
3.1.1 User Categories 46
3.1.2 Managing Service Providers 47
3.2 User Management 50
3.2.1 Users View 50
3.2.2 Managing User Accounts 51
3.2.3 Monitor User Activity 56
3.2.4 Customers 58
Chapter 4. Populating Gateway Data into NetManager 61

4.1 Configuring Equipment Overview 62
4.2 Equipment View 62
4.3 RLSS Profile 64
4.4 Equipment Wizard 66
4.5 Routers 67
4.5.1 Router Automatic configuration 67
4.5.2 Routers 67
4.5.3 Adding and Updating a Router 69
4.5.4 Deleting a Router 71
4.6 Performance Enhancement Proxy 71
4.6.1 Adding and Updating a PEP 73
4.6.2 Deleting a PEP 74
4.7 QoS Device 75
4.7.1 Route-level QoS management in PacketShaper 78
4.7.2 Route-level QoS management in SatNet QoS 79
27 August 2010 Advantech Satellite Networks Proprietary Page IV

850176 P08
4.7.3 QoS Device Configuration Statistics 79

4.8 IP DVB Encapsulator Profiles 80
4.8.1 Encapsulator Configuration 80
4.8.2 IP DVB Encapsulators 82
4.8.3 Adding and Updating an IP DVB Encapsulator 84
4.8.4 Deleting an IP DVB Encapsulator 86
4.9 ACM Adaptation Units 87
4.9.1 Adding and Updating an ACM Adaptation Unit 89
4.9.2 Deleting an ACM Adaptation Unit 91
4.10 Modulators 91
4.10.1 Adding and Updating a Modulator 93
4.10.2 Deleting a Modulator 95
4.11 SCPC Receivers 95
4.11.1 Adding and Updating a SCPC Receiver 97
4.11.2 Deleting a SCPC Receiver 98
Chapter 5. Air Interface 99

5.1 Configuring Air Interface Overview 100
5.1.1 Frequency Plan Management 100
5.1.2 Air Interface View 100
5.2 Default Values 102
5.3 Frequency Plan 105
5.3.1 Viewing Frequency Bands 105
5.3.2 Viewing Frequency Band Components 109
5.3.3 Frequency Plan Activation 112
5.4 Return Link 113
5.4.1 Viewing Carrier Sets (Superframes) 113
5.4.2 Viewing Areas 118
5.4.3 RL Partitions (Segments) 123
5.5 Forward Link 127
5.5.1 Tx Mode 127
5.5.2 Transport Streams 130
27 August 2010 Advantech Satellite Networks Proprietary Page V

850176 P08
Chapter 6. Configuring Services 137

6.1 Importing RLSS Configurations 138
6.1.1 RL SLA Creation Algorithm 138
6.1.2 Performing File Import 140
6.2 Services to Service Providers 142
6.2.1 Configuring Services Overview 142
6.2.2 Forward Link Services to Service Providers 144
6.2.3 Return Link Services to Service Providers 157
6.2.4 Services to SIT Groups 178
6.2.5 Services to SITs 194
6.3 Availability Services 218
6.3.1 RFCM Configuration 218
Chapter 7. Configuring Network 221

7.1 Configuring Network Overview 222
7.2 SIT Profiles 224
7.2.1 Viewing SITs 224
7.2.2 Overwriting RL QoS 232
7.3 SIT Queues 238
7.3.1 Queue Types 238
7.3.2 Viewing Traffic Queues 239
7.4 IP Routes 247
7.4.1 Viewing IP Routes 247
7.5 SIT Control System 251
7.5.1 Automatic Creation of Multicast Routes 251
7.6 VLAN 252
7.6.1 VLAN View 252
7.6.2 VLAN Address Space 253
7.7 VLAN ISP-Side Network 256
7.8 Ranges 259
7.8.1 Viewing Service Provider IP Address Ranges 259
7.8.2 Viewing SP VCC Ranges 262
7.8.3 Viewing SP PID Ranges 265
27 August 2010 Advantech Satellite Networks Proprietary Page VI

850176 P08
7.9 Mesh 269

7.9.1 Mesh View 269
Chapter 8. Monitoring The Gateway 271

8.1 Operations Overview 272
8.2 Monitoring / Control 274
8.2.1 SIT Monitoring / Control 274
8.2.2 SIT Group Monitoring / Control 282
8.2.3 Commands 283
8.3 Configuration Commands and Results 285
8.4 IP Sec Report 288
8.5 Events and Alarms 288
8.5.1 Viewing Events 289
8.5.2 Viewing Alarms 291
8.5.3 Deleting Events and Alarms 293
8.6 SIT Group Performance Statistics 294
8.6.1 Connection Statistics 295
8.6.2 Advanced RL Login Statistics 297
8.6.3 Return Link Traffic Statistics 299
8.6.4 Return Link Advanced Traffic Statistics 301
8.6.5 Managed VoIP Call Statistics 303
8.6.6 Managed VoIP Advanced Return Link Statistics 305
8.6.7 Return Link RFCM Statistics 307
8.6.8 Conditional Return Link Connection Statistics 309
8.6.9 SIT SCPC 312
8.6.10 MPEG PID Traffic Statistics 313
8.6.11 Route MPEG Traffic Statistics 315
8.6.12 FL Partition IP Traffic Statistics 317
8.7 Statistics Graphs 318
8.7.1 Custom Graphing 318
8.7.2 Fast Graph 322
8.8 Queries 323
27 August 2010 Advantech Satellite Networks Proprietary Page VII

850176 P08
Chapter 9. General System Administration 325

9.1 System Administration 326
9.1.1 System Administration Page 326
9.1.2 Connection Manager Redundancy 331
9.2 FL QoS Rules 333
9.2.1 Viewing FL QoS Rules 333
9.2.2 Adding and Updating a FL QoS Rule 334
9.2.3 Deleting a FL QoS Rule 338
Chapter 10. Security 339

10.1 Back-up and Restore 340
10.1.1 Backup and Restore of Service Provider Data 340
10.1.2 Scheduled Backup and Restore of entire NetManager database 343
10.2 User Security Certificates 344
Chapter 11. Server Operation and Maintenance 347

11.1 About Server Operation and Maintenance 348
11.1.1 Changing the Root Password 348
11.1.2 Using X-Windows 348
11.2 Checking RAID Status 349
11.2.1 Command Line Tool 349
11.2.2 GUI Tool 351
11.3 System Backup 352
11.3.1 Making an ISO Image 352
11.4 NetManager Software Updates 355
11.4.1 From the DVD 355
11.4.2 Manual Linux SLES Update 356
Chapter 12. Troubleshooting 359

12.1 Overview of User Input Validation 360
12.2 Return Link SIT Level QoS Checks 360
12.3 SIT Group Forward Link SLA Checks 360
12.4 SIT Group Checks 361
12.4.1 Return Link 361
27 August 2010 Advantech Satellite Networks Proprietary Page VIII

850176 P08
12.4.2 Forward Link 361

12.4.3 Other Validation 362
12.5 SIT Checks 362
12.6 Overwritten RL SIT Level QoS 362
12.7 Traffic Queue Checks 363
12.8 VCC Range Checks 363
12.9 IP Address Range Checks 363
12.10 PID Range Checks 363
12.11 Service Provider Forward Link SLA Check 364
12.12 Low Level Return Link SLA Checks 364
12.13 Service Provider Checks 364
Appendix A. SSL Basics 365
Appendix B. FCAPS 367
B.1 Overview 367
B.2 Fault 367
B.3 Configuration 367
B.4 Accounting 368
B.5 Performance 368
B.6 Security 368
Appendix C. Scheduled Backups and Vaccum 369
Appendix D. Contacting Advantech Satellite Networks 371
Appendix E. Reference Documents 373
Appendix F. List of Acronyms and Terms 375
Appendix G. Glossary 377
27 August 2010 Advantech Satellite Networks Proprietary Page IX

850176 P08
27 August 2010 Advantech Satellite Networks Proprietary Page X

850176 P08
List of Tables
Table 3.1 Service Provider page fields 47

Table 3.2 Service Provider Information fields 49
Table 3.3 Default Service Provider Users fields 49
Table 3.4 Manage Users page fields 52
Table 3.5 Manage User page fields 54
Table 3.6 User Activity Log page fields 57
Table 3.7 Customer Table page fields 58
Table 3.8 Customer Property page fields 59
Table 4.1 RLSS Profile page fields 65
Table 4.2 Equipment Wizard page field 66
Table 4.3 Routers page fields 68
Table 4.4 Router page fields 70
Table 4.5 Performance Enhancement Proxies (PEPs) page fields 72
Table 4.6 Performance Enhancement Proxy page fields 74
Table 4.7 QoS Device Page fields 76
Table 4.8 QoS Device Configuration Stats fields 80
Table 4.9 Novra Structure Mapping 81
Table 4.10 IP DVB Encapsulators page fields 83
Table 4.11 IP DVB Encapsulator page fields 85
Table 4.12 ACM Adaptation Units page fields 88
Table 4.13 ACM Adaptation Unit page fields 90
Table 4.14 Modulators page fields 92
Table 4.15 Modulator page fields 94
Table 4.16 SCPC Receiver page fields 96
Table 4.17 SCPC Receiver page fields 98
Table 5.1 Default System values page fields 103
Table 5.2 Frequency Bands page fields 105
Table 5.3 Frequency Band page fields 108
Table 5.4 Frequency Band Components page fields 110
27 August 2010 Advantech Satellite Networks Proprietary Page XI

850176 P08
Table 5.5 Frequency Guard page fields 112

Table 5.6 Carrier Sets (Superframes) page fields 114
Table 5.7 Carrier Set (Superframe) page fields 116
Table 5.8 Areas page fields 118
Table 5.9 Area page fields 120
Table 5.10 RL Partitions (Segments) page fields 124
Table 5.11 Partition (Segment) page fields 125
Table 5.12 Tx Mode page fields 128
Table 5.13 Tx Mode page fields 129
Table 5.14 Transport Streams page fields in Configuration Mode 131
Table 5.15 Transport Streams page fields in PIDs Mode 132
Table 5.16 Transport Stream page fields 133
Table 6.1 SP Forward Link SLAs page fields 145
Table 6.2 SP Forward Link SLA page fields 147
Table 6.3 FL QoS Device Partitions page fields 150
Table 6.4 FL QoS Device Partition page fields 153
Table 6.5 IP Partition Classification page fields 155
Table 6.6 Service Provider Return Link SLAs page fields 159
Table 6.7 SP Return Link SLA page fields 161
Table 6.8 Low Level RL SLAs page fields (LL Definition view) 163
Table 6.9 Low Level RL SLAs page fields (Conditioning view) 165
Table 6.10 Low Level Return Link SLA page fields 167
Table 6.11 Imported RL SLA page fields 169
Table 6.12 RL SLA Conditioning page fields 173
Table 6.13 RL SLA Application page fields 177
Table 6.14 SIT Groups page fields 179
Table 6.15 SIT Group page fields 182
Table 6.16 SIT Groups FL SLAs page fields 186
Table 6.17 SIT Group Forward Link SLA fields for G FL SLA linked to a DVB-S2 
ACM Transport Stream 191
Table 6.18 SIT Group Forward Link SLA fields for SG FL SLA linked to a DVB-S 
Transport Stream 193
Table 6.19 Default SIT Return Link QoS fields 196
Table 6.20 Default SIT Return Link QoS page fields 198
Table 6.21 Default SIT Forward link QoS page fields 200
Table 6.22 Forward Link SIT Level QoS page fields 202
Table 6.23 Default SIT RL Queue Filter page fields 204
Table 6.24 Default RL SIT Queue Filter page fields 206
Table 6.25 RL QoS Scalings page fields 208
Table 6.26 RL QoS Scaling page fields 209
Table 6.27 Multicast Scheduling page fields 212
Table 6.28 Multicast Scheduling Property page fields 213
Table 6.29 Multicast Event Recurrence fields 214
Table 6.30 SIT Software Versions page fields 216
27 August 2010 Advantech Satellite Networks Proprietary Page XII

850176 P08
Table 6.31 SIT Software Version page fields 217

Table 7.1 SITs page fields 225
Table 7.2 SIT page fields 229
Table 7.3 SIT Level RL QoS page fields 234
Table 7.4 VCC Fields 241
Table 7.5 Mesh Destinations Fields 241
Table 7.6 Traffic Queue page fields 243
Table 7.7 IP Routes page fields 248
Table 7.8 IP Route page fields 249
Table 7.9 VLAN Address Spaces page fields 253
Table 7.10 VLAN Address Space page fields 255
Table 7.11 ISP-Side Network page fields 256
Table 7.12 ISP-Side Network Update page fields 258
Table 7.13 SP IP Address Ranges page fields 260
Table 7.14 IP Address Range page fields 261
Table 7.15 SP VCC Ranges page fields 263
Table 7.16 VCC Range page fields 265
Table 7.17 SP PID Ranges page fields 266
Table 7.18 PID Range page fields 268
Table 8.1 SIT Monitoring / Control summary fields 275
Table 8.2 SIT Monitoring / Control (Operations) page fields 277
Table 8.3 SIT Monitoring / Control (Configuration) page fields 279
Table 8.4 SIT Monitoring / Control (ACM) page fields 280
Table 8.5 SIT Monitoring / Control (SCPC) page fields 281
Table 8.6 SIT Group Monitoring / Control page fields 282
Table 8.7 Configuration Commands and Results page fields 287
Table 8.8 IPSec Report page columns 288
Table 8.9 Connection Manager Events page fields 290
Table 8.10 Connection Manager Alarms page fields 292
Table 8.11 Connection Statistics page fields 295
Table 8.12 Advanced RL Login Statistics page fields 297
Table 8.13 RL Traffic Statistics page fields 299
Table 8.14 RL Advanced Traffic Statistics page fields 302
Table 8.15 Managed VoIP Call Statistics page fields 304
Table 8.16 Managed VoIP Advanced RL Statistics page fields 306
Table 8.17 Return Link RFCM Statistics page fields 308
Table 8.18 Conditional Return Link Connection Statistics page fields 310
Table 8.19 SIT SCPC Statistics page fields 312
Table 8.20 FL MPEG PID Traffic Statistics page fields 313
Table 8.21 FL Route MPEG Traffic Statistics page fields 315
Table 8.22 FL Partition IP Traffic Statistics page fields 317
Table 8.23 Statistic Graph page fields 319
Table 8.24 Query parameters 323
Table 9.1 System Administration page fields 328
27 August 2010 Advantech Satellite Networks Proprietary Page XIII

850176 P08
Table 9.2 Supported CM Redundancy Scenarios 331

Table 9.3 FL QoS Rules page fields 333
Table 9.4 Fl QoS Rule Configuration page fields 336
Table 10.1 Save/Restore page fields 342
Table 10.2 Restore fields 343
Table 11.1 CD Burning packages 352
Table 11.2 Configuration Parameters for a Suse Manual Update 357
27 August 2010 Advantech Satellite Networks Proprietary Page XIV

850176 P08
List of Figures
Figure 1.1 NetManager within the Satellite Network 3

Figure 1.2 NetManager Architecture 3
Figure 1.3 Service Level Agreement View 6
Figure 1.4 Return Link Resources 7
Figure 1.5 Digital Video Broadcast-Return Channel System (DVB-RCS) 9
Figure 2.1 NetManager Welcome page 13
Figure 2.2 Log in page 13
Figure 2.3 Advantech SatNet NetManager Page 15
Figure 2.4 Typical application page 16
Figure 2.5 Network Operator Navigation Bar 16
Figure 2.6 CFG Equipment Sub-menus 17
Figure 2.7 CFG Air Interface Sub-menus 18
Figure 2.8 CFG Services Sub-menus 19
Figure 2.9 CFG Network Sub-menus 21
Figure 2.10 CFG Mgmt Sub-menus 22
Figure 2.11 Operations Sub-menus 23
Figure 2.12 User Mgmt Sub-menus 24
Figure 2.13 Service Provider Drop-Down List 25
Figure 2.14 Sample page with fields to complete 27
Figure 2.15 Grid Table 28
Figure 2.16 Initial/Default Row Ordering 29
Figure 2.17 Descending Row Ordering 29
Figure 2.18 Ascending Row Ordering 30
Figure 2.19 Action buttons 30
Figure 2.20 Example of a confirmation message 30
Figure 2.21 Example of an error message 31
Figure 2.22 Navigation Buttons 31
Figure 2.23 Refresh Bar 31
Figure 2.24 Tooltips: Current value of the field 32
27 August 2010 Advantech Satellite Networks Proprietary Page XV

850176 P08
Figure 2.25 Tooltips: Range of possible values 33

Figure 2.26 Tooltips: Short description of the SIT-Level QoS Scaling wrt Nominal field 34
Figure 2.27 Expert Mode OFF 35
Figure 2.28 Expert Mode ON 36
Figure 2.29 Quick Access Links 37
Figure 2.30 Highlighting multiple records to update 39
Figure 2.31 Highlighting records to delete 41
Figure 2.32 Example View page 42
Figure 2.33 Typical Online Help Page 43
Figure 3.1 The main Service Provider page 47
Figure 3.2 Manage Service Provider page 48
Figure 3.3 Net Manager Users View page 51
Figure 3.4 Manage Users page 52
Figure 3.5 Manage User page 53
Figure 3.6 User Activity Log page 56
Figure 3.7 Customer Table page 58
Figure 3.8 Customer Property page 59
Figure 4.1 Equipment View page 62
Figure 4.2 CFG Equipment Sub-menus 63
Figure 4.3 RLSS Profile page 64
Figure 4.4 Equipment Wizard page 66
Figure 4.5 Routers page 67
Figure 4.6 Router page 69
Figure 4.7 Performance Enhancement Proxies (PEPs) page 71
Figure 4.8 Performance Enhancement Proxy page 73
Figure 4.9 QoS Device page 75
Figure 4.10 Setting the QoS Device to SatNet QoS 77
Figure 4.11 Mandatory Serial Number 77
Figure 4.12 Telnet Access 77
Figure 4.13 QoS Device Configuration Stats page 79
Figure 4.14 IP DVB Encapsulators fields 82
Figure 4.15 IP DVB Encapsulator page 84
Figure 4.16 ACM Adaptation Units page 87
Figure 4.17 ACM Adaptation Unit page 89
Figure 4.18 Modulators page 91
Figure 4.19 Modulator page 93
Figure 4.20 SCPC Receivers page 95
Figure 4.21 SCPC Receiver page 97
Figure 5.1 Air Interface View page 101
Figure 5.2 Air Interface Sub-menus 101
Figure 5.3 Default System values page 103
Figure 5.4 Frequency Bands page 105
Figure 5.5 Frequency Band page 107
Figure 5.6 Frequency Band Components page 109
27 August 2010 Advantech Satellite Networks Proprietary Page XVI

850176 P08
Figure 5.7 Frequency Guard page 111

Figure 5.8 Carrier Sets (Superframes) page 113
Figure 5.9 Carrier Set (Superframe) page 115
Figure 5.10 Areas page 118
Figure 5.11 Area page 120
Figure 5.12 RL Partitions (segments) page 123
Figure 5.13 RL Partition (Segment) page 125
Figure 5.14 Tx Modes page 127
Figure 5.15 Tx Mode page 129
Figure 5.16 Transport Streams page 130
Figure 5.17 Fields Available in the Configuration Tab 131
Figure 5.18 Fields Available in the PIDs Tab 132
Figure 5.19 Transport Stream page 133
Figure 6.1 File Import page 140
Figure 6.2 Service Level Agreement View page 143
Figure 6.3 SP Forward Link SLAs page 145
Figure 6.4 SP Forward Link SLA page 147
Figure 6.5 FL QoS Device Partitions page 150
Figure 6.6 FL QoS Device Partition page 152
Figure 6.7 IP Partition Classification page 155
Figure 6.8 Service Provider Return Link SLAs page 158
Figure 6.9 SP Return Link SLA page 160
Figure 6.10 Low Level RL SLAs page (LL Definition view) 163
Figure 6.11 Low Level RL SLAs page (Conditioning view) 164
Figure 6.12 Low Level return Link SLA page 166
Figure 6.13 Imported RL SLAs page 168
Figure 6.14 RL SLA Conditioning page 172
Figure 6.15 RL SLA Application page 176
Figure 6.16 SIT Groups page 178
Figure 6.17 SIT Group page 181
Figure 6.18 SIT Groups FL SLAs page 185
Figure 6.19 G FL SLA linked to a DVB-S2 ACM Transport Stream Page 187
Figure 6.20 SG FL SLA linked to a DVB-S Transport Stream Page 188
Figure 6.21 Default SIT Return Link QoS page 195
Figure 6.22 Default SIT Return Link QoS page 197
Figure 6.23 Default SIT Forward Link QoS page 200
Figure 6.24 Forward Link SIT Level QoS page 201
Figure 6.25 Default SIT RL Queue Filter page 203
Figure 6.26 Default RL SIT Queue Filter 205
Figure 6.27 RL QoS Scalings page 207
Figure 6.28 RL QoS Scaling page 209
Figure 6.29 Multicast Scheduling page 211
Figure 6.30 Multicast Scheduling Property page 212
Figure 6.31 Multicast Scheduling Recurrence 213
27 August 2010 Advantech Satellite Networks Proprietary Page XVII

850176 P08
Figure 6.32 Daily Scheduling Recurrence options 214

Figure 6.33 Weekly Scheduling Recurrence options 215
Figure 6.34 Monthly Scheduling Recurrence options 215
Figure 6.35 Yearly Scheduling Recurrence options 215
Figure 6.36 SIT Software Versions 216
Figure 6.37 SIT Software Version page 217
Figure 6.38 RFCM Modes hysteresis 219
Figure 7.1 Network View page 222
Figure 7.2 CFG Network Submenus 222
Figure 7.3 SITs page 224
Figure 7.4 SIT page 228
Figure 7.5 SIT Level RL QoS page 233
Figure 7.6 Traffic Queues page 240
Figure 7.7 VCC View 240
Figure 7.8 Mesh Destinations View 241
Figure 7.9 Traffic Queue page 242
Figure 7.10 Traffic Queue page (Usage Type: MESH_QUEUE) 245
Figure 7.11 IP Routes page 247
Figure 7.12 IP Route page 249
Figure 7.13 VLAN View page 252
Figure 7.14 VLAN Address Spaces page 253
Figure 7.15 VLAN Address Space page 254
Figure 7.16 ISP-Side Network Page 256
Figure 7.17 ISP-Side Network Update page 258
Figure 7.18 SP IP Address Ranges page 260
Figure 7.19 IP Address Range page 261
Figure 7.20 SP VCC Ranges page 263
Figure 7.21 VCC Range page 264
Figure 7.22 SP PID Ranges page 266
Figure 7.23 PID Range page 267
Figure 7.24 Mesh View page 269
Figure 8.1 Operations View page 272
Figure 8.2 SIT Monitoring / Control page 274
Figure 8.3 SIT Monitoring / Control - Grid Table Operations view 276
Figure 8.4 SIT Monitoring / Control - Grid Table Configuration view 278
Figure 8.5 SIT Monitoring / Control - ACM Table Configuration view 279
Figure 8.6 SIT Monitoring / Control - SCPC Table Configuration view 280
Figure 8.7 SIT Group Monitoring / Control page 282
Figure 8.8 Configuration Commands and Results page 286
Figure 8.9 IP Sec Report page 288
Figure 8.10 Connection Manager Events page 289
Figure 8.11 Connection Manager Alarms page 291
Figure 8.12 Connection Statistics page 295
Figure 8.13 Advanced RL Login Statistics page 297
27 August 2010 Advantech Satellite Networks Proprietary Page XVIII

850176 P08
Figure 8.14 RL Traffic Statistics page 299

Figure 8.15 RL Advanced Traffic Statistics page 301
Figure 8.16 Managed VoIP Call Statistics page 303
Figure 8.17 Managed VoIP Advanced RL Statistics page 305
Figure 8.18 Return Link RFCM Statistics page 307
Figure 8.19 Conditional RL Connection Statistics page 309
Figure 8.20 SIT SCPC Statistics page 312
Figure 8.21 FL MPEG PID Traffic Statistics page 313
Figure 8.22 FL Route MPEG Traffic Statistics page 315
Figure 8.23 FL Partition IP Traffic Statistics page 317
Figure 8.24 Example Performance data in Graph format 321
Figure 8.25 Example Performance data in TSV format 322
Figure 9.1 System Administration page 327
Figure 9.2 CM Redundancy Diagram 331
Figure 9.3 FL QoS Rules page 333
Figure 9.4 FL QoS Rule Configuration page 335
Figure 10.1 Save/Restore page 341
Figure 10.2 User Security certificate pop-up 344
Figure 11.1 Adaptec RAID Utility 351
Figure 11.2 K3b New Data CD Project 353
Figure 11.3 Burning a CD 354
Figure 11.4 Generate Joliet extensions 354
Figure 11.5 Burning an ISO image 355
27 August 2010 Advantech Satellite Networks Proprietary Page XIX

850176 P08
27 August 2010 Advantech Satellite Networks Proprietary Page XX

850176 P08
Chapter 1 Introduction
This chapter contains a general overview of the NetManager system and the context in
which it is used by Network Operators and Service Providers.
The following topics are covered:
• “Role of the NetManager Application” on page 2 is a general introduction on the
application.
• “NetManager Architecture” on page 3 presents the role of the NetManager within a
satellite network.
• “Operational Model” on page 4 is an overview of the various levels of configurations
available within NetManager.
• “Air Interfaces” on page 8 presents the various interfaces that are supported by the
NetManager.
27 August 2010 Advantech Satellite Networks Proprietary Page 1

850176 P08
1.1 Role of the NetManager Application

1.1.1 Overview
NetManager is a complete network management solution, built around the widely accepted
FCAPS model (see “FCAPS” on page 367). NetManager takes the complexity out of satel-
lite network management, allowing operators to concentrate on high-level organization
instead of dealing with the details typically needed to configure SIT access to a satellite net-
work.
NetManager gives operators control over the two main entities of a satellite network: the
Gateway and the SITs; it permits management of the Return Link (RLSS), Forward link
(FLSS) and IP Signaling (IPSS) sub-systems, all in a consistent manner and integrated in a
single user interface.
1.1.2 Features
Network operators can create hubs: reserved sets of resources on the Return Link and For-
ward Link that can then be managed independently by a Service Provider. Service Providers
can divide up their users into SIT Groups, which are logical groupings of terminals having
similar properties.
Traffic is managed using Service Level Agreements (SLAs) and Quality of Service (QoS)
configurations. Conditional SLAs can be programmed to easily handle changes in the oper-
ating environment, such as rain fade, in a consistent fashion.
Every part of the system can be monitored for status and presence of alarms, and many
counters are available to quantify, for instance, Connection Management features and
Return Link performance.
NetManager is also designed to take into account the interaction of different software. Net-
Manager can handle multiple FLSS's and thousands of SITs in an integrated environment.
In addition, the NetManager supports the management of various SIT types such as: DVB-
RCS SITs, SCPC SITs and Mesh SITs.
Finally, the entire NetManager core is built around security features, such as user manage-
ment permitting for different levels of access to the application and encrypted access to the
user interface (http over SSL using https). It also ensures that no unauthorized access to pro-
tected system resources can occur and allows delegation of different tasks to different peo-
ple without granting system-wide access to all users.

850176 P08
1.2 NetManager Architecture

1.2.1 Context
Figure 1.1 illustrates how the NetManager application fits within a Fully Managed Gateway
system as a complete solution for network management.
Figure 1.1: NetManager within the Satellite Network
1.2.2 Architecture
The NetManager architecture is composed of a SQL database, a web server and Java agents.
Figure 1.2 shows the NetManager architecture and the relations between the NetManager
components.
Figure 1.2: NetManager Architecture

850176 P08
1.2.2.1 Agents
1.2.2.1.1 CCS: Centralized Configuration System

The CCS agent is used by the Network Operators to perform the configuration of the Gate-
way elements. The CCS is also responsible for the segmentation of Forward Link and
Return Link resources so as to divide them up between Service Providers. It also allows
some level of direct configuration of system resources and equipment on the gateway with-
out the need for external software.
1.2.2.1.2 CM: Connection Manager

The CM module controls the real-time admission of SITs to the network. It is not used
directly by operators, but rather its behavior is dictated by the way they configure the Net-
Manager, admitting SITs to the network or preventing them from logging in based on the
rules they set.
1.2.2.2 SCS: SIT Command System

The SCS manages the Forward Link Control and Management (FLCM) which handles
commands from the NetManager to the SITs. The SCS permits advanced control over all
SITs managed by the NetManager. The SCS has the capability to send Unicast commands
to one SIT at a time or Multicast commands to multiple SITs simultaneously.
1.3 Operational Model

The operational model presented here is a conceptual overview of the basic levels of config-
urations available to tailor the bandwidth on the Forward Link and the Return Link. It is
intended to give a high level overview of the scope of the NetManager.
The main idea behind NetManager’s operation is the partitioning of bandwidth in a hierar-
chical fashion: there are four bandwidth management levels available in NetManager. This
approach gives operators the capability of configuring and allocating bandwidth in a very
flexible way while still keeping the process straightforward and intuitive.
1.3.1 Bandwidth Assignment: SLAs

Service Level Agreements are the mechanisms used to control bandwidth assignment on the
Return Link and Forward Link. The allocation of bandwidth at the SLA level is typically
based on four elements:
• Throughput
• Delay

850176 P08
• Jitter
• Packet Loss
NetManager currently considers mainly the aggregate throughput of a group of users or ser-
vices.
1.3.1.1 Service Provider SLAs

At the highest level, Network Operators partition the bandwidth of both the Return Link
and the Forward Link into Service Provider Service Level Agreements which are then dis-
tributed to the Service Providers. The Service Provider Return Link SLAs (SP RL SLAs)
are built upon NetManager RL carrier (MF-TDMA or SCPC) created by the Network Oper-
ator. The Service Provider Forward Link SLAs (SP FL SLAs) are tied to the QoS device
used (or the IP DVB Encapsulator used if no QoS device is present).
1.3.1.2 Finer Grained Assignment Control

At the next level on the Forward Link, Service Providers can partition their allotted SP FL
SLAs into SIT Group (SG) Forward Link SLAs to be distributed among groups of SITs:
SITs within a given Group receive all their Forward Link traffic bound by a specific SG FL
SLA.
On the Return Link, the Low Level RL SLAs (LL RL SLAs) provide the finer grained
assignment control over bandwidth.
1.3.2 Bandwidth Usage

1.3.2.1 SITs and SIT Groups
Each SIT is allowed usage of a certain fraction of the bandwidth; this is determined by its
Quality of Service Settings. To make configuration easier, SITs can be grouped into SIT
Groups, having similar bandwidth usage characteristics.
1.3.2.2 Quality of Service (QoS)

The Quality of Service (QoS) defines the bandwidth usage at the SIT level; default parame-
ters are defined at the SIT Group level to apply to all SITs in the Group.
1.3.2.2.1 Forward Link Quality of Service (FL QoS)

This defines the default bit rates available for SIT in a given group on the Forward Link,
and applies to all SITs in the group. This default can be overwritten at the route level.

850176 P08
1.3.2.2.2 Return Link Quality of Service (RL QoS)

This defines the default bit rates for different types of traffic available for SIT in a given
group on the Return Link. This default can be overwritten in each SIT’s profile (see “Over-
writing RL QoS” on page 232).
1.3.3 Resources Overview

1.3.3.1 System Level
The wide array of bandwidth configuration items that can be combined to provide fine gran-
ularity tuning over the satellite network are illustrated in Figure 1.3, showing a representa-
tion of a configured system.
Figure 1.3: Service Level Agreement View

850176 P08
1.3.3.2 Return Link Notes

Most of the bandwidth configuration happens on the Return Link; NetManager provides
additional levels of configuration under the LL RL SLAs to provide even finer grained
bandwidth assignment control; this includes the conditioning of LL RL SLAs, and applica-
tion-level bandwidth configuration (such as for VoIP). Figure 1.4 presents, through an
example configuration, the conceptual elements involved in configuring Return Link
Resources.
Figure 1.4: Return Link Resources

850176 P08
1.3.3.3 System Views

To assist the user in organizing and configuring the multitude of items in the system, Net-
Manager provides View pages that present a graphical representation of the current config-
uration of logical sub-parts of the system. The menu item which contains inter-linked
configuration items each provide a View page, making it easier to get an overview of the
existing configuration for that sub-part of the system.
Note: the menu items leading to the individual View pages are highlighted in blue.
1.4 Air Interfaces

1.4.1 DVB-RCS
DVB-RCS is a system that permits broadband receive and transmit capabilities via a geo-
stationary non-regenerative (also known as bent-pipe) satellite.
The link supporting communication from the Satellite Interactive Terminals (SITs) to the
Gateway, is called the Return Link (RL). The Return Link Sub-System (RLSS) manages the
Return Link: it handles SIT synchronization and network logon as well as allocates Return
Link capacity to them. The Return Link carries ATM cells and/or MPEG packets and allows
data rate from 64 to 8092 kbps.
The link supporting communication from the gateway to the SITs is called the Forward
Link (FL) and is based on a standard Digital Video Broadcasting (DVB) format. The For-
ward Link Sub-System (FLSS) manages the Forward Link. Data rates up to 90 Mbit/s are
possible on the Forward Link. The Forward Link is also used by the RLSS to send control
information to the SITs.

850176 P08
In Figure 1.5, the dotted lines indicate Forward Link communication and solid lines indi-
cate Return Link communication.
Figure 1.5: Digital Video Broadcast-Return Channel System (DVB-RCS)
One or several satellites can be used for the space segment. The satellite(s) handling the FL
usually operates at Ku band (14/12 GHz), but C and Ka bands are also possible. The RL sat-
tellite(s) can operate at Ku (14/12 GHz) or Ka band (30/18 GHz) as well as C band. In the
case of multiple satellites, they may be in the same or in different orbital slots.
The Internet Protocol Sub-System (IPSS) receives return link traffic from RLSS TRF,
routes IP packets towards appropriate destination and provides routing for forward link
multicast. The IPSS also provides the infrastructure for the management network and
optionally Traffic Shaping capability and Traffic accounting information.
The Timing Sub-System is part of the Gateway’s support equipment and provides highly
stable and reliable timing and frequency reference signals to the gateway.
1.4.2 Mesh Overlay

A DVB-RCS based transparent mesh system is an overlay to the standard DVB-RCS access
network architecture which achieves a combined star / mesh network The SITs of such a
star/mesh network incorporate additional mesh functionality used to receive mesh transmis-
sions directly from other SITs. These transmissions can be bi-directional unicast traffic
from one SIT to another, as well as a multicast stream from a mesh SIT to other mesh SITs.
The Hub station performs the network management and control functions for the mesh
overlay network, as well as supporting the gateway for any access traffic to the mesh termi-
nals operating in dual star/mesh mode.

850176 P08
In the current implementation, the MAC layer supports mesh and Star traffic on the mesh
carrier. The hub station only recovers the network bursts (CSC, SYNC) of the mesh carrier
to process terminal login and synchronization maintenance. The Star traffic is either for-
warded on the Forward Link to listening terminals, or sent on the terrestrial network inter-
face (e.g. the Internet).
Additionally, the mesh capacity supports guaranteed constant traffic allocations (CRA) and
volume based allocations (VBDC). The connectivity between mesh terminals is established
by the hub station and can be modified by the Network Operator. The capacity is pre-
assigned in the hub station but may be re-assignable through the network management sys-
tem. Both star and mesh networks are supported in the current implementation; however,
terminals belonging to a mesh network cannot concurrently belong to a star network.
The mesh overlay is configured at the Area level (see “Viewing Areas” on page 118) and at
the SIT level (see “Viewing SITs” on page 224). Mesh or Star usage for a given SIT can be
controlled in the SIT Monitoring and Control page (see “SIT Monitoring / Control” on
page 274).
The RLSS automatically get its configuration for Mesh from the NetManager.
1.4.3 SCPC
The NetManager supports the configuration of the SCPC Return Links in addition to DVB-
RCS Return Links. Therefore, the NetManager can manage a network where the SIT popu-
lation is a mix of DVB-RCS SITs and SCPC SITs.
It is possible, using the NetManager interface, to allocate an SCPC carrier set and link it to
SCPC receiver and to a SCPC SIT. Using these capabilities, the NetManager can manage
the frequency plans of the overall satellite network and the SLAs of DVB-RCS and SCPC
SITs.

850176 P08
Chapter 2 Overview of the NetManager Interface
This chapter explains the layout of the various components of the NetManager user inter-
face. The entire NetManager application uses the same basic layout, making access to its
features intuitive and consistent. These features will be explained throughout the user guide,
but the mechanics of using them is explained in the present chapter.
The chapter also covers basic access to the interface, broken down into the following sec-
tions:
• “Accessing the NetManager Application” on page 12 explains how to log on to the
NetManager application.
• “Navigating the NetManager User Interface” on page 15 explains how to use the vari-
ous buttons, menus, and fields in the NetManager application.
• “Adding, Updating and Deleting Records” on page 37 presents the common steps
involved in performing the basic NetManager operations: adding, updating, and delet-
ing various entities.
• “Interactive View Pages” on page 41 presents an overview of the functionality common
to all View Pages.
• “Getting Help with the NetManager” on page 43 explains how to access NetManager’s
online help feature.

850176 P08
2.1 Accessing the NetManager Application

NetManager is a web application: you do not install any software on your PC to access its
functionality but instead you use a web browser which, when connected with an NetMan-
ager server, acts as the user interface.
Note: NetManager is compatible with Internet Explorer version 6.0 or later.
To access the NetManager web application, you need to browse to the specific IP address
where the NetManager server is located. The IP address is made up of four sets of numbers
of up three digits each that you enter in the address bar of your web browser:
https://xxx.xxx.xxx.xxx
Note: You may also be able to type in the name of the server instead of the IP
address if your network supports DNS.
The IP address of your NetManager server is provided at commissioning time. Additionally,

your browser must support the https protocol (see “User Security Certificates” on page
344).
2.1.1 Log in to NetManager

Each user is associated with a user profile that grants its owner specific access rights to the
NetManager database and to its various functionalities. The user profile is determined by
the username and password entered at login time, and the access rights it grants apply for
the duration of the session (until logout, browser close, etc.).
Note: Your system administrator needs to provide you with a valid user account.
To log in to the NetManager application, follow these steps:
1. Type the IP address in the web browser’s address field and press <Enter>.

850176 P08
2. When the NetManager welcome page appears, click the Click here to login link as
shown in Figure 2.1.
Figure 2.1: NetManager Welcome page
3. The Log In page appears (see Figure 2.2) and you are prompted for a valid username
and password, in order to authenticate you on the system: type them in the
corresponding fields.
Figure 2.2: Log in page
If you need to reset the input fields, click the Clear button.
4. Click the Login button to validate the user profile and access the NetManager
application.

850176 P08
Once NetManager authenticates your username and password, you are granted access to the
rest of the NetManager application.
Note: NetManager is delivered with a default user “NO admin1” having default
password “no_admin1”. It is recommended to change these when turning
on the system.
2.1.2 Access Control List

In addition to the account authentication process, NetManager 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 NetManager 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 NetManager unless his host IP address has been allowed by adding it to
the ACL (see “Adding and Updating User Accounts” on page 52).
2.1.3 NetManager Entrance Page

The Advantech SatNet NetManager page (see Figure 2.3) is the entrance page to the Net-
Manager application. Its main purpose is to provide quick access to an overview of the con-
figuration state of the main functionality groups, through a series of large icon/buttons that
permit navigation to pages relevant to the overview of each topic:
• Air Interface: see “Configuring Air Interface Overview” on page 100

• Equipment: see “Equipment View” on page 62
• Network: see “Configuring Network Overview” on page 222
• User: see “Users View” on page 50
• Operations: see “Operations Overview” on page 272
• Service Level Agreement: see “Configuring Services Overview” on page 142
• SIT Management: see “SIT Monitoring / Control” on page 274

850176 P08
Figure 2.3: Advantech SatNet NetManager Page
2.2 Navigating the NetManager User Interface

The NetManager User Interface is divided into various sections as shown in Figure 2.4:
• The Navigation Bar, displayed at the top of the page, allows access to the different fea-
ture categories of the application, see “Navigation Bar” on page 16.
• The Presentation Pane displays the title of the current NetManager page, along with
the NetManager software version, as well as the Help button linking to context-sensi-
tive the NetManager online help, see “Getting Help with the NetManager” on page 43.
• The Filter Drop-Down List allows you to filter the information in the page, see “Filter
Drop-Down List” on page 25.
• The centre of the page displays the data associated to the feature you are using, see
“Workspace” on page 26.
• The buttons at the bottom of the page allow you to perform operations on the data dis-
played in the Workspace as well as providing some navigation functions, see “But-
tons” on page 30 and “Refresh Bar” on page 31.

850176 P08
• The Quick Access Links, as shown in Figure 2.4, are used to give the operator quick
access to the most frequently used NetManager pages. For more information on the
Quick Access Links, see “Quick Access Links” on page 36.
Figure 2.4: Typical application page
2.2.1 Navigation Bar

The navigation bar, displayed at the top of the page, provides access to the different feature
categories found in NetManager: clicking on each item in the menu will make sub-menu
items appear. Clicking the sub-menu items will either navigate to the appropriate applica-
tion page, or open a second sub-menu with additional items (indicated by an arrow).
Figure 2.5: Network Operator Navigation Bar
The following sub-sections list the features available for each item in the navigation bar.

850176 P08
2.2.1.1 CFG Equipment

The CFG Equipment menu item provides Network Operators with facilities for configur-
ing Gateway equipment.
Figure 2.6: CFG Equipment Sub-menus
The following sub-menus are available:
• Equipment View: graphical representation of all equipment currently configured, see

“Configuring Equipment Overview” on page 62.
• RLSS: provides access to general configuration of the RLSS, see “RLSS Profile” on
page 64.
• Equipment Wizard: guided configuration of NetManager equipment used for initial
configuration of an empty system, see “Equipment Wizard” on page 66.
• Routers: describes the configuration of the Routers, see “Routers” on page 67.
• PEP: allows for the configuration of parameters related to the Performance Enhance-
ment Proxies, see “Performance Enhancement Proxy” on page 71.
• QoS Device: permits setting configuration parameters related to Quality of Service
management devices, see “QoS Device” on page 75.
• IP DVB Encapsulators: provides access to configuration of IP/DVB Encapsulators,
see “IP DVB Encapsulator Profiles” on page 80.
• ACM Adaptation Units: allows for the configuration of the parameters associated
with the ACM Adaptation Unit, see “ACM Adaptation Units” on page 87.
• Modulator: allows for the configuration of parameters related to Modulators, see
“Modulators” on page 91.
• SCPC Receiver: allows configuration of single carrier receivers, see “SCPC Receiv-
ers” on page 95.

850176 P08
• System Admin: provides access to most System Administration tasks that Network
Operators need to perform, see “General System Administration” on page 325. This
menu groups the following sub-items:
• Db/CM: Provides general configuration applicable to the database and Connection
Manager, see “System Administration” on page 326.
• FL QoS Rules: Describes the Forward Link Quality of Services rules that can be
defined in the system, see “FL QoS Rules” on page 333.
2.2.1.2 CFG Air Interface

The CFG Air Interface menu item is used to configure Air Interface related items.
Figure 2.7: CFG Air Interface Sub-menus
• Air Interface View: presents a graphical interactive view of the current NetManager
Air Interface components, see “Configuring Equipment Overview” on page 62.
• Default Values: allows the user to define default values used in populating new Air
Interface elements, see “Default Values” on page 102.
• Frequency Plan: This menu item groups sub-items relevant to Frequency Plan man-
agement (see “Frequency Plan” on page 105), namely:
• Frequency Bands: provides access to the configuration of Frequency Bands, see
“Viewing Frequency Bands” on page 105.
• Frequency Band Components: allows for the configuration of the components
making up Frequency Bands, see “Viewing Frequency Band Components” on page
109.
• Return Link: This menu item groups sub-items relevant to RL management (see
“Return Link” on page 113), namely:
• Superframes: provides access to Superframe configuration, see“Viewing Carrier
Sets (Superframes)” on page 113.

850176 P08
• Areas: provides access to Area configuration, see “Viewing Areas” on page 118.
• Partitions (Segments): provides access to Partition configuration, see “RL Parti-
tions (Segments)” on page 123.
• Forward Link: This menu item groups sub-items relevant to FL management, see
“Forward Link” on page 127 , namely:
• TX Mode: provides access to Tx Modes (MODCODs) configuration, see “Tx
Mode” on page 127.
• Transport Streams: provides access to Transport Stream configuration, see
“Transport Streams” on page 130.
2.2.1.3 CFG Services

The CFG Services menu item groups the configuration of the bandwidth partitioning on the
Return and Forward links.
Figure 2.8: CFG Services Sub-menus
• SLA View: presents a graphical interactive view of the current NetManager Service
Configuration, see “Configuring Services Overview” on page 142.
• FL BW Management: grouping of the available configuration items for Service
related to Forward Link Bandwidth Management. The following sub-items are avail-
able:
• SP FL SLA: gives access to configuring Service Provider Forward Link Service
Level Agreements, see “Forward Link Services to Service Providers” on page 144.
• FL QoS Device Partition: permits the configuration of bandwidth partitions
related to the FL QoS Device, see “Viewing Forward Link QoS Device Partitions
(Packeteer QoS only)” on page 149.

850176 P08
• RL BW Management: grouping of the available configuration items for Services

related to Return Link Bandwidth Management. The following sub-items are avail-
able:
• SP RL SLA: gives access to configuring Service Provider Return Link Service
Level Agreements, see “Return Link Services to Service Providers” on page 157.
• Low-Level RL SLA: permits the configuration of Low Level Return Link SLAs,
see “Low Level Return Link SLAs” on page 162.
• SIT Groups: grouping of the available configuration items for Services related to SIT
Groups. The following sub-items are available:
• SIT Groups: provides SIT Groups configuration functionality, see “SIT Group
Configuration” on page 178.
• SG FL SLA: provides SIT Group Forward Link SLA configuration, see “Services
to SIT Groups” on page 178.
• SIT Services: grouping of the available configuration items for Service related to SITs
(see “Services to SITs” on page 194). The following sub-items are available:
• RL QoS: used to define the various SIT Return Link Quality of Service profiles,
see “Viewing Default SIT Return Link QoS Profiles” on page 194.
• FL QoS: used to define the various SIT Forward Link Quality of Service profiles,
see “Viewing Default SIT Forward Link QoS Profiles” on page 200.
• RL Queue Filter: permits the configuration of Queue Filters on the Return Link;
see “RL Queue Filters” on page 203.
• RL QoS Scaling: permits the adjusting of QoS Scaling parameters, see “Return
Link QoS Scaling” on page 207.
• Multicast Scheduling: used to schedule multicast events, see “Multicast Schedul-
ing” on page 211.
• SIT S/W Version: Allows for the management of SIT Software versions “SIT
Software Versions” on page 216.

850176 P08
2.2.1.4 CFG Network

The CFG Network menu item groups functionality related to the configuration of the satel-
lite network.
Figure 2.9: CFG Network Sub-menus
• Network View: presents a graphical interactive view of the current NetManager Net-
work Configuration, see “Configuring Network Overview” on page 222.
• SIT: allows for the configuration of individual SITs, see “SIT Profiles” on page 224.
• Traffic Queues: allows for the configuration of traffic queues, see “SIT Queues” on
page 238.
• FL Routes: configures IP Routes, see “IP Routes” on page 247.
• VLAN: provides access to VLAN management features, see “VLAN” on page 252.
• VLAN View, provides access to the menu items related to configuring the VLAN,
see “VLAN View” on page 252.
• Address Space, see “VLAN Address Space” on page 253.
• ISP-Side Network, allows the configuration of the private customer networks on
the ISP-side of the Gateway, see “VLAN ISP-Side Network” on page 256.
• Ranges: permits the configuration of assignable parameter ranges, see “Ranges” on
page 259). Three sub-items are available:
• IP Address: gives access to configuring ranges of assignable IP addresses, see
“Viewing Service Provider IP Address Ranges” on page 259.
• VCC: gives access to configuring ranges of assignable Virtual Channel Connec-
tions, see “Viewing SP VCC Ranges” on page 262.
• PID: gives access to configuring ranges of assignable Packet Identifiers, see
“Viewing SP PID Ranges” on page 265.

850176 P08
• Mesh View: presents a graphical interactive view of the current Mesh Network config-
uration, see “Mesh View” on page 269.
2.2.1.5 CFG Mgmt

The CFG Mgmt groups operations related to configuration data.
Figure 2.10: CFG Mgmt Sub-menus
• File Import: allows for the import of various file types into the NetManager, see
“Importing RLSS Configurations” on page 138.
• SP Save/Restore: allows for the back-up and re-load of entire Service Provider Con-
figurations, see “Back-up and Restore” on page 340.
• Command/Result: provides feedback on commands sent to equipment, see “Config-
uration Commands and Results” on page 285.
• IPSec Report: Provides a global report on IPSec (see “IP Sec Report” on page 288).

850176 P08
2.2.1.6 Operations
The Operations menu item provides access to various operational facilities of the NetMan-
ager, see “Monitoring The Gateway” on page 271.
Figure 2.11: Operations Sub-menus
• Operations View: presents a graphical interactive view of the current NetManager

Operations Configuration, see “Operations Overview” on page 272.
• SIT Monitoring/Control: provides SIT monitoring and command functions, see “SIT
Monitoring / Control” on page 274.
• SIT Group Monitoring/Control: provides SIT Group monitoring and command
functions, see “SIT Group Monitoring / Control” on page 282.
• Connection Manager Events: displays Connection Manager events, see “Viewing
Events” on page 289.
• Connection Manager Alarms: displays Connection Manager alarms, see “Viewing
Alarms” on page 291.
• RL Statistics: grouping of summary RL statistics functionality. The following sub-
items are available:
• Connections: displays summary connection statistics, see “Connection Statistics”
on page 295.
• RL Traffic: displays summary traffic statistics for the Return Link, see “Return
Link Traffic Statistics” on page 299.
• VoIP: displays a summary of Voice-Over-IP call statistics, see “Managed VoIP Call
Statistics” on page 303.
• RL RFCM: provides a summary of Rain Fade Counter Measure related statistics,
see “Return Link RFCM Statistics” on page 307.

850176 P08
• SIT SCPC: Displays a summary of the performance statistics of the SCPC SITs,
see “SIT SCPC” on page 312.
• RL Advanced Statistics: grouping of detailed RL statistics functionality. The follow-
ing sub-items are available:
• Cond. RL Connections: displays detailed Rain Fade Counter Measures statistics,
see “Conditional Return Link Connection Statistics” on page 309.
• Adv. Login: displays detailed statistics on connection activity, see “Advanced RL
Login Statistics” on page 297.
• Adv. RL Traffic: displays detailed traffic statistics for the Return Link, see
“Return Link Advanced Traffic Statistics” on page 301.
• Adv. VoIP: displays detailed Voice-over-IP call statistics, see “Return Link
Advanced Traffic Statistics” on page 301.
• FL Statistics: grouping of summary FL statistics functionality. The following sub-
items are available:
• MPEG PID Traffic: Displays MPEG traffic statistics based on PIDs, see “MPEG
PID Traffic Statistics” on page 313.
• Route MPEG Traffic: Displays MPEG traffic statistics based on Routes, see
“Route MPEG Traffic Statistics” on page 315.
• Partition IP Traffic: Displays Partition traffic statistics, see “FL Partition IP Traf-
fic Statistics” on page 317.
2.2.1.7 User Mgmt

The User Mgmt menu item allows for NetManager user management, see “NetManager
Configuration Management” on page 45.
Figure 2.12: User Mgmt Sub-menus

850176 P08
Three sub-menus are available:
• NetManager Users View: presents a graphical interactive view of the current Net-
Manager Users Configuration, see “User Management” on page 50.
• Service Provider: gives access to the Service Provider page, see “Managing Service
Providers” on page 47.
• Manage User: provides access to user modification tasks, see “Managing User
Accounts” on page 51.
• Monitor User Activity: displays user activity log, see “Monitor User Activity” on
page 56.
• Customer: Permits entering customer information which may then be associated with
services, see “Customers” on page 58.
2.2.1.8 Help and Logout
• Help: provides access to the NetManager online help.

• Logout: terminates the current NetManager session and logs out the user in the proc-
ess.
2.2.2 Filter Drop-Down List

Just below the navigation bar, certain NetManager pages display a filter drop-down list,
allowing for the filtering of information shown in that page; Figure 2.13 shows an example
of such a filter drop-down in which the Service Provider can be selected.
Figure 2.13: Service Provider Drop-Down List
To filter the information in the page according to specific criteria, simply select the desired
item from the drop-down list and the page will be refreshed with only the items relevant to
the selected filter; you can also sometimes select All to display un-filtered information.
Note: Some drop-down lists are restricted to certain users; for example, viewing
information on other Service Providers is only available to Network Operator
users.

850176 P08
2.2.3 Workspace
The Workspace is located toward the center of the browser page and shows the data you
interact with. The Workspace can present data in two formats, depending on what the appli-
cation needs to display:
• Property Page format used to view and edit the properties of a single item, see “Prop-
erty Page” on page 26.
• Grid Table format in which a list of items is displayed for selection, with the table col-
umns typically showing a subset of the items’ properties, see “Grid Table” on page 27.
2.2.3.1 Property Page

When you wish to view or edit a single item, the Workspace will display the fields that per-
tain to this item. You can configure the item by filling in the proper information in each
field and clicking one of the action buttons at the bottom of the page (see “Buttons” on page
30). Some fields may be drop-down lists from which you can select a value; the values
available for selection can depend on selections in other drop-down lists on the page. Other
fields may be free-text (text boxes) in which you type in a value.
Certain fields can be highlighted to stress a difference; for example, the SIT-Level Nominal
Login RL QoS fields will be highlighted if different from the SIT Group defaults; refer to
Figure 2.24 (page 32) for an example of highlighted fields. Other fields may be grayed-out,
indicating that the value cannot be edited: this can be due, for example, to lower user privi-
lege than required to change the field, a selection made in previous navigation or because
the field is system-assigned and cannot be manually changed.

850176 P08
Figure 2.14: Sample page with fields to complete
Note: If you require assistance on a specific field (definition, possible values, etc.),
access the online help (see “Getting Help with the NetManager” on page 43)
from the page in which the field is displayed in the application; alternatively,
consult the Table of Contents in this User Guide for the topic you require
assistance with.
2.2.3.2 Grid Table

Many pages in the NetManager present a list of items in the form of a table (one item per
row). The Grid has two areas (see Figure 2.15 (page 28)): the Header Row presents infor-
mation on the items displayed in the table, and the Item Rows which are the actual data.
The NB of Entries field above the Header Row shows the number of item rows displayed
in the page and the number of rows in the table, in the format: Nb in page / Nb in table.
When tables grow too large to fit in a single page, the data is paginated and navigation links
are provided to move forward and backward through the pages; in this case, the current
page number and number of pages in the table are also displayed in the NB of Entries field.

850176 P08
Note: The part of the NB of Entries field showing the number of items in the table
does not necessarily represent the total number of existing items in the table,
but rather the number of entries in the table after any filtering has been
applied to it (see “Filter Drop-Down List” on page 25).
NB of Entries
Header row
Item rows
Figure 2.15: Grid Table
You can perform operations on individual items in the grid by selecting a row using the
check-boxes found in the first column, then clicking one of the Action buttons at the bottom
of the page. Some actions can be performed on multiple rows, while others will only be
allowed when a single row is selected: this will be indicated by the button becoming
grayed-out when you select more than one row (see Figure 2.30 (page 39) with the Update
button grayed-out).
The default order in which rows appear when a Grid Table page is accessed depends on the
individual page, but the rows can be re-ordered based on any column by clicking the header
name of that column: the table will be refreshed with the rows now sorted according to that
column (alphabetically or numerically).
Note: The re-ordering of rows is not persistent: if you navigate away from a given
page and come back to it later on, the ordering will be back to the default one
for the page, which is normally ascending.

850176 P08
As an example, Figure 2.16 shows the initial view of a page: the default row ordering for
this page is currently in effect: when the default ordering is in effect, no specific row order-
ing is used.
Figure 2.16: Initial/Default Row Ordering
Figure 2.17 below shows the result of clicking the header of the Login Name column once:
rows are now ordered in descending alphabetical fashion; notice that the Login Name col-
umn header background is green, signifying that the table is currently ordered on this col-
umn.
Figure 2.17: Descending Row Ordering

850176 P08
Figure 2.18 displays the page after the Login Name header is clicked a second time: the
row ordering is reversed and the green background still emphasises the column on which
the table is ordered.
Figure 2.18: Ascending Row Ordering
2.2.4 Buttons
Many tasks in NetManager are performed using the buttons found at the bottom of NetMan-
ager pages (see Figure 2.19).
Some buttons act on data displayed in the Workspace (see “Workspace” on page 26) and are
called Action Buttons. One example is the Add button which will attempt to add an entity
to the database, based on the information currently displayed in the Workspace.
Figure 2.19: Action buttons
Once you click a button, the system will attempt to perform the requested action.
• If the operation succeeds, the page will be refreshed with the updated values and a con-
firmation message will be shown at the bottom of the page (highlighted in green) as
Figure 2.20: Example of a confirmation message
• If a problem occurs when attempting to perform the operation, feedback will also be
given at the bottom of the page. Errors, highlighted in red, indicate the failure of the
action, while Warnings are highlighted in yellow. The error messages typically name
the field involved in the failure to help you correct it as shown in Figure 2.21 (page
31).

850176 P08
For example, if you fail to add an SP FL SLA to the database because you omitted to fill in
the Service Category field, the following message will appear:
Figure 2.21: Example of an error message
Note: For more information on the cause of warnings and errors, see
“Troubleshooting” on page 359.
Note: The most common operations available with these buttons have to do with
the addition, deletion and update of items: refer to “Adding, Updating and
Deleting Records” on page 37 for further information on these operations.
Some buttons do not perform actions but are there to provide guided navigation. These
Navigation Buttons (see Figure 2.22) are distinguishable from Action buttons by the fact
that their text label contains either “<“ or “>” sign, indicating the logical direction of navi-
gation (forward or back in a given configuration process).
Figure 2.22: Navigation Buttons
2.2.5 Refresh Bar

NetManager has a feature allowing certain pages to be automatically refreshed at a given
interval. This is useful, for example, when monitoring system parameters, so as not to have
to continuously click the browser’s refresh button to follow the evolution of the parameters.
The pages that have the automatic refresh feature are identified by the presence of the
Refresh Bar at the bottom of the page, see Figure 2.23.
Figure 2.23: Refresh Bar
The period at which these pages will automatically refresh can be changed by clicking the
Auto Refresh Period (seconds) button and modifying the value in the Refresh Bar’s edit
box to the desired number of seconds between page updates. The page can also be manually
refreshed by clicking the Manual Refresh button.
Note: Some pages contain only the Manual Refresh button, and so can only be
manually refreshed.

850176 P08
The refresh period is a global parameter, so that changing it for a given page also changes it
for all other pages that have the automatic refresh feature. The default refresh period is 30
seconds, and the minimum refresh period is 5 seconds.
Note: Clicking the Stop icon disables automatic refresh for all pages.
2.2.6 Tooltips
To assist in performing various operations, the NetManager’s user interface includes Toolt-
ips: context-sensitive pop-ups showing information on a given field name in the application
window. To signify that a Tooltip is available for a given item, the field description for the
item is underlined. To view the Tooltip for the item, simply hover the mouse cursor over the
field description and immobilize it there: the pop-up will appear after a few seconds. To dis-
miss the Tooltip, simply move the cursor away from the item.
Figure 2.24 shows the tooltip that appears when hovering the mouse cursor over the Con-
stant Traffic (CRA) kbit/s field name, in this case displaying the default value for the field
before it was changed.
Figure 2.24: Tooltips: Current value of the field

850176 P08
Tooltips also show the range of possible values of the parameter on which the mouse is
pointed as shown in Figure 2.25.
Figure 2.25: Tooltips: Range of possible values

850176 P08
Finally, Tooltips show a short description of the field on which the mouse is pointed as
Figure 2.26: Tooltips: Short description of the SIT-Level QoS Scaling wrt Nominal field

850176 P08
2.2.7 Expert Mode

Certain pages contain fields that are intended for expert users; to make the pages easier to
view and use, these fields are hidden but can be revealed using the Expert mode feature.
The pages where the Expert Mode applies have an orange lightning icon at the top right of
the page as shown in Figure 2.27. By default, these pages have Expert Mode turned OFF, so
that expert fields are hidden.
Figure 2.27: Expert Mode OFF

850176 P08
To turn ON Expert Mode, simply click the orange lightning icon, revealing the expert
fields, as shown in Figure 2.28, where both the Priority on Opportunistic Capacity field
and the Priority on Guaranteed Capacity field which were initially hidden are now dis-
played.
Figure 2.28: Expert Mode ON
2.2.8 Quick Access Links

The Quick Access Links are a convenient way for the operator to access frequently used
pages without going through the Navigation Bar menus. The Quick access Links are always
located on the left side of any NetManager page. Figure 2.29 (page 37) shows an example
of the Quick Access Links.

850176 P08
Figure 2.29: Quick Access Links
2.3 Adding, Updating and Deleting Records

For almost every feature in the NetManager application, you need to add, update, or delete
items (records). The basic procedure associated to each of these operations is very similar
between types of record worked on. While the specifics of working with a particular type of
record (e.g. a SIT profile, an SP RL SLA, etc.) is discussed in its appropriate chapter, the
steps common to all types of records are presented in this section:
• To add records to the database, see “Adding Records to the Database” on page 38.
• To update records in the database, see “Updating Records in the Database” on page 38.
• To delete records in the database, see “Deleting Records from the Database” on page
40.
To perform these operations, first access the Grid Table page for the item type you will be
working on. To access a given Grid Table, simply select the sub-menu item of interest from
the navigation bar menu. The result (success or failure) of the action will be presented at the
bottom of the page (see “Buttons” on page 30).
For example, if you want to perform an operation on SIT Groups:
1. Select the SIT Groups item from the SIT Groups sub-menu in the navigation bar’s
CFG Services menu.
2. This will display a Grid Table containing a list of SIT group items,

850176 P08
3. Using the buttons at the bottom of the page, you now have access to adding, updating,
and deleting SIT Groups.
Note: Many operations require specific privilege level: if you do not have sufficient
privilege, you may not have access to those operations. Contact your
System Administrator for further assistance.
2.3.1 Adding Records to the Database

To add records to the database, follow these steps:
1. Select the sub-menu item of interest from the main menus of the navigation bar to
display the Grid Table to which you want to add an item.
2. Click the Add button. A blank version of the record will appear on the page (some
fields may have default values).
3. Fill in the fields required to configure this record. Information on individual fields can
be found in the chapter or the online help page of the specific feature.
4. When you are satisfied that the fields are complete and the record is ready to be added,
click the Add button.
The NetManager application will validate the information you provided in the fields. If
the data is valid, the record will be added to the database and a confirmation message
will be shown at the bottom of the page (highlighted in green).
Note: If there are problems with the information provided, the record will not be
added to the database and an error message will be displayed at the bottom
of the page. You must correct the entries and attempt to add the record again
by clicking Add, or abandon the changes without adding the record.
To return to the previous listing page, click the < Back to ... button.
2.3.2 Updating Records in the Database

If you need to make changes to an existing record, you can select the record from the Grid
Table page and edit the fields you desire using the Update operation.
Note: The Update operation can only be performed on an existing record. You
must select a single record from the displayed list for the button to become
active. If you select more than one record, the Update button will be grayed
out.

850176 P08
To update an existing record, follow these steps:
1. Select the sub-menu item of interest from the main menus on the navigation bar to
display the Grid Table containing the desired item.
2. Select the desired item in the Grid Table by clicking its checkbox (located in the first
column, on the row of the item you wish to update). The selected record will be
highlighted in yellow.
If you select
more than
one record,
the Update
button will be
grayed out.
Figure 2.30: Highlighting multiple records to update
3. Click the Update button. The Property Page for this record will appear, showing the
current values for the record’s fields.
4. Modify the fields you require and click the Update button.
Note: Some fields may be grayed-out, for example because you lack sufficient
privilege to modify them, or because they are strictly system-assigned.
Contact your System Administrator for further assistance.
Note: It is also possible to delete the record currently being modified by clicking on
Delete: refer to “Deleting Records from the Database” on page 40 for
additional information.

850176 P08
2.3.3 Deleting Records from the Database

You can remove records permanently from the database using the Delete operation.
Warning: The delete operation cannot be undone; once data is removed from the
database it cannot be recovered, short of performing a restore operation on
a previously saved backup, which in itself may overwrite more recent
operations. Refer to “Back-up and Restore” on page 340 for further
information.
The Delete button located in the Grid Table pages can be used to delete items.
Note: The Delete operation can only be performed on existing records. You must
select at least one record from the displayed list for the button to become
active.
Alternately, you can select a single record from the list and click the Update button to view
its properties (e.g. to confirm that this is indeed the record you wish to delete), and then
click the Delete button in the Property Page without having to navigate back to the Grid
Table. This will delete the current record from the database. For more information on updat-
ing records, see “Updating Records in the Database” on page 38.
Warning: There is no prompt for a confirmation of the operation when you click the
Delete button: the record is immediately removed from the database. Before
clicking the Delete button, ensure that only the desired records have been
selected.

850176 P08
To delete one or more records from the database, follow these steps:
1. Select the sub-menu item of interest from the main menus on the Navigation Bar to
display the Grid Table containing the item(s) to delete.
2. Select the desired items to delete in the Grid Table by clicking their checkbox (located
in the first column, on the rows of the items you wish to delete). The selected records
will be highlighted in yellow.
You can select

multiple items
to delete from
the database.
Figure 2.31: Highlighting records to delete
3. Click the Delete button.
2.4 Interactive View Pages

The View pages present an interactive graphical representation of a part of the NetManager
Operational model (see “Operational Model” on page 4). The individual View pages can be
accessed in two ways. Clicking on one of the image buttons in the Advantech SatNet Net-
Manager entrance page (see “NetManager Entrance Page” on page 14) navigates to the View
page for the functionality represented by the button; additionally, one of the menu items of
some of the menus (see “Navigation Bar” on page 16) is highlighted in blue: clicking on
one of these blue menu items navigates to the View page related to the particular menu.

850176 P08
The View pages present an overview of the items related to part of the Operational Model
grouped under the menu/image button, including the relationships between them. The pages
are arranged in columns, representing a type of element, and individual elements of a same
type are placed one on top of another. The individual elements’ relationships with other ele-
ments are represented by their vertical position, as well as arrows linking them together; the
implied relationships must be inferred by the context of the element usage.
The information presented in the page is a snapshot of the system and the page can be
updated by clicking the Refresh button (see “Refresh Bar” on page 31).
The elements represented in the View pages (e.g. Superframe2 in Figure 2.32) are hyper-
links: clicking on them directly navigates to that item’s property page (see “Property Page”
on page 26), if the element is managed by NetManager, or to a generic page if the element is
informational (i.e. not managed directly by NetManager). Similarly, the column headers
(e.g. Segments in Figure 2.32) are also hyperlinks, but to the Grid Table pages (see “Grid
Table” on page 27) of the element type they represent, when such a page is available. The
View Pages are therefore useful for getting an overview of the configuration of a given part
of the system; it enables operators to quickly navigate among the configured elements to
make adjustments or monitor the system.
Figure 2.32: Example View page

850176 P08
2.5 Getting Help with the NetManager

Assistance is available for all aspects of NetManager configuration, operation and trouble-
shooting. Help is available in multiple formats. The full online help can be accessed by
clicking the Help menu item. It is also possible to open the help page specifically related to
the current NetManager Management Interface page: this context-sensitive help feature
is available for each page and can be accessed by clicking the button.
The structure of an online help page is as follows (see Figure 2.33):
Link to show the

help table of
Contents.
Description of
the NetManager
page with links to
help on relevant
items.
Description of
parameters
available on the
NetManager
page.
Clickable buttons
that link to more
detailed instruc-
tions on data
entry.
Clickable buttons
that link to help
pages for other
NetManager
pages the user
can navigate to.
Links to related
help topics.
Figure 2.33: Typical Online Help Page

850176 P08

850176 P08
Chapter 3 NetManager Configuration Management
This chapter explains user categories and user profiles, which are the foundation of the
application’s security framework.
The following sections are covered:
• “Accessing the NetManager Database” on page 46 explains the two user categories
and the access they have to the NetManager database.
• “User Management” on page 50 details how to create, update, and delete users within
those two user categories.

850176 P08
3.1 Accessing the NetManager Database

3.1.1 User Categories
NetManager’s 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:
• 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,
terminals, 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 pass-
word for any operator account. They can also use special features, such as RLSS
configuration import.
• Operator: Users in this category can create, modify and delete SIT resources as
well as send commands to SITs belonging to any Service Provider.
• Viewer: These users have read-only access to the entire database.
Note: At installation time, NetManager is configured with three pre-defined user

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

850176 P08
3.1.2 Managing Service Providers

When logging in as a Network Operator, the Service Provider page is displayed (see Fig-
ure 3.1), listing the Service Providers configured in the NetManager.
Note: The Service Provider page is also accessible by selecting Service

Provider from the navigation bar’s User Mgmt menu.
Use these
three but-
tons to
add,
update,
and
delete
Figure 3.1: The main Service Provider page
This page lists each profile along with the following information:
Field Description
Name The Service Provider name.

Contact Name The full name of the main contact person linked to this
Service Provider.
Max Number Of  The maximum number of SITs that this Service Provider is
Configured Terminals allowed to configure into the system.
Table 3.1 Service Provider page fields
The NetManager application allows Network Operators to perform the following operations
on Service Providers:

850176 P08
• Create/Update Service Providers (see “Adding and Updating a Service Provider Pro-
file” on page 48).
• Delete Service Providers (see “Deleting a Service Provider Profile” on page 50).
3.1.2.1 Adding and Updating a Service Provider Profile

All services configured in the NetManager are linked to a Service Provider. Each Service
Provider has three default users, one for each category (see “User Categories” on page 46):
Administrator, Operator and Viewer, with distinct usernames and passwords.
To update an existing Service Provider, select it from the Grid Table in the Service Pro-
vider page and click the Update button, or to add a new Service Provider, click the Add
button. This brings up the Manage Service Provider property page as shown in Figure 3.2.
Note: For more information on adding and updating records in the database, see
“Adding, Updating and Deleting Records” on page 37.
Figure 3.2: Manage Service Provider page

850176 P08
Modify the Service Provider as required and click the Update button. The Service Provider
fields are described in Table 3.2.
Field Description
Service Provider Information

Name The name of the Service Provider.
Note: This field cannot be modified once the Service

Provider has been created.
Contact Name The full name of the main contact person for this Service
Provider profile.
Phone Number The primary phone number where the contact person can be
reached.
Max Number Of  The maximum number of SITs that this Service Provider
Configured Terminals profile is allowed to configure into the system.
Table 3.2 Service Provider Information fields
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 “Man-
aging User Accounts” on page 51).
The Network Administrator needs to define a user name and a password for each Service
Provider profile using the fields described in Table 3.3. Enter the fields as required and click
the Add button..
Default Service Provider Users

Administrator Login The login name for the default user with administrative
Name access to the database.
Password The password for the Administrator user profile.
Operator Login Name The login name for the default user having only access to
the SIT data for the Service Provider.
Password The password for the Operator user profile.
Viewer Login Name The login name for the default user having only read-only
access to the Service Provider’s database.
Password The password for the Viewer user profile.
Table 3.3 Default Service Provider Users fields

850176 P08
To return to the Service Provider page, click the < Back to Manage SP Table button.
3.1.2.2 Deleting a Service Provider Profile

To remove Service Providers from the database, select one or more items from the Grid
Table in the Service Provider page and click the Delete button.
Alternatively, you can open the property page for the Service Provider to delete (see “Add-
ing and Updating a Service Provider Profile” on page 48) and click the Delete button.
Note: For more information on deleting the records in the database, see “Deleting
Records from the Database” on page 40.
3.2 User Management

The User Management feature allows for the configuration and monitoring of NetManager
users. Network Operators can create new user accounts to link to a given Service Provider
profile as well as update or delete existing user accounts.
The menu items available for Operations are:
• NetManager Users View: brings up the Users View page (see “Users View” on page
50).
• Service Provider: brings up the Service Provider main page (see “Managing Service
Providers” on page 47).
• Manage User: allows for the creation, modification and deletion of user accounts (see
“Managing User Accounts” on page 51).
• Monitor User Activity: used to view User Activity Logs (see “Monitor User Activity”
on page 56).
• Customer: Permits entering customer information which may then be associated with
services (see “Customers” on page 58).
3.2.1 Users View

The Net Manager Users View page, see Figure 3.3 (page 51) presents an overview of the
hierarchy of users created on the NetManager. The page is accessed by selecting NetMan-
ager Users View from the User Mgmt menu.
Note: General usage of the view pages is explained in “Interactive View Pages” on
page 41.

850176 P08
Figure 3.3: Net Manager Users View page
3.2.2 Managing User Accounts

3.2.2.1 Viewing User Accounts
Along with the default users for each Service Provider (see “Adding and Updating a Service
Provider Profile” on page 48), additional user accounts can be created. Each of these addi-
tional accounts is linked with a Service Provider; they are associated with one of the basic
categories (see “User Categories” on page 46) and each has its own username and pass-
word. The User Management feature permits the creation and modification of those
accounts and link them to a Service Provider profile. The Manage Users page is used to
create, update, and delete user accounts for a given Service Provider.
Note: Only Network Operator Administrators can create or delete user accounts

850176 P08
You can see

the different
user
accounts
associated
with each
Service Pro-
vider in this
page.
Figure 3.4: Manage Users page
This page lists each user account along with the following information:
Field Description
Login Name The username identifying the user account.

User Type The type of user, which determines the level of access for that
user account (see “User Categories” on page 46).
Table 3.4 Manage Users page fields
From this page, you can perform the following:
• Add/Update User Accounts: you can create or modify a user account. For more infor-
mation, see “Adding and Updating User Accounts” on page 52.
• Delete a User Account: you can delete User Accounts from the database. For more
information, see “Deleting User Accounts” on page 55.
3.2.2.2 Adding and Updating User Accounts

To update an existing User Account, select it from the Grid Table in the Manage Users
page and click the Update button. Network Operator Administrators can create a new User
Account by clicking the Add button. This brings up the Manage User property page as
shown in Figure 3.5 (page 53).

850176 P08
Note: For general information on how to add or update the records in the database,
see “Adding, Updating and Deleting Records” on page 37.
Figure 3.5: Manage User page
Modify the User Account as required and click the Update or Add button, the case being.
The User Account fields are described in Table 3.5 on page 54. If you are creating a new
user account, select the Service Provider to associate with this user from the Service Pro-
vider drop-down list.
Note: Once you have created a user account, you cannot change the Service
Provider to which it is associated.
Network Operator Administrators can change the Login Name and ACL settings of any
Service Provider user.

850176 P08
Field Description
Login The Username assigned to the user account.

Old Password When changing the password for an existing user account,
you must provide the current password as a security measure.
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.
Note: You should use a password that has at least

six alphanumeric characters.
Verify New Password Re-enter the password you typed in the New Password field
to validate it: the password you type in the Verify New
Password field must match the New Password field for the
operation to be accepted.
User Type The user type associated to this user account. This field is
editable when adding a new user, otherwise it will be grayed-
out. Possible values are listed in “User Categories” on page
46.
Note: The Network Operator type is only available if

no Service Provider was associated with the
new user account.
For more information on NO and SP types of users, see

“Accessing the NetManager Database” on page 46.
Primary Client IP First ACL address from which the user can connect to the
Address NetManager (see “Access Control List” on page 14).
Secondary Client IP Second ACL address from which the user can connect to the
Third Client IP Third ACL address from which the user can connect to the
Table 3.5 Manage User page fields
To return to the Manage Users page, click the < Back Manage User Table button.

850176 P08
3.2.2.3 Deleting User Accounts

To remove User Accounts from the database, select one or more items from the Grid Table
in the Manage Users page and click the Delete button.
Alternatively, you can open the property page for the User Account to delete (see “Adding
and Updating User Accounts” on page 52) and click the Delete button.
Note: Only Network Operator Administrators can delete user accounts.
Note: For more information on deleting records from the database, see “Deleting

850176 P08
3.2.3 Monitor User Activity

All user operations in NetManager are logged to the database: the Monitor User Activity
feature is used to examine the User Activity Logs. Every action a user performs on the Net-
Manager system is tagged with the time at which it was initiated and logged in the database,
along with the username, type of action, and the details of the action. You can view a list of
these logs by selecting Monitor User Activity from the User Mgmt menu in the navigation
bar (see Figure 3.6).
Figure 3.6: User Activity Log page
The user activity log displays a limited number of records per page, which can be scrolled
using the right-hand side scroll bar. You can navigate forward or backward a full page's
worth of entries using the following buttons:
• Next: moves forward one page of user activity log entries.

• Previous: moves backward one page of user activity log entries.
Note: The Previous button will not appear when the first page of the log is
displayed; similarly, the Next button will not appear when the last page of the
log is displayed.

850176 P08
The list displays the records sorted, by default, in reverse chronological order, i.e. latest log
item first. The following information is displayed for each entry:
Field Description
Username The user that initiated the action.

Action Type The type of action performed by the user. Possible types of
actions are:
• Database Insertion: when a record is inserted in the Net-
Manager database.
• Database update: when an existing database record is modi-
fied.
• Database deletion: when a record is deleted from the data-
base.
• Other operation: such as creation of a new user
Action Description A description of the action.
Occurrence Time The time at which the operation was performed. Time format
is the following: YYYY-MM-DD HH.mm.ss.ms.
Table 3.6 User Activity Log page fields
Log entries can be deleted from the database by entering the number of hours worth of logs
to keep in the appropriate edit-box at the top of the page and clicking the Remove button at
the bottom of the page; any log entry older than the specified number of hours will be
deleted from the database.
Note: Only the Network Operator Administrator has the right to delete entries from
the User Activity Log.
Note: If a Service Provider or user has been deleted, the logs associated to it are
preserved, but the Username field in each entry will be blank.

850176 P08
3.2.4 Customers
3.2.4.1 Viewing Customers
The Customer table page (see Figure 3.7) is used to create, update, and delete customer
records that can later be associated with services such as SIT Groups.
Figure 3.7: Customer Table page
This page lists each customer record along with the following information:
Field Description
Name The name associated with the customer.

Contact Name The name of the main contact person for this customer.
Phone The phone number where the Contact for the customer can be
reached.
Email The address where email can be sent for the customer.
Table 3.7 Customer Table page fields

850176 P08
From this page, you can perform the following:
• Add/Update Customer Records: you can create or modify a customer record. For
more information, see “Adding and Updating Customers” on page 59.
• Delete Customer Records: you can delete customer records from the database. For
more information, see “Deleting User Accounts” on page 55.
3.2.4.2 Adding and Updating Customers

To update an existing Customer record, select it from the Grid Table in the Manage Users
page and click the Update button, or to create a new Customer record, click the Add but-
ton. This brings up the Customer property page as shown in Figure 3.8.
Figure 3.8: Customer Property page
Modify the Customer Record as required and click the Update or Add button, the case
being. The Customer fields are described in Table 3.8.
Field Description
Name The name associated with the customer.

Contact Name The name of the main contact person for this customer.
Phone The phone number where the Contact for the customer can be
reached.
Email The address where email can be sent for the customer.
Table 3.8 Customer Property page fields
To return to the Customer Table page, click the < Back to Customer Table button.

850176 P08
3.2.4.3 Deleting Customer Records

To remove Customer records from the database, select one or more items from the Grid
Table in the Customer Table page and click the Delete button.
Alternatively, you can open the property page for the Customer to delete (see “Adding and
Updating Customers” on page 59) and click the Delete button.

850176 P08
Chapter 4 Populating Gateway Data into NetManager
This chapter is centered around the tasks needed to tell NetManager about the equipment
found on the Gateway. This is broken down into the following sections:
• “Configuring Equipment Overview” on page 62 is a general overview of the process of
building gateway equipment profiles, which will be detailed in the following sections.
• “Equipment View” on page 62 describes the graphical representation of all equipment
currently configured.
• “RLSS Profile” on page 64 details the process of building a Return Link equipment
profile in NetManager.
• “Equipment Wizard” on page 66 describes the NetManager Equipment configuration
Wizard.
• “Routers” on page 67 describes the configuration of Routers on the NetManager.
• “Performance Enhancement Proxy” on page 71 describes the configuration of a Flight
Protocol Performance Enhancing Proxy device and router selection.
• “QoS Device” on page 75 describes the configuration of a QoS device on the NetMan-
ager.
• “IP DVB Encapsulator Profiles” on page 80 details the process of building a Forward
Link equipment profile in NetManager.
• “ACM Adaptation Units” on page 87 allows for the configuration of the parameters
associated with the ACM Adaptation Unit.
• “Modulators” on page 91 allows for the configuration of parameters related to Modu-
lators.
• “SCPC Receivers” on page 95 displays a summary of the performance statistics of the
SCPC SITs.

850176 P08
4.1 Configuring Equipment Overview

Many of the constraints applied to traffic depend on the Gateway equipment, but NetMan-
ager does not have the ability to discover this equipment autonomously. Network Operators
are therefore required to configure NetManager with this information, ensuring that the traf-
fic configuration services provided by NetManager are accurate.
4.2 Equipment View

The Equipment View page represents graphically all the equipment currently configured in
the NetManager. Clicking on the first menu item, Equipment View, brings up the Equip-
ment View page as shown in Figure 4.1.
page 41.
Figure 4.1: Equipment View page
The CFG Equipment menu provides access to the configuration pages for the Gateway
equipment that the NetManager needs to know about.

850176 P08
The other menu items available for equipment configuration are:
Figure 4.2: CFG Equipment Sub-menus
• RLSS: permits configuration NetManager with Return Link Sub-System information

into the NetManager, see “RLSS Profile” on page 64.
• Equipment Wizard: guided configuration of NetManager equipment, see “Equipment
Wizard” on page 66.
• Routers: used to configure a Gateway’s Routers, see “Routers” on page 67.
• PEP: permits configuration of Performance Enhancing Proxy device information into
the NetManager, see “Performance Enhancement Proxy” on page 71.
• QoS Device: used for the configuration of NetManager related to a Quality of Service
Device, see “QoS Device” on page 75.
• IP/DVB Encapsulators: used for configuring NetManager with IP DVB Encapsulator
information, see “IP DVB Encapsulator Profiles” on page 80.
• ACM Adaptation Units: allows for the configuration of the transport VCM/ACM
commands, see “ACM Adaptation Units” on page 87.
• Modulator: allows for the configuration of parameters related to Modulators, see
“Modulators” on page 91.
• SCPC Receiver: allows configuration of the received satellite transponder, see “SCPC
Receivers” on page 95.
• System Admin: provides access to System Administration tasks (see “General Sys-
tem Administration” on page 325). This menu groups the following sub-items:
• Db/CM: Provides general configuration applicable to the database and Connection
Manager, see “System Administration” on page 326.
• FL QoS Rules: permits the configuration of Forward Link Quality of Service
Rules “FL QoS Rules” on page 333.

850176 P08
4.3 RLSS Profile

NetManager needs to access the Gateway’s RLSS configuration in order to provide accurate
Return Link management services. To provide this, Network Operators creates an RLSS
Profile.
To access the RLSS profile page, select the RLSS sub-menu item from the CFG Equip-
ment menu item of the navigation bar. The RLSS Profile page appears as shown in Figure
4.1.
If an RLSS profile 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 profile has already
been created. In this case, the page displays the current RLSS configuration and only the
update operation is possible.
Figure 4.3: RLSS Profile page
Modify the RLSS profile as required and click the Update or Add button, the case being.
The RLSS profile fields are described in Table 4.1 on page 65.
Note: Certain fields will only appear on the page depending on the current selection
in the RLSS Version field.

850176 P08
Field Description
Name The name of the RLSS.

Primary IP Address The primary IP Address of the RLSS.
Secondary IP Address The secondary IP Address of the RLSS 1.5.x
management interface.
RLSS Version The system version of the RLSS. Supported RLSS
versions are 1.5.x and 2.x.
RLSS manager IP Address The IP Address to connect to for the RLSS 1.5.x
management interface.
Note: the field is disabled if RLSS Version 2.x is

selected.
RLSS FTP Server Password Password of the FTP server used to save the RLSS
configuration.
Automatic Configuration Determines whether or not this RLSS should be
automatically updated when changes affecting its
routes, etc. are modified in the NetManager.
Table 4.1 RLSS Profile page fields
To return to the Service Provider page, click the < Back to Service Provider button.
From the RLSS Profile page, it is also possible to access the QoS Device related configura-
tion page by clicking the QoS Device > button, see “QoS Device” on page 75.
The Sync RL+FL button exports the RL and FL information to the RLSS database.
The Sync Mesh button exports the SIT Mesh specific information to the RLSS database.
The Sync SITS button exports the SIT Configuration within SIT group to the RLSS data-
base.
The Save Config button instructs the RLSS to Save its configuration.
The Import Config button imports the running configuration data from the RLSS currently
configured in the NetManager.
The RLSS Calibration button accesses the RLSS Configuration page where the operator
can configure the Frequency Translation Error, the attenuation on the received RF signal
(MIF Attenuation Level) and the Satellite Ephemeris Data.
The GPS Receiver button accesses the GPS Receiver Configuration page.

850176 P08
4.4 Equipment Wizard

The Equipment Wizard page (see Figure 4.4) permits fast initial configuration of the Net-
Manager. The page is accessed by selecting the Equipment Wizard item from the Naviga-
tion Bar’s CFG Equipment menu.
Figure 4.4: Equipment Wizard page
Table 4.2 shows the fields that can be configured.
Field Description
Redundant Gateway Determines whether the Gateway is in redundant

configuration.
QoS Device Serial Number The serial number for the Quality of Service device.
Aux QoS Device Serial The serial number for the auxiliary Quality of Service
Number device.
Transport Stream The Transport stream to use.
Automatic Configuration Determines whether or not the system will attempt
automatic configuration of enabled devices.
Table 4.2 Equipment Wizard page field
To start the configuration of the system using the Equipment Wizard, click the Add button.
Note: The RLSS configuration must have been imported prior to attempting to run
the Wizard.

850176 P08
4.5 Routers
A Gateway can be equipped with one to four Routers. Network Operators must configure
NetManager with information on the routers so they can later be used to configure Routes.
More than one Router can be configured on the system depending on the options selected.
4.5.1 Router Automatic configuration

The NetManager can configure automatically up to two pairs of redundant Riverstone rout-
ers (Router models RS1100, RS3100 and RS8000) with the following information:
• Routing via the IPE(s)

• Routing through the PEP
The configuration commands are sent via Telnet and all relevant configuration operations
on the NetManager database are propagated to the router(s). In case of suspected mismatch
between the router(s) and the NetManager configuration, the selected router(s) can be
resynchronized using the Synchronize button (see “Routers” on page 67).
The NetManager doesn’t support the automatic configuration of SIT routes for the other
router models (Cisco 28xx/38xx and Cisco ASA 5500 series). The NetManager only man-
age the configuration of routes in the Cisco ASA 5500 series and Cisco 28xx/38xx routers
in order to support Geographic Redundancy.
4.5.2 Routers
To view the Router profiles, select the Routers item from the CFG Equipment menu in the
navigation bar, bringing up the Routers page, see Figure 4.5.
Figure 4.5: Routers page

850176 P08
This page lists each Router profile along with basic information on it, see Table 4.3:
Field Description
Name The Router’s identifier.

Management IP The IP address used to access the Router’s management
Address features.
Router Model The model or make of the Router.
Main Router Shows if this is a main router.
IP Route Auto Config Shows if NetManager will automatically update the Router’s
parameters when routes are changed.
FP Accelerated Route Shows if NetManager will automatically update the Router’s
Auto Config parameters when Flight Protocol PEP routes are changed.
Tunneling Router Reflects whether or not the Router is Tunneling enabled.
Firewall Router Reflects whether or not the Router is a Firewall.
Table 4.3 Routers page fields
Network Operators can perform the following additional operations:
• Add/update Router profiles, see “Adding and Updating a Router” on page 69.
• Delete Router profiles, see “Deleting a Router” on page 71.
• Synchronize device configuration information by clicking the Synchronize button.
• Save to flash: commits the active configuration to flash memory of the selected router.

850176 P08
4.5.3 Adding and Updating a Router

To update an existing Router, select it from the Grid Table in the Routers page and click the
Update button, or to add a new Router, click the Add button. This brings up the Router
property page as shown in Figure 4.2.
Note: For more information on adding or updating the records in the database, see
Figure 4.6: Router page

850176 P08
Modify the Router as required and click the Update or Add button, the case being. The
Router fields are described in Table 4.4.
Field Description
Name The identifier for this Router.

Router Model The model of the router. The supported router models are:
• Riverstone RS1100, RS3100 and RS8000
• Cisco 28xx/38xx
• Cisco ASA 5500 Series (Firewall)
Management IP Address The IP Address used to access the Router’s management
features.
Router Function When the system is configured with both a QoS device
and a Flight Protocol PEP device, two routers have to be
configured. This option allows for selecting if this
particular router is the main or the auxiliary one. Possible
values are:
• Main
• Aux
Address Used For Next Allows for entering a statically set route Next Hop IP
Hop Address when this feature is needed.
Login Password The password used to login to the Router.
Enable Password The password used to enable the device.
IP Route Automatic Con- Select this to have NetManager attempt to automatically
figuration update the router’s configuration when routing changes are
made. This is useful for cases where a subnet based
network is not easily configurable.
Exports Routing information to SITs within the router, via
the appropriate IPE.
FP Accelerated Route Select this to have NetManager attempt to automatically
Automatic Configuration update the router’s configuration when Flight Protocol
PEP routing changes are made.
Table 4.4 Router page fields
To return to the Routers Grid Table page, click the < Back to Router Table button.

850176 P08
4.5.4 Deleting a Router

To remove Routers from the database, select one or more items from the Grid Table in the
Routers page and click the Delete button.
Alternatively, you can open the property page for the Router to delete (see “Adding and
Updating a Router” on page 69) and click the Delete button.
Note: For more information on deleting entities, see “Deleting Records from the
Database” on page 40.
4.6 Performance Enhancement Proxy

A device may be attached to the RLSS to provide acceleration for certain types of transfer
over the satellite link; the Performance Enhancement Proxies (PEPs) page (see Figure
4.7) allows for the configuration of such a device. A single Performance Enhancement
Proxy PEP device can be associated with the RLSS profile, although redundant units may
be configured. The page also allows Route Configuration management.
To access the Performance Enhancement Proxies (PEPs), select the PEP menu item
from the CFG Equipment menu in the navigation bar (see Figure 4.7).
Figure 4.7: Performance Enhancement Proxies (PEPs) page

850176 P08
If a Performance Enhancement Proxy profile does not exist, the Add button will be
enabled, indicating that an initial profile must be created. Modify the PEP profile as
required and click the Update or Add button, the case being. The PEP fields are described
in Table 4.6.
This page lists each PEP along with basic information on it, see Table 4.5:
Field Description
Satellite IP Address The PEP device’s satellite-side IP Address.

Terrestrial IP Address The PEP devices’s land-side IP Address.
Equipment Type The model of the PEP device.
Table 4.5 Performance Enhancement Proxies (PEPs) page fields
From this page, you can perform the following operations:
• Add/Update a PEP: you can create or modify a frequency band. For more informa-
tion, see “Adding and Updating a PEP” on page 73.
• Delete a PEP: you can select one or more frequency band from the Grid Table and
delete them from the database. For more information, see “Deleting a PEP” on page
74.

850176 P08
4.6.1 Adding and Updating a PEP

To update an existing PEP, select it from the Grid Table in the Performance Enhancement
Proxies (PEPs) page and click the Update button, or to add a new PEP, click the Add but-
ton. This brings up the Performance Enhancement Proxy property page as shown in Fig-
ure 4.8.
Figure 4.8: Performance Enhancement Proxy page

850176 P08
Modify the PEP as required and click the Update or Add button, the case being. The PEP
Field Description
RLSS Name The name of the RLSS to which this device belongs.
Satellite IP Address The Performance Enhancement Proxy PEP device’s
satellite-side IP Address.
Terrestrial IP Address The Performance Enhancement Proxy PEP devices’s land-
side IP Address.
Aux. Satellite IP Address The Performance Enhancement Proxy PEP device’s
secondary satellite-side IP Address.
Aux. Terrestrial IP Address The Performance Enhancement Proxy PEP device’s
secondary land-side IP Address.
PEP Type The type or manufacturer of the PEP device. The Advan-
tech-Technology Performance Enhancement Proxy PEP is
supported.
Automatic Configuration Determines whether or not the PEP server should be
automatically updated when changes affecting its
configuration are done in the NetManager.
Table 4.6 Performance Enhancement Proxy page fields
To return to the Performance Enhancement Proxies (PEPs) Grid Table page, click the <
Back to PEPs button.
4.6.2 Deleting a PEP

To remove PEP from the database, select one or more items from the Grid Table in the Per-
formance Enhancement Proxies (PEPs) page and click the Delete button.
Alternatively, you can open the property page for the PEP to delete (see “Adding and
Updating a PEP” on page 73) and click the Delete button.

850176 P08
4.7 QoS Device

A Gateway can be equipped with a device to manage Quality of Service. Network Opera-
tors must configure NetManager with information on the QoS device so that it can work in
collaboration with the device.
To access the QoS Device page, select the QoS Device item from the CFG Equipment
menu in the navigation bar, bringing up the QoS Device page, see Figure 4.9.
Figure 4.9: QoS Device page

850176 P08
This page lists the configuration parameters associated with the QoS device, see Table 4.7:
Field Description
RLSS Name The name of the RLSS to which the QoS device is associated.
Primary QoS Device
IP Address The IP address used to access the QoS device.
Mandatory Serial The serial number identifying the QoS device (Packeteer QoS
Number only).
Password The password used to modify the QoS device’s configuration.
Auxiliary QoS Device
IP Address The IP address used to access the redundant QoS device.
Mandatory Serial The serial number identifying the redundant QoS device
Number (Packeteer QoS only).
Password The password used to modify the redundant QoS device’s
configuration.
General Information
Device Version The version number of the QoS device.
QoS Device The type of the QoS device.
Enable TCP Rate When selected, enables the QoS device to control TCP rate
Control (Packeteer QoS only).
Automatic Configura- When this option is selected, NetManager will attempt to
tion automatically update the QoS device’s configuration when
changes are made to QoS settings.
SNMP Parameters
SNMP Port The Port that management services must use to connect to the
QoS device.
Get Community Name The community name that must be used by management
services that are only allowed read the QoS device
parameters.
Set Community Name The community name that must be used by management
services that are allowed to modify the QoS device
parameters.
Table 4.7 QoS Device Page fields

850176 P08
The Enable TCP Rate Control checkbox is not displayed when the QoS Device field is set
to SatNet QoS, see Figure 4.10.
Figure 4.10: Setting the QoS Device to SatNet QoS
When the QoS Device is set to Packeteer, the Serial Number for the Primary and Auxillary
QoS Device is required in the Mandatory Serial Number field, see Figure 4.11.
Figure 4.11: Mandatory Serial Number
When the QoS Device is set to SatNet QoS, the Username and Password field are required
for Telnet access, see Figure 4.12.
Figure 4.12: Telnet Access

850176 P08
If no QoS Device is configured, the Add button will be enabled, indicating that an initial
profile can be created. If the Add button is disabled, then a QoS Device has already been
created. In this case, the page displays the current QoS Device configuration and only the
update operation is possible.
Note: An RLSS profile must have been configured prior to adding a QoS device
profile.
Additional features/navigation for QoS Device Page:
From the QoS Device page, the following additional functionality is available:
• Clicking the Back to RLSS Profile > button navigates to the RLSS Profile (see
“RLSS Profile” on page 64).
• Clicking the Configuration Stats > button navigates to the QoS Device Configura-
tion Stats (see “QoS Device Configuration Statistics” on page 79).
Note: The Configuration Stats are only available when the QoS Device is set to
Packeteer.
4.7.1 Route-level QoS management in PacketShaper

The NetManager can automatically configure the entire PacketShaper SLA structure. The
NetManager sends configuration commands to the PacketShaper in XML format, which is a
relatively slow communication method. A configuration command may include many
objects, therefore can take minutes. During that time, the command is in “Processing” state.
As with the other equipment the NetManager automatically configures, the PacketShaper
can be re-synchronized in case a mismatch has occurred. This done by clicking the Syn-
chronize button.
Note: Due to the low speed of the interface, this command will take time, as the
entire SLA structure needs to be re-built.
Note: This operation will have side effects on traffic passing through the
PacketShaper and on stored statistics and accounting data.

850176 P08
4.7.2 Route-level QoS management in SatNet QoS

The NetManager can automatically configure the entire SatNet QoS SLA structure. The
NetManager sends configuration commands via SNMP. The SatNet QoS can be re-synchro-
nized in case a mismatch has occurred. This is done by clicking the Synchronize button.
4.7.3 QoS Device Configuration Statistics

This page displays the QoS device’s configurable traffic parameters along with information
on the number of each that are currently configured; QoS devices have a limited number of
traffic classification parameters: this page allows for the tracking of configuration parame-
ters during the configuration process to ensure that the device is not getting close to its con-
figuration capacity. This page is accessible by clicking the QoS Device Configuration
Stats button in the QoS Device page as shown in Figure 4.13
Figure 4.13: QoS Device Configuration Stats page

850176 P08
Table 4.8 describes the statistics displayed in the page.
Field Description
Description The name of the QoS configuration item reflected in the

statistic for the line.
Current The running count for this configuration item, reflecting how
many have been configured so far on the QoS device.
Remaining The inverse running count for this configuration item,
reflecting how many can still be configured on the QoS
device.
Total The maximum number of these items that can be configured
on the QoS device.
Static Reflects whether the total is a dynamic figure determined
based on other parameters, or if the maximum is a static value
that does not change.
• Yes: static value
• No: dynamic value
Table 4.8 QoS Device Configuration Stats fields
To return to the QoS Device page, click the < QoS Device button.
4.8 IP DVB Encapsulator Profiles

4.8.1 Encapsulator Configuration
NetManager needs to be configured with information on the IP DVB Encapsulators used by
the Gateway in order to provide accurate Forward Link management services. Network
Operators can perform this task by creating IP DVB Encapsulator profiles for each Trans-
port Stream on the Gateway. NetManager supports different types of IP DVB Encapsula-
tors.
4.8.1.1 SMR-25 Configuration

The NetManager configures the routing table (IP-MAC-PID association) of the SMR-25
using two ways:
• Through SNMP for the configuration updates limited to one SIT.

• Through the sending of the routing table by FTP for the configuration spanning multi-
ple SITs.

850176 P08
Along with the routing table, the route rate limiting is also configured (max rate). The Net-
Manager handles the configuration of redundant IPEs and configures the IP Forwarding In
port.
When a SIT is added, modified or deleted (including modifications to Routes such as route-
level QoS; see “IP Routes” on page 247), the NetManager automatically updates the SIT
routes in the SMR-25 through SNMP messages.
4.8.1.2 Novra IPE Configuration

The NetManager configures the routing table (IP-MAC-PID association) of the Novra by
configuring the structure of the Novra database. This structure can be mapped to the Net-
Manager structure as shown in Table 4.9.
NetManager Item Novra Structure Item
Transport Stream Transport Stream

SP FL SLA Traffic Profile
SG FL SLA PID
FL Route Route
Table 4.9 Novra Structure Mapping
The NetManager can configure redundant IPEs: when a resource is added, modified or
deleted (for example modifications to Routes such as QoS; see “IP Routes” on page 247),
the NetManager automatically updates the corresponding resource in the Novra by sending
XML commands encapsulated in HTTP requests.
4.8.1.3 Advantech IPE

The NetManager can configure the routing table (IP-MAC-PID) of an Advantech IPE. The
configuration of the Advantech IPE by the NetManager is done via SNMP. The NetMan-
ager supports the configuration of route level QoS in the Advantech IPE when no QoS
device is present in the system. The NetManager sends the required configuration com-
mands to the Advantech IPE (or a redundant pair if necessary) when a SIT is added, modi-
fied or deleted.

850176 P08
4.8.2 IP DVB Encapsulators

To view the IP DVB Encapsulator profiles, select the IP DVB Encapsulators item from the
CFG Equipment menu in the navigation bar, bringing up the IP DVB Encapsulators
page, see Figure 4.14.
Figure 4.14: IP DVB Encapsulators fields

850176 P08
This page lists each IP DVB Encapsulator profile along with basic information on it, see
Table 4.10:
Field Description
Name The text identifier for the IP DVP Encapsulator.

Management IP The IP address of the management interface for the IP DVB
Address Encapsulator.
Traffic IP Address The Traffic IP Address for the Encapsulator.
Transport Stream The numerical identifier for the transport stream on which
this IP DVB Encapsulator operates.
Equipment Type The manufacturer, or model of the IP DVB Encapsulator.
Auto Config Reflects whether or not the Encapsulator is enabled for
automatic configuration.
Table 4.10 IP DVB Encapsulators page fields
• Create/update IP DVB Encapsulator profiles, see “Adding and Updating an IP DVB

Encapsulator” on page 84.
• Delete IP DVB Encapsulator profiles, see “Deleting an IP DVB Encapsulator” on page
86.
• Clicking the Synchronize button triggers the export of the complete encapsulator con-
figuration.

850176 P08
4.8.3 Adding and Updating an IP DVB Encapsulator

To update an existing IP DVB Encapsulator, select it from the Grid Table in the IP DVB
Encapsulators page and click the Update button, or to add a new IP DVB Encapsulator,
click the Add button. This brings up the IP DVB Encapsulator property page as shown in
Figure 4.15 (page 84).
Figure 4.15: IP DVB Encapsulator page
Modify the IP DVB Encapsulator as required and click the Update or Add button, the case
being. The IP DVB Encapsulator fields are described in Table 4.11 on page 85.

850176 P08
Field Description
Name The text identifier for this IP DVB Encapsulator.
Note: This field is automatically assigned by the

NetManager system when adding a new IP DVB
Encapsulator and cannot be edited.
Primary Management IP The IP address to connect to in order to access the IP DVB

Address Encapsulator's management interface.
Primary Traffic IP The Traffic IP Address associated with the Encapsulator.
Address
Secondary Management The IP address to connect to in order to access the standby
IP Address IP DVB Encapsulator's management interface.
Secondary Traffic IP The Traffic IP Address associated with the standby
Address Encapsulator.
Virtual IP Address The virtual IP address used on redundant units.
(Redundant)
FTP Username The username configured on the Encapsulator’s FTP
interface.
FTP Login The login to use when accessing the Encapsulator’s FTP
interface.
DVB Encapsulator Type The IP DVB Encapsulator manufacturer and/or model.
Supported IP DVB Encapsulator types are:
• IPE-440
• SMR-25
• Opal v2
• DBN-24
• IPE-410
• Opal v3+
• Media Sputnik 1102
• Custom IPE 1
• Custom IPE 2
• SatNet IPE 222
• SatNet IPE 422
Table 4.11 IP DVB Encapsulator page fields

850176 P08
Field Description
Device Version The product version for the specific device you are
configuring.
Transport Stream The numerical identifier for the transport stream managed
by this IP DVB Encapsulator.
Section Packing This field determines if Section Packing is enabled on this
IPE. This field is only available for SatNet IPEs.
Automatic Route Config- Signals that the Encapsulator is enabled for automatic
uration Route configuration.
SNMP Parameters
SNMP Port The Port that management services must use to connect to
the encapsulator.
services that are only allowed read the encapsulator’s
parameters.
services that are allowed to modify the encapsulator’s
parameters.
Table 4.11 IP DVB Encapsulator page fields
To return to the IP DVB Encapsulators page, click the < Back to IP DVB Encap. Table
button.
4.8.4 Deleting an IP DVB Encapsulator

To remove IP DVB Encapsulators from the database, select one or more items from the
Grid Table in the IP DVB Encapsulators page and click the Delete button.
Alternatively, you can open the property page for the IP DVB Encapsulator to delete (see
“Adding and Updating an IP DVB Encapsulator” on page 84) and click the Delete button.

850176 P08
4.9 ACM Adaptation Units

The ACM Adaptation Units page allows for the configuration of the parameters associated
with the ACM Adaptation Unit. To view the ACM Adaptation Units page (see Figure
4.16.), select the ACM Adaptation Units item from the CFG Equipment menu in the nav-
igation bar.
Figure 4.16: ACM Adaptation Units page

850176 P08
This page lists each ACM Adaptation Units profile along with basic information on it, see
Table 4.12:
Field Description
Name The text identifier for this ACM Adaptation Unit.

Management IP The IP address used to access the ACM Adaptation Unit
Address management features.
Secondary Manage- The ACM Adaptation Unit’s redundant management IP
ment IP Address address.
Transport Stream The transport stream associated with the ACM Adaptation
Unit.
Equipment Type The make/model of the ACM Adaptation Unit.
Auto Config Shows if NetManager will automatically update the ACM
Adaptation Unit’s parameters when changes affecting them
are made.
Table 4.12 ACM Adaptation Units page fields

850176 P08
4.9.1 Adding and Updating an ACM Adaptation Unit

To update an existing ACM Adaptation Unit, select it from the Grid Table in the ACM
Adaptation Units page and click the Update button, or to add a new Router, click the Add
button. This brings up the ACM Adaptation Unit property page as shown in Figure 4.17.
Figure 4.17: ACM Adaptation Unit page

850176 P08
Modify the ACM Adaptation Unit as required and click the Update or Add button, the case
being. The ACM Adaptation Unit fields are described in Table 4.13.
Field Description
Name The text identifier for this ACM Adaptation Unit.

Primary Management IP The IP address to connect to the ACM Adaptation Unit’s
Address management interface.
Secondary Management The ACM Adaptation Unit’s redundant management IP
IP Address address.
ACM Adaptation Unit The make or model of the ACM Adaptation Unit,
type selectable from the drop-down list.
Device Version The product version for the specific device you are
configuring.
Transport Stream The Transport Stream associated with the ACM
Adaptation Unit, selectable from the drop-down list.
Automatic Configuration Select this to have NetManager attempt to automatically
update the ACM Adaptation Unit’s configuration when
changes affecting it are made.
SNMP Parameters
the ACM Adaptation Unit’s SNMP interface.
services that are only allowed read the ACM Adaptation
Unit’s parameters.
services that are only allowed read the ACM Adaptation
Unit’s parameters.
Table 4.13 ACM Adaptation Unit page fields
To return to the ACM Adaptation Units Grid Table page, click the < Back to Mau Table
button.

850176 P08
4.9.2 Deleting an ACM Adaptation Unit

To remove ACM Adaptation Units from the database, select one or more items from the
Grid Table in the ACM Adaptation Units page and click the Delete button.
Alternatively, you can open the property page for the ACM Adaptation Unit to delete (see
“Adding and Updating a Router” on page 69) and click the Delete button.
4.10 Modulators
To view the Modulators page (see Figure 4.18.), select the Modulator item from the CFG
Equipment menu in the navigation bar.
Figure 4.18: Modulators page

850176 P08
This page lists each Modulator profile along with basic information on it, see Table 4.14:
Field Description
Name The text identifier for this Modulator.

IP Address The Modulator’s main management IP address.
Aux IP Address The Modulator’s redundant management IP address, if
available.
Transport Stream The transport stream associated with the modulator.
Equipment Type The make/model of the Modulator.
IF Type IF frequency band at the output of the modulator.
Auto Config Shows if NetManager will automatically update the
Modulator’s parameters when changes affecting them are
made.
Table 4.14 Modulators page fields

850176 P08
4.10.1 Adding and Updating a Modulator

To update an existing Modulator, select it from the Grid Table in the Modulators page and
click the Update button, or to add a new Router, click the Add button. This brings up the
Modulator property page as shown in Figure 4.21.
Figure 4.19: Modulator page

850176 P08
Modify the Modulator as required and click the Update or Add button, the case being. The
Modulator fields are described in Table 4.13.
Field Description
Name The text identifier for this Modulator.

Modulator IP Address The Modulator’s management IP address.
Secondary Management The Modulator’s redundant management IP address.
IP Address
Modulator Type The make or model of the Modulator, selectable from the
drop-down list.
Transport Stream The Transport Stream associated with the Modulator,
selectable from the drop-down list.
NCR Restamping When enabled the modulator performs NCR restamping of
the incoming MPEG stream.
IF Type IF frequency band at the output of the modulator.
update the Modulator’s configuration when changes
affecting it are made.
SNMP Parameters
Note: Parameters only available for ATM-70 Modulator Type selection.
the Modulator’s SNMP interface.
services that are only allowed read the Modulator’s
parameters.
services that are only allowed read the Modulator’s
parameters.
Table 4.15 Modulator page fields
To return to the Modulators Grid Table page, click the < Back to Modulators button.

850176 P08
4.10.2 Deleting a Modulator

To remove Modulators from the database, select one or more items from the Grid Table in
the Modulators page and click the Delete button.
Alternatively, you can open the property page for the Modulator to delete (see “Adding and
Updating a Router” on page 69) and click the Delete button.
4.11 SCPC Receivers

To view the SCPC Receivers page (see Figure 4.20.), select the SCP Receiver item from
the CFG Equipment menu in the navigation bar.
Figure 4.20: SCPC Receivers page

850176 P08
This page lists each SCPC Receiver profile along with basic information on it, see Table
4.14:
Field Description
Name The text identifier for this SCPC Receiver.

Management IP The SCPC Receiver’s main management IP address.
Address
Auxiliary Manage- The SCPC Receiver’s redundant management IP address, if
ment IP Address available.
Auto Config Shows if NetManager will automatically update the SCPC
Receiver’s parameters when changes affecting them are
made.
Table 4.16 SCPC Receiver page fields

850176 P08
4.11.1 Adding and Updating a SCPC Receiver

To update an existing SCPC Receiver, select it from the Grid Table in the SCPC Receivers
page and click the Update button, or to add a new Router, click the Add button. This brings
up the SCPC Receiver property page as shown in Figure 4.21.
Figure 4.21: SCPC Receiver page

850176 P08
Modify the SCP Receiver as required and click the Update or Add button, the case being.
The SCPC Receiver fields are described in Table 4.17.
Field Description
Name The text identifier for this SCPC Receiver.

SCPC Receiver IP The SCPC Receiver’s management IP address.
Address
Auxiliary Management The SCPC Receiver’s redundant management IP address.
IP Address
SCPC Receiver Type The make or model of the SCPC Receiver, selectable from
the drop-down list.
update the SCPC Receiver’s configuration when changes
affecting it are made.
SNMP Parameters
the SCPC Receiver’s SNMP interface.
services that are only allowed read the SCPC Receiver’s
parameters.
services that are only allowed read the SCPC Receiver’s
parameters.
Table 4.17 SCPC Receiver page fields
To return to the SCPC Receivers Grid Table page, click the < Back to SCPC Receivers
button.
4.11.2 Deleting a SCPC Receiver

To remove SCPC Receivers from the database, select one or more items from the Grid
Table in the SCPC Receivers page and click the Delete button.
Alternatively, you can open the property page for the SCPC Receiver to delete (see “Add-
ing and Updating a Router” on page 69) and click the Delete button.

850176 P08
Chapter 5 Air Interface
This chapter contains the following sections:

• “Configuring Air Interface Overview” on page 100 presents an overview of Air Inter-
face configuration.
• “Default Values” on page 102 explains how to define default values used in populating
new Air Interface elements.
• “Frequency Plan” on page 105 covers Frequency Band management.
• “Return Link” on page 113 explains the configuration of RL elements.
• “Forward Link” on page 127 covers Transport Stream configuration.

850176 P08
5.1 Configuring Air Interface Overview

5.1.1 Frequency Plan Management
NetManager not only has the capability of managing bit rate allocation, but it can also man-
age Frequency allocation. Frequency Plan management consists in separating Transport
Streams and Superframes into Frequency Bands. Different levels of control in the manage-
ment of Frequency Plan are afforded by the NetManager:
1. Frequency Plan management can be left solely to the RLSS; i.e. Frequency Bands are
configured on the RLSS, and then imported in the NetManager through the RLSS’s
exported configuration file (see “Importing RLSS Configurations” on page 138).
2. Basic modifications to Frequencies imported from the RLSS can be made in the
NetManager, which are then pushed back to the RLSS.
3. Superframes imported from the RLSS can be placed in Frequency Bands and re-
ordered using the Frequency Band Components tool (see “Viewing Frequency Band
Components” on page 109).
4. Frequency Bands and Superframes can be created directly on the NetManager (reading
only Transport Steams from the RLSS) and then configured completely using the
Frequency Band Components tool (see “Viewing Frequency Band Components” on
page 109), to be finally pushed back to the RLSS.
5.1.2 Air Interface View

The CFG Air Interface menu provides access to the configuration tools needed for Flight
Plan management.
Clicking on the first menu item, Air Interface View, brings up the Air Interface View
page, see Figure 5.1 (page 101) that graphically represents the NetManager Air Interface
components.
page 41.

850176 P08
Figure 5.1: Air Interface View page
The other menu items available for equipment configuration are:
Figure 5.2: Air Interface Sub-menus
• Default Values: allows the user to define default values used in populating new Air
Interface elements, see “Default Values” on page 102.

850176 P08
• Frequency Plan: This menu item groups sub-items relevant to Frequency Plan man-
agement (see “Frequency Plan” on page 105), namely:
• Frequency Bands: provides access to the configuration of Frequency Bands, see
“Viewing Frequency Bands” on page 105.
• Frequency Band Components: allows for the configuration of the components
making up Frequency Bands, see “Viewing Frequency Band Components” on page
109.
• Return Link: This menu item groups sub-items relevant to RL management (see
“Return Link” on page 113), namely:
• Superframes: allows for the configuration of Superframes, see “Viewing Carrier
Sets (Superframes)” on page 113.
• Areas: allows for the configuration of Areas, see “Viewing Areas” on page 118.
• Partitions (segments): allows for the configuration of partitions, see “RL Parti-
tions (Segments)” on page 123.
• Forward Link: This menu item groups sub-items relevant to FL management (see
“Forward Link” on page 127), namely:
• Tx Mode: provides access to Tx Modes (MODCODs) configuration, see “Tx
Mode” on page 127.
• Transport Streams: provides access to Transport Stream configuration, see
“Transport Streams” on page 130.
5.2 Default Values

The Default Values page allows the user to define some of the default values to be used
when populating new Air Interface elements: whenever a new element containing one of
these fields is created, the relevant fields will be populated with the values in this page as a
starting point for editing the element.
Note: Changing a value in this page does not affect values in already created/
configured Air Interface elements; values in this page can therefore be safely
changed without any impact on current NetManager configuration.

850176 P08
Clicking on the Default Values menu item from the CFG Air Interface menu in the navi-
gation bar brings up the Default System Values page (see Figure 5.3).
Figure 5.3: Default System values page
Table 5.1 explains the system parameters.
Field Description
MSL (multi-frames) This is the default macro synchronization of the

system, offsetting increased satellite transmission time.
Typical value used for a frame is 26.6 ms.
Frame Downconversion Default value to subtract from Frequency Plan
(MHz) reception frequency
RBDC Timeout (frames) The default RBDC timeout value.
Rain-Fade Countermeasures Thresholds
Increase Protection Mode The default threshold to use for moving to a higher
Threshold (DB) RFCM protection mode.
Decrease Protection Mode The default threshold to use for moving to a lower
Threshold (DB) RFCM protection mode.
Table 5.1 Default System values page fields

850176 P08
Field Description
FLCM Parameters
Port The default port used for FLCM transmission.
Data Rate (Kbit/s) The default FLCM data rate.
Block Size (Packets/Retry The default block size used for FLCM data.
Block)
Retry count The default number of retries for FLCM transmission.
Table 5.1 Default System values page fields
• Update: you can modify a system default value and save it into the database.
To navigate back to the Service Provider page, click the < Back To Service Provider but-
ton.

850176 P08
5.3 Frequency Plan

5.3.1 Viewing Frequency Bands
To access the Frequency Bands page (see Figure 5.4), select the Frequency Bands item
from the Frequency Plan sub-menu in the Navigation Bar’s CFG Air Interface menu.
Figure 5.4: Frequency Bands page
This page lists each Frequency Band Component with the parameters listed in Table 5.2.
The frequency band components can be displayed in either Uplink frequency or Downlink
frequency. When Uplink is selected from the Frequency Display Choice drop down list,
the frequency bands are displayed without satellite translation applied. When Downlink is
selected, the frequency bands are displayed with the satellite translation frequency
substracted. Select All displays all the components, regardless of frequency.
Field Description
Frequency Band The name of the Frequency Band.

Start Frequency (Hz) The Frequency Band’s lowest frequency edge.
End Frequency (Hz) The Frequency Band’s highest Frequency edge.
Table 5.2 Frequency Bands page fields

850176 P08
RL Beam The Return Link to which the Frequency Band is

associated.
FL Beam The Forward Link to which the Frequency Band is
associated.
Table 5.2 Frequency Bands page fields
• Add/Update a frequency band: you can create or modify a frequency band. For more
information, see “Adding and Updating a frequency band” on page 106.
• Delete a frequency band: you can select one or more frequency band from the Grid
Table and delete them from the database. For more information, see “Deleting a fre-
quency band” on page 108.
5.3.1.1 Adding and Updating a frequency band

This feature allows you to manually add a new frequency band for NetManager to manage,
or modify the attributes of a frequency band already in the system.
To update a frequency band, select it from the Grid Table in the Frequency Bands page and
click the Update button, or to add a new frequency band, click the Add button. This brings
up the Frequency Band property page as shown in Figure 5.5 (page 107).

850176 P08
Figure 5.5: Frequency Band page

850176 P08
You can modify the frequency band as required and click the Update or Add button, the
case being, to commit your changes. The frequency band fields are described in Table 5.3:
Field Description
Name The name that identifies the frequency band.

Frequency Display Uplink: The frequency bands are displayed without any
Choice satellite translation applied.
Downlink: The frequency bands are displayed with the satellite
translation frequency substracted.
Uplink Start Fre- The lower frequency edge for the Frequency Band.
quency (Hz)
Uplink End Fre- The higher frequency edge for the Frequency Band.
quency (Hz)
Frequency Span (Hz) Displays the width of the Frequency Band.
Satellite translation The frequency translation offset of the satellite
Offset
Satellite The satellite to which this Frequency Band is associated.
RL Beam The Return Link beam to which the Frequency Band is
associated.
FL Beam The Forward Link beam to which the Frequency Band is
associated.
Table 5.3 Frequency Band page fields
The lower part of the page presents a graphical outline of the Frequency Band as it is cur-
rently configured, displaying the Transport Streams, Superframes and Frequency Guards,
when applicable. The components for this Frequency Band can be configured by clicking
Freq. Band Components > button (see “Viewing Frequency Band Components” on page
109).
To return to the Frequency Bands page, click the < Back to Frequency Band button.
5.3.1.2 Deleting a frequency band

To remove frequency bands from the database, select one or more items from the Grid Table
in the Frequency Bands page and click the Delete button.
Alternatively, you can open the property page for the Frequency Band to delete (see “Add-
ing and Updating a frequency band” on page 106) and click the Delete button.

850176 P08
Note: For more information on removing records from the database, see “Deleting
5.3.2 Viewing Frequency Band Components

There are two ways to access to access the Frequency Band Components page (see Figure
5.6): directly from the Navigation Bar’s CFG Air Interface menu, by selecting the Fre-
quency Bands item from the Frequency Plan sub-menu; alternatively, by editing a Fre-
quency Band (see “Adding and Updating a frequency band” on page 106) and then clicking
the Freq. Band Components > button.
Figure 5.6: Frequency Band Components page

850176 P08
The page lists each Frequency Band Component with the parameters listed in Table 5.4. A
filter based on Frequency Band can be applied to the Components displayed; this is done by
selecting the desired Frequency Band from the Frequency Band drop down list at the top
of the page.
The frequency band components can be displayed in either Uplink frequency or Downlink
frequency. When Uplink is selected from the Frequency Display Choice drop down list,
the frequency bands are displayed without satellite translation applied. When Downlink is
selected, the frequency bands are displayed with the satellite translation frequency
substracted.
Selecting All displays all Components, regardless of Frequency Band or Frequency Display
Choice.
Field Description
Sequence Number The sequence number associated with the component.

Frequency Band Compo- The name given to the component.
nent
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.
Config Commit Pending Indicates that a committed frequency band component
change is pending.
Table 5.4 Frequency Band Components page fields
The page provides the tools and links necessary to build and configure a Frequency Band. It
is possible to manually create or associate components to the Frequency Band:
• Transport streams: existing Transport Streams can be associated to the Frequency

Band using the Assign Transport Stream button (see “Transport Streams” on page
130); alternatively, new ones can be added using the Add Transport Stream button
(see “Adding and Updating a Transport Stream” on page 132).
• Superframes: existing Superframes can be associated to the Frequency Band using
the Assign Superframe button (see “Viewing Carrier Sets (Superframes)” on page
113); alternatively, new ones can be added using the Add Superframe button (see
“Adding and Updating a Carrier Set (Superframe)” on page 114).
• Frequency Guard: new Frequency Guard components can be added to the Frequency
Band using the Add Frequency Guard button; existing ones can also be edited using
the Update Frequency Guard button (see “Adding and Updating a frequency guard”
on page 111).

850176 P08
• Frequency Plan Activation: provides access to the Frequency Plan Activation page
(see
Throughout the process of configuring components in a Frequency Band, it is possible to
change their relative positions with respect to one another; this is done by selecting a com-
ponent and clicking either the Move Up or Move Down buttons to shift it one position up
or down.
Finally, you can delete one or more component from the Frequency Band by selecting the
desired components and clicking the Delete button.
5.3.2.1 Adding and Updating a frequency guard

Frequency Guards are used as “buffer” areas between other Frequency Band Components.
To update a frequency Guard, select it from the Grid Table in the Frequency Band Compo-
nents page and click the Update Frequency Guard button, or to add a new frequency
guard, click the Add Frequency Guard button. This brings up the Frequency Guard
Figure 5.7: Frequency Guard page

850176 P08
The Frequency Guard fields are described in Table 5.5:
Field Description
Frequency Band The name of the Frequency Band to which this Frequency
Guard is associated.
Name The name of this Frequency Guard.
Sequence Number The sequence number for the Frequency Guard, representing its
position in the Frequency Band.
Occupied Band- The width of the Frequency Guard.
width (Hz)
Center Frequency The center frequency for the Frequency Guard.
(Hz)
Table 5.5 Frequency Guard page fields
You can modify the frequency guard as required and click the Update or Add button, the
case being, to commit your changes.
To return to the Frequency Band Components page, click the < Back to Freq. Band
Comp. button.
5.3.3 Frequency Plan Activation

This page is used to activate a configured frequency plan. The steps involved in performing
the automatic configuration of a new frequency plan are as follow:
1. The operator performs some changes to the Forward Link or Return Link frequency
plan.
2. The operator selects a frequency band component that has been modified and has its
Config Commit Pending flag set to YES and press the Frequency Plan Activation
button. Alternatively, the operator can press the Frequency Plan Activation button
when no Frequency Band Component is selected to activate all the modified
Frequency Band Components.
3. From the Frequency Plan Activation page, the operator enters a duration for which
the SCS commands are send and press the Start button. The SCS will configure the
alternate Transport Stream acquisition parameters in each of the SITs affected by the
modified frequency plan.
4. Once the duration entered previously finishes or if the operator presses the Terminate
Countdown button, the box labelled NIT/RMT modifications will turn green.
5. If the version of the RLSS is older than 2.4.2.5, the operator has to configure manually
the IPE with the NIT and RMT parameters displayed on the page.

850176 P08
6. Once the operator has completed the configuration of the IPE or if the RLSS is
configured to send the Forward Link signalling than the operator can now press the
NIT/RMT modifications button.
7. The Commit button will now be enabled. The operator must now press the Commit
button to activate all the configuration changes in the Gateway equipments.
8. Once the configuration changes of the Gateway equipments are completed, the SCS
commands on prime TS parameters button will turn green.
9. The operator has to enter a duration for which the SCS commands are send 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.
10.The new Frequency Plan has now been activated.
5.4 Return Link

5.4.1 Viewing Carrier Sets (Superframes)
There are two ways to access to access the Carrier Sets (Superframes) page (see Figure
5.8): directly from the Navigation Bar’s CFG Air Interface menu, by selecting the Carrier
Sets (Superframes) item from the Return Link sub-menu; alternatively, by viewing the
list of components making up a Frequency Band (see “Viewing Frequency Band Compo-
nents” on page 109) and then clicking the Assign Superframe button.
Figure 5.8: Carrier Sets (Superframes) page

850176 P08
This page lists each Superframe with the following parameters:
Field Description
Name The name that identifies the superframe.

ID The specific identification number.
Frame Type The type of frame for this Superframe.
Receiver The Receiver handling this Superframe.
Uplink Center Frequency The uplink center frequency for the Superframe.
(Hz)
Down Conversion (Hz) The value to subtract from Frequency Plan reception
frequency.
Freq. Band The Frequency Band to which this Superframe is
associated.
Table 5.6 Carrier Sets (Superframes) page fields
• Add/Update a Carrier Set (Superframe): you can create or modify a superframe.

For more information, see “Adding and Updating a Carrier Set (Superframe)” on page
114.
• Delete a Carrier Set (Superframe): you can select one or more superframe from the
Grid Table and delete them from the database. For more information, see “Deleting a
Carrier Set (Superframe)” on page 117.
5.4.1.1 Adding and Updating a Carrier Set (Superframe)

To update a superframe, select it from the Grid Table in the Carrier Set (Superframes)
page and click the Update button, or to add a new superframe, click the Add button. This
brings up the Carrier Set (Superframe) property page as shown in Figure 5.9. The page
can also be reached by viewing the list of components making up a Frequency Band (see
“Viewing Frequency Band Components” on page 109) and clicking the Add button.
When adding a carrier set, a field called “Create Simple RL & SLA” is displayed in the
Carrier Set (Superframe) page. When check, the NetManager will automatically create a
single Area, a single Segment and a Low-Level RL SLA for that carrier set.

850176 P08
Figure 5.9: Carrier Set (Superframe) page

850176 P08
The carrier set fields are described in Table 5.7.
Field Description
Name The name that identifies the Carrier Set.

ID The numerical identifier for the Carrier Set.
SCPC Dedicated When enabled, indicate that the carrier set is dedicated to SCPC
Return Links.
Burst Type The burst type for the Carrier Set.
Possible values are:
• ATM1
• ATM2
• IP
• MPEG
Coding Type The coding type for the Carrier Set.
• Concatenated
• Turbo
• None
Carrier Spacing The spacing between carriers.
DVB-RCS Parameters
Frame Type The type of frame for the Carrier Set.
RLSS Name The name of the managing the Carrier Set.
MCD The MCD handling the Carrier Set.
Create Simple RL & When adding a Carrier Set, this tell the NetManager to
SLA automatically create an Area, a Segment and Low-level RL
SLA.
Symbol rate (sym- The Symbol rate.
bols/s)
Frequency Band The Frequency Band to which the Carrier Set is associated.
Uplink Center Fre- The uplink center frequency for the Carrier Set.
quency (Hz)
Table 5.7 Carrier Set (Superframe) page fields

850176 P08
Field Description
Occupied Band- The width of the Superframe.

width (Hz)
Down Conversion The value to subtract from Frequency Plan reception
(Hz) frequency.
Table 5.7 Carrier Set (Superframe) page fields
You can modify the superframe as required and click the Update or Add button, the case
being, to commit your changes.
To return to the Carrier Sets (Superframes) page, click the < Back to Carrier Sets but-
ton.
You can also navigate back to the Frequency Band Components page by clicking < Back
to Freq. Band Components > button (see “Viewing Frequency Band Components” on
page 109).
5.4.1.2 Deleting a Carrier Set (Superframe)

To remove superframes from the database, select one or more items from the Grid Table in
the Carrier Sets (Superframes) page and click the Delete button.
Alternatively, you can open the property page for the carrier set (superframe) to delete (see
“Adding and Updating a Carrier Set (Superframe)” on page 114) and click the Delete but-
ton.

850176 P08
5.4.2 Viewing Areas

To access the Areas page (see Figure 5.10), select the Areas item from the Return Link
sub-menu in the navigation bar’s CFG Air Interface menu.
Figure 5.10: Areas page
The page displays each Area with the parameters listed in Table 5.8. A filter based on
Superframe can be applied to the Areas displayed; this is done by selecting the desired
Superframe from the Carrier Set (Superframe) drop down list at the top of the page (or
selecting All to display all Areas, regardless of Superframe).
Field Description
Name The name that identifies the Area.

ID The numerical identifier for the Area.
Size (Kbit/s) The bandwidth size of the Area.
FCA (Kbit/s) The FCA traffic bandwidth.
Table 5.8 Areas page fields

850176 P08
Carrier Set ID The ID of the Superframe to which the Area belongs.

Transport Stream ID The identifier of the Transport Stream associated with
the Area.
Table 5.8 Areas page fields
• Add/Update an Area: you can create or modify an Area. For more information, see
“Adding and Updating an Area” on page 119.
• Delete an Area: you can select one or more area from the Grid Table and delete them
from the database. For more information, see “Deleting an Area” on page 122.
5.4.2.1 Adding and Updating an Area

To update an Area, select it from the Grid Table in the Areas page and click the Update
button, or to add a new Area, click the Add button. This brings up the Area property page
as shown in Figure 5.11.
The Area page can alternatively be reached by viewing the list of Segments (see “RL Parti-
tions (Segments)” on page 123) and clicking one of the bold area names under the Area
Name column.

850176 P08
Figure 5.11: Area page
The area fields are described in Table 5.9:
Field Description
Name The name that identifies the Area.

ID The numerical identifier for the Area.
Assignment
Frequency Band The Frequency Band to which the Area is associated.
Carrier Set ID The Superframe to which the Area belongs.
Transport Stream The Transport Stream associated with the Area.
Id
Scheduling Parameters
Available Capacity / The capacity parameters based on the Superframe associated
Max Capacity / with the Area.
Granularity (kbit/s)
Table 5.9 Area page fields

850176 P08
Field Description
Size (kbit/s) The size of the Area.

FCA value (kbit/s) The FCA bandwidth for the Area.
Minimum Schedul- The minimum scheduling latency for the Area, in number of
ing Latency (frames)
frames.
Start Carrier Num- The starting carrier number.
ber
Number of carriers The number of carriers in the Area.
Table 5.9 Area page fields
You can modify the Area as required and click the Update or Add button, the case being, to
commit your changes.
To return to the Areas page, click the < Back to Scheduling Blocks button.
You can also directly manage the RL Partitions associated with this Area by clicking the
Segments > button (see “RL Partitions (Segments)” on page 123).
5.4.2.2 Mesh
Mesh requires the creation of a unique area in the Superframe, with only one carrier.
A Superframe (see “Viewing Carrier Sets (Superframes)” on page 113) must be configured
with a mesh-compatible frame type; the Frames must have the following common proper-
ties:
• Burst Type = ATM1 or ATM2

• Coding Type = Turbo
• Carrier Spacing = 1.25
Note: The frame type name should have the word "Mesh" as part of its name.

850176 P08
At least one SIT must then be set to Mesh Enabled (see “Adding and Updating a SIT Pro-
file” on page 227); SITs can then be configured for inclusion in the Mesh by linking their
LL-RL-SLA with the proper Area and Segment (see “Updating a Low Level Return Link
SLA” on page 166). Since all mesh traffic originates from a SIT, at least one traffic queue of
type Mesh_Queue must be configured (see “Adding and Updating a Traffic Queue” on
page 242).
5.4.2.3 Deleting an Area

To remove Areas from the database, select one or more items from the Grid Table in the
Areas page and click the Delete button.
Alternatively, you can open the property page for the Area to delete (see “Adding and
Updating an Area” on page 119) and click the Delete button.

850176 P08
5.4.3 RL Partitions (Segments)

There are two ways to access to access the RL Partitions (Segments) page (see Figure
5.12): directly from the Navigation Bar’s CFG Air Interface menu, by selecting the Parti-
tions (Segments) item from the Return Link sub-menu; alternatively, by editing a given
Area (see “Adding and Updating an Area” on page 119) and clicking the Segments > but-
ton.
Figure 5.12: RL Partitions (segments) page

850176 P08
The page lists each Partition (Segment) with the parameters listed in Table 5.10. A filter
based on Area can be applied to the Segments displayed; this is done by selecting the
desired Area from the Scheduling Block (Area) drop down at the top of the page (or select-
ing All to display all Segments, regardless of Area).
Field Description
ID The numerical segment identifier.

Name The name that identifies the Partition.
Scheduling Block Name The Area to which the Partition belongs.
Traffic Capacity (kbit/s) The traffic capacity for the Partition.
RBDC max (kbit/s) The maximum value for RBDC.
FCA (kbit/s) The FCA traffic associated with the Partition.
Table 5.10 RL Partitions (Segments) page fields
• Add/Update a Partition: you can create or modify a Partition. For more information,
see “Adding and Updating a Partition” on page 124.
• Delete a Partition: you can select one or more Partition from the Grid Table and
delete them from the database. For more information, see “Deleting a Partition” on
page 126.
5.4.3.1 Adding and Updating a Partition

To update a Partition, select it from the Grid Table in the RL Partitions (Segments) page
and click the Update button, or to add a new Partition, click the Add button. This brings up
the RL Partition (Segment) property page as shown in Figure 5.13 (page 125).

850176 P08
Note: For more information on adding or updating the records in the database, see “Adding,
Updating and Deleting Records” on page 37.
Figure 5.13: RL Partition (Segment) page
You can modify the Partition as required and click the Update or Add button, the case
being, to commit your changes. The Partition fields are described in Table 5.11:
Field Description
Area The Area associated with the Partition.

Name The name that identifies the Partition.
Segment ID The Segment to which the Area belongs.
Persistent Traffic The RBDC timeout for the Partition.
(RBDC) Timeout
Capacities
Table 5.11 Partition (Segment) page fields

850176 P08
Field Description
Burstable Determines if the Partition is burstable.

Maximum Capacity The maximum capacity that can be carried by the Partition.
(kbit/s)
Maximum Avail- The maximum capacity of the Area to which the Partition
able Capacity in belongs.
Area (kbit/s)
Granularity (slot The Partition’s slot size.
size) (kbit/s)
Guaranteed Capac- The Partition’s guaranteed capacity.
ity (kbit/s)
Persistent Traffic The partition RBDC traffic.
(RBDC) (kbit/s)
Left-over Capacity The left over capacity associated with the Partition.
(FCA) (kbit/s)
RFCM Thresholds
Increase Protection The threshold at which to upgrade to a higher RFCM protection
Mode Threshold mode.
(dB)
Decrease Protection The threshold at which to downgrade to a lower RFCM
Mode Threshold protection mode.
(dB)
Table 5.11 Partition (Segment) page fields
To return to the RL Partitions (Segments) page, click the < Back to RL Partitions button.
You can also navigate directly to the Area property page for the Area to which this Partition
belongs by clicking the < Back to Scheduling Block button (see “Adding and Updating an
Area” on page 119).
5.4.3.2 Deleting a Partition

To remove Partitions from the database, select one or more items from the Grid Table in the
RL Partitions (Segments) page and click the Delete button. Alternatively, you can open
the property page for the Partition to delete (see “Adding and Updating a Partition” on page
124) and click the Delete button.

850176 P08
5.5 Forward Link

5.5.1 Tx Mode
There are two ways to access the Tx Mode page (see Figure 5.14): directly from the Navi-
gation Bar’s CFG Air Interface menu, by selecting the Tx Mode item from the Forward
Link sub-menu.
Figure 5.14: Tx Modes page

850176 P08
The page lists each Tx Mode with the parameters listed in Table 5.12. Selecting All displays
all Tx Modes.
Field Description
Name Name of the Tx mode.

MODCOD The MODCOD (modulation coding) of this Tx mode.
CNI threshold This value is set automatically and represents the ideal
CNI (signal to noise ratio) threshold for the selected
MODCOD. This value is used as the default CNI
threshold. CNI thresholds are used by the SITs to
determine when to request a MODCOD change.
CNI Threshold If set, this value will override the ideal CNI threshold.
CNI Threshold margin If set, this value is added to the CNI threshold value.
Short Frame When enabled, this MODCOD used short FECFRAME
length of 16 200 bits. When disables, this MODCOD
used normal FECFRAME length of 64 800 bits.
With Pilots When enabled, pilot blocks are inserted every 16 slots
into the FECFRAME to help the receiver
synchronization.
Table 5.12 Tx Mode page fields
• Add/Update a Tx Mode: you can create or modify a Tx Mode. For more information,
see “Adding and Updating a Tx Mode” on page 128.
• Delete a Tx Mode: you can select one or more Tx Mode from the Grid Table and
delete them from the database. For more information, see “Deleting a Tx Mode” on
page 130.
5.5.1.1 Adding and Updating a Tx Mode

To create or update a Tx Mode, select it from the Grid Table in the Tx Modes page and
click the Add or Update button, depending on the requirement, to bring up the Tx Mode

850176 P08
Figure 5.15: Tx Mode page
You can modify the Tx Mode as required and click the Update or Add button, the case
being, to commit your changes. The Tx Mode fields are described in Table 5.13:
Field Description
Name Name of the Tx mode.

MODCOD The MODCOD (modulation coding) of this Tx mode.
Ideal CNI threshold This value is set automatically and represents the ideal
CNI (signal to noise ratio) threshold for the selected
MODCOD. This value is used as the default CNI
threshold. CNI thresholds are used by the SITs to
determine when to request a MODCOD change.
CNI Threshold If set, this value will override the ideal CNI threshold.
CNI Threshold margin If set, this value is added to the CNI threshold value.
Short Frame When enabled, this MODCOD used short FECFRAME
length of 16 200 bits. When disables, this MODCOD
used normal FECFRAME length of 64 800 bits.
With Pilots The PCR inserter bit rate.
Table 5.13 Tx Mode page fields
To return to the Tx Modes page, click the < Back to Tx Mode Table button.

850176 P08
5.5.1.2 Deleting a Tx Mode

To remove Tx Modes from the database, select one or more items from the Grid Table in the
Tx Modes page and click the Delete button. Alternatively, you can open the property page
for the Tx Mode to delete (see “Adding and Updating a Tx Mode” on page 128) and click
the Delete button.
5.5.2 Transport Streams

There are two ways to access the Transport Streams page (see Figure 5.16): directly from
the Navigation Bar’s CFG Air Interface menu, by selecting the Transport Stream item
from the Forward Link sub-menu; alternatively, by viewing the list of Frequency Band
Components (see “Viewing Frequency Band Components” on page 109) for a Given Fre-
quency Band, and clicking the Assign Transport Stream button
The Transport Streams page displays values in both Configuration and PIDs mode. To dis-
play the Transport Streams page in either mode, select the appropriate tab, see Figure 5.16.
Figure 5.16: Transport Streams page

850176 P08
5.5.2.1 Transport Streams Page in Configuration Mode

The Configuration tab allows for the configuration of the Transport Stream. Figure 5.17
shows the fields available in Configuration Mode.
Figure 5.17: Fields Available in the Configuration Tab
Table 5.14 below gives a description of each field in the Configuration tab.
Field Description
Transport Stream The numerical identifier for the Transport stream.

TS bit rate (kbit/s) Bit rate of the transport stream.
DVB-S2 Indicates whether or not this Transport Streams is
associated with DVB-S2.
DVB S2 Mode Indicate if the DVB S2 transport stream is in CCM,
VCM or ACM mode.
Modulation Scheme For a DVB S2 transport stream, indicate if the
modulation is QPSK, 8PSK, 16APSK or 32APSK.
Symbol Rate (symb/s) The symbol rate.
Coding Rate The coding rate.
Roll-Off Factor The roll-off factor.
Uplink Center Frequency The Transport Stream’s center frequency.
(Hz)
Frequency Band The Frequency Band to which the Transport Stream is
associated.
Table 5.14 Transport Streams page fields in Configuration Mode

850176 P08
5.5.2.2 Transport Streams Page in PIDs Mode

The Packet Identifiers (PIDs) tab allows for setting up the traffic for a given Transport
Stream. Figure 5.18 shows the fields available in Configuration Mode.
Figure 5.18: Fields Available in the PIDs Tab
Table 5.15 below gives a description of each field in the PIDs tab.
Field Description

FLS Service ID ID for the FLS Service.
IP/DVB Service ID ID for the IP/DVB Service.
RMT Service ID ID for the RMT Service.
Comp Table PID PID for the Comp Table.
Terminal Table PID PID for the Terminal Table.
PCR PID PID for the PCR.
MMT PID PID for the Multicast Map Table.
TMST PID PID for theTMST.
RMT PID PID for the RMT.
Table 5.15 Transport Streams page fields in PIDs Mode
From the Transport Streams page, you can also perform the following operation:
• Add or Update a Transport Stream: you can modify an existing Transport Stream.
For more information, see “Adding and Updating a Transport Stream” on page 132.
5.5.2.3 Adding and Updating a Transport Stream

To create or update a Transport Stream, select it from the Grid Table in the Transport
Streams page and click the Add or Update button to bring up the Transport Stream prop-
erty page as shown in Figure 5.19.

850176 P08
Figure 5.19: Transport Stream page
You can modify the Transports Streams as required and click the Update or Add button, the
case being, to commit your changes. The Transport Stream fields are described in Table
5.16:
Field Description
Equipment Assignment
Modulator Modulator associated with this transport stream.
IP DVB Encapsulator IPE associated with this transport stream.
MODCOD Adaptation MAU associated with this transport stream.

Unit
Table 5.16 Transport Stream page fields

850176 P08
Field Description
PCR Inserter When the modulator is not configure with NCR restamping,
this associated a PCR inserter to the transport stream.
Second PCR Inserter When the modulator is not configure with NCR restamping,
this associated the PCR inserter of the standby RLU to 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 mode.
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
(bit/s) the IP bit rate and of the signaling bit rate from the RLSS.
Clear Sky Transport This is the bit rate corresponding to the specified symbol rate
Stream Bit Rate (kbit/s) under clear sky condition (i.e. using the least protected
MODCOD).
RF Characteristics
Roll-Off Factor The roll-off factor.
Symbol Rate (symb/s) The symbol rate.
Reference Tx Mode The reference Tx Mode is used in the system as the

denominator when calculating the efficiency factors of the TX
Modes. The efficiency factor of a Tx Mode is calculated as
the ratio of its bit rate over the bit rate of the reference Tx
Mode. Therefore, the efficiency factor for the reference Tx
Mode is 1.
Tx Mode Provides access to Tx Modes (MODCODs) configuration.
Frequency Band The name of the frequency band.
Uplink Center Frequency This is the transport stream frequency from the Gateway to
(Hz) the Satellite.

850176 P08
Field Description
Downlink Center Fre- This is the transport stream frequency from the Satellite to the
quency (Hz) Gateway.
Occupied Bandwidth (Hz) The width of the Transport Stream.
Upconversion Offset (Hz) This is the Gateway frequency upconversion offset. This
value is 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 The automatically calculated calibration delay for this
(PCR ticks) transport stream.
Overwritten Calibration If set, this value overwrites the automatic calibration delay.
Delay (PCR ticks)
Services
RCS Map Service ID IDs of the specified services.
Forward Link Signaling ID of the Forward Link Signaling Service.

Service ID
IP/DVB Data Service ID ID of the IP/DVB Data Service.
Tables PIDs
Network Information PID of the Network Information Table (NIT).
Table (NIT) PID
RCS Map Table (RMT) The PCR inserter bit rate.
PID
Composition Tables (SCT, PID of the Composition tables (SCT, FCT, TCT, SPT).
FCT, TCT, SPT) PID
Terminal Tables (CMT, PID of the Terminal Tables (CMT, TBTP).
TBTP) PID
Terminal Information PID of the Terminal Information Message (TIM).
Message (TIM) PID
Program Clock Reference PID of the Program Clock Reference (PCR).
(PCR) PID
PCR Repetition Rate Rate of the PCR Repetition.

850176 P08
Field Description
Multicast Map Table PID of the Multicast Map Table (MMT).

(MMT) PID
Transmission Mode Sup- PID of the Transmission Mode Support Table (TMST).
port Table (TMST) PID
Mesh Flow Receive Param- PID of the Mesh Flow Receive Parameters Table (MFRxPT).
eters Table (MFRxPT) PID
Mesh Receive Definition PID of the Mesh Receive Definition Table (MRSDT).
Table (MRSDT) PID
To return to the Transport Streams page, click the < Back to TS Table button.
You can also navigate directly to Frequency Band Component property page for the Fre-
quency Band to which this Transport Stream was assigned by clicking the < Back to Freq.
Band Compo. button (see “Viewing Frequency Band Components” on page 109).

850176 P08
Chapter 6 Configuring Services
This chapter describes the items that the Network Operator must configure in order to set
up Service Providers, as well as the configuration options available to Service Providers.
Each Service Provider in NetManager operates within a sandbox, sometimes called hub: a
set of resources allocated by the Network Operator to each Service Provider and to which
no other Service Provider has access. This ensures that Service Providers are completely
isolated from each other.
As an initial step, NetManager has to know about the RLSS configuration in order to pro-
vide proper control over Return Link resources. This is done by exporting the configuration
from the RLSS, and then importing this data into NetManager.
• “Importing RLSS Configurations” on page 138 describes how to export an RLSS ver-
sion 1.5 configuration file.
• “Importing RLSS Configurations” on page 138 describes the initial Return Link con-
figuration steps.
Once the NetManager is fed with the information from the RLSS, the Network Operator can
configure the various services offered to the Service Providers. This is discussed in:
• “Services to Service Providers” on page 142 describes high level service configura-
tion.
• “Availability Services” on page 218 describes RFCM and other availability services.

850176 P08
6.1 Importing RLSS Configurations

The Gateway’s RLSS manages all traffic on the Return Link. To ease the configuration of
the Return Link bandwidth, NetManager is able to make use of the configuration file from
the RLSS to automatically create Return Link SLAs and Transport Streams.
Note: For additional information on RL SLA’s, see “Viewing Service Provider

Return Link SLAs” on page 158.
To import an RLSS configuration into the NetManager database, follow these steps:
1. Create a Return Link SLA (see “RL SLA Creation Algorithm” on page 138).
2. Import an RLSS configuration file (see “Performing File Import” on page 140).
6.1.1 RL SLA Creation Algorithm

6.1.1.1 SP RL SLA Creation
6.1.1.1.1 Rules for Creating RL SLAs

NetManager uses the following pre-defined rules for creating RL SLAs from the imported
RLSS configuration.
Note: The NetManager creates a single imported RL SLA (see “Auto Created
Return Link SLAs” on page 168) per segment found in the RLSS
configuration file.
The maximum and minimum guaranteed capacities as well as the Service Category for the
new RL SLA will depend on how the segments (see Segment in Appendix G) are config-
ured to use the pooled capacity from their areas (see Area in Appendix G).
If even a single segment in the area is configured to use pooled capacity with its maximum
capacity set to the area’s traffic capacity, the RL SLA will be created with Constant Bit Rate
(CBR) Service Category, and its minimum guaranteed capacity will be set to the segment’s
maximum capacity. The same applies if none of the segments in the area are allowed to use
pooled capacity.
In any other case, the RL SLA will be created with Variable Bit Rate (VBR) traffic capacity.
In the case of VBR, the limits on capacity also depend on pool capacity usage. If the seg-
ment is configured to use pooled capacity, then the RL SLA’s minimum guaranteed capacity
is set to the segment’s maximum capacity and the RL SLA’s maximum capacity is set to the
area’s traffic capacity. On the other hand, if the segment is not configured to use pooled

850176 P08
capacity, both the RL SLA’s maximum and minimum guaranteed capacity are set to the seg-
ment’s maximum capacity.
6.1.1.1.2 Example
The following is an example of an RLSS configuration that could be imported in NetMan-
ager, with the resulting created RL SLAs.
The RLSS Configuration has two areas, with the following segment configuration:
• Area 1: 512 kbit/s

• Segment 11: 256 kbit/s, pool enabled
• Segment 12: 128 kbit/s, pool disabled
• Area 2: 1024 kbit/s
• Segment 21: 512 kbit/s, pool enabled
After importing the file containing this RLSS configuration, the following RL SLAs will
have been created in the NetManager database based on the rules discussed in “Rules for
Creating RL SLAs” on page 138:
• Auto SLA 11: VBR

• Min 256 kbit/s; Max 512 kbit/s
• Auto SLA 12: VBR
• Min 128 kbit/s; Max 128 kbit/s
• Auto SLA 21: CBR
• Min 512 kbit/s
6.1.1.2 Low Level RL SLA creation

The Low Level Return Link SLAs (see “Low Level Return Link SLAs” on page 162) asso-
ciated with the newly created SP RL SLAs are also automatically created and configured
from the ptarameters found in the imported RLSS configuration file.
Note: The NetManager creates a single Low Level SLA for each imported RL SLA,
and each Low Level SLA is associated with a single segment.
Except for CRA Max, none of the parameters of the Low Level RL SLAs are modifiable in
the NetManager (see “Low Level Return Link SLAs” on page 162). Those parameters can
only be changed using the RLSS management solution.

850176 P08
Note: Changes made using the RLSS management solution are not synchronized
with the NetManager. The RLSS configuration file must be exported from the
RLSS and re-imported into NetManager.
6.1.1.3 Transport Stream and Area Creation

Each Transport Stream and Area (see Area in Appendix G) found in the RLSS configura-
tion file are imported into the NetManager. The RLSS configuration describes the relation-
ships between Transport Streams, Areas and Segments (see Segment in Appendix G).
Since NetManager creates imported RL SLAs based on segment information (see “SP RL
SLA Creation” on page 138), it can associate each imported RL SLAs to a related Area and
Transport Stream, and in turn, create the relationships as required.
6.1.2 Performing File Import

The File import feature allows for restoring previously saved RLSS configurations (see
“RLSS File Import” on page 141) or SIT configurations (see “SIT File Import” on page
141).
To access the feature, select File Import item from the CFG Mgmt menu in the navigation
bar to bring up the File Import page, as shown in Figure 6.1.
Figure 6.1: File Import page

850176 P08
6.1.2.1 RLSS File Import

To import an RLSS configuration, from the Import Format field, select the RLSS import
format you require, based on your Gateway configuration.
Note: NetManager is compatible with the two major Advantech RLSS releases: 1.5
and 2.
RLSS 1.5.7: versions must be 1.5.7 or later,
RLSS 2.X: version must be 2.2.1 or later.
The Delta Import checkbox is used to specify that the file to import was a partial RLSS
configuration export, as opposed to a full export of the SMS database.
Note: The Delta Import feature is deprecated and should not be used.
From the RLSS Name drop-down list, select the RLSS profile into which you want to
import the configuration file.
The Create SP RL SLA field determines whether the NetManager will automatically cre-
ate one SP RL SLA for each imported RL SLA, or if SP RL SLA creation will be left to be
performed manually by the Network Operator. The later case is more time-consuming, but
may be better suited for cases where many SP RL SLAs will have to be associated with
multiple Low Level RL SLAs. Without the option of performing this manually, the Net-
work Operator would have to delete many SP RL SLAs that were automatically associated
with a LL RL SLA.
Note: This field is automatically checked when importing RLSS 1.5.7 format.
Finally, click the Browse button to navigate to the file you wish to import. Select it and
click the Import button to launch the file import process.
6.1.2.2 SIT File Import

To import a SIT configuration, from the Import Format field (see Figure 6.1 (page 140)),
select the SIT Import format and click the Browse button to navigate to the file you wish
to import. Select it and click the Import button to launch the file import process.

850176 P08
6.2 Services to Service Providers

6.2.1 Configuring Services Overview
This section describes the tasks that Network Operators need to perform in order to partition
the total bandwidth into slices to distribute to individual Service Providers. This consists in
configuring Return Link and Forward Link Service Level Agreements (i.e. defining a slice
of bandwidth). The section then moves on to describe the configuration options available to
Service Providers to tailor their allotted bandwidth according to their needs.
The CFG Services menu of the navigation bar provides access to the menu items related to
configuring Services to Service Providers. Clicking on the first menu item, SLA View,
brings up the Service Level Agreement View page (see Figure 6.2 (page 143)) that graphi-
cally represents the different service levels configured and their relationship with each
other.

850176 P08
page 41.
Figure 6.2: Service Level Agreement View page
The other menu items available for Service Level configuration are:
• FL BW Management: This menu item groups sub-items relevant to bandwidth man-

agement on the Forward Link (see “Forward Link Services to Service Providers” on
page 144), namely:
• SP FL SLA: permits the configuration of SP SLAs on the Forward Link; see
“Viewing Service Provider Forward Link SLAs” on page 145.
• FL QoS Device Partition: allows for the configuration of FL QoS Device Parti-
tions; see “Viewing Forward Link QoS Device Partitions (Packeteer QoS only)” on
page 149.

850176 P08
• RL BW Management: This menu item groups sub-items relevant to bandwidth man-

agement on the Forward Link (see “Return Link Services to Service Providers” on
page 157), namely:
• SP RL SLA: permits the configuration of SP SLAs on the Return Link; see
“Viewing Service Provider Return Link SLAs” on page 158.
• Low-Level RL SLA: permits the configuration of LL RL SLAs; see “Low Level
• SIT Groups: This menu item groups sub-items relevant to SIT Group services man-
agement (see “Services to SIT Groups” on page 178), namely:
• SIT Groups: permits the configuration of SIT Groups; see “SIT Group Configura-
tion” on page 178.
• SG FL SLA: permits the configuration of SLAs at the SIT Group level on the For-
ward Link; see “SIT Groups FL SLAs” on page 185.
• SIT Services: This menu item groups sub-items relevant to SIT services management
(see “Services to SITs” on page 194), namely:
• RL QoS: permits the configuration of Quality of Service on the Return Link; see
“Viewing Default SIT Return Link QoS Profiles” on page 194.
• FL QoS: permits the configuration of Quality of Service on the Forward Link; see
“Viewing Default SIT Forward Link QoS Profiles” on page 200.
• RL Queue Filter: permits the configuration of Queue Filters on the Return Link;
see “RL Queue Filters” on page 203.
• RL QoS Scaling: permits the configuration of Quality of Service on the Return
Link; see “Return Link QoS Scaling” on page 207.
• Multicast Scheduling: permits the configuration of multicast events; see “Multi-
cast Scheduling” on page 211.
• SIT S/W Version: Allows for the management of SIT Software versions “SIT
Software Versions” on page 216.
6.2.2 Forward Link Services to Service Providers

Service Provider Forward Link Service Level Agreements (SP FL SLAs) are the tools used
by Network Operators to allocate bandwidth on the Forward Link to Service Providers.
Network Operators also have the flexibility to define multiple SP FL SLAs for a given Ser-
vice Provider.
The total bandwidth available on the Forward Link determines the total number of SP FL
SLAs that can be defined on the system, and is dependent on the rate limiting equipment
(QoS Device or IP/DVB Encapsulator) used. When changes are made to SP FL SLAs, the
resulting route changes have to be manually communicated to the equipment.

850176 P08
6.2.2.1 Viewing Service Provider Forward Link SLAs

To access the SP Forward link SLAs page (see Figure 6.3), select the SP FL SLA item
from the FL BW Management sub-menu in the navigation bar’s CFG Services menu.
Figure 6.3: SP Forward Link SLAs page
Table 6.1 explains the parameters displayed for each SP FL SLA:
Field Description
FL SLA The name that identifies the Forward Link Service

Level Agreement.
Min. Guar. Cap. (kbit/s) The guaranteed minimum capacity for this FL SLA in
kilobits per second.
Min Priority The priority associated with Guaranteed Capacity
traffic service category.
Table 6.1 SP Forward Link SLAs page fields

850176 P08
Field Description
Max. Guar. Cap. (kbit/s) The maximum guaranteed capacity for this FL SLA in
Max Priority The priority associated with Opportunistic Capacity
traffic service category.
Service Category This field indicates the type of service provided by this
FL SLA.
Transport Stream The Transport Stream this FL SLA is associated to.
Table 6.1 SP Forward Link SLAs page fields
• Add/Update/View a Service Provider Forward Link SLA: you can view, create or
modify an SP FL SLA and save it into the database. For more information, see “Add-
ing, Updating and Viewing an SP Forward Link SLA” on page 147.
• Delete a Service Provider Forward Link SLA: you can select one or more SP FL
SLAs from the Grid Table and delete them from the database. For more information
(see “Deleting an SP Forward Link SLA” on page 149).
• Configure the Encapsulator: Manually updates the routing table (see “Updating
Encapsulator Routes” on page 149).
You can return to the Service Provider page by clicking the < Back To Service Provider
button.
Note: Adding and deleting SP FL SLAs is restricted to Network Operators.

850176 P08
6.2.2.1.1 Adding, Updating and Viewing an SP Forward Link SLA

To view or update an existing Service Provider Forward Link SLA, select it from the Grid
Table in the SP Forward Link SLAs page and click the Update button, or to add an SP
Forward Link SLA, click the Add button. This brings up the SP Forward Link SLA prop-
erty page as shown in Figure 6.4.
Figure 6.4: SP Forward Link SLA page
Modify the SP Forward Link SLA as required and click the Update or Add button, the case
being. The SP Forward Link SLA fields are described in Table 6.2.
Field Description
Name The name that identifies the FL SLA.

MAC Properties
Transport Stream ID The Transport Stream that carries this FL SLA.
Table 6.2 SP Forward Link SLA page fields

850176 P08
Field Description
Service Category The service category provided by this SP FL SLA;

possible values are:
• ATM (Asynchronous Transfer Mode)
• CBR (Constant Bit Rate)
• UBR (Unspecified Bit Rate)
• VBR (Variable Bit Rate)
Note: The value selected in this field affects the

possibility of selecting values in the next four
fields related to capacity and priority.
Minimum Guaranteed The Minimum Guaranteed Capacity for this SLA (if
Capacity (kbit/s) applicable).
Warning: In the absence of a full CCS, no check is

done to ensure that the rates of the SP FL
SLA exceed the rate of the IP DVB
Encapsulator used.
Maximum Capacity (kbit/s) The maximum capacity for this SLA (if applicable).

done to ensure that the rates of the SP FL
SLA exceed the rate of the IP DVB
Encapsulator used.
Section Packing This field determines if Section Packing is enabled on

this Transport Stream.This field is not shown when a
SatNet IPE is used on the selected Transport Stream.
Table 6.2 SP Forward Link SLA page fields
Note: Once the desired changes have been made to all SP FL SLAs, route
information must be updated in the IP/DVB Encapsulator for the changes to
take effect (see “Updating Encapsulator Routes” on page 149).
To return to the SP Forward Link SLAs, click the < Back to SP FL SLAs button.

850176 P08
When viewing the SP Forward Link SLA page, you can also partition the bandwidth
defined in this SP FL SLA into SIT Group FL SLAs by clicking the Split into SG FL SLAs
> button (see “Adding and Updating a SIT Group FL SLA” on page 186).
6.2.2.1.2 Deleting an SP Forward Link SLA

To remove SP FL SLAs from the database, select one or more items from the Grid Table in
the Service Provider Forward Link SLAs page and click the Delete button.
Alternatively, you can open the property page for the Service Provider Forward Link SLA
to delete (see “Adding, Updating and Viewing an SP Forward Link SLA” on page 147) and
click the Delete button.
6.2.2.1.3 Updating Encapsulator Routes

For changes that affect many SITs, the routing table information in the IP encapsulator is
automatically updated:
• Changes to the SG-FL-SLA PID

• Changes to default route-level FL QoS
• Changes to SIT IP addresses
There are exceptional updates that do not trigger an automatic update of the routing table;
for example, changing the transport stream of the SIT (by updating the SIT group assign-
ment to a SG-FL-SLA). In case of doubt, the routing table update can be triggered manu-
ally.
To manually trigger the export of the complete encapsulator configuration (managed by the
NetManager), the NO user must navigate to the IP/DVB Encapsulator table (see “IP DVB
Encapsulator Profiles” on page 80) and click on the Synchronize button.
6.2.2.2 Viewing Forward Link QoS Device Partitions (Packe-

teer QoS only)
If the system is set up with an Packeteer FL QoS device, the SIT Group FL SLAs can be
configured with sub-classes called FL QoS Device Partitions so that the device can manage
bandwidth associated to it.

850176 P08
To access the FL QoS Device Partitions page (see Figure 6.5), select the FL QoS Device
Partition item from the FL BW Management sub-menu in the navigation bar’s CFG Ser-
vices menu.
Figure 6.5: FL QoS Device Partitions page
Table 6.3 explains the parameters displayed for each FL QoS Device Partition:
Field Description
Partition Name The name of the partition.

Min. Guaranteed Capacity The minimum guaranteed capacity for this partition.
(kbit/s)
Maximum Capacity The maximum capacity for the partition.
Maximum Capacity Priority The maximum capacity priority for the partition.
Service Category The type of service for this partition.
SIT-Level FL QoS Profile The Forward Link SIT-Level QoS to which this
partition is associated.
SG FL SLA Name The SIT Group FL SLA to which this partition is
associated.
Table 6.3 FL QoS Device Partitions page fields

850176 P08
• Add/Update/View a FL QoS Device Partition: you can view, create or modify an FL

QoS Device Partition and save it into the database. For more information, see “Adding
and Updating an FL QoS Device Partition” on page 152.
• Delete a FL QoS Device Partition: you can select one or more FL QoS Device Parti-
tions from the Grid Table and delete them from the database. For more information,
see “Deleting an FL QoS Device Partition” on page 154.
You can return to the Service Provider page by clicking the < Back To Service Provider
button.
Note: Adding and deleting FL QoS Device Partitions is restricted to Network

Operators and Service Provider Administrators.

850176 P08
6.2.2.2.1 Adding and Updating an FL QoS Device Partition

To update an existing FL QoS Device Partition, select it from the Grid Table in the FL QoS
Device Partitions page and click the Update button, or to add a new FL QoS Device Parti-
tion, click the Add button. This brings up the FL QoS Device Partition property page as
Figure 6.6: FL QoS Device Partition page

850176 P08
Modify the Forward Link QoS Device Partition as required and click the Update or Add
button, the case being. The FL QoS Device Partition fields are described in Table 6.4:
Field Description
SIT Group FL SLA

SIT Group QoS Device The name of the SG QoS Device Partition.
Partition Name
SIT Group FL SLA The SG FL SLA to which this partition will be associated.
Service Category The service category defined in the SIT Group.
Min. Capacity Guaran- The minimum Capacity configured for the SIT Group.
teed (kbits/s)
Max. Capacity (kbit/s) The maximum capacity for the SIT Group.
Nominal Traffic Shaping
Service Category The service category provided by the partition. Possible
values are:
• ATM
• CBR
• UBR
• VBR
Guaranteed Capacity The guaranteed capacity for the selected service category
(kbit/s) associated to the partition.
Maximum Capacity (kbit/ If applicable, the maximum capacity for the selected
s) service category associated to the partition.
Maximum Priority The maximum priority of traffic the partition.
Nominal Default QoS per SIT Route
FL QoS Type The FL QoS type associated to this partition.
Guaranteed (kbit/s) The nominal guaranteed rate for the FL QoS associated
with this partition.
Opportunistic (kbit/s) The nominal opportunistic rate for the FL QoS associated
with this partition.
Opportunistic Priority The nominal opportunistic priority for the FL QoS
associated with this partition.
Table 6.4 FL QoS Device Partition page fields

850176 P08
To return to the FL QoS Device Partitions page, click the < Back to FL QoS Partitions
button. Alternatively, to navigate back to the SIT Group Forward Link SLA page, click
the < Back to SG FL SLA button.
Once a FL QoS Device Partition has been defined, the traffic that will be directed to the par-
tition can be specified using the IP Partition Classification; to access it, click the IP Classi-
fication > button (see “IP Partition Classification (Packeteer QoS only)” on page 155).
6.2.2.2.2 Deleting an FL QoS Device Partition

To remove an FL QoS Device Partition from the database, select one or more items from
the Grid Table in the FL QoS Device Partitions page and click the Delete button.
Alternatively, you can open the property page of the FL QoS Device Partition to remove
(see “Adding and Updating an FL QoS Device Partition” on page 152) and click the Delete
button.

850176 P08
6.2.2.3 IP Partition Classification (Packeteer QoS only)

Once an FL QoS Device Partition has been defined, the traffic that will be directed to the
partition must be determined: traffic is classified into the partitions using the IP Partition
Classification page; to access it (see Figure 6.7), navigate to the FL QoS Device Partition
of interest (see “Adding and Updating an FL QoS Device Partition” on page 152) and click
the IP Classification > button.
Figure 6.7: IP Partition Classification page
Modify the IP Partition Classification as required and click the Update or Add button, the
case being. The IP Partition Classification fields are described in Table 6.5:
Field Description
Association
FL QoS Partition The FL QoS Device Partition for this classification.
SIT Group FL SLA The SG FL SLA to which the FL QoS Device Partition
belongs.
Table 6.5 IP Partition Classification page fields

850176 P08
Field Description
Managed Application
Pre-defined Application The Application related to the Partition.
Name
In the current NetManager implementation, the possible
values are for the different VoIP codecs:
• IPSec VoIP G.711 30 msec
• Video H.323 256
• Video H.323 385
• Video H.323 512
• Video H.323 768
• VoIP G.711 30 msec
Max Number of Guaran- The maximum number of guaranteed flows per route;
teed Flows per Route determined based on the FL QoS parameters.
Max Number of Flows The maximum number of flows per route; determined
per Route based on the FL QoS parameters.
Max Number of Guaran- The maximum number of guaranteed flows per partition;
teed Flows in Partition determined based on the FL QoS parameters.

850176 P08
Field Description
Max Number of Flows in The maximum number of flows per partition; determined
Partition based on the FL QoS parameters.
DiffServ DSCP The DiffServ DSCP setting; select value from the drop-
down list. Possible values are:
• Best Effort
• Assured Forwarding class 1
• Express Forwarding
• Network-layer control
• Link-layer control
Usage Type The type of usage intended for the partition. Possible
values are:
• OAM
• TRAFFIC
• IPSec
• MULTICAST
To delete the IP Partition Classification, click the Delete button.
To return to the FL QoS Device Partition page, click the < Back to QoS Partition button.
6.2.3 Return Link Services to Service Providers

The Return Link bandwidth is a function of the RLSS managing it. To make this initial par-
titioning as easy as possible for Network Operators, NetManager provides the ability to
import a complete RLSS configuration, which is then automatically transformed into
imported Return Link Service Level Agreements using specific rules (see “Importing RLSS
Configurations” on page 138).
The imported RL SLAs can then be assigned to a Service Provider (see “Auto Created
Return Link SLAs” on page 168) and further configured by specifying their behavior under
different environmental conditions (see “Low Level Return Link SLAs” on page 162).

850176 P08
6.2.3.1 Viewing Service Provider Return Link SLAs

The Service Provider Return Link SLAs page (see Figure 6.8) is used to view SP RL
SLAs and to perform operations on them. To access it, select the SP RL SLA item from the
RL BW Management sub-menu in the navigation bar’s CFG Services menu.
Figure 6.8: Service Provider Return Link SLAs page

850176 P08
Table 6.6 explains the parameters displayed for the SP RL SLAs:
Field Description
RL SLA The name that identifies the Service Provider Return Link
Service Level Agreement.
Min. Guar. Cap. (kbit/s) The guaranteed minimum capacity for this SP RL SLA, in
kilobits per second, determined automatically at RLSS
configuration import time (see “Importing RLSS Configu-
rations” on page 138).
Max. Guar. Cap. (kbit/s) The maximum guaranteed capacity for this SP RL SLA in
Service Category This field indicates the type of service provided by this SP
RL SLA, determined automatically at RLSS configuration
import time (see “Importing RLSS Configurations” on
page 138).
Slot Type The type of Slot associated to the SP RL SLA.
Table 6.6 Service Provider Return Link SLAs page fields
• Add: adds a new SP RL SLA. For more information, see “Adding and Updating SP
• Delete: deletes the selected SP RL SLA(s). For more information, see “Deleting SP
• Update: modifies the parameters of the selected SP RL SLA. For more information,
see “Adding and Updating SP Return Link SLAs” on page 160.
• Auto Created RL SLAs: navigates to the page listing all auto created RL SLAs. For
more information, see “Auto Created Return Link SLAs” on page 168.
• Unassign: returns the selected SP RL SLA to the unassigned Imported RL SLAs,
“Auto Created Return Link SLAs” on page 168.
Note: Only Network Operators can add, delete and unassign SP RL SLAs.

850176 P08
6.2.3.1.1 Adding and Updating SP Return Link SLAs

To update an existing Service Provider Return Link SLA, select it from the Grid Table in
the Service Provider Return Link SLAs page and click the Update button, or to add a
new SIT Group, click the Add button. This brings up the SP Return Link SLA property
page as shown in Figure 6.9. This page displays the properties for the selected SP RL SLA
and allows you to modify its parameters.
Figure 6.9: SP Return Link SLA page

850176 P08
Modify the SP Return Link SLA as required and click the Update button. The SP Return
Link SLA fields are described in Table 6.7.
Field Description
Name The name that identifies the SP RL SLA.

Burst Type The type of burst cell transported by this SP RL SLA,
from:
• ATM1
• ATM2
• MPEG (RLSS 2.X only)
Nominal SLA
Service Category The service category for this SP RL SLA; this value is
determined automatically at RLSS configuration
page 138).
Minimum Guaranteed The minimum guaranteed capacity for this SP RL
Capacity (kbit/s) SLA, in kilobits per second; this value is determined
automatically at RLSS configuration import time (see
“Importing RLSS Configurations” on page 138).
Maximum Capacity (kbit/s) The maximum capacity for this SP RL SLA, in
Oversubscription Limits on Nominal SLA
Constant Traffic (CRA) The CRA oversubscription factor. This allow to
control the amount of CRA oversubscription at
configuration time.
Persistent Traffic (RBDC) The RBDC oversubscription factor. This allow to
control the amount of RBDC oversubscription at
configuration time.
Best-Effort Traffic (VBDC) The VBDC oversubscription factor. This allow to
control the amount of VBDC oversubscription at
configuration time.
Table 6.7 SP Return Link SLA page fields
To return to the Service Provider Return Link SLAs page, click the < Back To RL SLA
Profiles button.

850176 P08
Oversubscription allows control of over-assignment resources at the configuration time.

Service Providers can over-assign resources because not all terminals are logged on to the
network simultaneously. A warning is displayed when the operator reaches the oversub-
scription limit. Oversubscription is available for the CRA, VBDC and RBDC capacity
types. The total capacity = oversubscription factor x capacity. Accepted values are numbers
and decimals numbers (ex, 1, 1.5, 2, 50, 100)
When viewing the SP Return Link SLA page, you can also: Change how the SP RL SLA
behaves under different conditions by modifying the Low Level Return Link SLAs that are
associated to it: Click the Low Level RL SLA > button (refer to “Low Level Return Link
SLAs” on page 162 for additional details).
6.2.3.1.2 Deleting SP Return Link SLAs

To remove SP RL SLAs from the database, select one or more items from the Grid Table in
the Service Provider Return Link SLAs page and click the Delete button.
6.2.3.2 Low Level Return Link SLAs

Low Level Return Link Service Level Agreements define the details of a Service Provider
RL SLA’s behavior. Multiple Low Level RL SLAs can be associated with a single SP RL
SLA to define its behavior under different conditions. For example, two Low Level RL
SLAs could be associated to a given SP RL SLA, one to be used under normal environmen-
tal conditions and one under rain fade conditions. Because of this conditional nature, Low
Level RL SLAs are sometimes called Conditional SLAs (see “RL SLA Conditioning” on
page 170).
To access the Low Level RL SLAs page, select the Low-level RL SLA item from the RL
BW Management sub-menu in the navigation bar’s CFG Services menu.

850176 P08
The Low Level RL SLAs page has two views; switching between them is done using the
two tab buttons at the top of the grid-table: the view associated with the LL Definition tab
is shown in Figure 6.10 and that for the Conditioning tab in Figure 6.11.
Figure 6.10: Low Level RL SLAs page (LL Definition view)
In the LL Definition view, the following parameters are displayed for each Low Level RL
SLA (see Table 6.8)
Field Description
Low Level RL SLA Name The name that identifies the Low Level RL SLA.
SP RL SLA name The SP RL SLA to which this Low Level RL SLA is
associated.
Protection Level The protection level afforded by the LL RL SLA.
User Carrier Rate The user carrier bit rate for this Low Level RL SLA,
in Kbit/s, obtained from the RLSS configuration file
that was imported to create this SLA (see “Importing
RLSS Configurations” on page 138).
Table 6.8 Low Level RL SLAs page fields (LL Definition view)

850176 P08
Field Description
Coding Type The coding type applied to the traffic, obtained from
the RLSS configuration file that was imported to
create this SLA (see “Importing RLSS Configura-
tions” on page 138).
Precedence Level The precedence level for the LL RL SLA.
Increase Threshold (C/N) The threshold at which a transition to a higher
protection level will be made.
Decrease Threshold (C/N) The threshold at which a transition to a lower
protection level will be made.
Segment ID The segment to which the LL RL SLA is associated.
Area ID The area to which the LL RL SLA is associated.
Unit ID The Unit to which the LL RL SLA is associated.
Table 6.8 Low Level RL SLAs page fields (LL Definition view)
Figure 6.11: Low Level RL SLAs page (Conditioning view)

850176 P08
In the Conditioning view, the following parameters are displayed for each Low Level RL
SLA (see Table 6.9)
Field Description
LL RL SLA Name The name that identifies the Low Level RL SLA.
SP RL SLA name The SP RL SLA to which this Low Level RL SLA is
associated.
CRA Max Rate (kbits/s) The maximum CRA bit rate.
CRA Overbooking The CRA overbooking factor.
RBDC Max Rate (kbit/s) The maximum RBDC bit rate.
RBDC Overbooking The RBDC overbooking factor.
QoS Scaling The Quality of Service Scaling.
Application Partition The Application Partition.
Table 6.9 Low Level RL SLAs page fields (Conditioning view)
• Delete: deletes the selected LL RL SLA(s). For more information, see “Deleting SP
• Update: modifies the parameters of the selected LL RL SLA. For more information,
see “Updating a Low Level Return Link SLA” on page 166.
• Clone: the button can be used to quickly duplicate a selected Low Level RL SLA. This
is particularly useful when adding new LL RL SLA that has characteristics very simi-
lar to an existing one, and is a quicker alternative to manually creating the LL RL SLA
from nothing.
• Conditioning: navigates to the RL SLA Conditioning page to the conditioning of a
given SP RL SLA, see “Adding and Updating SLA Conditioning” on page 171.
Overbooking allows control of over-assignment resources in real-time, when the SITs
attempts to join the network. SITs will be denied if the overbooking limit is reached. In this
case, the SITs will retry to logon, and will be accepted only if logged on terminals left the
network. Overbooking validation at logon time is available for the RBDC and CRA capac-
ity types. The CRA overbooking is used only for CCP. The total capacity = overbooking
factor x capacity. Accepted overbooking values are numbers and decimals numbers (ex, 1,
1.5, 2, 50, 100).
Note: Only Network Operators can update Low Level RL SLAs.

850176 P08
6.2.3.2.1 Deleting Low Level Return Link SLAs

To remove LL RL SLAs from the database, select one or more items from the Grid Table in
the Low Level Return Link SLAs page and click the Delete button.
6.2.3.2.2 Updating a Low Level Return Link SLA

To update an existing Low Level Return Link SLA, select it from the Grid Table in the Low
Level Return Link SLAs page and click the Update button. This brings up the Low Level
Return Link SLA property page as shown in Figure 6.12.
Figure 6.12: Low Level return Link SLA page

850176 P08
Modify the Low Level Return Link SLA as required and click the Update button. The Low
Level Return Link SLA fields are described in Table 6.10.
Field Description
SP RL SLA Name The SP RL SLA to which the Low Level RL SLA is

associated.
Low Level SLA Name The identifier for this Low Level RL SLA.
Precedence Level When more than one transition to a LL RL SLA is
available to the system, this parameter will be used to
determine which one is preferred.
Return Link SLA Properties
Segment ID The segment ID associated with this Low Level RL
SLA, obtained from the RLSS configuration file that
was imported to create this SLA (see “Importing RLSS
Area ID The Area ID associated with this Low Level RL SLA,
obtained from the RLSS configuration file that was
imported to create this SLA (see “Importing RLSS
Unit ID The Unit to which the LL RL SLA is associated.
Coding Type The coding type applied to the traffic.
User Carrier Rate The user carrier bit rate for this Low Level RL SLA, in
Kbit/s.
Symbol Rate (ksymbols/s) The symbol transmission rate.
Rain Fade Counter Measures Settings
Protection Level This defines the protection level afforded by the LL RL
SLA. Possible values are:
• Clear Sky
• Rain Fade 1
• Rain Fade 2
• Rain Fade 3
Threshold to Decrease Pro- The Carrier to Noise ratio at which a transition to a
tection Level (C/N dB) lower protection level will be made.
Threshold to Increase Pro- The Carrier to Noise ratio at which a transition to a
tection Level (C/N dB) higher protection level will be made.
Table 6.10 Low Level Return Link SLA page fields

850176 P08
Field Description
Threshold to Decrease Pro- The Signal to Noise ratio at which a transition to a

tection Level (Es/N dB) lower protection level will be made.
Threshold to Increase Pro- The Signal to Noise ratio at which a transition to a
tection Level (Es/N dB) higher protection level will be made.
Table 6.10 Low Level Return Link SLA page fields
To return to the Low Level Return Link SLAs page, click the < LL RL SLA button.
You can access conditioning options for the LL RL SLA by clicking the RL SLA Condi-
tioning > button at the bottom of the page (refer to “Adding and Updating SLA Condition-
ing” on page 171 for additional details).
6.2.3.3 Auto Created Return Link SLAs

To access the Auto Created Return Link SLAs page, first select the SP RL SLA item
from the RL BW Management sub-menu in the navigation bar’s CFG Services menu.
This brings up the Service Provider Return Link SLAs page (see Figure 6.8). Click the
Auto Created RL SLAs button to bring up the Auto Created RL SLAs page (see Figure
6.13).
Figure 6.13: Imported RL SLAs page

850176 P08
The following parameters are shown for each imported RL SLA.
Field Description
RL SLA The name that identifies the imported RL SLA.

Min. Guar. Cap. (kbit/s) The minimum guaranteed capacity for this RL SLA, in
Max. Guar. Cap. (kbit/s) The maximum capacity for this RL SLA, in kilobits per
second, determined automatically at RLSS configuration
page 138).
Service Category The service category for this RL SLA, determined
automatically at RLSS configuration import time (see
Table 6.11 Imported RL SLA page fields
To move imported RL SLAs to the list of SP RL SLAs (see “Viewing Service Provider
Return Link SLAs” on page 158), select the checkbox beside the imported RL SLAs of
your choice and click the Assign button. The application will automatically navigate to the
Service Provider Return Link SLA page.
6.2.3.4 Over-Assignment
Because statistically speaking not all SITs configured with a given RL SLA will log on to
the network simultaneously, Service Providers can over-assign resources, i.e. allow more
SITs on a specific RL SLA than would otherwise be permitted if all those SITs logged in
and used the SLA simultaneously. This allows for a more optimized bandwidth usage, but
does have drawbacks: if in fact more SITs than expected are logged in at the same time,
some customers may not receive the bandwidth they should, and could even be prevented
from logging on to the network due to lack of bandwidth. NetManager allows for over-
assignment of resources and provides Service Providers with two types of control over it:
Oversubscription limits and Overbooking limits.
In both Oversubscription and Overbooking, the risk is managed with a multiplication factor
that determines by how much the capacity can be exceeded. Each type of over-assignment
can therefore be disabled by setting its multiplication factor to 1, which makes the over-
assignment limit equal to the maximum set in the SLA, effectively protecting the bandwidth
for this SLA and traffic type.

850176 P08
Oversubscription is discussed in “Oversubscription” on page 170; the parameters associated

to oversubscription are configurable at the SP RL SLA level (see “Adding and Updating SP
Return Link SLAs” on page 160).
Overbooking is discussed in “Overbooking” on page 170; the configuration parameters

associated to overbooking are available at the SP RL SLA Conditioning level (see “Adding
and Updating SLA Conditioning” on page 171).
6.2.3.4.1 Oversubscription
Oversubscription allows for control of resource over-assignment at configuration time. The
Oversubscription limit on a given SLA sets the factor by which its maximum bandwidth of
a certain type can be exceeded, this factor being checked by NetManager when SITs are
configured to use it.
For example, if the oversubscription limit factor is set to 3 for a given SLA, an operator can
configure SITs on this SLA until their combined bandwidth usage is three times the maxi-
mum set in the SLA. When the oversubscription maximum is reached, an operator attempt-
ing to configure a new SIT on the SLA will be warned of this fact, but not prevented from
adding the SIT, i.e. the oversubscription is not a firm limit, but more of a suggestion that
Service Providers make for themselves for the configuration of SITs on an SLA and traffic
type.
6.2.3.5 RL SLA Conditioning

Most aspects of Return Link SLAs assigned to a Service Provider are configured by the
Network Operator: guaranteed capacities, bit rates, etc. (i.e. the implementation of the RL
SLA). Service Providers have some measure of control as to how RL SLAs assigned to
them are used. Various parameters can be tailored, including Overbooking factors.
6.2.3.5.1 Overbooking
As discussed in “Over-Assignment” on page 169, NetManager allows for over-assignment
of resources. Overbooking is one such over-assignment option, and is controlled through
RL SLA Conditioning (see “Adding and Updating SLA Conditioning” on page 171).
As opposed to oversubscription which controls over-assignment at configuration time,

Overbooking, provides for control of over-assignment of resources in real time. More pre-
cisely, it allows for setting a limit on over-assignment of a given SLA and traffic type that
will be checked when SITs attempt to join the network. For example, if the Overbooking
limit factor is set to 2, the system will keep granting SITs access to the network until their
combined usage for the SLA and traffic type is twice the maximum set in the SLA; at this
point, it will start denying entry to any additional SITs which use this SLA and traffic type,
until some of the SITs already logged in leave the network.

850176 P08
In both Oversubscription and Overbooking, risk is managed with a multiplication factor

that determines by how much the capacity can be exceeded. Each type of over-assignment
can therefore be disabled by setting its multiplication factor to 1, making the over-assign-
ment limit equal to the maximum set in the SLA, effectively protecting the bandwidth for
this SLA and traffic type.
6.2.3.5.2 Adding and Updating SLA Conditioning

To update the conditioning of a given Low Level RL SLA, click the RL SLA Condition-
ing> button in the Low Level Return Link SLA page (see “Updating a Low Level Return
Link SLA” on page 166); this brings up the RL SLA Conditioning property page as shown
in Figure 6.14.
Alternatively, to add a new Conditioning, you can select an SP RL SLA from the Grid
Table in the Low Level RL SLAs page (see “Low Level Return Link SLAs” on page 162)
and click the Conditioning > button.
Note: Only Administrators can update the Conditioning of an SLA.
Note: For more information on updating the records in the database, see “Adding,
Updating and Deleting Records” on page 37.

850176 P08
Figure 6.14: RL SLA Conditioning page

850176 P08
Modify the RL SLA’s Conditioning as required and click the Update button. The RL SLA
Conditioning’s fields are described in Table 6.12.
Field Description
Low-Level Return Link SLA

Low-Level RL SLA The name that identifies the RL SLA. This parameter is
Name informative only and cannot be changed.
Minimum Guaranteed The minimum bit rate that is guaranteed to subscribers of
Capacity (kbit/s) this SLA.
Maximum Capacity The maximum bit rate that is available to subscribers of
(kbit/s) this SLA.
Constant Traffic (CRA) fields
Aggregate Maximum The maximum rate available for users (SITs) of the SLA
Rate (kbit/s) for distribution as SIT-Level Constant Traffic (CRA) (see
“Viewing Default SIT Return Link QoS Profiles” on page
194).
Constant Rate Assignments (CRA) is a DVB-RCS specific
term for constant capacity on the Return Link that does not
need to be requested. Because of its constant nature and the
fact that it does not need to be requested, it is especially
suited for applications that require constant throughput,
low delays and low jitter.
Overbooking Limit The ceiling factor by which the Constant Rate Traffic
aggregate maximum rate is committed to SITs that use the
SLA to log into the network.
E.g. A CRA maximum aggregate rate of 64 kbit/s with
overbooking factor of 2.0 means that the sum of all CRA
maximum rate per SIT, summed over all SITs within SIT
groups using the SLA cannot exceed 128 kbit/s.
Warning: When a SIT is trying to log into the network

with an CRA max that would make the sum of
CRA Max exceed the allowed maximum
(Aggregate Max Rats x Overbooking Limit),
the Connection Manager refuses network
entry to this SIT.
Table 6.12 RL SLA Conditioning page fields

850176 P08
Field Description
Persistent Traffic (RBDC) fields

Aggregate Maximum The maximum rate available for users (SITs) of the SLA
Rate (kbit/s) for distribution as SIT-Level persistent traffic (RBDC), see
“Viewing Default SIT Return Link QoS Profiles” on page
194.
Rate-Based Dynamic Assignments (RBDC) is a DVB-RCS
specific term for variable capacity on the Return Rink that
needs to be requested as a rate. It is called persistent traffic
because the RBDC capacity does not need to be requested
at the scheduling time interval. Without updates, the
capacity is granted at the same rate for up to one second.
Because of its relatively constant nature, it is especially
suited for applications that require relatively constant
throughput.
Because the overbooking can be controlled (see RDBC
Overbooking Limit below), it can accommodate
applications that require moderately low delays and low
jitter.
Overbooking Limit The ceiling factor by which the Persistent Traffic aggregate
maximum rate is committed to SITs that use the SLA to log
into the network.
E.g. A persistent maximum aggregate rate of 64 kbit/s with
overbooking factor of 2.0 means that the sum of all RBDC
maximum rate per SIT, summed over all SITs within SIT
groups using the SLA cannot exceed 128 kbit/s.
Warning: When a SIT is trying to log into the network

with an RBDC max that would make the sum
of RBDC Max exceed the allowed maximum
(Aggregate Max Rats x Overbooking Limit),
the Connection Manager refuses network
entry to this SIT.
This field can be changed when updating an RL SLA’s

Conditioning.

850176 P08
Field Description
Optional (100% Scaling Assumed if Left Blank)

SIT-Level QoS Scaling Applies this factor to the QoS of SITs using this SLA
wrt Nominal conditioning; refer to “Return Link QoS Scaling” on page
207.
The Traffic Distribution bar chart (bottom part of Figure 6.12) graphically displays the rela-
tive weight associated with the CRA, RBDC, VBDC and Segments parts of the traffic
throughput for the Low Level RL SLA.
Most of the bandwidth related fields are non-editable: they display information on the phys-
ical transmission parameter related to this SLA and have been obtained from an imported
RLSS configuration file (see “Low Level RL SLA creation” on page 139 for additional
details). The only exception is the CRA Max field which can be modified.
Note: Exceeding the CRA max parameter could result in some terminals being
denied access to the network.
To return to the Low Level RL SLAs page, click the < Back to LL RL SLAs button.
You can also configure bandwidth partitions for specific applications in the LL RL SLA by
clicking the RL SLA Application > button (see “Application Return Link SLA” on page
175) to bring up the Application RL SLA page.
6.2.3.6 Application Return Link SLA

An Application RL SLA refers to bandwidth that is reserved for the traffic of a specific type
of application, such as Voice over IP.

850176 P08
6.2.3.6.1 Adding and updating an Application RL SLA

To update existing Application RL SLA, navigate to the RL SLA Conditioning page for the
LL RL SLA to which the application partition is to be associated and click on the RL SLA
Application > button (see “Adding and Updating SLA Conditioning” on page 171). This
brings up the RL SLA Application property page as shown in Figure 6.15.
Figure 6.15: RL SLA Application page

850176 P08
Modify the Application RL SLA as required and click the Update or Add button, the case
being. The Application RL SLA fields are described in Table 6.13.
Field Description
Application Type The application type, such as Voice Over IP.

Application Name The name of this Application RL SLA.
Aggregate SLA Properties
Minimum Guaranteed Capac- The minimum aggregate guaranteed capacity for the
ity (kbit/s) conditioned LL RL SLA.
Maximum Capacity (kbit/s) The maximum aggregate capacity for the
conditioned LL RL SLA.
Reserved for other Applica- The capacity reserved for other applications in the
tions (kbit/s) LL RL SLA.
Application Nominal Reservation
Capacity for Application (kbit/ The capacity available to reserve from the SLA for
s) this application, based on the CRA of the SLA.
Minimum Guaranteed Capac- The desired minimum guaranteed capacity alocated
ity (kbit/s) from the SLA for this application.
For example, if the capacity is configured for VoIP,
no other type of traffic will be allowed to use this
particular portion of bandwidth; this ensures a
certain level of service of the application.
Maximum Capacity (kbit/s) The maximum capacity the application has access to
for this SLA.
Table 6.13 RL SLA Application page fields
To return to the RL SLA Conditioning page, click the < RL SLA Conditioning button.
6.2.3.6.2 Deleting an Application RL SLA

To remove Application RL SLAs from the database, select one or more items from the Grid
Table in the Applications RL SLA page and click the Delete button.
Alternatively, you can open the property page for the Application RL SLA to delete (see
“Application Return Link SLA” on page 175) and click the Delete button.

850176 P08
6.2.4 Services to SIT Groups

6.2.4.1 SIT Group Configuration
Specific Services are seldom offered to single SITs, but rather to a number of them. Instead
of having to configure many terminals with the same information, NetManager provides the
concept of SIT Groups, allowing for the clustering of many SITs under a single entity. Each
SIT Group is configured with Services that apply to all the SITs it manages:
• Return Link SLA,

• Forward Link SLA,
• Login RL QoS,
• FL SIT-Level QoS (traffic and OAM),
• Max Return Link QoS for managed application (such as VoIP with CCP).
6.2.4.1.1 Viewing SIT Groups

The list of SIT Groups defined so far is available in the SIT Groups page (see Figure 6.16).
To access this page, select the SIT Groups item from the SIT Groups sub-menu in the nav-
igation bar’s CFG Services menu.
Figure 6.16: SIT Groups page

850176 P08
This page lists the SIT Groups and their associated parameters, as described in Table 6.14.
Field Description
SIT Group The name that identifies the SIT Group.

FL QoS The Forward Link QoSs that are assigned as default for the
members of this SIT group; the first name in the celle refers to the
QoS profile assigned to the OAM route and the second to the traffic
route(s).
Note: If this cell is empty, then the SIT group was not assigned
any default Forward Link QoS.
RL 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 can be reached with
CCP.
Note: If this cell is empty, then the SIT group was not assigned
a default Return Link QoS.
FL SLA The Forward Link Service Level Agreement for the SIT Group.
RL SLA The Return Link Service Level Agreement for the SIT Group.
Table 6.14 SIT Groups page fields
• Add/Update a SIT Group: you can create or modify a SIT Group. For more informa-
tion, see “Adding and Updating a SIT Group” on page 180.
• Delete a SIT Group: you can select one or more SIT Groups from the Grid Table and
delete them from the database. For more information, see “Deleting a SIT Group” on
page 184.
To return to the Service Provider page, click the < Back to Service Provider button.

850176 P08
6.2.4.1.2 Adding and Updating a SIT Group

Modifying a SIT Group typically involves changing the services associated to it: the QoSs
and SLAs (see “Services to SIT Groups” on page 178 and “Services to SITs” on page 194)
to be associated to the SIT Group should already have been defined.
Note: If you are adding a new SIT Group, you may also create the services at a
later time and update the SIT Group at that time.
Note: When adding and updating SIT Groups, user input is validated against a set
of consistency rules: if you encounter any errors when modifying SIT Groups,
refer to “SIT Group Checks” on page 361.
To update an existing SIT Group, select it from the Grid Table in the SIT Groups page and
click the Update button, or to add a new SIT Group, click the Add button. This brings up
the SIT Group property page as shown in Figure 6.17.

850176 P08
Figure 6.17: SIT Group page

850176 P08
Modify the SIT Group as required and click the Update or Add button, the case being. The
SIT Group fields are described in Table 6.15:
Field Description
SIT Group The name that identifies the SIT Group.

Customer The name of the Customer or entity that this SIT Group
represents.
Note: This is an informative field only and is not

required.
Multicast Enables the Group to receive SCS commands (see “SIT

Control System (SCS)” on page 284).
SIT MIB
Read Community Name The SIT MIB community name that allows for reading
the MIB.
Write Community Name The SIT MIB community name that allows for writing to
the MIB.
Default Manual Config When checked, prevents the NetManager's Connection
Manager from attempting to configure the SIT's MIB.
Note: This is a backward compatibility feature

present because some SITs may not
operate properly when the Connection
Manager is set to configure the MIB.
Max Number of Terminals The maximum number of terminals assignable to this

SIT Group.
Note: A warning will be displayed to operators

attempting to configure more than this
number of SITs in the group.
SCS Parameters
Uplink Power Control Determines whether or not Uplink Power Control is
Enabled enabled.
Target Eb/No The target Energy per bit per noise power spectral
density (Signal to Noise ration per bit).
Table 6.15 SIT Group page fields

850176 P08
Field Description
Population Id The population ID.

Default S/W Version The default Software Version.
VoIP Capabilities
CCP Enabled The CCP protocol is enabled for the SITs of that SIT
group.
Maximum Number of CCP The maximum number of CCP calls per SIT.
Calls (per SIT)
QoS Profiles
SIT Maximum FL Rate This is the maximum FL bit rate per SIT in that SIT
(kbits/s) group. By default, this field is populated with the
maximum bit rate of the SG FL SLA..
FL OAM QoS The Default Forward Link QoS profile assigned to
OAM routes for this SIT Group.
Note: This is the default for SITs in this SIT

group, but can be overwritten in each FL
Route profile, see “Adding and Updating
an IP Route” on page 248.
FL Traffic QoS The Default Forward Link QoS profile assigned to

Traffic routes for this SIT Group.
Note: This is the default for SITs in this SIT

group, but can be overwritten in each FL
Route profile, see “Adding and Updating
an IP Route” on page 248.
Maximum FL Rate per The default Forward Link QoS profile assigned to
Application TOS packets matching a ToS specified in a FL Traffic route.

850176 P08
Field Description
Login RL QoS The initial Return Link QoS profile assigned to SITs at
logon.
Note: This is the default for SITs in this Group,

but can be overwritten in each SIT’s
Profile, see “Overwriting RL QoS” on
page 232.
Max CCP RL QoS The maximum RL QoS available to SITs in this group.
RL Traffic Queue Filter RL Traffic Queue Filter
SLAs
FL SLA The Forward Link Service Level Agreement that this
SIT Group subscribes to.
RL SLA The Return Link Service Level Agreement that this
SIT Group subscribes to.
The graphic part of the SLAs pane presents a View-page-like (see “Interactive View Pages”
on page 41) representation of the Service Level Agreement elements related to this SIT
Group.
To return to the SIT Groups page, click the < Back to SIT Group button.
You can create a new SIT profile to make it a member of the current SIT Group by clicking
the Add SIT button, which brings up the SIT page (see “Adding and Updating a SIT Pro-
file” on page 227).
If the Group is Multicast Enabled, you can add a Multicast Route by clicking on the Add
Multicast Route button (see “Adding and Updating an IP Route” on page 248).
6.2.4.1.3 Deleting a SIT Group

To remove SIT Groups from the database, select one or more items from the Grid Table in
the SIT Groups page and click the Delete button.
Alternatively, you can open the property page for the SIT Group to delete (see “Adding and
Updating a SIT Group” on page 180) and click the Delete button.

850176 P08
6.2.4.2 SIT Groups FL SLAs

Service Providers can partition the SP FL SLA bandwidth allocated to them into SIT Group
FL SLAs. This affords flexibility to offer different level of services to different SIT Groups.
Each SIT Group is assigned to a particular SIT Group FL SLA and receives all its Forward
Link traffic bound by it.
The SIT Groups FL SLAs page displays the list of SIT Group FL SLAs configured so far
in the NetManager; it is accessed by selecting the SG FL SLA item from the SIT Groups
sub-menu in the navigation bar’s CFG Services menu (see Figure 6.18).
Figure 6.18: SIT Groups FL SLAs page

850176 P08
The following parameters are displayed for each SIT Group FL SLA:
Field Description
SIT Group FL SLA The name that identifies the SIT Group Forward Link
PID The PID assigned to the SIT Groups FL SLA.
Multicast PID The multicast PID for the SG FL SLA.
Min. Guaranteed Capacity The minimum bit rate that is guaranteed to SIT
(kbit/s) Groups that subscribe to this SLA.
Min. Guar. Oversub. Factor The guaranteed minimum oversubscription factor for
the SIT Group FL SLA.
Maximum Capacity (kbit/s) The maximum bit rate available to SIT Groups that
subscribe to this SLA.
Max. Oversub. Factor The maximum oversubscription factor for the SIT
Group FL SLA.
SP FL SLA The name of the Service Provider FL SLA to which
the SIT Group FL SLA is associated.
Table 6.16 SIT Groups FL SLAs page fields
• Add/Update a SIT Group FL SLA: you can create or modify a SIT Group FL SLA.
For more information, see “Adding and Updating a SIT Group FL SLA” on page 186.
Note: Only Administrators have the rights to modify SIT Group FL SLAs; other
categories of user can use the View button.
• Delete a SIT Group FL SLA: you can select one or more SIT Group FL SLAs from
the Grid Table and delete them from the database. For more information, see “Deleting
a SIT Group Forward Link SLA” on page 194.
6.2.4.2.1 Adding and Updating a SIT Group FL SLA

To update an existing SIT Group FL SLA, select it from the Grid Table in the SIT Groups
FL SLAs page and click the Update button, or to add a new SIT Group, click the Add but-
ton. This brings up the SIT Group Forward Link SLA property page as shown in Figure
6.19. Two types of pages are available depending on the SIT Groups FL SLA chosen. The
first figure (see Figure 6.19) depicts a G FL SLA linked to a DVB-S2 ACM transport
stream and the second figure (see Figure 6.20) depicts a SG FL SLA linked to a DVB-S
transport stream.

850176 P08
Figure 6.19: G FL SLA linked to a DVB-S2 ACM Transport Stream Page

850176 P08
Figure 6.20: SG FL SLA linked to a DVB-S Transport Stream Page
On either page, modify the SIT Group Forward Link SLA as required and click the Update
or Add button, the case being. The SIT Group Forward Link SLA fields for the G FL SLA
linked to a DVB-S2 ACM Transport Stream are described in Table 6.17 and the SIT Group

850176 P08
Forward Link SLA fields for SG FL SLA linked to a DVB-S transport stream are described
in Table 6.18.
Field Description
SIT Group FL SLA Name The name that identifies this SIT Group FL SLA.
SP FL SLA
Service Provider FL SLA The name of the SP FL SLA from which the
bandwidth for the SIT Group FL SLA will be
allocated.
Transport Stream ID The Transport Stream ID associated to the selected
Service Provider FL SLA.
Type The service category provided by the SP FL SLA
from which the SIT Group FL SLA will be
allocated.
Min. Capacity Guaranteed The minimum bit rate that is guaranteed for the SP
(kbit/s) FL SLA from which the SG FL SLA is allocated.
Max. Capacity (kbit/s) The maximum bit rate available for the SG FL SLA.
MAC Properties
Multicast PID The Multicast Packet Identifier that members of this
SIT Group FL SLA will listen to; it narrows down
the number of packets they have to look at to find
traffic directed to them.
Note: If an SP PID Range is defined for the

Service Provider, the PID in this field must
be unique within the SP PID range or the
entry will be rejected.

850176 P08
Field Description
Traffic Shaping
Service Category The Service Category associated with this SIT
Group FL SLA. The available categories are: CBR,
UBR, VBR and optionally ATM.
• If the SP FL SLA service category is CBR, then
the SG FL SLA Service Category can be CBR,
VBR, UBR.
• If the SP FL SLA service category is VBR, only
VBR and UBR are allowed for the SG FL SLA
Service Category.
• If the SP FL SLA service category is UBR, only
UBR is allowed for the SG FL SLA Service
Category.
Minimum Guaranteed Capac- The Minimum Guaranteed Capacity for this SG FL
ity (kbit/s) SLA (if applicable).
Warning: In the absence of a full CCS, no check

is done to ensure that the rates of an
SG FL SLA exceed the rate of the IP
DVB Encapsulator used.
Maximum Capacity (kbit/s) The Maximum Capacity for this SG FL SLA (if
applicable).
Warning: In the absence of a full CCS, no check

is done to ensure that the rates of an
SG FL SLA exceed the rate of the IP
DVB Encapsulator used.
DVB-S2 PID Assignment 1 (allocates the PID to each MODCOD)

MODCOD Name Name of MODCOD
PID (MODCOD disabled if left PID for the MODCOD
blank)
blank)

850176 P08
Field Description

blank)
Table 6.17 SIT Group Forward Link SLA fields for G FL SLA linked to a DVB-S2 ACM Transport
Stream

850176 P08
Field Description
SIT Group FL SLA Name The name that identifies the SIT Group Forward Link
SP FL SLA
Transport Stream ID The ID for the Transport Stream.
Type The service category provided by the SP FL SLA
from which the SIT Group FL SLA will be allocated.
Min. Capacity Guaranteed The minimum bit rate that is guaranteed for the SP FL
(kbits/s) SLA from which the SG FL SLA is allocated.
Maximum Capacity (kbit/s) The maximum bit rate available for the SG FL SLA.
MAC Properties
Unicast PID The Unicast Packet Identifier that members of this
SIT Group FL SLA will listen to; it narrows down the
number of packets they have to look at to find traffic
directed to them.
Note: If an SP PID Range is defined for the

Service Provider, the PID in this field
must be unique within the SP PID
range or the entry will be rejected.

850176 P08
Field Description
Multicast PID The Multicast Packet Identifier that members of this

SIT Group FL SLA will listen to; it narrows down the
number of packets they have to look at to find traffic
directed to them.
Note: If an SP PID Range is defined for the Service

Provider, the PID in this field must be unique
within the SP PID range or the entry will be
rejected.
Traffic Shaping
Service Category The Service Category associated with this SIT Group
FL SLA. The available categories are: CBR, UBR,
VBR and optionally ATM.
• If the SP FL SLA service category is CBR, then
the SG FL SLA Service Category can be CBR,
VBR, UBR.
• If the SP FL SLA service category is VBR, only
VBR and UBR are allowed for the SG FL SLA
Service Category.
• If the SP FL SLA service category is UBR, only
UBR is allowed for the SG FL SLA Service
Category.
Minimum Guaranteed The Minimum Guaranteed Capacity for this SG FL
Capacity (kbits/s) SLA (if applicable).

done to ensure that the rates of an SG
FL SLA exceed the rate of the IP DVB
Encapsulator used.
Maximum Capacity (kbits/s) The Maximum Capacity for this SG FL SLA (if
applicable).

done to ensure that the rates of an SG
FL SLA exceed the rate of the IP DVB
Encapsulator used.
Table 6.18 SIT Group Forward Link SLA fields for SG FL SLA linked to a DVB-S Transport Stream

850176 P08
To return to the SIT Group FL SLAs page, click the < Back To SG FL SLAs button.
6.2.4.2.2 Deleting a SIT Group Forward Link SLA

To remove SIT Group FL SLAs from the database, select one or more items from the Grid
Table in the SIT Groups FL SLAs page and click the Delete button.
Alternatively, you can open the property page for the SIT Group Forward Link SLA to
delete (see “Adding and Updating a SIT Group FL SLA” on page 186) and click the Delete
button.
6.2.5 Services to SITs

SITs have access to bandwidth on the Forward Link and Return Link based on Quality of
Service settings. To make configuration easier, global QoS settings, called Default SIT
QoS, are configured in SIT Groups; these will apply to all SITs that belong to the particular
group, unless an individual SIT overwrites the RL QoS settings (see “Overwriting RL QoS”
on page 232) or a Routes overwrites the FL QoS settings (see “Viewing IP Routes” on page
247).
6.2.5.1 Viewing Default SIT Return Link QoS Profiles

The Default SIT Return Link QoS page displays the list of Return Link Quality of Service
Profiles that can be assigned to SIT Groups as default RL QoS for SITs belonging to them.

850176 P08
To view the page, select the RL QoS item from the SIT Services sub-menu in the naviga-
tion bar’s CFG Services menu.
Figure 6.21: Default SIT Return Link QoS page

850176 P08
The following parameters are displayed for Default SIT RL QoS’:
Field Description
RL QoS The name that identifies the Return Link Quality of Service.
CRA (kbit/s) The CRA traffic bit rate for this RL QoS.
Constant Rate Assignments (CRA) is DVB-RCS specific
terminology for constant capacity on the Return Link that does
not need to be requested.
Because of its constant nature and the fact that it does not need
to be requested, it is especially suited for applications that
require constant throughput, low delays and low jitter.
RBDC (kbit/s) The RBDC traffic bit rate for the selected RL QoS.
Rate-Based Dynamic Assignments (RBDC) is DVB-RCS
specific terminology for variable capacity on the Return Link
that needs to be requested as a rate.
It is called persistent traffic because the RBDC capacity does not
need to be requested at the scheduling time interval. Without
updates, the capacity is granted at the same rate for up to one
second. Because of its relatively constant nature, it is especially
suited for applications that require relatively constant
throughput.
Because the overbooking can be controlled, it can accommodate
applications that require moderately low delays and low jitter.
VBDC Max (kbit/s) The maximum VBDC traffic bit rate for the RL QoS.
Volume-Based Dynamic Assignments (VBDC) is DVB-RCS
specific terminology for variable capacity on the Return Link
that needs to be requested as a quantity (volume).
It is called best-effort traffic because the VBDC traffic is granted
as a lower priority than persistent (RBDC) and constant (CRA)
traffic.
Because of its bursty nature, it is especially suited for
applications that require intermittently high throughput but are
robust to jitter and delays.
FCA Reflects whether or not the RL QoS is FCA enabled.
Table 6.19 Default SIT Return Link QoS fields

850176 P08
• Add/Update a SIT RL QoS: you can create or modify a SIT RL QoS. For more infor-
mation, see “Adding and Updating a SIT RL QoS” on page 197.
• Delete a SIT RL QoS: you can select one or more SIT RL QoSs from the Grid Table
and delete them from the database. For more information, see “Deleting a Default SIT
Return Link QoS” on page 199.
6.2.5.1.1 Adding and Updating a SIT RL QoS

To update an existing RL QoS, select it from the Grid Table in the Default SIT Return
Link QoS page and click the Update button, or to add a new RL QoS, click the Add but-
ton. This brings up the Default SIT Return Link QoS property page as shown in Figure
6.22.
Figure 6.22: Default SIT Return Link QoS page

850176 P08
Modify the Return Link SIT Level QoS as required and click the Update or Add button, the
case being. The RL QoS fields are described in Table 6.20.
Field Description
Return Link QoS Name The name that identifies the Return Link SIT QoS.
Constant Traffic (CRA) The CRA traffic bit rate for this RL QoS. Constant Rate
(kbit/s) Assignments (CRA) is DVB-RCS specific terminology for
constant capacity on the Return Link that does not need to
be requested.
Because of its constant nature and the fact that it does not
need to be requested, it is especially suited for applications
that require constant throughput, low delays and low jitter.
Persistent Traffic (RBDC) The RBDC traffic bit rate for the selected RL QoS. Rate-
(kbit/s) Based Dynamic Assignments (RBDC) is DVB-RCS
specific terminology for variable capacity on the Return
Link that needs to be requested as a rate.
It is called persistent traffic because the RBDC capacity
does not need to be requested at the scheduling time
interval. Without updates, the capacity is granted at the
same rate for up to one second. Because of its relatively
constant nature, it is especially suited for applications that
require relatively constant throughput.
Because the overbooking can be controlled, it can
accommodate applications that require moderately low
delays and low jitter.
Table 6.20 Default SIT Return Link QoS page fields

850176 P08
Field Description
Max Best-effort Traffic The VBDC maximum traffic bit rate for the selected RL
(VBDC) (kbit/s) QoS. Volume-Based Dynamic Assignments (VBDC) is
DVB-RCS specific terminology for variable capacity on
the Return Link that needs to be requested as a quantity
(volume).
It is called best-effort traffic because the VBDC traffic is
granted as a lower priority than persistent (RBDC) and
constant (CRA) traffic.
Because of its bursty nature, it is especially suited for
applications that require intermittently high throughput but
are robust to jitter and delays.
Left-over Capacity (FCA) Determines whether the RL QoS is FCA enabled or not.
This is the left over Return Link throughput capacity
available to subscribers of this QoS without having to
signal a request for it.
Table 6.20 Default SIT Return Link QoS page fields
To return to the Default SIT Return Link QoS page, click < Back To RL QoS Profile.
6.2.5.1.2 Deleting a Default SIT Return Link QoS

To remove SIT Group Return Link QoS profiles from the database, select one or more items
from the Grid Table in the Default SIT Return Link QoS page and click the Delete button.
Alternatively, you can open the property page for the SIT Return Link QoS to delete (see
“Adding and Updating a SIT RL QoS” on page 197) and click the Delete button.

850176 P08
6.2.5.2 Viewing Default SIT Forward Link QoS Profiles

The Default SIT Forward Link QoS page (see Figure 6.23) displays the list of Forward
Link Quality of Service Profiles that can be assigned to SIT Groups as default FL QoS for
SITs belonging to them. To view the page, select the FL QoS item from the SIT Services
sub-menu in the navigation bar’s CFG Services menu.
Figure 6.23: Default SIT Forward Link QoS page
The following parameters are displayed for each Default SIT Forward Link QoS:
Field Description
FL QoS The name that identifies the Forward Link SIT Quality of
Service.
Min. Guaranteed Rate The minimum guaranteed bit rate for the SIT FL QoS.
Maximum Rate (kbit/s) The maximum available bit rate for the SIT FL QoS.
Maximum Priority The maximum priority for this FL QoS.
Table 6.21 Default SIT Forward link QoS page fields

850176 P08
• Add/Update a SIT FL QoS: you can create or modify a default SIT FL QoS and save
it into the database. For more information, see “Adding and Updating a Forward Link
SIT Level QoS” on page 201.
• Delete a SIT FL QoS: you can select one or more SIT FL QoS’s from the Grid Table
and delete them from the database. For more information, see “Deleting a Forward
Link SIT Level QoS” on page 203.
6.2.5.2.1 Adding and Updating a Forward Link SIT Level QoS

To update an existing FL QoS, select it from the Grid Table in the Default SIT Forward
Link QoS page and click the Update button, or to add a new FL QoS, click the Add button.
This brings up the Forward Link SIT Level QoS property page as shown in Figure 6.24.
Figure 6.24: Forward Link SIT Level QoS page

850176 P08
Modify the Forward Link SIT Level QoS as required and click the Update or Add button,
the case being. The FL QoS fields are described in Table 6.22:
Field Description
Forward Link FL QoS The name that identifies the Forward Link SIT QoS.
Name
Note: You should choose a name describing the type
of route (OAM or traffic) that will use this QoS.
Minimum Guaranteed The minimum bit rate guaranteed to SITs that subscribe
Rate (kbit/s) to this FL QoS; the minimum increment is 1 kbit/s.
Note: The capacity entered here is not automatically

validated against Forward Link SLA nor
against IP DVB Encapsulator limits.
Note: Guaranteed capacity is not allowed in a system

without a Novra IPE or a Packeteer IP DVB
Encapsulator.
Maximum Rate (kbit/s) The maximum available bit rate for SITs that subscribe to
this FL QoS; the minimum increment is 1 kbit/s.
Note: The capacity entered here is not automatically

validated against Forward Link SLA nor
against IP DVB Encapsulator limits.
Note: Guaranteed capacity is not allowed in a system

without a Novra IPE or a Packeteer IP DVB
Encapsulator.
Maximum Priority The maximum priority given to this FL QoS.

Table 6.22 Forward Link SIT Level QoS page fields
To return to the Default SIT Forward Link QoS, click the < Back To FL QoS Profile but-
ton.

850176 P08
6.2.5.2.2 Deleting a Forward Link SIT Level QoS

To remove SIT FL QoS profiles from the database, select one or more items from the Grid
Table in the Default SIT Forward Link QoS page and click the Delete button.
Alternatively, you can open the property page of the SIT Forward Link QoS to remove (see
“Adding and Updating a Forward Link SIT Level QoS” on page 201) and click the Delete
button.
6.2.5.3 RL Queue Filters

The Default SIT RL Queue Filter page (see Figure 6.25) displays the list of RL Queue fil-
ters. To view the page, select the RL Queue Filter item from the SIT Services sub-menu in
the navigation bar’s CFG Services menu.
Figure 6.25: Default SIT RL Queue Filter page

850176 P08
The following parameters are displayed for SIT RL Queue Filters:
Field Description
Name The name of the Queue Filter.

IP Destination The destination IP Address for the Queue Filter.
Address
Protocol The protocol associated with the Filter.
TOS The TOS associated with the Filter.
Source Port The source port for the Filter.
Destination Port The destination port for the Filter
Table 6.23 Default SIT RL Queue Filter page fields
• Add/Update a Filter: you can create or modify a Filter on the Return Link, see
“Adding and Updating an RL SIT Queue Filter” on page 205.
• Delete a Filter: you can select one or more Filters from the Grid Table and delete them
from the database. For more information, see “Deleting an RL SIT Queue Filter” on
page 206.

850176 P08
6.2.5.3.1 Adding and Updating an RL SIT Queue Filter

To update an existing Filter, select it from the Grid Table in the Default SIT RL Queue Fil-
ter page and click the Update button, or to add a new Filter, click the Add button. This
brings up the Default RL SIT Queue Filter property page as shown in Figure 6.26.
Figure 6.26: Default RL SIT Queue Filter

850176 P08
Modify the Filter as required and click the Update or Add button, the case being. The Filter
Field Description
Return Link Queue Filter The name of the Filter.

Name
Destination IP Address The destination IP Address for the Filter.
Destination IP Mask The destination IP Mask for the Filter.
Protocol The protocol associated with the Filter.
Protocol Type Mask The protocol mask associated with the Filter.
TOS Field The TOS associated with the Filter.
TOS Field Mask The TOS mask associated with the Filter.
Source Port The Source Port associated with the Filter.
Source Port Mask The Source Port mask associated with the Filter.
Destination Port The Destination Port associated with the Filter.
Destination Port Mask The Destination Port mask associated with the Filter.
Table 6.24 Default RL SIT Queue Filter page fields
To return to the Default SIT RL Queue Filter page, click < Back To RL Queue Filters.
6.2.5.3.2 Deleting an RL SIT Queue Filter

To remove Filters from the database, select one or more items from the Grid Table in the
Default SIT RL Queue Filter page and click the Delete button.
Alternatively, you can open the property page for the Filter to delete (see “Adding and
Updating an RL SIT Queue Filter” on page 205) and click the Delete button.

850176 P08
6.2.5.4 Return Link QoS Scaling

RL QoS Scaling is used to throttle the QoS of SITs that use a given SLA conditioning; this
is useful if the SLA is used, for example, in rain fade conditions, to allow SITs to access it
with lower QoS, but still proportional to their configured settings. The RL QoS Scalings
page displays the list of RL QoS Scaling profiles. To view the page, select the RL QoS
Scaling item from the SIT Services sub-menu in the navigation bar’s CFG Services menu.
Figure 6.27: RL QoS Scalings page

850176 P08
The following parameters are displayed for RL QoS Scalings:
Field Description
Name The name of the QoS Scaling.

Conditional Con- The scaling factor applied to Constant Traffic.
stant Traffic (CRA)
(%)
Conditional Persis- The scaling factor applied to Persistent Traffic.
tent Traffic
(RBDC) (%)
Conditional Bursty The scaling factor applied to Bursty Traffic.
Traffic (VBDC)
(%)
Conditional Left- Reflects whether or not use of Left-Over Capacity is allowed.
Over Capacity
(FCA)
Table 6.25 RL QoS Scalings page fields
• Add/Update an RL QoS Scaling: you can create or modify a QoS Scaling on the
Return Link, see “Adding and Updating an RL QoS Scale” on page 209.
• Delete an RL QoS Scale: you can select one or more RL QoS Scalings from the Grid
Table and delete them from the database. For more information, see “Deleting an RL
QoS Scaling Profile” on page 210.

850176 P08
6.2.5.4.1 Adding and Updating an RL QoS Scale

To update an existing RL QoS scale, select it from the Grid Table in the RL QoS Scaling
page and click the Update button, or to add a new RL QoS Scaling, click the Add button.
This brings up the RL QoS Scaling property page as shown in Figure 6.28.
Figure 6.28: RL QoS Scaling page
Modify the Return Link QoS Scale as required and click the Update or Add button, the
case being. The RL QoS Scaling fields are described in Table 6.26.
Field Description
Name The name of the QoS Scaling.

Conditional Constant The scaling factor applied to Constant Traffic.
Traffic (CRA) (%)
Conditional Persistent The scaling factor applied to Persistent Traffic.
Traffic (RBDC) (%)
Conditional Bursty Traf- The scaling factor applied to Bursty Traffic.
fic (VBCDC) (%)
Conditional Left-Over Select this option to allow use of Left-Over Capacity.
Capacity (FCA)
Table 6.26 RL QoS Scaling page fields
To return to the RL QoS Scalings page, click < Back To RL QoS Scalings.

850176 P08
6.2.5.4.2 Deleting an RL QoS Scaling Profile

To remove RL QoS Scalings from the database, select one or more items from the Grid
Table in the RL QoS Scaling page and click the Delete button.
Alternatively, you can open the property page for the RL QoS Scaling to delete (see “Add-
ing and Updating an RL QoS Scale” on page 209) and click the Delete button.

850176 P08
6.2.5.5 Multicast Scheduling

The Multicast Scheduling page (see Figure 6.29) permits the scheduling of multicast
events. To view the page, select the Multicast Scheduling item from the SIT Services sub-
menu in the navigation bar’s CFG Services menu.
Figure 6.29: Multicast Scheduling page

850176 P08
The following parameters are displayed for Scheduling page:
Field Description
Name The name identifying the Multicast Event.

Active Reflects whether or not the event is currently active.
Description Describes the recurrence pattern of the event.
Table 6.27 Multicast Scheduling page fields
• Add/Update a Multicast Event: you can add or modify a scheduled multicast event,
see “Adding and Updating Multicast Scheduling” on page 212.
• Delete a Multicast Event: you can select one or more Events and delete them from the
schedule. For more information, see “Deleting Scheduled Multicast Event” on page
215.
You can navigate back to the Service Provider page by clicking the < Back to Service Pro-
vider button.
6.2.5.5.1 Adding and Updating Multicast Scheduling

To update an existing scheduled Multicast event, select it from the Grid Table in the Multi-
cast Scheduling page and click the Update button, or to add a new one, click the Add but-
ton. This brings up the Multicast Scheduling Property page as shown in Figure 6.30.
Figure 6.30: Multicast Scheduling Property page

850176 P08
Modify the scheduled Multicast event as required and click the Update or Add button, the
case being; the fields are described in Table 6.28.
Field Description
Service Provider The Service Provider to which the Scheduled Multicast

Event applies.
Condition Set The name identifying the scheduled Multicast Event.
Schedule (use recurrence Describes the recurrence characteristics of the event; this
GUI) can be edited using the Recurrence button (see “Editing
Event Recurrence” on page 213).
Table 6.28 Multicast Scheduling Property page fields
The recurrence characteristics of the Scheduled Multicast Event can be edited by clicking
the Recurrence button (see “Editing Event Recurrence” on page 213).
To return to the Multicast Scheduling page, click < Back to Scheduling.
6.2.5.5.2 Editing Event Recurrence

The recurrence pattern of a Multicast Event can be edited using the GUI provided (see Fig-
ure 6.31), which can be accessed by clicking the Recurrence button in the Multicast Event
Property page (see “Adding and Updating Multicast Scheduling” on page 212).
Figure 6.31: Multicast Scheduling Recurrence

850176 P08
The following fields are available to configure event recurrence (see Table 6.29):
Field Description
Time Span (GMT)

Start Time The starting time for the scheduled event.
End Time The stop time for the scheduled event.
Duration Displays the duration of the event, based on the configured
start and stop times.
Recurrence Pattern
left-hand side column Select the time unit for the recurrence pattern; this will
affect the available selection in the right-hand side
column.
• Daily: select recurrence in number of days or every
weekday (see Figure 6.32)
• Weekly: select recurrence in number of weeks, specify-
ing the day of the week (see Figure 6.33).
• Monthly: select either the nth day of every X month, or
an ordinal indication of given days (weekend days, etc.)
of every X month (see Figure 6.34).
• Yearly: select either month and day of the month, or an
ordinal indication of given days (weekend days, etc.) of
a given month (see Figure 6.35).
Recurrence Range
Start Clicking the ... button opens a calendar to select the start
date for the Scheduled Multicast Event.
End The end date can be selected as either ending after X
occurrences of the event (up to a maximum of 100), or by
clicking the ... button and selecting a date from the
calendar.
Table 6.29 Multicast Event Recurrence fields
Figure 6.32: Daily Scheduling Recurrence options

850176 P08
Figure 6.33: Weekly Scheduling Recurrence options
Figure 6.34: Monthly Scheduling Recurrence options
Figure 6.35: Yearly Scheduling Recurrence options
Clicking on the Save and Exit button closes the pop-up window and associates the recur-
rence pattern with the Scheduled Multicast Event being edited.
6.2.5.5.3 Deleting Scheduled Multicast Event

To remove a Scheduled Multicast Event, select one or more items from the Grid Table in
the Multicast Scheduling page and click the Delete button.
Alternatively, you can open the property page for the Scheduled Multicast Event to delete
(see “Adding and Updating Multicast Scheduling” on page 212) and click the Delete but-
ton.

850176 P08
6.2.5.6 SIT Software Versions

The SIT Software Versions page (see Figure 6.36) permits the management of terminal
software revisions. To view the page, select the SIT S/W Version item from the SIT Ser-
vices sub-menu in the navigation bar’s CFG Services menu.
Figure 6.36: SIT Software Versions
The following parameters are displayed for SIT Software Versions:
Field Description
Name The name of the SIT Software Version

Manufacturer The manufacturer for the type of SIT associated with the
Software version.
File Name The file containing the Software Version.
Table 6.30 SIT Software Versions page fields
• Add/Update a SIT Software Version: you can add or modify a Software Version, see
“Adding and Updating Software Versions” on page 217.
• Delete a Software Version: you can select one or more Software Versions and delete
them. For more information, see “Deleting Software Versions” on page 218.

850176 P08
6.2.5.6.1 Adding and Updating Software Versions

To update an existing Software Version, select it from the Grid Table in the SIT Software
Versions page and click the Update button, or to add a new one, click the Add button. This
brings up the Software Version property page as shown in Figure 6.37.
Figure 6.37: SIT Software Version page
Modify the SIT Software Version as required and click the Update or Add button, the case
being. The Software Version fields are described in Table 6.31.
Field Description
Version Name The name identifying the version.

Manufacturer The Software Version’s manufacturer.
Software File Name (in / The SIT software image file name.
var/sit_sw/)
Features The list of features for the Software Version.
Table 6.31 SIT Software Version page fields
To return to the SIT Software Versions page, click < Back to Sit Software Ver.

850176 P08
6.2.5.6.2 Deleting Software Versions

To remove Software Versions, select one or more items from the Grid Table in the SIT
Software Versions page and click the Delete button.
Alternatively, you can open the property page for the SIT Software Version to delete (see
“Adding and Updating Software Versions” on page 217) and click the Delete button.
6.3 Availability Services

6.3.1 RFCM Configuration
The following procedure outlines the steps needed to configure RFCM on a system.
1. Create the Return Link structure, including Superframes with different up link power
control targets on the Carrier to Noise (C/N) scale. The most common way to ensure
this requirement is to have Superframes with different user carrier rates (e.g. 2 Mbps, 1
Mbps, 512 kbps). The Superframes can be created either using the NetManager (see
“Viewing Carrier Sets (Superframes)” on page 113) or using the RLSS’s RMI and
imported into the NetManager (see “Importing RLSS Configurations” on page 138).
2. Enhance the Return Link structure with Areas included in the Superframes defined in
the previous step. The Areas can be created using the NetManager (see “Viewing
Areas” on page 118) or using the RLSS’s RMI and imported into the NetManager (see
3. Enhance the Return Link structure with Return Link Partitions (segments) included in
the areas defined in the previous step. Pay attention to the setting of the RFCM
thresholds (the user will be given an opportunity to adjust them in step 6 below). These
thresholds are set as per a Energy per symbol over noise scale (Es/No). The Return
Link Partitions can be created using the NetManager (see “RL Partitions (Segments)”
on page 123) or using the RMI and imported into the NetManager with the "Create SP-
RL-SLA" box of the File Import GUI unchecked (see “Importing RLSS
Configurations” on page 138); in either case, a LL-RL-SLA will be created per RL
partition (segment).
4. Create a SP-RL-SLA (see “Viewing Service Provider Return Link SLAs” on page
158) to join all the LL-RL-SLA to participate in a structure to enable RFCM for one or
many SIT groups (e.g. one LL-RL-SLA for 2 Mbps, one for 1 Mbps).
5. Update the LL-RL-SLAs (see “Low Level Return Link SLAs” on page 162); ensure
that the SP filter on the LL-RL-SLA table is set to "All" by specifying the SP-RL-SLA

850176 P08
created in the previous step and their respective RFCM level (e.g. Clear Sky for the
LL-RL-SLA at 2 Mbps and Rain 1 for the LL-RL-SLA at 1 Mbps). In the same GUI,
update the Precedence level to be unique per LL-RL-SLA. It is advisable to have lower
precedence level for LL-RL-SLA higher on the C/N scale (e.g. 1 for Clear Sky and 2
for Rain 1). The precedence level tells the Connection Manager in which order to
perform Connection Admission Control (CAC) on the LL-RL-SLA upon login or
RFCM change requests.
6. Verify that there is hysteresis in the position of all the RFCM thresholds on the C/N
scale using the RFCM columns of the LL-RL-SLA table, sorted by SP-RL-SLA.
Ideally, a graph such as that shown in Figure 6.38 would be useful to identify the
amount of hysteresis provided by a configuration. When not enough hysteresis is
provided, oscillation between protection levels may occur. If needed, the user may
modify the thresholds by updating them in the RL Partition (see “RL Partitions
(Segments)” on page 123).
Figure 6.38: RFCM Modes hysteresis

850176 P08
7. It may be advisable to create RL QoS Scaling profiles (see “Return Link QoS Scaling”
on page 207), to account for the fact that the LL-RL-SLA that are lower on the C/N
scale have typically lower user carrier rates and therefore cannot grant the same QoS
profile as the LL-RL-SLA that are higher on the C/N scale. 
For example, a SIT with 2 Mbps Best-Effort traffic (VBDC Max) setting on a 2 Mbps
Clear Sky LL-RL-SLA will be refused usage of the Rain 1 LL-RL-SLA with user
carrier rate of 1 Mbps, unless a scaling profile of 50% or less Best-Effort traffic
(VBDC Max) is configured with the RL-SLA conditioning of the Rain 1 LL-RL-SLA.
If needed, create the appropriate RL QoS Scaling profile(s).
8. Update the Conditioning of the LL-RL-SLA (see “Adding and Updating SLA
Conditioning” on page 171) that warrants a RL QoS profile. Note that the absence of
RL QoS Scaling implies a 100% scaling across all traffic types. Choose the RL QoS
Scaling profile that will maximize the probability of the CAC to grant access to the
LL-RL-SLA. Note that all SITs using the LL-RL-SLA will be subject to the same
scaling profile, those with or without overwritten RL QoS. In order to have SITs using
the same RL Partition with a different RL QoS Scaling profiles, the LL-RL-SLA
should be cloned, and configured to point to a different SP-RL-SLA. This is however
outside the scope of this procedure.
9. Update the SIT group(s) (see “SIT Group Configuration” on page 178) that are to be
use RFCM such that their RL SLA is the SP-RL-SLA defined in step 4 of this
procedure.
At this point, all SITs in the SIT group(s) modified in step 9 above will be allowed RFCM
upon their next login.
Note: Successful RFCM changes create a CM event (see “Viewing Events” on

page 289) and unsuccessful ones create a CM Alarm (see “Viewing Alarms”
on page 291).

850176 P08
Chapter 7 Configuring Network
This chapter explains the tasks related to configuring SITs; it details the following topics:
• “Configuring Network Overview” on page 222 provides a summary of network config-
uration.
• “SIT Profiles” on page 224 deals with management of individual SITs.
• “SIT Queues” on page 238 explains how to view SIT traffic reports.
• “IP Routes” on page 247 explains the configuration of IP Routes.
• “SIT Control System” on page 251 explains the configuration of IP Routes.
• “VLAN” on page 252 Describes VLAN functionalities.
• “Ranges” on page 259 explains the configuration of IP Routes.

850176 P08
7.1 Configuring Network Overview

The CFG Network menu of the navigation bar provides access to the menu items related to
configuring the network managed by NetManager. Clicking on the first menu item, Net-
work View, brings up the Network View page (see Figure 7.1) that graphically represents
the different conceptual network elements.
page 41.
Figure 7.1: Network View page
The sub-menus available for Network configuration are:
Figure 7.2: CFG Network Submenus
• SIT: This menu item permits configuration of SITs (see “SIT Profiles” on page 224).
• Traffic Queues: This menu item permits configuration of SIT Queues (see “SIT
Queues” on page 238).

850176 P08
• FL Routes: This menu item permits configuration of IP Routes (see “IP Routes” on
page 247).
• VLAN: Provides access to VLAN management features (see “VLAN” on page 252).
• VLAN View, see “VLAN View” on page 252.
• Address Space, see “VLAN Address Space” on page 253.
• ISP-Side Network, see “VLAN ISP-Side Network” on page 256.
• Ranges: This menu item groups sub-items for various Signaling quantities assignment
(see “Ranges” on page 259), namely:
• IP Address: permits the configuration of IP Address ranges; see “Viewing Service
Provider IP Address Ranges” on page 259.
• VCC: permits the configuration of VCC ranges; see “Viewing SP VCC Ranges” on
page 262.
• PID: permits the configuration of PID ranges; see “Viewing SP PID Ranges” on
page 265.
• Mesh View: presents a graphical interactive view of the current Mesh Network config-
uration, see “Mesh View” on page 269.

850176 P08
7.2 SIT Profiles

A SIT Profile defines the attributes associated with a particular physical terminal, providing
NetManager with the information it needs to manage it. Every SIT Profile is associated with
a SIT Group that defines the services it uses.
7.2.1 Viewing SITs

The list of SITs configured so far is available from the SITs page (see Figure 7.3). To access
this page, select the SIT item from the navigation bar’s CFG Network menu.
Figure 7.3: SITs page

850176 P08
This page lists each SIT profile with the following parameters:
Field Description
SIT The name that identifies the SIT.

MAC Address The SIT's unique MAC Address.
IP Address The IP Address assigned to the SIT.
FP PEPed The PEP enable/disable status of IDUs in Traffic-Ready
state. The NetManager uses SNMP to change the status
in the IDU. In order to synchronize this state in termi-
nal(s): select the relevant SIT(s) and click the FP-PEP
Synchronize button.
Note: This status is also synchronized with Routers.
Note: If the terminal is not in traffic ready at the time

of configuration (which is normally the case) or at
time of updates to this status, the command is stored
in the queue of commands and executed the next
time the terminal reaches the “Traffic Ready” state.
SIT Group The Group to which the SIT belongs.

OW FL QoS This field reflects whether or not the SIT has overwritten
the SIT Group’s Forward Link QoS.
• YES: (in green font) the Default FL QoS has been
overwritten.
• NO: the SIT is subject to the SIT Group’s FL QoS.
OW RL QoS This field reflects whether or not the SIT has overwritten
the SIT Group’s Return Link QoS.
• YES: (in green font) the Default RL QoS has been
overwritten.
• NO: the SIT is subject to the SIT Group’s RL QoS.
Table 7.1 SITs page fields

850176 P08
Field Description
IP Routes This field reflects whether IP Routes are defined for this
SIT.
• YES: (in green font) IP Routes defined.
• NO: IP Routes not defined.
Queues The list of Queues assigned to the SIT.
Table 7.1 SITs page fields
• Add/Update a SIT Profile: you can create or modify a SIT Profile. For more informa-
tion, see “Adding and Updating a SIT Profile” on page 227.
• Delete a SIT Profile: you can select one or more SIT Profiles from the Grid Table and
delete them from the database. For more information, see “Deleting a SIT Profile” on
page 232.
• Synchronize device configuration: by clicking the Synchronize FP PEP button.

850176 P08
7.2.1.1 Adding and Updating a SIT Profile

This feature allows you to manually add a new terminal for NetManager to manage, or
modify the attributes of a terminal already in the system.
Note: When adding a SIT, the NetManager checks that the number of SIT profiles
that are linked to the SIT group is smaller than the maximum of allowed
terminals for the SP and the NetManager license.
Note: The application also allows for importing previously saved SIT
configurations: see “SIT File Import” on page 141.
WARNING: When a SIT is added, an OAM queue is configured automatically;

traffic will flow through the system only when the queue information is
consistent between the NetManager and SIT databases (see “Queue
Types” on page 238).
To update a SIT Profile, select it from the Grid Table in the SITs page and click the Update
button, or to add a new SIT, click the Add button. This brings up the SIT property page as
shown in Figure 7.4 (page 228).

850176 P08
Figure 7.4: SIT page

850176 P08
You can modify the SIT Profile as required and click the Update or Add button, the case
being, to commit your changes. The SIT Profile fields are described in Table 7.2:
Field Description
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
(00:00:00:00:00:00) MAC address is a 6 byte value; its format is:
xx:xx:xx:xx:xx:xx
Customer The customer serviced by the SIT.
Ethernet IP The IP Address and Mask for the SIT's Ethernet-side (LAN).
Address/Mask (deci- The IP part is specified in decimal while the network mask is in
mal/CIDR mask) the CIDR format.
Note: The Ethernet IP Address must be unique and

within the range of SP IP Addresses Range with
Traffic usage type.
OAM IP Address The IP Address for the SIT's satellite side.

(decimal)
Note: The OAM IP Address must be unique and within
range of SP IP Addresses Range with OAM
usage type.
Flight Protocol PEP Determines whether or not the SIT uses Flight Protocol
Enabled Performance Enhancement Proxy acceleration.
Mesh Received Determines whether or not the SIT is enabled for Mesh
Enabled functionality.
SCPC Enabled Indicates if the SIT has an SCPC Return Link.
Automatic Ping Indicate if the SIT will automatically be pinged by the
Enabled NetManager. If not in Traffic Ready or OAM Ready, the
success or failure of a ping is used to determine if the SIT is in
a Sleep state.
Max Tx Rate The SIT's physical maximum symbol transmit rate: this can be
(kSymb/s) obtained from the terminal’s specifications. This value is
checked against the symbol rate of the RL SLAs linked by the
SIT group.
Table 7.2 SIT page fields

850176 P08
Field Description
Manufacturer The SIT manufacturer’s name.

Model The SIT’s model.
Note: If this parameter is set to 1000, then the CM does not

write to the SIT MIB.
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.
TX Disabled Prompts the RLSS to send a Tx Disable MAC command and
bring the SIT into “Transmit Disable” state.
When checked, disables transmission and brings the SIT into a
HOLD state.
Note: The HOLD state of the SIT is controlled by the

CM.
Manual Traffic Prevents the CM from writing to the SIT MIB.

VCC Configuration
SCS Parameters
CW Test Frequency The center wavelength used for testing the SIT.
(Hz)
S/W Version The SITs current software revision number.
Commissioning
X Coordinate (m) The X coordinate used in commissioning the SIT (sent by
SCS).
Y Coordinate (m) The Y coordinate used in commissioning the SIT (sent by
SCS).
Z Coordinate (m) The Z coordinate used in commissioning the SIT (sent by
SCS).

850176 P08
Field Description
View
Note: These parameters are not supported in this version of NetManager.
Segment Segment ID of the RLSS in which the SIT is logged or

“Unknown” otherwise.
Low Level SLA The low level RL SLA that the SIT is currently using (e.g.
Name Main, rain fade, etc.)
State The current State of the SIT.
RLSS ID The ID of the RLSS that manages the SIT.
Current S/W Ver- The software revision currently running on the terminal, as
sion decoded from the SIT capability field transferred to the CM.
VLAN
VLAN Tunnel IP If applicable, the automatically allocated VLAN Tunnel IP
Address (auto) Address for the SIT.
Network View area The Network view containing a graphical representation of the
network resources related to the SIT being displayed.
Note: General usage of the view pages is explained in

“Interactive View Pages” on page 41.

To return to the SITs page, click the < Back SIT Table button.
7.2.1.2 Additional navigation for SIT page

When viewing the SIT page, you can also:
• Access Traffic Queue management configuration features (see “SIT Queues” on page
238) by clicking on a specific Traffic Queue displayed in the Network View area.
• Add a Traffic Queue (see “SIT Queues” on page 238) by clicking on the Add Traffic
Queue (type, VCI, VPI, PID) element in the title bar of the Network View area.
• Overwrite the SIT's default RL QoS (inherited from its SIT Group) by clicking the RL
QoS > button (see “Overwriting RL QoS” on page 232).
• Access IP Route management configuration features (see “IP Routes” on page 247) by
clicking on a specific IP Route displayed in the Network View area.

850176 P08
• Add a FL Route (see “IP Routes” on page 247) by clicking on the Add FL Route ele-
ment in the title bar of the Network View area.
• Access the SIT Monitor and Control feature by clicking < SIT/Monitoring Control
button (see “Operations Overview” on page 272).
• Start CW test by clicking the Start CW Test button.
• Stop CW test by clicking the Stop CW Test button.
7.2.1.3 Deleting a SIT Profile

To remove SIT Profiles from the database, select one or more items from the Grid Table in
the SITs page and click the Delete button.
Alternatively, you can open the property page for the SIT Profile to delete (see “Adding and
Updating a SIT Profile” on page 227) and click the Delete button.
7.2.2 Overwriting RL QoS

7.2.2.1 SIT RL QoS
Each SIT inherits its RL QoS settings from the default QoS profiles of the SIT Group to
which it belongs. There may be situations when you want a specific SIT in the Group to use
different QoS settings than the default defined in the SIT Group. This is done by overwrit-
ing the SIT Group’s default QoS settings with new ones defined for the SIT Profile. In other
words, a SIT in a given Group uses the default QoS defined for the Group unless it over-
writes it in its individual SIT Profile.
To overwrite the default RL QoS for a given SIT click the SIT RL QoS button in the SIT
Monitoring/Control page (see “SIT Monitoring / Control” on page 274).
RL QoS can be dynamically modified: The SIT Level return link QoS configuration can be
changed without delogging the SIT:
• dynamic CRA modification is possible with RLSS 1.5 and 2.X

• dynamic VBDC Max, RBDC Max and FCA modifications are possible with RLSS 2.X
only
Upon setting new QoS values, the connection manager configures the RLSS and the SIT
through SNMP.

850176 P08
The two top sub-panes of the page, namely Current and Nominal Login are used to mod-
ify the QoS settings, while the bottom Nominal Maximum sub-pane displays information
on the maximum values for the SIT Level RL QoS (for CCP).
Figure 7.5: SIT Level RL QoS page
The parameters of the Current sub-pane represent the current state of the SIT. Changes to
these parameters are made effective by clicking the Set Current button. The changes take
effect right away, but only persist until the next time the SIT logs in to the network, at which
point it will use the parameters of the Nominal Login sub-pane. Upon clicking the Set Cur-
rent button, the NetManager:
• Configures the new parameters in the RLSS

• Configures the new parameters in the SIT

850176 P08
• Expects an SNMP trap from the RLSS acknowledging the changes. If the NetManager
does not receive the confirmation from the RLSS, the values in the Current section
are automatically reverted to the previous values and a CM event is generated.
Changes to the parameters in the Nominal Login sub-pane are done using the Update but-
ton and only take effect when the SIT next logs in to the network.
Note: The Update button only affects the parameters of the Nominal Login sub-
pane.
The parameters available in this page are described in Table 7.3. 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 update or add button (the case
being) is clicked, the NetManager highlights the differences between the default QoS pro-
file (for the SIT Group) and the overwritten profile.
Note: The QoS properties of the default profile are available through the tool tip
feature.
Field Description
Current (use Set Current button to change)

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

850176 P08
Field Description
Max Persistent Traffic (RBDC) The current maximum RBDC traffic bit rate for
kbit/s this SIT Level RL QoS.
Rate-Based Dynamic Assignments (RBDC) is
DVB-RCS specific terminology for variable
capacity on the Return Link that needs to be
requested as a rate.
It is called persistent traffic because the RBDC
capacity does not need 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.
accommodate applications that require
moderately low delays and low jitter.
Max Best-effort Traffic (VBDC) The current maximum VBDC traffic bit rate for
kbit/s the SIT Level RL QoS.
Volume-Based Dynamic Assignments (VBDC) is
requested as a quantity (volume).
It is called best-effort traffic because the VBDC
traffic is granted as a lower priority than
persistent (RBDC) and constant (CRA) traffic.
Because of its bursty nature, it is especially suited
for applications that require intermittently high
throughput but are robust to jitter and delays.
Left-Over Capacity (FCA) When checked, allows this SIT Level RL QoS to
receive left-over Return Link throughput capacity
(available to SITs without having to signal a
request for it).

850176 P08
Field Description
Nominal Login (use Update button to change)

Name The name that identifies the SIT Level RL QoS.
Constant Traffic (CRA) kbit/s The CRA traffic bit rate of the SIT Level RL QoS
that will take effet at next SIT network login.
Constant Rate Assignments (CRA) is DVB-RCS
specific terminology for constant capacity on the
Return Link that does not need to be requested.
Because of its constant nature and the fact that it
does not need to be requested, it is especially
suited for applications that require constant
throughput, low delays and low jitter.
Max Persistent Traffic (RBDC) The maximum RBDC traffic bit rate of this SIT
kbit/s Level RL QoS that will take effect at next SIT
network login.
Rate-Based Dynamic Assignments (RBDC) is
requested as a rate.
It is called persistent traffic because the RBDC
capacity does not need 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.
accommodate applications that require
moderately low delays and low jitter.

850176 P08
Field Description
Max Best-effort Traffic (VBDC) The maximum VBDC traffic bit rate of the SIT
kbit/s Level RL QoS that will take effect at next SIT
network login.
Volume-Based Dynamic Assignments (VBDC) is
requested as a quantity (volume).
It is called best-effort traffic because the VBDC
traffic is granted as a lower priority than
persistent (RBDC) and constant (CRA) traffic.
Because of its bursty nature, it is especially suited
for applications that require intermittently high
throughput but are robust to jitter and delays.
Left-Over Capacity (FCA) When checked, allows this RL QoS to start
receiving left-over Return Link throughput
capacity (available to SITs without having to
signal a request for it) at next SIT network login.
Nominal Maximum
Name The name that identifies the SIT Level RL QoS.
Constant Traffic (CRA) kbit/s The nominal maximum CRA traffic bit rate of the
SIT Level RL QoS.
Max Persistent Traffic (RBDC) The nominal maximum RBDC traffic bit rate of
kbit/s this SIT Level RL QoS.
Max Best-effort Traffic (VBDC) The nominal maximum VBDC traffic bit rate of
kbit/s the SIT Level RL QoS .
Left-Over Capacity (FCA) Reflects whether this SIT Level RL QoS is
allowed to receive left-over Return Link
throughput capacity.
To return to the SIT page (see “Adding and Updating a SIT Profile” on page 227), click the
< SIT Page button.
You can also access the SIT Monitor and Control feature by clicking < SIT/Monitoring
Control button (see “Operations Overview” on page 272).

850176 P08
Note: Certain validation rules are applied when updating an RL QoS. If you
encounter any errors, refer to “Overwritten RL SIT Level QoS” on page 362.
7.3 SIT Queues

7.3.1 Queue Types
Traffic Queues are a mechanism to classify the traffic handled by a SIT so that it is handled
in a specific way. This section deals with the configuration of Traffic Queues and their
assignment to SITs. The system allows two queues, each with a different purpose (only one
with MPEG based RL):
7.3.1.1 OAM_Queue
This queue is typically used for management and general purpose traffic.
When a SIT is added to the NetManager, an OAM queue is configured automatically, using
the following parameters (see “Adding and Updating a Traffic Queue” on page 242 for
parameter descriptions):
• Automatic generation of VCCs and PID

• Priority weight = 1
• IPSec disabled
• Channel ID = 0
Once the OAM queue is created, traffic will flow through the system only when the queue
information is consistent between the NetManager database and the SIT database. The
OAM queue is synchronized partly via the RLSS: The VCC/PID is Sent by the RLSS in the
network layer info descriptor.
Warning: It is the responsibility of the SP to make sure that the configuration of the SIT
queues matches the configuration of the SIT in the NetManager; for
example, the OAM queue must receive the VCCs through TIM.

850176 P08
7.3.1.2 Traffic_Queue
This queue is typically reserved for high priority traffic. It is also used de-facto by the man-
aged application feature – CCP for VoIP (see “Application Return Link SLA” on page
175).The traffic queue is synchronized by the NetManager via two protocols:
• SNMP: the NetManager sets the VCC/PID in the queue once the call request is
received.
• SCS: The NetManager sets the Queue ID 5 and link it to Filter pattern ID 5 in the ter-
minal.
The SCS sets the following parameters automatically once the queue is configured in the
NetManager:
• VCC Source = SNMP

• Priority weight
• IPSec enable/disable
7.3.2 Viewing Traffic Queues

To access the Traffic Queue page (see Figure 7.6 (page 240)), select Traffic Queues from
the CFG Network menu in the navigation bar. The page displays the Traffic Queues
defined so far. It can also be filtered according to SIT Profile by selecting the desired SIT
name from the SIT Profile Name drop-down list. To view the Traffic Queues in either
VCC (see “VCC Tab” on page 240) or Mesh Destinations mode, click either one of the
tabs at the top of the page.

850176 P08
Note: If navigating to the Traffic Queues page from a SIT Profile page, filtering will
automatically be locked on that SIT.
Figure 7.6: Traffic Queues page
7.3.2.1 VCC Tab

The VCC tab gives access to configuring ranges of assignable Virtual Channel Connec-
tions, see Figure 7.7.
Figure 7.7: VCC View

850176 P08
This page lists each Traffic Queue in the VCC mode along with the following parameters
(see Table 7.4):
Field Description
SIT Name The name of the SIT associated with the Traffic Queue.
VPI The Queue's Virtual Path Identifier.
VCI The Queue's Virtual Channel Identifier.
PID The Queue's Packet Identification.
Usage Type The type of traffic handled by the Queue.
Table 7.4 VCC Fields
7.3.2.2 Mesh Destinations Tab

The Mesh Destinations tab gives access to mesh destinations of traffic queues, see Figure
7.8.
Figure 7.8: Mesh Destinations View
This page lists each Traffic Queue in the Mesh Destinations mode along with the following
parameters (see Table 7.5):
Field Description
SIT Name The name of the SIT associated with the Traffic Queue.
Destinations List of SITs to which this SIT sends Mesh traffic.
Table 7.5 Mesh Destinations Fields

850176 P08
• Add/Update a Traffic Queue: you can create or modify a Traffic Queue. For more
information, see “Adding and Updating a Traffic Queue” on page 242.
• Delete a Traffic Queue: you can remove Traffic Queues from the database. For more
information, see “Deleting a Traffic Queue” on page 246.
• Set Mesh CRA: you can set the constant traffic (CRA) assigned to SITs running in
mesh mode.
7.3.2.3 Adding and Updating a Traffic Queue

To update a Traffic Queue, select it from the Grid Table in the Traffic Queue page and click
the Update button, or to add a new Traffic Queue, click the Add button. This brings up the
Traffic Queue property page as shown in Figure 7.9.
Note: For more information on adding or updating records in the database, see
Figure 7.9: Traffic Queue page

850176 P08
Modify the Traffic Queue as required and click the Update or Add button, the case being.
The Traffic Queue fields are described in Table 7.6.
Field Description
SIT Mac Address The MAC Address that identifies the SIT Profile to
which the Traffic Queue is associated.
VPI  The Virtual Path Identifier assigned to the Traffic
(auto assigned if blank) Queue. The value must be unique and within
allotted range.
Note: If you leave the field blank, a VPI will be

assigned to the Queue from the range available
to the Service Provider.
VCI  The Virtual Channel Identifier assigned to the

(auto assigned if blank) Traffic Queue.The value must be unique and within
allotted range.
Note: If you leave the field blank, a VCI will be

assigned to the Queue from the range available
to the Service Provider.
Return Link PID  The Return Link Packet Identifier assigned to the
(auto assigned if blank) Traffic Queue. The value must be unique and
within allotted range.
Note: If you leave the field blank, an RL PID will

be assigned to the Queue by the system.
Channel ID The Channel ID assigned to the Traffic Queue.

IPSec When checked shows the Traffic Queue handles
IPSec traffic.
Note: This field is reserved for use in a

future version.
Table 7.6 Traffic Queue page fields

850176 P08
Field Description
Usage Type Used by the CM for the VCC configuration of the

terminal at logon. Select a usage type for the queue
from the drop-down list.
• OAM_QUEUE
• TRAFFIC_QUEUE
• MESH_QUEUE (when selected, the "Mesh
parameters" data entry section appears; see
“Mesh” on page 244 and Figure 7.10).
Priority Weight A numerical value indicating the priority of the
Queue.
Note: This field is reserved for use in a

future version.
Table 7.6 Traffic Queue page fields

Depending on the Return Link burst format, either a VCC or a PID must be specified. It is
used by the NetManager for the Return Link traffic configuration of the terminal at logon.
The IPSec and priority are transferred to the IDU via the SCS (only with the traffic queue)
To return to the Traffic Queues page, click the < Back to Traffic Queues button. To return
to the SIT Profile page, click the < Back to SIT Profile button.
7.3.2.4 Mesh
Queues of type Mesh are similar to other queue types in that values for VPI and VCI may
be specified or left blank for auto-assignment.
It is highly recommended that the user defines a VCC range of type Mesh (select VCC from
the CFG Network->Ranges menu), ensuring that this VCC range is outside the range for-
warded by the Traffic Core of the RLSS. The range is defined on the RLSS Management
Interface (RMI). To inspect the current range in the RMI, open the Physical Resources
Workspace, navigate to the External Communications/TRF Configs and select the TRF
config defined. The range is defined by the attributes ATM VPI Min and ATM VPI Max,
as well as ATM VCI Min and ATM VCI Max.
Note: If the VPI/VCI were to be included in the same range as that of the Traffic
Core, the mesh traffic would go back to the terminal in Star mode over the
Forward Link, and the terminal would receive the traffic twice.

850176 P08
The channel ID is set to 0 for all Mesh queues. The priority weight can be used to give more
or less priority to the Mesh connection established by this queue.
Figure 7.10: Traffic Queue page (Usage Type: MESH_QUEUE)
The user shall then choose destination SIT(s) or SIT Groups for the traffic passing through
the queue under definition.
Note: Only mesh-capable SITs will appear in the choices and SIT Groups links to
the same area.

850176 P08
Setting up a bi-directional communication channel between two SITs requires solely the
definition of a destination SIT Name. Setting up a multicast transmission from one mesh-
enabled SIT to others, the user must select the potential receivers of the transmission. The
easiest way to do so is by selecting one or many SIT groups. Selecting many SIT Groups is
done by clicking SIT Groups with the control key pressed. If the user needs to restrict the
receiver candidates of the transmission to a granularity finer than the SIT Group, it can be
accomplished by selecting multiple SITs, by clicking on their name while the CTRL key is
pressed. For multicast transmission, the user needs to enter in the destination IP address a
valid multicast IP address (239.x.y.z). This information is used to populate the relevant fil-
ter in the SIT configuration. Once this is all done, the user shall press the "Add' or Update
button to make the changes effective. The NetManager uses this information to configure
the mesh tables broadcasted on the forward link by the RLSS. The SCS would also config-
ure the traffic queues and filters in the transmitting SIT once the queue is added or modi-
fied.
7.3.2.5 Deleting a Traffic Queue

To remove Traffic Queues from the database, select one or more items from the Grid Table
in the Traffic Queues page and click the Delete button.
Alternatively, you can open the property page for the Traffic Queue to delete (see “Adding
and Updating a Traffic Queue” on page 242) and click the Delete button.

850176 P08
7.4 IP Routes
IP Routes define the nominal Quality of Service for the network’s IP Routes.
In addition to the two mandatory SIT routes, OAM and Traffic, up to 15 additional traffic
routes can be defined. Each route is configured in the IPE and the routers ((automatic con-
figuration of routes is supported for SMR and SatNet IPEs and Riverstone routers).
7.4.1 Viewing IP Routes

To access the IP Routes page (see Figure 7.11), select the FL Routes item from the CFG
Network menu in the navigation bar.
The IP Routes page can be filtered by SIT by selecting it from the SIT Profile Name drop-
down list.
Note: If navigating to the IP Routes page from a SIT Profile page, filtering will
automatically be locked on that SIT.
Figure 7.11: IP Routes page

850176 P08
This page lists each IP Route along with the following parameters (see Table 7.7)
Field Description
Name The name of the IP Route.

Subnet The subnet for this IP Route.
Min. Guaranteed The guaranteed bit rate, in kilobits per second, for the IP Route.
Rate
Priority The priority applied to traffic in this route.
Max Rate The maximum bit rate, in kilobits per second, for the IP Route.
VLAN ID The VLAN ID for the route.
Usage Type The intended usage of the IP Route.
Condition Set The Condition Set name if applicable.
Name
Table 7.7 IP Routes page fields
• Add/Update an IP Routes: you can create or modify an IP Route. For more informa-
tion, see “Adding and Updating an IP Route” on page 248.
• Delete IP Routes: you can remove IP Routes from the database. For more informa-
tion, see “Deleting an IP Route” on page 251.
If you navigated to this page from the SIT page, the following options are also available:
• Navigate back to the SIT profile page by clicking the < Back to Sit Table button (see
“Viewing SITs” on page 224).
• Navigate back to the SITs page by clicking the < Back to Sit Profile button (see
“Adding and Updating a SIT Profile” on page 227).
7.4.1.1 Adding and Updating an IP Route

To update an IP Route, select it from the Grid Table in the IP Routes page and click the
Update button, or to add a new IP Route, click the Add button. This brings up the IP Route
property page as shown in Figure 7.12. Alternatively, click one of the IP Route elements or
on the Add FL Route header of the Network View in the SIT Profile page (see “Adding
and Updating a SIT Profile” on page 227).

850176 P08
Figure 7.12: IP Route page
Modify the IP Route as required and click the Update or Add button, the case being. The IP
Route fields are described in Table 7.8:
Field Description
Route Definition
Subnet The Route’s subnet.
(aaa.bbb.ccc.ddd/ee)
TOS (Hex format as 0X56) When a SatNet QoS device is configured, it is possible
to set a TOS value for a Traffic route. A FL packet
matching the IP route subnet and the specified TOS will
be shaped by the QoS device accordingly to the FL
TOS QoS profile of its SIT group.
Table 7.8 IP Route page fields

850176 P08
Field Description
Usage Type The Route’s intended usage, from:

• IP_SEC
• MULTICAST
• OAM
• TRAFFIC
Insert in Tunnel? Determines whether the Route is inserted into tunnels,
and if so, into which type.
SIT routes can be tunneled into another route of type
IPSec or VLAN (GRE); when the type is “…only”, the
original route is hidden to the IP/DVB encapsulator and
not programmed in it by the NetManager, otherwise,
both the original and tunnel route are programmed.
Note: The route association between the IPSec

tunnel and the traffic route must be manually
programmed in the IPSec server.
Unicast Association
SIT Name The SIT Profile to which the Route is associated.
SIT MAC Address The MAC Address of the SIT to which the Route is
associated.
Nominal Maximum Route QoS
Condition Set Name The Condition Set name for the Route.
Min. Guaranteed Rate for The nominal minimum traffic rate for this route.
Traffic (kbit/s)
Min. Guaranteed Priority The minimum guaranteed priority for the IP Route.
Maximum Rate for Traffic The nominal maximum traffic rate for this route.
(kbit/s)
Table 7.8 IP Route page fields
To overwrite the default FL QoS (see “Viewing Default SIT Forward Link QoS Profiles” on
page 200) for a route, the fields in the Nominal Maximum Route QoS section must be
written over.
Conversely, to remove the overwritten FL QoS profile and restore the Route to the Default
SIT Forward Link QoS profile, all entries of the Nominal Maximum Route QoS section
must be cleared.

850176 P08
When the QoS parameters are changed with respect to the Nominal values, the modified
fields will be highlighted; the default FL QoS parameters values can be viewed using the
tooltip feature. To remove the overwritten FL QoS, click the Delete Overwritten QoS but-
ton.
To return to the IP Routes page, click the < Back to IP Routes button. To return to the SIT
page, click the < Back to Sit Profile button.
7.4.1.2 Deleting an IP Route

To remove IP Routes from the database, select one or more items from the Grid Table in the
IP Routes page and click the Delete button.
Alternatively, you can open the property page for the IP Route to delete (see “Adding and
Updating an IP Route” on page 248) and click the Delete button.
7.5 SIT Control System

The SIT Control System (SCS) is a Forward Link Command Module (FLCM) integrated in
the NetManager. In order for it to be operational, it requires configuration of the encapsula-
tor, the router and the terminals to be able to send information in multicast mode, such as a
software update.
Note: Certain server configurations need to be performed in order for the SCS to be
operational.
Note: The MMT does not require updates for the SCS to function in multicast
mode.
7.5.1 Automatic Creation of Multicast Routes

The NetManager automatically creates one multicast route per existing SIT Group. The
route is named "SCS route for SIT_Group_Name". Thereafter, a multicast route is auto-
matically added when a new SIT group is added; the route is deleted when the SIT group is
deleted.

850176 P08
Note: The name of the route is also automatically updated if the name of the SIT
group is updated.
In a manner similar to the automatic configuration of user-generated multicast routes, those

multicast routes that are automatically created are also automatically configured. They do
not need to be programmed in the MMT, but are programmed in the encapsulator,. The
routes have the multicast PID defined in the SG-FL-SLA associated to the SIT Group. The
PID associated to the route is be updated if the PID of the SG-FL-SLA is updated.
7.6 VLAN
7.6.1 VLAN View
The VLAN sub-menu of the navigation bar’s CFG Network menu provides access to the
menu items related to configuring the VLAN. Clicking on the first menu item, VLAN
View, brings up the VLAN View graphical page (see Figure 7.13).
page 41.
Figure 7.13: VLAN View page

850176 P08
7.6.2 VLAN Address Space

To access the VLAN Address Spaces page (see Figure 7.14), select the Address Space
item from the VLAN sub-menu of the CFG Network menu in the navigation bar.
Figure 7.14: VLAN Address Spaces page
This page lists each VLAN Address Space along with the following parameters (see Table
7.9)
Field Description
Name The name of the VLAN Address Space.

Unique Route ID The unique identifier for the Route associated with the Address
Space.
GRE Tunnel IP The IP Address for the GRE Tunnel associated with the VLAN
Address Address Space.
Interface Name The name of the VLAN Interface associated with the Address
Space.
Table 7.9 VLAN Address Spaces page fields

850176 P08
• Add/Update a VLAN Address Space: you can create or modify a VLAN Address
Space. For more information, see “Adding and Updating a VLAN Address Space” on
page 254.
• Delete VLAN Address Space: you can remove VLAN Address Space from the data-
base. For more information, see “Deleting a VLAN Address Space” on page 255.
7.6.2.1 Adding and Updating a VLAN Address Space

To update a VLAN Address Space, select it from the Grid Table in the VLAN Address
Spaces page and click the Update button, or to add a new VLAN Address Space, click the
Add button. This brings up the VLAN Address Space property page as shown in Figure
7.15.
Figure 7.15: VLAN Address Space page

850176 P08
Modify the VLAN Address Space as required and click the Update or Add button, the case
being. The VLAN Address Space fields are described in Table 7.10:
Field Description
Service Provider The Service Provider to which the VLAN Address

Space will belong.
Name The name of the VLAN Address Space.
Interface Name The name of the VLAN Interface associated with the
VLAN Address Space.
Tunnel Properties
Unique Route ID The unique identifier associated with the Route for this
VLAN Address Space.
GRE Tunnel IP Address The Generic Routing Encapsulation Tunnel IP Address
for the VLAN Address Space.
Keep Alive Period The interval between Keep Alive’s for the VLAN
Address Space.
Keep Alive Retries The number of retries on failed Keep Alive’s for the
VLAN Address Space.
Table 7.10 VLAN Address Space page fields
To return to the VLAN Address Spaces page, click the < Back to Address Spaces button.
7.6.2.2 Deleting a VLAN Address Space

To remove a VLAN Address Space from the database, select one or more items from the
Grid Table in the VLAN Address Spaces page and click the Delete button.
Alternatively, you can open the property page for the VLAN Address Space to delete (see
“Adding and Updating a VLAN Address Space” on page 254) and click the Delete button.

850176 P08
7.7 VLAN ISP-Side Network

The VLAN ISP-Side Networks allows the configuration of the private customer networks
on the ISP-side of the Gateway. To access the VLAN ISP-Side Network page (see Figure
7.16), select the ISP-Side Network item from the VLAN sub-menu of the CFG Network
menu in the navigation bar.
Figure 7.16: ISP-Side Network Page
Table 7.13 describes each field in the ISP-Side Networks page:
Field Description
Name The name of the ISP-Side Network.

VLAN ID The VLAN ID for the ISP-Side Network.
IP Address The IP address for the ISP-Side Network.
Table 7.11 ISP-Side Network page fields

850176 P08
IP Mask The IP Mask for the ISP-Side Network.

Redundant IP The redundant IP address for the ISP-Side Network.
Address
Virtual IP Address The virtual IP address for theISP-Side Network.
Router Interface The name of the Router associated with the ISP-Side
Name Network interface.
Address Space The address space name for the ISP-Side Network.
Name
Table 7.11 ISP-Side Network page fields
• Add and Update: you can create or modify an ISP-Side Network. For more informa-
tion, see “Adding and Updating an ISP-Side Network” on page 257.
• Delete: you can select one or more ISP-Side Network from the Grid Table and delete
them from the database. For more information, see “Deleting an ISP-Side Network” on
page 259.
7.7.0.1 Adding and Updating an ISP-Side Network

To update an existing ISP-Side Network, select it from the Grid Table in the ISP-Side Net-
work page and click the Update button, or to add a new ISP-Side Network, click the Add
button. This brings up the ISP-Side Network property page as shown in Figure 7.17.

850176 P08
Figure 7.17: ISP-Side Network Update page
Modify the ISP-Side Network as required and click the Add or Update button, the case
being. The fields are described in Figure 7.12:
Field Description
Name The Name for the ISP-Side Network

Router Interface The Name for the Router Interface
Name
Address Space Name The Name for the Address Space
VLAN Properties
Note: The VLAN section of the ISP-Side Network Update page is not yet
supported by the NetManager.
VLAN Id The ID for the VLAN

Table 7.12 ISP-Side Network Update page fields

850176 P08
Field Description
IP Address The ISP-Side Network’s main management IP address.

IP Mask The IP Mask for the ISP-Side Network.
IP Address Virtual The IP Virtual Address for the ISP-Side Network.
IP Address Redundant The IP Redundant Address for the ISP-Side Network.
Table 7.12 ISP-Side Network Update page fields
To return to the ISP-Side Network page, click < Back to ISP-Side Networks button.
7.7.0.2 Deleting an ISP-Side Network

To remove an ISP-Side Network from the database, select one or more items from the Grid
Table in the ISP-Side Networks page and click the Delete button.
Alternatively, you can open the property page for the ISP-Side Network to delete (see
“Adding and Updating an ISP-Side Network” on page 257) and click the Delete button.
7.8 Ranges
Ranges are a tool that Network Operators can use to further compartmentalize Service Pro-
viders by restricting them to specified ranges of values for the following parameters:
• IP addresses (see “Viewing Service Provider IP Address Ranges” on page 259).

• PIDs (see “Viewing SP PID Ranges” on page 265).
• VCCs (see “Viewing SP VCC Ranges” on page 262).
7.8.1 Viewing Service Provider IP Address Ranges

IP address ranges allow for the partitioning of a domain of IP addresses into smaller, typi-
cally non-overlapping ranges for use by different Service Providers. Service Providers may
be restricted to use a particular range of IP Addresses when assigning them to SITs. Multi-
ple IP ranges can be assigned to a given Service Provider, and the ranges can be classified
according to usage.

850176 P08
The SP IP Address Ranges page displays the different ranges of IP Address made avail-
able to given Service Providers. To access the page, select the IP Address item from the
Ranges sub-menu in the navigation bar’s CFG Network menu.
Figure 7.18: SP IP Address Ranges page
Table 7.13 describes the parameters displayed for each IP Address Range:
Field Description
IP Address Range The numerical identifier assigned automatically by the

NetManager and used to name the IP Address range.
IP Address The first IP Address assignable for users of the IP
Address Range.
IP Mask The mask determines the valid assignable IP addresses,
limited at the lower-end by the Range Start (as
described in IP Address above).
Usage Type The intended usage type for the IP Address Range.
Table 7.13 SP IP Address Ranges page fields

850176 P08
• Add and Update: you can create or modify an IP Address Range. For more informa-
tion, see “Adding and Updating SP IP Address Range” on page 261.
• Delete: you can select one or more IP Address Ranges from the Grid Table and delete
them from the database. For more information, see “Deleting an IP Address Range” on
page 262.
7.8.1.1 Adding and Updating SP IP Address Range

To update an existing SP IP Address Range, select it from the Grid Table in the SP IP
Address Ranges page and click the Update button, or to add a new SP IP Address Range,
click the Add button. This brings up the IP Address Range property page as shown in Fig-
ure 7.19.
Figure 7.19: IP Address Range page
Modify the IP Address Range as required and click the Add or Update button, the case
being. The fields are described in Table 7.14:
Field Description
IP Address Range Id Numerical identifier assigned automatically by the

NetManager and used to name this IP Address range.
Table 7.14 IP Address Range page fields

850176 P08
Field Description
IP Address Range The first IP Address assignable for the Service Provider using
Start this range, entered as a numerical IP address:
xxx.xxx.xxx.xxx
IP Mask The mask determines the valid assignable IP addresses,
limited at the lower-end by the Range Start (as described in
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.
Table 7.14 IP Address Range page fields
To return to the SP IP Address Ranges page, click < Back to IP Address Ranges button.
7.8.1.2 Deleting an IP Address Range

To remove IP Address Ranges from the database, select one or more items from the Grid
Table in the SP IP Address Ranges page and click the Delete button.
Alternatively, you can open the property page for the IP Address Range to delete (see “Add-
ing and Updating SP IP Address Range” on page 261) and click the Delete button.
7.8.2 Viewing SP VCC Ranges

A virtual connection (VC) defines a logical networking path between two endpoints in an
ATM network and through which the 53 byte ATM cells travel. In other words, VCs 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 Connec-
tion (VCC). The VCC is formed by joining a series of Virtual Channels and uses the com-
bined 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 Providers
based on assigned ranges of VPIs and VCIs. Multiple VCC ranges can be assigned to a
given Service Provider.

850176 P08
The SP VCC Ranges page displays the VCC Ranges available for a Service Providers. To
view it, select VCC item from the Ranges sub-menu in the navigation bar’s CFG Network
menu.
Figure 7.20: SP VCC Ranges page
The following parameters are displayed for each SP VCC Range:
Field Description
VCC Range Numerical identifier assigned automatically by

NetManager and used to name the VCC Range.
VPI Start The first available VPI value for this VCC range.
VPI End The last available VPI value for this VCC range.
VCI Start The first available VCI value for this VCC range.
VCI End The last available VCI value for this VCC range.
Usage Type The intended usage type for this SP VCC Range.
Table 7.15 SP VCC Ranges page fields

850176 P08
• Add and Update a VCC Range: you can create or modify an VCC Range. For more
information, see “Adding and Updating SP VCC Ranges” on page 264
• Delete a VCC Range: you can select one or more VCC Ranges from the Grid Table
and delete them from the database. For more information, see “Deleting SP VCC
Ranges” on page 265.
7.8.2.1 Adding and Updating SP VCC Ranges

To update an existing VCC Range, select it from the Grid Table in the SP VCC Ranges
page and click the Update button, or to add a new VCC Range, click the Add button. This
brings up the VCC Range property page as shown in Figure 7.21.
Figure 7.21: VCC Range page

850176 P08
Modify the VCC Range as required and click the Add or Update button, the case being.
The fields are described in Table 7.16:
Field Description
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 The type of usage intended for the VCC Range.
Table 7.16 VCC Range page fields
To return to the SP VCC Ranges page, click the < Back to VCC Ranges button.
7.8.2.2 Deleting SP VCC Ranges

To remove VCC Ranges from the database, select one or more items from the Grid Table in
the SP VCC Ranges page and click the Delete button.
Alternatively, you can open the property page for the VCC Range to delete (see “Adding
and Updating SP VCC Ranges” on page 264) and click the Delete button.
7.8.3 Viewing SP PID Ranges

A Packet Identifiers (PID) is a numerical tag used to identify traffic intended for a given
SIT Group: its purpose is to narrow down the number of packets that SITs in a SIT Group
have to look at to find traffic directed to them.

850176 P08
The SP PID Ranges page displays the PID ranges available to a Service Provider. To view
it, select the PID item from the Ranges sub-menu in the navigation bar’s CFG Network
menu.
Figure 7.22: SP PID Ranges page
• Add, Update or View a PID Range: you can view, create or modify a PID Range. For
more information, see “Adding and Updating and Viewing SP PID Ranges” on page
267.
• Delete an SP PID Address Range: you can select one or more SP PID Ranges from
the Grid Table and delete them from the database. For more information, see “Deleting
SP PID Ranges” on page 268.
The following parameters are displayed for each SP PID Range:
Field Description
PID Range Numerical identifier assigned automatically by NetManager

and used to name the PID Range.
Table 7.17 SP PID Ranges page fields

850176 P08
PID Start The first PID assignable for users of the PID Range.
PID End The last PID assignable for users of the PID Range.
Transport Stream The Transport Stream this PID Range will be used on.
PID Range Type The type of PID Range, either RL or FL.
Usage Type The intended usage type for this PID Range.
Table 7.17 SP PID Ranges page fields
7.8.3.1 Adding and Updating and Viewing SP PID Ranges

To update or view an existing PID Range, select it from the Grid Table in the SP PID
Ranges page and click the Update or View button, or to add a new PID Range, click the
Add button. This brings up the PID Range property page as shown in Figure 7.23.
Figure 7.23: PID Range page

850176 P08
Modify the PID Range as required and click the Add or Update button, the case being.
The fields are described in Table 7.18.
Field Description
PID Start The first assignable PID for users of the PID Range.
PID End The last assignable PID for users of the PID Range.
PID Range Type Determines whether the traffic identified by this PID Range
is on the Forward or Return Link.
• Forward Link PID Range
• Return Link PID Range
Transport Stream ID The Stream ID to which this PID Range is associated.
Usage Type The intended usage type for this PID Range.
MODCOD Name (for The Modulation and Coding name for this PID Range.
DVB-S2 ACM sys-
tems)
Table 7.18 PID Range page fields
To return to the SP PID Ranges page, click the < Back to PID Ranges button.
7.8.3.2 Deleting SP PID Ranges

To remove PID Ranges from the database, select one or more items from the Grid Table in
the SP PID Ranges page and click the Delete button.
Alternatively, you can open the property page for the PID Range to delete (see “Adding and
Updating and Viewing SP PID Ranges” on page 267) and click the Delete button.

850176 P08
7.9 Mesh
7.9.1 Mesh View
The Mesh View sub-menu of the navigation bar’s CFG Network menu provides access to
the Mesh View graphical page (see Figure 7.24).
page 41.
Figure 7.24: Mesh View page

850176 P08

850176 P08
Chapter 8 Monitoring The Gateway
This chapter presents the monitoring facilities available to Operators. NetManager allows
for full monitoring of the Gateway including all the SITs it manages.
The following sections each describe a specific monitoring feature:
• “Operations Overview” on page 272 describes SIT monitoring and command facilities.
• “SIT Monitoring / Control” on page 274 describes the tools to monitor and control SIT
activity.
• “Configuration Commands and Results” on page 285 describes the Configuration
Commands and Results monitoring facilities.
• “Events and Alarms” on page 288 describes the types of alarms and events that can be
monitored.
• “SIT Group Performance Statistics” on page 294 describes Return Link and Connec-
tion statistics.
• “Statistics Graphs” on page 318 describes graphical views of Performance Statistics.
• “Queries” on page 323 explains the type of queries the user can use to search for infor-
mation on NetManager’ SMC/CM database.

850176 P08
8.1 Operations Overview

The Operations menu of the navigation bar provides access to the menu items related to
NetManager routine operation. Clicking on the first menu item, Operations View, brings
up the Network View page (see Figure 8.1) that graphically represents the different concep-
tual network elements.
page 41.
Figure 8.1: Operations View page
The other menu items available for Operations are:
• SIT Monitoring/Control describes SIT monitoring and command facilities (see “SIT
Monitoring / Control” on page 274).

850176 P08
• SIT Group Monitoring/Control describes SIT Group monitoring and command

facilities (see “SIT Group Monitoring / Control” on page 282).
• Connection Manager Events permits viewing Connection Manager Events (see
“Viewing Events” on page 289).
• Connection Manager Alarms permits viewing Connection Manager Alarms (see
“Viewing Alarms” on page 291).
• RL Statistics provides access to menu items related to Basic RL statistics, namely:
• Connections: provides basic information on Login Connection Statistics; see
“Connection Statistics” on page 295.
• RL Traffic: provides basic information on Return Link Traffic Statistics; see
“Return Link Traffic Statistics” on page 299.
• VoIP: provides basic information on VoIP Statistics; see “Managed VoIP Call Sta-
tistics” on page 303.
• RL RFCM: provides basic information on RL Counter Measure Statistics; see
“Return Link RFCM Statistics” on page 307.
• SIT SCPC: Displays a summary of the performance statistics of the SCPC SITs,
see “SIT SCPC” on page 312.
• RL Advanced Statistics provides access to menu items related to more advanced RL
statistics, namely:
• Cond. RL Connections: provides information on Conditional RL Connections
Statistics; see “Conditional Return Link Connection Statistics” on page 309.
• Adv. Login: provides advanced information on Login Statistics; see “Advanced
RL Login Statistics” on page 297.
• Adv. RL Traffic: provides advanced information on RL Traffic Statistics; see
“Return Link Advanced Traffic Statistics” on page 301.
• Adv VoIP: provides advanced information on Voice over IP Statistics; see “Man-
aged VoIP Advanced Return Link Statistics” on page 305.
• FL Statistics provides access to menu items related to Forward Link statistics, namely:
• MPEG PID Traffic: Displays MPEG traffic statistics based on PIDs, see “MPEG
PID Traffic Statistics” on page 313.
• Route MPEG Traffic: Displays MPEG traffic statistics based on Routes, see
“Route MPEG Traffic Statistics” on page 315.
• Partition IP Traffic: Displays Partition traffic statistics, see “FL Partition IP Traf-
fic Statistics” on page 317.

850176 P08
8.2 Monitoring / Control

8.2.1 SIT Monitoring / Control
NetManager enables operators to monitor and control SIT activity on the system using the
SIT Monitoring / Control page (see Figure 8.2). To access this page, select SIT Monitor-
ing/Control sub-menu item from the Operations menu in the navigation bar.
Figure 8.2: SIT Monitoring / Control page
The page’s Grid Table displays monitoring/control information about SIT. Because of the
number of different quantities to report for each SIT, the information available on the Grid
table has been split into four views, one showing Operation related information, the other
showing Configuration related information, another one showing ACM related information
and the last one showing SCPC information: switching between the views of the Grid Table
is accomplished using the four tabs at the top the Table, namely: Operations (see “Opera-

850176 P08
tions” on page 276), Configuration (see “Configuration” on page 278) and ACM (see
“ACM” on page 279) and SCPC (see “SCPC” on page 280).
The SITs displayed in the Grid Table can be filtered using the four list-boxes at the top of
the page: SITs can therefore be filtered according to the following four criteria:
• Service Provider
• SIT Group
• SIT Name
• SIT State (e.g. Traffic Ready)
The Grid Table 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 Grid Table, allowing nav-
igation between pages of SITs.
For convenience, an overview of the principal status information on SITs is presented,

above the Grid Table, to its right in a box named Stats. It shows a summary of number of
SITs in given states, as explained in Table 8.1.
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.
OAM Rdy The total number of SITs that are in OAM Ready state
(independent of the SIT State filtering selected).
Trf Rdy The total number of SITs that are in Traffic Ready state
(independent of the SIT State filtering selected).
Disabled The number of SITs currently disabled.
Unknown The number of SITs in an unknown state.
Sleep The number of SITs in the sleep state.
Table 8.1 SIT Monitoring / Control summary fields
Also, the NetManager presents an overview of the principal status information on filtered
SITs in a box named Filtered Stats. The filtered SITs are the subset from the whole SIT
population once the filters have been applied.
Various commands can be issued to SITs, using the buttons at the bottom of the page (see
“Commands” on page 283).

850176 P08
The SIT Events button navigates to the Connection Manager Events page (see “Viewing
Events” on page 289), while the SIT Alarms button navigates to the Connection Manager
Alarms page (see “Viewing Alarms” on page 291); both functions filter the displayed result
according to the selected SIT.
The SIT RL QoS button navigates to the SIT’s overwritten RL QoS properties page (see
“Overwriting RL QoS” on page 232).
The SIT Monitoring / Control page will automatically refresh at the given interval, and
can also be refreshed manually using the Refresh button (see “Refresh Bar” on page 31).
8.2.1.1 Operations
The Operations view (see Figure 8.3) of the Grid Table in the SIT Monitoring / Control
page is accessible by clicking on the Operations tab at the top of the Grid Table. 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 8.2 on page 277) for easier identifica-
tion.
Figure 8.3: SIT Monitoring / Control - Grid Table Operations view

850176 P08
The Operations view of the Grid Table displays the following parameters for each SIT:
Field Description
MAC Address The MAC address of the SIT, which is the primary identifier
for a Terminal.
SIT Name The name that identifies the SIT.
State 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 (black): 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 terminal did not complete suc-
cessfully.
• Traffic Ready (forest green): The SIT has requested to
transmit traffic and maintains its Return Link synchroniza-
tion; 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).
• Mesh Ready (forest green): SITs in Mesh mode transition
to this state (as opposed to Traffic Ready) when they are
synchronized with the RLSS, the reason being that the
Connection Manager (CM) cannot receive traffic from the
SITs in mesh mode: those SITs could therefore never tran-
sition to Traffic Ready.
• Sleep: The SIT is not currently synchronized into the net-
work but the last ping attempted to that SIT OAM IP
address succeeded.
CRA (kbit/s) The CRA traffic bit rate for the monitored SIT, based on the
SIT’s QoS.
Table 8.2 SIT Monitoring / Control (Operations) page fields

850176 P08
RBDC max (kbit/s) The RBDC traffic bit rate for the monitored SIT, based on
the SIT’s QoS.
VBDC max (kbit/s) The VBDC traffic bit rate for the monitored SIT, based on
the SIT’s QoS.
RL Es/No (db) The Return Link Signal to Noise ratio, as defined by:
Energy per symbol / Noise power spectral density.
Protection Level The current Protection level for the SIT (clear sky, rain fade
1-3).
Ping Time (ms) The resulting time from the last ping command sent to the
SIT.
Table 8.2 SIT Monitoring / Control (Operations) page fields
Note: The Entry Request and OAM ready states are transient states. A SIT
remaining in one of these states for a prolonged period of time may be
experiencing problems: 

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. 

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).
8.2.1.2 Configuration
The Configuration view (see Figure 8.4) of the Grid Table in the SIT Monitoring / Control
page is accessible by clicking on the Configuration tab at the top of the Grid Table. It pres-
ents information relevant to SIT configuration.
Figure 8.4: SIT Monitoring / Control - Grid Table Configuration view

850176 P08
In the Configuration view of the Grid Table, the following parameters are displayed for
each SIT:
Field Description
for a Terminal.
Ethernet Subnet The subnet for the SIT.
PEP Enabled Reflects whether or not the SIT is PEP enabled.
Mesh Receive Enabled Reflects whether the SIT is enabled for Mesh operation.
Software Version Reflect the software version running on the SIT.
Reboot Required Reflects whether the SIT is in a state where it requires a
reboot (after a software download).
SIT Group The SIT Group to which the SIT belongs.
Table 8.3 SIT Monitoring / Control (Configuration) page fields
8.2.1.3 ACM
The ACM view (see Figure 8.5) of the Grid Table in the SIT Monitoring / Control page is
accessible by clicking on the ACM tab at the top of the Grid Table. It presents information
relevant to the SIT ACM configuration.
Figure 8.5: SIT Monitoring / Control - ACM Table Configuration view

850176 P08
In the ACM view of the Grid Table, the following parameters are displayed for each SIT:
Field Description
for a Terminal.
FL PID Forward Link PID used by the SIT.
MODCOD Used MODCOD used by the SIT.
Efficiency Factor Bandwidth efficiency factor for this SIT.
Table 8.4 SIT Monitoring / Control (ACM) page fields
8.2.1.4 SCPC
The SCPC view (see Figure 8.6) of the Grid Table in the SIT Monitoring / Control page is
accessible by clicking on the SCPC tab at the top of the Grid Table. It presents information
relevant to the SIT SCPC configuration.
Figure 8.6: SIT Monitoring / Control - SCPC Table Configuration view

850176 P08
In the SCPC view of the Grid Table, the following parameters are displayed for each SIT:
Field Description
for a Terminal.
SCPC Enabled Indicates if the SIT RL type is SCPC.
Frequency (Hz) Frequency of the RL SCPC carrier
Frequency Offset (Hz) Frequency of the RL SCPC carrier as measured by the SCPC
receiver.
FL Es/No (dB) Es/No of the FL as measured by the SIT.
RL Power Level Power level of the RL SCPC carrier as measured by the
(dBm) SCPC receiver.
RL BER Bit Error Rate of the RL SCPC carrier as measured by the
SCPC receiver.
Table 8.5 SIT Monitoring / Control (SCPC) page fields

850176 P08
8.2.2 SIT Group Monitoring / Control

NetManager enables operators to monitor and control SIT Group activity on the system
using the SIT Group Monitoring / Control page. To access this page, select SIT Group
Monitoring/Control sub-menu item from the Operations menu in the navigation bar. The
Grid Table of the SIT Group Monitoring / Control page (see Figure 8.7) shows the list of
monitored SIT groups.
Figure 8.7: SIT Group Monitoring / Control page
The following parameters are displayed for each SIT Group:
Field Description
SIT Group The SIT Group being monitored.

Nbr. Configured SITs The number of SITs configured in the SIT Group.
Table 8.6 SIT Group Monitoring / Control page fields

850176 P08
Nbr. SITs Logged in The number of SITs of the SIT Group that are currently
logged in.
Multicast group Is the SIT Group multicast enabled, i.e. can SCS commands
be sent to the Group as a whole.
SIT Software Version The SIT software version running on SITs in the Group.
Geo Redundancy The current Geographic Redundancy state of the SIT Group.
State
Table 8.6 SIT Group Monitoring / Control page fields
Various commands can be issued to SIT Groups that are multicast enabled, through the SCS
buttons at the bottom of the page (see “SIT Control System (SCS)” on page 284).
The SIT Group Monitoring / Control page will automatically refresh at the given interval,
and can also be refreshed manually using the Refresh button (see “Refresh Bar” on page
31).
8.2.3 Commands
Both the SIT Monitoring / Control and SIT Group Monitoring / Control pages allow
operators to control the SITs through a set of commands. There are two types of mecha-
nisms available to send commands to SITs, mainly distinguished by the data transmission
method: Acknowledged (see “Acknowledged” on page 283) and through SCS (see “SIT
Control System (SCS)” on page 284).
8.2.3.1 Acknowledged
This method of sending commands to SITs uses TCP; the bidirectional aspect of the proto-
col allows each packet to be acknowledged; more to the point, it enables the system to know
whether or not a command was correctly transmitted. This is the most reliable way of send-
ing commands to SITs (compared to the SCS method). The main restrictions of the
Acknowledged method are that commands can only be issued to a single SIT at a time, and
that the overhead of the TCP protocol makes data transfers slower.
Individual SITs can be issued a command by selecting the checkbox beside its MAC
Address and clicking the appropriate button for the command:
• Wake Up: sends a wake up MAC command to the selected SIT; this does not com-
mand the SIT to log in.
• Log off: sends a log off command to the selected SIT.
• SIT Reboot: sends an SNMP reboot command to the selected SIT.
• TX Enable: enables the SIT’s transmitter; prompts the RLSS to send a Tx Enable
MAC command to bring the SIT out of the Transmit Disable state.

850176 P08
• TX Disable: forces the shutdown of the SIT’s transmitter; prompts the RLSS to send a
Tx Disable MAC command to bring the SIT into Transmit Disable state.
• Details: displays details about the selected SIT (see “SIT Profiles” on page 224).
• Allow: permits the selected SIT to logon to the network, presumably after a Deny com-
mand 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.
• SIT RL QoS: Navigates to the SIT Level RL QoS page (see “SIT RL QoS” on page
232).
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. If the state is inconsistent with the expected result, consult
“Troubleshooting” on page 359.
Note: Commands are sent to a single SIT, even if you select multiple SITs.
8.2.3.2 SIT Control System (SCS)

The SCS uses the UDP protocol to send commands to SITs. The commands are sent via uni-
cast IP traffic to the OAM address of the IDU.
The unidirectional nature of UDP has advantages over the TCP method. First, it means that
SITs only need to acquire the Forward Link to receive commands from NetManager: they
do not have to be synchronized with the Gateway, since communication only happens from
the Gateway to the SIT (i.e. on the Forward Link) and not in the opposite direction (Return
Link). UDP file transfer over the Satellite connection is also faster than TCP methods, due
to the decreased overhead of not having to acknowledge packets. Finally, UDP’s multicast
capability allows SCS to send commands not only to single SITs, but also to SIT Groups, as
long as the SIT Group is multicast enabled.
The SCS method of sending commands also has a two important constraints over its TCP
counterpart: there is no guarantee that packets have be received by the SITs, and no feed-
back can be provided on the status or result of the transmission of commands.
Commands can be sent to SITs by selecting the SIT (in the SIT Monitoring / Control) or
SIT Group (in the SIT Group Monitoring / Control) and clicking the appropriate button
for the command:

850176 P08
• Acquire Return Link: commands the SIT(s) to acquire the Return Link.
• Acquire Forward Link: forces the re-acquisition of the Forward Link (configuration
“A” on the IDU Satnetwork web page).
• Acquire Second Forward Link: forces the re-acquisition of the second Forward Link
(configuration “B” on the IDU Satnetwork web page).
• Synchronize SCS: Sends to the SIT, via their OAM IP address, the configuration nec-
essary to receive multicast commands.
• Reboot: restarts the SIT(s).
• Enable TX: enables Transmission on the SIT(s).
• Disable TX: disables Transmission on the SIT(s).
• Logoff: forces the SIT(s) to logoff from the network.
• Software Update: permits upgrading the SIT(s) software (software specified for the
SIT Group).
• Reboot from Alternate Image: reboots the SIT(s) and instructs them to restart using
their alternate software image (software B).
• SIT OAM Ping: Pings the SIT(s) (once, and only in Traffic Ready state) using SCS;
reports the value in the Ping Time column of the table, Operations tab.
8.3 Configuration Commands and Results

The Configuration Commands & Results page enables operators to monitor the result of
certain equipment configuration commands, such as the configuration of an IP/DVB Encap-
sulator with updated SP FL SLA information (see “Updating Encapsulator Routes” on page
149).

850176 P08
To access the functionality, select the Command/Result item from the CFG Mgmt menu
in the navigation bar. This brings up the Configuration Commands & Results page (see
Figure 8.8), listing all the commands that have been issued so far.
Figure 8.8: Configuration Commands and Results page

850176 P08
The following table explains the parameters displayed for each command listed
Field Description
Equipment The name of the equipment to which the command

was issued.
Resource Id The name or identifier for the resource that prompted
the equipment configuration command.
Command Type The type of operation that was performed on the
equipment regarding the resource.
Status The status of the command:
• IDLE: The command waits to be executed
• PROCESSING: The command is been executed
• SUCCESSFUL: The command has successfully
completed
• FAILED: The command could not have been exe-
cuted or the gateway device reported an error
Result The result returned by the command after completion.
Note: This field will be empty if the command has

not yet completed.
Start Time The timestamp marking the beginning of processing

for this command.
User The user that initiated the command.
Table 8.7 Configuration Commands and Results page fields
You can deleted selected command results by clicking the Remove button.
The Configuration Commands & Result page will automatically refresh at the given
interval, and can also be refreshed manually using the Refresh button (see “Refresh Bar”
on page 31).

850176 P08
8.4 IP Sec Report

To access the functionality, select the IP Sec Report item from the CFG Mgmt menu in the
navigation bar. This brings up the IP Sec Report page (see Figure 8.9).
Figure 8.9: IP Sec Report page
The report presents the following information
Field Description
Peer The Peer’s IP Address.

Remote The Remote’s IP Address
Subnet The subnet mask.
Table 8.8 IPSec Report page columns
8.5 Events and Alarms

There are two basic sources of alarms and events:
• Internally generated by the NetManager.

• Externally generated, such as those coming from SITs.
The NetManager server is also configured to detect certain system events. For instance, if it
detects a RAID failure (in either of the two disks), it will autonomously notify the proper
person (through an e-mail address configured at NetManager installation time) of this fact
so that corrective action can be taken, see “Checking RAID Status” on page 349.

850176 P08
8.5.1 Viewing Events

The NetManager system events are reported in the Connection Manager Events page (see
Figure 8.10). To access it, select Connection Manager Events from the Operations menu
in the navigation bar. The events display can be filtered by Service Provider and SIT Pro-
file Name using the drop-down lists.
Figure 8.10: Connection Manager Events page

850176 P08
The following parameters are displayed for each event in the grid:
Field Description
SIT Group Name The SIT Group to which the SIT related to this event
belongs.
SIT Name The name of the SIT related to this event.
SIT MAC Address The 6 byte value uniquely identifying the SIT related
to this event, in the format: xx:xx:xx:xx:xx:xx
Time The time of occurrence of the event.
Event Type The specific type of the event, such as: SIT Login
Request Accepted.
Description The description of the event.
Table 8.9 Connection Manager Events page fields
If not all events can be displayed in a single page, then a Previous and/or Next button will
be displayed to navigate between page fulls of events.
The Connection Manager Events page will automatically refresh at the given interval, and
Connection Manager Events can be deleted from the system using the Remove button to
prevent the database from growing too large: see “Deleting Events and Alarms” on page
293.

850176 P08
8.5.2 Viewing Alarms

The system alarms are reported in the Connection Manager Alarms page. To access it,
select Connection Manager Alarms from the Operations menu in the navigation bar. The
page displays all active alarms as shown in Figure 8.11.
Figure 8.11: Connection Manager Alarms page

850176 P08
The following parameters are displayed for each alarm in the grid:
Field Description
Severity This field describes the severity of the alarm.

• Informational: No direct action is required.
• Warning: No immediate action is required e.g.
a software issue.
• Minor: Requires an action in the short-term to
re-establish proper operation.
• Major: Requires immediate action to re-estab-
lish proper operation.
• Critical: System in jeopardy.
Note: In this implementation, CM alarms do not

generate traps to send to the CMS.
The CM detects SIT-related alarms and transmits

them to the SMS. For a list of the severity alarms, see
the severity messages listed below this table.
SIT Group Name The SIT Group to which the SIT belongs.
SIT MAC Address The MAC address is a 6 byte value uniquely
identifying the SIT; its format is: xx:xx:xx:xx:xx:xx
RLSS Id The RLSS for which the alarm has been detected, the
case being.
Time The time of occurrence of the alarm.
Description The description of the alarm.
Extra Info This field provides additional details on the alarm.
Table 8.10 Connection Manager Alarms page fields
If not all alarms can be displayed in a single page, then a Previous and/or Next button will
be displayed to navigate between page fulls of alarms.
The severity of Connection Manager and SIT events can be determined using the informa-
tive messages in the Severity column of the Connection Manager Alarms page:
• SIT login denied because of invalid MAC address (Minor).

• SIT login denied because in TX disabled mode (Minor).
• SIT login denied because in Denied Service mode (Minor).

850176 P08
• CM cannot write to the database (Major).

• CM cannot read from the database (Major).
• SIT login refused because of lack of Return Link resources (Warning).
• SIT accepted but never synchronized (i.e., receiving a disconnect trap first or after no
synchronization after 3 TBC multiframes) (Warning).
• SYNC event received from SIT after logoff (Warning).
• Entry request received after SIT already logged on (Warning).
• Too many consecutive SIT logins tentative (Minor).
• Missing configuration data (Minor).
• SIT failed to acknowledge MIB configuration (Minor).
• CM Process Started (Clear).
• CM Process Stopped (Critical).
• CM lost all communications with RLSS ID xxx (Major).
• CM regained communication with RLSS ID xxx (Clear).
• CM witnessed an RLSS ID xxx primeship change (Warning).
• CM automatically restarted after an abnormal termination (Major).
Alarm notifications can be deleted from the system using the Remove button (see “Delet-
ing Events and Alarms” on page 293).
8.5.3 Deleting Events and Alarms

NetManager allows for the deletion of events and alarms from the system. This is useful
when an alarm has been dealt with or an event acknowledged, and prevents cluttering the
system with obsolete information.
Note: Only Network Operator Administrators can delete events and alarms.
To remove alarms or events from the database, select the items to delete by clicking their
individual checkbox (in the first column of the list) and click the Remove button.

850176 P08
NetManager also provides a filtered deletion mechanism, allowing for the batch cleanup of
old alarms and events. In the Delete Alarms older than (hrs) box, enter the maximum age
for alarms you want to keep (in hours), and click the Remove button: all alarms/events that
are older (based on the Time column) than the threshold specified will be deleted from the
system.
Warning: The Alarm and Event deletion operation cannot be undone.
8.6 SIT Group Performance Statistics

As part of its monitoring facilities, NetManager provides performance data on all aspects of
the Gateway, such as Connections and RLSS.
NetManager presents performance data in two types of pages:
• Basic tables, showing a simplified summary of the performance data.

• Advanced tables, showing additional details (e.g. DVB-RCS related performance
data).
The data in each statistics page can also be viewed in the form of a graphic using the Graph
button (see “Statistics Graphs” on page 318).

850176 P08
8.6.1 Connection Statistics

The Login Connection Statistics page (see Figure 8.12) is the Basic Table related to con-
nection performance data: it shows a summary of the information on SIT Group connec-
tions to the network. To access this page, select the Connections item from the RL
Statistics sub-menu in the navigation bar’s Operations menu.
Figure 8.12: Connection Statistics page
The following information is provided for each entry:
Field Description
SIT Group Name The SIT Group for which the data was collected.
Nbr. of Configured SITs The number of SITs configured in the database
that belong to this SIT group.
Nbr. of Logged-in SITs (%) The percentage of SITs that are currently logged in
versus the number of registered SITs.
Table 8.11 Connection Statistics page fields

850176 P08
Field Description
Nbr. of Login Requests The number of login requests received for the SIT
Group within the data acquisition period.
Nbr. of Denied Logins The number of denied login requests received for
the SIT Group within the data acquisition period.
No. of Busy Replies The number of busy replies for the SIT Group.
FL Connection Capacity (kbit/s) The maximum guaranteed FL SLA multiplied by
the FL overbooking factor.
FL Current Percentage (%) The percentage of the sum of the FL maximum
traffic of SITs that are logged in versus the
Maximum Capacity for connection on the Forward
Link.
FL Rejection Ratio (%) The percentage of the connections that were
refused because of the constraint of Forward Link
traffic versus the total number of connection
requests within the SIT group (averaged over the
data acquisition period).
RL Connection Capacity (kbit/ The maximum CRA traffic plus the Maximum
s) RBDC, multiplied by the RBDC overbooking
factor.
RL Current Percentage (%) The percentage of the sum of the RL maximum
traffic of SITs (CRA and RBDC) that are logged
in versus the Maximum Capacity for Subscription
on the Return Link.
RL Rejection Ratio (%) The percentage of the connections that were
refused because of the constraint of Return Link
traffic versus the total number of connection
requests within the SIT group (averaged over the
data acquisition period).
Table 8.11 Connection Statistics page fields
The Login Connection Statistics page will automatically refresh at the given interval, and
The Graph button lets you navigate to the Login Connection Statistics Graph page which
enables you to setup graphical representations of the Connection Statistics parameters. For
a detailed description of the various NetManager Graph pages, refer to “Statistics Graphs”
on page 318.

850176 P08
8.6.2 Advanced RL Login Statistics

The Advanced RL Login Statistics page (see Figure 8.13) complements the Connection
Statistics Basic Table (see “Connection Statistics” on page 295) with more in-depth infor-
mation on logins to the network by including data on certain DVB-RCS parameters.
To access this page, select the Adv. Login item from the RL Advanced Statistics sub-
menu in the navigation bar’s Operations menu.
Figure 8.13: Advanced RL Login Statistics page
The following information is available for each item:
Field Description
RL SLA Name The name that identifies the Service Provider Return
Link Service Level Agreement.
SIT Group Name The name that identifies the SIT Group.
CRA Connection Capac- The CRA connection capacity.
ity (kbit/s)
Table 8.12 Advanced RL Login Statistics page fields

850176 P08
Field Description
Current CRA Percentage The percentage of the CRA Max summed over all logged
on SITs within the SIT Group versus the Maximum
Constant Traffic (CRA) for subscription.
CRA-Based Login Rejec- The percentage of login requests that were denied
tion Ratio (%) because of the constraint on the Maximum Constant
Traffic for connection versus the total number of
connection requests within the SIT group (averaged over
the data acquisition period).
CRA Requests Rejection The percentage of the requests for additional CRA (from
Ratio (%) synchronized SITs in the SIT Group) that were refused
because of the constraint on the Maximum Constant
Traffic.
RBDC Connection Capac- The RBDC traffic connection capacity equal to the
ity (kbit/s) RBDC of the segment multiplied by the RBDC
overbooking factor.
Current RBDC Percent- The percentage of the RBDC Max summed over all
age logged on SITs versus the maximum persistent traffic
(RBDC) for connection.
RBDC-Based Login The percentage of the connections that were refused
Rejection Ratio (%) because of the constraint on the max persistent traffic for
connection versus the total number of connection
requests within the SIT group (averaged over the data
acquisition period).
Table 8.12 Advanced RL Login Statistics page fields
The page will automatically refresh at the given interval, and can also be refreshed manu-
ally using the Refresh button (see “Refresh Bar” on page 31).
The Graph button lets you navigate to the Advanced RL Login Statistics Graph page
which enables you to setup graphical representations of the Advanced Connection Statistics
parameters. For a detailed description of the various NetManager Graph pages, refer to
“Statistics Graphs” on page 318.

850176 P08
8.6.3 Return Link Traffic Statistics

The RL Traffic Statistics page (see Figure 8.12) is the Basic Table related to Return Link
traffic performance data: it shows a summary of the information for SIT Group traffic on
the Network.
To access this page, select the RL Traffic item from the RL Statistics sub-menu in the nav-
igation bar’s Operations menu.
Figure 8.14: RL Traffic Statistics page
The following statistics and informative fields are displayed:
Field Description
SP RL SLA Name The name that identifies the SP Return Link SLA.
Low Level RL SLA Name The LL RL SLA used in this entry.
Protection Mode The protection Mode associated to the LL-RL-SLA,
such as Clear Sky, Rain 1, Rain 2, Rain 3, Rain 4.
Table 8.13 RL Traffic Statistics page fields

850176 P08
Field Description
SLA Min The guaranteed portion of the Return Link SLA.

SLA Max The maximum Forward Link traffic allowed by the
SLA.
Segment Id The Segment ID to which the low-level SLA is linked.
Current Allocated Traffic The percentage of the average allocated Return Link
(%) traffic versus the maximum Return Link traffic
allowed by the SLA. The average allocated Return
Link traffic is given by the sum of the average CRA,
the average allocated RBDC slots and the average
VBDC slots allocated to the segment linked to the
SLA.
Table 8.13 RL Traffic Statistics page fields
The RL Traffic Statistics page will automatically refresh at the given interval, and can also
be refreshed manually using the Refresh button (see “Refresh Bar” on page 31).
The Graph button lets you navigate to the RL Traffic Statistics Graph page which
enables you to setup graphical representations of the Traffic Statistics parameters. For a
detailed description of the various NetManager Graph pages, refer to “Statistics Graphs”
on page 318.

850176 P08
8.6.4 Return Link Advanced Traffic Statistics

The RL Advanced Traffic Statistics page (see Figure 8.15) complements the RL Traffic
Statistics Basic Table (see “Return Link Traffic Statistics” on page 299) with more in-depth
information on SIT Group traffic on the network by including data on certain DVB-RCS
parameters.
To access this page, select the Adv. RL Traffic item from the RL Advanced Statistics sub-
menu in the Navigation Bar’s Operations menu.
Figure 8.15: RL Advanced Traffic Statistics page

850176 P08
The following statistics and informational fields are displayed:
Field Description
Low Level RL SLA Name The name that identifies the Low Level Return Link
SLA.
Shared Segment This field indicates whether or not the segment for
which the statistics are summarized is shared by many
low-level RL SLA.
Worst Case Constant Traffic The maximum CRA parameter summed over all SITs
(kbit/s) logged in to the segment linked to the SLA.
Current Constant Traffic The sum of the CRA traffic currently allocated in the
(kbit/s) segment linked to the SLA.
Maximum Persistent Traf- The maximum RBDC traffic allowed in the segment
fic (kbit/s) linked to the SLA.
Maximum Requestable Per- The maximum RBDC traffic summed over all SITs
sistent Traffic (kbit/s) logged in to the segment linked to the SLA.
Average Requested Persis- The sum of the RBDC traffic currently requested in the
tent Traffic (kbit/s) segment linked to the SLA (as reported by the RLSS).
Average Allocated Persistent The sum of the RBDC traffic currently allocated in the
Traffic (kbit/s) segment linked to the SLA (as reported by the RLSS).
Peak Allocated Persistent The peak RBDC traffic currently allocated in the
Traffic (kbit/s) segment linked to the SLA (as reported by the RLSS).
Max Requestable Best- The maximum VBDC traffic summed over all SITs
Effort Traffic (kbit/s) logged in to the segment linked to the SLA.
Average Allocated Best- The sum of the VBDC traffic currently allocated in the
Effort Traffic (kbit/s) segment linked to the SLA (as reported by the RLSS).
Table 8.14 RL Advanced Traffic Statistics page fields
Note: If an SLA is linked to many segments, such as in load balancing, the

statistics of all segments will be summed and this sum will be shown in the
table.

If a segment is linked to many SLAs, then the statistics of the segment will be
reported in all relevant SLAs.
The RL Advanced Traffic Statistics page will automatically refresh at the given interval,
31).

850176 P08
The Graph button lets you navigate to the RL Advanced Traffic Statistics Graph page
which enables you to setup graphical representations of the Advanced Traffic Statistics
8.6.5 Managed VoIP Call Statistics

The Managed VoIP Call Statistics page (see Figure 8.16) is the Basic Table related to
Voice over IP performance data: it shows a summary of the information for SIT Group traf-
fic on the Network for the VoIP application.
To access this page, select the VoIP item from the RL Statistics sub-menu in the navigation
bar’s Operations menu.
Figure 8.16: Managed VoIP Call Statistics page

850176 P08
The following statistics and informative fields are displayed:
Field Description
Application RL SLA Name The Application RL SLA Name (see “Application
Return Link SLA” on page 175)
Current Nbr. Of G.723 con- The current number of active VoIP calls (managed by
nections the CM using CCP) using the G.723 protocol (after
commit).
commit).
commit).
Call Requests Ave. Rate The rate of call request (all codecs) averaged over the
(calls/min) configurable period of time.
Call Set-up Ave. Rate (calls/ The rate of call set-up (all codecs) averaged over a
min) configurable period of time.
Call Rejection Ratio (%) The ratio of call set-up refused by the connection
manager.
Table 8.15 Managed VoIP Call Statistics page fields
The Managed VoIP Call Statistics page will automatically refresh at the given interval,
31).
The Graph button lets you navigate to the Managed VoIP Call Statistics Graph page
which enables you to setup graphical representations of the VoIP Call Statistics parameters.
For a detailed description of the various NetManager Graph pages, refer to “Statistics
Graphs” on page 318.

850176 P08
8.6.6 Managed VoIP Advanced Return Link Statistics

The Managed VoIP Advanced RL Statistics page (see Figure 8.17) complements the
Managed VoIP Call Statistics Basic Table (see “Managed VoIP Call Statistics” on page 303)
with more in-depth information the VoIP application.
To access this page, select the Adv. VoIP item from the RL Advanced Statistics sub-menu
in the Navigation Bar’s Operations menu.
Figure 8.17: Managed VoIP Advanced RL Statistics page

850176 P08
Field Description
SIT Group Name The SIT Group Label.

Application RL SLA Name The Label identifying the Application RL SLA used
by the SIT Group for VoIP calls (see “Application
Return Link SLA” on page 175).
RL Aggregate Guar. Capac- The Aggregate return link capacity guaranteed for
ity (kbit/s) VoIP applications within the RL SLA.
RL Aggregate Max. Capac- The Maximum aggregate return link capacity
ity (kbit/s) accessible to VoIP applications within the RL SLA.
Current (% of Guar.) The current return link capacity used for managed
VoIP calls, as a percentage of the capacity guaranteed
for the VoIP application.
Nbr. of Call Requests The Number of call requests that were received during
a configurable period (used to calculate the rejection
ratios defined below).
Rejection Ratio due to RL The ratio of call set-ups that were rejected because the
VoIP cap. (%) return link capacity accessible to VoIP has been
exceeded. The check that should contribute to this
rejection ratio is #5 (Application Aggregate
Bandwidth Validation) and # 6 (Application Max CRA
Validation).
SIT cap. (%) return link capacity accessible to a SIT has been
exceeded. The check that should contribute to this
rejection ratio is #4 (SIT QoS Validation).
SLA cap. (%) return link service level agreement accessible to VoIP
has been exceeded. The checks that should contribute
to this rejection ratio are #1 (Segment Size Validation)
and #2 (Segment CRA Validation).
Table 8.16 Managed VoIP Advanced RL Statistics page fields
The Managed VoIP Advanced RL Statistics page will automatically refresh at the given
on page 31).

850176 P08
The Graph button lets you navigate to the Managed VoIP Advanced RL Statistics Graph
page which enables you to setup graphical representations of the Advanced VoIP Statistics
8.6.7 Return Link RFCM Statistics

The Return Link RFCM Statistics page (see Figure 8.18) is the Basic Table related to
Rain Fade Counter Measure performance data, showing a summary of the information for
SIT Group traffic on the Network.
To access this page, select the RL RFCM item from the RL Statistics sub-menu in the
Navigation Bar’s Operations menu.
Figure 8.18: Return Link RFCM Statistics page

850176 P08
Field Description
SIT Group Name The SIT Group identifier.

Nbr. of Configured SITs The number of SITs that belong to this SIT group.
Protection Mode This field indicates the protection mode for the SIT
Group. Choices are:
• Clear Sky,
• Rain 1 to 3.
The table shows one row per available protection
mode for the SIT Group.
Nbr. of SITs in Protection The number of SITs currently using the protection
Mode mode listed in the column to the left.
Logged-in SITs in Protec- The percentage of logged-in SITs currently using the
tion Mode (%) protection mode.
Nbr. of Protection Increase The number of protection increase requests to the
Requests protection mode listed on the third column from left
within the configurable period of time.
Protection Mode Increase The percentage of denied protection increase requests
Rejection Ratio (%) into the protection mode listed on the third column
from left within a configurable period of time. The
rejection ratio considers only the request rejection
replies sent to the RLSS. It doesn't cover the rejection
to a specific LL-RL-SLA, when the request is accepted
to a LL-RL-SLA with the same protection mode.
Nbr. of Protection Decrease The number of protection decrease requests to the
Requests mode listed on the third column from left within a
configurable period of time.
Protection Mode Decrease The percentage of denied protection Decrease requests
Rejection Ratio (%) into the protection mode within a configurable period
of time. The rejection ratio considers only the request
rejection replies sent to the RLSS. It doesn't cover the
rejection to a specific LL-RL-SLA, when the request is
accepted to a LL-RL-SLA with the same protection
mode.
Table 8.17 Return Link RFCM Statistics page fields

850176 P08
The Return Link RFCM Statistics page will automatically refresh at the given interval,
31).
The Graph button lets you navigate to the Return Link RFCM Statistics Graph page
which enables you to setup graphical representations of the Return Link RFCM Statistics
8.6.8 Conditional Return Link Connection Statistics

This advanced statistics page presents information on connection requests for given Low
Level RL SLA. This table complements the basic RFCM statistics page (see “Return Link
RFCM Statistics” on page 307). To access this page, select the Cond. RL Connections
item from the RL Advanced Statistics sub-menu in the Navigation Bar’s Operations
menu.
Figure 8.19: Conditional RL Connection Statistics page

850176 P08
Table 8.18 explains the statistics and informational fields displayed:
Field Description
Low Level RL SLA Name The name of the LL RL SLA.
Nbr. of SITs in Low Level The number of SITs from the SIT Group using the LL
RL SLA RL SLA.
Nbr. of Connection Requests The number of connection requests in the LL RL SLA
(from protection mode change) in the configurable
period of time.
Available CRA for Connec- The percentage of the CRA Max summed over all
tions (%) logged on SITs within the SIT Group versus the maxi-
mum CRA allowed in the LL RL SLA multiplied by
the CRA overbooking factor.
CRA-based Connection The percentage of protection mode change requests
Rejection Ratio (%) that were refused because of the constraint on the
available Const. Traffic for connection (the maximum
CRA allowed in the LL RL SLA multiplied by the
CRA overbooking factor), averaged over a config-
urable period of time.
Table 8.18 Conditional Return Link Connection Statistics page fields

850176 P08
Field Description
Available CRA Capacity The percentage of the CRA allocated in the LL RL

(%) SLA versus the maximum CRA allowed in the LL RL
SLA.
CRA-Based Capacity Rejec- The percentage of protection mode change requests
tion Ratio (%) that were refused because of the CRA capacity con-
straints on the SLA (LL RL SLA CRA Max, Applica-
tion CRA).
Available RBDC Capacity The percentage of the RBDC Max summed over all
(%) logged on SITs versus the Max persistent. traffic
(RBDC) for connection (maximum RBDC of the seg-
ment multiplied by the RBDC overbooking factor).
RBDC-Based Rejection The percentage of the connections that were refused
Ratio (%) because of the constraint on the max persistent traffic
for connection versus the total number of protection
mode change requests to the LL RL SLA, averaged
over a configurable period of time. Reasons for reject-
ing the connection requests are exceedence of the
overbooking factor limit or the RBDC max of the ter-
minal is higher than the RBDC max of the SLA.
VBDC-Based Rejection The percentage of the connections that were refused
Ratio (%) because the max best-effort traffic of the terminal is
larger than the size of the LL RL SLA versus the total
number of protection mode change requests to the LL-
RL-SLA, averaged over a configurable period of time.
Table 8.18 Conditional Return Link Connection Statistics page fields
The Conditional RL Connection Statistics page will automatically refresh at the given
on page 31).
The Graph button lets you navigate to the Conditional RL Connection Statistics Graph
page which enables you to setup graphical representations of the Conditional RL Connec-
tions Statistics parameters. For a detailed description of the various NetManager Graph
pages, refer to “Statistics Graphs” on page 318.

850176 P08
8.6.9 SIT SCPC

This statistics page displays a summary of the performance statistics of the SCPC SITs. To
access this page, select the SIT SCPC Statistics item from the RL Statistics sub-menu in
the Navigation Bar’s Operations menu.
Figure 8.20: SIT SCPC Statistics page
Table 8.18 explains the statistics and informational fields displayed:
Field Description
SIT Name The name that identifies the SIT Group.

Es/No (dB) The Energy per symbol / Noise power spectral density.
BER The Bit Error Rate (BER) for this SIT Group.
Freq Offset (Hz) The Freq Offset (Hz) for this SIT Group.
Power Level (%) The power level (%) for this SIT Group.
Table 8.19 SIT SCPC Statistics page fields

850176 P08
8.6.10 MPEG PID Traffic Statistics

The FL MPEG PID Traffic Statistics page (see Figure 8.21) presents MPEG Forward
Link traffic based on PIDs. To access this page, select the MPEG PID Traffic item from
the FL Statistics sub-menu in the navigation bar’s Operations menu.
Figure 8.21: FL MPEG PID Traffic Statistics page
The following information is provided for each entry:
Field Description
SIT Group Name The SIT Group for which the data was collected.
SG SLA Name The SIT Group Service Level Agreement name
associated with the particular MPEG Traffic.
PID The PID for the particular MPEG Traffic.
SLA Min (kbit/s) The minimum bit rate encountered for the MPEG
traffic item in the given SG FL SLA.
SLA Max (kbit/s) The maximum bit rate encountered for the MPEG
traffic item in the given SG FL SLA.
Table 8.20 FL MPEG PID Traffic Statistics page fields

850176 P08
Field Description
Current (%) The current traffic percent of maximum bit rate.

5 minute Average (%) The average traffic percent of maximum in the last
5 minute interval.
1 hour Average (%) The average traffic percent of maximum in the last
1 hour interval.
24 hour Average (%) The average traffic percent of maximum in the last
24 hour interval.
Table 8.20 FL MPEG PID Traffic Statistics page fields
The FL MPEG PID Traffic Statistics page will automatically refresh at the given interval,
31).
The Graph button lets you navigate to the FL MPEG PID Traffic Statistics page which
enables you to setup graphical representations of the MPEG PID parameters. For a detailed
description of the various NetManager Graph pages, refer to “Statistics Graphs” on page
318.

850176 P08
8.6.11 Route MPEG Traffic Statistics

The FL Route MPEG Traffic Statistics page (see Figure 8.22) presents MPEG traffic sta-
tistics based on Routes. To access this page, select the Route MPEG Traffic item from the
FL Statistics sub-menu in the navigation bar’s Operations menu.
Figure 8.22: FL Route MPEG Traffic Statistics page
Field Description
Route The Route for which MPEG traffic data was collected.
SIT Name The particular SIT through which the MPEG traffic
flowed.
MAC Address The MAC address identifying the SIT.
QoS Min (kbit/s) The minimum bit rate encountered on the for QoS.
Table 8.21 FL Route MPEG Traffic Statistics page fields

850176 P08
Field Description
QoS Max (kbit/s) The maximum bit rate encountered on the for QoS.
5 minute Average (%) The average traffic percent of maximum in the last 5
minute interval.
1 hour Average (%) The average traffic percent of maximum in the last 1
hour interval.
hour interval.
Table 8.21 FL Route MPEG Traffic Statistics page fields
The Graph button lets you navigate to the FL Route MPEG Traffic Statistics Graph
page which enables you to setup graphical representations of the Route MPEG Statistics

850176 P08
8.6.12 FL Partition IP Traffic Statistics

The FL Partition IP Traffic Statistics page (see Figure 8.23) presents traffic statistics
based on Partitions. To access this page, select the Partition IP Traffic item from the FL
Statistics sub-menu in the navigation bar’s Operations menu.
Figure 8.23: FL Partition IP Traffic Statistics page
Field Description
Partition Name The name of the partition.

Partition Type The type of partition.
SLA Min (kbit/s) The minimum bit rate encounter for the partition in the
SLA.
SLA Max (kbit/s) The maximum bit rate encounter for the partition in the
SLA.
Table 8.22 FL Partition IP Traffic Statistics page fields

850176 P08
Field Description
5 minute Average (%) The average traffic percent of maximum in the last 5
minute interval.
hour interval.
hour interval.
Table 8.22 FL Partition IP Traffic Statistics page fields
The Graph button lets you navigate to the FL Partition IP Traffic Statistics Graph page
which enables you to setup graphical representations of the Statistics. For a detailed
description of the various NetManager Graph pages, refer to “Statistics Graphs” on page
318.
8.7 Statistics Graphs

8.7.1 Custom Graphing
As well as present operational statistics in table form, NetManager can also display the
same data using a graphical representation that makes it easier to view trends and spot
abnormalities. This graphing functionality can be accessed from the different Statistic pages
(see “SIT Group Performance Statistics” on page 294) by clicking the Graph button.
Although the individual pages each present a different list of statistical parameters to setup
and graph, they are all identical in look-and-feel and the mechanics of graphing parameters
is identical for all of them.
Note: Graphs are displayed as bitmaps in the browser, allowing users to save them
locally.
Note: The list of available parameters in each Graph page is taken from the
columns in the specific statistics page linking to it.
For example, the statistics that can be graphed in the Advanced RL Login
Statistics Graph page are the column titles in the Advanced RL Login
Statistics page.
Refer to “SIT Group Performance Statistics” on page 294 for the parameter
list in each page.

850176 P08
All Graph pages display the same configuration parameters (see Table 8.23), used to setup
which statistic to graph and to define a filter on the range of data to be displayed.
Field Description
Statistic Select the parameter to graph from the drop-down list.

The list of parameter depends on the individual
statistics page being accessed; refer to the following
sections for the available parameters associated to a
given page:
• Connection Statistics, see “Connection Statistics” on
page 295.
• Advanced Connection Statistics, see “Advanced RL
Login Statistics” on page 297.
• RL Traffic Statistics, see “Return Link Traffic Statis-
tics” on page 299.
• RL Advanced Traffic Statistics, see “Return Link
Advanced Traffic Statistics” on page 301.
• Managed VoIP Call Statistics, see “Managed VoIP
Call Statistics” on page 303.
• Managed VoIP Advanced RL Statistics, see “Man-
aged VoIP Advanced Return Link Statistics” on page
305.
• Return Link RFCM Statistics, see “Return Link
RFCM Statistics” on page 307.
• Conditional RL Connections Statistics, see “Condi-
tional Return Link Connection Statistics” on page
309.
• MPEG PID Statistics, see “MPEG PID Traffic Statis-
tics” on page 313.
• MPEG Route Statistics, see “Route MPEG Traffic
• FL Partition Statistics, see “FL Partition IP Traffic
SIT Group Restricts the data to be displayed to the selected SIT
Group.
Period Span The gathering period for the statistics.
Period Type The units for the Period Span. Possible values are:
• Day
• Hour
• Minute
Table 8.23 Statistic Graph page fields

850176 P08
Field Description
End Date (YYYY-MM- Restricts the data to be displayed to the end date
DD HH:MM) sepcified.
Number of Points Restricts the number of data points to be displayed to

the selected maximum.
Possible values are: 100, 150, 200, ... 500
Table 8.23 Statistic Graph page fields

850176 P08
Once the statistic parameter has been selected and the range of data defined, click the
Graph It! button to generate the graph, which will be displayed below the Graph Parame-
ters section of the page (see Figure 8.24)
Figure 8.24: Example Performance data in Graph format

850176 P08
Additionally, it is possible to generate a text-box listing of the selected data range by click-
ing the Produce TSV button; the text data will be displayed below the Graph Parameters
section of the page (see Figure 8.25), replacing any graph that may currently be displayed
there. The text can be copied and pasted using normal edition capabilities and, because the
feature formats it as Tab Separated Value (TSV), it is ideal for exporting statistics data into
various analysis, graphing and spreadsheet applications for custom processing.
Figure 8.25: Example Performance data in TSV format
You can navigate back to the initial statistics page by clicking the < Statistics Table button
at the bottom of the page.
8.7.2 Fast Graph

Alternatively, each Statistics Table page has a Fast Graph feature that allows for the quick
display of particular data in a graph. To use the feature, simply click on one of the bold data
values in the table: the last 500 data points for the type of data identified by the column
header and for the particular row in which the cell was clicked will be displayed in a graph.
For example, in the FL MPEG PID Traffic Statistics table of Figure 8.21, clicking on the
value “200” at the intersection of the “SLA Min (kbits/s)” column and the “dw - Single”
row will display up to the last 500 points of SLA Min for the SIT Group dw - Single.

850176 P08
8.8 Queries
The SIT Import can be performed via scripts which run on the local computer of the Net-
Manager user. Scripts can also be used to query the SMS/CM database for the following
information:
• SIT configuration per MAC address,

• SIT status per MAC address,
• SIT alarms per MAC address,
• SIT group performance data per Service Provider.
Note: Script template can be provided by Advantech on demand.
The Query Script Requirements are:
• Perl interpreter (Unix/Linux OS)

• Perl + Curl (Windows OS)
• Knowledge of the SMS server IP address
• A number of arguments (required + optional)
Script executes a web page:
NetManager_API.php
The required arguments are:

<script> -s <login> –p <password> -o <results.xml> -sp <Service-Provider>
with optional argument:
-f <import_file>
Table 8.24 lists the parameters used in Queries and the specific information they return.
Option Definition
-s <login_name> The login name used by the Service Provider.

-p <password> The password of the user.
-sp <service_provider> The Service Provider name on which the query
(optional) will be performed. This option is only
applicable for Network Operator queries. As an
SP, the relationship is obvious.
Table 8.24 Query parameters

850176 P08
Option Definition
-statistics Performs a query on the SIT group statistics of

the Service Provider.
-sp_sit_group This query returns every SIT group related to
the Service Provider with MAC address and
login state of each SIT in those groups.
-sit_group <sit_group_name> Performs a query on the SIT group. This query
returns every SIT profile related to the SIT
group specified.
-sit_alarm <mac_address> Performs a query on the alarms generated by
the SIT specified by the <mac_address>.
Return only the alarms generated in the past 24
hours.
-sit <mac_address> Performs a query on the SIT specified by the
<mac_address>. Return its profile and
operational status.
-o <query_response.xml> The output filename of the query results as an
XML format.
Table 8.24 Query parameters

850176 P08
Chapter 9 General System Administration
This chapter presents the system administration tasks available to Network Operators from
the NetManager user interface.
This topic is covered in the following section:
• Db/CM: provides general configuration applicable to the database and Connection
Manager “System Administration” on page 326.
• FL QoS Rules: Describes the Forward Link Quality of Services rules that can be
defined in the system “FL QoS Rules” on page 333.

850176 P08
9.1 System Administration

9.1.1 System Administration Page
Many of the database and Connection Manager related tasks that Network Operators need
to perform are available through the System Administration page (see Figure 9.1 (page
327)). The page also presents certain non-configurable system settings, for information pur-
poses.
To access this page, select the Db/CM item from the System Admin sub-menu of the CFG
Equipment menu in the navigation bar.

850176 P08
Figure 9.1: System Administration page

850176 P08
The following system parameters are available from the System Administration page:
Field Description
Aging Data Cleanup In abnormal conditions, or normal conditions within a

Threshold (days) busy network, large numbers of CM events may be gen-
erated. To assist in managing this volume of information,
an automatic alarm and event clean up process exists.
This parameter permits setting the number of days after
which data in the alarm and events tables is considered
available for removal by the automatic data clean up pro-
cess.
Warning: When a log entry has reached the aging

threshold, it will be automatically
deleted by the system and is not
recoverable.
Network Id The network ID to be used for all the SITs in the network.
Connection Manager
Database IP Address The IP Address used to access the database.
Prime Database IP The IP Address of the database that is designated as
Address Prime.
Redundant Database IP The IP Address of the database that is designated as sec-
Address ondary.
CM Virtual Management The Connection Manager IP address, for SIT login pur-
IP Address pose. This is the IP address where SITs will send traps
when they login to the network.
CM Stats Computational The period (in seconds) for login performance statistics
Period (sec) computation by the Connection Manager.
Note: Refer to “Connection Statistics” on page

295 and “Advanced RL Login Statistics”
on page 297 for additional information on
connection statistics.
CM Period (sec) The period (in seconds) for the computation and database
storage of performance counters handled by the Connec-
tion Manager.
Table 9.1 System Administration page fields

850176 P08
Field Description
Licensing
Max Nb of Licensed SITs This field shows the maximum number of terminals
which can be configured into the database, as licensed to
the Network Operator.
Max Nb of Licensed Ser- This field shows the licensed maximum number of Ser-
vice Providers vice Providers that can be configured on the system.
Triggers
Trigger CM Port The Connection Manager socket port on which database
triggers are to communicate change messages.
Nb of Trigger Retries The number of times that triggers are to attempt to trans-
mit database change messages to the Connection Man-
ager.
Trigger Timeout (msec) The timeout (in milliseconds) for triggers to communi-
cate database change messages to the Connection Man-
ager when it is not acknowledging the message.
Trigger Abort Time (sec) The period (in seconds) for triggers to abort communica-
tion of database change messages with the Connection
Manager if no acknowledgment is received.
Rain Fade Login
Number of SIT Login The number of times SITs are allowed to attempt login in
Retries to a different protection level before failing.
SIT Login Interval (sec) When the events of the types SIT Login Request Refused
and SIT Logoff Received are generated too often from
the same SIT during a certain period of time, the CM
stops logging them and generates a “too many SIT con-
secutive login attempts” alarm; it then blocks those event
types until the alarm clears, when two SIT login requests
are separated by more than a given threshold.
This parameter permits setting this threshold; the parame-
ter also describes the number of seconds that a SIT must
wait between login attempts to a different protection
level.
Geographic Redundancy
CMS 1 IP Address The IP Address of the first redundant CMS.

850176 P08
Field Description
CMS 2 IP Address The IP Address of the second redundant CMS.

Geographic Redundancy The current redundancy state of the system.
State
N+1 Redundancy
N+1 Redundancy Enabled Indicates if the N+1 Redaundancy feature is enabled for
this NetManager.
Redundancy Backup Interval at which the NetManager will trigger a backup of
Period (Hours) the devices involved in the N+1 Redundancy scheme.
Number of Active Chain Number of chain in the N+1 redundant system that are
active under normal operating conditions.
Chain number Chain number of the chain managed by this NetManager.
Standby Chain Indicate if the chain managed by this NetManager is the
standby chain.
Standby chain CM IP IP address of the CM server of the standby chain.
Address
To change an editable field: modify its value as desired and click the Update button.
Note: For more information on updating the records in the database, see
“Updating Records in the Database” on page 38.
The Switch CM button can be used to switch to the Redundant Connection Manager; the
Restart CM button can be used to restart the Connection Manager.
You can also abandon your latest changes and go back to the Service Provider page by
clicking the < Back to Service Provider button.

850176 P08
9.1.2 Connection Manager Redundancy

9.1.2.1 Architecture
Connection Manager redundancy is based on 2 distinct concepts. The first is a mechanism
to handle failover scenarios which is based on a heartbeat scheme to determine the state of
nodes in a cluster of servers; the second is a database replication system which is responsi-
ble for ensuring mirroring of data across multiple databases (see Figure 9.2).
Figure 9.2: CM Redundancy Diagram
Note: As the redundancy scheme requires that SNMP be enabled, SNMP traffic
must be configured to pass through both CM server firewalls.
Table 9.3 summarizes the supported redundancy scenarios; cases B and C can be handled
by the failover scripts on the machines and are performed automatically. Cases A and D
require that the machines are aware who is prime and who is acting as a backup server at
boot up time.
Redundancy Case CM1 CM2
A) Normal Boot-up Alive as Prime server Alive as Backup server

B) Prime Failure Dead Alive as Prime server
Table 9.2 Supported CM Redundancy Scenarios

850176 P08
Redundancy Case CM1 CM2
C) Backup Failure Alive as Prime server Dead

D) Prime Boot up following a failure Alive as Backup server Alive as Prime server
Table 9.2 Supported CM Redundancy Scenarios
9.1.2.2 CM Failover
Failover management is implemented using Linux High-Availability project with the fol-
lowing components: heartbeat script, failover script, virtual CM IP address management
script.
The purpose of the heartbeat script is to determine which companion server has failed. This
is achieved using constant communication between the two servers at a user configurable
period. If the communication has been deemed as failed (e.g. after a user configurable time-
out), the backup server invokes the failover script to take over functions of the prime server.
The failover script invokes database failover logic, which is different for the prime CM and
backup CM. Of special interest, in the case when the backup CM is brought up as prime, a
CM alarm is written into the database: “CM redundancy failover happens”.
9.1.2.3 Database Replication

Database synchronization is implemented by copying the live master database to the backup
machine and restoring it every 8 hours. It works by a scheduled logging into the master
server by the backup server, running a script which backs up the master database, and copy-
ing this database back to the backup server. After a copying is finished, this database is
restored on the backup server.

850176 P08
9.2 FL QoS Rules

9.2.1 Viewing FL QoS Rules
The list of FL QoS Rules defined so far is available in the FL QoS Rules page (see Figure
9.3). To access this page, select the FL QoS Rules item from the System Admin sub-menu
in the navigation bar’s CFG Equipment menu.
Figure 9.3: FL QoS Rules page
This page lists the FL QoS Rules and their associated parameters, as described in Table 9.3.
Field Description
ID The Rule’s identifier.

System Entry Reflects whether or not the Rule has System Entry.
IP DVB Equip- The IP DVB Encapsulator associated with this Rule.
ment Type
QoS Device Type The Quality of Service equipment associated with this Rule.
Table 9.3 FL QoS Rules page fields

850176 P08
• Add/Update a FL Qos Rule: you can create or modify a Rule. For more information,
see “Adding and Updating a FL QoS Rule” on page 334.
• Delete a FL QoS Rule: you can select one or more FL QoS Rule from the Grid Table
and delete them from the database. For more information, see “Deleting a FL QoS
Rule” on page 338.
9.2.2 Adding and Updating a FL QoS Rule

To update an existing FL QoS Rule, select it from the Grid Table in the FL QoS Rules page
and click the Update button, or to add a new Rule, click the Add button. This brings up the
FL QoS Rule Configuration property page as shown in Figure 9.4 (page 335).

850176 P08
Figure 9.4: FL QoS Rule Configuration page

850176 P08
Modify the FL QoS Rule as required and click the Update or Add button, the case being.
The FL QoS Rule configuration fields are described in Table 9.4:
Field Description
Device Type The equipment model related to the Rule.

Device Name The name of the device associated with the Rule.
SP FL SLA
CBR Is Constant Bit Rate traffic associated with the Rule at
the SP FL SLA level.
VBR Is Variable Bit Rate traffic associated with the Rule at
the SP FL SLA level.
UBR Is Unspecified Bit Rate traffic associated with the Rule
at the SP FL SLA level.
ATM Is ATM traffic associated with the Rule at the SP FL
SLA level.
High Priority (guaranteed The high priority guaranteed bandwidth at the SP FL
bw) SLA level.
Low Priority (guaranteed The low priority guaranteed bandwidth.
bw)
High Priority (opportunis- The high priority opportunistic bandwidth at the SP FL
tic bw) SLA level.
Low Priority (opportunis- The low priority opportunistic bandwidth at the SP FL
tic bw) SLA level.
Max number of entries The maximum number of entries for this Rule.
Section Packing The section packing option associated with the Rule.
SG FL SLA
the SG FL SLA level.
the SG FL SLA level.
at the SG FL SLA level.
ATM Is ATM traffic associated with the Rule at the SG FL
SLA level.
Table 9.4 Fl QoS Rule Configuration page fields

850176 P08
Field Description
High Priority The high priority bandwidth at the SG FL SLA level.

Low Priority The low priority bandwidth at the SG FL SLA level.
QoS Partition
the QoS Partition level.
the QoS Partition level.
at the QoS Partition level.
ATM Is ATM traffic associated with the Rule at the QoS
Partition level.
High Priority The high priority bandwidth at the QoS Partition level.
Low Priority The low priority bandwidth at the QoS Partition level.
IPE Partition
the IPE Partition level.
the IPE Partition level.
at the IPE Partition level.
ATM Is ATM traffic associated with the Rule at the IPE
Partition level.

850176 P08
Field Description
High Priority The high priority bandwidth at the IPE Partition Profile
level.
Low Priority The low priority bandwidth at the IPE Partition level.
FL QoS Profile
Guaranteed BW Is Guaranteed bandwidth associated with the FL QoS
Profile.
Opportunistic BW Is Opportunistic bandwidth associated with the FL QoS
Profile.
High Priority The high priority bandwidth at the FL QoS Profile level.
Low Priority The low priority bandwidth at the FL QoS Profile level.
To return to the FL QoS Rules page, click the < Back to FL QOS Rules button.
9.2.3 Deleting a FL QoS Rule

To remove a FL QoS Rule from the database, select one or more items from the Grid Table
in the FL QoS Rule page and click the Delete button.
Alternatively, you can open the configuration page for the FL QoS Rule to delete (see
“Adding and Updating a FL QoS Rule” on page 334) and click the Delete button.

850176 P08
Chapter 10 Security
This chapter presents the general security framework put in place in the NetManager appli-
cation. It outlines the tasks operators must perform in order to ensure the security and
integrity of the system.
• “Back-up and Restore” on page 340 explains how to safeguard and reload your data.
• “User Security Certificates” on page 344 explains how to manage the security certifi-
cates necessary to connect securely to the NetManager application.

850176 P08
10.1 Back-up and Restore

Data safeguarding on any large system invariably involves the ability to save and restore all
user data. Regular backups protects against catastrophic system failure by enabling opera-
tors to load a previously saved backup. There are also other convenient uses of backup and
restore functionality:
• to roll-back the NetManager configuration to an earlier state after a catastrophic sys-

tem failure, such as database corruption or hardware failure;
• to revert back to a stable state after a manipulation error;
• to troubleshoot a problem by saving various configuration and quickly switching
between them without having to reconfigure the system.
NetManager provides a multi-level backup and restore solution for easier data management:
• Service Provider backup: Manually performed to safeguard Service Provider data.

• Network Operator backup: Network Operators can backup the data for any given
Service Provider in the same manner as individual Service Providers backup their own
data; Network Operators can also schedule backups of the entire NetManager database
to be performed at regular interval.
10.1.1 Backup and Restore of Service Provider Data

Service Providers can safeguard their data against catastrophic system failures by regularly
backing up their data. As a best practice, data backup should also be performed before any
significant change is made to the system: this way, if a major error happens during the mod-
ification, you can easily revert back to a stable configuration. This also ensures that any
interrupted service is quickly restored, minimizing the impact of potentially severe prob-
lems.

850176 P08
To access the Save/Restore page, select SP Save/Restore from the CFG Mgmt menu in
the navigation bar.
Figure 10.1: Save/Restore page
The Save/Restore page (see Figure 10.1) allows Service Providers to create a backup of
their current configuration and to re-load a previously-saved backup file.
Selecting either the backup or restore functionality is done using the Add/Save toggle but-
ton: clicking it changes the page function from Save mode to Restore mode.
• In Save mode, the Backup Name field allows you to enter the name of the backup file
to create.
• In Restore mode, the Backup Name field becomes a drop-down list that allows you to
select the name of the file to restore from the list of previously saved files.
Note: Before toggling between Save and Restore modes, ensure that all fields are
empty: the Add/Save button has dual functionality, as this same button also
initiates the backup and restore operations when the Backup Name field has
a value.
10.1.1.1 Backing-up the NetManager Configuration

You can backup the current NetManager configuration at any time using the Save/Restore
page. You do not have to remove previous backup files to create a new one.
Network Operators can backup the data for a given Service Provider by selecting it from the
Service Provider drop-down list.

850176 P08
Note: The backup performed by Network Operators only operates on the data for
the selected Service Provider. The full system backup is covered in the
“System Backup” section on page 352, and requires command line access. It
is not available under the web interface.
To create a backup, follow these steps:
1. Click the Add/Save toggle button to select the backup functionality: this will be
indicated by the Backup Name field changing from a drop-down list to a field and the
Restore button being disabled.
2. Using the following fields, customize the backup file to create.
Field Description
Backup Name The name to assign to the current NetManager configuration.

Creation Date The date of creation of the backup file.
Note: This field will be filled automatically with the

current system date when performing a backup.
Description A description, comments, etc. associated with the backup.

Table 10.1 Save/Restore page fields
3. Click the Add/Save button again. If the backup is successful, a confirmation message
appears below the Add/Save button.
Note: If the operation is unsuccessful, make a note of any error message displayed
and consult “Server Operation and Maintenance” on page 347 for resolution
steps.
10.1.1.2 Restoring an NetManager backup file

Restoring a backup file loads its contents into the database, overwriting its contents with the
data contained in the file.
Warning: Restoring a previously saved backup file overwrites the database. All
current configurations will be lost to be replaced by the contents of the
restored file. 

Make sure that the correct file is selected and that it contains the data you
wish to restore, since this operation cannot be undone.

850176 P08
Network Operators can restore the data for a given Service Provider by selecting it from the
Service Provider drop-down list: only this Service Provider’s data will be overwritten.
To restore an NetManager configuration backup:
1. Click the Add/Save toggle button to select the backup functionality: this will be
indicated by the Backup Name field changing from a text field to a drop-down list and
the Restore button being enabled.
2. Select the backup you wish to restore from the Backup Name drop-down list
Field Description
Backup Name The backup to restore from the drop-down list.

Creation Date The date of creation of the backup file.
Definition A user-entered description of the backup file.
Table 10.2 Restore fields
3. Click the Restore button.
10.1.1.3 Deleting an NetManager Configuration Backup

To delete a backup from the file system, select the backup you wish to permanently delete
from the Backup Name drop-down list and click the Delete button.
It is possible to remove backups for a specific Service Provider by selecting it from the Ser-
vice Provider drop-down list.
Note: This operation cannot be undone: the file will be deleted from the server’s file
system and cannot be restored; care must be taken to ensure that the file
you are deleting is not needed any further.
10.1.2 Scheduled Backup and Restore of entire NetManager

database
Network Operators can perform scheduled database backups by configuring scripts on the
database server. The web interface will provide controls over the scripts. The entire data-
base content will be dumped to a pre-defined location on the file system.
Note: The current implementation of NetManager does not provide a user interface
for this functionality: it must be performed directly on the server.

850176 P08
Note: Backup files are not erased once a new one is produced, nor are they
automatically archived on a remote location. These file management tasks
are left to the discretion of your System Administrator.
These database dumps can be used to restore the entire database if needed; they are also
useful for data migration to future NetManager releases.
10.2 User Security Certificates

NetManager is a web-based solution: operators connect to the application on the NetMan-
ager web-server using a web browser.
When an operator connects to the SMS web server, a pop-up window appears to verify the
digital Security Certificate for the web server to which they are connected. After verifying
the information therein (by clicking the View Certificate button), they must accept the cer-
tificate for this session in order to proceed with using the application.
Figure 10.2: User Security certificate pop-up
Warning: If the information cannot be validated, the operators should not accept the
certificate, suspend all activity related to NetManager and contact their
System Administrator.

850176 P08
Note: If you do not see this initial check, you may already have accepted the
certificate in an earlier session within the same web browser window. If this is
not the case, you may not be connected to the proper server: contact your
System Administrator before continuing on.
During NetManager installation, a Default Security certificate is created. This default certif-
icate can be replaced by one issued by a Certification Authority such as VeriSign or Certi-
com. Your System Administrator can provide you with additional details on this procedure.
More information on Security Certificates can be found in “SSL Basics” on page 365.

850176 P08

850176 P08
Chapter 11 Server Operation and Maintenance
This chapter covers basic operation and maintenance of the NetManager servers; it con-
tains the following sections:
• “About Server Operation and Maintenance” on page 348 explains how to ensure that
the servers are kept in proper working condition.
• “Checking RAID Status” on page 349 explains how to monitor the status of the RAID
array hard drives.
• “System Backup” on page 352 details the procedure to produce a CD backup.
• “NetManager Software Updates” on page 355 explains the software upgrade proce-
dures.

850176 P08
11.1 About Server Operation and Maintenance

The tasks described in this chapter make extensive use of the server’s operating system fea-
tures.
Note: The operating system is factory configured using a single account (root) with
a default password. If this password has not already been changed, it is
recommended to do so (see “Changing the Root Password” on page 348).
Some of the tasks are easier to perform using a graphical user interface than a simple com-
mand line. Refer to “Using X-Windows” on page 348 for details on launching the operating
system’s graphical user interface.
If you do not use the X-Windows graphical interface, a mount command is required to
access the DVD:
mount /dev/cdrecorder /media/cdrecorder
When you are done using the DVD, use the umount command before ejecting it from the
DVD drive.
umount /media/cdrecorder
11.1.1 Changing the Root Password

The servers are configured by default without any user accounts other than root. The default
root password is asnsatnet.
The root password can be changed by logging in to a console as root and typing passwd at
the command prompt. You will be prompted for the old and new passwords.
11.1.2 Using X-Windows

Although X Windows (KDE) is installed at NetManager commissioning time, it is not con-
figured to automatically run at system startup, so as to minimize loading on the CPU in nor-
mal operation and reduce potential security vulnerabilities.
If you require X-Windows for certain tasks, type startx at the command prompt after log-
ging in.
Note: The X-Windows environment is primarily used for changing the configuration
of the server via the SuSe YaST2 tool.

850176 P08
11.2 Checking RAID Status

Two tools, a command line interface, see “Command Line Tool” on page 349, and a GUI
interface, see section “GUI Tool” on page 351, are available for maintaining the RAID
array.
11.2.1 Command Line Tool

The command line tool can be run by root and is invoked by typing:
/usr/StorMan/hrconf getconfig 1
An example output is shown below:

Controllers found: 1
----------------------------------------------------------------------
Controller information
----------------------------------------------------------------------
Controller Status : Optimal
Channel description : SAS/SATA
Defunct disk drive count : 0
Logical devices/Failed/Degraded : 1/0/0
--------------------------------------------------------
Controller Version Information
--------------------------------------------------------
BIOS : 1.1-0 (1608)
Driver : 1.4-0 (11662)
----------------------------------------------------------------------
Logical device information
----------------------------------------------------------------------
Logical device number 1
Logical device name :
RAID level : 10
Status of logical device : Optimal
Size : 141460 MB
Write-cache mode : Disabled (write-through)
Partitioned : Yes
Number of segments : 4
Stripe-unit size : 64 KB
Stripe order (Channel,Device) : 2,7 2,6 2,5 2,4
----------------------------------------------------------------------
Physical Device information
----------------------------------------------------------------------
Device #0
Device is a Hard drive
State : Online
Supported : Yes
Transfer Speed : SATA 1.5 Gb/s
Reported Channel,Device : 2,4
Vendor : WDC
Model : WD740ADFD-00NL

850176 P08
Firmware : 7QR4
Serial number : WD-WMANS1688577
World-wide name : 500E081000018134
Size : 70858 MB
Write Cache : Disabled (write-through)
FRU : none
S.M.A.R.T. : No
Device #1
State : Online
Supported : Yes
Vendor : WDC
Firmware : 7QR4
Size : 70858 MB
FRU : none
S.M.A.R.T. : No
Device #2
State : Online
Supported : Yes
Vendor : WDC
Firmware : 7QR4
Size : 70858 MB
FRU : none
S.M.A.R.T. : No
Device #3
State : Online
Supported : Yes
Vendor : WDC
Firmware : 7QR4
Size : 70858 MB
FRU : none
S.M.A.R.T. : No
Command completed successfully.

850176 P08
11.2.2 GUI Tool

You can launch the Adaptec RAID Utility (see Figure 11.1) on the server by typing the fol-
lowing:
/usr/StorMan/StorMan.sh
Figure 11.1 Adaptec RAID Utility

850176 P08
11.3 System Backup

The NetManager server configuration includes software to perform CD burning. The fol-
lowing software packages have been included:
Command Description
cdrecord Command line based CD burning tool

mkisofs Command line tool to create an ISO image
that can be burned by cdrecord or k3b
k3b KDE front-end to cdrecord
Table 11.1 CD Burning packages
11.3.1 Making an ISO Image

Before using cdrecord to burn a CD, you must first create an ISO image of the files to be put
on the CD-ROM. The generated ISO image can be burned to a CD-ROM using cdrecord by
following the steps in “Using cdrecord” on page 352 or in “Using K3b” on page 353,
depending on the package you wish to use.
To generate an ISO image from the command line, use the following command:
mkisofs -J -r -o <image.iso> <source_dir>

where:
• <image.iso> is the path and name under which to save the image file. It is recom-
mended to included the .iso extension.
• <source_dir> is the directory in which the files to put in the image are located.
Note: The <source_dir> parameter will be the root directory in the image file, and
as such will not appear in the image.
To verify the ISO image that was generated, the following commands can be used:
1. mount -oloop <image.iso> /mnt

2. ls /mnt
3. umount /mnt
11.3.1.1 Using cdrecord

To use cdrecord to burn an ISO image to a CD, the following command is recommended:
cdrecord -v dev=/media/cdrecorder -tao driveropts=burnfree –data

<image.iso>

850176 P08
11.3.1.2 Using K3b

As the CD writer and/or Linux driver do not support DAO mode and K3b automatically
selects DAO write mode, some of the K3b default options must be changed to be able to
successfully write a CD. The options that must be changed are described in the next two
sections: “CD Project” on page 353 and “Burning an ISO Image” on page 355.
11.3.1.2.1 CD Project
This section describes changes to the K3b default options for successful CD burning when
creating a CD project using New Data CD Project (see Figure 11.2):
Figure 11.2 K3b New Data CD Project
After creating the project and adding the files to burn, select Burn under Project.

850176 P08
In the next dialog window (see Figure 11.3), select TAO under Writing Mode (the default is
auto). De-select the On the Fly checkbox (using On the Fly causes the process to fail).
Figure 11.3 Burning a CD
Click the Filesystem tabulation and select the Generate Joliet extensions checkbox, see
Figure 11.4.
Note: Selecting Joliet is not mandatory, but is recommended to ensure long

filename compatibility with other operating systems.
Figure 11.4 Generate Joliet extensions

850176 P08
11.3.1.2.2 Burning an ISO Image

To burn a CD-ROM from a pre-generated ISO image, select Tools > CD > Burn CD Image
in K3b (see Figure 11.5). It is necessary to change the Writing Mode setting to TAO.
Figure 11.5 Burning an ISO image
11.4 NetManager Software Updates

Software updates are provided by Advantech on hard medium: either CD or DVD. They
may include NetManager application updates as well as operating system updates. This sec-
tion details the general update procedure to follow using hard medium.
Note: It is also possible to download the latest operating system updates (patches)
directly from the SuSE by going to their maintained server on the internet
(see “Manual Linux SLES Update” on page 356).
11.4.1 From the DVD

Software updates are provided on CD-ROM or DVD and include:
• the Suse Enterprise Linux 9.0 Updates.

• the NetManager software update.

850176 P08
Note: The upgrade procedure will automatically migrate your data to the new
database version. It is recommended to perform a full backup before
proceeding with the update procedure.
Software update can be performed using the following procedure:
1. Insert the CD-ROM in the server you wish to update.

2. To update SLES, type the following command:
/media/cdrecorder/install_sles_updates
3. To update the NetManager software, select one of the following commands, depending
on which server you are updating:
• to update the CM Server:
cd /media/cdrecorder
./update_cm
• to update the SMS Server:
./update_sms
• to update a server running both CM and SMS:
./update_smscm
4. Reboot the server.
11.4.2 Manual Linux SLES Update

There are two options for updating SLES 9.0. You can either use the Yast Tool (see “Using
Yast” on page 356) or use the command line (see “Using the Command-Line” on page 356).
11.4.2.1 Using Yast

To update SLES using the Yast tool, launch the graphical version of Yast from X-Windows
or the text based version from the command line. Select Software > Online Update and
follow the instructions.
11.4.2.2 Using the Command-Line

To update SLES to the most current patches, use the following command:
online_update
For this command to work, the following files must be configured as indicated in Table
11.2, where:
• you is your home directory,

850176 P08
• userid is a valid user account name on the Suse server,

• password for the userid.
Configuration File Parameters

PASSWORD_http://sdb.suse.de/download="pass-
word"
USERNAME_http://sdb.suse.de/download="userid"
/var/lib/YaST2/you/password PASSWORD_http://sdb2.suse.de/download="pass-
word"
USERNAME_http://sdb2.suse.de/download="use-
rid"
http://sdb2.suse.de/download
/var/lib/YaST2/you/youservers
http://sdb.suse.de/download
SUSE SLES;9;x86_64;http://sdb.suse.de/down-
load/
/var/lib/YaST2/you/
you_server_settings SUSE CORE;9;x86_64;http://sdb.suse.de/down-
load/
Table 11.2 Configuration Parameters for a Suse Manual Update
If the Yast tool has previously been run and the Keep Authentication Data option selected,
the above files will already have been setup.
Note: The Suse support userid and password are in /var/lib/YaST2/you/password

and must be changed to values for a valid Suse account license.
Help for the online_update command can be listed by typing:
online_update --help
To list the current patches and updates available without downloading or installing the
patches, type:
online_update -s or -show_patches
To list the patches that have been installed on the system, type:
online_update -I or online_update -show_installed

850176 P08

850176 P08
Chapter 12 Troubleshooting
This chapter presents the error and warning messages that the NetManager application can
generate. It also presents the validation rules used when adding or updating the entities in
the NetManager database.
• “Overview of User Input Validation” on page 360

• “Return Link SIT Level QoS Checks” on page 360
• “SIT Group Forward Link SLA Checks” on page 360
• “SIT Group Checks” on page 361
• “SIT Checks” on page 362
• “Overwritten RL SIT Level QoS” on page 362
• “Traffic Queue Checks” on page 363
• “VCC Range Checks” on page 363
• “IP Address Range Checks” on page 363
• “PID Range Checks” on page 363
• “Service Provider Forward Link SLA Check” on page 364
• “Low Level Return Link SLA Checks” on page 364
• “Service Provider Checks” on page 364

850176 P08
12.1 Overview of User Input Validation

The NetManager application performs input validations whenever the operator enters infor-
mation to perform a database operation: i.e. the addition of a new entity in the system or the
modification of an existing one (see “Adding, Updating and Deleting Records” on page 37).
Many of these validation checks only produce a warning to the operator that a certain target
or limit has been exceeded. In certain cases, the limit may be strict: the operation is rejected
and NetManager displays an error message containing the name of the field where the prob-
lem was detected (see “Buttons” on page 30).
12.2 Return Link SIT Level QoS Checks

The following checks are performed when an RL QoS profile is added/updated (Return
Link SIT Level QoS page):
• All traffic data must be a multiple of:

• 16 kbit/second for ATM1
• 32 kbit/second for ATM2
• 57 kbit/second for MPEG
• The sum of Constant traffic bit rate (CRA), maximum persistent traffic bit rate
(RBDC) and maximum Best Effort Traffic bit rate (VBDC) must be:
• greater than 16 kbit/second
• smaller than 4 Mbit/second
12.3 SIT Group Forward Link SLA Checks

The following checks are performed when an SG FL SLA is added/updated (SIT Group
Forward Link SLA page):
• The PID must be unique within the SP PID Range.

• Priority must be in the range 1 to 8192 if the IP DVB Encapsulator is Novra, or
Null if SMR-25.
• The minimum capacity must be smaller than the minimum guaranteed bit rate for
the Service Provider Forward Link SLA minus the sum of the minimum guaranteed
bit rate of the SIT Group SLAs.

850176 P08
12.4 SIT Group Checks

The following checks are performed when an SIT group is added/updated (SIT Group
page):
12.4.1 Return Link

If a Default Return Link QoS profile and an SP Return Link SLA are defined:
• The sum of the default RL QoS components:

• Constant traffic bit rate (CRA),
• maximum Persistent traffic bit rate (RBDC)
• maximum Best Effort Traffic bit rate (VBDC)
must be smaller than, or equal to, the maximum capacity of the Return Link SLA for
the Service Provider.
• The sum of the Constant traffic bit rate (CRA) and the maximum Persistent traffic
bit rate (RBDC) of the default RL QoS profile must be smaller than, or equal to, the
minimum guaranteed capacity of the Return Link SLA of the specific Service Pro-
vider.
• The sum of the default RL QoS components:
• Constant traffic bit rate (CRA)
• maximum Persistent traffic bit rate (RBDC)
• maximum Best Effort Traffic bit rate (VBDC)
must be smaller than, or equal to, the Low Level Return Link Service Level
Agreement user carrier bit rate (i.e. user carrier rate to be added in the DB).
12.4.2 Forward Link

If a Default Forward Link QoS Profile and a SIT Group Forward Link Service Level Agree-
ment are defined:
• The maximum rate in the default FL QoS profile(s) shall be smaller than, or equal
to, the maximum capacity of the SIT Group Forward Link Service Level Agree-
ment.
• The minimum rate of the default Forward Link QoS profile shall be smaller than, or
equal to, the guaranteed capacity of the SIT Group Forward Link Service Level
Agreement.

850176 P08
12.4.3 Other Validation

The SMS shall check the existence of the link between the SIT group and default RL and
FL QoS profiles (i.e., one for RLSS, many for the RL queues, and many for the FL streams)
and signal a warning if one of the following items are specified for the SIT group:
• one RL QoS
• one queue QoS
• one FL QoS default
12.5 SIT Checks

The following checks are performed when an SIT is added/updated:
• Ethernet IP Address shall be within range of SP IP Addresses Ranges with Traffic

usage type.
• OAM IP Address shall be within range of SP IP Addresses Ranges with OAM
usage type.
• All IP addresses shall be unique considering their mask.
• The number of SIT profiles that are linked to the SIT group should be smaller than
the maximum of allowed terminals for the SIT Group.
• The number of SIT profiles that are linked to a SIT group should be smaller than
the maximum number of allowed terminals for the Service Provider and the SMS
license.
• The Low Level RL SLA User Carrier Rate should be smaller than the maximum
transmit rate.
12.6 Overwritten RL SIT Level QoS

• For the overwritten RL QOS, all traffic data shall be multiple of 16 (ATM1),
32(ATM2) or 57(MPEG).
• For the overwritten RL QOS, the sum of all traffic shall greater than 16 kbits and
smaller than 4 Mbits.
• The addition of a SIT, the RL QOS (CRA, RBDC, and VBDC) is validated accord-
ing to the CRA oversubscribing factor, RBDC oversubscribing factor, and VBDC
oversubscribing factor according to the following formulae:
• The sum of the maximum Constant traffic bit rate for all SITs of a Low Level
RL SLA is smaller than, or equal to, the maximum Constant traffic bit rate of
the corresponding Segment multiplied by the Constant traffic bit rate Oversub-
scribing factor.

850176 P08
• The sum of the maximum Persistent traffic bit rate (RBDC) for all SITs of a
Low Level RL SLA is smaller than, or equal to, the maximum Persistent traffic
bit rate of the corresponding Segment multiplied by the Persistent traffic bit
rate of the Oversubscribing factor.
• The sum of all maximum Best Effort Traffic bit rate (VBDC) for all SITs of a
Low Level Return link SLA should be smaller than, or equal to, (SLA maxi-
mum capacity minus Segment maximum Constant traffic bit rate minus Seg-
ment maximum Persistent traffic bit rate Segment) multiplied by the Best
Effort Traffic bit rate Oversubscribing factor.
12.7 Traffic Queue Checks

The following checks are performed when a traffic queue is added or updated (Traffic
Queue page):
• PID or VCC (VPI/VCI) shall be within range of PID or VCC, the case being.
• PID and VCC must be unique.
12.8 VCC Range Checks

The following check is performed when a VCC Range is added or updated (VCC Range
page):
• The VCC Ranges should not overlap.
12.9 IP Address Range Checks

The IP address ranges should not overlap.
12.10 PID Range Checks

The following checks are performed when a PID Range is added or updated (PID Range
page):
• PID Start shall be greater than 32 (DVB reserved).

• PID End shall be smaller than 8191 (null packet).
• The PID Ranges shall not overlap for the same IP DVB Encapsulator.

850176 P08
12.11 Service Provider Forward Link SLA Check

The following check is performed when a Service Provider Forward Link SLA is added or
updated (SP Forward Link SLA page):
• The allowed Priority range is:

• 1 to 5 for IP DVB Encapsulator of type SkyStream SMR-25,
• 1 to 255 for Novra IPE.
12.12 Low Level Return Link SLA Checks

The following check is performed when a Low Level Return Link SLA is added or updated
(Low Level Return Link SLA page):
• The maximum Constant traffic bit rate should be smaller than the minimum
guaranteed Return Link SLA for the specific Service Provider minus the maxi-
mum Persistent traffic bit rate (RBDC).
12.13 Service Provider Checks

The following checks are performed when a Service Provider is added or updated (Service
Provider page):
• The sum of the maximum number of configured terminals for all service providers
should be smaller than, or equal to, the licensed maximum number of configured
terminals of the network operator.
• The number of service providers should be smaller than, or equal to, the licensed
maximum number of service providers.

850176 P08
Appendix A SSL Basics
Secure Socket Layer (SSL) is a protocol for securing data transmissions across the Internet.
SSL is a part of most web browsers and uses a public-and-private key encryption system.
To establish an SSL connection, the SSL protocol requires that a server have a digital certif-
icate installed, which is an electronic file that uniquely identifies individuals and servers.
Digital certificates allow the client (Web browser) to authenticate the server prior to estab-
lishing the SSL session. Typically, digital certificates are signed by an independent and
trusted third party to ensure their validity. The "signer" of a digital certificate is known as a
Certification Authority such as VeriSign, Certicom, etc.
SSL enables secure online information exchange using the following:
• Authentication: A digital certificate is associated with a specific domain name.

Before issuing a digital certificate, the Certification Authority has the responsibility to
to confirm the identity of the organization requesting the certificate and whether it has
the right to use the domain name that will be associated with that certificate. This
strong binding between certificate and domain name provides users with an assurance
that they are interacting with a legitimate organization's Web site rather than an
imposter's.
• Encryption: Encryption is the process of transforming information to make it unintel-
ligible to all but the intended recipient. This forms the basis of data integrity and pri-
vacy in transacting with a web application. An SSL certificate, a special kind of digital
certificate, binds an identity to a pair of digital keys that can be used to encrypt and
sign information transmitted over the Internet via the "https" protocol. The Certifica-
tion Authority uses its private key to sign the certificate containing, among other
things, the organization's public key and "issues" the certificate to the organization.

850176 P08
• Message Integrity: After an SSL session has been established, the contents of all
communications between client and server are protected from tampering: no external
agent can modify the exchanged information. All parties to the transaction know that
the information they have received is exactly what originated from the other side of the
SSL session.

850176 P08
Appendix B FCAPS
B.1 Overview
FCAPS is an acronym for a categorical model of the working objectives of network man-
agement. There are five levels, called the fault-management level (F), the configuration
level (C), the accounting level (A), the performance level (P), and the security level (S).
B.2 Fault
At the F level, network problems are found and corrected. Potential future problems are
identified, and steps are taken to prevent them from occurring or recurring. In this way, the
network is kept operational, and downtime is minimized.
B.3 Configuration
At the C level, network operation is monitored and controlled. Hardware and programming
changes, including the addition of new equipment and programs, modification of existing
systems, and removal of obsolete systems and programs, are coordinated. An inventory of
equipment and programs is kept and updated regularly.

850176 P08
B.4 Accounting
The A level (also commonly called the allocation, the asset or the inventory level), is
devoted to distributing resources optimally and fairly among network subscribers. This
makes the most effective use of the systems available, minimizing the cost of operation.
This level is also responsible for ensuring that users are billed appropriately.
B.5 Performance
The P level is involved with managing the overall performance of the network. throughput
is maximized, bottlenecks are avoided, and potential problems are identified. A major part
of the effort is to identify which improvements will yield the greatest overall performance
enhancement.
B.6 Security
At the S level, the network is protected against hackers, unauthorized users, and physical or
electronic sabotage. Confidentiality of user information is maintained where necessary or
warranted. The security systems also allow network administrators to control what each
individual authorized user can (and cannot) do with the system.

850176 P08
Appendix C Scheduled Backups and Vaccum
The system can be programmed to periodically perform backups and vacuums of the data-
base. The vacuum operation consists in re-organizing the database data structures, while all
data and relationships, in order to optimize its operation.
A cron entry (/etc/cron.d/NetManagerdbcron) has been set to automatically perform

NetManager_vacuum_db and NetManager_backup_db on a daily basis. Backups are
stored to /var/lib/sms/NetManagerdb_backup_YYYYMMDD.tar.gz where YYYYM-
MDD is replaced by the current date.
The cron file is setup to perform the NetManager_vacuum_db at 07h00 GMT and the
NetManager_backup_db at 09h00 GMT (02h00 and 04h00 EST respectively).
During the vacuum and backup, the SMS/CM system can still be used, however, there may
be a performance/response impact. Therefore, it may be desirable to schedule the vacuum
and backup operation to occur at a time more convenient to the customer. The schedule can
be changed in the file /etc/cron.d/NetManagerdbcron.
The following has been reproduced from AD10 and also applies to the format of /etc/
cron.d/NetManagerdbcron.
Each line in the /etc/crontab file has the format:
minute hour day month dayofweek command
• minute — any integer from 0 to 59

• hour — any integer from 0 to 23
• day — any integer from 1 to 31 (must be a valid day if a month is specified)
• month — any integer from 1 to 12 (or the short name of the month such as jan, feb, and
so on)

850176 P08
• dayofweek — any integer from 0 to 7 where 0 or 7 represents Sunday (or the short
name of the week such as sun, mon, and so on)
• command — the command to execute. The command can either be a command such as
ls /proc >> /tmp/proc or the command to execute a custom script that you wrote.
• For any of the above values, an asterisk (*) can be used to specify all valid val-
ues. For example, an asterisk for the month value means execute the command
every month within the constraints of the other values.
• A hyphen (-) between integers specifies a range of integers. For example, 1-4
means the integers 1, 2, 3, and 4.
• A list of values separated by commas (,) specifies a list. For example, 3, 4, 6, 8
indicates those four specific integers.
• The forward slash (/) can be used to specify step values. The value of an integer
can be skipped within a range by following the range with /<integer>. For
example, 0-59/2 can be used to define every other minute in the minute field.
Step values can also be used with an asterisk. For instance, the value */3 can be
used in the month field to run the task every third month.
• Any lines that begin with a hash mark (#) are comments and are not processed.
An additional cron task has been setup to automatically delete database backups older than
30 days. The script that does this is installed in /etc/cron.daily/
NetManager_db_backup_clean. The threshold (currently 30 days) can be edited in this
file.

850176 P08
Appendix D Contacting Advantech Satellite Networks
Mailing Address
Advantech Satellite Networks

2341 boul. Alfred-Nobel, 4th floor
Saint Laurent (Montreal), QC
CANADA H4S 2A9
Telephone
• Advantech Satellite Networks Customer Service: +1-514-335-3908

• Fax: +1-514-335-6386
• Advantech Satellite Networks Satellite Networks general information: +1-514-335-
3550
Internet
• Support Web Site: www.advantechamt.com

• Support Email: support@advantechamt.com

850176 P08

850176 P08
Appendix E Reference Documents
The following documents provide reference material giving general descriptive and back-
ground information intended to aid in the understanding of this document.
Unless otherwise specified, the reference shall not be construed as imposing requirements
of any kind.
• NetManager Interface Control Document -

• 3Ware 8000 Series Users Guide
http://www.3ware.com/support/UserDocs/EscaladeUG7000-122003.pdf
• 3Ware Command Line Interface for Linux
http://www.3ware.com/support/UserDocs/3ware9000CLIGuide.pdf
• Apcupsd User Manual
http://www.apcupsd.com
• Nut UPS web site
http://us1.networkupstools.org/protocols/apcsmart.html
http://www.exploits.org/nut/library/apcsmart.html

850176 P08

850176 P08
Appendix F List of Acronyms and Terms
ACL Access Control List

ASI Asynchronous Serial Interface
ATM Asynchronous Transfer Mode
CBR Constant Bit Rate
CCS Centralized Configuration System
CM Connection Manager
CMS Command and Monitoring System
CMT Correction Message Table
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
DSM-CC Digital Storage Media-Command and Control
DVB Digital Video Broadcast
DVB-RCS Digital Video Broadcast – Return Channel System
ESD Electrostatic Discharge
FCAPS Faults, Configuration, Accounting, Performance, Security
FL Forward Link
FLCM Forward Link Command Module
FLSS Forward Link Sub-System
FTP File Transfer Protocol
GM Gateway Manager
GM-CCS Gateway Manager/Centralized Configuration System
GM-CMS Gateway Manager/Command and Monitoring System
GPS Global Positioning System
GUIs Graphical User Interface
HMI Human-Machine Interface
HTTP Hyper-Text Transfer Protocol
HTTPS Hyper-Text Transfer Protocol Secure
ID Identification or Identifier
IGMP Internet Group Management Protocol

850176 P08
IP Internet Protocol
IP/DVB Internet Protocol/Digital Video Broadcast
IPSec Internet Protocol Security
IPSS IP Sub-System
LAN Local Area Network
MAC Medium Access Control
MF-TDMA Multi-Frequency-Time Division Multiple Access
MIB(s) Management Information Base
MMT Multicast Map Table
MPE Multi-Protocol Encapsulation
MPEG Motion Pictures Experts Group
NAT Network Address Translation
NIT Network Information Table
NetMan- Network Management System
ager
NO Network Operator
NTPD Network Time Protocol Daemon
PCR Program Clock Reference
PEP Performance Enhancing Proxy
PID(s) Packet Identifier(s)
PMT Program Map Table
QoS Quality of Service
RCSS Return Channel System
RFC Request for Comments
RL Return Link
RLSS Return Link Sub-System
RMT RCS Map Table
RU Rack Unit
SCS SIT Command System
SG SIT Group
SIT(s) Satellite Interactive Terminal(s)
SLA(s) Service Level Agreement(s)
SLES Suse Linux Enterprise Server
SMS Subscriber Management System
SMS/SCS Subscriber Management System/SIT Command System
SNMP Simple Network Management Protocol
SP Service Providers
TBTP Terminal Burst Time Plan
TCP Transmission Control Protocol
TIM Terminal Information Message
TS Transport Stream
UBR Unspecified Bit rate
VBR Variable Bit Rate
VCC(s) Virtual Channel Connection(s)
VLAN Virtual Local Area Network

850176 P08
Appendix G Glossary
Area. A portion of physical Return Link bandwidth smaller than or equal to the SIT hopping
range. Each SIT transmits along the Return Link using bandwidth exclusively within a
single area. Areas are a scheduling tool used by the RLSS to assign traffic slots to SITs.
Comma Separated Values (CSV). A simple form of file for holding data, which is listed in columns
in a text file, each value being separated by a comma. Each new line represents a new set of data.
Continuous Rate Assignment (CRA). The Return Link throughput capacity provided to a SIT con-
tinuously and at all times when the SIT is logged in.
Forward Link. The path carrying communication from a gateway, via satellite, to SITs. It is based on
the DVB/MPEG standard.
Gateway. The central hub of a DVB-RCS network, responsible for managing all aspects of commu-
nication between SITs and terrestrial networks (e.g. the Internet).
Network Management System (NetManager). The part of the gateway responsible for managing all
elements of the DVB-RCS network.
Rate-Based Dynamic Capacity (RBDC). Throughput capacity that is requested dynamically by the
SIT and assigned by the RLSS. This capacity is rate-based in that the SIT requests, and the RLSS
assigns, a specific number of slots per frame, equivalent to a given throughput (traffic rate).
Return Link. The path carrying communication from SITs to the gateway. It uses a multi-frequency
time-division multiple access (MF-TDMA) scheme carrying ATM or MPEG cells.
Segment. The main SIT grouping for capacity assignment purposes. All SITs within a segment
share a guaranteed amount of Return Link capacity (GCA). As well, SITs within a segment can
receive additional capacity from a pool of throughput capacity that is shared by several segments.

850176 P08
Tab Separated Values (TSV). A simple form of file for holding data, which is listed in columns in a
text file, each value being separated by a tabulation space. Each new line represents a new set of
data; the format is similar to CSV.

850176 P08
Index
Numerics B
3DM see 3DM, under RAID Backup
Deleting 343
A Overview 340
Restoring 342
Access Control List, see ACL Scheduling 343
Access Rights 12 Best-Effort
ACL 14 see Best-Effort, under QoS
Acronyms 375 Bit Rate 138
Action Buttons 15 Burst Type 161
Confirmation 30
Error 30 C
Adding
Records 38 Categorical Model of the Working Ob-
Administration, see System Administra- jectives of Network Management, see
tion FCAPS
Alarms 288, 291, 371 CBR, see Service Category
Deleting 293 CCS
List 371 Overview 4
Overview 2 Centralized Configuration System, see
Severity 292 CCS
Area 138, 139, 140, 164, 167, 377 CM 288, 289
Assistance, see Help Alarms 292
ATM 8 Overview 2, 4
ATM, see Service Category Queries 323
Coding Type 164

850176 P08
Comma Separated Value, see CSV RLSS 64

Commands Type 83
Configuration 285 Error Message
Equipment 287 see Troubleshooting
Results 285 Event
SIT 283 Type 290
Type 287 Event notifications
Community Name 86, 90, 94, 98 List 371
Conditional Events 288, 289
see Conditional, under SLA RAID Failure 288
Configuration
Commands and Results 285 F
Configuration Summary 41
Connection Manager, see CM Faults
Connection Statistics List 371
see Statistics, under Connection FCA 235, 237
Contacting EMS 371 FCAPS 367
Context-Sensitive, see Tooltips Accounting 368
Continuous Rate Assignment, see CRA Configuration 367
Control 274 Fault 367
CRA 139, 175, 236, 237, 277, 377, 378 Performance 368
CSV 322 Security 368
FL, see Forward Link
D FLCM
Overview 4
Deleting FLSS 2, 8
Records 40 Forward Link 9
Recover 40 FLSS
Digital Security Certificate, see Security Overview 2
DNS 12 Overview 4, 8, 80, 377
Documents 373 QoS 5, 179, 200
DVB Encapsulator Overview 5
Type 85 Overwriting 5
DVB-RCS 301 SIT Group
Architecture 8 SLA 5
Overview 8 SLA see Forward Link, under SLA
Forward Link Control and Management,
E see FLCM
Forward Link Sub-System, see FLSS
EMS Satellite Networks 371
Enable TCP Rate Control 77 G
Equipment
Configuration 62 Gateway 9, 62, 80, 138, 377

850176 P08
Glossary 377 L
Grid Table, see GUI
GUI Licensed SITs, see SITs
Action Buttons 15 Log in 12
Grid Table 28 Low Level Return Link Service Level
Navigation Bar 16 Agreement
Overview 2 see Return Link, under SLA
Presentation Pane 15 Low Level Return Link SLA
Refresh Button 31 see Return Link, under SLA
SP Drop-Down List 25 Low Level RL SLA
Workspace 15, 26 see Return Link, under SLA
Grid Table 26, 27
Property Page 26
M
H MAC Address 277, 279, 280, 281
MAC-Address 229
Help 371 Maintenance 348
https Monitoring 42, 274
Overview 12
MPEG 8
overview 2
I N
Navigation Bar 16
Internet Protocol Sub-System, see IPSS Network Management System, see
IP Address NMS
Range 256, 259 Network Operator 46
Web Access 12 Administrator 46
IP Adress Operator 46
Range 259 Viewer 46
IP DVB Encapsulator NMS
Management IP Address 85 Architecture
Overview 5 DVB-RCS 2
Profile 80 FCAPS 2
IP Routes 247 Network Management 2, 3
IP Signaling 2 Overview 3
IPSec 243 Configuration
IPSS 9 Starter 3
Log in 12
K Operational Model 4
Overview 2, 377
KDE 348 NO, see Network Operator

850176 P08
O Q
OAM 244 QoS
Online Help, see Help Best-Effort 235
Operation 348 Forward Link 5, 179
Operational Model 41 Overview 2, 5
Overview 4 Overwriting 232
Over-Assignment Return Link 6, 178, 179
see Conditioning, under SLA Overwriting 232
Overbooking SIT 5
see Conditioning, under SLA SIT Forward Link 200
Oversubscription SIT Return Link 194, 207
see Conditioning, under SLA Quality of Service, see QoS
Queries 323
P
R
Password 46
PEP 71 RAID
Aux. Satellite IP Address 74 3DM 349, 351
Satellite IP Address 72, 74 Command Line Tool 349
Terrestial IP Address 72, 74 Failure 288
Type 74 Status 349
Performance 294 RAID Failure
PID 243, 256, 259 see Failure, under RAID
Postgres Rate-Based Dynamic Capacity, see
Backup 369 RBDC
cron job 369 RBDC 236, 237, 278, 377
Deleting 343 Records
Performance 369 Adding 37
Schedule 343 Deleting 37
Maintenance Updating 37
Vacuum Records, see Adding, Updating, Delet-
cron job 369 ing
Overview 369 Reference Documents, see Documents
Performance 369 Refresh Button 31, 42, 276, 283, 290,
Restore 340, 342 298, 316, 318
Schedule 343 Period 31
Presentation Pane Restore
see Presentation Pane, under GUI Overview 340
Primary Client IP Address, see ACL Schedule 343
Property Page, see GUI Return Link
ATM 8
MF-TDMA 8

850176 P08
MPEG 8 SSL 365

Overview 4, 8, 138, 377 User Category 46
Performance 2 Segment 138, 139, 140, 164, 167, 377
QoS 178, 179, 194, 207, 232 Service Category 146, 148, 159, 161,
Overview 6 169, 190
Overwriting 6 see Service Category, under SLA
RLSS 2 Service Level Agreement, see SLA
SLA Service Provider 46
see Return Link, under SLA Administrator 46
Return Link Sub-System, see RLSS Forward Link, see Forward Link
RL, see Forward Link Operator 46
RLSS 2, 8, 139, 157 Page 47
Configuration 138, 139 Profile 48
Importing 138 Adding 48
Importing 141 Deleting 50
Manager IP Address 65 Updating 48
Overview 138 Return Link, see Return Link
PEP 71 Viewer 46
Primary IP Address 65 Service Provider Forward Link SLA see
Profile 64 Forward Link, under SLA
Adding 64 Service Provider Return Link SLA see
Secondary IP Address 65 Return Link, under SLA
root Session 12
Password 348 Signal 278
Routes 9 SIT 8
Commands 283
S Control 274
Forward Link QoS 200
Satellite Interactive Terminals, see SIT Group 180
Save/Restore 341 Groups 178, 333
SCS Monitoring 274
Overview 4 Profile 224
Secondary Client IP Address, see ACL QoS 5
Section Packing 148 Queues 238
Secure Socket Layer, see SSL Type 244
Security Return Link QoS 194, 207
Access rights 46 State 277, 278
ACL 14 SIT Command System, see SCS
Certificate 344 SIT Group
Certificates 344 Overview 2
VeriSign 345 SLA
https 2 Forward Link 5
Overview 2 Overview 5

850176 P08
SIT Group Forward Link SLA 194 T

see SIT Group, under SLA
SIT Groups 185 Terminals, see SITs
SITs 47, 49, 329 Third Client IP Address, see ACL
SLA Tooltips 32
Bandwidth Traffic
Delay 4 Configuration 62
Jitter 4 Transport Stream 80, 83, 86, 140, 146,
Packet Loss 4 147, 189
Throughput 4 Trigger 329
Conditional 2 Abort Time 329
Conditioning 170 CM Port 329
Return Link 173 Nb. Retries 329
Forward Link 4, 5, 142, 144, 147, Timeout 329
149, 176, 178, 179, 185, 186 Troubleshooting 360
Overview 2, 4, 5 IP Address Range 363
Return Link 4, 5, 139, 142, 158, 160, Low Level Return Link SLA 364
178 Overwritten RL SIT Level QoS 362
Importing 138, 157, 168 PID Range 363
Low Level 139, 162, 166 Return Link SIT Level QoS 360
Overview 138 Service Provider 364
Service Category 138 Service Provider Forward Link SLA
Slot 9 364
SMS SIT 362
Overview 344 SIT Group
Queries 323 Forward Link 361
SNMP 86, 90, 94, 98 Return Link 361
SP Drop-Down List 25 SIT Group Forward Link SLA 360
SP, see Service Provider Traffic Queue 363
State VCC Range 363
see State, under SIT
Statistics 294
Connection 295, 313 U
Connection Advanced 297, 315, 317
csv 318 UBR, see Service Category
Graph 318 Updating
Managed VoIP 303, 307 Records 38
Managed VoIP Advanced RL 305 User
RL Advanced Traffic 301 Activity 56
RL Traffic 299 Description 57
System Administration 326 Occurrence 57
System Failure 340 Type 57
Category 46, 54
Default 14

850176 P08
Management 50, 51
Profile 12
Type, see User
category
User Account
Adding 52
Deleting 55, 60
Updating 52
User Interface, see GUI
User Logs, see Activity, under User
V
Vacuum, see Postgres
Maintenance
Variable Bit Rate, see VBR
VBDC 237, 278
VBR 138
VBR, see Service Category
VCC 256, 259
VCI 243
Voice over IP, see VoIP
VoIP 303, 307
VPI 243
W
Web Browser 12
Web Server 344
Web-Based Graphical User Interface,
see GUI
Workspace 15, 26
Grid Table 26, 27
Property Page 26
X
X-Windows
see KDE

850176 P08

NMS User Guide NO P08

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NMS User Guide NO P08

Uploaded by

Copyright:

Available Formats

NetManager User Guide

Network Operator’s Manual

Document Number: 850176

Document Number: 850176

Date: 27 August 2010

Proprietary Notice: Copyright © 2010 Advantech Satellite Networks, Inc. All

27 August 2010 Advantech Satellite Networks Proprietary Page II

Chapter 2. Overview of the NetManager Interface 11

27 August 2010 Advantech Satellite Networks Proprietary Page III

2.2.8 Quick Access Links 36

Chapter 3. NetManager Configuration Management 45

Chapter 4. Populating Gateway Data into NetManager 61

27 August 2010 Advantech Satellite Networks Proprietary Page IV

4.7.3 QoS Device Configuration Statistics 79

Chapter 5. Air Interface 99

27 August 2010 Advantech Satellite Networks Proprietary Page V

Chapter 6. Configuring Services 137

Chapter 7. Configuring Network 221

27 August 2010 Advantech Satellite Networks Proprietary Page VI

7.9 Mesh 269

Chapter 8. Monitoring The Gateway 271

27 August 2010 Advantech Satellite Networks Proprietary Page VII

Chapter 9. General System Administration 325

Chapter 10. Security 339

Chapter 11. Server Operation and Maintenance 347

Chapter 12. Troubleshooting 359

27 August 2010 Advantech Satellite Networks Proprietary Page VIII

12.4.2 Forward Link 361

27 August 2010 Advantech Satellite Networks Proprietary Page IX

27 August 2010 Advantech Satellite Networks Proprietary Page X

Table 3.1 Service Provider page fields 47

27 August 2010 Advantech Satellite Networks Proprietary Page XI

Table 5.5 Frequency Guard page fields 112

27 August 2010 Advantech Satellite Networks Proprietary Page XII

Table 6.31 SIT Software Version page fields 217

27 August 2010 Advantech Satellite Networks Proprietary Page XIII

Table 9.2 Supported CM Redundancy Scenarios 331

27 August 2010 Advantech Satellite Networks Proprietary Page XIV

Figure 1.1 NetManager within the Satellite Network 3

27 August 2010 Advantech Satellite Networks Proprietary Page XV

Figure 2.25 Tooltips: Range of possible values 33

27 August 2010 Advantech Satellite Networks Proprietary Page XVI

Figure 5.7 Frequency Guard page 111

27 August 2010 Advantech Satellite Networks Proprietary Page XVII

Figure 6.32 Daily Scheduling Recurrence options 214

27 August 2010 Advantech Satellite Networks Proprietary Page XVIII

Figure 8.14 RL Traffic Statistics page 299

27 August 2010 Advantech Satellite Networks Proprietary Page XIX

27 August 2010 Advantech Satellite Networks Proprietary Page XX

27 August 2010 Advantech Satellite Networks Proprietary Page 1

1.1 Role of the NetManager Application

27 August 2010 Advantech Satellite Networks Proprietary Page 2

1.2 NetManager Architecture

Figure 1.1: NetManager within the Satellite Network

Figure 1.2: NetManager Architecture

27 August 2010 Advantech Satellite Networks Proprietary Page 3

1.2.2.1.1 CCS: Centralized Configuration System

1.2.2.1.2 CM: Connection Manager

1.2.2.2 SCS: SIT Command System

1.3 Operational Model

1.3.1 Bandwidth Assignment: SLAs

27 August 2010 Advantech Satellite Networks Proprietary Page 4

1.3.1.1 Service Provider SLAs

1.3.1.2 Finer Grained Assignment Control