System Overview - 20Rx
System Overview - 20Rx
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer documentation and consulting with standards
bodies to ensure that terminology is inclusive and aligned with the industry. Our future customer documentation will be updated accordingly.
This document includes Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without
the prior written consent of Nokia.
This document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a product purchased or licensed from any company
within Nokia Group of Companies. Use this document as agreed. You agree to notify Nokia of any errors you may find in this document;
however, should you elect to use this document for any purpose(s) for which it is not intended, You understand and warrant that any
determinations You may make or actions You may take will be based upon Your independent judgment and analysis of the content of this
document.
Nokia reserves the right to make changes to this document without notice. At all times, the controlling version is the one available on Nokia’s
site.
This document is Nokia’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the
prior written consent of Nokia.
Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be
trademarks of their respective owners.
© 2023 Nokia.
Contents
1 Introduction to MantaRay NM........................................................................................................................ 5
2 Fault management......................................................................................................................................... 11
3 Configuration management.......................................................................................................................... 13
4 Performance management............................................................................................................................15
5 Security management................................................................................................................................... 17
6 Network administration.................................................................................................................................20
7 MantaRay NM administration....................................................................................................................... 24
7.1 High availability solutions........................................................................................................................25
7.1.1 Disaster Recovery solution.............................................................................................................25
7.2 MantaRay NM overload protection......................................................................................................... 25
7.3 MantaRay NM serviceability................................................................................................................... 26
9 Adaptations.................................................................................................................................................... 41
9.1 Static adaptation......................................................................................................................................41
9.2 Dynamic adaptation.................................................................................................................................41
9.3 MantaRay NM fast pass......................................................................................................................... 41
10 Interfaces...................................................................................................................................................... 44
10.1 Northbound Interfaces...........................................................................................................................44
10.2 Southbound Interfaces.......................................................................................................................... 46
10.3 Eastbound Interfaces............................................................................................................................ 49
11 User assistance............................................................................................................................................51
11.1 Operating documentation...................................................................................................................... 51
11.1.1 Operating Documentation application...........................................................................................52
11.1.2 MantaRay NM Operating Documentation information architecture.............................................. 53
11.2 Object Information Browser...................................................................................................................57
12 User experience........................................................................................................................................... 58
12.1 Multilanguage support overview........................................................................................................... 58
12.1.1 Supported applications................................................................................................................. 58
12.1.2 Unsupported functionality............................................................................................................. 59
12.1.2.1 Fault management................................................................................................................59
12.1.2.1.1 Monitor..........................................................................................................................59
12.1.2.1.2 Alarm Reports Dashboard........................................................................................... 61
12.1.2.2 Configuration management.................................................................................................. 62
12.1.2.3 Performance management................................................................................................... 64
12.1.2.4 Network administration......................................................................................................... 64
12.1.2.4.1 Trace Expert.................................................................................................................64
12.1.3 Limitations..................................................................................................................................... 64
12.2 Screen reader support overview...........................................................................................................65
12.2.1 Supported applications................................................................................................................. 65
12.2.2 Limitations..................................................................................................................................... 65
1 Introduction to MantaRay NM
Note: NetAct and MantaRay NM refer to the same product. Both product names are visible
in the software and operating documentation.
MantaRay NM serves both as a network management system and as an element management sys-
tem. MantaRay NM offers a wide range of unified operation and maintenance capabilities for network
elements in core, radio and transport networks both for managing physical network elements as well
as virtualized network functions. It consists of many tools for handling a number of network elements
and expanding networks. It is designed for handling an increase in both the complexity of the network
and the amount of traffic and data.
Note: You can find the network elements and their releases supported by the different Man-
taRay NM releases in the NetAct and NetAct Cloud Compatibility Matrix in Discovery Cen-
ter at https://doc.networks.nokia.com. Accessing the documentation in the portal requires au-
thentication. To locate the NetAct and NetAct Cloud Compatibility Matrix, select the NetAct
product from Discovery Center homepage and navigate to 23R3-NM > Compatibility Matrix >
Compatibility matrix.
With MantaRay NM, both the network and the services within the network are managed centrally so
that the operator can view network element failures, service quality indicators, and traffic from one
screen.
To facilitate its integration in multi-vendor environments, MantaRay NM provides several open north-
bound interfaces (standard-compliant and proprietary ones) that offer to operators a unified manage-
ment capability for the entire network. For this purpose a mediation application function provided by a
so-called Northbound Interface Agent performs the mapping between the management information re-
ceived by MantaRay NM or generated in MantaRay NM and the information required by the upper lev-
el management systems.
In addition to MantaRay NM applications there are also standalone tools that are dedicated to specif-
ic management functions and provide advanced management features, for example, Nokia Advanced
Configurator for configuration management. These standalone tools need a dedicated hardware plat-
form and are sold separately. For more information, refer to the operating documentation of each prod-
uct.
• Fault management
• Configuration management
• Performance management
• Security management
• Network administration
• MantaRay NM administration
Figure 1: MantaRay NM system with management functions, applications, and interfaces
The following table shows the management functions and corresponding applications for managing
the network and MantaRay NM itself. Note that some applications are for optional functions and not
available in a basic MantaRay NM configuration.
fault manage- Alarm Reports Dashboard Manages reports for Fault Monitoring
ment Management.
fault manage- Network Alarms Pattern Discovery Enables you to view and man- Monitoring
ment age the correlated and inform-
ing delay alarm patterns.
configuration Intelligent Feature Activation A web-based tool for fast and Configuration
management easy activation of new radio
features.
security manage- Network Element Access Control Network Element Access Con- Security
ment trol manages and administers
service users of network ele-
ments.
network adminis- Software Asset Monitoring Feature usage reports for net- Reporting
tration work elements and MantaRay
NM.
network adminis- MSC Server Pool Monitor Monitors MSC server pool dis- Monitoring
tration tribution.
MantaRay NM Working Set Manager Used for browsing and man- Administration
administration aging working sets across key
MantaRay NM applications.
User assistance Object Information Browser Allows browsing and export- User assis-
ing adaptation data informa- tance
tion and adaptation release
changes.
2 Fault management
In MantaRay NM, fault management enables you to manage the alarms from various network ele-
ments. Fault management helps in detecting and troubleshooting the faults that cause disruptions in
network services.
Network elements contain monitoring and diagnostic tools for detecting various types of fault situa-
tions. Each fault is represented as an alarm and this alarm is send to MantaRay NM.
Monitor plays the important function of Network Assurance in an end-to-end manner, supporting oper-
ator workflows from trouble detection to resolution.
Monitor enables centralized network monitoring for all technologies, from element management to op-
erational management. With Monitor, it is possible to define user-specific workspaces, create user-
specific workflows and enable monitoring the growing network. Alarm filtering and alarm correlation
make fast root cause identification possible.
• Alarm filtering and correlation: Monitor comes with alarm filtering and alarm correlation rules which
reduce the overall number of alarms.
• Alarm enrichment: Alarm enrichment collects additional information for root cause analysis in fault
situations, for example, the geographical location of the network element sending alarms.
• Alarm flow supervision: Alarm flow supervision monitors and reports any connectivity problems
with the network elements.
• Advanced usability features: Monitor supports quick buttons, context-sensitive and seamless in-
terworking of the tools and drag-and-drop functionality. Monitor views are easy to adjust to differ-
ent monitoring needs, ranging from network-wide views down to the single element, or technolo-
gy-specific expert monitoring.
• Reporting features: Fault management reports on a specific time frame or a specific network ele-
ment.
• Alarm trigger: Alarm trigger offers automation of fault correction processes based on specific
alarms. Certain alarms can, for example, initiate an automatic network element reset or network
element lock-down. Triggering rules are defined by the operator.
• Integration to external systems: Alarms can be forwarded to trouble ticketing or workflow manage-
ment systems via the OSS/J Trouble Ticket Client interface. Alarms from third-party equipment are
collected, viewed, and stored in Monitor together with all the other network alarms. Alarms can al-
so be distributed to external tools for remote access for further processing of offline analysis or for-
warded to email.
Monitor supports context-sensitive launch of Element Managers. Alarm inflow related statistics can be
gathered in a scheduled manner with the Alarm Reports Dashboard application for post processing.
Dynamic alarm suppression is an optional feature. It correlates alarms intelligently based on the run-
time data in the alarms. Dynamic Alarm Suppression rule helps find the root cause alarm, and sup-
press the secondary alarms. Alarms can also be correlated by defining the relationship between them
rather than on static attributes.
Alarm Reports Dashboard detects, collects and stores the failures in the network. It also schedules the
report generation and monitors the quality of service.
Network Alarms Pattern Discovery enables you to view and manage the correlated and informing de-
lay alarm patterns.
For more information, see the Fault Management category in Operating Documentation.
3 Configuration management
MantaRay NM Configurator offers comprehensive functionality for configuration management with
common processes and data storage in multi-technology radio and core networks. Automated network
planning and network consistency checking actions can be carried out with easy-to-use tools. Man-
taRay NM Configurator enables flexible and automatic workflows for fast network roll-out and expan-
sions as well as controlling the related processes.
In radio access management, Configurator can be used for mass modifications of network element pa-
rameters, BTS autoconfiguration, adjacency management throughout radio network technologies, site
planning and site rehosting, mass change verification as well as remote electric tilt management for
flexible network tuning.
In core network management, Configurator can be used for automatic upload of network element data,
display of data with a feature-rich Table Editor, comprehensive network planning in offline mode, ver-
ification of planned modifications, auditing of actual configuration data and it offers dedicated means
for spontaneous modifications. The supported core network technologies are Rel-4 Core, Packet Core,
IMS, and NT HLR FE.
With the MantaRay NM Configurator tools, the operator can handle daily configuration management
tasks easily. For the majority of the operations, there is also a command line interface. MantaRay NM
Configurator is a main enabler of self-organizing network (SON) functionality.
• CM Editor is used for creating, editing, and visualizing configuration plans and templates as well
as managing and manipulating parameters (minor edit to mass modification).
• CM Analyzer is used for checking the consistency of a plan or managed configuration against a
set of rules. With CM Analyzer it is possible to create consistency and audit reports on the actual,
reference, or plan configuration.
• CM Operations Manager provides visibility on what is happening and has happened with the man-
aged data in terms of network operations. It offers the means to start and schedule all different op-
erations supported by the system, such as export, import, upload, and provisioning.
• CM Workflow Manager (Workflow Engine) offers the means to design, start, and follow up macro
workflows. These are workflows which are perceived as a set of different steps, that is to say, a
defined sequence of tasks.
• CM Reference is a workspace for maintaining the reference configuration of a network. Deviations
in the actual and reference configuration can be audited and aligned to either one.
• Flexible CM Search is a web-based application for searching configuration management data in
the actual configuration. In addition, you can also view the data in CM Editor and upload the actual
configuration.
• CM History is a part of CM Editor and CM Reference, keeping a record of every configuration
change in the network. CM History records are stored both for the actual and reference configura-
tion.
• Intelligent Feature Activation allows the user to roll out new radio features easily. All parameters
relevant to a feature can be selected and modified. It also enables creating and storing feature
templates, that is, modified configurations for further use in a similar situation.
• CM Rule Editor allows the user to create user-defined rules in a simple way. Rules can be further
used in CM Analyzer to check the network consistency.
• CM Policy Manager checks the consistency of planned network configurations against a prede-
fined set of rules to avoid potential network outages.
• CM Express Data Exchange enables an easy method for mass configuration modification using
spreadsheet mode (CSV format and XLSX format). Exporting and importing data can be done
from CM Editor, CM Table Editor, or Search and Modify.
• Configurator Dashboard manages and verifies configuration operations and data. Configurator
Dashboard is a web-based application where different configuration management domains are
integrated together. It is possible to execute predefined workflow operations, for example Mass
Change Verification and Rebuilding BTS Sites, and manage configuration templates.
Hardware inventory management is integrated into MantaRay NM Configurator. This enables easy ac-
cess to hardware inventory data because of the rich data browsing feature set of Configurator. A dedi-
cated CM Editor view to view only hardware data of network elements is pre-defined.
• Hardware inventory data upload using CM Operations Manager or command line interface
• Hardware inventory data browser using CM Editor
• Hardware inventory data export via the northbound interfaces using CM Operations Manager or
command line interface
For more information on the MantaRay NM Configurator applications and related procedures, see the
Configuration Management category in Operating Documentation browser.
4 Performance management
The aim of any performance management activity is to collect data to support the following activities:
Performance Manager+ is able to process the raw performance data into information on the network
performance. It helps improve network service quality and optimize network performance through re-
al-time performance management and KPI monitoring. Performance Manager+ also covers MantaRay
NM self-monitoring, and supports both ad-hoc and pre-defined reports.
Performance Manager+ provides a wide range of functionalities and reporting tools that address the
needs of all user groups, from troubleshooting to executive or management type of reporting.
It is web-based and does not need client-side software installations and updates.
Performance Manager+
The easy-to-use GUI allows real-time performance monitoring and advanced reporting on raw and ag-
gregated data.
Capabilities
• Performance Manager+ allows the creation of boards, containing charts or tables, or both, to vi-
sualize raw and aggregated PM data. Those boards can be shared among the users.
• Reporting area to access and visualize Nokia predefined content as well as user created content.
• KPI Manager to create, edit, share and delete KPIs.
• Scheduler to create and manage scheduled jobs for boards, store the results in a MantaRay NM
server on pre-defined or configured folders and, optionally, distribute them via e-mail in XLSX for-
mat.
• Drill in time and in network dimensions, as well as drill in KPIs.
• Export to XLSX.
• Administration Toolkit enables administrator to configure the storage period for each measurement
(raw or aggregated) and after the time has elapsed, the database tables are cleaned up.
Optional features
• Reporting Suites deliver comprehensive off-the-shelf reports and Key Performance Indicators
(KPIs) that meet the most common CSP needs. Pre-defined reports for the different network tech-
nological domains can be integrated on MantaRay NM framework and run in MantaRay NM Per-
formance Manager+ to support with needed information on traffic, mobility, resources, quality,
charging, and Quality of Service. With Reporting Suites, you can analyze the radio and core net-
works’ performance and capacity and drill into further detail on time level, report level, and on KPI
level. Reporting Suites cover all major network technologies and can be used for example, in net-
work dimensioning and optimization, troubleshooting, traffic trend analysis or service usage.
• Reporting Suite Self PM delivers a set of counters, KPIs and reports providing information about
PM operational performance and configuration (for the different PM Pipe layers) and also about
the network it is managing or monitoring.
• Thresholder and Profiler allows you to set and manage thresholds, for the Performance Indica-
tors (PIs) and Key Performance Indicators (KPIs). It regularly compares the KPI values with the
KPIs threshold and sends notifications when it is exceeded.
• CM Filtering and CM Aggregation support.
• Real-Time Performance Monitoring of PM counters and KPIs, including state view of the alarms.
Administration of Measurements
Administration of Measurements (AoM) enables launching and stopping several measurements in var-
ious network elements as one operation. The data in Administration of Measurements is synchronized
with the network performance management data configuration. It has features for processing mea-
surement configuration data in a central storage.
With Administration of Measurements you can manage plans, upload measurement configurations
from network elements and to check what kind of measurement types are supported in network ele-
ments via network overview. AoM templates can be used to pre-define some standard parameters,
which can then be used as a starting point for faster creation of plans. Measurement plans can be de-
fined for multiple network element types, for example, to create a single plan of all the elements of the
core network.
5 Security management
Security management covers all the aspects shown in the following figure:
Security management consists of user security, data security, software security, and network security.
It is based on Nokia security policy and guidelines that consist of customer requirements and interna-
tional security standards.
All security parts (user security, data security, software security, network security) are needed to guar-
antee the confidentiality, integrity and availability of the network.
In addition, MantaRay NM Security Log NBI (SLNBI) provides centralized and secure way to forward-
ing security logs to external Security Information and Event Management Systems (SIEM).
Confidentiality means ensuring that information is accessible only to those authorized to have access
and that the access rights remain uncompromised.
Integrity means the accuracy and consistency of information, and ensuring that the information has
not been changed without proper authorization and any changes to the information can be verified.
Availability means the accessibility of information for all authorized parties in a timely manner.
User security
User security consists of authentication, authorization, and user event logging. Authentication in Man-
taRay NM is managed by user management and authorization by permission management.
User security is about the mechanisms for controlling and logging user access to the system. The
identity of users is verified through user authentication at login, and user authorization ensures that
users can only access applications and perform tasks they are allowed to according to defined security
policies.
Data security
Data security consists of file system and database access control, encryption and integrity protection,
and secure key storage.
Data security in MantaRay NM means protecting the data in the file system and databases. The confi-
dentiality, integrity and availability of the data is ensured by access control, encryption, and different in-
tegrity protection methods.
Access control is needed to guarantee the availability of data and to prevent unauthorized users from
accessing it.
Data encryption is used for ciphering the most sensitive information, such as user account and permis-
sion data, certificates, and user event logs. For example, passwords are encrypted with hash functions
and the encryption keys are stored into a secure key storage.
Integrity protection mechanisms are used to make sure that the structure or content of the data is not
changed unintentionally. They include checksums and maintaining the parent-child information of data
records in a tree-structured database.
Software security
Software security includes verifying software upgrade and patching processes, file integrity checking,
and software signing.
Software security in MantaRay NM means verifying that operating system and third-party software up-
dates and patches as well as updating and patching processes, do not harm the operation of the sys-
tem. The process of ensuring sufficient software security is referred to as Security Vulnerability Moni-
toring (SVM). In practice it means gathering information on possible software-related threats and vul-
nerabilities, and updating software based on that information.
File integrity checking and signing of Java files are software-error preventive actions performed in
MantaRay NM, and integrity checking is also done in network elements.
The MantaRay NM system includes file integrity checking software. The signing of Java files is per-
formed by MantaRay NM software configuration management to prevent the Java code in the software
from being tampered with.
Network security
Network security includes traffic access control, monitoring and protection including encryption, integri-
ty protection, separation and filtering.
Network security in MantaRay NM means protecting the traffic in a network where MantaRay NM is
used. The confidentiality of the traffic is ensured by using different encryption protocols. These proto-
cols are not enabled by default but they can be taken into use through a process referred to as securi-
ty hardening. The use of traffic separation and filtering is also recommended.
The traffic can be segregated into the following types: traffic resulting from user access to MantaRay
NM and the managed network, traffic between MantaRay NM clusters, traffic between MantaRay NM
and network elements in the managed network, and traffic between MantaRay NM and upper layer
management systems.
Users can access MantaRay NM and the managed network with web browsers, Java clients and re-
mote terminals. VPN client applications are also used for access from the internet. All traffic is encrypt-
ed with SSL/TLS or SSHv2, and VPN traffic with IPsec.
Traffic between MantaRay NM clusters is protected with IPsec or TLS. It is recommended to use TLS
and SSHv2 for encrypting all connections between MantaRay NM and network elements in the man-
aged network. However, some network elements only support Telnet and FTP, and IPsec tunneling
must be used for these connections.
It is recommended to separate tier one (presentation tier) from tier two (business logic) and three (da-
ta tier) as well as to configure own network segments for network elements and higher OSS and use
firewalls to protect all user connections to MantaRay NM and the managed network. MantaRay NM´s
product firewall rules support this setup.
For more information on MantaRay NM security management principles, applications, and related pro-
cedures, see the Security Management category.
6 Network administration
The network administration area of MantaRay NM functionality comprises tools for centralized network
element software management, for backup and restore across network domains and multi-vendor sys-
tems, and for methods for software asset protection in both network elements and MantaRay NM.
Tracing gives the operator an instant method of observing a specific event. Tracing applications
(TraceViewer and Trace Expert) enable the operator to trace mobile equipment and mobile users,
minimize site visits and drive tests, use tracing data for optimizing the network set-up, and for trou-
bleshooting purposes.
Software Asset Pro- Software Asset Protection offers various methods and tools for moni-
tection toring license use in the network and distributing license keys to Man-
taRay NM and network. It is also a centralized repository for storing li-
censes.
Software Manager Software Manager (SWM) is used for reading software configuration,
creating software backups for specific network elements and restoring
their functionality efficiently. Software Manager enables operations to a
large number of network elements to a predefined schedule. With Soft-
ware Manager, the user can change network element software versions
and manage network element software packages archived in Man-
taRay NM. The backup and restore functions offered by Software Man-
ager are used for specific network elements, for example, radio con-
trollers in the radio network, and older core network elements, such as
MSC or CDS.
Trace Expert Trace Expert provides tracing for a LTE and 5G network elements. Us-
ingTrace Expert the operator can manage, collect, and view tracing da-
ta from all subscribers from the specific cell coverage area.
MSC Server Pool MSC Server Pool Monitor application can monitor Mobile services
Monitor Switching Center Server Pool load distribution.
Centralized License Centralized License Server (CLS) is an application that enables cen-
Server tralized, semi-automatic license management in the whole network. In-
stalled as external application, CLS is deployed in one MantaRay NM
regional cluster (RC) in customer networks. All other RCs are integrat-
ed to this one with CLS.
For more information on the network administration tools, see the Network Administration category in
Operating Documentation.
7 MantaRay NM administration
MantaRay NM, as a Network Management System, is designed to operate and maintain a complex
telecommunications network; therefore, its availability is crucial to operators. MantaRay NM adminis-
tration tools and procedures essentially help operators manage system reliability and stability. Man-
taRay NM administration includes aspects, namely hardware, operating systems, third-party software,
services, tools, interfaces, and MantaRay NM applications.
In MantaRay NM, system reliability and availability are ensured through the following system proper-
ties and features:
System administrators are the most privileged users of the MantaRay NM system and are responsi-
ble for setting up and maintaining the operating environment for other users. They carry out routine
maintenance tasks to ensure that the resource utilization is optimized, check network performance to
respond better to resource contention, and to do basic troubleshooting in case of service or network
problems.
MantaRay NM administration consists of a set of proprietary, as well as third-party tools for administer-
ing the MantaRay NM system. MantaRay NM system administrators manage the MantaRay NM hard-
ware, that comprises servers, storage devices, and network equipment such as switches and routers.
Additionally, MantaRay NM administrators administer the virtual infrastructure and its corresponding
resources. They also maintain the services that provide the run-time environment to manage network
elements. The components that need to be managed include basic services (such as the directory ser-
vice, database service, and domain name service) and southbound and northbound interfaces.
For more information on the MantaRay NM administration tools and related instructions, see the topics
under the MantaRay NM Administration category in Operating Documentation.
MantaRay NM Disaster Recovery keeps operator data safe by replicating it continuously from the pri-
mary site to the recovery site. The replicated data consists of database content, DNS data, LDAP da-
ta, and configured file system. In case of an emergency, a single command from the primary site or re-
covery site moves all the network management functionality to the recovery site in less than 30 min-
utes to ensure business continuity.
• Stressing MantaRay NM with a peak, burst or continuous load exceeding its capacity limits
• Error situations
Such an overload can be temporary or permanent. Prolonged, uncontrolled overload eventually caus-
es MantaRay NM outage, resulting in, but not limited to, critical data and/or functionality loss.
The aim of the overload protection is to automatically keep MantaRay NM system functioning during
the above-mentioned overload conditions by protecting the critical system resources. The overload
protection always aims at avoiding the worst-case scenario in MantaRay NM system. Therefore, de-
pending on the overload protection mechanism triggered, temporary loss of functionality or data may
be caused. For detailed information on specific overload protection mechanisms, see Overload protec-
tion in MantaRay NM in Administering MantaRay NM Overload Protection.
Note: MantaRay NM system operates with reduced capacity when overload protection is ac-
tive.
Note: System Monitoring includes Preventive Health Check, Log Browser, Symptom
Collector, and Configuration Checker. A system administrator can use functionalities through
command line tools in the VM hosts.
• Preventive Health Check runs a set of tests to verify MantaRay NM system status. Several reports
can be compared with each other. Preventive Health Check, essentially, performs a series of
checks to show the system health status. For example, after fresh installation, before or after
the upgrade. After running the checks, it generates a summary report that can be viewed in the
System Monitoring dashboard. For more information about Preventive Health Check, see About
Preventive Health Check in Preventive Health Check.
• Log Browser allows an administrator to browse the specified log files in the specified directories in
the MantaRay NM system. This helps to locate relevant log files on all virtual machines and mini-
mize the time used to search for the files. In addition, the administrator can limit the search scope
by specifying the criteria, such as time, time range, and keywords. You can also define browsing
scenarios targeting specific MantaRay NM applications or data flow between certain network ele-
ment types or technologies and MantaRay NM; for example, 3G PM flow or LTE PM flow. Subse-
quently, relevant logs can be packaged and downloaded for further analysis. For more information
about Log Browser, see About Log Browser in Log Browser.
• Symptom Collector allows an administrator to collect the symptom information in case of a system
failure. The information is collected from the predefined components or through the predefined
scenarios and can contain component version, configuration files, logs and traces, runtime
status, data from database, and LDAP data. Once the symptom information is collected, it can
be downloaded for further troubleshooting and analysis. For more information about Symptom
Collector, see Introduction to Symptom Collector in Symptom Collector.
• Configuration Checker monitors changes in the specified configuration files. In addition, the Con-
figuration Checker backs up the configuration files detecting changes and enables an adminis-
trator to see the change history of a specified configuration file. The list of configuration files can
be filtered by VM nodes, service name, regular expression, and last change timestamp. There-
fore, the desired configuration files can be found easily. For more information about Configuration
Checker, see Introduction to Configuration Checker in Configuration Checker.
• Customization Checker searches for MantaRay NM customizations in the running environment
and an administrator can take a snapshot of the system customizations. Two snapshots can be
compared with each other and Customization Checker provides a report on the comparison show-
ing the system customizations and details on them. Subsequently, system administrator can then
evaluate the impact of customizations on the MantaRay NM upgrade. For more information about
Customization Checker, see Introduction to Customization Checker in Customization Checker.
User workstations must fulfill Nokia hardware requirements. For more information, see Prerequisites in
Installing and Configuring MantaRay NM User Workstations.
In a virtualized infrastructure (VI), software is set up in such a way that it can operate independent-
ly from the underlying hardware. The physical resources of multiple machines are shared across the
whole infrastructure, and they act as a resource pool. In a VI, the physical hardware resources are di-
vided into smaller units, virtual machines (VMs), that have their own allocated virtual CPU and memo-
ry.
Note: VMware vSphere 6.5 no longer supports vSphere thick client to manage ESXi hosts
and vCenter Server Appliance (vCSA). From VMware vSphere 6.5 onwards, you must use:
MantaRay NM applications, mediations, and services running on a number of VMs are powered by a
hardware resource pool. Each VM is dimensioned and optimized for the service or services running in
it. In this way, the same MantaRay NM functions can be provided but with better high availability and
scalability options.
MantaRay NM functionalities are split into small VMs, which bring the following benefits:
To know the services in each VM, see Locating the right virtual machine for a service in Administering
MantaRay NM Virtual Infrastructure.
The MantaRay NM virtualized infrastructure is based on the VMware solution. The following list sum-
marizes the benefits of having a VI:
• Hardware can be utilized more efficiently with the virtual machine granularity.
• High availability is enhanced.
• Zero downtime during hardware maintenance is possible.
MantaRay NM configurations
MantaRay NM is available in different configurations where the number of VMs, the size of the hard-
ware resource pool, and the capacity they generate as a whole vary. For supported configurations, see
the MantaRay NM Node Architecture and Resource Plan document available in Discovery Center at
https://doc.networks.nokia.com. Accessing the documentation in the portal requires authentication.
Additionally, MantaRay NM Compact configuration is available and has the same virtual machine
(VM) layout as the MantaRay NM small configuration. The resource requirements for MantaRay NM
Compact configuration is same as that of MantaRay NM small configuration. However, MantaRay NM
Compact configuration allows only a restricted number of integrations for radio network elements and
subscribers in the core network.
For more information on technical requirements for the underlying hardware in the different MantaRay
NM configurations, see the MantaRay NM Node Architecture and Resource Plan document available
in Discovery Center at https://doc.networks.nokia.com. Accessing the documentation in the portal re-
quires authentication.
For more information on MantaRay NM system requirements, see the MantaRay NM Reference Con-
figuration documents available in MantaRay NM Technical Product Support documentation.
Scalability is an important feature of the virtual MantaRay NM environment since there are software
components that can be located on more than one VM, and conversely, one VM can contain more
than one software component.
If the load increases beyond a virtual machine’s ability to handle the load, then the software compo-
nent and/or virtual machine must be scaled to cope with the increased demand, which means that ad-
ditional resources (CPU and memory) need to be allocated to the virtual machine where the software
component is hosted. However, not all software components scale in a similar way, some software
components can benefit more through vertical scaling by adding resources than others.
Note: MantaRay NM supports scaling only from small to mainstream or large configuration
and from mainstream to large configuration.
For detailed information about all the supported hardware configurations, see
• 23R3-NM Node Architecture and Resource Plan document available in Discovery Center at
https://doc.networks.nokia.com. Accessing the documentation in the portal requires authentication.
• 23R3-NM Storage Array Disk Configuration Guide available in MantaRay NM Technical Product
Support documentation.
The following table lists the sample reference hardware configurations for HPE hardware supported in
MantaRay NM 23R3 release.
Compact
Hardware Con-
- Single Compact Small Large 3XL
figuration
Node
Servers 1 x HPE 2 x HPE DL360 For Gen 10: For Gen 10: For Gen 10:
DL360 Gen10
• 3 x HPE • 4 x HPE • 5 x HPE
Gen10 plus
Gen10* Gen10* Gen10*
Compact
Hardware Con-
- Single Compact Small Large 3XL
figuration
Node
Note:
For
2BCPH
load
mod-
el:
6x
HPE
Pro-
Liant
Gen10
Servers
CPU core 55 CPU 63 CPU core For Gen 10: For Gen 10: For Gen 10:
core
• 47 CPU • 127 CPU • 159 CPU
core core core
Note:
For
2BCPH
load
mod-
el
(HPE
Pro-
Liant
Servers):
191
CPU
core.
Memory (GB) 504 752 For Gen 10: For Gen 10: For Gen 10:
Compact
Hardware Con-
- Single Compact Small Large 3XL
figuration
Node
• 1512 • 2016 • 2520
Note:
For
2BCPH:
2256
Backup storage 4 x 3. 7 x 1.2TB SAS 11 x 1.8TB 10k 21 x 1.8TB 10k 47 x 1.8TB 10k
drives 84TB SAS SAS**** SAS**** SAS****
SSD local
disks*****
DCN switch Customer Use any one of the following DCN switch:
DCN
• HPE 5500-24G-4SFP HI Switch
Compact
Hardware Con-
- Single Compact Small Large 3XL
figuration
Node
tiv-
ity
to
the
serv-
er
with
re-
quired
VLANs.
Note: HPE Gen10 plus should be marked as Synergy 480 Gen10 plus.
*****Compact Single Node configuration uses local disks inside the server as the storage and does
not require any external SAN or ToR LAN switches.
Note:
• In case you want to add Optional VMs, you must ensure to add additional hardware
resources on top of the above listed configurations.
• Hardware configurations with legacy hardware are still supported. For detailed
information, contact Nokia Technical Support.
The following table lists the sample reference hardware configurations for Dell hardware supported in
MantaRay NM 23R3 release.
Hardware Configura-
Small Large 3XL
tion
Servers 3 x Dell R650xs 2p28c 4 x Dell R650xs 2p28c 5 x Dell R650xs 2p28c
CPU 512 GB RAM CPU 512 GB RAM CPU 512 GB RAM
Product Models
Product Models
• Cisco 2951
* The DCN solution still supports these hardware models even if they may have reached end-of-sale.
For information on system requirements, see Reviewing the system requirements in Integrating DCN
Backbone to MantaRay NM.
If the recommended DCN solution is not the desired solution, it is possible to use an open DCN solu-
tion. For requirements on the open DCN solution, contact Nokia Technical Support.
8.2.1.2 Firewalls
Product Models
The following tables list the operating system and the major third-party software components used in
the current release.
KEYCLOAK 21.1.1
EsperHA 3.5.0
ESXi 7.0u3i
ServiceMix 3.4
Note: Any changes to third party OEM software configuration, administrator must follow the
OEM guidelines provided by the third party OEM SW provider.
For information on the software requirements for the presentation tier or the user workstations, see
Prerequisites for software in Installing and Configuring MantaRay NM User Workstations.
MantaRay NM Start Page is a centralized launch pad for starting MantaRay NM applications. You can
start all the MantaRay NM applications which you have permission to launch from Start Page. Man-
taRay NM uses single sign-on (SSO) for accessing applications through MantaRay NM Start Page.
You can authenticate or log in only once, and then use the applications without re-authenticating.
When you log out, all MantaRay NM application sessions are terminated even if some application win-
dows still remain open.
Note:
• Some applications require a license, otherwise they are not visible on MantaRay NM
Start Page.
• The availability of applications depend on your MantaRay NM configuration. For more
information, contact your administrator.
• You can add more applications on the MantaRay NM Start page. For more information,
see Adding an application to Start Page in Configuring Start Page.
Configuration CM Analyzer
Configuration CM Editor
Configuration CM Reference
Monitoring Monitor
Monitoring TraceViewer
All MantaRay NM Java EE applications are installed on the WebSphere Application Server (WAS)
cluster when MantaRay NM is deployed. When a Java Rich Client is accessed for the first time, it is
downloaded by the Java Web Start (JWS) technology to the user workstation and launched for the
user. The next time it is accessed, the application is started from the local JWS cache. JWS checks
the version of the application every time it is launched on the user workstation and, if necessary, up-
dates the application from the WAS.
9 Adaptations
MantaRay NM provides unified operation and maintenance capabilities for managing network ele-
ments in core, radio and transport networks. To integrate network elements, MantaRay NM adaptation
function maps each network element release specific data to the MantaRay NM existing data models
and semantics. Adaptation files are a set of different configuration artifacts that provides MantaRay
NM the capability to manage a particular type of network elements and the different release versions
of the network elements.
Nokia provides three types of solutions for adaptation delivery and deployment:
• Static adaptation
• Dynamic adaptation
• MantaRay NM fast pass
The network element adaptation files are generated through Dynamic Adaptation application during
MantaRay NM runtime.
For more information about Dynamic Adaptation application, see About dynamic adaptation in Dynam-
ic Adaptation Help.
With MantaRay NM fast pass, it is possible to introduce support for a particular network element (NE)
release on top of one baseline MantaRay NM release from which MantaRay NM fast pass supports
this type of network element. MantaRay NM fast pass allows optimization of MantaRay NM upgrade
timing and helps accommodate late changes coming from the NE side. It also allows you to pilot new
network element releases, independent of MantaRay NM releases.
Note: The MantaRay NM and NE releases used in the graphic are just examples.
To activate the support of network element releases supported through MantaRay NM fast pass SPs,
you need to install the compatible MantaRay NM fast pass SPs using fast pass installation toolkit (FIT)
according to Compatibility of MantaRay NM and MantaRay NM fast pass service packages in Man-
taRay NM Release Changes.
For more information on how to activate or install the MantaRay NM fast pass SPs, see Overview of
MantaRay NM fast pass service package installation in Installing MantaRay NM fast pass Service
Packages.
MantaRay NM fast pass support for new NE releases includes, for example:
• fault management (depending on the NE technologies): new alarms including man pages and ba-
sic alarm processing
• performance management (depending on the NE technologies): new measurements and counters
including aggregation and reporting on raw counters
• configuration management (depending on the NE technologies): new objects and visualizing con-
figuration management parameters
• compatibility (depending on the NE technologies) for log, trace, software management, and soft-
ware asset monitoring (SWAM)
For support for advanced functionalities, upgrade to the new MantaRay NM release may be needed.
Examples of advanced support are:
• Site rehosting
• Configurator workflows
• Plan prepare functionality
• CM consistency checks
• Reporting Suites (predefined KPIs and reports)
10 Interfaces
MantaRay NM offers a rich set of open northbound interfaces that are compliant with standards, as
well as some proprietary ones implemented according to Nokia specifications.
3GPP XML Format PM Northbound In- 3GPP based interface. Used for integrating with a higher-level
terface performance management system.
CM Data Repository WebService API XML based interface. Enables access to the Configurator data-
base and to conveniently read and write CM data and CM
metadata in the actual, planned and reference configuration.
CM Operation Web Service API CM Operations web service API is a web service interface to-
wards Configurator.
CSV Interface for Configuration Man- Proprietary open CSV interface. Used for integrating with a
agement Data higher-level configuration management system.
Configuration Change Notification This interface sends notification to the registered REST end-
points whenever there are changes to the actual configuration
in Configurator.
E-mail Alarm Forwarding E-mail Alarm Forwarding Interface is designed to notify opera-
tors through e-mail by sending the alarm details to their e-mail
addresses using external e-mail sender programs.
Integration Express based 3GPP XML Integration Express based 3GPP XML Format PM NBI sup-
Format PM Northbound Interface ports the external Network Management System (NMS) collect-
ing 3GPP XML performance data file with SFTP protocol.
OSS/J Trouble Ticket Interface OSS/J certified interface. Used for integrating with a trouble
ticketing system.
NetConf/Yang Interface for Configura- NetConf/Yang interface allows to read network configuration
tion Management Data files in NetConf/Yang format and export of network configura-
tion in this format.
PM North Mediation Interface Open Measurement Standard interface. Used for integrating
with a higher-level performance management system.
RESTful Web Service Data Access RESTful Web Service Data Access API (RESTDA) provides
API an easy and flexible access to network operating and manage-
ment (O&M) data for operating tools, applications and dash-
boards.
Security Log NBI Security Log Northbound Interface (SLNBI) enables north-
bound interfaces for security logs from network elements man-
aged by MantaRay NM and from MantaRay NM nodes them-
selves. It is intended for administrators, who are supposed to
check and analyze audit logs collected from both network ele-
ments and MantaRay NM.
SNMP Northbound Interface SNMP based interface. Used for integrating with a higher-level
fault management system.
TMF 615 User Management This interface deals with the information exchange required
between the UMS-C and a Local User Management system
XML Based Inventory Data Export Proprietary open XML interface. Used for integrating with a
higher-level inventory management system.
XML Interface for Configuration Man- Proprietary open XML interface. Used for integrating with a
agement Data higher-level configuration management system.
Operations Support Systems interoperability initiative (OSSii) promotes OSS interoperability be-
tween different vendors' equipment. Operations Support Systems are typically integrated with equip-
ment from many network technologies and from several equipment vendors as well as the telecom
operator's business systems, making the OSS integrations complex and costly. OSSii reduces overall
integration costs and enables shorter time-to-market for operators.
In OSSii, each party commits to offer licensing of their proprietary OSS northbound interfaces to oth-
er parties and the scope of the interfaces cover fault management, performance management, config-
uration management and event/trace interfaces. MantaRay NM shares the following interfaces in the
OSSii scope: 3GPP XML Format PM NBI (an alternative PM NBI for XML (OMeS) Based Measure-
ment Data Export).
The lower-level element management systems or network elements can also be the third party to
which the integration is carried out with the help of an Integration Software Development Toolkit
(ISDK).
Figure 6: Southbound interfaces shows the various southbound interfaces, the mediations through
which they connect MantaRay NM to the network elements, and a brief description of each south-
bound interface. The description is also listed in the Table 13: Southbound interfaces.
MantaRay NM comes with a pre-integrated support for Nokia network elements and other Nokia man-
agement products. Multi-vendor integrations are carried out with the help of ISDK. Integration to a
third-party network element or EMS involves the creation of mediation and adaptation. With the help
of ISDK, MantaRay NM can integrate to the third-party EMS or network elements via the SSH, FTP,
SFTP, HTTP, HTTPS, SNMP (v1, v2c, v3), CORBA and SOAP interfaces.
Table 13: Southbound interfaces describes each of the southbound interfaces shown in Figure 6:
Southbound interfaces.
Southbound in-
Interface type Description
terface
NE3S/SNMP Proprietary open inter- This interface is used for integrating net-
face works elements and element managers to
MantaRay NM using the NE3S/SNMP me-
diation.
NE3S/WS Proprietary open inter- This interface is used for integrating net-
face work elements or element managers to
MantaRay NM using the NE3S/WS media-
tion. The distribution of NE3S/WS change
notifications and operation status respons-
es from agents to appropriate manager(s) is
supported on this interface.
Southbound in-
Interface type Description
terface
MML Proprietary open inter- This interface is used for integrating net-
face work elements or element managers to
MantaRay NM.
SCLI Proprietary open inter- This interface is used for integrating net-
face work elements or element managers to
MantaRay NM using the SCLI mediation.
ISDK Standard open inter- The ISDK southbound interface is used for
face integrating networks elements and element
managers to MantaRay NM using the FTP,
SNMP or CORBA mediations.
Plain SNMP Standard open inter- This interface is used for integrating Nokia
face network elements, element management
systems or multivendor tools to MantaRay
NM using Plain SNMP.
XoH Standard open inter- XoH (XML over HTTP) southbound in-
face terface uses XML as data encoding and
HTTP/HTTPs as the transfer protocol. It us-
es simple object access protocol (SOAP)
Southbound in-
Interface type Description
terface
in operations requested by NMSs from net-
work element or element management sub-
system.
SAM Proprietary open inter- The SAM southbound interface is used for
face integrating 5620 SAM and NSP to Man-
taRay NM using SOAP, JMS and SFTP in-
terface.
Ve-Vnfm-em eastbound interface ETSI NFV standard based interface. Nokia Telco Cloud Appli-
cation (NTCApp) provides an implementation of Ve-Vnfm-em
eastbound interface in MantaRay NM.
MantaRay NM can integrate with the European Telecommunications Standards Institute (ETSI) Net-
work Function Virtualization Management and Orchestration (NFV-MANO) systems over the Ve-Vnfm-
em eastbound interface. Nokia Telco Cloud Application (NTCApp) provides the implementation of the
Ve-Vnfm-em eastbound interface. With NTCApp, MantaRay NM exchanges information and collabo-
rates with Virtualized Network Functions Manager (VNFM) provided by Nokia or third-party ETSI-com-
pliant VNFMs.
11 User assistance
The User Assistance applications help you in finding useful information when you operate MantaRay
NM. User Assistance includes two applications:
For more information about the User Assistance applications, see Operating documentation and Ob-
ject Information Browser.
The online helps of MantaRay NM applications are available in the MantaRay NM Operating Docu-
mentation library. Each online help topic can be launched context-sensitively from the MantaRay NM
applications.
You can also find MantaRay NM documents in Support portal at https://customer.nokia.com. Access-
ing the documentation and software in the portal requires authentication. Documentation is available in
both browsable and downloadable format through Discovery Center at https://doc.networks.nokia.com.
Accessing the documentation in the portal requires authentication. For instructions on how to locate
MantaRay NM documents in Support portal, see Locating MantaRay NM documents in support portal
in Administering Operating Documentation.
Note: NetAct and MantaRay NM refer to the same product. Both product names are visible
in the software and operating documentation.
The MantaRay NM Operating Documentation application provides multilanguage support. After in-
stalling a non-English documentation package, the desired language can be selected.
Note: After you select a new language, if content is still displayed in previous language when
you open the Operating Documentation application, click on any other documentation to
switch the language.
Note: User settings, computer and application settings, and character encoding settings may
cause problems when copy-pasting content from operating documentation in PDF or HTML
format. PDF reader selection may also affect the copy-pasting functionality available for you.
For these reasons, special care is required if you copy-paste from the documentation. In
case of both PDF and HTML formats, always verify the pasted content.
Limitation Workaround
When an existing hyphen is left as the last A paid version of Adobe Acrobat is needed.
item on a row, it is omitted when copy-past- Free readers are unable to copy-paste hy-
ing from the PDF. This happens in all PDF phenation as is.
readers, and it is standard behavior in the
In the paid version of Acrobat, select the text
PDF format.
to be copied, and select Copy with format-
ting. This will retain the “soft hyphen” at the
end of lines.
Copy-pasting from HTML is a more reliable Always verify the pasted content.
option than copy-pasting from PDF, howev-
If pasted or saved content differs from what
er it is not completely unproblematic. There
you have entered, refer to the documenta-
may be cases where the computer or com-
tion of the 3rd party tools that you are using.
mand line settings in your environment could
affect copy-pasting from HTML.
The Operating Documentation application also supports Nokia network element documentation pack-
ages. You can install Nokia network element documentation packages in the Operating Documenta-
tion application so you have access to all the necessary documentation within a single documentation
browser view. For instruction on installing a Nokia network element documentation package in the Op-
erating Documentation application, see Managing Nokia network element documentation packages in
Administering Operating Documentation.
Note: After executing license related operations, you may wait for maximum one hour to see
documentations available in the Operating Documentation application.
The structure of the MantaRay NM operating documentation set is based on the ISO Telecommunica-
tions Management Network model, FCAPS framework, and a generic operator process model to sup-
port the operator workflows. FCAPS is an acronym for fault, configuration, accounting, performance,
and security managements. (MantaRay NM does not provide accounting management, so accounting
management documents are excluded.)
Information
Content scope Target audience
categories
Release The Release Changes category offers All personnel who need information on
Changes information on what has changed in the the changes in the MantaRay NM re-
product and operating documentation lease and their impact on the system.
between releases.
Information
Content scope Target audience
categories
NM fast pass Service Package
is activated.
System The System Overviews category offers All operator personnel working with Man-
Overviews a comprehensive and consistent high- taRay NM.
level description of MantaRay NM and
an overview to Single RAN management
with MantaRay NM.
Installation The Installation category provides in- Operator personnel responsible for user
structions for installing MantaRay NM workstation and application installa-
user workstations, element manager tion. Normally MantaRay NM installation
applications, and the Thresholder and teams perform the system installation for
Profiler application. It also provides the customers.
overviews of the MantaRay NM installa-
tion and upgrade procedures.
Integration The Integration category gives network • Operator personnel responsible for
element specific instructions for con- integrating network elements or low-
necting a network element to MantaRay er-level element management sys-
NM so that data communication works tems into MantaRay NM.
smoothly and supported network man- • Operator personnel responsible for
agement functions performed from Man- network configuration.
taRay NM work well on the network el-
ement. The integration process is de-
scribed end-to-end and can cover the in-
tegration of any equipment in the opera-
tor network, including Nokia network ele-
ments, third-party network elements, in-
termediate systems, third-party network
management systems, or operator de-
veloped systems.
Fault Manage- The Fault Management category pro- Operator personnel responsible for net-
ment vides information about network monitor- work monitoring.
ing and describes tools for detecting and
troubleshooting faults that cause disrup-
tions in network services.
Configuration The Configuration Management catego- Operator personnel responsible for plan-
Management ry describes the operations and applica- ning, configuring, optimizing, and trou-
tions used in network configuration man- bleshooting networks.
Information
Content scope Target audience
categories
agement for various technologies in the
radio and core networks.
Performance The Performance Management category Operator personnel responsible for net-
Management offers information on MantaRay NM's re- work performance.
porting solution, the applications for pro-
cessing, analyzing, and visualizing per-
formance data that is coming from differ-
ent sources. The information in the re-
ports can be visualized in graphical and
textual format providing a view of the
network performance.
Security Man- The Security Management category of- Operator personnel responsible for Man-
agement fers information on MantaRay NM's se- taRay NM security administration.
curity solution defined by Nokia's secu-
rity policy and guidelines that consist of
customer requirements and international
security standards.
Network Ad- The Network Administration category Operator personnel responsible for net-
ministration provides information about tools for: work administration tasks such as soft-
ware management, license manage-
• centralized network element soft-
ment, system-level trace, network ele-
ware management
ment backup and restore management.
• managing both network element and
MantaRay NM software licenses
• a system-level trace for a number
of Nokia network elements and sys-
tems
• network element backup and restore
across network domains and mul-
ti-vendor system
MantaRay NM The MantaRay NM fast pass Network El- • Operator personnel responsible for
fast pass Net- ement Administration category provides integrating network elements or low-
the network element version specific
Information
Content scope Target audience
categories
work Element information or operational instructions er-level element management sys-
Administration when using MantaRay NM applications tems into MantaRay NM.
to manage the network element versions • Operator personnel responsible for
that are supported through MantaRay network configuration.
NM fast pass Service Packages. • Operator personnel responsible for
managing network elements.
Note: This category is avail-
able only if at least one Man-
taRay NM fast pass Service
Package is activated.
MantaRay NM The MantaRay NM Administration cate- Operator personnel responsible for Man-
Administration gory offers information on how to man- taRay NM administration.
age system reliability that is provided by
For more information on the MantaRay
the hardware, operating systems, third-
NM administrator role, see Responsibil-
party software, services, tools, inter-
ities of a MantaRay NM system admin-
faces, and applications comprising Man-
istrator in MantaRay NM Administration
taRay NM.
Overview and Operations.
Northbound In- The Northbound Interfaces category of- • Operator personnel responsible for
terfaces fers information on aspects that a net- network configuration, planning, or
work operator needs to know about an integrating MantaRay NM into high-
interface when connecting, for example, er-level network management sys-
other network management systems or tem or service management sys-
related tools to MantaRay NM. tems.
• Operator personnel responsible for
MantaRay NM administration.
Legal, Safety The Legal, Safety and Privacy Informa- All operator personnel working with Man-
and Privacy In- tion category offers information on third- taRay NM.
formation party software licenses and contains re-
quired legal statements.
General Glos- The General Glossary category of- All operator personnel working with Man-
sary fers information on central concepts of taRay NM.
Information
Content scope Target audience
categories
telecommunications as well as the con-
cepts related to Nokia products.
Object Information Browser application provides multi-language support. After installing a non-English
documentation package, the desired language can be selected.
Note: After you select a new language, if content is still displayed in previous language when
you open the Object Information Browser application, log in to MantaRay NM again to switch
the language.
Object Information Browser application is under User Assistance category in MantaRay NM Start
Page.
• searching by data type (objects, measurements, and counters for performance management, pa-
rameters for configuration management and alarms for fault management) and by adaptation re-
lease.
• viewing the details about an individual object, measurement, counter, parameter, or alarm, based
on search results.
• viewing changes between two selected adaptation releases for objects, measurements, counters,
parameters, or alarms.
• exporting the search result for one adaptation release in Excel or XML format.
• notifying the real-time change of alarm data, dynamic adaptation data for performance manage-
ment, or licenses of the visibility for specific adaptation data.
12 User experience
• display of Graphical User Interface (GUI) elements for the supported applications.
• display of FM MAN pages, CM parameter descriptions, and PM counter descriptions for the sup-
ported adaptations.
Note:
To enable the Multilanguage support feature, see Enabling Multilanguage support in En-
abling Multilanguage Support.
Area Application
Note:
• Once language selection is done for the user and MantaRay NM applications are
launched, the language selection is passed to the applications. The applications then lo-
calize and display the contents in the selected language.
• If there are any MantaRay NM applications open and the language is changed in the
MantaRay NM Start Page, then close all the applications and re-launch to view the local-
ized content.
• If the language selection for the user is changed in the User Management application,
log out and log in to MantaRay NM again to view the localized content.
The following tables lists the limitation of localization in some of the fault management tools.
12.1.2.1.1 Monitor
Navigation
Tools Restrictions
Path
Object (Ob- File → New • Dynamic names such as metadata from database are not local-
ject creation → Object... ized.
wizard )
Group Ex- Tools → Per- The tools launched from the main menu items are not localized.
plorer mission Man-
agement
Role Explorer
Scope Editor
Network View
Scope Editor
Object Ex- Tools → Man- • For Tree Table View, column header is not localized. Tooltip for
plorer aged Objects column header is partial based on the localization file availabili-
ty.
View Editor Tools → Man- • Tooltip for the top toolbar icons are not localized.
aged Objects
→ View Ex-
plorer
In Objects tab,
Navigation
Tools Restrictions
Path
• Column header is not localized.
• Tooltip localization for column header is partial based on the lo-
calization file availability.
Alarm Details Tools → The values of the following attributes are not localized:
Monitoring
• Probable Cause
Desktop →
• Severity
Alarm Details
• Alarm Type
Property Right-click any • All attributes and their values are displayed in English only.
Sheet alarm, choose • Attribute tool tip is localized based on the existence of metadata
Properties localization.
The following tables lists the fault management tool translation support.
• If a table column has content in multiple languages, sorting may not be applicable in Alarm
Reports Dashboard applications.
• Table column values display is dependent on how they are stored in the database. The values are
not localized in Alarm Reports Dashboard applications.
Alarm Re-
Navigation
ports Dash- Restrictions
Path
board
Search Start Page • Search alarm criteria values are not localized.
Alarms tab → Monitoring
→ Alarm Re-
ports Dash-
board
Schedule Start Page • Schedule Search criteria values are not localized.
Search tab → Monitoring • Task Name supports only English and numerics.
for New and → Alarm Re-
• In the View Report page, the words in the graph such as
Modify pages ports Dash-
COUNT, MAJOR, MINOR and WARNING are not localized.
board →
Schedule
Search
Configuration → CM • Parameters are not localized, but parameter descriptions are localized
Operations Manager • Below table headers are not localized:
→ Tools → Multipoint
– Table headers for MSS elements (Pools → Core → Actuals →
Configuration Assis-
MSS)
tant
– Table headers for MGW elements (Pools → Core → Actuals →
MGW)
For more information on NE data and Radio data, see Modifying the
scope of simple column set in Managing MSS Multipoint Configuration.
• While Adding MSS to a pool in Managing Adjacencies, the parameters
in the Basic Parameters and Advanced Parameters tab are not local-
ized.
Configuration → CM • In tools such as Workflow Engine where the content is based on exter-
Operations Manager nal files (for example, XML), localization is not provided, but could be
delivered as translation of XML file.
• Operation Statuses, Operation Feedbacks (including feedback types
used for filtering), Operation Types are not localized.
• The operation names (Upload, Provision, Generate MML, Compare,
Audit Plan, Delta Creation, Command Execution, TrxLoopTest) in
the feedback dialog title text are not localized.
• CM view and Operation List drop-down lists in the Rehosting tool are
not supported.
Configuration → CM Localization is not done for the Workflow Engine GUI. If you want to localize
Operations Manager the content, contact Nokia Technical Support.
→ Tools → Workflow
Engine...
Configuration → CM • In the Search and Modify panel, the MO states any, created from
Editor network, non-operational, and operational are not localized.
• The drop-down values for Group, State, and Owner for a plan are not
localized.
• Default parameter sets drop down.
Measurement and counter presentation names Report Creator, KPI Creator, Saved Reports
Export to excel
• Trace Collection Entity parameters - default names and details of the parameters.
• Activation parameters - names, details and values of the parameters.
• Protocols content - protocols names, list of messages as well as corresponding procedures and
procedure codes (if available).
• Default profile names.
• Default profile descriptions.
• Domain, technology, and trace target type profile components.
• Table menus.
12.1.3 Limitations
On the MantaRay NM Start Page, when the preferred language is changed from English to Chinese or
vice versa, untranslated message is displayed for 1 to 2 seconds before the localized message is dis-
played.
Note:
• Once the screen reader support is provided, you can directly start to use MantaRay NM
with a screen reader application.
• MantaRay NM supports WAI-ARIA roles, states and properties, allowing the usage of
wide variety of screen reader applications that support ARIA definition.
• User experience between different browsers and screen reader tools may vary.
Area Application
12.2.2 Limitations
There are some limitations for screen reader support in Operating Documentation application and Ob-
ject Information Browser:
• Graphics that are not critical for instructions do not necessarily have alternative texts. This
includes, for example, some screenshots.
• Rich media contents have limited support for screen reader applications. When the focus is moved
to the progress bar, screen reader applications cannot read the correct information of the progress
label.
• After clicking a hyperlink in Operating Documentation Help, you are directed to the corresponding
section. The screen reader application may not read the information of the section because of
compatibility issue.
• For Objects in Object Information Browser, when you move the focus to any cell in the Hierarchy
column under the Table tab and click the link, the Hierarchy tab with the object details does not
open sometimes.