NetAct System Overview

NetAct™ 8 EP1

NetAct System Overview DN09136965 Issue: 2-0

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is“ and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS I N T H I S D O C U M E N T AT AT I O N O R F O R A N Y D A M A G E S , I N C L U D I N G B U T N O T L I M I T E D T O S P E C I A L , D I R E C T, T, I N D I R E C T , I N C I D E N TA TA L O R C O N S E Q U E N T I A L O R A N Y L O S S E S , S U C H A S B U T N O T L I M I T E D T O L O S S O F P R O F I T, T, R E V E N U E , B U S I N E S S I N T E R R U P T I O N , B U S I N E S S O P P O R T U N I T Y O R D A TA TA , T H A T M A Y A R I S E F RO M T H E U S E O F T HI S DO CU M E N T O R T H E I N F O R MA T I O N I N I T. NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Solutions and Networks 2014/7/22. All rights reserved.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, offer, please contact us at Nokia Solutions and Networks for additional information.

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is“ and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS I N T H I S D O C U M E N T AT AT I O N O R F O R A N Y D A M A G E S , I N C L U D I N G B U T N O T L I M I T E D T O S P E C I A L , D I R E C T, T, I N D I R E C T , I N C I D E N TA TA L O R C O N S E Q U E N T I A L O R A N Y L O S S E S , S U C H A S B U T N O T L I M I T E D T O L O S S O F P R O F I T, T, R E V E N U E , B U S I N E S S I N T E R R U P T I O N , B U S I N E S S O P P O R T U N I T Y O R D A TA TA , T H A T M A Y A R I S E F RO M T H E U S E O F T HI S DO CU M E N T O R T H E I N F O R MA T I O N I N I T. NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Solutions and Networks 2014/7/22. All rights reserved.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, offer, please contact us at Nokia Solutions and Networks for additional information.

NetAct System Overview

Contents 1 Introduct Introduction ion to NetAct. NetAct.................................................................................................................................... ................................................................................................................................... 4 1.1 Fault Fault management................................................................................................................................... management..................................................................................................................................... 7 1.2 Optimization...............................................................................................................................................8 1.3 Configuration management....................................................................................................................... management....................................................................................................................... 9 1.4 Performance management........................................................................................................................9 1.5 Security Security management............................................................................................................................. management............................................................................................................................. 10 1.6 Network administration............................................................................................................................12 1.7 NetAct administration............................ administration.............................................................................................................................. .................................................................................................. 13 2 NetAct deployment and configurations...................................................... configurations...................................................................................................... ................................................ 14 2.1 NetAct virtualized architecture architecture................................................................................................................ ................................................................................................................ 14 2.2 NetAct hardware......................................................................................................................................17 2.2.1 User User workstations........................................................................................................................... workstations........................................................................................................................... 19 2.2.2 NetAct network connectivity........................................................................................................... connectivity........................................................................................................... 19 2.2.2.1 DCN DCN solution.......................................................................................................................... solution.......................................................................................................................... 19 2.2.2.2 Firewalls..................................................................................................................................20 2.3 Third-party Third-party software....................................................................................................... software................................................................................................................................ ......................... 20 2.4 Start Page............................................................................................................................................... Page............................................................................................................................................... 22 3 Interfaces........................................................................................................................................................ Interfaces.. ...................................................................................................................................................... 24 3.1 Nor thbound thbound interfaces.............................................................................................................................24 3.2 Southbound Southbound interfaces.................................................................................................. interfaces............................................................................................................................ .......................... 25 4 User Assistance.............................................................................................................................................31 Assistance.............................................................................................................................................31 4.1 Operating Operating documentation........................................................................................................................ documentation........................................................................................................................ 31 4.1.1 Operatin Operating g Documenta Documentation tion Browser Browser.................................................................................................31 .................................................................................................31 4.1.2 NetAct NetAct operating documentation information architecture..............................................................31 4.2 Object Information Browser............. Browser.................................................................................................................... ....................................................................................................... 36

3


Introduction to NetAct

1 Introduction to NetAct Nokia Solutions and Networks NetAct is a new generation network management system for multi-vendor and multi-technology networks. NetAct serves both as a network management system and as an element management system. Net Act offers a wide range of unified operation and maintenance capabilities for network elements in core, radio and transport networks. It consists of many tools for handling a number of network elements and expanding networks. It is designed for handling an increase in both complexity of the network and the amount of traffic and data. With NetAct 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, NetAct provides several open northbound interfaces (standard-compliant and proprietary ones) that offer to operators a unified management 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 received by NetAct or generated in NetAct and the information required by the upper level management systems. In addition to NetAct applications there are also standalone tools that are dedicated to specific management functions and provide advanced management features, for example, NetAct Audit Trail for security management, and NetAct Advanced Configurator for configuration management. These standalone tools need a dedicated hardware platform and are sold separately. For more information, refer to the operating documentation of each tool. NetAct provides the following management functions: • Fault management • Optimization • Configuration management • Performance management • Security management • Network administration • NetAct administration Figure 1: The NetAct system with management functions, applications, and interfaces

Issue: 2-0

DN09136965

4



The following table shows the management functions and corresponding applications for managing the network and NetAct itself. Management function

NetAct application

Function description

NetAct Start Page folder

Fault management

Alarm Reports Dash-

Manages reports for Fault

Monitoring

board

Management.

Monitor

Monitors the network and

Monitoring

provides access to further tools.

Issue: 2-0

DN09136965

5


Management function


NetAct application



TraceViewer

Supports network monitor-

Monitoring

ing and troubleshooting. Optimization

Optimizer

Optimizes operational

Optimization

GSM, WCDMA and LTE networks. Configuration man-

CM Analyzer

Checks parameter consis-

agement

Configuration

tency. Edits configuration parame- Configuration

CM Editor

ter data. CM Operations Man-

Manages provisioning and

ager

upload operations.

CM Reference

Manages reference config-

Configuration

Configuration

urations. Site Configuration Tool Manages repository for the

Configuration

site configuration data. SON Scheduler

Manages AC and SON

Configuration

Scheduler settings. Performance manage- Administration of Mea- Configures measurements ment for network elements or surements

Reporting

managed objects. Performance Manager Manages performance re-

Reporting

ports for telecommunications, IT/IP networks and services. Security management

Certification Authority

Provides and requests new Security certificates.

Network Element Ac-

Manages and administers

cess Control

service users of Network

Security

Element(s). Centralized Network Element User Management (CNUM) enables users to log in to a network ele-

Issue: 2-0

DN09136965

6


Management function


NetAct application



ment with their own user account. User Management

Manages and administers

Security

users and user groups. Network administra-

License Manager

tion

Manages licenses for NSN

Configuration

network elements and software. Software Asset Moni-

Reports features usage for Reporting

toring

network elements and Net Act.

Software Manager

Manages software configu-

Configuration

rations. NetAct administration

Adaptation Manager

Deploys adaptations.

Administration

AddOn Manager

Deploys AddOns.

Deployment

Map Administrator

Optimizer Map Administra- Administration tor

SNMP FM Mediator

Configures parameters

Administration

of SNMP FM mediation, agent supervision, trap reliability, and alarm synchronization. SNMP PM Mediator

Configures parameters of

Administration

performance measurement result polling in SNMP PM mediation. Table 1: Supported management functions and applications in NetAct

1.1 Fault management In NetAct, fault management enables you to manage alarms from various network elements. 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 situations. Each fault is represented as an alarm and this alarm is send to NetAct. NetAct Monitor with versatile monitoring tools enables you to:

Issue: 2-0

DN09136965

7



• collect, process, store, and display alarm information from the network in real-time. • visualize the network topology. • detect and analyze faults in network elements. In addition, NetAct Monitor enables you to collect alarm information from the external systems. Alarms from third-party equipment are collected, viewed, and stored in NetAct Monitor together with all the other network alarms. For more information, see the Fault Management category in Operating Documentation.

1.2 Optimization The radio network optimization process usually takes place when the monitored performance drops below the set targets, when a periodical tuning task is to be started or when there is need to optimize the behavior of new network elements in the network. Measurements are used for analyzing the network and service performance development against set targets. A detailed analysis is performed to find the reasons behind decreased performance and to select the right corrective actions. In this phase, the relations between performance indicators and element parameters are analyzed. After the analysis phase, the configuration parameter settings are optimized and the set quality criteria are checked. When the corrections are verified and implemented into the network, the quality monitoring cycle starts from the beginning.

Figure 2: Optimization cycle in NetAct

Issue: 2-0

DN09136965

8



For more information on radio network optimization, see the Optimization Overview and Operations document.

1.3 Configuration management NetAct configuration management is used for configuring and managing your radio and core network. You can make, for example single parameter changes, manage hardware data or launch new technologies and services. You can streamline and automate your configuration management processes and tasks, and react to network changes and demands. With the NetAct Configurator applications you can perform network-wide configuration management operations. NetAct Configurator provides one centralized data storage and the same tools and processes for all configuration management operations. For more information on the NetAct Configurator applications and related procedures, see the information under the Configuration Management category in Operating Documentation Browser.

1.4 Performance management The aim of any performance management activity is to collect data to support the following activities: • Verifying the physical and logical configuration of the telecommunications network. • Monitoring continuously how the network functions. • Legalizing potential problems as early as possible. • Providing optimum services to mobile subscribers. Depending on how the performance management applications use the collected data, they can be divided into two main types: performance monitoring and performance reporting applications. Performance monitoring is online-oriented and provides you with near real-time information on the network. Performance monitoring applications generally use shorter measurement output intervals because faster reaction is needed in severe problem cases for which a 24-hour interval would be too long. The outputs of performance monitoring applications are mainly used as additional information in solving problem cases for which no alarm information is available. Performance monitoring rules are intelligent threshold rules and can be calculated after the measurements are stored in the database. In cases where pre-defined threshold values are crossed, so-called threshold alarms may be generated to notify the operator about possible degradation of network performance. Performance reporting is offline-oriented and provides information on what happened in the network over a certain period of time. Performance reporting applications mainly rely on performance indicators and produce reports, which you can use, for example, when you are troubleshooting, planning, or optimizing the network. NetAct provides the following applications for performance management:

Issue: 2-0

DN09136965

9



• Performance Manager : application for creating reports based on performance management data, network configuration data, fault statistics, and service-related information from the entire network. • Administration of Measurements: the application is used for configuring measurements for network elements or managed objects. • Thresholder and Profiler : application for setting and managing thresholds and profiles for the performance indicators (PIs) defined with other performance management tools.

1.5 Security management Security management covers all the aspects shown in the following figure:

Figure 3: Security management

Security management consists of user security, data security, software security, and network security. It is based on NSN security policy and guidelines that consist of customer requirements and international security standards. All security parts (user security, data security, software security, network security) are needed to guarantee the confidentiality, integrity and availability of the network. 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 Net Act 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

Issue: 2-0

DN09136965

10



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 NetAct means protecting the data in the file system and databases. The confidentiality, integrity and availability of the data is ensured by access control, encryption, and different integrity 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 permission 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 NetAct means verifying that operating system and third-party software updates and patches as well as updating and patching processes, do not harm the operation of the system. The process of ensuring sufficient software security is referred to as Security Vulnerability Monitoring (SVM). In practice it means gathering information on possible software-related threats and vulnerabilities, and updating software based on that information. File integrity checking and signing of Java files are software-error preventive actions performed in Net Act, and integrity checking is also done in network elements. The NetAct system includes file integrity checking software. The signing of Java files is performed by NetAct 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, integrity protection, separation and filtering. Network security in NetAct means protecting the traffic in a network where NetAct is used. The confidentiality of the traffic is ensured by using different encryption protocols. These protocols are not en-

Issue: 2-0

DN09136965

11



abled by default but they can be taken into use through a process referred to as security 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 NetAct and the managed network, traffic between NetAct clusters, traffic between NetAct and network elements in the managed network, and traffic between NetAct and upper layer management systems. Users can access NetAct and the managed network with web browsers, Java clients and remote terminals. VPN client applications are also used for access from the internet. All traffic is encrypted with SSL/TLS or SSHv2, and VPN traffic with IPsec. Traffic between NetAct clusters is protected with IPsec or TLS. It is recommended to use TLS and SSHv2 for encrypting all connections between NetAct and network elements in the managed 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 (data tier) as well as to configure own network segments for network elements and higher OSS and use firewalls to protect all user connections to NetAct and the managed network. NetAct´s product firewall rules support this setup. For more information on NetAct security management principles, applications, and related procedures, see the Security Management category.

1.6 Network administration The network administration area of functionality of NetAct comprises tools for centralized network element software management, for backup and restore across network domains and multi-vendor systems, and for managing both network element and NetAct software licences. The applications are designed to help to deploy new software releases, security patches, enhancements to existing releases, and fault fixes. NetAct provides the following applications for network administration: NetAct Software Manager

With Software Manager the user can manage network elements software configuration; change network elements software; manage network element software packages archived in NetAct.

NetAct Software Asset Moni-

With Software Asset Monitoring Client the user can

toring

create monitoring modules for particular technology; view and export monitoring reports based on software feature usage; set an invoicing period (monthly or quarterly).

Issue: 2-0

DN09136965

12


NetAct License Manager


NetAct License Manager is a tool for managing hardware and software licenses in the NetAct system and in the telecoms network.

Table 2: NetAct network administration tools For more information, see the Network Administration category in Operating Documentation.

1.7 NetAct administration As a network management system designed to operate and maintain a complex telecommunications network, NetAct needs to be up and running always. NetAct administration is essentially managing system reliability that is provided by the hardware, operating systems, third-party software, services, tools, interfaces, and applications comprising NetAct. In NetAct, system reliability is ensured through the following basic features: • High availability in the hardware configuration, virtual infrastructure, and select software components to eliminate single points of failure in power, disk, memory, CPU, network connectivity, virtual machine, or service availability • Load balancing, which takes care of the distribution of server load within a WebSphere Application Server cluster and the distribution of resources within the virtual infrastructure • Online and offline backup and recovery solutions using vSphere Data Protection and the NetAct Backup Tool • System Self-monitoring for internal fault and performance management • Preventive Health Check, which is a tool that verifies the NetAct System status System administrators are the most privileged users of the NetAct system as it is their responsibility to set up and maintain the operating environment for other users. They carry out routine maintenance tasks to ensure that resource utilization is optimized, check network performance to better respond to resource contention, and do basic troubleshooting in case of service or network problems. NetAct administration consists of a set of proprietary as well as third-party tools and instructions for the administrators of the NetAct system. NetAct system administrators manage the NetAct hardware, which consists of three main items: servers, storage devices, and network equipment such as switches and routers. Along with this role, they 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 service, database service, and domain name service to name a few) as well as southbound and northbound interfaces. For more information on the NetAct administration tools and related instructions, see the topics under the NetAct Administration category in Operating Documentation Browser.

Issue: 2-0

DN09136965

13


NetAct deployment and configurations

2 NetAct deployment and configurations

2.1 NetAct virtualized architecture NetAct is connected to the network elements through southbound interfaces, and to the user workstations and to users’ external systems through northbound interfaces. The data communication network (DCN) backbone provides the infrastructure that connects network elements to NetAct and different NetAct sites. User workstations must fulfill Nokia Solutions and Networks requirements. For more information, see User workstations. In a virtualized infrastructure (VI), software is set up in such a way that it can operate independently 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 divided into smaller units, virtual machines (VMs), that have their own allocated virtual CPU and memory.

Issue: 2-0

DN09136965

14



Figure 4: NetAct architecture in a virtualized infrastructure, logical view

Compared to the previous NetAct releases, there are no longer dedicated hardware roles. Instead, NetAct 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 NetAct functions can be provided but with better high availability and scalability options. To know the services in each VM, see Locating the right virtual machine for a service in Administering NetAct Virtual Infrastructure.

Issue: 2-0

DN09136965

15



The NetAct virtualized infrastructure is based on the VMware solution. The following list summarizes the benefits of having a VI: • Hardware can be utilized more efficiently with the virtual machine granularity. • High availability is enhanced. • Scalability can be targeted more accurately. • Zero downtime during hardware maintenance is possible. • The virtualized infrastructure allows new ways of implementing disaster recovery. • NetAct migration can be carried out without additional servers. • Downtime during software upgrade and migration is minimized. Scalability in virtualized infrastructure Scalability is an important feature of the virtual NetAct 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 component and/or virtual machine must be scaled to cope with the increased demand. However, not all software components scale in a similar way: • Some software components are designed to scale horizontally, which means that additional virtual machines need to be provisioned in order to enable the software component to distribute its load. Horizontal scalability is enabled by placing software components behind load balancers. • Other software components scale better vertically, which means that additional resources (CPU and memory) need to be allocated to the virtual machine where the software component is hosted. NetAct configurations NetAct is available in small (S), mainstream (M), and large (L) configurations, where the number of VMs, the size of the hardware resource pool, and the capacity they generate as a whole vary. The following table shows the resource allocation for the underlying hardware in each standard NetAct configuration. Note: The db, arc, and redo disk sizes vary with different storage models. In the table, the figures on virtual disk spaces apply when the system uses the EMC VNX storage. Virtual disk space for db and nfs backup data (GB)

NetAct configuration

Total Total amount vCPU of alloon all cated VMs vRAM (vCPU*) (GB)

Total virtual disk spaces on VMs (GB)

Virtual disk space on redo (GB)

VirtuVirtuVirtual disk al disk al disk space space on space on on nfs db (GB) arc (GB) global (GB)

Virtual disk space for VM backup data (GB)

S

69

135

1555

66

750

1125

300

3000

3000

M

122

272

2005

66

1500

2250

400

3000

3000

Issue: 2-0

DN09136965

16




Total Total amount vCPU of alloon all cated VMs vRAM (vCPU*) (GB)

L

174

428

Total virtual disk spaces on VMs (GB)

VirtuVirtuVirtuVirtual disk al disk al disk al disk space space space on space on on nfs on redo db (GB) arc (GB) global (GB) (GB)

Virtual disk space for VM backup data (GB)

Virtual disk space for db and nfs backup data (GB)

2540

66

3000

3000

2500

3750

560

* Each processor core that is physically present with Hyper-Threading enabled is equal to 2 vCPU. Table 3: Technical requirements for the underlying hardware in the different NetAct configurations

2.2 NetAct hardware NetAct is delivered on three configurations: S, M, and L using HP blade servers. NetAct configuration

Server model

Number of servers

Primary storage

Backup storage

DCN switch/ router

S

HP BL460c Gen8

4

VNX Small:

VNX Backup:

2x HP

VNX5200:

VNX5100:

1x Intel E5-2658

3x100GB

6x2TB NL-

eight core proces-

SSD SSF +

SAS LFF

2x Cisco 2951

sor

9x600GB SAS

VNX Medium:

VNX Backup:

2x HP

VNX5200:

VNX5100:

2x Intel E5-2620

5x100GB

6x2TB NL-

six core processor

SSD SSF +

SAS LFF

23 VMs

1p8c 48GB

5500-24G-4SFP HI /

SFF + 13x1TB

48GB memory

NL_SAS SFF 2x300GB 15K SAS internal disks 2x10GbE LAN; fc controller (8G) M 32 VMs

HP BL460c Gen8

6

2p6c 64GB

5500-24G-4SFP HI / 2x Cisco 2951

13x600GB

64GB memory

SAS SFF + 2x300GB 15K SAS

19x1TB NL_

internal disks

SAS SFF

2x10GbE LAN; fc controller (8G)

Issue: 2-0

DN09136965

17




Server model

Number of servers

Primary storage

Backup storage

DCN switch/ router

L

HP BL460c Gen8

6

VNX Large:

VNX Backup:

2x HP

VNX5200:

VNX5100:

2x Intel E5-2658

5x200GB

6x2TB NL-

eight core proces-

SSD SSF +

SAS LFF

sor

17x600GB

40 VMs

2p8c 128GB

5500-24G-4SFP HI / 2x Cisco 2951

SAS SFF +

128GB memory

27x1TB NL_ 2x300GB 15K SAS

SAS SFF

internal disks 2x10GbE LAN; fc controller (8G) Table 4: Standard hardware configurations in a new NetAct delivery Hardware used with new deliveries • Servers – HP BL460c Gen8 with E5-2620, E5-2658, or E5-2670 (with NEBS configurations) processors • Storage equipment – EMC VNX5200 – HP 3PAR 7200 – EMC VNX5100 (backup storage) • DCN – Switches: HP 5500-24G-4SFP; HP 5900 (NEBS compliant); open DCN solution – Router: Cisco 2951 – Firewall: Juniper SRX240H Other supported hardware • Servers – HP BL460c G6 with E5540 processors • Storage equipment – HP EVA4400 without SecurePath software – HP P6300, HP P6350 – EMC CX4-120, EMC CX4-240 – EMC VNX5300 – Open SAN concept • DCN external switches

Issue: 2-0

DN09136965

18



– HP Procurve 2810G-24 – Catalyst 2960G-24TC-L (GigaEthernet) – Catalyst 3750G-24TS-1U (GigaEthernet)

2.2.1 User workstations Presentation tier hardware is typically a standalone user workstation. NOTICE: Nokia Solutions and Networks does not provide the presentation tier hardware. The following table provides the dimensioning guidelines for the presentation tier hardware. Product

User workstation

Type

A standard office PC, workstation, or laptop

CPU

Single-core IA-32/64 compatible

RAM

2 GB+

Display resolution

1600 x 1200

Free disk space

2 GB

Table 5: Hardware dimensioning guidelines for the presentation tier

2.2.2 NetAct network connectivity The recommended network equipment is listed in the following sections.

2.2.2.1 DCN solution The recommended DCN backbone solution consists of the following hardware. Product

Models

Switches

For the small configuration: • HP 5500-24G-4SFP HI Switch with 2 interface slots (JG311A), HP Procurve 2810-24G* • HP 5900 (NEBS compliant) For the mainstream configuration: • HP 5500-24G-4SFP HI Switch with 2 interface slots (JG311A), HP Procurve 2810-24G*

Issue: 2-0

DN09136965

19



Product

Models • HP 5900 (NEBS compliant) For the large configuration: • HP 5500-24G-4SFP HI Switch with 2 interface slots (JG311A), GigaEth: Catalyst 3750-24* • HP 5900 (NEBS compliant)

Routers

For the mainstream configuration:

(optional if there are no 2G network elements)

• Cisco 2951 For the large configuration: • Cisco 2951

* The DCN solution still supports these hardware models even if they may have reached end-of-sale. Table 6: Recommended DCN backbone hardware For information on system requirements, see Reviewing the system requirements in the document Integrating DCN Backbone to NetAct . If the recommended DCN solution is not the desired solution, it is possible to use an open DCN solution. For requirements on the open DCN solution, contact Technical Support.

2.2.2.2 Firewalls Product

Models

Firewall (optional)

Juniper SRX240 routers and software

Table 7: Firewall hardware

2.3 Third-party software If any third-party software is needed, the required licenses are provided by Nokia Solutions and Networks and cannot be obtained by the operator. NOTICE: The Oracle 11g version includes several optional extra-cost Enterprise Manager features. Only Oracle Diagnostic Pack, Oracle Tuning Pack, and Oracle Advanced Compression licenses are included in NetAct. Other optional extra-cost features may not be used.

Issue: 2-0

DN09136965

20



The following tables list the operating system and the major third-party software components used in the current release. Operating system

Version

Red Hat Enterprise Linux

6.5

Table 8: Operating system

Software component

Version

EsperHA

3.5.0

Oracle Client

11.2

Oracle 11g Enterprise Edition (EE)

11GR2

389 Directory Server

1.2

WebSphere Application Server Network Deployment (ND)

8.0

VMware vSphere Enterprise Plus

5.5

VMware vCenter Server Standard for vSphere

5.5

ILOG Jviews

8.8

Marben OSI stack

-

Windows Server

2008R2

ICA Connection Server

Citrix XenApp 6. 5

Table 9: Major third-party software components The following table lists the software requirements for the presentation tier or the user workstations. Software component

User workstation requirement

Operating system

Any operating system that is able to support the software components listed in this table.

Web browser

Windows 7 or 8 environment (64-bit): • Microsoft Internet Explorer 9.0 (64-bit) • Latest 32-bit version of Mozilla Firefox Linux environment (any 64-bit distribution with GNOME 2):

Issue: 2-0

DN09136965

21



Software component

User workstation requirement • Latest 64-bit version of Mozilla Firefox

Java Runtime Environment (JRE)

Windows 7 or 8 environment (64-bit): • Java 7 Update 51 (64-bit) Note: Some applications may require the 32-bit version of Java 7 Update 51. When using any version of Java 7 Update 51, you must install the server certificates before launching NetAct Monitor. For more information, see Installing NetAct server CA certificate for NetAct Monitor launch. Linux environment (any 64-bit distribution with GNOME 2): • Java 6 Update 45 (64-bit)

Adobe Flash Player

Adobe Flash Player 11.1.0 or higher

ICA Client (optional)

XenApp 6.5 compatible

Table 10: Software requirements for the presentation tier

2.4 Start Page The web browser on the user workstation is used for connecting to Start Page. Start Page is a centralized launch pad for starting NetAct applications. You can start all the NetAct applications which you have permission to launch from Start Page. NetAct uses single sign-on (SSO) for accessing applications through Start Page: you log in to Start Page only once and can use the applications without re-authenticating. When you log out, all NetAct application sessions are ended even if some application windows still remain open. Note: Some applications require a license, otherwise they are not visible on Start Page.

Start Page folder

Application

Administration

Adaptation Manager

Administration

Map Administrator

Administration

SNMP FM Mediator

Administration

SNMP PM Mediator

Issue: 2-0

DN09136965

22



Start Page folder

Application

Configuration

CM Analyzer

Configuration

CM Editor

Configuration

CM Operations Manager

Configuration

CM Reference

Configuration

License Manager

Configuration

SON Scheduler

Configuration

Site Configuration Tool

Configuration

Software Manager

Deployment

AddOn Manager

Monitoring

Alarm Reports Dashboard

Monitoring

Monitor

Monitoring

TraceViewer

Optimization

Optimizer

Reporting

Performance Manager

Reporting

Administration of Measurements

Reporting

Software Asset Monitoring

Security

Certification Authority

Security

Network Element Access Control

Security

User Management

User Assistance

Object Information Browser

User Assistance

Operating Documentation

Table 11: Start Page default applications All NetAct Java EE applications are installed on the WebSphere Application Server (WAS) cluster when NetAct 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, updates the application from the WAS.

Issue: 2-0

DN09136965

23


Interfaces

3 Interfaces

3.1 Northbound interfaces Northbound interfaces are used for integrating NetAct into higher-level systems, which are usually service management level systems for post-processing and possible provisioning of raw or processed network data that is collected into NetAct. Higher-level systems can be either NSN or third-party management systems. NetAct offers a rich set of open northbound interfaces that are compliant with standards, as well as some proprietary ones implemented according to NSN specifications. NetAct provides the following northbound interfaces. Open northbound interface

Description

3GPP Release 6 CORBA BulkCM

3GPP based interface. Used for integrating with a higher-level

Northbound Interface

configuration management system.

3GPP Release 6 CORBA FM North-


bound Interface

fault management system.

3GPP XML Format PM Northbound In-


terface

performance management system.

ASCII Alarm Forwarding Northbound

ASCII FM interface. Used for integrating with a higher-level fault

Interface

management system.

CM Data Repository WebService API

XML based interface. Enables access to the NetAct Configurator database and to conveniently read and write CM data and CM metadata in the actual, planned and reference configuration.

CSV Interface for Configuration Man-

Proprietary open CSV interface. Used for integrating with a

agement Data

higher-level configuration management system.

E-mail Alarm Forwarding

E-mail Alarm Forwarding Interface is designed to notify operators through e-mail by sending the alarm details to their e-mail addresses using external e-mail sender programs.

Interference Matrix Open Interface

Proprietary open CSV interface. Used for exporting interference matrices created by Optimizer to external systems and for importing interference matrices from external systems to Optimizer.

Issue: 2-0

DN09136965

24


Interfaces

Open northbound interface

Description

OSS/J Trouble Ticket Interface

OSS/J certified interface. Used for integrating with a trouble ticketing system. Open Measurement Standard interface. Used for integrating

PM North Mediation Interface

with a higher-level performance management system. SNMP Northbound Interface

SNMP based interface. Used for integrating with a higher-level fault 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.

Table 12: Northbound interfaces

3.2 Southbound interfaces Southbound interfaces are used for integrating lower-level systems and network elements into NetAct. Lower-level systems can be either Nokia Solutions and Networks or third-party element management systems or mediators. NetAct comes with a pre-integrated Nokia Solutions and Networks system which provides the following southbound interfaces for multivendor integrations. Southbound interface

Interface type

Description

NE3S/SNMP

Proprietary

This interface is used for in-

• Administration of

open inter-

tegrating networks elements

Measurements

face

and element managers to NetAct using the NE3S/SNMP mediation.

Used for

Network elements • BIG-IP • CMD

• fault management

• FIU 19E

• performance man-

• FlexiISN

agement

• Flexi NG 2.0 • Flexi NG 2.1 • FTFA • iNUM • LIG • NBG/Flexi Content Optimizer • One-EIR • One-MNP

Issue: 2-0

DN09136965

25


Southbound interface

Interfaces

Interface type

Description

Used for

Network elements • PowerHopper Vario • Q1 Agent (FM and PM) • NetViewer (FM and PM) • SAAM • SADM • Tellabs (FM) • Traffica

NE3S/WS

Proprietary



open inter-

tegrating network elements

Measurements

face

or element managers to Net Act using the NE3S/WS mediation. The distribution of NE3S/WS change notifications and operation status responses from agents to appropriate manager(s) is supported on this interface.

• CSCF • DRA

• Audit Trail

• DXA

• basic configura-

• Flexi NG 3.0

tion management

• Flexi NG 3.1

(topology)

• Flexi NS

• configuration management • fault management • hardware management • performance management • software management • user management

• HSS-FE • IMSHW • Load Balancer • MGW • NEBR • NT HLR FE • One-NDS • Open MGW • PCC • PCS-5000 • TIAMS

NWI3

Proprietary

Connects network man-


open inter-

agement systems or ele-

Measurements

• Femto BTS

face

ment managers with net-

• certificate man-

• Flexi Direct

work elements. Uses CORBA for management communication, and (S)FTP and HTTP(S) for bulk data transmission.

agement • configuration management

DN09136965

• Flexi LTE BTS • Flexi WCDMA BTS


• mcRNC

• hardware man-

• NEMU

agement

Issue: 2-0

• AXC

• RNC

26



Interfaces

Interface type

Description

Used for • integration data

Network elements • Ultra BTS

upload • license management • performance management • software management • system level trace (events) • user event log management (Audit Trail) • user management • symptom data collection • NEBR 3GPP CORBA Standard

3GPP CORBA south bound

• Basic configura-

open inter-

interface mediates manage-

tion management

face

ment operations and noti-

(topology)

fications between element


management systems (applications such as Radio commander, Switch Commander) and NetAct. MML

Proprietary



• BSS

open inter-


Measurements

• CDS

face

or element managers to Net Act using the MML adaptation.

• Audit Trail

• Flexi NS

• backup and re-

• HLR

store • configuration management • element management • license management

• HSS-FE • MSC • MGW • NT HLR FE • Open TAS • PCC • SGSN

• network element user management

Issue: 2-0

DN09136965

27



Interfaces

Interface type

Description

Used for

Network elements

• software management • system level trace • time management NX2S

Standard

NE3S/FTP XML Solution

open inter-

Suite Southbound Interface

face

(NX2S SBI) provides a well-

• Integration data management

• Tellabs • PowerHopper Vario

defined interface based on

• Q1 Agent

the extensible markup lan-

• NetViewer

guage (XML) which supports FTP file-based processes. Q3

Standard

Q3/MML mediation System

open inter-

Component (SC) implements

face

south mediation interfaces to an OSI based network element. In addition to that this mediation is also used to support different fragments for IP based network elements. Q3/MML mediations are mainly developed on top of Mediation Framework and are designed to be adaptable to multiple OSS Systems.


• BSS

Measurements

• CDS

• Audit Trail

• Flexi NS

• backup and re-

• Flexi NS SGSN

store • configuration management

• HLR • MGW • MSC

• element management • fault management • license management • network element user management • performance management • software management • system level trace • time management

SCLI

Proprietary


open inter-


face

or element managers to Net Act using the SCLI mediation.

• configuration management • element management

• BSS • Flexi NG • HSSFE • NTHLRFE • Open MGW • PCC

Issue: 2-0

DN09136965

28


Interfaces


Interface type

Description

(S)FTP

Standard

Connects network manage-

open interface

Used for

Network elements

• configuration man-

• BSS

ment systems or element

agement (hard-

• CDS

managers with network ele-

ware manage-

• CMD

ments. Uses FTP interface

ment)

• CSCF

for bulk data transmission.


• DRA

• integration data

• HLR

upload • license management • performance management • system level trace • dynamic adaptation

• HSS-FE • MGW • MSC • Flexi NS • FlexiISN • Load Balancer • NT HLR FE • One-AAA • One-EIR • One-MNP • SAAM • SADM • SGSN • TIAMS • Tellabs (PM)

SNMP

Standard


open inter-

tegrating Nokia Solutions

tion management

• CMS-3000

face

and Networks network ele-

(topology)

• CMS-9000

ments, element management systems or multivendor tools to NetAct using the SNMP mediation.

• basic configura-

• BIG-IP


• Cisco


• PKI INSTA

agement

• EMC CX4-120 and VNX5100 for One-NDS • FirstMile200i • Generic Agentbased OneAAA • Generic Agentbased One-NDS • HP Hardware for One-NDS One-

Issue: 2-0

DN09136965

29



Interfaces

Interface type

Description

Used for

Network elements EIR One-MNP and One-AAA • IBM Bladecenter for One-NDS • Infoblox DNS • Juniper Junos • LIG • Movius Mereon 6000 Media Server • NetViewer • nSigniaSGW • Oracle (SUN) and Fujitsu Hardware for One-NDS • SAMServer • SBC • SignalwareLB • TP5000

XoH

Standard

XoH (XML over HTTP)


• CDS

open inter-

southbound interface uses


• HLR

face

XML as data encoding and HTTP/HTTPs as the transfer protocol. It uses simple ob-

agement • system level trace

• MSC • Open TAS

management

ject access protocol (SOAP) in operations requested by NMSs from network element or element management subsystem. Table 13: Southbound interfaces

Issue: 2-0

DN09136965

30


User Assistance

4 User Assistance

4.1 Operating documentation NetAct operating documentation supports daily network management operations. It is available on NetAct user workstations in a browsable format. It is also available in a browsable format and as downloadable PDFs through Nokia Solutions and Networks Online Services, accessible at https:// online.portal.nsn.com (which requires authentication). The online helps of NetAct applications are available in the NetAct operating documentation library. Each online help instruction can be launched context-sensitively from the NetAct applications.

4.1.1 Operating Documentation Browser The electronic NetAct customer documentation library is accessible through the Operating Documentation application. NetAct Operating Documentation Browser is a web-based browser solution in the NSN system products' customer documentation libraries.

4.1.2 NetAct operating documentation information architecture The NetAct operating documentation contains system descriptions, network and system reference documents, and instructions needed for network management operations and maintenance tasks. The structure of the NetAct operating documentation set is based on the ISO Telecommunications Management Network model, FCAPS framework, and a generic operator process model to support the operator workflows. FCAPS is an acronym for fault, configuration, accounting, performance, and security managements. (NetAct does not provide accounting management, so accounting management documents are excluded).

Issue: 2-0

DN09136965

31


User Assistance

Figure 5: Information architecture of NetAct operating documentation

Information categories

Content scope

Release

Release Changes category offers informa-

• Release highlights

Changes

tion on what has changed in the product

• Functionality changes

Content structure

and operating documentation between releases.

• Supported network element changes • Operating documentation changes • Functionality Comparison between OSS5 and NetAct 8

NetAct Sys-

NetAct System Overview offers a compre-

• Introduction to NetAct

tem Overview

hensive and consistent high-level descrip-

• Supported Network Elements

tion of what NetAct is.

• Interfaces • NetAct Deployment and Configurations • User Assistance

Installation

Installation category offers information on

There is no specific heading structure for

NetAct installation and upgrade procedures

this category. The needed topics are listed

on high level so that the customer can know in alphabetical order. what phases and tasks are involved. Normally NSN installation teams perform the installation for the customers.

Issue: 2-0

DN09136965

32


User Assistance


Content scope

Content structure

Integration

Integration category gives network element


specific instructions for connecting a net-


work element to NetAct so that data com-

in alphabetical order.

munication works smoothly and supported network management functions performed from NetAct work well on the network element. The integration process is described end-to-end and can cover the integration of any equipment in the operator network, including NSN network elements, 3rd party network elements, intermediate systems, 3rd party network management systems, or operator developed systems. Fault Manage- Fault Management category offers three ment types of information: • descriptive information explaining what the fault management area is about and what operations it offers for man-

• Fault Management Overview and Operations • Fault Management Operating Procedures • Fault Management Helps

aging a telecoms network; • instructive information giving step-bystep instructions on performing operating procedures related to fault management; • the help documents for NetAct applications related to fault management. Optimization

Optimization category offers three types of

• Optimization Overview and Operations

information:

• Optimization Operating Procedures

• descriptive information explaining what

• Optimization Helps

the functional area is about and what operations it offers for managing a telecoms network; • instructive information giving step-bystep instructions on performing operating procedures related to optimization; • the help documents for NetAct applications related to optimization. Configuration

Configuration Management category offers

Management

three types of information:

Issue: 2-0

DN09136965

• Configuration Management Overview and Operations

33



User Assistance

Content scope

Content structure

• descriptive information explaining what the configuration management area is about and what operations it offers for

• Configuration Management Operating Procedures • Configuration Management Helps

managing a telecoms network; • instructive information giving step-bystep instructions on performing operating procedures related to configuration management; • the help documents for NetAct applications related to configuration management. Performance

Performance Management category offers

Management

three types of information: • descriptive information explaining what the performance management area is about and what operations it offers for

• Performance Management Overview and Operations • Performance Management Operating Procedures • Performance Management Helps

managing a telecoms network; • instructive information giving step-bystep instructions on performing operating procedures related to performance management; • the help documents for NetAct applications related to performance management. Security Man-

Security Management category offers three

agement

types of information:

• Security Management Overview and Operations

• descriptive information explaining what the security management area is about and what operations it offers for man-

• Security Management Operating Procedures • Security Management Helps

aging a telecoms network; • instructive information giving step-bystep instructions on performing operating procedures related to security management; • the help documents for NetAct applications related to security management.

Issue: 2-0

DN09136965

34


User Assistance


Content scope

Network Ad-

Network Administration category offers

ministration

three types of information:

Content structure

• descriptive information explaining what

• Network Administration Overview and Operations • Network Administration Helps

the network administration area is about and what operations it offers for managing a telecoms network; • instructive information giving step-bystep instructions on performing operating procedures related to network administration operation; • the help documents for NetAct applications related to network administration. NetAct Admin- NetAct Administration category offers three istration types of information: • descriptive information explaining what the NetAct administration area is about and what operations it offers for man-

• NetAct Administration Overview and Operations • NetAct Administration Operating Procedures • NetAct Administration Helps

aging NetAct; • instructive information giving step-bystep instructions on performing operating procedures related to NetAct administration operation; • the help documents for NetAct applications related to NetAct administration. Troubleshoot-

Troubleshooting category offers information

The troubleshooting cases are grouped by

ing

on how to recover from fault situations and

the type of network management functions

how to avoid operational problems.

as listed below. • Application Launch • Fault Management • Configuration Management • Performance Management • Network Administration • NetAct Northbound Mediations • NetAct Southbound Mediations • NetAct Administration

Issue: 2-0

DN09136965

35



User Assistance

Content scope

Content structure The troubleshooting cases under each management function are listed in alphabetical order.

Northbound

Northbound Interfaces category offers in-

The topics are grouped by interface proto-

Interfaces

formation on aspects that a network op-

cols in alphabetical order.

erator needs to know about this interface when connecting, for example, other network management systems or related tools to NetAct. Legal, Safety

Legal, Safety and Environmental Informa-


and Environ-

tion category offers information on third-


mental Infor-

party software licenses and contains other

in alphabetical order.

mation

statements that are legally required.

• Environmental Information • Microsoft Software License Terms • Open Source Software Licenses • Statement on Limitations to Operations Related to NetAct Database • Use and Installation of Third-Party Software in NetAct

General Glos-

General Glossary category offers informa-

The needed topics are listed in alphabetical

sary

tion on central concepts of telecommunica-

order.

tions as well as the concepts related to the products of Nokia and NSN. Table 14: Information categories of NetAct operating documentation

4.2 Object Information Browser Object Information Browser is a web application that is accessed through a web browser running on the user's workstation. It is a browser designed for browsing and exporting adaptation data information and adaptation release changes from NetAct. This information includes objects, measurements and counters for performance management, parameters for configuration management and alarms for fault management for adaptations deployed in NetAct. Object Information Browser application is under User Assistance category in NetAct Start Page.

Issue: 2-0

DN09136965

36


User Assistance

Figure 6: Object Information Browser in NetAct Start Page

The basic functions provided by Object Information Browser include: • searching by data type (objects, measurements and counters for performance management, parameters for configuration management and alarms for fault management) and by adaptation release • 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 or licenses of the visibility for specific adaptation data

Issue: 2-0

DN09136965

37

NetAct System Overview

Recommend Documents