NETWORK MANAGEMENT SYSTEM

Transcription

1 USER GUIDE AND OPERATIONS MANUAL SOFTWARE RELEASE 3.4 [UHP.NMS.34.EN] MAY 2017

2 CONTENT ACRONYMS AND ABBREVIATIONS... 4 INTRODUCTION... 6 Required Qualifications... 6 Document Version and Applicability... 6 Copyright SYSTEM OVERVIEW General Information Purpose Architecture Composition Installation Supported Modes of Operation and Limitations Preparation for use Licensing Powering On Initialization of the Server System Login Connection of the NMS to UHP Network Initial Configuration of UHP Controllers Objects of NMS Control Remote Stations Hub Controllers Network Virtual Network Operator Operations User Interface Dashboard and Navigation Charts Events Log Reports NMS Statistics Networks Maintenance Backup and Recovery Software Upgrade of Stations Licenses UHP Networks Inc 2

3 3.2.7 User Log Settings NMS User Accounts Scheduler Setup Booking API FIGURES Figure 1 Structure of UHP manuals... 6 Figure 2 Connection of the NMS... 8 Figure 3 UHP NMS interface Figure 4 Booking window UHP Networks Inc 3

4 ACRONYMS AND ABBREVIATIONS NAME 16APSK 32APSK 8PSK ACM AGC API BCH BUC Bandwidth C/N Carrier CCM COTM CRTP DAMA Data transmission Data rate DSCP DVB ES Eb/No EIRP ETSI FEC Frame Frame plan Hard priority HTTP Hub Hubless HW ICMP IESS IF IFL IGMP Inroute IP JSON LDPC DESCRIPTION 16 Amplitude and Phase-shift keying or Asymmetric Phase-shift keying, (APSK), is a digital modulation scheme that conveys data by changing, or modulating, both the amplitude and the phase of a reference signal (the carrier wave). 32 Amplitude and Phase-shift keying or Asymmetric Phase-shift keying, (APSK), is a digital modulation scheme that conveys data by changing, or modulating, both the amplitude and the phase of a reference signal (the carrier wave). 8 Phase-shift keying (8PSK) is a digital modulation scheme that conveys data by changing, or modulating, the phase of a reference signal (the carrier wave). Adaptive Code and Modulation (ACM) allows matching of the modulation and coding to the conditions on the radio link Automatic Gain Control. Application Programming Interface used by NMS to communicate with external software products BCH code is a multilevel cyclic variable-length digital error-correcting code used for correcting multiple random error patterns. BCH codes may also be used with multilevel phase-shift keying whenever the number of levels is a prime number or a power of a prime number. Block Up-Converter (BUC) is used in the transmission (uplink) of satellite signals. It converts a band (or "block") of frequencies from a lower frequency to a higher frequency. Bandwidth is the difference between the upper and lower frequencies in a continuous set of frequencies. Carrier-to-noise ratio, often written as CNR or C/N, is the signal-to-noise ratio (SNR) of a modulated signal. Carrier is a waveform that is modulated with an input signal for the purpose of conveying information. Constant coding and modulation. DVB-S2 mode when MODCOD is not changed during channel operation. Communication on the move Compressing IP/UDP/RTP Headers for Low-Speed Serial Links. Demand Assigned Multiple Access. Channel establishment on demand. Data transmission. Data (bit) rate is the number of bits that are conveyed or processed per unit of time. Differentiated Services Code Point (DSCP) is a 6-bit field in the header of IP packets for packet classification purposes. DSCP replaces the outdated IP precedence, a 3-bit field in the Type of Service byte of the IP header originally used to classify and prioritize types of traffic Digital Video Broadcasting (DVB) is a suite of internationally accepted open standards for digital television. Earth station Eb/No (the energy per bit to noise power spectral density ratio) is a normalized signal-to-noise ratio (SNR) measure, also known as the SNR per bit. Effective Isotropically Radiated Power The European Telecommunications Standards Institute (ETSI). Forward error correction (FEC) is a system of error control for data transmission, whereby the sender adds redundant data to its messages, also known as an error-correction code. Digital data transmission unit (consequence of packets) of fixed length and periodicity. TDMA service packet describing which station should transmit in which time slot. Method of transmission queues handling when packets from lower priority queue are not transmitted until all packets from higher priority queue are transmitted. Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. Central Station of satellite network that is managing all the stations and resources. Special mode of operation when all stations are transmitting to one TDMA carrier and all receiving this carrier. Hardware. The Internet Control Message Protocol (ICMP) is used by networked devices to send error messages indicating, for instance, that a requested service is not available or that a host or router could not be reached. Intelsat Earth Station Standards Intermediate Frequency is a frequency to which a carrier frequency is shifted as an intermediate step in transmission or reception. Connection from the indoor equipment (modem/router) to the outdoor equipment at the antenna normally involves two inter-facility (IFL) cables. The Internet Group Management Protocol (IGMP) is a communications protocol used by hosts and adjacent routers on IP networks to establish multicast group memberships. Channel from stations to Hub. IP is the usual abbreviation for Internet Protocol. JavaScript Object Notation is an open standard format that uses human-readable text to transmit data objects consisting of attribute value pairs. It is the most common data format used for asynchronous browser/server communication, largely replacing XML. Low-density parity-check (LDPC) code is a linear error correcting code, a method of transmitting a message over a noisy 2017 UHP Networks Inc 4

5 LNB Local oscillator Long frames Master MCPC Mesh MF-TDMA MODCOD NMS ODU Outroute QPSK RF RF level RSV Satellite router SCPC Short frames SNMP SNR SNTP SR Star Symbol rate SW TDM TDMA Telnet Terminal) TFTP Time-slot, TDMA slot Timestamp UDP UHP USB VLAN VNO VoIP VSAT WFQ X-modem XML transmission channel, and is constructed using a sparse bipartite graph. Low-noise block converter is the receiving converter installed at satellite antenna. Oscillator built into RF block converter (BUC or LNB) for the purpose of converting RF-IF frequencies. Value of LO is usually written on block enclosure or in datasheet. DVB-S2 frames bits long (including FEC). Require slightly lower C/N than short frames. Main station of Hubless network. Master allocates bandwidth and performs stations acquisition. Multiple channels per carrier. All TDM carriers generated by UHP can be treated as MCPC. Even if they are called SCPC. Capability of station to receive other stations via TDMA link. TDMA working on several RF channels simultaneously. All MF channels work as one aggregate TDMA channel and have similar parameters except frequency. Modulation and coding mode. Network Management System Outdoor Unit part of earth station installed outside. Forward TDM channel from Hub to stations. 4 Phase-shift keying (QPSK) is a digital modulation scheme that conveys data by changing, or modulating, the phase of a reference signal (the carrier wave). Radio frequency Absolute RF level of entire signal (carrier + adjacent carriers) expressed in dbm. Reed Solomon error correction is an error-correcting code that works by oversampling a polynomial constructed from the data. Satellite router is a networking device, commonly specialized hardware that forwards data packets between networks via satellite. Single Channel Per Carrier DVB-S2 frames bits long (including FEC). Advisable to use at lower symbol rates. Produce less delay than Long frames. Simple Network Management Protocol Signal-to-noise ratio is an electrical engineering measurement defined as the ratio of a signal power to the noise power corrupting the signal. Simple Network Time Protocol (SNTP) is a protocol and software implementation for synchronizing the clocks of computer systems over packet-switched, variable-latency data networks. Symbol Rate Type of network with one central station (Hub) and several peripheral stations. Symbol rate is the number of symbol changes (waveform changes) made to the transmission medium per second using a digitally modulated signal or a line code. Software. Time Division Multiplexing Time Division Multiple Access Telecommunication Network (Telnet) is a network protocol used on the Internet or local area networks to provide a bidirectional interactive communications facility. Earth Station (remote station) operated under management of network Hub. Trivial File Transfer Protocol (TFTP) is a file transfer protocol, with the functionality of a very basic form of File Transfer Protocol (FTP). Time interval for station transmission in TDMA mode. Time format used by UHP. Plus sign at the beginning (+HH:MM:SS or +NN d HH:MM:SS) denotes relative time from some event or UHP start-up. If UHP has time synchronized to Hub or SNTP absolute time can be displayed. Time zone affects absolute time. The User Datagram Protocol (UDP) is the set of network protocols used for the Internet. Universal Hardware Platform common name of UHP routers USB (Universal Serial Bus) is a specification to establish communication between devices and a host controller (usually personal computers). A virtual LAN, commonly known as a VLAN, is a group of hosts with a common set of requirements that communicate as if they were attached to the same broadcast domain, regardless of their physical location. A Virtual Network Operator is a provider of management services and a reseller of network services from other telecommunications suppliers that does not own the telecommunication infrastructure Voice over Internet Protocol (VoIP) is a general term for a family of transmission technologies for delivery of voice communications over IP networks such as the Internet or other packet-switched networks. Very Small Aperture Terminal satellite earth station with small-size antenna (<2.5m) Weighted fair queuing. Method of proportional division of bandwidth between transmission queues. Simple file-transfer protocol Extensible Markup Language is a markup language that defines a set of rules for encoding documents in a format which is both human-readable and machine-readable UHP Networks Inc 5

6 INTRODUCTION This document provides a general guidance of installation and operation of the Network Management System, which is a part of satellite networks based on UHP satellite routers. The document describes system composition, performance, capabilities and operation rules. Additional information about specifications and operation guidelines for the specific UHP router models or the specific modes of operation can be found in the GENERAL DESCRIPTION AND INSTALLATION GUIDES or in the USER MANUALS. Required Qualifications This manual is intended for engineering personnel planning, deploying and operating of UHP VSAT networks. Such specialists should have adequate educational credentials in the field of electronics and sufficient experience and skills in data networks administration and satellite systems. Document Version and Applicability UHP VSAT platform is based on the universal satellite router UHP, which is available in different fully-compatible hardware modifications. UHP satellite router is a basic element of any network architecture and can be used in any combinations and at any hierarchy level. Router functional capabilities and its operating modes are determined by the installed software and its configuration. The Network Management System allows configuring and operating UHP-based networks with a useful and easy-to-use web interface. This manual is applicable to UHP Network Management System with the software release 3.4 or higher. When ordering this document, please specify its ID: [UHP.NMS.34.EN]. System Level (Network engineering guide) Network Engineering Service Level (User manual) TDM/TDMA Station SCPC Modem Hubless TDMA Station Hardware Level (Installation guide and specifications) UHP-1000 UHP-100 UHP-200 UHP-IFS NMS Copyright Figure 1 Structure of UHP manuals The content of this document is the intellectual property of UHP Networks Inc. Copying or quoting this description as a whole or of any part of it without a written permission from UHP Networks Inc. is prohibited UHP Networks Inc 6

7 1. SYSTEM OVERVIEW 1.1 General Information Purpose UHP Network Management System (NMS) is a sophisticated and user-friendly tool for monitoring and controlling of satellite networks based on the UHP routers. The NMS substantially simplifies configuration of the Hub and of the remote stations, collects and stores in its database information about current and historical status of the whole network and its individual elements, and also displays this information in graphical and tabular formats. The NMS supports all UHP configurations and topologies, including TDM/ TDMA, SCPC, SCPC-DAMA and Hubless TDMA Architecture The NMS is realized as a server with the pre-installed software. The system hardware platform is a server running Ubuntu Linux OS. The NMS server may be collocated with the network Hub and can operate with TDM/TDMA, Hubless TDMA and SCPC DAMA networks. The system can be accessed using a web-based user interface. The recommended web-browsers are Firefox 10+ or Google Chrome 16+. The NMS consists of three basic components: System core Web-based user interface Configuration/statistics database Services implemented on the NMS server include data collection, initial processing and storage. The web interface is responsible for the user/system interaction as well as for data preparation and its presentation in a user-friendly form. The data storage or system database consists of two components: configuration held in MySQL database and statistics held in open binary format. The NMS server distributes configuration to all UHP network elements, collects statistics on operation of devices and stores statistics in the system database. It also analyzes the network status and allows the user to view such information in a graphical format. The system core communicates with the UHP equipment analyzing its behavior and collecting statistics. The database holds this information for a specified period of time, usually several years. The web interface shows all collected information in a graphical format and provides mechanisms for the network configuration. The NMS uses graphs to display current and historical network parameters, e.g. traffic, C/N levels, etc. Tables allow monitoring instantaneous values of respective parameters. The network events can be viewed using traditional events log and/or dynamic events groups tool (alerts) Composition The system is delivered on a 1U rack-mount server Installation The NMS server is traditionally collocated with the network Hub however availability of the web interface allows installation of the server at any alternate location. The basic requirements are: AC power and environmental conditions in accordance with the specification IP connection to UHP routers acting as Hub controllers with throughput not less than 0.2 kbps for each active station in the network. For example, if UHP network consists of 2000 terminals the NMS should be connected to the Hub with a 400 kbps throughput minimum. This can be a direct connection via LAN or VPN channel Ports 4660 and 4661 should be open and not restricted 2017 UHP Networks Inc 7

8 The NMS can be optionally connected to the Internet to retrieve weather information (at openweathermap.org) displayed on a dashboard s map. This service uses port #80 with minimal throughput of 32 kbps. Local NMS console Local HUB controller Ethernet switch Remote HUB controller Remote NMS console NMS server Internet Supported Modes of Operation and Limitations Figure 2 Connection of the NMS The Network Management System is compatible with any UHP routers with software release 3.4 or later. The following modes of VSAT network operation are supported: TDM/TDMA, TDM/TDMA Mesh, Hubless TDMA and SCPC DAMA. When operating in TDM/TDMA or TDM/TDMA Mesh modes the NMS should be located within the same LAN segment as all the Hub controllers. A Hubless Master station and the NMS should be located in the same LAN segment too UHP Networks Inc 8

9 2. PREPARATION FOR USE The NMS is usually supplied as a server with pre-installed software and requires no additional SW installation. 2.1 Licensing The Basic NMS server can manage a single TDM/TDMA or TDM/TDMA Mesh network or TDMA Hubless network or SCPC concentrator. Such basic configuration can be upgraded to support the following additional features: VNO support of multiple networks with ability to share such networks across a number of Virtual Network Operators Scheduler specialized module supporting automatic SCPC-DAMA scheduling and management This extended functionality can be ordered and activated at the factory or any time later. 2.2 Powering On After powering on the server no special actions are required. NMS software starts automatically during the system boot. Login to the server with Administrator account and execute the following command to turn the server off: sudo poweroff IT IS HIGHLY RECOMMENDED TO POWER THE NMS SERVER VIA UNINTERRUPTED POWER SUPPLY TO PREVENT POSSIBLE DATA LOSS IN CASE OF POWER FAILURE. 2.3 Initialization of the Server The following settings are to be configured when the server starts for the first time: IP address Default route DNS address These settings can be configured using the command line when connected to the NMS server via SSH. By default the NMS server is set to the following configuration: Table 1 Factory settings of NMS IP address Network mask Gateway User name Password 1 The built-in Ubuntu console editor "Nano" can be used to configure network settings: sudo nano /etc/network/interfaces The interfaces file defines the following settings: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address netmask gateway If the NMS needs to be connected to the Internet it is necessary to define a DNS address in the interface file. For example: dns-nameservers The changes in the configuration file interfaces can be saved using shortcut command ctrl + o -> enter. To apply the new settings, close the Nano editor using ctrl + x command and restart the network service using the following command: user 2017 UHP Networks Inc 9

10 sudo /etc/init.d/networking restart 2.4 System Login The NMS can be accessed via standard web-browser using respective domain name or IP address. The default login for the first user is admin/12345 which should be changed as soon as possible. 2.5 Connection of the NMS to UHP Network The NMS requires an IP connection to all UHP Hub controllers which can be located locally or remotely. 2.6 Initial Configuration of UHP Controllers UHP routers may work either autonomously or under management of the NMS. This can be configured on UHP controllers of the Hub (not need to configure it on UHP terminals): Use a web interface of each UHP controller to activate the following flags: o o Advanced/Network/STLC/NMS/Red/Monitoring activates monitoring of the router via NMS Advanced/Network/STLC/NMS/Red/Control activates controlling of the router via NMS Define a common security word (password) both on the NMS and on all UHP routers: o o UHP router: Advanced/Network/STLC/NMS/Red/Password NMS: Network/Controllers/name_of_controller/Basic settings/password Network management traffic can be separated into a separate VLAN-network. The respective VLAN number should be defined on the UHP controllers: OPTION_ADVANCED/NETWORK/STLC/NMS/RED/VLAN. The same VLAN number should be created in the NMS. 2.7 Objects of NMS Control The NMS monitors and controls the following network components: UHP Hub controllers; Virtual Hub controllers; Remote UHP routers (stations); Networks; Virtual Networks (VNO) Remote Stations Remote stations are satellite earth stations with installed UHP routers which are located remotely. The stations are managed by the Hub or Hubless Master stations or SCPC-DAMA controller. Each TDM/TDMA or Hubless station belongs to a particular network and to the corresponding controller, but profile switching of such station may result in a change of assigned Hub and/or controller. The NMS manages remote stations by transmitting appropriate service information through the forward channel (Outroute). This information is used to arrange transmission via the return channel, as well as for retrieving statistics data from the remote station. The service information is also used to manage routing map of remote stations Hub Controllers The concept of controller is introduced within the UHP network architecture in order to jointly configure UHP routers on the Hub side and the respective UHP routers on the station side. In addition, a virtual device managing network functionality, e.g. Scheduler ensuring change of operation modes and distribution of network resource according to the schedule, may also act as a controller. RF and network parameters required for operation of the communication link managed by the controller are specified during configuration UHP Networks Inc 10

11 Based on the selected operating mode, a single controller is able to ensure operation of a number of UHP routers within the associated stations. Mode of operation of the controller is specified during its initial configuration. The UHP routers within the stations are managed by the associated routers on the Hub side via a service channel embedded in the Outroute. In turn, the routers within the Hub are managed by the NMS. Accordingly, managing the Hub routers affects all network routers and NMS allows configuring and monitoring status of all UHP network objects. Depending on the configured mode, a single controller is capable of supporting simultaneously one Outroute and one Inroute, as well as a single Outroute or a single Inroute. The controller may also work as Master Hubless TDMA station or as SCPC-DAMA receiver. A single UHP network is a combination of one or more controllers and associated UHP routers both on the Hub side and on the station side, connected via satellite communication channels. TDM/TDMA network includes one Outroute and a set of Inroutes. UHP network may also consist of one or several Hubless TDMA channels when using Hubless mode. One UHP network has dedicated satellite capacity which is in exclusive use by this network. One NMS can simultaneously manage multiple networks Network UHP network consists of Hub controllers and associated remote stations. The network may include Hub controllers operating in different modes. OUTROUTE CONTROLLERS CONNECTED TO THE SAME NMS SHOULD HAVE DIFFERENT NET ID SETTINGS THAT CAN BE DEFINED VIA NMS: NETWORK/CONTROLLERS/NAME_OF_CONTROLLERS/CONFIGURATIONS/SITE SETUP/NET ID. The NMS interface uses hierarchical network structure, where all network controllers and stations organized as multi-level trees. Depending on active NMS license a single NMS can manage one or several networks. Each NMS user account can be configured to access such networks with a predefined permissions and roles. The following components can be configured for a network: Shapers Alarms VLANs Traffic policies RF setup NMS users Virtual Network Operator Part of network stations and associated network resources may be combined into a group called VNO (Virtual Network Operator). Using VNO allows creating: Traffic shaper applicable to the specified VNO-group Special NMS user accounts limited to monitoring and management of the respective VNO-group VNO can be created in the System/Networks configuration section of the NMS. VNO may be added to any of active networks. To add VNO, open appropriate window in the user interface and specify the name of the new operator and traffic shapers for the forward and the return channels. Once the VNO is created, the respective stations can be moved to this virtual network here NMS/Maintenance. Settings configured the VNO are immediately applied to the associated stations. IF NECESSARY TO PROVIDE A VNO NMS USER WITH ACCESS TO THE HUB CONTROLLERS, SUCH CONTROLLERS AND THE ASSOCIATED STATIONS SHOULD BE SEPARATED INTO A DEDICATED NETWORK WITH PROPER ACCESS RIGHTS UHP Networks Inc 11

12 3. OPERATIONS 3.1 User Interface The system provides a multi-user, multi-language interface and supports multiple Virtual Network Operators (VNO) sharing common network infrastructure Dashboard and Navigation The user interface (see Figure 3) focuses the operator s attention on the most important events in the network, and also provides the operator with exhaustive information needed for analysis and troubleshooting. By selecting most suitable settings for the display, the operator can view the information in the desired format: logs, graphs and/or tables. All key network characteristics are displayed on a single page, known as the dashboard. Network tree Controllers level Stations level Information charts Information tables Local menu Events acknowledgement Spectrum Visualization Events log & Notifications Search tool The dashboard includes the following components: Figure 3 UHP NMS interface Network tree comprises of all network components (controllers and stations) Controllers level comprises of all controllers associated with this network Stations levels comprises of all stations associated with the controllers of this networks Local menu quick access to statistical information and configuration of the selected object Information charts represents a dynamic of changes in respective parameters of the selected object Information tables summarize different actual parameters of the selected object Spectrum Visualization displays network s carriers positions Events log complete list of network events with time-stamps Search tool allows finding a given station in the network by its name Charts Statistical information of the network objects can be displayed in the form of graphs, allowing easy visualization of network performance for the specified period. The built-in charts of the NMS are flexible analytical tools to 2017 UHP Networks Inc 12

13 correlate statistical information on specific parameters with other events that took place at the same time. There are two types of charts for each network object in the Statistics section: C/N reception level on the station side and on the side of the controller; Transmitted and received traffic. The charts are updated every 5 seconds. The following data can also be displayed on Station Charts (see Network/Stations/Station_name/Graph section): Traffic summary Traffic to station Traffic from station Reception Transmission Bandwidth Traffic transmitted and received between the Hub and the Station Traffic received by the Station separated by its priority low, medium and high Traffic transmitted by the Station separated by its priority low, medium and high C/N reception level on the Station and the Hub, as well as number of ACM channel used Transmission level of the Station and respective C/N reception level on the Hub Number of TDMA slots requested by station for regular and real-time traffic The following data can also be displayed on Controllers Charts (see Network/Controllers/name_of_controller/Graph): TX traffic TX ACM station TX Own reception TX Levels TX State RX Traffic RX Allocation RX Station state RX Reception RX Levels RX CRC RX State Transmitted traffic of the Controller with its distribution between ACM channels Distribution of stations between ACM channels Self-reception C/N level of Outroute controller Self-reception С/N level, RF level of Outroute demodulator and Tx level of respective modulator Profile state parameter Received traffic of the Controller Number of TDMA-slots requested for regular and real-time traffic, total number slots requested Number of stations in UP, ACTIVE states and number of stations with low C/N level Self-reception C/N level of Outroute controller, average C/N level of Outroute channel on remote stations, average C/N level of Inroute channels at the Hub controllers Self-reception С/N level, RF level of Outroute demodulator, RF level of Inroute demodulator Number of CRC errors of SCPC/TDMA demodulator at the Hub controller Profile state parameter Customization of the Charts: Double-click on the chart - alignment of the selected value in the middle Dragging in the vertical / horizontal direction while pressing the "mouse" button zoom in Double-click on the left mouse button chart at a larger scale - zoom out Dragging with mouse button pressed and Shift or Alt relocation of the chart Special tools located above the chart allows: Choose the type of chart Set the time scale Reduce or enlarge the time scale Move left or right on the timeline Display the chart for the last hour/day/month Events Log The Event logs contain information about events that occurred with the network object for the entire period while this object was managed by the NMS. Logs available for the following network objects: 2017 UHP Networks Inc 13

14 Stations Network/Stations/name_of_station/Log Controllers Network/Controllers/name_of_controller/Log VNO Network/Stations/name_of_VNO/Log Network/Stations/name_of_VNO/name_of_station/Log Each event log entry matches one event occurring with the network object and contains the following information: Event date Event time Name of the network to which the object belongs Name of the network object Description of events occurred The Even log allows defining a time period for which the events should be displayed. Also, a report may be generated based on the last two hundred events occurred with the network object(s). LAST TEN EVENTS OF THE CONTROLLER/STATIONS ARE REPRESENTED IN THE RELEVANT STATISTIC SECTION Reports The NMS allows generating reports for a particular station, a VNO subnetwork or for the entire network. Reports can be generated and uploaded from the dashboard of the respective network object. There are three type of information that can be included in such reports: Availability Traffic Rate Availability of the specified network object for the specified period Traffic of the specified network object for the specified period Throughput of the specified network object for the specified period 3.2 NMS Statistics The NMS/Statistics section provides general information about the Network Management System, including: Active services of the system Actual load of the NMS resources Software version Active controllers User log An authorized administrator can stop or start NMS services Networks The NMS/Networks section allows managing VNO groups, including definition of traffic shapers for the forward and return channels Maintenance The NMS/Maintenance section allows moving stations between networks and VNO groups Backup and Recovery It is recommended to activate automatic backup function in the NMS/Backup section, which will back up the configuration of NMS locally and as a downloadable file UHP Networks Inc 14

15 Backup Type Comment Daily autobackup Enable Backup time Restore Recover from file Server backups Restore/delete Select type of backup file Server local copy of the configuration File downloadable file Annotations Daily automatic backup of the configuration Activation of daily backup Definition of backup time Recovery of the configuration from a backup file Specify and download an appropriate backup file Achieve of local backups Select one of local backups to restore the configuration. Unnecessary backup copies can be deleted here IT IS RECOMMENDED TO BACK UP THE CONFIGURATION MONTHLY OR AFTER EACH CHANGE OF THE CONFIGURATION IF AUTOMATIC BACKUP IS DISABLED Software Upgrade of Stations The NMS allows automatic software upgrade in the remote stations. The first step is to download the new software on the NMS server in the NMS/Software section. Once downloaded, this SW file will appear in the Available Software window. The NMS allows storing and using different SW versions. Upgrade of the respective stations can be configured in the section: Network/Stations/Maintenance Licenses Depending on active licenses the NMS may support different functionality: Basic base license VNO - expansion of the basic version to manage multiple networks and VNO Scheduler activates SCPC-DAMA Scheduler module on Basic or VNO NMS Restricted Demo License demo license, cannot be used to manage real networks The section NMS/License/Current represents all active licenses. Additional licenses can be activated by the following procedure: 1. In the NMS/License/New License section select required functionality and generate a respective license request 2. Forward the generated request text to our support center 3. When the requested activation code is received, copy it to Activation code field and apply this new license User Log The NMS/User Log section contains a summary of the chronology of the users activity in the NMS Settings Network management system/settings General settings General system configuration NMS has Internet connection This flag allows NMS retrieving weather/map information from the Internet. Login screen logo Customization of logo. Hide disabled controllers in navigation tree Hide disabled stations in navigation tree When selected, the disabled controllers will not be shown in the tree of network objects (see also Network/Controllers/name_of_controller/ Configuration/Basic Settings). When selected, the disabled stations will not be shown in the tree of network objects (see also Network/Stations/name_of_stations/ Configuration/Basic Settings) UHP Networks Inc 15

16 API Authorization token Open API sandbox Weather settings Receive weather updates (requires Internet connection of the NMS server) Delay between each request Min. delay for station request Max. delay for station request Configuration of the interface to external programs Generation of the authorization token that should be used by external programs to communicate via API interface of the NMS. Allows accessing API-settings. Weather update settings Activates weather information displayed on the map of stations. Restart the NMS core (section NMS/Statistics > Stop core >Start core) to apply these changes. Frequency of weather updates in msec. Minimal interval between station requests, msec. Maximal interval between station requests, min. 3.3 NMS User Accounts Users of the NMS can be defined in the section Network/Configuration/Users. Each user can be granted different level of access. By default the NMS has one user super-administrator (credentials: admin / 12345) with full rights. The default password should be changed at the first use of the system. The administrator may create necessary number of additional users and define their respective roles and permissions. A user account may also include useful additional information: Network/Configuration/Users/user_name/User settings User settings Basic user s data Username Unique login name First name Given name Last name Family name Password Password address Preferences Personalization Interface language User s interface language Display timezone Time zone of the user Display weather in Fahrenheit Switching the temperature display in Fahrenheit and Celsius Contacts (optional) Optional contact information Company Name of company Additional Phone 1 Contact phone Phone 2 Additional contact phone Address Contact address Network/Configuration/Users/user_name/User rights View level Definition of visible networks Network list Role Role name Permissions NMS Select visible network objects Select one of predefined role templates View only; Network operator; Manager; Superuser Schedule operator; Schedule user. Definition of permissions Login activate user s account; NMS management access to the Network Management System section 2017 UHP Networks Inc 16

17 Network (global) User Controller Station Routing Shaper Policy Schedule Control Information Actions Log out Set relogin timeout Create/Edit networks (access to the section NMS/Networks) Configure VLANs (access to the section Network/Configuration/VLANs) Configure alerts (access to the section Network/Configuration/Alerts) Acknowledge alerts permission to acknowledge alerts Station maintenance (access to the section Network/Stations/name_of_station/maintenance) Reports permission to generate reports (access to the section Network/Stations/name_of_station/Reports, Network/Stations/name_of_VNO/Reports, Network/Reports) Create add new users; Edit edit general data of users; Edit permissions change roles and permissions of users; Delete delete users. Create add new controllers Edit change settings of controllers Enable and disable activate/deactivate controllers Delete delete controllers Create add new stations Edit change settings of stations Enable and disable activate/deactivate stations Delete delete stations Create add new routes Edit edit routes Delete delete routes Create add new shapers Edit edit shapers Set public flag permission to use shapers in other networks Set template flag create template shapers Delete delete shapers Create add new policies Edit edit policies Delete delete policies Configure configuration of the scheduler Edit modification of own bookings Edit others/approve reservation modification and approval of all network bookings Management of NMS users Timestamp of the latest system login Forced system logout Prevents login of other users for specified time. Can be used during maintenance of the NMS or networks 3.4 Scheduler The Scheduler is based on a virtual controller Frequency Planner that performs switching stations from the common TDMA return channel to dedicated SCPC-DAMA return channel. This type of controller is available for the NMS with the respective license and can be configured in the section Controllers/Configuration Setup When a Frequency Planner controller is created it can be used to define standard Services configuration template for SCPC-DAMA carriers (see Controllers/name_of_scheduler/Configurations). The scheduler and any station operating under management of the Scheduler may use various Services UHP Networks Inc 17

18 Configuration of a Service includes the following parameters: Service name Modulation, FEC and Roll-off One of three settings: throughput (kbps), symbol rate (ksps) or allocated bandwidth (khz) Level of the Rx signal observed at the receiving controller Profile of the remote station used as location where to save this service settings The Scheduler should be associated with respective stations by selecting this controller in the filed Controlled by at the section Stations/name_of_station/Configuration. The Scheduler can also be associated with particular SCPC- DAMA controllers. If no SCPC-DAMA controllers are specified the Scheduler will automatically select idle SCPC- DAMA controllers of the Hub Booking Figure 4 Booking window Transmissions controlled by the Scheduler can be booked in the section Controllers/name_of_scheduler. Select the station, the desired Service profile and the start/end time. If necessary, specify the desired controller. Enable this reservation and apply it by clicking on the Add reservation button. All scheduled and enabled reservations are displayed on the dashboard of the Scheduler. Duration of the displayed time period can be changed from one hour to one month. The reservations can be also reviewed in a table view. 3.5 API The NMS can be integrated with external software objects through a program interface (API). Queries to the NMS can be based on XML or JSON messages and performed over the HTTP protocol. The requests should be sent as a data by the POST method: where: JSON: http: // <nms_address> / jsonapi /? Token = <token_key> & out = <out_type> XML: http: // <nms_address> / xmlapi /? Token = <token_key> & out = <out_type> <nms-address> - the IP address of the NMS or its domain name, if set; <token-key> - authentication key on the server. It can be generated in the section NMS/Settings; once generated, such new token key should be updated for all active queries; 2017 UHP Networks Inc 18

19 <out_type> - type of value to be returned; if this parameter is not specified, the type of response is appropriate to the type of the request. With inquiries via the API, external programs can get statistics or information from the NMS, add, edit or delete network objects. This allows deep integration of the NMS and of the entire UHP network into customer s OSS/BSS infrastructure. The detailed query syntax is available as a separate guide UHP Networks Inc 19