SHIRON IS-NMS Installation & Operation Manual 2.25
SHIRON IS-NMS Installation & Operation Manual 2.25
This publication contains proprietary information belonging to Elbit Systems-Land and C4I-Tadiran-
Shiron SATCOM Business Line. The information is supplied solely for the purpose of assisting explicitly
and properly authorized users of the 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 and C4I-Tadiran-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 and C4I-Tadiran-Shiron SATCOM Business Line reserves the right to alter the
equipment specifications and descriptions in this publication without prior notice.
© 2007-2010 Elbit Systems-Land and C4I-Tadiran-Shiron SATCOM Business Line, all rights reserved.
Elbit-Shiron, Shiron and InterSKY are trademarks of Elbit Systems-Land and C4I-Tadiran-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.
Audience
This manual is intended for use by Elbit-Shiron certified technicians with experience in
installing components of the InterSKY™ system.
References
• RLSS Installation and Operation Manual v3.42
• FLSS Installation and Operation Manual v3.42
• iRG Professional Series Installation and Operation Manual v3.42
• iRG Compact Series Installation and Operation Manual v3.42
• InterSKY NCC Operation Manual v3.42
• Drop&Insert Operation Manual
Table of Contents
1. Benefits of IS-NMS ............................................................................................................ 11
1.1 IS-NMS Environment .................................................................................................... 12
1.2 Inbound and Outbound .................................................................................................. 14
1.2.1 IP Encapsulator (IPE) ......................................................................................... 14
1.2.2 Multi Channel Demodulator Controller (MCDC) .............................................. 15
1.2.3 Network Control Center (NCC) .......................................................................... 15
2. IS-NMS New Features ....................................................................................................... 16
3. IS-NMS Browser ................................................................................................................ 17
3.1 View Selection ............................................................................................................... 18
3.2 Menu Bar ....................................................................................................................... 18
3.2.1 Help ..................................................................................................................... 18
3.2.2 Tools ................................................................................................................... 18
3.2.3 Search.................................................................................................................. 20
3.2.4 Log Out ............................................................................................................... 24
3.3 Navigation Tree ............................................................................................................. 24
3.3.1 Network View ..................................................................................................... 24
3.3.2 Remote View ...................................................................................................... 24
3.3.3 Add and Delete ................................................................................................... 25
3.3.4 Common Functions ............................................................................................. 25
3.4 Central Monitoring ........................................................................................................ 26
3.5 Work Area ..................................................................................................................... 27
3.6 Last Critical Events........................................................................................................ 27
3.6.1 Filtering InterSKY Events .................................................................................. 29
3.6.2 Event Log and Audit Enhancement .................................................................... 30
3.7 Extended Group Display................................................................................................ 31
4. Network Hub ...................................................................................................................... 33
4.1 Hub Creation.................................................................................................................. 35
4.2 InterSKY Hub Display .................................................................................................. 35
4.3 Hub Deletion.................................................................................................................. 36
4.4 Inbound .......................................................................................................................... 37
4.4.1 NCC .................................................................................................................... 38
4.4.2 NCC Groups ....................................................................................................... 44
4.4.3 MCDC ................................................................................................................. 48
4.5 Outbound ....................................................................................................................... 51
4.5.1 IP Encapsulator ................................................................................................... 52
5. InterSKY Remote Gateway .............................................................................................. 55
5.1 iRG Configuration ......................................................................................................... 56
5.1.1 iRG Configuration Enhancements ...................................................................... 61
5.1.2 Cross Polarization Test ....................................................................................... 62
5.1.3 Drop&Insert ........................................................................................................ 65
5.1.4 Migration ............................................................................................................ 68
5.1.5 Owner Information ............................................................................................. 70
5.1.6 Upgrade ............................................................................................................... 70
5.2 iRG Networking Feature................................................................................................ 73
5.2.1 Basic.................................................................................................................... 74
5.2.2 SkyX Accelerator ................................................................................................ 74
List of Figures
Figure 1: Elbit-Shiron InterSKY System ........................................................................................... 11
Figure 2: InterSKY™ Hub Hierarchy ................................................................................................ 12
Figure 3: IS-NSM Browser Window ................................................................................................. 17
Figure 4: Elbit-Shiron Menu Bar ....................................................................................................... 18
Figure 5: About IS-NMS.................................................................................................................... 18
Figure 6: Administration Navigation Tree ......................................................................................... 20
Figure 7: iRG Search Dialog.............................................................................................................. 21
Figure 8: iRG Name Search Results .................................................................................................. 21
Figure 9: iRG ID Search Results........................................................................................................ 23
Figure 10: Network Navigation Tree ................................................................................................. 24
Figure 11: Remote Navigation Tree................................................................................................... 25
Figure 12: Add and Delete ................................................................................................................. 25
Figure 13: Central Monitoring ........................................................................................................... 26
Figure 14: Current Channel Information ........................................................................................... 27
Figure 15: Last Critical Event Bar ..................................................................................................... 27
Figure 16: Last Critical Event with Message ..................................................................................... 27
Figure 17: Events and Notifications................................................................................................... 28
Figure 18: Ack. Column and Details ................................................................................................. 29
Figure 19: Filter Dialog...................................................................................................................... 29
Figure 20: Extended Group Display .................................................................................................. 32
Figure 21: Not Extended Group Display ........................................................................................... 32
Figure 22: System Properties ............................................................................................................. 32
Figure 23: Network View with no Hubs ............................................................................................ 34
Figure 24: Network View with a New Hub ....................................................................................... 34
Figure 25: New Hub Dialog ............................................................................................................... 35
Figure 26: Add New NCC ................................................................................................................. 35
Figure 27: Network Hub .................................................................................................................... 36
Figure 28: Delete Dialog .................................................................................................................... 36
Figure 29: Inbound for a Specific Hub .............................................................................................. 37
Figure 30: Add New NCC device ...................................................................................................... 38
Figure 31: NCC Configuration (associated groups are hidden) ......................................................... 39
Figure 32: Expanded NCC Buttons Bar ............................................................................................. 40
Figure 33: NCC Satellite Configuration ............................................................................................ 41
Figure 34: Add New Satellite............................................................................................................. 41
Figure 35: NCC Bandwidth Configuration ........................................................................................ 43
Figure 36: Add New Bandwidth ........................................................................................................ 44
Figure 37: Delete Bandwidth ............................................................................................................. 44
Figure 38: Add New NCC Group Dialog .......................................................................................... 45
Figure 39: NCC Group Configuration ............................................................................................... 45
Figure 40: NCC Group Owner Details .............................................................................................. 48
Figure 41: Add New MCDC dialog ................................................................................................... 49
Figure 42: MCDC Configuration ....................................................................................................... 50
Figure 43: MCDC view of the MCDs and ARUs .............................................................................. 51
Figure 44: Outbound view for a Specific Hub ................................................................................... 52
Figure 45: Add New IPE Device ....................................................................................................... 53
Figure 46: IPE Configuration............................................................................................................. 54
Figure 47: Remote Navigation Tree................................................................................................... 55
Figure 48: Four iRG Tabs .................................................................................................................. 56
1. Benefits of 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.
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). Elbit-Shiron combined AUPC
and ACM into a proprietary, patented AUPC & AMC Controller (AAC) to provide total
rain-proofing for InterSKY versions 3.41 and higher. The Remote Gateway to Hub is rain
proofed based on Elbit-Shiron 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 v3.51 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.
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.
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).
The InterSKY hub performs the functions of traffic routing, bandwidth assignments,
transmission to the satellite and network management.
The IPE encapsulates IP data into DVB packets. The IPE links together the InterSKY 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.
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.
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.
3. IS-NMS Browser
The four functional areas of the IS-NMS browser provide entry to all the IS-NMS
capabilities:
• View Selection
• Elbit-Shiron Menu Bar
• Navigation Tree
• Work Area
• Last Critical Events
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, and the IPE.
Display all the iRGs in the system. The view must be Remote to add,
modify, or delete an iRG.
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.
3.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).
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.
3.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 Elbit-Shiron and
can be changed by Elbit-Shiron 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 iRG; restricted to configuration and
view of the associated iRG, restricted to own account modification
• Group Operator: associated with more than one iRG, restricted to configuration and
view of group defined iRGs, restricted to own account modification
• Group Owner: associated with more than one iRG, restricted to configuration and view
of group defined iRGs, restricted to group account creation and modification
• Group Viewer: associated with more than one iRG, restricted to view of group defined
iRGs
• 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 iRG 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 iRG
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
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.
See Chapter 7 System Administration and VNO Support for information regarding system
accounts.
3.2.3 Search
Use the IS-NMS search feature to search for an iRG device and to qualify the search
according to the iRG name, iRG ID, group name, TX IP, LAN IP, and status. Searching by
iRG Name conforms to Microsoft Windows use of ‘*’ and ‘?’ to search for full or partial
iRG Names.
The procedure for searching for an iRG by Name is nearly identical to that of searching by
iRG ID. The only difference is the definition of the Search Filter criteria.
Parameter Description
iRG Name Name associated with a specific iRG
iRG ID ID number associated with a specific iRG
Group Name Group to which the iRG belongs. The group is comprised of like-service
iRGs
Tx IP IP address of the transmitter
LAN IP LAN IP address
Status Status of the iRG:
• Active: green, active and monitored
• Not Active: red, not active and monitored
• Not Monitored: yellow, (unknown status)
• Idle: Lime green, responding to SNMP but does not appear in an
active table
• Upgrade: blue, upgrade in process
2. Select the iRG 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 iRG ID, enter the iRG ID in the From: field. Leave the To: field
blank.
4. Click (to the right of the Filter criteria). The results display in the iRG Search
Result window according to the iRG ID.
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 iRG Search Results display according
to the Tx IP addresses.
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 iRG Search Results display according
to the LAN IP addresses.
The Network view displays all Hubs, Inbound devices, and Outbound devices.
and from the Navigation View create and remove an element in the
network or remote topology.
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 .
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.
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
parameter name turns red. The Save button is disabled.
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 iRGs in a group, and the number of active, idle, inactive, upgrade, and not
monitored iRGs associated with the group.
Starting with IS-NMS v2.25.5 the current Channel information for all groups of a given
satellite are displayed when Remote view is selected and the satellite is clicked.
The work area changes according to the current system function. For example, when doing a
search on an iRG, 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.
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.
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.
The Last Critical Events feature provides a filtering mechanism that allows the user to define
complex filtering criteria.
1. Click (at the bottom of the Last Critical Events table). The Filter dialog
opens.
Parameter Description
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
Indication Alarm bar 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.
In IS-NMS v2.25.5 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 iRG
• Remove iRG
• Change iRG Min Eb/No
• Change iRG Max Eb/No
• Change iRG Min Power Level
• Change iRG Max Power Level
• Upgrade iRG
• Cancel Upgrade iRG
• X-Poll Start
• X-Poll Stop
• Drop & Insert operation
• Multiple Upgrade
• Multiple Drop & Insert
• Logout
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 iRG in the group.
• Extended (default): displays the groups in the Navigation tree with the Group icon,
Group name, and the number of monitored iRGs in the group / the number of iRG in the
group.
Figure 20: Extended Group Display Figure 21: Not Extended Group Display
4. Network Hub
IS-NMS supports a hierarchical view of the entire local network, including all components:
• Hub view
• Inbound for specific hub
NCC for specific inbound
MCDC for specific inbound
• Outbound for specific hub
IPE 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.
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.
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.
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.
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.
All inbound and outbound devices are displayed under a specific hub node.
1. Select .
2. From the local network tree, click the specific hub node for display. The hub view
appears in the working area.
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
A hub can be deleted from the InterSKY system at any time. When there are elements
associated with the hub, the elements must first be deleted.
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.
4.4 Inbound
IS-NMS allows you to display inbound devices (only) for a specific hub 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 inbound node for display. The inbound view appears in the working
area.
Parameter Description
Label Device name (30 character maximum)
IP Address IP address of the device
Status Status of the device
• Green: Active, connected
• Yellow: Slave, redundant, connected
• Red: Not Active, disconnected
4.4.1 NCC
The NCC is responsible for data control functions in the InterSKY 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.
4. Click . The new device is added to the topology and appears in the Navigation
Tree.
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.
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.
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:
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.
3. Enter the name of the satellite and the transponder ID from the Satellite provider.
1. In the Network tree, select the active NCC. Open the Satellite Configuration tab.
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:
To add a bandwidth:
1. In the Network tree, select the active NCC. Open the Satellite Configuration tab.
2. Click Add Freq. in the button bar. The Add new bandwidth dialog opens.
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 .
3. Confirm that you want to delete this bandwidth or click to cancel the delete.
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.
6. Click located near the middle of the screen. The NCC group
owner details window is displayed.
7. Enter a Phone, E-Mail, and Address for the new NCC Group. Click .
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 .
1. Remove all the elements (bandwidth/iRGs) 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.
4.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.
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:
To delete an MCDC:
Parameter Description
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 iRGs, 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
4.5 Outbound
Configuration of the outbound devices for the InterSKY 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.
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.
4.5.1 IP Encapsulator
The IP Encapsulator (IPE) encapsulates IP data into DVB packets. The IPE is an essential
link between the InterSKY 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 modify an IPE:
1. Click Inbound under the selection hub. Click the IPE. The IPE configuration window is
displayed.
To delete an IPE:
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 InterSKY hub.
The Remote view is displayed by clicking on the main window. The tree changes
to present all the configured iRG 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 iRG groups are presented (third level).
• Under each group, all the configured iRG devices are presented (fourth level).
The iRG device node is color-coded by iRG device connection status and according to the
configured monitor state:
• Green: iRG device is connected and monitored
• Yellow: iRG device is not monitored
• Red: iRG device is not connected
• Blue: iRG device is in an upgrade process
• Lime Green: iRG is idle
To open iRG Device view, click a specific iRG device node on the Remote tree. Three or
four tabs appear across the top of the configuration window, depending on the InterSKY
version.
• iRG Status
• iRG Configuration
• iRG Network (v3.40 and higher)
• iRG Performance
In addition, the tool bar displays the iRG name (and IP address), the iRG group name and
the iRG status (Active, Disconnected, Not Monitored, Idle, In Upgrade).
To add an iRG:
2. Click (located on the bottom of the tree view). The Input dialog opens
prompting you to select a name for the new iRG.
3. Enter a name and click . The Input dialog closes and the iRG Configuration
screen opens.
4. Configure the parameters for the iRG device. For IS-NMS v2.25.5 and higher, the LAN
and PID information can be entered on the iRG Configuration screen.
5. Click to save the parameter values. Click to terminate the session
without creating the new iRG.
To modify an iRG:
1. From the Remote tree, select a specific iRG. The work area fills with the iRG status
window (the default) and the specific iRG status displays across the top of the
configuration.
To delete an iRG:
• 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 iRG and displayed
on the iRG configuration page.
During Cross-Poll, the iRG can be in either InterSKY mode (for iRG versions 3.41 and
above) or SCPC mode.
During the Cross Polarization test the iRG transmitter parameters are configured on the
Cross Poll window. From the Cross Poll window you can:
• Send Cross Poll parameters to the iRG transmitter via the FLSS (using SNMP protocol).
• Send a modulation free (CW) signal from iRG 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 (only in v3.41 and higher).
When Cross Poll is performed in InterSKY mode, the iRG 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 iRG. When
the transmitter is turned on due to Cross Poll testing, closing the dialog window causes the
iRG 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.
1. From the iRG Configuration window click . The Cross Poll sub-screen
opens for the selected iRG. The IS-NMS automatically changes the iRG’s priority to
“Deferred”.
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.
5.1.3 Drop&Insert
Drop&Insert facilitates quick deployment of multiple iRGs with maximum control and
minimum field expertise. Configuration files for specific iRGs are created and saved at the
Hub site, transferred to the field engineering laptop, taken to the remote site, and quickly
loaded into the iRG. 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 Elbit-Shiron Drop&Insert Operation Manual.
From the Drop&Insert sub-screen, the user can set either one or many iRG parameters for
the iRG. 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 iRGs only. To update other IP addresses, such as the
IP address of the IPE, you must use the iRG Configuration Screen.
1. From the iRG Configuration tab, click Drop&Insert. The Drop&Insert sub-screen
opens for the selected iRG.
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.
3. Select one or more iRG devices and groups from the System tree at the left of the screen.
4. Click Open. The Drop&Insert screen opens.
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 iRG devices.
Click Load to load an existing saved configuration from the iRG configuration file.
Click to save the (edited) configuration currently displayed to the iRG
configuration file.
Click Send to send all parameters currently configured on the Drop&Insert screen to
all selected iRG devices.
5.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 iRG 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.
1. From the iRG Configuration tab, click Drop&Insert. The Drop&Insert sub-screen
opens for the selected iRG.
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.
Owner Information is a set of text windows to enter and save contact information about the
owner.
1. From the Remote tree, select an iRG group. The iRG Configuration screen opens.
2. Click Owner Details. The Owner Details window opens for the selected iRG.
5.1.6 Upgrade
You can upgrade a specific group of iRGs or one specific iRG from the IS-NMS.
To upgrade an iRG:
1. In the lower left corner of the iRG Configuration page, click Upgrade. The Choose
Upgrade version window is displayed.
The current iRG 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 iRG are listed.
2. From the Available version list, select the version to which to upgrade the selected iRG.
3. Click Start. The iRG 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 iRG, click the Configuration tab. Monitoring Status displays a blue U and the
iRG icon in the Navigation window turns blue.
1. Right-click to open the menu of commands and select Multiple Versions Upgrade.
2. Select one or more iRG devices and groups from the System tree at the left of the screen.
Use Shift+cursor click to select a sequence of iRGs. Use Ctrl+cursor click to select
individual iRGs.
The iRGs must be the compatible to be upgraded together. For example, you want to
upgrade several iRGs to v3.40. However, one of the selected iRGs can only be upgraded
to v3.31 while the other selected iRGs can be upgraded to v3.40. This situation causes
an error.
3. Click Upgrade. The Available versions screen opens.
No current version is displayed since there are multiple and potentially different iRGs
begin upgraded at one time. Select the version to which to upgrade.
4. Click Start. The selected iRG 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.
When this happens, you must eliminate from the upgrade process any iRG that is not
compatible with the selected version or select a different upgrade version. Then restart
the upgrade process.
The iRG Networking tab is available only for iRGs of InterSKY version 3.40 or higher.
When an iRG of a lesser version is selected the iRG Networking tab is not displayed. After
InterSKY v3.40 the Networking tab supports version specific topics:
• Basic networking parameters
• InterSKY v3.40, v3.41, and v.3.42: SkyX Accelerator
• InterSKY v3.41 and above: QoS and Static Routing Table
• InterSKY v3.42 and above: NAT and VLAN support
5.2.1 Basic
Starting with the IS-NMS v2.25.5, the Networking tab has a new section called Basic. Use
this section to enter LAN and PID information. For systems older than IS-NMS v2.25.5 the
LAN and PID information is found on the Configuration tab.
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 SkyX Protocol overcomes these limitations of TCP/IP by transparently intercepting
TCP/IP data and converting it to the SkyX Protocol, a transport protocol specially optimized
for data transmission over satellites. The SkyX Protocol is used only for the transfer of data
between both sides of the satellite link: the SkyX Server on the Hub side and the SkyX
Client of the iRG side. The clients and servers continue to use standard TCP/IP for
communications with the SkyX 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 SkyX 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 SkyX Accelerator client in the iRG. The SkyX Accelerator
increases the amount of data carried over the link, accelerates Web applications, and speeds
large file transfer response times.
3. To update the screen to the actual device parameters, click . The device is
polled and the new values are displayed.
The iRG 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 an iRG 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 iRG is configured either at the iRG 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.
1. Click the arrow next to Static Routes. The window expands to the route type selection.
Parameter Description
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
3. To update the screen to the actual device parameters, click . The device is
polled and the new values are displayed.
4. To change a route status, select the Active box.
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 iRG, for a total 100% usage. The QoS Status indicator
appears to the right of the subnet definitions when at least one subnet is defined.
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.
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.
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.
Parameter Description
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.
Parameter Description
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.
Parameter Description
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
3. Enter the new values.
4. Click to save the new parameters. Click to cancel this session.
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.
Parameter Description
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
3. Enter the new values.
4. Click to save the new parameters. Click to cancel this session.
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 creation support starts in InterSKY v3.42 on the iRG 4G model only, and 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 starting with InterSKY version 3.30.
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 an IRG 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.
restores the previously defined settings.
causes the defined settings to be saved to the database and also reports to the IRG
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 IRG.
If this validation fails, no definitions are sent to IRG and error message is displayed.
Parameter Description
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:
5. To update the screen to the actual device parameters, click . The device is
polled and the new values are displayed.
5.2.6 NAT
Network Address Translation (NAT) support starts with iRG v3.42. 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 an iRG, 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 iRG that sits between an internal network and the rest of the world.
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.
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.
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)
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.
Parameter Description
Enable NAT This radio button enables or disables both Dynamic and Static
NAT settings for selected IRG. 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
bitmask being 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.
Note: Hovering the mouse over any valid NAT entry (Static or Dynamic) causes a display
of the range for IP addresses belonging to the subnet.
Parameter Description
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
bitmask being 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
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 .
The iRG status view displays information on the selected iRG by clicking the Status tab.
Parameter Description
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
Parameter Description
Monitoring Hovering over Monitoring state causes the tooltip to display.
State RG state:
• I: Idle
• X: not monitored
• V: Active and monitored
• U: Upgrade in progress
• O: Offline
Alert Send an email when the iRG is disconnected.
Notification
Receiver ID The type of receiving device controller
Receiver Type The type of receiving device
Channel ID The InterSKY Hub allocated channel ID
Channel Type Type of channel
Connect Status RG connection state
Keep Alive Number of allows unacknowledged keep alive before declaring RG
connection problems
Frequency Central frequency of connected channel
Frequency RG actual frequency Offset
Offset
MCD Eb/No MCD ratio of Energy per Bit (Eb) to the Spectral Noise Density (No);
refreshes every 10 seconds
DVB Eb/No RG ratio of Energy per Bit (Eb) to the Spectral Noise Density (No);
refreshes every 10 seconds
Data Rate Current data rate
Code Rate Forward Error Correction
Tx PWL Current transmit power level
CIR Committed Information Rate (in Kbps)
Max Rate The max data rate of a channel
You can perform a cold reset on the iRG using Restart on the Buttons bar.
1. At the bottom of the Status tab, click . The Buttons bar opens.
2. Click Restart to send a restart command to the iRG device. The restart process can take
several minutes.
3. Click at the bottom of the Status tab to close the Buttons bar.
5.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 iRG Installation and Operations Manual for information regarding the iRG interface
during a Telnet session.
1. Click Telnet to open a Telnet client and to create a Telnet session with the device
created.
2. Enter your User Name and password to gain access to the iRG interface. When you are
finished the Telnet session, disconnect and click the diminish button in the upper right
corner of the Telnet session window.
5.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.
Three reports are available to view performance for one iRG: 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.
The iRG outage presents the outage periods for iRG within the time frame defined in the
date filter.
Parameter Description
Graph Type Type of report:
• Outage Table, Outage Graph
• Inbound/Outbound Throughput Graph
• Inbound/Outbound Throughput Summary Report (v3.40 and
above)
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.
Parameter Description
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:
• Starting in v3.31 the two valid reasons are outage and power
outage.
• Before v3.31 the two valid reasons are outage and unknown.
Parameter Description
Graph Type Type of report:
Outage Table, Outage Graph
Inbound/Outbound Throughput Graph
Inbound/Outbound Throughput Summary Report (v3.40 and above)
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)
The throughput graph displays both inbound and outbound traffic for the selected iRG.
• 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.
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.
Parameter Description
Graph Type Type of report:
• Outage Table, Outage Graph
• Inbound/Outbound Throughput Graph
• Inbound/Outbound Throughput Summary Report (v3.40 and
above)
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
Throughput Traffic load measured in kbps.
Time Throughput period (relative to the Hub time)
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.
6. iRG Groups
The iRG group node is color-coded according to the aggregated status of the iRG devices
underneath.
When you roll the cursor over an iRG group node on the tree, a summary of the iRG group
status appears.
The iRG Group Status displays a table of iRG devices, all configured as members of the
same iRG group. Each row displays one of the iRG device parameters.
The IS-NMS protects the user from system thrashing due to iRG update interrupts. As a
result, there can be discrepancies between the displayed status of the iRGs in the tree view
and the displayed status of the iRGs in the Group status fields. The tree view maintains the
current status. This feature is especially important when the group contains many iRGs.
When iRGs have the same IP address, and are detected by the IS-NMS, the first iRG is in
the correct monitoring state, while the other iRGs with the same IP are shown as Not
Monitored.
• In the Navigation tree, click a specific iRG group node. Click the Status tab. The status
of the selected iRG group is displayed.
Parameter Description
iRG ID iRG unique ID
Name Name identifier of the iRG
Tx IP iRG Tx interface IP address
Data Rate Current data rate
MCD Eb/No MCD ratio of Energy per Bit (Eb) to the Spectral Noise Density
(No)
DVB Eb/No iRG 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 iRG actual frequency Offset
Offset
Monitor State iRG state:
I: Idle
X: not monitored
V: Active and monitored
U: Upgrade in progress
O: Offline
CIR The Committed Information Rate (in Kbps)
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.
Parameter Description
Graph Type Type of report:
• BW Utilization Chart
• BW Utilization Table
• Outage Report
• Throughput Chart
MHz or % Performance measurement display
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)
The Group Outage Report is a group summary for all the iRGs 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).
Parameter Description
iRG ID iRG unique ID
Power Outages total Total time of outage periods as a result of power failures
[minutes] (in 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)
Parameter Description
Total Down time [minutes] Total amount of outages for a specific iRG (in requested
timeframe)
Total Down time [%] Total amount of outages in percent for a specific iRG (in
requested timeframe)
Parameter Description
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)
Parameter Description
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
RGs connected
Group Bandwidth utilization charts the total usage of the group over a period of time.
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, double-click outside the graph.
Parameter Description
MHz Display utilization in MHz
% Display utilization as a % used
From Date and time to start report
To Date and time to end report
Starting with IS-NMS v3.41 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.
Parameter Description
Throughput Traffic load measured in Mbps
Time Throughput period (relative to the Hub time, plus 1 hour to ensure
correct averaging)
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.
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 iRG) 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 iRG device.
Note: Starting with IS-NMS v2.25.5 the Administrator can set a different activity timeout
value for each user in the system. The default timeout is 15 minutes.
• 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 iRG device in addition to restriction to a specific
iRG group, the iRG option box displays the list of configured iRG devices under the
selected iRG group.
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 modular design of the InterSKY hub enables a wide range of possibilities for
policing outbound bandwidth. The InterSKY hub configuration enables the network
operator to maximize statistical traffic gains resulting from a common bandwidth pool
on the outbound carrier shared by all Users and VNOs.
• The optional QoS Manager allows the network operator to dedicate separate bandwidth
partitions of the DVB carrier to each VNO or User.
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.
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 an iRG device and may not change their restriction.
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.
System operator profile allows the System Operator full operation on all InterSKY 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 iRG 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 iRG upgrade and
multiple Drop & Insert tasks.
System viewer profile allows the System Operator full view of all InterSKY 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.
• When in the Network view, a group owner sees only the Group Configuration screen.
The Group Operator profile allows full operation on all elements (iRGs) in its group. The
Group Operator cannot assign new accounts to the iRGs in its group.
The Group Viewer profile can display all elements (iRGs) in its group. The Group Viewer
cannot assign new accounts to the iRGs 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.
• When in the Network view, the iRG view is not available to User-level users.
Administrators can add, delete, and modify IS-NMS accounts. Group Owners can add,
delete, and modify user accounts specific to the group.
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.
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.
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.
1. Enter the Username and default Password provided by the user who has created the
account.
2. Click Login.
3. Once the session has been authenticated, enter a New Password in the Change Password
dialog.
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.
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.
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:
To run Update_SR_Grid.sql
2. Click OK.
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
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. iRG polling parameters are controlled here. The flags shown here are the default iRG
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
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. This is only available for NCC v3.31 and higher.
# 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 iRGs in the system, this value can be increased to
3000-4000. A 100 iRGs 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
C.1 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 (iRGs)
Medium IS-NMS server: up to 5000 concurrent users (iRGs)
Large IS-NMS server: up to 10000 concurrent users (iRGs)
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
C.2 Installation
The following IS-NMS installation options are available:
Installation Use this installation when…
Installation on a Clean Environment There are no previous installations of the IS-NMS
and MySQL Server.
Upgrading to a New IS-NMS Version IS-NMS is already installed, and you want to
upgrade to a new version.
Complete Removal of the Previous You want to clean up the environment upon which
Installation and Installation on Clean the IS-NMS and MySQL Server were previously
Environment installed before the new installation.
The following sections explain each of these installation types in detail.
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.
For InterSky v3.40b5 and before, or for 3.40b6 when the flag is off, use the old DR Grid.
After the installation process do the following steps:
• Stop the IS-NMS Server.
• Copy the files OldDRGrid.bat and Old_DR_Grid.sql into the Maintenance folder.
• Run the script OldDRGrid.bat.
• Start the IS-NMS Server.
For InterSky InterSky 3.40b6 when the flag is on or InterSky 3.42 and above use the new
DR Grid. After the installation process do the following steps:
• Stop the IS-NMS Server.
• Copy the files NewDRGrid.bat and New_SR_Grid.sql into the Maintenance folder.
• Run the script NewDRGrid.bat.
• Start the IS-NMS Server.
When you want to completely remove the current installation before installing the IS-NMS
and MySQL Server, the installation process consists of the following stages:
• Pre-Installation, section C.2.5.1
• IS-NMS Uninstall, section C.2.5.4
• MySQL Uninstall, section C.2.5.6
• IS-NMS Installation, section C.2.5.2
• MySQL Installation, section C.2.5.5
• Installing the database backup routine, section C.2.5.7
• Post-Installation, section C.2.5.8
• Creating Network Hierarchy Components, section C.2.5.9
The stages of installation are described in this section. Each section relates back to the
previous types of IS-NMS installation.
C.2.5.1 Pre-Installation
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.
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.
7. Click Next. The NMS files are extracted and copied. This operation usually takes about
1 to 2 minutes.
2. Click Next. Select the destination directory in which the application is to be installed.
3. Click Next. Uncheck the MySQL checkbox (checked by default).
4. Click Next.
5. Select the Start Menu destination folder for the program’s shortcuts. Click Next. The
Windows Services dialog opens.
6. Select the details of how the services are to be installed:
7. Click Next. The NMS files are extracted and copied. This operation usually takes about
1 to 2 minutes.
1. Click Next. Select the database installation type. The default is Typical.
2. Verify the Install Confirmation information Click Next. The Ready to Install the
Program window is displayed.
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.
6. Select Detailed Configuration and click Next. The Server Type selection screen opens.
7. Select the Server Machine and click Next. The Database Usage selection screen opens.
8. Select the Multifunctional Database Usage and click Next. The (destination) Drive
selection screen opens.
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.
11. Set the networking options and click Next. The Default Character selection screen
opens.
12. Select the default character-set and click Next. The Windows options definition screen
opens.
13. Set the Windows options and click Next. The Security Options definition screen opens.
14. Enter the root password: shiron and retype the password to confirm; then click Next.
The MySQL Server Instance Configuration prepares to execute.
15. Click Execute. The MySQL Server Instance Configuration process displays its progress.
16. Click Finish. The Database Installation prompt opens. When the database installation is
complete, click Next.
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.
echo %PATH%.
When the system is upgraded to work with the new DR Grid, run the script:
Update_SR_Grid_Standard.bat. By default, the script is stored in
<IS-NMS installation folder>\Maintenance\.
C.2.5.8 Post-Installation
1. In case the customer has a non-defaults values in ‘system.properties’ file and you saved
it to external location before uninstall process:
Copy the non-default values to the new ‘system.properties’ files.
Restart Elbit-Shiron NMS Service.
2. Verify that all accompanied patches, if any, are installed.
(See a separate patches release notes document for additional details).
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.
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.
1. Run the web browser application and direct the browser to the IS-NMS server URL. The
URLs are as follows:
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.
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.