SHIRON IS-NMS User Guide 5.1

InterSKY Network Management
System
Installation & Operation Manual
Version 5.1
IS-NMS Installation & Operation Manual
IS-NMS Installation & Operation Manual

v5.1 (isnms v2.26)
This publication contains proprietary information belonging to Elbit Systems - Land & C4I - Shiron
SATCOM Business Line. Such information is supplied solely for the purpose of assisting explicitly and
properly authorized users of the InterSKY IS-NMS system.
No part of its contents may be used for any other purpose, disclosed to any person or firm, or reproduced
by any means, electronic and mechanical, without the express prior written permission of Elbit Systems -
Land C4I - Shiron SATCOM Business Line.
The text and graphics are for the purpose of illustration and reference only. The specifications on which
they are based are subject to change without notice.
No part of this publication shall be deemed to be part of any contract or warranty unless specifically
incorporated by reference into such contract or warranty.
The information contained herein is merely descriptive in nature, and does not constitute a binding offer
for the sale of the product described herein.
The software described in this publication is furnished under a license. The software may be used or
copied only in accordance with the terms of that agreement.
Information in this publication is subject to change without notice. Corporate and individual names and
data used in examples herein are fictitious unless otherwise noted.
Elbit Systems - Land C4I - Shiron SATCOM Business Line reserves the right to alter the equipment
specifications and descriptions in this publication without prior notice.
©2007-2011 Elbit Systems - Land C4I - Shiron SATCOM Business Line, all rights reserved.
Elbit, Elbit-Shiron, Shiron, and InterSKY IS-NMS are trademarks of Elbit Systems - Land C4I - Shiron
SATCOM Business Line and may be registered in certain jurisdictions. All other company or product
names are the trademarks or registered trademarks of their respective holders.
Elbit-Shiron is used throughout the document when referencing the company. Shiron is used when
describing files on the host computer.
©2007-2011 Proprietary and Confidential Page 2 of 149

Elbit Systems – Land C4I – Shiron SATCOM Business Line
IS-NMS Installation & Operation Manual Elbit-Shiron InterSKY IS-NMS
About this Manual

This manual describes the IS-NMS™ management application, including its installation,
configuration, and basic operating procedures.
References
 RLSS Installation and Operation Manual v5.1
 FLSS Installation and Operation Manual v5.1
 InterSKY NCC Operation Manual v5.1
 Drop&Insert Operation Manual
Document Conventions
Convention Purpose
Used to indicate important information or caution.
Used to indicate useful information that might be tangential to the current topic.

Table of Contents
1. Elbit-Shiron InterSKY IS-NMS ....................................................................................... 10
1.1 IS-NMS Environment ...........................................................................................................11
1.2 Inbound and Outbound .........................................................................................................13
1.2.1 Multi Channel Demodulator Controller (MCDC)..................................................13
1.2.2 Network Control Center (NCC) .............................................................................14
1.2.3 IP Encapsulator (IPE).............................................................................................14
1.2.4 OptimISe ................................................................................................................14
1.2.5 Cisco Router...........................................................................................................15
2. IS-NMS Browser ................................................................................................................ 17
2.1 View Selection ......................................................................................................................18
2.2 Menu Bar ..............................................................................................................................18
2.2.1 Help ........................................................................................................................18
2.2.2 Tools ......................................................................................................................19
2.2.3 Search.....................................................................................................................20
2.2.4 Log Out ..................................................................................................................23
2.3 Navigation Tree ....................................................................................................................23
2.3.1 Network View ........................................................................................................23
2.3.2 Remote View .........................................................................................................23
2.3.3 Add and Delete ......................................................................................................24
2.3.4 Common Functions ................................................................................................24
2.4 Central Monitoring ...............................................................................................................25
2.5 Work Area ............................................................................................................................26
2.6 Last Critical Events...............................................................................................................26
2.6.1 Filtering InterSKY Events .....................................................................................27
2.6.2 Event Log and Audit Enhancement .......................................................................28
2.7 Extended Group Display.......................................................................................................29
3. Network InterSKY Hub .................................................................................................... 31
3.1 InterSKY Hub Creation ........................................................................................................32
3.2 Hub Display ..........................................................................................................................33
3.3 Hub Deletion.........................................................................................................................34
3.4 Inbound .................................................................................................................................35
3.4.1 NCC .......................................................................................................................35
3.4.2 NCC Groups...........................................................................................................42
3.4.3 MCDC ....................................................................................................................45
3.5 Outbound ..............................................................................................................................48
3.5.1 IP Encapsulator ......................................................................................................49
3.5.2 OptimISe ................................................................................................................51
3.5.3 Cisco Router...........................................................................................................53
4. InterSKY Remote Gateway .............................................................................................. 56
4.1 Terminal Configuration ........................................................................................................57
4.1.1 Terminal Configuration Enhancements .................................................................62
4.1.2 Cross Polarization Test ..........................................................................................62
4.1.3 Drop&Insert ...........................................................................................................65
4.1.4 Migration................................................................................................................70
4.1.5 Owner Information.................................................................................................72
4.1.6 Upgrade ..................................................................................................................72
4.2 Terminal Networking Feature...............................................................................................75
4.2.1 Basic.......................................................................................................................75
4.2.2 Acceleration ...........................................................................................................76
4.2.3 Terminal Static Routing Table ...............................................................................79
4.2.4 Terminal Quality of Service ...................................................................................80

4.2.5 DSCP......................................................................................................................84
4.2.6 NAT .......................................................................................................................88
4.2.7 VLAN Creation ......................................................................................................94
4.3 Terminal Status .....................................................................................................................96
4.3.1 Restart the Terminal ...............................................................................................97
4.3.2 Telnet .....................................................................................................................97
4.3.3 Ping ........................................................................................................................98
4.4 Terminal Performance ..........................................................................................................98
4.4.1 Outage Table ..........................................................................................................99
4.4.2 Outage Chart ........................................................................................................100
4.4.3 Terminal Inbound/Outbound Throughput Graph .................................................101
4.4.4 Export Terminal Performance Report Data .........................................................102
5. NCC Terminal Groups .................................................................................................... 104
5.1 Terminal Group Status........................................................................................................104
5.2 Terminal Group Performance .............................................................................................105
5.2.1 Group Outage Report ...........................................................................................106
5.2.2 Group Bandwidth Utilization Table .....................................................................107
5.2.3 Group Bandwidth Utilization Chart .....................................................................108
5.2.4 Group Throughput Chart......................................................................................109
5.2.5 Terminal Performance Export ..............................................................................110
6. System Administration and VNO Support ................................................................... 112
6.1 Restricted Access ................................................................................................................113
6.2 IS-NMS VNO Model..........................................................................................................114
6.3 IS-NMS Profiles System.....................................................................................................115
6.3.1 User Profile ..........................................................................................................116
6.3.2 Administrator Profile ...........................................................................................116
6.3.3 System Operator Profile .......................................................................................117
6.3.4 System Viewer Profile .........................................................................................117
6.3.5 Group Owner Profile............................................................................................117
6.3.6 Group Operator Profile ........................................................................................118
6.3.7 Group Viewer Profile ...........................................................................................118
6.3.8 User Profile ..........................................................................................................119
6.4 Managing IS-NMS Accounts .............................................................................................119
6.4.1 Adding a New IS-NMS Account .........................................................................119
6.4.2 Deleting an IS-NMS Account ..............................................................................120
6.4.3 Modifying an IS-NMS Account...........................................................................120
6.5 First Time Login .................................................................................................................121
6.6 Database Backup and Recovery .........................................................................................122
6.6.1 Database Backup Routine ....................................................................................122
6.6.2 Database Restore Routine ....................................................................................122
6.6.3 Database Backup/Recovery Routines Configuration ...........................................123
Appendix A System Properties ................................................................................... 124
Appendix B IS-NMS Installation................................................................................ 127
Appendix C SNMP Service and Traps ....................................................................... 140
Appendix D Initialize IS-NMS Server ........................................................................ 144
Appendix E Terms and Abbreviations ...................................................................... 146

List of Figures
Figure 1: InterSKY System ................................................................................................................ 10
Figure 2: InterSKY™4M Hub Hierarchy .......................................................................................... 11
Figure 3: IS-NSM Browser Window ................................................................................................. 17
Figure 4: Menu Bar ............................................................................................................................ 18
Figure 5: About IS-NMS.................................................................................................................... 18
Figure 6: Administration Navigation Tree ......................................................................................... 20
Figure 7: Terminal Search Dialog ...................................................................................................... 21
Figure 8: Terminal Name Search Results .......................................................................................... 21
Figure 9: iRG ID Search Results........................................................................................................ 22
Figure 10: Network Navigation Tree ................................................................................................. 23
Figure 11: Remote Navigation Tree................................................................................................... 24
Figure 12: Add and Delete ................................................................................................................. 24
Figure 13: Central Monitoring ........................................................................................................... 25
Figure 14: Current Channel Information ........................................................................................... 26
Figure 15: Last Critical Event Bar ..................................................................................................... 26
Figure 16: Last Critical Event with Message ..................................................................................... 26
Figure 17: Events and Notifications................................................................................................... 27
Figure 18: Filter Dialog...................................................................................................................... 28
Figure 19: Extended Group Display .................................................................................................. 30
Figure 20: Not Extended Group Display ........................................................................................... 30
Figure 21: System Properties ............................................................................................................. 30
Figure 22: Network View with no Hubs ............................................................................................ 32
Figure 23: Network View with a New Hub ....................................................................................... 32
Figure 24: New Hub Dialog ............................................................................................................... 33
Figure 25: Add New NCC ................................................................................................................. 33
Figure 26: Network Hub .................................................................................................................... 34
Figure 27: Delete Dialog .................................................................................................................... 34
Figure 28: Inbound for a Specific Hub .............................................................................................. 35
Figure 29: Add New NCC device (new fields) .................................................................................. 36
Figure 30: NCC Configuration .......................................................................................................... 37
Figure 31: Expanded NCC Buttons Bar ............................................................................................. 38
Figure 32: NCC Satellite Configuration ............................................................................................ 39
Figure 33: Add New Satellite............................................................................................................. 39
Figure 34: NCC Bandwidth Configuration ........................................................................................ 40
Figure 35: Add New Bandwidth ........................................................................................................ 41
Figure 36: Delete Bandwidth ............................................................................................................. 41
Figure 37: Add New NCC Group Dialog .......................................................................................... 42
Figure 38: NCC Group Configuration ............................................................................................... 43
Figure 39: NCC Group Owner Details .............................................................................................. 45
Figure 40: Add New MCDC dialog ................................................................................................... 46
Figure 41: MCDC Configuration ....................................................................................................... 47
Figure 42: MCDC view of the MCDs and ARUs .............................................................................. 48
Figure 43: Outbound view for a Specific Hub ................................................................................... 49
Figure 44: Add New IPE Device ....................................................................................................... 50
Figure 45: IPE Configuration ............................................................................................................. 51
Figure 46: Add New OptimISe .......................................................................................................... 52
Figure 47: OptimISe Configuration ................................................................................................... 53
Figure 48: Add New Cisco Router ..................................................................................................... 54

Figure 49: Cisco Router Configuration .............................................................................................. 55

Figure 50: Remote Navigation Tree................................................................................................... 56
Figure 51: Four Terminal Tabs .......................................................................................................... 57
Figure 52: Terminal Configuration .................................................................................................... 58
Figure 53: Illegal iRG to SLA Profile Association ............................................................................ 60
Figure 54: Input Dialog ...................................................................................................................... 60
Figure 55: Terminal Status ................................................................................................................. 61
Figure 56: Terminal Switch Group .................................................................................................... 61
Figure 57: iRG Delete Prompt ........................................................................................................... 61
Figure 58: Tooltip, Illegal Values Display......................................................................................... 62
Figure 59: Terminal Cross Poll .......................................................................................................... 63
Figure 60: Drop&Insert ...................................................................................................................... 66
Figure 61: GSM Backhaul Profile Selection...................................................................................... 68
Figure 62: GSM Backhaul Profile Parameters ................................................................................... 69
Figure 63: Multiple Drop&Insert ....................................................................................................... 70
Figure 64: Multiple Drop&Insert Terminal Configuration ................................................................ 70
Figure 65: Migration .......................................................................................................................... 71
Figure 66: InterSKY Migration Complete ......................................................................................... 71
Figure 67: Terminal Owner Details Dialog ....................................................................................... 72
Figure 68: Choose the Upgrade Version ............................................................................................ 72
Figure 69: Terminal Status During Upgrade...................................................................................... 73
Figure 70: Multiple Versions Selection ............................................................................................. 73
Figure 71: Multiple Version Upgrade ................................................................................................ 74
Figure 72: Multiple Version Upgrade Version Choice ...................................................................... 74
Figure 73: Server Error on Upgrade Terminal ................................................................................... 75
Figure 74: Networking Configuration................................................................................................ 75
Figure 75: New Network LAN and PID Configuration..................................................................... 76
Figure 76: Advanced Acceleration Settings....................................................................................... 77
Figure 77: Mapping Entries ............................................................................................................... 78
Figure 78: Terminal Static Routes Expansion ................................................................................... 79
Figure 79: Terminal Permanent Routing Table ................................................................................. 80
Figure 80: QoS Status Usage Indicator .............................................................................................. 80
Figure 81: QoS Subnets, Services, and Applications......................................................................... 81
Figure 82: Subnet, Service, Application Distribution ........................................................................ 81
Figure 83: Add/Edit Subnet ............................................................................................................... 82
Figure 84: Add Service Level ............................................................................................................ 82
Figure 85: Add Application ............................................................................................................... 83
Figure 86: DSCP PHB View, Policy View, PHB Statistics, Queue Statistics ................................... 86
Figure 87: Add PHB Class ................................................................................................................. 88
Figure 88: Public and Private Networks ............................................................................................ 89
Figure 89: Static NAT ........................................................................................................................ 90
Figure 90: Dynamic NAT .................................................................................................................. 90
Figure 91: NAT Configuration .......................................................................................................... 92
Figure 92: Static NAT Table .............................................................................................................. 93
Figure 93: Add Entry to Static NAT Table ........................................................................................ 94
Figure 94: VLAN Configuration........................................................................................................ 95
Figure 95: RG Status (new fields)...................................................................................................... 96
Figure 96: Telnet Session Login ........................................................................................................ 98
Figure 97: Ping Screen ....................................................................................................................... 98
Figure 98: Outage Table Report......................................................................................................... 99

Figure 99: Outage Chart Report ....................................................................................................... 100

Figure 100: Throughput Chart Report ............................................................................................. 101
Figure 101: Save CSV Dialog .......................................................................................................... 102
Figure 102: Save JPEG Dialog ........................................................................................................ 103
Figure 103: Terminal Group Status Display .................................................................................... 105
Figure 104: Terminal Group Performance Display ......................................................................... 106
Figure 105: Terminal Group Outage Report .................................................................................... 107
Figure 106: Terminal Group Bandwidth Utilization Table ............................................................. 108
Figure 107: Terminal Group Bandwidth Utilization Chart .............................................................. 109
Figure 108: Group Throughput Summary Report............................................................................ 110
Figure 109: Export CSV Save Dialog .............................................................................................. 110
Figure 110: Administration View .................................................................................................... 112
Figure 111: Group Restriction Menu ............................................................................................... 114
Figure 112: Terminal Restriction Menu........................................................................................... 114
Figure 113: VNO Configuration ...................................................................................................... 115
Figure 114: Profiles .......................................................................................................................... 116
Figure 115: System Administration ................................................................................................. 116
Figure 116: Group Owner Remote Network.................................................................................... 118
Figure 117: Group Configuration, Group Owner ............................................................................ 118
Figure 118: Remote User ................................................................................................................. 119
Figure 119: New User Account ....................................................................................................... 120
Figure 120: Login Dialog ................................................................................................................. 121
Figure 121: Change Password Dialog .............................................................................................. 121
Figure 122: Change Password Dialog (2) ........................................................................................ 121
Figure 126: Install Wizard Welcome ............................................................................................... 129
Figure 127: Installation Setup .......................................................................................................... 129
Figure 128: Installation System Size Selection................................................................................ 130
Figure 129: Installation Window Services ....................................................................................... 130
Figure 130: MySQL Server Setup Welcome ................................................................................... 131
Figure 131: MySQL Setup Type ...................................................................................................... 131
Figure 132: MySQL Ready to Install ............................................................................................... 132
Figure 133: MySQL Installation Complete ..................................................................................... 132
Figure 134: MySQL Server Instance Configuration ........................................................................ 133
Figure 135: MySQL Configure Server ............................................................................................ 133
Figure 136: MySQL Multifunctional Database ............................................................................... 134
Figure 137: MySQL InnoDB Tablespace Settings .......................................................................... 134
Figure 138: MySQL Decision Support ............................................................................................ 135
Figure 139: MySQL Enable Network Options ................................................................................ 135
Figure 140: MySQL Enable Character Set ...................................................................................... 136
Figure 141: MySQL Enable Window Options ................................................................................ 136
Figure 142: MySQL Enable Security Options ................................................................................. 137
Figure 143: MySQL Ready to Execute ............................................................................................ 137
Figure 144: MySQL Installation Complete ..................................................................................... 138
Figure 145: SNMP Service Properties ............................................................................................. 140
Figure 146: SNMP Service Properties ............................................................................................. 141
Figure 147: SNMP Trap Service ...................................................................................................... 141
Figure 148: Configure Traps ............................................................................................................ 142
Figure 149: Enable Trap Messages .................................................................................................. 143
Figure 150: IS-NMS running as Windows Service ......................................................................... 144
Figure 151: IS-NMS Client Login ................................................................................................... 145


1. Elbit-Shiron InterSKY IS-NMS
The InterSKYTM system is a two-way IP over Satellite system that provides a cost-effective,
reliable, and immediately deployable solution for servicing broadband applications. It uses
satellites to divert transmissions to and from different destinations and over large territory,
bypassing the bottlenecks of the terrestrial infrastructure. NMS access is from a central hub
with a standard DVB-S/S2 forward link. Burst-Mode Frequency Division Multiple Access
(BM -FDMA) is from the remote locations to the central hubs.
Figure 1: InterSKY System
InterSKY complies with the DVB-S/S2 standard. The hub to Satellite link is rainproof based
on Automatic Uplink Power Control (AUPC). The Satellite to Remote Gateway link is
rainproof based on Adaptive Coding and Modulation (ACM). The manufacturer combined
AUPC and ACM into a proprietary, patented AUPC & AMC Controller (AAC) to provide
total rain-proofing for InterSKY versions 5.1 and higher. The Remote Gateway to hub is rain
proofed based on proprietary algorithms.
16 APSK and 32 APSK modulation for the return channel, Automatic Control Functions,
Bandwidth on Demand (BoD), Redundancy, and Quality of Service (QoS) are among some
of the special features inherent in the InterSKY v5.1 system.

Service providers and enterprises using InterSKY gain an additional value of a satellite-
based network by combining their 2-way services with point-to-multi-point transmissions.
The InterSKY system comprises a central hub and remote gateways. The hub houses all the
equipment required to transmit and receive IP data over satellite.
1.1 IS-NMS Environment

The InterSKY network management system, IS-NMS, can be accessed from a standard
browser (Internet Explorer). It can manage more than one network system. IS-NMS includes
a private database that can store information and business cards of system users. The IS-
NMS permits multiple simultaneous connections, allowing it to monitor the system from
different places.
Figure 2: InterSKY™ Hub Hierarchy
The IS-NMS provides the five conceptual areas of management as defined by the
International Organization for Standardization (ISO): performance, configuration,
accounting, fault detection, and security. IS-NMS provisions and monitors multiple
InterSKY systems, from hub to remote gateway, by polling network devices, graphical
presentations of network components and traffic, and a variety of reporting tools.
The IS-NMS facilitates alert reporting of recognized problems (for example, when one or
more user-determined thresholds are exceeded). Upon receiving these alerts, management
entities react by executing one, several, or a group of actions, including operator notification,
event logging, system shutdown, and automatic attempts at system repair.
Management entities poll agent-managed devices. The agents compile information about the
managed devices in which they reside, then store this information in a management
database, and finally provide it (proactively or reactively) to management entities (within IS-
NMS net) via the Simple Network Management Protocol (SNMP).
Performance Measures and allocates various aspects of network performance so that internet
Management work performance can be maintained at an acceptable level.
Performance management involves:
 Gathering status and performance data of network entities, including the
MCDC with ARU and MCD information, IPE, and terminals

 Managing device agent response to all poll requests

 Summarizing performance report of every remote gateway based on
historical data collected
 Monitoring connection status providing Eb/N0 of the signals received at the
hub and at each remote terminal
 Analyzing data to determine normal (baseline) levels
 Determining appropriate performance thresholds for each important
variable so that exceeding these thresholds indicates a network problem
worthy of attention
Management entities continually monitor performance variables. When a
performance threshold is exceeded, the device generates an alert and sends it to
the IS-NMS.
The IS-NMS provides comprehensive traffic monitoring and analysis tools for
efficient bandwidth usage, including:
 Percentage of BW usage per group
 CIR bandwidth usage
Information is presented in a table for intuitive and simple system analysis.
Configuration Monitors network and system configuration information to track and manage the
Management effects on network operation of various versions of hardware and software
elements.
Each network device has an associated InterSKY version and build number.
Configuration management subsystems store this information in a database for
easy access. When a problem occurs, this database can be searched for clues that
may help solve the problem.
The IS-NMS allows for the configuration and control of hubs and remote
gateways. Hub configuration and control options include:
 Configuration of managed device threshold limits, automatic and user-
initiated Satellite Link
 Forward Link Subsystem
 Return Link Subsystem
 Grouping
 Group data
 Bandwidth
 Users Configuration
 Remote gateway configuration and control options include:
 General information
 Contact information
 Equipment data
 Technical data
 Monitoring
Accounting Measures network utilization parameters so that users or groups can be regulated
Management appropriately. Regulation minimizes network problems and maximizes network
access across all users.
The IS-NMS supports five levels of system administration:
 User: is allowed to monitor its own remote gateway.
 Group Operator: same permissions as User; also allowed to monitor all
group components and remote gateways.
 Group Owner: same permissions as Group Operator; also allowed to
configure new remote gateways in the group.
 System Operator: same permissions as Group Owner; also allowed to
configure hub elements and remote gateways, not able to create new

accounts.
 Limited System Operator same permissions as System Operator without
the ability to perform multiple terminal upgrade and multiple Drop & Insert
tasks.
 Basic System Operator: same permissions as System Operator without the
ability to add and remove hub devices, and the ability to perform multiple
terminal upgrade and multiple Drop & Insert tasks.
 Administrator: allowed to define users, groups, and user access privileges
and to configure hub elements and remote gateways.
User administration provides Virtual Network Operation (VNO). Each Group
Owner can remotely manage his own hardware and the customers using the IS-
NMS.
Fault Detects, logs, notifies users of, and automatically fixes network problems (when
Management able) to keep the network running effectively. Fault management determines
symptoms, isolates the problem, fixes the problem, and tests the solution on all-
important subsystems. Finally, it records the detection and resolution of the
problem.
Security Controls access to network resources according to local rules so that the network
Management cannot be sabotaged (intentionally or unintentionally) and sensitive information
cannot be accessed by those without appropriate authorization. IS-NMS
monitors network resources users and can refuse access to invalid access codes.
Security management partitions network resources into authorized and
unauthorized areas for Users, Group Operators, Group Owners, System
Operators, and Administrators. For some users, access to any network resource
is inappropriate, mostly because such users are usually network outsiders. For
other (internal) network users, access to information originating from a
particular group is inappropriate.
1.2 Inbound and Outbound

The hub performs the functions of traffic routing, bandwidth assignments, transmission to
the satellite and network management.
1.2.1 Multi Channel Demodulator Controller

(MCDC)
The Multi Channel Demodulator Controller (MCDC) manages and controls the MCD units.
A single MCD Controller manages up to ten MCD units. IS-NMS supports MCDC
redundancy for the demodulator control.
Through the MCDC, IS-NMS receives information about all the MCDs and ARUs in the
system.
Multi-Channel Demodulator (MCD)

The Multi-Channel Demodulator (MCD), 19-inch one shelf rack mountable device, is based
on DSP embedded technologies and implements advanced signal processing algorithms.

 Input: an L-band signal from the Master splitter, with both QPSK and 8PSK modulation
supported.
 Output: either proprietary Adaptation Layer (SAL) cells, or DVB-RCS compliant ATM
Adaptation Layer 5 (AAL5) cells encapsulated in an IP packet. These packets are sent to
the ATM Reassembly Unit (ARU).
The MCD, the basis of bandwidth processing, processes a fixed amount of bandwidth
regardless of the number of carriers residing in this bandwidth. Each MCD processes all of
the signals received in a contiguous L-band segment. The specific frequency range is
configured by the MCDC according to values assigned in the NCC. The MCD processes
everything from a single 2 Mbps signal to over sixty smaller signals. The specific number of
channels depends on the data rates of the channels whose rates are assigned by the
bandwidth on demand algorithm of the NCC.
ATM Reassembly Unit (ARU)

The ATM Reassembly Unit (ARU) receives IP packet fragments, encapsulated in ATM
cells, from the MCD. The ARU reconstructs the original IP packet and sends it on to the IP
Forwarding unit. Each ARU supports up to 8Mbps traffic flow. Where redundancy is
required, a single redundant ARU provides hot-standby redundancy for multiple active
ARUs.
1.2.2 Network Control Center (NCC)

The Network Control Center (NCC), governed by the IS-NMS, maintains overall control for
one system. The NCC manages both the hub equipment and the Remote Gateways. It also
maintains the connectivity status and statistics of the remote gateways.
Data control function decisions in the RLSS are based on information received from the
MCDC and other components. In order to facilitate data control, the NCC oversees the
satellite, Remote Gateway bandwidth allocation, and the Remote Gateway parameter
database. Satellite, bandwidth, and Remote Gateway parameters are each configured
independently and stored in their respective databases. The NCC coordinates their operation
to maintain an optimal working system.
1.2.3 IP Encapsulator (IPE)

The IPE encapsulates IP data into DVB packets. The IPE links together the hub LAN and
the transmission equipment. The output format is a standard Digital Video Broadcasting
(DVB) MPEG2 Transport Stream (ETSI EN 301 192). The IPE links directly to a DVB
modulator or to an optional DVB MUX (multiplexer). The Standard InterSKY IPE is the
CME-5010 IPE.
1.2.4 OptimISe
The OptimISe GatewayTM and Server accelerate the performance of TCP/IP over satellite
links. Though OptimISe Gateways and Servers are usually described in their role of

improving performance in satellite networks, they frequently provide the same benefit to
wireless and long-delay terrestrial networks.
OptimISe Platform
The OptimISe Gateway is used on point-to-point links or as remote units on a hub-and-
spoke network.
Two types of OptimISe capability keys are available. The OptimISe link-rate capability key
determines the maximum link rate for OptimISe. The OptimISe Client capability key
determines the maximum number of supported OptimISe Clients supported. Upgrade keys
are available from Elbit-Shiron to support larger link rates or to support greater numbers of
OptimISe Clients.
OptimISe Performance
OptimISe devices use a unique connection-splitting and protocol-translation system that
improves the performance of TCP/IP over satellite links. The performance enhancement is
entirely transparent to end users with no software, proxy settings, or any other modifications
to the clients or servers. Any TCP connection between any two hosts, separated by a satellite
or other high latency link, can benefit from the use of OptimISe Gateways or Servers.
Web browsing, FTP, email, and other TCP-based applications that transfer substantial
amounts of data over a satellite link have dramatically improved performance with
OptimISe. However, some popular applications including video conferencing, Voice over
IP, and various multimedia applications are based on UDP. The OptimISe system efficiently
forwards UDP packets over the satellite link; only TCP connections receive OptimISe
processing.
1.2.5 Cisco Router

The IP Forwarding unit is a router that connects the receivers and the central LAN. The IP
Forwarding unit sends IP packets received from the ARU to their proper destination on the
RLSS, while routing the packets back to the central LAN on the FLSS. Typically, these units
are provided in a fully redundant, hot-standby configuration
The Cisco 2811 Integrated Services Router, the IP Forwarding unit, is part of the Cisco 2800
Integrated Services Router Series which complements the Integrated Services Router
Portfolio. The Cisco 2811 Integrated Services Router provides the following support:
 Wire-speed performance for concurrent services such as security and voice, and
advanced services to multiple T1/E1/xDSL WAN rates
 Enhanced investment protection through increased performance and modularity
 Increased density through High-Speed WAN Interface Card Slots (four)
 Enhanced Network Module Slot
 Support for over 90 existing and new modules
 Support for majority of existing AIMs, NMs, WICs, VWICs, and VICs
 Two Integrated 10/100 Fast Ethernet ports

 Optional Layer 2 switching support with Power over Ethernet (PoE) (as an option)
 Security
 Voice

IS-NMS Installation & Operation Manual IS-NMS Browser
2. IS-NMS Browser
The four functional areas of the IS-NMS browser provide entry to all the IS-NMS
capabilities:
 View Selection
 Menu Bar
 Navigation Tree
 Work Area
 Last Critical Events
Figure 3: IS-NSM Browser Window

2.1 View Selection

Remote and Network view selection effects the ability to configure, monitor, and display
managed elements in the system.
View the hub, including the NCC, the MCDC, the IPE, the Router, and the
OptimISe.
Display all the terminals in the system. The view must be Remote to add, modify,
or delete a terminal.
2.2 Menu Bar

The Menu bar is located at the top of the IS-NMS browser, directly under the browser
address window. Three functions are central to all IS-NMS operations: Help, Tools, and
Search.
Figure 4: Menu Bar
2.2.1 Help
Help displays the current IS-NMS system version and build. Click to display the IS-
NMS version and the client information (User Name and Profile).
Figure 5: About IS-NMS
The version and build numbers refer to the IS-NMS, not InterSKY. The user name is the
unique name given to the login account. The profile is the type of login account:
Administrator, System Operator, Group Owner, Group Operator, or User.

2.2.2 Tools
The Tools button, , is the entry point to IS-NMS administration and the SLA
Profile Scheduler (refer to the SLA Profile Scheduler Manual for more information).
IS-NMS Administration
IS-NMS security uses a user login session where the user enters a name and password. The
system then verifies the name and password, and sends the profile permissions to the IS-
NMS Client. The IS-NMS Administrator is responsible for configuring and encrypting the
database password.
IS-NMS limits the number of logins that can simultaneously connect to the system. The
number of permissible users is determined by the license agreement with the manufacturer
and can be changed by certified personnel only. Licenses can be allocated according to the
user role, such as, between admin, group owner, sys operator, and user. However, the total
number of logins cannot exceed the number of licenses. The default IS-NMS license is 5
concurrent users, one of which must be Admin.
Any number of licenses can be allocated, up to the maximum agreement. At times the
number distributed licenses can be less than the actual number of licenses. When this occurs,
the number of logins left, after the distributed licenses are accounted for, can be used by any
of the login types (admin, group owner, group viewer, sys owner, sys viewer, and user).
The maximum number of supported concurrent users (client connections) depends on the
type of server as follows:
 Small IS-NMS server – up to 30 concurrent users
 Medium IS-NMS server – up to 50 concurrent users
 Big IS-NMS server – up to 100 concurrent users
By default, security related activities are not mandatory. A default license key and encrypted
database password are saved during the installation process.
IS-NMS provides an Administration function to create and maintain seven types of
accounts:
 User: the most basic account, associated with one terminal; restricted to configuration
and view of the associated terminal, restricted to own account modification
 Group Operator: associated with more than one terminal, restricted to configuration
and view of group defined terminals, restricted to own account modification
 Group Owner: associated with more than one terminal, restricted to configuration and
view of group defined terminals, restricted to group account creation and modification
 Group Viewer: associated with more than one terminal, restricted to view of group
defined terminals
 System Operator: restricted to configuration and view of network components within
InterSKY
 Limited System Operator: has all the ability of the System operator without the
ability to perform multiple terminal upgrade and multiple Drop & Insert tasks.
 Basic System Operator: has all the ability of the System operator without the
ability to add and remove hub devices, and the ability to perform multiple terminal
upgrade and multiple Drop & Insert tasks.

 System Viewer: restricted to view of network components within InterSKY

 Administrator: all privileges, add, modify, delete users and groups
To view the Admin functions:
1. Click on the Menu bar.
2. Select Admin from the pull-down list. The Administration navigation tree opens on the
left and the user information displays in the work area.
Figure 6: Administration Navigation Tree
See Chapter ‎6 System Administration and VNO Support for information regarding system
accounts.
SLA Profile Scheduler

The SLA Profile Scheduler is a standalone server that is configured and monitored from the
NMS. The SLA profile manager provides a mechanism to schedule certain repeatable
service level agreement tasks. This is covered in the SLA Profile Scheduler Operations
Manual.
2.2.3 Search
Use the IS-NMS search feature to search for a terminal device and to qualify the search
according to the terminal name, terminal ID, group name, TX IP, LAN IP, and status.
Searching by terminal name conforms to Microsoft Windows use of ‗*‘ and ‗?‘ to search for
full or partial terminal names.

The procedure for searching for a terminal by Name is nearly identical to that of searching
by terminal ID. The only difference is the definition of the Search Filter criteria.
Figure 7: Terminal Search Dialog
To search by terminal Name:
1. Click in the upper left-hand corner of the Main window.

2. Select the terminal Name from the Look For: pull-down menu in the Filter criteria at the
top of the Configuration tab main view.
3. Click . The terminal Search Result window is displayed with the data ordered
according to the terminal name.
Figure 8: Terminal Name Search Results
Parameter Description
iRG Name Name associated with a specific terminal
iRG ID ID number associated with a specific terminal
Group Name Group to which the terminal belongs. The group is comprised of like-service
terminals
Tx IP IP address of the transmitter
LAN IP LAN IP address
Status Status of the terminal:
 Active: green, active and monitored
 Not Active: red, not active and monitored
 Upgrade: blue, upgrade in process
If the terminal answers to a SNMP ―get request‖: it sends from the IS-NMS-it‘s
Active, if not it sends Not Active
To search for a specific terminal by ID:

2. Select the terminal ID from the Look For: pull-down menu in the Filter criteria at the
top of the Configuration tab main view. The From and To fields are displayed.
3. Define a range of ID numbers to restrict the display for the desired results by entering
bounding conditions in the From and To fields.
To search for a single terminal ID, enter the terminal ID in the From: field. Leave the
To: field blank.
4. Click (to the right of the Filter criteria). The results display in the terminal Search
Result window according to the terminal ID.
Figure 9: iRG ID Search Results
To search by terminal Tx IP address:
2. Select the Tx IP from the Look For: pull-down menu in the Filter criteria at the top of
the Configuration tab main view. The From and To fields are displayed.
3. Define a range of Tx IP address to restrict the display for the desired results by entering
bounding conditions in the From and To fields.
4. Click (to the right of the Filter criteria). The terminal Search Results display
according to the Tx IP addresses.
To search by terminal LAN IP address:
2. Select LAN IP from the Look For: pull-down menu in the Filter criteria at the top of the
Configuration tab main view. The From and To fields are displayed.
3. Define a range of LAN IP address to restrict the display for the desired results by
entering bounding conditions in the From and To fields.
4. Click (to the right of the Filter criteria). The terminal Search Results display
according to the LAN IP addresses.

2.2.4 Log Out
appears in the upper right panel, next to and . Click to

end the current user session. The login dialog box is then displayed.
2.3 Navigation Tree

The network tree display depends on the View Selection, or .
2.3.1 Network View

The Network view displays all hubs, Inbound devices, and Outbound devices.
The System node is the root.

2nd level displays all the hubs.
3rd level, under each hub is an Inbound and an Outbound entry.
4th level, under Inbound, displays the NCCs and MCDCs.
5th level, under NCC, displays the terminal Groups.
4th level, under Outbound, displays the IPEs, Router, and
OptimISe.
Figure 10: Network Navigation Tree
2.3.2 Remote View

Remote displays all satellites, groups, and terminals.
The System node is the root.
2nd level displays all the configured satellites.
3rd level, under each satellite, displays all the configured
terminals.
4th level, under each terminal group, displays all the
configured terminal devices.

Figure 11: Remote Navigation Tree
2.3.3 Add and Delete
and from the Navigation View create and remove an element in the
network or remote topology.
Figure 12: Add and Delete
To add an element to the topology, click the element one hierarchy above the new element to
be added. For example, in a new system the only element is System. To add a new hub, first
click System, then . To add an inbound element, select the inbound element of the
hub and then click .
has two aspects: deleting an element with no dependencies and deleting an

element with dependencies. To delete an element such as a terminal, click the terminal for
deletion and then click . The terminal is deleted from the topology. However,
when an element has dependencies, such as a Satellite which has assigned groups and a hub
has assigned equipment and groups, you must first delete all dependencies before deleting
the element.
2.3.4 Common Functions

IS-NMS windows present various common buttons to acknowledge, accept, or reject
activities.
Button Description
Stop the current activity. IS-NMS may or may not return to the previous window
level. Any new information entered onto the window and not saved is lost.

Button Description
Redisplay the contents of the current window. IS-NMS gets the most updated
information from the IS-NMS server database. While the IS-NMS Client does
not poll the devices for current status, the IS-NMS server does poll the devices
according to a user configured time interval. It then stores the status information
in the IS-NMS server database. The data reflected after clicking Refresh is the
most current polled data.
Save any changes to the parameters.
Acknowledge and agree with the current state.
Yes/No Agree or disagree with the current query. These are mostly used to confirm
deletion or other activities from which there is no recovery.
Roll-Over When the cursor rolls over a parameter, IS-NMS displays the valid range.
Invalid When a parameter outside the permitted range is entered, the parameter name
parameter turns red. The Save button is disabled.
2.4 Central Monitoring

The main IS-NMS window is the monitoring window, which displays the NCC group status.
This window displays as the default start window.
Click the System root from either the Remote or Network view. This displays the satellites
and the associated groups.
You can also move the mouse over the group bars. A tool-tip pop-up window displays the
total number of terminals in a group, and the number of active, idle, inactive, upgrade, and
not monitored terminals associated with the group.
Figure 13: Central Monitoring
The IS-NMS displays the current Channel information for all groups of a given satellite
when Remote view is selected and the satellite is clicked.

Figure 14: Current Channel Information
2.5 Work Area

The work area changes according to the current system function. For example, when doing a
search on a terminal, the work area is populated with the search results. In the figure above
the work area is filled with the satellites and groups in the system.
2.6 Last Critical Events

Critical events are displayed or hidden using the Last Critical Events expander at the bottom
of the IS-NMS main window. When an alarm is raised the most recent event message
displays in the Last Critical Events bar.
Figure 15: Last Critical Event Bar
Figure 16: Last Critical Event with Message
The Last Critical Events:

 Displays logged events
 Filters logged events, including Sort and Page functions
 Acknowledges logged events
Click Last Critical Events to display the Events and Notifications view. The display is
resizable via the mouse point-and-drag function.

Figure 17: Events and Notifications
Sorting of events is performed by clicking on the column header. Click the column header
once to sort in ascending order; click again to sort in descending order.
Five navigation buttons appear at the bottom of the display:
Button Description
Page backward through the event records. Each page holds 1,000 event records.
When moving to the previous page, another 1,000 event records are retrieved
from the IS-NMS server.
Page forward through the event records. Each page holds 1,000 event records.
When moving to the next page, another 1,000 event records are retrieved from
the IS-NMS server.
Acknowledgement of events is performed by selecting one or more event
records and clicking . The Ack. column is checked; the Ack. Details
column populates with the user name and time of operation.
By selecting one or more acknowledged events and clicking , the
acknowledge data for the selected events is removed from the table.
User defined filter.
2.6.1 Filtering InterSKY Events

The Last Critical Events feature provides a filtering mechanism that allows the user to define
complex filtering criteria.
To perform a complex filtering of critical events:
1. Click (at the bottom of the Last Critical Events table). The Filter dialog
opens.

Figure 18: Filter Dialog
Event ID Checked: Display only the events filtered by the selection menu to the
right. Enter the key Event ID in the field to the right of the
filter.
Unchecked: Don‘t use Event ID as a filter.
Severity Checked: Display only the events that meet the Severity filter.
Unchecked: Don‘t use Severity as a filter.
Ack Status Checked: Use the Ack, UnACK selection as the filter.
Unchecked: Don‘t use Ack Status as a filter.
Event Type Checked: Display only the event types filtered by the selection menu to
the right.
Unchecked: Don‘t use Event Type as a filter.
Source Path Checked: Filter according to the pull-down menu to the right and the
keyword entered in the field.
Unchecked: Don‘t use Source Path as a filter.
Select/Deselect Checked: Select or Deselect (toggle) all events.
All Unchecked: Don‘t change the event select status.
Audio/Visual Checked: Display the last event message in the Last Critical Alarm bar
Indication and sound an alarm when an event happens.
Unchecked: Don‘t display the event message in the Last Critical Alarm
bar and don‘t sound an alarm when an event happens.
2. Define the desired filter. Use the logical ‗AND‘ between the marked fields.
3. Click . IS-NMS selects the events to display according to the complex filter.
The results appear in the Last Critical Events table.
2.6.2 Event Log and Audit Enhancement

In IS-NMS v2.26 a set of messages has been added to the events log and audit table to
provide a better monitoring of user activities. Only Administrator users can see user
activities. The operations that added are:
 Login

 Remove Hub
 Add NCC
 Remove NCC
 Add MCDC
 Remove MCDC
 Add IPE
 Remove IPE
 Add Group
 Remove Group
 Add Satellite
 Remove Satellite
 Add Bandwidth
 Remove Bandwidth
 Add terminal
 Remove terminal
 Change terminal Min Eb/N0
 Change terminal Max Eb/N0
 Change terminal Min Power Level
 Change terminal Max Power Level
 Upgrade terminal
 Cancel Upgrade terminal
 X-Poll Start
 X-Poll Stop
 Drop & Insert operation
 Multiple Upgrade
 Multiple Drop & Insert
 Logout
2.7 Extended Group Display

Two group display options are available for the Navigation Tree.
 Not Extended: displays the groups in the Navigation tree with the Group icon, Group
name, and the number of terminals in the group.
 Extended (default): displays the groups in the Navigation tree with the Group icon,
Group name, and the number of monitored terminals in the group / the number of
terminal in the group.

Figure 19: Extended Group Display Figure 20: Not Extended Group Display
To configure the Extended Group Display:
1. Open C:\Program Files\ShironNMS\system.properties in a text editor.

(―C:\Program Files\...‖ is the default. However this might have been changed by the
administrator.)
Figure 21: System Properties
2. Change the extendedGroupBar to true.

3. Save the file and close.

IS-NMS Installation & Operation Manual Network InterSKY Hub
3. Network InterSKY Hub
IS-NMS supports a hierarchical view of the entire local network, including all components:
 InterSKY Hub view
 Inbound for specific hub
 NCC for specific inbound
 MCDC for specific inbound
 Outbound for specific hub
 IPE for specific outbound
 Router for specific outbound
 OptimISe for specific outbound
IS-NMS supports multiple hubs, but each hub has only one inbound and one outbound.
Inbound and outbound support multiple devices.
The first time the InterSKY system starts, there are no hubs. Only the root System is
displayed.

Figure 22: Network View with no Hubs
When a hub is created, inbound and outbound sub-branches are created automatically. When
clicking on a hub, you see the inbound and outbound frames of the hub.
Figure 23: Network View with a New Hub
3.1 InterSKY Hub Creation

The hub must be added before configuring the NCC, the MCDC, or the IPE. A new hub is
saved only after a new NCC is added under it. If no new device is added and the client is
closed or the Network View is closed, the new hub is not saved and it disappears.

To add a new hub:
1. On the tree, select the System.

2. Click (located on the bottom of the tree view). The New hub dialog opens.
Figure 24: New Hub Dialog
3. Enter the new hub name.
4. Click . The new hub appears in the Navigation Tree. If you close the Network
View before adding content (NCC or IPE), the hub is erased.
5. Click Inbound under the new hub.
6. Click . The Add new device dialog opens. The device type defaults to NCC.
Figure 25: Add New NCC
7. Enter a name for the NCC and click . You don‘t have to configure anything at
this moment. This device is only to insure that the hub is completely created.
3.2 Hub Display

All inbound and outbound devices are displayed under a specific hub node.
To display a selected hub:
1. Select .
2. From the local network tree, click the specific hub node for display. The hub view
appears in the working area.

Figure 26: Network Hub
Inbound/Outbound View
Label Device name
Status Status of the device
 Green: Active, connected
 Yellow: Slave, redundant, connected
 Red: Not Active, disconnected
IP Address IP address of the device
3.3 Hub Deletion

A hub can be deleted from the system at any time. When there are elements associated with
the hub, the elements must first be deleted.
To remove a hub from the IS-NMS topology:
1. On the Network tree, select a specific hub.

2. Click (located on the bottom of the tree view).
Figure 27: Delete Dialog
3. Click . The hub is removed from the topology. When there are elements associated
with the hub, either inbound or outbound, the elements must first be deleted.

3.4 Inbound
IS-NMS allows you to display inbound devices (only) for a specific hub node.
To display the Inbound View for a hub:
1. Select ; click the specific hub node for display. The hub view appears in the
working area (to the right of the network tree).
2. Click the specific inbound node for display. The inbound view appears in the working
area.
Figure 28: Inbound for a Specific Hub
Label Device name (30 character maximum)
3.4.1 NCC
The NCC is responsible for data control functions in the system. It is the focal point for
making decisions in the system, based on information received from other system
components.
The NCC oversees two primary areas of information:
 Remote Gateways: the NCC incorporates a database that includes parameters for
authorized Remote Gateways.
 Bandwidth: the NCC controls the allocation of all channels used by the Remote
Gateways to communicate with the hub and satellites.

The device Configuration tab displays the NCC IP address and billing information. You can
view and configure the connection information for the specific NCC device.
NCC Device Configuration

To add a new NCC:
1. Under the hub, click Inbound.

2. Click . The Add new device dialog opens. The device type defaults to NCC.
Figure 29: Add New NCC device (new fields)
Parameter Description Valid Ranges

Name Device Name in IS-NMS Free format text;
(Non-configurable and Mandatory) maximum 30
characters
IP Address Device IP address for IS-NMS Legal IP address
communications.
(Non-configurable and Mandatory)
Public community Read Only SNMP community name Free format text
(Non-configurable and Mandatory) Default: Public
Private community Read & Write SNMP community name Free format text
(Non-configurable and Mandatory) Default: Public
Type IS-NMS identified device Type NCC

(Non-configurable and Mandatory)
Next Hop IP address for the next hop Legal IP address
User Name Operator user name Free format text
Password Password that accompanies the user name Free format text
3. Enter the device name and IP address. Configure the SNMP communities. Verify that
the Type is NCC.
4. Enter the Next Hop address, valid user name and password.

5. Click . The new device is added to the topology and appears in the Navigation
Tree.
To modify NCC configuration parameters:
1. Click the specific NCC for display. The NCC device view appears in the working area
with the Configuration Tab displayed.
2. The first time this NCC is displayed, the group view (under the device in the Navigation
window) is contracted.
 : view contracted. The associated groups are hidden. Click to expand the NCC.
 : view expanded. The associated groups are visible. Click to contract the NCC
view.
Figure 30: NCC Configuration

General
NCC IP Address The Device IP address as entered in the Add not editable
session.
Version Version of the NCC and the specific build not editable
Connection Information
Billing Server Port Radius server port (optional) 1024–65534
Billing Mode Enable/Disable the InterSKY Radius interface ON–OFF
(optional)
Billing Server IP Radius server port (optional) Legal IP
address


Billing Client IP InterSKY's Radius assigned address (optional) Legal IP
address
Billing Secret Radius authentication string (optional) Free format
text
Buttons
Restart Restart the NCC device according to the
SNMP protocol.
Figure 31: Expanded NCC Buttons Bar
3. To open the Configuration tab button par, click . To close it, click .
4. Enter the updated parameters.
5. Click . The updated NCC configuration parameters are saved to the
management database.
To delete an NCC:
1. Delete any groups associated with the NCC for deletion.

2. Click the NCC to be deleted.
3. Click . Confirm in the delete confirmation dialog box that you want to delete
the selected NCC.
NCC Satellite Configuration

The InterSKY system supports a multi-satellite feature. This feature enables the management
of multiple bandwidth segments from multiple transponders/satellites in a single system. The
auto-calibration feature system demands the linkage of bandwidth groups to satellite. A
remote gateway belonging to satellite X can only be calibrated on the bandwidth of satellite
X.
The InterSKY system treats different transponders on the same satellite as different
satellites.
The Satellite Database contains parameters for each configured satellite in the InterSKY
system. You can add, delete, and modify satellites from this tab.

Figure 32: NCC Satellite Configuration

ID Internal database index for the satellite. This Positive number (not
parameter is automatically set by the hub. editable)
Satellite Name The name of the satellite; used mainly for display Free format text (30
purposes. characters maximum)
Transponder Specifies the transponder number. Mainly used to Positive number (30
differentiate between different transponders on the digits maximum)
same satellite (same satellite name).
To add a satellite:
1. In the Network tree, select the active NCC. Open the Satellite Configuration tab.
2. Click Add Sat. in the button bar. The Add Satellite dialog opens.
Figure 33: Add New Satellite
3. Enter the name of the satellite and the transponder ID from the Satellite provider.
4. Click to accept the satellite parameters.
To modify the satellite parameters:
2. Select the Satellite to be updated in the right pane and click Modify.

3. Enter any user-configurable parameter.

4. Click . The updated parameters are saved to the Satellite Database.
To delete a satellite:
1. Remove any bandwidth allocation for this satellite.

3. Select the Satellite to be deleted and click Remove Sat.
4. Click . Confirm in the delete confirmation dialog box that you want to delete
the selected satellite.
NCC Bandwidth Configuration

The RLSS frequencies are controlled and managed by the hub. It does not control the DVB
(outbound) frequencies. The inbound and outbound frequencies can be on different
transponders or even different satellites.
Frequencies for use in the system are received from the satellite operator when Bandwidth is
purchased.
The system supports the following bandwidth features:
 Non-contiguous bandwidth
 Online bandwidth changes after initial system setup (if all the required bandwidth is not
purchased at system setup)
The IS-NMS Bandwidth Configuration tab displays information for the segments of satellite
bandwidths that are available for use in the InterSKY system for return channels. This
information is used to generate all channels in the system.
The hub automatically concatenates frequencies into a single group. For example, suppose
the initial system‘s allocated frequencies were 1250 to 1253 MHz, and the operator added
frequencies 1253 to 1254. This would appear as one continuous frequency band as opposed
to two frequency groups.
Figure 34: NCC Bandwidth Configuration


Start Frequency: Starting frequency for the inbound signal 950–1525
bandwidth in MHz (configured in Add Freq.
window)
Stop Frequency: Ending frequency for the inbound signal bandwidth 950–1525
in MHz (configured in Add Freq. window)
Total Stop Frequency – Start Frequency 950–1525
Group: Logical gathering of terminals with the same RLSS Free format text (30
characteristics. (configured in Add Freq. window) characters maximum)
To add a bandwidth:
2. Click Add Freq. in the button bar. The Add new bandwidth dialog opens.
Figure 35: Add New Bandwidth
3. Enter the Start and Stop frequency.

4. Select the Group with which to associate this bandwidth slice.
5. Click to add the bandwidth. The parameters are saved to the Bandwidth
Database.
To delete bandwidth:
1. In the Network tree, select the active NCC. Open the Bandwidth Configuration tab.
2. Select the Bandwidth to be deleted and click .
Figure 36: Delete Bandwidth

3. Confirm that you want to delete this bandwidth or click to cancel the delete.
3.4.2 NCC Groups

The NCC grouping feature allows the system owner to partition the return channel
bandwidth among groups of terminals. The system owner can guarantee bandwidth for a
group of terminals, independent of the bandwidth demands of terminals outside this group.
Conceptually, the feature allocates CIR for a number of Remote Gateways.
To add a new NCC Group:
1. Under the selection hub, click Active NCC.

2. Click . The Add new device dialog opens.
Figure 37: Add New NCC Group Dialog

Name Group Name in IS-NMS (mandatory) Free format text (30
characters max)
IP Address Not relevant Not relevant
Public community Not relevant Not relevant
Private community Not relevant Not relevant
Type IS-NMS Type (mandatory) NCC Group
3. Enter the NCC group name.

4. Select NCC Group from the Type list of options.
5. Click . The new NCC Group is added to the Navigation Tree. The NCC Group
Configuration window is displayed.

Figure 38: NCC Group Configuration

Group ID The ID of the Group. The Group ID is Positive number
automatically set by the NCC and
cannot be manually modified.
Group Name Name of the NCC group. Free format text (30 characters
max)
Satellite Name of the satellite that this Group is Any satellite in the satellite
allocated to (mandatory). dropdown list
Description Description of the Group (optional). 30 character free format text
Rx Type The Group Type, which is either FDMA
FDMA or BM-FDMA. Every BM- BM-FDMA
FDMA Group must be assigned to a
specific MCDC (Multi-Channel
Demodulator Controller) using the
pull-down list (mandatory).
This is enabled for a new group only.
MCDC Name Group assigned MCDC (mandatory– Any MCDC in the MCDC list
BM-FDMA only) pull-down list.
MCD Type Group MCD type pull-down list: 1M, 1M, 2M, or 0.5M
2M, or 0.5M.
Adaptation layer Adaptation layer pull-down menu to SAL
configure the Group (mandatory –
BM-FDMA only).
Modulation The modulation to use for the Group QPSK, 8PSK
pull-down list (mandatory – BM-
FDMA only).
Frequency Offset RG actual frequency Offset -[2000] MHz – 2000 MHz
Restrictions How the MCDC is to be restricted Unlimited,
(pull-down list). An unlimited number 4 terminals, 8 terminals,
of terminals, 4 terminals, or 8
Calibration
terminals can be configured.
Calibration groups defined in the NCC
must be configured here.


Notification Group specific, notification of RG A percentage of the actual
Threshold disconnect happens when the number number of terminals in a group
of disconnected RGs is greater than the
% entered here. This can be defined
and updated per group.
Error Correction Controls errors in data transmission Turbo: used extensively in 3G
over unreliable or noisy and 4G mobile telephony
communication channels. Turbo and standards
LDPC can provide almost optimal LDPC: linear error correcting
efficiency. code, a method of transmitting a
message over a noisy
transmission channel
IB-ACM Inbound ACM (Adaptive Coding and When checked, the system uses
Modulation) ACM
Access Channel
Data Rate The mandatory Group data rate (pull- Data rate set depends on chosen
down list). Modulation and FEC
FEC Mandatory, modulation dependent ¼ (QPSK), 1/2, 3/4, 2/3, 8/9
Forward Error Correction schemes FEC,
(pull-down list). depends on chosen Modulation
Spacing Frequency difference between adjacent 22%–35%
channels (mandatory).
User Channel The spacing used for all User (or 22%–35%
Spacing traffic) channels generated within the
Group. (mandatory)
Clear Channel The spacing used for all clear channels 22%–35%
Spacing generated within the Group
(mandatory).
# of Channels Number of channels in Group 2-20
(mandatory).
Polling Interval Parameters
Performance Number of minutes between terminal 1–30 min
polling of terminal parameters (1
minute minimum)
Static Valid only when Automatic Polling is 1–24 hours
checked. This parameter governs how
frequently the IP addresses, PIDs,
QoS, Static Route, and acceleration are
polled.
Automatic Polling To better manage the system load, the  Checked, (automatic
terminal can be polled either polling): IS-NMS polls the
automatically with a configurable time terminal parameters
span or manually using the refresh according to Performance
capability. (above).
Refresh polls the device for the current  Not checked, (manual
information. refresh): the IP addresses,
PIDs, QoS, Static Route, and
acceleration parameters are
polled by request by clicking
the refresh buttons.

6. Click located near the middle of the screen. The NCC group
owner details window is displayed.
Figure 39: NCC Group Owner Details
7. Enter a Phone, E-Mail, and Address for the new NCC Group. Click .
8. Click (on the NCC Group configuration tab).
To modify an NCC Group:
1. Under the selection hub, click Inbound. Click the NCC Group. The NCC Group
configuration window is displayed.
2. Enter the parameter changes. To reject the new parameters, click Refresh. The window
redisplays with the saved parameters. To save the parameters, click .
To delete an NCC Group:
1. Remove all the elements (bandwidth/terminals) associated with the NCC group.
2. In the Network tree, select the active NCC Group.
3. Click . The NCC group is deleted from the topology.
3.4.3 MCDC
The Multi Channel Demodulator Controller (MCDC) provides the management and control
for the MCD and ARU units. Typically, the MCDC units come as a pair; this provides hot-
standby redundancy for the demodulator control.
The MCDC is an extension of the NCC that is used to configure MCDs and collect
monitoring information. The current deployment can be understood as follows:
 The InterSKY system implements bandwidth demodulation via the Multi-Channel
Demodulator (MCD). The MCD is a bandwidth demodulator. It can demodulate a
number of channels over a specific bandwidth segment.
 The MCDC Database contains parameters for each MCDC in the InterSKY system.
Parameters for a MCDC must be defined before the NCC can recognize the MCDC in
the system. The MCDC Parameters dialog box is used to specify MCDC attributes.

To add a new MCDC:
1. Click Inbound under the selection hub,

2. Click . The Add new device dialog opens.
Figure 40: Add New MCDC dialog

Name MCDC Name in IS-NMS (mandatory) Free format text (30
characters max)
communications. (mandatory)
Public community (Non- Read Only SNMP community name Free format text
configurable and Default: public
Mandatory)
(mandatory) Default: public
Type IS-NMS identified device Type MCDC
(mandatory); pull-down list
3. Enter the MCDC name. Enter the IP address, public and private community settings.
4. Select MCDC from the Type list of options.
5. Click . The new MCDC is added to the Navigation Tree.

To modify an MCDC:
Figure 41: MCDC Configuration

MCDC IP Address Device IP address for IS-NMS communications Not editable
Version MCDC version and build Not editable
FTP Server MCDC dedicated IP address for MCD upgrades Legal IP address
(optional)
User Name FTP User name for MCD upgrades (optional) Free format text
Password FTP password for MCD upgrades (optional) Free format text
1. Click Inbound under the selection hub. Click the MCDC. The MCDC configuration
window is displayed.
2. Enter the new device parameters. Click .
To delete an MCDC:
1. In the Network tree, select the MCDC.
2. Click . In the confirmation window, click to delete or No to cancel the

delete.
MCD and ARU Devices

The MCDC Devices tab displays a list of MCD and ARU devices as polled from the MCDC.
The upper part of the screen shows MCD devices; the lower part of the screen shows ARU
devices. This screen is view only.

Figure 42: MCDC view of the MCDs and ARUs
MCD MCD ID ID number of the MCD (from polling)
Label Label on the MCD
SW Version Software version and build number
MCD Type MCD Type 1 through 6, MCD 4G, MCD 4G-R
Status Active, Available, Not Found
Freq. Frequency
BW Bandwidth
Channel Channel
Modul. Modulation
Restrictions 4 or 8 terminals, or unlimited
ARU ARU ID ID number of the ARU (from polling)
SW Version Software and build number
Mode SAL
Status Accepted, Active, Not Found
3.5 Outbound
Configuration of the outbound devices for the hub is initiated by selecting the outbound
node from the Network tree.
IS-NMS allows you to display detailed information for a specific outbound node on the local
network tree.

To display an outbound node:
1. Select . Click the specific hub node for display. The hub view appears in the
working area (to the right of the network tree).
2. Click the specific outbound node for display. The outbound view appears in the working
area.
Figure 43: Outbound view for a Specific Hub
Parameter Device name

Label
3.5.1 IP Encapsulator
The IP Encapsulator (IPE) encapsulates IP data into DVB packets. The IPE is an essential
link between the hub LAN and the transmission equipment. The output format is a standard
Digital Video Broadcasting (DVB) MPEG2 Transport Stream (ETSI EN 301 192). The IPE
links directly to a DVB modulator or to an optional DVB MUX (multiplexer).
IS-NMS allows you to display detailed information for a specific IPE device on the local
network tree. These are selected from the IPE Type field at the top of the Configuration
view.
Note: Adding rows manually to the IPE might cause overrides and lead to
mismatching with the IS-NMS database.
The IS-NMS supports the CMR-5000 and Mencap versions 1.5.6, 1.7.1, and 1.7.3. The
Standard InterSKY IPE is the CME-5010 IPE.

To add a new IPE:
1. Select the Outbound node on the Network tree.

2. Click . The Add New Device dialog opens.
Figure 44: Add New IPE Device

Name IPE Name in IS-NMS (mandatory) Free format text (30
characters max)
(mandatory)
(mandatory)
Type IS-NMS identified device Type (mandatory) CME-5010
The Standard InterSKY IPE is the CME- CMR-8500
5010 IPE.
3. Enter the IPE name, IP address, public and private community. The CME-5010 IPE and
the CMR-8500 support ACM capabilities.
4. Click . The new IPE device is added to the Network Navigation Tree.
To modify an IPE:
1. Click Inbound under the selection hub. Click the IPE. The IPE configuration window is
displayed.

Figure 45: IPE Configuration

IPE Type Type of IPE (non-editable) CME-5010
CMR-8500
IPE IP Address Device IP address for IS-NMS communications Legal IP address
( non-editable)
Poll Interval Interval of to time poll the device 60–900 seconds
To delete an IPE:
1. In the Network tree, select the IPE. Click .

2. Confirm the deletion or cancel.
3.5.2 OptimISe
<>
To benefit from the OptimISe Gateways to your network topology, the topology must
consist of two or more networks that are connected by a satellite link or other link with long
latency, high error rates, or highly asymmetric bandwidth. You may have two sites, or
several. The network may be as small as two PCs or as big as an ISP supporting thousands
of users. The OptimISe Gateway can be installed in point-to-point, point-to-multipoint,
multipoint-to-point, and full mesh networks.
One OptimISe Gateway needs to be installed for each hub. At each site, there is a 10BaseT
or 100BaseT LAN, connected to a satellite modem through a router. The OptimISe Gateway
simply plugs into the LAN at each site, preferably between the router connected to the
satellite modem and the rest of the LAN. The network topology must consist of a hub site
with a broadcast satellite transmitter, and multiple remote terminals each having a PC
equipped to receive data over a satellite link. The OptimISe Server system does not require
any particular satellite hardware. A functioning IP satellite system, broadcasting successfully
to PCs while running one of the supported operating systems, is able to add an OptimISe
Server and an OptimISe Client software to the network.

At the hub site, there must be an Ethernet LAN connected to a satellite modem through a
router. The server or gateway plugs into the LAN at the hub site, preferably between the
router connected to the satellite modem and the rest of the LAN.
At each remote site, there must be a PC equipped to receive data over a satellite link,
running one of the supported operating systems, which is already successfully configured for
Internet access through the hub site. Traffic inbound to each remote PC will normally
To add a new OptimISe:

Figure 46: Add New OptimISe

Name OptimISe-r Name in IS-NMS (mandatory) Free format text (30
characters max)
(mandatory)
(mandatory)
Type IS-NMS identified device Type (mandatory). OptimISe-R
3. Enter the OptimISe name, IP address, public and private community.

4. Click . The new IPE device is added to the Network Navigation Tree.

To modify an OptimISe-R:
1. Click Inbound under the selection hub. Click the OptimISe. The OptimISe
Figure 47: OptimISe Configuration

IPE Type Type of OptimISe (non-editable) OptimISe
( non-editable)
To delete an OptimISe-R:
1. In the Network tree, select the OptimISe. Click .

3.5.3 Cisco Router

The IP Forwarding unit, the Cisco 2811 router, provides a scalable, secure, manageable
remote access server that meets FIPS 140-2 Level 2 requirements.
To add a new Cisco Router:


Figure 48: Add New Cisco Router

Name Cisco Router Name in IS-NMS (mandatory) Free format text (30
characters max)
(mandatory)
(mandatory)
Type IS-NMS identified device Type (mandatory) CISCO 2811
The Standard InterSKY Cisco Router is the
CISCO 2811.
3. Enter the Cisco Router name, IP address, public and private community. The CISCO
2811 supports ACM capabilities.
4. Click . The new Cisco Router device is added to the Network Navigation
Tree.
To modify a Cisco Router:
1. Click Inbound under the selection hub. Click the Cisco Router. The Cisco Router

Figure 49: Cisco Router Configuration

IPE Type Type of Cisco Router (non-editable) Cisco Router
( non-editable)
To delete a Cisco Router:
1. In the Network tree, select the Cisco Router. Click .


IS-NMS Installation & Operation Manual InterSKY Remote Gateway
4. InterSKY Remote Gateway
InterSKY offers a complete range of remote gateways for delivering high-quality two-way
IP satellite broadband services. These remote gateways combine VSAT and IP devices, with
separate inbound and outbound connections to the hub.
Figure 50: Remote Navigation Tree
The Remote view is displayed by clicking on the main window. The tree changes
to present all the configured terminal devices in groups. The network structure is fixed:
 The System node is the root.
 The second level displays a list of configured satellites.
 Under each satellite, all the configured terminal groups are presented (third level).
 Under each group, all the configured terminal devices are presented (fourth level).
The terminal device node is color-coded by terminal device connection status and according
to the configured monitor state:
 Green: terminal device is connected and monitored
 Red: terminal device is not connected
 Blue: terminal device is in an upgrade process
To open terminal Device view, click a specific terminal device node on the Remote tree.
Three or four tabs appear across the top of the configuration window, depending on the
InterSKY version.

Figure 51: Four Terminal Tabs
 Terminal Status
 Terminal Configuration
 Terminal Network
 Terminal Performance
In addition, the tool bar displays the terminal name (and IP address), the terminal group
name and the terminal status (Active, Disconnected, Not Monitored, Idle, In Upgrade).
4.1 Terminal Configuration

From the Remote view, configuration tab, you can:
 Add a new terminal device by selecting a specific terminal group node and clicking
.
 Edit an existing terminal.
 Delete an existing terminal device by selecting a specific terminal device node and
clicking .
 Upgrade a terminal device by selecting a specific terminal device node and clicking
Upgrade.
 Perform Cross-Poll by selecting a specific terminal device node and clicking X-Poll.
 Drop&Insert a terminal by selecting a specific terminal device node and clicking
Drop&Insert.
 Enter and maintain Owner Details by selecting a specific terminal device node and
clicking Owner Details.
 Associate an existing terminal to an SLA profile.

Figure 52: Terminal Configuration
Parameter Description Value

RG ID terminal unique ID (not editable) 4-6 digits number
RG Name terminal identified name in IS-NMS. This field is Read-only
read-only. The IS-NMS automatically uses the LAN
address to create the name. After the terminal
connects, the IS-NMS polls the terminal LAN
address (because it became Active from Not Active)
and changes the name according to the LAN address.
Group Associated group (mandatory) Any valid group for the
Use this pull-down menu to switch between groups specific terminal
at any time on the terminal Configuration window.
SW version Terminal Software version (not editable) SW version drop list
RG Type Type of terminal (not editable) MSR
MSR-R
MSR-Pro
RG DVB MAC address of terminal Rx interface (not editable) Configured according to
MAC the terminal ID


Eb/N0 Exact level depends on system‘s Link Budget. 2.8 – 12 dB
Normally there is 1 dB difference between Min and
Max.
Min: the minimum Eb/N0 value required for Remote
Gateway connection
Max: the maximum Eb/N0 value required for
Remote Gateway connection
LDPC Recommended Range:
 QPSK 1/4: 2.8-3.8 dB
 QPSK 3/4: 4.5 – 5.5 dB
 QPSK 2/3: 6.5 – 7.5 dB
 8PSK 8/9: 9.7 – 10.7 dB
Turbo Recommended Range:
 QPSK 3/4: 5.5 – 6.5 dB
 QPSK 2/3: 8.5 – 9.5 dB
 8PSK 8/9: 11 – 12 dB
Tx Power The min/max power level of the Remote Gateway  MSR-R, MSR-Pro:
Level transmitter. This parameter is set by the auto [-45] – [-2.5] dB
calibration process and is conveyed to the Remote
Gateway. When manual calibration is used, the NCC
operator is responsible to set the value according to
the result of the manual calibration process.
(mandatory)
Frequency Min: the minimum absolute value from which 0–30 Hz
Offset frequency corrections are performed Recommended Range:
Max: the maximum allowed dynamic frequency  FDMA: 1-6 KHz
offset for the Remote Gateway; this
 BM-FDMA: 0.3-6 KHz
parameter is conveyed to the Remote
Gateway. (mandatory)
AGC Min: the minimum AGC level of the demodulator BM-FDMA: [-25] – [0] dB
assigned to the terminal FDMA: [-25] – [-5] dB
Max: the maximum AGC level of the
demodulator assigned to the terminal
IB ACM Inbound ACM (Adaptive Coding and Modulation) When checked, the system
uses ACM
FEC Forward Error Correction algorithm for the terminal LDPC
transmitter. This is qualified by the Group and is  QPSK: 1/4, 3/4
modulation dependent.
 8PSK: 2/3, 8/9
Turbo
 QPSK: 3/4, 2/3
 8PSK: 8/9
Licensed Max UC: Maximum User channel rate in kbps taken from the terminal
DR CC: Maximum Clear channel rate in kbps
Max Link The maximum link budget of the Remote Gateway Data rate set dependent
Budget (mandatory)


SLA Profile Pull-down menu from which an SLA profile can be Only limited to the number
attached to this terminal configuration. of profiles configured in
When the Allot device is not configured for the the system
selected terminal, this field is disabled.
Priority terminal priority (pull-down list) Deferred BoD: Deferred, Low, Medium,
Low, Medium, High, CC: Clear Channel High, CC user
Min IR Minimum terminal data rate (pull-down list)
CIR Committed Information Rate for this Remote Data rate set dependent
Gateway (mandatory)
PIR Preferred terminal data rate (pull-down list)
Note: When an Allot device is not configured to the terminal in question, the
terminal cannot be attached to the related SLA profile. When adding a
terminal or set of terminals to the SLA profile using the Tools→SLA
Profiles tool, the Select terminal tasks responds with the following:
Figure 53: Illegal iRG to SLA Profile Association
To add a terminal:
1. From the Remote tree, select a terminal group.

2. Click (located on the bottom of the tree view). The Input dialog opens
prompting you to select a name for the new terminal.
Figure 54: Input Dialog
3. Enter a name and click . The Input dialog closes and the terminal
Configuration screen opens.
4. Configure the parameters for the terminal device. The LAN and PID information can be
entered on the terminal Configuration screen.
5. Click to save the parameter values. Click to terminate the session
without creating the new terminal. After clicking , the terminal addresses are
sent to the IPE, the router and the OptimISe devices.

To modify a terminal:
1. From the Remote tree, select a specific terminal. The work area fills with the terminal
status window (the default) and the specific terminal status displays across the top of the
configuration.
Figure 55: Terminal Status
2. Choose the Configuration or Networking tab.

3. Configure the parameters for the terminal device.
4. Select the NCC group from the dropdown menu. You can change NCC groups from the
terminal Configuration page.
Figure 56: Terminal Switch Group

without changing the terminal.
To delete a terminal:
1. From the Remote tree, select a terminal.

2. Click (located on the bottom of the tree view). The Delete dialog opens
prompting the user confirm deletion of the selected terminal.
Figure 57: iRG Delete Prompt
3. Click to delete. Click to exit without deleting the selected terminal.

4.1.1 Terminal Configuration Enhancements

The following parameters cannot be modified on a non-active terminal:
 IP addresses
 PIDs
 Data Rates (except for terminals that have never been connected to the system)
Four major enhancements aid terminal configuration:
 Tooltip pop-up window: displays the valid range for the parameter. In the example
below, the tooltip displays the Frequency valid range of [-45] – [-2.5] dB.
 Illegal value notice: turns the parameter name red when an illegal value is entered into
the field or when a parameter is required but not yet entered (such as PID 1).
 Dependencies notice: turns all dependent data set parameters red when one of the
parameters is not valid.
 Licensed Max DR: the licensed maximum data rate is read from the terminal and
displayed on the terminal configuration page.
Figure 58: Tooltip, Illegal Values Display
4.1.2 Cross Polarization Test

During Cross-Poll, the terminal can be in either InterSKY mode or SCPC mode.
During the Cross Polarization test the terminal transmitter parameters are configured on the
Cross Poll window. From the Cross Poll window you can:
 Send Cross Poll parameters to the terminal transmitter via the FLSS (using SNMP
protocol).

 Send a modulation free (CW) signal from terminal transmitter to satellite while
modifying its power level and frequency.
 Enable broadcast according to Cross Poll configuration by clicking Start, or stop
broadcasting by clicking Stop.
Cross-Poll is enabled in both SCPC mode and InterSKY mode. When Cross Poll is
performed in InterSKY mode, the terminal priority must be Deferred. Cross Poll can also
work in an unacknowledged environment, that is, when the return link is still not active.
CW modulation is used during Cross Poll mode; data is not transmitted by the terminal.
When the transmitter is turned on due to Cross Poll testing, closing the dialog window
causes the terminal to return to normal modulation (not CW).
When the dialog window is closed while the transmitter is turned off, and any of the three
buttons is clicked (Start, Submit, Stop) the warning ―You leave X-Poll while Tx is turned
off‖ is displayed. Click to leave Cross Poll mode.
To start Cross Poll:
1. From the iRG Configuration window click . The Cross Poll sub-screen
opens for the selected terminal. The IS-NMS automatically changes the terminal‘s
priority to ―Deferred‖.
Figure 59: Terminal Cross Poll
Parameter Description Range

Tx Power Level Transmitted power level (mandatory) [-45] – [-2.5] dBm
When this parameter is changed on the Cross Poll
window the new value is temporary. It is not
stored in the default properties file.
Tx Frequency Transmitted frequency (mandatory) 950 – 1525 MHz
When this parameter is changed on the Cross Poll
window the new value is temporary. It is not
stored in the default properties file.
Modulation (not editable) Clear Wave
Tx Data Rate (not editable) 0
2. Enter the Cross Poll parameters for the terminal.

3. Click Submit to check the parameters before Start or Stop.

Function Enabled Disabled

Start Turns on the terminal Dialog window is opened Dialog window is opened
transmitter with Tx when terminal is inactive when terminal is inactive
Power Level, Tx (red) Dialog window is (red), and user enters
Frequency, and CW opened when terminal is invalid parameters Dialog
Modulation inactive (red), and user window is opened when
changes the parameters to terminal is active (green);
valid ones transmitter is already On
Stop Turns off the terminal When transmitter is turned on When the terminal is off
transmitter and Start is enabled
Submit Applies parameters When terminal is active When terminal is active
from dialog window to (green) (green) and invalid
the terminal parameters are entered
transmitter. Submit When terminal is inactive
does not turn on the (red)
transmitter
4. Click Start or Stop. Broadcast starts or stops, accordingly.
Cross Poll Default Parameters

The Cross Poll window initially displays default values for Tx Power Level and Tx
Frequency. The Cross Poll parameters are stored in
ShironNMS/xpoll/default.properties. These values are applied to all hubs when the
default.properties file exists.
When a file of defaults for a specific hub exists, the IS-NMS applies the specified hub values
instead of the generic default properties.
When no default.properties file exists, the IS-NMS calculates the average value for Tx
Power Level and Tx Frequency. This average is from the system max and min values, not
the user entered max and min values.
The priority of defaults is applied in the following order:
1. Specific hub default properties.
2. Generic default properties.
3. No defaults; an average is calculated and used as the default.
To change the X-Poll default parameters for all hubs:
1. Open the default.properties file in NotePad.

2. Delete the Tx Power Level value and enter the new value. Do the same for Tx
Frequency.
3. Save the file.
4. Restart the IS-NMS server. Log in to the IS-NMS and transition to Cross Poll. The new
values display in the parameter fields.
To change the X-Poll default parameters for a specific hub:
1. Copy the default.properties and rename the copy to the specific hub. For example, the
hub name is Hub104. The default properties name is Hub104.properties.
2. Open the <hubname>.properties file in NotePad.

3. Delete the Tx Power Level value and enter the new value. Do the same for Tx
Frequency.
4. Save the file.
5. Restart the IS-NMS server. Log in to the IS-NMS and transition to a terminal on the
specific hub.
6. Click X-Poll. The new values display in the parameter fields.
4.1.3 Drop&Insert
Drop&Insert facilitates quick deployment of multiple terminals with maximum control and
minimum field expertise. Configuration files for specific terminals are created and saved at
the hub site, transferred to the field engineering laptop, taken to the remote site, and quickly
loaded into the terminal. Standard file creation and provisioning provides a level of quality
assurance while providing the maximum ease of installation. Features of the Drop&Insert
standalone application are present in the IS-NMS. For information about the standalone
Drop&Insert application refer to the Drop&Insert Operation Manual.
From the Drop&Insert sub-screen, the user can set either one or many terminal parameters
for the terminal. From this sub-screen, the user can reset the device, load and save
configurations and send them to the device.
Drop&Insert can also work in an unacknowledged environment, that is, when the return link
is still not active.
Note: Drop&Insert is available for terminals only. To update other IP addresses,

such as the IP address of the IPE, you must use the terminal Configuration
Screen.
DVB Receiver Active/Non-active

The DVB receiver status can be active or non-active. The receiver active status remains
active unless the signal is lost for approximately 50 seconds to 1 minute. At that time the
receiver changes state from active to non-active at that time. The Non-active receiver
becomes active at that time.
GSM Provisioning
Multiple GSM profiles can be stored in text files. The files are located in folder ‗gsm‘ under
the application root. The default profile is stored in the file gsm.properties. It is highly
recommended not to delete this file. Additional profile parameter files must have the
‗properties‘ file extension and include all the parameters in the same structure as the default
file.
To set terminal parameters using Drop&Insert:
1. From the terminal Configuration tab, click Drop&Insert. The Drop&Insert sub-screen
opens for the selected terminal.

Figure 60: Drop&Insert

iRG operational Pull-down menu to select the terminal InterSKY, SCPC
mode* operations mode. When the mode is
changed the terminal must be reset for the
new mode to become active.
NCC Multicast parameters
Address* NCC multicast address Legal IP address
Multicast port* terminal multicast port 1025–65535
Server port* NCC multicast port 1025–65535
DVB Receiver parameters (Active and Non Active)
DVB Frequency Receiver frequency (optional) in GHz 0.95–14.15 GHz
DVB Mode ETSI Digital Video Broadcasting mode for DVB-S or DVB-S2
satellite


DVB LNB LNB reference frequency (optional) 0 MHz, 5150 MHz, 5760
Frequency MHz, 5950 MHz, 9750
MHz, 10000 MHz,
10050 MHz, 10250
MHz, 10600 MHz,
10750 MHz, 11000
MHz, 11200 MHz,
11250 MHz, 11300
MHz, 11475 MHz,
11750 MHz, 17250
MHz, 18250 MHz,
19250 MHz
Symbol Rate DVB Carrier symbol rate in Msps (optional) 1-45 Msps for DVB-S/S2
Usage Mode Indicates whether or not the secondary In use, Not in use
(Non Active only) DVB settings are in use or not.
PID 1 – PID 5 Packet identifier for data transferred from 33 – 8191

hub to terminal. PID 1 is mandatory.
IP Configuration parameters
Tx IP terminal Tx interface IP address (optional) Legal IP address
Tx Subnet terminal Tx interface IP network subnet Legal IP subnet address;
address (optional). initialized to the
terminal‘s actual Tx
subnet.
LAN IP terminal LAN interface IP address Legal IP address
(optional)
LAN Subnet terminal Tx interface IP network subnet Legal IP subnet address
address (optional)
Default Gateway IP Enables the use of different default Legal IP address
address gateways for different Remote Gateways in
non-FDMA mode (optional)
Default Gateway Enables the use of different MAC address 6 hex double digits,
MAC address for different Remote Gateways in non- semicolon separated
FDMA mode (optional)
Default DVB-S IP terminal Rx interface IP address (optional) Legal IP address
address
Tx parameters
Tx Frequency RLSS frequency (optional) 950–1700 MHz
Tx Data Rate Transmitted Data Rate (optional) 9–4096 Kbps (depends
upon Tx Modulation)
Tx Modulation RLSS modulation type (optional) QPSK, 8PSK, OPSK,
CW, SINUS
Extended Frequency Permanent Frequency offset (optional) [-2500] – [2500] MHz
offset
Spectrum Inversion Spectrum inversion for C Band LO support Invert/Non-invert
(optional)


GSM Provisioning
Send GSM Enable GSM provisioning. When the Send Checked:
Provisioning GSM Provisioning checkbox is checked, Not Checked:
the parameters are loaded from a file and
validated.
Cellular Network Cellular network connects cell-site nodes 2G button
with central-site nodes, for both 2G and 3G 3G button
networks
Management IP Management LAN interface IP address Legal IP address
Management Port Management LAN interface port address range 1500-65000
Management Link Link name Free format text
Name
Send QoS When it is unchecked, QoS parameters are Checked
not sent. Unchecked
QoS Subnet IP If filled, its value overrides the parameter Valid IP address
QoS Subnet IP from the parameter file
QoS Subnet Mask If filled, its value overrides the parameter Valid Subnet mask
QoS Subnet Mask from the parameter file
2. Select the terminal Operational Mode, InterSKY or SCPC.

3. Use the action buttons at the bottom of the Drop&Insert sub-screen to:
 Click Reset to send a reset command to the selected terminal.
 Click Load to load an existing saved configuration from the terminal configuration
file.
 Click to save the (edited) configuration currently displayed to the
terminal configuration file.
 Click Send to send parameters currently configured on the Drop&Insert screen to
the selected terminal.
 Click Close to close the Drop&Insert sub-screen.
4. Click to display GSM Backhaul Parameters. Select the GSM
Backhaul profile.
Figure 61: GSM Backhaul Profile Selection
The GSM Provisioning Parameters are displayed.

Figure 62: GSM Backhaul Profile Parameters
Parameter Name of the parameter in the profile
Value Value for the parameter
Status Valid or Invalid
Description Free format text
5. Click to use the displayed GSM profile.
Multiple Drop&Insert
To perform Multi Drop&Insert over several terminals:
1. Point the cursor at any point on the Remote tree of the IS-NMS main screen.
2. Right-click to open the menu of commands and select Multiple Drop&Insert. The
Multiple Drop&Insert dialog opens.

Figure 63: Multiple Drop&Insert
3. Select one or more terminal devices and groups from the System tree at the left of the
screen.
4. Click Open. The Drop&Insert screen opens.
Figure 64: Multiple Drop&Insert Terminal Configuration
Refer to Figure 60: Drop&Insert for parameter details.

5. From the bottom of the Drop&Insert screen, select the action you wish to perform on the
selected devices:
 Click Reset to send a reset command to all selected terminal devices.
 Click Load to load an existing saved configuration from the terminal configuration
file.
 Click to save the (edited) configuration currently displayed to the
terminal configuration file.
 Click Send to send all parameters currently configured on the Drop&Insert screen to
all selected terminal devices. When QoS, 2G, or 3G are disabled only BoD
parameters are sent.
4.1.4 Migration
The InterSKY migration feature facilitates moving terminals from CCM to ACM. These
parameters affect the channel. If parameters are sent one after the other, connection will
break. During migration all parameters are sent at the same time.

When clicked, the values of the following fields are sent to the specified terminal using the
SNMP:
 Multicast Address
 DVB Frequency
 DVB Symbol Rate
 PID 1 – 5
 DVB Mode
The InterSKY Migration button is disabled unless all these fields have valid values. The
button tooltip indicates what field values are missing when the mouse rolls over the button.
Figure 65: Migration

Multicast port* terminal multicast port 1025–65535
Server port* NCC multicast port 1025–65535
DVB Frequency Receiver frequency (optional) in GHz 0.95–14.15 GHz
Symbol Rate DVB Carrier symbol rate in Msps 1-45 Msps for DVB-
(optional) S/S2
PID 1 – PID 5 Packet identifier for data transferred from 33 – 8191
hub to terminal. PID 1 is mandatory.
DVB Mode ETSI Digital Video Broadcasting mode for DVB-S or DVB-S2
satellite
To migrate terminals from CCM to ACM:
1. From the terminal Configuration tab, click Drop&Insert. The Drop&Insert sub-screen
opens for the selected terminal.
2. Enter valid parameters for the Multicast Address, DVB Frequency, DVB Symbol Rate,
PID 1-5, DVB Mode.
3. Click InterSKY Migration. The new parameters are sent to the terminal. A message
displays that new parameters were sent to the terminal.
Figure 66: InterSKY Migration Complete

4.1.5 Owner Information

Owner Information is a set of text windows to enter and save contact information about the
owner.
To modify terminal owner information:
1. From the Remote tree, select a terminal group. The terminal Configuration screen opens.
2. Click Owner Details. The Owner Details window opens for the selected terminal.
Figure 67: Terminal Owner Details Dialog
3. Enter the Phone number, E-mail, and Address.

4. Click . The Owner Details are stored to the database.

without changing the terminal.
4.1.6 Upgrade
You can upgrade a specific group of terminals or one specific terminal from the IS-NMS.
To upgrade a terminal:
1. In the lower left corner of the terminal Configuration page, click Upgrade. The Choose
Upgrade version window is displayed.
Figure 68: Choose the Upgrade Version

The current terminal version is displayed towards the top of the window. All possible
upgrade versions are listed in the pull-down menu next to Available versions. Only list
those versions that are compatible with the selected terminal are listed.
2. From the Available version list, select the version to which to upgrade the selected
terminal.
3. Click Start. The terminal icon in the Navigation window turns to blue for the duration
of the upgrade process. During device upgrade you can navigate in IS-NMS. To see the
status of the terminal, click the Configuration tab. Monitoring Status displays a blue U
and the terminal icon in the Navigation window turns blue.
Figure 69: Terminal Status During Upgrade
To perform Multi Upgrade:
1. Right-click to open the menu of commands and select Multiple Versions Upgrade.
Figure 70: Multiple Versions Selection

Figure 71: Multiple Version Upgrade
2. Select one or more terminal devices and groups from the System tree at the left of the
screen. Use Shift+cursor click to select a sequence of terminals. Use Ctrl+cursor click
to select individual terminals.
The terminals must be the compatible to be upgraded together. For example, you want to
upgrade several terminals to v5.1. However, one of the selected terminals can only be
upgraded to v5.0 while the other selected terminals can be upgraded to v5.1. This
situation causes an error.
3. Click Upgrade. The Available versions screen opens.
Figure 72: Multiple Version Upgrade Version Choice
The current version is displayed since the terminals are of the same version in the basic
system. When there no multiple and potentially different terminals begin upgraded at
one time, select the version to which to upgrade.
4. Click Start. The selected terminal icons turn blue during the upgrade process. When the
version selected is not compatible with any device selected, the upgrade process stops
and an error window is displayed.

Figure 73: Server Error on Upgrade Terminal
When this happens, you must eliminate from the upgrade process any terminal that is not
compatible with the selected version or select a different upgrade version. Then restart
the upgrade process.
4.2 Terminal Networking Feature

Terminal Networking provides access to the following features:
 Basic networking parameters
 SkyX Accelerator
 Static Routes
 Multi-field QoS
 DSCP
 NAT
 VLAN support
Figure 74: Networking Configuration
4.2.1 Basic
Use the section Basic to enter LAN and PID information.

Figure 75: New Network LAN and PID Configuration

Tx transmit IP address (mandatory) Legal IP address
LAN 1 IP terminal LAN interface IP address (mandatory) Legal IP address
LAN 1 terminal LAN interface network Subnet (mandatory) Legal Subnet address
SUBNET
LAN 2 IP Optional, configure secondary LAN Legal IP address
LAN 2 Configure subnet for secondary LAN (not optional if Legal subnet address
Subnet 2nd LAN above)
Packet Packet identification for terminal data. PID 1 is Range: 33 – 8191
Identifiers mandatory.
(PID)
QoS Mode Select which QoS mode to use. When this mode is DSCP, Multi-field
changed the terminal must be restarted.
4.2.2 Acceleration
TCP/IP is the suite of protocols used to transfer data over the Internet and over most other
data networks. While fiber and cable are commonly used for local and wide area networks,
the TCP/IP protocols can run over any physical media including satellite links. However, the
long latency, high bit error rates, and asymmetric bandwidth conditions typical of
communications over geostationary (GEO) satellite links, restrict the rate at which TCP/IP is
able to send data over these connections.
The XTP Protocol overcomes these limitations of TCP/IP by transparently intercepting
TCP/IP data and converting it to the XTP Protocol, a transport protocol specially optimized
for data transmission over satellites. The XTP Protocol is used only for the transfer of data
between both sides of the satellite link: the server on the hub side and the client of the
terminal side. The clients and servers continue to use standard TCP/IP for communications
with the gateway. This architecture offers a system that is entirely transparent to end users.
No changes, modifications, or settings to clients or servers are required. The gateway system

provides improved performance regardless of the operating system, TCP/IP implementation,

or settings on end clients, or servers.
The IS-NMS manages the accelerator client in the terminal. The accelerator increases the
amount of data carried over the link, accelerates Web applications, and speeds large file
transfer response times.
Figure 76: Advanced Acceleration Settings

Accelerator mode Turn the accelerator mode on or off. See the Off, SkyX Client,
accelerator advanced mapping entities below. OptimISeR
Client IP Address Taken from Client Subnet Address Legal IP address
Client Subnet Address Client IP Address is filled automatically by the Legal IP subnet
same value + 1. address Must be
divisible by 4
Client Netmask (Read-only) Legal netmask
Server IP Address IP address of the server Legal IP address
Inbound Rate Data rate inbound 1–170000000 bps
Outbound Rate Data rate outbound 1–3072000 bps
Round-trip time Round trip between the terminal and the SkyX 1–2500 ms
server on the hub
OptimISeR IP Calculated from the LAN address of the terminal, Read-only field.
Address the field is disabled
OptimISeR Netmask Netmask for the OptimISe-R Legal netmask
To set advanced terminal Network parameters:
1. Click Advanced. The Mapping Entries window displays.

Figure 77: Mapping Entries

Active When Mapping Entries exists, checkbox has a Checked or not
check checked
When checkbox is checked:
 Save acts as Modify
When checkbox is unchecked:
 Save acts as Delete. Mapping Entry not
available
ID The number identifier for the specific mapping 1–8
entry
Link Type Defines the link type None or Satellite
Attribute Type of acceleration associated with the mapping No SkyX: Can be
entry. either terminal or hub
 When the link is accelerated, its attribute must side
be Remote SkyX or Local SkyX. Remote SkyX: From
 When the link is not accelerated, its attribute the hub side
must be No SkyX. Local SkyX: From the
terminal side
Link Type and Attribute Link Type
Attribute No SkyX None, Satellite
interrelationship
Remote SkyX Satellite
Local SkyX None
IP Address IP address of the mapping entry Legal IP address
Netmask Netmask of the mapping entry Legal Netmask
2. Enter the parameters and click .
3. To update the screen to the actual device parameters, click . The device is
polled and the new values are displayed.

4.2.3 Terminal Static Routing Table

The terminal static routes table monitoring and configuration are enabled via iPG
―Networking‖ sub-panel. For permanent routes, the IS-NMS updates the IPE (supported
types) automatically.
For a terminal to be able to find a device over the network a pair of addresses must be
defined: the destination and the gateway. To get to the defined destination, communicate
must travel through the gateway.
The routing table for a specific terminal is configured either at the terminal or from the
NCC. Two types of entries co-exist: permanent and non-permanent (temporary) routes. For
permanent routes the IS-NMS automatically updates the IPE supported types, that is, the
add, remove, and update operations that are supported.
From this static table a route can be made active or inactive.
To display the static routes:
1. Click the arrow next to Static Routes. The window expands to the route type selection.
Figure 78: Terminal Static Routes Expansion

Route Type Routing table entries are permanent or Permanent: route is persistent
temporary. The route type selection allows Non-permanent: route is not
you the select which routes to view. persistent and can change or
disappear
2. Select the route type to display and click Show. The Static Routes table expands.

Figure 79: Terminal Permanent Routing Table
Active When checked the route is active
Destination IP address of the packet's final destination
Gateway IP IP address of the host that is connected to the destination IP
NetMask Which portion of the IP must match in order for that route to be used
4. To change a route status, select the Active box.
4.2.4 Terminal Quality of Service

Network management allows the creation of subnets, services, and applications in order to
support your customer requirements. Two subnets, eight services, and sixteen applications
give you the flexibility to offer complex broadband applications.
Subnets are an internal division of the network and frequently reflect boundaries such as
physical (between two Ethernets), administrative (between two departments), or
geographical (between two locations). This structure affects only the network's internal
behavior and is completely invisible to the outside world.
Click the arrow next to Quality of Service. The window expands to display three categories:
Subnet, Services, and Applications.
Two subnets can be defined for every terminal, for a total 100% usage. The QoS Status
indicator appears to the right of the subnet definitions when at least one subnet is defined.
Figure 80: QoS Status Usage Indicator
The complete circle represents 100% usage over the two subnets. Each subnet usage is
displayed in a unique color. The Free Space indicator displays the number of Kilobits not
allocated.

Figure 81: QoS Subnets, Services, and Applications
Edit and Delete are active over Subnets, Services, and Applications. You must select the
line before clicking Edit or Delete.
For each subnet four services can be defined. And for each service, two applications can be
defined.
Figure 82: Subnet, Service, Application Distribution

To add or edit a subnet:
1. Click Add Subnet (when 2 subnets are already defined this button is inactive) or select
the Subnet line and click Edit on the right side of the line.
Figure 83: Add/Edit Subnet
Subnet Name Unique name of the subnet
IP Address IP address of subnet
Mask Which portion of the IP must match in order for that route to be used
CIR Committed Information Rate The total of all the CIR values of all the
Subnets cannot exceed the CIR value defined for this terminal.
PIR Peak Information Rate The total of all the PIR values of all the Subnets
cannot exceed the PIR value defined for this terminal.
2. Enter the new values.

3. Click to save the new parameters. Click to cancel this session.
To add or edit a service level:
1. Select the Subnet to which to add the service level.

2. Click Add Service Level (when 8 service levels are already defined this button is
inactive) or select the Service Level line and click Edit on the right side of the line.
Figure 84: Add Service Level

Service Level Name Unique name of the service level
CIR Committed Information Rate The total of all the CIR values of all the
Subnets cannot exceed the CIR value defined for this terminal.
PIR Peak Information Rate The total of all the PIR values of all the
Subnets cannot exceed the PIR value defined for this terminal.
Max Delay Maximum delay allowed for this service
Min DR Minimum data rate allowed for this service
Priority Priority of the Service

To add or edit an application:
1. Select the Subnet and Service Level to which to add the application.
2. Click Add Application (when 16 applications are already defined this button is
inactive) or select the Application line and click Edit on the right side of the line.
Figure 85: Add Application
Application List List of pre-defined applications
Add new Application Checked: Add some new application to the Application List and
save the new application in the database table.
Not checked: Choose one of the existing in the list an application in
order to change current subnet configuration.
Application Name Unique name of the Application
Port From Port of origin
Port To Port of destination
Port Type Source, Destination
Protocol UDP, XTP, TCP, ICMP
Service Level of Pull-down menu of the valid services for this application
Application


4.2.5 DSCP
DSCP specifies a simple, scalable and coarse-grained mechanism for classifying and
managing network traffic and providing QoS. It can be used to provide low-latency to
critical network traffic such as voice or streaming media while providing simple best-effort
service to non-critical services such as web traffic or file transfers.
QoS DSCP Mode Configuration contains the definition of DSCP mode related configuration
options.
For each supported traffic class, defined by DSCP value (or group of values), a separate
queue is allocated. Bandwidth resources are allocated per queue according to configured
parameters, like rate and burst size. The allocation is automatic, according to active
transmission channel data rate. Packets from specific traffic class are shaped to
corresponding queue according to class-to-queue mapping.
In the case when there is traffic rate excess in a particular queue, policing is applied
according to supported policing scheme(s).
Scheduling algorithm, such as strict priority (LLQ) or WFQ: weighted fair queue are
implemented.
The IS-NMS receives QoS configuration by means of the SNMP interface.
The DSCP based configuration key parameters for configuration are:
 Class-to-queue mapping for supported PHBs
 Traffic class parameters: CIR, WRED thresholds
The PHB Classes, identified by specific DSCP values, are presented by specific QoS
configuration modules:
 EF (VoIP)
 CS5 (Broadcast Video)
 CS4 (Real-Time Interactive)
 AF4 (Multimedia Conferencing)
 AF3 (Multimedia Streaming)
 AF2 (Transactional Data)
 AF1 (Bulk Data)
 CS7 (Network Control)
 CS6 (Internetwork Control)
 CS3 (Call Signaling)
 CS2 (OAM)
 CS1 (Scavenger)
 DF (Best Effort)

For the relevant classes resources are allocated, such as queue buffer, bandwidth, and so on,
according to Class Policy Map. In other words, a packet with a DS field corresponding to the
selected class is forwarded to the dedicated queue and get configured service.
Unselected classes get service defined by DF (Best Effort) class.
Queue Policies
The list of supported queue policies is presented by the QoS DSCP configuration:
PQ 1..5: Strict Priority Queue (up to 5 queues)

CBWFQ + WRED 1..4: Class Based WFQ (up to 4 queues) with WRED
WFQ 1..5: WFQ (up to 5 queues)
WFQBE: Default Queue – WFQ with RED
Each selected PHB class is mapped to one of available policies according to the rules
defined in Policy Map section.
Class Policy Map

The Class Policy Map ties the PHB classes and queue policies, and is represented by the
number of class policies. Each class policy combines one PHB class, queue policy and set of
related parameters.
The mapping is done according to rules, as follows:
 EF class is mapped to one of PQ queues, configured parameters: CIR, Queue priority
 CS5 class is mapped to one of PQ queues, configured parameters: CIR, Queue priority
 CS4 class is mapped to one of PQ queues, configured parameters: CIR, Queue priority
 AF4 to AF1 classes mapped to one of CBWFQ+WRED queues, configured parameters:
CIR, PIR, PIR priority, 3 WRED drop precedence (DP) levels represented by Min
threshold, Max threshold, Mark probability denominator
 CS1, CS2, CS3 classes mapped to one of WFQ queues, configured parameters: CIR,
PIR, PIR priority
 CS6, CS7 classes mapped to one of PQ queues with configured parameters: CIR, Queue
priority; or WFQ queues, configured parameters: CIR, PIR, PIR priority
 DF class mapped to WFQ+RED queue, configured parameters: CIR, RED Min
threshold, Max threshold, Mark probability denominator

Figure 86: DSCP PHB View, Policy View, PHB Statistics, Queue Statistics
Parameter Details
PHB AF1 AF2 AF3 AF4
Application Transactional Multimedia Multimedia Real-time
Class Data Streaming Conferencing Interactive
Queue Policy Best Effort Best Effort Best Effort Best Effort
Queue LOW LOW LOW LOW
Priority
PIR Priority 15 15 15 15
Max Delay 0 0 0 0
CIR [bps] 0 0 0 0
PIR [bps] 0 0 0 0
Drop WRED WRED WRED WRED
Discipline
WRED DP 1 1 1 1
Min Th: - - - -
Max Th: - - - -
Probability: - - - -

Parameter Details
PHB CS1 CS2 CS3 CS4 CS5 CS6 CS7
Application Scaven OAM Call Broadcast Network Inter Bulk
Class ger Signaling Video Control network Data
Control
Queue Policy Best Best Best Best Best Best Best
Effort Effort Effort Effort Effort Effort Effort
Queue LOW LOW LOW LOW LOW LOW LOW
Priority
PIR Priority 15 15 15 15 15 15 15
Max Delay 0 0 0 0 0 0 0
CIR [bps] 0 0 0 0 0 0 0
PIR [bps] 0 0 0 0 0 0 0
Drop tailDro tailDrop tailDrop tailDrop tailDrop tailDrop tailDro

Discipline p p
WRED DP 1 1 1 1 1 1 1
Min Th: - - - - - - -
Max Th: - - - - - - -
Probability: - - - - - - -
Parameter Details
PHB DF EF EF
Application Best Effort VoIP VoIP
Class
Queue Policy WFQBE Best Effort PQ1
Queue LOW LOW HIGH
Priority
PIR Priority 15 15
Max Delay 5000 0 100

CIR [bps] 0 0 512000
PIR [bps] 0 0 512000
Drop tailDrop tailDrop tailDrop
Discipline
WRED DP 1 1 1
Min Th: - - -
Max Th: - - -
Probability: - - -
To refresh the PHB class list:
1. Click .

To add a new PHB class:
1. Click to add a new PHB class. The Add PHB window is displayed.
Figure 87: Add PHB Class
2. Use the charts above to configure the new class. Enter the new values.
3. Click to save the new parameters. Click to cancel this addition.
To modify a PHB class:
1. Select the PHB class and then click to add a new PHB class. The Modify
PHB window is displayed.
2. Use the charts above to modify the class. Enter the new values.
3. Click to save the new parameters. Click to cancel this modification.
To delete a PHB class:
1. Select the PHB class and then click to delete a PHB class. The confirmation
window is displayed.
2. Confirm the deletion or click to cancel the delete.
4.2.6 NAT
Network Address Translation (NAT) connects a private network with private IP addresses to
the public domain with globally unique registered addresses. NAT allows a single device,
such as a terminal, to act as agent between the public network and a local or private network.
This means that only a single unique IP address is required to represent an entire group of
computers to anything outside their network. NAT is used by the terminal that sits between
an internal network and the rest of the world.

Figure 88: Public and Private Networks
The need for IP Address translation arises when a network‘s internal IP addresses cannot be
used outside the network either for privacy reasons or because they are invalid for use
outside the network.
NAT maps the local IP, internal to the local private network to a global IP, recognized
outside the private network. In the example in the figure above the private IPs are not unique
outside the private network. They must be mapped to a global IP address before they are of
any use outside the private network.

Figure 89: Static NAT
Static NAT says that the local IP is always mapped to the same global IP. In the example
above station 1 is always mapped to 213.18.123.110. Stations 2 and 3 are also mapped
respectively. These mappings are fixed, static. They do not change until they are
reconfigured.
Figure 90: Dynamic NAT

Dynamic NAT maps the local IP to the first available global IP. In the example above station
1 maps to 213.18.123.116. At another time station 1 might map to 213.18.123.119. The
available IP is selected from the global IP configuration table.
This implementation of NAT is compliant with:
 RFC 2663 IP Network Address Translator (NAT) Terminology and Considerations
 RFC 3022 Traditional IP Network Address Translator (Traditional NAT)
NAT within IS-NMS

The IS-NMS supports an overall NAT solution. The IS-NMS retrieves from the terminal all
existing NAT entries during polling (both manual and automatic) and stores the information
in the database. These entries are displayed in a separate table, and are available for
modification, addition or deletion.
 Each entry contains a private IP address, a global IP address, and a subnet mask.
 The private network IP address is translated to a global IP address in inbound traffic and
vice versa. The global IP address is translated to a private IP address in outbound traffic.
 A subnet mask relates to both the private network IP address and the global IP address.
Its default value is 32 (255.255.255.255).
 The IS-NMS supports up to 254 Static NAT entries.
When the TERMINAL LAN or permanent static route settings change, some of previously
entered NAT entries may become invalid. The invalid entries on the NAT configuration
panel are displayed in red. No changes can be saved until the entries have correct values.
NAT Entry Validation

Static NAT entries must conform to the rules. Entries that do not conform cannot be saved in
persistent storage and nor can they be sent to terminal until they conform. Every static NAT
entry is subject to the following rules:
 Both private and global IP addresses must fit the entered subnet mask value
 Private IP addresses must belong to one of the following:
 LAN1 Subnet
 LAN2 Subnet
 Any of subnets defined in Permanent Static Routes section
 Private IP subnet must not intersect with any other defined private IP subnet
Dynamic NAT entries must conform to the rules specified for Static NAT entries. The only
exemption is that External IP address must represent a single computer address rather than a
network.
Validation is performed upon entry of the information. When validation fails, the field and
its label are colored in red and is disabled.
Static and Dynamic NAT Configuration

This panel contains settings for both Static and Dynamic NAT for a selected terminal.

Dynamic NAT entries are displayed when the NAT window is expanded. It is possible to
define up to 2 dynamic NAT entries. Changes in LAN definitions or Static Routes may have
an effect on the defined dynamic NAT; some of defined entries can become void. For
example:
User: 192.168.1.0/24 LAN1 and defines Dynamic NAT from 192.168.1.0/24 to
80.74.107.218.
Result: After the user changes the LAN to 192.168.204.0/24 the previously defined
Static NAT entry becomes meaningless.
These entries are left as-is. Once the user attempts to change NAT definitions, validation for
these entries fails and user can‘t save his changes until he corrects them.
Static NAT entries are displayed with by clicking the Static NAT button. Changes in LAN
definitions or Static Routes can have an effect on a defined Static NAT; some of the defined
entries become void. For example:
User: 192.168.1.0/24 LAN1
Defines Static NAT from 192.168.1.10/32 to 80.74.107.218
Result: After the user changes the LAN to 192.168.204.0/24 the previously defined
Static NAT entry becomes meaningless.
These entries are left as is. Once user attempts to change NAT definitions, validation for
these entries fails and user can‘t save the changes they are corrected.
To configure Dynamic NAT:
1. Select the NAT bar to expand the configuration window.
Figure 91: NAT Configuration
Enable NAT This radio button enables or disables both Dynamic and Static NAT
settings for selected TERMINAL. By default NAT is disabled.

Dynamic NAT
Check box Check to enable Dynamic NAT definition
Uncheck to disable Dynamic NAT definition
Private IP address Legal IP address that is not known outside the network
Private subnet External subnet bitmask is always 32 (single computer). It is being
bitmask displayed for user‘s information
External IP address Global legal IP address that is known and is the public portal into the
network
2. Select the NAT to be On or Off.

3. Enable dynamic NAT and enter the three parameters: private IP, subnet mask, and
Global IP address.
4. Click . If changes are made and not saved before moving off the window, the
changes will be lost.
To configure Static NAT:
1. Click to display the Static NAT table.
Figure 92: Static NAT Table
Private IP address Legal IP address that is not known outside the network
Private subnet External subnet bitmask is always 32 (single computer). It is being
bitmask displayed for user‘s information
External IP address Unlike the dynamic settings, the static global IP subnet bitmask
always equals the entered private subnet bitmask. User can not be
change it separately
2. To add an entry, select the entry and click .

Figure 93: Add Entry to Static NAT Table
3. Enter the Private IP, Range, and External IP. Click . The entry is displayed in
the Static NAT table.
4. To delete an entry, select the entry and click .
5. To save changes made to the NAT configuration click .

6. To redisplay the previous configuration click . This causes all unsaved
changes to disappear.
4.2.7 VLAN Creation

VLAN (Virtual Local Area Network) tagging creation is needed when VLANs span multiple
switches. By grouping multiple physical network segments into individual broadcast
domains, VLANS, you can create multiple virtual switches. This grouping of clients can be
organized logically rather than being limited to a subnet per physical switch.
VLAN facilitates VLANs across the Inbound and Outbound InterSKY satellite link. As part
of this effort the terminals can create VLAN tags for inbound traffic. VLAN pass-through is
supported and maintained.
VLAN and the Terminal

Two VLAN modes are supported: pass-through and create. Pass-through mode only looks
for tagged packets and only passes the tagged packets on. VLAN create mode creates a new
tag for every packet, regardless, and then passes the packet on.
The VLAN On/Off status is configurable only in the IS-NMS, and is sent to the terminal
MIB. The VLAN tag insertion mode is then configured on the integrated network switch
accordingly. All relevant VLAN configuration parameters can be seen in the terminal MIB.
VLAN Configuration
Initially the VLAN mode is set to VLAN pass-through. In this mode the VLAN ID for both
ports editing is disabled. Values in Port 1 VLAN ID and Port 2 VLAN ID represent VIDs
which are free to be allocated.

In order to define the VLAN ID‘s for a terminal you can change the VLAN mode to VLAN
create. In this mode the VLAN ID fields are editable. Either leave the existing automatically
generated values or define new values.
displays polled results from the terminal.
causes the defined settings to be saved to the database and also reports to the
terminal the success or failure of the following validation:
 It is best practices for the VLAN ID for both Port 1 and Port 2 to be the same.
 A VLAN ID can be equal to the VLAN ID defined for a port of a different terminal.
If this validation fails, no definitions are sent to terminal and error message is displayed.
Figure 94: VLAN Configuration
VLAN Mode VLAN pass-through: only pass on packets with VLAN tags.
VLAN create: always create a VLAN tag and insert into the
packet.
Port 1 VLAN ID This displays the 1st available port. You can change the port by
entering a new port number.
Port 2 VLAN ID This displays the 2nd available port. You can change the port by
entering a new port number.
To configure VLAN:
1. Select the VLAN bar to expand the configuration window.

2. Select VLAN pass-through or VLAN create.
3. Enter the Port 1 and Port 2 VLAN IDs.
4. Click to save the new parameters.

4.3 Terminal Status

The terminal status view displays information on the selected terminal by clicking the Status
tab.
Every time the IS-NMS recognize that a terminal changes its status from Not-Active to
Active, the IS-NMS polls the Tx address, primary and secondary LAN, acceleration and
routing table.
If the IS-NMS notices that there is a new address configured in the terminal, it updates the
IPE, Router and OptimISe.
In addition, the Tx address is calculated automatically from the ID of the terminal, the name
of the terminal is calculated automatically from the LAN address (once the IS-NMS polls the
LAN address, after the terminal connects). The OptimISe-R address (section ‎4.2.2
Acceleration) is calculated from the LAN address as well.
Figure 95: RG Status (new fields)
RG ID RG unique ID
HUB Associated hub
RG Version RG software version
Tx IP RG Tx interface IP address
LAN IP RG LAN interface IP address
Group Associated group
Monitoring State Hovering over Monitoring state causes the tooltip to display.
RG state:
 V: Active and monitored
 U: Upgrade in progress
 O: Offline
Alert Notification Send an email when the terminal is disconnected.
Receiver ID The type of receiving device controller

Receiver Type The type of receiving device
Channel ID The InterSKY IS-NMS hub allocated channel ID
Channel Type Type of channel
NCC Connection RG connection state
Keep Alive Number of allows unacknowledged keep alive before declaring RG connection
problems
Frequency Central frequency of connected channel
Frequency Offset RG actual frequency Offset
MCD Eb/N0 MCD ratio of Energy per Bit (Eb) to the Spectral Noise Density (No);
refreshes every 10 seconds
DVB Eb/N0 RG ratio of Energy per Bit (Eb) to the Spectral Noise Density (No); refreshes
every 10 seconds
Information Rate Current data rate
Code Rate Forward Error Correction
Tx PWL Current transmit power level
CIR Committed Information Rate (in Kbps)
Peak Rate The max data rate of a channel
SLA Profile Displays the SLA profile attached to this terminal configuration.
Operational Mode InterSKY or SCPC
4.3.1 Restart the Terminal

You can perform a cold reset on the terminal using Restart on the Buttons bar.
To restart the terminal:
1. At the bottom of the Status tab, click . The Buttons bar opens.
2. Click Restart to send a restart command to the terminal device. The restart process can
take several minutes.
3. Click at the bottom of the Status tab to close the Buttons bar.
4.3.2 Telnet
Telnet is available when the IS-NMS client computer can connect to the Remote Data
network, that is, when telnet is working from the command line of the local computer. Refer
to the terminal Installation and Operations Manual for information regarding the terminal
interface during a Telnet session.
To open a telnet session:
1. Click Telnet to open a Telnet client and to create a Telnet session with the device
created.

Figure 96: Telnet Session Login
2. Enter your User Name and password to gain access to the terminal interface. When you
are finished the Telnet session, disconnect and click the diminish button in the upper
right corner of the Telnet session window.
4.3.3 Ping
Ping is available when the IS-NMS client computer can connect to the Remote Data
network, that is, when ping is working from the command line of the local computer.
To Ping:
1. Click Ping to ping the device. The ping continues until the dialog is closed.
Figure 97: Ping Screen
2. Click Close to stop Ping and close the Ping window.
4.4 Terminal Performance

Three reports are available to view performance for one terminal: Outage Table, Outage
Chart, the Inbound/Outbound Throughput Chart, and starting from version 3.41, the
Inbound/Outbound Throughput Summary Report.

The information in the database remains active for 3 months. After that time, the information
is erased. The data is retrievable for up to 30 days in a row by selecting the time frame in the
date filter. A query can be defined in 1-hour resolution.
Report Start and Stop times are relative to the HUB (ISNMS/NCC server) time, no matter
where the web client is running. Therefore, time at the NCC and the IS-NMS must be
synchronized.
4.4.1 Outage Table

The terminal outage presents the outage periods for the terminal within the time frame
defined in the date filter.
To display the Outage Table:
1. Select the terminal on which to report. Select the Performance tab.
Figure 98: Outage Table Report
Graph Type Type of report:
 Outage Table, Outage Graph
 Inbound/Outbound Throughput Graph
 Inbound/Outbound Throughput Summary Report
Show Performance Inclusive report date and time
From  Start date and time (in date format, relative to the hub time)
To  Stop date and time (in date format, relative to the hub time)
2. Click Outage Table from Graph Type.

3. Enter the report From and To dates and times. Click Apply. The report displays in the
working area.

Start Time Outage period start time (in date format, relative to the hub time)
Stop Time Outage period stop time (in date format, relative to the hub time)
Total down time Total outage period in hours, minutes, and seconds
Reason Outage reason:
 Outage
 Power outage
4.4.2 Outage Chart

The Outage Chart displays terminal outage information in graph form.
 Traffic On/Off is displayed as a ―0‖ or a ―1‖.
 The graph displays two lines, one for outage and one power outage.
 The requested graph period is determined by the date filter (in hour resolution).
You can zoom in on a specific area on the graph by clicking and dragging across the target
region. The graph redisplays, zoomed into the selected area. To restore the graph to the
normal view, click and drag from right to left.
Figure 99: Outage Chart Report
To display the Outage Chart:

2. Click Outage Chart from Graph Type.
working area.

Outage Table, Outage Graph
Inbound/Outbound Throughput Graph
Inbound/Outbound Throughput Summary Report
Show Inclusive report date and time
Performance Start date and time (in date format, relative to the hub time)
From Stop date and time (in date format, relative to the hub time)
To
On-Off Traffic On/Off is displayed as a ―0‖ or a ―1‖
Time Outage period (relative to the hub time)
4.4.3 Terminal Inbound/Outbound Throughput

Graph
The throughput graph displays both inbound and outbound traffic for the selected terminal.
 Traffic throughput is measured in Kbps.
 The graph always displays two lines, one for inbound traffic and one for outbound
traffic.
 The requested graph period is determined by the date filter (in hour resolution).
You can export the graph data to CSV or save the picture to a JPEG.
region. The graph redisplays zoomed into the selected area. To restore the graph to the
normal view, click and drag from right to left.
Figure 100: Throughput Chart Report
To display the Throughput Chart:

2. Click Throughput Chart from Graph Type.

working area.
 Outage Table, Outage Graph
 Inbound/Outbound Throughput Graph
 Inbound/Outbound Throughput Summary Report
Throughput Traffic load measured in kbps.
Time Throughput period (relative to the hub time)
4.4.4 Export Terminal Performance Report Data

There are two buttons on the bottom of the report panel: Export CSV and Save JPEG. These
are used to export report data to files.
To export report data as a CSV file:
1. Click Export CSV. The Save dialog opens.
Figure 101: Save CSV Dialog
2. Select the destination folder and enter a file name.

3. Click . The report data is saved to the destination folder as a CSV file.
To export report data as a JPEG file:
1. Click Save JPEG. The Save dialog opens.

Figure 102: Save JPEG Dialog
2. Select the destination folder and enter a file name.

3. Click . The report data is saved to the destination folder as a JPEG file.

IS-NMS Installation & Operation Manual NCC Terminal Groups
5. NCC Terminal Groups
The terminal group node is color-coded according to the aggregated status of the terminal
devices underneath.
Green: terminal devices are connected and monitored

Yellow: terminal devices are connected, but not monitored
Red: terminal devices are not connected
When you roll the cursor over a terminal group node on the tree, a summary of the terminal
group status appears.
5.1 Terminal Group Status

The terminal Group Status displays a table of terminal devices, all configured as members of
the same terminal group. Each row displays one of the terminal device parameters.
The IS-NMS protects the user from system thrashing due to terminal update interrupts. As a
result, there can be discrepancies between the displayed status of the terminals in the tree
view and the displayed status of the terminals in the Group status fields. The tree view
maintains the current status. This feature is especially important when the group contains
many terminals.
When terminals have the same IP address, and are detected by the IS-NMS, the first terminal
is in the correct monitoring state, while the other terminals with the same IP are shown as
Not Monitored.
To view terminal group Status:
 In the Navigation tree, click a specific terminal group node. Click the Status tab. The
status of the selected terminal group is displayed.

Figure 103: Terminal Group Status Display
iRG ID terminal unique ID
Name Name identifier of the terminal
Tx IP terminal Tx interface IP address
Data Rate Current data rate
MCD Eb/N0 MCD ratio of Energy per Bit (Eb) to the Spectral Noise Density (No)
DVB Eb/N0 terminal ratio of Energy per Bit (Eb) to the Spectral Noise Density (No)
Tx PWL Current transmitter power level
Frequency Central frequency of connected channel
Frequency Offset terminal actual frequency Offset
Monitor State terminal state:
I: Idle
X: not monitored
V: Active and monitored
U: Upgrade in progress
O: Offline
CIR The Committed Information Rate (in Kbps)
5.2 Terminal Group Performance

The Performance tab is a tool for reporting outages and monitoring bandwidth utilization.
The main features of this tab include:
 The user can select the report type he wishes to view via the Graph Type option box.
 The user can set the start and end times for the report, and then generate the report by
clicking Apply.
 After the report is generated and displayed, the user can export the data as a CSV or
JPEG file.

To view terminal group Performance:
1. In the Navigation tree, click a specific terminal group node.

2. Click the Performance tab. The performance of the selected terminal group is
displayed.
Figure 104: Terminal Group Performance Display
 BW Utilization Chart
 BW Utilization Table
 Outage Report
 Throughput Chart
MHz or % Performance measurement display
5.2.1 Group Outage Report

The Group Outage Report is a group summary for all the terminals in the group. It describes
the reasons for power outages. There are two reasons for power outages:
 Power Failures: ―ungraceful‖ electrical power outages
 Other: other outage periods that do not result from power failures
Outage data history is retrievable for up to one month. The requested outage period can be
filtered according to dates (one-hour resolution).
To display the terminal Group Outage Report:
1. In the Navigation tree, select the specific group.

2. Select Outage Report. Enter the start and stop report times. Click Apply.

Figure 105: Terminal Group Outage Report
iRG ID terminal unique ID
Power Outages total Total time of outage periods as a result of power failures (in
[minutes] requested timeframe)
Power Outages total [%] Total time of outage periods in percent, as a result of power
failures (in requested timeframe)
Unknown Down [minutes] Total time of outage periods that are not from power failures
(in requested timeframe)
Unknown Down [%] Total time of outages in percent periods that are not from
power failures (in requested timeframe)
Total Down time [minutes] Total amount of outages for a specific terminal (in requested
timeframe)
Total Down time [%] Total amount of outages in percent for a specific terminal (in
requested timeframe)
5.2.2 Group Bandwidth Utilization Table

The BW utilization table displays the channel statistics list.
To display the Group Bandwidth Utilization Table:

2. Select BW Utilization Table. Enter the start and stop report times. Click Apply.

Figure 106: Terminal Group Bandwidth Utilization Table
Time Time stamp when the group parameters were measured
Total BW Total bandwidth allocated to this group
Total CIR Combined total, in MHz, of the CIR assigned to each Remote Gateway within
this group, and the bandwidth of the group‘s access channels (the access
channels‘ CIR equals their bandwidth)
Occupied BW Combined total bandwidth, in MHz, of all the channels in this group (except
traffic channels)
Active CIR Combined total, in MHz, of the CIR assigned to each connected (active)
Remote Gateway within this group, and the bandwidth of the access channels
of the group (access channels‘ CIR equals their bandwidth)
Total CIR The relation, in percent, between the Total CIR, in MHz, and the Total BW, in
MHz
Occupied BW The relation, in percent, between the Occupied BW, in MHz, and the Total
BW, in MHz
Active CIR The relation, in percent, between the Active CIR, in MHz, and the Total BW,
in MHz
Total RG(s) The number of Remote Gateways included in the group
Connected The number of the group‘s Remote Gateways that are currently connected
RGs
5.2.3 Group Bandwidth Utilization Chart

Group Bandwidth utilization charts the total usage of the group over a period of time.
region. The graph redisplays zoomed into the selected area. To restore the graph to the
normal view, double-click outside the graph.
To display the Group Bandwidth Utilization Chart:

2. Select BW Utilization Table. Enter the start and stop report times.
3. Select MHz or % for display. Click Apply.
Figure 107: Terminal Group Bandwidth Utilization Chart
MHz Display utilization in MHz
% Display utilization as a % used
From Date and time to start report
To Date and time to end report
5.2.4 Group Throughput Chart

The throughput for Inbound and Outbound can be displayed for the selected group.
Throughput is an average calculated per hour. As a result, to display the correct throughput
range you must enter a stop time 1 hour more than the desired result. This ensures that the
entire throughput range is correctly displayed.
To display the Group Throughput Chart:

2. Select Group Throughput Chart. Enter the start and stop (1 hour beyond the desired
time) report times. Click Apply.

Figure 108: Group Throughput Summary Report
Throughput Traffic load measured in Mbps
Time Throughput period (relative to the hub time, plus 1 hour to ensure correct
averaging)
5.2.5 Terminal Performance Export

The report data is exported as a file of the type selected. You can save the generated report
as a JPEG image by clicking Save JPEG. A dialog opens and you can select a destination
folder, file name, and type. See ‎Appendix A, System Properties, to configure the format of
the file, with or without titles.
To export as a CSV file:
1. Display a report in the Performance tab.

2. Click Export CSV. A dialog is opens that allows the user to select a folder, file type,
and file name.
Figure 109: Export CSV Save Dialog

3. Enter a file name, file type, and destination folder.

4. Click . The report is saved to the designated file.

IS-NMS Installation & Operation Manual System Administration and VNO Support
6. System Administration and VNO

Support
IS-NMS supports Administration functions to perform basic personnel management and

system access:
 Individual profile access
 Administrator-level access to add new users and configure system parameters
To display the Administration view in the IS-NSM main view, click Admin (upper right, in
line with Filter criteria). The Administration view opens displaying the user tab.
Figure 110: Administration View
Users
A list of users, grouped by level of permission
 Administrator
 System Operator
 System Viewer
 Group Owner
 Group Operator
 Group Viewer
 User

Login Information
 When a specific user is selected, the properties for that user are
presented on the right side of the view. The user may modify them.
 Username is editable only while creating a new user; it cannot be
modified at a later stage.
 The Change Password checkbox allows the user to enter a new
password into the Password and Confirm Password fields.
 The Never Expires checkbox creates a password that never
expires. Otherwise, an expiration date must be entered.
 Typing an IP address into the Hostname field restricts the user to a
specific client station. Trying to login from other IP address
triggers a failed login.
The Lock Account checkbox freezes the user account, Login is
impossible until the checkbox is reset.
Additional Information
 Other user information is configured by entering data in the
Additional Information fields (First and Last name, Department,
Location, Phone Number and email address).
Access
 The Access data fields (Profile, Group, and terminal) are used to
set the user profile (Administrator, System Operator, Group
Owner, Group Operator, and User), and to restrict access (as
required) to a specific group and/or to a specific terminal device.
Note: The Administrator can set a different activity timeout value for each user in
the system. The default timeout is 15 minutes.
6.1 Restricted Access

Access depends on the permissions of the selected user:
 When the user is a system operator, the Group and terminal pull-down menus are not
active.
 When the user is a System Viewer, the InterSKY components are available for viewing;
no parameters can be changed.
 When the user is restricted to a specific group (Group Owner, Group Operator, or User),
the group option box displays the list of configured terminal groups.

Figure 111: Group Restriction Menu
 When the user is a Group Viewer, the group configuration is available for viewing; no
parameters can be changed.
 When the user is restricted to a specific terminal device in addition to restriction to a
specific terminal group, the terminal option box displays the list of configured terminal
devices under the selected terminal group.
Figure 112: Terminal Restriction Menu
6.2 IS-NMS VNO Model

A Virtual Network Operator (VNO) is an NMS that has been partitioned to enable network
management capability only to those return links assigned to the specific VNO. The
Network Operator or Administrator manages the overall shared hub as well as defining the
degree of network management capability given to each VNO.
The optional VNO feature allows InterSKY shared hub service providers to manage
different groups of return links as if they were in separate networks.
 The VNO serves as a hosted MCD in the Network Operator‘s shared hub.
 Group Owner privileges are granted to the Group Administrator. This allows the Group
Administrator to provide network management capability to his customers, restricted to
their applicable sites, bandwidth, and status.
 Administration simplifies the process of setting the correct User permissions and
parameters for a Group Owner.
The Administrator can allocate and change the license settings, however the total amount of
allocated licenses cannot exceed the total purchased user licenses amount. The Administrator
is responsible for guaranteeing that the total number of allocated licenses does not exceed
the total purchased licenses.
When license number is not defined for a certain group, users belong to these groups get
licenses from a common pool with the following constraints:
 Customer can have up to 50 users logged in.
 There can be up to 20 users belong to Group1 logged in simultaneously.
 There can be up to 10 users belong to Group2 logged in simultaneously.

 No user from QPSK_1M_Rest4 can log in.

 There can be up to 20 users from the rest of the group logged in simultaneously.
Figure 113: VNO Configuration
Groups define in the HUB Value

Group 1, Group 2, 8PSK 0.5M, Group type. When checked, the group is
cal 8PSK 0.5M, Cal_8PSK_1M, allocated the number of licenses entered
in the box to the right of the checkbox.
Sash, QPSK_1M_Rest4,
QPSK_2M_rest8, 8PSK_1M,
A value of 0 indicates that users of the
8PSK_2M_A, 8PSK_2M_B
selected group cannot login.
License to allocate Display only field reflects the remaining

number of available licenses in the
system.
The remaining unassigned licenses are
equally distributed on the unchecked
groups.
6.3 IS-NMS Profiles System

The IS-NMS Profiles system determines what can be accessed on the Administration view,
by users with various permission levels.
 Administrator: Administrator users can view all system users, view profile definitions,
add/delete/modify all system users and configure system parameters.
 System Operator: System operators can view and modify their own properties and may
not change their restriction. They are restricted adding, configuring, and modifying
InterSKY components.
 System Viewer: System Viewers can only display their own properties. They are
restricted viewing InterSKY components.
 Group Owner: Group owners can view, add, delete, and modify group operator users
and simple users. The group owner user is restricted to a specific group. All of the users
are restricted automatically to the same group.

 Group Viewer: Group Viewers can only display group operator users and simple users.
The group viewer user is restricted to a specific group.
 System Operator/Group Operator/User: System operators, group operators, and
simple users can only view and modify their properties. They are restricted to a group or
to a terminal device and may not change their restriction.
6.3.1 User Profile

The Profiles tab displays the different profile permissions. The view is available only for
System Administrators. From this tab, the administrator can select one profile from the list
on the left side and view the profile permissions.
Figure 114: Profiles
6.3.2 Administrator Profile

The System Administration tab is used by System Administrators to configure IS-NMS
system parameters. It can only be opened by a System Administrator.
Figure 115: System Administration

From this tab, the System Administrator user can:

 Modify the database URL, Username, Password by entering new values in the
Application Database data fields.
 Modify the maximum events table size and the backup path for old events, via the
General parameters fields.
 Save the new settings by clicking Apply.
6.3.3 System Operator Profile

System operator profile allows the System Operator full operation on all hub elements. The
System Operator is not allowed to create new IS-NMS accounts or to change IS-NMS
configuration related parameters like database parameters (username, passwords, URL, etc.).
The System Operator licenses are the sum of the System Operator, Limited System
Operator, and Basic System Operator.
Two new System Operator types have been added to IS-NMS v2.25.5:
 Limited System Operator: has all the ability of the System operator without the ability
to perform multiple terminal upgrade and multiple Drop & Insert tasks.
 Basic System Operator: has all the ability of the System operator without the ability to
add and remove hub devices, and the ability to perform multiple terminal upgrade and
multiple Drop & Insert tasks.
6.3.4 System Viewer Profile

System viewer profile allows the System Operator full view of all hub elements. The System
Viewer is not allowed to change any element parameters, create new IS-NMS accounts, or to
change IS-NMS configuration related parameters.
Note: When the system is in Manual Refresh mode, the System Viewer cannot
perform a refresh. Consequently, the System Viewer might not see the
current system status.
6.3.5 Group Owner Profile

The Group Owner is able to see the following:
 When in the Remote view, a group owner sees only the group and the associated
terminal devices.

Figure 116: Group Owner Remote Network
 When in the Network view, a group owner sees only the Group Configuration screen.
Figure 117: Group Configuration, Group Owner
6.3.6 Group Operator Profile

The Group Operator profile allows full operation on all elements (terminals) in its group.
The Group Operator cannot assign new accounts to the terminals in its group.
6.3.7 Group Viewer Profile

The Group Viewer profile can display all elements (terminals) in its group. The Group
Viewer cannot assign new accounts to the terminals in its group.
Note: When the system is in Manual Refresh mode, the System Viewer cannot
perform a refresh. Consequently, the Group Viewer might not see the
current group status.

6.3.8 User Profile

The User is able to see the following:
 When in the Remote view, the user sees only the restricted terminal device.
Figure 118: Remote User
 When in the Network view, the terminal view is not available to User-level users.
6.4 Managing IS-NMS Accounts

Administrators can add, delete, and modify IS-NMS accounts. Group Owners can add,
delete, and modify user accounts specific to the group.
6.4.1 Adding a New IS-NMS Account

To add a new IS-NMS account:
1. Click New User (at the bottom of the screen). The New User dialog opens.
2. Select the Profile of the new user to be added: Administrator Account, System Operator
Account, System Viewer Account, Group Owner Account, Group Operator Account,
Group Viewer Account, or User Account.

Figure 119: New User Account
3. Enter the appropriate user details in the fields provided.

4. Click Apply.
6.4.2 Deleting an IS-NMS Account

You can delete an IS-NMS account.
To delete an IS-NMS account:
1. In the Navigation tree, select an existing user.

2. Click .
3. In the confirmation dialog, confirm that you wish to approve the deletion of the selected
user.
6.4.3 Modifying an IS-NMS Account

You can modify an IS-NMS account.
To modify an existing IS-NMS account:
1. In the Navigation tree, select an existing user. The properties for that user are displayed
in the main work area to the right of the Network tree.
2. Enter modifications to the user details in the property fields.
3. Click Apply. The modifications are saved.

6.5 First Time Login

First time login to the system includes the following general requirements:
 The user account must first be created by Administrator/Group Owner.
 Every user is required to change his password as part of the first login session.
To login to the system for the first time:
1. Enter the Username and default Password provided by the user who has created the
account.
Figure 120: Login Dialog
2. Click Login.
3. Once the session has been authenticated, enter a New Password in the Change Password
dialog.
Figure 121: Change Password Dialog
4. Confirm the New Password.

5. Click . Your Password is modified.
6. Click Contin… to login.
Figure 122: Change Password Dialog (2)

6.6 Database Backup and Recovery

The IS-NMS enables you to backup and recover information stored in the IS-NMS database.
When backing up the database, all information from the database is saved into external files.
At a later time, the database can be restored from these files. The backup and recovery
processes are performed by backup and restore routines.
6.6.1 Database Backup Routine

The database backup routine performs the following actions:
1. The structure of the database and data stored in small tables is saved into the file called
backup.sql. Every time the backup routine runs, this routine creates a new backup.sql
and overwrites the previous copy of this file.
2. For each big table (irgperfthroughputvalues, irgperfoutage, perfstatisticstablerow),
a separate file is created. These files contain data gathered for the last 24 hours. File
names contain a table name and the date when the file is created. For example,
06012009_outageBackup.dmp contains data from the irgperfoutage table for
01/06/2009.
3. Analysis of the most important tables that have an impact on the overall IS-NMS
performance takes place.
When the backup routine runs for the first time, the routine creates the DB_Maintenance.log
file in the Maintenance folder. All subsequent backup routines add logs to the existing log
file.
Installation of the database backup routine only can be done manually.
6.6.2 Database Restore Routine

The database restore routine performs the following actions:
1. The structure of the database and data stored in small tables are restored as defined in
backup.sql which is stored in the Maintenance folder.
Note: Because backup.sql contains SQL commands for creating the database and
all relevant tables, when the restore routine is run for an existing database,
messages notifying that a table already exists can be displayed.
2. Big tables are restored. If a table already exists, the error message notifying that the table
already exists can be displayed. These error messages are written to DB_Restore.log file.
3. Data stored in big tables is restored. The restore routine insert data from *outage*.dmp‖,
―*perf*.dmp, and *statistic*.dmp files stored in the backup_folder to the tables.
When you want to restore files that contain data for a specific period only, delete the files
from which data should not be manually restored.
When the database restore routine runs for the first time, the routine creates the DB_
Restore.log in the Maintenance folder. All subsequent restore routines add logs to the
existing log file.

6.6.3 Database Backup/Recovery Routines

Configuration
The database backup routine is performed by the file called DBMaintenance.bat. This file
automatically starts as a Windows task.
You can manually edit DBMaintenance.bat in the following cases:
1. Location in which backup files are stored is changed (for example, when backup files
are stored on an external storage device).
2. Default time period of stored files needs to be changed.
The database recovery routine is performed by the file called RestoreDB.bat. When you
want to recover the database, you can start this file manually.
DBMaintenance.bat and RestoreDB.bat have a configuration section. This section
contains the configuration parameters as shown in the following table:
Parameter Default Value

backup folder C:\Program Files\Shiron NMS\Maintenance\Files
db backup folder C:\\Program Files\\Shiron NMS\\Maintenance\\Files\\
backup_storing_time 30 (days)
Note: When a location or name of the folder in which backup files are stored is
changed, both the backup folder and db backup folder parameters must be
changed. Note that the path defined in the db backup folder parameter must
contain double back slashes. Both parameters must point to the same folder.
To change a default time period for historical backup storage, you can
specify another value in the backup storing time parameter. These
parameters can only be modified manually.

IS-NMS System Properties
Appendix A System Properties

The system.properties file contains information relevant to the installation of IS-NMS. The
IS-NMS server must be restarted when the system.properties file is modified.
1. The HTPS protocol on the server is designated by httpsServerPort. There is no reason to
change this parameter.
httpsServerPort=443
2. The MySQL database is configured with three parameters. There is no reason to change
these parameters. Note that the database User name is ―shiron‖ and the default password
is ―shiron‖.
# Data Data base
dataDatabaseUsername=shiron
dataDatabasePassword=w066hZiMpn0\=
dataDatabaseUrl=jdbc\:mysql\://localhost\:3306/shiron
3. The security database is configured with three parameters. There is no reason to change
these parameters. Note that the database User name is ―shiron‖ and the default password
is ―shiron‖.
# Security Data base
securityDatabaseUsername=shiron
securityDatabasePassword=w066hZiMpn0\=
securityDatabaseUrl=jdbc\:mysql\://localhost\:3306/shiron
4. Even and Audit table cleaners are IS-NMS specific.

The generateAlarms flag, when true, enables the alarms set by the System Administrator
(see the NCC and MCDC Operations Manuals, Settings, Traps tab).
evnetsTableThresh is the number of events allowed in the table before the system begins
deleting the oldest messages.
# Event & Audit tables cleaners parameters
generateAlarms=true
evnetsTableThresh=50000
auditTableThresh=10
5. The ―.csv‖ files can be exported with or without columns names. When the flag is
―false‖, no column names are exported.
# CSV files export with/without column names
addTitleToCsvFiles=false
# Limiting the Outage report only to not restricting users
limitedOutage=true
6. Extended Group Display effects the information displayed in the Navigation tree (see
3.7 Extended Group Display).
# Remote view group bar (amount of iRGs) presentation:
# true: (idle + alive)/monitored; false: monitored
extendedGroupBar=true

7. The IS-NMS can either automatically update the NCC with any changes or let the NCC
commit the changes.
True: any change the IS-NMS does to the NCC is committed immediately. The NCC
database is updated and the new values are immediately available.
False: the NCC decides to commit itself. A ―get‖ command potentially results in old
values because the changes are not immediately committed to the local NCC database.
# Immediate committing any change in the NCC database
commitNccUpdates=true
8. Terminal polling parameters are controlled here. The flags shown here are the default
terminal flags. All devices can be controlled by creating specific device flags and giving
unique names. For example, you can create NCC control flags by replacing ―IRG_‖ with
―NCC_‖. Other controllable devices include the MCDC and the IPE.
―device‖_SNMPRetries specifies the number of times to try polling the device after
failure.
―device‖_SNMPTimeout is the time to wait when the device does not answer.
# Devices polling parameters (possible prefixes IRG_, NCC_, MCDC_,
IPE_)
IRG_SNMPRetries=1
IRG_SNMPTimeout=5000
IRG_SNMPConCurrentGetReq=1000
IRG_SNMPConCurrentSetReq=500
9. Active polling, activePollingInterval, is the rate at which the device is polled during
normal system operation. Inactive polling, inActivePollingInterval, is the rate at which
the device is polled when it is not active. These parameters become important when the
device is online and active or it has gone offline and is inactive. To poll an inactive
device at the active rate is a waste of resources.
These parameters depend on the hub size, recommendation values appears in
system.properties file.
Once the inactive device is back in operation, and the system discovers its presence,
polling reverts to the active polling rate.
# Polling intervals in seconds
activePollingInterval=60
inActiveLongPollingInterval=900
10. When a device is polled and it does not respond, this parameter indicates the number of
failed polls the system tolerates before deciding that the device has a problem. At that
time the polling rate switches from activePollingInterval to the inactive polling rate,
inActivePollingInterval.
# Unsuccessful polling threshold
inActivePollingThreshold=5
# If true, SNMP polling of NCC's user table will be done only to

changed users
11. When polled, the device can send a full set of data or it can send the delta changes.
When deltaPolling is true, only the changes are sent. When deltaPolling is false, the full
information set is sent.
# Pay attention that "3.31 build 2" NCC is needed for it !!!

deltaPolling=true
12. The number of threads to open for polling is restricted by pollerThreadPool. An increase
in open threads results in an increase in resource usage.
For example, when there are 10,000 terminals in the system, this value can be increased
to 3000-4000. A 100 terminals in the system may only need 10.
Increase this value only when the system is very large.
# Thread pool size for SNMP requests
pollerThreadPool=1000
# Infrastructure thread pool parameters:

# number of threads to keep in the pool, even if they are idle.
corePoolSize=5
# maximum number of threads to allow in the pool.
maximumPoolSize=25
13. IsClientGroupNotify defines refreshing on client‘s group screen.

14. smtpServer defines the address of the SMTP Server that will handle event notification
emails from IS-NMS.
15. defaultReceipient defines the email address to which event notification emails will be
sent.
16. The session can time out according to the sessionTimeoutMinutes property. Two
conditions relate to the session timeout.
 If sessionTimeoutMinutes is missing, a default timeout is 15 minutes.
 If sessionTimeoutMinutes is defined as less than 5 minutes, it is ignored and
minimal timeout of 5 minuted is used instead.

IS-NMS IS-NMS Installation
Appendix B IS-NMS Installation

The IS-NMS is based on the Windows XP Operating System. When upgrading an existing
installation, contact the technical support group to verify that your servers are powerful
enough to handle the new operating system and software. In addition, an upgrade may
require new licenses.
The installation conforms to the Microsoft Windows installation format. The windows
displayed point out unusual or non-standard choices. Otherwise, the normal installation
window is not displayed in the text.
At any time during the installation, click Cancel to cancel the installation. Click Back to
retrace the previous installation step.
Prerequisites
The IS-NMS, NCC and MCDC servers must be configured according to the IS-NMS
Maintenance specifications.
Before attempting to run the IS-NMS Server, make sure you have the following:
 Operating System: Microsoft Windows XP/2003 or later
 Java Virtual Machine (JVM): Sun Java SE 1.6.0.03 and above.
 TCP port: Verify that the TCP port 3306 is opened in Windows Firewall (this port is
used for connection to MySQL server).
 InterSKY: InterSKY software version is 3.31 build 2 or above.
Before attempting to run the IS-NMS Client, the following hardware and software
requirements must be met:
 IS-NMS Client Hardware Specifications:
 Memory: 1GB
 Disk: 2GB of free disk space
 Fast Ethernet (100M) Interface
 Display resolution 1024 x 768 and above
 IS-NMS Client Software Specifications:
 Operating System: Microsoft Windows XP/2003 or later, must be in English
 Web Browser: Microsoft Internet Explorer 6.5 or later
 Java Virtual Machine (JVM): Sun Java SE 1.6.0.03 and above
 IS-NMS Server hardware (IS-NMS Server Types):
 Small IS-NMS server: up to 2000 concurrent users (terminals)
 Medium IS-NMS server: up to 5000 concurrent users (terminals)
 Large IS-NMS server: up to 10000 concurrent users (terminals)

Each SNMP response requires 1.072 Kbps. Minimal Bandwidth for connection client to IS-
NMS Server is:
 32 Kbps for Upload
 750 Kbps for Download
Installation
The IS-NMS installation is on a clean environment. There are no previous installations of
the IS-NMS and MySQL Server.
Note: Do not perform any action in the IS-NMS until the

'activeuserstatustablerow' is not created;
Make sure that all accompanied patches (if any) are also installed by during
its installation procedure (detailed in separate patch release notes
document).
Warning: The operating system must be in English.
Installation Stages
Installation on a clean environment process consists of the following stages:

 MySQL Installation
 Installing the Database Backup Routine
 Post-Installation
 Creating Network Hierarchy Components
When using non-defaults values in system.properties file (located under \Shiron NMS
folder), save this file to external location before starting the uninstall process.
Note: Changing the system.properties file requires restart of the IS-NMS server.
IS-NMS Installation
This section describes the IS-NMS installation process.
1. Run the Shiron_NMS_windows_2_26_xxx.exe execution file.

Figure 123: Install Wizard Welcome
2. Click Next. Select the destination directory in which the application is to be installed.
3. Click Next. Select the MySQL checkbox (checked by default). Click Next.
Figure 124: Installation Setup
4. Select the size of the system.

 Select Medium when the number of terminals is up to 5,000.
 Select Large when the number of terminals is up to 10,000.

Figure 125: Installation System Size Selection
Click Next. The Windows Services dialog opens.

5. Select the Start Menu destination folder for the program‘s shortcuts. Click Next. The
Windows Services dialog opens.
6. Choose the details of how the services are to be installed:
 Install service ―Shiron NMS Service‖ (using the default name)
 Automatic start on boot-up
Figure 126: Installation Window Services
7. Click Next. The NMS files are extracted and copied. This operation usually takes about
1 to 2 minutes.

MySQL Installation
After installing the My SQL database, and after the IS-NMS software installation finishes,
the database installer automatically starts running. This section explains the MySQL
installation process.
Figure 127: MySQL Server Setup Welcome
1. Click Next. Select the database installation type. The default is Typical.
Figure 128: MySQL Setup Type
2. Verify the Install Confirmation information Click Next. The Ready to Install the
Program window is displayed.

Figure 129: MySQL Ready to Install
3. Login to create the new MySQL account. The Setup Wizard completion screen opens.
4. Select Configure the MySQL Server now. Click Finish. The MySQL Server Instance
Configuration Wizard opens.
Figure 130: MySQL Installation Complete
5. Click Next. The Configuration type selection window opens.

Figure 131: MySQL Server Instance Configuration
6. Select Detailed Configuration and click Next. The Server Type selection screen opens.
Figure 132: MySQL Configure Server
7. Select the Server Machine and click Next. The Database Usage selection screen opens.

Figure 133: MySQL Multifunctional Database
8. Select the Multifunctional Database Usage and click Next. The (destination) Drive
selection screen opens.
Figure 134: MySQL InnoDB Tablespace Settings
9. Select the drive for the InnoDB data file and click Next. The Concurrent Connections
definition screen opens.
10. Set the number of concurrent connections to the server and click Next. The Networking
Options definition screen opens.

Figure 135: MySQL Decision Support
11. Set the networking options and click Next. The Default Character selection screen
opens.
Figure 136: MySQL Enable Network Options
12. Select the default character-set and click Next. The Windows options definition screen
opens.

Figure 137: MySQL Enable Character Set
13. Set the Windows options and click Next. The Security Options definition screen opens.
Figure 138: MySQL Enable Window Options
14. Enter the root password: shiron and retype the password to confirm; then click Next.
The MySQL Server Instance Configuration prepares to execute.

Figure 139: MySQL Enable Security Options
15. Click Execute. The MySQL Server Instance Configuration process displays its progress.
Figure 140: MySQL Ready to Execute
16. Click Finish. The Database Installation prompt opens. When the database installation is
complete, click Next.

Figure 141: MySQL Installation Complete
Installing the Database Backup Routine

1. From the Windows Start menu, select Control Panel→Scheduled Tasks.
2. If the Analyze job exists (this job is installed by the previous 2.23 version), delete this
job.
3. From the File menu, select New→Scheduled Task. Name the new task DBMaintenance
and click Enter.
4. Right-click on DBMaintenance and select Properties.
5. On the Task tab, under the Run field, click Browse. The Browse dialog box displays.
6. Locate DBMaintenance.bat. By default, the file is stored in
<IS-NMS installation folder>\Maintenance\. Click Open.
7. In the Start in field, enter the full path of the Maintenance subfolder of the IS-NMS
installation path (<IS-NMS installation path>\Maintenance).
8. Click the Schedule tab.
9. In the Schedule Task drop-down list, select Daily.
10. In the Start time field, select the desired time (e.g. 2:00 A.M).
11. Click Apply and OK.
12. Enter the password (usually: ‗ISNMSLpass‘) and confirm >> OK.
13. Verify that mysql.exe is accessible in the System PATH variable.
In the Windows command line, enter the following command:
echo %PATH%.
If not, right click My Computer→Properties→Advanced→Environment

Variables→ Path→Edit. Copy the mysql.exe path to the system variable path.
14. To verify that the newly created task is valid, in the Scheduled Tasks window, right
click DBMaintenance and select Run. After this operation is complete, the

Maintenance folder contains a file called DB_Maintenance.log. This file contains a

complete maintenance operation log.
Note: IS-NMS installation path is by default: C:\Program Files\Shiron NMS
15. Run the script Update_SR_Grid_Standard.bat. By default, the script is stored in

<IS-NMS installation folder>\Maintenance\.
Post-Installation
1. The system.properties file must be modified. Stop the NMS service.
2. Make a backup copy of the system.properties file.
3. Open system.properties and scroll down to the bottom of the file:
httpsServerPort=443
# Data Data base

dataDatabaseUsername=shiron
dataDatabasePassword=w066hZiMpn0\=
dataDatabaseUrl=jdbc\:mysql\://localhost\:3306/shiron
.
.
.
# Project name (some functionality will be only for given project)
# projectName=TRPC
4. Remove the ―#‖ from the line # projectName=TRPC.

5. Save the system.properties file.
6. Open and snmp session.
7. Send this command to the router:
Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.

Router(config)# snmp-server community public RO
8. To configure the OptimISe SNMP, use the following commands:

Snmp set rw community public
Snmp set rwhosts <IS-NMS address>
9. Restart the NMS Service.

10. Verify that all accompanied patches, if any, are installed.
(See a separate patches release notes document for additional details).
Creating Network Hierarchy Components

Create hub devices according IS-NMS Operator Manual (Chapter ‎3 Network ).
Note: Do not perform any action in the IS-NMS user interface until the groups in
the CSMS get their updates.

IS-NMS SNMP Service and Traps
Appendix C SNMP Service and Traps

InterSKY 3.30 and higher support the generation of SNMP traps. The Trap generator is
implemented in both the NCC and the MCDC.
Using the traps tab, MCDC and NCC operators determine the communication settings with
the trap server, the different group of traps to generate, and the performance monitor
thresholds in which to generate a performance trap.
The manufacturer recommends configuring the ghost SNMP Services and Traps at the same
time as the Main SNMP.
Configure SNMP Services

To configure SNMP Services:
1. Select My Computer→Manage→Services and Applications.

2. Right-click SNMP Services. Click Properties. The SNMP Service Properties (Local
Computer) window opens.
Figure 142: SNMP Service Properties
3. Change the Startup type to Disabled. Stop the service.

4. Click the Security tab.

Figure 143: SNMP Service Properties
5. Add or Edit Community Rights to be READ CREATE and Community Name to

public.
6. Check Accept SNMP packets from any host. Click OK.
Configure SNMP Traps

To configure SNMP Traps
1. For NCC and MCDC (masters and slaves) and IS-NMS servers, select My
Computer→Manage→Services and Applications. Right-click SNMP Trap Service.
Click Properties.
Figure 144: SNMP Trap Service
2. Click the General tab.

3. Change Startup type to Disabled. Stop the service.
Note: It is recommended to add it to the ghost. Restart the servers after changes.
Configure Traps
To configure Traps
1. Open Settings from the IS-NMS main menu.
Figure 145: Configure Traps
2. Select the Traps tab.

3. Change Traps Destination Address to the IS-NMS IP address.

Figure 146: Enable Trap Messages
4. Select the Logger tab.

5. Check the Trap combo-box to send Trap messages.

IS-NMS Initialize IS-NMS Server
Appendix D Initialize IS-NMS Server

After installing the IS-NMS, you can launch the IS-NMS server:
 Automatically as a Windows service
When IS-NMS is installed as a Windows service, no manual operation is required. The
server loads and starts running immediately after installation. To stop and restart the
server, you must use the Control Panel→Administrative Tools→Services view.
Furthermore, the IS-NMS server starts automatically any time Windows boots without
any need to manually login.
 Manually as an application
When IS-NMS is installed as an application, the IS-NMS server only starts after a user
command from the Windows Start menu.
Figure 147: IS-NMS running as Windows Service
By default, the IS-NMS server is configured to start automatically. However, you can choose
to start manually from the Windows Services view. The differences are as follows:
 While running as a service, the status Started displays in the Services view.
 While running as an application, a log window displays the log records.
IS-NMS Client
To start the IS-NMS client:
1. Run the web browser application and direct the browser to the IS-NMS server URL. The
URLs are as follows:

IS-NMS Initialize IS-NMS Server
 When the IS-NMS server port value is left as the default (HTTPS default TCP port -
443), the IS-NMS server URL is
https://<IS-NMS server IP address>/html/shiron.html.
 When the IS-NMS server port value is not the default, the URL is
https://<IS-NMS server IP address>:<port>/html/shrion.html.
The IS-NMS client loads from the IS-NMS server to the client machine. The Login
dialog box opens.
2. Enter your Username and Password.
Figure 148: IS-NMS Client Login
Note: The Hostname field displays the IP address of the IS-NMS server. The Port
field displays the port in use (443 by default or different if modified).
3. Click Login. The login values are sent to the IS-NMS server for verification. All
Client/Server traffic is encrypted via an HTTPS session.
Alternatively, click Cancel to close the IS-NMS client. The Login dialog box closes and
the web browser is redirected to an empty page.
4. Following login, one of three outcomes occurs in the system:
 Successful Login
When the login parameters (Username and Password) are verified by the IS-NMS
server, the login dialog box closes and the IS-NMS main screen opens.
 User Verification Fails
When the login parameters fail verification (wrong Username and/or Password), an
error message appears at the bottom of the login dialog box. You may attempt to
login again. If login fails three times, the IS-NMS client closes, the Login dialog box
closes, and the web browser is redirected to an empty page.
 Number of Allowable Users Exceeded
When the number of logged in users has reached the maximum allowed (by the
license key or by the configured maximum number of sessions), the login fails and
the user is notified.

IS-NMS Terms and Abbreviations
Appendix E Terms and Abbreviations
Acronym Term Explanation

AC Access Channels Secondary login channels in FDMA groups and the primary
login channel in non-FDMA groups.
ACM Adaptive Coding Assures highest DVB availability.
and Modulation
AFC Automatic Controls the frequency of the signal. This control enables the
Frequency Control NCC to ensure both power and bandwidth efficiency.
APC Automatic Power Allows the NCC to adjust the transmitted power level of the
Control Remote Gateway to an optimal value.
ARP Address Resolution Protocol
ARU ATM Reassembly Receives IP packet fragments, encapsulated in ATM cells,
Unit from the MCD. The ARU reconstructs the original IP packets
and sends them to the IP Forwarding Units.
AUPC Automatic Uplink Assures that DVB power is controlled at all times
Power Control
BM-FDMA Burst Mode Frequency division multiple access
BoD Bandwidth on A feature that enables fixed-size space segments to be
Demand assigned to a customer, and the allocation of a space segment
and data rate that matches a customer's momentary needs.
BUC Block-Up Converter A solid state power amplifier that is part of the ODU
BW Bandwidth A measure of the width of a range of frequencies, measured
in hertz
CC Clear Channel Communications channel on which only one transmitter
operates at a time.
CIR Committed The minimum guaranteed rate of transmission
Information Rate
CSV Comma Separated Text format for data files
Values
CW Clear Way Modulation used in X-Poll test
DAMA Demand Assign A technique that increases the amount of users that a limited
Multiple Access "pool" of satellite transponder space can support.
DR Data Rate Data rate, in kilobits per second (Kbps), of the channel.
DRA Dynamic Random Supports connectivity for 100% of the system users even
Access during extreme load conditions. When the system is required
to support a number of remote gateways at very low rates, it
dynamically allocates bandwidth for random access channels.
DVB-2/2S Digital Video Open standards for distribution digital data.
Broadcasting
(Satellite)


Dynamic Dynamic Burst Mode Frequency division multiple access
BM-FDMA
Eb/N0 Bit Energy to Noise Ratio
FDMA Frequency division Division of the frequency band allocated for wireless cellular
multiple access telephone communication into 30 channels, each of which
can carry a voice conversation or, with digital service, digital
data.
FEC Forward Error Data redundancy factor in the bit stream.
Correction
FLSS Forward Link Responsible for the encapsulation, transmission and
Subsystem reliability from the hub to the remote terminals. It is made up
of the AUPC, VCM and ACM.
GBW Group Bandwidth
Group Every terminal group is allocated a return channel bandwidth that is shared by
members of the group. The NCC uses the Group parameter, along with MIR, CIR and
Priority, to determine allocation of resources.
Hybrid Terminals communicate using the hub and amongst themselves.
Mesh
Network
HTTPS Hypertext Transfer Protocol over Secure Socket Layer
IDU InterSKY Indoor This is the terminal.
Unit
IF Intermediate The frequency to which a carrier frequency is shifted as an
Frequency intermediate step in transmission or reception.
InterSKY The NCC can only control a Remote Gateway that is in InterSKY mode. The NCC
mode only operates in InterSKY mode.
IPE The essential link between the hub LAN and the transmission equipment;
encapsulates IP data in DVB packets.
IP The connection between the receiver and the central LAN. It sends IP packets
Forwarding received from the ARU to their destinations.
Units
IS-NMS InterSKY Network Management System (See NMS)
ksps Kilo symbols per second
LNB Low-Noise Block Low noise amplification and down conversion from KU- and
C-band to L-band. This is part of the ODU.
MCD Multi-Channel A system and method for performing the digital receive
Demodulator processing for multiple signals received over the same RF
band
MCDC Multi-Channel Device to control multiple MCDs
Demodulator
Controller
Mesh Terminals communicate amongst themselves bypassing the hubs.
Network
MIR Minimum Information Rate
MODCOD Modulation and coding


MPLS Multi Protocol Label A data-carrying mechanism that belongs to the family of
Switching packet-switched networks.
NCC Network Control Maintains control over the RLSS and the bandwidth
Center allocation of the terminals.
NMS Network Network management involves auto polling of network
Management devices and workstation generation of real-time graphical
Systems views of network topology changes and traffic. The network
monitor is a service that assists human network managers in
monitoring and maintaining networks.
ODU Outdoor Unit Outside equipment for the terminals. This is made up of the
BUC and LNB.
PAMA Pre-Assigned VSATs are pre-allocated a designated frequency. Equivalent
Multiple Access of the terrestrial leased line, PAMA solutions use the satellite
resources constantly, making them ideal for interactive data
applications or high traffic volumes.
PEB Power Equivalent Bandwidth
PID Packet ID Used to identify audio/video streams in DVB "Digital Video
Broadcasting".
PIR Peak Information Rate
Priority When resources are scarce, the priority parameter establishes which Remote Gateway
is given the return channel bandwidth.
QoS Quality of Service
QPSK Quadrature Phase A phase modulation algorithm where the phase of the carrier
Shift Keying wave is modulated to encode bits of digital information in
each phase change.
RA Random Access
RFT RF Terminal — located on the ODU
RG ID Remote Gateway identification
RLSS Return Link Responsible for received signals from the terminals to the
Subsystem hub.
SCPC Single channel per A Remote Gateway in SCPC mode can communicate with the
carrier (SCPC) satellite but not the NCC. In this mode the NCC is not aware
of the Remote Gateway.
Session A session is a connection of the NMS client to the NMS server.
SLA Service Level A set of QoS Policy Rules
Agreement
SNMP Simple Network Management Protocol
SQL Structured Query Language
TC Traffic Channels The primary login channels in FDMA groups; Traffic
Channels do not exist in a system that only uses MCDs.
TDM Time Dimension A type of digital or (rarely) analog multiplexing in which two
Multiplexing or more signals or bit streams are transferred, apparently
simultaneously, as sub-channels in one communication
channel, but physically are taking turns on the channel.


THSS Traffic Handling The interface between the InterSKY baseband equipment and
Subsystem the outside world.
TNMA Traffic Network Management Agent
TRC Transmission Rate A control algorithm that kicks in when all attempts to
Control increase signal power due to rain fade have been exploited. In
order to maintain connection, the NCC automatically
decreases channel bandwidth. Decreasing channel bandwidth
frees more power in order to successfully handle rain fade.
UC User Channel
UI User Interface
VCM Variable Coding and Changes encoding parameters in real time.
Modulation
VLAN Virtual LAN A group of hosts with a common set of requirements that
communicate as if they were attached to the same wire,
regardless of their physical location. A VLAN has the same
attributes as a physical LAN, but it allows for end stations to
be grouped together even if they are not located on the same
LAN segment.
VNO Virtual Network operator
VSAT Very Small Aperture A 2-way satellite ground station with a dish antenna that is
Terminal smaller than 3 meters.


SHIRON IS-NMS User Guide 5.1

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

SHIRON IS-NMS User Guide 5.1

Uploaded by

Copyright:

Available Formats

InterSKY Network Management

IS-NMS Installation & Operation Manual

©2007-2011 Proprietary and Confidential Page 2 of 149

About this Manual

©2007-2011 Proprietary and Confidential Page 3 of 149

©2007-2011 Proprietary and Confidential Page 4 of 149

©2007-2011 Proprietary and Confidential Page 5 of 149

©2007-2011 Proprietary and Confidential Page 6 of 149

Figure 49: Cisco Router Configuration .............................................................................................. 55

©2007-2011 Proprietary and Confidential Page 7 of 149

Figure 99: Outage Chart Report ....................................................................................................... 100

©2007-2011 Proprietary and Confidential Page 8 of 149

©2007-2011 Proprietary and Confidential Page 9 of 149

1. Elbit-Shiron InterSKY IS-NMS

Figure 1: InterSKY System

©2007-2011 Proprietary and Confidential Page 10 of 149

1.1 IS-NMS Environment

Figure 2: InterSKY™ Hub Hierarchy

©2007-2011 Proprietary and Confidential Page 11 of 149

 Managing device agent response to all poll requests

©2007-2011 Proprietary and Confidential Page 12 of 149

1.2 Inbound and Outbound

1.2.1 Multi Channel Demodulator Controller

Multi-Channel Demodulator (MCD)

©2007-2011 Proprietary and Confidential Page 13 of 149

ATM Reassembly Unit (ARU)

1.2.2 Network Control Center (NCC)

1.2.3 IP Encapsulator (IPE)

©2007-2011 Proprietary and Confidential Page 14 of 149

1.2.5 Cisco Router

©2007-2011 Proprietary and Confidential Page 15 of 149

©2007-2011 Proprietary and Confidential Page 16 of 149

Figure 3: IS-NSM Browser Window

©2007-2011 Proprietary and Confidential Page 17 of 149

2.1 View Selection

2.2 Menu Bar

Figure 4: Menu Bar

Figure 5: About IS-NMS

©2007-2011 Proprietary and Confidential Page 18 of 149

©2007-2011 Proprietary and Confidential Page 19 of 149

 System Viewer: restricted to view of network components within InterSKY

To view the Admin functions:

1. Click on the Menu bar.

Figure 6: Administration Navigation Tree

SLA Profile Scheduler

©2007-2011 Proprietary and Confidential Page 20 of 149

Figure 7: Terminal Search Dialog

To search by terminal Name:

1. Click in the upper left-hand corner of the Main window.

Figure 8: Terminal Name Search Results

To search for a specific terminal by ID:

1. Click in the upper left-hand corner of the Main window.

©2007-2011 Proprietary and Confidential Page 21 of 149

Figure 9: iRG ID Search Results

To search by terminal Tx IP address:

1. Click in the upper left-hand corner of the Main window.

To search by terminal LAN IP address:

1. Click in the upper left-hand corner of the Main window.

©2007-2011 Proprietary and Confidential Page 22 of 149

2.2.4 Log Out

appears in the upper right panel, next to and . Click to

2.3 Navigation Tree

2.3.1 Network View

The System node is the root.